RE: MessageContext in handler

having access to MessageContext :) -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 06, 2008 3:46 AM To: axis-user@ws.apache.org Subject: Re: MessageContext in handler Why don't you use a static hook in the callback handler class itself? Thanks, Ru

Re: MessageContext in handler

Why don't you use a static hook in the callback handler class itself? Thanks, Ruchith On Fri, May 2, 2008 at 7:37 AM, Parham, Clinton <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > I'm new to Axis2 and still trying to get comfortable with the new > architecture. I have engaged the Rampart modul

MessageContext in handler

Hi, I'm new to Axis2 and still trying to get comfortable with the new architecture. I have engaged the Rampart module and during CallbackHandler.handle(), I need to connect to my database to verify the password. Once verified, I would like to store the database connection (along with some other

Re: Axis2 Namespace lookup error throw when I access the MessageContext in handler on client service request (JAXB RI databinding)

uestion > is why when I access the MessageContext in a handler does it behave > differently? The MessageContext surely gets accessed at some stage in the > normal (no custom handler) client invocation, so is there something I am > missing, or am I accessing the MessageContext too early, or a

Axis2 Namespace lookup error throw when I access the MessageContext in handler on client service request (JAXB RI databinding)

eatly appreciated… Pat -- View this message in context: http://www.nabble.com/Axis2-Namespace-lookup-error-throw-when-I-access-the-MessageContext-in-handler-on-client-service-request-%28JAXB-RI-databinding%29-tp14697730p14697730.ht