I've noticed a couple of threads about strange ClassCastException
problems (Call EJB in OC4J from Tomcat,
pulling my hair out re: EJB in tomcat).
I've run into a strange ClassCastException in a slightly different
context, but it seems that it might be related and might help
narrow down the
I've noticed a couple of threads about strange ClassCastException
problems (Call EJB in OC4J from Tomcat,
pulling my hair out re: EJB in tomcat).
I've run into a strange ClassCastException in a slightly different
context, but it seems that it might be related and might help
narrow down the
This is normal then. Class foo loaded by class
loader A is not castable to class foo loaded
by class loader B (if they are really independent,
of course - if A is the parent of B and B
delegates, it will work). You have to
put the class in a spot shared by both
webapps (that means the
: The Infamous ClassCastException Problem
This is normal then. Class foo loaded by class
loader A is not castable to class foo loaded
by class loader B (if they are really independent,
of course - if A is the parent of B and B
delegates, it will work). You have to
put the class in a spot shared
Thanks. I packaged the classes in a jar and put them
in common\lib and now things work fine.
I'm still curious tho on how RMI/EJB clients manage
to do this without having the same class/classloader.
Frank Lawlor
Athens Group, Inc.
(512) 345-0600 x151
Athens Group, an employee-owned consulting
On Fri, 2 Nov 2001, Frank Lawlor wrote:
Date: Fri, 2 Nov 2001 14:49:37 -0600
From: Frank Lawlor [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED],
[EMAIL PROTECTED]
To: Tomcat (E-mail) [EMAIL PROTECTED]
Subject: Re: The Infamous ClassCastException Problem
Thanks. I
