I thought about that too, but in the end, I think the chain is a little to inflexible for application workflow. Most workflows that I deal with are more than a simple linear execution of actions and while you can get the chain to branch by manipulating key values in the context, it is kinda awkward and error prone.
The solution, I feel, is more along the lines of what Alex is putting forth in his WARS architecture (http://www.theserverside.com/news/thread.jsp?thread_id=23625), specifically a clean separation between workflow and actions. He sees workflow being able to be implemented multiple ways although his primary implemention is through a JSR-94-compatible engine. Personally, I think the ideal workflow implementation would use Cocoon's flowscript which takes JavaScript and continuations support and uses them to smoothly script a complex web transaction possibily involving multiple pages. Don > It's striking me that my chain-config.xml files are looking somewhat > similar to the example workflow xml file over in the sandbox/workflow > area. > > In addition ComposableRequestProcessor by it's very name has a > workflow-ish ring to it. > > A "ComposableBusinessLogicInvoker" seems like it would fit the bill for > me very nicely, and would be rapidly closing in on the stated goals for > the functionality of the sandbox/workflow component. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > It's striking me that my chain-config.xml files are looking somewhat > similar to the example workflow xml file over in the sandbox/workflow > area. > > In addition ComposableRequestProcessor by it's very name has a > workflow-ish ring to it. > > A "ComposableBusinessLogicInvoker" seems like it would fit the bill for > me very nicely, and would be rapidly closing in on the stated goals for > the functionality of the sandbox/workflow component. > > > --------------------------------------------------------------------- > 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]
