Juergen Hoeller

We are not aware of an immediate alternative there. You might have to fork/patch spring-modules-jbpm31 yourself if needed. Please note that spring-modules-jbpm31 has never been officially supported and is unmaintained...

Superseded by PR #29423.

For completeness, note that the general `DataSource` usage pattern is incomplete in the examples above: For every `DataSource.getConnection()` call, there needs to be a corresponding `Connection.close()` call within the same...

This turns out to be rather involved due to the differences between URI and URL rules and the restricted behavior of the `java.net.URI#toURL()` method. As a first step, #29486 prepares...

With a combination of URI construction from a cleaned path and subsequent defensive URL conversion, all our tests pass. This is still rather involved but seems to be equivalent for...

@spencergibb we consider addressing this in `UriTemplate` itself for tomorrow's 6.1.5 release, and possibly also for a backport to the 6.0.18 and 5.3.33 releases.

This is a long-standing consequence of Spring's factory method overloading in combination with generic return types. Factory methods are primarily meant to refer to a specific component, potentially overloaded for...

A documentation note certainly makes sense here, warning against use of factory method name resolution against an inconsistent set of target methods, and naming Mockito as an example. Let's reopen...

Bean method overloading is effectively turned off by default as of 6.0, see #22609. From that perspective, formal deprecation does not seem urgent and might be better off in 7.0.

@contivero good point, I've added a documentation note with a suggestion along those lines.