Red Hat Bugzilla – Bug 779978
SOAPProcessor relies on new JBossWS CXF feature, not present in SOA
Last modified: 2011-02-10 22:59:42 EST
The invm invocation relies on BusHolder but this was not added until a later version of the JBossWS CXF integration.
Link: Added: This issue depends JBESB-3484
An alternative implementation has been provided, working around the use of BusHolder, but this requires modifications to the CXF configuration.
needs new WS and may need extra config
Resolved with revision 7340 of:
Take jbossesb-cxf.jar from ESB and add it to the WS CXF lib directory.
Modify the CXF installer and configuration for the ESB code.
Writer: Added: dlesage
Temporarily reopening to update release note info.
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3484
The SOA Platform's InVM invocation relied on BusHolder but this was not added until a later version of the JBossWS CXF integration. To rectify this, it was necessary to extend the JBossWS configuration to support InVM invocations. This means that the the ESB code can then choose whether to create a ServletControllerExt using the BusHolder or reference the instance stored in the extension 'bag'.