[jboss-jira] [JBoss JIRA] (AS7-1497) XTS host/port info should be configurable

[Stefano Maestri (Resolved) (JIRA)]

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

Stefano Maestri resolved AS7-1497.
----------------------------------

    Resolution: Done


It's done bye

<xs:complexType name="xts-environment">
        <xs:annotation>
            <xs:documentation>
            <![CDATA[
                url configures XTS clients to use remote transaction coordination services.
                if it is left unset then clients employ the local coordinator services.
                the value should identify an OASIS WSTX 1.1 Activation Coordinator service.
                The local JBoss Activation Service url has the format
                    "http://<bindadd>r:<webport>/ws-c11/ActivationService"
                where
                    <bindaddr> is the app server bind address (localhost by default) and
                    <webport> is the unsecured JBoss Web server port (8080 by default).
            ]]>
            </xs:documentation>
        </xs:annotation>
        <xs:attribute name="url" type="xs:string" use="optional" />
    </xs:complexType>
                
> XTS host/port info should be configurable
> -----------------------------------------
>
>                 Key: AS7-1497
>                 URL: https://issues.jboss.org/browse/AS7-1497
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Transactions
>    Affects Versions: 7.0.0.Final
>            Reporter: Jonathan Halliday
>            Assignee: Stefano Maestri
>             Fix For: 7.1.0.CR1
>
>
> The XTS (web services transactions) service needs URL information (host, port, protocol) for
> a) constructing self-referencing URLs
> b) determining the coordinator service location, when running as a client of a remote coordinator.
> In the former case this should default to using information from the web container, except that where the web container supports both http and https this should be selectable.  However, the host and port should also be capable of being overridden, as in proxy situations the public and internal host/ports are not the same.
> In the latter case it should likewise default to the local coordinator URL constructed as above, but allow an alternative URL to be specified for situations where a remote coordinator is preferred.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira