Agreed. But, remember that the plugin gets a reference to ActionServlet and ModuleConfig, so the plugin would have to be modified either way, or those objects provided somehow. I'm not sure how feasible the later is, and if you have to modify the plugins to not use them anyway, there's probably no point, might as well make each one its own listener then... then again, you could make an argument that one listener calling them all is less configuration for developers, which is good :)
Frank -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! On Tue, June 13, 2006 11:30 am, [EMAIL PROTECTED] wrote: > Frank W. Zammetti said: >> I suppose we could recommend people use ContextListeners >> instead, which >> I've come to prefer frankly, but if we're talking about >> upgrading/compatibility, that's maybe not the best answer. > > A ContextListener that calls all the plugins shouldn't be too hard. > > --------------------------------------------------------------------- > 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]
