[
https://issues.apache.org/jira/browse/AXIS2-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen moved TRANSPORTS-5 to AXIS2-5527:
-------------------------------------------------
Component/s: (was: JMS)
JMS transport
Fix Version/s: (was: 1.7.0)
1.6.3
1.7.0
Key: AXIS2-5527 (was: TRANSPORTS-5)
Project: Axis2 (was: Axis2 Transports)
> improve jms transport to support jta libraries
> ----------------------------------------------
>
> Key: AXIS2-5527
> URL: https://issues.apache.org/jira/browse/AXIS2-5527
> Project: Axis2
> Issue Type: Improvement
> Components: JMS transport
> Reporter: Amila Chinthaka Suriarachchi
> Fix For: 1.7.0, 1.6.3
>
> Attachments: patch.txt, patch.txt
>
>
> Currently jms transport always looks an JNDI context to get the user
> transactions and jmsfactories.
> But this code is used only in JMSConnectionFactory. So an alternative
> implementation can be written by giving a class which extends the
> JMSConnctionFactory.
> This parameter can be set at the transport sender and receiver descriptor
> level.
> eg
> <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender">
> <parameter
> name="jmsConnectionFactoryClass">test.com.jms.client.AtomicosActiveMQJMSConnectionFactory</parameter>
> </transportSender>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
