|
From: Mark P. <mar...@us...> - 2007-11-27 21:01:51
|
Update of /cvsroot/springnet/Spring.Net/doc/reference/src In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv3268 Modified Files: ado.xml aop.xml objects.xml transaction.xml Log Message: misc doc cleanup - most importantly some reworking of the intro section to chapter 2. Index: transaction.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/transaction.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -C2 -d -r1.20 -r1.21 *** transaction.xml 3 Oct 2007 14:38:35 -0000 1.20 --- transaction.xml 27 Nov 2007 21:01:42 -0000 1.21 *************** *** 232,245 **** ServiceDomainPlatformTransactionManager uses the 'Services without Components' update so that your objects do not need to inherit from ! ServicedComponent and as such calls ServiceDomain.Enter(), Leave; ! ContextUtil.SetAbort(). Note you can use Spring's EnterpriseServices ! exporter to have a EnterpriseService proxy created for your plain .NET ! object. TxScopePlatformTransactionManager calls new TransactionScope(); .Complete(), Dispose(), Transaction.Current.Rollback(). Configuration properties for each transaction manager are specific to the data access technology used. Refer to the API docs for comprehensive information but the examples should give you a good basis for getting started. The ! HibernatePlatformTransactionManager is described more in the section ! <classname></classname>.</para> <para>The <literal>GetTransaction(..)</literal> method returns a --- 232,244 ---- ServiceDomainPlatformTransactionManager uses the 'Services without Components' update so that your objects do not need to inherit from ! ServicedComponent or directly call the EnterpriseServices API ! ServiceDomain.Enter(), Leave; ContextUtil.SetAbort(). ! TxScopePlatformTransactionManager calls; new TransactionScope(); .Complete(), Dispose(), Transaction.Current.Rollback(). Configuration properties for each transaction manager are specific to the data access technology used. Refer to the API docs for comprehensive information but the examples should give you a good basis for getting started. The ! HibernatePlatformTransactionManager is described more in the following ! <link lang="" linkend="orm-tx-mgmt">section</link> .</para> <para>The <literal>GetTransaction(..)</literal> method returns a Index: ado.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/ado.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -C2 -d -r1.19 -r1.20 *** ado.xml 30 Oct 2007 16:38:03 -0000 1.19 --- ado.xml 27 Nov 2007 21:01:42 -0000 1.20 *************** *** 1213,1218 **** lightweight object mapping framework.</para> ! <sect2> ! <title id="ado-resultsetextractor">ResultSetExtractor</title> <para>The ResultSetExtractor gives you control to iterate over the --- 1213,1218 ---- lightweight object mapping framework.</para> ! <sect2 id="ado-resultsetextractor"> ! <title>ResultSetExtractor</title> <para>The ResultSetExtractor gives you control to iterate over the *************** *** 1291,1296 **** </sect2> ! <sect2> ! <title id="ado-rowcallback">RowCallback</title> <para>The RowCallback is usually a statefull object itself or populates --- 1291,1296 ---- </sect2> ! <sect2 id="ado-rowcallback"> ! <title>RowCallback</title> <para>The RowCallback is usually a statefull object itself or populates *************** *** 1346,1351 **** </sect2> ! <sect2> ! <title id="ado-rowmapper">RowMapper</title> <para>The RowMapper lets you focus on just the logic to map a row of --- 1346,1351 ---- </sect2> ! <sect2 id="ado-rowmapper"> ! <title>RowMapper</title> <para>The RowMapper lets you focus on just the logic to map a row of Index: objects.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/objects.xml,v retrieving revision 1.108 retrieving revision 1.109 diff -C2 -d -r1.108 -r1.109 *** objects.xml 11 Oct 2007 13:01:43 -0000 1.108 --- objects.xml 27 Nov 2007 21:01:42 -0000 1.109 *************** *** 1,43 **** <?xml version="1.0" encoding="UTF-8"?> <chapter id="objects"> ! <title>abstractObjectObjects, Object Factories, and Application ! Contexts</title> <sect1 id="objects-introduction"> <title>Introduction</title> <para>The <literal>Spring.Core</literal> assembly provides the basis for ! the Spring.NET Inversion of Control (IoC - sometimes also referred to as ! Dependency Injection) features (see <xref linkend="background-ioc" /> for ! some additional material describing this software engineering principle). ! The <classname><ulink url="http://www.springframework.net/doc/api/html/Spring.Objects.Factory.IObjectFactory.html">IObjectFactory</ulink></classname> ! interface from the <literal>Spring.Core</literal> assembly provides an ! advanced configuration mechanism capable of managing objects of any ! nature, using potentially any kind of storage facility. The ! <classname><ulink url="http://www.springframework.net/doc/api/html/Spring.Context.IApplicationContext.html">IApplicationContext</ulink></classname> ! interface from the same assembly builds on top of the functionality ! provided by the <classname>IObjectFactory</classname> interface, ! complementing it with features such as integration with Spring.NET's ! Aspect Oriented Programming (AOP) features and message resource handling ! (for use in internationalization).</para> <para>In short, the <classname>IObjectFactory</classname> provides the configuration framework and basic functionality, while the <classname>IApplicationContext</classname> adds more enterprise-centric ! functionality to it. In general, the ! <classname>IApplicationContext</classname> is a complete superset of the ! <classname>IObjectFactory</classname>, and any description of ! <classname>IObjectFactory</classname> capabilities and behavior should be ! considered to apply to <literal>IApplicationContext</literal>s as ! well.</para> ! <para>This chapter is divided into two parts, with the first part covering ! the basic principles that apply to both the ! <classname>IObjectFactory</classname> and ! <classname>IApplicationContext</classname>, with the second part covering ! those features that apply only to the ! <classname>IApplicationContext</classname> interface.</para> <para>If you are new to Spring.NET or IoC containers in general, you may --- 1,45 ---- <?xml version="1.0" encoding="UTF-8"?> <chapter id="objects"> ! <title>The IoC container</title> <sect1 id="objects-introduction"> <title>Introduction</title> + <para>This chapter covers the Spring Framework's implementation of the + Inversion of Control (IoC) <footnote> + <para>See the section entitled <xref + linkend="background-ioc" /></para> + </footnote> principle</para> + <para>The <literal>Spring.Core</literal> assembly provides the basis for ! the Spring.NET Inversion of Control container. The <classname><ulink url="http://www.springframework.net/doc/api/html/Spring.Objects.Factory.IObjectFactory.html">IObjectFactory</ulink></classname> ! interface provides an advanced configuration mechanism capable of managing ! objects of any nature. The <classname><ulink url="http://www.springframework.net/doc/api/html/Spring.Context.IApplicationContext.html">IApplicationContext</ulink></classname> ! interface builds on top of the <classname>IObjectFactory</classname> (it ! is a sub-interface) and adds other functionality such as easier ! integration with Spring.NET's Aspect Oriented Programming (AOP) features, ! message resource handling (for use in internationalization), event ! propagation and appliation layer-specific context such as ! <classname>WebApplicationContext</classname> for use in web ! applications.</para> <para>In short, the <classname>IObjectFactory</classname> provides the configuration framework and basic functionality, while the <classname>IApplicationContext</classname> adds more enterprise-centric ! functionality to it. The <classname>IApplicationContext</classname> is a ! complete superset of the <classname>IObjectFactory</classname>, and any ! description of <classname>IObjectFactory</classname> capabilities and ! behavior should be considered to apply to ! <literal>IApplicationContext</literal>s as well.</para> ! <para>This chapter is divided into two parts, with the <link ! linkend="objects-basics">first part</link> covering the basic principles ! that apply to both the <classname>IObjectFactory</classname> and ! <classname>IApplicationContext</classname>, with the <link ! linkend="context-introduction">second part</link> covering those features ! that apply only to the <classname>IApplicationContext</classname> ! interface.</para> <para>If you are new to Spring.NET or IoC containers in general, you may *************** *** 52,63 **** <sect1 id="objects-basics"> ! <title>Introduction to the IObjectFactory, IApplicationContext, and ! IObjectDefinition</title> <sect2 id="objects-factory"> ! <title>The IObjectFactory and IApplicationContext</title> ! <para>The <classname>IObjectFactory</classname> is the actual container ! that instantiates, configures, and manages a number of objects. These objects typically collaborate with one another, and thus can be said to have dependencies between themselves. These dependencies are reflected --- 54,65 ---- <sect1 id="objects-basics"> ! <title>Basics - containers and objects</title> <sect2 id="objects-factory"> ! <title>The container</title> ! <para>The <classname>IObjectFactory</classname> is the actual ! representation of the Spring IoC container that is responsible for ! instantiating, configuring, and managing a number of objects. These objects typically collaborate with one another, and thus can be said to have dependencies between themselves. These dependencies are reflected *************** *** 3779,3784 **** <note> ! In an ASP.NET environment you must specify the full, four-part name ! of the assembly when using a <classname>NameValueFileSectionHandler</classname> <programlisting> <section name="hibernateConfiguration" --- 3781,3790 ---- <note> ! In an ASP.NET environment you must specify the full, four-part name of the assembly when using a ! ! <classname>NameValueFileSectionHandler</classname> ! ! ! <programlisting> <section name="hibernateConfiguration" *************** *** 3786,3791 **** Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/> </programlisting> </note> ! <sect4> <title>Type, Ref, and Expression substitution</title> --- 3792,3799 ---- Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/> </programlisting> + + </note> ! <sect4> <title>Type, Ref, and Expression substitution</title> *************** *** 3913,3983 **** <title>IVariableSource</title> ! <para> ! The IVariableSource is the base interface for providing the ! ability to get the value of property placeholders (name-value) pairs ! from a variety of sources. Out of the box, Spring.NET supports a ! number of variable sources that allow users to obtain variable values ! from .NET config files, java-style property files, environment ! variables, command line arguments and the registry and the new ! connection strings configuraiton section in .NET 2.0. The list of ! implementing classes is listed below. Please refer to the SDK ! documentation for more information. ! </para> <itemizedlist> <listitem> ! <para> ! <classname>ConfigSectionVariableSource</classname> ! </para> </listitem> <listitem> ! <para> ! <classname>PropertyFileVariableSource</classname> ! </para> </listitem> <listitem> ! <para> ! <classname>EnvironmentVariableSource</classname> ! </para> </listitem> <listitem> ! <para> ! <classname>CommandLineArgsVariableSource</classname> ! </para> </listitem> <listitem> ! <para> ! <classname>RegistryVariableSource</classname> ! </para> </listitem> <listitem> ! <para> ! <classname>SpecialFolderVariableSource</classname> ! </para> </listitem> <listitem> ! <para> ! <classname>ConnectionStringsVariableSource</classname> ! </para> </listitem> </itemizedlist> ! <para> ! You use this by defining an instance of ! <classname>Spring.Objects.Factory.Config.VariablePlaceholderConfigurer</classname> ! in your configuraiton and set the property ! <literal>VariableSource</literal> to a single ! <classname>IVariableSource</classname> instance or the list property ! <literal>VariableSources</literal> to a list of <classname>IVariableSource</classname> ! instances. In the case of the same property defined in multiple ! <classname>IVariableSource</classname> implementations, the first one ! in the list that contains the property value will be used. ! <programlisting><object type="Spring.Objects.Factory.Config.VariablePlaceholderConfigurer, Spring.Core"> <property name="VariableSources"> <list> --- 3921,3975 ---- <title>IVariableSource</title> ! <para>The IVariableSource is the base interface for providing the ! ability to get the value of property placeholders (name-value) pairs ! from a variety of sources. Out of the box, Spring.NET supports a ! number of variable sources that allow users to obtain variable values ! from .NET config files, java-style property files, environment ! variables, command line arguments and the registry and the new ! connection strings configuraiton section in .NET 2.0. The list of ! implementing classes is listed below. Please refer to the SDK ! documentation for more information.</para> <itemizedlist> <listitem> ! <para><classname>ConfigSectionVariableSource</classname></para> </listitem> <listitem> ! <para><classname>PropertyFileVariableSource</classname></para> </listitem> <listitem> ! <para><classname>EnvironmentVariableSource</classname></para> </listitem> <listitem> ! <para><classname>CommandLineArgsVariableSource</classname></para> </listitem> <listitem> ! <para><classname>RegistryVariableSource</classname></para> </listitem> <listitem> ! <para><classname>SpecialFolderVariableSource</classname></para> </listitem> <listitem> ! <para><classname>ConnectionStringsVariableSource</classname></para> </listitem> </itemizedlist> ! <para>You use this by defining an instance of ! <classname>Spring.Objects.Factory.Config.VariablePlaceholderConfigurer</classname> ! in your configuraiton and set the property ! <literal>VariableSource</literal> to a single ! <classname>IVariableSource</classname> instance or the list property ! <literal>VariableSources</literal> to a list of ! <classname>IVariableSource</classname> instances. In the case of the ! same property defined in multiple ! <classname>IVariableSource</classname> implementations, the first one ! in the list that contains the property value will be used. ! <programlisting><object type="Spring.Objects.Factory.Config.VariablePlaceholderConfigurer, Spring.Core"> <property name="VariableSources"> <list> *************** *** 3988,3993 **** </property> </object> ! </programlisting> ! </para> </sect3> </sect2> --- 3980,3984 ---- </property> </object> ! </programlisting></para> </sect3> </sect2> *************** *** 4045,4050 **** <sect1 id="context-introduction"> ! <title>Introduction to the ! <classname>IApplicationContext</classname></title> <para>While the <literal>Spring.Objects</literal> namespace provides basic --- 4036,4040 ---- <sect1 id="context-introduction"> ! <title>The <classname>IApplicationContext</classname></title> <para>While the <literal>Spring.Objects</literal> namespace provides basic Index: aop.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/aop.xml,v retrieving revision 1.45 retrieving revision 1.46 diff -C2 -d -r1.45 -r1.46 *** aop.xml 2 Oct 2007 04:43:12 -0000 1.45 --- aop.xml 27 Nov 2007 21:01:42 -0000 1.46 *************** *** 2091,2097 **** <title>Using AOP Namespace</title> ! <para>The AOP namespace is under development, however as of Spring.NET 1.1 ! M1 you can define a simple advisor, i.e pointcut + 1 piece of advice, in a ! more declarative manner. Under the covers the DefaultAdvisorAutoProxyCreator is being used. Here is an example,</para> --- 2091,2096 ---- <title>Using AOP Namespace</title> ! <para>The AOP namespace allows you to define an advisor, i.e pointcut + 1 ! piece of advice, in a more declarative manner. Under the covers the DefaultAdvisorAutoProxyCreator is being used. Here is an example,</para> |
