web server - Borland Technical Publications

EJB Container-level Properties
Table 31.1
EJB container properties (continued)
Property Description Default
ejb.useDynamicStubs=true|false
ejb.usePKHashCodeAndEquals=true|false
This property is only relevant for CMP
2.0 entity beans that provide local
interfaces. If set, the Container, which
otherwise uses CORBA to dispatch
calls, uses a dynamic proxy-based
scheme to dispatch calls (creating
custom lightweight, non-CORBA
references). These local dynamic stubs
provide many optimizations, especially
due to the callers and callees being in
the same VM, making a direct dispatch
to the beans without going through the
CORBA layer. Also, since the dynamic
stubs are aware of the EJB container
data structures, they access the target
beans more quickly. Note that currently
the stub generator, java2iiop (called
using the iastool or directly) still
generates the stubs for all the interfaces
in the archive. When ejb.useDynamicStubs
is active, the subset of stubs that
correspond to the selected CMP 2.0
beans are ignored.
This feature, when used, makes the
whole dispatch mechanism dynamic,
providing dynamic stubs for the client
side as well as dynamic skeletons on
the server side. Any statically generated
stub and skeleton classes in the archive
are ignored.
You set the property in the bean.
However, if there isn't an issue with
using the property in all the entity
beans, the easiest way is to set it at the
EAR level in the deployment descriptor.
Important:
You must use this property in
conjunction with
ejb.usePKHashCodeAndEquals.
Data structures that support Active
Cache (TxReady cache) and
Associated Cache (Ready beans
cache) use java.util.Hashtable, and
java.util.HashMap. The values (entity
bean instances) pooled in these data
structures are keyed on the primary key
values of the cached entity beans. As
we know, the implementation of
Hashtable relies on computing
hashCode() and calling equals()
methods of the keys to place and locate
the values. These data structures are in
the critical code path and are accessed
frequently by the container while
dispatching calls to methods in entity
beans The default in BES is a reflectionbased
computation. When this property
is set, the container uses a user
supplied implementation of the equals()
and hashCode() methods.
true
true
332 BES Developer’s Guide