I’m pleased to announce the release of Spring Security OAuth 2.5.0.
The 2.5.0 release is the final minor release. See the announcement for further details.
Project Page | GitHub | Documentation | Help
I am happy to announce that Spring Fu 0.3.0 is available. As a reminder, Spring Fu is an incubator for Spring Boot programmatic configuration using DSLs in order to configure it explicitly with code in a declarative way, achieving great discoverability thanks to auto-complete.
This new milestone brings back JaFu (the Java DSL) in addition to KoFu (the Kotlin DSL). JaFu was removed in 0.1.0 because at that point, I had not the bandwidth to support both Java and Kotlin DSLs, and in term of API I was not sure that the Java variant was attractive enough to justify such effort, but I have changed my mind for various reasons:
I received a lot of requests to bring it back
Java as a language is moving faster
Getting more control on how configuration is applied is interesting for Java developers as well as Kotlin ones
Functional approach is naturally very efficient on the JVM and a good fit with GraalVM native images
2 great new contributors have join the team: Audrey Neveu with a focus on KoFu and Arjen Poutsma with a focus on JaFu. Welcome to them!
Dear Spring Community,
I am happy to announce the 4.6.2 release of the Spring Tools 4 for Eclipse, Visual Studio Code, and Theia.
Highlights from this release include:
This article continues our blog post series on What’s new in Spring Data Neumann. Today’s installment explains New and Noteworthy in Spring Data Elasticsearch. This blog post was written by P.J. Meisch who maintains the Spring Data Elasticsearch module.
This release addresses more than 140 issues, with more than 30 bugs fixed.
Spring Data Elasticsearch now uses Elasticsearch 7, 7.6.2 in particular. Elasticsearch clusters running on 6.x versions are not supported anymore. The ElasticsearchTemplate class is deprecated as it uses the TransportClient to access Elasticsearch, which itself is deprecated since Elasticsearch version 7.+ Users should switch to ElasticsearchRestTemplate or ReactiveElasticsearchTemplate.
Hi, Spring fans! Welcome to another installment of This Week in Spring! How’re things? My family and I spent the Memorial Day holiday weekend mostly playing video games and trying random new restaurants for delivery. Now, it’s back to the grind and there are a ton of things to look at so let’s get to it!
Reading time: about 6 minutes
Coding time: about 15 minutes
If you’ve been following this series, by now, you’ll have built a Spring Boot prototype that illustrates many of the features present in RSocket. This code isn’t production code, though; it’s a prototype, a stepping stone on your RSocket journey. For production code, I’d expect all the usual quality assurance and testing rules to apply. So in this exercise, I’ll show you how to write integration tests for RSocket responders, so you can get one step closer to production.
Hi Spring fans! In today’s installment Josh Long (@starbuxman) talks to Kohsuke Kawaguchi (@kohsukekawa) who needs no introduction - one of the original contributors to JAXB, COM4J, and a host of all sorts of other projects, and is the founder and CEO of Launchable. Oh, did I mention he also created Jenkins, the most popular CI server ever? Enjoy!
With Spring Data JDBC 2.0, we had to introduce some breaking changes. The goal of this article is to help in the migration process.
Use the default letter casing for custom column and table names or quote the names for table generation exactly as used in the annotations.
Use AbstractJdbcConfiguration for custom configuration of the application context.
Review event-handling code and ensure the data you try to use is not null.
Spring Data JDBC 1.x uses table and column names mostly without changing them. This causes problems when you use an SQL key word as a property or entity name or when you tried to use some special character in a column name.
For this reason Spring Data JDBC 2.0 quotes all identifiers by default. This makes the names case-sensitive, at least for most databases. Since we also, by default, convert the names generated into the default letter casing used by the database, this should not cause any problems, assuming you used no quotes in the CREATE TABLE statements, as most people do.
For example, consider a Student entity, as follows:
class Student {
@Id
Long id;
String name;
}A matching table for H2 could look like this:
CREATE TABLE STUDENT
(
ID SERIAL PRIMARY KEY,
NAME VARCHAR(30)
);That example is the same as in previous versions of Spring Data JDBC. Things change when you specify column or table names explicitly with @Column, @Table, or @MappedCollection. In this case, we assume that you specify the name exactly as you want it to be used and, therefore, the table definition has to use quoted identifiers or the names have to use the default letter casing of your database, as in this modified student example:
@Table("student")
class Student {
@Id
Long id;
@Column("LAST_NAME")
String name;
}A matching table for H2 could look like this:
CREATE TABLE "student" -- (1)
(
ID SERIAL PRIMARY KEY,
LAST_NAME VARCHAR(30) -- (2)
);The table name must be quoted, because it is given in lower-case letters but H2 converts unquoted SQL identifiers to upper case by default.
LAST_NAME does not have to get quoted because it already uses the default letter casing.
See below how to disable the forced quoting if you really want to.
Spring Cloud Data Flow team is pleased to announce the release of 2.5.1.
This release includes some bug fixes with the some of the notable changes as follows:
Spring Boot 2.2.7 and Spring Cloud Hoxton.SR4. New dependencies from these fixed an issue in Spring Data Rest which caused repository mappings DATAREST-1502 to stop working and effectively caused UI and Skipper to start behaving erratically in Data Flow 2.5.0.