I started putting together a doc update and found that this compatibility flag has been around a while. Can anyone explain why 2.0 behaves differently than 1.x by default? (ie. flag not needed on 1.2, but required for 2.0) Did some new 2.0 spec requirement require OpenJPA to behave differently in this scenario?
-Jeremy On Tue, May 25, 2010 at 8:09 AM, Jeremy Bauer <[email protected]> wrote: > Good call, Pinaki! That fixed the failing testcase. I did/do not see this > change documented in our 1.0 -> 2.0 migration considerations. I'll update > the JIRA, including the need for documentation. > > -Jeremy > > > On Tue, May 25, 2010 at 1:07 AM, Pinaki Poddar <[email protected]> wrote: > >> >> This should work: >> <property name="openjpa.Compatibility" >> value="StrictIdentityValues=true"/> >> >> >> ----- >> Pinaki >> -- >> View this message in context: >> http://openjpa.208410.n2.nabble.com/OpenJPA-confusing-classes-tp5094249p5097022.html >> Sent from the OpenJPA Users mailing list archive at Nabble.com. >> > >
