[dna-commits] DNA SVN: r389 - trunk/docs/reference/en.
dna-commits at lists.jboss.org
dna-commits at lists.jboss.org
Wed Aug 6 12:39:00 EDT 2008
Author: rhauch
Date: 2008-08-06 12:39:00 -0400 (Wed, 06 Aug 2008)
New Revision: 389
Modified:
trunk/docs/reference/en/master.xml
Log:
DNA-71 - Document development tools and environment
http://jira.jboss.com/jira/browse/DNA-71
Added to the Reference Guide a placeholder for a chapter about development tools and development environment. Formatted DocBook source file.
Modified: trunk/docs/reference/en/master.xml
===================================================================
--- trunk/docs/reference/en/master.xml 2008-08-06 16:31:28 UTC (rev 388)
+++ trunk/docs/reference/en/master.xml 2008-08-06 16:39:00 UTC (rev 389)
@@ -1,25 +1,14 @@
-<!--
- ~ JBoss, Home of Professional Open Source.
- ~
- ~ Copyright (c) 2008, Red Hat Middleware LLC or third-party contributors as
- ~ indicated by the @author tags or express copyright attribution
- ~ statements applied by the authors. All third-party contributions are
- ~ distributed under license by Red Hat Middleware LLC.
- ~
- ~ This copyrighted material is made available to anyone wishing to use, modify,
- ~ copy, or redistribute it subject to the terms and conditions of the GNU
- ~ Lesser General Public License, as published by the Free Software Foundation.
- ~
- ~ This program is distributed in the hope that it will be useful,
- ~ but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
- ~ or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License
- ~ for more details.
- ~
- ~ You should have received a copy of the GNU Lesser General Public License
- ~ along with this distribution; if not, write to:
- ~ Free Software Foundation, Inc.
- ~ 51 Franklin Street, Fifth Floor
- ~ Boston, MA 02110-1301 USA
+
+ <!--
+ ~ JBoss, Home of Professional Open Source. ~ ~ Copyright (c) 2008, Red Hat Middleware LLC or third-party contributors as ~
+ indicated by the @author tags or express copyright attribution ~ statements applied by the authors. All third-party
+ contributions are ~ distributed under license by Red Hat Middleware LLC. ~ ~ This copyrighted material is made available to
+ anyone wishing to use, modify, ~ copy, or redistribute it subject to the terms and conditions of the GNU ~ Lesser General
+ Public License, as published by the Free Software Foundation. ~ ~ This program is distributed in the hope that it will be
+ useful, ~ but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY ~ or FITNESS FOR A PARTICULAR
+ PURPOSE. See the GNU Lesser General Public License ~ for more details. ~ ~ You should have received a copy of the GNU Lesser
+ General Public License ~ along with this distribution; if not, write to: ~ Free Software Foundation, Inc. ~ 51 Franklin
+ Street, Fifth Floor ~ Boston, MA 02110-1301 USA
-->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
<!ENTITY % RH-ENTITIES SYSTEM "Common_Config/rh-entities.ent">
@@ -57,10 +46,13 @@
</bookinfo>
<preface id="preface" revision="1">
<title>Target audience</title>
- <para>This guide is for the developers of JBoss DNA and those users that want to have a better understanding of
- how JBoss DNA works or how to extend the functionality. For a higher-level introduction to JBoss DNA, see
- the <ulink url="http://www.jboss.org/file-access/default/members/dna/freezone/docs/0.2/manuals/gettingstarted/html/index.html">Getting Started</ulink> document.</para>
<para>
+ This guide is for the developers of JBoss DNA and those users that want to have a better understanding of how JBoss DNA
+ works or how to extend the functionality. For a higher-level introduction to JBoss DNA, see the
+ <ulink url="http://www.jboss.org/file-access/default/members/dna/freezone/docs/0.2/manuals/gettingstarted/html/index.html">Getting Started</ulink>
+ document.
+ </para>
+ <para>
If you have any questions or comments, please feel free to contact JBoss DNA's
<ulink url="mailto:dna-users at jboss.org">user mailing list</ulink>
or use the
@@ -75,9 +67,9 @@
same thing.
</para>
</preface>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
+ <!--
+ ====================================== Chapter ===============================================
+ -->
<chapter id="introduction">
<title>Introduction to JBoss DNA</title>
<para>There are a lot of choices for how applications can store information persistently so that it can be accessed at a
@@ -159,84 +151,105 @@
</para>
<sect1 id="roadmap">
<title>Project roadmap</title>
- <para>The roadmap for JBoss DNA is managed in the project's <ulink url="https://jira.jboss.org/jira/browse/DNA">JIRA instance</ulink>.
- The roadmap shows the different tasks, requirements, issues and other activities that have been targeted to each of the upcoming releases.
- (The <ulink url="https://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira.plugin.system.project:roadmap-panel">roadmap report</ulink>
- always shows the next three releases.)</para>
- <para>By convention, JIRA issues not immediately targeted to a release will be reviewed periodically to determine the appropriate release
- where they can be targeted. Any issue that is reviewed and that does not fit in a known release will be targeted to the
- <ulink url="https://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira.plugin.system.project:roadmap-panel">Future Releases</ulink>
- bucket. This should be reviewed periodically and at least at the beginning of each release cycle, with the goal of targeting most
- of the issues to specific releases.</para>
- </sect1>
+ <para>
+ The roadmap for JBoss DNA is managed in the project's
+ <ulink url="https://jira.jboss.org/jira/browse/DNA">JIRA instance</ulink>
+ . The roadmap shows the different tasks, requirements, issues and other activities that have been targeted to each of the
+ upcoming releases. (The
+ <ulink url="https://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira.plugin.system.project:roadmap-panel">roadmap report</ulink>
+ always shows the next three releases.)
+ </para>
+ <para>
+ By convention, JIRA issues not immediately targeted to a release will be reviewed periodically to determine the
+ appropriate release where they can be targeted. Any issue that is reviewed and that does not fit in a known release will
+ be targeted to the
+ <ulink url="https://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira.plugin.system.project:roadmap-panel">Future Releases</ulink>
+ bucket. This should be reviewed periodically and at least at the beginning of each release cycle, with the goal of
+ targeting most of the issues to specific releases.
+ </para>
+ </sect1>
<sect1 id="modules">
<title>JBoss DNA modules</title>
- <para>JBoss DNA consists of the following modules:
- <itemizedlist>
+ <para>
+ JBoss DNA consists of the following modules:
+ <itemizedlist>
<listitem>
<para>
<emphasis role="strong">dna-common</emphasis>
- is a low-level library of common utilities and frameworks, including logging, progress monitoring, internationalization/localization,
- text translators, component management, and class loader factories.
+ is a low-level library of common utilities and frameworks, including logging, progress monitoring,
+ internationalization/localization, text translators, component management, and class loader factories.
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">dna-spi</emphasis>
- defines the Service Provider Interface (SPI) for DNA, including the repository connectors, sequencers, graph interfaces, and MIME type detectors.
+ defines the Service Provider Interface (SPI) for DNA, including the repository connectors, sequencers, graph
+ interfaces, and MIME type detectors.
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">dna-repository</emphasis>
- is the main module and provides the repository-oriented services, including the Repository Service, Sequencing Service, Observation Service, and Rules Service.
+ is the main module and provides the repository-oriented services, including the Repository Service, Sequencing
+ Service, Observation Service, and Rules Service.
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">dna-jcr</emphasis>
- provides the JBoss DNA implementation of the JCR API, which relies upon a repository connector, such as the Federation Connector
- (see <code>dna-connector-federation</code>).
+ provides the JBoss DNA implementation of the JCR API, which relies upon a repository connector, such as the
+ Federation Connector (see
+ <code>dna-connector-federation</code>
+ ).
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">dna-integration-tests</emphasis>
- provides a home for all of the integration tests that involve more components that just unit tests. Integration tests
- are often more complicated, take longer, and involve testing the integration and functionality of many components
- (whereas unit tests focus on testing a single class or component and may use stubs or mock objects for other components).
- </para>
+ provides a home for all of the integration tests that involve more components that just unit tests. Integration
+ tests are often more complicated, take longer, and involve testing the integration and functionality of many
+ components (whereas unit tests focus on testing a single class or component and may use stubs or mock objects for
+ other components).
+ </para>
</listitem>
- </itemizedlist>
- The following modules are optional extensions that may be used selectively and as needed
- (and are located in the source under the <code>extensions</code> directory):
- <itemizedlist>
+ </itemizedlist>
+ The following modules are optional extensions that may be used selectively and as needed (and are located in the source
+ under the
+ <code>extensions</code>
+ directory):
+ <itemizedlist>
<listitem>
<para>
<emphasis role="strong">dna-maven-classloader</emphasis>
- is a small library that provides a <code>ClassLoaderFactory</code> implementation that can create <code>java.lang.ClassLoader</code> instances capable of loading
- classes given a Maven Repository and a list of Maven coordinates. The Maven Repository can be managed within a JCR repository.
+ is a small library that provides a
+ <code>ClassLoaderFactory</code>
+ implementation that can create
+ <code>java.lang.ClassLoader</code>
+ instances capable of loading classes given a Maven Repository and a list of Maven coordinates. The Maven Repository
+ can be managed within a JCR repository.
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">dna-connector-federation</emphasis>
- is a DNA repository connector that federates, integrates and caches information from multiple sources (via other repository connectors).
+ is a DNA repository connector that federates, integrates and caches information from multiple sources (via other
+ repository connectors).
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">dna-connector-inmemory</emphasis>
- is a simple DNA repository connector that manages content within memory. This can be used as a simple cache or as a transient
- repository.
+ is a simple DNA repository connector that manages content within memory. This can be used as a simple cache or as a
+ transient repository.
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">dna-connector-jbosscache</emphasis>
- is a DNA repository connector that manages content within a <ulink url="http://www.jboss.org/jbosscache/">JBoss Cache</ulink> instance. JBoss Cache is a powerful cache implementation
- that can serve as a distributed cache and that can persist information. The cache instance can be found via JNDI or created and managed
- by the connector.
+ is a DNA repository connector that manages content within a
+ <ulink url="http://www.jboss.org/jbosscache/">JBoss Cache</ulink>
+ instance. JBoss Cache is a powerful cache implementation that can serve as a distributed cache and that can persist
+ information. The cache instance can be found via JNDI or created and managed by the connector.
</para>
</listitem>
<listitem>
@@ -248,7 +261,8 @@
<listitem>
<para>
<emphasis role="strong">dna-sequencer-images</emphasis>
- is a DNA sequencer that extracts the image metadata (e.g., size, date, etc.) from PNG, JPEG, GIF, BMP, PCS, IFF, RAS, PBM, PGM, and PPM image files.
+ is a DNA sequencer that extracts the image metadata (e.g., size, date, etc.) from PNG, JPEG, GIF, BMP, PCS, IFF,
+ RAS, PBM, PGM, and PPM image files.
</para>
</listitem>
<listitem>
@@ -260,15 +274,17 @@
<listitem>
<para>
<emphasis role="strong">dna-sequencer-java</emphasis>
- is a DNA sequencer that extracts the package, class/type, member, documentation, annotations, and other information from
- Java source files.
+ is a DNA sequencer that extracts the package, class/type, member, documentation, annotations, and other information
+ from Java source files.
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">dna-sequencer-msoffice</emphasis>
- is a DNA sequencer that extracts metadata and summary information from <ulink url="http://office.microsoft.com/en-us/">Microsoft Office</ulink> documents. For example, the sequencer
- extracts from a PowerPoint presentation the outline as well as thumbnails of each slide. Microsoft Word and Excel files are also supported.
+ is a DNA sequencer that extracts metadata and summary information from
+ <ulink url="http://office.microsoft.com/en-us/">Microsoft Office</ulink>
+ documents. For example, the sequencer extracts from a PowerPoint presentation the outline as well as thumbnails of
+ each slide. Microsoft Word and Excel files are also supported.
</para>
</listitem>
<listitem>
@@ -280,18 +296,22 @@
<listitem>
<para>
<emphasis role="strong">dna-mimetype-detector-aperture</emphasis>
- is a DNA MIME type detector that uses the <ulink url="http://aperture.sourceforge.net/">Aperture</ulink> library to determine the best MIME type
- from the filename and file contents.
+ is a DNA MIME type detector that uses the
+ <ulink url="http://aperture.sourceforge.net/">Aperture</ulink>
+ library to determine the best MIME type from the filename and file contents.
</para>
</listitem>
- </itemizedlist>
- There are also documentation modules
- (located in the source under the <code>docs</code> directory):
- <itemizedlist>
+ </itemizedlist>
+ There are also documentation modules (located in the source under the
+ <code>docs</code>
+ directory):
+ <itemizedlist>
<listitem>
<para>
<emphasis role="strong">docs-getting-started</emphasis>
- is the project with the <ulink url="http://www.docbook.org/">DocBook</ulink> source for the JBoss DNA Getting Started document.
+ is the project with the
+ <ulink url="http://www.docbook.org/">DocBook</ulink>
+ source for the JBoss DNA Getting Started document.
</para>
</listitem>
<listitem>
@@ -303,52 +323,75 @@
<listitem>
<para>
<emphasis role="strong">docs-reference-guide</emphasis>
- is the project with the <ulink url="http://www.docbook.org/">DocBook</ulink> source for this document, the JBoss DNA Reference Guide document.
+ is the project with the
+ <ulink url="http://www.docbook.org/">DocBook</ulink>
+ source for this document, the JBoss DNA Reference Guide document.
</para>
</listitem>
- </itemizedlist>
- Finally, there is a module that represents the whole JBoss DNA project:
- <itemizedlist>
+ </itemizedlist>
+ Finally, there is a module that represents the whole JBoss DNA project:
+ <itemizedlist>
<listitem>
<para>
<emphasis role="strong">dna</emphasis>
- is the parent project that aggregates all of the other projects and that contains some asset files to create the necessary Maven artifacts during a build.
+ is the parent project that aggregates all of the other projects and that contains some asset files to create the
+ necessary Maven artifacts during a build.
</para>
</listitem>
- </itemizedlist>
- Each of these modules is a Maven project with a group ID of <code>org.jboss.dna</code>. All of these projects correspond to artifacts in the
- <ulink url="http://repository.jboss.com/maven2/">JBoss Maven 2 Repository</ulink>.</para>
- </sect1>
+ </itemizedlist>
+ Each of these modules is a Maven project with a group ID of
+ <code>org.jboss.dna</code>
+ . All of these projects correspond to artifacts in the
+ <ulink url="http://repository.jboss.com/maven2/">JBoss Maven 2 Repository</ulink>
+ .
+ </para>
+ </sect1>
</chapter>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="classloaders">
- <title>Class loaders</title>
- <para></para>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="development-environment">
+ <title>Developer environment and tooling</title>
+ <para>
+ Discuss our use of Maven, Eclipse, coding styles/preferences, SVN, Hudson, etc.
+ </para>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="classloaders">
+ <title>Class loaders</title>
+ <para></para>
<sect1 id="dna-maven-classloader">
<title>Maven Repository class loader</title>
<para></para>
- </sect1>
- </chapter>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="security">
- <title>Security</title>
- <para>JBoss DNA uses the <ulink url="http://java.sun.com/javase/technologies/security/">Java Authentication and Authorization Service (JAAS)</ulink>
- for its security mechanism. This offers the greatest flexibility and power for integrating JBoss DNA into other applications.
- </para>
+ </sect1>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="security">
+ <title>Security</title>
+ <para>
+ JBoss DNA uses the
+ <ulink url="http://java.sun.com/javase/technologies/security/">Java Authentication and Authorization Service (JAAS)</ulink>
+ for its security mechanism. This offers the greatest flexibility and power for integrating JBoss DNA into other
+ applications.
+ </para>
<sect1 id="jboss-security">
<title>JBoss Security</title>
- <para>The <ulink url="http://www.jboss.org/jbosssecurity/">JBoss Security</ulink> provides one of the best and most powerful
- implementations of the JAAS specification - plus it's open source. JBoss Security offers a number of login modules, including:
- <itemizedlist>
+ <para>
+ The
+ <ulink url="http://www.jboss.org/jbosssecurity/">JBoss Security</ulink>
+ provides one of the best and most powerful implementations of the JAAS specification - plus it's open source. JBoss
+ Security offers a number of login modules, including:
+ <itemizedlist>
<listitem>
<para>
<emphasis role="strong">User-Roles Login Module</emphasis>
- is a simple <code>javax.security.auth.login.LoginContext</code> implementation that uses usernames and passwords stored
- in a properties file.
+ is a simple
+ <code>javax.security.auth.login.LoginContext</code>
+ implementation that uses usernames and passwords stored in a properties file.
</para>
</listitem>
<listitem>
@@ -366,13 +409,13 @@
<listitem>
<para>
<emphasis role="strong">LDAP Login Module</emphasis>
- uses an LDAP directory to authenticate principals. Two implementations are available.
+ uses an LDAP directory to authenticate principals. Two implementations are available.
</para>
</listitem>
<listitem>
<para>
<emphasis role="strong">Certificate Login Module</emphasis>
- authenticates using X509 certificates, obtaining roles from either property files or a JDBC database.
+ authenticates using X509 certificates, obtaining roles from either property files or a JDBC database.
</para>
</listitem>
<listitem>
@@ -381,173 +424,184 @@
authenticates using the operating system's mechanism.
</para>
</listitem>
- </itemizedlist>
- and many others.
- </para>
- <para>JBoss Security also provides other capabilities, such as using XACML policies or using federated single sign-on.
- For more detail, see the <ulink url="http://www.jboss.org/jbosssecurity/">JBoss Security</ulink> project.
- </para>
- </sect1>
- </chapter>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="repositories">
- <title>Repositories</title>
- <para></para>
+ </itemizedlist>
+ and many others.
+ </para>
+ <para>
+ JBoss Security also provides other capabilities, such as using XACML policies or using federated single sign-on. For more
+ detail, see the
+ <ulink url="http://www.jboss.org/jbosssecurity/">JBoss Security</ulink>
+ project.
+ </para>
+ </sect1>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="repositories">
+ <title>Repositories</title>
+ <para></para>
<sect1 id="repository-service">
<title>Repository Service</title>
<para></para>
- </sect1>
- <sect1 id="connectors">
- <title>Repository connectors and sources</title>
- <para></para>
- <sect2 id="dna-connector-inmemory">
- <title>In-memory connector</title>
- <para></para>
- </sect2>
- <sect2 id="dna-connector-jbosscache">
- <title>JBoss Cache connector</title>
- <para></para>
- </sect2>
- <sect2 id="dna-connector-federation">
- <title>Federating connector</title>
- <para></para>
- </sect2>
- </sect1>
+ </sect1>
+ <sect1 id="connectors">
+ <title>Repository connectors and sources</title>
+ <para></para>
+ <sect2 id="dna-connector-inmemory">
+ <title>In-memory connector</title>
+ <para></para>
+ </sect2>
+ <sect2 id="dna-connector-jbosscache">
+ <title>JBoss Cache connector</title>
+ <para></para>
+ </sect2>
+ <sect2 id="dna-connector-federation">
+ <title>Federating connector</title>
+ <para></para>
+ </sect2>
+ </sect1>
<sect1 id="custom-connectors">
<title>Writing custom connectors</title>
<para></para>
- </sect1>
- </chapter>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="jcr">
- <title>Content Repositories for Java (JCR)</title>
- <para></para>
+ </sect1>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="jcr">
+ <title>Content Repositories for Java (JCR)</title>
+ <para></para>
<sect1 id="jcr-repositories">
<title>Obtaining JCR repositories</title>
- <para>Discuss how to obtain JCR repository instances (from the Repository Service).
- </para>
- </sect1>
+ <para>Discuss how to obtain JCR repository instances (from the Repository Service).</para>
+ </sect1>
<sect1 id="jcr-sessions">
<title>Creating JCR sessions</title>
- <para>Discuss how to obtain JCR sessions and how the credentials work.
- Also discuss that sessions should be created, used, and closed.
- </para>
- </sect1>
- </chapter>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="sequencing">
- <title>Sequencing content</title>
- <para></para>
+ <para>Discuss how to obtain JCR sessions and how the credentials work. Also discuss that sessions should be created,
+ used, and closed.</para>
+ </sect1>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="sequencing">
+ <title>Sequencing content</title>
+ <para></para>
<sect1 id="sequencing-service">
<title>Sequencing Service</title>
<para></para>
- </sect1>
+ </sect1>
<sect1 id="sequencers">
<title>JBoss DNA Sequencers</title>
<para></para>
- <sect2 id="dna-sequencer-images">
- <title>Image sequencer</title>
- <para></para>
- </sect2>
- <sect2 id="dna-sequencer-msoffice">
- <title>Microsoft Office document sequencer</title>
- <para></para>
- </sect2>
- <sect2 id="dna-sequencer-zip">
- <title>ZIP archive sequencer</title>
- <para></para>
- </sect2>
- <sect2 id="dna-sequencer-java">
- <title>Java source sequencer</title>
- <para></para>
- </sect2>
- <sect2 id="dna-sequencer-mp3">
- <title>MP3 audio file sequencer</title>
- <para></para>
- </sect2>
- <sect2 id="dna-sequencer-cnd">
- <title>JCR Compact Node Definition (CND) file sequencer</title>
- <para></para>
- </sect2>
- </sect1>
+ <sect2 id="dna-sequencer-images">
+ <title>Image sequencer</title>
+ <para></para>
+ </sect2>
+ <sect2 id="dna-sequencer-msoffice">
+ <title>Microsoft Office document sequencer</title>
+ <para></para>
+ </sect2>
+ <sect2 id="dna-sequencer-zip">
+ <title>ZIP archive sequencer</title>
+ <para></para>
+ </sect2>
+ <sect2 id="dna-sequencer-java">
+ <title>Java source sequencer</title>
+ <para></para>
+ </sect2>
+ <sect2 id="dna-sequencer-mp3">
+ <title>MP3 audio file sequencer</title>
+ <para></para>
+ </sect2>
+ <sect2 id="dna-sequencer-cnd">
+ <title>JCR Compact Node Definition (CND) file sequencer</title>
+ <para></para>
+ </sect2>
+ </sect1>
<sect1 id="custom-sequencers">
<title>Writing custom sequencers</title>
<para></para>
- </sect1>
- </chapter>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="mimetypes">
- <title>MIME types</title>
- <para></para>
+ </sect1>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="mimetypes">
+ <title>MIME types</title>
+ <para></para>
<sect1 id="detectors">
<title>JBoss DNA MIME type detectors</title>
<para></para>
- <sect2 id="dna-mimetype-detector-aperture">
- <title>Aperture MIME type detector</title>
- <para></para>
- </sect2>
- </sect1>
+ <sect2 id="dna-mimetype-detector-aperture">
+ <title>Aperture MIME type detector</title>
+ <para></para>
+ </sect2>
+ </sect1>
<sect1 id="custom-detectors">
<title>Writing custom detectors</title>
<para></para>
- </sect1>
- </chapter>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="configuration">
- <title>Configuration</title>
- <para>Discuss how to configure JBoss DNA and how configuration repositories are used to bootstrap the
- various services and components. Describe how the next release will focus on making this easier
- and will detail configuration using the <ulink url="http://www.jboss.org/jbossmc/">JBoss Microcontainer</ulink>.</para>
- </chapter>
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="testing">
- <title>Testing</title>
- <para></para>
+ </sect1>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="configuration">
+ <title>Configuration</title>
+ <para>
+ Discuss how to configure JBoss DNA and how configuration repositories are used to bootstrap the various services and
+ components. Describe how the next release will focus on making this easier and will detail configuration using the
+ <ulink url="http://www.jboss.org/jbossmc/">JBoss Microcontainer</ulink>
+ .
+ </para>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="testing">
+ <title>Testing</title>
+ <para></para>
<sect1 id="unit-tests">
<title>Unit tests</title>
<para></para>
- </sect1>
+ </sect1>
<sect1 id="integration-tests">
<title>Integration tests</title>
<para></para>
- </sect1>
- </chapter>
-
-
- <!-- ====================================================================================================
- Chapter
- ==================================================================================================== -->
- <chapter id="future_directions">
- <title>Looking to the future</title>
- <para>What's next for JBoss DNA? Well, the sequencing system is just the beginning. With this release, the sequencing system
- is stable enough so that more <link linkend="sequencers">sequencers</link> can be developed and used within your own applications.
- If you're interested in getting involved with the JBoss DNA project, consider picking up one of the sequencers on our
- <ulink url="http://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira.plugin.system.project:roadmap-panel">roadmap</ulink>.
- Or, check out <ulink url="http://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12310520&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12311436">JIRA</ulink>
- for the list of sequencers we've thought of. If you think of one that's not there, please add it to JIRA!
- </para>
- <para>
- The next release will focus on creating the <link linkend="federation">federation engine</link> and connectors
- for several popular and ubiquitous systems. The 0.2 release will likely only federate information in a read-only manner,
- but updates will soon follow. Also, during the early part of the next release, the JBoss DNA project will switch to use JDK 6.
- Java 5 is being end-of-lifed, so we want to move to a supported JDK. However, a number of JBoss projects and products continue to
- require Java 5, so our next release will most likely use JDK 6 with Java 5 compatibility.</para>
- <para>
- Other components on our roadmap include a web user interface, a REST-ful server, and a view system that allows domain-specific
- views of information in the repository. These components are farther out on our roadmap, and at this time have not been
- targeted to a particular release. If any of these are of interest to you, please <link linkend="preface">get involved</link> in the community.
- </para>
- </chapter>
+ </sect1>
+ </chapter>
+ <!--
+ ====================================== Chapter ===============================================
+ -->
+ <chapter id="future_directions">
+ <title>Looking to the future</title>
+ <para>
+ What's next for JBoss DNA? Well, the sequencing system is just the beginning. With this release, the sequencing system is
+ stable enough so that more
+ <link linkend="sequencers">sequencers</link>
+ can be developed and used within your own applications. If you're interested in getting involved with the JBoss DNA project,
+ consider picking up one of the sequencers on our
+ <ulink url="http://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira.plugin.system.project:roadmap-panel">roadmap</ulink>
+ . Or, check out
+ <ulink
+ url="http://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12310520&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12311436">JIRA</ulink>
+ for the list of sequencers we've thought of. If you think of one that's not there, please add it to JIRA!
+ </para>
+ <para>
+ The next release will focus on creating the
+ <link linkend="federation">federation engine</link>
+ and connectors for several popular and ubiquitous systems. The 0.2 release will likely only federate information in a
+ read-only manner, but updates will soon follow. Also, during the early part of the next release, the JBoss DNA project will
+ switch to use JDK 6. Java 5 is being end-of-lifed, so we want to move to a supported JDK. However, a number of JBoss
+ projects and products continue to require Java 5, so our next release will most likely use JDK 6 with Java 5 compatibility.
+ </para>
+ <para>
+ Other components on our roadmap include a web user interface, a REST-ful server, and a view system that allows
+ domain-specific views of information in the repository. These components are farther out on our roadmap, and at this time
+ have not been targeted to a particular release. If any of these are of interest to you, please
+ <link linkend="preface">get involved</link>
+ in the community.
+ </para>
+ </chapter>
</book>
\ No newline at end of file
More information about the dna-commits
mailing list