Rating: 
Summary: Mundane and Dry - Not for Me
Review: I have read dry and flat technical books before, but this one stands out as being unusually so. There is no passion for the subject here and it is the kind of book that does not make an impact. What really makes for a good architecture is not something that is really discussed and things that require further explanation often seem nipped in the bud. You are not going to get a feel for the nuances of J2EE architecture with this book, and I think it is when you understand those, your retention and grasp go up a great deal. Only then can you weigh options and consider the alternatives intelligently. Sorry guys, I think you needed a bit more time to organize and explain the material more fully. I also think the consistent, machine like quality of the prose detaches the reader rather than pull them in. Some may get what they want from this book, but it was not a book I enjoyed nor one that gave me much insight. Many facts are here and stated, but the pie was not finished when it was pulled from the oven.
Rating:
Summary: Mundane and Dry - Not for Me
Review: I have read dry and flat technical books before, but this one stands out as being unusually so. There is no passion for the subject here and it is the kind of book that does not make an impact. What really makes for a good architecture is not something that is really discussed and things that require further explanation often seem nipped in the bud. You are not going to get a feel for the nuances of J2EE architecture with this book, and I think it is when you understand those, your retention and grasp go up a great deal. Only then can you weigh options and consider the alternatives intelligently. Sorry guys, I think you needed a bit more time to organize and explain the material more fully. I also think the consistent, machine like quality of the prose detaches the reader rather than pull them in. Some may get what they want from this book, but it was not a book I enjoyed nor one that gave me much insight. Many facts are here and stated, but the pie was not finished when it was pulled from the oven.
Rating: 
Summary: Do not expect to pass SCEA by reading this book
Review: I just passed SCEA part I with score 81. I used this book to prepare my exam. I agree with other reviewers, this is a poorly written book. A lot questions from the book are duplicated and have wrong answers. But I do think the mock exam is a bit of helpful. It is close to the real exam, but the real exam has much more scenario questions. It will help you control time and familar with the testing environment. The bottom line is that you can not depend on this book to pass the exam. Here are some suggested materials:Enterprise JavaBeans (3rd Edition) and Java Message Service by Richard Monson-Haefel,SCEA yahoo group.
Good luck!
Rating:
Summary: Good time waste
Review: I purchased this book last month. In one month, I am able to read only two chapters of this book. This book is not organized properly. It has more than 500 pages of boring essays. This certification is for java developers not law makers. Chapters has been made big by repeating the same lines but in different ways. After reading the whole chapter, I always felt like I have read two - three lines of info. It should be technically organized for example more diagrams, making list of technical points, using bullets.
Rating:
Summary: Badly written and unclear
Review: I would not advise buying this book for studying for the SCEA exam. It is very badly written and not clear at all. Much of the material is repeated and long-winded. It contains some of the most useless diagrams I've seen in a long time. I would recommend the Mark Cade book and some of the notes and files that are available from other people who sat the exam. (mainly from the Yahoo groups and JavaRanch). The good points of the book are that there are plenty of practice questions and a sample exam.
Rating: 
Summary: Very Weak on Part II
Review: I've already passed the SCEA part I and was working on part II when this came out. I got it hoping to get some good insight but was very disappointed. I assume the part I coverage is better from briefly looking it over, but wasn't wowed by that either.
Rating: 
Summary: Much more than a certification guide
Review: More is better and that's where this book comes out as a winner!Chapters cover all objectives and are neatly organized. Every chapter concludes with a small test and a "Two minute drill" that is great for last minute reviews (and index cards!). "Exam watch" sections are interspersed throughout the book to draw your focus on test specific issues and "Scenario-Solution" sections present potential design/architectural issues with solutions in a quick to read format. Many chapters include exercises for problem solving and essay-type answering required for the final part of certification. A sample case study of a securities trading system helps the readers to prepare for part II assignment. Here's where the "more" factor comes in - the accompanying CD contains a large collection (250+) of questions in the form of two simulated tests. One can register free on their website to download an additional test. The testing software not only includes detailed answers for every question, but will also generate a score report to help you identify your weak areas. The CD also contains code samples referenced in the book and all chapters in electronic (pdf) format. That's very helpful for someone on the run! This book is much more than a certification guide. It can very well be used as a complete J2EE quick reference guide. Some of the extras packed in the book include XML coverage in Common architectures/protocols section, a great OOAD/UML refresher, lots of J2EE best practices and tips, introductory coverage of JCA and working code for many design patterns. The "On the Job" sections present the reader with some interesting real-life architectural scenarios. Some code samples are two to three pages long, and one of them has a three-page output listing!! Perhaps that's the only not-cool thing about the book. Ajith Kallambella
http://www.javaranch.com/contact.jsp#AjithKallambella
Rating:
Summary: Stay away from this book
Review: Right from the start the book lacks a smooth flow and a sense of purpose. It rambles on and on about the greatness of all things irrelevant (from the exam point of view). The chapter on architecture never seems to end and before we know it we are being told about the parameters and bad practices when it is not clear in the first place what constitutes an architecture. The authors chose to quote some standard definitions but that does not cut it. There is a chapter on UML which doesn't state anything in precise terms. This is the trend through out the book. There is a chapter on design patterns and this is an example of how not to teach things. The authors write tons and tons of code detailing what could have been explained by a simple UML diagram. After all UML is on the exam and the chapter on UML precedes the chapter on design patterns. Most of the examples are meaningless. Then there is a chapter on legacy connectivity which talks about JCA in the text but asks questions about everything non-JCA! This is written for somebody who is aware of JCA. This is not required for the exam. Since I was new to subject matter, I read the specification which like most specs from Sun is really written well and was an easy reading. When I went back to the book, things made sense. The same patterns are repeated in the chapters on Security, EJB and Internationalization. If I were to do it again, I wouldn't even touch this book. The books by Richard Monson-Hafael and Cade and Roberts are more than sufficient for the exam. For everything else, there is the spec which should be read at some point anyway. Most people who take this exam are short of time and the kind of useless diversions offered by the book only waste time. This examination resembles written exams taken by medical students where the subject matter is vast and trying to cover everything leads to a shallow knowledge. Just as there, the goals here are very clear and if one focuses on knowing the key points, one can reconstitute all the other material by reasoning. This book fails to emphasize the key points. Cade and Roberts do exactly that and that is the difference between a good book and this which is destined to be a door stop.
Rating:
Summary: J2EE Enterprise Architect study guide
Review: Terribly written book. While the TOC look good the content is woolly and not very specific from a technical standpoint. The 2 minute drills are way too short and the chapter questions are not comprehensive - and many of the answers are wrong. Lots of typos and not very readable. Using this study guide will not help you pass the exam - dont waste your money... Clearly the authors didnt have a clue and the whole thing looks rushed and never proof read.
Rating:
Summary: better to read articles than expending on this
Review: The book has both good and bad in an unwanted blend. It is good because, it tries to cover each and every objective of the exam by name and reminds the exam at each point. It even tries to discuss the objective. It is bad because it fails to show the required information in required form. The UML chapter (Chapter 3) starts with the explanation on OOA&D, which is irrelevant for the exam. The person who is ready to get certified as an architect from SUN would have obviously spent enough time in software development and be aware of the terms the book tries to explain. If we think that it is OK, to our surprise there is no figure for the elements of UML (Example class, package, collaboration etc.,). The book tries to write 1000 words but does not show a figure for the same. Hope the authors do believe that a picture is worth 1000 words. Even the figures that follow for other topics are not up to the mark. For example, a single class is shown in maximum size and the title says it is a class diagram. As per my knowledge, the class is just an element of a class diagram and not a diagram by itself. The book never tries to be product neutral. It always tries to force the user to know about web-logic. More pathetically, the code is only for Weblogic and that too for a specific version. I am disappointed with this to a greater extent. In my opinion, the book needs one more parse to make it ready for only architects.
| 
