Spring Framework 1.1.1 ReferenceFramework Version 1.1.2 75 unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 194 页 | 1.12 MB | 1 年前3- Spring Framework 1.1.3 ReferenceFramework Version 1.1.3 80 unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 203 页 | 1.15 MB | 1 年前3
- Spring Framework 1.1.2 ReferenceFramework Version 1.1.2 79 unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 199 页 | 1.14 MB | 1 年前3
- Spring Framework 1.1.5 ReferenceFramework Version 1.1.5 80 unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 223 页 | 1.22 MB | 1 年前3
- Spring Framework 1.2.1 ReferenceFramework Version 1.2.1 83 unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 244 页 | 1.30 MB | 1 年前3
- Spring Framework 1.2.0 ReferenceSpring Framework Version 1.2 82 unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 243 页 | 1.29 MB | 1 年前3
- Spring Framework 1.2.2 Reference(roll back is automatic only on unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 269 页 | 1.41 MB | 1 年前3
- Spring Framework 1.2.6 Reference(roll back is automatic only on unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 290 页 | 1.49 MB | 1 年前3
- Spring Framework 1.2.x Reference(roll back is automatic only on unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 289 页 | 1.50 MB | 1 年前3
- Spring Framework 1.2.3 Reference(roll back is automatic only on unchecked exceptions), it's often useful to customize this. On our benchmarks, the performance of Spring declarative transaction management exceeds that of EJB CMT. The usual had to write a single line of JNDI lookup or other EJB plumbing code as part of our application. Benchmarks and experience in real applications indicate that the performance overhead of this approach (which0 码力 | 276 页 | 1.44 MB | 1 年前3
共 50 条
- 1
- 2
- 3
- 4
- 5