Getting resources from WEB-INF instead of WEB-INF/classes isn't defined in the spec. So its not portable for an application to put stuff there anyway. The example shown, is just a conflict in metadata extensions between the MC and the Spring deployer. You'd get a similar problem if somebody wrote a deployer that asked for ".xml" extensions :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133728#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...