I was wondering why there is a need to have two interfaces, namely, home and remote for the Beans in the EJB Spec.
Wouldnt a remote interface suffice, with the Container trapping method calls to an object and instantiating the object if it is not already active? In CORBA for example there are only remote interfaces, with the Object Adapter doing the job of managing the instance lifecycles. Shouldnt the client be unconcerned with the need to manage the lifecycle of server side objects?

- U