I'm new on the Java scene..... fundamentally, I'm still really at the "Hello World" stage with Java. In tandem, I'm also focusing on the OO paradigm (i.e. Arthur J. Riel's Object-Oriented Design Heuristics) and "extreme programming" concepts.
POJOs in Action is about how to use POJOs and lightweight frameworks to build applications that are testable and maintainable. It weaves together several key ideas including test-driven development, object-oriented design and separation of concerns. Another important theme is that every design approach and framework has both benefits, and drawbacks and that it�s important to know when and when not to use it.
After introducing the concept of POJOs and lightweight frameworks, this book breaks the problem of designing the backend of an enterprise Java application into the following sub-problems: * How to organize the business logic � procedural design versus domain model/object-oriented design * How to encapsulate the business logic � session fa�ade versus POJO fa�ade versus exposed domain model * How to access the database � JDBC versus iBATIS versus ORM (JDO/Hibernate/EJB3) * How to handle database concurrency � optimistic locking versus pessimistic locking, serializable transactions * How to handle long term concurrency � optimistic offline locking versus pessimistic offline locking
The rest of the book then explores each of those design options and their respective benefits and drawbacks.
For example, part two of the book looks at one particular combination of design options: * Business logic organized using a domain model * Domain model persisted using Hibernate and JDO * Business encapsulated by POJO fa�ade that uses Spring for transaction management
Part three looks at different design options including: * Using a procedural design that uses iBATIS to access to access the database * Using EJB3 instead of Spring/Hibernate/JDO.
Part 4 covers the various concurrency options including optimistic locking and how to implement edit-style use cases using detached objects.
Throughout the book there is a big emphasis on testing. For example, it contains examples of how to test a domain model in isolation using mock objects and describes strategies for effectively testing a persistence layer.
I hope this gives a flavor of what the book is about.
Enterprise Java consulting and training - <a href="http://www.chrisrichardson.net" target="_blank" rel="nofollow">http://www.chrisrichardson.net</a> Author, POJOs in Action - <a href="http://www.manning.com/crichardson" target="_blank" rel="nofollow">http://www.manning.com/crichardson</a> Enterprise POJOs blog - <a href="http://chris-richardson.blog-city.com" target="_blank" rel="nofollow">http://chris-richardson.blog-city.com</a>
Joined: Jan 18, 2006
I am currently studying system development and it sounds like this book would add greatly to what we are studying. We are looking heavily at framework and portal development.
From what I can gather, this would be a great follow up to our course readings, after all the uml to code stuff!
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: To Chris Richardson : Give us some details of your book