[esb-issues] [JBoss JIRA] Created: (JBESB-3376) Provide support for SOAPProcessor to invoke CXF WS Endpoints

Provide support for SOAPProcessor to invoke CXF WS Endpoints ------------------------------------------------------------ Key: JBESB-3376 URL: https://jira.jboss.org/browse/JBESB-3376 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Magesh Kumar B Assignee: Magesh Kumar B Fix For: 4.9 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.S... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira