A single home factory component capable of servicing both locally and remotely deployed EJBs (e.g.
findLocalHome) was considered. This approach was abandoned for a number of reasons:
- Inconsistent API for local/remote EJBs
- Certain configuration information, e.g. use of RMI-IIOP, is superfluous in the case of local interfaces
- Weak separation between local and remote clients fosters opportunities for improper usage of pass-by-reference versus pass-by-value semantics
- A unified implementation class is less flexibile in terms of how home interface caching is performed for local versus remote interfaces