Update of /cvsroot/springnet/Spring.Net/doc/reference/src In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv31288 Modified Files: ado.xml ajax.xml aop-aspect-library.xml aop-quickstart.xml aop.xml dao.xml data-quickstart.xml dbprovider.xml expressions.xml index.xml javadevelopers.xml logging.xml migration.xml navigation.xml objects-misc.xml objects.xml orm.xml overview.xml pool.xml psa-intro.xml quickstarts.xml remoting-quickstart.xml remoting.xml resources.xml services.xml springair.xml testing.xml threading.xml transaction.xml tx-quickstart.xml validation.xml vsnet.xml web.xml webservices.xml xml-config-reference.xml Log Message: Thank you Ruben for your edits! Index: webservices.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/webservices.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -C2 -d -r1.16 -r1.17 *** webservices.xml 20 Dec 2007 23:28:28 -0000 1.16 --- webservices.xml 16 Jan 2008 17:21:44 -0000 1.17 *************** *** 84,88 **** <classname>WebMethod</classname> attribute and (at the class-level) the <classname>WebService</classname> attribute. Application developers can ! create this web service within Visual Studio.NET just like any other class.</para> --- 84,88 ---- <classname>WebMethod</classname> attribute and (at the class-level) the <classname>WebService</classname> attribute. Application developers can ! create this web service within Visual Studio just like any other class.</para> *************** *** 130,137 **** service object internally for each request, all Spring.NET needs to provide is the <classname>System.Type</classname> of the service class, ! which can be retrieved from the object definition even if it is amrked as <literal>abstract</literal>.</para> ! <para>That's pretty much it as can access this web service using the value specified for the <literal>name</literal> attribute of the object definition as the service name:</para> --- 130,137 ---- service object internally for each request, all Spring.NET needs to provide is the <classname>System.Type</classname> of the service class, ! which can be retrieved from the object definition even if it is marked as <literal>abstract</literal>.</para> ! <para>That's pretty much it as we can access this web service using the value specified for the <literal>name</literal> attribute of the object definition as the service name:</para> *************** *** 184,189 **** </programlisting> ! <para>The problem with standard SpringNET DI usage in this case is that ! Spring.NEt does not control the instantiation of the web service. This happens deep in the internals of the .NET framework, thus making it quite difficult to plug in the code that will perform the --- 184,189 ---- </programlisting> ! <para>The problem with standard Spring.NET DI usage in this case is that ! Spring.NET does not control the instantiation of the web service. This happens deep in the internals of the .NET framework, thus making it quite difficult to plug in the code that will perform the *************** *** 251,255 **** exported interfaces.</para> ! <para>However, that is still not the ideal solution. You would looe information that the optional <classname>WebService</classname> and <classname>WebMethod</classname> attributes provide, such as service --- 251,255 ---- exported interfaces.</para> ! <para>However, that is still not the ideal solution. You would lose information that the optional <classname>WebService</classname> and <classname>WebMethod</classname> attributes provide, such as service *************** *** 260,264 **** <para>A second, better way, is to set all the necessary values within ! the definoitn of the service exporter, like so...</para> <programlisting> --- 260,264 ---- <para>A second, better way, is to set all the necessary values within ! the definition of the service exporter, like so...</para> <programlisting> *************** *** 310,314 **** Distributed computing principles still apply and you need to make sure that your services are not chatty and that arguments and return values ! are serializable.</para> <para>You still need to exercise common sense when deciding whether to --- 310,314 ---- Distributed computing principles still apply and you need to make sure that your services are not chatty and that arguments and return values ! are Serializable.</para> <para>You still need to exercise common sense when deciding whether to *************** *** 381,386 **** service implementation or a local service instead of a web service.</para> ! <para>The goal for Spring.NET's web sevices support is to enable the easy ! generation of the client-side proxies that implement a specific service interface.</para> --- 381,386 ---- service implementation or a local service instead of a web service.</para> ! <para>The goal for Spring.NET's web services support is to enable the easy ! generation of client-side proxies that implement a specific service interface.</para> *************** *** 442,454 **** <classname>WebServiceExporter</classname>, which requires an interface in order to work.</para> - </sect2> <sect2> ! <title>Generating proxy dynamically</title> <para>The <classname>WebServiceProxyFactory</classname> can also dynamically generate a web-service proxy. The XML object definition for ! this factoroy object is shown below</para> <programlisting> --- 442,453 ---- <classname>WebServiceExporter</classname>, which requires an interface in order to work.</para> </sect2> <sect2> ! <title>Generating proxies dynamically</title> <para>The <classname>WebServiceProxyFactory</classname> can also dynamically generate a web-service proxy. The XML object definition for ! this factory object is shown below</para> <programlisting> *************** *** 470,479 **** typed data sets through a web service. Leaving the pros and cons of this approach aside, the current behavior of the proxy generator in .NET is ! to create wrapper types for the typed dataset. This not only polutes the ! solution with extraneous classes but also results in multiple wrapper ! types being created, one for each web service that uses the typed ! dataset. This can quickly get confusing. The proxy created by Spring ! allows you to reference you typed datasets directly, avoiding the above ! mentioned issues.</para> </sect2> --- 469,478 ---- typed data sets through a web service. Leaving the pros and cons of this approach aside, the current behavior of the proxy generator in .NET is ! to create wrapper types for the typed dataset. This not only pollutes ! the solution with extraneous classes but also results in multiple ! wrapper types being created, one for each web service that uses the ! typed dataset. This can quickly get confusing. The proxy created by ! Spring allows you to reference you typed datasets directly, avoiding the ! above mentioned issues.</para> </sect2> *************** *** 481,493 **** <title>Configuring the proxy instance</title> ! <para> ! The <classname>WebServiceProxyFactory</classname> also implements ! the interface, ! <classname>Spring.Objects.Factory.IConfigurableFactoryObject</classname>, ! allowing to specify configuration for the product that the ! <classname>WebServiceProxyFactory</classname> creates. This is done by ! specifying the ProductTemplate property. This is particularly useful for ! securing the web service. An example is shown below. ! </para> <programlisting> --- 480,490 ---- <title>Configuring the proxy instance</title> ! <para>The <classname>WebServiceProxyFactory</classname> also implements ! the interface, ! <classname>Spring.Objects.Factory.IConfigurableFactoryObject</classname>, ! allowing to specify configuration for the product that the ! <classname>WebServiceProxyFactory</classname> creates. This is done by ! specifying the ProductTemplate property. This is particularly useful for ! securing the web service. An example is shown below.</para> <programlisting> *************** *** 506,510 **** </object> </property> ! <emphasis role="bold"><!-- Configure client certficiate for the web service --> </emphasis> <property name="ClientCertificates"> <list> --- 503,507 ---- </object> </property> ! <emphasis role="bold"><!-- Configure client certificate for the web service --> </emphasis> <property name="ClientCertificates"> <list> Index: objects-misc.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/objects-misc.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** objects-misc.xml 4 Dec 2006 08:09:07 -0000 1.3 --- objects-misc.xml 16 Jan 2008 17:21:44 -0000 1.4 *************** *** 5,11 **** <sect1 id="objects-misc-introduction"> <title>Introduction</title> - - <para><emphasis>(Available in 1.0)</emphasis></para> - <para>The concepts encapsulated by the <classname>IObjectWrapper</classname> interface are fundamental to the --- 5,8 ---- *************** *** 60,64 **** <para>The aforementioned <methodname>SetPropertyValue()</methodname> and ! <methodname>GetPropertyValue()</methodname> methods do have a number of conventions for indicating the path of a property. A property path is an expression that implementations of the --- 57,61 ---- <para>The aforementioned <methodname>SetPropertyValue()</methodname> and ! <methodname>GetPropertyValue()</methodname> methods have a number of conventions for indicating the path of a property. A property path is an expression that implementations of the *************** *** 370,374 **** <entry>Capable of resolving a string representation of a URI to ! an actual <literal>URI</literal>-object.</entry> </row> --- 367,371 ---- <entry>Capable of resolving a string representation of a URI to ! an actual <literal>Uri</literal>-object.</entry> </row> *************** *** 405,409 **** <row> ! <entry><literal>RGBColorConverter</literal></entry> <entry>Capable of resolving a comma separated list of Red, --- 402,406 ---- <row> ! <entry><literal>RgbColorConverter</literal></entry> <entry>Capable of resolving a comma separated list of Red, *************** *** 416,420 **** <entry>Converts string representation of regular expression into ! an instance of System.Text.RegularExpressions RegEx</entry> </row> </tbody> --- 413,417 ---- <entry>Converts string representation of regular expression into ! an instance of System.Text.RegularExpressions.Regex</entry> </row> </tbody> *************** *** 426,429 **** --- 423,438 ---- checking any configuration files associated with your application, checking the Global Assembly Cache (GAC), and assembly probing.</para> + + <sect2> + <title>Custom type converters</title> + + <para>You can register a custom type converter either Programatically + using the class TypeConverterRegistry or through configuration of + Spring's container and described in the section <link + linkend="context-type-converters">Registering Type + Converters</link>.</para> + + <para></para> + </sect2> </sect1> </chapter> \ No newline at end of file Index: vsnet.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/vsnet.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -C2 -d -r1.12 -r1.13 *** vsnet.xml 20 Dec 2007 16:33:52 -0000 1.12 --- vsnet.xml 16 Jan 2008 17:21:44 -0000 1.13 *************** *** 10,14 **** ! <para>Most of this section is well traveled territory for those familiar with editing XML files in their favorite XML editor. The XML configuration data that defines the objects that Spring will manage for you are --- 10,14 ---- ! <para>Most of this section is well travelled territory for those familiar with editing XML files in their favorite XML editor. The XML configuration data that defines the objects that Spring will manage for you are *************** *** 32,36 **** </spring></programlisting> ! The VS.NET 2005 XML editor can use the attribute <literal>xsi:schemaLocation</literal> --- 32,36 ---- </spring></programlisting> ! The VS.NET 2005 XML editor can use the attribute <literal>xsi:schemaLocation</literal> *************** *** 40,44 **** <literal>xsi:schemaLocation</literal> ! element. If you reference the Spring.NET XML schema as shown below, you can get IntelliSense and validation support while editing a Spring configuration file in VS.NET 2005. In order to get this functionality in VS.NET 2002/2003 you you will need to register the schema with VS.NET or include the schema as part of your application project. <programlisting><?xml version="1.0" encoding="UTF-8"?> --- 40,44 ---- <literal>xsi:schemaLocation</literal> ! element. If you reference the Spring.NET XML schema as shown below, you can get intellisense and validation support while editing a Spring configuration file in VS.NET 2005. In order to get this functionality in VS.NET 2002/2003 you will need to register the schema with VS.NET or include the schema as part of your application project. <programlisting><?xml version="1.0" encoding="UTF-8"?> *************** *** 65,69 **** <para><literal>C:\Program Files\Microsoft Visual Studio .NET ! 2003\Common7\Packages\schemas\xml</literal> for VS.NET 2003</para> --- 65,69 ---- <para><literal>C:\Program Files\Microsoft Visual Studio .NET ! 2003\Common7\Packages\schemas\xml</literal> for VS 2003</para> *************** *** 91,95 **** <para>Spring's .xsd schemas are located in the directory doc/schema. In that directory is also a NAnt build file to help copy over the .xsd files ! to the appropriate VS.NET locations. To execute this scripte simply type '<literal>nant</literal>' in the doc/schema directory.</para> --- 91,95 ---- <para>Spring's .xsd schemas are located in the directory doc/schema. In that directory is also a NAnt build file to help copy over the .xsd files ! to the appropriate VS.NET locations. To execute this script simply type '<literal>nant</literal>' in the doc/schema directory.</para> *************** *** 117,122 **** <para>Once registered, the namespace declaration alone is sufficient to ! get IntelliSense and validation of the configuration file from within ! VS.NET. Alternatively, you can select xsd file to use by setting the targetSchema property in the Property Sheet for the configuration file.</para> --- 117,122 ---- <para>Once registered, the namespace declaration alone is sufficient to ! get intellisense and validation of the configuration file from within ! VS.NET. Alternatively, you can select the .xsd file to use by setting the targetSchema property in the Property Sheet for the configuration file.</para> *************** *** 126,131 **** <para>As shown in the section <xref linkend="objects-factory-client" /> Spring.NET supports using .NET's application configuration file as the ! location to store the object defintions that will be managed by the object ! factory.</para> --- 126,131 ---- <para>As shown in the section <xref linkend="objects-factory-client" /> Spring.NET supports using .NET's application configuration file as the ! location to store the object definitions that will be managed by the ! object factory.</para> *************** *** 159,167 **** <para>In this case VS.NET 2002/2003 will still provide you with ! IntelliSense help but you will not be able to fully validate the document as the entire schema for App.config is not known. To be able to validate this document one would need to install the <ulink url="http://www.radsoftware.com.au/articles/intellisensewebconfig.aspx">.NET ! Configuration File schema</ulink> and and addition schema that incorporates the <literal><spring></literal> and <literal><context></literal> section in addition to the --- 159,167 ---- <para>In this case VS.NET 2002/2003 will still provide you with ! intellisense help but you will not be able to fully validate the document as the entire schema for App.config is not known. To be able to validate this document one would need to install the <ulink url="http://www.radsoftware.com.au/articles/intellisensewebconfig.aspx">.NET ! Configuration File schema</ulink> and an additional schema that incorporates the <literal><spring></literal> and <literal><context></literal> section in addition to the *************** *** 176,180 **** ! <para>Keep these tradeoffs in mind as you decide where to place the bulk of your configuration information. Conventional wisdom is do quick prototyping with App.config and use another IResource location, file or --- 176,180 ---- ! <para>Keep these trade offs in mind as you decide where to place the bulk of your configuration information. Conventional wisdom is do quick prototyping with App.config and use another IResource location, file or *************** *** 199,204 **** <para>Spring provides API documentation that can be integrated within Visual Studio. There are two versions of the documentation, one for VS.NET ! 2002/2003 and the other for VS.NET 2005. They differ only in the format ! applied, VS.NET 2005 using the sexy new format. Enjoy!</para> </sect1> </chapter> \ No newline at end of file --- 199,204 ---- <para>Spring provides API documentation that can be integrated within Visual Studio. There are two versions of the documentation, one for VS.NET ! 2002/2003 and the other for VS 2005. They differ only in the format ! applied, VS 2005 using the sexy new format. Enjoy!</para> </sect1> </chapter> \ No newline at end of file Index: expressions.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/expressions.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** expressions.xml 7 Dec 2006 06:50:25 -0000 1.9 --- expressions.xml 16 Jan 2008 17:21:44 -0000 1.10 *************** *** 4,39 **** <sect1 id="expressions-introduction"> <title>Introduction</title> ! <para> ! The Spring.Expressions namespace provides a powerful expression language for ! querying and manipulating an object graph at runtime. The language supports setting and ! getting of property values, property assignment, method invocation, ! accessing the context of arrays, collections and indexers, ! logical and arithmetic operators, named variables, ! and retrieval of objects by name from Spring's IoC container. ! It also supports list projection and selection, as well as common list aggregators.</para> [...1260 lines suppressed...] --- 978,982 ---- Inventor pupin = new Inventor("Mihajlo Pupin", new DateTime(1854, 10, 9), "Serbian"); ! pupin.Inventions = new string[] {"Long distance telephony & telegraphy", "Secondary X-Ray radiation", "Sonar"}; pupin.PlaceOfBirth.City = "Idvor"; pupin.PlaceOfBirth.Country = "Serbia"; *************** *** 650,654 **** ieee.Members.Add(pupin); ieee.Officers["president"] = pupin; ! ieee.Officers["advisors"] = new Inventor[] {tesla, pupin};]]></programlisting> </sect1> ! </chapter> --- 986,990 ---- ieee.Members.Add(pupin); ieee.Officers["president"] = pupin; ! ieee.Officers["advisors"] = new Inventor[] {tesla, pupin};</programlisting> </sect1> ! </chapter> \ No newline at end of file Index: aop-aspect-library.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/aop-aspect-library.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -C2 -d -r1.10 -r1.11 *** aop-aspect-library.xml 13 Oct 2007 22:34:10 -0000 1.10 --- aop-aspect-library.xml 16 Jan 2008 17:21:44 -0000 1.11 *************** *** 10,15 **** module. However, the aspects that are documented in this section are those contained within the Spring.Aop module itself. The aspects in within ! Spring.Aop.dll are are Caching, Exception Handling, Logging, and Retry. ! Other traditional advice types such as validation, security, and thread management, will be included in a future release.</para> </sect1> --- 10,15 ---- module. However, the aspects that are documented in this section are those contained within the Spring.Aop module itself. The aspects in within ! Spring.Aop.dll are Caching, Exception Handling, Logging, and Retry. Other ! traditional advice types such as validation, security, and thread management, will be included in a future release.</para> </sect1> *************** *** 40,44 **** ASP.NET cache and a simple implementation, <classname>Spring.Caching.NonExpiringCache</classname> that stores cache ! entries in memory and never expires these entries. Custom implementation based on 3rd party implementations, such as Oracle Coherence, or memcached, can be used by implementing the <literal>ICache</literal> --- 40,44 ---- ASP.NET cache and a simple implementation, <classname>Spring.Caching.NonExpiringCache</classname> that stores cache ! entries in memory and never expires these entries. Custom implementations based on 3rd party implementations, such as Oracle Coherence, or memcached, can be used by implementing the <literal>ICache</literal> *************** *** 91,95 **** <listitem> ! <para><literal>Key</literal> - an string representing a Spring Expression Language (SpEL) expression used as the key in the cache.</para> --- 91,95 ---- <listitem> ! <para><literal>Key</literal> - a string representing a Spring Expression Language (SpEL) expression used as the key in the cache.</para> *************** *** 120,124 **** <listitem> <para><literal>SlidingExperation</literal> - If this property value is ! set to true, every time the marked object is accessed it'sTimeToLive value is reset to its original value</para> </listitem> --- 120,124 ---- <listitem> <para><literal>SlidingExperation</literal> - If this property value is ! set to true, every time the marked object is accessed it's TimeToLive value is reset to its original value</para> </listitem> *************** *** 150,154 **** <listitem> ! <para><literal>High</literal> - low likelihood of deletion when cache is purged.</para> </listitem> --- 150,154 ---- <listitem> ! <para><literal>High</literal> - high likelihood of deletion when cache is purged.</para> </listitem> *************** *** 178,186 **** variables to the key expression. If you do not specify a key, then all the parameter values will be used to cache the returned value. The expression ! may also call out to other objects in the spring container allowing for a more complex key algorithm to be encapsulated. The end result is that the Airport object is cached by id for 60 seconds in a cache named ! AspNetCache. The TimetoLive property could also havfe been specified on ! the configuration of the AspNetCache object.</para> <para>The configuration to enable the caching aspect is shown below</para> --- 178,186 ---- variables to the key expression. If you do not specify a key, then all the parameter values will be used to cache the returned value. The expression ! may also call out to other objects in the Spring container allowing for a more complex key algorithm to be encapsulated. The end result is that the Airport object is cached by id for 60 seconds in a cache named ! AspNetCache. The TimetoLive property could also have been specified on the ! configuration of the AspNetCache object.</para> <para>The configuration to enable the caching aspect is shown below</para> *************** *** 209,215 **** <para>in this example an <classname>ObjectNameAutoProxyCreator</classname> ! was used to apply this the cache aspect to objects that have Dao in their ! name. The AspNetCache setting for TimetoLive will override the TimeToLive ! value set on the method level via the attribute.</para> </sect1> --- 209,215 ---- <para>in this example an <classname>ObjectNameAutoProxyCreator</classname> ! was used to apply the cache aspect to objects that have Dao in their name. ! The AspNetCache setting for TimeToLive will override the TimeToLive value ! set at the method level via the attribute.</para> </sect1> *************** *** 241,249 **** that may form part of the exception. Once you get familiar with the feature set of Spring declarative exception handling advice you should ! evaluate where it maybe effectively applied in your code base. It is worth ! to note that you can still chain together multiple pieces of exception ! handling advice allowing you to mix the declarative approach shown in this ! section with the traditional inheritance based approach, i.e. implementing ! IThrowsAdvice or IMethodInterceptor.</para> <para>Declarative exception handling is expressed in the form of a --- 241,249 ---- that may form part of the exception. Once you get familiar with the feature set of Spring declarative exception handling advice you should ! evaluate where it may be effectively applied in your code base. It is ! worth noting that you can still chain together multiple pieces of ! exception handling advice allowing you to mix the declarative approach ! shown in this section with the traditional inheritance based approach, ! i.e. implementing IThrowsAdvice or IMethodInterceptor.</para> <para>Declarative exception handling is expressed in the form of a *************** *** 260,264 **** </object></programlisting>What this is instructing the advice to do is the following bit of code when an ArithmeticException is thrown, throw new ! System.InvalidOperationException("Wrapped ArithmeticException", e). where e is the original ArithmeticException. The default message, "Wrapped ArithmethicException" is automatically appended. You may however specify --- 260,264 ---- </object></programlisting>What this is instructing the advice to do is the following bit of code when an ArithmeticException is thrown, throw new ! System.InvalidOperationException("Wrapped ArithmeticException", e), where e is the original ArithmeticException. The default message, "Wrapped ArithmethicException" is automatically appended. You may however specify *************** *** 347,352 **** performed and the search for other matching exception names continues. For all other actions, namely translate, wrap, replace, swallow, return, once ! can exception handler is matched, those in the chain are no longer ! evaluated. Note, do not confuse this handler chain wit the general advice AOP advice chain. For translate, wrap, and replace actions a SpEL expression is created and used to instantiate a new exception (in addition --- 347,352 ---- performed and the search for other matching exception names continues. For all other actions, namely translate, wrap, replace, swallow, return, once ! an exception handler is matched, those in the chain are no longer ! evaluated. Note, do not confuse this handler chain with the general advice AOP advice chain. For translate, wrap, and replace actions a SpEL expression is created and used to instantiate a new exception (in addition *************** *** 354,359 **** which is then thrown.</para> ! <para>The exception handling DSL also supports the the ability to provide ! a SpEL boolean expression to determine if the advice will apply instead of just filtering by the expression name. For example, the following is the equivalent to the first example based on exception names but compares the --- 354,359 ---- which is then thrown.</para> ! <para>The exception handling DSL also supports the ability to provide a ! SpEL boolean expression to determine if the advice will apply instead of just filtering by the expression name. For example, the following is the equivalent to the first example based on exception names but compares the *************** *** 368,372 **** for a specific error number in an exception, i.e. <literal>(#e is T(System.Data.SqlException) && #e.Errors[0].Number in ! {156,170,207,208})</literal>, to catch and translate bad grammer codes in a SqlException.</para> --- 368,372 ---- for a specific error number in an exception, i.e. <literal>(#e is T(System.Data.SqlException) && #e.Errors[0].Number in ! {156,170,207,208})</literal>, to catch and translate bad grammar codes in a SqlException.</para> *************** *** 390,394 **** expression]</literal></para> ! <para>The exception names are requires as well as the action. The valid actions are</para> --- 390,394 ---- expression]</literal></para> ! <para>The exception names are required as well as the action. The valid actions are</para> *************** *** 421,425 **** <para>The form of the expression depends on the action. For logging, the entire string is taken as the SpEL expression to log. Translate expects ! an exception to be returned from evaluation the SpEL expression. wrap and replace are shorthand for the translate action. For wrap and replace you specify the exception name and the message to pass into the standard --- 421,425 ---- <para>The form of the expression depends on the action. For logging, the entire string is taken as the SpEL expression to log. Translate expects ! an exception to be returned from evaluation the SpEL expression. Wrap and replace are shorthand for the translate action. For wrap and replace you specify the exception name and the message to pass into the standard *************** *** 428,432 **** resolve the typename across all referenced assemblies. You may also register type aliases for use with SpEL in the standard manner with ! Spring.NET and those will be accessible form within the exception handling expression.</para> </sect2> --- 428,432 ---- resolve the typename across all referenced assemblies. You may also register type aliases for use with SpEL in the standard manner with ! Spring.NET and those will be accessible from within the exception handling expression.</para> </sect2> *************** *** 466,470 **** <para>You declare the logging advice in IoC container with the following XML fragment. Alternatively, you can use the class ! <classname>SimpleLoggingAdvice</classname> progammatically.</para> <programlisting><object name="loggingAdvice" type="Spring.Aspects.Logging.SimpleLoggingAdvice, Spring.Aop"> --- 466,470 ---- <para>You declare the logging advice in IoC container with the following XML fragment. Alternatively, you can use the class ! <classname>SimpleLoggingAdvice</classname> programatically.</para> <programlisting><object name="loggingAdvice" type="Spring.Aspects.Logging.SimpleLoggingAdvice, Spring.Aop"> *************** *** 497,501 **** true target type and not the proxy type.</para> ! <para>To futher extend the functionality of the <classname>SimpleLoggingAdvice</classname> you can subclass <classname>SimpleLoggingAdvice</classname> and override the methods</para> --- 497,501 ---- true target type and not the proxy type.</para> ! <para>To further extend the functionality of the <classname>SimpleLoggingAdvice</classname> you can subclass <classname>SimpleLoggingAdvice</classname> and override the methods</para> *************** *** 520,525 **** </itemizedlist> ! <para>The default implementation to calculate a unique identifer is to use ! a Guid. You can alter this behavior by overriding the method <literal>string CreateUniqueIdentifier()</literal>. The <classname>SimpleLoggingAdvice</classname> class inherits from --- 520,525 ---- </itemizedlist> ! <para>The default implementation to calculate a unique identifier is to ! use a GUID. You can alter this behavior by overriding the method <literal>string CreateUniqueIdentifier()</literal>. The <classname>SimpleLoggingAdvice</classname> class inherits from *************** *** 553,557 **** <para>The Spring 1.2 release will have an additional logging advice ! implementation the leverages the Spring Expression Language to further customize the content of the logging messages via simple configuration using similar syntax to the retry and exception handling advice.</para> --- 553,557 ---- <para>The Spring 1.2 release will have an additional logging advice ! implementation that leverages the Spring Expression Language to further customize the content of the logging messages via simple configuration using similar syntax to the retry and exception handling advice.</para> *************** *** 561,571 **** <title>Retry</title> ! <para>When making a distributed call it is oftena common requirement to be ! able to retry the method invocation if there was an exception. Typically ! the exception will be due to a communication issue that is intermitent and ! a retrying over a period of time will likely result in a successful ! invocation. When applying retry advice it is important to know if making ! two calls to the remote service will cause side effects. Genreally ! speaking, the method being invoked should be <ulink url="http://en.wikipedia.org/wiki/Idempotent#Computer_Science">idempotent</ulink>, that is, it is safe to call multiple times.</para> --- 561,571 ---- <title>Retry</title> ! <para>When making a distributed call it is often a common requirement to ! be able to retry the method invocation if there was an exception. ! Typically the exception will be due to a communication issue that is ! intermittent and retrying over a period of time will likely result in a ! successful invocation. When applying retry advice it is important to know ! if making two calls to the remote service will cause side effects. ! Generally speaking, the method being invoked should be <ulink url="http://en.wikipedia.org/wiki/Idempotent#Computer_Science">idempotent</ulink>, that is, it is safe to call multiple times.</para> *************** *** 577,582 **** <para>The meaning is: when an exception that has 'ArithmeticException' in ! its classname is thrown, retry the invocaiton up to 3 times and delay for ! 1 second in between each retry event.</para> <para>You can also provide a SpEL (Spring Expression Language) expression --- 577,582 ---- <para>The meaning is: when an exception that has 'ArithmeticException' in ! its type name is thrown, retry the invocation up to 3 times and delay for ! 1 second between each retry event.</para> <para>You can also provide a SpEL (Spring Expression Language) expression *************** *** 629,633 **** </itemizedlist>You declare the advice in IoC container with the following XML fragment. Alternatively, you can use the ! <classname>RetryAdvice</classname> class progammatically.</para> <programlisting><object name="exceptionHandlingAdvice" type="Spring.Aspects.RetryAdvice, Spring.Aop"> --- 629,633 ---- </itemizedlist>You declare the advice in IoC container with the following XML fragment. Alternatively, you can use the ! <classname>RetryAdvice</classname> class programatically.</para> <programlisting><object name="exceptionHandlingAdvice" type="Spring.Aspects.RetryAdvice, Spring.Aop"> *************** *** 638,642 **** <title>Language Reference</title> ! <para>The general syntax of the languae is</para> <para><literal>on exception name [ExceptionName1,ExceptionName2,...] --- 638,642 ---- <title>Language Reference</title> ! <para>The general syntax of the language is</para> <para><literal>on exception name [ExceptionName1,ExceptionName2,...] Index: psa-intro.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/psa-intro.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** psa-intro.xml 6 Dec 2007 07:25:30 -0000 1.1 --- psa-intro.xml 16 Jan 2008 17:21:44 -0000 1.2 *************** *** 12,21 **** define an exporter for that object. Similarly, on the client side you define an corresponding endpoint accessor. Of course, the object's methods ! stil need to be suitable for remoting, i.e. course grained, to avoid ! making uncessary and expensive remote calls. </para> <para>Since these exporters and client side endpoint accessors are defined using meta data for Spring IoC container, you can easily use dependency ! injection on then 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 --- 12,21 ---- 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.</para> <para>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 *************** *** 29,33 **** 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 programmatically.</para> <para>The diagram shown below is a useful way to demonstrate the key --- 29,33 ---- 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.</para> <para>The diagram shown below is a useful way to demonstrate the key *************** *** 58,62 **** by a thin layer over the client access mechanism of the underlying distributed technology, though in some cases such as client side access to ! web services, you can the option to create a proxy on the fly from the .wsdl definition, much like you would have done using the command line tools.</para> --- 58,62 ---- by a thin layer over the client access mechanism of the underlying distributed technology, though in some cases such as client side access to ! web services, you have the option to create a proxy on the fly from the .wsdl definition, much like you would have done using the command line tools.</para> *************** *** 67,71 **** following this practice, and also lends itself to a straightforward approach to unit testing business functionality as stub or mock ! implementations maybe defined for testing purposes.</para> <para>The assembly <literal>Spring.Services.dll</literal> contains support --- 67,71 ---- following this practice, and also lends itself to a straightforward approach to unit testing business functionality as stub or mock ! implementations may be defined for testing purposes.</para> <para>The assembly <literal>Spring.Services.dll</literal> contains support Index: web.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/web.xml,v retrieving revision 1.33 retrieving revision 1.34 diff -C2 -d -r1.33 -r1.34 *** web.xml 4 Jan 2008 17:09:51 -0000 1.33 --- web.xml 16 Jan 2008 17:21:44 -0000 1.34 *************** *** 41,46 **** Microsoft. It is worth noting that Spring Java has a very popular MVC framework and much of that experience and added value can be ! transliterated to help developers be more productive when using .NET ! upcoming MVC support.</para> <para>As we said earlier, event handlers in code-behind classes really --- 41,46 ---- Microsoft. It is worth noting that Spring Java has a very popular MVC framework and much of that experience and added value can be ! transliterated to help developers be more productive when using the ! upcoming ASP.NET MVC support.</para> <para>As we said earlier, event handlers in code-behind classes really *************** *** 51,57 **** team implemented bidirectional data binding framework to handle the mapping of values to and from the controls on a page to the underlying ! data model. Data binding framework also transparently takes care of data ! type conversion and formatting, enabling application developers to work ! with fully typed data (domain) objects in the event handler's of code-behind files.</para> --- 51,57 ---- team implemented bidirectional data binding framework to handle the mapping of values to and from the controls on a page to the underlying ! data model. The data binding framework also transparently takes care of ! data type conversion and formatting, enabling application developers to ! work with fully typed data (domain) objects in the event handlers of code-behind files.</para> *************** *** 65,69 **** mapping solves this problem by allowing application developers to specify aliases for action results that map to target URLs based on information in ! an external configuration file that easily can be edited. Under consideration for future releases of Spring.NET is a process management framework, which will take this approach to another level, allowing you to --- 65,69 ---- mapping solves this problem by allowing application developers to specify aliases for action results that map to target URLs based on information in ! an external configuration file that can easily be edited. Under consideration for future releases of Spring.NET is a process management framework, which will take this approach to another level, allowing you to *************** *** 71,75 **** <para>Standard localization support is also limited in versions of ASP.NET ! prior to ASP.NET 2.0. Even though Visual Studio.NET 2003 generates a local resource file for each ASP.NET <classname>Page</classname> and user control, those resources are never used by the ASP.NET infrastructure. --- 71,75 ---- <para>Standard localization support is also limited in versions of ASP.NET ! prior to ASP.NET 2.0. Even though Visual Studio 2003 generates a local resource file for each ASP.NET <classname>Page</classname> and user control, those resources are never used by the ASP.NET infrastructure. *************** *** 98,102 **** Spring.NET team had to extend (as in the object-oriented sense) the standard ASP.NET <classname>Page</classname> and ! <classname>UserControl</classname>classes. This means that in order to take advantage of the <emphasis>full</emphasis> feature stack of Spring.Web (most notably bidirectional data binding, localization and --- 98,102 ---- Spring.NET team had to extend (as in the object-oriented sense) the standard ASP.NET <classname>Page</classname> and ! <classname>UserControl</classname> classes. This means that in order to take advantage of the <emphasis>full</emphasis> feature stack of Spring.Web (most notably bidirectional data binding, localization and *************** *** 137,142 **** to locate an appropriate <classname>Page</classname> to handle a HTTP request. The <classname>WebSupportModule</classname> configures ! miscellaneous Spring infrastructure class for use in a web environment, ! for example setting the storage strategy of <classname>LogicalThreadContext</classname> to be <classname>HybridContextStorage</classname>.</para> --- 137,142 ---- to locate an appropriate <classname>Page</classname> to handle a HTTP request. The <classname>WebSupportModule</classname> configures ! miscellaneous Spring infrastructure classes for use in a web ! environment, for example setting the storage strategy of <classname>LogicalThreadContext</classname> to be <classname>HybridContextStorage</classname>.</para> *************** *** 145,150 **** container by the Spring.Web infrastructure is wholly transparent to application developers, who will typically never have to explicitly ! instatiate and configure an IoC container manually (by for example using ! the <literal>new</literal> operator in C#). In order to effect the transparent bootstrapping of the IoC container, the Spring.Web infrastructure requires the insertion of the following configuration --- 145,150 ---- container by the Spring.Web infrastructure is wholly transparent to application developers, who will typically never have to explicitly ! instantiate and configure an IoC container manually (by for example ! using the <literal>new</literal> operator in C#). In order to effect the transparent bootstrapping of the IoC container, the Spring.Web infrastructure requires the insertion of the following configuration *************** *** 251,255 **** context, and resource locations that contain the object definitions that will be used within the web application (such as service or ! busniness tier objects) then need to be specified as child elements within the <context> element. Object definition resources can be fully-qualified paths or URLs, or non-qualified, as in the --- 251,255 ---- context, and resource locations that contain the object definitions that will be used within the web application (such as service or ! business tier objects) then need to be specified as child elements within the <context> element. Object definition resources can be fully-qualified paths or URLs, or non-qualified, as in the *************** *** 268,272 **** application assemblies (<literal>assembly://</literal>), while continuing to load other object definitions from web resources that ! can be easily more easily edited.</para> </listitem> </orderedlist> --- 268,272 ---- application assemblies (<literal>assembly://</literal>), while continuing to load other object definitions from web resources that ! can be more easily edited.</para> </listitem> </orderedlist> *************** *** 382,386 **** <title>Dependency Injection for ASP.NET Pages</title> ! <para>Spring.Web builds on top of the featureset and capabilities of ASP.NET; one example of this can be seen the way that Spring.Web has used the code-behind class of the <classname>Page</classname> mechanism to --- 382,386 ---- <title>Dependency Injection for ASP.NET Pages</title> ! <para>Spring.Web builds on top of the feature set and capabilities of ASP.NET; one example of this can be seen the way that Spring.Web has used the code-behind class of the <classname>Page</classname> mechanism to *************** *** 388,392 **** pattern. In MVC-based (web) applications, the <literal>Controller</literal> is typically a thin wrapper around one or ! more service objects. in the specific case of Spring.Web, the Spring.NET team realized that it was very important that service object dependencies be easily injected into <classname>Page</classname> --- 388,392 ---- pattern. In MVC-based (web) applications, the <literal>Controller</literal> is typically a thin wrapper around one or ! more service objects. In the specific case of Spring.Web, the Spring.NET team realized that it was very important that service object dependencies be easily injected into <classname>Page</classname> *************** *** 517,521 **** </httpModules></programlisting> ! <para>To configure this module, naming conventions are use to identify the module name with configuration instructions in the Spring configuration file. The ModuleTemplates property of --- 517,521 ---- </httpModules></programlisting> ! <para>To configure this module, naming conventions are used to identify the module name with configuration instructions in the Spring configuration file. The ModuleTemplates property of *************** *** 523,527 **** of the HTTP module, HtmlCommentAppender, and as a value the configuration instructions as you would normally use for configuring an ! object with spring. An example is shown below. HttpApplicationConfigurer' ModuleTemplates property.</para> --- 523,527 ---- of the HTTP module, HtmlCommentAppender, and as a value the configuration instructions as you would normally use for configuring an ! object with Spring. An example is shown below. HttpApplicationConfigurer' ModuleTemplates property.</para> *************** *** 549,553 **** standard ASP.NET providers that are registered using the standard ASP.NET mechanism. The adapters inherit from their correspondingly named ! provider class from the BCL.</para> <itemizedlist> --- 549,553 ---- standard ASP.NET providers that are registered using the standard ASP.NET mechanism. The adapters inherit from their correspondingly named ! provider class in the BCL.</para> <itemizedlist> *************** *** 620,624 **** </object></programlisting> ! <para>Your own custom providers of course will contain the additional configuration specific to your implementation.</para> </sect2> --- 620,624 ---- </object></programlisting> ! <para>Your own custom providers of course will contain additional configuration specific to your implementation.</para> </sect2> *************** *** 783,788 **** <literal><body></literal> tags from the previous example are not strictly necessary because they are already defined in the master page. ! However, if these tags are omitted, then Visual Studio.NET.2003 will ! complain about a schema and IntelliSense won't work, so it's much easier to work in the HTML view if those tags are included. They will be ignored when the page is rendered.</para> --- 783,788 ---- <literal><body></literal> tags from the previous example are not strictly necessary because they are already defined in the master page. ! However, if these tags are omitted, then Visual Studio 2003 will ! complain about a schema and intellisense won't work, so it's much easier to work in the HTML view if those tags are included. They will be ignored when the page is rendered.</para> *************** *** 812,821 **** </objects></programlisting> ! <para>This approach alows application developers to change the master page being used for a number of pages within a web application. Of course, the master page can still be overridden on a per context or per page basis by creating a new abstract page definition within a child ! context, or by specifiying the <literal>MasterPageFile</literal> ! property directly.</para> </sect2> </sect1> --- 812,821 ---- </objects></programlisting> ! <para>This approach allows application developers to change the master page being used for a number of pages within a web application. Of course, the master page can still be overridden on a per context or per page basis by creating a new abstract page definition within a child ! context, or by specifying the <literal>MasterPageFile</literal> property ! directly.</para> </sect2> </sect1> *************** *** 825,834 **** <para>A problem with the existing data binding support in ASP.NET is that ! that it is one-way only. It allows application developers to bind page ! controls to the data model and display information from said data model, ! but it doesn't allow for the extraction of values from the controls when ! the form is submitted. Spring.Web adds such bidirectional data binding to ! ASP.NET by allowing developers to specify data binding rules for their ! page, and by automatically evaluating configured data binding rules at the appropriate time in the page's lifecycle.</para> --- 825,834 ---- <para>A problem with the existing data binding support in ASP.NET is that ! it is one-way only. It allows application developers to bind page controls ! to the data model and display information from said data model, but it ! doesn't allow for the extraction of values from the controls when the form ! is submitted. Spring.Web adds such bidirectional data binding to ASP.NET ! by allowing developers to specify data binding rules for their page, and ! by automatically evaluating configured data binding rules at the appropriate time in the page's lifecycle.</para> *************** *** 1001,1005 **** RoundTrip } ! }</programlisting>As you can see, <classname>Trip</classname> class uses <classname>TripPoint</classname> class to represent departure and return, which are exposed as <literal>StartingFrom</literal> and --- 1001,1005 ---- RoundTrip } ! }</programlisting>As you can see, <classname>Trip</classname> class uses the <classname>TripPoint</classname> class to represent departure and return, which are exposed as <literal>StartingFrom</literal> and *************** *** 1066,1070 **** } } ! }</programlisting>There are quite a few of things that are happening in this relatively simple piece of code, so it's worth that we spend some time on each one:<orderedlist> --- 1066,1070 ---- } } ! }</programlisting>There are quite a few things that are happening in this relatively simple piece of code, so it's worth that we spend some time on each one:<orderedlist> *************** *** 1072,1077 **** <para>When the page is initially loaded (<literal>IsPostback == false</literal>), the <literal>InitializeModel</literal> method is ! called which initializes trip object by creating a new instance and ! setting its properties to desired values. Right before page is rendered, <literal>SaveModel</literal> method will be invoked and whatever the value it returns will be stored within HTTP Session. --- 1072,1077 ---- <para>When the page is initially loaded (<literal>IsPostback == false</literal>), the <literal>InitializeModel</literal> method is ! called which initializes the trip object by creating a new instance ! and setting its properties to desired values. Right before page is rendered, <literal>SaveModel</literal> method will be invoked and whatever the value it returns will be stored within HTTP Session. *************** *** 1106,1124 **** now let's focus on the source and target expressions.</para> ! <para>Data Binding framework uses Spring.NET Expression Language to ! define binding expressions. In most cases, like in the example above, both source and target expression will evaluate to a property or a field within one of the controls or a data model. This is ! always the case when you are setting bi-directional binding, as both ! binsing expressions need to be "settable". What is important to remember about <literal>InitializeDataBindings</literal> method (other than the fact that you should configure your data binding rules there, of course ;-), is that it is executed only once <emphasis>per page type</emphasis>. Basically, all of the binding ! expressions are parsed the first time page is instantiated, and are ! the cached and used by all instances of that same page type that are ! created at a later time. This is done for performance reasons, as ! data binding expression parsing on every postback is unnecessary and ! would add a significant overhead to the overall page processing time.</para> </listitem> --- 1106,1124 ---- now let's focus on the source and target expressions.</para> ! <para>The Data Binding framework uses Spring.NET Expression Language ! to define binding expressions. In most cases, like in the example above, both source and target expression will evaluate to a property or a field within one of the controls or a data model. This is ! always the case when you are setting a bi-directional binding, as ! both binding expressions need to be "settable". What is important to remember about <literal>InitializeDataBindings</literal> method (other than the fact that you should configure your data binding rules there, of course ;-), is that it is executed only once <emphasis>per page type</emphasis>. Basically, all of the binding ! expressions are parsed the first time the page is instantiated, and ! are the cached and used by all instances of that same page type that ! are created ... [truncated message content] |
