In my humble opinion, which is humble for good reason, learning the ins and
outs and use of reflection is one of the most important things a Java
developer can do to enhance his or her career.
Mike
At 10:49 AM 6/22/2004, Frank Zammetti wrote:
This is similar to some things we've done or thought
This is similar to some things we've done or thought about.
Well, at least that makes me think I'm on the right track :)
Personally, I'm a pretty big fan of using reflection to find methods (a la
DispatchAction) although I do think that some folks find it less appealing.
I've always been a bit con
One way I could see doing it would be do add a PrepView attribute to
the action mapping that would be in the form "class.method".
Basically, any time validation fails and your going to return to the
input page, call that method, who's job it is to prep the page for
viewing. There's of course d
I notice that as soon as someone is talking about forwarding to
another Action all these flags go up and "Chain of Responsibility"
gets said.
The flags go up just because Struts was not designed to make two
passes through the RequestProcessor with a single HttpServletRequest,
and action chainin
od of an existing Action (I
could see either being appropriate in some situations).
Frank
From: Joe Germuska <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: RE: Pulling Pun
Joe Germuska wrote:
At 10:48 PM -0400 6/21/04, Joe Hertz wrote:
Okay, whew. Knew I had seen something else about it.
http://www.jguru.com/faq/view.jsp?EID=1057613
"...There are times when one Action should forward to another, but only
to display the final result. Using a second action to complete a
At 9:28 AM -0400 6/22/04, Frank Zammetti wrote:
Interesting... I wonder if the answer would be different if you make
the distinction between forwarding to another Action and just
calling execute() of another Action. I think both have problems
certainly, but just calling execute() seems a little
is tangled up with other details of our implementation that are
more specific to how we do things and probably not the kind of thing
we want to foist on all Struts users.
Joe
-Joe
-Original Message-
From: Frank Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, June 21, 2004 10:21 PM
greater
degree of control over what is being done (i.e., no auto-population to worry
about for instance).
Frank
From: "Joe Hertz" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[E
avid Hibbs, ACS
Staff Programmer / Analyst
American National Insurance Company
> -Original Message-
> From: Mark R. Diggory [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 21, 2004 6:33 PM
> To: Struts Users Mailing List
> Subject: Pulling Punches
>
>
> Here
> Sent: Monday, June 21, 2004 10:21 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Pulling Punches
>
>
> I don't know if it's the recommended solution (I would expect
> not), but one
> option is to instantiate your own instance of Action A and
> call execute() on
cases this is quite sufficient.
Frank
From: "Joe Hertz" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>
Subject: RE: Pulling Punches
Date: Mon, 21 Jun 2004
> This is not a great solution, for all the reasons that action
> chaining is considered dangerous. After the validation fails, Struts
> would begin an entire re-execution of the RequestProcessor chain, and
> the archives have plenty of discussion on why that's unpredictable
> and worth avoidi
Joe Germuska wrote:
At 7:47 PM -0400 6/21/04, Joe Hertz wrote:
Would making a Struts Action your "input" parameter solve this?
This is not a great solution, for all the reasons that action chaining
is considered dangerous. After the validation fails, Struts would
begin an entire re-execution of
Niall Pemberton wrote:
More info on the circumstances would be helpful..
1) How Often - just for one particular Action, for all Actions or somewhere
in between?
I'm looking for a generic solution for about 6 to 10 Actions that all
work on a set of objects.
2) What kind of ActionForms are you u
ge -
From: "Mark R. Diggory" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 22, 2004 12:32 AM
Subject: Pulling Punches
> Here's an interesting one for ya.
>
> I have a struts action in which I use the &
input page.
-Original Message-
From: Mark R. Diggory [mailto:[EMAIL PROTECTED]
Sent: Monday, June 21, 2004 7:33 PM
To: Struts Users Mailing List
Subject: Pulling Punches
Here's an interesting one for ya.
I have a struts action in which I use the "input" parameter
to forward
: Struts Users Mailing List
> Subject: Pulling Punches
>
>
> Here's an interesting one for ya.
>
> I have a struts action in which I use the "input" parameter
> to forward
> back to the jsp when validation errors occur (pretty basic).
> There is an
Here's an interesting one for ya.
I have a struts action in which I use the "input" parameter to forward
back to the jsp when validation errors occur (pretty basic). There is an
instance where an object could be stale once the browser gets into my
Actions execute method, when this is encountered
19 matches
Mail list logo
