#Tomcat 8 vs 9 update
#Tomcat 8 vs 9 software
#Tomcat 8 vs 9 code

That should hopefully be expanded to include the Tomcat community and the aim is to have a standard API shared between Jetty and Tomcat that applications can useвЂ¦If the expert group decide that they want this in Servlet 4.0, this gives us a good starting model for putting the reactive APIs into Servlet 4.0 as well.Д«eyond that however,В lack of progress from the Expert Group becomes very apparent. Spring and the Jetty folks started a discussion for having Reactive support in a servlet container. Two other things under discussionВ are non-blocking access to request parameters, which would be similar to how you can already do a non-blocking read of the request body and would provide a mechanism by which a developer would be able to read parameters from a request body in a non-blocking way В and reactive support, which is a major theme of Spring 5. It hasn't yet been agreed by the Servlet 4.0 expert group, however. This is something that the JSF expert group have wanted for some time,В and they have proposed an API which has been implemented in Tomcat with some tweaks, and is currently being implemented in Jetty. Under discussion is access to how a request was mapped to the current Servlet - i.e ifВ it mapped using extension mapping, path mapping, and/or which part of the URL actually matched to the wildcard in that mapping. 'ItвЂ™s there so you can work with HttpServletRequest HttpServletResponse in your filter rather than having to work with ServletRequest, ServletResponse and casting,' Thomas said. Along similar lines, an Abstract Base class for HttpFilter has been introduced which is a direct counterpart to HttpServlet.

#Tomcat 8 vs 9 code

Servlet 4.0 also includes a number of default NO-OP methods for listeners to reduce the amount of boiler-plate code you need to write. Really the only place the application will get involved with HTTP/2 is on push requests.' The API for this has been agreed by the expert group and has been implemented already in Tomcat 9.

In terms of the agreed elements of Servlet 4.0 HTTP/2 support will be included, though Thomas pointed out that 'the application isnвЂ™t going to see it. 'Really this falls into threeВ categories: the stuff the expert group has already broadly agreed, the stuff it is sort of working on, and some possible future plans,' Thomas said. In terms of the roadmap, Tomcat 9 will add support for Servlet 4.0.

#Tomcat 8 vs 9 software

He stressed that the presentation represents his personal view on the future of Tomcat and is therefore not necessarily representative of the views of either the Apache Software Foundation or Pivotal. Thomas, a consultant software engineer at Pivotal, has been an Apache Tomcat committer since 2003.

#Tomcat 8 vs 9 update

Mark Thomas ( gave an update on the Apache Tomcat roadmap on the first day of the SpringOne Platform conference in Las Vegas this week, in which he brought up the fact that ongoing delays to Java EE 8, something we've highlighted on InfoQ before, are also causing problems for the Apache Tomcat team.