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-428) StateTransitionsReturnedObjects disallows makePersistent() on a detached-clean instance from being hollow
Date Wed, 04 Oct 2006 02:59:19 GMT
    [ http://issues.apache.org/jira/browse/JDO-428?page=comments#action_12439712 ] 
            
Craig Russell commented on JDO-428:
-----------------------------------

It might be surprising for users who attach a detached instance and the clean state of the
instance silently disappears. Why is this desirable?

The answer will determine whether we consider this a spec bug to be fixed to specify that
attaching a detached-clean instance results in a persistent-clean state or specify that the
state can be persistent-clean or hollow.


> StateTransitionsReturnedObjects disallows makePersistent() on a detached-clean instance
from being hollow
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JDO-428
>                 URL: http://issues.apache.org/jira/browse/JDO-428
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>         Assigned To: Craig Russell
>            Priority: Minor
>
> Element 10 (0-based) of the "makePersistent" array in org/apache/jdo/tck/lifecycle/StateTransitionsReturnedObjects.java
asserts that a detached-clean instance passed to makePersistent() should have the resulting
object be in the "persistent-clean" state. However, section 12.6.7 of the JDO 2 spec merely
says that: "During application of changes of the detached state, if the JDO implementation
can determine that there were no changes made during detachment, then the implementation is
not required to mark the corresponding instance dirty." Based on this, it should be legal
for the object to be in either the hollow state as well as the persistent-clean state.
> The easiest fix, short of changing the test case to allow for multiple states, is to
change element 10 from "PERSISTENT_CLEAN" 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

        

Mime
View raw message