[ http://jira.jboss.com/jira/browse/JBESB-172?page=all ] Mark Little updated JBESB-172: ------------------------------ Fix Version/s: 4.0 RC1 (was: 4.0) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-172?page=comments#action_12346071 ] Mark Little commented on JBESB-172: ----------------------------------- Take the discussion to the forum and cross reference it here: makes it easier to read the JIRA entry. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-172?page=all ] Mark Little updated JBESB-172: ------------------------------ Fix Version/s: 4.0 (was: 4.0 RC1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-172?page=all ] Mark Little updated JBESB-172: ------------------------------ Priority: Critical (was: Major) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-172?page=all ] Kurt Stam closed JBESB-172. --------------------------- Resolution: Done Done. 1. In our configuration we previously we had: jndi-Type jndi-URL Now we have: jndi-URL jndi-connection-factory jndi-pkg-prefix See also Scott's comments on: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=94539 For example this is what you have to do for activeMQ: <ContentBasedRouter service-category="MessageRouting" service-name="ContentBasedRoutingService" service-description="This CBR routs messages to different service destination based whether the messageType is XML or Serializable" listenerClass="org.jboss.soa.esb.listeners.message.CbrJmsQueueListener" connection-factory="ConnectionFactory" destination-type="queue" destination-name="queue/A" jndi-context-factory="org.apache.activemq.jndi.ActiveMQInitialContextFactory" jndi-URL="tcp://localhost:61616" message-selector="service='ContentBasedRouting-SerializableOrXml'" while for jboss you'd use: jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-URL="localhost" 2. Also as part of this change support other jms providers I create the queues and/or topics on the fly. Much like is done for MDBs in jboss. I had to do this b/c ActiveMQ does not have a full fledged JNDI, and lookups can be problematic. 3. If you want to use activemq, you need the jars in lib/ext/jms/activemq on your classpath, and you obviously need to run activemq. (Just download and click the activemq.bat) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira