Not an error, per se, but there is an alternate solution to the puzzle:

class PoolPuzzleOne {
public static void main(String[] args) {
int x = 0;

while (x < 4) {
System.out.print("a");
if (x < 1) {
System.out.print(" ");
}
System.out.print("n");
if (x < 1) {
System.out.print("oise");
x = x - 1;
}
if (x == 1) {
System.out.print("noys");
}
if (x > 1) {
System.out.print(" oyster");
}
System.out.println("");
x = x + 2;
}
}
}

There is the common misconception of a blueprint once again.
Most believe that "blueprint" stands for the original when it is actually the opposite.

Original drawings where made on semi-transparent film (frosted film). When making copies to paper you use light-sensitive
paper the same size as the original. You place the original on top of the paper and insert into a giant exposure machine.
The result is a paper drawing with blue lines and blueish background.

So you see the blueprint is actually the instance object and not the class.

The error is one of omission:

While the solution is **a** possible solution to the puzzle, there are others. Lines
11 and 14 as printed read
if ( x == 3 ) {
and
if ( x < 0 ) {

Other solutions include
(A)
if ( x > 0 ) {
and
if ( x > 1 ) {

(B)
if ( x == 4 ) {
and
if ( x < 5 ) {

However, only (A) also solves the bonus question.

The problem in the exercise is to find the code which will give compilation errors by
the compiler. However the problem B is fine for the compilation. The error mentioned
in the exercise solution, i.e the ArrayIndexOutOfBoundsException is a runtime
exception, which will never be caught by the compiler.

The statement x=6; is superfluous. After the while loop, x is already 6.

The output of running "java SimpleDotComTestDrive" should read:

hit
passed

instead of just "hit"

Maybe not a mistake - since variable isAlive is a boolean I would write:

while(isAlive) {

instead of

while(isAlive == true) {

The line reads:

String [] alphacoords = new String [comSize]; // holds 'f6' type coords

The local string array "alphacoords" appears nowhere else in the placeDotCom method.
I suspect the comment regarding 'f6' coords belongs with the preceding line:

ArrayList<String> alphaCells = new ArrayList<String>();

These six lines that test for a valid cell position:

if (location >= gridSize) { // out of bounds - 'bottom'
success = false; // failure
}if (x>0 && (location % gridLength==0)) { //out of bounds - right edge
success = false; // failure
}

are unnecessarily restrictive and therefore inefficient. Cells are often falsely
rejected. In order to not restructure the code any more than absolutely necessary
these six lines can be replaced by the following - admittedly complex - line.

// Disallow running off edge:
success = !((x < 3) && ((location >= gridSize) || ((incr == 1) && (location %
gridLength == 0))));

The answer to the first question is missing "protected" which is a perfectly valid
access modifier for a constructor. (this should also reference appendix B).

the sentence 'there is no other way to create an object other than someone, somewhere
saying new on the class type' is not correct - objects can also be created by
deserialization and cloning. Josh Bloch calls these 'pseudo-constructors' in
'Effective Java'.

roll(int field, boolean up)

-- It might be clearer to use the other overloaded version of this method, namely:

roll(int field, int amount)

That's the one that was used on the previous page, i.e., "c.roll (c.DATE, 35);".

Close parenthesis missing for the "catch block".

this code fragment should read:

public void crossFingers() {
try {
anObject.takeRisk();
} catch (BadException ex) {
System.out.println("Aaargh!");
}
}

Note the addition of the next-to-last close parenthesis...

The code as it is does work, but after it is finished something stays active because the player is not stopped when finished.
This can be solved by inserting the following code between "player.start();" and "} catch ...":

long length = player.getTickLength();
Thread.sleep(length*200);
player.close();

This happens at least another time in a similar piece of code on another page.

graphics.setColor(Color.blue);
should be:
g.setColor(Color.blue);

g.fillRect is called with height and width reversed - should be:

g.fillRect(x, y, width, ht);

Call to sequencer.setTempoInBPM(120) should probably be done before
sequencer.start().

In the method setUpGui() I am missing the middle line of the next three lines:

f.setContentPane(m1);
f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
f.setBounds(30, 30, 300, 300);

And near the end of the page I am missing

long length = (long) (sequencer.getMicrosecondLength()/1000);
Thread.sleep(length);

sequencer.close();

as well, between "sequencer.setTempoInBMP(120);" and "} catch...".

reads: theFrame = new JFrame("Cyber Beatbox");

Compiler rejects this. It works as:
JFrame theFrame = new JFrame("Cyber Beatbox");

In the main method it says "new BeatBox2().buildGUI();". The "2" should not be there.

On my system: Windows Vista, Java 1.6.03, Java SE RE 1.6.03-b05, these programs do not release the CMD prompt on close.

I fixed it by adding:

abstract class MyExitListener implements WindowListener {

public void windowClosing(WindowEvent e) {
sequencer.stop();
}
}

as an inner class. Maybe there's a better way?

JCheckBox jc = (JCheckBox) checkboxList.get(j + 16*i);
may be changed to:
JCheckBox jc = checkboxList.get(j + 16*i);

The "(JCheckBox)" cast is superfluous.

The contents of the command window should be changed from:

% java GameSaver
Elf
Troll
Magician

to:

% java GameSaverTest
One's type: Elf
Two's type: Troll
Three's type: Magician

Format of UML-like diagram for QuizCard class has had no prior explanation of the
components and does not correspond to similar example on page 255 (which is also
presented without explanation).

JFileChooser fileSave = new JFileChooser();
fileSave.showSaveDialog(frame);
saveFile(fileSave.getSelectedFile());

could potentially benefit from an added conditional test:

JFileChooser fileSave = new JFileChooser();
fileSave.showSaveDialog(frame);
if (fileSave.getSelectedFile() != null)
saveFile(fileSave.getSelectedFile());

This will prevent the java.lang.NullPointerException which results
from cancelling out of the file chooser dialog.

private JTextArea answer is declared but never used in the class.

The phone has little bubbles coming out if it like it's going to say something, but
there's no thought bubble.

I'm confirming that "balance++" is not atomic, and here's why:
the corresponding assembly langugage (which is what is being run) is not.

Pegagogically, though, it may be helpful to represent this as 2 statements. But if you do, I suggest a note explaining that the ++ operator is not atomic.

Printed: "It uses a naming convention that is the name of your remote implementation, with either _Stub or _Skeleton added to the end."

Correction: Printed: "It uses a naming convention that is the name of your remote implementation, with either _Stub or _Skel added to the end."

Naming.rebind("Remote Hello", service)
s/b
Naming.rebind("RemoteHello", service)

The space is not allowed - executing javac MyRemoteImpl with the space results in an
error. See also page 621, and remove the space from
Naming.lookup("rmi:127.0.0.1/Remote Hello");