You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2009/06/03 00:40:07 UTC
[jira] Updated: (WSCOMMONS-472) improve jms transport to support
jta libraries
[ https://issues.apache.org/jira/browse/WSCOMMONS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated WSCOMMONS-472:
--------------------------------------
Fix Version/s: Transports 1.1
Reference to additional discussion:
http://markmail.org/thread/wmp5lbm6jcy2av47
> improve jms transport to support jta libraries
> ----------------------------------------------
>
> Key: WSCOMMONS-472
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-472
> Project: WS-Commons
> Issue Type: Improvement
> Components: Transport
> Reporter: Amila Chinthaka Suriarachchi
> Fix For: Transports 1.1
>
> 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.