cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dk...@apache.org
Subject svn commit: r436785 [6/18] - in /incubator/cxf/trunk: ./ api/ api/src/main/java/org/apache/cxf/buslifecycle/ api/src/main/java/org/apache/cxf/databinding/ api/src/main/java/org/apache/cxf/endpoint/ api/src/main/java/org/apache/cxf/interceptor/ api/src/...
Date Fri, 25 Aug 2006 13:17:37 GMT
Modified: incubator/cxf/trunk/docs/src/demos/index.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/demos/index.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/demos/index.xml (original)
+++ incubator/cxf/trunk/docs/src/demos/index.xml Fri Aug 25 06:16:36 2006
@@ -1,165 +1,165 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
-<document> 
-  <header> 
-    <title>CeltiXfire Demos</title> 
-	<abstract>This page is a collection of samples showing what people have developed for CeltiXfire or on top of CeltiXfire. The intent is to demonstrate CeltiXfire's capabilities and provide a starting point for developers.</abstract>
-  </header> 
-  <body> 
-    <section>
-      <title>Overviews</title>
-    <table>
-        <tr>
-          <td>
-            <a href="#intalio">
-              Intalio Integration
-            </a>
-          </td>
-          <td>
-            This demo describes how to write two CeltiXfire applications:
-            <ul>
-              <li>an application that kicks off an Intalio|n3 process</li>
-              <li>an application that provides the business logic representing an Intalio|n3 task.</li>
-            </ul>
-          </td>
-        </tr>
-        <tr>
-          <td>
-            <a href="#rss">
-              RSS Integration
-            </a>
-          </td>
-          <td>
-            This demo shows how to use RSS as a place to syndicate Web services in a simple way using CeltiXfire and RSSLib4J.
-            It shows how to wrap the RSSLib4J APIs in order to use them to implement a name lookup for a WSDL from a RSS feed.
-          </td>
-        </tr>
-        <tr>
-          <td>
-            <a href="#bpel">
-              ActiveBPEL Integration
-            </a>
-          </td>
-          <td>
-            This demo shows how to use the ActiveBPEL business process engine to
-            coordinate information flow between multiple CeltiXfire Web services. This demo also shows interoperability between
-            CeltiXfire and the ActiveBPEL engine, which uses Axis as its underlying Web services toolkit.
-          </td>
-        </tr>
-        <tr>
-          <td>
-            <a href="#mashup">Enterprise Mashup</a>
-          </td>
-          <td>
-            This demo shows how Celtix can be used to build an enterprise quality mashup. It uses PHP, MySQL, and Celtix to 
-			consume data from a database and generate a series of XML documents that are consumable by AJAX client.
-          </td>
-        </tr>
-		</table>
-	</section>
-    <section>
-      <title>Detailed Descriptions</title>
-	  <section id="intallio">
-		<title>Intalio Integration</title>
-		<p><strong>Description:</strong>
-      An Intalio|n3 business process may be exposed as a Web service, which allows a client application to
-      initiate a business process by sending a Web service request. Additionally, a task within an Intalio|n3
-      business process may represent an invocation on a distributed Web service. When the process reaches
-      this task, Intalio|n3 sends a Web services request to the external Web service. This application note
-      describes how to write two CeltiXfire applications:
-      </p>
-      <ul>
-        <li>An application that kicks off an Intalio|n3 process</li>
-        <li>An application that provides the business logic representing an Intalio|n3 task</li>
-      </ul>
-    <p><strong>Contributed by:</strong> John Lifter</p>
-    <p><strong>Created:</strong> 29 December 2005</p>
-    <p><strong>Last updated:</strong> 29 December 2005</p>
-    <p><strong>Tested with:</strong> Celtix 1.0</p>
-    <p><strong>Download:</strong></p>
-    <ul>
-      <li>Overview (<a href="./intalio/celtix_intalio_integration.pdf">pdf</a>)</li>
-      <li>Source (<a href="./intalio/celtix_intalio_integration.zip">zip</a>)</li>
-    </ul>
-	  </section>
-	  <section id="rss">
-		<title> RSS Integration</title>
-		<p><strong>Prerequisites:</strong> Please download RSSLib4J from <a href="http://devzone.stealthp.org/cms/index.php?page=RSSLib4J#RSSLib4J"> here</a>.</p>
-		<p><strong>Motivation:</strong> Today there are two fundamental ways to connect to a Web service:</p>
-		<ul>
-		  <li>Bootstrap the consumer with the service's WSDL file.</li>
-		  <li>Use a UDDI registry to look up a service.</li>
-		</ul>
-		<p>The problem for many small organizations is that UDDI is a substantial investment in terms of licensing, programming to the APIs, and perhaps hosting.
-           UDDI seems like a lot of infrastructure for simply looking up a Web service. And if the developer doesn't want to bootstrap using a WSDL file, what other alternative do they have?
-			<br/>
-			Why not use RSS as a place to syndicate Web services in a simple way. I found <a href="http://www.xml.com/pub/a/2002/12/18/dive-into-xml.html#RSS"> this</a> site useful in describing RSS and its various flavors. RSS stands for Really Simple Syndication and is used by news web sites and bloggers to create feeds. Basically RSS provides a channel that contains one or more items. Each item has, among other things, a title, a description, and a link. Usually the link is an HTML link to the news or blog content. However there is no reason why that link cannot be to a link to a service's WSDL.</p>
-		<p><strong>Description:</strong> This demo uses CeltiXfire and an RSS feed parser called RSSLib4J that you can <a href="http://devzone.stealthp.org/cms/index.php?page=RSSLib4J#RSSLib4J"> download here</a>. It includes a simple class that wraps the RSSLib4J APIs in order to use them for a name lookup for a WSDL from the feed.
-<br/>
-This demo is similar to the simple Hello_World demo. The major differences are the source of the WSDL and how the client looks up the service's WSDL.
-The client uses the new RSSSRegistry class to parse the RSS feed. It then uses the link provided through the feed to bootstrap the service's WDL.
-The build.xml has been modified to pickup the RSSLib4J jar file in the demo's lib directory.
-<br/>
-Please read the readme.txt file for more information on running the demo.
-</p>
-    <p><strong>Contributed by:</strong> <a href="mailto:william.henry@iona.com">William Henry</a></p>
-    <p><strong>Created:</strong> 10 January 2006</p>
-    <p><strong>Last updated:</strong> 8 Febuary 2006</p>
-    <p><strong>Tested with:</strong>Celtix 1.0</p>
-    <p><strong>Download:</strong> <a href="./rss/hello_world_RSS.zip">zip</a></p>
-  </section>
-    <section id="bpel">
-	  <title>ActiveBPEL Integration</title>
-	  <p><strong>Description:</strong> In many situations, developers need to integrate several Web service applications into a larger application, such as
-      using a credit checking service, an inventory service, or a shipping service to process a sales order. It is
-      possible to write an application that accepts customer input, invokes the various services, and then returns shipping
-      and billing information to the customer. However, an alternative approach would be to define the process using business process execution
-      language (BPEL) and leave the details of persistence, compensation, coordination, and exception handling to a business process engine.
-      This demo shows how to use the ActiveBPEL business process engine to coordinate information flow between multiple CeltiXfire Web service
-      applications. This demo also shows interoperability between CeltiXfire and the ActiveBPEL engine, which uses Axis as its underlying
-      Web services toolkit.</p>
-	  <p><strong>Contributed by:</strong> John Lifter</p>
-	  <p><strong>Created:</strong> 27 January 2006</p>
-      <p><strong>Last updated:</strong> 27 January 2006</p>
-	  <p><strong>Tested with:</strong> Celtix 1.0</p>
-	  <p><strong>Download:</strong></p>
-    <ul>
-      <li>Overview (<a href="./bepl/celtix_activeBPEL_integration.pdf">pdf</a>)</li>
-      <li>Source (<a href="./bepl/celtix_activeBPEL_integration.zip">zip</a>)</li>
-    </ul>
-	</section>
-	<section id="mashup">
-    <title>Enterprise Mashup</title>
-    <p><strong>Prerequisites:</strong></p> 
-    <ul>
-      <li>Celtix 1.0 (<a href="http://celtix.objectweb.net">celtix.objectweb.net</a>)</li>
-      <li>Java JDK 1.5.0 (<a href="http://java.sun.com">java.sun.com</a>)</li> 
-      <li>MySQL Database Ver 14.7 Distrib 4.1.13 (<a href="http://www.mysql.com">www.mysql.com</a>)</li>
-      <li>MySQL Connector/J JDBC Driver 3.1.13 (<a href="http://www.mysql.com">www.mysql.com</a>)</li>
-      <li>Apache Webserver 2.0 (<a href="http://www.apache.org">www.apache.org</a>)</li>
-      <li>PHP 5.0 (Previous versions should work) (<a href="http://www.apache.org">www.php.net</a>)</li>
-      <li>NuSoap (<a href="http://sourceforge.net/projects/nusoap">sourceforge.net/projects/nusoap</a>)</li>
-      <li>Google Maps key for your server (<a href="http://www.google.com/apis/maps/signup.html">www.google.com/apis/maps/signup.html</a>)</li>
-    </ul>
-	<p>
-      <strong>Description:</strong> This demo is intended to model an applicaiton that could be used by a 
-	  call center employee. It takes phone numbers from a database and 
-	  displays a Google map containing a markers that show the zip codes for 
-	  the phone numbers. In addition, it displays the number of calls from each 
-	  zip code. To do this it makes calls to NetSleuth.com to find the zip 
-	  codes and to Google Maps for a lat/lon pair for each zip code.
-	  <br />For a more complete description see: <a href="http://www.hautetechno.net/2006/08/post.html">www.hautetechno.net</a>
-    </p>
-    <p><strong>Contributed by:</strong> Barry O'Mahony</p>
-    <p><strong>Created:</strong> 15 August 2006</p>
-    <p><strong>Last updated:</strong> 15 August 2006</p>
-    <p><strong>Tested with:</strong> Celtix 1.0</p>
-    <p><strong>Download:</strong></p>
-    <ul>
-      <li>Overview (<a href="./mashup/celtix_mashup.pdf">pdf</a>)</li>
-      <li>Source (<a href="./mashup/celtix_mashup_demo.tar.gz">gzip</a>)</li>
-    </ul>
-	</section>
-	  </section>
-  </body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document> 
+  <header> 
+    <title>CeltiXfire Demos</title> 
+	<abstract>This page is a collection of samples showing what people have developed for CeltiXfire or on top of CeltiXfire. The intent is to demonstrate CeltiXfire's capabilities and provide a starting point for developers.</abstract>
+  </header> 
+  <body> 
+    <section>
+      <title>Overviews</title>
+    <table>
+        <tr>
+          <td>
+            <a href="#intalio">
+              Intalio Integration
+            </a>
+          </td>
+          <td>
+            This demo describes how to write two CeltiXfire applications:
+            <ul>
+              <li>an application that kicks off an Intalio|n3 process</li>
+              <li>an application that provides the business logic representing an Intalio|n3 task.</li>
+            </ul>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <a href="#rss">
+              RSS Integration
+            </a>
+          </td>
+          <td>
+            This demo shows how to use RSS as a place to syndicate Web services in a simple way using CeltiXfire and RSSLib4J.
+            It shows how to wrap the RSSLib4J APIs in order to use them to implement a name lookup for a WSDL from a RSS feed.
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <a href="#bpel">
+              ActiveBPEL Integration
+            </a>
+          </td>
+          <td>
+            This demo shows how to use the ActiveBPEL business process engine to
+            coordinate information flow between multiple CeltiXfire Web services. This demo also shows interoperability between
+            CeltiXfire and the ActiveBPEL engine, which uses Axis as its underlying Web services toolkit.
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <a href="#mashup">Enterprise Mashup</a>
+          </td>
+          <td>
+            This demo shows how Celtix can be used to build an enterprise quality mashup. It uses PHP, MySQL, and Celtix to 
+			consume data from a database and generate a series of XML documents that are consumable by AJAX client.
+          </td>
+        </tr>
+		</table>
+	</section>
+    <section>
+      <title>Detailed Descriptions</title>
+	  <section id="intallio">
+		<title>Intalio Integration</title>
+		<p><strong>Description:</strong>
+      An Intalio|n3 business process may be exposed as a Web service, which allows a client application to
+      initiate a business process by sending a Web service request. Additionally, a task within an Intalio|n3
+      business process may represent an invocation on a distributed Web service. When the process reaches
+      this task, Intalio|n3 sends a Web services request to the external Web service. This application note
+      describes how to write two CeltiXfire applications:
+      </p>
+      <ul>
+        <li>An application that kicks off an Intalio|n3 process</li>
+        <li>An application that provides the business logic representing an Intalio|n3 task</li>
+      </ul>
+    <p><strong>Contributed by:</strong> John Lifter</p>
+    <p><strong>Created:</strong> 29 December 2005</p>
+    <p><strong>Last updated:</strong> 29 December 2005</p>
+    <p><strong>Tested with:</strong> Celtix 1.0</p>
+    <p><strong>Download:</strong></p>
+    <ul>
+      <li>Overview (<a href="./intalio/celtix_intalio_integration.pdf">pdf</a>)</li>
+      <li>Source (<a href="./intalio/celtix_intalio_integration.zip">zip</a>)</li>
+    </ul>
+	  </section>
+	  <section id="rss">
+		<title> RSS Integration</title>
+		<p><strong>Prerequisites:</strong> Please download RSSLib4J from <a href="http://devzone.stealthp.org/cms/index.php?page=RSSLib4J#RSSLib4J"> here</a>.</p>
+		<p><strong>Motivation:</strong> Today there are two fundamental ways to connect to a Web service:</p>
+		<ul>
+		  <li>Bootstrap the consumer with the service's WSDL file.</li>
+		  <li>Use a UDDI registry to look up a service.</li>
+		</ul>
+		<p>The problem for many small organizations is that UDDI is a substantial investment in terms of licensing, programming to the APIs, and perhaps hosting.
+           UDDI seems like a lot of infrastructure for simply looking up a Web service. And if the developer doesn't want to bootstrap using a WSDL file, what other alternative do they have?
+			<br/>
+			Why not use RSS as a place to syndicate Web services in a simple way. I found <a href="http://www.xml.com/pub/a/2002/12/18/dive-into-xml.html#RSS"> this</a> site useful in describing RSS and its various flavors. RSS stands for Really Simple Syndication and is used by news web sites and bloggers to create feeds. Basically RSS provides a channel that contains one or more items. Each item has, among other things, a title, a description, and a link. Usually the link is an HTML link to the news or blog content. However there is no reason why that link cannot be to a link to a service's WSDL.</p>
+		<p><strong>Description:</strong> This demo uses CeltiXfire and an RSS feed parser called RSSLib4J that you can <a href="http://devzone.stealthp.org/cms/index.php?page=RSSLib4J#RSSLib4J"> download here</a>. It includes a simple class that wraps the RSSLib4J APIs in order to use them for a name lookup for a WSDL from the feed.
+<br/>
+This demo is similar to the simple Hello_World demo. The major differences are the source of the WSDL and how the client looks up the service's WSDL.
+The client uses the new RSSSRegistry class to parse the RSS feed. It then uses the link provided through the feed to bootstrap the service's WDL.
+The build.xml has been modified to pickup the RSSLib4J jar file in the demo's lib directory.
+<br/>
+Please read the readme.txt file for more information on running the demo.
+</p>
+    <p><strong>Contributed by:</strong> <a href="mailto:william.henry@iona.com">William Henry</a></p>
+    <p><strong>Created:</strong> 10 January 2006</p>
+    <p><strong>Last updated:</strong> 8 Febuary 2006</p>
+    <p><strong>Tested with:</strong>Celtix 1.0</p>
+    <p><strong>Download:</strong> <a href="./rss/hello_world_RSS.zip">zip</a></p>
+  </section>
+    <section id="bpel">
+	  <title>ActiveBPEL Integration</title>
+	  <p><strong>Description:</strong> In many situations, developers need to integrate several Web service applications into a larger application, such as
+      using a credit checking service, an inventory service, or a shipping service to process a sales order. It is
+      possible to write an application that accepts customer input, invokes the various services, and then returns shipping
+      and billing information to the customer. However, an alternative approach would be to define the process using business process execution
+      language (BPEL) and leave the details of persistence, compensation, coordination, and exception handling to a business process engine.
+      This demo shows how to use the ActiveBPEL business process engine to coordinate information flow between multiple CeltiXfire Web service
+      applications. This demo also shows interoperability between CeltiXfire and the ActiveBPEL engine, which uses Axis as its underlying
+      Web services toolkit.</p>
+	  <p><strong>Contributed by:</strong> John Lifter</p>
+	  <p><strong>Created:</strong> 27 January 2006</p>
+      <p><strong>Last updated:</strong> 27 January 2006</p>
+	  <p><strong>Tested with:</strong> Celtix 1.0</p>
+	  <p><strong>Download:</strong></p>
+    <ul>
+      <li>Overview (<a href="./bepl/celtix_activeBPEL_integration.pdf">pdf</a>)</li>
+      <li>Source (<a href="./bepl/celtix_activeBPEL_integration.zip">zip</a>)</li>
+    </ul>
+	</section>
+	<section id="mashup">
+    <title>Enterprise Mashup</title>
+    <p><strong>Prerequisites:</strong></p> 
+    <ul>
+      <li>Celtix 1.0 (<a href="http://celtix.objectweb.net">celtix.objectweb.net</a>)</li>
+      <li>Java JDK 1.5.0 (<a href="http://java.sun.com">java.sun.com</a>)</li> 
+      <li>MySQL Database Ver 14.7 Distrib 4.1.13 (<a href="http://www.mysql.com">www.mysql.com</a>)</li>
+      <li>MySQL Connector/J JDBC Driver 3.1.13 (<a href="http://www.mysql.com">www.mysql.com</a>)</li>
+      <li>Apache Webserver 2.0 (<a href="http://www.apache.org">www.apache.org</a>)</li>
+      <li>PHP 5.0 (Previous versions should work) (<a href="http://www.apache.org">www.php.net</a>)</li>
+      <li>NuSoap (<a href="http://sourceforge.net/projects/nusoap">sourceforge.net/projects/nusoap</a>)</li>
+      <li>Google Maps key for your server (<a href="http://www.google.com/apis/maps/signup.html">www.google.com/apis/maps/signup.html</a>)</li>
+    </ul>
+	<p>
+      <strong>Description:</strong> This demo is intended to model an applicaiton that could be used by a 
+	  call center employee. It takes phone numbers from a database and 
+	  displays a Google map containing a markers that show the zip codes for 
+	  the phone numbers. In addition, it displays the number of calls from each 
+	  zip code. To do this it makes calls to NetSleuth.com to find the zip 
+	  codes and to Google Maps for a lat/lon pair for each zip code.
+	  <br />For a more complete description see: <a href="http://www.hautetechno.net/2006/08/post.html">www.hautetechno.net</a>
+    </p>
+    <p><strong>Contributed by:</strong> Barry O'Mahony</p>
+    <p><strong>Created:</strong> 15 August 2006</p>
+    <p><strong>Last updated:</strong> 15 August 2006</p>
+    <p><strong>Tested with:</strong> Celtix 1.0</p>
+    <p><strong>Download:</strong></p>
+    <ul>
+      <li>Overview (<a href="./mashup/celtix_mashup.pdf">pdf</a>)</li>
+      <li>Source (<a href="./mashup/celtix_mashup_demo.tar.gz">gzip</a>)</li>
+    </ul>
+	</section>
+	  </section>
+  </body>
+</document>

Propchange: incubator/cxf/trunk/docs/src/demos/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/demos/index.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/demos/index.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/guides/configuration.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/guides/configuration.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/guides/configuration.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/guides/develop_consumer.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/guides/develop_consumer.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/guides/develop_consumer.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/guides/dynamic_lang.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/guides/dynamic_lang.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/guides/dynamic_lang.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/guides/getting_started.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/guides/getting_started.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/guides/getting_started.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/guides/installation.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/guides/installation.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/guides/installation.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/guides/jms.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/guides/jms.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/guides/jms.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/guides/management.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/guides/management.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/guides/management.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/guides/tomcat_deploy.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/guides/tomcat_deploy.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/guides/tomcat_deploy.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Modified: incubator/cxf/trunk/docs/src/docs/index.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/index.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/index.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/index.xml Fri Aug 25 06:16:36 2006
@@ -1,73 +1,73 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
-<document> 
-  <header> 
-    <title>CeltiXfire Documentation</title> 
-  </header> 
-  <body> 
-    <section>
-      <title>Contributing</title>
-      <p>If you are interested in contributing to the CeltiXfire documentation click on the <a href="site:docco/proj">Documentation Project</a> link on the menu.</p>
-    </section>
-	<section>
-	  <title>User FAQs</title>
-      <ul>
-        <li><a href="site:general">General</a></li>
-        <li><a href="site:license">Licensing</a></li>
-        <li><a href="site:project">Project</a></li>
-        <li><a href="site:features">Features</a></li>
-        <li><a href="site:tech">CeltiXfire Technology</a></li>
-      </ul>
-	  </section>
-      <section>
-	  <title>Installation Documentation</title>
-      <ul>
-        <li><a href="site:install">Installation Guide</a></li>
-        <li><a href="site:rel_notes">Release Notes</a></li>
-      </ul>
-	  </section>
-      <section>
-	  <title>Tutorials</title>
-      <ul>
-        <li><a href="site:get_started">Getting Started with CeltiXfire</a></li>
-      </ul>
-	  </section>
-      <section>
-	  <title>User Guides</title>
-	  <section>
-	  <title>Development</title>
-        <ul>
-		  <li><a href="site:consumer_dev">Developing a CeltiXfire Consumer</a></li>
-		  <li><a href="site:jms">Using the JMS Transport</a></li>
-		  <li><a href="site:dyn_lang">Using Dynamic Languages to Implement Services</a></li>
-		  <li><a href="site:mgmt">Using CeltiXfire Management</a></li>
-		</ul>
-	  </section>
-	  <section>
-	  <title>Deployment</title>
-		<ul>
-          <li><a href="site:config">Using CeltiXfire Configuration</a></li>
-		  <li><a href="site:tomcat">Deploying CeltiXfire into a Servlet Container</a></li>
-        </ul>
-      </section>
-	  </section>
-	  <section>
-	  <title>References</title>
-        <ul>
-          <li><a href="../docs/api/index.html">CeltiXfire APIs</a></li>
-          <li><a href="site:toolsref">Command-line Tools</a></li>
-        </ul>   
-      </section>
-	  <section>
-	  <title>Arcitecture Guides</title>
-      <ul>
-        <li><a href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=Components">Components</a></li>
-        <li><a href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=RequestHandling">Request Handling</a></li>
-        <li><a href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=CeltixJBIOverview">JBI Integration</a></li>
-      </ul>
-	</section>
-      <section>
-	  <title>Standards</title>
-	  </section>
-  </body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document> 
+  <header> 
+    <title>CeltiXfire Documentation</title> 
+  </header> 
+  <body> 
+    <section>
+      <title>Contributing</title>
+      <p>If you are interested in contributing to the CeltiXfire documentation click on the <a href="site:docco/proj">Documentation Project</a> link on the menu.</p>
+    </section>
+	<section>
+	  <title>User FAQs</title>
+      <ul>
+        <li><a href="site:general">General</a></li>
+        <li><a href="site:license">Licensing</a></li>
+        <li><a href="site:project">Project</a></li>
+        <li><a href="site:features">Features</a></li>
+        <li><a href="site:tech">CeltiXfire Technology</a></li>
+      </ul>
+	  </section>
+      <section>
+	  <title>Installation Documentation</title>
+      <ul>
+        <li><a href="site:install">Installation Guide</a></li>
+        <li><a href="site:rel_notes">Release Notes</a></li>
+      </ul>
+	  </section>
+      <section>
+	  <title>Tutorials</title>
+      <ul>
+        <li><a href="site:get_started">Getting Started with CeltiXfire</a></li>
+      </ul>
+	  </section>
+      <section>
+	  <title>User Guides</title>
+	  <section>
+	  <title>Development</title>
+        <ul>
+		  <li><a href="site:consumer_dev">Developing a CeltiXfire Consumer</a></li>
+		  <li><a href="site:jms">Using the JMS Transport</a></li>
+		  <li><a href="site:dyn_lang">Using Dynamic Languages to Implement Services</a></li>
+		  <li><a href="site:mgmt">Using CeltiXfire Management</a></li>
+		</ul>
+	  </section>
+	  <section>
+	  <title>Deployment</title>
+		<ul>
+          <li><a href="site:config">Using CeltiXfire Configuration</a></li>
+		  <li><a href="site:tomcat">Deploying CeltiXfire into a Servlet Container</a></li>
+        </ul>
+      </section>
+	  </section>
+	  <section>
+	  <title>References</title>
+        <ul>
+          <li><a href="../docs/api/index.html">CeltiXfire APIs</a></li>
+          <li><a href="site:toolsref">Command-line Tools</a></li>
+        </ul>   
+      </section>
+	  <section>
+	  <title>Arcitecture Guides</title>
+      <ul>
+        <li><a href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=Components">Components</a></li>
+        <li><a href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=RequestHandling">Request Handling</a></li>
+        <li><a href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=CeltixJBIOverview">JBI Integration</a></li>
+      </ul>
+	</section>
+      <section>
+	  <title>Standards</title>
+	  </section>
+  </body>
+</document>

Propchange: incubator/cxf/trunk/docs/src/docs/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/index.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/index.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Modified: incubator/cxf/trunk/docs/src/docs/project.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/project.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/project.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/project.xml Fri Aug 25 06:16:36 2006
@@ -1,74 +1,74 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
-<document> 
-  <header> 
-    <title>CeltiXfire Documentation Project</title> 
-  </header> 
-  <body> 
-    <section>
-      <title>Roadmap</title>
-      <p>The full 1.0 Documentation plan in PDF format is available here: <a href="../docs/oneoplan.pdf">1.0 Doc Plan</a></p>
-      <section>
-	  <title>Milestones</title>
-	  <section>
-      <title>Doc Milestone 1 - 4/28/06</title>
-      <ul>
-        <li><strong>Installation Guide (finsihed)</strong></li>
-        <li><strong>Getting Started with CeltiXfire (finished)</strong></li>
-        <li><strong>Developing a Service with CeltiXfire</strong></li>
-        <li><strong>Developing a Consumer with CeltiXfire (finished)</strong></li>
-        <li><strong>CeltiXfire Configuration Guide (finished)</strong></li>
-      </ul>
-	  </section>
-	  <section>
-      <title>Doc Milestone 2 - 5/26/06</title>
-      <ul>
-        <li><strong>Writing Handlers</strong></li>
-        <li><strong>Creating Routes with CeltiXfire</strong></li>
-        <li><strong>Using the JMS Transport (finished)</strong></li>
-        <li><strong>Deploying CeltiXfire in a Servlet Container (drafted)</strong></li>
-      </ul>
-	  </section>
-	  <section>
-      <title>Doc Milestone 3 - 6/30/06</title>
-      <ul>
-        <li><strong>Writing Asynchronous Services</strong></li>
-        <li><strong>Securing CeltiXfire Services</strong></li>
-        <li><strong>Using Reliable Messaging in CeltiXfire</strong></li>
-        <li><strong>Deploying CeltiXfire Applications in a J2EE Environment</strong></li>
-      </ul>
-	  </section>
-	  <section>
-      <title>Docs 1.0 - 7/28/06</title>
-      <ul>
-        <li><strong>Deploying CeltiXfire Applications in an SCA Container</strong></li>
-        <li><strong>Deploying CeltiXfire Applications in a JBI Container</strong></li>
-        <li><strong>Command Line Tool Reference (finished)</strong></li>
-      </ul>
-	  </section>
-	  <section>
-      <title>Post 1.0</title>
-      <ul>
-        <li><strong>Implementing a CeltiXfire Transport</strong></li>
-        <li><strong>Implementing a CeltiXfire Binding</strong></li>
-        <li><strong>Extending CeltiXfire Configuration</strong></li>
-        <li><strong>CeltiXfire Architecture Guide</strong></li>
-        <li>Tutorials</li>
-        <li>FAQs</li>
-      </ul>
-	  </section>
-	  </section>
-	  </section>
-	  <section>
-      <title>How to participate</title>
-      <p>To work on the CeltiXfire documentation do the following:</p>
-      <ol>
-        <li>Check the list of tasks in the <a href="http://forge.objectweb.org/pm/task.php?group_project_id=182">documentation subproject</a>.</li>
-        <li>E-mail a notice to the <a href="mailto:celtix-dev@objectweb.org">CeltiXfire developers list</a> stating which document you want to work on.</li>
-        <li>If you are writing a new document, see the <a href="site:style">CeltiXfire Style Guide</a>.</li>
-        <li>If you are updating existing documentation, download the current version from the repository and edit that.</li>
-        <li>Send the finished product to the <a href="mailto:celtix-dev@objectweb.org">CeltiXfire developers list</a>.</li>
-      </ol>
-	  </section>
-  </body>
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document> 
+  <header> 
+    <title>CeltiXfire Documentation Project</title> 
+  </header> 
+  <body> 
+    <section>
+      <title>Roadmap</title>
+      <p>The full 1.0 Documentation plan in PDF format is available here: <a href="../docs/oneoplan.pdf">1.0 Doc Plan</a></p>
+      <section>
+	  <title>Milestones</title>
+	  <section>
+      <title>Doc Milestone 1 - 4/28/06</title>
+      <ul>
+        <li><strong>Installation Guide (finsihed)</strong></li>
+        <li><strong>Getting Started with CeltiXfire (finished)</strong></li>
+        <li><strong>Developing a Service with CeltiXfire</strong></li>
+        <li><strong>Developing a Consumer with CeltiXfire (finished)</strong></li>
+        <li><strong>CeltiXfire Configuration Guide (finished)</strong></li>
+      </ul>
+	  </section>
+	  <section>
+      <title>Doc Milestone 2 - 5/26/06</title>
+      <ul>
+        <li><strong>Writing Handlers</strong></li>
+        <li><strong>Creating Routes with CeltiXfire</strong></li>
+        <li><strong>Using the JMS Transport (finished)</strong></li>
+        <li><strong>Deploying CeltiXfire in a Servlet Container (drafted)</strong></li>
+      </ul>
+	  </section>
+	  <section>
+      <title>Doc Milestone 3 - 6/30/06</title>
+      <ul>
+        <li><strong>Writing Asynchronous Services</strong></li>
+        <li><strong>Securing CeltiXfire Services</strong></li>
+        <li><strong>Using Reliable Messaging in CeltiXfire</strong></li>
+        <li><strong>Deploying CeltiXfire Applications in a J2EE Environment</strong></li>
+      </ul>
+	  </section>
+	  <section>
+      <title>Docs 1.0 - 7/28/06</title>
+      <ul>
+        <li><strong>Deploying CeltiXfire Applications in an SCA Container</strong></li>
+        <li><strong>Deploying CeltiXfire Applications in a JBI Container</strong></li>
+        <li><strong>Command Line Tool Reference (finished)</strong></li>
+      </ul>
+	  </section>
+	  <section>
+      <title>Post 1.0</title>
+      <ul>
+        <li><strong>Implementing a CeltiXfire Transport</strong></li>
+        <li><strong>Implementing a CeltiXfire Binding</strong></li>
+        <li><strong>Extending CeltiXfire Configuration</strong></li>
+        <li><strong>CeltiXfire Architecture Guide</strong></li>
+        <li>Tutorials</li>
+        <li>FAQs</li>
+      </ul>
+	  </section>
+	  </section>
+	  </section>
+	  <section>
+      <title>How to participate</title>
+      <p>To work on the CeltiXfire documentation do the following:</p>
+      <ol>
+        <li>Check the list of tasks in the <a href="http://forge.objectweb.org/pm/task.php?group_project_id=182">documentation subproject</a>.</li>
+        <li>E-mail a notice to the <a href="mailto:celtix-dev@objectweb.org">CeltiXfire developers list</a> stating which document you want to work on.</li>
+        <li>If you are writing a new document, see the <a href="site:style">CeltiXfire Style Guide</a>.</li>
+        <li>If you are updating existing documentation, download the current version from the repository and edit that.</li>
+        <li>Send the finished product to the <a href="mailto:celtix-dev@objectweb.org">CeltiXfire developers list</a>.</li>
+      </ol>
+	  </section>
+  </body>
 </document>

Propchange: incubator/cxf/trunk/docs/src/docs/project.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/project.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/project.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/refs/tools.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/refs/tools.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/refs/tools.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

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?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml Fri Aug 25 06:16:36 2006
@@ -1,97 +1,97 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter>
-  <title>Admonitions</title>
-  <section>
-    <title>Overview</title>
-    <para>Admonitions are pieces of text that are offset from the main flow of text. They include 
-	      things like warnings, notes, and tips. They should be used sparingly because they 
-		  interupt the flow of the text. However, if you think one is needed, use one.</para>
-	<para>As a general rule, warnings and notes are the <emphasis role="strong">prefered</emphasis> 
-	      admonitions in CeltiXire documentation. That does not mean the use of the other types are 
-		  prohibited. It only means that they should be used with caution.</para>
-  </section>
-  <section id="warn">
-    <title>Warnings</title>
-	<para>Warnings are used to callout instances where a serious loss of data could occur. The 
-	      text of the warning should make it clear what will cause the data loss and what data 
-		  is at risk. For example, if using a value greater than 1 million will cause a method 
-		  invocation to return garbage, you should use a warning to mention this.</para>
-	<para>Warnings are marked up using a <sgmltag class="element">warning</sgmltag> element. The 
-	      <sgmltag class="element">warning</sgmltag> element should contain a single 
-		  <sgmltag class="element">para</sgmltag> element that contains the text for the warning.</para>
-	<para>The <sgmltag class="element">warning</sgmltag> element can, however, contain more than one 
-	      paragraph, a code listing, or a table. These are exceptions that are to be used sparingly.</para>
-  </section>
-  <section id="note">
-    <title>Notes</title>
-	<para>Notes are used to callout information that the reader should be aware of, but is 
-	      ancillary to the topic being discused in the main flow of the text. For example, if you 
-		  are discussing the mapping of a CORBA service from IDL to WSDL and want to reference the
-		  official IDL to WSDL mapping, you might put the reference in a note.</para>
-	<para>Notes are marked up using a <sgmltag class="element">note</sgmltag> element. Like the 
-	      <sgmltag class="element">warning</sgmltag> element, the <sgmltag class="element">note</sgmltag> 
-		  element should contain a single <sgmltag class="element">para</sgmltag> element that 
-		  contains the text for the warning. The <sgmltag class="element">note</sgmltag> element 
-		  can also contain more than one paragraph, a code listing, or a table.</para>
-  </section>
-  <section>
-    <title>Footnotes</title>
-	<para>In general, you should not need to use footnotes in CeltiXfire documentation. If you 
-	      find that a footnote is required, you can use one. However, most information that would 
-		  be put in a footnote is more appropriately placed in a note. For example, if there is a 
-		  related specification for a feature or some other ancilary piece of information, you might 
-		  put it in a footnote.</para>
-	<para>Footnotes are marked up using the <sgmltag class="element">footnote</sgmltag> element. 
-	      The <sgmltag class="element">footnote</sgmltag> element must contain a block element such 
-		  as a <sgmltag class="element">para</sgmltag> element or a 
-		  <sgmltag class="element">table</sgmltag> element. The contents of the footnote will be 
-		  placed according to the formatting rules and a link will be inserted where the 
-		  <sgmltag class="element">footnote</sgmltag> element was in the text.</para>
-	<para>In addition to using a footnote as a holder for text, you can also create a footnot that 
-		  refers to another footnote. To do this you use the 
-		  <sgmltag class="element">footnoteref</sgmltag> element. It takes a single attribute, 
-		  <sgmltag class="attribute">linkend</sgmltag>, that specifies the 
-		  <sgmltag class="attribute">id</sgmltag> of the referenced footnote. The generated link 
-		  will point back to the referenced footnote.</para>
-  </section>
-  <section>
-    <title>Others</title>
-    <para>In addition to the above admonition types, Docbook has elements for three other types:</para>
-	<itemizedlist>
-	  <listitem><para><link linkend="caution">cautions</link></para></listitem>
-	  <listitem><para><link linkend="important">important notes</link></para></listitem>
-	  <listitem><para><link linkend="tip">tips</link></para></listitem>
-	</itemizedlist>
-	<section id="caution">
-	  <title>Cautions</title>
-	  <para>Cautions are intended for use when a <link linkend="warn">warning</link> is too 
-	        strong. For example, a caution may be used when an action will potentially cuase a 
-			service to return an exception, but not crash or result in any loss of critical data. 
-			In general, it is best to use a <link linkend="warn">warning</link>.</para>
-		<para>Cautions are marked up using the <sgmltag 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>
-	<section id="important">
-	  <title>Important Notes</title>
-	  <para>Important notes are used to point out information that is important for the user to 
-	        know, but that may not be obvious. For example, if you change a value in a context and 
-			the new value overrides a transport setting for the service. Or if the new value 
-			persists for all future uses of the context.</para>
-	  <para>Important notes are marked up using the <sgmltag class="element">important</sgmltag> 
-	        element. The <sgmltag 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>
-	<section id="tip">
-	  <title>Tips</title>
-	  <para>Tips are bits of information that may help a user be more productive, but that are not 
-	        critical to using the product. In general, this type of information should either be 
-			worked directly into the text or placed in a <link linkend="note">note</link>.</para>
-	  <para>Tips are marked up using the <sgmltag class="element">tip</sgmltag> element. The 
-	        <sgmltag 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>
-  </section>
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter>
+  <title>Admonitions</title>
+  <section>
+    <title>Overview</title>
+    <para>Admonitions are pieces of text that are offset from the main flow of text. They include 
+	      things like warnings, notes, and tips. They should be used sparingly because they 
+		  interupt the flow of the text. However, if you think one is needed, use one.</para>
+	<para>As a general rule, warnings and notes are the <emphasis role="strong">prefered</emphasis> 
+	      admonitions in CeltiXire documentation. That does not mean the use of the other types are 
+		  prohibited. It only means that they should be used with caution.</para>
+  </section>
+  <section id="warn">
+    <title>Warnings</title>
+	<para>Warnings are used to callout instances where a serious loss of data could occur. The 
+	      text of the warning should make it clear what will cause the data loss and what data 
+		  is at risk. For example, if using a value greater than 1 million will cause a method 
+		  invocation to return garbage, you should use a warning to mention this.</para>
+	<para>Warnings are marked up using a <sgmltag class="element">warning</sgmltag> element. The 
+	      <sgmltag class="element">warning</sgmltag> element should contain a single 
+		  <sgmltag class="element">para</sgmltag> element that contains the text for the warning.</para>
+	<para>The <sgmltag class="element">warning</sgmltag> element can, however, contain more than one 
+	      paragraph, a code listing, or a table. These are exceptions that are to be used sparingly.</para>
+  </section>
+  <section id="note">
+    <title>Notes</title>
+	<para>Notes are used to callout information that the reader should be aware of, but is 
+	      ancillary to the topic being discused in the main flow of the text. For example, if you 
+		  are discussing the mapping of a CORBA service from IDL to WSDL and want to reference the
+		  official IDL to WSDL mapping, you might put the reference in a note.</para>
+	<para>Notes are marked up using a <sgmltag class="element">note</sgmltag> element. Like the 
+	      <sgmltag class="element">warning</sgmltag> element, the <sgmltag class="element">note</sgmltag> 
+		  element should contain a single <sgmltag class="element">para</sgmltag> element that 
+		  contains the text for the warning. The <sgmltag class="element">note</sgmltag> element 
+		  can also contain more than one paragraph, a code listing, or a table.</para>
+  </section>
+  <section>
+    <title>Footnotes</title>
+	<para>In general, you should not need to use footnotes in CeltiXfire documentation. If you 
+	      find that a footnote is required, you can use one. However, most information that would 
+		  be put in a footnote is more appropriately placed in a note. For example, if there is a 
+		  related specification for a feature or some other ancilary piece of information, you might 
+		  put it in a footnote.</para>
+	<para>Footnotes are marked up using the <sgmltag class="element">footnote</sgmltag> element. 
+	      The <sgmltag class="element">footnote</sgmltag> element must contain a block element such 
+		  as a <sgmltag class="element">para</sgmltag> element or a 
+		  <sgmltag class="element">table</sgmltag> element. The contents of the footnote will be 
+		  placed according to the formatting rules and a link will be inserted where the 
+		  <sgmltag class="element">footnote</sgmltag> element was in the text.</para>
+	<para>In addition to using a footnote as a holder for text, you can also create a footnot that 
+		  refers to another footnote. To do this you use the 
+		  <sgmltag class="element">footnoteref</sgmltag> element. It takes a single attribute, 
+		  <sgmltag class="attribute">linkend</sgmltag>, that specifies the 
+		  <sgmltag class="attribute">id</sgmltag> of the referenced footnote. The generated link 
+		  will point back to the referenced footnote.</para>
+  </section>
+  <section>
+    <title>Others</title>
+    <para>In addition to the above admonition types, Docbook has elements for three other types:</para>
+	<itemizedlist>
+	  <listitem><para><link linkend="caution">cautions</link></para></listitem>
+	  <listitem><para><link linkend="important">important notes</link></para></listitem>
+	  <listitem><para><link linkend="tip">tips</link></para></listitem>
+	</itemizedlist>
+	<section id="caution">
+	  <title>Cautions</title>
+	  <para>Cautions are intended for use when a <link linkend="warn">warning</link> is too 
+	        strong. For example, a caution may be used when an action will potentially cuase a 
+			service to return an exception, but not crash or result in any loss of critical data. 
+			In general, it is best to use a <link linkend="warn">warning</link>.</para>
+		<para>Cautions are marked up using the <sgmltag 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>
+	<section id="important">
+	  <title>Important Notes</title>
+	  <para>Important notes are used to point out information that is important for the user to 
+	        know, but that may not be obvious. For example, if you change a value in a context and 
+			the new value overrides a transport setting for the service. Or if the new value 
+			persists for all future uses of the context.</para>
+	  <para>Important notes are marked up using the <sgmltag class="element">important</sgmltag> 
+	        element. The <sgmltag 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>
+	<section id="tip">
+	  <title>Tips</title>
+	  <para>Tips are bits of information that may help a user be more productive, but that are not 
+	        critical to using the product. In general, this type of information should either be 
+			worked directly into the text or placed in a <link linkend="note">note</link>.</para>
+	  <para>Tips are marked up using the <sgmltag class="element">tip</sgmltag> element. The 
+	        <sgmltag 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>
+  </section>
 </chapter>

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/admon.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

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?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml Fri Aug 25 06:16:36 2006
@@ -1,163 +1,163 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter>
-  <title>Elements Excluded from CeltiXfire Documentation</title>
-  <para>The CeliXfire documentation uses a subset of elements defined by Docbook. For 
-        simplification, the following elements are excluded from the set used:</para>
-	<itemizedlist>
-	  <listitem><para><sgmltag class="element">ackno</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">acronym</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">address</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">affiliation</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">appendixinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">artpagenums</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">audiodata</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">audioobject</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">authorblurb</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">beginpage</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliocoverage</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliodiv</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">biblioentry</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliography</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliographyinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">biblioid</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliolist</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliomisc</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliomixed</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliomset</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">biblioref</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliorelation</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">biblioset</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bibliosource</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">blockinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">blockquote</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">book</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bookinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bridgehead</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">chapter</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">chapterinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">citation</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">citebiblioid</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">citerefentry</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">citetitle</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">city</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">collab</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">collabname</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">colophone</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">confdates</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">confgroup</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">conftitle</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">contractnum</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">contractsponsor</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">corpauthor</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">corpname</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">country</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">dedication</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">fax</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">firstname</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">formalpara</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">glossaryinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">highlights</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">holder</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">honorific</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">informalequation</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">inlineequation</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">invpartnumber</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">isbn</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">issn</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">issuenum</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">jobtitle</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">lineage</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">manvolnum</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">modespec</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">olink</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">bridgehead</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">orgdiv</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">orgname</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">otheraddr</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">pagenums</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">part</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">partinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">partintro</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">personblurb</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">personname</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">phone</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">pob</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">postcode</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">preface</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">prefaceinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">primary</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">primaryie</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">printhistory</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">productnumber</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">publisher</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">publishername</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">pubsnumber</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsect1</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsect1info</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsect2</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsect2info</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsect3</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsect3info</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsectioninfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsynopsisdiv</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">refsynopsisdivinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">releaseinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">remark</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">revdescription</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">revhistory</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">revision</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">screeninfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">secondary</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">secondaryie</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect1</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect1info</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect2</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect2info</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect3</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect3info</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect4</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect4info</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect5</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sect5info</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sectioninfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">see</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">seealso</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">seealsoie</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">seeie</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">seg</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">seglistitem</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">segmentedlist</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">segtitle</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">seriesvolnums</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">set</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">setindex</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">setindexinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">setinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">shortaffil</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sidebar</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">sidebarinfo</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">simpara</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">simplesect</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">state</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">street</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">surname</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">tertiary</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">tertiearyie</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">titleabbrev</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">toc</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">tocback</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">tocchap</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">tocentry</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">tocfront</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">toclevel1</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">toclevel2</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">toclevel3</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">toclevel4</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">toclevel5</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">tocpart</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">videodata</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">videoobject</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">volumenum</sgmltag></para></listitem>
-	  <listitem><para><sgmltag class="element">year</sgmltag></para></listitem>
-    </itemizedlist>
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter>
+  <title>Elements Excluded from CeltiXfire Documentation</title>
+  <para>The CeliXfire documentation uses a subset of elements defined by Docbook. For 
+        simplification, the following elements are excluded from the set used:</para>
+	<itemizedlist>
+	  <listitem><para><sgmltag class="element">ackno</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">acronym</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">address</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">affiliation</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">appendixinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">artpagenums</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">audiodata</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">audioobject</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">authorblurb</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">beginpage</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliocoverage</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliodiv</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">biblioentry</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliography</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliographyinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">biblioid</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliolist</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliomisc</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliomixed</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliomset</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">biblioref</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliorelation</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">biblioset</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bibliosource</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">blockinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">blockquote</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">book</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bookinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bridgehead</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">chapter</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">chapterinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">citation</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">citebiblioid</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">citerefentry</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">citetitle</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">city</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">collab</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">collabname</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">colophone</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">confdates</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">confgroup</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">conftitle</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">contractnum</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">contractsponsor</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">corpauthor</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">corpname</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">country</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">dedication</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">fax</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">firstname</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">formalpara</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">glossaryinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">highlights</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">holder</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">honorific</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">informalequation</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">inlineequation</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">invpartnumber</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">isbn</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">issn</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">issuenum</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">jobtitle</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">lineage</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">manvolnum</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">modespec</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">olink</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">bridgehead</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">orgdiv</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">orgname</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">otheraddr</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">pagenums</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">part</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">partinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">partintro</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">personblurb</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">personname</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">phone</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">pob</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">postcode</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">preface</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">prefaceinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">primary</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">primaryie</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">printhistory</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">productnumber</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">publisher</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">publishername</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">pubsnumber</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsect1</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsect1info</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsect2</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsect2info</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsect3</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsect3info</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsectioninfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsynopsisdiv</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">refsynopsisdivinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">releaseinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">remark</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">revdescription</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">revhistory</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">revision</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">screeninfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">secondary</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">secondaryie</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect1</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect1info</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect2</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect2info</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect3</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect3info</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect4</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect4info</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect5</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sect5info</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sectioninfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">see</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">seealso</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">seealsoie</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">seeie</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">seg</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">seglistitem</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">segmentedlist</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">segtitle</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">seriesvolnums</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">set</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">setindex</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">setindexinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">setinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">shortaffil</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sidebar</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">sidebarinfo</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">simpara</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">simplesect</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">state</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">street</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">surname</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">tertiary</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">tertiearyie</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">titleabbrev</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">toc</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">tocback</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">tocchap</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">tocentry</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">tocfront</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">toclevel1</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">toclevel2</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">toclevel3</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">toclevel4</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">toclevel5</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">tocpart</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">videodata</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">videoobject</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">volumenum</sgmltag></para></listitem>
+	  <listitem><para><sgmltag class="element">year</sgmltag></para></listitem>
+    </itemizedlist>
 </chapter>

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/exclude.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/figures.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/figures.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/figures.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Modified: incubator/cxf/trunk/docs/src/docs/styleguide/general.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/docs/styleguide/general.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/docs/styleguide/general.xml (original)
+++ incubator/cxf/trunk/docs/src/docs/styleguide/general.xml Fri Aug 25 06:16:36 2006
@@ -1,30 +1,30 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter>
-  <title>Genral Elements and Other Elements not Discussed Elsewhere</title>
-  <section>
-    <title>Overview</title>
-	<para>Since Docbook was defined to describe a wide range of publishable content, it includes 
-	      a number of elements that are used to perform common tasks. These elements include ones 
-		  that specify superscripts and emphasis.</para>
-	<para>It also includes a number of elements that you are unlikely to need when documenting 
-	      CeltiXfire. Among these elements are a large set used to define GUI elements. These 
-		  elements are legal in the CeltiXfire documentation. However, they are not used enough to 
-		  mertit a full discussion.</para>
-  </section>
-  <section>
-    <title>Formating Elements</title>
-	<para>The following are common formating elements used in Docbook:</para>
-	<segmentedlist>
-	  <segtitle>Element</segtitle>
-	  <segtitle>Description</segtitle>
-	  <seglistitem>
-	    <seg><sgmltag class="element">emphasis</sgmltag></seg>
-		<seg>Specifies that the content of the element is to be empasized by either 
-		     <emphasis>itallics</emphasis> or <emphasis role="strong">boldface</emphasis>. The 
-			 default is to use itallics. You specify boldface by setting the 
-			 <sgmltag class="attribute">role</sgmltag> attribute to 
-			 <sgmltag class="attrvalue">strong</sgmltag>.</seg>
-	  </seglistitem>
-    </segmentedlist>
-  </section>	
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter>
+  <title>Genral Elements and Other Elements not Discussed Elsewhere</title>
+  <section>
+    <title>Overview</title>
+	<para>Since Docbook was defined to describe a wide range of publishable content, it includes 
+	      a number of elements that are used to perform common tasks. These elements include ones 
+		  that specify superscripts and emphasis.</para>
+	<para>It also includes a number of elements that you are unlikely to need when documenting 
+	      CeltiXfire. Among these elements are a large set used to define GUI elements. These 
+		  elements are legal in the CeltiXfire documentation. However, they are not used enough to 
+		  mertit a full discussion.</para>
+  </section>
+  <section>
+    <title>Formating Elements</title>
+	<para>The following are common formating elements used in Docbook:</para>
+	<segmentedlist>
+	  <segtitle>Element</segtitle>
+	  <segtitle>Description</segtitle>
+	  <seglistitem>
+	    <seg><sgmltag class="element">emphasis</sgmltag></seg>
+		<seg>Specifies that the content of the element is to be empasized by either 
+		     <emphasis>itallics</emphasis> or <emphasis role="strong">boldface</emphasis>. The 
+			 default is to use itallics. You specify boldface by setting the 
+			 <sgmltag class="attribute">role</sgmltag> attribute to 
+			 <sgmltag class="attrvalue">strong</sgmltag>.</seg>
+	  </seglistitem>
+    </segmentedlist>
+  </section>	
 </chapter>

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/general.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/general.xml
------------------------------------------------------------------------------
    svn:keywords = Rev Date

Propchange: incubator/cxf/trunk/docs/src/docs/styleguide/general.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml



Mime
View raw message