Tapestry uses this kind of structure quite a bit; the service interface specifies a void method, and one of the parameters that is passed to each command in the chain exists to store state about the invocation. Very useful, powerful, extensible ... and very testable!
On 7/22/07, Peter Beshai <[EMAIL PROTECTED]> wrote:
Hi everyone, I am interested using something similar to the workflow in Mac OS X's automator, and I'd like to know if the ChainBuilder provided in T5-IoC will be a suitable tool for this. That is, I would like to have several processes with different inputs and outputs and have them feed each other in order. For instance, Files come in and enter a service, which outputs a path. The path can be given to another service which will output a list. The list can be given to another service which also outputs a list. And so on. Is there anyway to have this kind of interaction using the chain of command principles? It seems to me that they don't directly allow transfer between subsequent commands. Is the way to do this with an external object (ASO?) that would store the information between commands? -- Peter Beshai CS 134 Tutor University of Waterloo
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
