|Re: Snaps-based app doesn't allow welcome files? [message #820045 is a reply to message #817193]
||Tue, 13 March 2012 16:57
| Chris Frost
Registered: January 2010
Location: Southampton, England
Could you show the web.xml for the host as well please. What is the full context path you are requesting as for just "/lm/spring"? Interesting, what makes you think that "null path request gets shunted through the StaticResourceServlet"
Where is "__resource-servlet" defined, I can't see it in the web.xml so I don't know how it's mapped the request to it? I think I'm missing something, want to get this straight before I try and recreate it myself.
Also, how were these bundles deployed, Pickup, Admin Console or through the tooling?
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.
[Updated on: Tue, 13 March 2012 17:00]
Report message to a moderator
|Re: Snaps-based app doesn't allow welcome files? [message #820070 is a reply to message #820045]
||Tue, 13 March 2012 17:29
| Jason Levine
Registered: July 2009
The web.xml for the host (again minus the root element, because the forum sees the URLs in it and won't let me post links):|
<?xml version="1.0" encoding="UTF-8"?>
<display-name>Virgo Web Portal</display-name>
The host is configured at Web-ContextPath '/lm'.
I'm not sure what you mean by "What is the full context path you are requesting as for just '/lm/spring'?". Guessing, the context should be to my Snap bundle -- called lmportal-spring, and residing in the lmportal-spring.jar file that you see in that log. That bundle's MANIFEST.MF has "Snap-ContextPath: /spring", mapping it to the full context '/lm/spring'.
__resource-servlet comes from Snap's own default web.xml -- in org.eclipse.virgo.snaps.core, in the src/main/resources/META-INF/snaps/default-web.xml file. It maps to Virgo's own StaticResourceServlet (org.eclipse.virgo.snaps.core.internal.webapp.StaticResourceServlet).
These bundles are all deployed via uploading them in the Admin Console.
I believe that Tomcat natively is supposed to handle welcome-file negotiation, so something's happening in Snaps to override this. (It's all spelled out in the Servlet spec, section 9.10 in Servlet 2.4.) Just looking at the log file I posted originally, I suspect that the problem here is that the default configuration for the Snaps host (as spelled out in that default-web.xml, etc.) is claiming control over the root ('/') of all deployed Snaps, rather than allowing Tomcat to try to do its welcome-file dance first.
Powered by FUDForum
. Page generated in 0.12923 seconds