[
https://issues.jboss.org/browse/JBTM-980?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-980:
-------------------------------
Fix Version/s: 5.0.0.M2
(was: 5.0.1.Final)
Description: Currently the developer specifies the type of transaction that the
service and any lifecycle callbacks expect to participate in. For example, via @WSBA or
@RESTJDI class level annotation. However, the participation requirements for these
protocols is very similar. It would be better if the developer could simply specify that
the service can participate in any forward compensation style transaction (such as
REST-JDI or WS-BA) using a @BA annotation. The type of transaction is determined by the
inflowed TX context. (was: Currently the developer specifies the type of transaction that
the service and any lifecycle callbacks expect to participate in. For example, via @WSBA
or @RESTJDI class level annotation. However, the participation requirements for these
protocols is very similar. It would be better if the developer could simply specify that
the service can participate in any forward compensation style transaction (such as
REST-JDI or WS-BA) using a @BA annotation. The type of transaction is determined by the
inflowed TX context.
To take this a step further, by leaving off the transaction type annotation altogether,
the service could participate in any transaction type. Of course, this would require a mix
of ACID and forward compensation lifecycle callbacks to be present. Again, the inflow TX
context would decide the actual TX type used. )
Support generic participants that can partcipate in multiple TX
protocol types
-------------------------------------------------------------------------------
Key: JBTM-980
URL:
https://issues.jboss.org/browse/JBTM-980
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: TXFramework
Reporter: Paul Robinson
Assignee: Paul Robinson
Labels: TXFramework
Fix For: 5.0.0.M2
Currently the developer specifies the type of transaction that the service and any
lifecycle callbacks expect to participate in. For example, via @WSBA or @RESTJDI class
level annotation. However, the participation requirements for these protocols is very
similar. It would be better if the developer could simply specify that the service can
participate in any forward compensation style transaction (such as REST-JDI or WS-BA)
using a @BA annotation. The type of transaction is determined by the inflowed TX context.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira