axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand Hatwalne" <anand_hatwa...@persistent.co.in>
Subject RE: Wrapped document/literal support in Axis 1.0
Date Fri, 25 Oct 2002 04:56:39 GMT
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: axis-user@xml.apache.org
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.









_________________________________________________________________
Get a speedy connection with MSN Broadband.  Join now!
http://resourcecenter.msn.com/access/plans/freeactivation.asp


Mime
View raw message