Product SiteDocumentation Site

4. XTS

New features
JBTM-798 XTS service and initialization classes are now packaged in a JAR, for easy deployment outside JBossAS.
XTS service and initialization classes are now packaged into a separate JAR, to make it easier to deploy XTS into other application servers, such as Tomcat.
JBTM-799 You can now programmatically configure the WS-C and WS-T service endpoint URLs and paths.
In the past, WS-C and WS-T service endpoint URLs were hard-coded to conform to the pattern http://bindAddress:bindPort/war-name/service-name. This made it more difficult to deploy these services in different application servers. The path portion of the URLs of the service endpoints are now configurable.
Resolved issues
JBTM-518 WST 1.1 support is now included in the default configuration
WS-BA 0.2.1 only imported the WST 1.0-compliant class libraries, and required a patch to import the WST 1.1-compliant class libraries. The BA framework now includes a libs/ directory that hosts the WST 1.1-compliant libraries, so WST 1.0 and 1.1 are both supported in the default configuration.
JBTM-800 Deploying just the Coordinator component of XTS no longer causes an exception to be thrown.
The configuration instructions for deploying just the Coordinator component of XTS used to cause an exception, because the ATParticipantRecoveryModule was not available on the Participant component. he Participant and Coordinator recovery modules now create and install a manager if one is not already found, and the exception is no longer thrown.
JBTM-803 WSDLs ares no longer duplicated in the WS-C and WS-TX JARs.
The WSDLs have been removed from the WS-TX JAR. Both the WS-C and WS-TX JAR are needed by XTS, and the duplicate information was causing confusion without serving a purpose.
JBTM-804 The log of an invalid state SOAP fault now correctly reports that the participant is compensated, not cancelled.
An invalid state SOAP fault causes the participant to be compensated, but the log message used to report that was cancelled. This has been fixed, so that the log message now agrees with the actual action.
JBTM-816 Threads in several components have been given names, for easier profiling.
The threads in the transaction reaper, reaper worker, action store scanner, and the XTS reaper worker have been given names. This makes them easier to identify during profiling.