Update of /cvsroot/springnet/Spring.Net/doc/reference/src
In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv11497
Modified Files:
xml-custom.xml
Log Message:
Renamed INamespaceHandler to INamespaceParser.
Index: xml-custom.xml
===================================================================
RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/xml-custom.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** xml-custom.xml 5 May 2008 20:04:55 -0000 1.2
--- xml-custom.xml 13 May 2008 12:47:11 -0000 1.3
***************
*** 29,33 ****
<listitem>
! <para><link linkend="extensible-xml-namespacehandler">Coding</link>
a custom <interfacename>INamespaceParser</interfacename>
implementation (this is an easy step, don't worry).</para>
--- 29,33 ----
<listitem>
! <para><link linkend="extensible-xml-namespaceparser">Coding</link>
a custom <interfacename>INamespaceParser</interfacename>
implementation (this is an easy step, don't worry).</para>
***************
*** 135,149 ****
</section>
! <section id="extensible-xml-namespacehandler">
! <title>Coding a <interfacename>INamespaceHandler</interfacename></title>
<para>In addition to the schema, we need an
<interfacename>INamespaceParser</interfacename> that will parse all
elements of this specific namespace Spring encounters while parsing
! configuration files. The <interfacename>INamespaceHandler</interfacename>
should in our case take care of the parsing of the
<literal>myns:regex</literal> element.</para>
! <para>The <interfacename>INamespaceHandler</interfacename> interface is
pretty simple in that it features just two methods:</para>
--- 135,149 ----
</section>
! <section id="extensible-xml-namespaceparser">
! <title>Coding a <interfacename>INamespaceParser</interfacename></title>
<para>In addition to the schema, we need an
<interfacename>INamespaceParser</interfacename> that will parse all
elements of this specific namespace Spring encounters while parsing
! configuration files. The <interfacename>INamespaceParser</interfacename>
should in our case take care of the parsing of the
<literal>myns:regex</literal> element.</para>
! <para>The <interfacename>INamespaceParser</interfacename> interface is
pretty simple in that it features just two methods:</para>
***************
*** 151,155 ****
<listitem>
<para><methodname>Init()</methodname> - allows for initialization of
! the <interfacename>INamespaceHandler</interfacename> and will be
called by Spring before the handler is used</para>
</listitem>
--- 151,155 ----
<listitem>
<para><methodname>Init()</methodname> - allows for initialization of
! the <interfacename>INamespaceParser</interfacename> and will be
called by Spring before the handler is used</para>
</listitem>
***************
*** 165,169 ****
<para>Although it is perfectly possible to code your own
! <interfacename>INamespaceHandler</interfacename> for the entire namespace
(and hence provide code that parses each and every element in the
namespace), it is often the case that each top-level XML element in a
--- 165,169 ----
<para>Although it is perfectly possible to code your own
! <interfacename>INamespaceParser</interfacename> for the entire namespace
(and hence provide code that parses each and every element in the
namespace), it is often the case that each top-level XML element in a
|
