Web Services Essentials Distributed Applications with XML-RPC, SOAP, UDDI & WSDL By Ethan Cerami 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 : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification This page was updated April 19, 2007. UNCONFIRMED errors and comments from readers: {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. (ix) 2 nd paragraph - Audience; There is two time the work "to" in page ix (Preface): Audience This book... It aims to to provide... (x) (Organization): 1 first Paragraph -> "The" book ... (suggestion: I think that is best use the word "This") (xii) 4 rd paragraph; For more information "abut" this book... I think that is "about" {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/ (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! {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. {39} 4th line from top of page; 26 should be 26 {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 (51) Diagram at top; Shouldn't the box on the right be labeled "SOAP server" as opposed to client? Great book by the way!!! [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... [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. (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.