| Summary: | SOAPProxy throws SAXParseException when soapAction is missing in WSDL and message has attachment | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jeff DeLong <jdelong> |
| Component: | JBossESB | Assignee: | tcunning |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0 GA | CC: | dward, kevin.conner |
| Target Milestone: | --- | ||
| Target Release: | 5.2.0.ER3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3148 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
SOA-P 5.1 running on Mac 10.6 JDK 1.6
|
|
| Last Closed: | 2011-11-04 11:06:09 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
Jeff DeLong
2011-07-05 19:14:37 UTC
This sounds like it may be JBESB-3585, in which case it has already been fixed. Just looked at JBESB-3585 and the current code, it assumes that the content is just XML and does no checking for attachments. This is a definitely a new issue. Link: Added: This issue Cloned to SOA-3173 Link: Added: This issue is related to SOA-3172 Help Desk Ticket Reference: Added: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007C9e5&sfdc.override= JBESB-3636 has been fixed and closed. It looks like David already fixed this on the 4_10_CP branch. Resolving. Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3148 SOAPProxy threw a SAXParseException when the the WSDL was missing a soapAction and the message had attachment. A code fix has rectified this problem and, as a result, users will no longer encounter this exception. Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-3148 SOAPProxy threw a SAXParseException when the the WSDL was missing a soapAction and the message had attachment. A code fix has rectified this problem and, as a result, users will no longer encounter this exception. Added: https://issues.jboss.org/browse/SOA-3148 SOAPProxy threw a SAXParseException when the the WSDL was missing a soapAction and the message had attachment. A code fix has rectified this problem and, as a result, users will no longer encounter this exception. Verified in ER6 |