If you deploy your TreeCacheAop as a mbean service, you can then access from
ejb (directly or through a wrapper). As a result, all memebers in the group
will have the replicated state.
-Ben
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877286#3877286
Reply
Ben,
Does the use-case above appear in any of the cache docs? If you have any more
info on this, I would very much like to read it. I want to do something
similar to the above, i.e., access a distributed cache from EJBs in order to
implement an in-memory, cluster-aware singleton.
I was readi
DistributedState is ok but JBossCache is now recommended for the state
replication since future DistributedState will be refactored using cache
underneath as well.
-Ben
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871777#3871777
Reply to the post :
http:
Try using DistributedState of HAPartition. I have similar application where I
need to share information in two nodes. All my caches are stored in
DistributedState. Whenever this state is changes, jboss frameworks informs all
the nodes about change in state.
Thanks,
Anup
View the original post
James,
I am interested to see your use case on TreeCacheAop for this one. Would mind
to share more details? :-)
You can email me ([EMAIL PROTECTED]) if you prefer.
Thanks,
-Ben
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871728#3871728
Reply to the pos
Thanks for your response.
Yes this is exactly what I am doing now, I only wish I had known of this
possibility before wasting so much time trying to use a Singleton. I now have
MBeans which use the TreeCacheAop service with synchronous replication, and
except for a few minor problems it is wor
Did you try putting the state of your HASingleton in a distributed cache (like
JBossCache ) instead of having it locally on your Master Singleton alone? So
when the master dies and one of the slaves is promoted to Master, the state
should be still accessible to it via the distributed cache. No?
