Hi Anne! Yeah! wrap/lit can be a solution, but... What do you think about Axis's doc/lit wsdl generation. Is it doing it right? For what use case does Axis generate the doc/lit wsdl in such a fashion that it is generating currently? Do you see some scope to better it? If yes, what kind of betterment?
Thank you Jayachandra On 5/25/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > If you want to interoperate with.NET, then you want to use the wrapped > convention (Axis WSDD style="wrapped"). It generates document/literal, > and automatically creates the wrapper element that wraps your multiple > input parameters. > > Anne > > > On 5/24/05, Henry Lu <[EMAIL PROTECTED]> wrote: > > Here is the wsdl file generated by .NET with the same interface: > > > > <?xml version="1.0" encoding="utf-8"?> > > <definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > xmlns:s="http://www.w3.org/2001/XMLSchema"; > > xmlns:s0="http://tempuri.org/"; > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > > xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"; > > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; > > targetNamespace="http://tempuri.org/"; > > xmlns="http://schemas.xmlsoap.org/wsdl/";> > > <types> > > <s:schema elementFormDefault="qualified" > > targetNamespace="http://tempuri.org/";> > > <s:element name="echoString"> > > <s:complexType> > > <s:sequence> > > <s:element minOccurs="0" maxOccurs="1" name="in0" > > type="s:string" /> > > </s:sequence> > > </s:complexType> > > </s:element> > > <s:element name="echoStringResponse"> > > <s:complexType> > > <s:sequence> > > <s:element minOccurs="0" maxOccurs="1" > > name="echoStringResult" type="s:string" /> > > </s:sequence> > > </s:complexType> > > </s:element> > > <s:element name="echoString_double"> > > <s:complexType> > > <s:sequence> > > <s:element minOccurs="0" maxOccurs="1" name="in0" > > type="s:string" /> > > <s:element minOccurs="0" maxOccurs="1" name="in1" > > type="s:string" /> > > </s:sequence> > > </s:complexType> > > </s:element> > > <s:element name="echoString_doubleResponse"> > > <s:complexType> > > <s:sequence> > > <s:element minOccurs="0" maxOccurs="1" > > name="echoString_doubleResult" type="s:string" /> > > </s:sequence> > > </s:complexType> > > </s:element> > > </s:schema> > > </types> > > <message name="echoStringSoapIn"> > > <part name="parameters" element="s0:echoString" /> > > </message> > > <message name="echoStringSoapOut"> > > <part name="parameters" element="s0:echoStringResponse" /> > > </message> > > <message name="echoString_doubleSoapIn"> > > <part name="parameters" element="s0:echoString_double" /> > > </message> > > <message name="echoString_doubleSoapOut"> > > <part name="parameters" element="s0:echoString_doubleResponse" /> > > </message> > > <portType name="EchoSoap"> > > <operation name="echoString"> > > <input message="s0:echoStringSoapIn" /> > > <output message="s0:echoStringSoapOut" /> > > </operation> > > <operation name="echoString_double"> > > <input message="s0:echoString_doubleSoapIn" /> > > <output message="s0:echoString_doubleSoapOut" /> > > </operation> > > </portType> > > <binding name="EchoSoap" type="s0:EchoSoap"> > > <soap:binding transport="http://schemas.xmlsoap.org/soap/http"; > > style="document" /> > > <operation name="echoString"> > > <soap:operation soapAction="http://tempuri.org/echoString"; > > style="document" /> > > <input> > > <soap:body use="literal" /> > > </input> > > <output> > > <soap:body use="literal" /> > > </output> > > </operation> > > <operation name="echoString_double"> > > <soap:operation soapAction="http://tempuri.org/echoString_double"; > > style="document" /> > > <input> > > <soap:body use="literal" /> > > </input> > > <output> > > <soap:body use="literal" /> > > </output> > > </operation> > > </binding> > > <service name="Echo"> > > <port name="EchoSoap" binding="s0:EchoSoap"> > > <soap:address location="http://localhost/ws_axis/Echo/Echo.asmx"; > > /> > > </port> > > </service> > > </definitions> > > > > I don't know how to find my case in the Jira. WHere is the web site? > > > > -Henry > > > > >>> [EMAIL PROTECTED] 5/24/2005 9:56:25 AM >>> > > Hi Henry! > > Can you point to the jira issue number, if you logged one. I'll see if > > I can help the Axis team with my effort. It will expedite the whole > > process if you can attach the .NET generated wsdl for the said > > interface in your reply (if it's already attached at the jira site > > then no need). > > > > Thanks > > Jayachandra > > > > On 5/24/05, Henry Lu <[EMAIL PROTECTED]> wrote: > > > You are right. But if you look at the wsdl file generated by the > > > java2wsdl of Axis1.2, it still comes out with multiple parts. If you > > > look at a wsdl file generated by .NET from the same interface, it > > > implements correctly. I'd raised this issue for years and put it in > > > the request a couple of times and it seems to me it has never been > > fixed > > > based upon the W3C standard. > > > > > > -Henry > > > > > > > > > > > > ********************************************************** > > > Electronic Mail is not secure, may not be read every day, and should > > not be used for urgent or sensitive issues. > > > > > > > > > -- > > -- Jaya > > > > > > ********************************************************** > > Electronic Mail is not secure, may not be read every day, and should not be > > used for urgent or sensitive issues. > > > -- -- Jaya
