As we remove the one one association between container STACK and invoker we
keep this around. IN the future the creation of proxies is a task done on a
container basis but the container as a logical representation. In other
words, the container "Entity with RMI/IIOP" is not a container stack but
an association at the invocation level that points to all metadata for
a given container.
In other words this is here for legacy reason and to not disrupt the
container at once.
In particular we declare that we "implement" the container invoker
interface when we are just implementing the Proxy generation calls.
Separation of concern.
todo eliminate this class, at least in its present form.
author: Marc Fleury author: Scott Stark/a> author: Thomas Diesler/a> version: $Revision: 61258 $
The bindProxy method creates the home proxy and binds
the home into jndi. It also creates the InvocationContext and client
container and interceptor chain.
throws: Exception - if an error occurs