> As you have pointed out, this gets a bit trickier due to the > xml schema > definitions for the orm.xml file. We can't just define new > stanzas and > expect the orm.xml files to be portable across persistence providers.
But do we care? That is, how do we want to balance portability vs. ease of use? Put another way, if we were to define schema extensions, we could presumably allow both interleaving of the contents as in my example and parallel files, so that people could choose how they wanted to configure. This would have the downside of allowing multiple configuration mechanisms, but would allow the upside of letting people use one file instead of two if they so desired. > Your second guideline was a surprise to me. Are you saying that if an > application is using orm.xml to override certain > spec-compliant annotations, > then the OpenJPA annotations are also ignored? Currently, I believe that that is the case. > If I am reading that right, > then isn't this just a bug that needs to be resolved? Yes, but the fix has implications on behavior in the future, if we decide to have a single file instead of multiple. > Does OpenJPA provide > alternative annotation support for the JPA spec-compliant > annotations? I > knew we provided additional annotations, but I wasn't aware > that we overrode > JPA annotations. No, OpenJPA doesn't provide any way to override JPA annotations / descriptor elements. > On a related note... Will the xml-mapping-metadata-complete > element apply > to the openjpa annotations as well? If we put contents into the same file, I'd say yes. If we put contents into a different file, dunno. Maybe we'd want to have another xml-mapping-metadata-complete stanza there too. -Patrick _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
