Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-986

Automatically setup the client side handler chain

    XMLWordPrintable

Details

    • Feature Request
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • None
    • 5.0.0.M2
    • XTS

    Description

      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());
      bindingProvider.getBinding().setHandlerChain(handlers);
      

      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/src/test/java/org/jboss/test/ws/jaxws/samples/webserviceref/
      http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/src/test/resources/jaxws/samples/webserviceref/
      http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/src/test/ant-import/build-samples-jaxws.xml

      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.

      Attachments

        Issue Links

          Activity

            People

              gtrikler@redhat.com Gytis Trikleris (Inactive)
              paul.robinson@redhat.com Paul Robinson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 days Original Estimate - 4 days
                  4d
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 weeks, 30 minutes
                  2w 30m