Spring 12 release notes pdf

You can disable this behavior by setting spring. Spring Boot 2. This release switches to Cassandra v4 that brings a number of backward incompatible changes. If you were relying on ClusterBuilderCustomizer to customize the Cluster , this concept no longer exists in v4 and has been replaced by two more specific customizers:.

DriverConfigLoaderBuilderCustomizer customizes the properties of the driver. Please use this for any property that is not exposed yet. The Cassandra v4 driver no longer has automatic local DC inference from contact points. As a result, the "local-datacenter" property must be set with the default load balancing policy and the contact points must be of that data center. A new spring. To connect to a cluster, you should now use spring.

If you were extending CouchbaseConfiguration to customize the environment, please use ClusterEnvironmentBuilderCustomizer to do so in a more idiomatic fashion. Support for the Jest library has also been removed in this release.

This release switches to MongoDB 4 and harmonizes the reactive and imperative drivers. One notable change is that MongoClientSettingsBuilderCustomizer beans are now applied when using the imperative driver. Previously they were only applied in the reactive case. With this harmonization, the non reactive infrastructure is no longer provided if you use spring-boot-starter-data-mongodb-reactive. If you need to use the imperative infrastructure on startup e.

MongoOperations , consider adding spring-boot-starter-data-mongodb. The open session in view interceptor for Neo4j is now disabled by default. If you need to enable it again, use the standard spring. The details of the Neo4j health indicator now contains the version and edition of the server, as shown in the following example:.

Service Level Agreements have been renamed to Service Level Objectives and the boundary is expressed as a double rather than a long. Wavefront metrics are now exported via WavefrontSender. As a result the read and connection timeout properties are no longer honoured. This release upgrades to Jackson 2. Date and java. The Spring Cloud Connectors starter was deprecated in 2. The configuration properties for configuring the threads used by embedded Servlet web servers Jetty, Tomcat, and Undertow have moved to dedicated threads groups.

The properties can now be found in server. The old properties remain in a deprecated form to ease migration. The error message and any binding errors are no longer included in the default error page by default. This reduces the risk of leaking information to a client.

Supported values are always , on-param , and never. The auto-configured disk space health indicator no longer requires the path that is monitored to exist when the application starts. A non-existent path will be detected as having zero usable space resulting in a down response from the indicator. Any manual configuration of developmentOnly should be removed from your Gradle build scripts as its presence will result in a build failure with the message cannot add a configuration with name 'developmentOnly' as a configuration with that name already exists.

If you were relying on that, you can restore that behaviour as follows:. For consistency with SpringApplication , ApplicationContextRunner now disables bean overriding by default. If you need to use bean overriding for a test, withAllowBeanDefinitionOverriding can be used to enable it.

Security improvements: Avoided instantiation of new objects and calls to static classes in restricted expression evaluation mode , both for OGNL and SpringEL-based scenarios. Users of Spring : Avoided execution of view names as a fragment expressions when the view name is contained in the URL path or query parameters. Issues fixed: Fixed numbers. Fixed package-list not being produced for JavaDoc since JDK 11 started being used for compiling the project.

Feature changes: Users of Spring 5. If you are using this plugin, make sure to specify a version in your own pluginManagement. If you currently use mainClassName , for example:. SpringBootTest no longer configures available monitoring systems and only provide the in-memory MeterRegistry. If you were exporting metrics as part of an integration test, you can add AutoConfigureMetrics to your test to restore the previous behaviour.

Reflecting the Spring Boot release compatibility policy , code deprecated in Spring Boot 2. Code deprecated in Spring Boot 2. See the Spring Data wiki for release details. This release brings support of reactive repositories and rely on a separate auto-configuration for the Neo4j driver. As a result, it is now possible to use Neo4j with or without Spring Data.

Health checks for Neo4j use the Driver and are available as long as the Neo4j driver is configured. The minimum supported version remains Java 8. When using constructor binding the name of the property is derived from the parameter name.

This can be a problem if you want to use a java reserved keyword. For such situations, you can now use the Name annotation, something like:. This release enables layered jars and include the layertools by default. This should improve the efficiency of generated image using the build pack out-of-the-box and lets you benefit of that feature when crafting custom Dockerfile.

You can use the spring. See this section of the reference guide for more details. The spring. Each pair is declared in its own file, with the filename forming the property key, and the file contents providing the value. For a complete example, see the updated reference documentation. Some Cloud platforms only allow you to volume mount files without a file extension.

The Origin interface has been updated with a new getParent method. This allows us to provide a full origin chain that can show exactly where an item originated from. For example, you might use spring. The Origin of properties loaded from this second file will have a parent that points back to the orginal import declaration.

A new startup actuator endpoint is now available that shows information about your applications startup. The endpoint can help you identify beans that are taking longer than expected to start. This work builds on the application startup tracking feature that was recently added to Spring Framwork 5.

You can read more about the feature in the Spring Framework reference documentation. The new actuator API is documented here. The Maven plugin spring-boot:build-image goal and Gradle plugin bootBuildImage task now have the ability to publish the generated image to a Docker registry.

See the Maven and Gradle plugin documentation for more details on configuring the plugins for publishing images. The Maven and Gradle documentation have been updated to show the new configuration. The image builder used by the Maven plugin spring-boot:build-image goal and Gradle plugin bootBuildImage task by default has been upgraded to the latest Paketo images.

The spring-boot:build-image Maven goal now puts all project modules dependencies in the "application" layer. This means that if you have multiple project modules in your build, they will now all end up in the same layer.

See the updated Maven documentation for details. The bootBuildImage Gradle task now puts all project modules dependencies in the "application" layer. See the updated Gradle documentation for details. The number of pending requests and the lock wait duration are also recorded. To enable the feature, set spring. The new properties are:. A new property has been added to support configuration of the actuators management endpoint with either the servlet or reactive web stack:. RC1 Spring Cloud Consul 2.

RC2 issues Spring Cloud Config 2. RC2 issues Spring Cloud Gateway 2. RC2 issues Spring Cloud Greenwich. RC1 Greenwich. M3 Spring Cloud Greenwich. M3 Spring Cloud Zookeeper 2. M1 Spring Cloud Gateway 2. M3 Spring Cloud Bus 2. M2 issues Spring Cloud Consul 2. M2 Spring Cloud Stream Fishtown. RC2 Spring Cloud Aws 2. M3 Spring Cloud Commons 2. M2 Spring Cloud Vault 2. M2 Spring Cloud Netflix 2.

M3 Spring Cloud Openfeign 2. M2 Spring Cloud Kubernetes 1. M2 issues Spring Cloud Gcp 1. M3 Spring Cloud Config 2. M3 Spring Cloud Dependencies Greenwich. M3 Spring Cloud Contract 2. M2 issues Spring Cloud Sleuth 2. M2 issues Spring Cloud Build 2. RC2 Spring Cloud Security 2. M1 Spring Cloud Function 2. M1 issues Spring Cloud Cloudfoundry 2. M1 Spring Cloud Starter Greenwich.