Also, JAX-WS requires a SOAP 1.1 default so there will be additional work
there that will need to be addressed.
I'm for keeping the SOAP 1.1 default for now. There still isn't a WS-I
profile that includes SOAP 1.2 either, is there? I thought that was coming
in BP 2.0.
Regards,
-Nick
"Angel Todorov"
<[EMAIL PROTECTED]
com> To
[email protected]
06/19/2007 12:50 cc
PM
Subject
Re: [axis2] SOAP 1.1 default?
Please respond to
[EMAIL PROTECTED]
e.org
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: [EMAIL PROTECTED]
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]
<<inline: graycol.gif>>
<<inline: pic21325.gif>>
<<inline: ecblank.gif>>
