anonymous wrote :
|
| Ignorant question whose answer I should know. If you bind the Cache itself in the
java:/ namespace, does it serialize it or just store a ref to the cache in the JNDI tree?
If not, then the user can just bind the cache in java:/ for the local clients.
|
Should be a ref - in which case storing a Cache instance would work too.
anonymous wrote :
|
| Interesting. I think the tricky bit is you have to have a cleanup API to remove the
caches (or use WeakReferences).
|
Or the cleanup could be triggered when a cache.destroy() is called - this could cause it
to be "unregistered" with the cache factory.
anonymous wrote :
| If the client is local and JMX is available, they can just use CacheJmxWrapper and JMX
becomes a registry. Or maybe binding the Cache in JNDI in java:/ will work.
|
See, I've always believed that JMX is for management information and management
processes. To actually use a service, the service should be in JNDI. Maybe that's
just me oversimplifying things.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051362#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...