Are all the dependend beans deployed on the same JBoss server? If so, the
ClassCastException is normal. JBoss makes a call by reference to beans on the
same JBoss server, even if they have remote interfaces. When you
undeploy/redeploy an ear the classloader changes. A class is defined as
identical
I've been having this same issue. Only "solution" I've found so far is
to redeploy all my apps that depend on the SLB. Not such a great
solution. I'm also very interested to find a way to deploy my app
without redeploying all the dependencies as well.
Gary.
On Tue, 2003-11-18 at 16:52, Rod Mac
Anybody else having a problem hot deploying SLBs? Fetching the home
interface fails with a class-cast exception. That is the proxy itself
cannot be cast to the home interface. Happens every time after you
redeploy the SLB jar.
---
This SF.net e
I think, redeploying everything that references the redeployed beans is
only way.
Rod Macpherson wrote:
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 tha
Title: Message
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 be
