[ 
http://issues.apache.org/jira/browse/JDO-429?page=comments#action_12439857 ] 
            
Craig Russell commented on JDO-429:
-----------------------------------

The intent of a detached instance is that it represents a persistent instance 
that is not actively managed by a PersistenceManager but has identity and can 
be attached to a PersistenceManager. In the case of a deleted instance, this 
concept is violated and will cause problems for the application.

Specifically, if a deleted instance is treated as detached, and the detached 
instance is subsequently attached, an exception should result because the 
instance no longer exists in the datastore, and the assumption is that detached 
instances have persistent identity that corresponds to a persistent instance. 

Regarding element 10, persistent-nontransactional-dirty, I will create another 
JIRA for this, since it's a separate issue.


> StateTransitionsReturnedObjects assumes that serializing deleted instances 
> will transition them to transient
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JDO-429
>                 URL: http://issues.apache.org/jira/browse/JDO-429
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>            Priority: Minor
>
> Elements 7 and 8 (0-based) of the "serialize with active tx" array in 
> org/apache/jdo/tck/lifecycle/StateTransitionsReturnedObjects.java assert that 
> a persistent-new-deleted and persistent-deleted instance (respectively) will 
> transition to transient when then are serialized then deserialized. However, 
> the specification does not seem to mandate this anywhere: detached-clean 
> should be an equally valid state to be in.
> The easiest fix, short of changing the test case to allow for multiple 
> states, is to change elements 7 and 8 from "TRANSIENT" to "IMPOSSIBLE", which 
> will disable the state check altogether.

-- 
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

        

Reply via email to