iBatis in Action First Edition

I really like iBatis, and am grateful to Begin for writing it. I've used it for several years, and recommend it. But I hate this book.The author quotes himself as having said that iBatis would be a failure if there had to be a book written about it. The problem is, although he changed his mind about writing the book, he never changed his mind about there being no need for a book.The implicit narrative thread running throughout this book is, "iBatis is so simple, so self-evident, you don't need a book", and so, instead of writing a tutorial/reference book, he has written a pastiche of anecdotes about how to implement his sample project.Here's the problem: instead of breaking out a section, for example, on how to handle stored procedures that would start with an overview, then go through get object, get list, update, insert, execute, how to deal with custom data types, how to get your result as a return from the procedure call as opposed to putting it into an OUT or INOUT parameter; instead of doing that, along the way to other things, he shows an embedded example of how to use a stored proc in a particular case.I can see that the major problem he had to solve in writing this book was how he was going to manage to fill enough pages for it to be a book rather than an article. He rambles on, talking *about* topics rather than *in* topics, skimming along, rather than digging in.I recommend the book simply because it's the only one out there, but I think you'll find that it's fine if all you want to do is learn *about* iBatis, but that if you have specific questions on how to implement certain things, or solve very real problems, you'll wind up frustrated and disappointed.

As Authors mentioned and I totally agree, IBATIS is relatively small framework that does what it says it does very well, I have used it before and the only reason I bought this book was to have a reference guide. and it does exactly that very very well, IBATIS is not complicated concept it does not need 800 pages, this book is something One can look over and over again for techniques and ways to use for example dynamic SQL appenders etcno more digging through Google or through, not so clear, official IBATIS reference guide.

I found it easier to make things running using free manuals available from same authors. Something is wrong with the way information presented. Didn't feel bad about buying the book just because I paid $5 for new book at amazon

claro y conciso..con ejemplos puntuales ,, este libro se deja entender a pesar de estar en ingles y de que mi nivel en java no es tan alto.

Very well written and introduces reader to the concept of sql mapping and iBatis DAO. Clear explanations and simple to the point language makes it a enjoyable learning resource.Highly recommended. Also see developer-guide and tutorial from Ibatis site directly for additional references.A second edition covering Ibator and new features would be nice.

Having suffered through Hibernate and also done pure JDBC projects before, I became ecstatic upon reading the iBATIS Developer's Guide (pdf) freely available on the iBATIS web site. From there, I decided to read the iBATIS book to get more in depth knowledge.PROS====+ Gives you the philosophy and background about the technology about how iBATIS came about. If you are trying to pitch this technology to your team you'll find nearly every positive/negative angle has been covered. There can be much pain caused by choosing the wrong approach at this layer, and sometimes people may not be aware of the pain they cause. Some may even be unaware that there are better alternatives such as iBATIS.+ Broad in its coverage. Touches on how to use iBATIS in several common environments. Gives background on transactions and isolation choices. Introduces the DAO pattern to those unfamiliar with it. So this book is much more than about iBATIS thankfully.+ Covers advance topics such as how to write your own cache or transactional manager. Ideally you shouldn't but the information is there if need be.CONS=====> Organization problems. For example, when you are first learning about the 'select' tag, you are just shown the basics (and I mean really basic) along with the basics for delete, update, and insert. A few chapters later you get to learn the advanced stuff. I'd prefer a chapter just on 'select' and Result Maps including some examples of a object graph (complex objects). Then another chapter on inserts and parameterMaps... You get the idea. This would greatly help in learning process in my opinion.=> The book does need a second edition to cover some of the changes done to iBATIS 2. But don't look for that anytime soon as iBATIS 3 is in beta and I think all their energy will go to that en devour.=> Not enough coverage on iBATIS with Spring. I think the popularity of Spring warrants a full example of integrating iBATIS with Spring.FINAL THOUGHTS==============iBATIS reminds me of technology crafted by those who learned from all the wrong ways of doing things to come together with a well-though out technology that puts the pleasure back into the persistence/DOA layer. Rarely are books written by the authors of the technology written in a clear manner -- but this book is an exception as I enjoy these author's clarity. Yes, and I agree with other reviewers that there should be more examples in this book. However despite my minor complaints, this book (and iBATIS) has been very helpful to me. I recommend the book for those using iBATIS 2. If you are going with iBATIS 3, this book may not be of much value other than for the philosophy sections. In that case, you might as well read those first 1-2 chapters in the book store and save yourself some money.

Since this is the only book available on Ibatis, so i purchased it.But the latest version of ibatis has a lot of changes and this book is based on the older version.I got a lot of information on ibatis online.Download ibatis and go through the docs( there is Ibatis_SqlMap.pdf ) and same some money ;)