Customer Reviews

Java 2 Bible (Bible (Wiley))

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

 

 

As a programmer I found this book to be fairly useless in comparison to the O'Reilly line of books. There are countless instances where the plainly obvious is spelled out in long tedious paragraphs, but other obscure parts of the code are left unexplained. For a book that claims to be the "bible" there were also many notes indicating that a given topic was outside the scope of the book. I'd have to agree with the writer who said that this book doesn't explain how to put the various building blocks together to make a functional program. I think the tutorial on Sun's website is at least as useful and certainly a lot cheaper.

I am an experienced programmer, but I found this book difficult. By Page 120, you have been given the Hello World example and by page 323 you have been given the basic syntax. However, alot of the code examples continually use stuff that the reader has not yet been exposed to. Also, no where up to page 323 does the book really explain how you write a basic java class. The chapters cover individual topics, but nothing links the chapters together. The book gives the reader separate building blocks, but little guidance on how to construct a usable program with those blocks. I learned much more at the Sun tutorial site than I did from reading this book.

I don't really know what to make of this book. It started out great. I devoured the first 5 chapters (~170 pages) in a weekend. Then, inexplicably, the authors depart from their tutoring role and go into lecture mode. After the obligatory HelloWorld example and a few sample applications and applets in the first part of the book, we are subjected to reading the next 200 pages before another interactive exercise appears. It's a shame, too, because I really like the authors' writing style. They definitely kept me interested but I just felt that I wasn't learning anything with the meager offering of hands-on exercises. I'll give the book 2 stars for the excellent Part I of the book. The rest is all down hill. What a letdown.

I got through 300 or so pages and so far all i've learned is "Hello World". I wish i'd spent the extra $10 and bought the wrox press book. Few examples, no online support; not a good book for beginners. I learned more pracitcal information from the free online Sun tutorial.

I couldn't recommend this book to anyone.

I bought this book on the strength of the publisher, simply because the Javascript Bible is so fantastic. What waste of my money.

What really tears at a technical book is it's ability as a reference. In this regard, it is useless, clumsy and horrible. I was trying to learn java coming from ASP & JavaScript experience and this got me nowhere. Trying to code with this at my side just didn't work.

If you want to learn java, go straight to the source...Want a reference... learn to use javadoc.

This book showed me nothing, and did little to excite myself in Java. It shows that the writers came from another language, and weren't excited about what java was bringing to the table.

For example: From the outset, java was an integration of a wealth of experience from it's developers. Built into the language is a documentation tool. JavaDoc. Brilliant to use, and truly an excellent solution. This book did tell you to have documentation, but all their code is blocks of single line comments! They do mention JavaDoc... but why not use it yourself!??

Never got anything from this book. Threw the book out last week.

Can't believe a contryman below gave it a good wrap. sad.

Major problems:

- Willey (Hungryminds) do not support this book any more. No supplemental web site, no book available on their web, isbn unknown. Author doesn't provide any support (http://www.vlc.com.au/~justin/about/resume.html) on his site.

- Book lacks complete runnable examples. I don't care which tools should I use to run (ant, eclipse, websphere, jbuilder - all trials available).

- It is not for beginners, it is not for gurus. I respect the good books for beginners. A good beginner book can make a guru out of a newbie, depends on the author's approach and reader's way of learning. If they match, you have win-win combination.

-Too much introductions in each chapter, e.g. related to LDAP, Novell Directory Services product was introduced in 1994, bla bla bla, it includes many good things, bla bla, it is shame that programers dont benefit of its capabilities, bla bla. - Oh ! Come on, who cares ! Give us the real stuff, give us examples and show us how to improve them, show us advantages and disadvantages of each approach. Give us some skeletons. No sencences starting "In 1998...".

I wish this book was written as some of my favourites. After all, this is not a bad book, but you will need at least 5 other books to learn what you need to know.

So far O'Reilly's Struts book (isbn 0596006519) helped me to integrate struts and ejb. Addison Wesley Pr, Websphere related book helped me out with IDE (032118579X), and several IBM red books helped me to learn what I needed.

Finally best book ever written, with the best examples, attitude, is isbn 0072226846. It is a j2se book. By my opinion this should be a new standard of writing books. Exact, sharp, smart, examples, rules, best practices, etc. If only they could write a j2ee book.

Finally 2 starts go to this book. I never rated any j2ee book with 4 or 5 stars, so 2 should be good.

My big disappointment about many j2ee books is that the best articles and examples and answers to my questions are found on the internet. I am still looking for a j2ee top book.

Coming from a programmer experienced in other languages, I thought the pace and depth of this book were perfect. It helped me pick up java and after reading it cover-to-cover, I'm now coding java apps for a living.

It's not going to be the only book on java technologies I ever read, but it makes a great first book on java technology.

As an experienced C programmer I have to say that this book
is a great introduction to Java 2 but it is not for
beginners from my experience. The chapers are written in a
friendly way that makes them easy enough to understand, but
after the first section that covers getting up to speed with
Java in general, Object Oriented Programming concepts, etc
you REALLY have be a programmer to absorb the concepts and
examples.

Starting with chapter 6 the authors take off the kid gloves.
This particular section was the most complex part of the
book for me, and I found it easier to skim through this
collection of chapters lightly at first and then revist
these topics later once I got into the other more hands-on
parts of the book (such as input/output, creating graphical
user interfaces, and networking, etc): plan to make two
passes on the "middle" chapters if you want to memorize them
by heart.

Because the Java language is covered in such detail I found
this book to be a good desk reference for fundamental
concepts, making it a good book for C programmers like me
who want to learn Java, especially when combined with the
free online API specifications. Overall I give it four out
of five stars. Between the book itself and the free online
support site it was defintely worth the $$ since I bought it
used, but be warned it's not for beginners!

I get annoyed with these "kitchen sink" books that purport to cover everything and in reality *teach* us very little. I never need just *one* book for everything. I'd also like to highlight the fact that J2EE includes RMI (incl. Activation fwk), Corba (IDL, etc..), JNDI, EJB, Servlets (perhaps JSP). These topics are conspicuous by their absence so avoid this for J2EE and get: Java Enterprise in a Nutshell.
I pity any java-junior trying to balance this weighty tome on their knees: it's sheer size is unworkable. The book is a cancerous polyp on the butt of an over published tech-book-market.

This book assumes you know the subject already. The problem is that the book explains things as if the reader is already a Java programmer. How can one read & understand a company's 10Q filing if he didn't know what PE ratio meant? Then it leaves out too many details to be useful to anyone.