Sun Certified Enterprise Architecture for J2EE Technology Study Guide [ペーパーバック]

And considering the purpose of architect certification is to certify someone with 5+ years experience and deep understanding of design and architectural issues, then a more detailed book would be a thick painful experience. Also, a more detailed book would commit the authors to exposing more of the exam content, and devalue it as a fair measure of an architect. The fact that it requires a wide professional background with some core reading is excellent. If you struggle with the exam, enjoy the honest feedback! You have more reading to do, and experience to gain.

With sufficient experience in Java, UML, design patterns, security, general IT and web knowledge, and basic architectural principles, the book more than suffices. Basic EJB knowledge is sufficient since the book doesn't expect a programmer's knowledge of APIs and such.

If you are new to architecture, my recommendations are similar to another reviewers:
UML Distilled, Martin Fowler
Design Patterns, Gamma et al
Mastering Enterprise Java Beans, Roman, Amber, Jewell
EJB Design Patterns, Floyd Marinescu

And if you don't know enough about design patterns and UML to pass those chapters before even reading the chapters, you may be taking the exam a bit prematurely.

I will agree with one statement- the book lacks chapters on some of the objectives. But, considering that they might be considered fair prerequisites for someone qualified to take the exam, I'm not complaining. Though, in looking over my exam results, most of my wrong answers were from the sections without corresponding chapters...common architectures, legacy connectivity, messaging :(. I think my proclivity for screen-scraping did me in.

All-in-all, a masterful book and exam.

If it had taken 1000 pages to help me prepare for a 48 questions exam, then I would think that the author merely just did a 'cut and paste' from EJB specs and a few other books. Instead, this author bothered to extract the essence of the information required for SCEA and presented it to the reader.

Most of the sections - Security, I18n, Protocols, EJB, and Design Pattern are well written in an easy to understand and concise manner.

Having said all that, I wonder why some objectives are missing. Common Architecture, Legacy Connectivity and Messaging are left out completely. Also, the UML section could have covered a few more notations.

Still a good book for SCEA candidates but take note, it says "Study Guide" not "Idiot's Guide". So don't expect the book to teach you how to write the "Hello World" Bean.

I finally decide to give it 4 stars instead of 5 because of two reasons:
1. There is nothing about messaging. legacy connectivity.
2. They copied the nine sample questions from Sun's site, but gave no more explanation. What's more, in the book, the answer of question 5 is incomplete (it should be A, E, but in the book, the answer is E), and the answer of question 9 does not appear in the book (which is D).

Since it's the only one available, I suggest you buy (or borrow) this book...