On Dec 13, 2012, at 11:32 , Scott Ferguson <f...@caucho.com> wrote:
> That behavior is part of the spec.
>
> If the mapping already exists, the addMapping does nothing. It's not an
> override.
Wait, really? In my web.xml, I used to have:
<servlet>
<servlet-name>Dispatcher</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<init-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/config/springWebDispatcherConfig.xml</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Dispatcher</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
And you're saying that the new hotness doesn't allow me to do that? Or is there
a way to avoid the resin mapping?
--
Rick
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
