[EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30694>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30694
Classes specified in config are not loaded by the servlet's classloader...
------- Additional Comments From [EMAIL PROTECTED] 2004-08-16 13:10 ------- Ahh, but see, that won't help:
Because Domain.xml is using self.getClass().getClassLoader(), it will fail to find things *in the war* - specifically, it will fail to find my own, WAR-contained Nodestore.
I'm more than happy to put the wars into the shared/lib directory - but doing so immediately makes it impossible to use a custom nodestore, because domain is loading them with the wrong classloader.
I don't see how. Just put the custom nodestore in shared/lib instead of in the war and see what happens.
What should happen is that the servlet should set, on Domain, the classloader from the WAR;
This is not possible. If Slide is bootstrapped from the shared classloader it does not have access to the context classloader.
then, Domain and its subcomponents should always use a getClassLoader() method on the Domain object to get the appropriate classloader for loading nodestores.
That would then just magically work. Basically, get/setClassLoader() on Domain, with the default being Domain.class.getClassLoader(), but with the WebdavServlet calling setClassLoader() before loading the domain configuration.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
