[ http://issues.apache.org/jira/browse/JDO-368?page=comments#action_12442136 ] Dave commented on JDO-368: --------------------------
[[ Old comment, sent by email on Tue, 6 Jun 2006 09:38:41 -0600 ]] Craig, I think you missed the point of this bug report. Your explanation below makes since and explains what is going on. My point is that the JavaDoc documentation of these methods is confusing. During attachment, the state of "the copy" that was previously detached is synchronized with the original object and ultimately the with the datastore. Instead of "after/before the copy is made", it should say something like: "after/before the detached object's state is transfered to the persistent object's state". upon whether the original persistent object instance is still in memory. On 6/3/06, Craig Russell (JIRA) <[EMAIL PROTECTED]> wrote: > AttachCallback javadoc issue > ----------------------------- > > Key: JDO-368 > URL: http://issues.apache.org/jira/browse/JDO-368 > Project: JDO > Issue Type: Bug > Components: api20 > Affects Versions: JDO 2 rc1 > Environment: N/A > Reporter: Dave > Assigned To: Craig Russell > > Javadoc issue. > Descriptions of the AttachCallback methods appear to be copied from > DetachCallback. A copy is made during Detach, but not Attach. Which > instance are these methods executed on? The attaching copy, or the > persistent copy? > jdoPostAttach(java.lang.Object attached) > This method is called during the execution of > PersistenceManager.makePersistent(java.lang.Object) on the persistent > instance after the copy is made. > void jdoPreAttach() > This method is called during the execution of > PersistenceManager.makePersistent(java.lang.Object) on the detached instance > before the copy is made. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
