spring3.0发布后,其web方面一个很大的特性是支持rest的架构。rest的好处不用多说,spring中关于rest的配置也很简单。看了下spring-sample中的例子,主要的设置在web.xml中,首先增加了tomcat容器中关于响应静态资源的servlet:
<!-- Defines the 'default' servlet (usually for service static resources). Uncomment this in containers (GlassFish) that do not declare this implicit definition out of the box, or change the name of the servlet mapping below to the appropriate one. <servlet> <servlet-name>default</servlet-name> <servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class> <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param> <init-param> <param-name>listings</param-name> <param-value>false</param-value> </init-param> <load-on-startup>1</load-on-startup> </servlet> --> <!-- - Map static resources to the default servlet - examples: - http://localhost:8080/static/images/pets.png - http://localhost:8080/static/styles/petclinic.css --> <servlet-mapping> <servlet-name>default</servlet-name> <url-pattern>/static/*</url-pattern> </servlet-mapping>
其次将org.springframework.web.servlet.DispatcherServlet的url过滤改为“/”:
<!-- - Servlet that dispatches request to registered handlers (Controller implementations). - Has its own application context, by default defined in "{servlet-name}-servlet.xml", - i.e. "petclinic-servlet.xml". - - A web app can contain any number of such servlets. - Note that this web app has a shared root application context, serving as parent - of all DispatcherServlet contexts. --> <servlet> <servlet-name>petclinic</servlet-name> <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class> <load-on-startup>2</load-on-startup> </servlet> <!-- - Maps the petclinic dispatcher to "*.do". All handler mappings in - petclinic-servlet.xml will by default be applied to this subpath. - If a mapping isn't a /* subpath, the handler mappings are considered - relative to the web app root. - - NOTE: A single dispatcher can be mapped to multiple paths, like any servlet. --> <servlet-mapping> <servlet-name>petclinic</servlet-name> <url-pattern>/</url-pattern> </servlet-mapping>
最后有一个辅助的filter:
<filter> <filter-name>httpMethodFilter</filter-name> <filter-class>org.springframework.web.filter.HiddenHttpMethodFilter</filter-class> </filter> <filter-mapping> <filter-name>httpMethodFilter</filter-name> <servlet-name>petclinic</servlet-name> </filter-mapping>
第一个servlet处理的静态资源的请求,但是只有在tomcat容器(或者是spring的那个容器)中才有效果,如果放在resin中是不行的,即使你将tomcat的jar包通过maven将其引入你的项目lib中。根据看DefaultServlet的源码可知,其需要找一些默认的容器资源,而这些在resin中是没有的……而且通过看spring-sample的源码可知,这个方法要求页面引用WebRoot根目录下的资源时,通过“/static/styles/petclinic.css”这样的路径去引用css,而不是真正的路径“/petclinic.css”。
如果不再resin中解决这个问题,spring的DispatcherServlet就会处理静态资源进而报错。为此,我们使用resin自带的servlet:“resin-file”,详见resin中的配置文件:app-default.xml。其做法也很简单,将之前tomcat的servlet中web.xml中去掉,换成这个:
<servlet-mapping> <servlet-name>resin-file</servlet-name> <url-pattern>/resources/*</url-pattern> </servlet-mapping>
这个配置与之前tomcat的不同,区别在于,我们将静态资源放在WebRoot的resources文件夹下(或者任何一个你喜欢的并且允许放的位置),在页面上直接使用这个css的真正路径“/resources/css/system.css”即可。如果静态资源有任何的变动,只要将servlet中的url-pattern修改或者多配几个</servlet-mapping>即可。