Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <struts-user@jakarta.apache.org>
Content-return: allowed
Date: Fri, 24 Jan 2003 15:49:35 -0700
From: Wendy Smoak <Wendy.Smoak@asu.edu>
Subject: RE: Validator validates too early (was RE: Validator won't valida	te
 single required field)
To: 'Struts Users Mailing List' <struts-user@jakarta.apache.org>
Message-id: <A7AF1AE70A8C124593A1AC831EFE46FE0EEF6D@ex3.asurite.ad.asu.edu>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_kJE9+03VeEEPP/Kx8Qqhpw)"

--Boundary_(ID_kJE9+03VeEEPP/Kx8Qqhpw)
Content-type: text/plain;	charset="iso-8859-1"

David wrote:
> The naming convention in the example app wasn't intuitive for me so I 
> usually do:
> GetAccountFormAction maps to getAccountForm.do
> SaveAccountFormAction maps to saveAccountForm.do
> There's no "right" way, just the way that makes sense for you.

I had a walk in the Big Blue Room and realized I was making this way too
hard.  I don't need to place a token in the session to tell me that this
isn't the first time the form has been displayed.  There already *is* a
token, in the request, commonly known as the Submit button!

So now I have this:
public final class ChooseProfileForm extends ValidatorForm implements
Serializable
{
       public ActionErrors validate(ActionMapping mapping,
                                 HttpServletRequest request) {
      /*only validate if the form has actually been submitted.
      We can tell this by checking to see if the Submit
      button is in the request
      */
      
      if (request.getParameter("Submit") != null) {
         return super.validate( mapping, request );
      } else {
        return null;
      }
    }
}

And all is well again in my world. :)

-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University PA Information Resources Management

--Boundary_(ID_kJE9+03VeEEPP/Kx8Qqhpw)--