Head First EJB

But it’s not per bean instance... It’s per bean home

The scope of a bean’s environment is for all beans from the same home. If you deployed a particular bean type into your server three times, each of the three deployments would have it’s own unique home, so there’d be three different environments.

All beans from the same home have the same environment

Environment subcontexts

in a bean’s business method:

Brain Power

How can we deal with this? How does the programmer hard-code a lookup String like “java:comp/env/jdbc/CustomerDB” without knowing how the database was configured into the server?

(hint: how did we deal with it earlier when the Bean Provider used programmatic security with isCallerInRole(“someRole”)?)