On Thu, 2007-06-14 at 09:44 +0200, Jiri Mares wrote: > Hi, > > > Yeah, but what to do when the test fails then? Rewrite creation > > of dummy fields to whatever, or pull all fields for the whole > > application in page classes. > > > > Unit tests help to detect the problem then, but do not solve it > > basically ;) > > > > And I'm still interested, why the interface expects a Field, > > if only the element name is used - mostly there's some reason... ;) > > you have to encapsulate to code into one method to be able to change it > easilly, nothing more ... Sorry, but I don't understand what you want to say with this...
Cheers, Martin > > >> How are you satisfied with using Hibernate Validator? > > Two issues until now: > > - the NotNull validator is applied even if you turn off validation, > > however, all other validators are not applied. We wrote our own > > NotNull validator as a workaround - really simple > > - integration with spring is not designed if you have your own > > validators - so there's no validatorfactory or anything, so > > that you have to pull other resources like DAOs or services > > from the spring bean factory if you need them > > > > Apart from that it feels really good. > > Thanks for your opinion ... > > Jirka > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Martin Grotzke http://www.javakaffee.de/blog/
signature.asc
Description: This is a digitally signed message part
