JBTM-1184. Update documentation for Narayana and Wildfly changes

ArjunaCore/docs/development_guide/en-US/About_This_Guide.xml

@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='utf-8' ?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "JBossJTA_Development_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Development_Guide.ent">
 %BOOK_ENTITIES;
 ]>
 <chapter>

ArjunaCore/docs/development_guide/en-US/Appendix_Object_Store_Implementations.xml

@@ -15,7 +15,7 @@
       implementations and plugging into an application.
     </para>
     <para>
-      This release of JBoss Transaction Service contains several different implementations of a basic object store. Each
+      This release of &PRODUCT; contains several different implementations of a basic object store. Each
       serves a particular purpose and is generally optimized for that purpose. Each of the implementations implements 
       the <interfacename>ObjectStoreAPI</interfacename> interface, which defines the minimum operations which must be
       provided for an object store implementation to be used by the Transaction Service. You can override the default
@@ -28,9 +28,9 @@
       <programlisting language="Java" role="JAVA"><xi:include href="extras/appendix_StateStatus.java" xmlns:xi="http://www.w3.org/2001/XInclude" parse="text" /></programlisting>
     </example>
     <para>
-      JBoss Transaction Service programmers do not usually need to interact with any of the object store implementations
+      &PRODUCT; programmers do not usually need to interact with any of the object store implementations
       directly, apart from possibly creating them in the first place. Even this is not necessary if the default store
-      type is used, since JBoss Transaction Service creates stores as necessary. All stores manipulate instances of the
+      type is used, since &PRODUCT; creates stores as necessary. All stores manipulate instances of the
       class <classname>ObjectState</classname>. These instances are named using a <systemitem>type</systemitem> (via the
       object's <methodname>type()</methodname> operation) and a <systemitem>Uid</systemitem>.
     </para>
@@ -82,7 +82,7 @@
           </listitem>
           <listitem>
             <para>
-              All of the stores have a common root directory that is determined when JBoss Transaction Service is
+              All of the stores have a common root directory that is determined when &PRODUCT; is
               configured. This directory name is automatically prepended to any store-specific root information.
             </para>
           </listitem>
@@ -118,7 +118,7 @@
         <para>
           Since transactional objects are concurrency-controlled through <classname>LockManager</classname>, you do not
           need to impose additional locking at the file level. The basic ShadowingStore implementation handles
-          file-level locking. Therefore, the default object store implementation for JBoss Transaction Service,
+          file-level locking. Therefore, the default object store implementation for &PRODUCT;,
           <systemitem>ShadowNoFileLockStore</systemitem>, relies upon user-level locking. This enables it to provide
           better performance than the <systemitem>ShadowingStore</systemitem> implementation.
         </para>

ArjunaCore/docs/development_guide/en-US/ArjunaCore_Development_Guide.ent

@@ -1,4 +1,5 @@
-<!ENTITY PRODUCT "Documentation">
+<!ENTITY PRODUCT "Narayana">
 <!ENTITY BOOKID "ArjunaCore_Development_Guide">
-<!ENTITY YEAR "2011">
+<!ENTITY YEAR "2014">
 <!ENTITY HOLDER "jboss.org">
+<!ENTITY APPSERVER "WildFly Application Server">

ArjunaCore/docs/development_guide/en-US/Book_Info.xml

@@ -12,7 +12,7 @@
   <pubsnumber>0</pubsnumber>
   <abstract>
     <para>
-      This guide is most relevant to engineers who are responsible for administering JBoss Transactions
+      This guide is most relevant to engineers who are responsible for administering &PRODUCT;
       installations. Although this guide is specifically intended for service developers, it will be useful to anyone
       who would like to gain an understanding of transactions and how they function.
     </para>

ArjunaCore/docs/development_guide/en-US/General_Transaction_Issues.xml

@@ -104,7 +104,7 @@
       </listitem>
     </itemizedlist>
     <para>
-      Therefore, JBoss Transaction Service provides runtime options to enable possible threading optimizations. By setting the
+      Therefore, &PRODUCT; provides runtime options to enable possible threading optimizations. By setting the
       <varname>CoordinatorEnvironmentBean.asyncBeforeSynchronization</varname>
       environment variable to <literal>YES</literal>, during the
       <methodname>beforeSynchronization</methodname> phase a separate thread
@@ -209,13 +209,13 @@
     </para>
     <note>
       <para>
-        Default timeout values for other JBoss Transaction Service components, such as JTS, may be different and you should consult the
+        Default timeout values for other &PRODUCT; components, such as JTS, may be different and you should consult the
         relevant documentation to be sure.
       </para>
     </note>
     <para>
       When a top-level transaction is created with a non-zero timeout, it is subject to being rolled back if it has not
-      completed within the specified number of seconds. JBoss Transaction Service uses a separate reaper thread which
+      completed within the specified number of seconds. &PRODUCT; uses a separate reaper thread which
       monitors all locally created transactions, and forces them to roll back if their timeouts elapse. If the
       transaction cannot be rolled back at that point, the reaper will force it into a rollback-only state so that it
       will eventually be rolled back.
@@ -238,7 +238,7 @@
     </warning>
     <para>
       If a value of <literal>0</literal> is specified for the timeout of a top-level transaction, or no timeout is
-      specified, then JBoss Transaction Service will not impose any timeout on the transaction, and the transaction will
+      specified, then &PRODUCT; will not impose any timeout on the transaction, and the transaction will
       be allowed to run indefinitely. This default timeout can be overridden by setting the
       <varname>CoordinatorEnvironmentBean.defaultTimeout</varname> property variable when using to the required timeout
       value in seconds, when using ArjunaCore, ArjunaJTA or ArjunaJTS.

ArjunaCore/docs/development_guide/en-US/Overview.xml

@@ -22,9 +22,9 @@
   <note>
     <title>Stand-Alone Transaction Manager</title>
     <para>
-      Although JBoss Transaction Service can be embedded in various containers, such as JBoss Application Server, it
-      remains a stand-alone transaction manager as well. There are no dependencies between the core JBoss Transaction
-      Service and any container implementations.
+      Although &PRODUCT; can be embedded in various containers, such as &APPSERVER;, it
+      remains a stand-alone transaction manager as well. There are no dependencies between the core &PRODUCT; and any
+      container implementations.
     </para>
   </note>
 

ArjunaCore/docs/development_guide/en-US/fallback_content/Legal_Notice.xml

@@ -1,5 +1,7 @@
 <?xml version='1.0' encoding='utf-8' ?>
 <!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "../ArjunaCore_Development_Guide.ent">
+%BOOK_ENTITIES;
 ]>
 <legalnotice>
 	<para>

ArjunaCore/docs/failure_recovery_guide/en-US/About_This_Guide.xml

@@ -1,24 +1,24 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recover_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recovery_Guide.ent">
 %BOOK_ENTITIES;
 ]>
 <chapter>
   <title>About This Guide</title>
   <para>
-    The Failure Recovery for TxCore and TXOJ contains information on how to use JBoss Transactions 4.10.0 failure recovery system when not
+    The Failure Recovery for TxCore and TXOJ contains information on how to use &PRODUCT; failure recovery system when not
     embedding it within an application server or using TXOJ.
   </para>
   <section>
     <title>Audience</title>
     <para>
-      This guide is most relevant to engineers who are responsible for administering JBoss Transactions 4.10.0 installations.
+      This guide is most relevant to engineers who are responsible for administering &PRODUCT; installations.
     </para>
   </section>
   <section>
     <title>Prerequisites</title>
     <para>
-      You should have installed JBoss Transactions 4.10.0. The reader should be familiar with the main Failure Recovery Guide.
+      You should have installed &PRODUCT;. The reader should be familiar with the main Failure Recovery Guide.
     </para>
   </section>
 </chapter>

ArjunaCore/docs/failure_recovery_guide/en-US/ArjunaCore_Failure_Recovery_Guide.ent

@@ -1,7 +1,6 @@
-<!ENTITY PRODUCT "JBoss Transactions">
+<!ENTITY PRODUCT "Narayana">
 <!ENTITY BOOKID "ArjunaCore_Failure_Recover_Guide">
-<!ENTITY VERSION "4.15">
-<!ENTITY YEAR "2011">
+<!ENTITY YEAR "2014">
 <!ENTITY HOLDER "JBoss.org">
-<!ENTITY APPSERVER "JBoss Application Server">
+<!ENTITY APPSERVER "WildFly Application Server">
 <!-- <!ENTITY APPSERVER "Enterprise Application Platform Server"> -->

ArjunaCore/docs/failure_recovery_guide/en-US/Author_Group.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recover_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recovery_Guide.ent">
 ]>
 <authorgroup>
     <author>

ArjunaCore/docs/failure_recovery_guide/en-US/Book_Info.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recover_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recovery_Guide.ent">
 %BOOK_ENTITIES;
 ]>
 <bookinfo id="book-ArjunaCore_Failure_Recover_Guide">
@@ -12,7 +12,7 @@
     <pubsnumber>0</pubsnumber>
     <abstract>
         <para>
-        The ArjunaCore Failure Recovery Guide contains information on how to use JBoss Transaction Service to develop
+        The ArjunaCore Failure Recovery Guide contains information on how to use &PRODUCT; to develop
         applications that use transaction technology to manage business processes.
       </para>
     </abstract>

ArjunaCore/docs/failure_recovery_guide/en-US/Further_failure_recovery.xml

@@ -1,10 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recover_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recovery_Guide.ent">
+%BOOK_ENTITIES;
 ]>
 <chapter>
   <title>Introduction</title>
-  <para>In this chapter we shall cover information on failure recovery that is specific to TxCore, TXOJ or using JBossTS outside the scope of a
+  <para>In this chapter we shall cover information on failure recovery that is specific to TxCore, TXOJ or using &PRODUCT; outside the scope of a
     supported application server.</para>
   <section>
     <title>Embedding the Recovery Manager</title>
@@ -27,7 +28,7 @@
     </warning>
     <section>
       <title>Additional Recovery Module Classes</title>
-      <para>JBossTS provides a set of recovery modules that are responsible to manage recovery according to the nature of the participant and its
+      <para>&PRODUCT; provides a set of recovery modules that are responsible to manage recovery according to the nature of the participant and its
         position in a transactional tree. The provided classes over and above the ones covered elsewhere (that all implements the RecoveryModule
         interface) are:</para>
       <itemizedlist>
@@ -40,7 +41,7 @@
   </section>
   <section>
     <title>Understanding Recovery Modules</title>
-    <para>The failure recovery subsystem of JBossTS will ensure that results of a transaction are applied consistently to all resources affected
+    <para>The failure recovery subsystem of &PRODUCT; 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
@@ -61,8 +62,8 @@
       resources, an attempt to activate the Transactional Object (as when trying to get a lock) will fail.</para>
     <section>
       <title>The Recovery Manager</title>
-      <para>The failure recovery subsystem of JBossTS requires that the stand-alone Recovery Manager process be running for each ObjectStore
-        (typically one for each node on the network that is running JBossTS applications). The RecoveryManager file is located in the package
+      <para>The failure recovery subsystem of &PRODUCT; requires that the stand-alone Recovery Manager process be running for each ObjectStore
+        (typically one for each node on the network that is running &PRODUCT; applications). The RecoveryManager file is located in the package
         com.arjuna.ats.arjuna.recovery.RecoveryManager. To start the Recovery Manager issue the following command:</para>
       <para>
         <programlisting language="Java" role="JAVA">java com.arjuna.ats.arjuna.recovery.RecoveryManager</programlisting>
@@ -138,10 +139,10 @@
         the original process to see if they are
         still in progress</para>
       <note>
-        <para>In previous versions of JBossTS there was no contact mechanism, and the backoff period had to be long enough to avoid catching
+        <para>In previous versions of &PRODUCT; there was no contact mechanism, and the backoff period had to be long enough to avoid catching
           transactions in flight at all. From 3.0, there is no such risk.</para>
       </note>
-      <para>Two recovery modules (implementations of the com.arjuna.ats.arjuna.recovery.RecoveryModule interface) are supplied with JBossTS,
+      <para>Two recovery modules (implementations of the com.arjuna.ats.arjuna.recovery.RecoveryModule interface) are supplied with &PRODUCT;,
         supporting various aspects of transaction recovery including JDBC recovery. It is possible for advanced users to create their own recovery
         modules and register them with the Recovery Manager. The recovery modules are registered with the RecoveryManager using
         RecoveryEnvironmentBean.recoveryExtensions. These will be invoked on each pass of the periodic recovery in the sort-order of the property
@@ -176,13 +177,13 @@
         absolute
         value)</para>
       <para>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 JBossTS – they contain the information
+      <para>TransactionStatusManager items: one of these is created by every application process that uses &PRODUCT; – 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 com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime (in hours – default
         is 12, zero
-        means never expire). The expiry time should be greater than the lifetime of any single JBossTS-using process.</para>
+        means never expire). The expiry time should be greater than the lifetime of any single &PRODUCT;-using process.</para>
       <para>The Expiry Scanner properties for these are:</para>
       <example>
         <title>Recovery Environment Bean XML</title>
@@ -207,7 +208,7 @@
     <para>In order to recover from failure, we have seen that the Recovery Manager contacts recovery modules by invoking periodically the methods
       periodicWorkFirstPass and periodicWorkSecondPass. Each Recovery Module is then able to manage recovery according the type of resources that
       need
-      to be recovered. The JBoss Transaction product is shipped with a set of recovery modules (TOReceveryModule, XARecoveryModule…), but it is
+      to be recovered. The &PRODUCT; product is shipped with a set of recovery modules (TOReceveryModule, XARecoveryModule…), but it is
       possible for a user to define its own recovery module that fit his application. The following basic example illustrates the steps needed to
       build such recovery module</para>
     <section>
@@ -271,7 +272,7 @@
       </example>
       <para>Once started, the Recovery Manager will automatically load the listed Recovery modules.</para>
       <note>
-        <para>The source of the code can be retrieved under the trailmap directory of the JBossTS installation. </para>
+        <para>The source of the code can be retrieved under the trailmap directory of the &PRODUCT; installation. </para>
       </note>
     </section>
     <section>

ArjunaCore/docs/failure_recovery_guide/en-US/Preface.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recover_Guide.ent">
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recovery_Guide.ent">
 ]>
 <preface id="pref-ArjunaCore_Failure_Recover_Guide-Preface">
     <title>Preface</title>

ArjunaCore/docs/failure_recovery_guide/en-US/Revision_History.xml

@@ -1,13 +1,7 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recover_Guide.ent">
-<!ENTITY PRODUCT "JBoss Transactions">
-<!ENTITY BOOKID "ArjunaCore_Failure_Recover_Guide">
-<!ENTITY VERSION "4.15">
-<!ENTITY YEAR "2011">
-<!ENTITY HOLDER "JBoss.org">
-<!ENTITY APPSERVER "JBoss Application Server">
-<!-- <!ENTITY APPSERVER "Enterprise Application Platform Server"> -->]>
+<!ENTITY % BOOK_ENTITIES SYSTEM "ArjunaCore_Failure_Recovery_Guide.ent">
+]>
 <appendix id="appe-ArjunaCore_Failure_Recover_Guide-Revision_History">
     <title>Revision History</title>
     <simpara>

ArjunaCore/docs/failure_recovery_guide/en-US/fallback_content/Legal_Notice.xml

@@ -1,5 +1,7 @@
 <?xml version='1.0' encoding='utf-8' ?>
 <!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "../ArjunaCore_Failure_Recovery_Guide.ent">
+%BOOK_ENTITIES;
 ]>
 <legalnotice>
 	<para>

ArjunaJTA/docs/administration_guide/en-US/Book_Info.xml

@@ -4,11 +4,11 @@
 %BOOK_ENTITIES;
 ]>
 <bookinfo id="book-JBossJTA_Administration_Guide">
-  <title>JBossJTA Administration Guide</title>
-  <subtitle>Administration of the &PRODUCT; toolkit, which implements the JTA API in the &PRODUCT;
+  <title>&PRODUCT; Administration Guide</title>
+  <subtitle>Administration of the &PRODUCT; toolkit, which implements the JTA API in the &PARENT_PRODUCT;
     Transaction Service</subtitle>
-  <productname>JBossJTA</productname>
-  <productnumber>4.15.1</productnumber>
+  <productname>&PRODUCT;</productname>
+  <productnumber>&VERSION;</productnumber>
   <edition>1</edition>
   <pubsnumber>1</pubsnumber>
   <!-- <abstract> <para> A short overview and summary of the book&#39;s subject and purpose, traditionally no more than one paragraph long. Note: the abstract 

ArjunaJTA/docs/administration_guide/en-US/JBossJTA_Administration_Guide.ent

@@ -1,4 +1,7 @@
-<!ENTITY PRODUCT "JBossJTA">
+<!ENTITY PARENT_PRODUCT "Narayana">
+<!ENTITY PRODUCT "Narayana JTA">
+<!ENTITY PRODUCT_WEBSITE "http://www.narayana.io">
+<!ENTITY VERSION "5.0.0.Final">
 <!ENTITY BOOKID "JBossJTA_Administration_Guide">
-<!ENTITY YEAR "2011">
+<!ENTITY YEAR "2014">
 <!ENTITY HOLDER "JBoss.org">

ArjunaJTA/docs/administration_guide/en-US/Preface.xml

@@ -9,9 +9,9 @@
    <section>
      <title>Prerequisites</title>
      <para>
-       &PRODUCT; works in conjunction with &PRODUCT;. In addition to the documentation here, consult the &PRODUCT;
-       documentation, which ships as part of &PRODUCT; and is also available on the JBoss Transaction Service website
-       at <ulink url="http://www.jboss.org/jbosstm" />.
+       &PRODUCT; works in conjunction with &PARENT_PRODUCT;. In addition to the documentation here, consult the &PARENT_PRODUCT;
+       documentation, which ships as part of &PARENT_PRODUCT; and is also available on the &PARENT_PRODUCT; website
+       at <ulink url="&PRODUCT_WEBSITE;" />.
      </para>
    </section>