Hi,

I am seeing some odd behaviour with hbm2java.

- hibernate version 2.12
- extensions 2.02.

I am using <meta> tags in my hbm file in order to create base classes (i.e. plumbing/linking etc., occurs in super class). This seemed (from what I have read) to be common practice and worked well... until I required a class with a <composite-element > within a set. I have a simplified mapping below...



There are two <meta> tags in the class definition.

If I omit both of them, the classes are generated as you would expect.

If I insert just the first meta tag to force the generator create 'test.BaseTest', it will only generate one class (test.BaseTest) and the contents of the file are what you would expect in test.Member. i.e. test.BaseTest is generated with properties of memberProperty and user, with id, name, and members nowhere to be seen.

If I insert the both meta tags, specifying that the composite-element class to be test.Member, the problem is solved and the two classes are generated correctly.

So what is the big deal you ask? Well, it seems that I can not use the hbm file with both meta tags, as the standard hibernate parser barfs on it. For example, if I try to generate DDL, I get the following....



It would seem the dtd being used by the standard parser does not allow meta tags in composite-elements.

- Steven

first thing: put an inherit="false" on your <meta>'s you don't want to "flow down" to embedded parts in your hbm.xml file.

second thing: yes - there seems to be a "bug" in the hibernate-mapping dtd about <meta> ;(

third thing: simple to fix - just add them to the dtd and use it ;)
(and add a jira for it so we remember to fix it)

Man - I though we caught all of the extra meta tags in the DTD :-(

yeah - they seem to creep up on us! :)

Thanks.... I had fixed my local dtd to get around the problem but was not aware of the inherit="false" trick. I will submit something to Jira.