[
https://issues.apache.org/jira/browse/SANDESHA2-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
irantha suwandarathna updated SANDESHA2-185:
--------------------------------------------
Attachment: sandesa2_JTA.diff
Attached initial Sandesha2 JTA transaction implementation diffs for review.
Last JTA transactions created in InvocationWorker spans up to inserting
SenderBean in ApplicationMessageProcessor (this transactions spans through the
service invocation).
At lease this works for the simplest configuration with no threads created in
between.
To enable JTA transactions, add following assertion to Sandesha2 policy
configuration,
<sandesha2:UseJTATransactions>true</sandesha2:UseJTATransactions>
Sandesha2 module configuration is changed as following to use JTA aware
datasource for persistance,
<moduleConfig>
<parameter name="db.dsName">java:DerbyDS</parameter>
<parameter name="db.icClass">org.jnp.interfaces.NamingContextFactory</parameter>
<parameter name="db.url">localhost:1099</parameter>
<parameter name="db.user">synapse</parameter>
<parameter name="db.password">synapse</parameter>
</moduleConfig>
> Sandesha2 need to support JTA transactions
> ------------------------------------------
>
> Key: SANDESHA2-185
> URL: https://issues.apache.org/jira/browse/SANDESHA2-185
> Project: Sandesha2
> Issue Type: New Feature
> Reporter: irantha suwandarathna
> Attachments: sandesa2_JTA.diff
>
>
> Sandesha2 need to be able to participate in JTA transactions.
--
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]
