J2EE™ Applications and BEA™ WebLogic Server™

EJB References

EJB components do not exist in a vacuum, and the business logic within EJBs often makes use of other EJBs deployed in the server. Normally, a client references another EJB by looking up the JNDI name where the EJB was deployed. It is undesirable to hard-code the JNDI name within the bean code because this limits the EJB's portability and reusability. One possible solution is to store the JNDI name as an EJB environment entry because this approach allows the names to be changed at deployment time without modifying the bean code. However, there is essentially no validation that can be performed on this JNDI name by the server's tools. For instance, the EJB server cannot validate that this JNDI name corresponds to an EJB of the appropriate ...