Slide integration as an mbean service featuring embedded configuration in jboss-service.xml

Cache invalidation based on JBoss clustering framework

Creation of content at startup when it does not exist

Possibility to list system properties in the slide configuration for better flexibility

Hibernate 3.0 store implementation

When using the hibernate store the datasource in the application server must be a non transactionnal datasource because Slide manages it as a managed resources and demarcates the transaction itself.

The slide service configuration is located in META-INF/jboss-service.xml which contains the service definition with the embedded slide domain configuration.

The default store implementation is the hibernate store, however the file store based configuration is commented in the service configuration.

The DoChecking mbean attribute of the service tells the service to check wether the content exists or not and if it does not exists it is imported from the default-content directory present in the sar file.

The webdav access has a configuration slightly different from the default configuration bundled with slide, it has the domain init parameter commented and a dependency on the cms service in order to have the cms service setup the service before the servlet startup and avoid that the servlet tries to startup its own service.

The HA version of can be enabled by uncommenting the listener class org.jboss.portal.cms.ha.InvalidationListener.

The source code is available as part of the JBoss Portal 2.0 project, we have not built a source versions of the cms only because our build system is not flexible enough to make it easy.