You can take a look at the details of how to handle cross-component validation by reading the source code for the Tomahawk sandbox t:compareToValidator validator.
However, this is probably a case where it makes more sense to perform your business validation in the action. On 4/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi, In a login page I have 3 components: Login Password Domain I have a validator for Login & Password I should like in Validator of password to "knows" the value of the Domain. The value of the domain is not set when I validate the password. Do I have somethink special to do for defining the setting order? How to perform a "cross component validation"? Thanks a lot. Stephane
