- This topic has 2 replies, 3 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
It would be nice if…
1) the Export through Hibernate… dialog did not require that the package and source folder be set every time.
2) the Export through Hibernate… dialog could generate code for multiple tables at a time.
3) when I refactored the name of a method/class, the associated hbm.xml file was updated.
This one is a biggie, but I’d really like to have the ability to define relationships when I do the export. The GUI could be a grid below Key Field Class which would list all columns that reference external entities which the following columns in the grid:
Include? Col Name Rel. Type
Include? would be a checkbox to specify whether the relationship is included in the mapping file.
Col Name would be the name of the column
Rel. Type would be a picklist with hibernate’s relationship types: one-to-one, many-to-one, one-to-many (maybe broken down into map, list, set and bag), many-to-many (broken down as one-to-many is).
This could grow to be quite complex, but it would be a really helpful start!
Hi…
I have been watching the developing of ME since 2.7 version. You guys are working hard, I can see that. By the way, 3.8b2 it´s incredable… But, I would like to make a sugestion/feature request, based in my needs/reality.
Today my resource files (ie hibernate mapping, libs/jars, common jsp pages) are placed in a non-java(resource/Simple project) project in eclipse. These resources are used through many projects… Well, ME 3.8b2 doesn´t suport to create hibernate mapping files in this particular kind of project. I dont know if i´m being clear or naive, but from who is “outside” is just a “if condition” do be changed/removed (like if projets are java, web, ejb). Do you think this can be done, even though a patch (without having to wait the new version)? ❓ Or can I modify any file to allow this particular need? ❓
Thank you very much for you attention.
🙂
Clayton Fonseca
Brazil
