• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Differences between iBatis implementations...

 
hernan silberman
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Clinton, Brandon & Larry. Glad to have you here! All of the "* In Action" books I've read have been great and I look forward to reading yours.

I've been learning iBatis over the past few weeks and I've noticed that the .NET and Java implementations differ in various ways. I can understand that they will be necessarily different in some ways, but some really great features--like the ability to use constructors to build objects from result sets--seem to exist in the .NET version but not yet in the Java version (v2.2). What's the plan for bringing this great feature to the Java version and for preserving parity across iBatis implementations in general?

I'm also curious how you approach this in your book--do you cover both the .NET and Java (and even the Ruby) implementations?

thnx...
Hernan
 
Clinton Begin
author
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
>> have been great and I look forward to reading yours.

Oh the pressure. ;-)

>> .NET version but not yet in the Java version (v2.2).

Yes, the Java and .NET editions naturally differ in some ways. In some cases it was due to different priorities of the users, in others it was differences in the platform itself, and in some cases it was just the choice of the development team (i.e. innovation).

We'll probably try to sync up when we do the next major version (iBATIS 3.0 -- no ETA), but even after we did something like that I'd hope and expect the frameworks to branch out and innovate independently.

Although we do value the concept being portable, we're not trying to make a cross platform ORM. I'd hate to hold back one version because we're catering to the lowest common denominator (which is now in fact Java). The Ruby version will likely start and continue to be very different from the others. iBATIS is a concept and a set of values more than it is a piece of software.

That said, some features like join mapping (N+1 selects solution) is critical to include in the .NET version, which does not yet have it. Similarly constructor injection and direct field mapping is pretty important to get in the Java version.

They'll be implemented as soon as someone makes it a priority.

>> book--do you cover both the .NET and Java (and even the Ruby)
>> implementations?

The book is Java focused. We mention .NET a lot and have an appendix to get .NETters started. There is only a slight mention of the Ruby version.

FWIW: I think iBATIS has even greater potential on the .NET platform than it does on the Java platform. So I fully expect someone to write a book on it. ;-)

Cheers,
Clinton
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic