I'm not sure what you mean by RPC vs XML.
If you are building the service with Axis, then your interface will be implemented using SOAP, and descibed using WSDL. The WSDL should fully describe the structure of the input and output message using XML Schema.

In WSDL parlence, a service can be defined as document/literal, rpc/literal, or rpc/encoded. For best interoperability, you should use document/literal.

From a programming perspective, document/literal services can conform to two types of conventions: wrapped and unwrapped. Wrapped produces a programming interface that looks and feels a lot like RMI. It takes parameters in and returns a return value (simple type or bean). Unwrapped produces a similar programming interface, but it doesn't accept multiple parameters. It takes a bean in and return a return value.

You can also develop your service using a messaging style interface, in which Axis accepts a DOM Document or Element aray as input and returns a DOM Document or Element array.
See the Wiki for more info:
http://wiki.apache.org/ws/FrontPage/Axis/StyleInWSDDAndWSDL

On 2/24/06, Santunu Podder <[EMAIL PROTECTED] > wrote:
Hi all,

I am new to Web services and so would require some guidance to start with.

If I would like to deploy a webservice having clients in different
platforms (e.g. .NET, C# etc), should I go for RPC or XML ?

On what basis do I decide this?

And as a part of agrrement with all partners what should I provide them ?
Is it only the WSDL file generated by AXIS or are there something else
also?

Regards,
Santunu

This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.

  • XML or RPC? Santunu Podder
    • Re: XML or RPC? Anne Thomas Manes

Reply via email to