tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty" <>
Subject Re: [OT] Usage of Ibatis in production
Date Sat, 29 Jul 2006 19:44:11 GMT
Does it have some capability to export to JNDI?
Martin --
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

----- Original Message ----- 
From: "Larry Meadors" <>
To: "Tomcat Users List" <>
Sent: Saturday, July 29, 2006 11:27 AM
Subject: Re: [OT] Usage of Ibatis in production

>I almost agree, but one point of clarification: iBATIS is not ORM,
> which is a way to map tables and views to Java beans.
> iBATIS is SQL mapping, and there are a few key differences. First and
> foremost is that you can map from anything to anything.
> Not just tables and views to beans, but also queries or stored
> procedures to beans or Maps or even XML - one way to look at iBATIS is
> just as JDBC made simple. No more connection /statement/resultset
> resource management, no more indexed parameter mapping, no more
> StringBuilder SQL statement builders. Just simple (or complex) SQL
> mapped to java objects.
> For some interesting reading on why I use tools like iBATIS instead of
> ORM tools, here are some articles on the topic...
> Larry
> On 7/29/06, Tomi NA <> wrote:
>> On 7/29/06, Phil (waex) <> wrote:
>> > Hi,
>> > Sorry for if this question is slightly off topic, I'm revisiting my work
>> > practices at the moment and I'm considering the usage of various frameworks
>> > to replace hand coding.
>> > I was wondering if any of the users in the list use Ibatis in production /
>> > commercial systems for data persistence to RDB, or if someone have some
>> > dreadful stories prevent me from looking further into it. It looks to me
>> > that it is quite easy to use and the learning curve is not as steep as
>> > Hibernate for instance.
>> Use whatever ORM technology you like - iBatis, Hibernate, Cayenne -
>> just don't fall back to writing volumes of mixed Java or JSP and SQL
>> code.
>> You'll always be able to handcode (e.g. in stored procedures) a couple
>> of critical points of your application, but for most applications,
>> you'll be jumping for joy working with clean OO code, leaving all the
>> gory details (sql injection, statement construction etc.) to the ORM
>> framework.
>> Cheers,
>> t.n.a.
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail:
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To start a new topic, e-mail:
> To unsubscribe, e-mail:
> For additional commands, e-mail:
View raw message