Ok,
then maybe we should start to work on that. The first step should be to define
the requirements, i. e. what do we expect from the workflow implementation is
struts?
My requirements would be the following (part 1 and 2 I already implemented):
1. Define which actions can follow the current action.
2. Define which actions are allowed to be executed immediately before the
current action.
3. A stack with actions to which to return, if some branched action path is
finished.
4. Your requirement, Ted, to allow configuration of form action parameters via
struts-config.xml
What about setting up a new thread with a request for required features?
--- Matthias
Ted Husted wrote:
> A few people were working on diagramming workflows, but didn't seem to
> be working on actually implementating workflows in Struts.
>
> There's been a lot of hand-waving discussions as to workflows on the
> list, but nothing concrete.
>
> The committers do not work together outside the DEV list, so anything
> that's being done is being done here.
>
> I agree there should be a reasonable high concept. What are your
> thoughts here?
>
> Matthias Bauer wrote:
>
>>Ok, that's fine with me and it makes pretty much sense. However, this will not
>>be enough to implement workflow completely. It is just a little step toward
>>workflow control as a whole, just the same as the simple workflow extension I
>>already proposed together with some code on this list.
>>
>>I think all this should be put together to come up with a reasonable concept how
>>to implement workflow, instead of multiple single efforts to implement some
>>single aspects only.
>>
>>Is there a team working on that?
>>
>>--- Matthias
>>
