The key plug in point will be a ConfigurationProvider. You can inject your provider by setting the init-param configProviders. As much as possible, try to scan and set up the configuration ahead of time. If that won't work, have your plugin provide an UnknownHandler. See the codebehind plugin for examples.
Don On 7/30/07, Mark Menard <[EMAIL PROTECTED]> wrote: > > I'm in the process of trying to add Groovy support to the Zero Config in > Dispatcher. I have a few questions: > > 1. It look to me like the ConfigurationManager is instantiated and > initialized once on load of the application. Is that right? > > 2. Other than adding a method to Dispatcher, is there a way to hook into > the > Dispatcher's init process so I can compile and instantiate my Groovy > actions > and read their annotations, etc.? > > Now, for bonus points... As I see it looks like the ConfigurationManager > is > initialized once and that's it. If that is right, and you wanted to have > the > ability to add actions dynamically, how might you go about doing it? (I'll > do the lifting, just wondered if someone might have an idea on where first > to start digging.) > > Thanks, > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
