[
https://issues.apache.org/jira/browse/WSCOMMONS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi updated WSCOMMONS-472:
---------------------------------------------------
Attachment: patch.txt
this patch gives this feature to JMS sender. this code only tested with an
inonly service at client side.
eg.
UserTransactionManager userTransactionManager = new UserTransactionManager();
userTransactionManager.begin();
serviceClient.getOptions().setProperty(BaseConstants.JTA_TRANSACTION,
Constants.VALUE_TRUE);
serviceClient.fireAndForget(null);
// commit the transaction
userTransactionManager.commit();
> 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
> Reporter: Amila Chinthaka Suriarachchi
> Attachments: 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.
