[jboss-jira] [JBoss JIRA] Resolved: (JBAS-3473) Fix DistributedStateImpl.nodeRemove

[Jerry Gauthier (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3473?page=all ]

Jerry Gauthier resolved JBAS-3473.
----------------------------------

    Resolution: Done

Fixed based upon changes in JBCACHE-595

> Fix DistributedStateImpl.nodeRemove
> -----------------------------------
>
>                 Key: JBAS-3473
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3473
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Jerry Gauthier
>             Fix For: JBossAS-5.0.0.Beta2
>
>
> AFAICT, this is not correct.  Key/value pairs are stored in the category node's data map; nodeRemoved treats things as if each key is its own node.
> Actually, I think the node per key approach is correct, until TreeCacheListener can provide info on what data was changed.
> Also, remove() itself notifies listeners of a removal, and then the listener does as well.  Needs to be one or the other; probably nodeRemoved() as that gets called for both local and remote removes.

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