> I think build time enhancement solved it. FYI: The run-time enhancement via subclassing has lot's of other problems (the agent seems fine though; it does essentially the same thing as the build time thing)... we specify openjpa.RuntimeUnenhancedClasses = unsupported (@see http://openjpa.apache.org/builds/1.2.1/apache-openjpa-1.2.1/docs/manual/ ref_guide_conf_openjpa.html#openjpa.RuntimeUnenhancedClasses) in our OpenJPA bootstrap stuff to prevent it in all situations (final runtime & unit/integration tests).
PS, also see https://issues.apache.org/jira/browse/OPENJPA-651. -----Original Message----- From: Cil-Gamir [mailto:[email protected]] Sent: Friday, November 13, 2009 8:56 AM To: [email protected] Subject: Re: Locking Exception after Persisting new entity Hi I think build time enhancement solved it. I'm getting a different error now org.apache.openjpa.persistence.EntityExistsException: An object of type "za.co.rmb.rac.riskRatingEngineWeb.entities.Variable" with oid "0" already exists in this context; another cannot be persisted. But at least the optimistic locking thing has taken a hike Unfortunately I have a teambuilding thing on today... so I can't fix this thing any further. Thanks a lot for the help Daryl Regards Hannes -- View this message in context: http://n2.nabble.com/Re-SOLVED-Re-Locking-Exception-after-Persisting-new -entity-tp3992651p3997874.html Sent from the OpenJPA Users mailing list archive at Nabble.com. ____________________________________________________________ This email and any files transmitted with it are CONFIDENTIAL and intended solely for the use of the individual or entity to which they are addressed. Any unauthorized copying, disclosure, or distribution of the material within this email is strictly forbidden. Any views or opinions presented within this e-mail are solely those of the author and do not necessarily represent those of Odyssey Financial Technologies SA unless otherwise specifically stated. An electronic message is not binding on its sender. Any message referring to a binding engagement must be confirmed in writing and duly signed. If you have received this email in error, please notify the sender immediately and delete the original.
