Bug 779703 (SOA-2067) - SOAPProxy breaks when WSDL elements have special characters
Summary: SOAPProxy breaks when WSDL elements have special characters
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2067
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.0.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0.2
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
: 779790 779862 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-04 13:41 UTC by Kevin Conner
Modified: 2010-08-13 08:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 15:02:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2067 0 None None None Never

Description Kevin Conner 2010-05-04 13:41:11 UTC 
Date of First Response: 2010-05-04 10:28:23
project_key: SOA
Comment 1 Kevin Conner 2010-05-04 13:41:39 UTC 
Link: Added: This issue depends JBESB-3300
Comment 2 David Ward 2010-05-04 14:28:23 UTC 
JBESB-3300 has been closed.
Comment 3 Dana Mison 2010-06-08 01:05:12 UTC 
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
Comment 4 Dana Mison 2010-06-22 04:30:04 UTC 
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.
Comment 5 Boris Belovic 2010-06-28 15:02:49 UTC 
Verified in SOA-P 5.0.2 CR3 (covered by WebServiceProxyTest).
Comment 6 Kevin Conner 2010-08-13 08:34:10 UTC 
Link: Added: This issue is duplicated by SOA-2221
Comment 7 Kevin Conner 2010-08-13 08:36:54 UTC 
Link: Added: This issue is duplicated by SOA-2151
Note You need to log in before you can comment on or make changes to this bug.