:-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
_
EMAIL PROTECTED]
Sent: Friday, April 04, 2003 11:25 AM
To: [EMAIL PROTECTED]
Subject: RE: ValidatorLookupDispatchAction or VLDAction
>P.S. When will the 2.0 discussions start? I would love to be involved in
>them...
If you're anxious to talk about 2.0 why not volunteer some time in
P.S. When will the 2.0 discussions start? I would love to be involved in
them...
If you're anxious to talk about 2.0 why not volunteer some time in the
commons projects we're dependant on so we can finish 1.1? DBCP and Pool
still need some work.
David
__
Brandon Goodin
P.S. When will the 2.0 discussions start? I would love to be involved in
them...
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003 5:14 AM
To: Struts Developers List
Subject: Re: ValidatorLookupDispatchAction or VLDAction
The altern
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 look
On Monday, March 31, 2003, at 10:01 AM, Brandon Goodin wrote:
I'm curious why you consider it such a problem. It has solved several
issues
for me. Quite the opposite. I rarely use the base Action class :-)
LookupDispatchAction itself requires a tighter coupling between what is
in the presentatio
List
Subject: Re: ValidatorLookupDispatchAction or VLDAction
good ol' LookupDispatchAction I know folks are using it and seem to
like it, but I created it in the context of a project gone way wrong
and now that I'm on to something bigger and better I have not used it
at all, believ
I have made some needed changes and updates to the
ValidatorLookupDispatchAction (scheduled for 1.2). But, I cannot decide on
whether I should keep the name as ValidatorLookupDispatchAction (which
is a mouthful) or change it to VLDAction (tight! baby!). What do you all
think?
-1
The longer name des
good ol' LookupDispatchAction I know folks are using it and seem to
like it, but I created it in the context of a project gone way wrong
and now that I'm on to something bigger and better I have not used it
at all, believe it or not. I just want to say "my apologies" to the
Struts team for
