On Sun, Feb 7, 2010 at 4:48 PM, Guy Rouillier <guyr-...@burntmail.com>wrote:
> I don't know if what you are trying to do is possible, but it seems to > defeat the intent of iBATIS (remove all the routine JDBC code and replace it > with declarations, so your Java code becomes much simpler.) > > Simpler Java code is nice, but there are lots of ways to simplify it. Moving SQL to XML is better than using string concatenation in Java but not as good as an internal DSL for building queries. Having everything in Java yields superior capabilities such as compile-time checks, refactorings, etc. > If you are going to add lots of Java code to build the mappings, you might > as well just go back to using straight JDBC. > > But... then I won't have SQL to Object mapping anymore... iBATIS is about SQL Mapping - it should not force any particular approach to using that core service. -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:da...@6degrees.com
