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:[EMAIL PROTECTED] Sent: Thursday, August 09, 2007 6:11 PM To: [email protected]; [EMAIL PROTECTED] 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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
