Juergen Hoeller

@gregw I suppose the user who reported that Jetty issue uses Spring MVC on a Servlet stack, or even a custom Servlet arrangement on a similar stack, but not WebFlux....

Superseded by PR #32097.

As a general note: For reactive transactions, there is only a single `TransactionContext` in the pipeline which is to be managed by a single transaction manager. Any interleaved use is...

The difference comes from every nested bean being independently bound: Once the outer `ExampleTestFilter` instance is dereferenced to the inner `SimpleFilter` field, further binding occurs on that `SimpleFilter` instance -...

As far as I was able to reproduce this, the case only applies to multi-nested Map values. There is a dedicated code path for auto-growing map values in `getPropertyHoldingValue` which...

A quick update from Spring's side: Our `setNull` code path still uses `getParameterMetaData` there if no explicit SQL type has been specified, so any improvement towards caching this within the...

The root of the problem is the use of `InputStreamResource` with a pre-obtained `InputStream` here. Once you pass that step, there is always a chance of failing before the InputStream...

In addition to specific notes in the reference documentation, I'm also taking the opportunity to add an `InputStreamResource(InputStreamSource)` constructor where the argument can be provided as a lambda expression that...

@vlsi we appreciate the intention there but unless this becomes a standard JDBC feature - and there ideally even in our JDBC baseline version -, we would effectively introduce separate...

We got some related efforts in Spring's core JDBC support for 6.1.2: https://github.com/spring-projects/spring-framework/pull/29932 https://github.com/spring-projects/spring-framework/issues/19688 https://github.com/spring-projects/spring-framework/issues/21415 In addition to enabling late-bound connection pool routing, a lazy connection setup goes along nicely...