Java 2 for Professional Developers

Rating:
Summary: 0 stars
Review: 'bout a year ago I bought this book at London Drugs for 9.99. What I want to say is that I wasted my money and the only reason was the word "Professional" on the cover. Mr. Morgan, could you please explain me what it means?

I thought I'll find something there (also book was published in 1999)...
Doh. It looks like author didnt know what to write about. He jumps from one subject to another, from his 'hospital' application to UML, then back, then to threads, then ... There is no complete text of application itself, only pieces. Thus it gives nothing to 'professional' developer.

I also dunno who is supposed to read it. From beginning it looks like it is for novice, but in fact it would become incomprehensible (for novice) just in 20 pages. But why bother about simple examples on threads, awt etc then?

There are no topics which completely covered. Author gives NO explanations on UML, although he uses it. He quickly discusses software development, but never shows how to apply it and never uses on his example (which is, as I told, incomplete). Etc etc.

Actually, a year ago I found this book too difficult to me and put it on the shelf in the hope id read it in some time. 4 months ago I did, and found nothing more than empty phrases on academic subjects and trivial (and bad) Java basics.

If you will find this book in thrift store, buy it and throw away.

Rating:
Summary: 0 stars
Review: 'bout a year ago I bought this book at London Drugs for 9.99. What I want to say is that I wasted my money and the only reason was the word "Professional" on the cover. Mr. Morgan, could you please explain me what it means?

I thought I'll find something there (also book was published in 1999)...
Doh. It looks like author didnt know what to write about. He jumps from one subject to another, from his 'hospital' application to UML, then back, then to threads, then ... There is no complete text of application itself, only pieces. Thus it gives nothing to 'professional' developer.

I also dunno who is supposed to read it. From beginning it looks like it is for novice, but in fact it would become incomprehensible (for novice) just in 20 pages. But why bother about simple examples on threads, awt etc then?

There are no topics which completely covered. Author gives NO explanations on UML, although he uses it. He quickly discusses software development, but never shows how to apply it and never uses on his example (which is, as I told, incomplete). Etc etc.

Actually, a year ago I found this book too difficult to me and put it on the shelf in the hope id read it in some time. 4 months ago I did, and found nothing more than empty phrases on academic subjects and trivial (and bad) Java basics.

If you will find this book in thrift store, buy it and throw away.

Rating:
Summary: Java 2 for Professional Developers
Review: A lot of the sample code contains typos and the online sample code doesn't exist. Also, the author just points out where to find information in the SunSoft java documentation rather than go into any detail. Stick with O'Riley books

Rating:
Summary: Bad content, nice cover though...
Review: Beginners, don't ever make a mistake in buying this book! Intermediate and advanced users, if you like, you can buy this book and have something to mock about during spare time.

I am an intermediate programmer, and I already know a couple of languages (COBOL, Visual Basic, ASP, some C/C++), I tell you, the author wrote the book not knowing who should read it, or who can benefit from it. It's too advanced for a beginner, and yet, doesn't really offer much for an intermediate or advanced user. Sometimes he talks to a beginner, sometimes, to who knows who. Everything is in bits and pieces.

One more thing, the author likes to tell you by looking at information in another place you'll be able to understand how he presents code in the book. What do you think is the reason why people buy this book? Also, the source codes which the book said is in the support website, it doesn't exist. It figures, the author knows that with a poorly-written book like this, whether the source codes exist or not, it really doesn't make any difference. My first java book-----money down the drain----I should have just donated it to charity!

Rating:
Summary: Good Premise, Awful Follow Through
Review: I spent about an hour flipping through various books before choosing this one. The writing seemed pretty clear, and there seemed to be enough examples to give an experienced programmer in other languages a good starting point for learning Java. However, I discovered several things about the examples in the book -

1) The source code isn't on the company's web page, as described in the book.
2) The company won't provide the source code, meaning you have to type it in (not a huge deal, just an inconvenience)
3) The source code does not compile (The Tstore example has at least seven compiler errors) and it isn't obvious to a non-experienced Java programmer how to fix it.
4) The author's website/e-mail doesn't exist.
5) E-mail to the publisher about the problems go unanswered.

So you're left with a book for which you paid for, and if like me, without the experience to correct the errors. Without being able to resolve the conflict between what the compiler is telling me and what the book is telling me, I found it impossible to learn the language from this book. Find another place to spend your money.

Rating:
Summary: Handbook of survival for Professional Java programmers
Review: No one has ever covered Java programming the way Mike Morgan has. As the title implies, this book is originally meant for medium to expert Java programmers, and certainly not for the newbies.

This books covers the Java language and capabilities like any other book on Java, but what is more impressive is the way all the phases of a development project in Java are exposed. Instead of merely covering Java alone, the author covers the Software Engineering side of a Java development.

Covers hot topics including Streams, Sockets, Security, CORBA and entire chapter on EJB.

Certainly this book is for Java development team lead aspirants.