Andrew Dinn closed JBTM-265.
This is now complete in so far as functionality is concerned. The current trunk allows a
CXF compatible version of XTS to be built and deployed as a sar into a JBossAS with
JBossWS/CXF deployed. This passes all the unit tests and runs the XTS demo.
Note, however that for this to work it is necessary to use a version of CXF which includes
patches for CXF-2161 and CXF-2167. Fixes for these have been included in CXF 2.1.5 and
2.2.1. The current JBossWS/CXF (3.1.1) is based on 2.2.0 and the preceding one (3.1.0) on
2.1.4 so until WS upgrades to a newer release this can't be used without either
patching or upgrading the CXF stack.
Note also that the interop tests have not yet been run on CXF because of a bug in the
JBossWS spi layer.
Also, there is still the need to do a little bit of repackaging to avoid the need for XTS
to be dual source and to simplify testing of the CXF version. Ideally the CXF/Native
versions of the MAP classes (which provide a common interface to the WSA management
classes) would probably be best moved down into the stack-specific parts of JBossWS. That
way the correct library would be deployed as part of the JBossWS deployment and only one
version of the XTS sar would need to be built and deployed.
Port XTS to CXF/XFire
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.2.3.SP5
Reporter: Mark Little
Assignee: Andrew Dinn
Fix For: 4.7.0
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira