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
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
taylor coreySubject: Doc/Literal Wrapped
Author: taylor corey
Date: 06 Apr 2009 11:58 PM
Hello,

I had asked a while back if a web service was doc literal wrapped, and the reply was yes because:

'. . . the content for the getCountries message is an element having the same name of the message.'.

. . . that question was asked here:

http://www.stylusstudio.com/SSDN/default.asp?action=9&read=7306&fid=23

. . . but here is an IBM web page that shows an example (scroll down a little) of doc literal wrapped but it makes no sense to me as to why it is wrapped:

http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/

. . . they say it is wrapped because:

'. . . name of the input element is the same as the name of the operation . . .'

. . . so, my questions are:

1. Is the above IBM web page example also doc/literal wrapped?

2. If so, and for any WSDL, what specifically do I look at in Stylus Studio to know for sure if something is wrapped or not?

In other words, if I am looking at a diagram of some WSDL, what elements and/or names do I match up to know 100% it is wrapped and can I always do it at the WSDL level or do I need to sometimes look at the schema diagrams?

3. Is doc/literal wrapped officially defined by the w3 (I could not find it) or are folks using a loose definition of it?

Thanks.

--tc

Postnext
Ivan PedruzziSubject: Doc/Literal Wrapped
Author: Ivan Pedruzzi
Date: 07 Apr 2009 01:49 AM
Hi Taylor,

Document/Literal/Wrapped is a convention invented by Microsoft, it is based on document/literal and adds some additional restrictions:

- The input messages always references a single global element named with the operation's name. The global elements embeds a complex type which inside defines the operation's parameters.

- The Output messages always references a single global element named with the operation name plus the suffix "Response".

The Stylus Studio WSDL editor should help you to determine if the above rules are used.


Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Postnext
taylor coreySubject: Doc/Literal Wrapped
Author: taylor corey
Date: 07 Apr 2009 03:50 AM
Hi Ivan,

Thanks for the reply, that helps a lot. The diagrams are nice and I have no problems visually seeing what I read in a book about the different WSDL styles but doc/literal wrapped is really frustrating because I did not know what to look for in the diagram.

I searched the MS website and could not find anything that describes the wrapped style, is there such a page from MS?

Also, is the wrapped style a sort of 'loose' spec? In other words, if I look at a diagram of some WSDL and see all the elements you describe, but the output message references a global element that does not use a 'response' suffix, is it still a wrapped style?

Thanks.

--tc

Posttop
Ivan PedruzziSubject: Doc/Literal Wrapped
Author: Ivan Pedruzzi
Date: 07 Apr 2009 10:30 AM

I am having hard time to find a formal specification on MSDN.

You can find references scattered around various documentation like
http://msdn.microsoft.com/en-us/library/4cxy91t2(vs.80).aspx
http://msdn.microsoft.com/en-us/library/2b4bx2t6(VS.80).aspx

The use of "Response" suffix seems not be mandatory.


Ivan Pedruzzi
Stylus Studio Team

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
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.