yes, this is bad design. you should be able to get/set contextual message information from within handlers just as in the same way you can from jax-rpc and jax-ws handlders.
> -----Original Message----- > From: Ruchith Fernando [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 29, 2007 10:39 AM > To: axis-user@ws.apache.org > Subject: Re: MessageContext.getCurrentMessageContext() returns null. > > Hi, > > MessageContext.getCurrentMessageContext() will return the > message context only after the message reaches the message > receiver. The callback handler is called way before this and > at this point this will be null. > > Thanks, > Ruchith > > On 5/29/07, Wang, Hailong (NIH/CIT) [C] <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi, > > > > > > > > I happened a problem. After I used Rampart in the axis2, from the > > CallbackHandler in the server side I can not get MessageContext > > Instance throught > MessageContext.getCurrentMessageContext(). Is there > > anyone has any clue on this problem? Thanks in advance. > > > > > > > > Hailong Wang > > > > National Database for Autism Research(NDAR) > > > > NIH/CIT/DECA (MOM CONTRACTOR) > > > > 9000 Rockville Pike, Bld 12A/Room 2027 > > > > Bethesda, MD 20892 > > > > Phone: 301-402-3045 > > > > Fax: 301-480-0028 > > > > Email: [EMAIL PROTECTED] > > > > URL: http://ndar.nih.gov > > > > > > > -- > www.ruchith.org > www.wso2.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
