anonymous wrote : | Say we solve the Cache issue and a remote Cache proxy is available. Any API call that requires use of a Node will fail, since the Node won't be a remote object. The only available API will be those methods that don't involve a Node. | Hmm, this may involve exposing and binding each Node, which sucks/bordering on completely ridiculous. How about mandating that if you intend to access the cache via JMX, don't use Node APIs? Yes, this restricts some functionality, but not all, and even then only for people remotely accessing a cache bound in JMX/JNDI. And for local usage, people would either create a cache instance directly, or how about binding the CacheFactory (java:/ namespace) so people can get a hold of the cache? Related topic - should CacheFactory always construct caches? Should it also be able to retrieve already-constructed, named caches? E.g., | Cache c1 = DefaultCacheFactory.createCache("MyCache", "cfg.xml"); | Cache c2 = DefaultCacheFactory.createCache("MyCache", "cfg.xml"); | | assertSame(c1, c2); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051065#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...