Well it took a bit of reading and a little bit of work but I have successfully gotten the iBatis Quick Start working. There was actually quite a few things I had to do to get it working. Some of them were things that were missing from the guide and others might just be me not understanding better/quicker ways to do things using iBatis.
I’ve contacted the person who wrote it to see about having my notes rolled into the actual guide. I was going to try to post my changes here but I’m having a problem posting some of it so I’ll have to do it later once I have a minute to figure out what I’m doing wrong.
With those problems aside I do have to say I’m quite impressed with how easy it was to get a list of entities returned from the system. It is definitely a much different experience then NHibernate is. Next up is to get the rest of basic CRUD functionality working.
Having written a fairly massive mapper layer for the last project I was on I decided it was time to look into this ORM thing I’ve been hearing so much about. The first thing I looked at was NHibernate and while I found that it was a really cool solution I’ve also heard it’s not the best solution when you are being required to use stored procedures. I’m not going to get into the whole stored procedures vs direct sql debate because at the end of the day some decisions are made for us. We sometimes find ourselves inheriting a big collection of stored procs we need to map from.
It was at this point that I started to hear about a product called iBatis. I’ve been told that if you have to deal with stored procedures and want a nice simple mapper that iBatis is your man. So I’ve decided to start taking a look into it. And my plan is to post information as I go along so that maybe someone else who is just starting to take a look at this product can gain from my experience.
So the first step has been to download the two seperate projects (DataAccess and DataMapper) and their respective documents. Now time to start doing some reading and playing..