Spring.Core Send comments on this topic.

Assembly Overview

Namespaces

NamespaceDescription
Spring.Attributes Custom .NET Attributes provided by the Spring.NET Framework.
Spring.Collections Collection style classes used throughout the Spring.NET framework.  Most notably an implementation of a Set collection class.
Spring.Context Builds on the feature set provided by the Spring.Objects namespace to add support for message sources and for the Observer design pattern, and the ability for application objects to obtain resources.

There is no necessity for Spring.NET applications explicitly to depend on the functionality provided by either of the IApplicationContext or IObjectFactory interfaces. One of the strengths of the Spring.NET architecture is that application objects can almost always be configured without any dependency on Spring.NET-specific APIs.

Spring.Context.Events Support classes for application events, such as standard context events.
Spring.Context.Support Support classes for the functionality defined in the Spring.Context namespace.

Contains abstract base classes for the IApplicationContext and IMessageSource interfaces.

Spring.Core Provides core interfaces that are not specific to any part of the framework.
Spring.Core.IO Generic abstraction for resources such as files accessed via HTTP or the local file system.
Spring.DataBinding Provides data binding of objects to view components.
Spring.Expressions Provides evaluation of object graph expressions.
Spring.Globalization Defines the core interfaces and support classes for internationalization support.
Spring.Globalization.Formatters  
Spring.Globalization.Localizers Defines implementations of the ILocalizer interface that apply resources to target objects as well as any supporting classes.
Spring.Globalization.Resolvers Defines implementations of the ICultureResolver strategy interface for resolving CultureInfo instances as well as any supporting classes.
Spring.Objects Contains interfaces and classes for manipulating plain old .NET objects (PONOs).

The classes and interfaces declared in this namespace are central to Spring.NET's Inversion of Control (IoC) container implementation.

Spring.Objects.Events Interfaces that define a loosely coupled event model.
Spring.Objects.Events.Support Support classes for the interfaces defined in the Spring.Objects.Events namespace, such as an implementation of the IEventRegistry interface.
Spring.Objects.Factory The core namespace implementing Spring.NET's lightweight Inversion of Control (IoC) container.
            
Provides an alternative to the Singleton and Prototype design patterns, including a consistent approach to configuration management. Builds on top of the classes defined in the Spring.Objects namespace.
Spring.Objects.Factory.Config Configuration-related convenience classes for object factories.
Spring.Objects.Factory.Support Classes supporting the classes defined in the Spring.Objects.Factory namespace.
            <p />
            Contains a number of abstract base classes for custom IObjectFactory implementations.
Spring.Objects.Factory.Xml Contains an abstract XML-based IObjectFactory implementation, including an XML Schema for validation.
Spring.Objects.Support Classes supporting the classes defined in the Spring.Objects.Factory namespace.

Contains a number of abstract base classes for custom IObjectFactory implementations.

Spring.Objects.TypeConverters TypeConverters are used to convert between string and objects and vice versa.

Some of the custom type converter implementation classes in this namespace are registered automatically by an appropriate IObjectWrapper implementation class.


Please consult either the reference documentation or the embedded (API) documentation (for the appropriate IObjectWrapper implementation class) for the specifics of which TypeConverters are pre-registered.

Spring.Pool Contains object pool interfaces.
Spring.Pool.Support Contains simple object pool implementation.
Spring.Proxy Provides classes that can create proxy types via composition or inheritance, and apply any number of custom attributes to the class definition and / or members of the proxied type.

This is useful in those cases where attributes may need to be applied to a class definition to take advantage of behavior that relies on the presence of such attributes. Examples of behavior that can be controlled via the use of attributes include COM+ ServicedComponents and web services.

Spring.Util Miscellaneous utility classes, such as string manipulation utilities.
Spring.Validation Provides validation functionality, for usage in business and / or UI layers.
Spring.Validation.Actions Implementations of IValidationAction.

 

 


© 2004-2006 Spring.NET Authors. All Rights Reserved.