-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thom,
Thom Burnett wrote:
> With that fixed I can take out the sub class' validate() method and still
> get a set of errors.
That's good, I guess. What do you mean, the subclass's validate method?
I didn't realize that you had multiple levels of validation being performed.
> However, getting errors still depopulate's the form's fields.
That shouldn't happen. Lemmie look at your JSP source again...
Ah. You didn't provide any of the HTML code that contains the <input>
elements. Could you post a representative sample?
> Again, I can
> fix that by overriding the validate method (calling super) and that's not a
> horrible solution
Yeah... don't do that. You should be able to work directly with the bean
that you already have. No need to go through any acrobatics like this.
Just so I know, what is the superclass for this bean and what does its
super.validate method do that you aren't doing in the subclass?
Come to think of it, why are you overriding the superclass's validate
method in the first place? And... if you are overriding it, why aren't
you calling that superclass method first thing in your overidden method
implementation?
If you have a "base form bean" that contains some utility methods, you
should not have to call super.validate(). On the other hand, if you have
a super class bean that needs its validation done /too/, then you should
do this:
public ActionErrors validate(...)
{
ActionErrors errors = super.validate(...);
// Now perform your own validation.
return errors;
}
> As near as I can see the form is being named and associated correctly but I
> must be missing something.
It looks like validate() is being called, otherwise you wouldn't be
getting error messages. Since your action mapping names the bean /and/
the input attribute is associated with the mapping (i.e. there's no
redirect), that bean (including its invalid input) ought to be available
in the session (as per your 'scope' preference).
Post your JSP code around your <input> elements and let me have a look.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFUM8a9CaO5/Lv0PARAsyxAJ9YtgRv+A4MQgUi5n4zppJVkTcFIQCfeM3n
yrmuTXI0ttkeoceXAFyr/aQ=
=wyhj
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
