Problem with Spring 3.0 when DispatcherServlet is decladed as a Spring bean itself [SPR-6964]

[spring-projects-issues]

Pablo opened SPR-6964 and commented

When multiple DispatcherServlet instances are configured in the root application context, in spring 3.0, all those instances get the refresh events from all application contexts. Each refresh event forces the DispatcherServlet to reconfigure the handler mappings with the context being refreshed. As a result, all DispatcherServlets end up being configured with the same mappings, as if they all where sharing the same spring app context.

---

Affects: 3.0.1

Reference URL: http://forum.springsource.org/showthread.php?p=287750#post287750

Referenced from: commits 461c200

[spring-projects-issues]

Juergen Hoeller commented

I've addressed this for 3.0.2, restricting onApplicationEvent callbacks on DispatcherServlet itself to its local ApplicationContext only. This will be available in tonight's 3.0.2 snapshot - feel free to give it an early try if you have the chance, and let me know whether it works for you.

Juergen