Errata

Web Services Essentials

Errata for Web Services Essentials

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page 00
import statements

In the source code for the XML-RPC examples, the import statements have the text
"helma" when it should be "org.apache", as in the book.

 Anonymous   
Printed Page ix
2 nd paragraph - Audience

There is two time the work "to" in page ix (Preface):

Audience
This book... It aims to
to provide...

 Anonymous   
Printed Page x
(Organization)

1 first Paragraph -> "The" book ... (suggestion: I think that is best use the word
"This")

 Anonymous   
Printed Page xii
4 rd paragraph

For more information "abut" this book...

I think that is "about"

 Anonymous   
Printed Page 6
Web Services and the Semantic Web text box

The URL for the 2001 Scientific American Tim Berners-Lee article is outdated and should be:

http://www.sciam.com/article.cfm?id=the-semantic-web

 Anonymous   
Printed Page 6
Web Services and the Semantic Web text box

The URL for the 2001 Scientific American Tim Berners-Lee article is outdated and should be:

http://www.sciam.com/article.cfm?id=the-semantic-web

 Anonymous  Jun 18, 2008 
Printed Page 11-13
Example URLs for IBM Web Services are in error.

IBM has changed its web services demo. I believe it is no longer available as set
forth in the text.

See: http://www.alphaworks.ibm.com/

 Anonymous   
Printed Page 11
1st paragraph

The given URL is invalid:
http://demo.alphaworks.ibm.com/browser/

 Anonymous  Nov 08, 2008 
Printed Page 18
2nd paragraph

The references to the UDDI Business Registry are out of date, as this was shut down in January 2006 (http://uddi.microsoft.com/about/FAQshutdown.htm)

 Anonymous   
Printed Page 18
2nd paragraph

The references to the UDDI Business Registry are out of date, as this was shut down in January 2006 (http://uddi.microsoft.com/about/FAQshutdown.htm)

 Anonymous  Jun 18, 2008 
Printed Page 19
Final paragraph

The RESTWiki URL is no longer at internet.conveyor.com but at http://rest.blueoxen.net/

 Anonymous   
Printed Page 19
Final paragraph

The RESTWiki URL is no longer at internet.conveyor.com but at http://rest.blueoxen.net/

 Anonymous  Jun 18, 2008 
Printed Page 20
SOAP over BEEP URL

The SOAP ove BEEP URL is no longer at http://beepcore.org/beepcore/docs/beep-soap.jsp but at http://beepcore.org/docs/rfc3288.html

 Anonymous   
Printed Page 20
SOAP over BEEP URL

The SOAP ove BEEP URL is no longer at http://beepcore.org/beepcore/docs/beep-soap.jsp but at http://beepcore.org/docs/rfc3288.html

 Anonymous  Jun 18, 2008 
Printed Page 25
1 first paragrah

... Web Services Activity. The new Activity adds Working Groups for Web Services
"Architecutre" and Web Services Description.

I think that is Architecture!

 Anonymous   
Printed Page 37
2nd listing

The description of the Host header is misleading. According to section 14.23 of RFC
2068, the HTTP/1.1 standard, Host referers to the (perhaps virtual) host receiving
the HTTP request, not making it.

 Anonymous   
Printed Page 39
4th line from top of page

<value><int>26</int>

should be

<value><int>26</int></value>

 Anonymous   
Printed Page 44
2nd paragraph

The last sentence in the paragraph says that the XML-RPC code which follows is a
response when in fact it is a request

 Anonymous   
Printed Page 51
Diagram at top

Shouldn't the box on the right be labeled "SOAP server"
as opposed to client? Great book by the way!!!

 Anonymous   
Printed Page 66
last paragraph

The section on setting the classpath for tomcat is correct only for tomcat 3.2.
These instructions do not help with tomcat 3.3. tomcat 4.0 is also coming soon...

 Anonymous   
Printed Page 71-72
Listing of HelloClient.java

I don't have SAX and I don't have DOM installed on my laptop. I unzipped the
examples and compiled HelloServer.java and HelloClient.java without errors. When I
run the command "java com.ecerami.sopa.HelloClient.java Jim" I the first line that
comes back is correct, "Hello SOAP Client", but then I get two lines of
java.lang.NoClassDefFoundError errors because "org.w3c.dom.Node" was not found at
"getGreeting" (line 53) und "main" (line 33). It looks to me, as if I need the DOM
API installed and included in the HelloClient.java program.

 Anonymous   
Printed Page 74
1st paragraph, 4th bullet

If the encoding style argument is set to null, the parameter will use the
encoding style of the Call object, not the Class object as stated.

 Anonymous