I am porting a legacy app to JBoss AS7 and ran into the exact same issue. Spring 3.1 works great, but you're right 2.5 doesn't work. I even created an ultra-tiny demo with 1 class to rule out the rest of my app being a culprit in breaking it.

I have no idea if the bug is because of Servlet 3.0 or AS7. However, it definitely doesn't work.

I just upgraded my version of Spring...the POM became messy, but it seems to work well so far. It hasn't gone through a full QA cycle, though.

Thanks,Steven

If anyone wants help reproducing this issue, create a project with the archetype and add:

I've no clue about Spring. So one of you will have to explain what exactly is not working. Is that class annotated with @Component not being scanned for that annotation or is it something else? And what does the application packaging look like?

Hmm, simply changing Spring fixed the error, but I haven't yet completed the final step of the full wiring and proving the UI is viewing the component correctly. We're not using MVC. I can see through debugging that the container is initializing the beans correctly, simply by upgrading the library, though. If I find that additional work needs to be done to get the UI to read the beans, I'll update this post.