|
From: Mark P. <mar...@us...> - 2007-12-06 21:38:03
|
Update of /cvsroot/springnet/Spring.Net/doc/reference/src In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv6598 Modified Files: background.xml overview.xml resources.xml Log Message: SPRNET-798 Add overview documentation from web site into reference docs Index: overview.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/overview.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -C2 -d -r1.20 -r1.21 *** overview.xml 6 Dec 2007 07:54:17 -0000 1.20 --- overview.xml 6 Dec 2007 21:37:49 -0000 1.21 *************** *** 6,15 **** <title>Overview</title> ! <para>Spring.NET is an application framework focused on helping build ! enterprise .NET applications. It provides a wide range of functionality ! such as Dependency Injection, Aspect Oriented Programming (AOP), data ! access abstractions, and ASP.NET integration. Based on the Spring ! Framework for Java, the core concepts and values found in Spring.Java have ! been applied to .NET.</para> <para>Enterprise applications typically are composed of a number of a --- 6,26 ---- <title>Overview</title> ! <para>Spring.NET is an application framework that provides comprehensive ! infrastructural support for developing enterprise .NET applications. It ! allows you to remove incidental complexity when using the base class ! libraries makes best practices, such as test driven development, easy ! practices. Spring.NET is created, supported and sustained by <ulink ! url="http://www.springsource.com">SpringSource</ulink>.</para> ! ! <para>The design of Spring.NET is based on the Java version of the Spring ! Framework, which has shown real-world benefits and is used in thousands of ! enterprise applications world wide. Spring .NET is not a quick port from ! the Java version, but rather a 'spiritual port' based on following proven ! architectural and design patterns in that are not tied to a particular ! platform. The breath of functionality in Spring .NET spans application ! tiers which allows you to treat it as a âone stop shopâ but that is not ! required. Spring .NET is not an all-or-nothing solution. You can use the ! functionality in its modules independently. These <link ! linkend="intro-modules">modules</link> are described below.</para> <para>Enterprise applications typically are composed of a number of a *************** *** 46,60 **** yourself in your application.</para> ! <para>The IoC component of the Spring Framework addresses the enterprise ! concern of taking the classes, objects, and services that are to compose ! an application, by providing a formalized means of composing these various ! disparate components into a fully working application ready for use. The ! Spring Framework takes best practices that have been proven over the years ! in numerous applications and formalized as design patterns, and actually ! codifies these patterns as first class objects that you as an architect ! and developer can take away and integrate into your own application(s). ! This is a Very Good Thing Indeed as attested to by the numerous ! organizations and institutions that have used the Spring Framework to ! engineer robust, maintainable applications.</para> </sect1> --- 57,71 ---- yourself in your application.</para> ! <para>The Spring Framework takes best practices that have been proven over ! the years in numerous applications and formalized as design patterns, and ! actually codifies these patterns as first class objects that you as an ! architect and developer can take away and integrate into your own ! application(s). This is a Very Good Thing Indeed as attested to by the ! numerous organizations and institutions that have used the Spring ! Framework to engineer robust, maintainable applications. For example, the ! IoC component of the Spring Framework addresses the enterprise concern of ! taking the classes, objects, and services that are to compose an ! application, by providing a formalized means of composing these various ! disparate components into a fully working application ready for use</para> </sect1> *************** *** 73,90 **** </sect1> ! <sect1> <title>Modules</title> <para>The Spring Framework contains a lot of features, which are ! well-organized into modules shown in the diagram below. The 1.0 release of ! Spring.NET contains a full featured Inversion of Control container and an ! AOP library. The 1.1 releases will contain Web, ORM and Data modules. ! Seperate modules not part of the standard Spring.NET download are dediated ! to integration with other libraries such a NHibernate, TIBCO EMS, Anthem, ! and IIOP.NET. The diagram below shows the various core modules of ! Spring.NET. The dark shaded modules are in the 1.0 release while the other ! modules are planned for future releases. In many cases you can already ! find working implementations for the planned modules available on our ! download site.</para> <para><mediaobject> --- 84,93 ---- </sect1> ! <sect1 id="intro-modules"> <title>Modules</title> <para>The Spring Framework contains a lot of features, which are ! well-organized into modules shown in the diagram below. The diagram below ! shows the various core modules of Spring.NET.</para> <para><mediaobject> *************** *** 94,147 **** </mediaobject></para> ! <para>The <emphasis>Spring.Core</emphasis> library is the most fundamental ! part of the framework, and provides Dependency Injection functionality. ! Most of the libraries in the Spring.NET distribution depend upon and ! extend the functionality provided by this core library. The basic concept ! here is provided by the <classname>IObjectFactory</classname> interface ! that provides a simple yet elegant factory pattern removing the need for ! programmatic singletons and numerous service locator stubs, allowing you ! to decouple the configuration and specification of dependencies from your ! actual program logic. An extension to the ! <classname>IObjectFactory</classname>, the ! <classname>IApplicationContext</classname> is also located here and adds ! more enterprise-centric features such as text localization using resource ! files, event-propagation, and resource-loading.</para> ! <para>The <emphasis>Spring.Aop</emphasis> library provides Aspect Oriented ! Programming (AOP) support to your business objects. The Spring.Aop library ! complements the IoC container in the Spring.Core library to provide a ! rock-solid foundation for building enterprise applications and applying ! services to business objects declaratively.</para> ! <para>The <emphasis>Spring.Web</emphasis> library extends ASP.NET by ! adding a variety of features such as Dependency Injection for ASP.NET ! pages, Bidirectional data binding, Master pages for ASP.NET 1.1 and ! improved localization support.</para> ! <para>The <emphasis>Spring.Services</emphasis> library let you expose any ! "normal" object (meaning an object that does not inherit from a special ! service base class) as an enterprise (COM+) service or remoting object. ! .NET Web services get additional configuration flexibility with support ! for depedency injection and overriding of attribute metadata. Windows ! Service intergration is also provided.</para> ! <para>The <emphasis>Spring.Data</emphasis> library provides a Data Access ! Layer abstraction that can be used across a variety of data access ! providers, from ADO.NET to various ORM providers. It also contains an ! ADO.NET abstraction layer that removes the need for tedious coding and ! declarative transaction management for ADO.NET.</para> ! <para>The <emphasis>Spring.ORM</emphasis> library provides integration ! layers for popular object relational mapping libraries. This provides ! functionality such as support for declarative transaction ! management</para> ! <para>This document provides a reference guide to Spring.NET's features. ! Since this document is still very much a work-in-progress endeavour, if ! you have any requests or comments, please post them on the user forums at ! <ulink ! url="http://forum.springframework.net/">forum.springframework.net</ulink> ! The latest version of this document can be found <ulink ! url="http://www.springframework.net/doc-latest/reference/index.html">here</ulink></para> </sect1> --- 97,184 ---- </mediaobject></para> ! <para>Click on the module name for more information.</para> ! <para><link lang="" linkend="objects">Spring.Core</link> is the most ! fundamental part of the framework allowing you to configure your ! application using Dependency Injection. Other supporting functionality, ! listed below, is located in Spring.Core</para> ! <para><link linkend="aop">Spring.Aop</link> - Use this module to perform ! Aspect-Oriented Programming (AOP). AOP centralizes common functionality ! that can then be declaratively applied across your application in a ! targeted manner. Spring's <link linkend="aop-aspect-library">aspect ! library</link> provides predefined easy to use aspects for transactions, ! logging, performance monitoring, caching, method retry, and exception ! handling.</para> ! <para><link linkend="index-middle-tier">Spring.Data</link> - Use this ! module to achieve greater efficiency and consistency in writing data ! access functionality in ADO.NET and to perform declarative transaction ! management.</para> ! <para><link linkend="orm">Spring.Data.NHibernate</link> - Use this module ! to integrate NHibernate with Springâs declarative transaction management ! functionality allowing easy mixing of ADO.NET and NHibernate operations ! within the same transaction. NHibernate 1.0 users will benefit from ease ! of use APIs to perform data access operations.</para> ! <para><link linkend="web">Spring.Web</link> - Use this module to raise the ! level of abstraction when writing ASP.NET web applications allowing you to ! effectively address common pain-points in ASP.NET such as data binding, ! validation, and ASP.NET page/control/module/provider configuration.</para> ! <para><link linkend="ajax">Spring.Web.Extensions</link> - Use this module ! to raise the level of abstraction when writing ASP.NET web applications ! allowing you to effectively address common pain-points in ASP.NET such as ! data binding, validation, and ASP.NET page/control/module/provider ! configuration.</para> ! ! <para><link linkend="index-services">Spring.Services</link> - Use this ! module to adapt plain .NET objects so they can be used with a specific ! distributed communication technology, such as .NET Remoting, Enterprise ! Services, and ASMX Web Services. These services can be configured via ! dependency injection and âdecoratedâ by applying AOP.</para> ! ! <para><link linkend="testing">Spring.Testing.NUnit</link> - Use this ! module to perform integration testing with NUnit.</para> ! ! <para>The Spring.Core module also includes the following additional ! features</para> ! ! <itemizedlist> ! <listitem> ! <para><link linkend="expressions">Expression Language</link> - ! provides efficient querying and manipulation of an object graphs at ! runtime.</para> ! </listitem> ! ! <listitem> ! <para><link linkend="validation">Validation Framework</link> - a ! robust UI agnostic framework for creating complex validation rules for ! business objects either programmatically or declaratively.</para> ! </listitem> ! ! <listitem> ! <para>Data binding Framework - a UI agnostic framework for performing ! data binding.</para> ! </listitem> ! ! <listitem> ! <para>Dynamic Reflection - provides a high performance reflection ! API</para> ! </listitem> ! ! <listitem> ! <para><link linkend="threading">Threading</link> - provides additional ! concurrency abstractions such as Latch, Semaphore and Thread Local ! Storage.</para> ! </listitem> ! ! <listitem> ! <para><link lang="" linkend="resources">Resource abstraction</link> - ! provides a common interface to treat the InputStream from a file and ! from a URL in a polymorphic and protocol-independent manner.</para> ! </listitem> ! </itemizedlist> </sect1> *************** *** 169,174 **** <title>Support</title> ! <para>Training and Support are available through <ulink ! url="http://www.springsource.com">SpringSource</ulink> in addition to mailing lists and fourms you can find on the main <ulink url="http://www.springframework.net">Spring.NET</ulink> website.</para> --- 206,211 ---- <title>Support</title> ! <para>Training and support are available through <ulink ! url="http://www.springsource.com">SpringSource</ulink> in addition to the mailing lists and fourms you can find on the main <ulink url="http://www.springframework.net">Spring.NET</ulink> website.</para> Index: resources.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/resources.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** resources.xml 8 Aug 2007 17:45:39 -0000 1.5 --- resources.xml 6 Dec 2007 21:37:49 -0000 1.6 *************** *** 1,5 **** <?xml version="1.0" encoding="UTF-8"?> <chapter id="resources"> ! <title>The IResource abstraction</title> <section id="objects-iresource"> --- 1,5 ---- <?xml version="1.0" encoding="UTF-8"?> <chapter id="resources"> ! <title>Resources</title> <section id="objects-iresource"> *************** *** 217,221 **** <literal>UriResource</literal> ! accesses data from the standard System.Uri protocols such as http and https. In .NET 2.0 you can use this also for the ftp protocol. Standard Uri syntax is supported. </listitem> </itemizedlist> Refer to the MSDN documentation for more information on --- 217,221 ---- <literal>UriResource</literal> ! accesses data from the standard System.Uri protocols such as http and https. In .NET 2.0 you can use this also for the ftp protocol. Standard Uri syntax is supported. </listitem> </itemizedlist> Refer to the MSDN documentation for more information on Index: background.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/background.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** background.xml 2 Aug 2005 11:15:54 -0000 1.6 --- background.xml 6 Dec 2007 21:37:48 -0000 1.7 *************** *** 1,18 **** <chapter id="background"> ! <title>Background information</title> ! <sect1 id="background-ioc"> ! <title>Inversion of Control</title> ! <para> ! In early 2004, Martin Fowler asked the readers of his site: when talking ! about Inversion of Control: <emphasis>"the question, is what aspect of ! control are they inverting?"</emphasis>. After talking about the term ! Inversion of Control Martin suggests renaming the pattern, or at least ! giving it a more self-explanatory name, and starts to use the term ! <emphasis>Dependency Injection</emphasis>. His ! <ulink url="http://martinfowler.com/articles/injection.html">article</ulink> continues to ! explain some of the ideas behind this important software engineering principle. ! </para> ! </sect1> ! </chapter> --- 1,34 ---- + <?xml version="1.0" encoding="UTF-8"?> <chapter id="background"> ! <title>Background information</title> ! ! <sect1 id="background-ioc"> ! <title>Inversion of Control</title> ! ! <para>In early 2004, Martin Fowler asked the readers of his site: when ! talking about Inversion of Control: <emphasis>"the question, is what ! aspect of control are they inverting?"</emphasis>. After talking about the ! term Inversion of Control Martin suggests renaming the pattern, or at ! least giving it a more self-explanatory name, and starts to use the term ! <emphasis>Dependency Injection</emphasis>. His <ulink ! url="http://martinfowler.com/articles/injection.html">article</ulink> ! continues to explain some of the ideas behind this important software ! engineering principle.</para> + <para>Other references you may find useful are</para> + <itemizedlist> + <listitem> + <para>Wikipedia Article - <ulink + url="http://en.wikipedia.org/wiki/Dependency_injection">Dependency + Injection</ulink></para> + </listitem> + + <listitem> + <para>CodeProject article - <ulink + url="http://www.codeproject.com/cs/design/DependencyInjection.asp">Dependency + Injection for Loose Coupling</ulink></para> + </listitem> + </itemizedlist> + </sect1> + </chapter> \ No newline at end of file |
