db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-347) JPOX fails some lifecycle tests
Date Thu, 23 Mar 2006 19:48:20 GMT
    [ http://issues.apache.org/jira/browse/JDO-347?page=comments#action_12371626 ] 

Craig Russell commented on JDO-347:

It might be useful here to review the process of detachCopy.

First, the instances in the parameter list are made persistent as if makePersistent had been
called. This will recursively make detached and transient instances persistent (detached instances
are replaced in this process by corresponding persistent instances).

Second, the FetchPlan is used to instantiate the object graph.

Third, the detached instance graph is created from the persistent object graph, using the
FetchPlan to determine which fields are to be marked as loaded in the detached instance graph.

The detached instances corresponding to persistent instances by position in the original parameter
list are returned to the user.

So the test case that calls detachCopy on a detached instance expects that the instance returned
is a newly created detached instance with the same object id as the persistent instance in
the cache and the parameter instance.

> JPOX fails some lifecycle tests
> -------------------------------
>          Key: JDO-347
>          URL: http://issues.apache.org/jira/browse/JDO-347
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Reporter: Martin Zaun
>  Attachments: errors_state_transition_argument_instances.txt, errors_state_transition_returned_instances.txt
> The integration of fixes for JDO-273 and JDO-258 has added (and fixed) a number of lifecycle
test cases that are
> failed by JPOX.  See attached error messages.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message