[jboss-cvs] JBossAS SVN: r76708 - in projects/docs/enterprise/4.3/Transactions: Transactions_Web_Services_Programmers_Guide/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Aug 6 09:21:37 EDT 2008
Author: irooskov at redhat.com
Date: 2008-08-06 09:21:36 -0400 (Wed, 06 Aug 2008)
New Revision: 76708
Modified:
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Administration_of_ArjunaTA.xml
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Appendix.xml
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Preface.xml
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Revision_History.xml
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Transactions_JTA_Administration_Guide.xml
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/en-US/Preface.xml
Log:
updated with make clean_ids
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Administration_of_ArjunaTA.xml
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Administration_of_ArjunaTA.xml 2008-08-06 12:43:02 UTC (rev 76707)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Administration_of_ArjunaTA.xml 2008-08-06 13:21:36 UTC (rev 76708)
@@ -2,11 +2,11 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<chapter id="Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA">
+<chapter id="chap-Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA">
<title>Administration of ArjunaTA</title>
<para>
</para>
- <section id="Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-Introduction">
+ <section id="sect-Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-Introduction">
<title>Introduction</title>
<para>
Apart from ensuring that the run-time system is executing normally, there is little continuous administration needed for the <firstterm>ArjunaTA</firstterm> software. There are a few points however, that should be made:
@@ -34,22 +34,25 @@
</listitem>
</itemizedlist>
</section>
- <section id="Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-ObjectStore_management">
+
+ <section id="sect-Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-ObjectStore_management">
<title>ObjectStore management</title>
<para>
Within the transaction service installation, the object store is updated regularly whenever transactions are created, or when Transactional Objects for Java is used. In a failure free environment, the only object states which should reside within the object store are those representing objects created with the Transactional Objects for Java API. However, if failures occur, transaction logs may remain in the object store until crash recovery facilities have resolved the transactions they represent. As such it is very important that the contents of the object store are not deleted without due care and attention, as this will make it impossible to resolve in doubt transactions. In addition, if multiple users share the same object store it is important that they realise this and do not simply delete the contents of the object store assuming it is an exclusive resource.
</para>
</section>
- <section id="Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-ArjunaTA_runtime_information">
+
+ <section id="sect-Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-ArjunaTA_runtime_information">
<title>ArjunaTA runtime information</title>
<para>
Each module that comprises ArjunaTA possesses a class called Info. These classes all provide a single toString method that returns an XML document representing the configuration information for that module. So, for example:
</para>
<screen>
- <module-info name="arjuna"><source-identifier>unknown</source-identifier><build-information>Arjuna Technologies [mlittle] (Windows 2000 5.0)</build-information><version>unknown</version><date>2002/06/15 04:06 PM</date><notes></notes><configuration><properties-file dir="null">arjuna.properties</properties-file><object-store-root>null</object-store-root></configuration></module-info>
+ <module-info name="arjuna"><source-identifier>unknown</source-identifier><build-information>Arjuna Technologies [mlittle] (Windows 2000 5.0)</build-information><version>unknown</version><date>2002/06/15 04:06 PM</date><notes></notes><configuration><properties-file dir="null">arjuna.properties</properties-file><object-store-root>null</object-store-root></configuration></module-info>
</screen>
</section>
- <section id="Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-Failure_recovery_administration">
+
+ <section id="sect-Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-Failure_recovery_administration">
<title>Failure recovery administration</title>
<para>
The failure recovery subsystem of ArjunaTA will ensure that results of a transaction are applied consistently to all resources affected by the transaction, even if any of the application processes or the machine hosting them crash or lose network connectivity. In the case of machine (system) crash or network failure, the recovery will not take place until the system or network are restored, but the original application does not need to be restarted – recovery responsibility is delegated to the Recovery Manager process (see below). Recovery after failure requires that information about the transaction and the resources involved survives the failure and is accessible afterward: this information is held in the ActionStore, which is part of the ObjectStore.
@@ -62,7 +65,7 @@
<para>
Until the recovery procedures are complete, resources affected by a transaction that was in progress at the time of the failure may be inaccessible. For database resources, this may be reported as tables or rows held by <emphasis>in-doubt transactions</emphasis>. For TransactionalObjects for Java resources, an attempt to activate the Transactional Object (as when trying to get a lock) will fail.
</para>
- <formalpara>
+ <formalpara id="form-Transactions_JTA_Administration_Guide-Failure_recovery_administration-The_Recovery_Manager">
<title>The Recovery Manager</title>
<para>
The failure recovery subsystem of ArjunaTA requires that the stand-alone Recovery Manager process be running for each ObjectStore (typically one for each node on the network that is running ArjunaTA applications). The <filename>RecoveryManager</filename> file is located in the <filename>arjunacore</filename> jar file within the package <package>com.arjuna.ats.arjuna.recovery.RecoveryManager</package>. To start the Recovery Manager issue the following command:
@@ -77,7 +80,7 @@
<screen>
java com.arjuna.ats.arjuna.recovery.RecoveryManager -test
</screen>
- <formalpara>
+ <formalpara id="form-Transactions_JTA_Administration_Guide-Failure_recovery_administration-Configuring_the_Recovery_Manager">
<title>Configuring the Recovery Manager</title>
<para>
The RecoveryManager reads the properties defined in the arjuna.properties file and then also reads the property file RecoveryManager.properties, from the same directory as it found the arjuna properties file. An entry for a property in the RecoveryManager properties file will override an entry for the same property in the main TransactionService properties file. Most of the entries are specific to the Recovery Manager.
@@ -86,14 +89,14 @@
<para>
A default version of RecoveryManager.properties is supplied with the distribution – this can be used without modification, except possibly the debug tracing fields (see below, Output). The rest of this section discusses the issues relevant in setting the properties to other values (in the order of their appearance in the default version of the file).
</para>
- <formalpara>
+ <formalpara id="form-Transactions_JTA_Administration_Guide-Failure_recovery_administration-Output">
<title>Output</title>
<para>
It is likely that installations will want to have some form of output from the RecoveryManager, to provide a record of what recovery activity has taken place. RecoveryManager uses the logging tracing mechanism provided by the Arjuna Common Logging Framework (CLF), which provides a high level interface that hides differences that exist between existing logging APIs such Jakarta log4j or JDK 1.4 logging API. CLF indirects all logging via the Apache Commons Logging framework and configuration is assumed to occur through that framework.
</para>
</formalpara>
<para>
- With the CLF applications make logging calls on logger objects. Loggers may use logging Levels to decide if they are interested in a particular log message. Each log message has an associated log Level, that gives the importance and urgency of a log message. The set of possible Log Levels are DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to their integer values as follows: DEBUG < INFO < WARN < ERROR < FATAL.
+ With the CLF applications make logging calls on logger objects. Loggers may use logging Levels to decide if they are interested in a particular log message. Each log message has an associated log Level, that gives the importance and urgency of a log message. The set of possible Log Levels are DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to their integer values as follows: DEBUG < INFO < WARN < ERROR < FATAL.
</para>
<para>
The CLF provides an extension to filter logging messages according to finer granularity an application may define. That is, when a log message is provided to the logger with the DEBUG level, additional conditions can be specified to determine if the log message is enabled or not.
@@ -109,7 +112,7 @@
<itemizedlist>
<listitem>
<para>
- Debugging level: this is where the log request with the DEBUG Level is generated from, for example, constructors or basic methods.
+ Debugging level: this is where the log request with the DEBUG Level is generated from, for example, constructors or basic methods.
</para>
</listitem>
<listitem>
@@ -119,12 +122,12 @@
</listitem>
<listitem>
<para>
- Facility code: for instance the package or sub-module within which debugging is generated, for example, the object store.
+ Facility code: for instance the package or sub-module within which debugging is generated, for example, the object store.
</para>
</listitem>
</itemizedlist>
<para>
- According to these variables the CLF defines three interfaces. A particular product may implement its own classes according to its own finer granularity. ArjunaTA uses the default Debugging level and the default Visibility level provided by CLF, but it defines its own Facility Code. ArjunaTA uses the default level assigned to its logger objects (DEBUG). However, it uses the finer debugging features to disable or enable debug messages. Finer debugging values used by the ArjunaTA are defined below:
+ According to these variables the CLF defines three interfaces. A particular product may implement its own classes according to its own finer granularity. ArjunaTA uses the default Debugging level and the default Visibility level provided by CLF, but it defines its own Facility Code. ArjunaTA uses the default level assigned to its logger objects (DEBUG). However, it uses the finer debugging features to disable or enable debug messages. Finer debugging values used by the ArjunaTA are defined below:
</para>
<para>
Debugging level – ArjunaTA uses the default values defined in the class <classname>com.arjuna.common.util.logging.DebugLevel</classname>
@@ -132,7 +135,7 @@
<itemizedlist>
<listitem>
<para>
- NO_DEBUGGING: No diagnostics.
+ NO_DEBUGGING: No diagnostics.
</para>
<para>
A logger object assigned with this values discard all debug requests
@@ -158,7 +161,7 @@
</listitem>
<listitem>
<para>
- DESTRUCTORS: Diagnostics from finalizers.
+ DESTRUCTORS: Diagnostics from finalizers.
</para>
</listitem>
<listitem>
@@ -168,12 +171,12 @@
</listitem>
<listitem>
<para>
- FUNCTIONS: Diagnostics from functions.
+ FUNCTIONS: Diagnostics from functions.
</para>
</listitem>
<listitem>
<para>
- OPERATORS: Diagnostics from operators, such as equals.
+ OPERATORS: Diagnostics from operators, such as equals.
</para>
</listitem>
<listitem>
@@ -188,7 +191,7 @@
</listitem>
<listitem>
<para>
- TRIVIAL_FUNCS: Diagnostics from trivial functions.
+ TRIVIAL_FUNCS: Diagnostics from trivial functions.
</para>
</listitem>
<listitem>
@@ -198,7 +201,7 @@
</listitem>
<listitem>
<para>
- ALL_TRIVIAL: Diagnostics from all trivial operations.
+ ALL_TRIVIAL: Diagnostics from all trivial operations.
</para>
</listitem>
</itemizedlist>
@@ -301,7 +304,7 @@
To ensure appropriate output, it is necessary to set some of the finer debug properties explicitly in the <filename>CommonLogging.xml</filename> file, to enable logging messages issued by the ArjunaTA module.
</para>
<para>
- Messages describing the start and the periodical behavior made by the RecoveryManager are output using the INFO level. If other debug tracing is wanted, the finer debugging level should be set appropriately. For instance, the following configuration, in the <filename>CommonLogging.xml</filename>, enables all debug messages related to the Crash Recovery protocol and issued by the ArjunaTA module.
+ Messages describing the start and the periodical behavior made by the RecoveryManager are output using the INFO level. If other debug tracing is wanted, the finer debugging level should be set appropriately. For instance, the following configuration, in the <filename>CommonLogging.xml</filename>, enables all debug messages related to the Crash Recovery protocol and issued by the ArjunaTA module.
</para>
<screen>
<!-- Common logging related properties. -->
@@ -317,20 +320,20 @@
</screen>
<note>
<para>
- Two logger objects are provided, one manages I18N messages and a second does not.
+ Two logger objects are provided, one manages I18N messages and a second does not.
</para>
</note>
<para>
Setting the normal recovery messages to the INFO level allows the RecoveryManager producing a moderate level of reporting. If nothing is going on, it just reports the entry into each module for each periodic pass. To disable INFO messages produced by the Recovery Manager, the logging level could be set to the higher level: ERROR. Setting the level to ERROR means that the RecoveryManager will only produce error, warning or fatal messages.
</para>
- <formalpara>
+ <formalpara id="form-Transactions_JTA_Administration_Guide-Failure_recovery_administration-Periodic_Recovery">
<title>Periodic Recovery</title>
<para>
The RecoveryManager scans the ObjectStore and other locations of information, looking for transactions and resources that require, or may require recovery. The scans and recovery processing are performed by recovery modules, (instances of classes that implement the com.arjuna.ats.arjuna.recovery.RecoveryModule interface), each with responsibility for a particular category of transaction or resource. The set of recovery modules used are dynamically loaded, using properties found in the RecoveryManager property file.
</para>
</formalpara>
<para>
- The interface has two methods: <methodname>periodicWorkFirstPass</methodname> and <methodname>periodicWorkSecondPass</methodname>. At an interval (defined by property <property>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</property>), the RecoveryManager will call the first pass method on each property, then wait for a brief period (defined by property <property>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</property>), then call the second pass of each module. Typically, in the first pass, the module scans (e.g. the relevant part of the ObjectStore) to find transactions or resources that are in-doubt (i.e. are part way through the commitment process). On the second pass, if any of the same items are still in-doubt, it is possible the original application process has crashed and the item is a candidate for recovery.
+ The interface has two methods: <methodname>periodicWorkFirstPass</methodname> and <methodname>periodicWorkSecondPass</methodname>. At an interval (defined by property <property>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</property>), the RecoveryManager will call the first pass method on each property, then wait for a brief period (defined by property <property>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</property>), then call the second pass of each module. Typically, in the first pass, the module scans (e.g. the relevant part of the ObjectStore) to find transactions or resources that are in-doubt (i.e. are part way through the commitment process). On the second pass, if any of the same items are still in-doubt, it is possible the original application process has crashed and the item is a candidate for recovery.
</para>
<para>
An attempt, by the RecoveryManager, to recover a transaction that is still progressing in the original process(es) is likely to break the consistency. Accordingly, the recovery modules use a mechanism (implemented in the <package>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</package> package) to check to see if the original process is still alive, and if the transaction is still in progress. The RecoveryManager only proceeds with recovery if the original process has gone, or, if still alive, the transaction is completed. (If a server process or machine crashes, but the transaction-initiating process survives, the transaction will complete, usually generating a warning. Recovery of such a transaction is the RecoveryManager’s responsibility).
@@ -351,7 +354,7 @@
com.arjuna.ats.arjuna.recovery.recoveryExtension2 = com.arjuna.ats.txoj.recovery.TORecoveryModule
</screen>
- <formalpara>
+ <formalpara id="form-Transactions_JTA_Administration_Guide-Failure_recovery_administration-Expired_entry_removal">
<title>Expired entry removal</title>
<para>
The operation of the recovery subsystem will cause some entries to be made in the ObjectStore that will not be removed in normal progress. The RecoveryManager has a facility for scanning for these and removing items that are very old. Scans and removals are performed by implementations of the <interfacename>com.arjuna.ats.arjuna.recovery.ExpiryScanner</interfacename> interface. Implementations of this interface are loaded by giving the class name as the value of a property whose name begins with <property>com.arjuna.ats.arjuna.recovery.expiryScanner</property>. The RecoveryManager calls the <methodname>scan()</methodname> method on each loaded Expiry Scanner implementation at an interval determined by the property <property>com.arjuna.ats.arjuna.recovery.expiryScanInterval</property>. This value is given in hours – default is 12. An expiryScanInterval value of zero will suppress any expiry scanning. If the value as supplied is positive, the first scan is performed whe!
n RecoveryManager starts; if the value is negative, the first scan is delayed until after the first interval (using the absolute value)
@@ -361,7 +364,7 @@
The kinds of item that are scanned for expiry are:
</para>
<para>
- TransactionStatusManager items : one of these is created by every application process that uses ArjunaCore – they contain the information that allows the RecoveryManager to determine if the process that initiated the transaction is still alive, and what the transaction status is. The expiry time for these is set by the property <property>com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime</property> (in hours – default is 12, zero means never expire). The expiry time should be greater than the lifetime of any single ArjunaTA-using process.
+ TransactionStatusManager items : one of these is created by every application process that uses ArjunaCore – they contain the information that allows the RecoveryManager to determine if the process that initiated the transaction is still alive, and what the transaction status is. The expiry time for these is set by the property <property>com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime</property> (in hours – default is 12, zero means never expire). The expiry time should be greater than the lifetime of any single ArjunaTA-using process.
</para>
<para>
The Expiry Scanner properties for these are:
@@ -370,7 +373,8 @@
com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager = com.arjuna.ats.internal.ts.arjuna.recovery.ExpiredTransactionStatusManagerScanner
</screen>
</section>
- <section id="Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-Errors_and_Exceptions">
+
+ <section id="sect-Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-Errors_and_Exceptions">
<title>Errors and Exceptions</title>
<para>
In this section we shall cover the types of errors and exceptions which may be thrown or reported during a transactional application and give probable indications of their causes.
@@ -398,12 +402,13 @@
</listitem>
<listitem>
<para>
- Object store warnings about access problems on states may occur during the normal execution of crash recovery. This is the result of multiple concurrent attempts to perform recovery on the same transaction. It can be safely ignored.
+ Object store warnings about access problems on states may occur during the normal execution of crash recovery. This is the result of multiple concurrent attempts to perform recovery on the same transaction. It can be safely ignored.
</para>
</listitem>
</itemizedlist>
</section>
- <section id="Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-Selecting_the_JTA_implementation">
+
+ <section id="sect-Transactions_JTA_Administration_Guide-Administration_of_ArjunaTA-Selecting_the_JTA_implementation">
<title>Selecting the JTA implementation</title>
<para>
Two variants of the JTA implementation are now provided and accessible through the same interface. These are:
@@ -446,5 +451,6 @@
</para>
</note>
</section>
+
</chapter>
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Appendix.xml
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Appendix.xml 2008-08-06 12:43:02 UTC (rev 76707)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Appendix.xml 2008-08-06 13:21:36 UTC (rev 76708)
@@ -2,9 +2,9 @@
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<appendix id="Transactions_JTA_Administration_Guide-Revision_History">
+<appendix id="appe-Transactions_JTA_Administration_Guide-Revision_History">
<appendixinfo>
- <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
</appendixinfo>
<title>Revision History</title>
<para>
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Book_Info.xml 2008-08-06 12:43:02 UTC (rev 76707)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Book_Info.xml 2008-08-06 13:21:36 UTC (rev 76708)
@@ -2,27 +2,28 @@
<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<bookinfo id="Transactions_JTA_Administration_Guide-Product_Name_and_Version">
+<bookinfo id="book-Transactions_JTA_Administration_Guide-Transactions_JTA_Administration_Guide">
<title>Transactions JTA Administration Guide</title>
<subtitle>JBoss Enterprise Application Platform</subtitle>
<issuenum>0.1</issuenum>
<productnumber>0</productnumber>
- <abstract><para>This book is about the administration of Arjuna TA</para></abstract>
+ <abstract>
+ <para>This book is about the administration of Arjuna TA</para></abstract>
<corpauthor>
<inlinemediaobject>
<imageobject>
- <imagedata format='SVG' fileref="Common_Content/images/title_logo.svg" />
+ <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" />
</imageobject>
- <textobject><phrase>Logo</phrase></textobject>
+ <textobject>
+ <phrase>Logo</phrase>
+ </textobject>
</inlinemediaobject>
</corpauthor>
<copyright>
<year>&YEAR;</year>
<holder>&HOLDER;</holder>
</copyright>
- <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
</bookinfo>
-
-
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Preface.xml 2008-08-06 12:43:02 UTC (rev 76707)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Preface.xml 2008-08-06 13:21:36 UTC (rev 76708)
@@ -2,14 +2,12 @@
<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<preface id="Transactions_JTA_Administration_Guide-Preface">
+<preface id="pref-Transactions_JTA_Administration_Guide-Preface">
<title>Preface</title>
<para>
</para>
- <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude">
- <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">
- <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </xi:fallback>
- </xi:include>
+ <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ </xi:fallback></xi:include>
</preface>
+
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Revision_History.xml 2008-08-06 12:43:02 UTC (rev 76707)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Revision_History.xml 2008-08-06 13:21:36 UTC (rev 76708)
@@ -18,3 +18,4 @@
</revdescription>
</revision>
</revhistory>
+
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Transactions_JTA_Administration_Guide.xml
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Transactions_JTA_Administration_Guide.xml 2008-08-06 12:43:02 UTC (rev 76707)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/en-US/Transactions_JTA_Administration_Guide.xml 2008-08-06 13:21:36 UTC (rev 76708)
@@ -3,9 +3,9 @@
]>
<book>
- <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="Administration_of_ArjunaTA.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Appendix.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Administration_of_ArjunaTA.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Appendix.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
</book>
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/en-US/Preface.xml 2008-08-06 12:43:02 UTC (rev 76707)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/en-US/Preface.xml 2008-08-06 13:21:36 UTC (rev 76708)
@@ -8,9 +8,9 @@
</para>
<xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude">
- <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">
+ <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> -->
<xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</xi:fallback>
- </xi:include>
+ </xi:include>
</preface>
More information about the jboss-cvs-commits
mailing list