|Re: Problem in generated server.xml preventing web-app from reading files [message #713498 is a reply to message #711443]
||Mon, 08 August 2011 14:27
| Larry Isaacs
Registered: July 2009
On 8/6/2011 2:12 AM, Steve Ash wrote:|
> It appears that its related to bug 318449 which was supposed to have
> been fixed in 3.3.0 -- I'm guessing this didn't happen.
Actually, I believe your problem is a side effect of Bug 333102. I
may not be recollecting exactly, but the problem goes something like
this. To get servlet annotations working, the servlet classes have to
be accessible as resources in addition to being accessible via
classloading. As a result, when Tomcat "asks" if "WEB-INF/classes"
exists as a resource, the answer from the custom classloader used by the
"Serve modules without publishing" is "yes". Tomcat then asks for the
URL to "/WEB-INF/classes" in your project, appends the name of the
resource (such as "log4j.properties") to that URL and tries to use the
URL to read the resource. Since resources destined for
"WEB-INF/classes" exist in multiple locations in your project, the URL
returned above can only work for one of them. In your case, it's the
The workaround is to either not use "Serve modules without publishing",
or arrange for the desired file to be at the location the
"WEB-INF/classes" URL will try to access.
Powered by FUDForum
. Page generated in 0.02679 seconds