I have a question on eviction policy implementation. Sometimes I need to delay eviction till, e.g., the next eviction thread wakeup. But I found that if eviction event occures, cache.get(Fqn) within eviction policy implementation doesn't cause nodeVisited event, thus, second eviction request is not initiated for the same node.
I found a kind of workaround - something like | cache.put(fqn,cache.get(fqn).getData()) | , i.e. just putting the same values into the cache. But I'm not sure this is a good decision, since node modification within listeners is undesirable, as far as I can understand. Can someone propose correct decision? Regards, Eugene aka Skipy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893019#3893019 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893019 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
