Are RMI-IIOP Stubs Needed to Access Remote
EJBs?

No. Unlike previous releases of the Enterprise Server, the current
version does not require static RMI-IIOP stubs at runtime.

Removing this requirement provides the following benefits:

Faster deployment and redeployment time for applications
containing remote EJBs or clients of remote EJBs

Fewer runtime errors caused by stub CLASSPATH configuration
problems

In addition, the Enterprise Server achieves these
benefits without significant impact on runtime performance, while
maintaining full RMI-IIOP interoperability.

The only scenario
where RMI-IIOP stubs are still required is for standalone clients
that explicitly instantiate an InitialContext for
the CosNaming naming service. This is not the
recommended approach for using the naming service in the Enterprise Server.
However, to maintain compatibility for these kinds of standalone clients,
there is a deployment-time option that forces the generation of RMI-IIOP
stubs in a way that matches previous releases. To use it, set

--generatermistubs=true

when deploying with asadmin or the Administration
Console. The RMI-IIOP stubs are placed in the client.jar file,
just as they were in previous releases.