Thanks for the quick reply!
jaikiran pai wrote:
The server cannot guess what the appname, module name and bean name would be for that target bean (which resides on a different server) to be. It's the user's application which has that idea.
I know it can't guess the appname and module name, that's what I wanted to know if I could configure somewhere. I guess my idea is that I should be able to tell the web app "Hey, use this server, this appname and this module name for ejb lookups," and the servers figure out the rest from there.
But your answer made me realize that we also need to know the name for the implementing class, since that's part of every standard jndi name. Thinking about it, it seems weird that the client should have to know about the name of the server-side class implementing the interface (the exception is of course multiple implementations of the same interface).
Is this just a limitation of jndi and remote ejb? Other than mapping these session beans to custom, shorter jndi names, is there no simpler way to accomplish something like this?