Bug report has been filed: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13979
From: "Anand Hatwalne" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: RE: java:MSG vs. document binding style
Date: Mon, 28 Oct 2002 09:27:27 +0530
Welcome to the confusion club!
Also, notice that a document style WSDL will also have encoding
specified..is that a bug too?
I am posting a so-called document style WSDL generated (which .NET fails to
parse; complaining about the encoding present in the WSDL)
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions
targetNamespace="http://localhost:8080/axis/services/MessageService";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:apachesoap="http://xml.apache.org/xml-soap";
xmlns:impl="http://localhost:8080/axis/services/MessageService";
xmlns:intf="http://localhost:8080/axis/services/MessageService";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
- <wsdl:types>
- <schema
targetNamespace="http://localhost:8080/axis/services/MessageService";
xmlns="http://www.w3.org/2001/XMLSchema";>
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"; />
- <complexType name="ArrayOf_apachesoap_Element">
- <complexContent>
- <restriction base="soapenc:Array">
<attribute ref="soapenc:arrayType" wsdl:arrayType="apachesoap:Element[]"
/>
</restriction>
</complexContent>
</complexType>
<element name="ArrayOf_apachesoap_Element" nillable="true"
type="impl:ArrayOf_apachesoap_Element" />
</schema>
</wsdl:types>
- <wsdl:message name="echoElementsResponse">
<wsdl:part element="impl:ArrayOf_apachesoap_Element"
name="echoElementsReturn" />
</wsdl:message>
- <wsdl:message name="echoElementsRequest">
<wsdl:part element="impl:ArrayOf_apachesoap_Element" name="in0" />
</wsdl:message>
- <wsdl:portType name="MessageService">
- <wsdl:operation name="echoElements" parameterOrder="in0">
<wsdl:input message="impl:echoElementsRequest" name="echoElementsRequest"
/>
<wsdl:output message="impl:echoElementsResponse"
name="echoElementsResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="MessageServiceSoapBinding" type="impl:MessageService">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"; />
- <wsdl:operation name="echoElements">
<wsdlsoap:operation soapAction="" />
- <wsdl:input name="echoElementsRequest">
<wsdlsoap:body
namespace="http://localhost:8080/axis/services/MessageService"; use="literal"
/>
</wsdl:input>
- <wsdl:output name="echoElementsResponse">
<wsdlsoap:body
namespace="http://localhost:8080/axis/services/MessageService"; use="literal"
/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="MessageServiceService">
- <wsdl:port binding="impl:MessageServiceSoapBinding" name="MessageService">
<wsdlsoap:address
location="http://localhost:8080/axis/services/MessageService"; />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
-----Original Message-----
From: alanz [mailto:ajz96@;yahoo.com]
Sent: Sunday, October 27, 2002 11:07 PM
To: [EMAIL PROTECTED]
Subject: java:MSG vs. document binding style
In the user guide it seems indicates java:MSG mapping
to the document binding style defined in the WSDL.
I am looking at the sample MessgeService. In the WSDD
the style is java:MSG.
However after deployed to AXIS v1.0, the ?wsdl url
showed the binding style is rpc instead of document.
Also the WSDL tool always generates the WSDD with
provider="java:RPC" regardless the binding style in
WSDL
Is this a bug?
Thanks
__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/
_________________________________________________________________
Internet access plans that fit your lifestyle -- join MSN. http://resourcecenter.msn.com/access/plans/default.asp
