I checked the JCR message store code into the trunk. The required configuration files and libraries are now bundled in the jbossesb.sar during the build. There are two basic configurations: load the JCR repository from JNDI or initialize it from the repository.xml in the root directory of the sar. To enable the JCR message store, add the following line to the "core" section of the jbossesb-properties.xml: | <property name="org.jboss.soa.esb.persistence.base.plugin.jcr" value="org.jboss.internal.soa.esb.persistence.format.jcr.JCRMessageStorePlugin"/> | To configure the message store, add the following properties to the "dbstore" section of the jbossesb-properties.xml: | <property name="org.jboss.soa.esb.persistence.jcr.jndi.path" value="jcr"/> | <property name="org.jboss.soa.esb.persistence.jcr.username" value="username"/> | <property name="org.jboss.soa.esb.persistence.jcr.password" value="password"/> | <property name="org.jboss.soa.esb.persistence.jcr.root.node.path" value="JBossESB/MessageStore"/> | If the "jcr.jndi.path" property is not specified, the repository will be configured locally using the repository.xml in the root of the sar. The "jcr.username" and "jcr.password" are passed to the repository to get a session. The "root.node.path" property determines the relative path in the repository under which message nodes will be stored. An easy test for whether the JCR message store is configured properly is to add the org.jboss.soa.esb.actions.persistence.StoreJCRMessage action onto an existing service. The action will attempt to store the current message to the JCR store. Let me know if you run into any problems. Thanks, Derek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036072#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...