> -----Original Message----- > From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 13, 2003 4:29 PM > To: [EMAIL PROTECTED] > Subject: Re: processing (lifecycle) events > > > >> > >>>>I need to acquire resources for a processing phase and then would > >>>>like to automatically release it at processing end. > >>>> > >>>> > >>Isn't this something RequestLifecycleComponent is intended for? I.e., > >>when you obtain this component it gets all the resources needed, and > >>when request processing is done, it gets recycled and releases those > >>resources. > >> > >> > >> > >If you only want to cleanup afterwards, yes the > RequestLifecycleComponent > >is one possibility. > >But I (and I thought Jakob as well) need a notification to a custom > >object when the processing begins and ends. > > > > I've read that he needs to release resources, not to get a > notification... Then RequestLifecycleComponent should work. Using > notifications you can also hack something like this but I think writing > a proper component will result in cleaner architecture... > > > > The beginning could be > >done by a custom action at the top of the sitemap, but this is not > >a nice solution. And the ending of the processing can not be notificated > >right now (without hacking the servlet or something at least). > > > > *IF* you need notification at all. May be all you need is a component > doing the work with proper lifecycle... > IMHO, of course. > Yes, I need notification and *not* a mechanism that cleans up at the end of the process.
Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
