jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Strasser (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-237) Item.isNew() does not work correctly within a transaction
Date Mon, 03 Oct 2005 16:32:48 GMT
     [ http://issues.apache.org/jira/browse/JCR-237?page=all ]
Tobias Strasser resolved JCR-237:

    Fix Version: 1.0
     Resolution: Fixed

corrected Item.isNew() method by relying on the transient/overlaid state. this corrupted the
locking related methods, when running inside a transaction. added an iterim method ItemImpl.isTransactionalNew()
using the old behaviour. as soon locking is tx aware, this method can be removed.

Date: Mon Oct  3 09:29:32 2005
New Revision: 293380

> Item.isNew() does not work correctly within a transaction
> ---------------------------------------------------------
>          Key: JCR-237
>          URL: http://issues.apache.org/jira/browse/JCR-237
>      Project: Jackrabbit
>         Type: Bug
>  Environment: r293331
>     Reporter: Tobias Strasser
>     Assignee: Tobias Strasser
>      Fix For: 1.0

> javadoc on Item.isNew() states:
>      * Returns <code>true</code> if this is a new item, meaning that it exists
only in transient
>      * storage on the <code>Session</code> and has not yet been saved. Within
a transaction,
>      * <code>isNew</code> on an <code>Item</code> may return
<code>false</code> (because the item
>      * has been saved) even if that <code>Item</code> is not in persistent
storage (because the
>      * transaction has not yet been committed).
> but currently, Item.isNew() returns "true" after beeing saved in a transaction.

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