On Wed, 29 Oct 2003, Vic Cekvenich wrote: > But... the chain has a set of steps that are "pre-progrmed", and there > was some discusion as to what those steps should be idealy. Yes, it can > do return codes but.... > > If HiveMind (or an aproach like it) is used to do the chain, then I can > easily add interceptors, and alterantice idea for consideration
The chain supports the interceptors as well. A command can have any number of commands with each having commands and so on. > > I found this very educational: > http://jakarta.apache.org/~hlship/HiveMind.ppt > > ... and based on that I made a "leap", that, hey, we can intercept the > flow. A bit of AOP. > (There are some other ideas in there, like code to the interface "contract") Since you can already "intercept the flow" with the chain, I don't see what an IoC, if even applicable, could offer. Struts needs a composible process flow that is easily manipulatable and pluggable. I agree all those other fancy service-oriented features are nice, but IMO, they belong in the action/form layer. Don > > .V > > > > --------------------------------------------------------------------- > 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]
