| Summary: | Support Patch for SOA-3148, SOAPProxy throws SAXParseException when soapAction is missing in WSDL and message has attachment | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Rick Wagner <rwagner> | ||||||
| Component: | unspecified | Assignee: | Rick Wagner <rwagner> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 5.0.2 | CC: | bbelovic, dpalmer, dward, jdelong, kevin.conner, rwagner, tcunning | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | One Off Releases | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-3172 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: |
SOA-P 5.0.2 -- customer patched codebase
|
|||||||
| Last Closed: | 2011-11-30 19:52:02 UTC | Type: | Support Patch | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
The fix for this is to introduce new behaviour into SOAPProxy. At present SOAPProxy does not understand multi-part HTTP formats, so does not work with SOAP attachments. We need to add functionality into SOAPProxy so that it can identify the different parts and extract the SOAP body. Link: Added: This issue relates to SOA-3148 JBESB-3642 if fixed and closed. Attachment: Added: jbossesb-soap.jar Patch Instructions: Removed: PATCH NAME:
[patch id of the support patch, e.g., JBPAPP-7890. This will not be known until you
create the jira, so this section will have to be edited after the creation.]
PRODUCT NAME:
JBoss Enterprise Application Platform
VERSION:
5.1.0
SHORT DESCRIPTION:
[summarze what problem this patch fixes. Often based on the jira Summary]
LONG DESCRIPTION:
[detailed explanation of the problem. Often based on the jira Description]
MANUAL INSTALL INSTRUCTIONS:
[indicate how a user should manually install this patch.]
To install this patch replace the following with the jars included in this patch:
$JBOSS_HOME/jboss-as/lib/some.jar
$JBOSS_HOME/jboss-as/lib/another.jar
COMPATIBILITY:
[known usages and known combinations that don't work]
DEPENDENCIES:
[list any patches this patch is dependent on, i.e., is required to be applied with this patch]
SUPERSEDES:
[list any patches this patch supersedes, i.e., replaces]
SUPERSEDED BY:
[list any patches this patch is superseded by]
CREATOR:
[author of this patch, usually the SEG creating the jira]
DATE:
[date these instructions were written]
Added: PATCH NAME: SOA-3172
PRODUCT NAME: SOA-P
VERSION: 5.0.2
SHORT DESCRIPTION: SOAPProxy throws SAXParseException
LONG DESCRIPTION: SOAPProxy throws SAXParseException when SOAPAction is missing in WSDL
MANUAL INSTALL INSTRUCTIONS: Replace jbossesb-soap.jar in all locations. (See $SERVER/deploy/soap.esb)
COMPATIBILITY: This patch specifically built on top of previous 5.0.2 patch for this customer
DEPENDENCIES: N/A
SUPERSEDES: Previous patch for this customer
SUPERSEDED BY: N/A
CREATOR: Tom C.
DATE: 07/22/2011
Patched SOA-P zips can be found at http://jawa05.englab.brq.redhat.com/patches/SOA-3172 Is this correct SVN url for patched ESB bits (ESB sources containing fix for customer) https://svn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_7_CP2_SOA_3172 ? I'm not sure if that's what you should be building from, but I just looked, and it does indeed contain the fix I put in. I think Boris is just asking so he can review the code. Boris - yes, that's the correct version to be looking at and Doug Palmer supplied the SOA JARs to test. The fixes contained in jbossesb-soap.jar attached to this JIRA solve SOAPProxy's SAXParseException problem. But jbossesb-soap.jar attached to this JIRA and the same jar in zipped distro doesn't contain JBOSSCOD.RSA and JBOSSCOD.SF files. Also note that MANIFEST.MF doesn't contain SHA1 sums this jar's classes. QE will continue in testing after both files are in place. All other jar files in soap.esb directory contain signing information except for jbossesb-soap.jar. QE will continue in testing after all jar will contain proper signing information. QE has finished the testing of this patch. All QE tests passed and the patch fixes bugs reported by customer. 217f8ef72f7aecc74c810129c276aca1 jbossesb-soap.jar This patch is applicable to JBoss SOA-P 5.0.2. It is available for download from the following location: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=7863 Patch Repository Link: Added: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=7863 I just realized that this jira still contains unsigned version of the jar. This version was uploaded on customer portal, please can someone attached signed version to this jira and upload signed jar to customer portal. Customer should get correct version of jar. Signed jar can be found here: http://jawa05.englab.brq.redhat.com/patches/SOA-3172/ Signed version of patch. Attachment: Added: SOA-3172-patch.zip Upload of signed jar has been requested. Resolved. |
Patch Instructions: PATCH NAME: SOA-3172 PRODUCT NAME: SOA-P VERSION: 5.0.2 SHORT DESCRIPTION: SOAPProxy throws SAXParseException LONG DESCRIPTION: SOAPProxy throws SAXParseException when SOAPAction is missing in WSDL MANUAL INSTALL INSTRUCTIONS: Replace jbossesb-soap.jar in all locations. (See $SERVER/deploy/soap.esb) COMPATIBILITY: This patch specifically built on top of previous 5.0.2 patch for this customer DEPENDENCIES: N/A SUPERSEDES: Previous patch for this customer SUPERSEDED BY: N/A CREATOR: Tom C. DATE: 07/22/2011 Patch Repository Link: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=7863 Support Case Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007C9e5&sfdc.override= project_key: SOA When the message has an attachment and no SOAPAction is specified, SOAPProxy throws an Exception. Note: This patch is needed for HP, they already have one patch so we have to build on that source base. The existing patch JIRA is SOA-2984.