Feature #25
Use a more appropriate classloader to load the default content-handler
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
fixed
Description
The attached patch is really simple fix to get mulgara working in environments where mulgara
<br/>
is loaded from a classloader other than the system classloader (webapps, beanshell, etc). It uses
<br/>
the classloader with which the Database class was loaded, which is the same algorithm as used
<br/>
to load the various factory classes (they use Class.forName()).
<br/>
<br/>
A more complete fix would be along the lines of what's in Kowari 1.1 (CVS), using the
<br/>
org.kowari.util.ClassLoaderUtil stuff (though [[ClassLoaderUtil]] needs to be fixed for the case where
<br/>
no classloader is explicitly configured).
Updated by ronald - over 17 years ago
Load the default content-handler using the current class' classloader instead
<br/>
of the system classloader.