[jbossts-issues] [JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain
Paul Robinson (JIRA)
jira-events at lists.jboss.org
Mon Feb 11 09:32:56 EST 2013
[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753418#comment-12753418 ]
Paul Robinson commented on JBTM-986:
This is what, I think, we should do if no WS-TX transaction present:
* WSTXFeature enabled. Throw an Exception as the developer has explicitly stated that they wish to propagate transaction context for this port.
* WSTXFeature absent, server configured to propagate by default. log to trace and do nothing.
> 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: 1 week, 2 hours
> Remaining Estimate: 2 hours
> 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:
> BindingProvider bindingProvider = (BindingProvider) client;
> List<Handler> handlers = new ArrayList<Handler>(1);
> handlers.add(new JaxWSHeaderContextProcessor());
> 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:
> 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
More information about the jbossts-issues