I've found the source of my problem. Thankfully I came across Scott's classloading
debug sample in the Jboss 3.2 admin doc. This revealed that I did in fact have another
copy of the class available to my web app - it had been unexpectedly included in a
dependency jar in WEB-INF/lib even though
I found the source of my problem. Thankfully I came across Scott's classloading debug
sample in the Jboss 3.2 admin doc. This revealed that I did in fact have another copy
of the class available to my web app - it had been unexpectedly included in a
dependency jar in WEB-INF/lib even though
of folks dupe classes all over the place to get things working but get bitten later.
-Original Message-
From: Alastair Rodgers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2003 10:45 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] RE: Classloader issues
I found the source of my
