NetBeans: The Definitive Guide
by Tim Boudreau, Jesse Glick, Simeon Greene, Vaughn Spurlin, Jack J. Woehr

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated March 19, 2004.


UNCONFIRMED  errors and comments from readers: 


(32)  2nd to last paragraph;
"If you click the little horizontal lever to the left of one of the Explorer's node
icons that happens to represent Java source+class, [...] illustrated in Figure 2-10."
Figure 2-10 show the runtime view and not a java+class node, and none of the nodes
are expanded. Perhaps this was meant to refer to figure 2-1 instead.


(57)  3rd paragraph;
In the section on Abbreviations, the last paragraph refers to figures 3-3 and 3-4.
Only figure 3-4 concerns abbreviations, however. Figure 3-3 has to do with updating
the parser database (nothing in the section on this refers to any figures).


(117) 
under "When to Use CVS" - change "It isa important" to "It is important"


(118) 
under "NetBeans and CVS" - change "project,C NetBeans" to "project, NetBeans"


[161]  Example 9-4;
Both setTetA and setTextB refer to a method
firePropertyChangeListenerPropertyChange(event) but the example provides no source
for that method.  It is in the examples along with the other PropertyChangeListener
methods that aren't in the example either.


(163)  Example 9-7;
The two lines in example 9-7:
  //jLabel1.setText(jTextField1.getTextSum());
should be changed to:
  //jLabel1.setText(jTextField1.getText() + jTextField2.getText());
according to what we wrote in example 9-3, p 159


(181) 
under "Browsing and Editing" - change "examinining" to "examining"


[182]  Figure 11-2;
Figure 11-2 is identical to Figure 11-1.  It should be a tree view of an XML document
with the "Inventory" DTD.


(201)  First paragraph, first sentence;
... by a special icon and the name of it's root folder in the...

The "it's" should be "its"


(238) midpage above "What Modules Can Do" - 
suggest adding reference to earlier example by changing "layer is fairly 
simple" to "layer is fairly simple (see Example 14-1)"


{254}  first paragraph;
The URL is resolved relative to the layer within the JAR


(284)  Code sample for performAction() under step 8;
The TopManager class has been replaced.
The code sample for the performAction() method should be as follows:
  NotifyDescriptor desc = new NotifyDescriptor.Message("Hello from a module!");
  DialogDisplayer.getDefault().notify(desc);


(284)  Item #7;
First, the jar file wasn't actually created automatically. I had to build it with
Build > Build. The jar file also didn't show the display name, just the package name:
com-newt-nbmodules-helloworld.

Then, when I executed the jar file as described, I got the following error message:

Failed to load Main-Class manifest attribute from
/home/bwohler/.9780596002800/exp/netbeans/modules/com-newt-nbmodules-helloworld.jar

I fixed this by viewing the properties of the jar file, and setting the Executor to
Install as Module.

NetBeans 3.6.


{319}  Figure 18-2;
The figure shows the class, fields and methods Nodes when -according to the code
provided- it should only display files and directories.