"saylor09" wrote : | As there are certain domain data elements in the client application that are considered to always be there, I'd like to be able to mark specific nodes in the cache as non-expiring so we aren't processing extra cache miss operations (because the requested data may have been evicted). What nodes these are is not known until runtime. |
Hmm, I suppose extending the LRUPolicy may help as a quick fix - extend it to ignore specific FQNs if you know which FQNs need to be pinned? Or have I misunderstood your use case? "saylor09" wrote : | BTW, I found an answer to my question about modifying the caching policy at runtime by searching around the forums a bit harder. It turns out this just isn't supported (yet). Thanks for not flamming me like some of the other jboss guys do in the other forums. I was a bit apprehensive about even posting anything to the jboss forums. :) | :-) Some of us have better things to do with our time than flame people! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3904571#3904571 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3904571 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
