al Message-
From: Ray Madigan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 5:39 PM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: Problem with Formbean validate method forwarding to input pag e
Why don't you tell your action not to validate, and call validate yourse
fault form validation to false in a
config file?
-Original Message-
From: Todd Bryant [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 08, 2004 8:34 AM
To: 'Struts Users Mailing List'
Subject: RE: Problem with Formbean validate method forwarding to input pag e
Excellent idea Ray. I
ECTED]
Sent: Wednesday, April 07, 2004 5:39 PM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: Problem with Formbean validate method forwarding to input pag e
Why don't you tell your action not to validate, and call validate yourself
in your action. Seems like you will have
t: Re: Problem with Formbean validate method forwarding to input
pag e
The form bean is populated by the RequestProcessor, but you can put your
logic to validate the session where ever you want. The easiest way to
understand it is to just look at the source cod
The form bean is populated by the RequestProcessor, but you can put your
logic to validate the session where ever you want. The easiest way to
understand it is to just look at the source code for
org.apache.struts.action.RequestProcessor. It has a number of
processXXX methods, one being proce
Interesting. I have never looked at the request processor before. The main
question I have is - is the formbean populated BEFORE the request processor
runs or after? If the form bean is populated before the method you mention,
then the request process will still be circumvented by the formbean.
-
Todd,
You should use a Filter for authentication. That way,
you can remove all of the logic from your actions and
JSP's and handle it in one central place. It is also a
good practice to put all of your JSP's under WEB-INF
so they can't be accessed directly and to use actions
to forward to your JSPs
That is a good suggestion, and I had thought of that, but the problem is
that a user would have to go from the error page back to the page they were
on. This would make it prohibitively difficult to interact with this
particular app (too many clicks).
-Original Message-
From: Paul Barry [
That is a good question. The problem is the way struts processes requests.
The first thing struts does when receiving a request to an action is to fill
in the formbean associated with the action. Then it runs the validate()
method of the formbean. If the method returns a non-empty ActionErrors
obje
9 matches
Mail list logo
