Feature-complete Spring Framework 5.0 RC1 is here
© Shutterstock / Uniyok
A feature-complete Spring Framework 5.0 release candidate has just become available. The next release candidate should arrive later this month and the final release is expected in late June. Let’s revisit the four biggest Spring Framework 5 feature themes.
Juergen Hoeller, the co-founder and project lead of the Spring Framework open source project, announced the release of Spring Framework 5.0 RC1. This feature-complete release candidate comes with a Java 8+ baseline and many infrastructure refinements such as their own Commons Logging bridge autodetecting Log4j 2, SLF4J, JUL by default; streamlined use of Servlet 3.1+; and early support for JUnit 5.0 M4, Hoeller wrote in the blog post.
Major Spring Framework 5 feature themes
Hoeller emphasized that Spring Framework 5 will have the following feature themes:
- Reactive programming: introducing the new Spring WebFlux framework built on Reactor 3.1, with support for RxJava 1.3 & 2.1 and running on Tomcat, Jetty, Netty or Undertow.
- Functional style with Java 8 & Kotlin: several API refinements and Kotlin extensions across the framework, in particular for bean registration and functional web endpoints in WebFlux.
- Integration with Java EE 8 APIs: support for Servlet 4.0, Bean Validation 2.0, as well as the JSON Binding API (as an alternative to Jackson and Gson in Spring MVC).
- Ready for JDK 9: fully aligned with JDK 9 at runtime, on the classpath as well as the module path (on the latter: as “automatic modules” for the time being).
If you want to get an overview of the changes made since 4.3, checked out the updated What’s New page.
Spring Boot 2: First milestone due next week
He also reminded readers that the first Spring Boot 2 milestone is due early next week. The current schedule can be found here.
Speaking of Spring Boot 2, JAXenter talked to Stéphane Nicoll, software engineer at Pivotal about what’s new apart from Spring 5 support.
As Spring Boot is much more opinionated, a new generation allows us to revisit these opinions and rework some of them when it makes sense. For instance, we completely rewrote the Gradle plugin from scratch with the feedback of the community and we have heavily reworked how configuration keys are handled internally. This release is mainly about setting up firm foundations and a good base to build on.
Nicoll also said that reactive programming has a supportive role in Spring Boot 2.0:
If you decide to use the WebFlux stack, we will auto-configure the necessary bits the same way we do it for WebMvc today. And if you decide to use the functional route, we will detect that as well. We have plans to rework existing components to support the reactive stack but mostly there is not going to be many user-facing changes. WebFlux will be the entry point, much like WebMvc is today.
Read the entire interview here.