Carsten Ziegeler wrote:
Vadim Gritsenko wrote: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...
Carsten Ziegeler wrote:If you only want to cleanup afterwards, yes the RequestLifecycleComponent is one possibility.
Hi Jakob,Carsten,
I think this is a great idea, (because) I need it in several areas
as well. Could you expand a little bit more on how to configure
the listeners and what their interface should/could look like.
This might then help to convince others that listeners are usefull
in some scenarios.
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.I need to acquire resources for a processing phase and then would
like to automatically release it at processing end.
But I (and I thought Jakob as well) need a notification to a custom
object when the processing begins and ends.
*IF* you need notification at all. May be all you need is a component doing the work with proper lifecycle...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).
IMHO, of course.
Vadim
Carsten
Carsten Ziegeler Open Source Group, S&N AG
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
