Sorry if this is not the right forum. This could be something trivial though.
I decided to give Jboss-5.0.0.Beta2 a try and ran into the following:
I have and ear with a stateless EJB3 within. It is accessed remotely by an EJB client (through jndi lookup)
When starting jboss with the ear in the deploy directory, it starts and works fine.
Upon removing and/or overwriting the ear jboss successfully undeploys it (according to the logs).
Then, (again according to the log) a successful (re)deployment happens, but the bean does not (re)appear in the jndi namespace and the client returns with "xxxinterface not bound".
Is there any trick to it ?
I have noticed similar hot-deployment glitches in 5.0 beta 2. I would not rely on hot deployment for this beta. It is, after all, a beta, and the hot deployment mechanism has changed radically since 4.x.