FieldValidatorSource is heavily geared for form fields; form field validation involves potentially hooking up client-side js to the form field, displaying error messages to the user, tracking the field that generated the error, etc. If you don't have a form field, where does the request parameter come from?
If you're using tapestry 5.3, you could try using the "alerts" service + components. Check the request parameter in "onActivate" with whatever logic you need, then if there's an issue, you can display an alert to the user. Robert On Aug 26, 2011, at 8/264:05 PM , David Rees wrote: > Trying to validate a request parameter but without using a form field. > > Was going down the route of @Injecting a FieldValidatorSource and then > using that to create a validator which I can then use to validate the > parameter, but that requires me to insert a Field into the tml file > and the tml file is XML output so I can't insert a field into the > page. > > Any suggestions? > > -Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
