5 comments about Developing Java Beans.

1. Actually I bought this book about two years ago, and at that time Java Beans were gaining popularity as an instance of component model for distributed computing. I was at that time interested in Enterprise Java Beans rather than client side beans. So I did not really use the book that much. However, from the limited reading I did, it seemed like a very well written book for the uninitiated, gave a good view of the Beans, how to create the client side beans etc. However, since then I have moved my field of interest from Java to some thing else, and in the mean time EJB have taken an increasingly important role in the server side component model. So I hope this book is updated or the same authors write a separate book on EJB (more meaningful to do the latter).



2. This book is titled "Developing Java Beans". It spends lots of time to talk about the detailed architecture of Event model and other important topics used in Beans. It is well written and easy to follow. However, may not be the good book for those poeple in a rush just want to how to write a Java Beans.



3. This is not a good tutorial about Java Beans. In order to explain the Java Bean concept you have to start with the Java Beans specifications of Sun. This would answer question about which things are relevant and why they are relevant in JavaBeans development. Now the the reader almost jumps into a long winded explanation about events and adapters, wondering why this is relevant and what the writer wants to explain. To make matters worse: the example contains errors! Basically, after the first three chapters I was utterly confused.

   This book also needs a clearer description about the use of Java Beans. In a next update we definitely need a chapter about how JavaBeans are used in Java Server Pages.




4. I've been programming for 10 years, and I have 2 bookcases full of ORA and ADW books. I have to say that this is among the most confusing programming books I've seen.

   I'm in the same position as the guy below who's confused after 3 chapters. The first couple of chapters of this book seem to be a tutorial about event handling, and applet creation. Applets? I have no idea where the author is going with this stuff. It's not that I don't understand the concept of event handling, it's just that this guy does not explain what the heck handlers and listeners have to do with beans. I'm sure they do, somehow...

   Perhaps if the author provided an an explanation up front about where he's going with the code, I'd stick with the program. Even better, how about an overview of why beans are so great and useful, with some trivial examples. Then progress to the 'real world' stuff.

   I'm dissapointed with this book because I need to learn about Beans... fast. 3 chapters of working bean code and good examples would have been enough for my instincts to kick in and take me the rest of the way. I don't have the time to search for answers, I thought that a $30.00 investment in an ORA book would have saved me hours of searching. Well, not this time.

   If you can get the applets from chapters 1 and/or 2 working, please post how in this forum. You'd be doing a lot of folks a favor. Good luck figuring out if you should be compiling *.java.1 or *.java.2 examples.

   That's enough about this one... Now I have to find a GOOD beans book.




5. A nice little text with useful snippets of code, and advice on
   applying them. However, the order of presentation can be a little
   confusing. Also, some of the topics were a little beyond what I
   needed it for, though that is not a bad thing.
   
   What I found annoying at times was that it did not always address a
   question I may have had about how to apply a particular class.
   Having "Learning Java: 2nd Edition" helped somewhat to alleviate
   this as it had more in the way of explanations than this book.
   
   For the absolute beginner I would probably recommend another book.
   However, if the reader has background knowledge in Java, or other
   programming languages then this book will probably prove to be
   useful.

5 comments about J2EE Applications and BEA WebLogic Server.

1. A great way to learn J2EE if you are looking to use Weblogic as your application server. Most of the examples are clear easy to follow. I definitely recommend it.



2. This book is an excellent survey of WebLogic Server 8.1 and, more generally, building applications with J2EE. It describes each of the functional areas of the server - JSP and servlets, EJBs, JMS, JDBC, security, administration, etc. It also reviews other technologies, such as web services, XML, and SOA, and how they relate to J2EE. The example application is thorough and useful. This is an excellent book for someone new to WebLogic Server and J2EE or an expert looking to polish skills.



3. This book might be a good book for beginner/intermediate programmers but it does little for intermediate/advance programmers who want to learn about weblogic. Advanced users will easily get bored with its simplicity and lack of detail on critical topics such as command line depoyment or even console for that matter (not practical). Their are a lot of things that are assumed in this book and really just scratches the surface of weblogic. Just when topics get interesting, the authors refer the reader to weblogic's online edocs.
   
   If you have understanding of j2ee and need to get upto date with weblogic , this is not the book for you. The examples in this book are very simple, with probably a hello world example for each chapter. You can see this as either good or bad. warning: Some beginners to j2ee will find some difficulty understanding deployment without previous knowledge in j2ee, The book is not very PRACTICAL. It would have been prefaired if the examples in each chapter continued on to the following chapter, this way the reader could learn how the different components in j2ee work together and more prefairably in a weblogic environment.
   
   Overall I didnt enjoy reading this book very much, some chapters are really well done while others are not, I give this book a 3 only because this book would serve well for a beginner in j2ee and not weblogic.



4. While I have found this book useful, it also has some obvious errors that should have been caught. The explanation of how to use many of the examples on the CD-ROM is either poor, or non-existent in some cases. All in all it is an ok book, but I think I will need to find a better book and buy it before I will feel I really understand Weblogic. Cannot fully recommend this book. If you can buy it cheap as a used book then maybe it might be worth your money.



5. This book provides comprehensive coverage on J2EE architecture, key concepts, and elements (Servlets, EJBs, JNDI, JDBC, JMS, and JSP) using WebLogic application server 8 as a platform. In later chapters, the book also covers practical topics such as WebLogic administration, security, design and product deployment processes, clustering, and capacity planning. It provides insightful design methodologies that have quality production systems as an end goal.
   
   This book can serves as a good reference book for reviewing key J2EE concepts. I highly recommend this book to software architects and senior J2EE developers.

No comments about Introduction to Cryptography with Java Applets.

No comments about A Guide to Programming in Java.

5 comments about Aspect-Oriented Programming with AspectJ.

1. As the subject is relatively "new" for the general public, the documents obtainable from [URL] had been the best tutorial until the arrival of this book.

   The author has a in-depth understanding on the AspectJ and he was able to present his knowledge clearly in his book. The "aspect traces" provided were able to help the readers understand how AspectJ really works. The examples helped me to grasp the difference between the "call" and "execution" pointcuts.

   I didn't give this book five-star because the few chapters on the "AspectNews" application were not convincing because I don't think it likely that AspectJ will be applicable to a non-trivial Web application for the exact reasons given by the author in the last chapter (ch. 14) of the book.




2. I have never rated a book as lowly as I have for this one. It is horrible. Let me count the ways:

   1. They forgot to edit the book

   Not only are there spelling errors and grammatical errors, but numerous code errors, API errors (or ommissions), and code left out of the book! The grammatical errors actually make certain parts of the book impossible to understand. I had to search on the web to find the answers.

   2. VERY poor organization

   In one chapter he tells you the code you'll need to compile something we won't do until four chapters later. Worse, although he attempts to create an incremental build of your code, the code you can download online only works in the final version. Of course if the book actually had the incremental code that wouldn't matter, but it only has some of it. I spent half my time just trying to figure out what in chapter 4 goes with what in chapters 2, 5 and 7 (for example).

   3. Missing SQL Code

   I had to guess what the tables were like since he forgot to include SQL code in the book AND (!!!) it isn't in the code download online either!

   4. Poor explanation of everything

   Almost every example he gives in the book has either no explanation, or a useless one. For example, he might tell you that some code "introduces" the class to their new parents and that "introduce" is the official name for this action. Of course, don't ask him to define the keyword "introduce" for you. You have to figure that out for yourself. This whole book reads as though it were written by someone who loves to be smart, loves big names and acronyms that define him as a high level programmer and doesn't want to sound too simple by actually taking the time to explain it to you. As they say, "those who can't do, teach." In other words, those who weren't naturals at it had to struggle to learn so they understand they have to explain it to you - Kiselev does not.

   Don't buy this book.




3. I liked that book - it manages to squeeze a lot of new information into relatively small volume - though may be at the expense of the ease of understanding by novices.
   Explanations are concise and relying on reader's intelligence, without "I'm teaching you" condescending approach so common for many "methodology" books.

   Code examples are useful - if you don't care much to compile them. They rather have to be treated as pseudo-code that illustrates the AOP concepts - and very effectively, I think.

   I wish more books like this one were published - short, to the point, respecting both my time and my bookshelf space.




4. If you need a book that explains the technology, then buy this book.
   If you need a reference guide, then buy this book.
   If you need some examples that illustrate the power and limitations of this technology, then you should *definitely* buy this book.
   If you are looking for the big picture, concerning the big freaking aspect-oriented programming thing, if you want to read about scientific justification, and if you're looking for proof, then you *might* consider buying this book, but I didn't find it very valuable from that perspective.
   If you just want to be entertained, then you might consider buying something else. Maybe something like 'The Amazing Adventures of Kavalier & Clay'.



5. I have read this book with great interest. My conclusion - this is
   excellent introduction into new field of information technology. The great
   advantage of the book is the "from simple to complicated" style of
   presentation that allows to recommend it as a great introductory course for
   self study. The extension of Java classes into AspectJ can play the same
   revolutionary role for Java developers as some years ago
   Microsoft MFC implementation did for Windows 3.1
   programmers. The concept of dynamic crosscutting can be enormously useful
   for everybody involved in the development of real-life business applications.
   The style of presentation allows to start using AspectJ for application
   development very quickly. The large number of simple examples is
   represented in the way similar to the famous Stroustroup's C++ book.
   This book can be recommended to everyone who is interested in the new way
   of thinking and the current state of information technology innovations.

   I have not succeeded to compile and execute the code from the book due to a
   lot of technical problems. The code listings and examples in Kiselev's book
   can be recommended as invitation to think and develop you first application
   in AspectJ.

No comments about Practical Debugging in Java.

5 comments about Mastering Java 2 (Mastering).

1. The advanced topics are same as developer's handbook by Roberts and Heller.

   I have been through both the books and noticed that the chapters on advanced topics of Java are identical (word to word,figure to figure). Both the books have same wordings, diagrams,tables and even the same coding examples. I find it very hard to believe that different authors would write end up writing using same wordings, diagrams and think of even the same coding example.

   I am giving below the comparisons for ready reference :

   Mastering Java 2 | Java 2 Dev. Handbook

   By John Zukowski | By Simon Roberts, Philip Heller

   1. Ch 21. JDBC API | CH 11. Database Connectivity

   2. Ch 24. Security | Ch 18. Security

   3. Ch 25. RMI | Ch 12. Persistence and RMI

   4. Ch 26. Java & CORBA | Ch 13. Java & CORBA connectivity

   I gave up after this. Is this a strange coincidence or is someone cheating here (Either one of the authors is cheating or Sybex is cheating by selling the same material under different titles and using different author names and making more money). I know Sybex has the copyrights but is it ethical? And why are the authors silent or they just care about the money or maybe they are not the real authors in the first place? Just wanted to spread the awareness.




2. I bought this book yesterday and am returning it tomorrow after realizing that a lot of the example contained within it are incorrect and do not even compile. The book has references to: import com.sun.java.swing.*; which after some investigation I realized must have been renamed to import javax.swing.*; so any references to swing components in the example code do not work. A friend recommended "The Complete Reference - Java 2 - Third Edition" by Naughton / Schildt as an excellent book.



3. I wish I'd checked out the reviews here before I hastily went and bought this book. It is a terrible book, bereft of any useful, real-world examples and full of typos. It skims over topics giving the reader no hope of fully understanding the concepts. This would be acceptable if it had a load of examples that you could use to get coding straight away but it doesn't. By Chapter 5 the only fully compilable code example (as opposed to snippets) was the mandatory "Hello World" program in Chapter 1.

   Terrible book.




4. Having worked with Java technologies since 1995, I feel this is a brilliant book. Agreed - it does not go in depth into many of the topics it covers, but I do not feel that is its intent. The book is aimed at imparting a decent level knowledge of all the essential technologies behind the Java 2 enterprise platform.

   The book does unfortunately contain a number of typing errors and non-compilable examples, mostly due to the fact that it was written before Java 1.2 was available (so the Swing package changed, for example) - check the errata list for this sort of thing.

   If you are looking for a book that takes you through Java from the beginning to the end, without going too deep into any one topic, then this is the book. Business programmers especially will find this an invaluable aid. Hackers and people wanting to use fancy tricks and get the maximum power out of a particular part of Java should read the Java Docs distributed with the JDK, or get specialised books.




5. Excellent book that explains the principles and underlying architecture of various Java technologies. Provides the full understanding of the features with simple examples focused on the topic. Easy to read and understand without too much surrounding words. I own a couple of Java books for different levels but I always end up going back to this book if I want to really understand the solution. Also has excellent index. It is easy and quick to find answer to any Java related question.

5 comments about Java 2 Developer's Handbook.

1. Authors and editors spent very little time updating is book to Java 2. Its too bad Sybex places such little value on the quality of their books. Sybex is no O'Reilly. Really wish I had not wasted my money on this book.



2. Lots of useful code without any explanation, but nice cover and pictures with cups of coffee, wich suppose to make it easier psyhologically...but not in real life



3. I bought this book when I was a beginner and read it rather quickly. Today I started work on a telnet client and remembered the book describing the use of telnet URLConnection. Cool, so I loaded the CD-ROM and to my disappointment no protocol handlers (the telnet handler or one for the other example) were included at all. I e-mailed their support person but after a few exchanges it became clear he didn't have a clue.



4. I was reading this book for reference on ChangeListener (page 729). The examples given does not even IMPLEMENT the ChangeListener interface. What a strange way to programing. This is entirely different from LeMay's TY 21 day examples. I am really confused. I am not buying another book by the same authors.



5. all the adanced aspects of java is mentioned, but out of date

No comments about Java Programming Projects.

1 comments about Essential Java Class Reference for Programmers, The (3rd Edition).

1. As Java has gotten built out, the default SDK has a huge number of packages. Can be overwhelming. Typically you don't need to know all or even most of these. But which should you know? Durney supplies one such choice of packages in his book. It does not cover those packages or classes involving elementary syntax. You should already have these down.
   
   Instead, he offers certain packages of high utility. Take the NumberFormat class as an example. It lets you control the number of digits in an output. Then there are the far more complex Date and Calendar classes. These deal with various different conventions for showing the date, as well as a host of language dependent issues. For example, in most of the world, a date is written in the format day-month-year. But the US uses month-day-year. So you might need to customise your displays accordingly. These classes are also deal with the non-metric nature of the many time divisions. As a programmer, you can use the classes instead of having to re-invent a lot of functionality.
   
   But the book's chapter on Applet usage may be less useful to many readers. As Java has developed, Applets have gotten steadily downplayed. Little serious programming appears to be done with these. Before some of you get irate and berate me, take a look at the latest Sun documentation. Sun has pushed Java steadily into server-side applications, where it is doing quite well.