I think the disconnect here is the idea that multiple beans would have the same EJB name. The EJB spec says:
(1) The EJB name must be unique in an EJB jar (2) The EJB name defaults to the unqualified bean class name So, it seems to me that this potential for conflicts is more a problem with the EJB spec itself than with our implementation. (Yes, sure, I understand that you could have them packaged in multiple ejb jars inside the same ear, but this still seems like a very uncommon case.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922543#3922543 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922543 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
