Re: Does Doc/Literal allows users to directly work with language constructs (classes, structures etc..)?

[Anne Thomas Manes]

Just to be clear, when using Doc/Lit, the *SOAP engine* can process the XML payload using XML Schema -- meaning that it can validate it and transform it using standard utilities. An RPC/Encoded payload does not conform to a schema, therefore you can't validate it.   But there's no need for the "end user" or the application to work with XML unless it chooses to do so. Tools such as wsdl2java and the .NET wsdl.exe WSDL compiler automatically generate language constructs from the Doc/literal schema definition in the WSDL document, and the SOAP engines automatically transform the XML into the appropriate language constructs.   Such functionality is supported by many SOAP platforms, such as Axix, WASP, GLUE, Cape Clear, XMLBus, BEA WebLogic, .NET, MS SOAP, PocketSOAP, and lots others.   Anne ----- Original Message ----- From: Tony Opatha To: [EMAIL PROTECTED] Sent: Thursday, July 10, 2003 1:42 PM Subject: RE: Does Doc/Literal allows users to directly work with language constructs (classes, structures etc..)? Most importantly Doc/Lit allows end users to process payloads using the corresponding XML Schema for the payload that is packaged in the SOAP Body. This is quite important when the WSDL2Java compiler creates the stubs and skeletons it is basically creating serializable beans that produce XML payloads for the SOAP body such that the XML payload is always compliant with the XSD.     -----Original Message----- From: Hittesdorf,Michael [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 7:56 AM To: '[EMAIL PROTECTED]' Subject: RE: Does Doc/Literal allows users to directly work with language constructs (classes, structures etc..)?   Axis is JAX-RPC compliant which means that you can develop Doc/Literal Web Services where you need not ever deal directly with XML. Rather you can work directly with Java stubs and server-side skeletons. Axis will marshal and unmarshall your Doc/Literal SOAP message for you using Java classes generated from your WSDL by the WSDL2Java compiler. The same kind of support for Doc/Literal is provided by GLUE and others. Mick   -----Original Message----- From: Agarwal, Naresh [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 8:22 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Does Doc/Literal allows users to directly work with language constructs (classes, structures etc..)? Hi Srinivas, thanks for the reply. Doc/Literal support in Axis allows users to directly work with constructs (classes, structures etc..) available in languages. But in general can we do this in case of Doc/Literal? I believe that the fundamental difference between RPC/Encoded and Doc/Literal is that in case of RPC/Encoded, users can directly work with constructs (classes, structures etc..) available in languages. However, we cann't do this in Doc/Literal since, it is the service implementation, who pareses the SOAP message and interpret it. Does doc/literal support in other SOAP implementation also allows this? -----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 4:06 PM To: [EMAIL PROTECTED] Subject: Re: Does Doc/Literal allows users to directly work with language constructs (classes, structures etc..)?   Yes, Doc/Literal support in Axis can do the same. --- "Agarwal, Naresh" <[EMAIL PROTECTED]> wrote: > Hi > > RPC/Encoded allows users to directly work with constructs (classes, structures etc..) available > in languages. > Does Doc/Literal allows the same? > > AFAIK, it does not, as in case of Doc/Literal, it is responsibility of client and the service to > interpret the SOAP message. > > thanks > Naresh Agarwal >   Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!