Hi, Ant. 1) I checked WS-I BP 1.1. It only talks about SOAP 1.1, I agree it makes sense to have the default as SOAP 1.1.
2) I tried the hack and it seems to be working for me. With the change I proposed, I got the following SOAP messages from my unit test. Request: <soapenv:Envelope xmlns:lit="http://www.example.org/Test/DocLit"; xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Header> <lit:context soapenv:mustUnderstand="0" xmlns:lit="http://www.example.org/Test/DocLit";>transactionId-0001</lit:conte xt> </soapenv:Header> <soapenv:Body> <lit:source xmlns:lit="http://www.example.org/Test/DocLit";>123</lit:source> <lit:target xmlns:lit="http://www.example.org/Test/DocLit";>2</lit:target> </soapenv:Body> </soapenv:Envelope> Response: <soapenv:Envelope xmlns:lit="http://www.example.org/Test/DocLit"; xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <lit:index xmlns:lit="http://www.example.org/Test/DocLit";>1</lit:index> </soapenv:Body> </soapenv:Envelope> The section of the change is: public interface MessageElementPackage extends EPackage { /** * The package name. * <!-- begin-user-doc --> * <!-- end-user-doc --> * * @generated */ String eNAME = "message"; /** * The package namespace URI. * <!-- begin-user-doc --> * <!-- end-user-doc --> * * @generated */ // String eNS_URI = "http://www.w3.org/2003/05/soap-envelope";; String eNS_URI = "http://schemas.xmlsoap.org/soap/envelope/";; Thanks, Raymond ----- Original Message ----- From: "ant elder" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, January 13, 2006 2:23 AM Subject: Re: Does Tuscany support SOAP 1.1? 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 > > > > > >
