spring-framework

Spring Framework

Juergen Hoeller bbfc807b0c TransactionInterceptor avoids reflective method search for method identification As of Spring 3.0.4, we were trying to expose the target method signature as transaction name. Unfortunately, the algorithm called the ClassUtils.getMostSpecificMethod helper method which performs a quite expensive reflective search. As of this commit, we're simply concatenating the target class name with the method name, accepting the use of the concrete target class (which is arguably more meaningful for monitoring anyway) even when the method implementation actually sits on a base class. Issue: SPR-9802		13 years ago
..
.settings	Merge 3.1.0 development branch into trunk	15 years ago
src	TransactionInterceptor avoids reflective method search for method identification	13 years ago
.classpath	[SPR-8222] Upgraded to JUnit 4.9.	15 years ago
.project	adding eclipse project meta-data, .classpath file is based on dependencies listed in ivy.xml	17 years ago
build.xml	+ upgrade to AspectJ 1.6.8	16 years ago
ivy.xml	shortened build properties "org.junit.version" to "junit.version" and "org.testng.version" to "testng.version"; reverted SLF4J version back to 1.5.3 (for Hibernate 3.3.1 compatibility)	15 years ago
pom.xml	Increment version to 3.1.3.BUILD-SNAPSHOT	14 years ago
template.mf	fixed package declaration	15 years ago
transaction.iml	Convert CRLF=>LF on files missed earlier	14 years ago