AppFuseSupport |
|
| Your trail: |
Difference between
version 118
and
version 117:
| At line 165 changed 1 line. |
| * Do I have to use XDoclet to generate my *.hbm.xml files? Is it possible to override a single hbm.xml file and create it by hand? |
| * __Do I have to use XDoclet to generate my *.hbm.xml files? Is it possible to override a single hbm.xml file and create it by hand?__ |
| At line 168 changed 6 lines. |
| If you have an @hibernate.class tag on a POJO - the hibernatedoclet |
| will generate the mapping file into build/dao/gen. If you have a |
| mapping file (*.hbm.xml) file for your POJO in the src/dao/**/model/* |
| directory, it will *overwrite* the generated version. If you don't |
| want to worry about the two conflicting - just remove the @ sign from |
| @hibernate.class in your POJO and put your *.hbm.xml file in the model |
| If you have an @hibernate.class tag on a POJO - hibernatedoclet will generate the mapping file into build/dao/gen. If you have a mapping file (*.hbm.xml) file for your POJO in the src/dao/**/model/* |
| directory, it will __overwrite__ the generated version. If you don't want to worry about the two conflicting - just remove the @ sign from @hibernate.class in your POJO and put your hbm.xml file in the {{model}} |
| At line 176 changed 2 lines. |
| No build.xml modification are need for this to work. The |
| "package-dao" target will include these mapping files: |
| No build.xml modification are need for this to work. The "package-dao" target will include these mapping files: |
| At line 184 changed 3 lines. |
| If you want to get rid of the hibernatedoclet process, you can do that |
| - but make sure and run it first - and then copy all of the generated |
| hbm.xml files into your {{model}} directory. |
| If you want to get rid of the hibernatedoclet process, you can do that- but make sure and run it first - and then copy all of the generated hbm.xml files into your {{model}} directory. |
Back to AppFuseSupport,
or to the Page History.
|