On 10/8/07, Ted Husted wrote: >On 10/8/07, Dave Newton <[EMAIL PROTECTED]> wrote: >> Is validation firing at *all*? I had been under the >> impression that classes needed to be annotated with >> the "Validation" annotation. >> >> http://struts.apache.org/2.x/docs/validation-annotation.html > >True. > >First, @Validations() tags the class, and then the individual >annotations specify the validations as a separate statement or >statements. >
I'm confused. You say True, but then seem to imply that the class doesn't need an extra explicit annotation in addition to the annotation on the method? I've been looking at the Login class inthe mailreader-zero app and it doesn't tag the class in addition to the method. However, it almost working now and it looks like the primary problem was that something in my build chain is misbehaving -- changes to annotations are only getting picked up by every other build/deployment. Other minor issue: I was suprised that @EmailValidator doesn't appear to detect a missing email, it seems like you have to also use @RequiredStringValidator. And this indirectly caused most of my problems since I my initial automated tests for seeing how to hook up validations was only testing a missing email field. Thank you. Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
