[
https://issues.jboss.org/browse/AS7-1497?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1497:
---------------------------------------
Stefano, last week Jaikiran added support for an outgoing-socket-binding in a socket
binding group. This encapsulates configuration information for a client side socket, which
could either be used by the AS itself, if it is the client, or could be used to provide
information to an external client (e.g. the above "a) constructing self-referencing
URLs".)
So, if this configuration information isn't coming from the web connector service
(e.g. a proxy situation), please use a reference to an outgoing-socket-binding to get it.
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