Sam Brannen f5d36aa47a Revert use of Map::computeIfAbsent in thread and tx scopes ... Issues gh-25038 and gh-25618 collectively introduced a regression for thread-scoped and transaction-scoped beans. For example, given a thread-scoped bean X that depends on another thread-scoped bean Y, if the names of the beans (when used as map keys) end up in the same bucket within a ConcurrentHashMap AND an attempt is made to retrieve bean X from the ApplicationContext prior to retrieving bean Y, then the use of Map::computeIfAbsent in SimpleThreadScope results in recursive access to the same internal bucket in the map. On Java 8, that scenario simply hangs. On Java 9 and higher, ConcurrentHashMap throws an IllegalStateException pointing out that a "Recursive update" was attempted. In light of these findings, we are reverting the changes made to SimpleThreadScope and SimpleTransactionScope in commits 50a4fdac6e and 148dc95eb1. Closes gh-25801		2020-09-25 11:00:06 +02:00
..
src	Revert use of Map::computeIfAbsent in thread and tx scopes	2020-09-25 11:00:06 +02:00
.springBeans	Rename modules {org.springframework.*=>spring-*}	2012-01-31 14:37:10 +01:00
spring-context.gradle	Upgrade to BeanShell 2.0b6	2020-04-07 18:06:43 +02:00