Community
Participate
Working Groups
Paul Fullbright is working the management of the persistence.xml file for the 0.5 release. I would also like to see the management of a generated orm.xml file. Per a discussion on the Dali forum, Paul suggested writing an Enhancement request. Here's the wording from my original post on the subject: "What I am looking for is the ability to generate the orm.xml from the annotated source. The annotated source is what I would be using for development. I would tweak the annotations until I got the desired functionality. But, once I go into production with this "Persistence Unit" with all of the associated classes and jars, I don't want to have to modify source and re-build just to get some different behaviour. At this point, I would like to deal with xml files to modify the configuration. It would be great if Dali could generate the "base" xml files for me. I've done the annotations in the code, now create the corresponding xml file(s) so that I know what I have as the base configuration (template, if you will)." Hope this is a sufficient description. Thanks. Kevin
Good day Dali, I guess you guys know this already but it seems to me that Dali 0.5 basically ignores the settings in orm.xml. There doesn't seem to be a way to tell it to store settings in orm.xml either. My use case involves JPA-enabling EMF-generated POJIs so I don't want to use the annotation approach, nice though it is. Thanks, Adrian Price. (In reply to comment #0) > Paul Fullbright is working the management of the persistence.xml file for the > 0.5 release. I would also like to see the management of a generated orm.xml > file. Per a discussion on the Dali forum, Paul suggested writing an > Enhancement request. Here's the wording from my original post on the subject: > > "What I am looking for is the ability to generate the orm.xml from the > annotated source. The annotated source is what I would be using for > development. I would tweak the annotations until I got the desired > functionality. But, once I go into production with this "Persistence Unit" > with all of the associated classes and jars, I don't want to have to modify > source and re-build just to get some different behaviour. At this point, I > would like to deal with xml files to modify the configuration. > > It would be great if Dali could generate the "base" xml files for me. I've > done the annotations in the code, now create the corresponding xml file(s) so > that I know what I have as the base configuration (template, if you will)." > > Hope this is a sufficient description. Thanks. > > Kevin >
Oh - one further thing - 'Generate DDL...' doesn't appear to work if the mappings are all in orm.xml. The command fails silently with no indication as to what went wrong (no error log entries either). Thanks, Adrian.
This enhancement will be considered for 1.0.
Adjusting the title for this request to more accurately reflect its nature. We are delivering the management of orm.xml with the 1.0 release, but this is a specific request for a meta data conversion facility. We still like the idea of this enhancement but it doesn't look like we will have time to get it into 1.0 at this point.
Moving JPA specific bugs to new JPA component in bugzilla.
Moving JPA global metadata (queries, generators, and converters) will be tracked in bug 353149.
