On behalf of the community, I’m pleased to announce the release of Spring Security 3.2.10, 4.1.4, and 4.2.1 which fix CVE-2016-9879. Users are encouraged to update immediately.
It is important to note that Spring Framework 3.2.x has reached EOL. As with Spring Framework, we expect all users to upgrade to 4.2.1+ for further support. Detailed instructions (including samples) on migrating both XML and Java Config based projects can be found in the reference appendix
On behalf of the community, I’m pleased to announce the release of Spring LDAP 2.2.1 and 2.3 RC1.
A special thanks to Mark Paluch for getting spring-data-ldap aligned on the Spring Data side!
Spring LDAP 2.3 RC1
This release brings in a new era for Spring Data compatibility. Integration for Spring LDAP and Spring Data has been moved to spring-data-ldap so that it can partake in the Spring Data release train and ensure compatibility with the latest and greatest Spring Data code base. For additional details refer to the changelog
Spring LDAP 2.2.1
This release contains some minor bug fixes along with an update to make updates to newer versions of Spring Data more seamless. For additional details refer to the changelog…
4.3.5 is a significant refinement release with 37 enhancements (including e.g. WebSocket support for the recently released Jetty 9.4) and several bug fixes, serving as the basis for the upcoming Spring Boot 1.4.3 release.
Please note that the 4.2.9 and 3.2.18 bug fix releases are the last in their respective line, with 4.2.x being superseded by 4.3.x now and 3.2.x reaching its EOL point. Going forward, we expect all users to upgrade to 4.3.5+ for further support.
All three releases also fix a path traversal vulnerability (CVE-2016-9878) in ResourceServlet.
If you happen to be among its rare users, please upgrade ASAP. Note that this functionality has been superseded for years already and will get removed in 5.0, so we actually recommend a migration to Spring MVC's resource handling features within a DispatcherServlet…
The plugin's been rewritten in Java and its API has been formalised. A clear separation between that API and the plugin's internals has been introduced. This has required a few breaking changes but you are unlikely to be affected if you were using the Groovy DSL.
Converting to Java and formalising the API has also enabled a couple of enhancements:
### Official support for Gradle 3
Previously, the plugin was written in Groovy and attempted to support Gradle 1, 2, and 3. This proved to be overly ambitious. The two main problems were binary incompatibilities across the three different Groovy runtimes (1.8, 2.3, and 2.4) and breaking changes across the three versions of Gradle. To address these, the Gradle team's recommendation was to rewrite the plugin in Java and to drop support for Gradle 1.x. This release does just that, with the plugin's main code now being 100% Java and Gradle 2.9 now being the minimum supported version. As a result, Gradle 3.x is now officially supported and it should be easier to support new versions of…
On behalf of the community, I’m pleased to announce the release of Spring Session 1.3.0.RELEASE. This release evolved through 1.3.0.M1, 1.3.0.M2, 1.3.0.RC1, and 1.3.0.RELEASE
Releases | Rajini Sivaram | December 15, 2016 | ...
We are pleased to announce the release of the first milestone of Reactor Kafka 1.0.0.
What is Reactor Kafka?
Reactor Kafka is a reactive API for Apache Kafka based on Project Reactor. Reactor Kafka API enables messages to be published to Kafka topics and consumed from Kafka topics using functional APIs with non-blocking back-pressure and very low overheads. This enables applications using Reactor to use Kafka as a message bus or streaming platform and integrate with other systems to provide an end-to-end reactive pipeline.
The value proposition for Reactor Kafka is the efficient utilization of…
We are pleased to announce that the first milestone for the 5.0 version of Spring Integration is now available.
This is a new major version, based on Spring Framework 5.0 and requires Java 8; this is the biggest change so far, but the following are also included:
The Java DSL is now rolled into the framework itself; there are some minor changes to the DSL, such as the removal of the .handleWithAdapter() methods and some general Factory classes. A complete discussion of the DSL changes can be found in the Migration Guide.
First class support for TCP/UDP has been added to the DSL.
Spring Integration is now based on Reactor 3.0 and Messaging Gateway Promise methods now have to be changed to return Mono.
You can now configure mid-flow transactions via TransactionHandleMessageAdvice for adviceChain Messaging Annotations attribute and <transactional> sub-element when using XML configuration.