This is getting further and further off-topic, but we have started talking about iBATIS 3.x as a more generic Data Mapper that would allow more than JDBC mapping and SQL query management.
While that is still a way out, that would mean that anything where you have this pattern: (Business Layer) <--> (Data Layer) <--> (Data) You would be able to use iBATIS in the data layer for JDBC, LDAP, Web service, MP3s on a file system, or some wacked-out IBM interface (why do they insist on doing that to us, anyway?). Heck, even Hibernate's HQL could be used in this way, to eliminate the StringBuffer work that you have to do with it now to build dynamic queries. All of these should be usable with iBATIS3...and theoretically in Java or .net, too. Larry On 7/22/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > No one except those of us who have no choice. :) I use a multi-valued > database, IBM's UniData, which does not [easily] speak JDBC. (The DBMS > can, > but there is a third-party app sitting on top of it that severely limits > my > options.) My only way in is through IBM's proprietary Java API, UniObjects > for Java. >
