SSDN - WSDL import not working

XML Editor

Sign Up

Search

Options

Chat

Help

News

Log in

Not Logged in

Topic

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Tim Drury

Subject: WSDL import not working
Author: Tim Drury
Date: 27 Apr 2006 12:13 PM

Our WSDLs use the schema import function to keep our schemas modular -
we have around a hundred. Stylus Studio 501i can't seem to handle
the import. I've paired the WSDL down to a working and non-working
version (attached, around 70 lines each). Note that the "non-working"
WSDL works fine with several other tools I've tested with.

-tim

testcase_notworking.wsdl
non-working wsdl using import

testcase_common.xsd
imported xsd in non-working testcase

testcase_working.wsdl
working WSDL

(Deleted User)

Subject: WSDL import not working
Author: (Deleted User)
Date: 27 Apr 2006 03:15 PM

Hi Tim,

I am not sure I understand what you mean by "...can't seem to handle
...". What is the behavior that you see?

Could you elaborate on what exact feature/steps in Stylus Studio that you are trying with the documents you attached?

Thank you
- Srini

Tim Drury

Subject: WSDL import not working
Author: Tim Drury
Date: 27 Apr 2006 03:31 PM

If you create a new WS call and load the non-working WSDL, it builds
out the following soap input:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The other tools I ran would create this:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:mrns0="http://www.visiprise.com/schemas/4.2/common" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<mrns0:create>
<mrns0:item/>
</mrns0:create>
</soap:Body>
</soap:Envelope>

If, instead of using import, you pull the external schema into the
WSDL (as shown in the working WSDL), then Stylus Studio will render
the the input soap correctly:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<common:create xmlns:common="http://www.visiprise.com/schemas/4.2/common">
<common:item/>
</common:create>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Eliminating the import from our WSDL is not possible - we have dozens
of them (each importing others) and they are large.

-tim

Ivan Pedruzzi

Subject: WSDL import not working
Author: Ivan Pedruzzi
Date: 27 Apr 2006 04:00 PM

Hi Tim,

Thank You for the test case. We are investigating if we can fix it in next update or delay until 7.3.

Ivan Pedruzzi
Stylus Studio Team

Vito Iannuzzelli

Subject: WSDL import not working
Author: Vito Iannuzzelli
Date: 12 Jul 2006 07:12 AM

Ivan, has the issue of supporting wsdl:import been fixed yet ?

I appear to be having the same problem. My wsdl looks as follows

<wsdl:import location="ProcessOrderInterface.wsdl" namespace="http://HelloWorld/ProcessOrderInterface"/>

The information contained in the ProcessOrderInterface.wsdl file is not being pulled in

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!

Go to Conference:

Log In Options Username: Password:

Site Map | Privacy Policy | Terms of Use | Trademarks

Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.