Uploaded image for project: 'JBoss ESB'
  1. JBoss ESB
  2. JBESB-3376

Provide support for SOAPProcessor to invoke CXF WS Endpoints

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.7
    • Fix Version/s: 4.9
    • Component/s: Web Services
    • Labels:
      None

      Description

      SOAPProcessor uses JBossWS-SPI to invoke the WS Endpoint. This is not compatible with CXF.

      java.lang.UnsupportedOperationException: Not yet supported
      at org.jboss.soa.esb.actions.soap.adapter.SOAPProcessorServletContext.getAttribute(SOAPProcessorServletContext.java:45)
      at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:53)
      at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:187)

      SOAPProcessor issue is not just with the mock classes. Even if the mock class is fixed to support attributes, the CXF's JBossWS SPI implementation[1] does not handle this well. The reason is that it expects a ServletControllerExt in the ServletContext and we cannot create this by ourselves. It has to be set by CXF somehow inside the RequestHandlerImpl. Using the JBossWS-SPI is not possible on CXF ATM.

      [1] http://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-3.3.1.SP1/modules/server/src/main/java/org/jboss/wsf/stack/cxf/RequestHandlerImpl.java

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mageshbk Magesh Bojan
                  Reporter:
                  mageshbk Magesh Bojan
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: