user manual

386 BES Developer’s Guide
EJB Container-level Properties
ejb.useDynamicStubs=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.>
true
Property Description Default