[jbossts-issues] [JBoss JIRA] Commented: (JBTM-799) Provide a way to configure the WS-C and WS-T service endpoint URLs/paths

[Misty Stanley-Jones (JIRA)]

    [ https://jira.jboss.org/browse/JBTM-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568835#comment-12568835 ] 

Misty Stanley-Jones commented on JBTM-799:
------------------------------------------

Release Note:

Cause: The paths to the exposed service endpoints of WS-C and WS-T services was hard-coded, based on <replaceable>war-name</replaceable>/<replaceable>service-name</replaceable> as the path. For instance, the ActivationService URL was expected to be http://<replaceable>bindAddress</replaceable>:<replaceable>bindPort</replaceable>/ws-c11/ActivationService.

Consequence: Deploying in another environment, such as your own web application running on Tomcat with CXF, you may need to change the endpoint URL, and it may be difficult.

Fix: the path portion of the URL for every component is configurable by the user.

Result: It is easier to deploy WS-C and WS-T service endpoints on different application servers.

> Provide a way to configure the WS-C and WS-T service endpoint URLs/paths
> ------------------------------------------------------------------------
>
>                 Key: JBTM-799
>                 URL: https://jira.jboss.org/browse/JBTM-799
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: XTS
>    Affects Versions: 4.13.0
>            Reporter: Mauro Molinari
>            Assignee: Andrew Dinn
>             Fix For: 4.14.0
>
>
> As of now, the paths to get to the exposed service endpoints of the different WS-C and WS-T services is hard coded, based on the JBossAS/JBossWS convention of using the path <war-name>/<service-name> (where <war-name> is the name of the war containing the service). For instance, the ActivationService URL is expected to be http://bindAddress:bindPort/ws-c11/ActivationService.
> However, if you want to deploy to another environment (for instance: your own web application, running on Tomcat with CXF), you may want (or you may even be forced) to change the endpoint URLs as you like.
> Since with CXF (and, in general, with JAX-WS) you are free to expose a webservice with the URL you prefer, the best would be to make XTS configurable in this sense.
> Every component (Client, Participant, Coordinator) should be improved to let the user specify the URL at which he wants to expose the corresponding webservices (i.e.: for WS-AT, it's the CompletionInitiator on the Client, the Participant on the Participant, the Coordinator, CompletionCoordinator, Activation and Registration on the Coordinator). More precisely, since the bindAddress and bindPort are already settable, just the path part should be made configurable.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira