POJOs in Action: Developing Enterprise Applications with Lightweight Frameworks 1st Edition

This book is a rare find. It is completely practical, teaching you what you need to know to use Spring and Hibernate (or JDO). It also gives you a background on how far Java web services have come from a much more strict and IMO bureaucratic approach.As a tech lead, I even got copies of this book for new hires that were not versed in POJO or even web development. (Or even Java in one case!)And while this book is completely practical it does the best job I have seen to give the pros and cons of each choice you can make with POJO, in a completely no-nonsense way. How refreshing! For instance, you can save objects to a database in 3 basic ways, each of which can either preserve the class hierarchy, save space, but possibly cost multiple table reads per object. It is up to you to choose what is important in your situation. Quick lists of trade-offs are all throughout this book.I'm a little late to review this book, and Spring has gone on to add many more features (for instance lots of annotations to replace XML configuration files). However, I can't rate this book more highly and I still think it would make a great first book into POJOs, Spring, or web back-end web development.

Despite the fact that it was written a few years ago, it is no less valuable today in helping developers understand how to create an application architecture using the Domain Model approach. I have been using the Exposed Domain Model architectural pattern ever since I began using the Spring framework a few years ago, although I had no idea that's what it is called until reading this book. I really appreciated how the author compared its use with the façade-driven Domain Model architectural pattern.It provides a brief introduction to the Spring Framework and Hibernate (as well as JDO), and covers at least enough material on each in order to demonstrate how to put both to use (together) in the example application that is used throughout the book. But it would be best to consult any of the numerous books and/or web resources that target those technologies specifically for more background and up-to-date implementation reference.Other than a simple Servlet example in the Exposed Domain Model chapter, the book does not cover the Presentation layer - the focus is on the Business/Model layer.Certainly the development framework landscape has changed and evolved since this book was published, but it's still a great practical resource which remains relevant in addressing important facets of application architecture that need to be considered and planned out.

the book lightly covers the use of pojo in spring, ejb, hibernate, and jdo. the coverage of each topic is like say 30-40%. you are probably better of getting spring and hibernate books to get complete picture of pojos in spring and hibernate. all in all, this book is pure waste of time and shouldn't exist at all.

The book is amazing. Even if it's like 7 years old now , the patterns still hold true. May be with the release of Java MVC as standard till that time this holds true. And the condition of the book was excellent.

This book covers the use of several lightweight frameworks for developing enterprise applications. If you have no clue at all about the issues involved in enterprise Java, I would not advise reading this yet. Despite being C#-based, Applying Domain-Driven Design and Patterns by Jimmy Nilsson would provide the gentle introduction required. On the other hand, if you've had previous experience with server side programming, and want to be brought up to speed quickly on how POJO-based frameworks can be used to replace EJB 2.x style development, this is right up your alley. If you've got used to computer books belying their dimensions with disappointingly little information, you'll be pleasantly surprised with PiA - it's packed with good content.What's nice about this book is that it goes beyond the basics of the likes of Spring that most people have read several times already (e.g. explaining what dependency injection is) and actually shows how it obviates the need to run in an EJB container and do JNDI look ups. You don't just get to read about, e.g. lazy and eager loading, the author shows you how to use Hibernate and JDO to implement those strategies. That said, this book is not a replacement for documentation or specialised references, so it doesn't get too bogged down. Particularly helpful is that the author provides pros and cons for each of the different approaches he advocates, which helps put them into perspective.The focus of the book is on using Object Relational Mapping tools, either Hibernate or JDO, in combination with Spring's dependency injection and AOP-based interceptors for transactions. There is also converage of the more procedural-based iBATIS, and using EJB3, although the author does not seem to be a big fan of the latter, despite it being an improvement on EJB2. Many of the persistence-related patterns in Martin Fowler's Patterns of Enterprise Application Architecture are covered here, including the concurrency patterns like pessimistic and optimistic locking. The author shows how to implement these patterns with the frameworks, often showing multiple ways of doing things. He's not afraid to highlight where one framework is lacking compared to another, which is refreshing.As you can perhaps tell, the coverage is predominantly devoted to the persistence layer - there's not much here on the presentation layer, although there is some material on using servlets. If you're looking for lots of detail on how to hook your domain model up to, say, Struts, or one of the many other web frameworks, you won't find much here.My only quibble with the book is that although the author pushes increased testability as a important benefit of freeing oneself from EJB containers (a good thing) and uses JUnit tests to illustrate how to develop a POJO-based application (another good thing), the tests use mock objects heavily. I hesitate to call that a bad thing, as clearly there's a whole bunch of people who are much cleverer than I using them productively, but here there's so much set up and setting of expectations, that the actual test is hard to spot, and the intention difficult to fathom. Your mileage may of course vary.If you're neither an enterprise dummy nor expect, I wholeheartedly recommend this excellent book.

Das Buch ist nicht akzeptabel: der Einband ist nicht intakt (Riss an der unteren Kante des Buchrückens)... muss man bei den ersten Seiten vorsichtig umblättern, damit das Buch nicht auseinanderfällt... dies als "gut" anzupreisen ist schon eine Frechheit... bin leider enttäuscht. Nicht zu empfehlen!