hi, IMHO here we deal here with two problems (at least), one of my first question is which is your goal ? Here are my answers to your problem : 1.The EJBs does JNDI behind the scene and to solve this you must help him a little - with some configuration files. 2.If two bean are implementing the same interface (strategy which is not desirable) then you shod use the beanName attribute to inject the right bean. In most of the cases you use the EJB without any attribute and let the container to do the look up job. Why you use the @EJB together with the name ?
Regards, M View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198183#4198183 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198183 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
