Hi Elias,

Showing my ignorance of iBatis here, but I thought that iBatis was a very thin wrapper around SQL.

So if you support multiple databases, don't you need different SQL for each one?

Is this an extended iBatis you are using or has iBatis changed in ways that I didn't know about?

Thanks,

Craig

On Jan 29, 2007, at 3:43 PM, Elias Torres wrote:

Hi Everyone,

I know I have been away for over a month now but I still wanted to let
you know what we have been up to at IBM in regards to the Roller
project. First, we have some great news around the use of Roller at
IBM. Lotus announced Connections, a social networking package for the
enterprise that includes Roller as its blogging component.

...
I guess the main discussion point I would like to start from this
email is which data access strategy we should use in Roller.  We have
an iBatis (Apache License) implementation that is working well and
continually being optimized. So far the results are very promising and
would like to donate that back. I just want to know if using iBatis
can still be a choice in the decision and what would need to do to
make sure it happens.

Regards,

-Elias

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to