Spring MVC, two instances of configuration instead of one

Question

I\'m starting to learn about Spring MVC. I\'m trying to get rid of all Spring XML configuration. Here is my web.xml:

Answer 1

I found that by including my @Configuration classes as a ContextConfigLocation in stead of identifying them through Component scanning, I avoid a memory leak where duplicate ListableBeanFactories would be created and lock up the Hibernate SessionFactory.