[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-929?page=co...
]
Norman Franke commented on HBX-929:
-----------------------------------
Cool, that works and without modifying the HBM template files. I sill needed to modify the
pojo ones to add an import, since I want the Base classes in a different package for
easier mainteance (i.e. I can delete the whole folder in Eclipse and regenerate without
worrying about deleting stuff I wrote.)
A field to specify a package for a base class could take the place of a checkbox, and if
non-empty, would do this. That would really ease modelling.
While you are at it, maybe generate DAO's using this pattern:
http://www.hibernate.org/328.html of generics indead of separate classes per table.
Enable base class generation
----------------------------
Key: HBX-929
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-929
Project: Hibernate Tools
Issue Type: New Feature
Components: datagen, hbm2java
Affects Versions: 3.2beta9
Environment: Hibernate 3.2.3
Reporter: Norman Franke
Fix For: 3.2beta10
Using the reverse engineering features, I'd like to be able to have it generate base
classes (e.g. TableNameBase) and yet tell Hibernate to use the parent class, e.g.
TableName. I read that one can add a meta attribute "generated-class" to do this
but (a) there is no way to make this happen via the Eclipse Plugin and (b) even if one
modifies the template to add it, it doesn't seem to pick it up (it does end up in the
resulting hbm.xml files.) The Run... GUI can't seem to generate Java files from the
hbm.xml files either, so one must reverse engineer anyway, which is another annoyance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira