Dashboard

SWS-966 Increase to Spring Framework 4.2 and Spring Security 4.0

INT-4103: Fix Amqp Channel Header Mappers

JIRA: https://jira.spring.io/browse/INT-4103

(cherry picked from commit 89e0d13)

INT-4103: Fix Amqp Channel Header Mappers

JIRA: https://jira.spring.io/browse/INT-4103

Next development version

Release version 2.3.1.RELEASE

Checkstyle Fixes for Previous Commit

LiveBeansView exposes aliases as well

Issue: SPR-14632

(cherry picked from commit 57cb7c7)

LiveBeansView exposes aliases as well

Issue: SPR-14632

INT-3913 Remove/resolve deprecation from the past

JIRA: https://jira.spring.io/browse/INT-3913

  • Remove deprecated classes and methods/constructors, deprecated XML attributes
  • Remove `TcpConnectionEventListeningMessageProducer` and rework tests logic to the `ApplicationEventListeningMessageProducer`
  • Fix several typos
  • Remove/rework deprecated entities mentioning
  1. … 72 more files in changeset.

Polishing (cherry picked from commit 430180a)

Polishing

Wrap RestTemplate extractor exceptions in RestClientExceptions

When using a `RestTemplate` instance within a Spring MVC application,

client exceptions may propagate in the MVC stack and can be wrongly

mapped by server `ExceptionHandlers`, leading to a wrong HTTP response

sent to the MVC client.

The `RestTemplate` instance uses `HttpMessageConverter` to decode

the remote service responses; and when those fail decoding an HTTP

response, they can throw an `HttpMessageNotReadableException`. That

exception then bubbles up through the `HttpMessageConverterExtractor`,

`RestTemplate` and the whole MVC stack, later mapped to HTTP 400

responses, since those exceptions can also be throws by the server stack

when the incoming requests can't be deserialized.

This commit wraps all `IOException` and `HttpMessageNotReadableException`

instances thrown by the extractor into `RestClientException`` instances.

It's now easier to consistently handle client exceptions and avoid such

edge cases.

Issue: SPR-13592

Polishing

Polishing (cherry picked from commit e828be9)

Avoid getParameterType use with Oracle 12c driver by default

Issue: SPR-14629

Issue: SPR-14574

Issue: SPR-14191

Avoid getParameterType use with Oracle 12c driver by default

Issue: SPR-14629

Issue: SPR-14574

Issue: SPR-14191

(cherry picked from commit 52447ef)

Support target type in JsonPath assertions

This change adds support for a target type in JsonPath assertions in

Spring MVC Test.

The existing assertValue(String expression, Object expectedValue)

transparently falls back on using an alternative JsonPath API that

allows specifying the target type to coerce to.

There is also a new overloaded method

assertValue(String expression, Matcher<T> matcher, Class<T> targetType)

for use with Hamcrest matchers where the target type can be specified.

Issue: SPR-14498

(cherry picked from commit 7fdb892)

Support target type in JsonPath assertions

This change adds support for a target type in JsonPath assertions in

Spring MVC Test.

The existing assertValue(String expression, Object expectedValue)

transparently falls back on using an alternative JsonPath API that

allows specifying the target type to coerce to.

There is also a new overloaded method

assertValue(String expression, Matcher<T> matcher, Class<T> targetType)

for use with Hamcrest matchers where the target type can be specified.

Issue: SPR-14498

Fix server errors for invalid If-None-Match request headers

HttpEntityMethodProcessor should not throw IllegalArgumentExceptions for

invalid If-None-Match headers.

For those cases, this commit makes sure that both

`HttpEntityMethodProcessor` and `ServletWebRequest` have a consistent

behavior and stop processing the request as conditional and leave the

handler handle it.

Issue: SPR-14559

Fix server errors for invalid If-None-Match request headers

HttpEntityMethodProcessor should not throw IllegalArgumentExceptions for

invalid If-None-Match headers.

For those cases, this commit makes sure that both

`HttpEntityMethodProcessor` and `ServletWebRequest` have a consistent

behavior and stop processing the request as conditional and leave the

handler handle it.

Issue: SPR-14559

Simplify exception handling in JsonPathExpectationsHelper

Consistent use of JDK 7 StandardCharsets over Charset.forName

Issue: SPR-14492

  1. … 3 more files in changeset.

Revert "Consistently use annotation attributes in refdoc"

This reverts commit bbd5993945f91fdfcaecf86fc43e22e073753a36.

Polishing

Consistent use of Charset.forName over JDK 7 StandardCharsets in 4.x line (cherry picked from commit 2a82b8f)

Consistent use of Charset.forName over JDK 7 StandardCharsets in 4.x line

Moved encodeHttpHeaderFieldParam method to HttpHeaders itself (including tests)

This commit also sets the test source encoding to UTF-8.

Issue: SPR-14547

Moved encodeHttpHeaderFieldParam method to HttpHeaders itself (including tests)

This commit also sets the test source encoding to UTF-8.

Issue: SPR-14547

(cherry picked from commit a8f7f75)

Consistently use annotation attributes in refdoc

Revert to snapshots

    • -1
    • +1
    /tests/annotation/custom-grant/pom.xml
  1. … 19 more files in changeset.