servicecppcon_add_library(service LIBRARIES Asio::asio) add_subdirectory(tests)0 码力 | 1 页 | 73.00 B | 5 月前3- Spring Framework 3.0.0 Changelog@DependsOn annotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 9 页 | 24.89 KB | 1 年前3
- Spring Framework 3.0.1 Changelog@DependsOn annotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 11 页 | 29.04 KB | 1 年前3
- Spring Framework 3.0.2 Changelog@DependsOn annotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 12 页 | 32.08 KB | 1 年前3
- Spring Framework 3.0.3 Changelog@DependsOn annotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 13 页 | 36.82 KB | 1 年前3
- Spring Framework 3.0.4 Changelog@DependsOn annotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 15 页 | 41.47 KB | 1 年前3
- Spring Framework 3.0.5 Changelog@DependsOn annotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 17 页 | 45.75 KB | 1 年前3
- Spring Framework 3.0.x Changelog@DependsOn annotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 19 页 | 52.25 KB | 1 年前3
- Spring Framework 3.0.6 Changelogannotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 18 页 | 49.26 KB | 1 年前3
- Spring Framework 3.1.0 Changelog@DependsOn annotations for scanned components * custom stereotype annotations can be meta-annotated with @Service, @Controller etc as well * @Scope and @Transactional are now supported as meta-annotations on custom into Java types * ProceedingJoinPoint resolves parameter names using ASM-based parameter name discovery * MethodInvocations and ProceedingJoinPoints always expose original method (not bridge) * bridge0 码力 | 22 页 | 60.32 KB | 1 年前3
共 73 条
- 1
- 2
- 3
- 4
- 5
- 6
- 8