Errata

ffd

In the body of the first for loop, args[i] is used both to create the primary key,
the firstName AND the lastName of the customer. Not sure how useful and/or practical
this would be, even for the demonstration purposes.

the exception EJBException which is declared in the throws clause of
method setAddress is a RuntimeException and would not have to be
declared.

first line of the code:

public class CustomerBean inplements javax.ejb.EntityBean{

should be

public abstract class CustomerBean implements javax.ejb.EntityBean{

it lost the "abstract" modifier.

"...the RESERVATION_CUSTOMER_LINK table...

should be

"...the CUSTOMER_RESERVATION_LINK table..."

The remote interface returned by the findByPrimaryKey() method is ShipRemote, not
Ship.

The findByPrimaryKey() method should return ShipRemote, not Ship.

"the EntityContext.getPrimary() method..."

should be

"the EntityContext.getPrimaryKey() method..."

The line that reads:

throw new PaymentException("Expiration date has"+ " passed");

should probably just be:

throw new PaymentException("Expiration date has passed");

There doesn't appear to be any need to concatenate the two strings.
Perhaps there used to be a variable in there that was removed?

The code that parses the price should be:

double price = Double.valueOf(...).doubleValue();

instead of

double price = double.valueOf(...).doubleValue();

The valueOf() method is a static method of java.lang.Double.

There are two semicolons ending the line that reads:

PreparedStatement ps = null;;

javax.jta.UserTransaction does not exist!!!

It should be

javax.transaction.UserTransaction

see -
http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/transaction/UserTransaction.html

Need the following import statements in ReservationProcessorBean:

import javax.naming.Context;
import javax.naming.InitialContext;

QueueConnection connect = factory.createQueueConneciton should read
QueueConnection connect = factory.createQueueConnection

Minor typo - missing the "t" in the setStringProperty(...) method call

Monson-Haefel. In Chapter 14, "Transactions", on page 419, the last
sentence of the second paragraph in section "Balancing Performance Against
Consistency" reads

The Serializable isolation level ensures that data is never accessed
concurrently by transactions, thus ensuring that the data is always
consistent.

Actually, the meaning of "Serializable" is that the result obtained would be
as though the data were never accessed concurrently, even if in fact
concurrent access occurs. Where there is no conflict, such as the case when
all access is simply to read the database, then concurrent access is
allowed.

For example, if 50 processes read the same column from the same row, and no
updates occurred, then all 50 processes could read as concurrently as the
underlying hardware would allow, and Serializable access would be achieved.

See p. 40 of Java Enterprise In a Nutshell, which describes
TRANSACTION_SERIALIZABLE as follows:

..this level of isolation forces the database to treat transactions
as if they occurred one at a time. (emphasis added.)

Put another way, Serializable isolation can be obtained if read locks
prevent write locks, and write locks are serialized.

Your description could be called "Serialized" access. It's one way to
implement Serializable, but it's overkill.

HypotheticalBean should implement the SessionBean interface, not extend it.

for each BMT EJBs definition : it would be clearer to have the rollback statement in
the catch statement:
so
}catch(Exception e){
throw new EJBexception(e);
}
becomes:
}catch(Exception e){
ejbContext.getUserTransaction().rollback();
throw new EJBexception(e);
}

for the BMT examples, it should be the bean developer to decide to rollback the
transaction and not the client.

Schedule remote interface should extend javax.ejb.EJBObject, not implement it.

HypotheticalBean should implement the EntityBean interface, not extend it.

The variable 'CabinHome' should probably be 'CabinHomeLocal' since the code is
illustrating local interface not remote

The <role-source> elements all should be <relationship-role-source> elements, as
there is no <role-source> element

In the Figure B-4, the arrow for business method from EJB OBJ to Contianer should be
corrected from EJB Obj to "Bean Instance".

In Figure B-5 Data Sync Part,

ejbStore() should occures after business method.
So, READ before business method, and then Save it to DB again.