Ant,
I agree that the default for our Web Services binding should be SOAP 1.1.
Here's some background on why we have SOAP 1.2 now:
- Independent of any SCA Web Service binding, interactions flowing
through the Tuscany runtime are carried in a Tuscany Message.
- Other runtimes have defined their own "normalized" message format, in
Tuscany we have chosen to use a SOAP envelope/header+body instead of
re-inventing our own message format.
- We chose SOAP 1.2 over SOAP 1.1 for our Tuscany message because SOAP
1.2 provided more built-in function, for example SOAP role and relay
attributes, which perhaps we'll want to leverage at some point to govern
the flow of interactions inside the runtime.
- We are also using WS-addressing endpoint references in the runtime
(and I believe that this is an important design point and that
WS-addressing will be key to how we will handle and flow interactions)
and WS-addressing integrates with SOAP 1.2 better than with SOAP 1.1
(afaik SOAP 1.1 only defines addressing extensions for backwards
compatibility).
- Our Web Service binding code currently uses the fact that the Tuscany
message is a SOAP message to produce SOAP messages itself and uses Axis
basically as a "transport" mechanism. That's why it sends SOAP 1.2
messages at the moment.
As already discussed on this thread, we want to change how the Web
Service binding works. I don't think that it should continue to handle
the production of SOAP messages itself and we should let Axis 2 do it.
We need to make this change as part of the port to Axis2. Then we'll be
able to decouple the form/version of the SOAP messages flowing in/out of
a Web Service binding and the form/version of the Tuscany message
flowing inside the runtime.
Does that help?
--
Jean-Sebastien
ant elder wrote:
Hi Raymond, thanks, but that doesn't seem to make any difference, even after
that change i still get the 1.2 namespace. Any other suggestions?
I was wondering how it was decided that the default would be SOAP 1.2? WS-I
basic profile says only SOAP 1.1, so wouldn't having that as the default be
better?
...ant
On 1/11/06, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
I think there's a hack to force SOAP 1.1.
You can change the constant of
"org.apache.tuscany.core.message.sdo.MessageElementPackage.eNS_URI" to be
"http://schemas.xmlsoap.org/soap/envelope/";.
Here are the namespaces for SOAP:
SOAP 1.1: http://schemas.xmlsoap.org/soap/envelope/
SOAP 1.2: http://www.w3.org/2003/05/soap-envelope
Thanks,
Raymond
----- Original Message -----
From: "ant elder" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, January 11, 2006 4:14 AM
Subject: Re: Does Tuscany support SOAP 1.1?
Thanks for the reply Raymond.
It would be good to also support SOAP 1.1 sooner rather than later.
There's
a lot of SOAP stacks that don't support 1.2 by default yet, and it will be
frustrating for people trying out Tuscany if the first thing they try
other
than the provided samples is using an existing service and that ends in
failure due to this restriction.
Assuming that does happen eventually, any pointers to a hack I can make
for
now to use the 1.1 namespace by default? Changing the constant in the
constructor of o.a.t.binding.axis.mediator.impl.SOAPEnvelopeImpl seems to
be
ignored and deep within ecore XMLHelperImpl is getting the SOAP namespace
from the registry in o.e.e.e.util.BasicExtendedMetaData but I can't see
how
thats getting populated.
Thanks,
...ant
On 1/11/06, Raymond Feng <[EMAIL PROTECTED]> wrote:
The current Tuscany WS support uses an XML info model for SOAP 1.2Schema
to
create SOAP 1.2 messages by default. There's no switch at this moment.
Adding the support to produce SOAP 1.1 messages is not a big deal. The
real
question here is if we want to capture the requirement (like version="
1.1"
or version="1.2") from the SCDL for web service binding so that the
Tuscany
runtime can act differently on the setting. I don't think such an
attribute
is defined by SCA 2.0 spec version 0.9.
The WSDL SOAP binding doesn't have such information either. In Axis, the
SOAP vesion is set a property on the Call object.
Raymond Feng
Raymond Feng Proud owner of www.enjoyjava.com The Cyber Cafeteria to
Enjoy
Java!
----- Original Message -----
From: "ant elder" <[EMAIL PROTECTED] >
To: <[email protected]>
Sent: Tuesday, January 10, 2006 11:23 AM
Subject: Does Tuscany support SOAP 1.1?
The current Tuscany WS support uses SOAP 1.2 by default, is there a way
to
say you want SOAP 1.1?
...ant
