WS-BA to 2xJTA bridge --------------------- Key: JBTM-1099 URL: https://issues.jboss.org/browse/JBTM-1099 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public(Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.Final Original Estimate: 2 days Remaining Estimate: 2 days Allow a TXFramework @ACID enabled class to offer REST-AT, WS-AT and regular EJB (JTS xor Remote JTA) endpoints at the same time. Also allow switching between protocols, whilst only needing to change the protocol specific annotations. E.g, drop @WebService and @WebMethod, Replace with @Get and @Path.

WS-BA to 2xJTA bridge --------------------- Key: JBTM-1099 URL: https://issues.jboss.org/browse/JBTM-1099 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public(Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.Final Original Estimate: 1 week Remaining Estimate: 1 week It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when if a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated. There may be other windows in Compensate and Close. This needs investigating. The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close. This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.

WS-BA to 2xJTA bridge --------------------- Key: JBTM-1099 URL: https://issues.jboss.org/browse/JBTM-1099 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public(Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Labels: assign Fix For: 5.0.0.Final Original Estimate: 1 week Remaining Estimate: 1 week It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when if a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated. There may be other windows in Compensate and Close. This needs investigating. The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close. This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.