andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Preparing to write some real guide ...

Browse Source
This commit is contained in:
Trustin Lee 2008-09-10 12:37:58 +00:00
parent b14b4c8714
commit 77b23c97e2
20 changed files with 63 additions and 5647 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
pom.xml
View File

@ -267,11 +267,6 @@
</includes> </includes>
</imageResource> </imageResource>
<formats> <formats>
<format>
<formatName>pdf</formatName>
<stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
<finalName>${project.artifactId}.pdf</finalName>
</format>
<format> <format>
<formatName>html</formatName> <formatName>html</formatName>
<stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource> <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>

1017
src/docbook/image/build.graffle
View File

File diff suppressed because it is too large Load Diff

BIN
src/docbook/image/build.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 48 KiB

1183
src/docbook/image/docbook-dir.graffle
View File

File diff suppressed because it is too large Load Diff

BIN
src/docbook/image/docbook-dir.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 45 KiB

1658
src/docbook/image/messaging-docs.graffle
View File

File diff suppressed because it is too large Load Diff

BIN
src/docbook/image/messaging-docs.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 60 KiB

1509
src/docbook/image/target-dir.graffle
View File

File diff suppressed because it is too large Load Diff

BIN
src/docbook/image/target-dir.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 56 KiB

59
src/docbook/master.xml
View File

@ -1,45 +1,32 @@
<?xml version='1.0' encoding='ISO-8859-1'?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" "../support/support/docbook-dtd/docbookx.dtd" [ <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" "../support/support/docbook-dtd/docbookx.dtd" [
<!ENTITY introduction SYSTEM "module/introduction.xml"> <!ENTITY introduction SYSTEM "module/introduction.xml">
<!ENTITY howto SYSTEM "module/howto.xml"> <!ENTITY architecture SYSTEM "module/architecture.xml">
<!ENTITY styles SYSTEM "module/styles.xml"> <!ENTITY codec SYSTEM "module/codec.xml">
<!ENTITY threading SYSTEM "module/threading.xml">
<!ENTITY security SYSTEM "module/security.xml">
<!ENTITY transport SYSTEM "module/transport.xml">
<!ENTITY appendix SYSTEM "module/appendix.xml">
]> ]>
<book lang="en"> <book lang="en">
<bookinfo> <bookinfo>
<title>How to use the JBoss DocBook system</title> <title>The Netty Project 3.0 User Guide</title>
<subtitle>A guide for content developers</subtitle> <subtitle>The proven approach for rapid network application development</subtitle>
<releaseinfo>2.0</releaseinfo> <releaseinfo>$Rev$, $Date$</releaseinfo>
</bookinfo> </bookinfo>
<toc/> <toc/>
<preface id="target" revision="1">
<title>Target Audience</title> <preface id="preface">
<para>All JBoss.org documentation content developers and style developers
should read this document. You should also read this if you want to
build JBoss.org DocBooks from the <ulink url="http://anonsvn.jboss.org">public SVN repositories</ulink>. </para>
</preface>
<preface id="preface" revision="1">
<title>Preface</title> <title>Preface</title>
<para>This document introduces the unified DocBook system for JBoss.org <para>To be written...</para>
documentation based on Maven2. Using this system provides the following benefits:</para>
<itemizedlist>
<listitem>
<para>The DocBook libraries and all other dependencies are stored in Maven plugins located in the <ulink url="http://repository.jboss.org/maven2">JBoss public maven repository</ulink>. This allows the entire build environment to be automatically downloaded and configured from just a single <literal>pom.xml</literal> file stored in a project&apos;s <literal>docs</literal> directory.</para>
</listitem>
<listitem>
<para>Styles are also stored in Maven plugins so that they can be managed from a central location. This allows updates to be automatically downloaded when new designs are created or bugs are fixed.</para>
</listitem>
<listitem>
<para>It provides a default style based on the JBoss.org community-driven theme that looks clean, fresh and modern.</para>
</listitem>
<listitem>
<para>Custom styles can easily be created for individual projects, or groups of related projects, to cater for different requirements. For example some projects may have their own logos or wish to have collapsable menus at the start of each chapter. </para>
</listitem>
<listitem>
<para>The build process is simplified and standardized. Just
follow the instructions in this guide to setup your <literal>docs</literal>
directory and copy a very simple <literal>pom.xml</literal> file. </para>
</listitem>
</itemizedlist>
<para> If you have any questions, please feel free to contact <ulink url="mailto:mark.newton@jboss.org">Mark Newton</ulink> (Content Lead) for more information. </para>
</preface> </preface>
&introduction;&howto;&styles;</book>
&introduction;
&architecture;
&codec;
&threading;
&securty;
&transport;
&appendix;
</book>

5
src/docbook/module/appendix.xml Normal file
View File

@ -0,0 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="appendix">
<title>Additional Resources</title>
<para>To be written...</para>
</chapter>

5
src/docbook/module/architecture.xml Normal file
View File

@ -0,0 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="architecture">
<title>Architecture &amp; Road Map</title>
<para>To be written...</para>
</chapter>

5
src/docbook/module/codec.xml Normal file
View File

@ -0,0 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="codec">
<title>Encoders and Decoders</title>
<para>To be written...</para>
</chapter>

179
src/docbook/module/howto.xml
View File

@ -1,179 +0,0 @@
<?xml version='1.0' encoding='UTF-8'?><chapter id="howto">
<title>How to develop content for JBoss DocBook</title>
<section>
<title>Install Maven2</title>
<para>Before you can start to build DocBook documents you first need to install and configure <ulink url="http://maven.apache.org/">Maven2</ulink>. At the time of writing Maven 2.0.8 is the latest released version that has been tested and found to work correctly. System requirements and download instructions can be found <ulink url="http://maven.apache.org/download.html">here</ulink>.</para>
<para>In order for Maven to reference the JBoss public maven repository you will need to create a <literal>~/.m2/settings.xml</literal> file with the following contents:</para>
<programlisting>&lt;settings&gt;
&lt;profiles&gt;
&lt;profile&gt;
&lt;id&gt;jboss.repository&lt;/id&gt;
&lt;activation&gt;
&lt;property&gt;
&lt;name&gt;!jboss.repository.off&lt;/name&gt;
&lt;/property&gt;
&lt;/activation&gt;
&lt;repositories&gt;
&lt;repository&gt;
&lt;id&gt;snapshots.jboss.org&lt;/id&gt;
&lt;url&gt;http://snapshots.jboss.org/maven2&lt;/url&gt;
&lt;snapshots&gt;
&lt;enabled&gt;true&lt;/enabled&gt;
&lt;/snapshots&gt;
&lt;/repository&gt;
&lt;repository&gt;
&lt;id&gt;repository.jboss.org&lt;/id&gt;
&lt;url&gt;http://repository.jboss.org/maven2&lt;/url&gt;
&lt;snapshots&gt;
&lt;enabled&gt;false&lt;/enabled&gt;
&lt;/snapshots&gt;
&lt;/repository&gt;
&lt;/repositories&gt;
&lt;pluginRepositories&gt;
&lt;pluginRepository&gt;
&lt;id&gt;repository.jboss.org&lt;/id&gt;
&lt;url&gt;http://repository.jboss.org/maven2&lt;/url&gt;
&lt;snapshots&gt;
&lt;enabled&gt;false&lt;/enabled&gt;
&lt;/snapshots&gt;
&lt;/pluginRepository&gt;
&lt;pluginRepository&gt;
&lt;id&gt;snapshots.jboss.org&lt;/id&gt;
&lt;url&gt;http://snapshots.jboss.org/maven2&lt;/url&gt;
&lt;snapshots&gt;
&lt;enabled&gt;true&lt;/enabled&gt;
&lt;/snapshots&gt;
&lt;/pluginRepository&gt;
&lt;/pluginRepositories&gt;
&lt;/profile&gt;
&lt;/profiles&gt;
&lt;/settings&gt;</programlisting>
<para>If you already have a <literal>~/.m2/settings.xml</literal> file then you simply need to add the above <literal>&lt;profile&gt;</literal> element to your <literal>&lt;profiles&gt;</literal>.</para>
</section>
<section>
<title>Setup the directories</title>
<para>Each JBoss.org project stores its documentation in a <literal>docs</literal> directory, typically located at <literal>&lt;projectName&gt;/trunk/docs</literal>. By convention the source for each DocBook should be placed into subdirectories directly beneath this. For example, the DocBook source for a project&apos;s User Guide should be placed in
<literal>&lt;projectName&gt;/trunk/docs/userguide</literal> whilst the DocBook source for a Reference Guide should be placed in <literal>&lt;projectName&gt;/trunk/docs/reference</literal>. Alongside these DocBook subdirectories any number
of other subdirectories containing API references, code examples, and articles may also be created.</para>
<para>For example the
docs directory for the JBoss Messaging
project is shown in <xref linkend="aop.fig"/>. </para>
<figure id="aop.fig">
<title>The JBoss Messaging docs directory</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="image/messaging-docs.png"/>
</imageobject>
</mediaobject>
</figure>
<para>To facilitate translation into other languages the original source of a DocBook is written in English and located in a directory named <literal>en</literal>. Within this there are typically two subdirectories for the content:</para>
<itemizedlist>
<listitem>
<para><literal>images </literal>- stores images</para>
</listitem>
<listitem>
<para> <literal>modules</literal> - stores DocBook
text modules, usually one per chapter</para>
</listitem>
</itemizedlist>
<para>The <literal>master.xml</literal> file contains the top-level <literal>&lt;book&gt;</literal> element and is used to group all of the other text modules together. If you choose to use Ant to perform the build then a <literal>build.xml</literal> file is used to call the relevant tasks. Otherwise a <literal>pom.xml</literal> file can be called using Maven2.</para>
<para>The easiest way to
setup a DocBook subdirectory within your project is to copy the
<literal>
<ulink url="http://anonsvn.jboss.org/repos/jbossas/trunk/docbook-support/docs/guide/">docbook-support/docs/guide</ulink>
</literal> directory (containing the DocBook source for this guide) and use it as a template. </para>
</section>
<section>
<title>Author the content</title>
<para>Now you can write your content in DocBook format. Make sure that
the master file of your DocBook (i.e. the file that contains the
<literal>&lt;book&gt;</literal> element) is called
<literal>master.xml</literal> and lives directly under the <literal>en</literal>
directory (see <xref linkend="aop.fig"/>). You can either put the
entire content in <literal>master.xml</literal> or divide up the
chapters and place them in the <literal>modules/</literal>
directory. If you do the latter, you should reference the chapter
files from the <literal>master.xml</literal> file via entity
references. Please see the
<literal>
<ulink url="http://anonsvn.jboss.org/repos/jbossas/trunk/docbook-support/docs/guide/en/master.xml">docbook-support/docs/guide/en/master.xml</ulink>
</literal> file to
see how this is done. </para>
</section>
<section>
<title>Build the documents</title>
<para>To perform a build using Maven you simply need to enter the following commands from the directory containing the <literal>pom.xml</literal> file:</para>
<itemizedlist>
<listitem>
<para><command>mvn compile</command> - processes the DocBook source using the XSL stylesheets</para>
</listitem>
<listitem>
<para><command>mvn package</command> - creates WAR archives containing the various output formats</para>
</listitem>
<listitem>
<para><command>mvn clean</command> - removes the target directory containing the build output</para>
</listitem>
</itemizedlist>
<para>It is also possible to chain commands together if required. e.g. <command>mvn clean compile</command></para>
<para>Once the <literal>compile</literal> or <literal>package</literal> goals have been reached then a <literal>target/</literal> directory will be created containing the build output.</para>
<figure>
<title>The JBoss Messaging target directory</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="image/target-dir.png"/>
</imageobject>
</mediaobject>
</figure>
<para>The <literal>attach</literal> directory contains WAR archives that package together all of the files for the various output formats. The intention is that these can be easily deployed into a web server such as Tomcat or JBoss AS.</para>
<para>The <literal>docbook</literal> directory contains a number of subdirectories; one per output format. This is where you will find the XHTML, PDF and Eclipse Help files.</para>
<para>The <literal>staging</literal> directory contains resources such as CSS files, images and fonts that are needed for the final output. They need to be placed into this directory during the build as the DocBook XSL stylesheets can only reference a single location for images. Similarly the FOP libraries can only reference a single location for fonts.</para>
</section>
<section>
<title>Migrating from Ant </title>
<para>Previously the JBoss DocBook system used Ant to perform builds. This meant that each DocBook subdirectory contained a <literal>build.xml </literal>file as follows:</para>
<programlisting>
&lt;project name=&quot;Documentation&quot; default=&quot;all.doc&quot; basedir=&quot;.&quot;&gt;
&lt;property name=&quot;pdf.name&quot; value=&quot;jboss-mybook.pdf&quot; /&gt;
&lt;import file=&quot;../../../docbook-support/support.xml&quot; /&gt;
&lt;target name=&quot;all.doc&quot; depends=&quot;clean&quot;&gt;
&lt;antcall target=&quot;lang.all&quot;&gt;
&lt;param name=&quot;lang&quot; value=&quot;en&quot;/&gt;
&lt;/antcall&gt;
&lt;/target&gt;
&lt;/project&gt;
</programlisting>
<para>The idea was for this file to delegate most of the work to a
<literal>support.xml</literal> file maintained by the
<literal>
<ulink url="http://anonsvn.jboss.org/repos/jbossas/trunk/docbook-support/">docbook-support</ulink>
</literal> project. Developers were supposed to check out the <literal>docbook-support</literal> project alongside their own project in order to reference this file together with the associated libraries and XSL stylesheets. However what usually happened was that the contents of the <literal>docbook-support</literal> project were copied into each project&apos;s SVN tree. This meant that projects ended up having to maintain their own DocBook build systems and any changes made to the <literal>docbook-support</literal> project would have to be manually synchronised with their own copy.</para>
<para>With the new Maven2 based system this is no longer an issue as Maven takes care of downloading dependencies automatically. As a result all of the build environment can now be centrally maintained by the Content Team as a set of Maven plugins. You are free to continue using Ant if you prefer but since you won&apos;t be using the Maven plugins you will have to maintain any DocBook libraries, XSL stylesheets and CSS files copied or referenced from the <literal>docbook-support</literal> project yourself.</para>
<para>To perform the build using Ant simply enter the <command>ant</command> command from the directory containing the <literal>build.xml</literal> file. After it is finished, you should have three output documents in the following places:</para>
<itemizedlist>
<listitem>
<para>The <literal>build/en/html </literal>directory contains
the HTML version of the document. Each chapter is broken into a
separate HTML file and they are linked together by an
<literal>index.html</literal> file.</para>
</listitem>
<listitem>
<para>The <literal>build/en/html_single</literal> directory
contains a single <literal>index.html</literal> file which holds
the entire document. </para>
</listitem>
<listitem>
<para>The <literal>build/en/pdf</literal> directory contains
the PDF version of the document. </para>
</listitem>
</itemizedlist>
<note>
<para>The HTML output created by Ant is not XHTML. If you wish to gaurantee the separation of content and style then Maven2 should be used instead to produce strict XHTML.</para>
</note>
<para>If you wish to migrate from Ant to Maven then all you need to do is copy the <literal>
<ulink url="http://anonsvn.jboss.org/repos/jbossas/trunk/docbook-support/docs/guide/pom.xml">docbook-support/docs/guide/pom.xml</ulink>
</literal> file to your own DocBook subdirectory (alongside the <literal>build.xml</literal> file) and then follow the instructions in the previous section. You can then delete the <literal>build.xml</literal> file as it&apos;s not longer needed.</para>
</section>
</chapter>

28
src/docbook/module/introduction.xml
View File

@ -1,25 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?><chapter id="introduction"> <?xml version="1.0" encoding="UTF-8"?>
<title>Introduction to DocBook processing</title> <chapter id="introduction">
<para>DocBook is an XML format for writing documents. It allows the author to <title>Introduction</title>
focus on the content itself during the writing process instead of <para>To be written...</para>
worrying about the presentation. </para>
<para>Using standard DocBook tags, we can tag the content according to
its syntatic structure. The DocBook document is then processed using
XSL stylesheets so that each tagged DocBook element is transformed to a
corresponding element in the target output format. For example each &lt;para&gt;&lt;/para&gt; element in DocBook could be transformed into a &lt;p&gt;&lt;/p&gt; element in XHTML. </para>
<para>Using different XSL stylesheets, we can generate different
output formats. For example, we can generate both XHTML and PDF outputs from
a single DocBook source. We can also generate multiple versions of XHTML
(or PDF) files each with a different style if necessary.</para>
<para>In the JBoss DocBook system, we provide XSL stylesheets to build XHTML, PDF and Eclipse Help output formats from the DocBook source. The build process is
illustrated in <xref linkend="build.fig"/>. </para>
<figure id="build.fig">
<title>The DocBook build process </title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="image/build.png"/>
</imageobject>
</mediaobject>
</figure>
<para>XHTML is used instead of HTML as it ensures that the content is completely separated from its style using Cascading Style Sheets (CSS) and image files.</para>
</chapter> </chapter>

5
src/docbook/module/security.xml Normal file
View File

@ -0,0 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="security">
<title>Securing the Wire</title>
<para>To be written...</para>
</chapter>

35
src/docbook/module/styles.xml
View File

@ -1,35 +0,0 @@
<?xml version='1.0' encoding='UTF-8'?><chapter id="styles">
<title>Maintaining the JBoss DocBook system</title>
<para>The structure of the <literal>
<ulink url="http://anonsvn.jboss.org/repos/jbossas/trunk/docbook-support/">docbook-support</ulink>
</literal> project is
illustrated in <xref linkend="docbook.fig"/>. The contents are as follows:</para>
<figure id="docbook.fig">
<title>The docbook-support project </title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="image/docbook-dir.png"/>
</imageobject>
</mediaobject>
</figure>
<itemizedlist>
<listitem>
<para>The <literal>docs</literal> directory contains the DocBook source for this guide to
serve as a template for other projects. </para>
</listitem>
<listitem>
<para>The <literal>jbossorg-documentation</literal> directory contains the maven plugin source for the parent POM that is referenced by each project&apos;s <literal>pom.xml</literal> file. The parent POM contains common configuration information so that it does not have to be duplicated across multiple JBoss.org projects.</para>
</listitem>
<listitem>
<para>The <literal>jbossorg-docbook-xslt</literal> directory contains the maven plugin source for the default JBoss.org XSL stylesheets. These stylesheets produce XHTML, PDF and Eclipse Help output.</para>
</listitem>
<listitem>
<para>The <literal>jbossorg-jdocbook-style</literal> directory contains the maven plugin source for the default JBoss.org CSS and image files. These provide the JBoss.org community-driven look &amp; feel.</para>
</listitem>
<listitem>
<para>The <literal>styles</literal> and <literal>support</literal> directories together with the <literal>support.xml</literal> file are provided for backwards compatibility with projects that wish to continue using Ant instead of Maven. The <literal>styles</literal> directory contains XSL stylesheets together with CSS files to produce HTML and PDF outputs. The <literal>support</literal> directory contains the DocBook
libraries and DTDs along with
the standard XSL stylesheets. The <literal>support.xml</literal> file contains common Ant tasks to perform the build.</para>
</listitem>
</itemizedlist>
</chapter>

5
src/docbook/module/template.xml Normal file
View File

@ -0,0 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="chapter-id">
<title>Chapter title</title>
<para>To be written...</para>
</chapter>

5
src/docbook/module/threading.xml Normal file
View File

@ -0,0 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="threading">
<title>Threading</title>
<para>To be written...</para>
</chapter>

5
src/docbook/module/transport.xml Normal file
View File

@ -0,0 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="transport">
<title>Transports</title>
<para>To be written...</para>
</chapter>