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
I'm new to struts and haven't watched all the discussion about workflow
processing. If anyone could give me a short introduction on what has
happened so far I would be thankful (since I like the design behind struts I
would really like to contribute). As far as I can see from the discu
The differences are not much between what u are suggesting vs what I
mentioned.
but I would like to point some differences though:
1. I believe that a Struts action's should have outcomes/results rather
than basing workflows right away. So a manager can say Action has
Result/Outcome (we can choos
Instead of changing the perform action, how about extending the action
mappings to support workflow constructs? In addition to form bean types,
forwards, redirects, and input pages, the ActionMappings tree could also
store workflows.
if (..) return (mapping.findWorkflow("Failure") ;
else return (
Currently the perform() method in the Action object takes ActionMapping as
one of the parameters & returns the ActionForward instance corresponding
to an evaluated result.
Instead, we could let the perform(...) method return a String which is the
result value. The ActionServlet can then determine
There's a relatively new archive for Struts-Dev at mail-archive.com.
There's an older archive there to for Struts-User, which is pleasant to
use.
Craig's mentioned the workflow processing several times, but I don't
believe there has been anything like a detailed discussi
I'm new to this list, so excuse me if this has already been discussed ad
nauseum. I couldn't find a digest for the dev mailing list.
I was busy developing my own portal framework, complete with workflow
processing, when a friend pointed me to Struts. Well, I've now convinced
