Absolutely. The only reason that version 2.x has been so quiet lately is that I've been focused on version 3.0. Initially I didn't think a compatibility kit would be possible, but it's looking more and more like it will be. I'm nearly finished it to a point where I can make a release of an iBATIS 3.0 Alpha with 2.x compatibility. There are a few features intentionally left out of 3.0 though, including nullValue substitution, direct XML mappings and of course the existing deprecated stuff like PaginatedList etc.
That said, 2.3.3 is a really big release, and I probably should have called it 2.4. But live and learn... It's not like the mistake hasn't been made before (Windows 3.1 ... ;-) iBATIS has been around for 6 years, and we're the only framework of our kind. So we're not going anywhere. http://www.javaworld.com/javaworld/jw-07-2008/jw-07-orm-comparison.html Cheers, Clinton On Thu, Jul 17, 2008 at 7:47 AM, Ian Zabel <[EMAIL PROTECTED]> wrote: > As a new user to iBatis (we just began using it two weeks ago at my > company!), I just want to give you guys a big thanks for your work on > the framework. It's made it a lot more comfortable to know that iBatis > is under active development, and has a lively community around it. > > Keep up the good work! > > Ian. > > On Thu, Jul 17, 2008 at 9:40 AM, Clinton Begin <[EMAIL PROTECTED]> > wrote: > > > > No. The Spring integration is using internals of iBATIS which are not > meant to be publicly consumed. We're not going to stop evolving our code > just to keep compatible with 3rd party frameworks that reach into the guts > of iBATIS. Waiting for 2.4 would just delay the inevitable. > > > > The solutions is: > > > > * Update the Spring plug-in, and > > * Use 2.3.0 until it is updated. > > > > This doesn't happen every day. In fact it's the first time it's happened > in 4 years. Let's not make it out to be more of an issue than it is. > Spring will be updated and all will be well. > > > > Clinton >
