If you want to leave your code as is, then, yes, you should just wait.
I don't think the deprecation "problem" is something you need to fix --
its just a warning that, in this case, is benign.
On 2005-03-03 23:38:50 -0500, Paul Tomsic <[EMAIL PROTECTED]> said:
hmmm, are you saying that I should
hmmm, are you saying that I should just "wait" until a
solution comes along?
Not sure I'm understanding.
How would you fix the deprecation problem in my
situation?
--- Bill Siggelkow <[EMAIL PROTECTED]> wrote:
> On 2005-03-03 21:31:43 -0500, Paul Tomsic
> <[EMAIL PROTECTED]> said:
>
> > What i
On 2005-03-03 21:31:43 -0500, Paul Tomsic <[EMAIL PROTECTED]> said:
What is the preferred way to obtain errors on a
ValidatorForm now that ActionErrors is mostly
deprecated?
Is there a better way to do this:
ActionErrors errors = myForm.validate(mapping,
request);
if(!errors
What is the preferred way to obtain errors on a
ValidatorForm now that ActionErrors is mostly
deprecated?
Is there a better way to do this:
ActionErrors errors = myForm.validate(mapping,
request);
if(!errors.isEmpty()) {
saveErrors(request, errors);
4 matches
Mail list logo
