Return-Path: 
 <axis-user-return-56459-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 60956 invoked from network); 22 Feb 2007 11:44:18 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 22 Feb 2007 11:44:18 -0000
Received: (qmail 52888 invoked by uid 500); 22 Feb 2007 11:44:18 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 52873 invoked by uid 500); 22 Feb 2007 11:44:18 -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 52861 invoked by uid 99); 22 Feb 2007 11:44:18 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 03:44:18 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 03:44:05 -0800
Received: from [72.21.53.38] (helo=jubjub.nabble.com)
	by talk.nabble.com with esmtp (Exim 4.50)
	id 1HKCMT-000400-6w
	for axis-user@ws.apache.org; Thu, 22 Feb 2007 03:43:45 -0800
Message-ID: <9098426.post@talk.nabble.com>
Date: Thu, 22 Feb 2007 03:43:45 -0800 (PST)
From: tgb <TBuss@SERENA.com>
To: axis-user@ws.apache.org
Subject: Re: [Axis2] RPC WSDL/ Codegen?
In-Reply-To: <9094660.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: TBuss@SERENA.com
References: <8E5B605D380F004C8698887B10B8CF960CA175@ALPMLVEM08.e2k.ad.ge.com>
 <9092547.post@talk.nabble.com>
 <541aa82a0702211746s1ab990i6ac145e9a531b51e@mail.gmail.com>
 <9093041.post@talk.nabble.com> <9093543.post@talk.nabble.com>
 <60708f4b0702212045r95bbf96q405f3ab67e24236c@mail.gmail.com>
 <9094660.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org


There appears to be two problems.  The most obvious is that the RPC-literal
message sent by the generated client and accepted by the generated service
is incorrect - or so I believe.  The following message body  is sent for the
various test cases I have tried - string, complex type, nested complex type.

<soapenv:Body>
    <ns:OperationName>
        <ns:PartName>
.............content.....
        </ns:PartName>
    </ns:OperationName>
</soapenv:Body>

but it should be:

<soapenv:Body>
    <ns:OperationName>
        <PartName>
.............content.....
        </PartName>
    </ns:OperationName>
</soapenv:Body>

PartName should be a non qualified name.  Axis 1.3 did it this way, and
other sources support this as being the correct form for rpc-literal.

The second problem that I have yet to narrow down is that with a much more
complex type, the generated client sends a message with a body like this
where the "part" element is not present:

<soapenv:Body>
    <ns:OperationName>
 .............content.....
     </ns:OperationName>
</soapenv:Body>

One other differnce that may be a factor is that my complex service is one
way.

I have attached the WSDL I'm using for the test cases in case someone can
point out my obvious error.

Thanks,
Tim




tgb wrote:
> 
> Thanks, that makes sense. I understand the workaround for getting the
> service to show the correct WSDL.
> 
> However, there seems to be a problem with the client codegen for
> rpc/literal.  So far I have only managed to make it work correctly with
> parameter that has a simple type (I tried xs:string)  When I change the
> type of the parameter to complex type, the client no longer adds the
> "part" element to the SOAP message it sends.   Instead the "operation"
> element contains the complex data directly as if the SOAP message was a
> document literal style message.
> 
> I am using the axis2 eclipse codegen plugin 1.1.1 with the default option
> (ie adb generation).  I'll attach the WSDLs once I think I have a
> reproducible case
> 
> Tim
> 
> 
> Amila Suriarachchi wrote:
>> 
>> hi,
>> In codegeneration with wsdl, we convert the rpc style wsdl in to document
>> style (similar in messages) by generating the elements for rpc type
>> messages. And finally save the wsdl file to resource directory. When
>> saving
>> the wsdl file back it serializes the generated axis service object
>> structure
>> instead of saving the origianl wsdl as it is. That is the reason why you
>> get
>> a wsdl which is converted to document style. So can you please replace
>> your
>> saved wsdl in resource folder with the original wsdl and see.
>> On the other hand axis2 generates a wsdl only if the Message receiver is
>> one
>> of RPCMessageReceivers. but when generating the code from the wsdl it
>> creates a custom message receiver for the given wsdl file.
>> 
>> Amila.
>> -- 
>> Amila Suriarachchi,
>> WSO2 Inc.
>> 
>> 
> 
> 
http://www.nabble.com/file/6694/Axis2RPCLiteralTest.wsdl
Axis2RPCLiteralTest.wsdl 
-- 
View this message in context: http://www.nabble.com/RPC-WSDL---Codegen--tf2593238.html#a9098426
Sent from the Axis - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org