[jbossts-issues] [JBoss JIRA] (JBTM-1963) Automatically added TXBridge handler should be optional
Gytis Trikleris (JIRA)
jira-events at lists.jboss.org
Tue Oct 8 05:09:03 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gytis Trikleris updated JBTM-1963:
----------------------------------
Description:
XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException.
The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory.
We could write a wrapper for the current handler, which will delegate the call only if the transaction is available.
was:
XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException.
The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory.
> Automatically added TXBridge handler should be optional
> -------------------------------------------------------
>
> Key: JBTM-1963
> URL: https://issues.jboss.org/browse/JBTM-1963
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, TxBridge
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Fix For: 5.0.0.Final
>
>
> XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException.
> The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory.
> We could write a wrapper for the current handler, which will delegate the call only if the transaction is available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list