Following was for server side header manipulation btw. Regards Chathura
On 5/26/06, Chathura Herath <[EMAIL PROTECTED]> wrote:
The out message context is created at the end of the in chain by the message receiver only if required(e.g. if the mep is In-Only the particular message receiver will not create the out message context). Anyway, what you have described below isnt the anticipated programming model of axis2. Here is wht you should do. Write an inflow handler that saves the headers/state(that u want to lookup in the outflow) in the operationcontext using the setProperty method. Write and outflow handler that extracts this saved state/header from the operation context and set it to the out soapEnvelop. Create amodule out of this handler(s) and deploy. You can use the same handler for both, have a look at the login module in the user guide. http://ws.apache.org/axis2/1_0/userguide4.html#Step2_:_LogHandler HTH Chathura On 5/26/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Hi all, > > is it possible to get the same result with outgoing messages as well by > using the setOperationContext() (it seems to me that the > > outMsgCtx = opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE); > > into the setOperationContext() doesn't work as espected > )? > > If no, is there any way to add some headers to outgoing messages? > > Thanks in advance, > Michele > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Chathura Herath http://people.apache.org/~chathura/ http://chathurah.blogspot.com/
-- Chathura Herath http://people.apache.org/~chathura/ http://chathurah.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
