Spring Framework 1.2.7 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * refined StopWatch to not add new lines for "shortSummary()" but rather only for "prettyPrint()" ConnectionHolder to explicitly fetch a current Connection on demand and release it on receiving "released" Package org.springframework.orm * removed resource acquisition methods with "allowSynchronization"0 码力 | 87 页 | 248.22 KB | 1 年前3- Spring Framework 1.2.8 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * refined StopWatch to not add new lines for "shortSummary()" but rather only for "prettyPrint()" ConnectionHolder to explicitly fetch a current Connection on demand and release it on receiving "released" Package org.springframework.orm * removed resource acquisition methods with "allowSynchronization"0 码力 | 89 页 | 254.65 KB | 1 年前3
- Spring Framework 1.2.x ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * refined StopWatch to not add new lines for "shortSummary()" but rather only for "prettyPrint()" ConnectionHolder to explicitly fetch a current Connection on demand and release it on receiving "released" Package org.springframework.orm * removed resource acquisition methods with "allowSynchronization"0 码力 | 94 页 | 267.57 KB | 1 年前3
- Spring Framework 2.0.0 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * changed ConcurrencyThrottleSupport's default "concurrencyLimit" to -1 (keeping ConcurrencyThrottleInterceptor0 码力 | 33 页 | 91.32 KB | 1 年前3
- Spring Framework 2.0.1 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * changed ConcurrencyThrottleSupport's default "concurrencyLimit" to -1 (keeping ConcurrencyThrottleInterceptor0 码力 | 37 页 | 103.65 KB | 1 年前3
- Spring Framework 2.0.2 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * changed ConcurrencyThrottleSupport's default "concurrencyLimit" to -1 (keeping ConcurrencyThrottleInterceptor0 码力 | 41 页 | 115.44 KB | 1 年前3
- Spring Framework 2.0.3 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * changed ConcurrencyThrottleSupport's default "concurrencyLimit" to -1 (keeping ConcurrencyThrottleInterceptor0 码力 | 49 页 | 138.10 KB | 1 年前3
- Spring Framework 2.0.4 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * changed ConcurrencyThrottleSupport's default "concurrencyLimit" to -1 (keeping ConcurrencyThrottleInterceptor0 码力 | 52 页 | 148.51 KB | 1 年前3
- Spring Framework 2.0.5 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * changed ConcurrencyThrottleSupport's default "concurrencyLimit" to -1 (keeping ConcurrencyThrottleInterceptor0 码力 | 56 页 | 157.72 KB | 1 年前3
- Spring Framework 2.0.6 ChangelogWeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * changed ConcurrencyThrottleSupport's default "concurrencyLimit" to -1 (keeping ConcurrencyThrottleInterceptor0 码力 | 57 页 | 161.42 KB | 1 年前3
共 27 条
- 1
- 2
- 3