the cms can be configured to do cache invalidation and use one single database providing the feature you want.
for that you need to configure the slide repository such it uses a JDBC store and shared by all the servers. also you need to use the HA version of the CMS that uses cache invalidation to invalidate entries in the cluster avoiding stale entries when modification occurs. I have not yet tested it with JDBC repository yet, only with shared file system. So if you want to try it you need to go on the jakarta slide website and use the doc to configure the JDBC store. All the configuration occurs in portal-core.sar/portal-cms.sar/META-INF/jboss-service.xml View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868489#3868489 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868489 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
