> However, I'm not completely sure I understand why the other didn't work.
> Before the second deployment the previous is undeployed. Why does the
> TraceCategory instance live beyond this undeployment. And is there
> something specific I can do such that it is destroyed and will not affect a
> second deployment?
>
There is nothing you can do since you can't unload a class in general, and
you certainly can't unload a class that is being used as is the case here
since the Category is keeping track of its instances in a hashtable.
> Perhaps I am looking at this wrong. Should helper classes not be part of
> the deployed jar file? Is that jar file only for EJBs? In general, should
> helper classes be installed elsewhere and pointed to by a ClassPathExtension
> MBean?
>
Not if there are being shared across deployment jars. In this case they should
be loaded by a class loader that is a parent class loader to all classes using
the shared class.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
