On Sat, Aug 27, 2011 at 9:14 AM, Robert Zeigler <robert.zeig...@roxanemy.com> wrote: > 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?
It's a REST style API use for data services. > 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. Unfortunately, I'm not using T5.3 yet. What I've done in the mean time is embed a form into a block which is never rendered. A bit of a hack but works well for now. :-) -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
