I was pleased to read the plans for workflow processing in Struts 1.1 - though I'm not entirely clear on what it's all about. One thing I feel is limiting about Struts ( this surely has been voiced ) is the inability to forward biz logic processing among various Action classes. "Action chaining" if you will. I realize this can be accomplished messily by forwarding from Action to Action. It sounds like the Workflow initiative will speak to this need.
The Workflow Processing To Do description states the goal is to: Create a mechanism by which business logic (now encoded in Action classes) can be subdivided into individual work Tasks that are combined according to configuration information (including flow control and iteration support) in the struts-config.xml file Indeed this sounds like these individual work Tasks will get the 'chaining' job done. However the workflow proposal at http://jakarta.apache.org/struts/proposal-workflow.html didn't seem to back up this notion as much as I was hoping (And no doubt the proposal came first ). Rather, it demonstrates 2 example scenarios workflow processing could be utilized, 1) a pluggable logon bean and 2) a wizard interface that collects information over several requests. I didn't take away anything that specifically spoke to the subdivision of biz logic processing among 'Tasks' or Actions. Apparently Workflow Processing will tackle a much bigger set of goals and tasks. But will it be in there? Thanks, Craig
