Update reference documentation generation tools to get source highlighting [SPRNET-1045]

doc/reference/src/pool.xml

@@ -1,8 +1,25 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<chapter id="pool">
+<!--
+/*
+ * Copyright 2002-2008 the original author or authors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+-->
+<chapter xml:id="pool" xmlns="http://docbook.org/ns/docbook" version="5">
   <title>Object Pooling</title>
 
-  <sect1 id="pool-introduction">
+  <sect1 xml:id="pool-introduction">
     <title>Introduction</title>
 
     <para>The Spring.Pool namespace contains a generic API for implementing
@@ -37,7 +54,7 @@
     <para>Note, that if you are concerned only with applying pooling to an
     existing object, the pooling APIs discussed here are not very important.
     Instead the use and configuration of
-    <classname>Spring.Aop.Target.SimplePoolTargetSource</classname> is more
+    <literal>Spring.Aop.Target.SimplePoolTargetSource</literal> is more
     relevant. Pooling of objects can either be done Programatically or through
     the XML configuration of the Spring .NET container. Attribute support for
     pooling, similar to the ServicedComponent approach, will be available in a
@@ -47,21 +64,21 @@
     use of the pooling API independent of AOP functionality.</para>
   </sect1>
 
-  <sect1 id="pool-api">
+  <sect1 xml:id="pool-api">
     <title>Interfaces and Implementations</title>
 
     <para>The <literal>Spring.Pool</literal> namespace provides two simple
     interfaces to manage pools of objects. The first interface,
-    <classname>IObjectPool</classname> describes how to take and put back an
+    <literal>IObjectPool</literal> describes how to take and put back an
     object from the pool. The second interface
-    <classname>IPoolableObjectFactory</classname> is meant to be used in
-    conjunction with implementations of the <classname>IObjectPool</classname>
+    <literal>IPoolableObjectFactory</literal> is meant to be used in
+    conjunction with implementations of the <literal>IObjectPool</literal>
     to provide guidance in calling various lifecycle events on the objects
     managed by the pool. These interfaces are based on the Jakarta Commons
-    Pool API. <classname>Spring.Pool.Support.SimplePool</classname> is a
-    default implementation of <classname>IObjectPool</classname> and
-    <classname>Spring.Aop.Target.SimplePoolTargetSource</classname> is the
-    implementation of <classname>IPoolableObjectFactory</classname> for use
+    Pool API. <literal>Spring.Pool.Support.SimplePool</literal> is a
+    default implementation of <literal>IObjectPool</literal> and
+    <literal>Spring.Aop.Target.SimplePoolTargetSource</literal> is the
+    implementation of <literal>IPoolableObjectFactory</literal> for use
     with AOP. The current goal of the Spring.Pool namespace is not to provide
     a one-for-one replacement of the Jakarta Commons Pool API, but rather to
     support basic object pooling needs for common AOP scenarios. Consequently,