> From: Filip Hanik [mailto:[EMAIL PROTECTED] > not sure why someone would go in and mock with the Tomcat > source when there is no need to :)
My goal was simply to get it to WORK so I could continue development. This solution worked for me. I'm not at all confident that it's the correct or ideal solution. > have fun maintaining upgrades.... ;) For me, this won't matter, because this is just a development system on my local box. Production deployment will be on Websphere and this issue won't even matter. > We use the digester in our webapp without any problems what > so ever, we simple place it in WEB-INF/lib I think I've further isolated the problem to be tied to the Tomcat plugin for Eclipse. I'm not sure of this, but I suspect that the classpaths are different or something which causes the commons-digester.jar to be found in the WEB-INF/lib directory before the server/lib directory, so Catalina uses the wrong one. I just tested this, using the old catalina.jar file without my changes. Server starts fine in stand-alone mode, but inside Eclipse the Digester can't find org.apache.catalina.core.StandardServer > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Nonetheless, it's good to see someone actually put his money where his > mouth is, report a problem they're having, try to fix it, > come up with a > working solution (even if breaks something else), and report their > findings. I wish more people did that. Thanks -- so do I! I found multiple references to the problem itself, but none to a solution, except for the proposed patch on bugzilla. That headed me in the right direction, which was great. As I said originally, I'm ignorant about some of the issues involved (this is my first time using Tomcat, and the first time hearing about these different classloaders) so my fix may or may not be appropriate. But if someone like me searches the list archives later and finds the original post, at least they'll find my hack too, and maybe save a bunch of head scratching :) Matt Kruse
