Use the new ExoCache config instead of adding a new creator ----------------------------------------------------------- Key: GTNPORTAL-2174 URL: https://issues.jboss.org/browse/GTNPORTAL-2174 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Hai Nguyen Priority: Minor Exo JCR 1.14 has added a new Feature that allows us to choose the ExoCache implementation. (https://issues.jboss.org/browse/EXOJCR-1180 for more details) So no need to define a new ExoCacheCreator( org.exoplatform.commons.cache.SimpleExoCacheCreator ) in order to instantiate org.exoplatform.services.cache.concurrent.ConcurrentFIFOExoCache, you will have simply to choose the type of cache in config, as follows: <type>org.exoplatform.services.cache.ExoCacheConfigPlugin</type> <description>add Exo Cache Config</description> <init-params> <object-param> <name>cache.config.MOPSessionManager</name> <description>The JBoss Cache configuration for the MOP session Manager</description> <object type="org.exoplatform.services.cache.ExoCacheConfig"> <field name="name"> <string>MOPSessionManager</string> </field> <field name="maxSize"> <int>5000</int> </field> <field name="liveTime"> <long>600</long> </field> <field name="implementation"><string>org.exoplatform.services.cache.concurrent.ConcurrentFIFOExoCache</string></field> </object> </object-param> </init-params> </component-plugin> via the implementation field. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira