OK, I think I now understand where this is going. :-)
Who will then change the no-interface view and singleton binder / deployer to use this new naming schema?
Should I do this or will you do it?
(I'm still lost on 1M of your ejb3 subprojects :) )
Each EJB bean has a jndi binder (MC bean). the "bean" in such a case would be the name of the EJB. so the no-interface view and singleton binder deployer would install binders for each EJB using that naming scheme.
What's the EJB name in this case -- from JBossSessionBeanMetaData?
JBossSessionBeanMetaData::getEjbName?