I hope someone is reading it... or am I writing to myself?
Anyway, I think this is the problem code (from TreeCacheAop.java):

   public void evict(Fqn fqn) throws CacheException {
      // We will remove all children nodes as well since we assume all children 
nodes are part
      // of this "object" node.
      if(isAopNode(fqn)) {
         if(log.isDebugEnabled()) {
            log.debug("evict(): evicting whole aop node " +fqn);
         }
//         _remove(null, fqn, create_undo_ops, false);
         // TODO Why do we not want to remove the interceptor??? I think we 
should.
         // Because if we remove it, the caller has no idea that it has been 
taken off.
         // She will still think that caching is in effect. But this returns 
null value from cache.
         // What's is a good policy?
         boolean removeCacheInterceptor = false;
         _removeObject(fqn, removeCacheInterceptor);      } else {
         super.evict(fqn);
      }
   }

Is it possible to remove the interceptor only for this one call (_removeObject) 
and then put it back? Seems like that would be the right thing to do.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875060#3875060

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875060


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to