From 219d5087b8f7a85bcfae1380e65cdb226bac0761 Mon Sep 17 00:00:00 2001 From: markpollack Date: Tue, 4 Nov 2008 22:01:34 +0000 Subject: [PATCH] polishing API docs --- doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc | 9 +++- .../Spring-1.2/net-1.1/Spring.Aop.dxc.bak | 7 +++ doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc | 5 +- .../Spring-1.2/net-1.1/Spring.Core.dxc.bak | 21 ++++---- .../net-1.1/Spring.Testing.NUnit.dxc | 4 +- .../net-1.1/Spring.Testing.NUnit.dxc.bak | 1 + doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc | 35 ++++++++----- .../Spring-1.2/net-1.1/Spring.Web.dxc.bak | 42 ++++++++++------ doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp | 40 ++++++++++----- .../Spring-1.2/net-2.0/Spring-1.2.0.dxp.bak | 49 ++++++++++--------- .../net-2.0/Spring.Data.NHibernate20.dxc | 24 ++++++--- .../net-2.0/Spring.Data.NHibernate20.dxc.bak | 10 +++- doc/docx/Spring-1.2/net-2.0/Spring.Data.dxc | 5 +- .../net-2.0/Spring.Messaging.Nms.dxc | 5 +- .../net-2.0/Spring.Messaging.Nms.dxc.bak | 21 +++++++- .../net-2.0/Spring.Scheduling.Quartz.dxc | 4 +- .../net-2.0/Spring.Scheduling.Quartz.dxc.bak | 14 +++++- .../Spring-1.2/net-2.0/Spring.Services.dxc | 38 +++++++++++++- 18 files changed, 245 insertions(+), 89 deletions(-) diff --git a/doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc b/doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc index d271b644..c023f78d 100644 --- a/doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc +++ b/doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc @@ -10,6 +10,12 @@ Aspect-Oriented Programming (AOP) complements OOP by providing another way of thinking about program structure. Whereas OO decomposes applications into a hierarchy of objects, AOP decomposes programs into aspects or concerns.  This enables the modularization of concerns such as transaction management that would otherwise cut across multiple objects (such concerns are often termed crosscutting concerns).

]]> AOP Quickstart included in the distribution is a good starting point to explore the functionality offered in Spring.NET's AOP Framework.]]> +Provides Spring's Aspect Oriented Programming (AOP) functionality.  Spring AOP offers:

+]]> AOP Alliance API.]]> AOP Alliance interception interfaces. Core Spring.NET AOP interfaces, built on top of and implementing all of the AOP Alliance AOP interoperability interfaces.

@@ -36,8 +42,9 @@ This namespace contains implementations of the %Spring.Aop.ITargetSource:Spring.Aop~Spring.Aop.ITargetSource% interface.

The simplest implementation is the %SingletonTargetSource:Spring.Aop~Spring.Aop.Target.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).

]]> -Reusable aspects + Caching asepct Exception handling aspect Logging aspect +Parameter validation aspect diff --git a/doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc.bak b/doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc.bak index b3d019d0..25552479 100644 --- a/doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc.bak +++ b/doc/docx/Spring-1.2/net-1.1/Spring.Aop.dxc.bak @@ -10,6 +10,12 @@ Aspect-Oriented Programming (AOP) complements OOP by providing another way of thinking about program structure. Whereas OO decomposes applications into a hierarchy of objects, AOP decomposes programs into aspects or concerns.  This enables the modularization of concerns such as transaction management that would otherwise cut across multiple objects (such concerns are often termed crosscutting concerns).

]]> AOP Quickstart included in the distribution is a good starting point to explore the functionality offered in Spring.NET's AOP Framework.]]> +Provides Spring's Aspect Oriented Programming (AOP) functionality.  Spring AOP offers:

+
    +
  • Introduction support
    • +
  • A Pointcut abstraction, supporting "static" pointcuts  (class and method-based) and "dynamic" pointcuts (also considering method arguments).
    • +
  • A full range of advice types, including around, before, after returning and throws advice.
    • +
  • Extensibility allowing arbitrary custom advice types to be plugged in without modifying the core framework.

    Spring AOP can be used programmatically or (preferably) integrated with the Spring IoC container.
]]> AOP Alliance API.]]> AOP Alliance interception interfaces. Core Spring.NET AOP interfaces, built on top of and implementing all of the AOP Alliance AOP interoperability interfaces.

@@ -20,6 +26,7 @@
  • A full range of advice types, including around, before, after returning and throws advice.
  • Extensibility points allowing arbitrary custom advice types to be plugged in without modifying the core framework.

    • Spring.NET AOP can be used programmatically or (preferably) in conjunction with the Spring.NET IoC container.

    ]]>     +Custom schema for configuration 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:Spring.Aop~Spring.Aop.Framework.ProxyConfig% AOP configuration interface in this namespace to add or remove interceptors.

    diff --git a/doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc b/doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc index 3d552487..173df848 100644 --- a/doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc +++ b/doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc @@ -16,7 +16,9 @@

    An introductory article to IoC containers can be found in the September 2005 edition of MSDN Magazine.  Links to additional introductory material on IoC containers can be found on the Spring.NET or Spring Framework web sites.

    The design of Spring.NET's IoC container is such that your application objects configured by the IoC container almost always to not need to depend on any classes or interfaces contained in this namespace. 

    However, you may find it useful to reference this namespace as it contains some general framework style classes   These range from %Spring.Expressions:Spring.Core~Spring.Expressions_namespace% that provides evaluation of object graph expressions to %Spring.Util:Spring.Core~Spring.Util_namespace% that provides various Reflection, String, and XML utility functions.

    ]]>     -Inversion of Control (IoC) containers provide a non-invasive means to configure the dependency of objects in your application.  A more detailed introduction to IoC containers can be found is this article by Martin Fowler which uses a simple movie search application as a means to demonstrate the IoC container.  This example implemented using Spring.NET's IoC is available as part of the the Spring.NET distribution and documented as the MovieFinder Quickstart.

    ]]>     +Inversion of Control (IoC) containers provide a non-invasive means to configure the dependency of objects in your application.  A more detailed introduction to IoC containers can be found is this article by Martin Fowler which uses a simple movie search application as a means to demonstrate the IoC container. 

    +

    This example implemented using Spring.NET's IoC is available as part of the the Spring.NET distribution and documented as the MovieFinder Quickstart.

    ]]>     + General caching interfaces and abstract base classes. 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.

    @@ -40,6 +42,7 @@ Interfaces that define a loosely coupled event model. Support classes for the interfaces defined in the Spring.Objects.Events namespace, such as an implementation of the %IEventRegistry:Spring.Core~Spring.Objects.Events.IEventRegistry% interface.             
    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:Spring.Core~Spring.Objects_namespace% namespace.]]>     + Configuration-related convenience classes for object factories. Helper classes used when parsing XML configuration files Classes supporting the classes defined in the Spring.Objects.Factory namespace.

    diff --git a/doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc.bak b/doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc.bak index 314ad7ea..38aca2b1 100644 --- a/doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc.bak +++ b/doc/docx/Spring-1.2/net-1.1/Spring.Core.dxc.bak @@ -1,4 +1,4 @@ - + Globalization|instantiating @@ -8,7 +8,7 @@ on on on - 2072 + 0 The Spring.Core namespace provides an implementation of an Inversion of Control container. 

    @@ -16,8 +16,10 @@

    An introductory article to IoC containers can be found in the September 2005 edition of MSDN Magazine.  Links to additional introductory material on IoC containers can be found on the Spring.NET or Spring Framework web sites.

    The design of Spring.NET's IoC container is such that your application objects configured by the IoC container almost always to not need to depend on any classes or interfaces contained in this namespace. 

    However, you may find it useful to reference this namespace as it contains some general framework style classes   These range from %Spring.Expressions:Spring.Core~Spring.Expressions_namespace% that provides evaluation of object graph expressions to %Spring.Util:Spring.Core~Spring.Util_namespace% that provides various Reflection, String, and XML utility functions.

    ]]>     -Inversion of Control (IoC) containers provide a non-invasive means to configure the dependency of objects in your application.  A more detailed introduction to IoC containers can be found is this article by Martin Fowler which uses a simple movie search application as a means to demonstrate the IoC container.  This example implemented using Spring.NET's IoC is available as part of the the Spring.NET distribution and documented as the MovieFinder Quickstart.

    ]]>     -Custom .NET Attributes provided by the Spring.NET Framework. +Inversion of Control (IoC) containers provide a non-invasive means to configure the dependency of objects in your application.  A more detailed introduction to IoC containers can be found is this article by Martin Fowler which uses a simple movie search application as a means to demonstrate the IoC container. 

    +

    This example implemented using Spring.NET's IoC is available as part of the the Spring.NET distribution and documented as the MovieFinder Quickstart.

    ]]>     + +General caching interfaces and abstract base classes. 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:Spring.Core~Spring.Context.IApplicationContext% or %IObjectFactory:Spring.Core~Spring.Objects.Factory.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.

    ]]>     @@ -26,6 +28,8 @@

    Contains abstract base classes for the %IApplicationContext:Spring.Core~Spring.Context.IApplicationContext% and %IMessageSource:Spring.Core~Spring.Context.IMessageSource% interfaces.

    ]]>     Provides core interfaces that are not specific to any part of the framework. Generic abstraction for resources such as files accessed via HTTP or the local file system. +TypeConversion utilities +TypeResolution utilities Provides data binding of objects to view components. Provides additional functionality such as MAX, MIN to evaluation of object graph expressions @@ -39,22 +43,21 @@ Support classes for the interfaces defined in the Spring.Objects.Events namespace, such as an implementation of the %IEventRegistry:Spring.Core~Spring.Objects.Events.IEventRegistry% interface.             
    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:Spring.Core~Spring.Objects_namespace% namespace.]]>     Configuration-related convenience classes for object factories. +Helper classes used when parsing XML configuration files Classes supporting the classes defined in the Spring.Objects.Factory namespace.

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

    ]]>     Contains an abstract XML-based %IObjectFactory:Spring.Core~Spring.Objects.Factory.IObjectFactory% implementation, including an XML Schema for validation. Classes supporting the classes defined in the %Spring.Objects.Factory:Spring.Core~Spring.Objects.Factory_namespace% namespace.

    Contains a number of abstract base classes for custom %IObjectFactory:Spring.Core~Spring.Objects.Factory.IObjectFactory% implementations.

    ]]>     -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.

    ]]>     Contains object pool interfaces. Contains simple object pool implementation. 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.

    ]]>     +High performance reflection Threading utilities such as LogicalThreadContext (Thread Local Storage) Latch and Semaphore. Miscellaneous utility classes, such as string manipulation utilities. -High performance reflection. Provides validation functionality, for usage in business and / or UI layers. Implementations of %IValidationAction:Spring.Core~Spring.Validation.IValidationAction%. +Custom schema for validation +Validation implementations such as CreditCardValidation, EmailValidator - diff --git a/doc/docx/Spring-1.2/net-1.1/Spring.Testing.NUnit.dxc b/doc/docx/Spring-1.2/net-1.1/Spring.Testing.NUnit.dxc index fa7d32ec..78e9bf94 100644 --- a/doc/docx/Spring-1.2/net-1.1/Spring.Testing.NUnit.dxc +++ b/doc/docx/Spring-1.2/net-1.1/Spring.Testing.NUnit.dxc @@ -8,7 +8,7 @@ 0 - +reference documentation is the best place to get started using Spring and NUnit together.  If you are not familiar with NUnit, check out the NUnit website at www.nunit.org]]>
      @@ -17,5 +17,7 @@

    • Data access using ADO.NET or an ORM tool. This would include such things such as the correctness of SQL statements / or NHibernate XML mapping files.

    The Spring Framework provides first class support for integration testing in the form of the classes that are packaged in the Spring.Testing.NUnit.dll library

    ]]>     +Superclasses for tests requiring Spring application contexts, including support for transactional execution of test cases,
    with automatic rollback on completion. Useful as base classes for application-specific tests.

    +

    The superclasses in this package are ideal for integration testing. Unit testing should not normally involve the Spring container,
    but should test classes in isolation.

    ]]>     Classes for Applicationcontext-ased and transactional tests with NUnit diff --git a/doc/docx/Spring-1.2/net-1.1/Spring.Testing.NUnit.dxc.bak b/doc/docx/Spring-1.2/net-1.1/Spring.Testing.NUnit.dxc.bak index e0516078..fa7d32ec 100644 --- a/doc/docx/Spring-1.2/net-1.1/Spring.Testing.NUnit.dxc.bak +++ b/doc/docx/Spring-1.2/net-1.1/Spring.Testing.NUnit.dxc.bak @@ -17,4 +17,5 @@

  • Data access using ADO.NET or an ORM tool. This would include such things such as the correctness of SQL statements / or NHibernate XML mapping files.

    • The Spring Framework provides first class support for integration testing in the form of the classes that are packaged in the Spring.Testing.NUnit.dll library

    ]]>     +Classes for Applicationcontext-ased and transactional tests with NUnit diff --git a/doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc b/doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc index 50ef91a2..31d16d3b 100644 --- a/doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc +++ b/doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc @@ -5,25 +5,38 @@ on on - 345 + 0 -Spring.Web is an framework that extends the functionality of ASP.NET.  It provides the following features

    -
      -
        -
      • Enables Dependency Injection for ASP.NET web pages and controls
        • -
      • Enables bi-directional data binding
        • -
      • Greatly improves support for data validation
        • -
      • Adds localization support
        • -
      • Implements ‘result mapping’-based page flow
        • -
      • Adds Master Pages support to ASP.NET 1.1
    +Spring.NET's web application framework aims to increase your productivity writing ASP.NET WebForms applications. It offers a unique value proposition to creating ASP.NET applications not found in other .NET web frameworks.

    +

    The goal of the framework is to make it easy to write 'thin and clean' web applications. By thin, what is meant is that the WebForm's responsibility is to act as adapter between the HTML based world of the web and the oo world of your application. The application layer your web form communicates with is where the business logic resides, not in the web tier. By 'clean' what is meant that the web framework should have a good separation of concerns, leading ideally to an event-handler that does not contain any reference to UI elements. This makes it possible to test your event handler code in integration style tests. Last but not least, Spring's web framework reduces the incidental complexity of common tasks in the web tier, for example the conversion of HTML control data to object and then vice-versa after the request has been processed by the application layer.

    +

    Highlights of Spring's Web framework are

    +
    +
      +
    • +

      Dependency Injection for all ASP.NET artifacts. This includes pages and user controls but also modules, providers and HTTP handlers. Your pages, controls, etc., do not have any Spring dependencies in order to be configured via dependency injection.

      • +
    • +

      Bi-directional data binding. This allows you to declaratively define the data that will be marshaled out of your html/user controls and into a data model that in turn is generally submitted to the application layer. After the data model is updated in the application layer, those changes are automatically reflected in the html/user controls on post back. This removes large amounts of tedious, error prone boilerplate code.

      • +
    • +

      Web object scopes. Object definitions can be defined at the application, session or request scope. This makes it easy to inject, say a session scoped shopping cart, into your page without having to do any lower level programming

      • +
    • +

      Data Model Management. While ASP.NET managed the view state of your form, it does not offer facilities to manage the data model that you build up to submit to the application layer. Spring provides a mechanism similar to view state to help manage your data model.

      • +
    • +

      UI agnostic validation framework. Declaratively define complex validation rules, for example that take into account complex relationships in your data model. Error controls are provided to easily render validation failure. This allows you to centralize your validation logic and also reuse it on the server side, for example using parameter validation advice described in the aspect library chapter

      • +
    • +

      Externalized page navigation through 'result mapping'. Instead of hard coding urls and data to direct where a page should go next, result mappings are externally defined and configured that associate logical names and a URL (+ data). This also allows to encryption of values that are sent via Response.Redirect.

      • +
    • +

      Improved localization and master page support - Advanced localization features (including image localization) as well as declarative configuration of what mater page to apply to different parts of your web application are easy to perform.

      +

    +

    All you know about ASP.NET development still applies, Spring's approach is to 'embrace and extend' the basic ASP.NET programming model so you can be as productive as possible.

     

     

    ]]>     - +ASP.NET Web Framework section of the reference documentation and QuickStart applications (SpringAir and Spring.WebQuickStart)  are the best places to get started using the functionality contained in Spring.Web.]]> Caching provider based on ASP.NET cache Contains implementation of IoC Container for the web environment. Abstraction for web resources +Provides infrastructure for supporting Globalization in the web tier. through the UserCulture property on the Page and UserControl classes.  ]]> Support classes for web based IoC container. Support classes for web based IoC container. diff --git a/doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc.bak b/doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc.bak index 0307dd06..a379ff27 100644 --- a/doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc.bak +++ b/doc/docx/Spring-1.2/net-1.1/Spring.Web.dxc.bak @@ -1,4 +1,4 @@ - + depednecy @@ -8,31 +8,43 @@ 0 -Spring.Web is an framework that extends the functionality of ASP.NET.  It provides the following features

    -
      -
        -
      • Enables Dependency Injection for ASP.NET web pages and controls
        • -
      • Enables bi-directional data binding
        • -
      • Greatly improves support for data validation
        • -
      • Adds localization support
        • -
      • Implements ‘result mapping’-based page flow
        • -
      • Adds Master Pages support to ASP.NET 1.1
    +Spring.NET's web application framework aims to increase your productivity writing ASP.NET WebForms applications. It offers a unique value proposition to creating ASP.NET applications not found in other .NET web frameworks.

    +

    The goal of the framework is to make it easy to write 'thin and clean' web applications. By thin, what is meant is that the WebForm's responsibility is to act as adapter between the HTML based world of the web and the oo world of your application. The application layer your web form communicates with is where the business logic resides, not in the web tier. By 'clean' what is meant that the web framework should have a good separation of concerns, leading ideally to an event-handler that does not contain any reference to UI elements. This makes it possible to test your event handler code in integration style tests. Last but not least, Spring's web framework reduces the incidental complexity of common tasks in the web tier, for example the conversion of HTML control data to object and then vice-versa after the request has been processed by the application layer.

    +

    Highlights of Spring's Web framework are

    +
    +
      +
    • +

      Dependency Injection for all ASP.NET artifacts. This includes pages and user controls but also modules, providers and HTTP handlers. Your pages, controls, etc., do not have any Spring dependencies in order to be configured via dependency injection.

      • +
    • +

      Bi-directional data binding. This allows you to declaratively define the data that will be marshaled out of your html/user controls and into a data model that in turn is generally submitted to the application layer. After the data model is updated in the application layer, those changes are automatically reflected in the html/user controls on post back. This removes large amounts of tedious, error prone boilerplate code.

      • +
    • +

      Web object scopes. Object definitions can be defined at the application, session or request scope. This makes it easy to inject, say a session scoped shopping cart, into your page without having to do any lower level programming

      • +
    • +

      Data Model Management. While ASP.NET managed the view state of your form, it does not offer facilities to manage the data model that you build up to submit to the application layer. Spring provides a mechanism similar to view state to help manage your data model.

      • +
    • +

      UI agnostic validation framework. Declaratively define complex validation rules, for example that take into account complex relationships in your data model. Error controls are provided to easily render validation failure. This allows you to centralize your validation logic and also reuse it on the server side, for example using parameter validation advice described in the aspect library chapter

      • +
    • +

      Externalized page navigation through 'result mapping'. Instead of hard coding urls and data to direct where a page should go next, result mappings are externally defined and configured that associate logical names and a URL (+ data). This also allows to encryption of values that are sent via Response.Redirect.

      • +
    • +

      Improved localization and master page support - Advanced localization features (including image localization) as well as declarative configuration of what mater page to apply to different parts of your web application are easy to perform.

      +

    +

    All you know about ASP.NET development still applies, Spring's approach is to 'embrace and extend' the basic ASP.NET programming model so you can be as productive as possible.

     

     

    ]]>     - +ASP.NET Web Framework section of the reference documentation and QuickStart applications (SpringAir and Spring.WebQuickStart)  are the best places to get started using the functionality contained in Spring.Web.]]> +Caching provider based on ASP.NET cache Contains implementation of IoC Container for the web environment. +Abstraction for web resources through the UserCulture property on the Page and UserControl classes.  ]]> Support classes for web based IoC container. Support classes for web based IoC container. -Support classes for dependency injection on Page/UserControl classes. +Support classes for thread local storage Miscellaneous utility classes -Support classes for web based IoC container Support for processing across multiple distinct requests. Exporters to create server and client side web service proxies that support dependency injection and AOP. Support classes for web based IoC container. Master Pages support for .NET 1.1 and Spring Page/UserControl base classes. Various web controls for use with validation and localization features of Spring.Web -Renderers for displaying results of validation. +Renderers for the validaiton framework     - diff --git a/doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp b/doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp index b0f4b5f9..03485918 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp +++ b/doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp @@ -1,6 +1,6 @@  - + @@ -263,39 +263,55 @@ Spring.Data.NHibernate20~Spring.Data.NHibernate.Generic.FindByValueObjectHibernateCallback`1 Spring.Data.NHibernate20~Spring.Data.NHibernate.Generic.ExecuteFindHibernateCallbackUsingDelegate`1 Spring.Data.NHibernate20~Spring.Data.NHibernate.CloseSuppressingMethodInterceptor + Spring.Core~Spring.Core.IO.ResourceHandlerRegistry+TolerantUriParser + Spring.Core~Spring.Objects.Factory.Config.VariablePlaceholderConfigurer+PlaceholderResolvingCompositeVariableSource + Spring.Core~Spring.Objects.Factory.Support.AbstractObjectFactory+ObjectOrderComparator + Spring.Core~Spring.Objects.Factory.Xml.NamespaceParserRegistry+XmlResourceUrlResolver + Spring.Core~Spring.Util.ConfigXmlDocument+CurrentTextPositionHolder + Spring.Core~-PrivateImplementationDetails-{2C2A7DBC-D953-442F-984D-1E79F0F07D7F}+__StaticArrayInitTypeSize=496 + Spring.Core~-PrivateImplementationDetails-{2C2A7DBC-D953-442F-984D-1E79F0F07D7F}+__StaticArrayInitTypeSize=12 + Spring.Core~-PrivateImplementationDetails-{2C2A7DBC-D953-442F-984D-1E79F0F07D7F}+__StaticArrayInitTypeSize=10 + Spring.Web~Spring.Context.Support.WebSupportModule+HandlerConfigurationMetaData + Spring.Web~Spring.Globalization.AspNetResourceCache + Spring.Web~Spring.Web.Support.ControlAccessor + Spring.Web~Spring.Web.Support.ControlCollectionAccessor + Spring.Web~Spring.Web.Support.LocalResourceManager + Spring.Web~Spring.Web.Support.NamingContainerSupportsWebDependencyInjectionOwnerProxy + Spring.Web~Spring.Web.Support.WebFormsResultWebNavigator+NavigableControlInfo + Spring.Messaging~Spring.Messaging.Support.Converters.MessageConverterFactoryObject - - + - + + + - - - - - - - - + + + + + + + diff --git a/doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp.bak b/doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp.bak index fb60badd..ea9019ca 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp.bak +++ b/doc/docx/Spring-1.2/net-2.0/Spring-1.2.0.dxp.bak @@ -1,5 +1,5 @@  - + @@ -120,8 +120,6 @@ Spring.Scheduling.Quartz~Spring.Scheduling.Quartz.SimpleThreadPoolTaskExecutor+ThreadRunnableDelegate Spring.Web~Spring.Caching.AspNetCache+RuntimeCache Spring.Web~Spring.Context.Support.HttpApplicationConfigurer+ModuleDefinitionsTable - Spring.Web~Spring.Util.ControlAccessor - Spring.Web~Spring.Util.ControlCollectionAccessor Spring.Web~Spring.Util.VirtualEnvironment+HttpRuntimeEnvironment+SessionDictionaryAdapter Spring.Web~Spring.Web.Support.AbstractHandlerFactory+NamedObjectDefinition Spring.Web~Spring.Web.Support.ControlInterceptor @@ -152,7 +150,6 @@ Spring.Core~Spring.Expressions.PropertyOrFieldNode+EnumValueAccessor Spring.Core~Spring.Expressions.PropertyOrFieldNode+TypeValueAccessor Spring.Core~Spring.Objects.Factory.Config.PlaceholderResolvingStringVariableSource - Spring.Core~Spring.Objects.Factory.Config.PlaceholderResolvingCompositeVariableSource Spring.Core~Spring.Objects.Factory.Support.UnsatisfiedDependencyExceptionData Spring.Core~Spring.Objects.Factory.Support.ConstructorResolver Spring.Core~Spring.Objects.Factory.Support.ConstructorResolver+AutowiredArgumentMarker @@ -266,39 +263,43 @@ Spring.Data.NHibernate20~Spring.Data.NHibernate.Generic.FindByValueObjectHibernateCallback`1 Spring.Data.NHibernate20~Spring.Data.NHibernate.Generic.ExecuteFindHibernateCallbackUsingDelegate`1 Spring.Data.NHibernate20~Spring.Data.NHibernate.CloseSuppressingMethodInterceptor + Spring.Core~Spring.Core.IO.ResourceHandlerRegistry+TolerantUriParser + Spring.Core~Spring.Objects.Factory.Config.VariablePlaceholderConfigurer+PlaceholderResolvingCompositeVariableSource + Spring.Core~Spring.Objects.Factory.Support.AbstractObjectFactory+ObjectOrderComparator + Spring.Core~Spring.Objects.Factory.Xml.NamespaceParserRegistry+XmlResourceUrlResolver + Spring.Core~Spring.Util.ConfigXmlDocument+CurrentTextPositionHolder + Spring.Core~-PrivateImplementationDetails-{2C2A7DBC-D953-442F-984D-1E79F0F07D7F}+__StaticArrayInitTypeSize=496 + Spring.Core~-PrivateImplementationDetails-{2C2A7DBC-D953-442F-984D-1E79F0F07D7F}+__StaticArrayInitTypeSize=12 + Spring.Core~-PrivateImplementationDetails-{2C2A7DBC-D953-442F-984D-1E79F0F07D7F}+__StaticArrayInitTypeSize=10 + Spring.Web~Spring.Context.Support.WebSupportModule+HandlerConfigurationMetaData + Spring.Web~Spring.Globalization.AspNetResourceCache + Spring.Web~Spring.Web.Support.ControlAccessor + Spring.Web~Spring.Web.Support.ControlCollectionAccessor + Spring.Web~Spring.Web.Support.LocalResourceManager + Spring.Web~Spring.Web.Support.NamingContainerSupportsWebDependencyInjectionOwnerProxy + Spring.Web~Spring.Web.Support.WebFormsResultWebNavigator+NavigableControlInfo + Spring.Messaging~Spring.Messaging.Support.Converters.MessageConverterFactoryObject - - - - - - - - - - - - - + - - - - - - - + + + + + + + diff --git a/doc/docx/Spring-1.2/net-2.0/Spring.Data.NHibernate20.dxc b/doc/docx/Spring-1.2/net-2.0/Spring.Data.NHibernate20.dxc index 4f5a698b..a59b979a 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring.Data.NHibernate20.dxc +++ b/doc/docx/Spring-1.2/net-2.0/Spring.Data.NHibernate20.dxc @@ -1,10 +1,20 @@  - + - This assembly provides integration of NHibernate 1.2 with Spring concepts.

    + + + on + on + 0 + + +This assembly provides integration of NHibernate 2.0 with Spring concepts.

    Contains SessionFactory helper classes, a template plus callback for Hibernate access, and an implementation of Spring's transaction SPI for local Hibernate transactions.

    ]]>     - Contains HibernateTemplate - Generic implementation of HibernateTemplate - Generic implementation of base DAO class - Provides Open Session In View module, base DAO class for HibernateTemplate usage, and SessionScope utilty class -     +NHibernate integration are good places to get started.]]> +The Spring Framework provides integration with NHibernate in terms of resource management, DAO implementation support, and transaction strategies. For example for NHibernate, there is first-class support with lots of IoC convenience features, addressing many typical NHibernate integration issues. All of these support packages for O/R (Object Relational) mappers comply with Spring's generic transaction and DAO exception hierarchies. There are usually two integration styles: either using Spring's DAO 'templates' or coding DAOs against the 'plain' NHibernate APIs. In both cases, DAOs can be configured through Dependency Injection and participate in Spring's resource and transaction management.

    +

    You can use Spring's support for NHibernate without needing to use Spring IoC or transaction management functionality. The NHibernate support classes can be used in typical 3rd party library style. However, usage inside a Spring IoC container does provide additional benefits in terms of ease of configuration and deployment; as such, most examples in this section show configuration inside a Spring containe

    ]]>     +Contains HibernateTemplate +Generic implementation of HibernateTemplate +Generic implementation of base DAO class +Provides Open Session In View module, base DAO class for HibernateTemplate usage, and SessionScope utilty class +     diff --git a/doc/docx/Spring-1.2/net-2.0/Spring.Data.NHibernate20.dxc.bak b/doc/docx/Spring-1.2/net-2.0/Spring.Data.NHibernate20.dxc.bak index 36baaa60..4f5a698b 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring.Data.NHibernate20.dxc.bak +++ b/doc/docx/Spring-1.2/net-2.0/Spring.Data.NHibernate20.dxc.bak @@ -1,2 +1,10 @@  - + + + This assembly provides integration of NHibernate 1.2 with Spring concepts.

    +

    Contains SessionFactory helper classes, a template plus callback for Hibernate access, and an implementation of Spring's transaction SPI for local Hibernate transactions.

    ]]>     + Contains HibernateTemplate + Generic implementation of HibernateTemplate + Generic implementation of base DAO class + Provides Open Session In View module, base DAO class for HibernateTemplate usage, and SessionScope utilty class +     diff --git a/doc/docx/Spring-1.2/net-2.0/Spring.Data.dxc b/doc/docx/Spring-1.2/net-2.0/Spring.Data.dxc index 26228d7a..29eff718 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring.Data.dxc +++ b/doc/docx/Spring-1.2/net-2.0/Spring.Data.dxc @@ -3,9 +3,9 @@ - 704 on on + 1139 The Spring.Data assembly provides an implementation of best practice approaches to data access.

    @@ -42,7 +42,8 @@

    Simple DataReader to Object mapping framework.

     

    For more information refer to the Getting Started section within this documentation and the reference documentation, the latest copy of which can be found on the Spring.NET web site.

    ]]>     -The reference documentation and Spring.DataQuickStart are the best places to get started using the functionality contained in Spring.Data. +Spring.DataQuickStart are the best places to get started using the functionality contained in Spring.Data.]]> +Foundational support for Data Access, providing and ADO.NET Framework, declarative transaction management, and exception translation features. Exception hierarchy enabling sophisticated error handling independent of the data access approach in use.

    For example, when DAOs and data access frameworks use the exceptions in this package (and custom subclasses), calling code can detect and handle common problems such as deadlocks without being tied to a particular data access strategy such as ADO.NET or ORM libraries, as well as vendor specific error codes.

    ]]>     Support classes for DAO implementations, providing miscellaneous utility methods. diff --git a/doc/docx/Spring-1.2/net-2.0/Spring.Messaging.Nms.dxc b/doc/docx/Spring-1.2/net-2.0/Spring.Messaging.Nms.dxc index 40ff7244..623c9db3 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring.Messaging.Nms.dxc +++ b/doc/docx/Spring-1.2/net-2.0/Spring.Messaging.Nms.dxc @@ -3,11 +3,14 @@ - 463 on on + 0 + +Spring.NmsQuickStart as well as the section in the reference docs are good places to get started.]]> + Support namespace for declarative messaging configuration, with XML schema being the primary configuration format. Provides a IPlatformTransactionManager implementation for a single NMS ConnectionFactory, a SingleConnectionFactory and a CachingConnectionFactory. diff --git a/doc/docx/Spring-1.2/net-2.0/Spring.Messaging.Nms.dxc.bak b/doc/docx/Spring-1.2/net-2.0/Spring.Messaging.Nms.dxc.bak index 772ef3e3..f57e7c02 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring.Messaging.Nms.dxc.bak +++ b/doc/docx/Spring-1.2/net-2.0/Spring.Messaging.Nms.dxc.bak @@ -1,2 +1,21 @@  - + + + + + on + on + 0 + + + +Spring.NmsQuickStart as well as the section in the reference docs are good places to get started.]]> +Support namespace for declarative messaging configuration, with XML schema being the primary configuration format. +Provides a IPlatformTransactionManager implementation for a single NMS ConnectionFactory, a SingleConnectionFactory and a CachingConnectionFactory. + + +Message listener adapter mechanism that delegates to target listener methods, converting messages to appropriate message content types (such as String or byte array) that get passed into listener methods. +to be used by higher-level classes like NmsTemplate.]]> +between .NET objects and NMS messages.]]> +Support classes that deal with destination management. + diff --git a/doc/docx/Spring-1.2/net-2.0/Spring.Scheduling.Quartz.dxc b/doc/docx/Spring-1.2/net-2.0/Spring.Scheduling.Quartz.dxc index c3c60ffd..7374f4f1 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring.Scheduling.Quartz.dxc +++ b/doc/docx/Spring-1.2/net-2.0/Spring.Scheduling.Quartz.dxc @@ -3,12 +3,14 @@ - 0 on on + 0 Support for configuring Quartz.NET scheduler objects in a Spring context. +Spring.Scheduling.Quartz.Example, as well as the Quartz section in the reference docs are good places to get started.]]> + Base exceptions diff --git a/doc/docx/Spring-1.2/net-2.0/Spring.Scheduling.Quartz.dxc.bak b/doc/docx/Spring-1.2/net-2.0/Spring.Scheduling.Quartz.dxc.bak index bcf39296..c3c60ffd 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring.Scheduling.Quartz.dxc.bak +++ b/doc/docx/Spring-1.2/net-2.0/Spring.Scheduling.Quartz.dxc.bak @@ -1,2 +1,14 @@  - + + + + + 0 + on + on + + +Support for configuring Quartz.NET scheduler objects in a Spring context. +Base exceptions + + diff --git a/doc/docx/Spring-1.2/net-2.0/Spring.Services.dxc b/doc/docx/Spring-1.2/net-2.0/Spring.Services.dxc index f5c03ba0..9ded4c53 100644 --- a/doc/docx/Spring-1.2/net-2.0/Spring.Services.dxc +++ b/doc/docx/Spring-1.2/net-2.0/Spring.Services.dxc @@ -1,2 +1,38 @@  - + + + + + on + on + 0 + + +here.  The reference docs are also a good place to get started.]]> +The goal of Spring's integration with distributed technologies is to adapt plain .NET objects so they can be used with a specific distributed technology. This integration is designed to be as non-intrusive as possible. If you need to expose an object to a remote process then you can define an exporter for that object. Similarly, on the client side you define an corresponding endpoint accessor. Of course, the object's methods still need to be suitable for remoting, i.e. coarse grained, to avoid making unnecessary and expensive remote calls.

    +

    Since these exporters and client side endpoint accessors are defined using meta data for Spring IoC container, you can easily use dependency injection on them to set initial state and to 'wire up' the presentation tier, such as web forms, to the service layer. In addition, you may apply AOP aspects to the exported classes and/or service endpoints to apply behavior such as logging, security, or other custom behavior that may not be provided by the target distributed technology. The Spring specific terminology for this approach to object distribution is known as Portable Service Abstractions (PSA). As a result of this approach, you can decide much later in the development process the technical details of how you will distribute your objects as compared to traditional code centric approaches. Changing of the implementation is done though configuration of the IoC container and not by recompilation. Of course, you may choose to not use the IoC container to manage these objects and use the exporter and service endpoints programatically.

    +

     

    +

    Supported technologies are:

    +
      +
        +
      • .NET Remoting
        • +
      • EnterpriseServices
        • +
      • .ASMX WebServices
        • +
      • WCF Services
    ]]>     + +
      +
    • .NET Remoting
      • +
    • EnterpriseServices
      • +
    • .ASMX WebServices
      • +
    • WCF Services
    ]]>     +Remoting classes for EnterpriseService/COM+ Services in .NET. Provides a proxy factory for accessing .NET EnterpriseService objects, an exporter for making object available to .NET EnterpriseService clients, and an application exporter to register EnterpriseService applications +Remoting classes for conventional .NET remotoing. Provides a proxy factory for accessing .NET remoted objects and an exporter for making objects available to .NET Remoting clients. +

     

    ]]>     +Configuration support classes for Spring .NET Remoting support, such as custom namespaces +Support classes for the .NET Remoting subsystem, such as the proxy type builder. +Provides a Spring specific System.ServiceModel.ServiceHost +Support for hosting WCF services in a standalone application +Support classes for the WCF subsystem, providing proxy builder, such as the proxy type builder. + +