Hi, I'm very new to Hibernate, I've been playing with hbm2java (from hibernate-extensions-2.1.2) and found something that seems to be a bug.

In my .hbm.xml file I have defined the attribute "package" for "hibernate-mapping". Every class has an attribute "name" non-qualified and the .java files are correctly generated.

But for every many-to-one tag I have to define the attribute "class" as the fully-qualified classname in order to avoid an incorrect "import" in the generated .java file. The problem is that IMO hbm2java shouldn't generate that "import" line because if either:
1) the class is not qualified it means it should be in the same package (and the import is not needed)
or 2) the class is fully-qualified and the import is not needed too.

Am I wrong or is any parameter to avoid this effect? I have a workaround for this, but I would prefer to have only one reference for the package in the .hbm.xml.

Best regards,
Jose M Beas

hmm - I *think* the CVS version of hbm2java honor's the package attribute.

Please check there - and if it still fails make a jira for it (with a failing, but complete hbm.xml file)

Hi, I have exactly the same problem, i'm using hbm2java from hibernate-ext dated 22 november 2004.
Is there any solution to this?
thanks