| Summary: | SOAPProcessor relies on new JBossWS CXF feature, not present in SOA | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Kevin Conner <kevin.conner> |
| Component: | JBossESB | Assignee: | Julian Coleman <jcoleman> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.1.0.ER1 | ||
| Target Milestone: | --- | ||
| Target Release: | 5.1.0 GA, 5.1.0.ER5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2338 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-11 03:59:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Kevin Conner
2010-09-22 11:40:48 UTC
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: build-tools/builders/eap/post-patch/patch_wscxf_webapp.xml build-tools/builders/eap/resource/patch_wscxf_webapp_macros.xsl (added) build-tools/builders/eap/resource/patch_wscxf_webapp_beans.xsl (added) build-tools/builders/esb/build.xml Commit message: SOA-2338 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'. |