Angel, "always using / converting to SOAP 1.1 no matter which soap version is chosen by the client" <== is a Very serious bug!!!
please log a JIRA and any help to recreate the issue would be wonderful. thanks, dims On 6/19/07, Angel Todorov <[EMAIL PROTECTED]> wrote:
Defaulting to SOAP 1.2 will have more negative effects than positive, in my opinion -:) have in mind that SOAP 1.2 interop with other WS frameworks is very volatile at the moment (i.e. DotNET, and JAX-WS, more specifically - the wsimport tool) - that's what our experiences with soap 1.2 interop testing have shown. In addition to that some Axis2 modules such as Rampart are always using / converting to SOAP 1.1 no matter which soap version is chosen by the client. Thanks. Regards, Angel On 6/19/07, Tom Jordahl <[EMAIL PROTECTED]> wrote: > Really? You want to default to SOAP 1.2? Really? > > Did you actually flip this switch? I thought you were going to work on > stabilizing Axis2 for the 1.3 release. This is going to rock the boat > in a serious way. > > Tom Jordahl > > -----Original Message----- > From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] > Sent: Friday, June 08, 2007 12:36 PM > To: axis-dev@ws.apache.org > Subject: Re: [axis2] SOAP 1.1 default? > > Definitely +1! Can't remember why we default to 1.1 .. > > Sanjiva. > > Glen Daniels wrote: > > Forgive me if this has been covered recently, but why are we > defaulting > > to SOAP 1.1 everywhere? Shouldn't our default be SOAP 1.2? > > > > --Glen > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- Davanum Srinivas :: http://davanum.wordpress.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
