Created a Jira http://issues.apache.org/jira/browse/AXISCPP-725
Samisa... On Thu, 2005-06-30 at 10:49, John Hawkins wrote: > agreed, as long as there are both servers out there. > > > > > Samisa Abeysinghe > <[EMAIL PROTECTED]> > > 30/06/2005 17:43 > Please respond to > "Apache AXIS C Developers List" > To > Apache AXIS C > Developers List > <[email protected]> > cc > > Subject > Re: SOAP 1.2 > support > > > > > > Is Axis c going to support only SOAP 1.2? > > Well we already support SOAP 1.1 to great depth. So don't see any > reason > to drop SOAP 1.1. > > Rather I hope SOAP 1.2 would live alongside SOAP 1.1. > > Thanks, > Samisa... > > On Thu, 2005-06-30 at 10:22, sanjaya gayan wrote: > > The document.... > > > > > http://www.idealliance.org/papers/xmle02/dx_xmle02/papers/02-02-02/02-02-02.html > > > > may of be use here. It gives the following information on how a SOAP > > 1.2 should react to other SOAP versions. Is Axis c going to support > > only SOAP 1.2? > > > > > > 3.3. Versioning Mechanism > > SOAP 1.2 adds semantics for deailing with messages from different > > versions of SOAP: > > A SOAP 1.2 node that receives a SOAP 1.1 message will respond with a > > SOAP 1.1 envelope containing a SOAP 1.1 "VersionMismatch" fault. > > A SOAP 1.2 node that receives a message from any other version of > SOAP > > (including future versions) will respond with a SOAP 1.2 envelope > > containing a SOAP 1.2 "VersionMismatch" fault and an Upgrade header > > with a list of the supported envelope versions. > > > > sanjaya. > > > > John Hawkins <[EMAIL PROTECTED]> wrote: > > sounds a good plan. > > > > We've identified a number of areas that we need to look at > in > > order to support SOAP 1.2 correctly. Adrian is going to look > > into them in a few wks time. The biggest area is the > > fault/exception model. If you get there first then that's > > great otherwise you can count on Adrian :-) > > > > > > > > > > Samisa Abeysinghe > > <[EMAIL PROTECTED]> > > > > 30/06/2005 10:34 > > Please respond to > > "Apache AXIS C Developers List" > > > > > > To > > Apache AXIS C > > Developers List > > <[email protected]> > > cc > > > > Subject > > SOAP 1.2 > > support > > > > > > > > > > Hi all, > > As I mentioned in an earlier email, we have SOAP 1.1 > verion > > hardcoded in generated code. > > > > This also means that we have been always using SOAP 1.1 > and > > never > > tested SOAP 1.2 code. (Correct me if I am wrong) > > > > I propose that we provide and an API at Stub level to set > > the SOAP > > version. (e.g. Stub::setSOAPVersion() ). Then like we do for > > the SOAP > > action in the generetd code, the generated code would not > set > > the SOAP > > version if it is laready set. Else it would set that to the > > default > > of SOAP 1.1 9which is the de-facto hard coded default that > we > > have as > > of now. > > > > Value your thougts on this. > > Thanks, > > Samisa... > > > > > > > ______________________________________________________________________ > > How much free photo storage do you get? Store your holiday snaps for > > FREE with Yahoo! Photos. Get Yahoo! Photos > -- > Samisa Abeysinghe <[EMAIL PROTECTED]> > Virtusa Corporation -- Samisa Abeysinghe <[EMAIL PROTECTED]> Virtusa Corporation
