I'm sorry. My bad. I guess I didn't read your post too carefully. AFAIK translator by design runs first so that your validator can check on the intended value. For instance, if you're collecting a String which is a number translator will do its work and give you number so that you can further check on it with the validator. If a translator for some reason cannot translate because a value doesn't make sense, then it will behave as if it were a validator.
So I'd validate on an already translated value, not the original. On 3/6/06, Andreas Bulling <[EMAIL PROTECTED]> wrote: > Hi Adam, > > thanks for your answer, but I don't understand how this is related > to my problem?! I'm already using a custom ValidationDelegate > and I've also set up both the translator and the validator > in my hivemodule.xml file (I verified that they get called/used when > submitting the form). > > My problem is the order of execution not that I don't know how > to use a custom delegate/translator/validator ;) > > Sincerly and thanks again anyway, > Andreas > > On 06. Mär 2006 - 10:28:28, Adam Zimowski wrote: > | In your page class you can populate delegate object with your custom > | validations. For instance, if you add the following to you page class: > | > | @Bean > | public abstract ValidationDelegate getDelegate(); > | > | you then can add errors to this delegate in your listener (onSubmit or > | whatever). I suggest first to check javadoc on ValidationDelegate > | object, play with it a little and you're gonna strik a home run :-) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
