The alternative Erik is thinking of is FindForward
http://cvs.apache.org/viewcvs/jakarta-struts/contrib/scaffold/src/java/org/apache/struts/scaffold/FindForwardAction.java
The idea is that you include a forward=whatever in the request, and it
trundles through the local and global forwards
Craig R. McClanahan wrote:
These tags don't belong in struts-html because they don't generate any
HTML-speicifc output -- they are perfectly usable when you are generating
WML, for example. It's fine to consider a new library for
HTML-independent output, but I'm -1 on dumping them into
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18370.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Fri, 4 Apr 2003, Ted Husted wrote:
Date: Fri, 04 Apr 2003 07:29:00 -0500
From: Ted Husted [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: logic:forward and logic:redirect
Craig R. McClanahan wrote:
These
The ValidatorLookupDispatchAction is it's own class. I DID duplicate the
code and made some changes that I felt needed to exist in the current
LoookupDispatchAction. For example, if the parameter is not in the the
request then it will default to the uspecified method. For example, assuming
submit
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18221.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I would do those things in an Action as I can't see how they're related to
the view. If they were tags they would most definitely not go in the html
taglib.
David
From: Craig R. McClanahan [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL
+1
IMHO, we are talking about View - [Protocol] - Controller layers.
We have taglibs for the View and Actions for the Controller. logic:redirect and
logic:forward are definitely an encroachment of the view on controller domain.
In an ideal world we should just take them out. Barring which
The one legitimate use for them that I can think of to have the welcome-page
of your web app forward or redirect to an action, because you can't
(portably) use an action as the welcome-page.
-Original Message-
From: Mohan Kishore [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003
But you can use a filter or code the http redirect pragma by hand. The
redirect and forward tags don't belong in our taglibs, IMO.
David
From: Jeff Robertson [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: 'Struts Developers List' [EMAIL PROTECTED]
Subject: RE:
In real life usually *do* code the redirects by hand. Reading this
discussion was the first time I'd actually thought of using them for that.
However, using the actions has one advantage. Compare:
logic:forward name=welcome /
to
jsp:forward page=/welcome.do /
These are mostly
:-D Oh, okay... so we aren't going to get ahead of ourselves? Shucks! I
thought the goal was to get everything done good enough and then move on
;-). Thanks for the tip. I will check out the needs in commons.
Brandon Goodin
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
That argument only holds as long as you're on a pre-servlet 2.3 container.
2.3 and up support filters so the tags become obsolete. I think the tags
should be deprecated soon and removed in whatever release we set out minimum
servlet version to 2.3 in.
David
From: Jeff Robertson [EMAIL
:-D Oh, okay... so we aren't going to get ahead of ourselves? Shucks! I
thought the goal was to get everything done good enough and then move on
;-). Thanks for the tip. I will check out the needs in commons.
Thanks! Any help you can give is much appreciated.
David
Ted Husted [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I've always wanted to move them to the HTML taglib, since they are tied
to the Struts controller (where the other taglibs are not). This would
put, I believe, all the Struts-dependant tags in one place.
Nope. I'd say
I queryed the bug database and I see 10 or fewer bugs for commons dbcp and
pool. I assume these are the bugs that need to be fixed. But, I have a few
questions.
1) When I queried the bug database there were several parameters that I
wasn't sure about... How do I know I am querying the database
-Original Message-
From: Martin Cooper [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003 2:11 PM
To: [EMAIL PROTECTED]
Subject: Re: logic:forward and logic:redirect
Ted Husted [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I've always wanted to move them to
Hi all!
I have development/design question. Please do not read it as a
atack of any kind. I jsut try to understand what I am missing. Beacuse
obviously I am missing something.
First an only question: why org.apache.struts.upload.FormFile is
not on the list of types suported by
Submit an *enhancement* request in bugzilla and attach a cvs diff -u format
patch file to it so we can consider it.
David
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: File upload Validator
Date: Fri, 4 Apr 2003 14:49:39 -0500 (EST)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18725.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16107.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16107.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
We need an FAQ about action chaining that lists the reasons that it is a bad
idea. Then we could point people to that page.
David
From: [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: DO NOT REPLY [Bug 16107] - Configure if you want to
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18727.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18727.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18727.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
As David said when closing this bug PLEASE POST QUESTIONS TO THE USERS
LIST
On Fri, 2003-04-04 at 17:07, [EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18727.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18727.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18727.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Jeff Robertson wrote:
In real life usually *do* code the redirects by hand. Reading this
discussion was the first time I'd actually thought of using them for
that.
However, using the actions has one advantage. Compare:
logic:forward name=welcome /
to
jsp:forward page=/welcome.do
There should be an action property here too, so that we can go directly to
the Welcome action, or whatever is appropriate for the application.
Ted,
I really think these tags violate MVC principles and the functionality they
provide should be contained in Actions. Can you explain how you view
In general, I only use them to get around the bootstrapping issue. You
can't use an ActionMapping as a Welcome page. I realize there may be
alternatives available for later specifications, but not for the one we
support today.
Another likely use might be to assert a page's preconditions and
A few comments:
1) All of the tags in the logic taglib relate to flow control. There are two
sets - conditionals and 'goto's - but they are all flow control. I find it
strange to want to claim that some flow control tags break the MVC model
while others don't.
2) If we removed these tags, we
--- Martin Cooper [EMAIL PROTECTED] wrote:
1) All of the tags in the logic taglib relate to flow control. There are two
sets - conditionals and 'goto's
Not true
- conditionals relate to layout and display (i.e. View)
- gotos send control out of the current file (i.e. Control)
2) If we
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18343.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Mohan Kishore [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
--- Martin Cooper [EMAIL PROTECTED] wrote:
1) All of the tags in the logic taglib relate to flow control. There are
two
sets - conditionals and 'goto's
Not true
- conditionals relate to layout and display (i.e. View)
A few comments:
1) All of the tags in the logic taglib relate to flow control. There are
two
sets - conditionals and 'goto's - but they are all flow control. I find it
strange to want to claim that some flow control tags break the MVC model
while others don't.
I see the usage as being something
--- Martin Cooper [EMAIL PROTECTED] wrote:
Conditionals relate to whatever the developer wants them to relate to. They
are in no way limited to layout and display. I can just as easily use a
conditional tag to control (sic) a SQL update as I can to determine whether
or not to show someone's
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18727.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
Is it a standard (at least within jakarta) to prefix the bugs with patches
available with a [PATCH]? Any ideas w.r.t creating a status called Has Patch?
I ask because there are quite a few bugs in the commons which have no
indication about available patches. I guess the commiters can finish
41 matches
Mail list logo
