You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Marc Prud'hommeaux (JIRA)" <ji...@apache.org> on 2006/08/30 02:05:22 UTC

[jira] Created: (JDO-409) IsTransactionalFalse makes invalid assumption that transaction is optimistic

IsTransactionalFalse makes invalid assumption that transaction is optimistic
----------------------------------------------------------------------------

                 Key: JDO-409
                 URL: http://issues.apache.org/jira/browse/JDO-409
             Project: JDO
          Issue Type: Bug
          Components: tck20
    Affects Versions: JDO 2 final
            Reporter: Marc Prud'hommeaux


The test IsTransactionalFalse.testIsTransactionalFalse mandates that an instance will be persistent-clean after a field is accessed in a transaction. However, when the transaction type is optimistic, it is also valid for the instance to be persistent-nontransactional after a field access.

The test can be fixed by ensuring that the transaction is a datastore transaction. E.g.:

    public void testIsTransactionalFalse() {
        pm = getPM();
        Transaction tx = pm.currentTransaction();
        tx.setOptimistic(false); // make sure the transaction is not optimisitic
        tx.begin();


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

        

Re: [jira] Created: (JDO-409) IsTransactionalFalse makes invalid assumption that transaction is optimistic

Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Marc,

Thanks for submitting this bug report.

Would it be possible for you to attach a patch to the issue? That  
makes it a lot easier for one of the committers to test and check in  
the fix.

Thanks,

Craig

On Aug 29, 2006, at 5:05 PM, Marc Prud'hommeaux (JIRA) wrote:

> IsTransactionalFalse makes invalid assumption that transaction is  
> optimistic
> ---------------------------------------------------------------------- 
> ------
>
>                  Key: JDO-409
>                  URL: http://issues.apache.org/jira/browse/JDO-409
>              Project: JDO
>           Issue Type: Bug
>           Components: tck20
>     Affects Versions: JDO 2 final
>             Reporter: Marc Prud'hommeaux
>
>
> The test IsTransactionalFalse.testIsTransactionalFalse mandates  
> that an instance will be persistent-clean after a field is accessed  
> in a transaction. However, when the transaction type is optimistic,  
> it is also valid for the instance to be persistent-nontransactional  
> after a field access.
>
> The test can be fixed by ensuring that the transaction is a  
> datastore transaction. E.g.:
>
>     public void testIsTransactionalFalse() {
>         pm = getPM();
>         Transaction tx = pm.currentTransaction();
>         tx.setOptimistic(false); // make sure the transaction is  
> not optimisitic
>         tx.begin();
>
>
> -- 
> 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
>
>

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


[jira] Commented: (JDO-409) IsTransactionalFalse makes invalid assumption that transaction is optimistic

Posted by "Marc Prud'hommeaux (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/JDO-409?page=comments#action_12431472 ] 
            
Marc Prud'hommeaux commented on JDO-409:
----------------------------------------

You are correct about the title, and I agree that it is a duplicate. The fixed check in at http://svn.apache.org/repos/asf/db/jdo/trunk/tck20/src/java/org/apache/jdo/tck/api/jdohelper/IsTransactionalFalse.java looks correct to me.

> IsTransactionalFalse makes invalid assumption that transaction is optimistic
> ----------------------------------------------------------------------------
>
>                 Key: JDO-409
>                 URL: http://issues.apache.org/jira/browse/JDO-409
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>
> The test IsTransactionalFalse.testIsTransactionalFalse mandates that an instance will be persistent-clean after a field is accessed in a transaction. However, when the transaction type is optimistic, it is also valid for the instance to be persistent-nontransactional after a field access.
> The test can be fixed by ensuring that the transaction is a datastore transaction. E.g.:
>     public void testIsTransactionalFalse() {
>         pm = getPM();
>         Transaction tx = pm.currentTransaction();
>         tx.setOptimistic(false); // make sure the transaction is not optimisitic
>         tx.begin();

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

        

[jira] Closed: (JDO-409) IsTransactionalFalse makes invalid assumption that transaction is optimistic

Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JDO-409?page=all ]

Michael Bouschen closed JDO-409.
--------------------------------

    Resolution: Duplicate

Closed as a duplicate of JDO-400.

> IsTransactionalFalse makes invalid assumption that transaction is optimistic
> ----------------------------------------------------------------------------
>
>                 Key: JDO-409
>                 URL: http://issues.apache.org/jira/browse/JDO-409
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>
> The test IsTransactionalFalse.testIsTransactionalFalse mandates that an instance will be persistent-clean after a field is accessed in a transaction. However, when the transaction type is optimistic, it is also valid for the instance to be persistent-nontransactional after a field access.
> The test can be fixed by ensuring that the transaction is a datastore transaction. E.g.:
>     public void testIsTransactionalFalse() {
>         pm = getPM();
>         Transaction tx = pm.currentTransaction();
>         tx.setOptimistic(false); // make sure the transaction is not optimisitic
>         tx.begin();

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

        

[jira] Commented: (JDO-409) IsTransactionalFalse makes invalid assumption that transaction is optimistic

Posted by "Ilan Kirsh (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/JDO-409?page=comments#action_12431434 ] 
            
Ilan Kirsh commented on JDO-409:
--------------------------------

I believe the title should be "IsTransactionalFalse makes invalid assumption that transaction is datastore" and that this issue duplicates JDO-400 that had already been fixed.

> IsTransactionalFalse makes invalid assumption that transaction is optimistic
> ----------------------------------------------------------------------------
>
>                 Key: JDO-409
>                 URL: http://issues.apache.org/jira/browse/JDO-409
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>
> The test IsTransactionalFalse.testIsTransactionalFalse mandates that an instance will be persistent-clean after a field is accessed in a transaction. However, when the transaction type is optimistic, it is also valid for the instance to be persistent-nontransactional after a field access.
> The test can be fixed by ensuring that the transaction is a datastore transaction. E.g.:
>     public void testIsTransactionalFalse() {
>         pm = getPM();
>         Transaction tx = pm.currentTransaction();
>         tx.setOptimistic(false); // make sure the transaction is not optimisitic
>         tx.begin();

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