Both problems reproducible with nightly build of 10-19-2002. Filed bugzilla bugs 13979 and 13980.
Thanks.
From: Tom Jordahl <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: Wrapped document/literal support in Axis 1.0
Date: Fri, 25 Oct 2002 11:27:28 -0400
The WSDL generation in for literal "use" should never generate a SOAP encoding for any data type. This sounds like a bug in the WSDL generation, and I would file a small test case in a bugzilla bug demonstrating the problem. Please try the test case on a recent nightly build or the CVS source tree first. There have been improvements in this area post-1.0.
As far as WSDL2Java is concerned, it should generally correctly "unwrap" .NET WSDL providing the following conditions are true:
0. You aren't using the --noWrapped switch
1. The is a single part in the Input message
2. That part is defined with an element= attribute
3. The operation name is the same as the element name specified in the input part
.NET generates this type of WSDL by default.
If WSDL2Java is not correctly doing this, please file a sample WSDL file to reproduces the problem in a bug report.
Thanks!
--
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: Cun Yong Tan [mailto:cyongtan@;hotmail.com]
Sent: Friday, October 25, 2002 10:32 AM
To: [EMAIL PROTECTED]
Subject: RE: Wrapped document/literal support in Axis 1.0
Curious to see what would happen if the roles were reversed,
I created a .NET service (defaults to wrapped doc/lit) with
a method that accepts a single parameter of string[]. Then
used WSDL2Java to create Axis client.
The method signature that WSDL2Java produced for the method
is a bean that has a single property of a String[] instead of
a String[] by itself.
It does work but the wrapper bean makes programming rather
inconvenient.
>From: "Anand Hatwalne" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: RE: Wrapped document/literal support in Axis 1.0 Date: Fri, 25 Oct
>2002 10:26:39 +0530
>
>This exactly is the problem I am facing. .NET fails to parse such
>WSDL.(complaining that the WSDL should have not have specified the
>encoding).
>Why would a document based service in Axis still use encoding?
>Anyone knows the solution?
>
>-----Original Message-----
>From: Cun Yong Tan [mailto:cyongtan@;hotmail.com]
>Sent: Friday, October 25, 2002 2:36 AM
>To: [EMAIL PROTECTED]
>Subject: Wrapped document/literal support in Axis 1.0
>
>
>
>According to the Axis 1.0 user guide, it is possible to create
>a wrapped document/literal service. It says that Axis will bind
>the Java representation to the XML.
>
>Is my assumption correct that the service class will look exactly
>the same as it would be if it were rpc/encoded ?
>
>I tried to create a wrapped doc/lit service with WSDD line:
>
><service name="Test" provider="java:RPC" style="wrapped"> ...
>
>The doc didn't specify which provider to use so I assumed it was RPC.
>The service has a method that accepts a String array. The WSDL
>produced by the service seems to be wrong because it generated this
>type for the String array:
>
><complexType name="ArrayOf_xsd_string">
> <complexContent>
> <restriction base="soapenc:Array">
> <attribute ref="soapenc:arrayType" wsdl:arrayType="xsd:string[]"/>
> </restriction>
> </complexContent>
></complexType>
>
>The problem is that it still uses SOAP encoding to define an array.
>So .NET's wsdl.exe complains about it.
>
>Is wrapped doc/lit fully supported in Axis 1.0 ?
>Or am I not configuring something right in the WSDD or whatever ?
>
>Thanks.
>
>
_________________________________________________________________
_________________________________________________________________
Internet access plans that fit your lifestyle -- join MSN. http://resourcecenter.msn.com/access/plans/default.asp
