> -----Original Message----- > From: Sylvain Wallez [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 13, 2003 6:37 PM > To: [EMAIL PROTECTED] > Subject: Re: processing (lifecycle) events > > > Carsten Ziegeler wrote: > > >Hi Jakob, > > > >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. > > > > > > Same here. In our in-house product, we have extended > CocoonServlet.service() for this. But it's a real hack and I > don't like it. > > Listeners would be good as there are several states in the sitemap > execution where being notified makes sense : > - start of pipeline construction (for this an action could be fine) > - pipeline setup > - pipeline processing (when setup has detected that cache content is not > valid) > - end of processing (including a status indicating cached-content / > sucessfull execution / erroneous execution) > > We also have to find a way to distinguish between the different sitemap > invocations that can occur within a single request with "cocoon:" sources. > Yes, sounds good to me. When is it finished? :)
I guess we should come up with an Interface, how/where to configure it and which events we want to observe. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
