The type in Java is a combination of a fully qualified class name and its
defining classloader. So the two objects with the same class name are
considered different types in your two web applications because each web
application is loaded by the dedicated webapp classloader.
To solve your
while sharing objects accross applications
The type in Java is a combination of a fully qualified class name and its
defining classloader. So the two objects with the same class name are
considered different types in your two web applications because each web
application is loaded
From: Andrés Glez. [mailto:[EMAIL PROTECTED]
Subject: Re: ClassCastException while sharing objects accross
applications
What about using JNDI to share objects between webapps?
Won't change anything, due to the previously noted classloader-specific casting
issue. What should work
only the interface (and
any referenced types) need go in common. Refactoring here we go :)
HTH,
Jon
Caldarale, Charles R wrote:
From: Andrés Glez. [mailto:[EMAIL PROTECTED]
Subject: Re: ClassCastException while sharing objects accross
applications
What about using JNDI to share objects
possible way is to utilize the system
MBeanServer.
--Seva
-Original Message-
From: Jon Wingfield [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 04, 2005 9:47 AM
To: Tomcat Users List
Subject: Re: ClassCastException while sharing objects accross applications
What Chuck says is right
