2 Replies Latest reply on Mar 3, 2007 5:06 PM by daniel.brum

    Message Store - new implementation changes


      I have committed some changes to the Message Store with the way the connection manager works. It's now possible to use the datasource provided in an app. server, tomcat, etc. The design also supports adding in your own connection pooling logic, through a factory. 2 managers are provided
      - StandaloneConnectionManager which uses 3CPO for it's connection pooling management.
      - J2EEConnectionManager which allows you to use the jndi datasource of your choice.

      Some changes have been made to the config of the ESB through the jbossesb-properties.xml to support this:

      <!-- connection manager type -->
      <property name="org.jboss.soa.esb.persistence.db.conn.manager" value="org.jboss.soa.esb.persistence.manager.StandaloneConnectionManager"/>
      <!-- property name="org.jboss.soa.esb.persistence.db.conn.manager" value="org.jboss.soa.esb.persistence.manager.J2eeConnectionManager"/ -->
      <!-- this property is only used if using the j2ee connection manager -->
      <property name="org.jboss.soa.esb.persistence.db.datasource.name" value="java:/JBossesbDS"/>

      You specify the manager type, and if you want to use a datasource, just give it's jndi name. All other settings for a stanadlone deployment stay as they were before.

      Please let me know if you have any questions, or issues. I have run all the tests and tested with a SAR deployment inside of JBoss AS only.