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
,
Sacha
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:jboss-user-admin@;lists.sourceforge.net]De la part de Jaydeep
> Dhar
> Envoye : vendredi, 25 octobre 2002 17:24
> A : [EMAIL PROTECTED]
> Objet : [JBoss-user] JBOSS-EJB HOT DEPLOYMENT PROB
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
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
the mark.
-saroj
-Original Message-
From: [EMAIL PROTECTED]
[mailto:jboss-user-admin@;lists.sourceforge.net] On Behalf Of Jaydeep
Dhar
Sent: Friday, October 25, 2002 8:54 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] JBOSS-EJB HOT DEPLOYMENT PROBLEM
Hi,
I am using jboss 3.0.3 integrated
Hi,
I am using jboss 3.0.3 integrated with jetty web server.
I am getting following problem during devlepment of simple application.
1) I have developed a simple staless session bean and putted the .jar file
in deploy directory. It works fine when i call it from the servlet but once
I change anythi
