The most frequent cause of this is that your bean class files are somewhere
in your system classpath. Check your classpath, and make sure none of your
classes are anywhere in the classpath.
----- Original Message -----
From: "Jonas Bergström" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 02, 2001 3:14 AM
Subject: [JBoss-user] Hot undeployment problem.
Hello.
When I hot-undeploy an EJB by removing it's jar-file from the /deploy
directory, JBoss prints out 'undeploying-messages', which seems ok. But, if
I from another bean invoke methods on the removed bean, I don't get a
RemoteException (as I thought I would), instead it seems as if the bean is
still valid since the invoked methods return valid values.
Why isn't the bean completely removed?
Is there a way to check (from the client) if an ejb is valid or not?
I use JBoss-2.2 final w/ Tomcat 3.2.1 running within the Visual Café
debugger in JVM 1.2.2.
Thanks / Jonas
Jonas Bergström
Software Engineer
[EMAIL PROTECTED]
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
