Hi! I am using the Xerces parser within some kind of self-developed plugin mechanism. There we use a separated URLClassLoader to load the plugin classes into the VM. But we have a problem using the Xerces parser with this mechanism because the thread context class loader is the system loader while the parser is loaded via the separated URLClassLoader. We analysed the problem using Xerces and found out that the context class loader of the threasd is used in the NewInstance class (to get the class loader for new parser instances). We cannot put the Xerces parser into the boot classpath nor setting the context class loader to the separated URLClassLoader created for loading Xerces.
Does anyone have in idea how to solve this problem without patching Xerces? Why is the context class loader used withiin Xerces in opposite to the normal class loader of the Xerces classes? Need help... Best regards, Sebastian and Martin P.S.: Please send an answer to [EMAIL PROTECTED], too. Thanks!!! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
