2
Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0
java -classpath %CLIENTCLASSES%;%CLASSPATH%
examples.ejb.basic.statelessSession.Client
This command ensures that the EJB interfaces are referenced in your client's
classpath.
Steps for Converting an EJB 1.1 to an EJB 2.0
To convert an EJB 1.1 bean to an EJB 2.0 bean, you can use the WebLogic Server
DDConverter utility.
BEA Systems recommends that you develop EJB 2.0 beans in conjunction with
WebLogic Server 7.0. For 1.1 beans already used in production, it is not necessary to
convert them to 2.0 beans. EJB 1.1 beans are deployable with WebLogic Server 7.0. If
you do wish to convert 1.1 beans to 2.0 beans, see the
Programming WebLogic Enterprise JavaBeans for information on how to do this
conversion.
The basic steps required to convert a simple CMP 1.1 bean to a 2.0 bean are as follows:
1. Make the bean class abstract. EJB 1.1 beans declare CMP fields in the bean. CMP
2.0 beans use abstract
Beans will use
String getName()
this modification, the bean class should now read the container-managed fields
with the
2. Any CMP 1.1 finder that used
java.util.Collection.
java.util.Enumeration
public Enumeration findAllBeans()
becomes:
public Collection findAllBeans()
2-22
BEA WebLogic Server 7.0 Upgrade Guide
getXXX
public String name
and
public abstract void setName(String n)
method and update them with the
getName
Throws FinderException, RemoteException;
Throws FinderException, RemoteException;
and
methods for each field. For instance, 1.1
setXXX
. 2.0 Beans should use
java.util.Enumeration
CMP 2.0 finders cannot return
. Change your code to reflect this:
DDConverter
documentation in
public abstract
method.
setName
should now use
. With
Need help?
Do you have a question about the WebLogic Server 7 and is the answer not in the manual?