It should be possible to re-use the JMS connection information from the
axis2.xml JMSSender when specifying JMS EPRs
--------------------------------------------------------------------------------------------------------------------
Key: SYNAPSE-183
URL: https://issues.apache.org/jira/browse/SYNAPSE-183
Project: Synapse
Issue Type: Improvement
Reporter: Asankha C. Perera
The JMSSender now supports the definition of connection factory entries as
follows:
<transportSender name="jms" class="org.apache.synapse.transport.jms.JMSSender">
<parameter name="myQueueConnectionFactory">
<parameter
name="java.naming.factory.initial">com.swiftmq.jndi.InitialContextFactoryImpl</parameter>
<parameter
name="java.naming.provider.url">smqp://10.25.51.38:18000/type=com.swiftmq.net.JSSESocketFactory;timeout=10000</parameter>
<parameter
name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
<parameter
name="java.naming.security.principal">xxxadapter</parameter>
<parameter
name="java.naming.security.credentials">xxxadapter</parameter>
</parameter>
</transportSender>
Thus it should be now possible to refer to this information when specifying a
JMS EPR as:
<syn:endpoint name="myJMSEndpoint">
<syn:address uri="jms:/[EMAIL PROTECTED]"/>
</syn:endpoint>
instead of specifying the IC class, url, username and password etc
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
