Inline. On Tue, 23 Nov 2004 11:42:37 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote: > At 11:26 AM -0600 11/23/04, Hubert Rabago wrote: > >It would be nice if plugins can inject chain elements at specific > >points in the chain at startup, programatically. This way, plugins > >can be programmed to modify specific portions of the chain that it is > >concerned with, without affecting other portions of the chain or > >modifications of other plugins. > > I don't think you could do this with zero modifications to the > chain-config, but it would be easy enough to add one or more > LookupCommands like the one in the current example chain-config which > look for injected commands under specific names and in specific > catalogs. If you thought that there were some clear logical ways to > group the base chain-config.xml, we could have it run as a series of > lookup commands. I already am thinking that we should partition it > into an "action-chain" and "view-chain", but maybe it should be more > finely grained? >
The extreme case I have in mind would be one chain for each step that the current request processor does. Yes, I know, it's extreme. At this point, it's just an idea I'm bringing up. > On the other hand, why not just specify an alternate chain-config > file which does exactly what you need it to do? Specific apps would be able to do this, but I was trying to think from the perspective of a plugin developer. I haven't looked at an example yet, but would the use of tiles require both a struts-config change to activate the plugin, as well as a chain-config change to modify the chain? What if an app were to use multiple plugins that inject their own commands at different points? Do we leave the changes to the end-user/app-developer? > Or are you looking for a more comprehensive and flexible solution, > like Maven's "preGoal" and "postGoal" definitions which allow you to > add arbitrary goals anywhere. This would be tricky right now because > commands aren't required to have names. > > Joe > Hubert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
