EJB3 deployments should be bound with rebind instead of bind ------------------------------------------------------------ Key: EJBTHREE-677 URL: http://jira.jboss.com/jira/browse/EJBTHREE-677 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Roland R?z Using bind instead of rebind may cause trouble when the JNDI implementation is persistent (e.g. in an ldap directory) because deploying a previously crashed application will fail. I know that the current situation can also be seen as a feature because the developer cannot deploy two different beans with the same jndi name but this has in my opinion a lesser priority. Further the ejb 2.x stack uses rebind too. The request http://jira.jboss.com/jira/browse/EJBTHREE-51 describtes to use Util.rebind() but in fisheye I saw Util.bind(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira