From: bstansberry <nu...@jb...> - 2005-07-13 04:59:30
|
Quick note on what's going on with this: Code basically along the lines discussed above has been checked into Branch_4_0 and HEAD. JBossCacheCluster has been changed in that it does not expose attributes to configure the TreeCache in detail (e.g. "isolationLevel", "cacheMode", etc.). Instead an attribute is exposed where the user can configure a relative path to a jboss-service.xml-style MBean deployment descriptor that configures the cache. If the attribute is not set, JBossCacheCluster will look for a file named cache-cluster.xml in the Tomcat conf folder. If no file is found, the TreeCache will be configured using reasonable defaults. No need to worry about a TransactionManager; DummyTransactionManager works fine. Using JOTM would be a mistake, as that would potentially involve session replication with user transactions. All of StandaloneJBossCacheManager's functionality has been merged into JBossCacheManager. JBossCacheManager can determine based on how it's configured whether its running embedded or standalone. JBossCacheManager handles deploying its ClusteredSessionValve itself; this has been removed from TomcatDeployer. The manager needs to be able to do this in standalone mode, so I saw no point in having the code duplicated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884651#3884651 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884651 |