Craig,
Your Workflow Proposal seems like a great start. Several of us have
played around with some workflow concepts on our current project but it
would be great to have something integrated into Struts.
We have a few concepts that weren't mentioned that we think are worth
considering:
- "boo
craigmcc01/08/15 20:52:09
Modified:src/share/org/apache/struts/action Action.java
Log:
Add a variation of the existing isTokenValid() method that optinally
resets the token in the same, indivisible, operation. This avoids a
potential race condition that bypasses the check made
It would be useful to have an 'alt' attribute on
tag. eg.
There are two uses:
In case Struts fails to find the message/resource, it can display the
default label (and display a warning on the console).
For design-time tools (eg. Dreamweaver), it will be easier for the
tools to display some me
Two questions.
Has anybody made a JSP 1.1 version of the jsptl? The
documentation mentions that this may be considered (I
think), but I couldn't find anything in the newsgroups
regarding this.
Has anybody played with modifying Struts tags to use
the expression language?
If not, I may take
There is an html:messages tag that is basically the
same as html:errors except it iterates over messages
and errors so you can remove the html from the message
resources. There are the classes ActionMessages and
ActionMessage for general messages like "Record has
been deleted.". ActionErrors is
Sounds very good. Addresses my concerns, as well. It would be nice if the
two concepts, Activity and Process, had similar grammars for specifying
them. This is only because they seem to me to be such similar concepts.
The context as you outline is fine. This functions exactly the same way I
h
The initial version of the proposal is focused on the Activity and Step
components (we refined the vocabulary a little based on feedback -- there
is now a distinction between Process and Acivity). Activity is more for
things that are relatively short term, and involving only a single person
(such
Yes. This is exactly the reason I proposed the addition to
the schema a few days ago. If you are persisting the state across a
workflow, you have to have some method of retrieving the state. My thought
was to identify each FormBean (the data that creates the state of the
workflow) by a unique
dwinterfeldt01/08/15 10:41:50
Modified:doc struts-html.xml
Log:
Added a clearer description of the message attribute for the messages tag.
Revision ChangesPath
1.19 +5 -3 jakarta-struts/doc/struts-html.xml
Index: struts-html.xml
I think a new tag that allows you to not put HTML in your resource file
already exists in post 1.0 Struts in the form of the tag.
It can be used in place of . The errors class is now a subclass
of a message class.
-Original Message-
From: Martin D Bayly [mailto:[EMAIL PROTECTED]]
Sent: W
Hal,
That is exactly what I'm looking for. Thank you for you help.
-Original Message-
From: Deadman, Hal [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 4:14 PM
To: [EMAIL PROTECTED]
Subject: RE: findForward and Errors
You can put an entry in the property files like t
A useful enhancement to the tag would be to have a single message
header/footer as well as an error block header and footer.
This enables you to keep your message strings free of html markup such as the
shown in the examples.
eg.
errors.header=Validation ErrorYou must correct
the following e
12 matches
Mail list logo
