 |
|
Title: Enterprise JavaBeans, Fourth Edition
ISBN: 059600530X
Author:
Richard Monson-Haefel
Bill Burke
Sacha Labourey
Publicate Date: 2004-06
Publish: 2004-06
List Price: $44.95
Average Customer Rating: 4.5
Format: Paperback
 |
|
|
|
|
Amazon Lowest New Price: $3.33
Amazon Lowest Used Price: $0.84
Amazon Merchant Price: $40.45
|
|
|
|
|
|
|
|
|
|
|
| Customer Review: |
|
1: Good reference book .. Not for learning the basics
I started reading this book with a basic understanding of EJB 3.0. But the book does not keep you interested in the topic. I found the reference manual more interesting. I use this as a reference book.
|
2: Everything EJB
This book covers almost everything related to EJBs in their new reincarnation. Its author have rightfully chosen to scrap any information concerning EJB 2.1. This is the right path to take as the new 3.X standard is so radically different (read much more useful) from the earlier versions.
The book starts out with a fairly detailed introduction to JPA 1.0 persistence mappings, entity relations and inheritance. It then moves on to covering session beans, interceptors, JAX-WS/RPC, the JNDI ENC and JTA.
This is a massive amount of stuff and still the author manages to convey its primary use, pitfalls and corner cases in an engaging technical style. So from a topical point of view you get what you pay for (and then some). The book is however not without some problems. First of all it contains some annoying errors, like:
1) In the interceptor chapter, the author fails to inform you that EJB interceptors are only used on direct invocations. That is if you put a interceptor on EJB A and inject it into EJB B, then delegated method invocations on EJB A from B are not intercepted. This is annoying at best, and at worst it could be considered an enormous flaw in the EJB spec.
2) Some JPA information is just plain wrong (like the use of named parameters in native queries). Most of these errors can be traced back to the fact that the author uses Hibernate which indeed supports this non-standard functionality. While understandable, it does confuse you some when confronted with strange errors in other containers
Many other errors exists and this book badly needs a review from some of the other EJB/JPA spec members, preferably someone not involved with the JBoss container. Another and more grave problem is the fact that the book presents most technologies as separate entities, and thereby you fail to see the complete picture. I really miss a complete real life EJB applications including:
1) Security (propagation of client role to the server (i.e. getCallerPrincipal)).
2) Interceptors (for logging and security).
3) Use of EJBs from a web application.
4) Testing of EJBs (best practices for easy unit testing).
5) Packaging and compiling (these days you cannot write a JEE book without a complete Maven sample)
This might sound like allot of grief, but I still choose to give the book four stars from the simple fact that it is complete, contains allot of useful samples (like the .NET SOAP application client) and manages to make many hard topics easy to understand.
In general a well written and useful book with a heap of information, written in a pragmatic style without to much fluff.
|
3: Great EJB3 Book! You will be greatly pleased with your purchase.
This is a great introduction to EJBs in general, and now EJB3. (the JSR 220 standard) Just like EJBs are now easier to develop with version 3, so is it easy to read and study this book. I hold O'Reilly in a high regard, (doesn't mean I'm a fan boy though, they do have their share of bad apples) and their high standards show in the quality of writing in this book. You will be happy with your purchase.
|
4: Good but outdated
To be brief, this is a great book, but you will almost certainly want the newest edition of it.
|
5: Is Good but Quality down in the code
I recommend this book. The book cover almost topics in EJB 3.0 and you can depend it for preparing the SCBCD 5. The author explain and describe the topics in easy way.
The problem of this book have more error in code I escalation it for author. cause the book have his name not auditor name.
I will give this book three stars for losing the quality.
|
|
|
|
|
