ws-commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (WSCOMMONS-472) improve jms transport to support jta libraries
Date Sun, 31 May 2009 21:46:07 GMT

     [ https://issues.apache.org/jira/browse/WSCOMMONS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Veithen updated WSCOMMONS-472:
--------------------------------------

    Component/s: Transport

> 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
>         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.


Mime
View raw message