"bill.burke@jboss.com" wrote:"adrian@jboss.org" wrote:
"Maybe this is something I should just not do for JBoss 4.x."
In JBoss4, not only might not the jndi name be bound, the class might not
even be deployed, yet... :-)
I don't think so...
1. EJB 1 has @EJB ref bound to a specific JNDI name we'll say "foo".