Head First EJB

Deployer responsibility for the Deployment Descriptor

Modifications to Bean Provider information:

• ensure legal values for all environment entries

Other tasks related to the deployment descriptor. All are done in a vendor-specific tool and NOT a part of the ejb-jar deployment descriptor:

SECURITY

• assign of the security domain and principal realm to the app

• assign principals and/or groups to security roles, but NOT the security role references.

• principal delegation for inter-component calls (i.e. configuring the run-as principal).

RESOURCE MANAGER CONNECTION FACTORIES

• binding of resource manager connection factory references to an actual resource manager connection factory in the operational environment

• configuration sign-on info for container-authorized resource access.

EJB REFERENCES

• ensure that all EJB references are bound to the homes of beans that exist in the operational environment

• ensure that the target bean is type-compatible with the types declared in the EJB reference.

RESOURCE ENVIRONMENT REFERENCES (JMS topic or queue)

• ensure that all declared resource references are bound to objects that exist in the operational environment, and ensure that the target object is type-compatible with the declared type

Note

The Deployer does things using vendor-specific tools

You might see a question about the deployer and things related to the deployment descriptor and think: “The deployer isn’t supposed ...