[jboss-cvs] JBossAS SVN: r82122 - in projects/docs/community/5/Installation_And_Getting_Started_Guide: en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Dec 8 18:52:52 EST 2008
Author: scott.stark at jboss.org
Date: 2008-12-08 18:52:51 -0500 (Mon, 08 Dec 2008)
New Revision: 82122
Modified:
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Server_Configurations.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
projects/docs/community/5/Installation_And_Getting_Started_Guide/pom.xml
Log:
JBAS-6280, manually break the tables that are overflowing for now
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Server_Configurations.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Server_Configurations.xml 2008-12-08 21:33:45 UTC (rev 82121)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/Server_Configurations.xml 2008-12-08 23:52:51 UTC (rev 82122)
@@ -121,13 +121,13 @@
To start the server using an alternate configuration refer to <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/>.
</para>
</note>
-<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations-Server_Configuration_Directory_Structure">
+<section id="Server_Configuration_Directory_Structure">
<title>Server Configuration Directory Structure</title>
<para>
- The directory server configuration you’re using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure-Server_Configuration_Directory_Structure"/> shows the directories inside the server configuration directory (<filename class="directory"><JBoss_Home>/server/<instance-name></filename>) and their functions.
+ The directory server configuration you’re using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure_table"/> shows the directories inside the server configuration directory (<filename class="directory"><JBoss_Home>/server/<instance-name></filename>) and their functions.
</para>
<para>
- <table id="Server_Configuration_Directory_Structure-Server_Configuration_Directory_Structure">
+ <table id="Server_Configuration_Directory_Structure_table">
<title>Server Configuration Directory Structure</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="1*"/>
@@ -204,7 +204,7 @@
</table>
</para>
</section>
-<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations-The_default_Server_Configuration_File_Set">
+<section id="The_default_Server_Configuration_File_Set">
<title>The "default" Server Configuration File Set</title>
<para>
The "<literal>default</literal>" server configuration file set is located in the <literal><JBoss_Home>/server/default</literal> directory. The following example illustrates a truncated directory structure of the <literal>jboss-as-<release></literal> server configuration files:
@@ -492,8 +492,8 @@
The files in the <literal>deployers</literal> directory are explained in the following table.
</para>
<para>
- <table id="Contents_of_deploy_directory-Contents_of_deployers_directory">
- <title>Contents of "deploy" directory</title>
+ <table id="Contents_of_deployers_directory_table1">
+ <title>Contents of "deployers" directory</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="4*"/>
<colspec colname="c2" colnum="2" colwidth="4*"/>
@@ -598,6 +598,25 @@
<literal>jboss-jca.deployer</literal> description
</entry>
</row>
+ </tbody>
+ </tgroup>
+ </table>
+ <table id="Contents_of_deployers_directory_table2">
+ <title>Contents of "deployers" directory continued</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
<row>
<entry>
<literal>jbossweb.deployer</literal>
@@ -658,7 +677,7 @@
The files in the <literal>deploy</literal> directory are explained in the following table.
</para>
<para>
- <table id="Contents_of_deploy_directory-Contents_of_deploy_directory">
+ <table id="Contents_of_deploy_directory_table1">
<title>Contents of "deploy" directory</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="4*"/>
@@ -781,11 +800,30 @@
web application deployment service
management.</entry>
</row>
- <row>
- <entry><literal>jbossws.sar</literal></entry>
- <entry>provides JEE web services support. </entry>
- </row>
- <row>
+ </tbody>
+ </tgroup>
+ </table>
+ <table id="Contents_of_deploy_directory_table2">
+ <title>Contents of "deploy" directory continued</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><literal>jbossws.sar</literal></entry>
+ <entry>provides JEE web services support. </entry>
+ </row>
+ <row>
<entry>
<literal>jca-jboss-beans.xml</literal>
</entry>
@@ -875,7 +913,26 @@
simple web interface for managing the MBean server.
</entry>
</row>
- <row>
+ </tbody>
+ </tgroup>
+ </table>
+ <table id="Contents_of_deploy_directory_table3">
+ <title>Contents of "deploy" directory continued(2)</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
<entry>
<literal>jmx-invoker-service.xml</literal>
</entry>
@@ -949,7 +1006,11 @@
<entry>
<literal>properties-service.xml</literal>
</entry>
- <entry></entry>
+ <entry> The <literal>properties-service.xml</literal>
+ file is an MBean service descriptor that allows for
+ customization of the JavaBeans
+ <literal>PropertyEditor</literal>s as well as
+ the definition of system properties. </entry>
</row>
<row>
<entry>
@@ -968,24 +1029,36 @@
contains the unified invokers based on JBoss
Remoting. </entry>
</row>
- <row>
- <entry> The <literal>properties-service.xml</literal>
- file is an MBean service descriptor that allows for
- customization of the JavaBeans
- <literal>PropertyEditor</literal>s as well as
- the definition of system properties. </entry>
- </row>
- <row>
+ </tbody>
+ </tgroup>
+ </table>
+ <table id="Contents_of_deploy_directory_table4">
+ <title>Contents of "deploy" directory continued(3)</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <literal>scheduler-service.xml</literal>
+ </entry>
+ <entry> The <literal>scheduler-service.xml</literal> and
+ <literal>schedule-manager-service.xml</literal>
+ files are MBean service descriptors that provide a
+ scheduling type of service. </entry>
+ </row>
+ <row>
<entry>
- <literal>scheduler-service.xml</literal>
- </entry>
- <entry> The <literal>scheduler-service.xml</literal> and
- <literal>schedule-manager-service.xml</literal>
- files are MBean service descriptors that provide a
- scheduling type of service. </entry>
- </row>
- <row>
- <entry>
<literal>security/security-jboss-beans.xml</literal>
</entry>
<entry>
@@ -1042,7 +1115,7 @@
</section>
</section>
-<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations-The_all_Server_Configuration_File_Set">
+<section id="The_all_Server_Configuration_File_Set">
<title>The "all" Server Configuration File Set</title>
<para>
The "all" server configuration file set is located in the <filename class="directory"><JBoss_Home>/server/all</filename> directory. In addition to the services in the "default" set, the all configuration contains several other services in the <literal>conf/</literal> directory as shown below.
@@ -1119,7 +1192,7 @@
</table>
</para>
</section>
-<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations-EJB3_Services_">
+<section id="EJB3_Services">
<title>EJB3 Services </title>
<para>
The following table explains the files providing ejb3 services.
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2008-12-08 21:33:45 UTC (rev 82121)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2008-12-08 23:52:51 UTC (rev 82122)
@@ -1,5 +1,5 @@
<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.docbook.org/xml/4.4/docbookx.dtd"
[
<!ENTITY versionNumber "5.0.0.GA">
@@ -86,15 +86,20 @@
This is hot-deployment in action.
</para>
</section>
+
<section id="The_JBoss_Server___A_Quick_Tour-Basic_Configuration_Issues">
<title>Basic Configuration Issues</title>
<para>
- Now that we have examined the JBoss server, we will take a look at some of the main configuration files and what they are used for. All paths are relative to the server configuration directory (<filename class="directory">server/production</filename>, for example).
+ Now that we have examined the JBoss server, we will take a look at some of the main configuration files and what they are used for. All paths are relative to the server configuration directory (<filename class="directory">server/default</filename>, for example).
</para>
+ <section id="The_JBoss_Server___A_Quick_Tour-Bootstrap_Configuration">
+ <title>Bootstrap Configuration</title>
+ <para>The microcontainer bootstrap configuration is described by the <filename>conf/bootstrap.xml</filename> and the <filename>conf/bootstrap/*.xml</filename> it references.</para>
+ </section>
<section id="Basic_Configuration_Issues-Core_Services">
<title>Core Services</title>
<para>
- The core services specified in the <filename>conf/jboss-service.xml</filename> file are started first when the server starts up. If you have a look at this file in an editor you will see MBeans for various services including logging, security, JNDI, JNDIView etc. Try commenting out the entry for the <literal>JNDIView</literal> service.
+ The legacy core services specified in the <filename>conf/jboss-service.xml</filename> file are started just after server starts up the microcontainer. If you have a look at this file in an editor you will see MBeans for various services including logging, security, JNDI, JNDIView etc. Try commenting out the entry for the <literal>JNDIView</literal> service.
</para>
<para>
Note that because the mbeans definition had nested comments, we had to comment out the mbean in two sections, leaving the original comment as it was.
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/pom.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/pom.xml 2008-12-08 21:33:45 UTC (rev 82121)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/pom.xml 2008-12-08 23:52:51 UTC (rev 82122)
@@ -15,7 +15,7 @@
<plugin>
<groupId>org.jboss.maven.plugins</groupId>
<artifactId>maven-jdocbook-plugin</artifactId>
- <version>2.0.0</version>
+ <version>2.1.2</version>
<extensions>true</extensions>
<dependencies>
<dependency>
@@ -29,11 +29,17 @@
<version>1.0.0</version>
<type>jdocbook-style</type>
</dependency>
+ <dependency>
+ <groupId>org.hibernate</groupId>
+ <artifactId>hibernate-jdocbook-style</artifactId>
+ <version>1.0.2</version>
+ <type>jdocbook-style</type>
+ </dependency>
</dependencies>
<configuration>
<!--minmemory>1024m</minmemory>
<maxmemory>1024m</maxmemory -->
- <sourceDocumentName>resolved.xml</sourceDocumentName>
+ <sourceDocumentName>Installation_And_Getting_Started_Guide.xml</sourceDocumentName>
<sourceDirectory>en-US</sourceDirectory>
<imageResource>
<directory>en-US</directory>
@@ -60,8 +66,12 @@
<format>
<formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <!--
+ <stylesheetResource>classpath:/xslt/hibernate/pdf/main-pdf.xsl</stylesheetResource>
+-->
<finalName>Installation_And_Getting_Started_Guide.pdf</finalName>
+ <profilingTypeName>two_pass</profilingTypeName>
</format>
More information about the jboss-cvs-commits
mailing list