Hi, personally I totally agree with Clinton, generally speaking it should be a task of a higher level of applications, validations seems easy but it could become so complex that trying to mix it with the persistence layer could be painful; also Hibernate guys have been tried but at the end they created 2 different layers, the validation one and the persistence one.
By the way, there is a JSR specification that takes care about Bean Validation, the 303[1], and the Hibernate Validator[2] is the only one production-ready implementation that I know, and you can use it without any other hibernate dependency. Hope this helps, Simo [1] http://jcp.org/en/jsr/detail?id=303 [2] https://www.hibernate.org/412.html - see the 4.0.2.GA release http://people.apache.org/~simonetripodi/ On Wed, Feb 3, 2010 at 5:49 PM, Guy Rouillier <guyr-...@burntmail.com> wrote: > On 2/3/2010 8:36 AM, Paul Spencer wrote: > >> Ideally I would like to use a >> mode in the query parameter, like #{col2Value,nonNullValue=required}, >> that would cause iBatis to throw an exception when the property >> evaluated to null. > > If you are willing to impose a clause like that above, then just require > something similar in a comment preceding the statement in the mapper file. > Then your generic engine can look for such comments and apply the > constraints before invoking the query. Something like this: > > <!-- @NotNull=col2Value, col3Value --> > <select id="sampleQuery" parameterType="Map" resultType="Map"> > select column_1 from foo where column_2 = #{col2Value} > </select> > > -- > Guy Rouillier > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org > For additional commands, e-mail: user-java-h...@ibatis.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org For additional commands, e-mail: user-java-h...@ibatis.apache.org
