> > That's good idea using the Shale filter commands. Seems like a great place > > to > capture state at a page level and if the managed beans are defined in request > scope, you wouldn't have to clone the object before pushing on the context > stack. > > Just so you know I was refering to the Filter class in commons-chain. >
Oh, same difference. I thought you were registering preprocess and postprocess Shale filter commands like you would a remote command. I did get that you are using the Filter Command interface. That CoR is a great pattern - works in any tier of the application. Chains will be as "bread and butter" as the digester and bean utils :-). > > Gary > > sean > > --------------------------------------------------------------------- > 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]
