[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-703) Remove does not work anymore using non-String keys

[Manik Surtani (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-703?page=all ]

Manik Surtani closed JBCACHE-703.
---------------------------------

    Fix Version/s: 1.4.0.SP1
       Resolution: Done

> Remove does not work anymore using non-String keys
> --------------------------------------------------
>
>                 Key: JBCACHE-703
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-703
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0
>            Reporter: Benjamin Papez
>         Assigned To: Manik Surtani
>            Priority: Blocker
>             Fix For: 1.4.0.SP1
>
>
> I am using the following, while getFqn() is a Fqn-object of an existing tree node like "/FieldsCache" and entry is any object.
> getTreeCache().put(new Fqn(getFqn(), new Integer(10)), "entry", entry);
> getTreeCache().get(new Fqn(getFqn(), new Integer(10)), "entry");
> getTreeCache().remove(new Fqn(getFqn(), new Integer(10)));
> Since switching to jbosscache 1.4.0.GA (did not test with the betas) the remove will not really remove the item, will also not throw an exception and if I issue another get after the remove the node will again be returned. 
> I am using pessimistic locking with either READ_UNCOMMITED or even NONE as locking level.
> When debugging I see in the _remove method on line 4537 that the 
>       parent_node.removeChild(n.getName());
> does not work, because n.getName() returns a String, while the childrenNames in the parent_node have Integers as keys.

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