Errata

"Microsoft's MXSML [sic!] Parser [...]"

---> Must be "MSXML"

In the DTD,
<!ATTLIST chapter
title CDATA #REQUIRED
number CDATA #REQUIRED
>

should be

<!ATTLIST chapter
title CDATA #REQUIRED
label CDATA #REQUIRED
>
since in the contents.xml, chapter has an attribute called "label" and not "number".

instead of

'Notice the rather odd ... This construct generates a space between the word
"Chapter" and the chapter number (there is a single space ...'

it should be

'Notice the rather odd ... This construct generates a space between the dot after
chapter number and the chapter title (there is a single space ...'

URI stands for "uniform resource identifier", not "uniform resource indicator". In other words
not "indicator" but "identifier".

No error, just a comment.

You recommend the "contents.xml"-File here. But you don't give any hint that this is
already a very specialized XML-file for which the parser has to look up one or more
URL's on the internet for the namespace definitions.
I experienced the examples you provide won't work if
1) there's no connection to the internet
2) if you don't set the proxy settings if behind a firewall, e.g. if you didn't think
about using the -Dhttp.proxyHost and the -Dttp.proxyPort option when running the
example.

You should at least place a comment here for the users trying your xml examples the
first time. I guess there'll be a lot of readers running into the same problem, then
puzzling over the correct XML URI and wondering why they get a NoRouteToHost-
Exception.

You refer to the setSystemId() method as setSystemID() (note the capital "D" in
"ID"), which at least where the very latest Xerces parser is concerned throws a
complier error.

Wrong method name. The line should be changed from

inputSource.setSystemID(xmlURI);

to

inputSource.setSystemId(xmlURI);

changing DTD to <?xml version="1.2"?>

causes a fatal error....not a non fatal error

What is presented regarding the LexicalHandler is correct, but there is an omission, failing
to say that the lexical handler 'property' must be registered with the reader (filter), in
order to enable this handling. The same is true for the DeclHandler.

I didn't download the source from O'Reilly, but rather built the source by hand to get more
intimate with the individual steps outlined in the examples. But it required me to download
the source eventually in order to find this omission.

case Node.COMMENT_NODE:
writer.write(indentLevel + "< !--" +
node.getNodeValue() + "--> ");
writer.write(lineSeparator);
break;

should be:

case Node.COMMENT_NODE:
writer.write(indentLevel + "<!--" +
node.getNodeValue() + "-->");
writer.write(lineSeparator);
break;

The difference is there is an unwanted space around <!--> and <!-->. (shoud
be "<!--" not "< !-- " and "-->" not "--> ")

You should close the writer after use, eg. writer.close();.

At the end:

writer.write("<xml version="1.0">");

to:

writer.write("<?xml version="1.0"?>");

The lines:

System.out.println(" PUBLIC "" +
docType.getPublicId() + "" ");

should be:

writer.write(" PUBLIC "" +
docType.getPublicId() + "" ");

(Safari in 5.2.3.3) down near the bottom:

case Node.DOCUMENT_TYPE_NODE:
DocumentType docType = (DocumentType)node;
writer.write("<!DOCTYPE " + docType.getName( ));
if (docType.getPublicId( ) != null) {
System.out.print(" PUBLIC "" +
docType.getPublicId( ) + "" ");
} else {
writer.write(" SYSTEM ");
}
writer.write(""" + docType.getSystemId( ) + "">";
writer.write(lineSeparator);
break;

It's missing a parenthesis -

Original:
writer.write(""" + docType.getSystemId( ) + "">";
Corrected:
writer.write(""" + docType.getSystemId( ) + "">");

A File object called outputFile is declared at the beginning of the code block. A
functionally equivalent File object is declared in the added code at
serializer.serialize(doc, new File(outputFilename)); instead it should be
serializer.serialize(doc,outputFile);

The code example at the bottom of page 123 incorporates a try/catch block so that 'doc' is
only defined within the block. Consequently the reference to 'doc' outside the block on
the top of page 124 will fail to compile

The line which reads:

Text descriptionText = doc.createText(description);

Should read:

Text descriptionText = doc.createTextNode(description);

In the book You wrote:
root.removeChild(descriptionElement);

while in the code I downloaded from this site, at the following path:
9780596001971/ch06/src/javaxml2/UpdateItemServlet.java

the following code is shown:

// Remove and recreate description
Range range = ((DocumentRange)doc).createRange();
range.setStartBefore(descriptionElement.getFirstChild());
range.setEndAfter(descriptionElement.getLastChild());
range.deleteContents();

Which is the better solution?

The valueChanged function does not handle the special case when clicking on the
top node in the tree (containing the filename). Therefore a ClassCastException
occurs when trying to convert the String to a JDOMNode.

I used the following code instead, and this seemed to remove the problem:

public void valueChanged( TreeSelectionEvent e ) {
TreePath path = selectionModel.getLeadSelectionPath();
if( path != null ) {
Object selection = ((DefaultMutableTreeNode)path.getLastPathComponent()
).getUserObject();
if( selection instanceof JDOMNode ) {
buildXPath( (JDOMNode)selection );
}
}
}

[Note: I used the Text class instead of String in the TextNode class. But I don
't think this caused any side effects. ]

Checking the JavaDoc and class files, I can find no parse() method for
javax.xml.parsers.DocumentBuilder taking an InputStream and HandlerBase as
parameters. In fact, I can find no parse() method which takes a HandlerBase
parameter at all. I question the code below which looks like a SAXParser.parse()
invocation (see pp. 226-227):

// Use an InputStream
Document doc = builder.parse(myInputStream, myHandlerBaseInstance);

I did find two overloaded DocumentBuilder.parse() methods taking an InputStream as
a parameter and returning an org.w3c.dom.Document:

Document parse(InputStream is)

and

Document parse(InputStream is, String systemID)

Using setErrorListener() on the TransformerFactory DOES NOT set you up for dealing
with errors that occur during transformation. The error event listener for the
TransformerFactory is used for the processing of transformation instructions, and
not for the transformation itself.

Using setErrorListener() on the Transformer DOES set you up for dealing with errors
that occur during transformation. You must first obtain the Transformer from the
TransformerFactory.

It is interesting to note that the ErrorListener interface parameter is the same for both.

There is no setErrorResolver() method for the TransformerFactory.
We might however, code as follows:

// Configure the factory
factory.setErrorListener(myFactoryErrorListener);
factory.setURIResolver(myURIResolver);

// Get a transformer to work with
Transformer transformer =
factory.newTransformer(new StreamSource("foundation.xsl"));
transformer.setErrorListener(myTransformerErrorLstener);

missing a '>' at the <xls:processing-instruction> tag.

Simple minor trouble.

I have the June 2000 printing of the book. As the text on the page says this book is
not about threading, but it does appear that the code has a thread error. The code
reads:

public boolean addEvent (String eventName, Date evenTime) {
// Add this event to the list of events
if (!events.contains(eventName)) {
events.addElement(eventName);
eventDetails.put (eventName, eventTime);
eventsSorted = false;
// Start thread on server sorting
SortedEventsThread sorter = new SortEventsThread();
sorter.start();
}
}

The code for sorting is on pages 299-300. I don't reproduce it all here, but the
pseudo-code is as follows:

private synchronized sortEvents() {
if (eventsSorted) {
return;
}
String eventNames[] = new String [events.size()];
events.copyInto(eventNames);

// sort eventNames
Vector sortedEvents = new Vector();
// copy eventNames into sortedEvents
events = sortedEvents;
eventsSorted = true;
}

The trouble seems to me that addEvents() is not synchronized. This could lead to the
following scenario:

reployment command line reads

(gandalf)/9780596001971/Ch12$ java org.apache.soap.server.ServiceManagerClient
http://localhost:8080/soap/servlet/rpcrouter xml/CDCatalogDD.xml

but it should contain the delopyment parameter, so should read

(gandalf)/9780596001971/Ch12$ java org.apache.soap.server.ServiceManagerClient
http://localhost:8080/soap/servlet/rpcrouter deploy xml/CDCatalogDD.xml