On Tue, Oct 20, 2009 at 12:43 PM, Martin Cooper <mart...@apache.org> wrote: > On Tue, Oct 20, 2009 at 8:24 AM, Musachy Barroso <musa...@gmail.com> wrote: >> If I don't remember wrong, there is a bug in tomcat, or one of its xml >> deps that tries to get the dtd online. This has popped multiple times >> in user@ right? > > I guess that's possible. When this happened with S1, though, it was > because something went wrong when we tried to register the URI with > the name resolver. (The resolver basically tells the parser "when you > see this URI, use this local file instead of retrieving it from the > net.) It would be good if we could make sure it's Tomcat and not us, > somehow. :-) >
It is an issue that comes up from time-to-time. The trick is that it's not every install of tomcat. There is some magic combination (xalan jars in your web-app?) that crops up and causes the problem. I can't think of the last time we've come across it, but people only complain if their web-app can't go out and grab the DTDs from the web, so it's a somewhat obscure problem. The last time it came up, I remember that removing jars from either common/lib or WEB-INF/lib solved it for the user. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
