Hi Charlie,
thanks for your mail. After some heavy thinking (gee, this topic lasted
longer than expected! :-) ), we came to the following conclusion:
We will copy the HashTable.class to the application library. We believe
this is the best we can do because
(1) we maintain the concept of stori
Hi Charlie,
You are right saying that it is a consequence of how classes are loaded
Still, this can be an error... ;-)
I think I could live with the fact that as long as the "container" of the
serialized classes was just a HashTable. This would, of course, require
that I always keep the cur
Hi Charlie,
I gave it a try. And guess what: it worked! Now, in this very simple case
one can argue that adding the collection classes to the application's lib
directory is not a bad thing to do. But what would one do if the scenario
wasn't that simple? (Actually, it isn't!)
Anyway, I consi
Hello,
I have to fix some bugs in our application.
But I don't want create all jar-files again.
I want to pack all fixed classes into one jar-file.
In which directory I have to put this jar-file.
thanks
jürgen
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
--
To unsubs
see intermixed, too
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Fri, 9 Aug 2002 08:42:05 -0400
Subject: RE: Problems with class loader
see intermixed
>
> Hello,
>
> we have problems with the tomcat class loaders.
>
> scenario:
> Tomcat 4.0.4, jdk1.3
> 2 Applications
>
> App1:webapps/App
Hello,
we have problems with the tomcat class loaders.
scenario:
Tomcat 4.0.4, jdk1.3
2 Applications
App1:webapps/App1/WEB-INF/lib/x.jar
App2:webapps/App2/WEB-INF/lib/x.jar (the same .jar-file)
x.jar: a.class, b.class, c.class
b.class has a Hashtable (com.sun.java.util.collections.Hashtable)
