anonymous wrote : @Mircea - you should be able to bind to JNDI. This is useful not only for local mode, but even clustered modes where you want to share 1 cache instance across several webapps/enterprise apps in the same container. You can't put it in JNDI as the CacheInvocationDelegate is not serializable(see stack trace from original post); re:putting clustered caches in JNDI, that's a bit more tricky: between JNDI serailization and deserialization the cache might miss replication events and be in a inconsistent state. On the other hand what's the point of putting a replicated cache in JNDI because you can create an handler to it from any JVM you want to. Perhaps serializing+unserializing is more efficient than creating a new handler, but again there's the advantage of not loosing replication events.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235186#4235186 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235186 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
