minor doc updates for various JIRA issues...

2008-10-03 16:24:38 +00:00
parent c1aa74632b
commit 26cb75d4e0
5 changed files with 74 additions and 16 deletions
--- a/doc/reference/src/dbprovider.xml
+++ b/doc/reference/src/dbprovider.xml
@@ -108,11 +108,16 @@
      </listitem>

      <listitem>
-        <para><literal>SqlServerCe-3.1</literal> (aliased to
-        <literal>System.Data.SqlServerCe</literal>) - Microsoft SQL Server
+        <para><literal>SqlServerCe-3.1</literal> - Microsoft SQL Server
        Compact Edition, provider V9.0.242.0</para>
      </listitem>

+      <listitem>
+        <para><literal>SqlServerCe-3.5.1</literal> (aliased to
+        <literal>System.Data.SqlServerCe</literal>) - Microsoft SQL Server
+        Compact Edition, provider V3.5.1.0</para>
+      </listitem>
+
      <listitem>
        <para><code>OleDb-1.1</code> - OleDb, provider V1.0.5000.0 in
        framework .NET V1.1</para>
@@ -219,6 +224,11 @@
        15.x</para>
      </listitem>

+      <listitem>
+        <para><literal>SybaseAse-AdoNet2</literal> - Sybase ADO.NET 2.0
+        provider for ASE 12.x and 15.x</para>
+      </listitem>
+
      <listitem>
        <para><literal>Odbc-1.1</literal> - ODBC provider V1.0.5000.0 in
        framework .NET V1.1</para>
--- a/doc/reference/src/messaging.xml
+++ b/doc/reference/src/messaging.xml
@@ -257,7 +257,7 @@
        <title>Caching EMS Resources</title>

        <para>The class
-        Spring.Messaging.Nms.Connections.CachingConnectionFactory </para>
+        Spring.Messaging.Nms.Connections.CachingConnectionFactory</para>
      </section>
    </section>

@@ -290,9 +290,9 @@

        <para><classname>Spring.Messaging.Nms.Connections.CachingConnectionFactory</classname>
        extends the functionality of SingleConnectionFactory and adds the
-        caching of Sessions, MessageProducers, and MessageConsumers. </para>
+        caching of Sessions, MessageProducers, and MessageConsumers.</para>

-        <para> The initial cache size is set to 1, use the property
+        <para>The initial cache size is set to 1, use the property
        <literal>SessionCacheSize</literal> to increase the number of cached
        sessions. Note that the number of actual cached sessions will be more
        than that number as sessions are cached based on their acknowledgment
@@ -302,7 +302,7 @@
        <classname>MessageProducers</classname> and
        <classname>MessageConsumers</classname> are cached within their owning
        session and also take into account the unique properties of the
-        producers and consumers when caching. </para>
+        producers and consumers when caching.</para>

        <para><classname>MessageProducers</classname> are cached based on
        their destination. <classname>MessageConsumers</classname> are cached
@@ -1129,7 +1129,8 @@ namespace MyApp
 &lt;/nms:listener-container&gt;</programlisting>

      <para>The example above is equivalent to creating two distinct listener
-      container object definitions and two distinct MessageListenerAdapter object      definitions as demonstrated in the section entitled <xref
+      container object definitions and two distinct MessageListenerAdapter
+      object definitions as demonstrated in the section entitled <xref
      linkend="message-listener-adapter" />. In addition to the attributes
      shown above, the listener element may contain several optional ones. The
      following table describes all available attributes:</para>
@@ -1271,7 +1272,7 @@ namespace MyApp
              <entry>connection-factory</entry>

              <entry><para>A reference to the NMS
-              <interfacename>ConnectionFactory</interfacename> bean (the
+              <interfacename>ConnectionFactory</interfacename> object (the
              default object name is
              <literal>'ConnectionFactory'</literal>).</para></entry>
            </row>
@@ -1351,6 +1352,14 @@ namespace MyApp
              Spring's TimeSpanConverter (e.g. 10s, 10m, 3h, etc)
              </para></entry>
            </row>
+
+            <row>
+              <entry>auto-startup</entry>
+
+              <entry>Set whether to automatically start the listeners after
+              initialization. Default is true, optionally set to
+              false.</entry>
+            </row>
          </tbody>
        </tgroup>
      </table>
--- a/doc/reference/src/objects.xml
+++ b/doc/reference/src/objects.xml
@@ -5062,6 +5062,17 @@ cfg.PostProcessObjectFactory(factory);</programlisting></para>
  &lt;/spring&gt;

 &lt;/configuration&gt;</programlisting>
+
+      <para>You can also register custom parser programmatically using the
+      NamespaceParserRegistry. Here is an example taken from the code used in
+      the Transactions Quickstart application.</para>
+
+      <programlisting>NamespaceParserRegistry.RegisterParser(typeof(DatabaseNamespaceParser));
+NamespaceParserRegistry.RegisterParser(typeof(TxNamespaceParser));
+NamespaceParserRegistry.RegisterParser(typeof(AopNamespaceParser));
+
+IApplicationContext context = 
+      new XmlApplicationContext("assembly://Spring.TxQuickStart.Tests/Spring.TxQuickStart/system-test-local-config.xml");</programlisting>
    </sect2>

    <sect2 id="context-custom-resourcehandler">
@@ -5125,7 +5136,7 @@ cfg.PostProcessObjectFactory(factory);</programlisting></para>
      the configSecitons section of App.config. The type alias configuration
      section contains one or more &lt;alias&gt; elements each with a name and
      a type attribute. Below is an example that registers the alias for
-      WebServiceExporter </para>
+      WebServiceExporter</para>

      <programlisting>&lt;configuration&gt;

@@ -5144,7 +5155,7 @@ cfg.PostProcessObjectFactory(factory);</programlisting></para>

 &lt;/configuration&gt;</programlisting>

-      <para> For an example showing type aliases for generic types see <xref
+      <para>For an example showing type aliases for generic types see <xref
      linkend="objects-creation-generic-types" />.</para>

      <para>Another way is to define an object of the type
--- a/doc/reference/src/overview.xml
+++ b/doc/reference/src/overview.xml
@@ -188,7 +188,7 @@
    <para>With the building blocks described above you can use Spring in all
    sorts of scenarios, from simple stand alone console applications to
    fully-fledged enterprise applications using Spring's transaction
-    management functionality and web framework integration. </para>
+    management functionality and web framework integration.</para>

    <para>It is important to note that the Spring Framework <emphasis>does
    not</emphasis> force you to use everything within it; it is not an
@@ -198,13 +198,13 @@
    access features that Spring offers. The only things you need to do is wire
    up your business logic using Spring's IoC container and integrate it into
    your web layer using WebApplicationContext to locate middle tier services
-    and/or configure your standard ASP.NET pages with depdenency injection.
-    </para>
+    and/or configure your standard ASP.NET pages with depdenency
+    injection.</para>

    <para>While the Spring framework does not force any particular application
    architecure it encourages the use of a well layered application
    architecture with distinct tiers for the presentation, service, data
-    access, and database. </para>
+    access, and database.</para>
  </sect1>

  <sect1>
@@ -244,7 +244,13 @@
        - A calculator demonstrating remote service abstractions that let you
        'export' a plain .NET object (PONO) via .NET Remoting, Web Services,
        or an EnterpriseService ServiceComponent. Corresponding client side
-        proxies are also demonstrated. .</para>
+        proxies are also demonstrated.</para>
+      </listitem>
+
+      <listitem>
+        <para><link linkend="wcf-quickstart">WCF</link> - Shows a WCF based
+        calculator example that configures your WCF service via dependency
+        injection and apply AOP advice.</para>
      </listitem>

      <listitem>
@@ -283,6 +289,22 @@
        included showing how to use the Open-Session In View approach to
        session management in the web tier.</para>
      </listitem>
+
+      <listitem>
+        <para><link linkend="quartz-quickstart">Quartz Quickstart</link> -
+        Application that shows the use of Quartz.NET integration for
+        scheduling.</para>
+      </listitem>
+
+      <listitem>
+        <para><link lang="" linkend="msmq-quickstart">MSMQ</link> -
+        Application demonstrating MSMQ helper classes.</para>
+      </listitem>
+
+      <listitem>
+        <para><link linkend="nms-quickstart">NMS</link> - Applicatoin
+        demonstrating NMS helper classes.</para>
+      </listitem>
    </itemizedlist>
  </sect1>

--- a/doc/reference/src/transaction.xml
+++ b/doc/reference/src/transaction.xml
@@ -455,7 +455,13 @@
    rollback the transaction programmatically and you are using declarative
    transaction management, use the utility method</para>

-    <programlisting>TransactionInterceptor.CurrentTransactionStatus.RollbackOnly = true;</programlisting>
+    <programlisting>TransactionInterceptor.CurrentTransactionStatus.SetRollbackOnly();</programlisting>
+
+    <note>
+      <para>Prior to Spring.NET 1.2 RC1 the API call would be
+      <literal>TransactionInterceptor.CurrentTransactionStatus.RollbackOnly =
+      true;</literal></para>
+    </note>

    <sect2 id="tx-understandingimpl">
      <title id="objectnameautoproxycreator-for-transactions">Understanding