You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Shalab Goel <sh...@oracle.com> on 2007/08/10 00:07:11 UTC
Is this regression for MTOM functionality in Axis2 1.3
Hello,
I have a .NET service for which I am writing an Axis2 client. One of the operations streams MTOM content to the client.
This works with Axis2 -1.2 but does not work with RC candidate build location for Axis 2-1.3 referenced in Deepal's message from two days ago?
Wondering if this is a regression, and is it a known issue? Appreciate your response.
Thanks
Shalab Goel
Re: Soap Stub generation using ADB in Axis2-1.3
Posted by keith chapman <ke...@gmail.com>.
You can use the -pn option to specify the portName that the code should be
generated for. Or you can use the -ap option which will genarate code for
all ports.
Thanks,
Keith.
On 8/10/07, Shalab Goel <sh...@oracle.com> wrote:
>
>
> In Axis2, the Soap stubs for SOAP 1.1 and Soap 1.2 were automatically
> generated. In Axis 1.3, only soap 1.2 Stubs are generated by default.
> Is there an argument that can be fed to wsdl2java to say I want Soap 1.1compatible stubs?
>
> The following is my command line for generating stub class using ADB.
>
> %AXIS2_HOME%\bin\wsdl2java -uri MyWS.wsdl -d adb -p com.myws.client
>
> Is MTOM functionality for Axis2 1.3 tested with both Soap 1.1 and Soap 1.2generated stubs?
>
> The .NET service, against which I am writing an Axis client, generates a
> Soap 1.1 response. And it clashes if I try to use Soap1.2 Stub. Is there
> an Axis client configuration setting (like CUSTOM_SESSION_ID setting for
> sessions) to overcome this issue?
>
> Thanks
> Shalab
>
>
> -----Original Message-----
> From: Davanum Srinivas [mailto:davanum@gmail.com]
> Sent: Thursday, August 09, 2007 6:11 PM
> To: axis-user@ws.apache.org; shalab.goel@oracle.com
> Subject: Re: Is this regression for MTOM functionality in Axis2 1.3
>
> Shalab,
>
> Not a known issue, please log a bug with some way for us to recreate the
> issue.
>
> thanks,
> dims
>
> On 8/9/07, Shalab Goel <sh...@oracle.com> wrote:
> >
> >
> >
> >
> > Hello,
> >
> >
> >
> > I have a .NET service for which I am writing an Axis2 client. One of the
> > operations streams MTOM content to the client.
> >
> > This works with Axis2 -1.2 but does not work with RC candidate build
> > location for Axis 2-1.3 referenced in Deepal's message from two days
> ago?
> >
> >
> >
> > Wondering if this is a regression, and is it a known issue? Appreciate
> your
> > response.
> >
> >
> >
> > Thanks
> >
> > Shalab Goel
> >
> >
> >
> >
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/
Soap Stub generation using ADB in Axis2-1.3
Posted by Shalab Goel <sh...@oracle.com>.
In Axis2, the Soap stubs for SOAP 1.1 and Soap 1.2 were automatically generated. In Axis 1.3, only soap 1.2 Stubs are generated by default.
Is there an argument that can be fed to wsdl2java to say I want Soap 1.1 compatible stubs?
The following is my command line for generating stub class using ADB.
%AXIS2_HOME%\bin\wsdl2java -uri MyWS.wsdl -d adb -p com.myws.client
Is MTOM functionality for Axis2 1.3 tested with both Soap 1.1 and Soap 1.2 generated stubs?
The .NET service, against which I am writing an Axis client, generates a Soap 1.1 response. And it clashes if I try to use Soap1.2 Stub. Is there an Axis client configuration setting (like CUSTOM_SESSION_ID setting for sessions) to overcome this issue?
Thanks
Shalab
-----Original Message-----
From: Davanum Srinivas [mailto:davanum@gmail.com]
Sent: Thursday, August 09, 2007 6:11 PM
To: axis-user@ws.apache.org; shalab.goel@oracle.com
Subject: Re: Is this regression for MTOM functionality in Axis2 1.3
Shalab,
Not a known issue, please log a bug with some way for us to recreate the issue.
thanks,
dims
On 8/9/07, Shalab Goel <sh...@oracle.com> wrote:
>
>
>
>
> Hello,
>
>
>
> I have a .NET service for which I am writing an Axis2 client. One of the
> operations streams MTOM content to the client.
>
> This works with Axis2 -1.2 but does not work with RC candidate build
> location for Axis 2-1.3 referenced in Deepal's message from two days ago?
>
>
>
> Wondering if this is a regression, and is it a known issue? Appreciate your
> response.
>
>
>
> Thanks
>
> Shalab Goel
>
>
>
>
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Is this regression for MTOM functionality in Axis2 1.3
Posted by Davanum Srinivas <da...@gmail.com>.
there is an option in wsdl2java to generate all stubs..
-ap Generate code for all ports
On 8/10/07, Shalab Goel <sh...@oracle.com> wrote:
>
> Thanks Dims for your response.
>
> I tried take3 today. I am still seeing the same problem.
> MTOM streaming works if using same client code and .NET webservice with Axis2 1.2, but does not work with Axis2-1.3.
>
> I am using ADB generated stubs in both cases.
>
> Noticed that in Axis1.3 only Soap12 stubs are generated. Is there an argument to wsdl2java to generate Soap11 compliant ADB stubs?
>
> Will appreciate a response.
>
> Thanks
> Shalab Goel
>
> -----Original Message-----
> From: Davanum Srinivas [mailto:davanum@gmail.com]
> Sent: Thursday, August 09, 2007 6:11 PM
> To: axis-user@ws.apache.org; shalab.goel@oracle.com
> Subject: Re: Is this regression for MTOM functionality in Axis2 1.3
>
> Shalab,
>
> Not a known issue, please log a bug with some way for us to recreate the issue.
>
> thanks,
> dims
>
> On 8/9/07, Shalab Goel <sh...@oracle.com> wrote:
> >
> >
> >
> >
> > Hello,
> >
> >
> >
> > I have a .NET service for which I am writing an Axis2 client. One of the
> > operations streams MTOM content to the client.
> >
> > This works with Axis2 -1.2 but does not work with RC candidate build
> > location for Axis 2-1.3 referenced in Deepal's message from two days ago?
> >
> >
> >
> > Wondering if this is a regression, and is it a known issue? Appreciate your
> > response.
> >
> >
> >
> > Thanks
> >
> > Shalab Goel
> >
> >
> >
> >
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Is this regression for MTOM functionality in Axis2 1.3
Posted by Shalab Goel <sh...@oracle.com>.
Thanks Dims for your response.
I tried take3 today. I am still seeing the same problem.
MTOM streaming works if using same client code and .NET webservice with Axis2 1.2, but does not work with Axis2-1.3.
I am using ADB generated stubs in both cases.
Noticed that in Axis1.3 only Soap12 stubs are generated. Is there an argument to wsdl2java to generate Soap11 compliant ADB stubs?
Will appreciate a response.
Thanks
Shalab Goel
-----Original Message-----
From: Davanum Srinivas [mailto:davanum@gmail.com]
Sent: Thursday, August 09, 2007 6:11 PM
To: axis-user@ws.apache.org; shalab.goel@oracle.com
Subject: Re: Is this regression for MTOM functionality in Axis2 1.3
Shalab,
Not a known issue, please log a bug with some way for us to recreate the issue.
thanks,
dims
On 8/9/07, Shalab Goel <sh...@oracle.com> wrote:
>
>
>
>
> Hello,
>
>
>
> I have a .NET service for which I am writing an Axis2 client. One of the
> operations streams MTOM content to the client.
>
> This works with Axis2 -1.2 but does not work with RC candidate build
> location for Axis 2-1.3 referenced in Deepal's message from two days ago?
>
>
>
> Wondering if this is a regression, and is it a known issue? Appreciate your
> response.
>
>
>
> Thanks
>
> Shalab Goel
>
>
>
>
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Is this regression for MTOM functionality in Axis2 1.3
Posted by Davanum Srinivas <da...@gmail.com>.
Shalab,
Not a known issue, please log a bug with some way for us to recreate the issue.
thanks,
dims
On 8/9/07, Shalab Goel <sh...@oracle.com> wrote:
>
>
>
>
> Hello,
>
>
>
> I have a .NET service for which I am writing an Axis2 client. One of the
> operations streams MTOM content to the client.
>
> This works with Axis2 -1.2 but does not work with RC candidate build
> location for Axis 2-1.3 referenced in Deepal's message from two days ago?
>
>
>
> Wondering if this is a regression, and is it a known issue? Appreciate your
> response.
>
>
>
> Thanks
>
> Shalab Goel
>
>
>
>
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org