I am trying to use JAXB to auto-generated the elements defined in the hibernate-mapping-3.0.dtd file; but I get the following error:


I am able to auto-generate the hibernate-mappings.dtd file successfully. The only difference between these two files that causes these errors are the following:
hibernate-mapping-3.0.dtd:
vs hibernate-mapping.dtd:
And hibernate-mapping-3.0.dtd: vs hibernate-mapping.dtd:


Its seems there is a problem when specifying both children elements "formula" and "type". But when specifying either or via the "Or" operator, all works fine.

You can download a example JAXB2 project at https://maven-jaxb2-plugin.dev.java.net/docs/guide.html. Look for a link called, "See the sample JAXB2 plugins project for example.".

Any suggestion is much appreciated!

Thanks!

Ok after further investigation, I have narrowed it down to the following snippets of xml in the hiberante-mapping-3.0.dtd:



I believe the above xml snippets is why a I am getting the aforementioned errors.

Is this a bug in the hibernate-mapping-3.0.dtd file?
Is there anybody out there that can help me with this issue?

I'm not sure what you are asking about.

You refer to both hibernate-mapping-3.0.DTD and hibernate-mapping.DTD - which one is it ?

And why is it a bug in the DTD that jaxb can't generate mappings for it ? The DTD is valid, are you
sure it isn't jaxb that are problematic ?

I referred to both of the DTDs to show how they differ in regards to the formula and type children elements. If you do a quick compare of the two DTDs, you will find that these two children elements are always used with an "OR" operator in hibernate-mapping.dtd. In the hibernate-mapping-3.0.dtd these two children elements are always used with an "OR" operator, except for lines 380 and 728. Which brings me to the question is there a typo or an over site in the hibernate-mapping-3.0.dtd file at the lines 380 and 728? Should these two lines use a "OR" operator like so on line 728 of hibernate-mapping-3.0.dtd file: instead of what is actually there; which is . And on line 380 of hibernate-mapping-3.0.dtd file: instead of what is actually there; which is

I am able to use JAXB to generate the java objects for hibernate-mapping.dtd, because it uses the "OR" operator for the formula and type children elements. However because of how the hibernate-mapping-3.0.dtd file does NOT use the "OR" operator, as described above; I am not able to generate the java objects via JAXB.

I understand that the hibernate-mapping-3.0.dtd is syntactically valid; but I want to know is it logically correct in not using the "OR" operator as described above? If you say it is logically correct, then I will look for an alternative solution. One alternative solution would be to just change my local copy of the hibernate-mapping-3.0.dtd to use the "OR" operators as described above. If I opt for this solution, do you see anything wrong with that? Another solution is to work with JAXB and its custom binding features to solve the original error. Either one of these works for me, but I didn't want to start changing stuff without first understanding the root problem.

Thanks!

No, first you want a sequence of column and formula with an optional last type element. The current one is correct.



It is semantically correct what is in the DTD.

May I ask why you want to JAXB hibernate mappings ?

I'm curious which approach you took to solve this problem. I am also looking to generate java files from the hibernate 3.0 dtd and encounter this error.

The reason I am trying to do it is because we have a very large hbm.xml (around 180 class elements) and we are in the process of converting these definitions to JPA annotated classes. One way I thought I could do this was to write a custom script to parse each class element in the hbm.xml to generate a rough outline for the JPA annotated class (I'm not expecting perfection, but something to eliminate the bulk of the grunt work).

Anther suggestion that I found on the web was to use Hibernate's SchemaExport tool and then the Hibernate Pojo Generator that generates Hibernate annotated classes from the DB schema. From what I can tell though it looks like the Hibernate Pojo Generator is limited to a MySql dialect and I need to use an Oracle dialect (difference being the support of ID vs. Sequence support).

Anyways, were you ever able to generate Java classes from the hibernate-mapping-3.0.dtd using JAXB?

I found an alternate solution to my specific problem. JBoss has a Hibernate-tools Eclipse plugin which includes an hbm2java tool. This tool can be configured to generate EJB3 (JPA) annotated classes from hbm.xml files and is good enough for the purposes I am looking for.