> > Have I overlooked something? Is there some other way to accomplish > this? With the current implementation it seems like my only real > option is to use:
Have you thought about creating a custom errors component that does a better job at displaying equal error-messages for different components?That way you keep Tapestry validation intact, the labels and fields still get a t-error style assigned to them and you have control over what errors get displayed. I personally prefer putting the error-messages directly after the field that is in error. Especially if you have a lot of fields in your form. Check out the demo-page for the jQuery validation plugin to see an example of this type of cross-field password validation: http://jquery.bassistance.de/validate/demo/ I have disabled client validation in Tapestry as well, since it mostly gets in my way. I'm planning to use the jQuery validation plugin instead and I have adopted the same style of reporting server-side validation errors already by implementing a custom ValidationDecorator in Tapestry. See http://piraya-blog.blogspot.com/2009/06/creating-custom-validationdecorator-for.html . regards, Onno
