In addition to Ravi's comments it sounds like there's a different in which
fields are eagerly / lazily fetched. Which version of OpenJPA are you using
for the RESOURCE_LOCAL tests (there is a change this behavior recently so
trunk might be different from say 1.2.1).
-mike
On Mon, Jul 27, 2009 at
Hi,
My guess is that the SQL generation should not be different between JTA and
RESOURCE_LOCAL.
Can you please add default trace level logging to both the scenarios and
attach the logs here.
That way we can compare between both scenarios and find if there are any
differences in the properties b
please my project runs ok and generate all Sql statements under
RESOURCE_LOCAL persistence.xml. when i change to run in the container using
JTA , it does not generate the same number on sql statements causing the
application to throw exceptions.
for example when i run a test under RESOURCE_LOCAL,
