Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move bundled client-side resources (.js, .css) to META-INF/web-resources instead of META-INF [SWF-1388] #575

spring-operator opened this issue Aug 25, 2010 · 1 comment


Copy link

Rossen Stoyanchev opened SWF-1388 and commented

Placing resources in META-INF/web-resources is recommended by the new resource serving mechanism in Spring MVC 3.0.4. Moving bundled client-side resources (Spring.js, Spring-Dojo.js, Dojo Toolkit, etc) to the recommended location would allow applications to use this configuration:

<mvc:resources location="/, classpath:/META-INF/web-resources/" mapping="/resources/**"/>

Instead of this:

<mvc:resources location="classpath:/META-INF/dojo/" mapping="/resources/dojo/"/>
<mvc:resources location="classpath:/META-INF/dijit/" mapping="/resources/dijit/
<mvc:resources location="classpath:/META-INF/spring/" mapping="/resources/spring/"/>
<mvc:resources location="/" mapping="/resources/

Affects: 2.2.0.M1

Issue Links:

  • ROO-1388 Security issue with roo 1.1.0.M3
    ("is depended on by")
Copy link
Contributor Author

Rossen Stoyanchev commented

All client-side resources (.js, .css, etc.) bundled in the spring-js jar have been moved to META-INF/web-resources. The change should be transparent for applications using the ResourceServlet, which checks for classpath resources under META-INF/web-resources.

As before the ResourceServlet continues to check directly under META-INF and can also be customized to use a classpath prefix other than META-INF via the servlet init parameter "jarPathPrefix". Regardless of any of that the ResourceServlet always checks for resources under META-INF/web-resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants