Customer Reviews

Building Java Enterprise Systems with J2EE

5 star:		(24)
4 star:		(4)
3 star:		(2)
2 star:		(4)
1 star:		(4)

 

 

The authors deserve an "A" for effort (but much lower for usefulness). They wrote 1300+ pages and tried to cover every aspect of Enterprise Java Development: every major Java API, tie-ins/comparisons to CORBA and COM/COM+, etc. In the areas where I already had a deep understanding, I never found any factual problems with what the authors were presenting. Certainly, there are books that cover individual topics (JSP, Servlets, EJB) in more depth but the sections here are respectable.

I was disappointed because I was looking for solid direction on architecting Java Enterprise Applications. The book constantly presents what a Java API (or CORBA model, etc.) can do for you. Only in a few instances does it clearly help you weigh the strengths/weaknesses of alternative approaches to solve a problem. It regularly presents a whole series of "solutions" (i.e. Java support for x, y, z) but it fails to tell you that Solution A would be required in most J2EE development projects while Solution B would generally be used to solve a particular niche problem.

What you are left with is an overload of information but nowhere to "store" the information in your mind (e.g. I should use this API or class to solve this type of problem). I give two sample areas below where I read the book hoping for much but feeling empty-handed when I'd read the material. Only when I later read better (and often shorter) articles on the topic later did I come to truly understand the "real" issues.

EXAMPLE 1, SECURITY: There are three chapters covering 100 pages on security. Having read them, I felt like I knew very little more about how one could/should implement security on a J2EE project. Having read the three chapters, I still didn't know: a) what aspects of security would I typically need to implement on a J2EE web application? (hundreds of options were presented - surely some are "core" to typical projects while others might apply to very particular situations while others are available are not used in industry) b) does a typical application server supporting J2EE model provide me with all I'd need for security/authentication or would I typically need other packages/custom code to augment what is provided (in fact, I've since learned that there are definite gaps to be filled but in all mess of saying "what is available" in J2EE, the authors don't articulate the clear gaps).

EXAMPLE 2, XML PARSING: The authors present the main models for XML parsing (SAX and DOM). They spend 30 pages diving into the details of using the two models. However, after reading them, I only get the sense that they are two alternate ways of reading XML documents. Their discussion didn't tell me: Conceptually, how does each model work? What is the fundamental difference between the two? When would I use one vs. the other? I have since read an article introduction that in three paragraphs gave me a clear conceptual picture of how the two models worked and when I'd use one vs. the other. Now I might be ready to understand what the authors wrote but, at the time, my eyes glazed over.

In conclusion, I cannot offer a suggestion for a better book on architecting Java applications (I've certainly looked). Right now, it seems like one needs to research particular articles that will address specific aspects of the Java articles (and be prepared to spend a lot of time doing so). This book has a lot of useful Java reference information but it is not the consolidated Java architectural reference that I was hoping for.

I found that this is the only book which covers all J2EE APIs at great length and with real world working examples. I am impressed by the way the authors explained the various aspects of J2EE APIs Servlets, JSP, JMS, EJB, JNDI, RMI-IIOP and deploying in two different Application Servers (J2EE RI and Weblogic 5.1). The chapters are put together in a very well organized manner. At the end of the book, there is a working version of online Store using all the J2EE technologies, which I found very useful. The material is clear and straight forward. The book covers the interests ranging from novice to expert Java Developer. The books has lot of pages like other java books, the difference is that the book does not waste any page to show api. Overall this book is a very good book for a J2EE Developer.

Overall this is a useful book for J2EE developers. I specially like the integrated e-commerce sample, which was developed and is targeted for deployment using WebLogic 5.1 and Oracle 8i (both are real-world technology of choice by major companies), and this alone makes the book unique. This is accompanied by detailed instructions at the end of book for setting up the environment for running the sample application. The CD even includes an evaluation copy of the WebLogic Web Server 5.1.

Since the previous reviewer has already pointed out that this book covers all J2EE related topics, I don't need to repeat them here. Another unique feature of this book is that it also covers Microsoft's DCOM technology and its version of Java, and briefly mentioned how to integrate DCOM into J2EE apps.

My biggest complain about this book is that while trying to be comprehensive and make this as a single-volume reference source for J2EE, the authors actually sacrificed to some degree the focus of the book and omitted certain would-have-been very useful details. I would like to see basic information on HTML, TCP/IP, HTTP, web secutiry, OOD, Java fundamentals, client-side Java, CGI, and basic RDBMS/SQL content (13 out of 38 chapters) removed from the book. I my opinion these are prerequisite knowledge for any J2EE developer and are better left for other books. Instead of those topics, I would like to see more pages added to explain the code of the integrated sample (for example an explanation of the overall architecture and design decisions). Also, I think the book's repeated use of class diagrams to show Java class API is over-done.

Being the first book available on the market that toughs upon all aspects of J2EE, this book definitely has its value, even though there are obvious shortcomings. One final thing, this book is more about an overall picture of J2EE, not so much about every single detail of its component technologies. Therefore, if you are looking for a book on a specific topic, such as JSP, servlets, EJB, there are better books for them.

This book is not want you want. I bought this book based on the all the stars I saw and was very disapointed. I already know J2EE. I am an engineer working for an application server company. I was looking for a good J2EE book to give to some new hires so they could learn J2EE. With each chapter and topic, I kept waiting to read any real information that would be helpful to someone that wants to write a jsp, servlet, ejb etc...When it was over, I just kept asking myself "Is that it? What about this and that etc..."

This book misses everywhere , right from the Title "Building Java Enterprise Systems..." - let me make this VERY CLEAR - This book does NOT teach you how to BUILD J2EE applications. It reads more like a case study or product sheet than anything else.

What it does is define all the aspects of J2EE and yes has a real world example that is the best example I have seen but every aspect is glazed over. The only chapter I thought had any depth to it was the JDBC chapter. The servlets, EJB, JNDI, JTS, JSP sections...please! This book has less detail in it than a master java in 21 days book. This book describes the basic concept of each j2ee object and then dumps a picture of the api on a couple of pages...then, moves on to another topic. If you want to know what the api does then get another book. If you want to know how program using the api then get another book.

Even worse after dumping all this information bit by bit in different chapters this book never ties all the technologies together.

This book should be titled "An Overview of Systems Built with J2EE" because it does suceed at defining and describing the various pieces of J2EE but to imply that it teaches you or provides you real information on how to write any J2EE code is a crime!

BTW, I also bought the WILEY book Developing Java Enterpise Applications and thought it was much better at covering J2EE than this book. For those developers out there working with a J2EE application server, the Wiley book is much better than this one.

Pros: Covers almost every topic that is even remotely related to J2EE (I guess this is a pro...). A few of the individual chapters dealing with specific topics were actually quite useful (the JNDI and JMS chapters come to mind)

Cons: First off, while I have a tremendous amount of respect for the author's technical knowledge, his writing style is as dry as sand. Trudging through the prose in this book was a burden I won't soon repeat. The countless (and I do mean countless) class diagrams failed to add any value whatsoever and usually just tended to add to the confusion. Tried to cover too much and therefore failed to cover the critical topics in enough depth.

My advice? Sun's J2EE Blueprint is a MUCH better overview of the J2EE architecture. Once you've absorbed that, buy individual books on the specific technologies. I can recommend Monson-Haefel's Enterprise JavaBeans 2nd Ed. and Hall's Core Servlets and JavaServer Pages. Both are a pleasure to read and cover their respective topics in depth.

I bought this book along with a few other books on EJB and JSP and it has stood out as my favorite so far. It has also been involving. First of all it is the only book that really covers J2EE and gives EJB examples deployed with J2EE (and Web Logic). This book has xml deployment to 2 servers which I think is really good. It also had information that wasnt even in books specialised on EJB and JSP and Servlets. There is information on J2EE servlet security and transaction and alot of EJB advanced stuff (security and transactions, JMS-EJB, JavaMail-EJB). I jumped to this information first, but there is JDBC 2 and CORBA and RMI server information as well.

In general, there is alot of info and examples and a JSP to EJB ecommerce example. While I cannot use all of the information in here, there are things talked about being used by other people in my group (LDAP, alot of security, etc). I only had a complaint when my Web Logic license expired but found a new license only after going to the books web site and being redirected to Web Logic for a new license.

Finally I have a book that doesnt try to sell me the glories of a technology or vendor and explains how to get my work done.

The J2EE technologies are very wide ranging and can be quite overwhelming at times. As a software engineer and CTO of a software company performing J2EE services work, I have found this book to be a very valuable asset in deepening my understanding of all the pieces making up the J2EE and related technology set.

The authors have a very thorough understanding of the material they present, and the text is well backed up with many, many UML diagrams and other supporting technical illustrations.

I feel this book is an excellent starting point for determining the applicability of J2EE for your company's projects and products. In the software industry we often get very focused in small technology pockets with little time for exploring other alternatives. This book will help you pop out of your hole, and take a look around at what is available in the industry, and how to use it appropriately.

This book provides a one stop read for J2EE APIs like JMS, JSP, Servlets, JNDI and RMI-IIOP. I found that the authors have spent a great deal of time in putting out well tested examples that explains nitty-gritties of J2EE specification. This book has provided me with lot of expertise for writing mission critical applications. I would highly recommend this book to any serious JAVA developer who wants to get his feet wet with juicy code.

i have read this book in my country with over 50 class mate and we regrard it as our best book yet. the author have cptured everthing possible in short forma and without talking more than onc about same idea. I am so happy I bougt book and didnt buy many books of same topics.

When I first read the proposal for this book, I was overwhelmed with the magnitude of what the authors were trying to accomplish. My first impression, and one that I repeated throughout the editing process, was that in their attempt to do everything, they may do nothing in sufficient depth. The proposal contained the following claim: "Master J2EE, EJB, servlets, JSP, XML, JMS, JDBC, security, JNDI, Jini, CORBA, RMI, DCOM, JTA, JTS and JavaMail." Nearly every one of these topics could be the topic of a large book in itself, so there was ample reason to be skeptical of the quality of the book.
As the chapters began arriving and I began to filter through them, my attitude changed, although I still believe that some topics are not presented in the depth that they probably should. However, it is in the realm of opinion as to what is adequate depth, and honorable people can reasonably disagree. It is clear that the topics are covered in sufficient depth so that the persistent reader can learn them.
This broad coverage in adequate depth makes the book a bargain. With so many topics covered under the unifying themes, reading this from cover to cover, (believe me a challenge for anyone), will expose you to all aspects of the development of Java Enterprise Systems. It is not for beginners, as a great deal of experience in Java is needed, essentially from the first pages.
This book is a heavyweight, both physically and in content. Built with the experienced in mind, it should be read slowly and thoroughly to be completely appreciated. This is made easier by having trial editions of some Java development environments and all the source code on a companion CD.

Disclaimer: The author of this review served as the technical editor for the book.