Ruchith: could you describe further. Do you mean a static object, populated in the handler, that I can reference later in the processing? That might work but I would need a reliable way to clean it up and for it to be thread safe. It just seems like there should be a simple approach - like 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, 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 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 related information) for reuse later in the > processing. Under heavy utilization, requesting two database connections per > request starts adding up. > > > > How can I do this? MessageContext (where I stored this with Axis1) is null > during CallbackHandler.handle(). I've seen other similar postings but no > clear answer. > > > > Thank you. > > -- --------------------------------------------------------------------- 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]
