[
https://issues.apache.org/jira/browse/TRANSPORTS-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen moved WSCOMMONS-472 to TRANSPORTS-5:
----------------------------------------------------
Project: Axis2 Transports (was: WS-Commons)
Key: TRANSPORTS-5 (was: WSCOMMONS-472)
Fix Version/s: 1.1.0
(was: Transports 1.1)
Component/s: JMS
(was: Transport)
> improve jms transport to support jta libraries
> ----------------------------------------------
>
> Key: TRANSPORTS-5
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-5
> Project: Axis2 Transports
> Issue Type: Improvement
> Components: JMS
> Reporter: Amila Chinthaka Suriarachchi
> Fix For: 1.1.0
>
> 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.
-
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]
