Not a bug, but I understand how it looks. A couple things in this area make life hard for
EJB vendors and then of course for users in return.
This is legal and normal:
RedBean implements ColorRemote
BlueBean implements ColorRemote
In this case what should the JNDI name of each bean be?
As well, beans can have an unlimited number of both @Remote and @Local interfaces:
BrownBean implements CMYKRemote, RGBRemote
OrangeBean implements CMYKRemote, RGBRemote, ColorRemote, ColorLocal
This one is more common with @Local and less common with @Remote.
Really the only unique thing is the ejb-name and even that is only unique within the ejb jar. The only truly unique JNDI name would be something horrendously long like "{application-name}/{module-name}/{ejb-name}/{interface-name}"
We did our best to pick a pragmatic default which is essentially "TheBean" + "@Remote" , but with the "@" yanked, so essentially "TheBeanRemote". Same for @Local views, etc. We will log all JNDI names to the log output and do our best to keep log messages to a minimum so that they won't be missed.
We also, however, understand that what the "right" JNDI name format is is entirely subjective and there is no "one size fits all" answer. So, it is possible to change the default format to whatever you like and still only configure by exception (i.e. you won't have to specify the name of each and every bean to get a format you like). Details here:
http://openejb.apache.org/3.0/jndi-names.html
Hope this helps!
-David