Re: Axis 1.2 with doc/lit implementation
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: > > > > > > 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/";> > > > > > targetNamespace="http://tempuri.org/";> > > > > > > > > > type="s:string" /> > > > > > > > > > > > > > > > name="echoStringResult" type="s:string" /> > > > > > > > > > > > > > > > type="s:string" /> > > > type="s:string" /> > > > > > > > > > > > > > > > name="echoString_doubleResult" type="s:string" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://schemas.xmlsoap.org/soap/http"; > > style="document" /> > > > > http://tempuri.org/echoString"; > > style="document" /> > > > > > > > > > > > > > > > > > > http://tempuri.org/echoString_double"; > > style="document" /> > > > > > > > > > > > > > > > > > > > > > > http://localhost/ws_axis/Echo/Echo.asmx"; > > /> > > > > > > > > > > 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
Re: Axis 1.2 with doc/lit implementation
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: > > > 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/";> > > targetNamespace="http://tempuri.org/";> > > > > type="s:string" /> > > > > > > > name="echoStringResult" type="s:string" /> > > > > > > > type="s:string" /> > type="s:string" /> > > > > > > > name="echoString_doubleResult" type="s:string" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://schemas.xmlsoap.org/soap/http"; > style="document" /> > > http://tempuri.org/echoString"; > style="document" /> > > > > > > > > > http://tempuri.org/echoString_double"; > style="document" /> > > > > > > > > > > > http://localhost/ws_axis/Echo/Echo.asmx"; > /> > > > > > 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. >
Re: Axis 1.2 with doc/lit implementation
Here is the wsdl file generated by .NET with the same interface: 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/";> http://tempuri.org/";> http://schemas.xmlsoap.org/soap/http"; style="document" /> http://tempuri.org/echoString"; style="document" /> http://tempuri.org/echoString_double"; style="document" /> http://localhost/ws_axis/Echo/Echo.asmx"; /> 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.
RE: Axis 1.2 with doc/lit implementation
It is not a good idea to manually change the wsdl file in that way. I think Axis develop team should fix this bug ASAP. -Henry >>> [EMAIL PROTECTED] 5/24/2005 9:59:21 AM >>> Hi Henry I don't think the java2WSDL properly generates document/literal WSDL in Axis 1.1, but I haven't tried this in 1.2. I have always needed to edit the WSDL output, change the style/encoding and use a single complex type as the request argument to the methods called - there needs to be a single root element in the SOAP body to adhere to WS-I BP1.0. Regards Tim -Original Message- From: Henry Lu [mailto:[EMAIL PROTECTED] Sent: 24 May 2005 14:46 To: [EMAIL PROTECTED]; axis-user@ws.apache.org Subject: Re: Axis 1.2 with doc/lit implementation 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. DISCLAIMER The information contained in this e-mail is confidential and is intended for the recipient only. If you have received it in error, please notify us immediately by reply e-mail and then delete it from your system. Please do not copy it or use it for any other purposes, or disclose the content of the e-mail to any other person or store or copy the information in any medium. The views contained in this e-mail are those of the author and not necessarily those of Admenta UK Group. ** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues.
RE: Axis 1.2 with doc/lit implementation
Title: RE: Axis 1.2 with doc/lit implementation Hi Henry I don't think the java2WSDL properly generates document/literal WSDL in Axis 1.1, but I haven't tried this in 1.2. I have always needed to edit the WSDL output, change the style/encoding and use a single complex type as the request argument to the methods called - there needs to be a single root element in the SOAP body to adhere to WS-I BP1.0. Regards Tim -Original Message- From: Henry Lu [mailto:[EMAIL PROTECTED]] Sent: 24 May 2005 14:46 To: [EMAIL PROTECTED]; axis-user@ws.apache.org Subject: Re: Axis 1.2 with doc/lit implementation 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. DISCLAIMER The information contained in this e-mail is confidential and is intended for the recipient only. If you have received it in error, please notify us immediately by reply e-mail and then delete it from your system. Please do not copy it or use it for any other purposes, or disclose the content of the e-mail to any other person or store or copy the information in any medium. The views contained in this e-mail are those of the author and not necessarily those of Admenta UK Group.
Re: Axis 1.2 with doc/lit implementation
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
Re: Axis 1.2 with doc/lit implementation
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.
Re: Axis 1.2 with doc/lit implementation
Hi Henry!
I remember once there was a long discussion (around 3months back)
about this thing (Thanks to Anne's several informative inputs). In a
nutshell the conclusion as I remember it is that... if you want to
publish your service as doc/lit you shouldn't have method signatures
that accept more than one parameter.
Regards,
Jayachandra
On 5/24/05, Henry Lu <[EMAIL PROTECTED]> wrote:
> Is there any one can implement the following interface with
> server/client examples with style/use of DOC/Lit in AXIS 1.2?
>
>
> public interface Echo
> {
>public String echoString(String arg);
>public String echoString_double(String arg1, String arg2);
> }
>
> I got the following result:
>
> echoString(String arg);: Henry
> public String echoString_double(String arg1, String arg2);: Henrynull
>
> -Henry
>
>
> **
> Electronic Mail is not secure, may not be read every day, and should not be
> used for urgent or sensitive issues.
>
--
-- Jaya
