Add Commons Pool 2 support
Deprecated CommonsPoolTargetSource (supporting commons pool 1.5+) in favor of CommonsPool2TargetSource with a similar contract. Commons Pool 2.x uses object equality while Commons Pool 1.x used identity equality. This clearly means that Commons Pool 2 behaves differently if several instances having the same identity according to their `Object#equals(Object)` method are managed in the same pool. To provide a smooth upgrade, a backward-compatible pool is created by default; use `setUseObjectEquality(boolean)` if you need the standard Commons Pool 2.x behavior. Issue: SPR-12532
This commit is contained in:
@@ -2049,12 +2049,17 @@ A crucial difference between Spring pooling and SLSB pooling is that Spring pool
|
||||
be applied to any POJO. As with Spring in general, this service can be applied in a
|
||||
non-invasive way.
|
||||
|
||||
Spring provides out-of-the-box support for Jakarta Commons Pool 1.3, which provides a
|
||||
Spring provides out-of-the-box support for Commons Pool 2.2, which provides a
|
||||
fairly efficient pooling implementation. You'll need the commons-pool Jar on your
|
||||
application's classpath to use this feature. It's also possible to subclass
|
||||
`org.springframework.aop.target.AbstractPoolingTargetSource` to support any other
|
||||
pooling API.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Commons Pool 1.5+ is also supported but deprecated as of Spring Framework 4.2.
|
||||
====
|
||||
|
||||
Sample configuration is shown below:
|
||||
|
||||
[source,xml,indent=0]
|
||||
@@ -2064,7 +2069,7 @@ Sample configuration is shown below:
|
||||
... properties omitted
|
||||
</bean>
|
||||
|
||||
<bean id="poolTargetSource" class="org.springframework.aop.target.CommonsPoolTargetSource">
|
||||
<bean id="poolTargetSource" class="org.springframework.aop.target.CommonsPool2TargetSource">
|
||||
<property name="targetBeanName" value="businessObjectTarget"/>
|
||||
<property name="maxSize" value="25"/>
|
||||
</bean>
|
||||
|
||||
@@ -18305,12 +18305,18 @@ A crucial difference between Spring pooling and SLSB pooling is that Spring pool
|
||||
be applied to any POJO. As with Spring in general, this service can be applied in a
|
||||
non-invasive way.
|
||||
|
||||
Spring provides out-of-the-box support for Jakarta Commons Pool 1.3, which provides a
|
||||
Spring provides out-of-the-box support for Commons Pool 2.2, which provides a
|
||||
fairly efficient pooling implementation. You'll need the commons-pool Jar on your
|
||||
application's classpath to use this feature. It's also possible to subclass
|
||||
`org.springframework.aop.target.AbstractPoolingTargetSource` to support any other
|
||||
pooling API.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Commons Pool 1.5+ is also supported but deprecated as of Spring Framework 4.2.
|
||||
====
|
||||
|
||||
|
||||
Sample configuration is shown below:
|
||||
|
||||
[source,xml,indent=0]
|
||||
@@ -18321,7 +18327,7 @@ Sample configuration is shown below:
|
||||
... properties omitted
|
||||
</bean>
|
||||
|
||||
<bean id="poolTargetSource" class="org.springframework.aop.target.CommonsPoolTargetSource">
|
||||
<bean id="poolTargetSource" class="org.springframework.aop.target.CommonsPool2TargetSource">
|
||||
<property name="targetBeanName" value="businessObjectTarget"/>
|
||||
<property name="maxSize" value="25"/>
|
||||
</bean>
|
||||
|
||||
Reference in New Issue
Block a user