> 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
>
installed elsewhere and pointed to by a ClassPathExtension
MBean?
thanks,
-mike.
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 19, 2001 7:19 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] 2nd Deployment Fails
You can't deploy the custom catg
You can't deploy the custom catgory and factory in the
same jar as the ejb-jar because each deployment results
in a new type of TraceCategory. In Java the identity of
a class is determined by both the class name and its
ClassLoader. The first time you deploy it works and the
log4j Category class s
I am using log4j as the trace mechanisim for all of my beans. I have
extended log4j slightly to add new categories. The typical static
definition inside each bean class is:
static TraceCategory trace =
(TraceCategory) TraceCategory.getInstance( MyMDB.class );
MDB or Enti
