diff --git a/doc/reference/src/objects.xml b/doc/reference/src/objects.xml index 3fd88644..abc2c657 100644 --- a/doc/reference/src/objects.xml +++ b/doc/reference/src/objects.xml @@ -3922,7 +3922,7 @@ public sealed class Font : MarshalByRefObject, ICloneable, ISerializable, IDispo <object id="exampleInitObject" type="Examples.ExampleObject" init-method="init"/> - [C#] + [C#] public class ExampleObject { public void Init() @@ -4741,10 +4741,10 @@ cfg.PostProcessObjectFactory(factory); with a database connection and also a value for the maximum number of results to return in a query. Instead of hard coding the values into the main Spring.NET configuration file we use place holders, in the - NAnt style of ${variableName}, and obtain their values from - NameValueSections in the standard .NET application configuration file. - The Spring.NET configuration file looks like: <configuration> + NAnt style of ${variableName}, and obtain their + values from NameValueSections in the standard .NET + application configuration file. The Spring.NET configuration file + looks like: <configuration> <configSections> <sectionGroup name="spring"> @@ -4770,9 +4770,9 @@ cfg.PostProcessObjectFactory(factory); </configuration> - Notice the presence of two NameValueSections in the - configuration file. These name value pairs will be referred to in the - Spring.NET configuration file. In this example we are using an + Notice the presence of two NameValueSections + in the configuration file. These name value pairs will be referred to + in the Spring.NET configuration file. In this example we are using an embedded assembly resource for the location of the Spring.NET configuration file so as to reduce the chance of accidental tampering in deployment. This Spring.NET configuration file is shown @@ -4783,29 +4783,29 @@ cfg.PostProcessObjectFactory(factory); xsi:schemaLocation="http://www.springframework.net http://www.springframework.net/xsd/spring-objects.xsd" > - <object name="productDao" type="DaoApp.SimpleProductDao, DaoApp "> - <property name="maxResults" value="${maxResults}"/> - <property name="dbConnection" ref="myConnection"/> - </object> - - <object name="myConnection" type="System.Data.Odbc.OdbcConnection, System.Data"> - <property name="connectionstring" value="${connection.string}"/> - </object> + <object name="productDao" type="DaoApp.SimpleProductDao, DaoApp "> + <property name="maxResults" value="${maxResults}"/> + <property name="dbConnection" ref="myConnection"/> + </object> + + <object name="myConnection" type="System.Data.Odbc.OdbcConnection, System.Data"> + <property name="connectionstring" value="${connection.string}"/> + </object> - <object name="appConfigPropertyHolder" - type="Spring.Objects.Factory.Config.PropertyPlaceholderConfigurer, Spring.Core"> + <object name="appConfigPropertyHolder" + type="Spring.Objects.Factory.Config.PropertyPlaceholderConfigurer, Spring.Core"> + <property name="configSections"> + <value>DaoConfiguration,DatabaseConfiguration</value> + </property> + </object> - <property name="configSections"> - <value>DaoConfiguration,DatabaseConfiguration</value> - </property> - - </object> </objects> The values of ${maxResults} and ${connection.string} match the key names used in - the two NameValueSectionHandlers DaoConfiguration - and DatabaseConfiguration. The + the two NameValueSectionHandlers + DaoConfiguration and + DatabaseConfiguration. The PropertyPlaceholderConfigurer refers to these two sections via a comma delimited list of section names in the configSections property. If you are using section @@ -4846,8 +4846,10 @@ cfg.PostProcessObjectFactory(factory); If the class is unable to be resolved at runtime to a valid type, resolution of the object will fail once it is about to be - created (which is during the PreInstantiateSingletons() phase of an - ApplicationContext for a non-lazy-init object.) + created (which is during the + PreInstantiateSingletons() phase of an + ApplicationContext for a non-lazy-init + object.) Similarly you can replace 'ref' and 'expression' metadata, as shown below @@ -4961,14 +4963,14 @@ cfg.PostProcessObjectFactory(factory); IVariableSource - 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 configuration section in .NET 2.0. The list of - implementing classes is listed below. Please refer to the SDK + 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 configuration section in .NET 2.0. The + list of implementing classes is listed below. Please refer to the SDK documentation for more information. @@ -5015,17 +5017,17 @@ cfg.PostProcessObjectFactory(factory); property defined in multiple IVariableSource implementations, the first one in the list that contains the property value will be used. <object type="Spring.Objects.Factory.Config.VariablePlaceholderConfigurer, Spring.Core"> - <property name="VariableSources"> - <list> - <object type="Spring.Objects.Factory.Config.PropertyFileVariableSource, Spring.Core"> - <property name="Location" value="~\application.properties" /> - <property name="IgnoreMissingResources" value="true"/> - </object> - <object type="Spring.Objects.Factory.Config.ConfigSectionVariableSource, Spring.Core"> - <property name="SectionNames" value="CryptedConfiguration" /> - </object> - </list> - </property> + <property name="VariableSources"> + <list> + <object type="Spring.Objects.Factory.Config.PropertyFileVariableSource, Spring.Core"> + <property name="Location" value="~\application.properties" /> + <property name="IgnoreMissingResources" value="true"/> + </object> + <object type="Spring.Objects.Factory.Config.ConfigSectionVariableSource, Spring.Core"> + <property name="SectionNames" value="CryptedConfiguration" /> + </object> + </list> + </property> </object> The use of the IgnoreMissingResources