Hi Mike,
So are you saying that after Stripes performs its validation, you want to
interrogate (from within the ActionBean) to see what validation errors (if
any) occurred?
If so, then you can have a method which is annotated with @After(
LifecycleStage.CustomValidation ). In that method, you can call
getContext().getValidationErrors() and loop through each error (which will
have the field inside of it if it is a field-level error).
Is that what you are wanting?
Thanks.
-- Rick
On Mon, Jul 17, 2017 at 5:50 PM, Mike McNally <emmecin...@gmail.com> wrote:
> First, still on Stripes 5.something.
>
> In actions with List<Foo> arguments, it seems that validation errors are
> produced (as far as I can tell) such that it's not possible to determine
> which of the parameter values in the list (that is, which of the HTTP
> parameters matching the list name) was the one with the problem, or whether
> multiple inputs had problems, etc.
>
> Is there something I'm missing, or is that just something that Stripes
> just sort of doesn't do?
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Stripes-users mailing list
> Stripes-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
