gtriant wrote:Insisting on a bad solution to a problem isn't going to help you. The best solution is to make 2 subclasses with the shared functionality in a common superclass. in fact, i seem to remember some app servers getting confused if you tried to deploy the same class multiple times under different names (at least for stateless ejbs). This is a simple, clean solution to your problem.
I appreciate the suggestion. But as I said lets just keep this as a question of how to access the MDB name from within the MDB at runtime.