Hi, Spring fans! In this installment, Josh Long (@starbuxman) talks to Manning’s The Java Module System author Nicolai Parlog (@nipafx) about Java modularity.
Dear Spring Community,
I am happy to announce the 4.4.0 release of the Spring Tools 4 for Eclipse, Visual Studio Code, and Theia.
Highlights from this release include:
This post was authored by Vedran Pavić
On behalf of the community I’m pleased to announce the releases of Spring Session Corn-M4. This release is picked up by Spring Boot 2.2.0.M6.
Corn-M4The Corn-M4 release is based on:
Spring Session core modules 2.2.0.M4
Spring Session Data Geode 2.2.0.M4
Spring Session Data MongoDB 2.2.0.RC2
Some of the highlights of Spring Session 2.2.0.M4 are:
support for customizing configuration of session repositories using new SessionRepositoryCustomizer/ReactiveSessionRepositoryCustomizer
support for configuring transactional behavior for JdbcOperationsSessionRepository
support for Spring Security’s AuthenticatedPrincipal in SpringSessionBackedSessionRegistry
Complete details of these releases can be found in the changelog.
On behalf of the Spring Batch team, I am pleased to announce the release of Spring Batch 4.2.0.RC1. We have been working on some performance improvements in the core framework, and this post highlights the major changes.
We have made some performance improvements, including:
JpaItemWriterBeanWrapperFieldSetMapperStarting a partitioned step is an area where the framework wasn’t well optimized. In this version, we have dug deep into the partitioning process to figure out the root cause of this performance issue. One of the main steps of the partitioning process is to find the last step execution (to see if the current execution is a restart). We found that looking up the last step execution involved loading all step executions from all job executions for a given job instance in-memory, which is obviously inefficient!
Hi, Spring fans! Welcome to another installment of This Week in Spring - and what a week it is! I’m at the epic annual eventapalooza that is Oracle CodeOne (formerly JavaOne). I just finished a talk today on reactive programming and I’ll have another talk on Kotlin on Wednesday. Don’t miss it!
Meanwhile, we’ve got a ton of things to get to this week so let’s get to it!
In response to our nohttp announcement, Maven Central’s announcement, and JFrog’s announcement, beginning January 15 2020, Spring’s Maven Repository will no longer support HTTP. More concretely, http://repo.spring.io will not respond to requests. Users will need to ensure that they are using https://repo.spring.io
We are not going to redirect from http to https because it perpetuates the vulnerability. When the first request is made over http, a man in the middle (MITM) can prevent the redirect and replace the response with a malicious payload. Users that continue to use http will continue to be vulnerable to MITM attacks.
On behalf of the Spring and Apache Geode communities, it is my pleasure to announce the release of Spring Boot for Apache Geode & Pivotal GemFire (SBDG) 1.1.1.RELEASE as well as 1.2.0.M2.
Bits for 1.1.1.RELEASE are available in Maven Central.
Bits for the 1.2.0.M2 release are available in the Spring Milestone Repository.
SBDG 1.1.1.RELEASE has been upgraded to Spring Boot 2.1.8.RELEASE while SBDG 1.2.0.M2 has been upgraded to Spring Boot 2.2.0.M6.
Additionally, both 1.2.0.M2 and 1.1.1.RELEASE now support running your Spring Boot, Apache Geode ClientCache applications in Pivotal Platform using Pivotal Cloud Cache (PCC) as a specific user.
See Issue-44 for more details.
This is useful if you are deploying Spring Boot applications to Platform using PCC and the app needs read-only access.
In the words of the PCC product director, Pulkit Chandra, "With v1.9.0 we are introducing the concept of "shared service instances", which means an app in Space A can access a Cloud Cache cluster in Space B, but will only be able to "read" the data. This ensures for a healthy pattern of isolation for each domain cluster, where one space has the "read/write" access while others only have "read" access."
This capability and 1.9 are still in development, so this feature is tentatively planned for 1.9. However, in anticipation for this UC in Pivotal Platform, SBDG has you covered.
This feature is not limited to only being used when deploying your Spring Boot apps to Pivotal Platform. SBDG’s support for a specific runtime user works equally well when running your Spring Boot apps off Platform, connected to an externally managed Apache Geode cluster.
See the documentation for more details.
For a complete list of changes in the 1.1.1.RELEASE see the changelog.
For a complete list of changes in the 1.2.0.M2 release, see the changelog.
Hi, Spring fans! Welcome to another extra-special, extra-long installment of A Bootiful Podcast. In this episode, I talk to Spring Framework lead and #2 co-founder of Spring itself, the one, the only, the amazing Juergen Hoeller. We talk about his tenure as the longest and most prolific contributor to Spring; designing clean code; the early days of Spring the project; new features in Spring Framework 5.2; the role of Kotlin, Project Loom, Graal in the Spring ecosystem; Spring’s role in the ecosystem; Java’s place and possibilities; and so much more.
On behalf of the community, I am pleased to announce that the Service Release 3 (SR3) of the Spring Cloud Greenwich Release Train is available today. The release can be found in Maven Central. You can check out the Greenwich release notes for more information. All issues closed in this release across all projects can be found in the Spring Cloud Greenwich.SR3 project on GitHub
Spring Cloud Greenwich.M3 is the first release containing both blocking and non-blocking load balancer client implementations as an alternative to Netflix Ribbon which has entered maintenance mode.
On behalf of the community, I’m excited to announce the availability of Spring Vault 2.2 M1. This release ships with over 90 fixed tickets in total, containing several features, bug fixes, and dependency upgrades.
The most notable new changes are:
Support for PCF-based authentication by using instance identity certificates.
Kotlin extensions.
Builders for RestTemplate and WebClient to customize interceptors, filter functions, and default headers.
Vault namespace support (Vault Enterprise edition only).
@VaultPropertySource now supports versioned key-value backends.
Added listener and events support to LifecycleAwareSessionManager.
Support for the Jetty HTTP Client as an alternative reactive HTTP client.
Reactive support for AWS IAM authentication.
