March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1447) Create WebserviceFeature for TXBridge

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1447?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1447: ------------------------------------- Waiting for this to pass: http://172.17.131.2/job/narayana/176 > Create WebserviceFeature for TXBridge > ------------------------------------- > > Key: JBTM-1447 > URL: https://issues.jboss.org/browse/JBTM-1447 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 6 hours > > h2. Create: > * JTAOverWSATFeature > * Configuration option on the XTS Subsytem (defaultContextPropagation) > h2. Semantics: > h4. JTAOverWSATFeature absent, defaultContextPropagation disabled > This is the current OOTB experience for EAP 5&6. No handlers are activated automatically. The developer has to add them manually for all ports. When the developer does add the handlers, the MustUnderstand attribute of the WS-TX context is set to true. > h4. JTAOverWSATFeature absent, defaultContextPropagation enabled (Default OOTB) > All Web service requests that are made in the context of a JTA transaction will be bridged to WS-AT and the WS-AT context added to the request soap header. MustUnderstand is set to false. > h4. JTAOverWSATFeature enabled, defaultContextPropagation disabled > All Web service requests, for this port, that are made in the context of a JTA transaction will be bridged to WS-AT and the WS-AT context added to the request soap header. MustUnderstand is set to true. > h5. JTAOverWSATFeature disabled, defaultContextPropagation enabled > All Web service requests, for this port, don't bridge JTA. > h2. Implementation > The XTS Subsystem reads its config on boot. It carries out one of the following actions depending on what it finds: > # <defaultContextPropagation enabled=”true” /> (default OOTB config) > Add the Bridge handler initialized to be enabled by default then do [JBTM-986] after. Ensure that the Bridge handler is invoked before the WSTX handler. > # <defaultContextPropagation enabled=”false” /> > Add the Bridge handler initialized to be disabled by default then do [JBTM-986] after. Ensure that the Bridge handler is invoked before the WSTX handler. > # Config absent. > Error. Fail config parse. > h5. Bridge handler > Two handlers that delegate to the existing TXBridge handler: > # Disabled by default. Only invokes the TXBridge handler if the JTAOverWSATFeature is present and enabled. > # Enabled by default. Always invokes the TXBridge handler unless the JTAOverWSATFeature is present and disabled. > If the bridge detects the JTAOverWSATFeature, but no WSTXFeature, it adds the WSTXFeature to the invocation context (setting WSTXFeature.enabled = JTAOverWSATFeature.enabled). This is needed by the WSTX handler and prevents the developer from having to add both. > h5. Backwards compatibility > Existing applications (written before this feature was released) will be specifying Handler chains manually via the binding provider. Therefore we need to tolerate the situation where these handlers are added twice. Once for by this feature and again by the developer. > In particular the handlers added by this feature and [JBTM-986] should do nothing if the com.arjuna.mw.wst11.client.JaxWSHeaderContextProcessor handler is already in the handler chain. We could achieve this by adding this handler in the post handler chain. We could then look for an existing WSTX header and do nothing if we find it. This is just a suggestion, there may be a better way to achieve this behaviour. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Paul Robinson commented on JBTM-986: ------------------------------------ Waiting for this to pass: http://172.17.131.2/job/narayana/176 > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Time Spent: 2 weeks, 30 minutes > Remaining Estimate: 0 minutes > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > The feature should be "enabled" by default providing the feature is enabled in the XTS server config. > The quickstarts also need updated to use this. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1503) Update tools/maven to the 3.0.5

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1503?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1503: ------------------------------------- Waiting for this to pass: http://172.17.131.2/job/narayana/176 > Update tools/maven to the 3.0.5 > ------------------------------- > > Key: JBTM-1503 > URL: https://issues.jboss.org/browse/JBTM-1503 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1504) Update TXFramework tests to use WSTXFeature

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1504?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1504: ------------------------------------- Waiting for this to pass: http://172.17.131.2/job/narayana/176 > Update TXFramework tests to use WSTXFeature > ------------------------------------------- > > Key: JBTM-1504 > URL: https://issues.jboss.org/browse/JBTM-1504 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M2 > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1503) Update tools/maven to the 3.0.5

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1503?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1503: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/227 > Update tools/maven to the 3.0.5 > ------------------------------- > > Key: JBTM-1503 > URL: https://issues.jboss.org/browse/JBTM-1503 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1504) Update TXFramework tests to use WSTXFeature

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1504?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1504: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/227 > Update TXFramework tests to use WSTXFeature > ------------------------------------------- > > Key: JBTM-1504 > URL: https://issues.jboss.org/browse/JBTM-1504 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M2 > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1447) Create WebserviceFeature for TXBridge

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1447?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1447: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/narayana/pull/227 > Create WebserviceFeature for TXBridge > ------------------------------------- > > Key: JBTM-1447 > URL: https://issues.jboss.org/browse/JBTM-1447 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 6 hours > > h2. Create: > * JTAOverWSATFeature > * Configuration option on the XTS Subsytem (defaultContextPropagation) > h2. Semantics: > h4. JTAOverWSATFeature absent, defaultContextPropagation disabled > This is the current OOTB experience for EAP 5&6. No handlers are activated automatically. The developer has to add them manually for all ports. When the developer does add the handlers, the MustUnderstand attribute of the WS-TX context is set to true. > h4. JTAOverWSATFeature absent, defaultContextPropagation enabled (Default OOTB) > All Web service requests that are made in the context of a JTA transaction will be bridged to WS-AT and the WS-AT context added to the request soap header. MustUnderstand is set to false. > h4. JTAOverWSATFeature enabled, defaultContextPropagation disabled > All Web service requests, for this port, that are made in the context of a JTA transaction will be bridged to WS-AT and the WS-AT context added to the request soap header. MustUnderstand is set to true. > h5. JTAOverWSATFeature disabled, defaultContextPropagation enabled > All Web service requests, for this port, don't bridge JTA. > h2. Implementation > The XTS Subsystem reads its config on boot. It carries out one of the following actions depending on what it finds: > # <defaultContextPropagation enabled=”true” /> (default OOTB config) > Add the Bridge handler initialized to be enabled by default then do [JBTM-986] after. Ensure that the Bridge handler is invoked before the WSTX handler. > # <defaultContextPropagation enabled=”false” /> > Add the Bridge handler initialized to be disabled by default then do [JBTM-986] after. Ensure that the Bridge handler is invoked before the WSTX handler. > # Config absent. > Error. Fail config parse. > h5. Bridge handler > Two handlers that delegate to the existing TXBridge handler: > # Disabled by default. Only invokes the TXBridge handler if the JTAOverWSATFeature is present and enabled. > # Enabled by default. Always invokes the TXBridge handler unless the JTAOverWSATFeature is present and disabled. > If the bridge detects the JTAOverWSATFeature, but no WSTXFeature, it adds the WSTXFeature to the invocation context (setting WSTXFeature.enabled = JTAOverWSATFeature.enabled). This is needed by the WSTX handler and prevents the developer from having to add both. > h5. Backwards compatibility > Existing applications (written before this feature was released) will be specifying Handler chains manually via the binding provider. Therefore we need to tolerate the situation where these handlers are added twice. Once for by this feature and again by the developer. > In particular the handlers added by this feature and [JBTM-986] should do nothing if the com.arjuna.mw.wst11.client.JaxWSHeaderContextProcessor handler is already in the handler chain. We could achieve this by adding this handler in the post handler chain. We could then look for an existing WSTX header and do nothing if we find it. This is just a suggestion, there may be a better way to achieve this behaviour. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Gytis Trikleris updated JBTM-986: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/227 > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Time Spent: 2 weeks, 30 minutes > Remaining Estimate: 0 minutes > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > The feature should be "enabled" by default providing the feature is enabled in the XTS server config. > The quickstarts also need updated to use this. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1504) Update TXFramework tests to use WSTXFeature

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1504: ------------------------------------- Summary: Update TXFramework tests to use WSTXFeature Key: JBTM-1504 URL: https://issues.jboss.org/browse/JBTM-1504 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TXFramework Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.0.0.M2 -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1502) Update JBossWS dependencies to 4.2.0.Alpha1

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1502?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-1502. --------------------------------- Resolution: Duplicate Issue > Update JBossWS dependencies to 4.2.0.Alpha1 > ------------------------------------------- > > Key: JBTM-1502 > URL: https://issues.jboss.org/browse/JBTM-1502 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TxBridge, TXFramework, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2013