[
https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-986:
------------------------------------
Feel free to update the time estimate once you have a feel for how long it would take.
Don't worry about increasing the time beyond 4d. This estimate was for me to do the
work after having done some of the prep.
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: Paul Robinson
Priority: Minor
Labels: assign
Fix For: 5.0.0.M2
Original Estimate: 4 days
Remaining Estimate: 4 days
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