Hmmm... So, that information is narrowing in on an OpenJPA issue and not an Oracle JDK issue... You are saying that your same test works just fine with OpenJPA 2.2.0, but is now failing with OpenJPA 2.2.1 SNAPSHOT? But, it's only with the Oracle JDK and not the IBM JDK?
Can you provide a testcase scenario to demonstrate the issue? Specific information on the Oracle JDK being used, etc. Thanks, Kevin On Thu, Oct 11, 2012 at 12:26 PM, garpinc <garp...@yahoo.com> wrote: > Ok. but fyi if the plan is soon to release 2.2.1 then perhaps someone needs > to look into it because 2.2.0 didn't have this problem > > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/JDK-1-7-seems-to-be-causing-an-issue-with-latest-snapshot-tp7581417p7581426.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
