Re: svn commit: r751910 - in /openjpa/trunk: openjpa-kernel/src/main/java/org/apache/openjpa/conf/ openjpa-kernel/src/main/java/org/apache/openjpa/kernel/ openjpa-kernel/src/main/java/org/apache/openjpa/meta/ openjpa-persistence-jdbc/src/test/java/org/apac...

[Craig L Russell]

Hi Pinaki,




Do you have a test case for the old behavior with the new configuration?

Regards,

Craig

On Mar 10, 2009, at 3:05 PM, Pinaki Poddar wrote:

Since the JPA signature has no return value, how can the user get the detached objects?

Hi Craig,

change does retain the past behavior exactly as it was. The user only
requires the following configuration to get exactly the same behavior
 openjpa.Compatibility=FlushBeforeDetach=true,CopyOnDetach=true



 Regards --


--
View this message in context: 
http://n2.nabble.com/Re%3A-svn-commit%3A-r751910---in--openjpa-trunk%3A-openjpa-kernel-src-main-java-org-apache-openjpa-conf--openjpa-kernel-src-main-java-org-apache-openjpa-kernel--openjpa-kernel-src-main-java-org-apache-tp2458104p2458226.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.

I understand your concerns because I had similar ones. That is why this In fact, JDO having a separate signature as detachCopy() is a good news because then we can add the same signature to Broker so that the user will not even need the above configuration for backward compatible behavior.

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@sun.com
P.S. A good JDO? O, Gasp!

smime.p7s
Description: S/MIME cryptographic signature