Support for Servlet 4.0 API [SPR-12674]

[spring-projects-issues]

Juergen Hoeller opened SPR-12674 and commented

A placeholder for dedicated Servlet 4.0 support, such as declaring push resources in an MVC controller. Targeting Spring Framework 5.0 in Q2 2017, against Servlet 4.0 public final draft.

---

Issue Links:

• Comprehensive Servlet 3.1 support in spring-web and spring-test [SPR-14467] #19036 Comprehensive Servlet 3.1 support in spring-web and spring-test
• Drop Servlet 2.5 runtime compatibility [SPR-13189] #17781 Drop Servlet 2.5 runtime compatibility
• Support for JSON Binding API (JSON-B) [SPR-14923] #19490 Support for JSON Binding API (JSON-B)
• Compatibility with Servlet 4.0 final draft [SPR-15379] #19942 Compatibility with Servlet 4.0 final draft
• Upgrade to Servlet API 4.0 for MVC (PushBuilder and Servlet mocks) [SPR-15879] #20434 Upgrade to Servlet API 4.0 for MVC (PushBuilder and Servlet mocks)
• Make use of Servlet 4.0 mapping introspection when available [SPR-15320] #19883 Make use of Servlet 4.0 mapping introspection when available

Referenced from: commits eeb01db, 199aa77

2 votes, 7 watchers

[spring-projects-issues]

Juergen Hoeller commented

The Servlet 4.0 b02 API was released a few days ago, appearing feature-complete.

It turns out that there are only really new setSessionTimeout and addJspFile methods on ServletContext, both of which we can easily support in our MockServletContext while retaining Servlet 3.1 compatibility. The new GenericFilter and HttpFilter base classes are overdue for a decade but don't really matter for Spring at this point.

The single new feature addition is the PushBuilder mechanism: HttpServletRequest.getPushBuilder() is fortunately declared as a default method, so it doesn't get in the way of our MockHttpServletRequest's Servlet 3.1 compatbility. Programmatic access can be streamlined through direct support for a PushBuilder handler method argument in ServletRequestMethodArgumentResolver which we can easily do for 5.0.

A declarative resource-push variant seems too first-class and too specific at this point, and therefore not within the scope of this ticket. If we ever provide something in that direction, it needs to be well-integrated with our static resource handling support.

[spring-projects-issues]

Juergen Hoeller commented

Servlet 4.0 b03 is available in the meantime, adding setters and getters for a default request/response character encoding to the ServletContext interface, which we're supporting on our MockServletContext for 5.0 RC1 now.

[spring-projects-issues]

Juergen Hoeller commented

We've tested against Servlet 4.0 b05 in the meantime, still waiting for b06 which corresponds to the recently submitted Servlet 4.0 public final draft. This might work out for our 5.0 RC1 still; otherwise we'll pick it up for RC2, along with a corresponding Tomcat 9 milestone.