Weblogic.management.configuration.ejbcomponentmbean Changes; Max-Beans-In-Cache Parameter - BEA WebLogic Server 7 Upgrade Manual

1
Upgrading WebLogic Server 6.x to Version 7.0
There were no local interfaces in 6.0, but they exist in 6.1 and 7.0.
Remote relationships do not exist in 6.1 and 7.0.
The new implementation of read-only beans in WebLogic 7.0 does not require
NOT_SUPPORTED
but gives each transaction its own instance of the read-only bean to use.
In pre-2.0 final versions of our EJB implementation you could refer to a CMP or
CMR field in a
final specification, all
The new implementation of read-only beans in WebLogic 7.0 does not require
NOT_SUPPORTED
not do exclusive locking, but gives each transaction its own instance of the
read-only bean to use.
If you have trouble with a servlet within the scope of application deployment see
"Deployment" on page

weblogic.management.configuration.EJBComponentMBean Changes

Beginning in Weblogic Server 6.1 and continuing in WebLogic Server 7.0, the
interface
so that it extends both
that implement
getVerboseEJBDeploymentEnabled
EJBContainerMBean

max-beans-in-cache Parameter

In WebLogic Server 7.0 the
number of beans in the cache for Database concurrency. In earlier WebLogic Server
versions,
You may need to increase the size of this parameter.
1-26 BEA WebLogic Server 7.0 Upgrade Guide
for a transaction attribute. It also doesn't do exclusive locking,
query without using a qualified path. However, as of the
EJB QL
EJB QL
for a transaction attribute. The new implementation also does
1-24.
weblogic.management.configuration.EJBComponentMBean
ComponentMBean
EJBComponentMBean
when you port from WebLogic Server 6.0 to 7.0.
max-beans-in-cache
max-beans-in-cache
queries must have a qualified path.
and
EJBContainerMBean
(for example,
) must be changed to support
parameter controls the maximum
was ignored; the size of the cache was unlimited.
changed
. Any methods