[jboss-cvs] JBossAS SVN: r100455 - projects/docs/enterprise/5.0/mod_cluster/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Feb 5 02:06:31 EST 2010
Author: gmeintjes
Date: 2010-02-05 02:06:31 -0500 (Fri, 05 Feb 2010)
New Revision: 100455
Modified:
projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml
Log:
Amended to reflect latest review comments
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml 2010-02-05 06:31:40 UTC (rev 100454)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml 2010-02-05 07:06:31 UTC (rev 100455)
@@ -7,7 +7,7 @@
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>5.0</productnumber>
<edition>1</edition>
- <pubsnumber>1.5</pubsnumber>
+ <pubsnumber>1.7</pubsnumber>
<abstract>
<para>
mod_cluster is an httpd-based load balancer that uses a
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2010-02-05 06:31:40 UTC (rev 100454)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2010-02-05 07:06:31 UTC (rev 100455)
@@ -128,7 +128,7 @@
<term>Configuration properties</term>
<listitem>
<para>
- For the complete list of configuration properties available to ModClusterService, refer to the following sections:
+ For the complete list of configuration properties available to ModClusterService, refer to the following in Configuration Properties:
</para>
</listitem>
</varlistentry>
@@ -172,11 +172,11 @@
The state of each proxy will be kept in sync on each node in the cluster.
</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>
Proxies will be proactively notified of view changes - specifically crashed members, allowing the proxy to gracefully reconfigure itself potentially avoiding failover processing.
</para>
- </listitem>
+ </listitem> -->
</orderedlist>
<para>
If your application server already uses other clustering services (e.g. session replication), then you should consider running mod_cluster in clustered-mode. If your application server is stateless (i.e. no sessions), or you are not using other clustering services, then non-clustered mode may be more appropriate.
@@ -218,7 +218,7 @@
<varlistentry><term>An <classname>HAModClusterConfig</classname> bean, defining containing the configuration properties.</term>
<listitem>
<para>
-For the complete list of configuration properties available to ModClusterService, refer to the following sections:
+For the complete list of configuration properties available to ModClusterService, refer to the following in Configuration Properties:
<itemizedlist>
<listitem>
<para>
@@ -281,7 +281,7 @@
<tgroup colsep="1" cols="3">
<colspec colname="c1"/>
<colspec colname="c2"/>
- <colspec colname="c3"/>
+ <colspec colname="c3" colwidth="2*"/>
<thead>
<row>
<entry>Attribute</entry>
@@ -309,12 +309,12 @@
<property>excludedContexts</property>
</entry>
<entry>
-ROOT,invoker,jbossws,jmx-console,juddi,web-console
+ROOT, invoker, jbossws, jmx-console, juddi, web-console
</entry>
<entry>
List of contexts to exclude from httpd registration, of the form:
<varname>host1:context1, host2:context2, host3:context3</varname>
-If no host is indicated, it is assumed to be the default host of the server (e.g. localhost). "ROOT" indicates the root context. Using the default configuration, this property can by manipulated via the <varname>jboss.modcluster. excludedContexts</varname> system property.
+If no host is indicated, it is assumed to be the default host of the server (e.g. localhost). "ROOT" indicates the root context. Using the default configuration, this property can by manipulated via the <varname>jboss.modcluster.excludedContexts</varname> system property.
</entry>
</row>
<row>
@@ -399,7 +399,7 @@
<tgroup colsep="1" cols="3">
<colspec colname="c1"/>
<colspec colname="c2"/>
- <colspec colname="c3"/>
+ <colspec colname="c3" colwidth="2*"/>
<thead>
<row>
<entry>Attribute</entry>
@@ -639,7 +639,7 @@
<property>sslKeyStore</property>
</entry>
<entry>
-<filename>System.getProperty("user.home") + "/.keystore"</filename>
+<literallayout><property>System.getProperty("user.home") + "/.keystore"</property></literallayout>
</entry>
<entry>
The location of the key store containing client certificates
@@ -832,7 +832,7 @@
<property>loadMetricClass</property>
</entry>
<entry>
-<classname>org.jboss.load.metric. impl.BusyConnectorsLoadMetric</classname>
+<classname>org.jboss.load.metric.impl.BusyConnectorsLoadMetric</classname>
</entry>
<entry>
Class name of an object implementing <filename>org.jboss.load.metric.LoadMetric</filename>
@@ -914,17 +914,17 @@
</listitem>
<listitem>
<para>
-The capacity of a metric serves 2 functions:
+The capacity of a metric serves two functions:
</para>
<itemizedlist mark='opencircle'>
<listitem>
<para>
-The weight (default is 1) indicates the significance of a metric with respect to the other metrics. For example, a metric of weight 2 will have twice the impact on the overall load factor than a metric of weight 1.
+To normalize the load values from each metric. In some load metrics, capacity is already reflected in the load values. The capacity of a metric should be configured such that 0 <= (load / capacity) >= 1.
</para>
</listitem>
<listitem>
<para>
-The capacity of a metric serves 2 functions:
+To favor some nodes over others. By setting the metric capacities to different values on each node, proxies will effectively favor nodes with higher capacities, since they will return smaller load values. This adds an interesting level of granularity to node weighting. Consider a cluster of two nodes, one with more memory, and a second with a faster CPU; and two metrics, one memory-based and the other CPU-based. In the memory-based metric, the first node would be given a higher load capacity than the second node. In a CPU-based metric, the second node would be given a higher load capacity than the first node.
</para>
</listitem>
</itemizedlist>
@@ -941,25 +941,27 @@
</para>
<programlisting>
-<![CDATA[L = (L0 + L1/D + L2/D2 + L3/D3 + ... + LH/DH) * (1 + D + D2 + D3 + ... DH)
- ]]>
+L = (L<subscript>0</subscript> + L<subscript>1</subscript>/D + L<subscript>2</subscript>/D<superscript>2</superscript> + L<subscript>3</subscript>/D<superscript>3</superscript> + ... + L<subscript>H</subscript>/D<superscript>H</superscript>) * (1 + D + D<superscript>2</superscript> + D<superscript>3</superscript> + ... D<superscript>H</superscript>)
+
</programlisting>
<para>
- The aggregate load can be expressed more concisely as by the following formula:
+ The aggregate load can be expressed more concisely by the following formula, where D = decayFactor and H = history:
</para>
<programlisting>
-<![CDATA[ H H
- L = ∑ Li/Di * ∑ Di
+ H H
+ L = ∑ L<subscript>i</subscript>/D<superscript>i</superscript> * ∑ D<superscript>i</superscript>
i=0 i=0
- ]]>
+
</programlisting>
-
<para>
Setting <varname>history = 0</varname> effectively disables the time decay function and only the current load for each metric will be considered in the load balance factor computation.
</para>
<para>
+ Setting <varname>history = 0</varname> effectively disables the time decay function and only the current load for each metric will be considered in the load balance factor computation.
+ </para>
+ <para>
The <varname>mod_cluster proxy</varname> module expects the load factor to be an integer between 0 and 100, where 0 indicates max load and 100 indicates zero load. Therefore, the final load balance factor sent to the proxy = 100 - (L * 100).
</para>
<para>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2010-02-05 06:31:40 UTC (rev 100454)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2010-02-05 07:06:31 UTC (rev 100455)
@@ -126,7 +126,7 @@
<section id="sect-mod_cluster-Overview-Current_Limitations">
<title>Current Limitations</title>
<para>
- The mod_cluster install currently has the following limitations:
+ The mod_cluster install currently has no known limitations.
</para>
<!-- <itemizedlist>
<listitem>
@@ -138,14 +138,14 @@
<para>
Clustered-mode support is currently limited to the JBoss AS integration
</para>
- </listitem> -->
+ </listitem>
<itemizedlist>
<listitem>
<para>
Checksum verification of proxy advertisements (if advertise is enabled) will never fail.
</para>
</listitem>
- </itemizedlist>
+ </itemizedlist> -->
</section>
</chapter>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-02-05 06:31:40 UTC (rev 100454)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-02-05 07:06:31 UTC (rev 100455)
@@ -4,7 +4,7 @@
<chapter id="chap-mod_cluster-Quick_Start_Guide">
<title>Quick Start Guide</title>
<para>
- The following steps are required to set up a minimal working installation of mod_cluster on a single httpd server and a single back end server, either <application>JBoss AS</application>, <application>JBossWeb</application> or <application>Tomcat</application>. The steps can be repeated to add as many httpd servers or back end servers to your cluster as desired.
+ The following steps are required to set up a minimal working installation of mod_cluster on a single httpd server and a single back end server, either <application>JBoss EAP</application>, <application>JBossWeb</application> or <application>Tomcat</application>. The steps can be repeated to add as many httpd servers or back end servers to your cluster as desired.
</para>
<para>
The steps shown here are not intended to demonstrate how to set up a production install of mod_cluster; for example using <application>SSL</application> to secure access to the httpd-side mod_manager component is not covered. See the <citetitle>httpd-side</citetitle> and <citetitle>Java-side configuration documentation</citetitle> for the full set of configuration options.
@@ -17,7 +17,256 @@
<!-- <para>
If there is no pre-built httpd bundle appropriate for your OS or system architecture, you can build the binary from source.
</para> -->
- </section>
+
+ <formalpara>
+ <title>mod_proxy configuration</title>
+ <para>
+ mod_proxy directives, such as ProxyIOBufferSize, could be used to configure mod_cluster. There is no need to use ProxyPass directives because mod_cluster automatically configures which URLs have to be forwarded to JBossWEB.
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>mod_slotmem configuration</title>
+ <para>
+ The actual version does not require configuration directives.
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>mod_proxy_cluster</title>
+ <para>
+
+ </para>
+ </formalpara>
+<variablelist>
+ <varlistentry>
+ <term>CreateBalancers</term>
+ <listitem>
+ <para>
+ Define how the balancer are created in the httpd VirtualHosts, this is to allow directives like:
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>UseAlias</term>
+ <listitem>
+ <para>
+ Check that the Alias corresponds to the ServerName (See Host Name Aliases)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>LBstatusRecalTime </term>
+ <listitem>
+ <para>
+ Time interval in seconds for loadbalancing logic to recalculate the status of a node: (Default: 5 seconds)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ProxyPassMatch/ProxyPass </term>
+ <listitem>
+ <para>
+ ProxyPassMatch and ProxyPass are mod_proxy directives that when using ! (instead of the back-end url) prevent to reverse-proxy in the path.
+ </para>
+ <para>
+ This could be used allow httpd to serve static information like images.
+ </para>
+<programlisting>
+ProxyPassMatch ^(/.*\.gif)$ !
+</programlisting>
+ <para>
+ The above, for example, will allow httpd to directly server the .gif files.
+ </para>
+
+ </listitem>
+ </varlistentry>
+</variablelist>
+ <formalpara>
+ <title>mod_manager</title>
+ <para>
+
+ </para>
+ </formalpara>
+<variablelist>
+ <varlistentry>
+ <term>MemManagerFile</term>
+ <listitem>
+ <para>
+ That is the base name for the names mod_manager will use to store configuration, generate keys for shared memory or lock files. That must be an absolute path name; the directories will created if needed. It is highly recommended that those files are placed on a local drive and not an NFS share. Default: $server_root/logs/
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Maxnode</term>
+ <listitem>
+ <para>
+ That is the number max nodes supported by mod_cluster. Default: 20
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Maxhost</term>
+ <listitem>
+ <para>
+ That is the number max host (Aliases) supported by mod_cluster. That is also the max number of balancers. Default: 10
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Maxsessionid</term>
+ <listitem>
+ <para>
+ That is the number of active sessionid we store to give number of active sessions in the mod_cluster-manager handler. A session is unactive when mod_cluster doesn't receive any information from the session in 5 minutes. Default: 0 (the logic is activated).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ManagerBalancerName</term>
+ <listitem>
+ <para>
+ That is the name of balancer to use when the JBoss AS/JBossWeb/Tomcat doesn't provide a balancer name. That is not supported in the current version. (Default value is used). Default: mycluster
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>PersistSlots</term>
+ <listitem>
+ <para>
+ Tell mod_slotmem to persist the nodes, Alias and Context in files. Default: Off
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>SetHandler mod_cluster-manager</term>
+ <listitem>
+ <para>
+ That is the handler to display the node mod_cluster sees from the cluster. It displays the information about the nodes like INFO and additionaly counts the number of active sessions.
+ </para>
+<programlisting><![CDATA[
+ <Location /mod_cluster-manager>
+ SetHandler mod_cluster-manager
+
+ Order deny,allow
+ Deny from all
+ Allow from 127.0.0.1
+ </Location>
+]]></programlisting>
+ </listitem>
+ </varlistentry>
+</variablelist>
+
+ <note>
+<variablelist>
+ <varlistentry>
+ <term>Transferred</term>
+ <listitem>
+ <para>
+ Corresponds to the POST data sent to the back-end server.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Connected</term>
+ <listitem>
+ <para>
+ Corresponds to the number of requests processed when the mod_cluster status page was requested.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>sessions</term>
+ <listitem>
+ <para>
+ Corresponds to the number of sessions mod_cluster report as active (on which there was a request during the past 5 minutes). That field is not present when Maxsessionid is zero.
+ </para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+ </note>
+
+
+
+
+
+
+
+
+
+ <formalpara>
+ <title>mod_advertise</title>
+ <para>
+ mod_advertise uses multicast packets to advertise the VirtualHost where it is configured that must be the same VirtualHost where mod_manager is defined. Of course at least one mod_advertise must be in the VirtualHost to allow mod_cluster to find the right IP and port to give to the ClusterListener.
+ </para>
+ </formalpara>
+<variablelist>
+ <varlistentry>
+ <term>ServerAdvertise On</term>
+ <listitem>
+ <para>
+ Use the advertise mechanism to tell the JBoss EAP/JBossWeb/Tomcat to whom it should send the cluster information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ServerAdvertise On http://hostname:port</term>
+ <listitem>
+ <para>
+ Tell the hostname and port to use. Only needed if the VirtualHost is not defined correctly, if the VirtualHost is a Name-based Virtual Host or when VirtualHost is not used.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ServerAdvertise Off</term>
+ <listitem>
+ <para>
+ Don't use the advertise mechanism. Default: On.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>AdvertiseGroup IP:port </term>
+ <listitem>
+ <para>
+ That is the multicast address to use (something like 232.0.0.2:8888 for example). IP should correspond to AdvertiseGroupAddress and port to AdvertisePort in the JBoss EAP/JBossWeb/Tomcat configuration. Note that if JBoss EAP is used and the -u startup switch is included in the EAP startup command, the default AdvertiseGroupAddress is the value passed via the -u. Default: 224.0.1.105:23364. If port is missing the default port will be used: 23364.
+ </para>
+ </listitem>
+</varlistentry>
+<varlistentry>
+ <term>AdvertiseFrequency seconds[.miliseconds]</term>
+ <listitem>
+ <para>
+ Time between the multicast messages advertising the IP and port. Default: 10 Ten seconds.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>AdvertiseSecurityKey value</term>
+ <listitem>
+ <para>
+ key string to identify the mod_cluster in JBossWEB. Default: No default value. Information not sent.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>AdvertiseManagerUrl value</term>
+ <listitem>
+ <para>
+ Not used in this version (It is sent in the X-Manager-Url: value header). That is the URL that JBoss EAP/JBossWeb/Tomcat should use to send information to mod_cluster. Default: No default value. Information not sent.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>AdvertiseBindAddress IP:port </term>
+ <listitem>
+ <para>
+ That is the address and port httpd is bind to send the multicast messages. This allow to specify an address on multi IP address boxes. Default: 0.0.0.0:23364
+ </para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+
+</section>
<section id="sect-mod_cluster-Quick_Start_Guide-Install_the_httpd_binary">
<title>Install the httpd binary</title>
@@ -347,7 +596,7 @@
<note>
<para>
- The demo application does not actually depend on mod_cluster in any way. Its only dependency is on JBossWeb/Tomcat.1 So, the demo could be used to demonstrate the effect of different server-side scenarios on the routing decisions made by any load balancer, including mod_jk, mod_proxy or the various hardware load balancers.
+ The demo application does not actually depend on mod_cluster in any way. Its only dependency is on JBossWeb/Tomcat. The demo could therefore be used to demonstrate the effect of different server-side scenarios on the routing decisions made by any load balancer, including mod_jk, mod_proxy or the various hardware load balancers.
</para>
</note>
<note>
@@ -375,12 +624,12 @@
</listitem>
<listitem>
<para>
- Install mod_cluster into your JBossAS/JBossWeb/Tomcat servers as described at Installation on the Java side.
+ Install mod_cluster into your JBossEAP/JBossWeb/Tomcat servers as described at Installation on the Java side.
</para>
</listitem>
<listitem>
<para>
- Start httpd and your JBossAS/JBossWeb/Tomcat servers.
+ Start httpd and your JBossEAP/JBossWeb/Tomcat servers.
</para>
</listitem>
<listitem>
@@ -417,7 +666,7 @@
</listitem>
<listitem>
<para>
- Configure the hostname and address of the httpd server, the number of client threads, etc and click the "Start" button. See Client Driver Configuration Options for details on the configuration options.
+ Configure the hostname and address of the httpd server, the number of client threads, etc and click the "Start" button. Refer to the Client Driver Configuration Options for details on the configuration options.
</para>
</listitem>
<listitem>
@@ -437,7 +686,7 @@
</listitem>
<listitem>
<para>
- Restart some of your JBossAS/JBossWeb/Tomcat servers and/or re-deploy the load-demo.war to some of the servers and see the effect this has on load balancing.
+ Restart some of your JBoss EAP/JBossWeb/Tomcat servers and/or re-deploy the load-demo.war to some of the servers and see the effect this has on load balancing.
</para>
</listitem>
<listitem>
@@ -453,7 +702,7 @@
<formalpara>
<title>Client Driver Configuration Options</title>
<para>
- The configuration of the client is driver is done via the application's "Client Control" tab.
+ The configuration of the client driver is done via the application's "Client Control" tab.
</para>
</formalpara>
<para>
@@ -464,21 +713,21 @@
<term>Proxy Hostname</term>
<listitem>
<para>
- Hostname of the load balancer or the IP address on which it is listening for requests
+ Hostname of the load balancer or the IP address on which it is listening for requests.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Proxy Port</term>
<listitem>
- <para>Port on which the load balancer is listening for requests</para>
+ <para>Port on which the load balancer is listening for requests.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Context Path</term>
<listitem>
<para>
- Portion of the request URL that specifies the request is for the load-demo.war
+ Portion of the request URL that specifies the request is for the <filename>load-demo.war</filename>
</para>
</listitem>
</varlistentry>
@@ -554,7 +803,7 @@
</listitem>
<listitem>
<para>
- If the JBoss AS/JBossWeb/Tomcat servers are running the HttpConnector as well as the AJP connector, you can specify the address and port on which a particular server's HttpConnector is listening. The standard port is 8080.
+ If the JBoss EAP/JBossWeb/Tomcat servers are running the HttpConnector as well as the AJP connector, you can specify the address and port on which a particular server's HttpConnector is listening. The standard port is 8080.
</para>
</listitem>
</orderedlist>
@@ -627,68 +876,6 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
</section>
</chapter>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml 2010-02-05 06:31:40 UTC (rev 100454)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml 2010-02-05 07:06:31 UTC (rev 100455)
@@ -6,8 +6,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1.5</revnumber>
- <date>Tue 02 Feb 2010</date>
+ <revnumber>1.7</revnumber>
+ <date>Fri 05 Feb 2010</date>
<author>
<firstname>Gary</firstname>
<surname>Meintjes</surname>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml 2010-02-05 06:31:40 UTC (rev 100454)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml 2010-02-05 07:06:31 UTC (rev 100455)
@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<book>
+<book status="draft">
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- <xi:include href="Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
More information about the jboss-cvs-commits
mailing list