Hi,
Several people have reported similar problems in the past. It often turns
out that the problem is that the classes are already in the classpath even
before the deploy directory is consulted. Typically they put a jar file
with the classes in something like lib/ext. The classloader for this stuff
is not discarded on redeploy of a bean, so the old def is still present
when you redeploy. If this is not the problem, you might want to check the
mail archives for other possibilities -- I think this was about 2-3 weeks
ago.
David Jencks
On 2001.05.09 00:36:52 -0400 Norton Lam wrote:
> Hi,
>
> I love the auto-deploy feature of JBoss. However, it's not
> working as I expect it to.
>
> I created a jar file and put it in the $JBOSS_HOME/deploy
> directory. One of the remote interface classes didn't throw
> a RemoteException, and JBoss reported that problem on the
> auto-deploy. So I added the 'throws RemoteException' to the
> interface definition, compiled, jar'ed it up, and copied
> it to the deploy directory. JBoss recognized the change
> and attempted a redeploy, but the same error came up.
>
> When I stop and start the server (without a change to
> the jar), the auto-deployer doesn't report any errors
> and my new application is successfully started.
>
> Shouldn't the auto-deployer have retrieved the new class
> file and deployed my app successfully without a restart?
>
> Thanx.
>
> Norton
>
> _______________________________________________
> 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
