Hi,
Why not define a separate OpenJPA XML schema? Then declare its namespace
in
orm.xml and one can use JPA and custom elements in the same document.
Yes that is a possibility. And this idea looks like a neat one.
This limitation to translate OpenJPA-specific source code annotations to
Hi
The OpenJPA describes how to indicate that a field should use OpenJPA's
large result set proxies using the @LRS Java annotation.
Can I specify LRS using orm.xml instead?
Thanks,chris
Hi,
Any OpenJPA specific annotations are, unfortunately, not supported in XML
descriptor. Because, JPA spec does not define a XML schema with a simple
name,value mechanism for vendor extensions. OpenJPA can merge source code
annotations with orm.xml -- so, one has to leave OpenJPA-specific
Hi Pinaki,
Thanks for the quick response.
Why not define a separate OpenJPA XML schema? Then declare its namespace in
orm.xml and one can use JPA and custom elements in the same document. The
original JPA schema is untouched.
-chris
Hi,
Any OpenJPA specific annotations are, unfortunately, not
