Errata

The word applicatation (vs. application) is misspelled in the last line beginning with "Once the..."

Note from the Author or Editor:
Last line on page 6:

The word "applicatation" should be "application"

MIME = Multipurpose Internet Mail Extensions

Note from the Author or Editor:
Page 12, 2nd bullet: the definition of MIME in the bullet is wrong. The
current text is

...with a MIME (Multiple Internet Mail Extension)...

It should be changed to

...with a MIME (Multipurpose Internet Mail Extensions)...

The class QName belongs to java[b]x[/b].xml.namespace, not java.xml.namespace.

Note from the Author or Editor:
On p. 14, 1st paragraph, the fully qualified name should be

javax.xml.namespace.QName

instead of

java.xml.namespace.QName

Appearing twice.

1st, in the line of code:

TimeServer port = service.getPort(TimeServer.class);

is referred to in the preceding line as the statement of interest. However; the example to which this line is referring is Example 1-9 from the previous page which uses 'eif' for the variable name instead of 'port'.

The line of code should read:

TimeServer eif = service.getPort(TimeServer.class);

2nd, in the 4th sentence.

"The port object reference..."

should read:

"The eif object reference..."

with 'eif' in bold.

Note from the Author or Editor:
On page 14, two changes:

The indented code line in roughly the middle of the page is

TimeServer port = service.getPort(TimeServer.class);

It should be

TimeServer eif = service.getPort(TimeServer.class);

So "TimeServer port = ..." should be "TimeServer eif = ...".

The 2nd change is in the immediately following paragraph, last word in 3rd line:

...operations. The port

should be

...operations. The eif

The "eif", like the "port" it replaces, should be in bold typeface.

The referenced wsimport-generated class, "client.TempServerImplService", should have been "client.TimeServerImplService ".

Note from the Author or Editor:
Page 34, last line:

client.TempServerImplService

should be

client.TimeServerImplService

So "Temp" should be "Time" and all else remains the same.

The paragraphs on page 39, beginning at "The TimeServer service
can be changed to a document-style service ..." to the beginning
of the next subsection "Key Features of Document-Style Services"
seem to contain six related typos.

Given, that "chapter2/ch02/tsd" (note the trailing "d") in the
source code distribution contains the code for subsection "A
Closer Look at WSDL Bindings", then, the content of "chapter2/ch02/tsd" needs a few rectifications.

--- Rectifications in "chapter2/ch02/tsd":
The current file "ch02.tsd.TimeServer.java" is not the SEI but
the SIB, since it contains a class and not an interface.
The SEI is missing. Solution:

1. Rename "ch02.tsd.TimeServer.java" to "ch02.tsd.TimeServer-
Impl.java" (SIB) and change "class TimeServer" to "class
TimeServerImpl" in the new file.
2. Copy "ch01.ts.TimeServer.java" from "chapter1" to "ch02.tsd-
.TimeServer.java" (SEI) and change "package ch01.ts" to
"package ch02.tsd" in the new file.
3. In the Endpoint-Publisher "ch02.tsd.TimeServerPublisher.java"
change "new TimeServer()" to "new TimeServerImpl()".

The wsgen utility know works and generates four source and four
compiled files in the "jaxws" subdirectory.

--- Six related typos (change package infix "ts" to "tsd"):
+ "... in the SEI source, ch02.tsd[not "ts"].TimeServer.java,
before recompiling."
+ "The package has been changed from ch01.ts to
ch02.tsd [not "ts"] to reflect that this is Chapter 2."
+ "% wsgen -keep -cp . ch02.tsd[not "ts"].TimeServerImpl"
+ "The wsgen utility then ... in the subdirectory
ch02/tsd[not "ts"]/jaxws."
+ "... at the published URL
http://localhost:9876/tsd[not "ts"]?wsdl."
+ "...: the package name changes from ch01.ts to
ch02.tsd[not "ts"], ..."

Note from the Author or Editor:
On page 39, the package name

ch02.ts

should be

ch02.tsd

The closing tag of the num2 parameter in boch the wrapped and unwrapped sample should be </num2> instead of </num1>.

Note from the Author or Editor:
In Example 2-8 on p. 44, the 8th line

...>94</num1>

should instead be

...>94</num2>

On the same page in Example 2-9, the 8th line

<num2>94</num1>

should instead be

<num2>94</num2>

"XSD's message section" should be "WSDL's message section".

Note from the Author or Editor:
1st full paragraph, 2nd sentence should read:

Here is a segment from the WSDL's message section...

Right now it has "XSD's" instead of "WSDL's"

In the sentence "Here is the call to invokeSearch in the simplified client", invokeSearch should be itemSearch.

Note from the Author or Editor:
In the sentence "Here is the call to invokeSearch in the simplified client", the term "invokeSearch" should be "itemSearch".

First sentence describes custom.xml as having a

Note from the Author or Editor:
Page 54, end of 1st sentence. The last word in the sentence is "true" but should be "false" --- and the typeface should remain monospace.
This is immediately above Example 2-15.

"The maximam value of the Java..." should be "The maximum value of the Java..."

Note from the Author or Editor:
Page 67, 2nd full paragraph, last sentence:

"The maximam value..." should be "The maximum value..."

In short, "maximum" is misspelled as "maximam."

In the 4th line: ?? important namespace URI is the same in both: http://ts.ch01.? ? missing slash at the end. It should be ?? in both: http://ts.ch01/.?

Note from the Author or Editor:
P. 67, 1st full paragraph, 4th line:

...is the same in both: http://ts.ch01. In the SOAP...

should be

...is the same in both: http://ts.ch01/. In the SOAP...

There is a comma missing in "Universal Description Discovery and Integration"; it should be "Universal Description, Discovery and Integration".

Note from the Author or Editor:
"Universal Description Discovery and Integration" should be
"Universal Description, Discovery, and Integration"

On several places, "uddi" is used instead of "uuid" to refer to the header block. An understandable typo in this context!

Note from the Author or Editor:
"uddi" should be replaced by "uuid" on p. 83.

Instead of "uuid", "uddi" is used (3 times) to refer to the header block. An understandable typo in the context of web service!
The next page (84) also has this typo (1 time).

Note from the Author or Editor:
On p. 83, the acronym UDDI (in lowercase and in uppercanse) should be
replaced by UUID (maintaining case in the replacement). The first time
is right above Example 3-1: "uddi" should be "uuid".
The second time is right after the example: "uddi" should be "uuid".
The last time is the 3rd sentence after the example: "UDDI" should be
"UUID".

On page 84, 1st sentence, "uddi" should be "uuid".

SOAPMessageHandler and LogicalMessageHandler should be SOAPHandler and LogicalHandler, respectively. The next page (102) has the same typo in the first paragraph.

Note from the Author or Editor:
p. 101, last paragraph:

Replace "SOAPMessageHandler" with "SOAPHandler"

Replace "LogicalMessageHandler" with "LogicalHandler"

UUIDValidator (i.e. the server-side handler) should be changed into UUIDHandler (i.e. the client-side handler).

Note from the Author or Editor:
p. 103, 1st line: replace "UUIDValidator" with "UUIDHandler"

LogicalMessageMessageContext should be LogicalMessageContext.

Note from the Author or Editor:
4th line from top: "LogicalMessageMessageContext" should be
"LogicalMessageContext"

The code in my copy of the book (Feb 2009 1st edition) and in the accompanying jar file (jwsur_code.jar) downloaded from oreillynet.com is different, and neither version gives me the expected result.

Using the code from the book (apologies if I've missed anything in transcription, I've double-checked) gives an exception: "javax.xml.transform.TransformerException: Extra illegal tokens: '(', '1', ')', '/', 'urn:yahoo:yn', ':', 'Title'"

Using the downloaded code produces ten identical result lines (save for the line number given by variable i) on the console.


The following amendment worked for me, though there's probably a better way (NB - had to import org.w3c.dom.Node to make this work):

int len = resultList.getLength();
for (int i = 0; i < len; i++) {


Node thisResultNode = resultList.item(i);

NodeList thisResultNodeChildren = thisResultNode.getChildNodes();
String title = thisResultNodeChildren.item(0).getFirstChild().getNodeValue();
String click = thisResultNodeChildren.item(3).getFirstChild().getNodeValue();

System.out.printf("[%d] %s\n", (i + 1), title + " - " + click);

}

Note from the Author or Editor:
I've contacted the reader directly. My code runs as advertised.

The code in display at the top of p. 169 is wrong. The code in the book shows

String title =
xp.evaluate("/yn:ResultSet/yn:Result(" + i + ")/yn:Title",
dom_result.getNode());

but should show

String title =
xp.evaluate("/yn:ResultSet/yn:Result[" + i + "]/yn:Title",
dom_result.getNode());

This occurs twice in the code display. In summary, there should be square brackets [ ] rather than round brackets ( ) in the segment

...:Result[" + i + "]...

SRP is expanded as Secure Remote Protocol, but per http://srp.stanford.edu/ it is Secure Remote Password.

Note from the Author or Editor:
Page 199, third line from bottom:

(Secure Remote Protocol) should be (Secure Remote Password protocol)

Last sentence reads: "In development phase, however, it may be useful to turn off validation because, for example, the truststore has does not contain the appropriate certificates".

Should perhaps be:

"In the development phase, however, it may be useful to turn off validation because, for example, the truststore does not contain the appropriate certificates".

Note from the Author or Editor:
P. 201, last sentence:

In development phase,...

should be changed to

In the development phase,...

The last line

% wsimport -keep -p clientC...

should be

% wsimport -keep -p teamsC...

So the package for the client artifacts should be teamsC rather than clientC.

on page 256, line 8: It says "EBJ-Based" in the paragraph heading. I think it should have been "EJB-Based" instead.

Note from the Author or Editor:
On p. 256, the header on line 8

The Endpoint URL for an EBJ-Based Service

should be

The Endpoint URL for an EJB-Based Service

In short, "EBJ" should be "EJB".

"Transparent XML sounds like an empty slogan only to someone who has not had to deal directly with large and complicated XML documents."

If you have not dealt with complicated XML documents, would you not consider the slogan to be sensible and correct, i.e. non-empty? In other words, shouldn't the sentence be something more along the lines of:

"Transparent XML is nothing but an empty slogan to everyone who has had to deal directly with large and complicated XML documents."

Note from the Author or Editor:
P. 288, 2nd paragraph in SOAP and REST in Harmony section, last sentence:

The sentence

Transparent XML sounds like...

should be changed to

Transparent XML is nothing but an empty slogan to everyone who has had to deal directly with large and complicated XML documents.

The "Transparent XML" should still be in in italics.

Note from the Author or Editor:
p. 288, last sentence, 4th paragraph from top:

"XML dcouments" should be "XML documents"

So the word "documents" is misspelled.