Set Spring MVC context when RequestContextFilter is absent

[Mishenevd]

Summary

Zen creates the Spring MVC context only by instrumenting RequestContextFilter#doFilterInternal. WebMvcAutoConfiguration.requestContextFilter() is @ConditionalOnMissingBean({RequestContextListener.class, RequestContextFilter.class}), so when the application registers a RequestContextListener bean the filter is never added to the chain. The context is then never set: controllers log Received Spring Annotations, but no context set on every request, and input/IP/user-agent inspection does not run.

Fix

Add SpringMVCDispatcherWrapper wrapping FrameworkServlet#processRequest — the entry point of every DispatcherServlet request, independent of the filter chain — which creates the context when none exists. The filter sets a per-request marker the fallback checks, so the normal path is unchanged and the context is not created twice.

Testing

Reproduced on Spring Boot 4.0.7 (Spring 7.0.8 / Tomcat 11.0.22) with a RequestContextListener bean: exact error on every request. Verified with the fix, forcing a single Tomcat worker thread, 3 sequential requests:

• filter absent (RequestContextListener present): 0 errors, 3 fresh contexts, correct per-request routes;
• filter present (default): 0 errors, 3 fresh contexts (no double creation), behavior unchanged.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!