[
Lists Home |
Date Index |
Thread Index
]
Just one slight correction (typed too fast):
CHANGE:
The other is "usage" (aka "usage" or "encoding")
TO:
The other is "usage" (aka "use" or "encoding")
Joseph Chiusano wrote:
>
> RPC vs. Document type (or "style") is actually only 1 of 2 factors that
> one needs to consider for this topic. The other is "usage" (aka "usage"
> or "encoding"), which can be "literal" or "encoded". The combination of
> style and usage therefore yields 4 possible combinations, only 2 of
> which are really considered in practice. Style can have the values
> "document" or "RPC." "Document" implies that the messages contain a
> document (such as a purchase order), while "RPC" implies that the
> messages contain parameters and return values (think of a
> request/response query-type operation).
>
> Usage can have the values "literal" or "encoded". "Literal" implies
> that the information in the messages is *literally* what the XML schema
> for the types in the messages dictates. "Encoded" implies that the
> information in the messages is further encoded by the SOAP encoding
> rules (which are found at http://www.w3.org/2002/06/soap-encoding for
> SOAP 1.2), or other encoding rules.
>
> So in using the document/literal combination, one literally defines the
> structure of the message using an XML schema; this means that a
> resulting SOAP message can be validated using the schema definition
> (obviously an advantage in data exchange scenarios). In using the
> rpc/encoded combination, SOAP encoding rules are used to construct the
> message based on abstract type descriptions - therefore, a type
> definition must be provided. However, an XML schema definition of the
> message is not provided, which means that the resulting SOAP message
> cannot be validated using an XML schema (it of course may be validated
> in a sending/receiving system through other means).
>
> The WS-I Basic Profile 1.0 [1] prefers the use of literal, non-encoded
> XML - it therefore disallows the use of SOAP encoding and favors
> document/literal style.
>
> Hope that helps--
>
> [1] http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html
>
> Kind Regards,
> Joe Chiusano
> Booz | Allen | Hamilton
> Strategy and Technology Consultants to the World
>
> dilum@opensource.lk wrote:
> >
> > Hi,
> > We are going to develope a tool to convert Web services in to WSDL.
> > For that I want to know the exact differences between RPC type and
> > Document type in a WSDL file(Specially in the complextype area in the
> > WSDL file). I read so many documents but I didn't find any exact
> > answer for that. most of the documents didn't talk about complextype
> > area. So, can anyone give me solution for this.
> > Please help. Thanks.
> >
> > -----------------------------------------------------------------
> > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> > initiative of OASIS <http://www.oasis-open.org>
> >
> > The list archives are at http://lists.xml.org/archives/xml-dev/
> >
> > To subscribe or unsubscribe from this list use the subscription
> > manager: <http://www.oasis-open.org/mlmanage/index.php>
>
> --
> Kind Regards,
> Joseph Chiusano
> Associate
> Booz | Allen | Hamilton
--
Kind Regards,
Joseph Chiusano
Associate
Booz | Allen | Hamilton
|
