Errata
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
| Version |
Location |
Description |
Submitted By |
| Printed |
Page xiii
5th paragraph, line 2 |
says:
book happen
should be:
book to happen
|
Anonymous |
| Printed |
Page 1
Entire Book |
I tried several examples in the book, but the web services do not seem to be hosted
there anymore. The examples are less useful than they could be. The author should
make the server code for these samples available, so the examples could actually be
run. Otherwise, maybe the author could find more stable web services, like
governmental or standards organizations?
|
Anonymous |
| Printed |
Page 28
paragraph 3, line 1 |
Just a suggestion...
where it says "at once"
change to "both"
or perhaps just remove "at once"
|
Anonymous |
| Printed |
Page 30
Example 2-3 |
<element name ="code" type="CodeModule">
should be
<element name ="code" type="SoftwareModule">
since that is the name of the complex type defined earlier in the example.
|
Anonymous |
| Printed |
Page 30
Example 2-3 |
<element name ="code" type="CodeModule">
should be
<element name ="code" type="SoftwareModule">
since that is the name of the complex type defined earlier in the example
|
Anonymous |
| Printed |
Page 40
1st paragraph |
line 5: content-encoding
line 7: content encoding
RFC 2616 refers to the "Content-Encoding" entity-header field. Which leads to some
ambiguoity. It is quite possible on line 5 where the text reads:
"chunked" content-encoding
should read: "chunked" Content-Encoding
|
Anonymous |
| Printed |
Page 47
Example 3-8, line -5 |
says -
resolve_name
should be -
get_data
|
Anonymous |
| Printed |
Page 52
paragraph 3 |
As of February 11, 2003 RPC::XMLSimple is still not available on CPAN. In order to
make Example 4-1 work on page 53:
change
RPC::XMLSimple::Client
to
Frontier::Client
Eventually our mystery maintainer of RPC::XMLSimple will release something to CPAN
(one would hope), and this passage won't need to be updated.
|
Anonymous |
| Printed |
Page 57
Example 4-3 |
Until Frontier is renamed RPC::XMLSimple, Example 4-3 must be modified as follows:
"use RPM::XMLSimple::Daemon;"
changes to
"use Frontier::Daemon;"
"RPC::XMLSimple:Daemon->new(" (also incorrect due to missing second colon before Daemon)
changes to
"Frontier::Daemon->new("
|
Anonymous |
| Printed |
Page 186
2/3 of the way down |
The line
<soap:operation soapAction="urn:/WishListCustomer">
should read
<soap:operation soapAction="urn:/WishListCustomer" />
|
Anonymous |
| Printed |
Page 203
2nd para, 3rd line |
soap:address
s/b:
http:address
|
Anonymous |
