XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + rtf to XML (4)
-> + Questions Regarding Existing B... (3)
-> + Bug: Saved Changes Lost Switch... (3)
-> + Adding Simple Types to Attribu... (4)
-> + SQL Table to XML Convert error... (9)
-> + please help me with style shee... (2)
-> - WSDL Misbehaving (4)
-> ->WSDL Misbehaving
-> ->WSDL Misbehaving
-> ->WSDL Misbehaving
-> + Regarding XSLT logic for a sim... (2)
-> + Regarding XSLT logic for a sim... (2)
-> + Integration with VB.Net (5)
-> + License for end user (5)
-> + Error when running xalan sampl... (3)
-> + generate the date time in xslt... (2)
-> + Error When Using XMLConverters... (5)
-> + Viewing the toolbox pane (3)
-> + In Sync (2)
-> + Java EE 5 SDK vs. Java 2 SDK S... (2)
-> - Odd behavior of Begin Field in... (1)
-> + I/O-error while saving style s... (2)
-> + WEB Service Session (2)
-> - XML Report - Horizontal Line (1)
-- Previous [1381-1400] [1401-1420] [1421-1440] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Nick LockeSubject: WSDL Misbehaving
Author: Nick Locke
Date: 14 Nov 2007 08:00 AM
I have a WSDL structure which I have created using Stylus Studio. It has the "Service" in one WSDL file and the "Messages" in another. The "Messages" file references a number of XSDs.

I am trying to use the Web Service Call Composer and, although it "sees" the three Operations, I can't get any further.

I have run the WSDL through the validator at www.xmethods.com and that does not find any errors. I can also generate .NET code using Microsoft's WSDL.EXE (which is usually very fussy).

I have attached a screen-shot from Stylus Studio. It is worth mentioning that SOAP Sonar also shows similar behaviour - in that tool, I can see the XML Elements within the SOAP Header, but then just get a single tag called "Body" rather than the XML elements that I would expect.

The WSDL is temporarily available at http://nick.21jubileepark.com/Schemata/AutomaticFiling/Demo/AutofileServiceDemo-v1-00a.wsdl

All assistance welcome. Thanks, Nick.

Stylus Studio Screen Shot

Postnext
Ivan PedruzziSubject: WSDL Misbehaving
Author: Ivan Pedruzzi
Date: 14 Nov 2007 12:07 PM
Hi Nick,

This is caused by a restriction in the Stylus Studio WSDL processor that doesn't support wsdl:import.

We will be working on enhancing our WSDL processor in future versions but we do not have yet a firm plan for it.


Ivan Pedruzzi
Stylus Studio Team

Postnext
Nick LockeSubject: WSDL Misbehaving
Author: Nick Locke
Date: 14 Nov 2007 12:13 PM
> This is caused by a restriction
> in the Stylus Studio WSDL processor
> that doesn't support wsdl:import.

Ivan, thanks for the prompt and helpful response. Does this just mean that I cannot split the WSDL Service and the WSDL Messages into separate files, or does it go further and mean that I can't import the XSD files either?

I guess I could live with combining the Service and Message WSDL files, but I need to keep the XSDs separate.

Sorry if that's a crazy question!

Thanks, Nick

Posttop
Ivan PedruzziSubject: WSDL Misbehaving
Author: Ivan Pedruzzi
Date: 14 Nov 2007 12:17 PM

You may still use an external schema, you will need to define an empty schema embedded the WSDL then use xsd:import


Hope this helps
Ivan Pedruzzi
Stylus Studio Team

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! 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

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
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.