cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ericjohn...@apache.org
Subject svn commit: r440874 - in /incubator/cxf/trunk/docs/src/docs: guides/ styleguide/
Date Wed, 06 Sep 2006 21:17:40 GMT
Author: ericjohnson
Date: Wed Sep  6 14:17:39 2006
New Revision: 440874

URL: http://svn.apache.org/viewvc?view=rev&rev=440874
Log:
revised how block sections work

Modified:
    incubator/cxf/trunk/docs/src/docs/guides/configuration.xml
    incubator/cxf/trunk/docs/src/docs/guides/develop_consumer.xml
    incubator/cxf/trunk/docs/src/docs/guides/getting_started.xml
    incubator/cxf/trunk/docs/src/docs/guides/jms.xml
    incubator/cxf/trunk/docs/src/docs/guides/management.xml
    incubator/cxf/trunk/docs/src/docs/guides/tomcat_deploy.xml
    incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml
    incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml
    incubator/cxf/trunk/docs/src/docs/styleguide/lists.xml
    incubator/cxf/trunk/docs/src/docs/styleguide/overview.xml
    incubator/cxf/trunk/docs/src/docs/styleguide/structure.xml
    incubator/cxf/trunk/docs/src/docs/styleguide/tables.xml

Modified: incubator/cxf/trunk/docs/src/docs/guides/configuration.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/guides/configuration.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/guides/configuration.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/guides/configuration.xml Wed Sep  6 14:17:39 2006
@@ -221,7 +221,7 @@
 
     <para>The CeltiXfire XML metadata files are as follows:</para>
 
-    <section>
+    <simplesect>
       <title>bus-config.xml</title>
 
       <para><filename>resources/config-metadata/bus-config.xml</filename>
@@ -249,9 +249,9 @@
       attribute in the <sgmltag class="element">bean</sgmltag> element is
       derived from the following namespace declaration:
       <classname>org.objectweb.celtix.bus.bus_config.spring.BusConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>endpoint-config.xml</title>
 
       <para><filename>resources/config-metadata/endpoint-config.xml</filename>
@@ -283,9 +283,9 @@
       class="attribute">class</sgmltag> attribute in the <sgmltag
       class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.jaxws.endpoint_config.spring.EndpointConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>http-client-config.xml</title>
 
       <para><filename>resources/config-metadata/http-client-config.xml</filename>
@@ -318,9 +318,9 @@
       class="attribute">class</sgmltag> attribute in the <sgmltag
       class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.transports.http.http_client_config.spring.HttpClientConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>http-listener-config.xml</title>
 
       <para><filename>resources/config-metadata/http-listener-config.xml</filename>
@@ -344,9 +344,9 @@
       class="attribute">class</sgmltag> attribute in the <sgmltag
       class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.transports.http.http_server_config.spring.HttpListenerConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>http-server-config.xml</title>
 
       <para><filename>resources/config-metadata/http-server-config.xml</filename>
@@ -373,9 +373,9 @@
       class="attribute">class</sgmltag> attribute in the <sgmltag
       class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.transports.http.http_server_config.spring.HttpServerConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>instrumentation-config.xml</title>
 
       <para><filename>resources/config-metadata/instrumentation-config.xml</filename>
@@ -397,9 +397,9 @@
       class="attribute">class</sgmltag> attribute in the <sgmltag
       class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.instrumentation.spring.InstrumentationConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>jms-client-config.xml</title>
 
       <para><filename>resources/config-metadata/jms-client-config.xml</filename>
@@ -423,9 +423,9 @@
       class="attribute">class</sgmltag> attribute in the <sgmltag
       class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.transports.jms.jms_client_config.spring.JmsClientConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>jms-server-config.xml</title>
 
       <para><filename>resources/config-metadata/jms-server-config.xml</filename>
@@ -448,9 +448,9 @@
       class="attribute">class</sgmltag> attribute in the <sgmltag
       class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.transports.jms.jms_server_config.spring.JmsServerConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>port-config.xml</title>
 
       <para><filename>resources/config-metadata/port-config.xml</filename>
@@ -490,9 +490,9 @@
       class="attribute">class</sgmltag> attribute in the <sgmltag
       class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.jaxws.port_config.spring.PortConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>rm-config.xml</title>
 
       <para><filename>resources/config-metadata/rm-config.xml</filename>
@@ -519,9 +519,9 @@
       entries, the value of the <sgmltag class="attribute">class</sgmltag>
       attribute in the <sgmltag class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.bus.ws.rm.rm_config.spring.RmConfigBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>router-config.xml</title>
 
       <para><filename>resources/config-metadata/router-config.xml</filename>
@@ -533,15 +533,15 @@
       entries, the value of the <sgmltag class="attribute">class</sgmltag>
       attribute in the <sgmltag class="element">bean</sgmltag> element is:
       <classname>org.objectweb.celtix.routing.configuration.spring.ConfigurationBean</classname>.</para>
-    </section>
+    </simplesect>
 
-    <section>
+    <simplesect>
       <title>service-config.xml</title>
 
       <para><filename>resources/config-metadata/service-config.xml</filename>
       is a placeholder for future service level configuration settings. It
       currently has no content.</para>
-    </section>
+    </simplesect>
   </section>
 
   <section>
@@ -1339,8 +1339,8 @@
     write a CeltiXfire configuration file, this example will show you how to
     direct your application to use the configuration file.</para>
 
-    <section>
-      <title>The Application Code</title>
+    <simplesect>
+      <title>The application code</title>
 
       <para>For this example, you build on the hello_world product demo. You
       need to perform the following steps:</para>
@@ -1405,10 +1405,10 @@
           the server and the invocation requests will fail.</para>
         </step>
       </procedure>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>The Configuration File</title>
+    <simplesect>
+      <title>The configuration file</title>
 
       <procedure>
         <step>
@@ -1499,10 +1499,10 @@
           server mainline have the same URL.</para>
         </step>
       </procedure>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Running the Example</title>
+    <simplesect>
+      <title>Running the example</title>
 
       <procedure>
         <step>
@@ -1548,6 +1548,6 @@
 &lt;/target&gt;</programlisting>
         </step>
       </procedure>
-    </section>
+    </simplesect>
   </section>
 </article>

Modified: incubator/cxf/trunk/docs/src/docs/guides/develop_consumer.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/guides/develop_consumer.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/guides/develop_consumer.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/guides/develop_consumer.xml Wed Sep  6 14:17:39 2006
@@ -54,7 +54,7 @@
       </listitem>
     </itemizedlist>
 
-    <section>
+    <simplesect>
       <title>Basic HelloWorld WSDL contract</title>
 
       <para><xref linkend="Table3" /> shows the HelloWorld WSDL contract. This
@@ -218,10 +218,10 @@
       CeltiXfire wsdl2soap or wsdl2xml utilities. Likewise, the SOAPService
       service can be generated automatically by running the CeltiXfire
       wsdl2service utility.</para>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Generating the Stub Code</title>
+    <simplesect>
+      <title>Generating the stub code</title>
 
       <para>After defining the WSDL contract, you can generate client code
       using the CeltiXfire wsdl2java utility. Enter the following command at a
@@ -306,7 +306,7 @@
           model.</para>
         </listitem>
       </itemizedlist>
-    </section>
+    </simplesect>
   </section>
 
   <section>
@@ -328,8 +328,8 @@
       </listitem>
     </itemizedlist>
 
-    <section>
-      <title>Generated Service Class</title>
+    <simplesect>
+      <title>Generated service class</title>
 
       <para><xref linkend="Table2" /> shows the typical outline a generated
       service class, <classname>ServiceName</classname>, which extends the
@@ -394,10 +394,10 @@
           methods.</para>
         </listitem>
       </itemizedlist>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Service Endpoint Interface</title>
+    <simplesect>
+      <title>Service endpoint interface</title>
 
       <para>For every port type defined in the original WSDL contract, you can
       generate a corresponding service endpoint interface in Java. A service
@@ -446,10 +446,10 @@
   public void pingMe() throws PingMeFault;
 }</programlisting>
       </example>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Client Main Function</title>
+    <simplesect>
+      <title>Client main function</title>
 
       <para><xref linkend="Table1" /> shows the Java code that implements the
       HelloWorld client. In summary, the client connects to the SoapPort port
@@ -480,7 +480,7 @@
   public static void main(String args[]) throws Exception
   {
     if (args.length == 0)
-	{
+    {
       System.out.println("please specify wsdl");
       System.exit(1);
     }
@@ -488,11 +488,11 @@
     URL wsdlURL;
     File wsdlFile = new File(args[0]);
     if (wsdlFile.exists())
-	{
+    {
       wsdlURL = wsdlFile.toURL();
     }
-	else
-	{
+    else
+    {
       wsdlURL = new URL(args[0]);
     }
 
@@ -573,7 +573,7 @@
           <classname>PingMeFault</classname> fault exception.</para>
         </listitem>
       </orderedlist>
-    </section>
+    </simplesect>
   </section>
 
   <section>
@@ -607,8 +607,8 @@
       </listitem>
     </itemizedlist>
 
-    <section>
-      <title>Setting a Request Context</title>
+    <simplesect>
+      <title>Setting a request context</title>
 
       <para>To set a particular request context property,
       <replaceable>ContextPropertyName</replaceable>, to the value,
@@ -634,10 +634,10 @@
       hash map that has keys of <type>String</type> and values of arbitrary
       type. Use <methodname>java.util.Map.put()</methodname> to create a new
       entry in the hash map.</para>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Reading a Response Context</title>
+    <simplesect>
+      <title>Reading a response context</title>
 
       <para>To retrieve a particular response context property,
       <replaceable>ContextPropertyName</replaceable>, use the code shown in
@@ -660,10 +660,10 @@
       hash map that has keys <type>String</type> and values of arbitrary type.
       Use <methodname>java.util.Map.get()</methodname> to access an entry in
       the hash map of response context properties.</para>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Contexts Supported by CeltiXfire</title>
+    <simplesect>
+      <title>Supported contexts</title>
 
       <para>CeltiXfire supports the following context properties:</para>
 
@@ -688,7 +688,7 @@
           </tbody>
         </tgroup>
       </table>
-    </section>
+    </simplesect>
   </section>
 
   <section>
@@ -722,8 +722,8 @@
     <para>Both of these asynchronous invocation approaches are described here
     and illustrated by code examples.</para>
 
-    <section>
-      <title>WSDL Contract for Asynchronous Example</title>
+    <simplesect>
+      <title>Contract for asynchronous example</title>
 
       <para><xref linkend="async1" /> shows the WSDL contract that is used for
       the asynchronous example. The contract defines a single port type,
@@ -744,8 +744,8 @@
   &lt;wsdl:types&gt;
     &lt;schema targetNamespace="http://objectweb.org/hello_world_async_soap_http/types"
             xmlns="http://www.w3.org/2001/XMLSchema"
-			xmlns:x1="http://objectweb.org/hello_world_async_soap_http/types"
-			elementFormDefault="qualified"&gt;
+            xmlns:x1="http://objectweb.org/hello_world_async_soap_http/types"
+            elementFormDefault="qualified"&gt;
       &lt;element name="greetMeSometime"&gt;
         &lt;complexType&gt;
           &lt;sequence&gt;
@@ -788,10 +788,10 @@
   &lt;/wsdl:service&gt;
 &lt;/wsdl:definitions&gt;</programlisting>
       </example>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Generating the Asynchronous Stub Code</title>
+    <simplesect>
+      <title>Generating the asynchronous stub code</title>
 
       <para>The asynchronous style of invocation requires extra stub code (for
       example, dedicated asychronous methods defined on the service endpoint
@@ -928,11 +928,11 @@
 
       <para>The details of the callback approach and the polling approach are
       discussed in the following subsections.</para>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Implementing an Asynchronous Client with the Polling
-      Approach</title>
+    <simplesect>
+      <title>Implementing an asynchronous client with the polling
+      approach</title>
 
       <para><xref linkend="async4" /> illustrates the polling approach to
       making an asynchronous operation call. Using this approach, the client
@@ -1022,11 +1022,11 @@
   );</programlisting>
         </listitem>
       </itemizedlist>
-    </section>
+    </simplesect>
 
-    <section>
-      <title>Implementing an Asynchronous Client with the Callback
-      Approach</title>
+    <simplesect>
+      <title>Implementing an asynchronous client with the callback
+      approach</title>
 
       <para>An alternative approach to making an asynchronous operation
       invocation is to implement a callback class, by deriving from the
@@ -1139,6 +1139,6 @@
       <methodname>response.isDone()</methodname>. The value of the response is
       only made available to the callback object,
       <classname>testAsyncHandler</classname>.</para>
-    </section>
+    </simplesect>
   </section>
 </article>

Modified: incubator/cxf/trunk/docs/src/docs/guides/getting_started.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/guides/getting_started.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/guides/getting_started.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/guides/getting_started.xml Wed Sep  6 14:17:39 2006
@@ -130,7 +130,7 @@
       </listitem>
     </itemizedlist>
 
-    <section id="using_eclipse">
+    <simplesect id="using_eclipse">
       <title>Using CeltiXfire with Eclipse</title>
 
       <para>Eclipse provides an excellent Java IDE for CeltiXfire development.
@@ -197,9 +197,9 @@
       <para>After you have created a user library for CeltiXfire, you can add
       it to the Java project build path and Eclipse will auto-compile your
       code.</para>
-    </section>
+    </simplesect>
 
-    <section id="using_ant">
+    <simplesect id="using_ant">
       <title>Using CeltiXfire with Ant</title>
 
       <para>Many Java developers use the Apache Ant build system. It is
@@ -275,7 +275,7 @@
       applications are useful models for building applications using a
       directory structure similar to that used by the CeltiXfire
       samples.</para>
-    </section>
+    </simplesect>
   </section>
 
   <section>

Modified: incubator/cxf/trunk/docs/src/docs/guides/jms.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/guides/jms.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/guides/jms.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/guides/jms.xml Wed Sep  6 14:17:39 2006
@@ -98,8 +98,8 @@
       class="element">jms:JMSNamingProperties</sgmltag> element specifies the
       Java properties used to connect to the JNDI service.</para>
 
-      <section>
-        <title>The address Element</title>
+      <simplesect>
+        <title>The <sgmltag class="element">address</sgmltag> element</title>
 
         <para>The basic configuration for a JMS endpoint is done by using a
         <sgmltag class="element">jms:address</sgmltag> element as the child of
@@ -172,10 +172,10 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
 
-      <section>
-        <title>The JMSNamingProperties Element</title>
+      <simplesect>
+        <title>The <sgmltag class="element">JMSNamingProperties</sgmltag> element</title>
 
         <para>To increase interoperability with JMS and JNDI providers, the
         <sgmltag class="element">jms:address</sgmltag> element has a child
@@ -259,10 +259,10 @@
         <para>For more details on what information to use in these attributes,
         check your JNDI provider’s documentation and consult the Java API
         reference material.</para>
-      </section>
+      </simplesect>
 
-      <section id="ReplyDest">
-        <title>Using a Named Reply Destination</title>
+      <simplesect id="ReplyDest">
+        <title>Using a named reply destination</title>
 
         <para>By default, CeltiXfire endpoints using JMS create a temporary
         queue for sending replies back and forth. You can change this behavior
@@ -276,9 +276,9 @@
         attribute as the location for placing replies if there is no
         destination specified in the request’s <classname>ReplyTo</classname>
         field.</para>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Example</title>
 
         <para><xref linkend="Table3" /> shows an example of an CeltiXfire JMS
@@ -299,7 +299,7 @@
   &lt;/port&gt;
 &lt;/service&gt;</programlisting>
         </example>
-      </section>
+      </simplesect>
     </section>
 
     <section id="BasicConfig">
@@ -309,7 +309,8 @@
       information for a JMS endpoint, you can supply it in the endpoint's
       configuration file. The information in the configuration file will
       override the information in the endpoint's WSDL file.</para>
-
+<simplesect>
+<title>The <classname>jmsAddress</classname> property</title>
       <para>JMS connection information is specified using the
       <classname>jmsAddress</classname> property. The
       <classname>jmsAddress</classname> property has a single value:
@@ -326,8 +327,8 @@
       <para>The <classname>jmsAddress</classname> property can be specified in
       either the client configuration bean or the service configuration
       bean.</para>
-
-      <section>
+</simplesect>
+      <simplesect>
         <title>Example</title>
 
         <para><xref linkend="Table9" /> shows a CeltiXfire configuration entry
@@ -360,15 +361,15 @@
 ...
 &lt;/beans&gt;</programlisting>
         </example>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>More information</title>
 
         <para>For more information on using CeltiXfire configuration see the
         <ulink url="site:config">CeltiXfire Configuration
         Guide</ulink>.</para>
-      </section>
+      </simplesect>
     </section>
   </section>
 
@@ -421,7 +422,8 @@
 
     <section id="ConsumerConfig">
       <title>Using CeltiXfire Configuration</title>
-
+<simplesect>
+<title>Specifying the configuration data</title>
       <para>Consumer endpoint configuration is specified using the
       <classname>org.objectweb.celtix.bus.transports.jms.jms_client_config.spring.JMSClientConfigBean</classname>
       class for the configuration bean. Using this configuration bean, you
@@ -446,8 +448,8 @@
           </tbody>
         </tgroup>
       </table>
-
-      <section>
+</simplesect>
+      <simplesect>
         <title>Example</title>
 
         <para><xref linkend="Table8" /> shows a CeltiXfire configuration entry
@@ -470,9 +472,9 @@
 ...
 &lt;/beans&gt;</programlisting>
         </example>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Adding address information</title>
 
         <para>In addition to specifying the <classname>jmsClient</classname>
@@ -480,15 +482,15 @@
         consumer for contacting a service endpoint. This is done by adding the
         <classname>jmsAddress</classname> property to the consumer endpoint's
         configuration bean.</para>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>More information</title>
 
         <para>For more information on using CeltiXfire configuration see the
         <ulink url="site:config">CeltiXfire Configuration
         Guide</ulink>.</para>
-      </section>
+      </simplesect>
     </section>
 
     <section id="ConsumerWSDL">
@@ -559,7 +561,8 @@
 
     <section id="ServiceConfig">
       <title>Using CeltiXfire Configuration</title>
-
+<simplesect>
+<title>Specifying configuration data</title>
       <para>Service endpoint configuration is specified using the
       <classname>org.objectweb.celtix.bus.transports.jms.jms_server_config.spring.JMSServerConfigBean</classname>
       class for the configuration bean. Using this configuration bean, you
@@ -615,8 +618,8 @@
           </tbody>
         </tgroup>
       </table>
-
-      <section>
+</simplesect>
+      <simplesect>
         <title>Example</title>
 
         <para><xref linkend="Table11" /> shows a CeltiXfire configuration
@@ -642,24 +645,24 @@
 ...
 &lt;/beans&gt;</programlisting>
         </example>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Adding address information</title>
 
         <para>In addition to specifying the <classname>jmsServer</classname>
         property, you can also specify the contact information of the service
         endpoint. This is done by adding the <classname>jmsAddress</classname>
         property to the service endpoint's configuration bean.</para>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>More information</title>
 
         <para>For more information on using CeltiXfire configuration see the
         <ulink url="site:config">CeltiXfire Configuration
         Guide</ulink>.</para>
-      </section>
+      </simplesect>
     </section>
 
     <section id="ServiceWSDL">
@@ -738,7 +741,7 @@
       response context. In addition, you can see how long the client will wait
       for a response before timing out.</para>
 
-      <section>
+      <simplesect>
         <title>JMS Header Properties</title>
 
         <para>The JMS properties table lists the properties in the JMS header
@@ -845,9 +848,9 @@
         optional properties are returned as a <classname>List</classname> of
         <classname>JMSPropertyType</classname>. Optional properties are stored
         as name/value pairs.</para>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Example</title>
 
         <para><xref linkend="Table13" /> shows code for inspecting some of the
@@ -908,7 +911,7 @@
             <para>Prints some of the message header properties.</para>
           </listitem>
         </orderedlist>
-      </section>
+      </simplesect>
     </section>
 
     <section>
@@ -920,7 +923,8 @@
       will need to reset them each time you invoke an operation on the service
       proxy.</para>
 
-      <para>JMS Header Properties</para>
+<simplesect>
+      <title>JMS Header Properties</title>
 
       <para><xref linkend="Table14" /> lists the properties in the JMS header
       that you can set using the consumer endpoint's request context.</para>
@@ -989,8 +993,8 @@
           argument.</para>
         </step>
       </procedure>
-
-      <section>
+</simplesect>
+      <simplesect>
         <title>Optional JMS Header Properties</title>
 
         <para>You can also set optional properties into the JMS header.
@@ -1027,9 +1031,9 @@
             been added to the message header.</para>
           </step>
         </procedure>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Client Receive Timeout</title>
 
         <para>In addition to the JMS header properties, you can set the amount
@@ -1040,9 +1044,9 @@
         argument and a <type>long</type> representing the amount of time in
         milliseconds that you want to consumer to wait as the second
         argument.</para>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Example</title>
 
         <para><xref linkend="settingProps" /> shows code for setting some of
@@ -1131,7 +1135,7 @@
             <para>Sets the client receive timeout property to 1 second.</para>
           </listitem>
         </orderedlist>
-      </section>
+      </simplesect>
     </section>
   </section>
 </article>

Modified: incubator/cxf/trunk/docs/src/docs/guides/management.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/guides/management.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/guides/management.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/guides/management.xml Wed Sep  6 14:17:39 2006
@@ -197,7 +197,7 @@
       It also manages the flow of messages between the network and the
       WorkQueue that is responsible for processing the message.</para>
 
-      <section>
+      <simplesect>
         <title>Attributes</title>
 
         <para><xref linkend="Table2" /> lists the managed attributes for the
@@ -255,7 +255,7 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
     </section>
 
     <section id="workqueue">
@@ -265,7 +265,7 @@
       servants implementing the service's business logic. It instantiates
       servants and passes data to and from them.</para>
 
-      <section>
+      <simplesect>
         <title>Attributes</title>
 
         <para><xref linkend="Table3" /> lists the managed attributes for the
@@ -355,7 +355,7 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
     </section>
 
     <section id="wsdlmgr">
@@ -364,7 +364,7 @@
       <para>The WSDLManager component provides a WSDL registry and a numer of
       methods to retrieve WSDL.</para>
 
-      <section>
+      <simplesect>
         <title>Attributes</title>
 
         <para><xref linkend="Table4" /> lists the managed attributes for the
@@ -427,9 +427,9 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Operations</title>
 
         <para><xref linkend="Table5" /> lists the operations supported by the
@@ -469,7 +469,7 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
     </section>
 
     <section id="endpt">
@@ -479,7 +479,7 @@
       the CeltiXfire runtime. It allows you to monitor and control the state
       of an endpoint based on its service name and port name.</para>
 
-      <section>
+      <simplesect>
         <title>Attributes</title>
 
         <para><xref linkend="Table6" /> lists the managed attributes for the
@@ -552,9 +552,9 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Operations</title>
 
         <para><xref linkend="Table7" /> lists the operations provided by the
@@ -599,7 +599,7 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
     </section>
 
     <section id="http">
@@ -609,7 +609,7 @@
       component receives an HTTP address to instantiate. It provides a logical
       view of the HTTP transport for the service side.</para>
 
-      <section>
+      <simplesect>
         <title>Attributes</title>
 
         <para><xref linkend="Table8" /> lists the managed attributes for the
@@ -704,7 +704,7 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
     </section>
 
     <section id="jms">
@@ -714,7 +714,7 @@
       receives a JMS address to instantiate. It provides a logical view of the
       JMS transport for the service side.</para>
 
-      <section>
+      <simplesect>
         <title>Attributes</title>
 
         <para><xref linkend="Table9" /> lists the managed attributes for the
@@ -809,7 +809,7 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
+      </simplesect>
     </section>
   </section>
 
@@ -853,7 +853,7 @@
       be accessible through the same JMX connection as the CeltiXfire internal
       components used by your service.</para>
 
-      <section>
+      <simplesect>
         <title>Creating your custom MBean</title>
 
         <para>When you use the JMX APIs to instrument your service
@@ -931,9 +931,9 @@
   }
 }</programlisting>
         </example>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>Registering the MBean</title>
 
         <para>For your MBean to be exposed to a management console, it must be
@@ -1000,7 +1000,7 @@
 mbserver.registerMBean(sName, name);
 ...</programlisting>
         </example>
-      </section>
+      </simplesect>
     </section>
 
     <section id="celtix">
@@ -1043,8 +1043,8 @@
         </step>
       </procedure>
 
-      <section id="writeclass">
-        <title>Implementing the Instrumentation Class</title>
+      <simplesect id="writeclass">
+        <title>Implementing the instrumentation class</title>
 
         <para>Like an MBean a CeltiXfire instrumentation class is responsible
         for providing access to the attributes you want to track and implement
@@ -1333,9 +1333,9 @@
   }
 }</programlisting>
         </example>
-      </section>
+      </simplesect>
 
-      <section id="activate">
+      <simplesect id="activate">
         <title>Activating your custom instrumentation</title>
 
         <para>To make your custom instrumentation available to management
@@ -1381,9 +1381,9 @@
 InstrumentationManager im = bus.getInstrumentationManager();
 im.register(in);</programlisting>
         </example>
-      </section>
+      </simplesect>
 
-      <section id="deactivate">
+      <simplesect id="deactivate">
         <title>Deactivating your custom instrumentation</title>
 
         <para>Unlike MBeans created using the JMX APIs, CeltiXfire
@@ -1407,7 +1407,7 @@
 InstrumentationManager im = bus.getInstrumentationManager();
 im.unregister(in);</programlisting>
         </example>
-      </section>
+      </simplesect>
     </section>
   </section>
 
@@ -1437,7 +1437,7 @@
 
     <programlisting>xmlns:im="http://celtix.objectweb.org/bus/instrumentation"</programlisting>
 
-    <section id="instrumentcontrol">
+    <simplesect id="instrumentcontrol">
       <title>Configuring the instrumentation event listeners</title>
 
       <para><xref linkend="Table12" /> lists the values for the
@@ -1472,9 +1472,9 @@
           </tbody>
         </tgroup>
       </table>
-    </section>
+    </simplesect>
 
-    <section id="mbserver">
+    <simplesect id="mbserver">
       <title>Configuring the MBean server</title>
 
       <para><xref linkend="Table13" /> lists the values for the
@@ -1533,7 +1533,7 @@
 
       <para>For more information on configuring CeltiXfire see the <ulink
       url="site:config">CeltiXfire Configuration Guide</ulink>.</para>
-    </section>
+    </simplesect>
   </section>
 
   <section>

Modified: incubator/cxf/trunk/docs/src/docs/guides/tomcat_deploy.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/guides/tomcat_deploy.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/guides/tomcat_deploy.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/guides/tomcat_deploy.xml Wed Sep  6 14:17:39 2006
@@ -106,7 +106,7 @@
       configuration information specific to the CeltiXfire Web service
       endpoint.</para>
 
-      <section>
+      <simplesect>
         <title>The web.xml File</title>
 
         <para>Although this file contains the standard servlet configuration
@@ -146,9 +146,9 @@
         <para>Also note the <sgmltag class="element">url-pattern</sgmltag>
         entry <literal>/celtix/*</literal>. This will become part the the URL
         that client applications use to invoke on the Web service.</para>
-      </section>
+      </simplesect>
 
-      <section>
+      <simplesect>
         <title>The celtix-servlet.xml File</title>
 
         <para>This file contains content specific to the cXf Web service
@@ -190,7 +190,7 @@
         multiple CeltiXfire Web service endpoints into the same Tomcat
         instance, you can simply add additional <sgmltag
         class="element">endpoint</sgmltag> elements to this XML file.</para>
-      </section>
+      </simplesect>
     </section>
   </section>
 
@@ -308,8 +308,8 @@
       subdirectory (<filename class="directory">webapps/helloworld</filename>)
       holding one of the hello_world deployed applications.</para>
 
-      <section>
-        <title>Removing Unneeded Application Files</title>
+      <simplesect>
+        <title>Removing unneeded application files</title>
 
         <para>Under the <filename
         class="directory">webapps/helloworld/WEB-INF/classes/demo/hw</filename>
@@ -322,15 +322,15 @@
         <filename>Server.class</filename> file from the <filename
         class="directory">webapps/helloworldrpclit/WEB-INF/classes/demo/hwRPCLit/server</filename>
         subdirectory.</para>
-      </section>
+      </simplesect>
 
-      <section>
-        <title>Removing Unneeded CeltiXfire JAR Files</title>
+      <simplesect>
+        <title>Removing unneeded CeltiXfire JAR files</title>
 
         <para>Delete the following JAR files from the <filename
         class="directory">webapps/helloworld/WEB-INF/lib</filename> directory:
         (REVISIT at v1.0 GA.)</para>
-      </section>
+      </simplesect>
     </section>
 
     <section>

Modified: incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml Wed Sep  6 14:17:39 2006
@@ -100,7 +100,7 @@
       </listitem>
     </itemizedlist>
 
-    <section id="caution">
+    <simplesect id="caution">
       <title>Cautions</title>
 
       <para>Cautions are intended for use when a <link
@@ -113,9 +113,9 @@
       class="element">caution</sgmltag> element. As with warnings elements,
       the <sgmltag class="element">caution</sgmltag> element should contain
       only a single <sgmltag class="element">para</sgmltag> element.</para>
-    </section>
+    </simplesect>
 
-    <section id="important">
+    <simplesect id="important">
       <title>Important Notes</title>
 
       <para>Important notes are used to point out information that is
@@ -129,9 +129,9 @@
       class="element">important</sgmltag> element should contain only a single
       <sgmltag class="element">para</sgmltag> element. However, it is
       allowable to use other block elements in an important note.</para>
-    </section>
+    </simplesect>
 
-    <section id="tip">
+    <simplesect id="tip">
       <title>Tips</title>
 
       <para>Tips are bits of information that may help a user be more
@@ -144,7 +144,7 @@
       class="element">tip</sgmltag> element should contain only a single
       <sgmltag class="element">para</sgmltag> element. However, it is
       allowable to use other block elements in a tip.</para>
-    </section>
+    </simplesect>
   </section>
 
   <section>

Modified: incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml Wed Sep  6 14:17:39 2006
@@ -931,4 +931,4 @@
         </para>
       </listitem>
     </itemizedlist>
- </chapter>
\ No newline at end of file
+</chapter>
\ No newline at end of file

Modified: incubator/cxf/trunk/docs/src/docs/styleguide/lists.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/styleguide/lists.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/lists.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/lists.xml Wed Sep  6 14:17:39 2006
@@ -8,7 +8,7 @@
     simple, in-line tags, and therefore cannot contain sublists, examples,
     code listings or multiple paragraphs. Simple lists are rarely used in CeltiXfire (CXF)
     documentation.</para>
-    <section>
+    <simplesect>
       <title>Specifying a simple list</title>
       <para>A simple list is specified by a <sgmltag class="element">simplelist</sgmltag> element. 
    <sgmltag class="element">simplelist</sgmltag> has two optional attributes:</para>
@@ -42,8 +42,8 @@
       </table>
       <para>The elements of a simple list are specified using a <sgmltag class="element">member</sgmltag> element. The contents of each <sgmltag>member</sgmltag> element can only contain character data and
       inline elements.</para>
-    </section>
-    <section>
+    </simplesect>
+    <simplesect>
       <title>Example</title>
       <para><xref linkend="simpmarkup"/> shows the markup for a simple
       list.</para>
@@ -56,7 +56,7 @@
   &lt;member&gt;Gummy Bears&lt;/member&gt;
 &lt;/simplelist&gt;</programlisting>
       </example>
-    </section>
+    </simplesect>
   </section>
   <section>
     <title>Itemized Lists</title>
@@ -64,8 +64,8 @@
     the list does not matter. They are like bulleted lists or the lists that
     are created by the <sgmltag class="element">ul</sgmltag> tag in
     HTML.</para>
-    <section>
-      <title>Specifying an Itemized List</title>
+    <simplesect>
+      <title>Specifying an itemized list</title>
       <para>An itemized list is specified by an <sgmltag class="element">itemizedlist</sgmltag> element. You can specify an
       <sgmltag class="attribute">id</sgmltag> attribute for itemized lists. If
       the list is going to referenced by an <sgmltag class="element">xref</sgmltag> element, you should also specify a value
@@ -73,8 +73,8 @@
       <para>Each item in an itemized list is specified by a <sgmltag class="element">listitem</sgmltag> element. The <sgmltag class="element">listitem</sgmltag> element is a wrapper element and can
       contain any container elements such as a <sgmltag class="element">para</sgmltag> element. All content within a <sgmltag class="element">listitem</sgmltag> element will be indented to the same
       level. You can also specify sub-lists within a <sgmltag class="element">listitem</sgmltag> element.</para>
-    </section>
-    <section>
+    </simplesect>
+    <simplesect>
       <title>Example</title>
       <para><xref linkend="itemmarkup"/> shows the markup for an itemized
       list.</para>
@@ -97,7 +97,7 @@
   &lt;/listitem&gt;
 &lt;/itemizedlist&gt;</programlisting>
       </example>
-    </section>
+    </simplesect>
   </section>
   <section>
     <title>Ordered List</title>
@@ -105,8 +105,8 @@
     important and made explicit. They are like numbered lists and lists that
     are created using the <sgmltag class="element">ol</sgmltag> tag in
     HTML.</para>
-    <section>
-      <title>Specifying an Ordered List</title>
+    <simplesect>
+      <title>Specifying an ordered list</title>
       <para>Ordered lists are specified by an <sgmltag class="element">orderedlist</sgmltag> element. In addition to the
       <sgmltag class="attribute">id</sgmltag> attribute and <sgmltag class="attribute">xreflabel</sgmltag> attribute, <sgmltag class="element">orderedlist</sgmltag> elements have three optional
       elements.</para>
@@ -148,7 +148,7 @@
       <para>Items in an ordered list are specified using a <sgmltag class="element">listitem</sgmltag> element. The <sgmltag class="element">listitem</sgmltag> element is a wrapper element and can
       contain any container elements such as a <sgmltag class="element">para</sgmltag> element. All content within a <sgmltag class="element">listitem</sgmltag> element will be indented to the same
       level. You can also specify sub-lists within a <sgmltag class="element">listitem</sgmltag> element.</para>
-    </section>
+    </simplesect>
   </section>
   <section>
     <title>Segmented Lists</title>
@@ -191,19 +191,19 @@
       supply a title for a variable list by adding a <sgmltag class="element">title</sgmltag> element as the <sgmltag class="element">variablelist</sgmltag> element&apos;s first child.</para>
       <para>The items in a variable list are specified using a <sgmltag class="element">varlistentry</sgmltag> element. The <sgmltag class="element">varlistentry</sgmltag> element has two children elements
       that specify the contents of the item: <sgmltag class="element">term</sgmltag> and <sgmltag class="element">listitem</sgmltag>.</para>
-      <section>
+      <simplesect>
         <title>Specifying terms</title>
         <para>You can specify one or more <sgmltag class="element">term</sgmltag> elements in a <sgmltag class="element">varlistentry</sgmltag> element. Each <sgmltag class="element">term</sgmltag> element can contain text and inline
         markup elements. Each <sgmltag class="element">term</sgmltag> element
         should contain a single term or phrase that the list item
         describes.</para>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title>Describing a term</title>
         <para>You describe the term, or terms, defined by the <sgmltag class="element">term</sgmltag> elements using a single <sgmltag class="element">listitem</sgmltag> element. The <sgmltag class="element">listitem</sgmltag> element is a wrapper element and
         can contain any container elements such as a <sgmltag class="element">para</sgmltag> element. All content within a <sgmltag class="element">listitem</sgmltag> element will be indented to the
         same level. You can also specify sub-lists within a <sgmltag class="element">listitem</sgmltag> element.</para>
-      </section>
+      </simplesect>
     </section>
     <section>
       <title>Example</title>
@@ -280,8 +280,8 @@
       <para>The entries in a glossary list are specified using a <sgmltag class="element">glossentry</sgmltag> element. The <sgmltag class="element">glossentry</sgmltag> element typically has two children:
       <sgmltag class="element">glossterm</sgmltag> and <sgmltag class="element">glossdef</sgmltag>. You can also use the <sgmltag class="element">glosssee</sgmltag> element to xref with other
       definitions.</para>
-      <section>
-        <title>Specifying a Term</title>
+      <simplesect>
+        <title>Specifying a term</title>
         <para>A <sgmltag class="element">glossentry</sgmltag> element can have
         only one <sgmltag class="element">glossterm</sgmltag> element. This
         element specifies the term being defined by this entry. If you are
@@ -292,9 +292,9 @@
           also be used in text entries to refer to terms defined in a glossary
           entry. When used in this manner, you supply a value for the <sgmltag class="attribute">linkend</sgmltag> attribute.</para>
         </note>
-      </section>
-      <section>
-        <title>Defining a Term</title>
+      </simplesect>
+      <simplesect>
+        <title>Defining a term</title>
         <para>You define a term using either one or more <sgmltag class="element">glossdef</sgmltag> elements or a <sgmltag class="element">glosssee</sgmltag> element. The <sgmltag class="element">glossdef</sgmltag> element is a content element that
         contains markup specifying a definition. If you use more than one
         <sgmltag class="element">glossdef</sgmltag> element, they are treated
@@ -303,7 +303,7 @@
         redirects the reader to a term with the same meaning. It acts like a
         &quot;See&quot; entry in a dictionary. It has one attribute, <sgmltag class="attribute">otherterm</sgmltag>, whose value is the id of the
         term to which the reader is redirected.</para>
-      </section>
+      </simplesect>
     </section>
     <section>
       <title>Example</title>

Modified: incubator/cxf/trunk/docs/src/docs/styleguide/overview.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/styleguide/overview.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/overview.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/overview.xml Wed Sep  6 14:17:39 2006
@@ -1,129 +1,171 @@
-<?xml version='1.0' encoding='UTF-8'?>
+<?xml version="1.0" encoding="UTF-8"?>
 <chapter id="overview">
   <title>Writing Documentation for CeltiXfire (CXF)</title>
+
   <section>
     <title>Why XML Based Documents?</title>
+
     <para>The easy answer is because XML is cool!! However, it does have some
     distinct advantages over other means of sourcing documentation:</para>
+
     <itemizedlist>
       <listitem>
         <para>It is stored as text files.</para>
       </listitem>
+
       <listitem>
         <para>It provides structure to a document.</para>
       </listitem>
+
       <listitem>
         <para>It is an easy way to single source documentation.</para>
       </listitem>
     </itemizedlist>
-    <section>
+
+    <simplesect>
       <title>Text vs. Binary</title>
+
       <para>Text files have a number of advantages over binary formats:</para>
+
       <itemizedlist>
         <listitem>
           <para>They tend to take up less space.</para>
         </listitem>
+
         <listitem>
           <para>They can be edited by a slew of freely available tools.</para>
         </listitem>
+
         <listitem>
           <para>They can be easily diffed when being committed to a
           repository.</para>
         </listitem>
+
         <listitem>
           <para>They are readable by both humans and machines.</para>
         </listitem>
       </itemizedlist>
-    </section>
-    <section>
+    </simplesect>
+
+    <simplesect>
       <title>Structure</title>
+
       <para>Writing documentation with a markup language may give writers
       visions of troff and LaTex. Unlike those markups, the XML tags used by
       both XDOC and DocBook are used to describe the structure of a document.
       It also provides tags to help identify different types of content with
       in your document.</para>
+
       <para>This means that it It makes no assumptions about the presentation
       of the content. Using a structured markup allows you to worry about
       creating and structuring your content.</para>
-    </section>
-    <section>
+    </simplesect>
+
+    <simplesect>
       <title>Single Source, Multiple Outputs</title>
-      <para>Formatting is handled by back end processing tools. CeltiXfire (CXF) uses
-      Apache Forrest to generate HTML and PDF versions of its content. There
-      are also a number of other tools, both open source and commercial, that
-      generate documentation from XML source. This means that all of the
-      writers can work on a consistent framework no matter what the eventual
-      output medium is going to be.</para>
+
+      <para>Formatting is handled by back end processing tools. CeltiXfire
+      (CXF) uses Apache Forrest to generate HTML and PDF versions of its
+      content. There are also a number of other tools, both open source and
+      commercial, that generate documentation from XML source. This means that
+      all of the writers can work on a consistent framework no matter what the
+      eventual output medium is going to be.</para>
+
       <para>Using these tools, you can completely customize the look of your
       documentation without needing to change the documentation source. If at
       some point in the future you decide to update the look and feel of your
       documentation, you simply update the stylesheets used to process the
       XML. The source content never needs to change.</para>
-    </section>
+    </simplesect>
   </section>
+
   <section>
     <title>General Guidelines</title>
-    <section>
+
+    <simplesect>
       <title>Types of XML Used</title>
+
       <para>Depending on the type of document you are writing you will use one
       of two types of XML:</para>
+
       <itemizedlist>
         <listitem>
           <para><ulink url="#FAQ">FAQs in XDOC</ulink></para>
         </listitem>
+
         <listitem>
-          <para><ulink url="#the_rest">Everything else in DocBook</ulink></para>
+          <para><ulink url="#the_rest">Everything else in
+          DocBook</ulink></para>
         </listitem>
       </itemizedlist>
-    </section>
-    <section>
+    </simplesect>
+
+    <simplesect>
       <title>Formatting the XML</title>
+
       <para>To make the source as readable as possible there are a few general
       guidelines to follow when writing CXF documentation:</para>
+
       <itemizedlist>
         <listitem>
           <para>Keep lines under 100 characters long so that they can be read
           easily.</para>
         </listitem>
+
         <listitem>
-          <para>Don&apos;t leave white space between elements.</para>
+          <para>Don't leave white space between elements.</para>
         </listitem>
+
         <listitem>
           <para>Use indenting to show the hierarchy.</para>
         </listitem>
       </itemizedlist>
-    </section>
+    </simplesect>
   </section>
+
   <section id="FAQ">
     <title>Writing FAQs</title>
-    <para>FAQs are written using Apache&apos;s xdoc format. This format was chosen
+
+    <para>FAQs are written using Apache's xdoc format. This format was chosen
     for its simplicity. You can find more information on the xdoc format used
-    for FAQs <ulink url="http://forrest.apache.org/dtdx/faq-v20.dtdx.html">here</ulink>.</para>
+    for FAQs <ulink
+    url="http://forrest.apache.org/dtdx/faq-v20.dtdx.html">here</ulink>.</para>
+
     <para>Depending on the complexity of the FAQ topic, you can include FAQ
     sections inside of an FAQ document. Typically, however, an FAQ should have
     fewer than 20 questions.</para>
+
     <para>When naming an FAQ you need to append <filename>-faq</filename> to
     the name of the file. For example, an FAQ about the CXF JAX-WS
     implementation could be called <filename>jaxws-faq.xml</filename>.</para>
   </section>
+
   <section id="the_rest">
     <title>Writing General Documentation</title>
-    <para>All other types of documentation are written using DocBook 4.2. DocBook 4.2
-    provides a structured, XML based grammar for writing complex technical
-    documentation. It is also an OASIS standard. This makes it a natural fit
-    for writing open source documentation.</para>
-    <para>The remainder of this style guide discusses how the CXF
-    project uses DocBook. For more general references and some help getting
-    familiar with DocBook, see the following:</para>
+
+    <para>All other types of documentation are written using DocBook 4.2.
+    DocBook 4.2 provides a structured, XML based grammar for writing complex
+    technical documentation. It is also an OASIS standard. This makes it a
+    natural fit for writing open source documentation.</para>
+
+    <para>The remainder of this style guide discusses how the CXF project uses
+    DocBook. For more general references and some help getting familiar with
+    DocBook, see the following:</para>
+
     <itemizedlist>
       <listitem>
         <para><ulink url="http://DocBook.org/">DocBook.org</ulink></para>
       </listitem>
+
       <listitem>
-        <para><ulink url="http://opensource.bureau-cornavin.com/crash-course/">The Crash Course to DocBook</ulink></para>
+        <para><ulink
+        url="http://opensource.bureau-cornavin.com/crash-course/">The Crash
+        Course to DocBook</ulink></para>
       </listitem>
+
       <listitem>
-        <para><ulink url="http://nwalsh.com/DocBook/">Norman Walsh&apos;s DocBook page</ulink></para>
+        <para><ulink url="http://nwalsh.com/DocBook/">Norman Walsh's DocBook
+        page</ulink></para>
       </listitem>
     </itemizedlist>
   </section>

Modified: incubator/cxf/trunk/docs/src/docs/styleguide/structure.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/styleguide/structure.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/structure.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/structure.xml Wed Sep  6 14:17:39 2006
@@ -1,66 +1,102 @@
-<?xml version='1.0' encoding='UTF-8'?>
+<?xml version="1.0" encoding="UTF-8"?>
 <chapter id="structure">
   <title>Structuring CeltiXfire (CXF) Documents</title>
+
   <section>
     <title>Top-level Elements</title>
+
     <para>Because we strive to keep individual documents as specific as
-    possible, CXF documents use the <sgmltag class="element">article</sgmltag> element as their root element. If you
-    are writing a document that you feel needs to be more than an article,
-    consider breaking the topic into smaller chunks. This does not mean you
-    cannot link to other documents, but documents should not have such a large
-    scope that they need to be more than an article.</para>
-    <para><xref linkend="topLevel"/> shows a sample CXF document.</para>
+    possible, CXF documents use the <sgmltag class="element">article</sgmltag>
+    element as their root element. If you are writing a document that you feel
+    needs to be more than an article, consider breaking the topic into smaller
+    chunks. This does not mean you cannot link to other documents, but
+    documents should not have such a large scope that they need to be more
+    than an article.</para>
+
+    <para><xref linkend="topLevel" /> shows a sample CXF document.</para>
+
     <example id="topLevel">
       <title>High-level View of a CXF Document</title>
-      <programlisting>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;!DOCTYPE article PUBLIC &quot;-//OASIS//DTD DocBook XML V4.2//EN&quot;
-&quot;http://www.oasis-open.org/DocBook/xml/4.2/DocBookx.dtd&quot;&gt;
-&lt;article lang=&quot;en-US&quot;&gt;
+
+      <programlisting>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/DocBook/xml/4.2/DocBookx.dtd"&gt;
+&lt;article lang="en-US"&gt;
   &lt;title&gt;Developing a Consumer with CeltiXfire&lt;/title&gt;
 ...
 &lt;/article&gt;</programlisting>
     </example>
   </section>
+
   <section>
     <title>Attributions</title>
+
     <para>CXF documents do not not use the attribution elements.</para>
   </section>
+
   <section>
-    <title>Sections</title>
-    <para>CXF documents are broken into sections. Generally, a document
-    should have five or fewer sections. If you need more sections, it may be
-    because the topic for your document is too broad or you need to reconsider
-    how you are chunking the information. Top level sections are denoted using
-    <sgmltag class="element">section</sgmltag> elements.</para>
-    <para>Top-level sections can be broken down into five or fewer subsections.
-    Subsections are denoted using <sgmltag class="element">section</sgmltag>
-    elements.</para>
-    <para>Like top-level sections, subsections can be broken up into five or fewer
-    block-sections. Block-sections are denoted using <sgmltag class="element">section</sgmltag> elements. Block-sections cannot be
-    subdivided.</para>
-    <para>While it is considered good practice to supply a descriptive value
-    for the <sgmltag class="attribute">id</sgmltag> attribute, it is not
-    required.</para>
-    <para>shows a more detailed view of a CeltiXfire document.</para>
-    <example id="sectLevel">
-      <title>Detailed View of a CXF Document</title>
-      <programlisting>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;!DOCTYPE article PUBLIC &quot;-//OASIS//DTD DocBook XML V4.2//EN&quot;
-&quot;http://www.oasis-open.org/DocBook/xml/4.2/DocBookx.dtd&quot;&gt;
-&lt;article lang=&quot;en-US&quot;&gt;
+    <title>Structural Elements</title>
+
+    <para>CXF documents are broken into sections and blocks.</para>
+
+    <simplesect>
+      <title>Sections</title>
+
+      <para>Generally, a document should have five or fewer sections. If you
+      need more sections, it may be because the topic for your document is too
+      broad or you need to reconsider how you are chunking the information.
+      Top level sections are denoted using <sgmltag
+      class="element">section</sgmltag> elements.</para>
+
+      <para>Top-level sections can be broken down into five or fewer
+      subsections. Subsections are also denoted using <sgmltag
+      class="element">section</sgmltag> elements.</para>
+    </simplesect>
+
+    <simplesect>
+      <title>Blocks</title>
+
+      <para>Block are the smallest structural unit of organization in a
+      CeltiXfire document. They divide up the information in a section into
+      managebale chunks of information. There should be no more than five
+      block-sections in a section.</para>
+
+      <para>Block-sections are denoted using <sgmltag
+      class="element">simplesect</sgmltag> elements. Block-sections cannot be
+      subdivided.</para>
+    </simplesect>
+
+    <simplesect>
+      <title>Example</title>
+
+      <para><xref linkend="sectLevel" /> shows a more detailed view of a
+      CeltiXfire document.</para>
+
+      <example id="sectLevel">
+        <title>Detailed View of a CXF Document</title>
+
+        <programlisting>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/DocBook/xml/4.2/DocBookx.dtd"&gt;
+&lt;article lang="en-US"&gt;
   &lt;title&gt;Developing a Consumer with CXF&lt;/title&gt;
-  &lt;section id=&quot;stubGen&quot;&gt;
+  &lt;section id="stubGen"&gt;
     &lt;title&gt;Generating Stub Code&lt;/title&gt;
     ...
   &lt;/section&gt;
-  &lt;section id=&quot;...&quot;&gt;
+  &lt;section id="..."&gt;
     ...
-    &lt;section id=&quot;subsection&quot;&gt;
+    &lt;section id="subsection"&gt;
       &lt;title&gt;Sample Subsection&lt;/title&gt;
       ...
+      &lt;simplesect id="block"&gt;
+        &lt;title&gt;Sample Block Section&lt;/title&gt;
+        ...
+      &lt;/simplesect&gt;
     &lt;/section&gt;
   &lt;/section&gt;
 &lt;/article&gt;</programlisting>
-    </example>
+      </example>
+    </simplesect>
   </section>
 </chapter>

Modified: incubator/cxf/trunk/docs/src/docs/styleguide/tables.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/styleguide/tables.xml?view=diff&rev=440874&r1=440873&r2=440874
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/tables.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/tables.xml Wed Sep  6 14:17:39 2006
@@ -165,7 +165,7 @@
       table to have multiple tgroup elements. In such a case, each <sgmltag class="element">tgroup</sgmltag> element would define a unique portion
       of table where the columns and spans had different
       specifications.</para>
-      <section>
+      <simplesect>
         <title>Attributes</title>
         <para><xref linkend="tgroupattrs"/> shows the attributes for the
         <sgmltag class="element">tgroup</sgmltag> element. Attributes in the
@@ -218,8 +218,8 @@
           <para>Attributes not listed in <xref linkend="tgroupattrs"/> are
           not used in CXF documentation.</para>
         </note>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title>Example</title>
         <para><xref linkend="groupexample"/> shows the markup for a <sgmltag class="element">tgroup</sgmltag> element that defines a 3 column
         table.</para>
@@ -230,7 +230,7 @@
   &lt;/tgroup&gt;
 &lt;/table&gt;</programlisting>
         </informalexample>
-      </section>
+      </simplesect>
     </section>
     <section>
       <title>Specifying Column Properties</title>
@@ -238,7 +238,7 @@
       for the column in a table by adding <sgmltag class="element">colspec</sgmltag> elements to a <sgmltag class="element">tgroup</sgmltag> element. A <sgmltag class="element">colspec</sgmltag> element defines properties for all of
       the entries in one column in a group. You can set different properties
       for each column in a group.</para>
-      <section>
+      <simplesect>
         <title>Attributes</title>
         <para><xref linkend="colattrs"/> shows the attributes for the
         <sgmltag class="element">colspec</sgmltag> element. Attributes in the
@@ -306,8 +306,8 @@
           <para>Attributes not listed in <xref linkend="colattrs"/> are not
           used in CXF documentation.</para>
         </note>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title>Example</title>
         <para><xref linkend="colspecexample"/> shows the markup for
         specifying a column that is two inches wide and whose content is
@@ -321,7 +321,7 @@
   &lt;/tgroup&gt;
 &lt;/table&gt;</programlisting>
         </informalexample>
-      </section>
+      </simplesect>
     </section>
     <section>
       <title>Defining Spans</title>
@@ -329,7 +329,7 @@
       columns and name them for use by the cells in the group. To define a
       span you use the <sgmltag class="element">spanspec</sgmltag>
       element.</para>
-      <section>
+      <simplesect>
         <title>Required Attributes</title>
         <para>The <sgmltag class="element">spanspec</sgmltag> element has
         three required attributes as described in <xref linkend="spanreqattrs"/>.</para>
@@ -365,8 +365,8 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title>Optional Attributes</title>
         <para>In addition to the required attributes, the <sgmltag class="element">spanspec</sgmltag> element can also have the
         attributes described in <xref linkend="spanoptattrs"/>. Attributes in
@@ -413,8 +413,8 @@
           <para>Attributes not listed in <xref linkend="spanoptattrs"/> are
           not used in CXF documentation.</para>
         </note>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title>Example</title>
         <para><xref linkend="spanexample"/> shows the markup for a span that
         crosses the second and third column of a five column table. The
@@ -429,7 +429,7 @@
     ...
 &lt;/informaltable&gt;</programlisting>
         </informalexample>
-      </section>
+      </simplesect>
     </section>
     <section>
       <title>Adding a Heading Row to a Table</title>
@@ -438,7 +438,7 @@
       The <sgmltag class="element">thead</sgmltag> element is a child of a
       <sgmltag>tgroup</sgmltag> element. It must be placed after any <sgmltag class="element">colspec</sgmltag> elements and <sgmltag class="element">spanspec</sgmltag> elements. It should also be placed
       before any <sgmltag class="element">tbody</sgmltag> elements.</para>
-      <section>
+      <simplesect>
         <title>Attributes</title>
         <para><xref linkend="theadattrs"/> lists the attributes of the
         <sgmltag class="element">thead</sgmltag> element.</para>
@@ -464,15 +464,15 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title>Adding content</title>
         <para>The content of the heading row is specified using a single
         <sgmltag class="element">row</sgmltag> element and one entry <sgmltag class="element">child</sgmltag> element for each column in the table.
         For more information on the row element and the entry element see
         <xref linkend="rowsect"/> and <xref linkend="entrysect"/>.</para>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title>Example</title>
         <para><xref linkend="theadexample"/> shows the markup for tables used
         in this chapter.</para>
@@ -497,7 +497,7 @@
   &lt;/tgroup&gt;
 &lt;/informaltable&gt;</programlisting>
         </informalexample>
-      </section>
+      </simplesect>
     </section>
     <section>
       <title>Adding Rows to a Table</title>
@@ -505,7 +505,7 @@
       <sgmltag class="element">tbody</sgmltag> element. Each row in the table
       is defined using a <sgmltag class="element">row</sgmltag> element. The
       contents of each column in the row is defined using an <sgmltag class="element">entry</sgmltag> element.</para>
-      <section>
+      <simplesect>
         <title>The <sgmltag class="element">tbody</sgmltag> Element</title>
         <para>The <sgmltag class="element">tbody</sgmltag> element is a
         wrapper for all of the rows in the body of a group. It is placed after
@@ -514,8 +514,8 @@
         <sgmltag class="element">thead</sgmltag> element. It has a single
         attribute, <sgmltag class="attribute">valign</sgmltag>, that is
         described in <xref linkend="theadattrs"/>.</para>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title id="rowsect">The <sgmltag class="element">row</sgmltag> Element</title>
         <para>Rows in a table are defined using the <sgmltag>row</sgmltag>
         element. Each <sgmltag>row</sgmltag> element wraps a number of
@@ -566,8 +566,8 @@
             </tbody>
           </tgroup>
         </table>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title id="entrysect">The <sgmltag class="element">entry</sgmltag> Element</title>
         <para>The contents of of a table are specified using
         <sgmltag>entry</sgmltag> elements. <sgmltag>entry</sgmltag> elements
@@ -671,8 +671,8 @@
           <para>Attributes not listed in <xref linkend="entryattrs"/> are not
           used in CXF documentation.</para>
         </note>
-      </section>
-      <section>
+      </simplesect>
+      <simplesect>
         <title>Example</title>
         <para><xref linkend="tbodyexample"/> shows the markup for tables used
         in this chapter.</para>
@@ -719,7 +719,7 @@
   &lt;/tgroup&gt;
 &lt;/informaltable&gt;</programlisting>
         </informalexample>
-      </section>
+      </simplesect>
     </section>
     <section>
       <title>Example</title>



Mime
View raw message