| Namespace | Description |
|---|---|
| AopAlliance.Aop | AOP framework interfaces based on the AOP Alliance API. |
| AopAlliance.Intercept | AOP Alliance interception interfaces. |
| Spring.Aop | Core Spring.NET AOP interfaces, built on top of and implementing all of the AOP Alliance AOP interoperability interfaces.
Spring.NET AOP also offers:
Spring.NET AOP can be used programmatically or (preferably) in conjunction with the Spring.NET IoC container. |
| Spring.Aop.Advice | Implementations of common types of Advice (Aspects). |
| Spring.Aop.Framework | Basic AOP infrastructure compliant with the AOP Alliance interfaces.
Spring.NET AOP supports proxying interfaces or classes, introductions, and offers static and dynamic pointcuts. Any Spring.NET AOP proxy can be cast to the ProxyConfig AOP configuration interface in this namespace to add or remove interceptors. The ProxyFactoryObject is a convenient way to create AOP proxies in an IObjectFactory or IApplicationContext. However, proxies can be created programmatically using the ProxyFactory class. |
| Spring.Aop.Framework.Adapter | Service Provider Interface (SPI) namespace allowing Spring.NET AOP framework to handle arbitrary advice types. Users who want to use the Spring.NET AOP framework, rather than extend its capabilities, don't need to concern themselves with this namespace. |
| Spring.Aop.Framework.AutoProxy | Object post-processors for use in IApplicationContexts to simplify AOP usage by automatically creating AOP proxies without the need to use a ProxyFactoryObject.
The various post-processors in this package need only be added to an IApplicationContext (typically in an XML object definition document) to automatically proxy selected objects. |
| Spring.Aop.Framework.AutoProxy.Target | Generic support classes for target source creation. |
| Spring.Aop.Framework.DynamicProxy | Contains functionality relating to the creation of dynamic proxy instances. |
| Spring.Aop.Support | Convenience classes for using Spring.NET's AOP API. |
| Spring.Aop.Target | This namespace contains implementations of the Spring.Aop.ITargetSource interface. The simplest implementation is the SingletonTargetSource, which is used in the AOP framework to wrap a single target instance. This is normally appropriate, and is the current default. Other features include pooling implementations, that provides a target from a pool for each request, ensuring a single threaded programming model; and a "prototype" implementation, that uses a new target instance for each invocation. (Much like single-call .NET remoting semanics). |
© 2004-2006 Spring.NET Authors. All Rights Reserved.