blocks|key|1836780|text|我建议尽可能使用过滤器而不是默认的servlet。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1836781|其他两种可能性：|1836782|自己编写一个FileServlet。你会发现很多例子，它只需通过URL打开文件并将其内容写入输出流即可。然后，使用它来服务静态文件请求。|1836783|实例化Google+App+Engine使用的FileServlet类，并在需要为给定FileServlet提供静态文件时调用该URL上的服务(请求、响应)。|1836784|您可以将/res/*映射到YourFileServlet或其他任何地方，以便从DispatcherServlets的处理中排除它，或者直接从DispatcherServlet调用它。|1836785|我不得不问，Spring文档是怎么描述这种冲突的呢？我从来没有用过它。|1836786|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I'd recommend trying to use a Filter instead of a default servlet whenever possible.

Other two possibilities:

Write a FileServlet yourself. You'll find plenty examples, it should just open the file by URL and write its contents into output stream. Then, use it to serve static file request.

Instantiate a FileServlet class used by Google App Engine and call service(request, response) on that FileServlet when you need to serve the static file at a given URL.

You can map /res/* to YourFileServlet or whatever to exclude it from DispatcherServlets' handling, or call it directly from DispatcherServlet.

And, I have to ask, what does Spring documentation say about this collision? I've never used it.

blocks|key|2050908|text|我也遇到过这种情况，但从来没有找到一个很好的解决方案。我最终将我的servlet映射到URL层次结构中更高的一层：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2050909|<servlet-mapping>+++++++
++<servlet-name>home</servlet-name>+++++++++++++
++<url-pattern>/app/*</url-pattern>+++++
</servlet-mapping>|code-block|syntax|javascript|2050910|现在，基本上下文(以及您的/res目录中)中的所有内容都可以由容器提供。|2050911|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I've run into this also and never found a great solution. I ended up mapping my servlet one level higher in the URL hierarchy:

<pre class="lang-xml prettyprint-override"><code>&lt;servlet-mapping&gt; 
 &lt;servlet-name&gt;home&lt;/servlet-name&gt; 
 &lt;url-pattern&gt;/app/*&lt;/url-pattern&gt; 
&lt;/servlet-mapping&gt;
</code></pre>

And now everything at the base context (and in your /res directory) can be served up by your container.

blocks|key|1836813|text|如果使用Tomcat，则可以将资源映射到默认servlet：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1836814|<servlet-mapping>
++++<servlet-name>default</servlet-name>
++++<url-pattern>/static/*</url-pattern>
</servlet-mapping>|code-block|syntax|javascript|1836815|并使用url静态路径访问您的资源}/+http://{context+/res/...|offset|length|1836816|也适用于Jetty，但不确定其他servlet容器。|1836817|entityMap|0|LINK|mutability|MUTABLE|url|http://{context/^0|0|0|J|F|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@$I|X|J|Y|1|Z]]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

If you use Tomcat, you can map resources to the default servlet:

<pre><code>&lt;servlet-mapping&gt;
 &lt;servlet-name&gt;default&lt;/servlet-name&gt;
 &lt;url-pattern&gt;/static/*&lt;/url-pattern&gt;
&lt;/servlet-mapping&gt;
</code></pre>

and access your resources with url http://{context path}/static/res/...

Also works with Jetty, not sure about other servlet containers.

blocks|key|2050948|text|你的应用不能直接访问app+Engine中的“‘Static”文件。您要么需要上传它们两次，要么自己提供静态文件，而不是使用静态处理程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2050949|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

'Static' files in App Engine aren't directly accessible by your app. You either need to upload them twice, or serve the static files yourself, rather than using a static handler.

blocks|key|1836843|text|冲突的原因似乎是因为，默认情况下，上下文根"/“将由org.apache.catalina.servlets.DefaultServlet处理。此servlet旨在处理对静态资源的请求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1836844|如果您决定使用您自己的servlet来处理动态请求，那么顶级servlet还必须执行由catalina最初的"DefaultServlet“处理程序完成的所有任务。|1836845|如果您通读tomcat文档，就会发现True+Apache+(httpd)在处理静态内容方面比Apache+Tomcat更好，因为它就是专门为此而构建的。我猜是因为Tomcat默认使用org.apache.catalina.servlets.DefaultServlet来处理静态请求。因为它们都包装在JVM中，而Tomcat是作为Servlet/JSP容器使用的，所以他们可能没有将该类作为超级优化的静态内容处理程序来编写。它就在那里。它可以完成工作。足够好了。|1836846|但这是处理静态内容的东西，它位于"/“。所以，如果你在那里放了任何东西，而那个东西不能处理静态请求，那么，你的静态资源就消失了。|1836847|我一直在到处寻找同样的答案，我得到的答案是“如果你不想让它这么做，就不要这么做”。|1836848|长话短说，您的配置正在用根本不是静态资源处理程序的东西替换默认的静态资源处理程序。您需要尝试不同的配置才能获得您想要的结果(我也是如此)。|1836849|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

The reason for the collision seems to be because, by default, the context root, "/", is to be handled by org.apache.catalina.servlets.DefaultServlet. This servlet is intended to handle requests for static resources.

If you decide to bump it out of the way with your own servlet, with the intent of handling dynamic requests, that top-level servlet must also carry out any tasks accomplished by catalina's original "DefaultServlet" handler.

If you read through the tomcat docs, they make mention that True Apache (httpd) is better than Apache Tomcat for handling static content, since it is purpose built to do just that. My guess is because Tomcat by default uses org.apache.catalina.servlets.DefaultServlet to handle static requests. Since it's all wrapped up in a JVM, and Tomcat is intended to as a Servlet/JSP container, they probably didn't write that class as a super-optimized static content handler. It's there. It gets the job done. Good enough. 

But that's the thing that handles static content and it lives at "/". So if you put anything else there, and that thing doesn't handle static requests, WHOOPS, there goes your static resources. 

I've been searching high and low for the same answer and the answer I'm getting everywhere is "if you don't want it to do that, don't do that".

So long story short, your configuration is displacing the default static resource handler with something that isn't a static resource handler at all. You'll need to try a different configuration to get the results you're looking for (as will I).

blocks|key|1836859|text|您要做的就是在web.xml中添加一个欢迎文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1836860|<welcome-file-list>
++++<welcome-file>index.html</welcome-file>
</welcome-file-list>|code-block|syntax|javascript|1836861|然后将其添加到servlet映射中，这样当有人转到应用程序的根目录时，就会在内部将其发送到index.html，然后映射会在内部将它们发送到映射到的servlet|1836862|<servlet-mapping>
++++<servlet-name>MainActions</servlet-name>
++++<url-pattern>/main</url-pattern>
</servlet-mapping>
<servlet-mapping>
++++<servlet-name>MainActions</servlet-name>
++++<url-pattern>/index.html</url-pattern>
</servlet-mapping>|1836863|最终结果:您访问了/Application，但是出现了/Application/MainActions+servlet，而没有中断任何其他根请求。|1836864|明白了吗？因此，您的应用程序仍然位于子url，但当用户转到您网站的根目录时，它会自动显示。这允许您让/images/bob.img仍然转到常规位置，但'/‘是您的应用程序。|1836865|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

What you do is add a welcome file in your web.xml

<pre><code>&lt;welcome-file-list&gt;
 &lt;welcome-file&gt;index.html&lt;/welcome-file&gt;
&lt;/welcome-file-list&gt;
</code></pre>

And then add this to your servlet mappings so that when someone goes to the root of your application, they get sent to index.html internally and then the mapping will internally send them to the servlet you map it to

<pre><code>&lt;servlet-mapping&gt;
 &lt;servlet-name&gt;MainActions&lt;/servlet-name&gt;
 &lt;url-pattern&gt;/main&lt;/url-pattern&gt;
&lt;/servlet-mapping&gt;
&lt;servlet-mapping&gt;
 &lt;servlet-name&gt;MainActions&lt;/servlet-name&gt;
 &lt;url-pattern&gt;/index.html&lt;/url-pattern&gt;
&lt;/servlet-mapping&gt;
</code></pre>

End result: You visit /Application, but you are presented with /Application/MainActions servlet without disrupting any other root requests.

Get it? So your app still sits at a sub url, but automatically gets presented when the user goes to the root of your site. This allows you to have the /images/bob.img still go to the regular place, but '/' is your app.

blocks|key|1836895|text|将您不想触发servlet处理的文件夹添加到appengine-web.xml文件的<static-files>部分。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1836896|我刚刚这样做了，看起来事情开始正常工作了。这是我的结构：|1836897|/|1836898|/pages/<.jsp+files>|1836899|/css|1836900|我向<static-files>部分添加了"/pages/**“和"/css/**”，现在可以从servlet+doGet内部转发到.jsp文件，而不会导致无限循环。|1836901|entityMap^0|16|E|0|0|0|0|0|2|E|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|X|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|Q|$]]

Add the folders which you don't want to trigger servlet processing to the <code>&lt;static-files&gt;</code> section of your appengine-web.xml file.

I just did this and looks like things are starting to work ok. Here's my structure:

/

/pages/&lt;.jsp files>

/css

I added "/pages/**" and "/css/**" to the <code>&lt;static-files&gt;</code> section and I can now forward to a .jsp file from inside a servlet doGet without causing an infinite loop.

blocks|key|1837013|text|将控制器servlet映射到更具体的url-pattern+(如/pages/*+)上，将静态内容放在特定的文件夹(如/static+)中，并创建监听/*的Filter，它透明地继续任何静态内容的链，并将请求分派给控制器servlet以获取其他内容。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1837014|简而言之：|1837015|<filter>
++++<filter-name>filter</filter-name>
++++<filter-class>com.example.Filter</filter-class>
</filter>
<filter-mapping>
++++<filter-name>filter</filter-name>
++++<url-pattern>/*</url-pattern>
</filter-mapping>

<servlet>
++++<servlet-name>controller</servlet-name>
++++<servlet-class>com.example.Controller</servlet-class>
</servlet>
<servlet-mapping>
++++<servlet-name>controller</servlet-name>
++++<url-pattern>/pages/*</url-pattern>
</servlet-mapping>|code-block|syntax|javascript|1837016|在过滤器的doFilter()中包含以下内容|1837017|HttpServletRequest+req+=+(HttpServletRequest)+request;
String+path+=+req.getRequestURI().substring(req.getContextPath().length());

if+(path.startsWith("/static"))+{
++++chain.doFilter(request,+response);+//+Goes+to+default+servlet.
}+else+{
++++request.getRequestDispatcher("/pages"+%2B+path).forward(request,+response);
}|1837018|不，这不会在浏览器地址栏中以/pages结尾。它是完全透明的。如有必要，您可以将"/static"和/或"/pages"作为过滤器的init-param。|1837019|entityMap^0|I|B|W|8|1N|7|23|2|26|6|0|0|0|5|A|0|0|E|6|14|9|1G|8|1U|A|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|T|$]]

Map the controller servlet on a more specific <code>url-pattern</code> like <code>/pages/*</code>, put the static content in a specific folder like <code>/static</code> and create a <code>Filter</code> listening on <code>/*</code> which transparently continues the chain for any static content and dispatches requests to the controller servlet for other content.

In a nutshell:

<pre class="lang-xml prettyprint-override"><code>&lt;filter&gt;
 &lt;filter-name&gt;filter&lt;/filter-name&gt;
 &lt;filter-class&gt;com.example.Filter&lt;/filter-class&gt;
&lt;/filter&gt;
&lt;filter-mapping&gt;
 &lt;filter-name&gt;filter&lt;/filter-name&gt;
 &lt;url-pattern&gt;/*&lt;/url-pattern&gt;
&lt;/filter-mapping&gt;

&lt;servlet&gt;
 &lt;servlet-name&gt;controller&lt;/servlet-name&gt;
 &lt;servlet-class&gt;com.example.Controller&lt;/servlet-class&gt;
&lt;/servlet&gt;
&lt;servlet-mapping&gt;
 &lt;servlet-name&gt;controller&lt;/servlet-name&gt;
 &lt;url-pattern&gt;/pages/*&lt;/url-pattern&gt;
&lt;/servlet-mapping&gt;
</code></pre>

with the following in filter's <code>doFilter()</code>:

<pre class="lang-java prettyprint-override"><code>HttpServletRequest req = (HttpServletRequest) request;
String path = req.getRequestURI().substring(req.getContextPath().length());

if (path.startsWith("/static")) {
 chain.doFilter(request, response); // Goes to default servlet.
} else {
 request.getRequestDispatcher("/pages" + path).forward(request, response);
}
</code></pre>

No, this does not end up with <code>/pages</code> in browser address bar. It's fully transparent. You can if necessary make <code>"/static"</code> and/or <code>"/pages"</code> an <code>init-param</code> of the filter.

blocks|key|2051137|text|处理这个问题的最好方法是使用某种URL重写。通过这种方式，您可以拥有干净的restful+URL，并且没有任何扩展名，例如abc.com/welcom/register，而不是abc.com/welcom/Resier.html|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2051138|我使用的是Tuckey+URL，它非常酷。|offset|length|2051139|它有关于如何设置web应用程序的说明，我已经用我的Spring+MVC+web应用程序进行了设置。当然，一切都很好，直到我想使用注释进行Spring3验证，比如对域对象使用@Email或@Null。|style|CODE|2051140|当我添加Spring+mvc指令时：|2051141|<+mvc:annotation-driven++/>+
<+mvc:default-servlet-handler+/>|code-block|syntax|javascript|2051142|。。它破解了好的Tuckey密码。显然，<+mvc:default-servlet-handler+/>取代了Tuckey，而我仍在努力解决这个问题。|2051143|entityMap|0|LINK|mutability|MUTABLE|url|http://www.tuckey.org/urlrewrite/^0|0|5|A|0|0|2E|6|2L|5|0|0|0|K|W|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|6|7|15|8|@$D|16|E|17|H|I]|$D|18|E|19|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1B|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1C|8|@$D|1D|E|1E|H|I]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

The best way to handle this is using some kind of URL re-writing. In this way, you can have clean restful URLs, and NOT with any extensions i.e abc.com/welcom/register as opposed to abc.com/welcome/resister.html

I use <a href="http://www.tuckey.org/urlrewrite/" rel="nofollow noreferrer">Tuckey URL</a> which is pretty cool.

It's got instructions on how to set up your web app.I have set it up with my Spring MVC web app. Of course, everything was fine until I wanted to use annotations for Spring 3 validations like <code>@Email</code> or <code>@Null</code> for domain objects. 

When I add the Spring mvc directives:

<pre><code>&lt; mvc:annotation-driven /&gt; 
&lt; mvc:default-servlet-handler /&gt;
</code></pre>

.. it breaks the good ol Tuckey code. Apparently, <code>&lt; mvc:default-servlet-handler /&gt;</code> replaces Tuckey, which I'm still trying to solve.

blocks|key|1837145|text|在3.0.4版本中，您应该能够结合使用mvc:resources和mvc:default-servlet-handler来实现这一点，如spring文档中所述。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1837146|http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/mvc.html#mvc-static-resources|1837147|entityMap|0|LINK|mutability|MUTABLE|url^0|J|D|X|R|0|0|32|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@$9|U|A|V|1|W]]|E|$]]|$1|H|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|G]]]]

As of 3.0.4 you should be able to use <code>mvc:resources</code> in combination with <code>mvc:default-servlet-handler</code> as described in the spring documentation to achieve this.

<a href="http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/mvc.html#mvc-static-resources" rel="noreferrer">http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/mvc.html#mvc-static-resources</a>

blocks|key|2051289|text|我发现使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2051290|<mvc:default-servlet-handler+/>|code-block|syntax|javascript|2051291|在spring中，MVC+servlet+bean定义文件适合我。它将任何未由注册的MVC控制器处理的请求传递到容器的原始默认处理程序，该处理程序应将其作为静态内容提供服务。只需确保您没有注册控制器来处理所有事情，并且它应该工作得很好。不知道为什么@logixplayer建议重写URL；只要充分使用Spring+MVC，你就可以达到他想要的效果。|2051292|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I found that using 

<pre><code>&lt;mvc:default-servlet-handler /&gt;
</code></pre>

in the spring MVC servlet bean definition file works for me. It passes any request that isn't handled by a registered MVC controller on to the container's original default handler, which should serve it as static content. Just make sure you have no controller registered that handles everything, and it should work just fine. Not sure why @logixplayer suggests URL rewriting; you can achieve the effect he's looking for just adequately using Spring MVC alone.

blocks|key|2051378|text|我找到了一个使用虚拟索引文件的更简单的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2051379|创建一个Servlet+(或使用您想要响应的Servlet)，它映射到"/index.html“(这里提到的解决方案通过XML使用映射，我使用带有注释@WebServlet的3.0版本)，然后在静态内容的根目录下创建一个静态(空)文件，名为"index.html”|2051380|我使用的是Jetty，所发生的情况是服务器识别了文件，而不是列出目录，但当请求资源时，我的Servlet接管了控制权。所有其他静态内容保持不受影响。|2051381|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I found a simpler solution with a dummy index file.

Create a Servlet (or use the one you wanted to respond to "/") which maps to "/index.html"
(Solutions mentioned here use the mapping via XML, I used the 3.0 version with annotation @WebServlet)
Then create a static (empty) file at the root of the static content named "index.html"

I was using Jetty, and what happened was that the server recognized the file instead of listing the directory but when asked for the resource, my Servlet took control instead. All other static content remained unaffected.

blocks|key|1837286|text|在Embedded+Jetty中，我通过为web.xml中的"css“目录添加一个映射来实现类似的功能。显式地告诉它使用DefaultServlet：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1837287|<servlet>
++<servlet-name>DefaultServlet</servlet-name>
++<servlet-class>org.eclipse.jetty.servlet.DefaultServlet</servlet-class>
</servlet>

<servlet-mapping>
++<servlet-name>DefaultServlet</servlet-name>
++<url-pattern>/css/*</url-pattern>
</servlet-mapping>|code-block|syntax|javascript|1837288|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In Embedded Jetty I managed to achieve something similar by adding a mapping for the "css" directory in web.xml. Explicitly telling it to use DefaultServlet:

<pre><code>&lt;servlet&gt;
 &lt;servlet-name&gt;DefaultServlet&lt;/servlet-name&gt;
 &lt;servlet-class&gt;org.eclipse.jetty.servlet.DefaultServlet&lt;/servlet-class&gt;
&lt;/servlet&gt;

&lt;servlet-mapping&gt;
 &lt;servlet-name&gt;DefaultServlet&lt;/servlet-name&gt;
 &lt;url-pattern&gt;/css/*&lt;/url-pattern&gt;
&lt;/servlet-mapping&gt;
</code></pre>

blocks|key|1837294|text|<?xml+version="1.0"+encoding="UTF-8"?>
<beans+xmlns="http://www.springframework.org/schema/beans"
++++xmlns:mvc="http://www.springframework.org/schema/mvc"
++++xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
++++xsi:schemaLocation="
++++++++http://www.springframework.org/schema/beans
++++++++http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
++++++++http://www.springframework.org/schema/mvc
++++++++http://www.springframework.org/schema/mvc/spring-mvc-3.0.xsd">
<mvc:default-servlet-handler/>
</beans>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1837295|如果您想使用基于注释的配置，请使用以下代码|unstyled|1837296|@Override
++++public+void+configureDefaultServletHandling(DefaultServletHandlerConfigurer+configurer)+{
++++++++configurer.enable();
++++}|1837297|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|I|3|-4|5|F|7|N|8|@]|9|@]|A|$]]]|J|$]]

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;beans xmlns="http://www.springframework.org/schema/beans"
 xmlns:mvc="http://www.springframework.org/schema/mvc"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="
 http://www.springframework.org/schema/beans
 http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
 http://www.springframework.org/schema/mvc
 http://www.springframework.org/schema/mvc/spring-mvc-3.0.xsd"&gt;
&lt;mvc:default-servlet-handler/&gt;
&lt;/beans&gt;
</code></pre>

and if you want to use annotation based configuration use below code

<pre><code>@Override
 public void configureDefaultServletHandling(DefaultServletHandlerConfigurer configurer) {
 configurer.enable();
 }
</code></pre>

blocks|key|1837313|text|关于Tomcat，很大程度上取决于特定的版本。有一个错误修复https://bz.apache.org/bugzilla/show_bug.cgi?id=50026，这意味着默认servlet的servlet映射(而不是'/')在Tomcat6.0.29(以及更早的版本)中的行为与后来的版本不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1837314|entityMap|0|LINK|mutability|MUTABLE|url|https://bz.apache.org/bugzilla/show_bug.cgi?id=50026^0|U|1G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

With regard to Tomcat, a lot depends on the particular version. There was a bug fix
<a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=50026" rel="nofollow noreferrer">https://bz.apache.org/bugzilla/show_bug.cgi?id=50026</a>
which means the servlet-mapping (other than for '/') for the default servlet behaves differently in Tomcat 6.0.29 (and earlier) compared with later versions.

I've mapped the Spring MVC dispatcher as a global front controller servlet on <code>/*</code>.

<pre class="lang-xml prettyprint-override"><code>&lt;servlet&gt; 
 &lt;servlet-name&gt;home&lt;/servlet-name&gt; 
 &lt;servlet-class&gt;org.springframework.web.servlet.DispatcherServlet&lt;/servlet-class&gt; 
&lt;/servlet&gt; 
&lt;servlet-mapping&gt; 
 &lt;servlet-name&gt;home&lt;/servlet-name&gt; 
 &lt;url-pattern&gt;/*&lt;/url-pattern&gt; 
&lt;/servlet-mapping&gt;
</code></pre>

However, this mapping stops the access to static files like CSS, JS, images etc which are all in the <code>/res/</code> folder.

How can I access them anyway?

How to access static resources when mapping a global front controller servlet on /*

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我已经将Spring MVC dispatcher映射为/*上的全局前端控制器servlet。<servlet> <servlet-name>home</servlet-name> <servlet-class>org.springframework.web.servlet.Disp...

问如何在/*上映射全局前端控制器servlet时访问静态资源
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在/*上映射全局前端控制器servlet时访问静态资源EN