It may be due to different class loader loading the same bean during
Hot deployment.
When JBOSS Starts up, it will load all the beans using (IMHO, Not Sure)
Default classloader and anything which is re-deployed may be getting
Loaded using different class loader.
So, When you refer to the same be
You'll probably see that due to the classloading. I'd suggest
packaging your servlets and ejbs into an .ear file. That way both
your servlets and your EJBs will use the same classloader, and will
be restarted at the same time during hot deployment. I do this, and
don't have any problems with cl
IMHO, this behavior defeats the purpose of hot deployment.
If I have a dozen web-apps that all depend on one ejb jar file, and I
redeploy that ejb jar file, I shouldn't have to redeploy the other dozen
web-apps!
-- Jim
Neal Sanche wrote:
You'll probably see that due to the classloading. I'd su
Hello,
Can you try to put any class/interface that is shared by both your EJB and
Web components (for example the home and remote interfaces, the Data
objects, etc.) in a separate JAR and NOT in any other WAR, EAR or EJB-JAR.
Then deploy this JAR independently of the EJB.
Cheers,
Good point, for sure. The way I understand classloading is that if a
new classloader is used to load a class that may have already been
loaded by an older classloader instance, any classes that have a
reference to the old class, and an instance of the new class is
compared against it, classcast
