Hi Mike, > One of the ugly parts is determining whether the validation > annotations go directly on model objects or on intermediate business > logic classes (which for some people might be Stripes actions of > course) is sometimes a head-scratcher. Really it's the "required" > property that causes the most problems, but there are other issues as > well.
Indeed, these are the kinds of issues that cause me some head-scratching when I'm thinking about the integration of bean validation. > I haven't looked at the Hibernate thing much (we don't use Hibernate), > but it seems like something that could mine that information and > present the Stripes validation code with the metadata it expects would > be useful. I said Hibernate Validator, but really it is not Hibernate-specific anymore; it's become the JSR 303[1]: Bean Validation of which it is the reference implementation. Sorry to cause some confusion there. A while back I had looked at oVal[2], which remains interesting but is not as well known as the "standard" JSR and the big name Hibernate. Then again, Stripes suffers from the same kind of discrimination vs. say JSF. But, I digress... [1]: http://jcp.org/en/jsr/detail?id=303 [2]: http://oval.sourceforge.net Cheers, Freddy http://www.stripesbook.com ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
