[ 
> JPOX fails some lifecycle tests
> -------------------------------
>
>          Key: JDO-347
>          URL: [url]http://issues.apache.org/jira/browse/JDO-347" target="_blank">http://issues.apache.org/jira/brows.../browse/JDO-347
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Reporter: Martin Zaun
>  Attachments:  errors_state_transition_argument_instanc
es.txt, errors_state
_transition_returned_instances.txt
>
> The integration of fixes for JDO-273 and JDO-258 has added (and fixed) a n
umber 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:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]

Hi Craig,

> Craig Russell commented on JDO-347:
> -----------------------------------
> The transient clean state is not persistent. It has no object id.
> When it's serialized, it should have no detached state.
> When jdoPreSerialize is executed, the StateManager should not create a detached[/v
bcol]
state.[vbcol=seagreen]
> When the instance is deserialized, it should still have no detached state.
> Unlike detachCopy, which makes the object graph persistent, serialize does
n't
> make transient instances persistent.

Thanks. Makes sense now. Another 8 state transitions fixed in JPOX CVS.

--
Andy

[ Post a follow-up to this message ]