Return-Path: 
 <axis-user-return-34892-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 64191 invoked from network); 10 Jul 2005 16:44:01 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 10 Jul 2005 16:44:01 -0000
Received: (qmail 32288 invoked by uid 500); 10 Jul 2005 16:43:50 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 32277 invoked by uid 500); 10 Jul 2005 16:43:50 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-user@ws.apache.org>
List-Id: <axis-user.ws.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 32264 invoked by uid 99); 10 Jul 2005 16:43:49 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jul 2005 09:43:49 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [206.40.33.101] (HELO mailrelay.savvion.com) (206.40.33.101)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jul 2005 09:43:47 -0700
Received: from mail.savvion.com (mail.savvion.com [10.1.6.6])
	by mailrelay.savvion.com (Postfix) with ESMTP id AEFED7046F
	for <axis-user@ws.apache.org>; Sun, 10 Jul 2005 13:29:50 -0400 (EDT)
Received: from [127.0.0.1] (unknown [10.1.4.52])
	by mail.savvion.com (Postfix) with ESMTP id 6A8F12FC008
	for <axis-user@ws.apache.org>; Sun, 10 Jul 2005 12:15:39 -0400 (EDT)
Message-ID: <42D1508B.3030707@savvion.com>
Date: Sun, 10 Jul 2005 09:44:59 -0700
From: Ravi Krishnamurthy <ravik@savvion.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: axis-user@ws.apache.org
Subject: Re: document/literal webservice does not work good if the operation
 contains more than one parameter
References: <19D5C85D4C03114EB17EF52B34E719DC0322970F@ptp-mail.ptpusa.com>
	 <bf414ee605070907371d115b16@mail.gmail.com>	 <42D0025C.1040306@savvion.com>
 <bf414ee605071006177286fd38@mail.gmail.com>
In-Reply-To: <bf414ee605071006177286fd38@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Thanks Anne.

Regards,
Ravi

Anne Thomas Manes wrote:

>That's correct. That's the way SOAP is supposed to work. SOAP
>processes only the first child of the soap:Body. If you send multiple
>children, then either all children after the first child are ignored
>or they are treated as separate request invocations. (The spec isn't
>clear on this point, so results will vary based on the tool you're
>using.) The WS-I Basic Profile
>(http://www.ws-i.org/Profiles/BasicProfile-1.1.html) clarifies this
>ambiguity:
><ws-i-bp-excerpt>
>4.4.1 Bindings and Parts
>
>There are various interpretations about how many wsdl:part elements
>are permitted or required for document-literal and rpc-literal
>bindings and how they must be defined.
>
>R2201 A document-literal binding in a DESCRIPTION MUST, in each of its
>soapbind:body element(s), have at most one part listed in the parts
>attribute, if the parts attribute is specified.
>
>R2209 A wsdl:binding in a DESCRIPTION SHOULD bind every wsdl:part of a
>wsdl:message in the wsdl:portType to which it refers with a binding
>extension element.
>
>R2210 If a document-literal binding in a DESCRIPTION does not specify
>the parts attribute on a soapbind:body element, the corresponding
>abstract wsdl:message MUST define zero or one wsdl:parts.
></ws-i-bp-excerpt>
>
>If you want to send multiple parameters, you must used wrapped
>doc/literal (or RPC style).
>
>Anne
>
>On 7/9/05, Ravi Krishnamurthy <ravik@savvion.com> wrote:
>  
>
>>Hello:
>>Created a simple java class called DocLit1 with the following method:
>>
>>public String testString(String str1, String str2){
>>        System.out.println(" str 1 is " + str1);
>>        System.out.println(" str2 is " + str2);
>>        return str1 + str2;
>>    }
>>
>>Deployed it as document/literal (NOT WRAPPED )
>>
>>When the input values are {"str1", "str2") the response is str1null. On
>>further investigation found out that the second parameter is always null.
>>
>>I have attached the WSDL and my client code(DocLit1.java as dynamic
>>invocation) with this email. Would appreciate any pointers.
>>
>>Even generated the stubs using the WSDL2JAVA and tried it but got the
>>same result. The client for the stub is DocLiteralClient.java.
>>
>>Thanks,
>>Ravi
>>
>>
>>
>>
>> 
>>
>>
>>    
>>