capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The TransactionInterceptor defined here depends on a PlatformTransactionManager definition Commons Attributes appears to be the most promising. All these require a special pre- or post-compilation step. Spring Framework Version 1.1.2 80 8.2. Spring's metadata support In keeping with its provision

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The TransactionInterceptor defined here depends on a PlatformTransactionManager definition Commons Attributes appears to be the most promising. All these require a special pre- or post-compilation step. Spring Framework Version 1.1.3 85 8.2. Spring's metadata support In keeping with its provision

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The TransactionInterceptor defined here depends on a PlatformTransactionManager definition Commons Attributes appears to be the most promising. All these require a special pre- or post-compilation step. Spring Framework Version 1.1.2 84 8.2. Spring's metadata support In keeping with its provision

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The TransactionInterceptor defined here depends on a PlatformTransactionManager definition Commons Attributes appears to be the most promising. All these require a special pre- or post-compilation step. Spring Framework Version 1.1.5 85 8.2. Spring's metadata support In keeping with its provision

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The TransactionInterceptor defined here depends on a PlatformTransactionManager definition Framework Version 1.2.1 88 appears to be the most promising. All these require a special pre- or post-compilation step. 8.2. Spring's metadata support In keeping with its provision of abstractions over important

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The TransactionInterceptor defined here depends on a PlatformTransactionManager definition Framework Version 1.2 87 appears to be the most promising. All these require a special pre- or post-compilation step. 8.2. Spring's metadata support In keeping with its provision of abstractions over important

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The /annotation directory of the JPetStore sample application contains an analogous example Commons Attributes appears to be the most promising. All these require a special pre- or post-compilation step. 8.2. Spring's metadata support In keeping with its provision of abstractions over important

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The /annotation directory of the JPetStore sample application contains an analogous example Commons Attributes appears to be the most promising. All these require a special pre- or post-compilation step. 9.2. Spring's metadata support In keeping with its provision of abstractions over important

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The /annotation directory of the JPetStore sample application contains an analogous example Commons Attributes appears to be the most promising. All these require a special pre- or post-compilation step. 9.2. Spring's metadata support In keeping with its provision of abstractions over important

capabilities and goals Spring AOP is implemented in pure Java. There is no need for a special compilation process. Spring AOP does not need to control the class loader hierarchy, and is thus suitable for attribute information. (The application code must have been compiled using the Commons Attributes compilation task.) The /annotation directory of the JPetStore sample application contains an analogous example Commons Attributes appears to be the most promising. All these require a special pre- or post-compilation step. 8.2. Spring's metadata support In keeping with its provision of abstractions over important