Bug 779703 (SOA-2067)
Summary: | SOAPProxy breaks when WSDL elements have special characters | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Kevin Conner <kevin.conner> |
Component: | JBossESB | Assignee: | Kevin Conner <kevin.conner> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.0.0 GA | ||
Target Milestone: | --- | ||
Target Release: | 5.0.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/SOA-2067 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-28 15:02:49 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: | |
Embargoed: |
Description
Kevin Conner
2010-05-04 13:41:11 UTC
Link: Added: This issue depends JBESB-3300 JBESB-3300 has been closed. More information needed for release notes: What is the most appropriate name for the deployable unit here ? Deploying a ??? would fail if the schemalocation URL in the WSDL contained characters that would be invalid in a filename on the host. This occured because the URL was used in the name of a temp file. The fix is that the URL is no longer used as part of the filename added to the SOA 5.1 release notes as resolved: JBESB-3300 Deploying an ESB archive that used SOAProxy would fail if the schema location URL in the WSDL contained characters that would be invalid in a filename on the host. This occurred because the URL was used in the name of a temp file. The URL is no longer used as part of the filename and deployment is successful. Verified in SOA-P 5.0.2 CR3 (covered by WebServiceProxyTest). Link: Added: This issue is duplicated by SOA-2221 Link: Added: This issue is duplicated by SOA-2151 |