Ted Husted writes:
...
So, I would envision something like this for the ActionMappings
!-- This Action would be passed the path to the current workflow,
if any. It would check for any pending ActionRequest (workflow
already begun) and forward to that instead of next if present --
To: [EMAIL PROTECTED]
Subject: Re: ActionMapping Workflows
I'm liking the ActionRequest idea. I've tried
similar things, but needed
the parameter map idea.
Do you have any code yet?
I agree that leveraging ActionForwards sounds like
the way to go.
As to the requirements Matthias
This sounds like a good strategy. I'd like to do very much the same
thing, but with ActionMappings rather than tablibs. One reason would be
to allow a form to be used both with and without a workfow.
Ronel Sumibcay wrote:
It hasn't caused any problems for me *so far*, but what i did was
OK, so our initial draft working requirements are
1. Define which actions can follow the current action.
2. Define which actions are allowed to be executed immediately before
the current action.
3. Define which action will follow the current action (dynamic action
path).
4. Invoke another
Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 11, 2001 8:13 AM
To: [EMAIL PROTECTED]
Subject: Re: ActionMapping Workflows
OK, so our initial draft working requirements are
1. Define which actions can follow the current action.
2. Define which actions are allowed
My first thought here would be to make this information available as a
helper object that would read the forwards from the ActionMappings and
bundle them up for the view. The view could then write whatever buttons
it liked by reference to the helper object and the logic tags. Of
course, someone
I think this is a great idea. I can't tell you how many times I've
dynamically loaded hidden fields to determine the nextAction. A standard
way of doing this would be very nice.
Chuck
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 4:44 PM
The general idea I'm playing with now is
1) Extend ActionMappings with request and actionPath properties.
2) Extend ActionServlet to place the ActionMapping in the request
context if request=true.
3) Extend html:form to check for ActionMapping.getActionPath() when the
path is not specified.
Ted and others,
I don't really see the necessity of this extension for your update/insert scenario.
What you want to do is the following:
Insert: - InsertAction
/
ActionForm
\
Update: - UpdateAction
I suppose storing the information in the session would work. Though, I
imagine this means the state value would be hardcoded into the Java
source. I'm working toward scripting workflows from within the
ActionMappings, and would like to be able to reroute the flow without
changing the Java source.
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
-
From: Matthias Bauer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 10, 2001 9:12 AM
Subject: Re: ActionMapping Workflows
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
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
from
anyone or has someone solved this issue more elegantly?
-Original Message-
From: Jonathan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 8:35 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: ActionMapping Workflows
Can I ask how you all are thinking about bouncing
I'm thinking about scripting workflows through the ActionMappings.
Each step in the flow would be a mapping, and the ways the steps could
branch would be local forwards for those mappings. As you progress
through the workflow, the Action decides which logical forward to
return.
I'm finding
Something I have found generally useful is a Resource Cache. This is
just a hashtable in the session where I can (judiciously) tuck objects
for future reference. In the case of a multiform workflow, each of the
subforms could be saved to the cache, and then recalled as needed along
the way.
Of
.
- Original Message -
From: Matthias Bauer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 10, 2001 9:12 AM
Subject: Re: ActionMapping Workflows
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
-workflow is
popped from the stack.
Thanks.
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 8:37 AM
To: [EMAIL PROTECTED]
Subject: Re: ActionMapping Workflows
I'm thinking about scripting workflows through the ActionMappings.
Each step
in this discussion when a sub-workflow is
popped from the stack.
Thanks.
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 8:37 AM
To: [EMAIL PROTECTED]
Subject: Re: ActionMapping Workflows
I'm thinking about scripting workflows through
with a solution?
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 4:16 PM
To: [EMAIL PROTECTED]
Subject: Re: ActionMapping Workflows
I'm liking the ActionRequest idea. I've tried similar things, but needed
the parameter map idea.
Do you have any code yet?
I
]
Subject: Re: ActionMapping Workflows
I'm liking the ActionRequest idea. I've tried
similar things, but needed
the parameter map idea.
Do you have any code yet?
I agree that leveraging ActionForwards sounds like
the way to go.
As to the requirements Matthias started, I would
change 3
PROTECTED]
Sent: Tuesday, July 10, 2001 4:04 PM
Subject: Re: ActionMapping Workflows
What your thinking of may already do this, but I
thought I would mention this in case it didn't. If
you end up contructing a workflow using the actions,
it would be nice if it could be defined as a linked
list
WorkFlowEntry.
After assigning the result, it then does an internal forward to the uri
specifed by 'workFlowExitTarget'.
-ronel
-Original Message-
From: Robbin L. Gratz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 3:10 PM
To: [EMAIL PROTECTED]
Subject: RE: ActionMapping Workflows
AM
To: [EMAIL PROTECTED]
Subject: Re: ActionMapping Workflows
I'm thinking about scripting workflows through the ActionMappings.
Each step in the flow would be a mapping, and the ways the steps could
branch would be local forwards for those mappings. As you progress
through
may still
be a stack, though. :-}
--
Martin Cooper
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 10, 2001 2:16 PM
Subject: Re: ActionMapping Workflows
I'm liking the ActionRequest idea. I've tried similar things
25 matches
Mail list logo
