[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-565) Optimistic locking - cache.exists() refers to the tree while cache.get() refers to the workspace
Manik Surtani (JIRA)
jira-events at jboss.com
Wed Jan 17 11:25:52 EST 2007
[ http://jira.jboss.com/jira/browse/JBCACHE-565?page=comments#action_12351037 ]
Manik Surtani commented on JBCACHE-565:
---------------------------------------
Fixed.
exists() is now an internal API anyway, which directly returns peek(fqn, false) != null
The equivalent public API is Node.hasChild(), which returns getChild() != null
> Optimistic locking - cache.exists() refers to the tree while cache.get() refers to the workspace
> ------------------------------------------------------------------------------------------------
>
> Key: JBCACHE-565
> URL: http://jira.jboss.com/jira/browse/JBCACHE-565
> Project: JBoss Cache
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.3.0.GA
> Reporter: Manik Surtani
> Assigned To: Manik Surtani
> Fix For: 2.0.0.BETA1
>
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> This is apparent when used within a tx:
> txManager.begin();
> cache.put("/test", "testKey", "Somevalue");
> assertNotNull(cache.get("/test", "testKey"));
> assertTrue(cache.exists("/test")); // should return true but returns false instead since the workspace hasn't been committed back to the tree yet
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list