JBossDeveloper

BTW, I am working off of the jboss-esb.xml schema:

<xsd:complexType name="jms-provider-type">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">A specific instance of a provider, providing JMS.</xsd:documentation>
 </xsd:annotation>
 <xsd:complexContent>
 <xsd:extension base="jesb:bus-provider">
 <xsd:attribute name="connection-factory" type="xsd:string" use="required">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">The connection-factory used to lookup queues/topics in a naming directory (JNDI)</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 <xsd:attribute name="jndi-context-factory" type="xsd:string">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">The context factory class the JBossESB will use to do naming lookups.</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 <xsd:attribute name="jndi-pkg-prefix" type="xsd:string">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">The pkg-prefix which will be used to do naming lookups. It is left empty by default.</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 <xsd:attribute name="jndi-URL" type="xsd:anyURI">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">The URL used to do naming lookups.</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 </xsd:extension>
 </xsd:complexContent>
 </xsd:complexType>
 <xsd:element name="jms-provider" substitutionGroup="jesb:provider" type="jesb:jms-provider-type" />

Sorry, I'm good now. I had added some debugging code to the courier which caused a problem.

Yes. I believe my original problem was that the queue connection factory URL was not set in EMS, so that the factory returned tcp://localhost:7222, which resulted in a failure when the JmsConnectionPool tried to create a new connection.

I have been using a queue which does not require authentication. I am going to move to a queue which does. As discussed earlier, this should require a patch, which we will contribute.

Just get around to this, and having a problem which probably does not belong here:

I extend the jbossesb schema to include jndi-principal and jndi-authentication, so that I now must have the jboss-esb.xml file point to a schema in the esb jar. However, I cannot figure out the syntax to have the jboss-esb.xml file point to this local schema. Any ideas?

Thanks. This looks lilke a good solution. In the long run, however, it might make sense to add the other naming attributes to the schema.

OK on t he JIRA item. I would see two alternatives here. First, we could create new attributes for all of the JNDI properties. As an alternative that would simplify the code (no required translation from "jndi-URL" to "java.naming.provider.url", for example), all of the JNDI attributes could be deprecated, and replaced with property elements.

I found that I needed to add code to the JmsConnectionPool class to handle optional authentication after the lookup, during the creation of queue and topic connections:

String userName = jndiEnvironment.getProperty(Context.SECURITY_PRINCIPAL);
 String password = jndiEnvironment.getProperty(Context.SECURITY_AUTHENTICATION);
 if (JMSEpr.QUEUE_TYPE.equals(destinationType)) {
 QueueConnectionFactory factory = (QueueConnectionFactory) factoryConnection;
 if (password != null) {
 jmsConnection = factory.createQueueConnection(userName, password);
 } else {
 jmsConnection = factory.createQueueConnection();
 }
 } else {
 TopicConnectionFactory factory = (TopicConnectionFactory) factoryConnection;
 if (password != null) {
 jmsConnection = factory.createTopicConnection(userName, password);
 } else {
 jmsConnection = factory.createTopicConnection();
 }
 }