We use loose
EJB jars during development rather than an EAR file so we can hot-deploy
specific pieces. Unfortunately a session bean hot-deploy causes a class-cast
exception the next time that bean is used.
This fails if and only if you hot-deploy the session
bean that is being looked up. A proxy comes back in both cases but the cast
fails after a redeploy. This prevents us from hot deploying session beans. Not
good.
MyHome home = (MyHome)context.lookup("acme.widget.foo.bar.bean");
Suggestions?
TIA,
Rod
