5:07 p.m.
[
https://jira.jboss.org/jira/browse/JBESB-3299?page=com.atlassian.jira.plu...
]
Uday updated JBESB-3299:
------------------------
Description:
When Proxing a webservice that has special characters in the URL SOAPProxy breaks.
Here is a xml fragment that breaks the SOAPProxy
<xsd:schema xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
targetNamespace="http://com.metamatrix/MMFinancials_VDB">
<xsd:import namespace="http://metamatrix.com/customerholdings/input"
schemaLocation="http://192.168.128.139:8080/metamatrix-soap/servlet/ArtifactDocumentService/MMFinancials/CustomerHoldings/CustomerHoldingsInput.xsd?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
/>
<xsd:import namespace="http://metamatrix.com/customerholdings/schema"
schemaLocation="http://192.168.128.139:8080/metamatrix-soap/servlet/ArtifactDocumentService/MMFinancials/CustomerHoldings/CustomerHoldingsSchema.xsd?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
/>
<xsd:import namespace="http://www.metamatrix.com/account_Input"
schemaLocation="http://192.168.128.139:8080/metamatrix-soap/servlet/ArtifactDocumentService/MMFinancials/AllCustomerAccounts/AllCustomerAccounts_Input.xsd?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
/>
<xsd:import namespace="http://www.metamatrix.com/account_Output"
schemaLocation="http://192.168.128.139:8080/metamatrix-soap/servlet/ArtifactDocumentService/MMFinancials/AllCustomerAccounts/AllCustomerAccounts_Output.xsd?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
/>
</xsd:schema>
As seen in the above URL's the "schemalocation" has
"?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
after the .xsd extension.
SOAPProxy tries to create a temp file of the form "protocol + - + suffix" and
since the suffix has special characters the temp file creation fails.
was:
When Proxing a webservice that has special characters in the URL SOAPProxy breaks.
SOAPProxy breaks when WSDL elements have special characters
-----------------------------------------------------------
Key: JBESB-3299
URL: https://jira.jboss.org/jira/browse/JBESB-3299
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.8
Reporter: Uday
Assignee: David Ward
Fix For: 4.9
Attachments: MyFinan.xml
When Proxing a webservice that has special characters in the URL SOAPProxy breaks.
Here is a xml fragment that breaks the SOAPProxy
<xsd:schema xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
targetNamespace="http://com.metamatrix/MMFinancials_VDB">
<xsd:import namespace="http://metamatrix.com/customerholdings/input"
schemaLocation="http://192.168.128.139:8080/metamatrix-soap/servlet/ArtifactDocumentService/MMFinancials/CustomerHoldings/CustomerHoldingsInput.xsd?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
/>
<xsd:import namespace="http://metamatrix.com/customerholdings/schema"
schemaLocation="http://192.168.128.139:8080/metamatrix-soap/servlet/ArtifactDocumentService/MMFinancials/CustomerHoldings/CustomerHoldingsSchema.xsd?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
/>
<xsd:import namespace="http://www.metamatrix.com/account_Input"
schemaLocation="http://192.168.128.139:8080/metamatrix-soap/servlet/ArtifactDocumentService/MMFinancials/AllCustomerAccounts/AllCustomerAccounts_Input.xsd?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
/>
<xsd:import namespace="http://www.metamatrix.com/account_Output"
schemaLocation="http://192.168.128.139:8080/metamatrix-soap/servlet/ArtifactDocumentService/MMFinancials/AllCustomerAccounts/AllCustomerAccounts_Output.xsd?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
/>
</xsd:schema>
As seen in the above URL's the "schemalocation" has
"?ServerURL=mm://localhost:31000&VDBName=MMFinancials_VDB&VDBVersion=1"
after the .xsd extension.
SOAPProxy tries to create a temp file of the form "protocol + - + suffix" and
since the suffix has special characters the temp file creation fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira