From my own digging through the spec, I'm pretty sure that the container doesn't automatically determine if it should hand out local or remote references according to the type of interface the client uses (unlike ejbFind<METHOD>s, which are handled appropriately automatically). That means that if you want to provide the same kind of functionality via a home business method in both local and remote homes, you'll need two different methods.
Hi Reid,
I do not agree with what you quoted. The idea of local interface was designed for light weight access. If the container does not know, then who knows.
Firstly, you cannnot mix both local and remote methods in one single home. At the time the client does a look up through JNDI, the type of interface (local or remote) is already determined - remember all the
home/remote and
local-home/local tags in the deployment descriptor.