| Summary: | Upgrade jbossws-cxf to cxf-2.4.1 to overcome signature verification regression | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Gary Brown <gary.pi4tech> |
| Component: | JBossWS, EAP | Assignee: | Jim Ma <ema> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | unspecified | CC: | asoldano, ema, gary.pi4tech |
| Target Milestone: | --- | ||
| Target Release: | 5.2.0 GA, 5.2.0.ER2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3146 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-05 08:42:10 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Gary Brown
2011-07-04 08:26:20 UTC
We can't and are not going to upgrade to Apache CXF 2.4.x in JBossWS 3.4.x or lesser. The move to CXF 2.4.x requires integration changes that are in JBossWS 4.x only. As this has been isolated into an Apache CXF issue, we need to backport the fix for that issue into our maintenance fork of the CXF version that's consumed by EAP / SOA-P as we did for other issues. We can stick with jbossws-cxf 3.2.2.GA in the community, so I am fine with this just being fixed for EAP/SOA-P. Link: Added: This issue relates to JBPAPP-6822 The fix has been ported in EAP 5.1.1 branch . Gary, do you know if the SOA 5.2 will consume EAP 5.1.1 ? Thanks. Hi Jim, as far as I am aware it will be 5.1.1 in SOA-P 5.2. Thanks Gary, then I update this issue to resolved. Did not make EAP 5.1.1, need to keep open to track Link: Added: This issue depends JBPAPP-6834 Release Notes Docs Status: Added: Not Yet Documented Writer: Added: dlesage Patch jar integrated into SOA-P for ER2. Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required Verified in SOA 5.2 ER6 - bpel_secure_invoke quickstart is running fine now. |