BEA WebLogic Server 7 Upgrade Manual page 67

For instance, WebLogic Server 7.0 ensures that a method exists if a transaction
attribute is set for that method name. This helps identify a common set of errors
where transaction attributes were mistakenly set on non-existent methods.
Look at the WebLogic Server 7.0 examples
The WebLogic Server distribution contains several EJB examples including their
deployment descriptors. The EJB examples can be found in the
samples\server\src\examples\ejb11
samples\server\src\examples\ejb20
7.0 distribution.
The following table shows the descriptor combinations supported by WebLogic
Server 7.0.
Table 2-1
EJB Version
Any existing WebLogic Server 5.1 deployment uses the following combination and can be deployed without
changing descriptors or code in WebLogic Server 7.0.
1.1
The below combinations include a WebLogic Server 7.0 CMP deployment descriptor. The WebLogic Server 7.0
EJB 1.1 CMP deployment descriptor allows multiple EJBs to be specified within a single EJB JAR file, and it
supports using a TxDataSource which is required when an EJB is enlisted in a two-phase /XA transaction.
1.1
1.1
EJB 2.0 beans always use the WebLogic Server 6.x or 7.0 deployment descriptors.
2.0
2.0
For more information on Enterprise JavaBeans, see
and
Porting and Converting Enterprise JavaBeans Applications
Programming WebLogic Enterprise Java
and
directories of the WebLogic Server
WebLogic Server
Version
5.1
5.1
7.0
6.x
7.0
Beans.
BEA WebLogic Server 7.0 Upgrade Guide
The CMP Version
5.1
7.0
7.0
7.0
7.0
Enterprise JavaBean Components
2-19