Thank you all for some great feedback. Especially the 2 for 1 deal from Clinton - an ORM discussion and a history lesson :)
However, I'm still in search of "answers" - maybe it's because I'm not sure what it is I'm asking for, kind of like the answer to the ultimate question ;) I have tried Hibernate, many prototypes and tests, and one live app which we have supported and extended for over 2 years. It has been an uphill struggle. Although a lot the struggle was more down to moving from a "procedural with lots of SQL" mindset to a more OO paradigm, and much of what I have learnt thru doing it with hibernate would probably be applicable to getting more out of something like ibatis. I came across ibatis ~3 months ago, no learning curve at all and we have successfully delivered one small app already. What I'm looking for I guess, is positive affirmation that ditching all the hibernate hard work (not to mention many expensive books) and going down the ibatis path is the right route. It feels right, but still, I like to hear from other people with good experiences - would be really good if you can give brief description of what the problem was you were trying to solve or what the app was delivering. Rather than a like for like matrix type comparison, real "war stories with battle scars" would make it much more meaningful. Thanks Ron Clinton Begin wrote: > > The problem with pros and cons is that they change almost on a per project > basis. > > I'd suggest just adding the above comments to the "Feedback and > experiences" > section of the wiki page. > > Cheers, > Clinton > > > On 12/18/06, Eric T. Blue <[EMAIL PROTECTED]> wrote: >> >> IMHO, I think Larry and Nathan are both partially right. I believe it's >> safe to say that discussions on the topic of persistence frameworks in >> Java >> are sometimes as intense as political or religious debates ;) >> Personally, I >> think a high-level breakdown of the differences between frameworks would >> be >> good. Even having a feature matrix that compares against some other >> frameworks would be helpful for people that are in the process of >> evaluating >> different solutions. >> >> Per Nathan's suggestion, I think it would be good to list some pros and >> cons of different approaches. And, I would be careful how one product is >> categorized as better than the other. Obviously, what's best is often >> subjective, so there should ideally be some specific benchmarks ( e.g. >> solution A's response time is faster than solution B w/ X concurrent >> users). >> >> On 12/18/06, Nathan Maves < [EMAIL PROTECTED]> wrote: >> > >> > How about a more general description of the differences and usage. >> > >> > BTW there is nothing wrong with stating reasons why our product is >> > better then others at specific tasks. >> > >> > Nathan >> > >> > On 12/18/06, Larry Meadors <[EMAIL PROTECTED]> wrote: >> > > >> > > Heh, that it would probably be considered "flame-bait'. >> > > >> > > Larry >> > > >> > > >> > > On 12/18/06, Nathan Maves < [EMAIL PROTECTED]> wrote: >> > > > These are all great success stories. Coming from someone who has >> > > never >> > > > tried Hibernate I love reading these. What are some thought about >> > > putting >> > > > together a page about IBATIS vs ORM (Hibernate)? >> > > > >> > > > Nathan >> > > > >> > > >> > >> > >> > > -- View this message in context: http://www.nabble.com/ibatis-v-hibernate-tf2830264.html#a7955710 Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
