Errata

you forgot to update SessionContext and EJBContext Interfaces, in 3.1 there are additional methods wasCancelCalled() and getContextData() respectively.

@Stateless
public class A_Bean implements A_BusinessRemote {
@Resource private SessionContext context;
public void someMethod( ) {
B_BusinessRemote b = ... // Get a remote reference to B_Bean.
A_BusinessRemote mySelf = context.getBusinessObject(A_BusinessRemote.class);
b.aMethod( mySelf );
}
...
}

@Stateless(name = "EncryptionEJB")
@Local(EncryptionLocalBusiness.class)
@Remote(EncryptionRemoteBusiness.class)
public class EncryptionBean
{ ...

you don't need explicitly implements the businessinterfaces when you use @local and @remote

Text says a bean provider may optionally prohibit parallel invocations upon a particular stateful bean via the use of @javax.ejb.ConcurrencyManagement (with associated fig 7-4).

According to Java EE 6 API discussiong for this attribute
"This annotation may be applied to stateful session beans, but doing so has no impact on the semantics of concurrency management for such beans. The concurrency management type for bean-managed concurrency (BEAN) does not apply to stateful session beans."

[Original]

A bean provider may also optionally prohibit parallel invocations upon a particular stateful session via the use of @javax.ejb.ConcurrencyManagement (Figure 7-4).

[Correction]

A bean provider may also optionally prohibit parallel invocations upon a particular stateful session via the use of @javax.ejb.AccessTimeout (Figure 7-4).

[Original]

Figure 7-4. Concurrent requests upon the same session blocking until the session is available for use

[Correct]

Figure 7-4. Concurrent requests upon the same session throwing an exception without blocking

The same parameter connectionFactory is injected twice - which wont compile.

Is:
User user = getUser(); // Assume we have this from somewhere
...
MessageProducer producer = session.createProducer(topic);
ObjectMessage objectMsg = session.createObjectMessage();
// Error: ObjectMsg is the object we just created, hence should be lower case!
ObjectMsg.setObject(user);
// Error: We set out to create an objectMsg, so no point in sending a mapMsg, an object we do not have!
producer.send(mapMsg);

Should be:
User user = getUser(); // Assume we have this from somewhere
...
MessageProducer producer = session.createProducer(topic);
ObjectMessage objectMsg = session.createObjectMessage();
objectMsg.setObject(user);
producer.send(objectMsg);

Regards
Thomas

dave.setName(NAME_DAVE_NEW);
has absolutely no impact since it is run on the detached unmanaged object. Only
managedDave.setName(NAME_DAVE_NEW);
would be meaningful, in order to actually reflect this change to the EntityManager.

SELECT t
FROM Team AS t, IN (t.members) AS m, Employee AS e
WHERE
e = :myCustomer
AND
e MEMBER OF m.members

Is wrongly written. m in "IN (t.members) as m" resolves to *a* member not a collection of member's.

It should either be :

SELECT t
FROM Team AS t, Employee AS e
WHERE
e = :myCustomer
AND
e MEMBER OF t.members

or

SELECT t
FROM Team AS t, IN (t.members) AS m, Employee AS e
WHERE
e = :myCustomer
AND
e = m

The Code-Snippet will not work properly, in the case of an exception.
The finally-Block needs a second if-clause

finally
{
if (startOurOwnTx()) {
if (txManager.getStatus().equals(Status.STATUS_MARKED_ROLLBACK) ) {
txManager.rollback();
} else {
txManager.commit();
}
}
}

package org.ejb3book.annotations;
import java.lang.annotation.*;
@Target({ElementType.METHOD, ElementType.FIELD})
@Retention(RetentionPolicy.RUNTIME)
public @interface JndiInjected {
String value();
}


@Stateless
public class MySessionBean implements MySession {
@JndiInject("java:/TransactionManager")
private javax.transaction.TransactionManager tm;
...
}

The annotation declared is not the one used in the Bean Class. The one
used in bean class is not even declared.