Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 23897 invoked from network); 19 Jul 2004 18:50:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 19 Jul 2004 18:50:20 -0000 Received: (qmail 26866 invoked by uid 500); 19 Jul 2004 18:50:05 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 26836 invoked by uid 500); 19 Jul 2004 18:50:05 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 26826 invoked by uid 99); 19 Jul 2004 18:50:05 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=HTML_70_80,HTML_MESSAGE,MIME_HTML_NO_CHARSET X-Spam-Check-By: apache.org Received: from [208.139.169.228] (HELO asmcimc.suzukihq.asmc.us) (208.139.169.228) by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 19 Jul 2004 11:50:02 -0700 Received: by asmcimc.suzukihq.asmc.us with Internet Mail Service (5.5.2653.19) id <38XGC6AW>; Mon, 19 Jul 2004 11:50:40 -0700 Message-ID: <8765557836794E4EADF7F31290F4C39F06175484@asmcmail.suzukihq.asmc.us> From: Vikas Phonsa To: "'axis-user@ws.apache.org'" Subject: changing from RPC to Document based encoding Date: Mon, 19 Jul 2004 11:50:39 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C46DC1.49592070" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C46DC1.49592070 Content-Type: text/plain Hi Everybody, I'm in a spot here. I have implemented a web services program in java using Axis and used the java2wsdl to generate the wsdl and for the most part it works fine with the client I generated, again using Axis. The encoding style is RPC which was the default. But the people who are going to be users of this webservice, say that their client generator application (something in Siebel ), won't handle complex types and so their SOAP message is always different from the one generated my axis client and has wrong tags and hence is rejected. They say that instead of rpc encoding, use Document-Literal encoding. I have never worked with Doc-Literal So I would appreciate if some one can tell what it takes to make a rpc based web service to work with Document based protocol . Has anyone here done such a conversion here ? And any ideas about where to start ? Thanks Vikas ------_=_NextPart_001_01C46DC1.49592070 Content-Type: text/html

Hi Everybody,

I'm in a spot here. I have implemented a web services program in java using Axis and used the java2wsdl to generate the wsdl and for the most part it works fine with the client I generated, again using Axis. The encoding style is RPC which was the default.

But the people who are going to be users of this webservice, say that their client generator application (something in Siebel ), won't handle complex types and so their SOAP message is always different from the one generated my axis client and has wrong tags and hence is rejected.

They say that instead of rpc encoding, use Document-Literal encoding. I have never worked with Doc-Literal

So I would appreciate if some one can tell what it takes to make a rpc based web service to work with Document based protocol .

Has anyone here done such a conversion here ?

And any ideas about where to start ?

Thanks

Vikas

------_=_NextPart_001_01C46DC1.49592070--