Справочник Пользователя для BEA 7

BEA WebLogic Server 7.0 Upgrade Guide

The EJB 2.0 specification has changed substantially between WebLogic Server 6.0 
and WebLogic Server 7.0, and somewhat between WebLogic Server 6.1 and 
WebLogic Server 7.0. 

Some of the prominent changes are listed here. To see a complete listing of the 
specification changes from WebLogic Server 6.0 to WebLogic Server 7.0, you can 
view and download the 

 at 

http://java.sun.com/products/ejb/2.0.html.

For more information about the changes between WebLogic Server 6.0 and WebLogic 
Server 6.1, see 

 in Introducing WebLogic 

Server Enterprise JavaBeans in the WebLogic Server 6.1 documentation. EJB 1.1 
beans that worked in WebLogic Server 6.x should work just as well in WebLogic 
Server 7.0 with no alteration.

You may have to make the following changes to EJB 2.0 beans:

„

If your deployment descriptor contains a 6.0 element that has a different name in 
7.0, you have to manually change the name in your deployment descriptor. The 
following are some examples of element names that you may need to change in 
7.0:

z

In 7.0, the name of the element that is used to identify a particular EJB that 
participates in a relationship is 

relationship-role-source

. In 6.0, the 

element name was 

role-source

.

z

In 7.0, the name of the element that specifies whether the destination is a 
queue or a topic is 

destination-type

. In 6.0, the element name was 

jms-destination-type

.

z

In 7.0, the name of the element that specifies whether the destination is a 
queue or a topic is 

run-as

. In 6.0, the element name was 

run-as-specified-identity

.

„

In 7.0, 

EJB-QL

 queries require a 

SELECT

 clause.

„

All EJB 2.0 CMP beans must have an 

abstract-schema-name

 element 

specified in their 

ejb-jar.xml

 in WebLogic Server 7.0.

Other major changes that resulted from the EJB 2.0 specification changes are as 
follows: