Ok, I have found answer to the problem.
I can either add each value to the link parameters, or disable the
validation within the annotation:
@Validate(field="county", on="!showTab2Link"..
This didn't quite match what I needed to do, as I needed the validation for
all, so I have simply styled a submit to do the same job rather than add an
extensive list of parameters to the url.
On 9 June 2010 14:57, David Miller <dmiller2...@gmail.com> wrote:
> I have stripes:link tag in a jsp with an event attribute:
>
> <stripes:link
> href="${actionBean.context.currentStage.stripesForwardAction}"
> addSourcePage="true" event="showTab2Link">
>
> This triggers the validation to trigger on nested properties:
>
> @ValidateNestedProperties({
> @Validate(field="county", required=true, minlength=2, maxlength=2,
> mask="\\d\\d"),
> @Validate(field="parish", required=true, minlength=3, maxlength=3,
> mask="\\d\\d\\d"),
> @Validate(field="holding", required=true, minlength=4, maxlength=4,
> mask="\\d\\d\\d\\d")
> })
>
> However this would been fine if the actual values it is validation are not
> present, but they are present within the html and when debugging the bean.
> Why would the stripes:link trigger this?
> If I change it to an stripes:submit then it is fine.
>
> thanks,
>
> Dave
>
>
>
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
