Spring/spring-net
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SPRNET-701 - Self-registering namespace parsers

Browse Source
This commit is contained in:
markpollack
2008-11-06 06:18:44 +00:00
parent 2f5d7a556f
commit f9cb55f9ce
1 changed files with 53 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

56
doc/reference/src/xsd-configuration.xml
View File

@@ -76,10 +76,18 @@
<literal>&lt;object/&gt;</literal> definitions into like you have always
done. However, the entire point of using custom schema tags is to make
configuration easier.</para>
</section>
<para>The rest of this chapter gives an overview of custom XML Schema
based configuration that are included with the release.</para>
<para>The rest of this chapter gives an overview of custom XML Schema
based configuration that are included with the release.</para>
<note>
<para>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.</para>
</note>
</section>
<section xml:id="xsd-config-body-schemas-tx">
<title>The <literal>tx</literal> (transaction) schema</title>
@@ -132,6 +140,13 @@
parsers in the main .NET application configuration file as shown
below</para>
<note>
<para>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.</para>
</note>
<programlisting language="myxml">&lt;configuration&gt;
&lt;configSections&gt;
@@ -177,6 +192,13 @@
<para>You will also need to configure the AOP namespace parser in the
main .NET application configuration file as shown below</para>
<note>
<para>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.</para>
</note>
<programlisting language="myxml">&lt;configuration&gt;
&lt;configSections&gt;
@@ -218,6 +240,13 @@
<para>You will also need to configure the Database namespace parser in
the main .NET application configuration file as shown below</para>
<note>
<para>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.</para>
</note>
<programlisting language="myxml">&lt;configuration&gt;
&lt;configSections&gt;
@@ -257,6 +286,13 @@
<para>You will also need to configure the remoting namespace parser in
the main .NET application configuration file as shown below</para>
<note>
<para>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.</para>
</note>
<programlisting language="myxml">&lt;configuration&gt;
&lt;configSections&gt;
@@ -295,6 +331,13 @@
<para>You will also need to configure the remoting namespace parser in
the main .NET application configuration file as shown below</para>
<note>
<para>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.</para>
</note>
<programlisting language="myxml">&lt;configuration&gt;
&lt;configSections&gt;
@@ -334,6 +377,13 @@
<para>You will also need to configure the validation namespace parser in
the main .NET application configuration file as shown below</para>
<note>
<para>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.</para>
</note>
<programlisting language="myxml">&lt;configuration&gt;
&lt;configSections&gt;