[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-745) nodeEvicted being called for nodes that don't actuall get evicted

[Manik Surtani (JIRA)]

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

Manik Surtani closed JBCACHE-745.
---------------------------------

    Resolution: Won't Fix

This is valid behaviour as Brian pointed out.

> nodeEvicted being called for nodes that don't actuall get evicted
> -----------------------------------------------------------------
>
>                 Key: JBCACHE-745
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-745
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0.SP1
>            Reporter: gregorypierce
>         Assigned To: Manik Surtani
>         Attachments: CacheEviction.java
>
>
> Working on class example from training materials CacheEviction.java. Will receive a nodeEvicted call that the root node has been evicted, but if you look at the console itself and print the tree - the root node doesn't get evicted. Should not call nodeEvicted with a node that hasn't actually already been evicted from the tree. Looks like it realizes that the node is a parent node and decides against evicting it after the interface call.
> // FIXME We extend AbstractTreeCacheListener, which provides a default implementation
> // of the TreeCacheListener interface. You just need to override methods to write to
> // the console for cache events in which you are interested.  Do something like this:
>    public void nodeCreated(Fqn fqn) {
>       System.out.println("nodeCreated(): fqn: " +fqn);
>    }
>    public void nodeEvicted(Fqn fqn)
>    {
> 	   System.out.println("nodeEvicted(): fqn: " +fqn);
>    }

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