Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Upgrade and Migration Guide

- Previous: EJB 2.0 Container-Managed Persistence (CMP)
- Next: Migrating CMP Entity EJBs

# Migrating EJB Client Applications

This section includes the following topics:

- Declaring EJBs in the JNDI Context

- Recap on Using EJB JNDI References

## Declaring EJBs in the JNDI Context

In Sun Java System Application Server 8.1, EJBs are systematically mapped to the JNDI sub-context ejb/. If we attribute the JNDI name Account to an EJB, then Sun Java System Application Server 8.1 will automatically create the reference ejb/Account in the global JNDI context. The clients of this EJB will therefore have to look up ejb/Account to retrieve the corresponding home interface.

Let us examine the code for a servlet method deployed in Sun ONE Application Server 6.x.

The servlet presented here calls on a stateful session bean, BankTeller, mapped to the root of the JNDI context. The method whose code we are considering is responsible for retrieving the home interface of the EJB, so as to enable a BankTeller object to be instantiated and a remote interface for this object to be retrieved, in order to make business method calls to this component.

    /**
       * Look up the BankTellerHome interface using JNDI.
       */
    private BankTellerHome lookupBankTellerHome(Context ctx)
          throws NamingException
    {
        try
        {
          Object home = (BankTellerHome) ctx.lookup("ejb/BankTeller");
          return (BankTellerHome) PortableRemoteObject.narrow(home, BankTellerHome.class);
        }
        catch (NamingException ne)
        {
          log("lookupBankTellerHome: unable to lookup BankTellerHome" +
              "with JNDI name ’BankTeller’: " + ne.getMessage() );
          throw ne;
        }
    }

As the code already uses `ejb/BankTeller` as an argument for the lookup, there is no need for modifying the code to be deployed on Sun Java System Application Server 8.1.

## Recap on Using EJB JNDI References

This section summarizes the considerations when using EJB JNDI references. Where noted, the consideration details are specific to a particular source application server platform.

### Placing EJB References in the JNDI Context

It is only necessary to modify the name of the EJB references in the JNDI context mentioned above (moving these references from the JNDI context root to the sub-context ejb/) when the EJBs are mapped to the root of the JNDI context in the existing WebLogic application.

If these EJBs are already mapped to the JNDI sub-context `ejb/` in the existing application, no modification is required.

However, when configuring the JNDI names of EJBs in the deployment descriptor within the Sun Java Studio IDE, it is important to avoid including the prefix `ejb/` in the JNDI name of an EJB. Remember that these EJB references are automatically placed in the JNDI `ejb/` sub-context with Sun Java System Application Server 8.1. So, if an EJB is given to the JNDI name BankTeller in its deployment descriptor, the reference to this EJB will be translated by Sun Java System Application Server 8.1 into `ejb/BankTeller`, and this is the JNDI name that client components of this EJB must use when carrying out a lookup.

### Global JNDI context versus local JNDI context

Using the global JNDI context to obtain EJB references is a perfectly valid, feasible approach with Sun Java System Application Server 8.1. Nonetheless, it is preferable to stay as close as possible to the J2EE specification, and retrieve EJB references through the local JNDI context of EJB client applications. When using the local JNDI context, you must first declare EJB resource references in the deployment descriptor of the client part (`web.xml` for a Web application, `ejb-jar.xml` for an EJB component).

- Previous: EJB 2.0 Container-Managed Persistence (CMP)
- Next: Migrating CMP Entity EJBs

- © 2010, Oracle Corporation and/or its affiliates