You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "irantha suwandarathna (JIRA)" <ji...@apache.org> on 2008/11/13 13:05:44 UTC
[jira] Created: (SYNAPSE-480) Transaction mediator for synapse
Transaction mediator for synapse
--------------------------------
Key: SYNAPSE-480
URL: https://issues.apache.org/jira/browse/SYNAPSE-480
Project: Synapse
Issue Type: New Feature
Components: Core
Affects Versions: FUTURE
Reporter: irantha suwandarathna
Fix For: FUTURE
New synapse mediator to manipulate JTA transactions.
syanpse.xml configuration for new mediator:
<transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
Meaning of action attribute values are explained below:
new : create a new jta transaction. generate a fault if a transaction already exist.
use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
commit : commit transaction. generate a fault if no transaction exist.
rollback: rollback transaction. generate a fault if no transaction exist.
suspend: suspend transaction. generate a fault if no transaction exist.
resume: resume transaction. generate a fault if no transaction exist.
There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: tx_mediator.patch
Tested with Jboss.
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna resolved SYNAPSE-480.
-------------------------------------------
Resolution: Fixed
patch attached.
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: (was: axis2_transaction.patch)
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: tx_mediator.patch
Change according to axis2 transaction changes
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch, tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: axis2_transaction.patch
Axis2 patch to support transaction configuration in axis2.xml
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: axis2_transaction.patch, tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648078#action_12648078 ]
irantha suwandarathna commented on SYNAPSE-480:
-----------------------------------------------
Until we add a new transaction configuration section to axis2.xml, we can add transaction JNDI configurations into the transaction mediator itself to to take this off the ground quickly.
For example:
<transaction action="new" >
<parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
<parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
<parameter name="UserTransactionJNDIName">UserTransaction</parameter>
</transaction>
WDYT?
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-480) Transaction mediator for synapse
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647998#action_12647998 ]
Asankha C. Perera commented on SYNAPSE-480:
-------------------------------------------
The most common case would be a transactional receipt and processing of a message, where a rollback should imply the message being returned to the source for a subsequent retry.
A JTA transaction is only useful when more than one resource is involved, and the most common being JMS and DB's. Thus, the value of a transactional sequence (which is a list) would be reduced, since this implies that the message was not received transactionally - e.g. maybe over http/s. Thus the proposed mediator seems like a good first step, as it allows one to realize the benefits of transactionality, without burning it too much into the core.
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: tx_mediator.patch
fixed tx mediator according to axis2 transaction configuration implementation.
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch, tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: tx_mediator.patch
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: (was: tx_mediator.patch)
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: (was: tx_mediator.patch)
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-480) Transaction mediator for synapse
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reassigned SYNAPSE-480:
------------------------------------
Assignee: Ruwan Linton
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Assignee: Ruwan Linton
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch, tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-480) Transaction mediator for synapse
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved SYNAPSE-480.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: FUTURE)
1.3
Applied the patch with minor modifications
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Assignee: Ruwan Linton
> Fix For: 1.3
>
> Attachments: tx_mediator.patch, tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton updated SYNAPSE-480:
---------------------------------
Affects Version/s: (was: FUTURE)
1.2
changed the affects version
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.2
> Reporter: irantha suwandarathna
> Assignee: Ruwan Linton
> Fix For: 1.3
>
> Attachments: tx_mediator.patch, tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-480) Transaction mediator for synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
irantha suwandarathna updated SYNAPSE-480:
------------------------------------------
Attachment: tx_mediator.patch
Need fix up the mediator after completing Axis2 configuration changes.
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Issue Comment Edited: (SYNAPSE-480) Transaction mediator for
synapse
Posted by "irantha suwandarathna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650144#action_12650144 ]
irantha edited comment on SYNAPSE-480 at 11/24/08 11:42 PM:
--------------------------------------------------------------------------
Tested with Jboss.
Scenario : Update two databases within a jta transaction.
<!-- Synapse configuration used for testing this scenario -->
<definitions xmlns="http://ws.apache.org/ns/synapse">
<sequence name="myFaultHandler">
<log level="custom">
<property name="text" value="** Rollback Transaction**"/>
</log>
<transaction action="rollback"/>
<send/>
</sequence>
<sequence name="main" onError="myFaultHandler">
<in>
<send>
<endpoint>
<address uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
</endpoint>
</send>
</in>
<out>
<transaction action="new" />
<log level="custom">
<property name="text" value="** Reporting to the Database synapse**"/>
</log>
<dbreport xmlns="http://ws.apache.org/ns/synapse">
<connection>
<pool>
<dsName>java:XADerbyDS</dsName>
<icClass>org.jnp.interfaces.NamingContextFactory</icClass>
<url>localhost:1099</url>
<user>synapse</user>
<password>synapse</password>
</pool>
</connection>
<statement>
<sql>update company set price=? where name =?</sql>
<parameter expression="//m0:return/m0:last/child::text()"
xmlns:m0="http://services.samples/xsd" type="DOUBLE"/>
<parameter expression="//m0:return/m0:symbol/child::text()"
xmlns:m0="http://services.samples/xsd" type="VARCHAR"/>
</statement>
</dbreport>
<log level="custom">
<property name="text" value="** Reporting to the Database synapse2**"/>
</log>
<dbreport xmlns="http://ws.apache.org/ns/synapse">
<connection>
<pool>
<dsName>java:XADerbyDS2</dsName>
<icClass>org.jnp.interfaces.NamingContextFactory</icClass>
<url>localhost:1099</url>
<user>synapse</user>
<password>synapse</password>
</pool>
</connection>
<statement>
<sql>update company set price=? where name =?</sql>
<parameter expression="//m0:return/m0:last/child::text()"
xmlns:m0="http://services.samples/xsd" type="DOUBLE"/>
<parameter expression="//m0:return/m0:symbol/child::text()"
xmlns:m0="http://services.samples/xsd" type="VARCHAR"/>
</statement>
</dbreport>
<transaction action="commit" />
<send/>
</out>
</sequence>
</definitions>
was (Author: irantha):
Tested with Jboss.
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-480) Transaction mediator for synapse
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647991#action_12647991 ]
Andreas Veithen commented on SYNAPSE-480:
-----------------------------------------
My feeling is that for many use cases this mediator is too low level and that (in addition) we should have a ListMediator that executes a sequence of mediators in a transaction and that handled commit/rollback automatically. It could also be interesting to have transaction support at the ProxyService level so that the user can easily specify that the whole flow (in sequence & out sequence) is executed in a transaction. Again in that case ProxyService should take care of commit/rollback automatically.
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Reopened: (SYNAPSE-480) Transaction mediator for synapse
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reopened SYNAPSE-480:
----------------------------------
> Transaction mediator for synapse
> --------------------------------
>
> Key: SYNAPSE-480
> URL: https://issues.apache.org/jira/browse/SYNAPSE-480
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: FUTURE
> Reporter: irantha suwandarathna
> Assignee: Ruwan Linton
> Fix For: FUTURE
>
> Attachments: tx_mediator.patch, tx_mediator.patch
>
>
> New synapse mediator to manipulate JTA transactions.
>
> syanpse.xml configuration for new mediator:
> <transaction action="new|use-existing-or-new|fault-if-no-tx|commit|rollback|suspend|resume"/>
>
> Meaning of action attribute values are explained below:
> new : create a new jta transaction. generate a fault if a transaction already exist.
> use-existing-or-new : create a new jta transaction. do nothing if a transaction exist.
> fault-if-no-tx : generate a fault if no transaction exist. do nothing if a transaction exist.
> commit : commit transaction. generate a fault if no transaction exist.
> rollback: rollback transaction. generate a fault if no transaction exist.
> suspend: suspend transaction. generate a fault if no transaction exist.
> resume: resume transaction. generate a fault if no transaction exist.
>
> There will be a new transaction configuration section in axis2.xml to define UserTransaction (used to create a new transaction) and TransactionManager (need for suspend and resume actions ) JNDI parameters.
> newly created usertransaction is assigned to axis2 message context property named BaseConstants.USER_TRANSACTION and newly created transaction manager is assigned to axis2 message context property named BaseConstants.TRANSACTION_MANAGER
>
> Same message context property is used by JMS transport when creating a new usertransaction.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org