Configuring a Stateless Session bean
With the code compiled, the next step is to deploy the bean onto the EJB container.
As you saw yesterday, EJBs are designed to be portable across EJB containers, and the configuration information that defines the bean's name, interfaces, classes, characteristics, dependencies, and so on, is stored in an XML document called a deployment descriptor. This is provided along with the bean code itself.
As you appreciate from Day 2, there are several EJB roles involved in building a deployment descriptor. The bean provider specifies the information about a given bean (“intra-bean” configuration information, if you like), and the application assembler specifies the information about all the beans in an application ...