First of all: Sounds good to restate the requirement.
Second: Maybe we can talk of some use cases here, in order to put some flesh to
the workflow bones.
How about considering the following really simple use case:
Workflow1: The user browses in an open community board and is currently visiting
Thinking about this some more, if we have the 'indexId' attribute, do we
need the 'indexed' attribute as well? Wouldn't the specification of a value
for 'indexId' imply 'indexed="true"' anyway?
--
Martin Cooper
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent:
What happend if the user opens a new browser window in the workflow and works
on in the new window, then come back to the first window and also
wants to work on ? This is not only a workflow problem
Our solution for navigation is also a navigation stack in the session,
to rember the link to go ba
Right now, what I have is a combination of code fragments, pseudo-code, and
stuff that's still in my head. I expect to turn this into real code in the
next day or so.
Point taken regarding not implying an implementation. I agree with your
restatement of the real requirement. My near-term implemen
Hello dhay,
Wednesday, July 11, 2001, 12:07:13 AM, you wrote:
dlc> Have changed the LinkTag to allow users to specify the indexId.
dlc> After doing some more investigation, don't think your first suggestion, Oleg,
dlc> would ever come up. If the user specifies the paramName, Id and property in
dwinterfeldt01/07/10 20:33:57
Modified:src/test/org/apache/struts/taglib/logic
TestNotPresentTag.java
Log:
Added tests for cookie, header, and parameter.
Revision ChangesPath
1.2 +136 -45
jakarta-struts/src/test/org/apache/struts/taglib/l
dwinterfeldt01/07/10 20:29:52
Modified:src/test/org/apache/struts/taglib/logic TestPresentTag.java
Log:
Added tests for cookie, header, and parameter.
Revision ChangesPath
1.2 +97 -8
jakarta-struts/src/test/org/apache/struts/taglib/logic/TestPresentTag.java
I will follow up with all of you about the
documentation when I return in a few weeks.
dwinterfeldt01/07/10 19:20:51
Added: src/test/org/apache/struts/taglib/logic TestEqualTag.java
TestNotPresentTag.java TestPresentTag.java
Log:
Initial tests for the EqualTag, PresentTag, and NotPresentTag.
Revision ChangesPath
1.1
dwinterfeldt01/07/10 19:05:58
jakarta-struts/src/test/org/apache/struts/taglib/logic - New directory
dwinterfeldt01/07/10 19:05:46
jakarta-struts/src/test/org/apache/struts/taglib - New directory
dwinterfeldt01/07/10 19:04:49
Modified:conf/test web.xml
Log:
Added a servlet reference and mapping for the JspRedirector.
Revision ChangesPath
1.2 +14 -0 jakarta-struts/conf/test/web.xml
Index: web.xml
===
dwinterfeldt01/07/10 18:59:10
Added: web/test/test redirector.jsp
Log:
Component of Cactus for JSP Unit Testing. Modified from distribution to set session
to true.
Revision ChangesPath
1.1 jakarta-struts/web/test/test/redirector.jsp
Index: redir
dwinterfeldt01/07/10 18:58:09
jakarta-struts/web/test/test - New directory
dwinterfeldt01/07/10 18:57:46
Modified:.build-tests.xml
Log:
Added a batch test that will run all tests for the Logic Taglibs. Added a cleanup
for Tomcat 3 and 4 so the "test.all" can be run twice in a row.
Revision ChangesPath
1.2 +16 -2 jakarta-stru
It hasn't caused any problems for me *so far*, but what i did was defined a
class called WorkFlowEntry with the following properties:
workFlowEntryTarget : the entry point (uri) of a workflow
workFlowCancelTarget : the uri of where to go when the user cancels the
workflow...i found
I agree that the idea of lock-step stack doesn't seem to fit well within
a Web application.
A more useful idea might be a cursor that tracked the farthest step
reached. The entry point of the workflow (step 1) could "fast-forward"
if a cursor for that workflow was present. The cursor might be o
Why not try enforcing some kind of composition. For instance, a workflow
might have 5 steps. Separate the components themselves from the order in
which they must be carried out. That is, if you must do 5 steps, then one
"WorkflowObject" will be composed of 5 "StepObject" s. Upon completion of
Maybe the token that can be generated in an action be
used or make a workflow token.
David
--- "Robbin L. Gratz" <[EMAIL PROTECTED]>
wrote:
>
>
> With the "return stack" concept, I'm assuming this
> will be a session scope
> variable. What happens when the user clicks the
> back button rather
With the "return stack" concept, I'm assuming this will be a session scope
variable. What happens when the user clicks the back button rather than
going through the process the app provides? Now the session is out of synch
with the actual position in the process that the user is in. It seems
I do keep thinking that a single stack might not be the best mechanism
for a Web application, where we have no control over the client.
It might be that each workflow would have it's own stack, or cursor, so
that if the actor entered it again, they would be returned to where they
left off. So, i
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 (or at least kept track of the last action). So
you wouldn't just go forward, but coul
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 to
3. The ability to call (or nest) another wo
One thing you may want to consider when tucking workflow data away
is the scope of the data. For example, if I jump out of the normal
workflow to do some object creation that will eventually be used by
the original workflow, the sub-workflow should probably not be able
to access the data of the o
Have changed the LinkTag to allow users to specify the indexId.
After doing some more investigation, don't think your first suggestion, Oleg,
would ever come up. If the user specifies the paramName, Id and property in a
link in a particular row in the table ie in your example:
> paramId="whe
Has anybody thought about what happens when a user cancels 'sub-workflow'?
Should there be a path defined for each local ActionForward for this case?
Thus allowing a way to get back to the parent workflow if this occurs, or is
this functionality already implied in this discussion when a sub-workfl
I have a similar concern. In addition, there may be runtime parameter
values that need to be passed along, particularly when actions are chained
(something I do a lot of).
I am working on something related, in conjunction with what Matthias
referred to as a return stack. The goal is to be able
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
I just submitted the following bug. I'm posting this here just to get any
comments people might have.
--
The current docs on the select tag says:
If set to any arbitrary value, the rendered select element will support multiple
selections. [RT Expr]
This wording and the fact that it can be a
While I like the idea of PDF to print and give to managers, I hate reading
PDF online.
Please consider a HTML version with a "Print/PDF" link.
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 3:15 AM
To: [EMAIL PROTECTED]
Subject: Re: *TED* - r
As Components can be used to build "views" of the MVC framework, it could
be interesting to have the term "view" in the new name.
I have thought about "viewlet", but this is already used ;-).
Maybe "viewparts" or "viewpieces" ? This sound nice and can reflect the
fact that framework is for
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 tha
Another point that I believe is getting ignored on the workflow stuff is how
is data getting transferred between the different steps. In the system I
just worked on, we had a number of two or more step workflows that were used
within other larger workflows. The output from these "sub workflows"
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
Hi,
I'm working on Wesphere 3.5.3.
I've got a jsp which allow the user to modify a field .
I have to make controls on it and when it's wrong I call
errors.add("DateDeNaissance",new ActionError("error.modgen.datenaiss"));
In my Jsp i've the tag
My ApplicationResources.properties has the appriopri
Can I ask how you all are thinking about bouncing around between steps in
the workflow? Is it a stack that each step gets popped off? Arent workflow
steps cyclical sometimes? Developers talk alot about graphing workflows but
I have not read about the implementation.
- Original Message ---
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 anythi
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 thin
The HTML error tags looks for a errors.header and errors.footer string
in the applications resources file, which it wraps around the errors. So
this file should exist even if you are not otherwise using it. The
default name is ApplicationResources.properties, and it needs to be on
your application
Hi,
I'm working on Wesphere 3.5.3.
I've got a jsp which allow the user to modify a field .
I have to make controls on it and when it's wrong I call
errors.add("DateDeNaissance",new ActionError("error.modgen.datenaiss"));
In my Jsp i've the tag
And It throws this exception :
Original Error:
Mess
ok
- Original Message -
From: "Ted Husted" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 6:14 AM
Subject: Re: *TED* - round 2 of documentation
> At some point someone proposes something in a final form that can be
> committed directly to the distribution.
>
>
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.
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
At some point someone proposes something in a final form that can be
committed directly to the distribution.
We're all volunteers here, and share suggestions about what we each
would like, but what anyone actually does is up to the individual.
Once something is done, and ready to ship, or at
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 specifie
The standard approach is to create an Action for each of your JSP's and
visit that before displaying the page. In the Action, you can make the
database retreival and populate the ActionForm properties relating to
the HTML controls. For list boxes, there is a handy LabelValue class in
the Example A
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
T
47 matches
Mail list logo
