If you tell Spring 2.5.6 to scan the classpath for application context XML files and you’re deploying to JBoss 5, you may run into this bug; something to do with JBoss’ new Virtual File System (VFS) and its non-standard URLs. It looks like this issue was caught in time to be fixed for 2.5.6, but I guess the SpringSource guys didn’t have time to test it before releasing — the fix doesn’t really work.
It appears there will be a 2.5.7 release within the next couple of months (see slide 14), but it’s probably going to be the first of the commercial-only Spring releases. However, Spring 3.0 is also due within the next couple of months (see slide 5); let’s hope for a fix then. Otherwise, they may have to take JBoss off of the deploy graph on slide 4 
Ales Justin said,
January 11, 2009 at 4:36 am
Some VFS + JBoss info:
– http://jira.springframework.org/browse/SPR-5120?focusedCommentId=41972&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_41972
a developer said,
August 9, 2009 at 6:42 pm
and so the mass exodus to Rails continues
developer said,
November 16, 2009 at 2:29 pm
I’m still looking for information on how to resolve these things. I got spring 3.0 RC1 to work on jboss 5.1 and now i upgraded to RC2 and now nothing works again. You are right about moving to rails.