All, after looking at several Web Service/SOAP implementations (.NET, BEA, Axis, SUN O.N.E.) and reading several specs (SOAP 1.1, SOAP 1.2, and XML protocol abstract model, several proposal from MS about SOAP routing, SOAP security, etc). IMO the header issue will become more relevant in the future. However, none of the current SOAP implementations really support SOAP headers, not to speak about interoperability.
At .NET MS says it supports headers if you provide the classes that handle it etc, but it seems it doesn't really work. Looking at the axis architecture I think axis can be extended to fully support SOAP headers. If there is interest I would propose that we start some discussions about SOAP Header support in axis and how it can be implemented. This can be done in parallel (at least most of it) with the ongoing more important encoding interoperability issues. Any thoughts? Regards, Werner > -----Ursprüngliche Nachricht----- > Von: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 5. Februar 2002 22:59 > An: [EMAIL PROTECTED] > Betreff: RE: (Rewriten): Setting the SOAP header through an > operation... > > > Thanks. > > Do you know what kind of work is involved there? > > FYI, It does not work in .Net either although we find some > articles that > mentioned that it should work.... > > Sylvain. > > -----Original Message----- > From: Russell Butek [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 05, 2002 2:42 PM > To: [EMAIL PROTECTED] > Subject: Re: (Rewriten): Setting the SOAP header through an > operation... > > > Excuse me. Let me rephrase what I just said. > > Is there a way to do this in AXIS? No. Should there be? Yes. > > You CAN specify what parameters go into the soap header vs > the soap body, > but AXIS doesn't support it. > > Russell Butek > [EMAIL PROTECTED] > > > Russell Butek/Austin/IBM@IBMUS on 02/05/2002 01:08:33 PM > > Please respond to [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > cc: > Subject: Re: (Rewriten): Setting the SOAP header through an > operation... > > > > Now? No. Should there be? Yes. > > Russell Butek > [EMAIL PROTECTED] > > > "St-Germain, Sylvain" <[EMAIL PROTECTED]> on > 02/05/2002 12:29:58 > PM > > Please respond to [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > cc: > Subject: (Rewriten): Setting the SOAP header through an operation... > > > > Hi all, > > Is there a syntax in the WSDL that will make Axis store a > method parameter > in the SOAP header? > > Regards, > Sylvain. > > -----Original Message----- > From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 04, 2002 6:05 PM > To: Axis-User (E-mail) > Subject: Setting the SOAP header through an operation... > > > Hi all, > > This is a little off topic but I though you might know. > > Is there a way in WSDL to define an operation that creates a header > element? > > I found this in the W3C's WSDL spec www.w3.org/TR/wsdl#_soap-e > ... (I slightly modified the namespaces stuff...) > > Look near the end for: > > <soap:header message="cm1:SubscribeToQuotes" part="subscribeheader" > use="literal"/> > > > <?xml version="1.0"?> > <definitions name="ContentManagerService" > targetNamespace="http://cm1.cognos.com/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:types="http://cm1.cognos.com/xsd"; > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:cm1="http://cm1.cognos.com/ > "> > <types> > <schema targetNamespace="http://cm1.cognos.com/xsd"; > xmlns="http://www.w3.org/2001/XMLSchema"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";> > <complexType name="uriReference"> > <sequence> > <element name="uri" type="xsd:string" maxOccurs="1"/> > </sequence> > </complexType> > > <element name="SubscribeToQuotes"> > <complexType> > <all> > <element name="tickerSymbol" type="string"/> > </all> > </complexType> > </element> > > <element name="SubscriptionHeader" type="types:uriReference"/> > > </schema> > </types> > > <message name="SubscribeToQuotes"> > <part name="body" element="types:SubscribeToQuotes"/> > <part name="subscribeheader" element="types:SubscriptionHeader"/> > </message> > > <portType name="StockQuotePortType"> > <operation name="SubscribeToQuotes"> > <input message="cm1:SubscribeToQuotes"/> > </operation> > </portType> > > <binding name="StockQuoteSoap" type="cm1:StockQuotePortType"> > <soap:binding style="document" > transport="http://example.com/smtp"/> > <operation name="SubscribeToQuotes"> > <input message="cm1:SubscribeToQuotes"> > <soap:body part="body" use="literal"/> > <soap:header message="cm1:SubscribeToQuotes" > part="subscribeheader" > use="literal"/> > </input> > </operation> > </binding> > > <service name="StockQuoteService"> > <port name="StockQuotePort" binding="cm1:StockQuoteSoap"> > <soap:address location="mailto:[EMAIL PROTECTED]"/> > </port> > </service> > > </definitions> > > > > > > -- > Sylvain > > This message may contain privileged and/or confidential > information. If > you > have received this e-mail in error or are not the intended > recipient, you > may not use, copy, disseminate or distribute it; do not open any > attachments, delete it immediately from your system and > notify the sender > promptly by e-mail that you have done so. Thank you. > > This message may contain privileged and/or confidential > information. If > you > have received this e-mail in error or are not the intended > recipient, you > may not use, copy, disseminate or distribute it; do not open any > attachments, delete it immediately from your system and > notify the sender > promptly by e-mail that you have done so. Thank you. > > > > > This message may contain privileged and/or confidential > information. If you > have received this e-mail in error or are not the intended > recipient, you > may not use, copy, disseminate or distribute it; do not open any > attachments, delete it immediately from your system and > notify the sender > promptly by e-mail that you have done so. Thank you. >
