From f9cb55f9ce740d5db64adb094c97ca775ccb86cd Mon Sep 17 00:00:00 2001 From: markpollack Date: Thu, 6 Nov 2008 06:18:44 +0000 Subject: [PATCH] SPRNET-701 - Self-registering namespace parsers --- doc/reference/src/xsd-configuration.xml | 56 +++++++++++++++++++++++-- 1 file changed, 53 insertions(+), 3 deletions(-) diff --git a/doc/reference/src/xsd-configuration.xml b/doc/reference/src/xsd-configuration.xml index 1fdf2142..49be534f 100644 --- a/doc/reference/src/xsd-configuration.xml +++ b/doc/reference/src/xsd-configuration.xml @@ -76,10 +76,18 @@ <object/> definitions into like you have always done. However, the entire point of using custom schema tags is to make configuration easier. - - The rest of this chapter gives an overview of custom XML Schema - based configuration that are included with the release. + The rest of this chapter gives an overview of custom XML Schema + based configuration that are included with the release. + + + As of Spring.NET 1.2.0 it is no longer necessary to explicitly + configure the namespace parsers that come with Spring + via a custom section in App.config. You will still need to register custom namespace + parsers if you are writing your own. + + +
The <literal>tx</literal> (transaction) schema @@ -132,6 +140,13 @@ parsers in the main .NET application configuration file as shown below + + As of Spring.NET 1.2.0 it is no longer necessary to explicitly + configure the namespace parsers that come with Spring + via a custom section in App.config. You will still need to register custom namespace + parsers if you are writing your own. + + <configuration> <configSections> @@ -177,6 +192,13 @@ You will also need to configure the AOP namespace parser in the main .NET application configuration file as shown below + + As of Spring.NET 1.2.0 it is no longer necessary to explicitly + configure the namespace parsers that come with Spring + via a custom section in App.config. You will still need to register custom namespace + parsers if you are writing your own. + + <configuration> <configSections> @@ -218,6 +240,13 @@ You will also need to configure the Database namespace parser in the main .NET application configuration file as shown below + + As of Spring.NET 1.2.0 it is no longer necessary to explicitly + configure the namespace parsers that come with Spring + via a custom section in App.config. You will still need to register custom namespace + parsers if you are writing your own. + + <configuration> <configSections> @@ -257,6 +286,13 @@ You will also need to configure the remoting namespace parser in the main .NET application configuration file as shown below + + As of Spring.NET 1.2.0 it is no longer necessary to explicitly + configure the namespace parsers that come with Spring + via a custom section in App.config. You will still need to register custom namespace + parsers if you are writing your own. + + <configuration> <configSections> @@ -295,6 +331,13 @@ You will also need to configure the remoting namespace parser in the main .NET application configuration file as shown below + + As of Spring.NET 1.2.0 it is no longer necessary to explicitly + configure the namespace parsers that come with Spring + via a custom section in App.config. You will still need to register custom namespace + parsers if you are writing your own. + + <configuration> <configSections> @@ -334,6 +377,13 @@ You will also need to configure the validation namespace parser in the main .NET application configuration file as shown below + + As of Spring.NET 1.2.0 it is no longer necessary to explicitly + configure the namespace parsers that come with Spring + via a custom section in App.config. You will still need to register custom namespace + parsers if you are writing your own. + + <configuration> <configSections>