Ok, no refresh ever or a refresh all the time is a bit "bone-head" and there are "soft ball" requirements at the level of the cache. Option D, is when the cache is invalidated every X seconds, but in between the state is not reloaded which will GREATLY speed the container (because we avoid JDBC serialization) in most cases. The fact is that "hard ball" requirements, i.e. refreshing all the time, is kind of overkill and never refreshing is way under-kill. So I actually give that as an excercise in the "JBoss Training" that I am giving. It is really about 10 lines in the right interceptor... see if you guys can do it. Same... if you are interested let the board know. marc _________________ Marc Fleury, Ph.D [EMAIL PROTECTED] _________________ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
