Book: "Enterprise JavaBeans 3.1"
Language : English
Paperback: 766 pages
Release Date : September 24, 2010
Andrew Lee Rubinger (@ALRubinger) is an advocate for and speaker on testable enterprise Java development and a member of the JBoss Application Server development team. Beside that he is the technical lead of the ShrinkWrap project. Working for JBoss / Red Hat. He is running his blog at exitcondition.alrubinger.com
The technical manuscript was adapted from Bill Burke and Richard Monson-Haefel’s fifth edition of this book.
Some statistics front-up. With 766 pages this clearly is a visible book in your book-shelf. If you would remove the preface, index and the code examples you end up with 408 pages of content and 318 pages of examples . This is obviously wrong. Due to many reasons (Environment, cost of the book, my back ...).
But let's start with the overview: The book is organized in five parts. Parts 1 through 4 make up the so-called technical manuscript. Part 5 contains the examples and a detailed guide on installing, configuring and running the examples. Nobody is wondering about the fact that this is done using Arquillian and ShrinkWrap :) All examples run on OpenEJB.
Part 1 starts with a bird’s-eye view of the technology introducing your to component types and container services and leads you to write your first ever EJB.
Part 2 draws you deeper into the different component models (stateless-, statefull-, singleton- and message driven beans.
Part 3 is all about persistence with JPA. What that is, how to configure and package and simply how to use it.
Part 4 examines the different container services like Security, Injection, Transaction, Interceptors, Timer Services and Web Services.
Writing and Style
Entertaining. That is the right word. If you are used to technical documentation you shouldn't struggle with this book. For a non native speaker it reads very easy and I didn't find very many complex sentences which stopped my reading. For native speaker it might be more likely to identify the different writing styles in it. The extensive examples doesn't make any sense to me. It feels like ages ago when I was used to typewriting stuff from books.
Conclusion and recommendation
Hard to judge on this one. Beside the fact that I have a personal history with this book, I still believe that is helpful to people which want to get a good and basic introduction to the EJB programming model. The clear separation from any appserver makes this only half as valuable than it could be. And this is the surprising bottom line. I still would prefer any vendor specific book over a plain technology focused one. Anyway, congratulations to Andrew for doing a good job in taking over such a piece of history and making it up to date. And thanks to O'Reilly for keeping traditions alive.