[JBoss JIRA] Created: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
5:49 a.m.
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
Fix For: 4.15.3, 5.0.0.M1
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: http://www.atlassian.com/software/jira
10:14 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson updated JBTM-861:
-------------------------------
Assignee: Paul Robinson
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.M1
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: http://www.atlassian.com/software/jira
6:09 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
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: http://www.atlassian.com/software/jira
8:02 a.m.
New subject: [JBoss JIRA] Commented: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-861:
------------------------------------
{quote}
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.
{quote}
Am I right in thinking that this is referring to the coordinator'r bind address rather
than the default address that the Client should use to contact it's coordinator?
{quote}
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.
{quote}
Basically, you are saying that if no coordinator address and port is specified, in the
<xts/> section of the standalone.xml, then localhost:8080 is currently used. The
default should be set to whatever address JBoss is bound to as the default address and
whatever port JBossWS is running on (secure or normal) as the default port?
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: http://www.atlassian.com/software/jira
8:04 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson edited comment on JBTM-861 at 9/23/11 8:02 AM:
-------------------------------------------------------------
Andrew:
{quote}
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.
{quote}
Am I right in thinking that this is referring to the coordinator'r bind address rather
than the default address that the Client should use to contact it's coordinator?
{quote}
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.
{quote}
Basically, you are saying that if no coordinator address and port is specified, in the
<xts/> section of the standalone.xml, then localhost:8080 is currently used. The
default should be set to whatever address JBoss is bound to as the default address and
whatever port JBossWS is running on (secure or normal) as the default port?
was (Author: paul.robinson):
{quote}
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.
{quote}
Am I right in thinking that this is referring to the coordinator'r bind address rather
than the default address that the Client should use to contact it's coordinator?
{quote}
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.
{quote}
Basically, you are saying that if no coordinator address and port is specified, in the
<xts/> section of the standalone.xml, then localhost:8080 is currently used. The
default should be set to whatever address JBoss is bound to as the default address and
whatever port JBossWS is running on (secure or normal) as the default port?
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: http://www.atlassian.com/software/jira
11:51 a.m.
New subject: [JBoss JIRA] Commented: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn commented on JBTM-861:
----------------------------------
"Am I right in thinking that this is referring to the coordinator'r bind address
rather than the default address that the Client should use to contact it's
coordinator?"
No. This is referring to the address that an XTS client uses to contact it's
coordinator. When you deploy an XTS client it uses this globally configured property to
decide where to send its ActivationCoordinator request (which happens under the
client's call to UserTransaction.begin() or UserBusinessActivity.begin()).
The address at which the deployed XTS activation, registration and protocol-specific
coordination service endpoints get deployed is essentially determined by JBossWS which, in
turn, is at the mercy of JBossWeb. At present it will always be an endpoint locate via
localhost:8080. This is not user-configurable as far as XTS is concerned -- the config
belongs to JBossWeb settings in standalone.conf or, possibly, the AS7 command line (some
option like -b www.foo.org for backwards compatibility with prevous AS releases)
"Basically, you are saying that if no coordinator address and port is specified, in
the <xts/> section of the standalone.xml, then localhost:8080 is currently used. The
default should be set to whatever address JBoss is bound to as the default address and
whatever port JBossWS is running on (secure or normal) as the default port?"
At present if this URL is left unconfigured then the coordinator URL used by the client
code is http://localhost:8080/ws-c11/ActivatonCoordinator. This is ok for now but
eventually JbossWeb/JBossWS will start endpoints with a configured bind address, web port
and secure web port. If nothing is configured then it should use
http://<bindaddress>:<webport>/ws-c11/ActivatonCoordinator where the angle
bracketed terms need replacing with the values configured for JBossWeb/WS.
However, we should also allow for some halfway config. So, if for example the XTS config
specifies <coordinatorScheme>https</coordinatorScheme> then we should use
https://<bindaddress>:<securewebport>/ws-c11/ActivatonCoordinator i.e. we
should talk to the secure activation coordinator endpoint and, thence, the secure
registration and coordination services.
Similarly, if the XTS config additionally specifies
<coordinatorHost>foo.bar.org</coordinatorHost> then we should use
https://foo.bar.org:<securewebport>/ws-c11/ActivatonCoordinator and similarly
substitute whatever values are configured for config elements <coordinatorPort/>,
<coordinatorSecurePort/> and <coordinatorPath/>. None of these affect where
the local coordinator services are published. They merely control where client requests
get dispatched.
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: http://www.atlassian.com/software/jira
11:53 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn edited comment on JBTM-861 at 9/23/11 11:53 AM:
------------------------------------------------------------
"Am I right in thinking that this is referring to the coordinator'r bind address
rather than the default address that the Client should use to contact it's
coordinator?"
No. This is referring to the address that an XTS client uses to contact it's
coordinator. When you deploy an XTS client it uses this globally configured property to
decide where to send its ActivationCoordinator request (which happens under the
client's call to UserTransaction.begin() or UserBusinessActivity.begin()).
The address at which the deployed XTS activation, registration and protocol-specific
coordination service endpoints get deployed is essentially determined by JBossWS which, in
turn, is at the mercy of JBossWeb. At present it will always be an endpoint locate via
localhost:8080. This is not user-configurable as far as XTS is concerned -- the config
belongs to JBossWeb settings in standalone.conf or, possibly, the AS7 command line (some
option like -b www.foo.org for backwards compatibility with prevous AS releases)
"Basically, you are saying that if no coordinator address and port is specified, in
the <xts/> section of the standalone.xml, then localhost:8080 is currently used. The
default should be set to whatever address JBoss is bound to as the default address and
whatever port JBossWS is running on (secure or normal) as the default port?"
At present if this URL is left unconfigured then the coordinator URL used by the client
code is http://localhost:8080/ws-c11/ActivatonCoordinator. This is ok for now but
eventually JbossWeb/JBossWS will start endpoints with a configured bind address, web port
and secure web port. If nothing is defined in the XTS config then we should use
http://<bindaddress>:<webport>/ws-c11/ActivatonCoordinator as the coordinator
URL, where the angle bracketed terms need replacing with the values configured for
JBossWeb/WS.
However, we should also allow for some halfway config. So, if for example the XTS config
specifies <coordinatorScheme>https</coordinatorScheme> then we should use
https://<bindaddress>:<securewebport>/ws-c11/ActivatonCoordinator i.e. we
should talk to the secure activation coordinator endpoint and, thence, the secure
registration and coordination services.
Similarly, if the XTS config additionally specifies
<coordinatorHost>foo.bar.org</coordinatorHost> then we should use
https://foo.bar.org:<securewebport>/ws-c11/ActivatonCoordinator and similarly
substitute whatever values are configured for config elements <coordinatorPort/>,
<coordinatorSecurePort/> and <coordinatorPath/>. None of these affect where
the local coordinator services are published. They merely control where client requests
get dispatched.
was (Author: adinn):
"Am I right in thinking that this is referring to the coordinator'r bind
address rather than the default address that the Client should use to contact it's
coordinator?"
No. This is referring to the address that an XTS client uses to contact it's
coordinator. When you deploy an XTS client it uses this globally configured property to
decide where to send its ActivationCoordinator request (which happens under the
client's call to UserTransaction.begin() or UserBusinessActivity.begin()).
The address at which the deployed XTS activation, registration and protocol-specific
coordination service endpoints get deployed is essentially determined by JBossWS which, in
turn, is at the mercy of JBossWeb. At present it will always be an endpoint locate via
localhost:8080. This is not user-configurable as far as XTS is concerned -- the config
belongs to JBossWeb settings in standalone.conf or, possibly, the AS7 command line (some
option like -b www.foo.org for backwards compatibility with prevous AS releases)
"Basically, you are saying that if no coordinator address and port is specified, in
the <xts/> section of the standalone.xml, then localhost:8080 is currently used. The
default should be set to whatever address JBoss is bound to as the default address and
whatever port JBossWS is running on (secure or normal) as the default port?"
At present if this URL is left unconfigured then the coordinator URL used by the client
code is http://localhost:8080/ws-c11/ActivatonCoordinator. This is ok for now but
eventually JbossWeb/JBossWS will start endpoints with a configured bind address, web port
and secure web port. If nothing is configured then it should use
http://<bindaddress>:<webport>/ws-c11/ActivatonCoordinator where the angle
bracketed terms need replacing with the values configured for JBossWeb/WS.
However, we should also allow for some halfway config. So, if for example the XTS config
specifies <coordinatorScheme>https</coordinatorScheme> then we should use
https://<bindaddress>:<securewebport>/ws-c11/ActivatonCoordinator i.e. we
should talk to the secure activation coordinator endpoint and, thence, the secure
registration and coordination services.
Similarly, if the XTS config additionally specifies
<coordinatorHost>foo.bar.org</coordinatorHost> then we should use
https://foo.bar.org:<securewebport>/ws-c11/ActivatonCoordinator and similarly
substitute whatever values are configured for config elements <coordinatorPort/>,
<coordinatorSecurePort/> and <coordinatorPath/>. None of these affect where
the local coordinator services are published. They merely control where client requests
get dispatched.
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: http://www.atlassian.com/software/jira
11:55 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn edited comment on JBTM-861 at 9/23/11 11:54 AM:
------------------------------------------------------------
"Am I right in thinking that this is referring to the coordinator'r bind address
rather than the default address that the Client should use to contact it's
coordinator?"
No. This is referring to the address that an XTS client uses to contact it's
coordinator. When you deploy an XTS client it uses this globally configured property to
decide where to send its ActivationCoordinator request (which happens under the
client's call to UserTransaction.begin() or UserBusinessActivity.begin()).
The address at which the deployed XTS activation, registration and protocol-specific
coordination service endpoints get deployed is essentially determined by JBossWS which, in
turn, is at the mercy of JBossWeb. At present it will always be an endpoint locate via
localhost:8080. This is not user-configurable as far as XTS is concerned -- the config
belongs to JBossWeb settings in standalone.conf or, possibly, the AS7 command line (some
option like -b www.foo.org for backwards compatibility with prevous AS releases)
"Basically, you are saying that if no coordinator address and port is specified, in
the <xts/> section of the standalone.xml, then localhost:8080 is currently used. The
default should be set to whatever address JBoss is bound to as the default address and
whatever port JBossWS is running on (secure or normal) as the default port?"
At present if this URL is left unconfigured then the coordinator URL used by the client
code is http://localhost:8080/ws-c11/ActivatonCoordinator. This is ok for now but
eventually JbossWeb/JBossWS will start endpoints with a configured bind address, web port
and secure web port. If nothing is defined in the XTS config then we should use
http://<bindaddress>:<webport>/ws-c11/ActivatonCoordinator as the coordinator
URL, where the angle bracketed terms need replacing with the values configured for
JBossWeb/WS.
However, we should also allow for some halfway config. So, if for example the XTS config
specifies <coordinatorScheme>https</coordinatorScheme> then we should use
https://<bindaddress>:<securewebport>/ws-c11/ActivatonCoordinator i.e. we
should talk to the secure activation coordinator endpoint and, thence, the secure
registration and coordination services.
Similarly, if the XTS config additionally specifies
<coordinatorHost>foo.bar.org</coordinatorHost> then we should use
https://foo.bar.org:<securewebport>/ws-c11/ActivatonCoordinator. Similarly, we
should be willing to substitute whatever values are configured for config elements
<coordinatorPort/>, <coordinatorSecurePort/> and <coordinatorPath/>.
None of these affect where the local coordinator services are published. They merely
control where client requests get dispatched.
was (Author: adinn):
"Am I right in thinking that this is referring to the coordinator'r bind
address rather than the default address that the Client should use to contact it's
coordinator?"
No. This is referring to the address that an XTS client uses to contact it's
coordinator. When you deploy an XTS client it uses this globally configured property to
decide where to send its ActivationCoordinator request (which happens under the
client's call to UserTransaction.begin() or UserBusinessActivity.begin()).
The address at which the deployed XTS activation, registration and protocol-specific
coordination service endpoints get deployed is essentially determined by JBossWS which, in
turn, is at the mercy of JBossWeb. At present it will always be an endpoint locate via
localhost:8080. This is not user-configurable as far as XTS is concerned -- the config
belongs to JBossWeb settings in standalone.conf or, possibly, the AS7 command line (some
option like -b www.foo.org for backwards compatibility with prevous AS releases)
"Basically, you are saying that if no coordinator address and port is specified, in
the <xts/> section of the standalone.xml, then localhost:8080 is currently used. The
default should be set to whatever address JBoss is bound to as the default address and
whatever port JBossWS is running on (secure or normal) as the default port?"
At present if this URL is left unconfigured then the coordinator URL used by the client
code is http://localhost:8080/ws-c11/ActivatonCoordinator. This is ok for now but
eventually JbossWeb/JBossWS will start endpoints with a configured bind address, web port
and secure web port. If nothing is defined in the XTS config then we should use
http://<bindaddress>:<webport>/ws-c11/ActivatonCoordinator as the coordinator
URL, where the angle bracketed terms need replacing with the values configured for
JBossWeb/WS.
However, we should also allow for some halfway config. So, if for example the XTS config
specifies <coordinatorScheme>https</coordinatorScheme> then we should use
https://<bindaddress>:<securewebport>/ws-c11/ActivatonCoordinator i.e. we
should talk to the secure activation coordinator endpoint and, thence, the secure
registration and coordination services.
Similarly, if the XTS config additionally specifies
<coordinatorHost>foo.bar.org</coordinatorHost> then we should use
https://foo.bar.org:<securewebport>/ws-c11/ActivatonCoordinator and similarly
substitute whatever values are configured for config elements <coordinatorPort/>,
<coordinatorSecurePort/> and <coordinatorPath/>. None of these affect where
the local coordinator services are published. They merely control where client requests
get dispatched.
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: http://www.atlassian.com/software/jira
3:58 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson updated JBTM-861:
-------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M2)
(was: 4.15.x)
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: 5.0.0.Final
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: http://www.atlassian.com/software/jira
4:38 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-861:
-------------------------------
Fix Version/s: 4.15.4
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.4, 5.0.0.Final
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: http://www.atlassian.com/software/jira
9:54 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-861:
-------------------------------
Fix Version/s: 5.0.0.M2
(was: 5.0.0.Final)
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.4, 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: http://www.atlassian.com/software/jira
10:22 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-861:
-------------------------------
Priority: Critical (was: Major)
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
Priority: Critical
Fix For: 4.15.4, 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: http://www.atlassian.com/software/jira
6:55 a.m.
New subject: [JBoss JIRA] Commented: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-861:
------------------------------------
Thanks for the clarification,
So I think we have/need the following properties in the XTS config:
||Key||Description||Default||Exists?
|coordinatorUrl|The address of the client's
coordinator|http://<bindaddress>:<webport>/ws-c11/ActivatonCoordinator, where
<bindaddress> and <webport> is obtained from JBossWS|yes
|coordinatorScheme|"http" or "https"|"http" or whatever is
specified in the "coordinatorUrl" if present.|no
|deployedServices|A list of XTS services to be deployed|participant,coordinator,client|no
|enabledProtocols|Which WS-TX protocols to support|WS-AT,WS-TX|no
Do the deployed services currently bind to whatever JBossWS is configured to bind to, or
does this need fixing too?
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
Priority: Critical
Fix For: 4.15.4, 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: http://www.atlassian.com/software/jira
9:54 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson edited comment on JBTM-861 at 9/27/11 9:53 AM:
-------------------------------------------------------------
After talking to Andrew we are thinking that it would be sensible to only expose the
necessary XTS configuration properties in standalone-xts.xml, rather than all of them.
This is to reduce the support, testing and documentation burden.
The properties exposed are as follows:
||FullPropertyName||Default
|org.jboss.jbossts.xts11.coordinatorURL|http://<jbossws.bind.address>:<jbossws.http.port>/ws-c11/ActivationService
|org.jboss.jbossts.xts11.coordinator.scheme|http
|org.jboss.jbossts.xts11.coordinator.address|<jbossws.bind.address>
|org.jboss.jbossts.xts11.coordinator.port|<jbossws.http.port>
|org.jboss.jbossts.xts11.coordinator.path|/ws-c11/ActivationService
_Note:_ It is invalid to specify any of the org.jboss.jbossts.xts11.coordinator.*
properties if the org.jboss.jbossts.xts11.coordinatorURL is set.
The following properties are set by XTSPropertyManager by querying JBossWS. They are not
configurable via standalone-xts.xml:
||FullPropertyName||Set to
|org.jboss.jbossts.xts11.bind.address|<jbossws.bind.address>
|org.jboss.jbossts.xts11.bind.port|<jbossws.http.port>
|org.jboss.jbossts.xts11.bind.port.secure|<jbossws.https.port>
How do we decide whether to bind to http or https?
was (Author: paul.robinson):
Thanks for the clarification,
So I think we have/need the following properties in the XTS config:
||Key||Description||Default||Exists?
|coordinatorUrl|The address of the client's
coordinator|http://<bindaddress>:<webport>/ws-c11/ActivatonCoordinator, where
<bindaddress> and <webport> is obtained from JBossWS|yes
|coordinatorScheme|"http" or "https"|"http" or whatever is
specified in the "coordinatorUrl" if present.|no
|deployedServices|A list of XTS services to be deployed|participant,coordinator,client|no
|enabledProtocols|Which WS-TX protocols to support|WS-AT,WS-TX|no
Do the deployed services currently bind to whatever JBossWS is configured to bind to, or
does this need fixing too?
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
Priority: Critical
Fix For: 4.15.4, 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: http://www.atlassian.com/software/jira
10:16 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson edited comment on JBTM-861 at 9/27/11 10:16 AM:
--------------------------------------------------------------
After talking to Andrew we are thinking that it would be sensible to only expose the
necessary XTS configuration properties in standalone-xts.xml, rather than all of them.
This is to reduce the support, testing and documentation burden.
The properties exposed are as follows:
||FullPropertyName||Default
|org.jboss.jbossts.xts11.coordinatorURL|http://<jbossws.bind.address>:<jbossws.http.port>/ws-c11/ActivationService
|org.jboss.jbossts.xts11.coordinator.scheme|http
|org.jboss.jbossts.xts11.coordinator.address|<jbossws.bind.address>
|org.jboss.jbossts.xts11.coordinator.port|<jbossws.http.port>
|org.jboss.jbossts.xts11.coordinator.path|/ws-c11/ActivationService
_Note:_ It is invalid to specify any of the org.jboss.jbossts.xts11.coordinator.*
properties if the org.jboss.jbossts.xts11.coordinatorURL is set.
The following properties are set by XTSPropertyManager by querying JBossWS. They are not
configurable via standalone-xts.xml:
||FullPropertyName||Set to
|org.jboss.jbossts.xts11.bind.address|<jbossws.bind.address>
|org.jboss.jbossts.xts11.bind.port|<jbossws.http.port>
|org.jboss.jbossts.xts11.bind.port.secure|<jbossws.https.port>
Considerations:
* How do we decide whether to bind to http or https?
* Make sure the coordinator url is passed correctly in the XTS context to remote parties.
was (Author: paul.robinson):
After talking to Andrew we are thinking that it would be sensible to only expose the
necessary XTS configuration properties in standalone-xts.xml, rather than all of them.
This is to reduce the support, testing and documentation burden.
The properties exposed are as follows:
||FullPropertyName||Default
|org.jboss.jbossts.xts11.coordinatorURL|http://<jbossws.bind.address>:<jbossws.http.port>/ws-c11/ActivationService
|org.jboss.jbossts.xts11.coordinator.scheme|http
|org.jboss.jbossts.xts11.coordinator.address|<jbossws.bind.address>
|org.jboss.jbossts.xts11.coordinator.port|<jbossws.http.port>
|org.jboss.jbossts.xts11.coordinator.path|/ws-c11/ActivationService
_Note:_ It is invalid to specify any of the org.jboss.jbossts.xts11.coordinator.*
properties if the org.jboss.jbossts.xts11.coordinatorURL is set.
The following properties are set by XTSPropertyManager by querying JBossWS. They are not
configurable via standalone-xts.xml:
||FullPropertyName||Set to
|org.jboss.jbossts.xts11.bind.address|<jbossws.bind.address>
|org.jboss.jbossts.xts11.bind.port|<jbossws.http.port>
|org.jboss.jbossts.xts11.bind.port.secure|<jbossws.https.port>
How do we decide whether to bind to http or https?
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
Priority: Critical
Fix For: 4.15.4, 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: http://www.atlassian.com/software/jira
12:18 p.m.
New subject: [JBoss JIRA] (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-861:
-------------------------------
Priority: Minor (was: Critical)
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
Priority: Minor
Fix For: 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.
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:18 p.m.
New subject: [JBoss JIRA] (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-861:
-------------------------------
Description:
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.
was:
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.
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
Priority: Critical
Fix For: 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.
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:18 p.m.
New subject: [JBoss JIRA] (JBTM-861) Enhance XTS AS7 configuration
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-861:
-------------------------------
Summary: Enhance XTS AS7 configuration (was: XTS AS7 configuration is
incomplete and inadequate for binding/web port other than localhost:8080)
Fix Version/s: (was: 4.15.4)
Enhance XTS AS7 configuration
-----------------------------
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
Priority: Minor
Fix For: 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.
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
New subject: [JBoss JIRA] (JBTM-861) Enhance XTS AS7 configuration
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-861:
------------------------------------
Split into two issues. See https://issues.jboss.org/browse/JBTM-946 for other half of this
issue.
Enhance XTS AS7 configuration
-----------------------------
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
Priority: Minor
Fix For: 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.
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:07 a.m.
New subject: [JBoss JIRA] (JBTM-861) Enhance XTS AS7 configuration
[
https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-861:
-------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M2)
Enhance XTS AS7 configuration
-----------------------------
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
Priority: Minor
Fix For: 5.0.0.Final
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4528
days inactive
4656
days old
jbossts-issues@lists.jboss.org
19 comments
5 participants
participants (5)
-
Andrew Dinn (JIRA) -
Paul Robinson (Commented) (JIRA)
-
Paul Robinson (JIRA)
-
Paul Robinson (Updated) (JIRA)
-
Tom Jenkinson (JIRA)