Yes, I would need matching postprocess commands to accomplish my task. My custom command basically checks if the ClayContext's parent component id is 'clayView' and if it is then it goes and adds the appropriate javascript to the top of the component child list.
I originally had thought that the Filter interface provided a callback for after the entire chain had been excecuted, but know I realize that it is just a callback for after that 1 particular command has been executed. On 11/17/05, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > Cool, thanks Gary. > > > > so the following > > > > <catalog name="clayCustomization"> > > <chain name="preprocessAddComponent"> > > <command className="org.apache.shale.usecases.rolodex.CustomCommand"/> > > </chain> > > </catalog> > > > > would execute CustomCommand before the creation of a component, > > validator, etc? I guess if I make CustomCommand a Filter then I would > > get a hook to the postProcess method which would actually be executed > > after the component, validator, etc is created? > > > > I believe that the postprocess for the CustomCommand implementing Filter will > execute before the addComponent chain is invoked. We could add postprocess > chains matching all the preprocess commands if you need processing after the > component is created. > > Gary > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
