[esb-issues] [JBoss JIRA] Commented: (JBESB-3484) SOAPProcessor relies on new JBossWS CXF feature, not present in SOA

[ https://jira.jboss.org/browse/JBESB-3484?page=com.atlassian.jira.plugin.s... ] Kevin Conner commented on JBESB-3484: ------------------------------------- The code has been changed so that it provides two mechanisms for handling the invm invocations with CXF. If BusHolder is present then it will use the current mechanism, if not then it requires modification of the jbossws.deployer configuration. In order to handle this in older versions of the JBossWS CXF integration (i.e. the productised version in EAP) it is necessary to extend the jbossws configuration to support our invm invocations. - a deployment aspect (ExtensionDeploymentAspect) is added to the jbossws deployer configuration to create an extension 'bag' as an attachment to each endpoint. - The servlet is extended so that it stores the ServletControllerExt in the extension 'bag' on initialisation - a further deployment aspect to force initialisation of the servlet on deployment (LoadOnStartupDeploymentAspect) The ESB code can then choose whether to create a ServletControllerExt using the BusHolder or reference the instance stored in the extension 'bag'. Note, the modification of the JBossWS CXF configuration should only be necessary within the SOA platform, at least until that version catches up with the version now supported in ESB. -- 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