]
Paul Robinson updated JBTM-861:
-------------------------------
Fix Version/s: 5.0.0.M2
(was: 5.0.0.M1)
XTS AS7 configuration is incomplete and inadequate for binding/web
port other than localhost:8080
-------------------------------------------------------------------------------------------------
Key: JBTM-861
URL:
https://issues.jboss.org/browse/JBTM-861
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.15.2
Reporter: Andrew Dinn
Assignee: Paul Robinson
Fix For: 4.15.x, 5.0.0.M2
The current integration of XTS into AS7 as an AS7 extension allows optional configuration
of the coordinator URL from the <xts/> element in the AS7 standalone configuration
file. No other configuration options are currently supported. This is inadequate on two
counts.
Firstly, if no URL is provided the coordinator address is located via localhost:8080 (or
localhost:8443 if an https scheme is employed). Similarly, the deployed web services are
assumed to have localhost:8080 addresses. The XTS extension ought to depend on JBoss web
and use the bind address and ports (non-secure and secure) JBoss web employs.
Secondly, XTS ought to support more precise configuration. IN particular, it ought to be
possible to enable or disable deployment of coordinator, participant or client services
independently and also to choose whether to deploy WS-AT or WS-BA services or both. This
requires selectively deploying only the required web service endpoints, selectively
executing the required initialization routines and selectively loading the required high
level service implementations and context factory implementations.
The XTS implementation has already been factored so as to to support such discriminated
bootstrapping. So this task only requires modifying the AS7 extension code to manage the
relevant configuration information and install the relevant values into the XTS
environment configuration beans before starting the XTS service.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: