Pro Spring

What is Spring? How good is "Pro Spring"? I will attempt to answer these questions based on my experiences with both. Spring is a light-weight container and framework for building java applications, both J2SE and J2EE. 1. This means that, unlike other web frameworks, like struts, spring is not only limited to web applications. 2. "light-weight" does not mean that it is a tiny framework; rather it means that it is not an intrusive framework like EJB. To support these claims, we can say that spring provides container and/or framework features for 1. Presentation Layer: Spring MVC, Spring Web flow, support for struts(and various other MVC frameworks) 2. Business Logic Layer: Transaction Management, Remoting, J2EE support(support for JMS, EJB, Mail etc), Job Scheduling support 3. Data Access Layer: JDBC support, ORM Support(Hibernate, JDO, iBatis etc), Database Exception Translation etc. 4. Common Features for all layers: Inversion of Control, Aspect Oriented Programming, Bean Factory, Application Context By providing the above features (and more) in a light-weight fashion, spring introduces the following traits into your application 1. Ease of development 2. Non-Intrusive Source code 3. Good Design Patterns and Practices 4. Testable Design and Code... and much more Both the above lists are by no means exhaustive, but is a good starting point on how you look at spring. "Pro Spring" does a very good job of explaining all these features in very organized and easy to understand fashion. The best thing that I liked about this book was that, it was able to portray the bigger picture accurately and then zoom-in on individual items in a very orderly fashion. This helped me understand the individual parts of this extensive framework in the context of the bigger picture. BTW, version 1.2 of spring is covered in this book. Now the "not-so-good" news: This book has 2 authors, Rob Harrop and Jan Machacek. They are both highly skilled spring developers, but I am afraid, one among them is not so great writer. I found that the chapters written by Rob Harrop were extremely clear. The chapters written by Jan Machacek were not very easy to read at least during my first pass. The silver lining here is that, the fundamentals of spring are written by Rob Harrop, which puts us in a better position to read Jan Machacek's work. Also, during my second and third passes, I was able to get a better value out of Jan Machacek's work, which means that we don't need to worry about this con if you are fine with reading a few chapters twice or thrice. Overall, "Pro Spring" truly makes you a Spring Pro. I highly recommend this book, if you are seriously interested in learning and using spring.

The depth of this book is matched only by it's heft. For a book this big you would expect something with a ton of screenshots and page after page of code, but such is not the case. In fact, this book has better exposition than a lot of APress book's I've read. The authors do a very good job at not only explaining the technology but in providing some perspective on it's use as well. Between this book and Manning's "Spring Into Action" I would take this book.

Pro Spring is a big, thick book that covers a big, thick topic--not thick as in obtuse, nor even dense and hard to comprehend, but thick as in many layers piled atop each other. Spring comprises many layers of technology that solve different problems, but work together under the Spring moniker. When I cracked this book, I knew nothing about Spring except that it was an IoC container. I knew enough about IoC to recognize its power, so the hype swirling about Spring led me to Pro Spring. Both the concepts behind and the practice of using the various technologies wrapped into Spring unfold gradually through the pages of this book. At times, I felt they unfolded too slowly; I felt impatient as I absorbed, bite by bite, the behemoth of Spring. The authors don't skimp, however, when they cover a topic, but take the time and pages to explain a concept, then illustrate it through code and configuration. Proper understanding of Spring defies a mad dash through its usage, as I quickly learned. Still, I felt somewhat betrayed when I didn't learn about ApplicationContext until page 141. This likely reflects a matter of taste: I think I'd prefer a presentation of the big picture, then a breakdown of its constituent parts, rather than a presentation of the pieces, building up to a whole. Although I felt a little impatient as I read, I'm astounded by how well this book covers each topic. I found myself thinking, "Well, I may not get this all in the first pass, but I'll dive into this book again and again as I tackle new facets of Spring." That, perhaps, is the strength of this book, and they way it can best be used: skim through it to get a handle on what Spring is and what it can do, and then zero in on those sections that interest you at a particular moment. The explanations and examples are fully fleshed out without becoming belabored, and I will continue to lean on this book as I learn to implement all the technologies in Spring. Well done, and well worth the investment.

If you're reading this, you probably don't need to be convinced about learning Spring. The question you're really asking yourself is, which book should I buy? Or should I just stick with the online docs and save some money? Or should I just download the code and start playing with it? I'm going to try to answer those questions. First, Spring was born out of the thinking by Rod Johnson in "Expert One-on-One J2EE Design and Development", and later with this followup book co-authored with Juergen Hoeller in "Expert One-on-One J2EE Development without EJB". These books are excellent books in general and I highly recommend them. However, the first book is not really about Spring and is more about general enterprise application development strategies (and very good at that). The second is sort a essay on why EJB has failed, and also a short introduction to Spring along with the philosophy behind the design decision in Spring. However, it's too sparse to be a full-fledged Spring manual or tutorial. It's more a well-argued anti-EJB book with a short tour guide to Spring. In contrast, Rob Harrop (who is also a Spring developer) has written the first truly comprehensive introduction and tutorial to Spring. It covers the whole gamut, from a clear introduction to why Dependency Injection makes a lot of sense, on Aspect Oriented Programming and how it applies to Spring, then on to a detailed coverage of how to use Spring for persistence, transactions, remoting, messaging, scheduling, email, and MVC web applications. He shows how to integrate with Hibernate, iBATIS, JDBC, JTA, JMS, Quarts, Struts, Velocity, etc. What's amazing is that it covers Spring 1.2, which is still in release candidate stage, and gives you updates on the current stage of various supporting software, what to watch for in the near future and what the changes will most likely be. Just as one example, the Spring IDE plugin to Eclipse has really no online documentation to speak of since it's still relatively new, but this book shows you how to get it, install it, use it. The book has better documentation than the canonical website. That's just one example of many. So how does this compare with the online docs for Spring? The online docs are good in most places, but there are still some big gaps in the documentation, whereas this book is nothing but exhaustive in its coverage and clearly superior in most places compared to the online-docs. I've read both of Rod Johnson's books, the online docs and Rob Harrop's book, and this book is probably the best out there right now for its coverage of Spring, and it's also a one-stop shop. You don't really need anything else, unless you're looking to expand your knowledge with the other books into areas outside of Spring. The only other book that might come close is the (as yet) unpublished book by Rod Johnson titled "Professional Java Development with the Spring Framework". However, that book is not out yet, so unless you can stal

When I cracked open the first book dedicated solely to the Spring framework, I expected a rush job. After all, the book covers Spring 1.2, which hasn't been out there all that long. I was pleasantly surprised. It's tough for a book this fat to be this timely. But it is. Let me start with what I liked the most about the book. - The authors start with examples that don't use dependency injection at all. They refactor those exmaples, so you can see the value of the core design pattern supported by Spring. This, in my view, was nicely done. It's critical. - The authors treat each topic completely before moving on to the next. For example, for the base container, they walk through the edge cases, like method injection and introduction, and explain the core problem that they solve. As early contributors of Spring, the authors were well positioned to do this. - The example is simple. I think that there's been too much of a movement to building real business applications in books. These treatments quickly bog down into details, and distract from the topics that they're trying to cover. - The sense of humor is there, and it's not overdone. I like having the obscenity filters as an AOP example. (I just wish that the book found some way to include a logging example...or not.) - The book is comprehensive. It covers the core subjects of DI, AOP, persistence, messaging and remoting, but also some edge scenarios like mail, scheduling, and the like. It's tough to find a down side, but if I had to pick, I'd say that the language bogs down at some points. This, in my opinion, falls on the editors, and not the authors. I do think that the order of the topics was a bit strange, like introducing AOP before establishing a need. But I'm picking here. This book is very well done, and I'm glad I got it. I would definitely buy it again.