>From a high-level point of view it looks like the concept of Service Context is what I need.
However, I find it quite limiting the use of the StringHolder as only definition of the SOAP Header (if that is what is meant by the example). I cannot find any mention of header persistence anywhere (I am under the impression that this would belongs to the SOAP spec anyway, right?) This being said, I know that in .Net you can set the header once and they persist for the life of the Service object. Also, in .Net the SOAP Header is bound to the operation (as defined below) (and by the way is supported although I said the opposite earlier this week) <operation name="addFolder"> <soap:operation soapAction="http://cm1.cognos.com/"/> <input> <soap:body use="encoded" .../> <soap:header required="true" message="cm1:CAMElement" part="CAM" use="encoded" .../> </input> <output> <soap:body use="encoded" .../> </output> </operation> but it does not translate into a message part, which is good since IMO you do not necessarily want to pollute the public API with authentication credential for example. JAX-RPC spec. seems to suggest that the message would have a part defined for the SOAP Header with which I disagree (this also probably suggests that there would be no persistence between calls). In conclusion, my understanding of the ServiceContext described in JAX-RPC section 11 tells me that allowing access to the SOAP Header only through the operation's parameters would be nice but too limiting. Sylvain. -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 07, 2002 10:43 AM To: [EMAIL PROTECTED] Subject: Re: Setting SOAP Headers AXIS doesn't implement it yet, but take a look at section 11 in the JAX-RPC spec (http://java.sun.com/xml/downloads/jaxrpc.html) and see if that's what you need. Russell Butek [EMAIL PROTECTED] "St-Germain, Sylvain" <[EMAIL PROTECTED]> on 02/07/2002 09:29:51 AM Please respond to [EMAIL PROTECTED] To: "Axis Dev (E-mail)" <[EMAIL PROTECTED]> cc: Subject: Setting SOAP Headers Hi all, I need to the ability to set the SOAP Header and currently the Call object is private to the BindingStub class. I understand that I can hack my way in there and do whatever I like but I would prefer to be able to set the headers from my client application. But this is not possible since the the Call object is created by each of the service's operations. I am under the impression that having access to the SOAP header is something that should be allowed and that possibly the header should persists between calls... Am I wrong? -- 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.
