Laird & Kevin,
This bug has been around a while. It is filed under JIRA OPENJPA-400[1].
The typical workaround is to use the openjpa.jdbc.Schema property. It looks
like OpenJPA *may* also pick up the value if you define your entities in the
orm.xml -- but my memory is cloudy regarding that worka
Hi Laird,
I agree with you. You should be able to specify a default schema and/or
catalog via the persistence-unit-defaults element of the orm.xml file. I
just looked through our junits, and I don't see any tests for this
particular configuration... I do see other defaults being tested, just not
I have a test suite that runs my JPA entities across all the major JPA
providers.
None of my entities has a schema name in it; I want to keep it that way.
None of my entities are configured in any way other than annotations.
I understand from the JPA specification that if I put in a
element in
