As for the first problem, I think there is a bug in the deployment descriptor processing. Could you post your deploment descriptor?
The second problem is a bean trying to bind it's home interface over a JNDI name that's already taken. In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens. Can you confirm this scenario? http://jira.jboss.com/jira/browse/EJBTHREE-1045 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081194#4081194 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081194 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
