Hi All,
One of our FOP developers, Keiron Liddle has come across the following
bug/feature to do with classloaders and serializers. Below is a
summary of what is happening. Any comments ?
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: Open Software Associates GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&' Email : [EMAIL PROTECTED]
&&&&. Business Hours : +49 69 9757 200
&&&&&&&:
---------- Forwarded message ----------
Date: Wed, 25 Jul 2001 13:17:51 +0200
From: Keiron Liddle <[EMAIL PROTECTED]>
To: Marcus Crafter <[EMAIL PROTECTED]>
Subject: ClassLoader bug in serializers
Hi,
I have encountered a problem with the class loader when using a serializer.
The serializer in question is the FOPSerializer.
The class has the following class loader when add as a component from the
sitemap (in the method addSitemapComponent).
org.apache.tomcat.loader.AdaptiveClassLoader12
This eventually (through a convoluted path) leads to FOP itself being
loaded with the same class loader. This happens when the
org.apache.fop.app.Driver class is instantiated (or possibly some other
place, loading config).
The problem is that I want to load a class (from FOP) that is in another
jar file. The jar file in question is correctly placed into WEB-INF/lib/.
Due to the class loader being incorrect it cannot find the classes (files)
in the other jar file.
Does the Serializer have the correct class loader?
If so, Can FOP be loaded using the correct class loader (the one that
contains the WEB-INF/lib/*.jar)?
Tomcat: v 3.2.2
Cocoon: Current CVS (also older versions)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
