You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Bill Nagy <na...@watson.ibm.com> on 2006/05/01 19:58:37 UTC

Re: [Axis2] Axis2 Lifecycle

On Sat, 2006-04-29 at 09:10 +0600, Sanjiva Weerawarana wrote:
> Hi Jens,
> 
> > While Tony reported this today for services only (AXIS2-633) it seems Axis2
> > does not have full lifecycle support.
> > 
> > Since I was trying to come up with a fix for Axis2-595 I was looking for
> > something within Axis2 codebase which would help to do some cleanup during
> > shutdown. It turned out that the Axis2 deployment engine is not exposed for
> > clean shutdown and Handler#cleanup()/ TransportSender#cleanUp(MessageContext
> > msgContext) is never called.
> 
> Handler.cleanup() was never implemented and I thought it was removed! If
> not it should be .. we have an on-going discussion around some cleanup
> activity like that (look for a thread originated by Bill Nagy) but we
> agreed to do that post 1.0.

Actually what I was talking about and what Jens is talking about are two
different things I believe.  The discussion that I started is around
"cleanup" on an interaction/message level.  The method that Jens is
referring to is for "cleanup" at an artifact (i.e. handler instance)
level, analogous to the init() method.  For example, if your handler
acquired a database connection during init(), you would rely upon the
cleanup() method to close that connection.  While I don't have a
particular need for it right now, I can see how it could be useful to
someone (and completes the handler lifecycle.)

-Bill