[Springnet-commits] Spring.Net/doc/reference/src web.xml, 1.38, 1.39
Brought to you by:
aseovic,
markpollack
Menu
▾
▴
[Springnet-commits] Spring.Net/doc/reference/src web.xml, 1.38, 1.39
|
From: Mark P. <mar...@us...> - 2008-04-29 01:46:03
|
Update of /cvsroot/springnet/Spring.Net/doc/reference/src In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv328 Modified Files: web.xml Log Message: SPRNET-925 - Update documentation for DI in ASP.NET regarding use of name attribute and object definition inheritance Index: web.xml =================================================================== RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/web.xml,v retrieving revision 1.38 retrieving revision 1.39 diff -C2 -d -r1.38 -r1.39 *** web.xml 3 Apr 2008 06:03:10 -0000 1.38 --- web.xml 29 Apr 2008 01:45:56 -0000 1.39 *************** *** 44,47 **** --- 44,57 ---- upcoming ASP.NET MVC support.</para> + <para></para> + + <para>Spring.Web also adds support for applying the dependency injection + principle to one's ASP.NET <classname>Pages</classname> and + <classname>Controls</classname> as well as http modules and custom + provider modules. This means that application developers can easily inject + service dependencies into web controllers by leveraging the power of the + Spring.NET IoC container. See <link linkend="web-di">Dependency Injection + for ASP.NET Pages</link> for more information.</para> + <para>As we said earlier, event handlers in code-behind classes really should not have to deal with ASP.NET UI controls directly. Such event *************** *** 86,97 **** more information.</para> - <para>Spring.Web also adds support for applying the dependency injection - principle to one's ASP.NET <classname>Pages</classname> and - <classname>Controls</classname> as well as http modules and custom - provider modules. This means that application developers can easily inject - service dependencies into web controllers by leveraging the power of the - Spring.NET IoC container. See <link linkend="web-di">Dependency Injection - for ASP.NET Pages</link> for more information.</para> - <para>In addition to the aforementioned features that can be considered to be the <emphasis>'core'</emphasis> features of the Spring.Web framework, --- 96,99 ---- *************** *** 415,419 **** <programlisting><objects xmlns="http://www.springframework.net"> ! <object id="basePage" abstract="true"> <property name="MasterPageFile" value="~/Web/StandardTemplate.master"/> </object> --- 417,421 ---- <programlisting><objects xmlns="http://www.springframework.net"> ! <object name="basePage" abstract="true"> <property name="MasterPageFile" value="~/Web/StandardTemplate.master"/> </object> *************** *** 481,491 **** simply use the name of the <literal>.aspx</literal> file as the object identifier (minus any leading path information, and minus the file ! extension too).</para> ! <para>Of course, nothing prevents an application developer from specifying ! an <literal>id</literal> or <literal>name</literal> value explicitly; one ! use case when the explicit naming might be useful is when one wants to ! expose the same page multiple times using a slightly different ! configuration (Add / Edit pages for example).</para> <sect2 id="web-di-controls"> --- 483,496 ---- simply use the name of the <literal>.aspx</literal> file as the object identifier (minus any leading path information, and minus the file ! extension too). </para> ! <para>Nothing prevents an application developer from specifying an ! <literal>id</literal> or <literal>name</literal> value explicitly; one use ! case when the explicit naming might be useful is when one wants to expose ! the same page multiple times using a slightly different configuration (Add ! / Edit pages for example). If you would like to use abstract object ! definitions and have your page inherit from them, the use of the name ! attribute should be used instead of the id attribute on the abstract ! object definition.</para> <sect2 id="web-di-controls"> *************** *** 829,833 **** <objects xmlns="http://www.springframework.net"> ! <object id="basePage" abstract="true"> <property name="MasterPageFile" value="~/MasterLayout.ascx"/> </object> --- 834,838 ---- <objects xmlns="http://www.springframework.net"> ! <object name="basePage" abstract="true"> <property name="MasterPageFile" value="~/MasterLayout.ascx"/> </object> *************** *** 1860,1864 **** <programlisting><object id="localizer" type="Spring.Globalization.Localizers.ResourceSetLocalizer, Spring.Core"/> ! <object id="basePage" abstract="true"> <description> Pages that reference this definition as their parent --- 1865,1869 ---- <programlisting><object id="localizer" type="Spring.Globalization.Localizers.ResourceSetLocalizer, Spring.Core"/> ! <object name="basePage" abstract="true"> <description> Pages that reference this definition as their parent *************** *** 2002,2006 **** shown below.</para> ! <programlisting><object id="BasePage" abstract="true"> <property name="CultureResolver"> <object type="Spring.Globalization.Resolvers.CookieCultureResolver, Spring.Web"/> --- 2007,2011 ---- shown below.</para> ! <programlisting><object name="BasePage" abstract="true"> <property name="CultureResolver"> <object type="Spring.Globalization.Resolvers.CookieCultureResolver, Spring.Web"/> *************** *** 2396,2400 **** such configuration is shown below:</para> ! <programlisting><object id="basePage" abstract="true"> <description> Convenience base page definition for all the pages. --- 2401,2405 ---- such configuration is shown below:</para> ! <programlisting><object name="basePage" abstract="true"> <description> Convenience base page definition for all the pages. *************** *** 2424,2435 **** <para>The location in the web page where validation errors are to be ! rendered can be specifies by using the ValidationSummary and ! ValidationError controls. There are two controls since they have ! different defaults for how errors are rendered. ValidationSummary is ! used to display potentially multiple errors identified by the validation ! framework. ValidationError is used to display field-level validation ! errors. Please refer to the validation section <link ! linkend="validation-aspnet-usage">ASP.NET usage tips</link> for more ! information.</para> </sect2> --- 2429,2443 ---- <para>The location in the web page where validation errors are to be ! rendered can be specifies by using the ! <classname>ValidationSummary</classname> and ! <classname>ValidationError</classname> controls. There are two controls ! since they have different defaults for how errors are rendered. ! <classname>ValidationSummary</classname> is used to display potentially ! multiple errors identified by the validation framework. ! <classname>ValidationError</classname> is used to display field-level ! validation errors. Please refer to the section <link ! linkend="validation-aspnet-usage">ASP.NET usage tips</link> in the ! chapter on the <link linkend="validation">Validation Framework</link> ! more information.</para> </sect2> |
