Errata

Print Print Icon

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. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question



Version Location Description Submitted By Corrected
Printed Page xiv
2nd paragraph under "Software and Versions"

ftp://ftp.orielly.com/pub/examples/java/jms

has been changed to the HTML examples page:

http://www.oreilly.com/catalog/9780596000684/examples/index.html

 Anonymous  May 2001
Printed Page 3
Ack

Anonymous 
Printed Page 4
Ack

TO:

 Anonymous 
Printed Page 4
Ack

has been changed to:

 Anonymous  May 2001
Printed Page 6
Ack

Anonymous  May 2001
Printed Page 37
3rd Paragraph

if (deliverymode = javax.jms.DeviveryMode.PERSISTENT){

has been changed to:

if (deliverymode == javax.jms.DeviveryMode.PERSISTENT){

(Need a doulbe equals ("==") between the deliverymode and javax.jms.)

 Anonymous  May 2001
Printed Page 45
Line 13

The word "then" should be replaced by "than" in the sentence
"An online retailer wants to deliver a special catalog to any consumer that orders more then
$500.00 word of..."

 Anonymous 
Printed Page 50
middle

16-bit (4-byte)

has been changed to:

16-bit (2-byte)

 Anonymous  May 2001
Printed Page 53
Table 3-1

The types "Int" and "Long" should be lower case in the left column.

 Anonymous 
Printed Page 67
3rd paragraph

has been changed to:

"The publishPriceQuotes method of the Wholesaler class......"

Next paragraph now starts with:

"The onMessage() method of the Retailer class...."

 Anonymous  May 2001
Printed Page 85
3rd line from top

"a queue can be either a QueueConnection or a TopicConnection"

has been changed to:

"a connection can be either a QueueConnection or a TopicConnection"

 Anonymous  May 2001
Printed Page 100
Figure 6-1

Anonymous  May 2001
Printed Page 101
CHANGE figure 6-2

Anonymous 
Printed Page 112

The paragraph that reads:

"Unless you are doing a synchronous request-reply, you should avoid
grouping together a send followed by an asynchronous receive within a
transaction. There could be a long interval between the time a that a
message is sent and the related message is asynchronously received,
depending on failures or downtime of other processes that are involved. It
is more practical to group the receipt of a message with the send of
another message."

has been changed to:

"Grouping together a receive followed by a send within a single transacted
is useful. However, you should never group together a send followed by a
receive within a single transaction. If you are intending to do this in a
request-reply fashion, the result would be deadlock. The request message
will never get to the replier until the transaction is commited. The
requestor will wait indefinitely for a reply that will never arrive."

 Anonymous  May 2001
Printed Page 116, 117, 118
Code sample

In the Retailer example in chapter 6, a single line has been added.
At this location toward the middle of the file:

...
if( redelivered && inRollback ){ // at the end, start fresh
inRollback = false;
rollbackOnly = false;
session.commit(); <---- This is the added line
}
else if( rollbackOnly )
...

 Anonymous  Jan 2001
Printed Page 142
1st paragraph

"...and JNDI. are also..." should be changed to "...and JNDI are also..."

 Anonymous 
Printed Page 149
1st paragraph (below source code)

The word "pole" should be changed to "poll"

 Anonymous 
Printed Page 157
Last paragraph

The word "ans" should be changed to "and".

 Anonymous 
Printed Page 200

second to last line:

"flaot"

has been changed to:

"float"

last line on page 200:

float weight2 = message.getFloatProperty();

has been changed to:

float weight2 = message.getFloatProperty("Weight");

 Anonymous  May 2001