[jboss-jira] [JBoss JIRA] (AS7-6641) Enhance XTS AS7 configuration

[Paul Robinson (JIRA)]

     [ https://issues.jboss.org/browse/AS7-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Robinson moved JBTM-861 to AS7-6641:
-----------------------------------------

              Project: Application Server 7  (was: JBoss Transaction Manager)
                  Key: AS7-6641  (was: JBTM-861)
    Affects Version/s:     (was: 4.15.2)
          Component/s: XTS
                           (was: XTS)
             Security:     (was: Public)

    
> Enhance XTS AS7 configuration
> -----------------------------
>
>                 Key: AS7-6641
>                 URL: https://issues.jboss.org/browse/AS7-6641
>             Project: Application Server 7
>          Issue Type: Enhancement
>          Components: XTS
>            Reporter: Andrew Dinn
>            Priority: Minor
>
> 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.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira