-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
This is an umbrella issue for all the issues that were squashed into one commit in preperation for raising a pull request on the AS.
- is blocked by
-
JBTM-1335 Remove TXFramework SOAPHandler as JBossWS now supports CDI Interceptors
- Closed
-
JBTM-1002 Default bridge semantics for @WSAT annotated services
- Closed
-
JBTM-1050 Support BridgeType.NONE for @WSAT annotated services
- Closed
-
JBTM-747 Implement REST-tx specifications
- Closed
-
JBTM-978 Support REST-AT protocol in the TXFramework
- Closed
-
JBTM-999 Support plain old JAX-WS services in TXFramework
- Closed
-
JBTM-1048 Automatically setup server side handler chain
- Closed
-
JBTM-1408 TXFramework: XTS Handler not added to HandlerChain
- Closed
-
JBTM-972 LifecycleHandlers implemented via an EJB are invoked directly and not via the EJB stub
- Closed
-
JBTM-1046 Provide the TXFramework as a JBoss Module
- Closed
-
JBTM-1097 Use sensible names for generic transaction types
- Closed
-
JBTM-1100 TXFramework generic services
- Closed
-
JBTM-1114 Update TXFramework branch of JBossAS to use re-factored XTS subsytem
- Closed
-
JBTM-1168 Apply AS7 TXFramework commits to 5_BRANCH
- Closed
-
JBTM-1435 Prune TXFramework module dependencies
- Closed
-
JBTM-1477 Migrate TXF subsytem contents into relavent transport subsytem
- Closed