[jboss-cvs] JBossAS SVN: r74212 - in projects/docs/enterprise/4.3/Transactions/Administrators_Guide: de-DE and 6 other directories.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Thu Jun 5 18:50:43 EDT 2008


Author: mhideo at redhat.com
Date: 2008-06-05 18:50:43 -0400 (Thu, 05 Jun 2008)
New Revision: 74212

Added:
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Appendix.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Author_Group.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Book_Info.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Chapter.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Feedback.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/JBoss_Transactions_Administrators_Guide.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Preface.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Revision_History.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Appendix.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Author_Group.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Book_Info.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Chapter.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Feedback.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/JBoss_Transactions_Administrators_Guide.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Preface.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Revision_History.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Appendix.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Author_Group.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Book_Info.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Chapter.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Feedback.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/JBoss_Transactions_Administrators_Guide.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Preface.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Revision_History.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Appendix.pot
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Author_Group.pot
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Book_Info.pot
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Chapter.pot
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Feedback.pot
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/JBoss_Transactions_Administrators_Guide.pot
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Preface.pot
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Revision_History.pot
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/messages.mo
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Appendix.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Author_Group.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Book_Info.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Chapter.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Feedback.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/JBoss_Transactions_Administrators_Guide.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Preface.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Revision_History.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Appendix.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Author_Group.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Book_Info.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Feedback.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/JBoss_Transactions_Administrators_Guide.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Preface.po
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Revision_History.po
Modified:
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/Makefile
   projects/docs/enterprise/4.3/Transactions/Administrators_Guide/ja-JP/Chapter.po
Log:
init l10n

Modified: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/Makefile
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/Makefile	2008-06-05 22:46:25 UTC (rev 74211)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/Makefile	2008-06-05 22:50:43 UTC (rev 74212)
@@ -6,8 +6,7 @@
 BRAND	= JBoss
 
 
-#OTHER_LANGS	= as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW
-OTHER_LANGS	= ja-JP
+OTHER_LANGS	= de-DE es-ES fr-FR ja-JP pt-BR zh-CN 
 TRANSLATIONS	= $(XML_LANG) $(OTHER_LANGS)
 
 CHUNK_FIRST = 0

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Appendix.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Appendix.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Author_Group.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Author_Group.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,29 @@
+# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "FF0000 Headgear Documentation Group"
+msgstr ""
+
+#. Tag: author
+#: Author_Group.xml:7
+#, no-c-format
+msgid ""
+"<firstname>Dude</firstname> <surname>McDude</surname> <affiliation> "
+"<orgname>My Org</orgname> <orgdiv>Best Div in the place</orgdiv> </"
+"affiliation> <email>dude.mcdude at myorg.org</email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Book_Info.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Book_Info.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,40 @@
+# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions API 4.2.3 Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:10
+#, no-c-format
+msgid "JBoss Enterprise Application Platform"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid ""
+"This book is the JBoss Enterprise Application Platform edition of the JBoss "
+"Transactions Administrators Guide"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:22
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Chapter.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Chapter.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Chapter.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,932 @@
+# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Chapter.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:7
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBoss Transactions software. "
+"There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:10
+#, no-c-format
+msgid ""
+"The present implementation of the JBoss TA system provides no security or "
+"protection for data. The objects stored in the JBoss Transactions object "
+"store are (typically) owned by the user who ran the application that created "
+"them. The Object Store and Object Manager facilities make no attempt to "
+"enforce even the limited form of protection that Unix/Windows provides. "
+"There is no checking of user or group IDs on access to objects for either "
+"reading or writing."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:13
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"StateManager.destroy method is invoked on the object or some application "
+"program explicitly deletes them. This means that the Object Store gradually "
+"accumulates garbage (especially during application development and testing "
+"phases). At present we have no automated garbage collection facility. "
+"Further, we have not addressed the problem of dangling references. That is, "
+"a persistent object, A, may have stored a Uid for another persistent object, "
+"B, in its passive representation on disk. There is nothing to prevent an "
+"application from deleting B even though A still contains a reference to it. "
+"When A is next activated and attempts to access B, a run-time error will "
+"occur."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:16
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The JBoss Transactions software can "
+"neither detect nor correct references to old object state by new operation "
+"versions or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:19
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:24
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:28
+#, no-c-format
+msgid "JBoss Transactions runtime information"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:29
+#, no-c-format
+msgid ""
+"Each module that comprises JBoss Transactions 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:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"&lt;module-info name=\"arjuna\"&gt;\n"
+"        &lt;source-identifier&gt;unknown&lt;/source-identifier&gt;\n"
+"        &lt;build-information&gt;\n"
+"           Arjuna Technologies [mlittle] (Windows 2000 5.0)\n"
+"        &lt;/build-information&gt;\n"
+"        &lt;version&gt;unknown&lt;/version&gt;\n"
+"        &lt;date&gt;2002/06/15 04:06 PM&lt;/date&gt;\n"
+"        &lt;notes&gt;&lt;/notes&gt;\n"
+"        &lt;configuration&gt;\n"
+"                &lt;properties-file dir=\"null\"&gt;arjuna.properties&lt;/"
+"properties-file&gt;\n"
+"                &lt;object-store-root&gt;null&lt;/object-store-root&gt;\n"
+"        &lt;/configuration&gt;\n"
+"&lt;/module-info&gt;"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:34
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:38
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:41
+#, no-c-format
+msgid ""
+"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 “in-doubt transactions”. For TransactionalObjects for Java "
+"resources, an attempt to activate the Transactional Object (as when trying "
+"to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:43
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:44
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions requires that the stand-"
+"alone Recovery Manager process be running for each ObjectStore (typically "
+"one for each node on the network that is running JBoss Transactions "
+"applications). The RecoveryManager file is located in the arjunacore jar "
+"file within the package <classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryManager</classname>. To start the Recovery Manager issue the "
+"following command:"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:45
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:46
+#, no-c-format
+msgid ""
+"If the <literal>-test</literal> flag is used with the Recovery Manager then "
+"it will display a “Ready” message when initialised, i.e.,"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:47
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:50
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:51
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the <filename>arjuna."
+"properties</filename> file and then also reads the property file "
+"<filename>RecoveryManager.properties</filename>, 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:52
+#, no-c-format
+msgid ""
+"A default version of <filename>RecoveryManager.properties</filename> 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)"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:54
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:55
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:58
+#, no-c-format
+msgid ""
+"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 &lt; INFO &lt; WARN &lt; ERROR &lt; "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:61
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:67
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:71
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:74
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, e.g., constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:77
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:80
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, e.g., the object store."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:83
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. JBoss Transactions uses the default Debugging level and the "
+"default Visibility level provided by CLF, but it defines its own Facility "
+"Code. JBoss Transactions 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 JBoss Transactions "
+"are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"Debugging level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:87
+#, no-c-format
+msgid ""
+"NO_DEBUGGING:  No diagnostics. A logger object assigned with this values "
+"discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:90
+#, no-c-format
+msgid ""
+"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
+"allows all debug requests if the facility code and the visibility level "
+"match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:93
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:96
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid "DESTRUCTORS:  Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:102
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid "FUNCTIONS:  Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:108
+#, no-c-format
+msgid "OPERATORS:  Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:114
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:117
+#, no-c-format
+msgid "TRIVIAL_FUNCS:  Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:120
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:123
+#, no-c-format
+msgid "ALL_TRIVIAL:  Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:126
+#, no-c-format
+msgid ""
+"Visibility level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:129
+#, no-c-format
+msgid "VIS_NONE:  No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:132
+#, no-c-format
+msgid "VIS_PRIVATE :  only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:135
+#, no-c-format
+msgid "VIS_PROTECTED  only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:138
+#, no-c-format
+msgid "VIS_PUBLIC   only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:141
+#, no-c-format
+msgid "VIS_JBoss_Transactions_Administrators_Guide   only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:144
+#, no-c-format
+msgid "VIS_ALL:  Full Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:147
+#, no-c-format
+msgid ""
+"Facility Code – JBoss Transactions uses the following values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:150
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:153
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:156
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:159
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:162
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:165
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:174
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:177
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:180
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"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 JBoss Transactions module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:184
+#, no-c-format
+msgid ""
+"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 CommonLogging.xml, enables all debug "
+"messages related to the Crash Recovery protocol and issued by the JBoss "
+"Transactions module."
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:186
+#, no-c-format
+msgid ""
+"&lt;!-- Common logging related properties. --&gt;\n"
+"&lt;property\n"
+"  name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+"  value=\"0x00000000\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:189
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:192
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:196
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:198
+#, no-c-format
+msgid ""
+"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
+"<literal>periodicWorkSecondPass</literal>. At an interval (defined by "
+"property <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
+"classname>), the RecoveryManager will call the first pass method on each "
+"property, then wait for a brief period (defined by property <classname>com."
+"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>), 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:199
+#, no-c-format
+msgid ""
+"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 "
+"<classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
+"classname> 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)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the <literal>periodicRecoveryPeriod</"
+"literal>, <literal>recoveryBackoffPeriod</literal> and the length of time it "
+"takes to scan the stores and to attempt recovery of any in-doubt "
+"transactions found, for all the recovery modules. The recovery attempt time "
+"may include connection timeouts while trying to communicate with processes "
+"or machines that have crashed or are inaccessible (which is why there are "
+"mechanisms in the recovery system to avoid trying to recover the same "
+"transaction for ever). The total iteration time will affect how long a "
+"resource will remain inaccessible after a failure – "
+"<literal>periodicRecoveryPeriod</literal> should be set accordingly (default "
+"is 120 seconds). The <literal>recoveryBackoffPeriod</literal> can be "
+"comparatively short (default is 10 seconds) – its purpose is mainly to "
+"reduce the number of transactions that are candidates for recovery and which "
+"thus require a “call to the original process to see if they are still in "
+"progress"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"In previous versions of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:206
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <classname>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</classname> interface) are supplied with "
+"JBoss Transactions, 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 properties "
+"that begin with “<classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryExtension</classname>”. These will be invoked on each pass of the "
+"periodic recovery in the sort-order of the property names – it is thus "
+"possible to predict the ordering (but note that a failure in an application "
+"process might occur while a periodic recovery pass is in progress). The "
+"default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+"\n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
+"  com.arjuna.ats.txoj.recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:211
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"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 <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> "
+"interface. Implementations of this interface are loaded by giving the class "
+"name as the value of a property whose name begins with <classname>com.arjuna."
+"ats.arjuna.recovery.expiryScanner</classname>. The RecoveryManager calls the "
+"<command>scan()</command> method on each loaded Expiry Scanner "
+"implementation at an interval determined by the property <classname>com."
+"arjuna.ats.arjuna.recovery.expiryScanInterval</classname>. This value is "
+"given in hours – default is 12. An <classname>expiryScanInterval</classname> "
+"value of zero will suppress any expiry scanning. If the value as supplied is "
+"positive, the first scan is performed when RecoveryManager starts; if the "
+"value is negative, the first scan is delayed until after the first interval "
+"(using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:213
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:214
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses JBoss Transactions – 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 <classname>com.arjuna."
+"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> (in hours "
+"– default is 12, zero means never expire). The expiry time should be greater "
+"than the lifetime of any single JBoss Transactions-using process."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:217
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery."
+"ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:220
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:221
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:224
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"<classname>OutOfMemoryError</classname>) and JBoss Transactions has "
+"attempted to do some cleanup (by running the garbage collector) before re-"
+"throwing the exception. This is probably a transient problem and retrying "
+"the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:227
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:230
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:233
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:236
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:241
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:242
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:245
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the JBoss Transactions "
+"product."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:248
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:252
+#, no-c-format
+msgid ""
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:255
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:258
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaTMImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:261
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaUTImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:265
+#, no-c-format
+msgid ""
+"these settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Feedback.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Feedback.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Feedback.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,34 @@
+# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Feedback.xml:6
+#, no-c-format
+msgid "Feedback"
+msgstr ""
+
+#. Tag: para
+#: Feedback.xml:7
+#, no-c-format
+msgid ""
+"If you spot a typo in this guide, or if you have thought of a way to make "
+"this manual better, we would love to hear from you! Submit a report in "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> against "
+"the Product: JBoss Enterprise Application Platform, Version: "
+"<replaceable>&lt;version&gt;</replaceable>, Component: <emphasis>Doc</"
+"emphasis>. If you have a suggestion for improving the documentation, try to "
+"be as specific as possible. If you have found an error, include the section "
+"number and some of the surrounding text so we can find it easily."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/JBoss_Transactions_Administrators_Guide.po
===================================================================

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Preface.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Preface.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,123 @@
+# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:14
+#, no-c-format
+msgid "What This Guide Contains"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:15
+#, no-c-format
+msgid ""
+"The Administration Guide contains information on how to administer JBoss "
+"Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:17
+#, no-c-format
+msgid "Audience"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:18
+#, no-c-format
+msgid ""
+"This guide is most relevant to engineers who are responsible for "
+"administration of JBoss Transactions API 4.2.3 installations."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:21
+#, no-c-format
+msgid "Prerequisites"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:22
+#, no-c-format
+msgid ""
+"In order to administer JBoss Transactions it is first necessary to "
+"understand that it relies on ArjunaCore for a lot of the transaction "
+"functionality. As such, it is important to read the ArjunaCore "
+"Administration Guide before attempting to administer JBoss Transactions."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:25
+#, no-c-format
+msgid "Organization"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:26
+#, no-c-format
+msgid "This guide contains the following chapters:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:29
+#, no-c-format
+msgid ""
+"Chapter 1, Administration of JBoss Transactions: describes how to administer "
+"JBoss Transactions, mainly by selecting the variant of JTA implementation: "
+"pure local or remote (allowing distributed transactions)."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:34
+#, no-c-format
+msgid "Additional Documentation"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:35
+#, no-c-format
+msgid ""
+"In addition to this guide, the following guides are available in the JBoss "
+"Transactions API 4.2.3 documentation set:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:38
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
+"information about JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:41
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
+"instructions for installing JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:44
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
+"writing applications."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/de-DE/Revision_History.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: author
+#: Revision_History.xml:9
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Appendix.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Appendix.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Author_Group.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Author_Group.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,29 @@
+# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "FF0000 Headgear Documentation Group"
+msgstr ""
+
+#. Tag: author
+#: Author_Group.xml:7
+#, no-c-format
+msgid ""
+"<firstname>Dude</firstname> <surname>McDude</surname> <affiliation> "
+"<orgname>My Org</orgname> <orgdiv>Best Div in the place</orgdiv> </"
+"affiliation> <email>dude.mcdude at myorg.org</email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Book_Info.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Book_Info.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,40 @@
+# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions API 4.2.3 Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:10
+#, no-c-format
+msgid "JBoss Enterprise Application Platform"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid ""
+"This book is the JBoss Enterprise Application Platform edition of the JBoss "
+"Transactions Administrators Guide"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:22
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Chapter.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Chapter.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Chapter.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,932 @@
+# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Chapter.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:7
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBoss Transactions software. "
+"There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:10
+#, no-c-format
+msgid ""
+"The present implementation of the JBoss TA system provides no security or "
+"protection for data. The objects stored in the JBoss Transactions object "
+"store are (typically) owned by the user who ran the application that created "
+"them. The Object Store and Object Manager facilities make no attempt to "
+"enforce even the limited form of protection that Unix/Windows provides. "
+"There is no checking of user or group IDs on access to objects for either "
+"reading or writing."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:13
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"StateManager.destroy method is invoked on the object or some application "
+"program explicitly deletes them. This means that the Object Store gradually "
+"accumulates garbage (especially during application development and testing "
+"phases). At present we have no automated garbage collection facility. "
+"Further, we have not addressed the problem of dangling references. That is, "
+"a persistent object, A, may have stored a Uid for another persistent object, "
+"B, in its passive representation on disk. There is nothing to prevent an "
+"application from deleting B even though A still contains a reference to it. "
+"When A is next activated and attempts to access B, a run-time error will "
+"occur."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:16
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The JBoss Transactions software can "
+"neither detect nor correct references to old object state by new operation "
+"versions or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:19
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:24
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:28
+#, no-c-format
+msgid "JBoss Transactions runtime information"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:29
+#, no-c-format
+msgid ""
+"Each module that comprises JBoss Transactions 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:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"&lt;module-info name=\"arjuna\"&gt;\n"
+"        &lt;source-identifier&gt;unknown&lt;/source-identifier&gt;\n"
+"        &lt;build-information&gt;\n"
+"           Arjuna Technologies [mlittle] (Windows 2000 5.0)\n"
+"        &lt;/build-information&gt;\n"
+"        &lt;version&gt;unknown&lt;/version&gt;\n"
+"        &lt;date&gt;2002/06/15 04:06 PM&lt;/date&gt;\n"
+"        &lt;notes&gt;&lt;/notes&gt;\n"
+"        &lt;configuration&gt;\n"
+"                &lt;properties-file dir=\"null\"&gt;arjuna.properties&lt;/"
+"properties-file&gt;\n"
+"                &lt;object-store-root&gt;null&lt;/object-store-root&gt;\n"
+"        &lt;/configuration&gt;\n"
+"&lt;/module-info&gt;"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:34
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:38
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:41
+#, no-c-format
+msgid ""
+"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 “in-doubt transactions”. For TransactionalObjects for Java "
+"resources, an attempt to activate the Transactional Object (as when trying "
+"to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:43
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:44
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions requires that the stand-"
+"alone Recovery Manager process be running for each ObjectStore (typically "
+"one for each node on the network that is running JBoss Transactions "
+"applications). The RecoveryManager file is located in the arjunacore jar "
+"file within the package <classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryManager</classname>. To start the Recovery Manager issue the "
+"following command:"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:45
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:46
+#, no-c-format
+msgid ""
+"If the <literal>-test</literal> flag is used with the Recovery Manager then "
+"it will display a “Ready” message when initialised, i.e.,"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:47
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:50
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:51
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the <filename>arjuna."
+"properties</filename> file and then also reads the property file "
+"<filename>RecoveryManager.properties</filename>, 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:52
+#, no-c-format
+msgid ""
+"A default version of <filename>RecoveryManager.properties</filename> 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)"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:54
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:55
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:58
+#, no-c-format
+msgid ""
+"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 &lt; INFO &lt; WARN &lt; ERROR &lt; "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:61
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:67
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:71
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:74
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, e.g., constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:77
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:80
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, e.g., the object store."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:83
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. JBoss Transactions uses the default Debugging level and the "
+"default Visibility level provided by CLF, but it defines its own Facility "
+"Code. JBoss Transactions 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 JBoss Transactions "
+"are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"Debugging level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:87
+#, no-c-format
+msgid ""
+"NO_DEBUGGING:  No diagnostics. A logger object assigned with this values "
+"discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:90
+#, no-c-format
+msgid ""
+"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
+"allows all debug requests if the facility code and the visibility level "
+"match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:93
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:96
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid "DESTRUCTORS:  Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:102
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid "FUNCTIONS:  Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:108
+#, no-c-format
+msgid "OPERATORS:  Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:114
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:117
+#, no-c-format
+msgid "TRIVIAL_FUNCS:  Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:120
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:123
+#, no-c-format
+msgid "ALL_TRIVIAL:  Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:126
+#, no-c-format
+msgid ""
+"Visibility level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:129
+#, no-c-format
+msgid "VIS_NONE:  No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:132
+#, no-c-format
+msgid "VIS_PRIVATE :  only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:135
+#, no-c-format
+msgid "VIS_PROTECTED  only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:138
+#, no-c-format
+msgid "VIS_PUBLIC   only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:141
+#, no-c-format
+msgid "VIS_JBoss_Transactions_Administrators_Guide   only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:144
+#, no-c-format
+msgid "VIS_ALL:  Full Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:147
+#, no-c-format
+msgid ""
+"Facility Code – JBoss Transactions uses the following values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:150
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:153
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:156
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:159
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:162
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:165
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:174
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:177
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:180
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"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 JBoss Transactions module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:184
+#, no-c-format
+msgid ""
+"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 CommonLogging.xml, enables all debug "
+"messages related to the Crash Recovery protocol and issued by the JBoss "
+"Transactions module."
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:186
+#, no-c-format
+msgid ""
+"&lt;!-- Common logging related properties. --&gt;\n"
+"&lt;property\n"
+"  name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+"  value=\"0x00000000\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:189
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:192
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:196
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:198
+#, no-c-format
+msgid ""
+"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
+"<literal>periodicWorkSecondPass</literal>. At an interval (defined by "
+"property <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
+"classname>), the RecoveryManager will call the first pass method on each "
+"property, then wait for a brief period (defined by property <classname>com."
+"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>), 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:199
+#, no-c-format
+msgid ""
+"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 "
+"<classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
+"classname> 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)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the <literal>periodicRecoveryPeriod</"
+"literal>, <literal>recoveryBackoffPeriod</literal> and the length of time it "
+"takes to scan the stores and to attempt recovery of any in-doubt "
+"transactions found, for all the recovery modules. The recovery attempt time "
+"may include connection timeouts while trying to communicate with processes "
+"or machines that have crashed or are inaccessible (which is why there are "
+"mechanisms in the recovery system to avoid trying to recover the same "
+"transaction for ever). The total iteration time will affect how long a "
+"resource will remain inaccessible after a failure – "
+"<literal>periodicRecoveryPeriod</literal> should be set accordingly (default "
+"is 120 seconds). The <literal>recoveryBackoffPeriod</literal> can be "
+"comparatively short (default is 10 seconds) – its purpose is mainly to "
+"reduce the number of transactions that are candidates for recovery and which "
+"thus require a “call to the original process to see if they are still in "
+"progress"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"In previous versions of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:206
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <classname>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</classname> interface) are supplied with "
+"JBoss Transactions, 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 properties "
+"that begin with “<classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryExtension</classname>”. These will be invoked on each pass of the "
+"periodic recovery in the sort-order of the property names – it is thus "
+"possible to predict the ordering (but note that a failure in an application "
+"process might occur while a periodic recovery pass is in progress). The "
+"default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+"\n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
+"  com.arjuna.ats.txoj.recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:211
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"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 <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> "
+"interface. Implementations of this interface are loaded by giving the class "
+"name as the value of a property whose name begins with <classname>com.arjuna."
+"ats.arjuna.recovery.expiryScanner</classname>. The RecoveryManager calls the "
+"<command>scan()</command> method on each loaded Expiry Scanner "
+"implementation at an interval determined by the property <classname>com."
+"arjuna.ats.arjuna.recovery.expiryScanInterval</classname>. This value is "
+"given in hours – default is 12. An <classname>expiryScanInterval</classname> "
+"value of zero will suppress any expiry scanning. If the value as supplied is "
+"positive, the first scan is performed when RecoveryManager starts; if the "
+"value is negative, the first scan is delayed until after the first interval "
+"(using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:213
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:214
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses JBoss Transactions – 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 <classname>com.arjuna."
+"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> (in hours "
+"– default is 12, zero means never expire). The expiry time should be greater "
+"than the lifetime of any single JBoss Transactions-using process."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:217
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery."
+"ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:220
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:221
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:224
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"<classname>OutOfMemoryError</classname>) and JBoss Transactions has "
+"attempted to do some cleanup (by running the garbage collector) before re-"
+"throwing the exception. This is probably a transient problem and retrying "
+"the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:227
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:230
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:233
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:236
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:241
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:242
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:245
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the JBoss Transactions "
+"product."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:248
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:252
+#, no-c-format
+msgid ""
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:255
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:258
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaTMImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:261
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaUTImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:265
+#, no-c-format
+msgid ""
+"these settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Feedback.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Feedback.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Feedback.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,34 @@
+# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Feedback.xml:6
+#, no-c-format
+msgid "Feedback"
+msgstr ""
+
+#. Tag: para
+#: Feedback.xml:7
+#, no-c-format
+msgid ""
+"If you spot a typo in this guide, or if you have thought of a way to make "
+"this manual better, we would love to hear from you! Submit a report in "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> against "
+"the Product: JBoss Enterprise Application Platform, Version: "
+"<replaceable>&lt;version&gt;</replaceable>, Component: <emphasis>Doc</"
+"emphasis>. If you have a suggestion for improving the documentation, try to "
+"be as specific as possible. If you have found an error, include the section "
+"number and some of the surrounding text so we can find it easily."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/JBoss_Transactions_Administrators_Guide.po
===================================================================

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Preface.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Preface.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,123 @@
+# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:14
+#, no-c-format
+msgid "What This Guide Contains"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:15
+#, no-c-format
+msgid ""
+"The Administration Guide contains information on how to administer JBoss "
+"Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:17
+#, no-c-format
+msgid "Audience"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:18
+#, no-c-format
+msgid ""
+"This guide is most relevant to engineers who are responsible for "
+"administration of JBoss Transactions API 4.2.3 installations."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:21
+#, no-c-format
+msgid "Prerequisites"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:22
+#, no-c-format
+msgid ""
+"In order to administer JBoss Transactions it is first necessary to "
+"understand that it relies on ArjunaCore for a lot of the transaction "
+"functionality. As such, it is important to read the ArjunaCore "
+"Administration Guide before attempting to administer JBoss Transactions."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:25
+#, no-c-format
+msgid "Organization"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:26
+#, no-c-format
+msgid "This guide contains the following chapters:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:29
+#, no-c-format
+msgid ""
+"Chapter 1, Administration of JBoss Transactions: describes how to administer "
+"JBoss Transactions, mainly by selecting the variant of JTA implementation: "
+"pure local or remote (allowing distributed transactions)."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:34
+#, no-c-format
+msgid "Additional Documentation"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:35
+#, no-c-format
+msgid ""
+"In addition to this guide, the following guides are available in the JBoss "
+"Transactions API 4.2.3 documentation set:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:38
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
+"information about JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:41
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
+"instructions for installing JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:44
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
+"writing applications."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/es-ES/Revision_History.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: author
+#: Revision_History.xml:9
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Appendix.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Appendix.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Author_Group.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Author_Group.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,29 @@
+# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "FF0000 Headgear Documentation Group"
+msgstr ""
+
+#. Tag: author
+#: Author_Group.xml:7
+#, no-c-format
+msgid ""
+"<firstname>Dude</firstname> <surname>McDude</surname> <affiliation> "
+"<orgname>My Org</orgname> <orgdiv>Best Div in the place</orgdiv> </"
+"affiliation> <email>dude.mcdude at myorg.org</email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Book_Info.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Book_Info.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,40 @@
+# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions API 4.2.3 Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:10
+#, no-c-format
+msgid "JBoss Enterprise Application Platform"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid ""
+"This book is the JBoss Enterprise Application Platform edition of the JBoss "
+"Transactions Administrators Guide"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:22
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Chapter.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Chapter.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Chapter.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,932 @@
+# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Chapter.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:7
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBoss Transactions software. "
+"There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:10
+#, no-c-format
+msgid ""
+"The present implementation of the JBoss TA system provides no security or "
+"protection for data. The objects stored in the JBoss Transactions object "
+"store are (typically) owned by the user who ran the application that created "
+"them. The Object Store and Object Manager facilities make no attempt to "
+"enforce even the limited form of protection that Unix/Windows provides. "
+"There is no checking of user or group IDs on access to objects for either "
+"reading or writing."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:13
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"StateManager.destroy method is invoked on the object or some application "
+"program explicitly deletes them. This means that the Object Store gradually "
+"accumulates garbage (especially during application development and testing "
+"phases). At present we have no automated garbage collection facility. "
+"Further, we have not addressed the problem of dangling references. That is, "
+"a persistent object, A, may have stored a Uid for another persistent object, "
+"B, in its passive representation on disk. There is nothing to prevent an "
+"application from deleting B even though A still contains a reference to it. "
+"When A is next activated and attempts to access B, a run-time error will "
+"occur."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:16
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The JBoss Transactions software can "
+"neither detect nor correct references to old object state by new operation "
+"versions or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:19
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:24
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:28
+#, no-c-format
+msgid "JBoss Transactions runtime information"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:29
+#, no-c-format
+msgid ""
+"Each module that comprises JBoss Transactions 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:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"&lt;module-info name=\"arjuna\"&gt;\n"
+"        &lt;source-identifier&gt;unknown&lt;/source-identifier&gt;\n"
+"        &lt;build-information&gt;\n"
+"           Arjuna Technologies [mlittle] (Windows 2000 5.0)\n"
+"        &lt;/build-information&gt;\n"
+"        &lt;version&gt;unknown&lt;/version&gt;\n"
+"        &lt;date&gt;2002/06/15 04:06 PM&lt;/date&gt;\n"
+"        &lt;notes&gt;&lt;/notes&gt;\n"
+"        &lt;configuration&gt;\n"
+"                &lt;properties-file dir=\"null\"&gt;arjuna.properties&lt;/"
+"properties-file&gt;\n"
+"                &lt;object-store-root&gt;null&lt;/object-store-root&gt;\n"
+"        &lt;/configuration&gt;\n"
+"&lt;/module-info&gt;"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:34
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:38
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:41
+#, no-c-format
+msgid ""
+"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 “in-doubt transactions”. For TransactionalObjects for Java "
+"resources, an attempt to activate the Transactional Object (as when trying "
+"to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:43
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:44
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions requires that the stand-"
+"alone Recovery Manager process be running for each ObjectStore (typically "
+"one for each node on the network that is running JBoss Transactions "
+"applications). The RecoveryManager file is located in the arjunacore jar "
+"file within the package <classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryManager</classname>. To start the Recovery Manager issue the "
+"following command:"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:45
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:46
+#, no-c-format
+msgid ""
+"If the <literal>-test</literal> flag is used with the Recovery Manager then "
+"it will display a “Ready” message when initialised, i.e.,"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:47
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:50
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:51
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the <filename>arjuna."
+"properties</filename> file and then also reads the property file "
+"<filename>RecoveryManager.properties</filename>, 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:52
+#, no-c-format
+msgid ""
+"A default version of <filename>RecoveryManager.properties</filename> 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)"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:54
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:55
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:58
+#, no-c-format
+msgid ""
+"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 &lt; INFO &lt; WARN &lt; ERROR &lt; "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:61
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:67
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:71
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:74
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, e.g., constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:77
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:80
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, e.g., the object store."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:83
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. JBoss Transactions uses the default Debugging level and the "
+"default Visibility level provided by CLF, but it defines its own Facility "
+"Code. JBoss Transactions 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 JBoss Transactions "
+"are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"Debugging level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:87
+#, no-c-format
+msgid ""
+"NO_DEBUGGING:  No diagnostics. A logger object assigned with this values "
+"discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:90
+#, no-c-format
+msgid ""
+"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
+"allows all debug requests if the facility code and the visibility level "
+"match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:93
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:96
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid "DESTRUCTORS:  Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:102
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid "FUNCTIONS:  Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:108
+#, no-c-format
+msgid "OPERATORS:  Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:114
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:117
+#, no-c-format
+msgid "TRIVIAL_FUNCS:  Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:120
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:123
+#, no-c-format
+msgid "ALL_TRIVIAL:  Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:126
+#, no-c-format
+msgid ""
+"Visibility level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:129
+#, no-c-format
+msgid "VIS_NONE:  No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:132
+#, no-c-format
+msgid "VIS_PRIVATE :  only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:135
+#, no-c-format
+msgid "VIS_PROTECTED  only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:138
+#, no-c-format
+msgid "VIS_PUBLIC   only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:141
+#, no-c-format
+msgid "VIS_JBoss_Transactions_Administrators_Guide   only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:144
+#, no-c-format
+msgid "VIS_ALL:  Full Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:147
+#, no-c-format
+msgid ""
+"Facility Code – JBoss Transactions uses the following values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:150
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:153
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:156
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:159
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:162
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:165
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:174
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:177
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:180
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"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 JBoss Transactions module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:184
+#, no-c-format
+msgid ""
+"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 CommonLogging.xml, enables all debug "
+"messages related to the Crash Recovery protocol and issued by the JBoss "
+"Transactions module."
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:186
+#, no-c-format
+msgid ""
+"&lt;!-- Common logging related properties. --&gt;\n"
+"&lt;property\n"
+"  name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+"  value=\"0x00000000\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:189
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:192
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:196
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:198
+#, no-c-format
+msgid ""
+"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
+"<literal>periodicWorkSecondPass</literal>. At an interval (defined by "
+"property <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
+"classname>), the RecoveryManager will call the first pass method on each "
+"property, then wait for a brief period (defined by property <classname>com."
+"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>), 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:199
+#, no-c-format
+msgid ""
+"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 "
+"<classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
+"classname> 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)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the <literal>periodicRecoveryPeriod</"
+"literal>, <literal>recoveryBackoffPeriod</literal> and the length of time it "
+"takes to scan the stores and to attempt recovery of any in-doubt "
+"transactions found, for all the recovery modules. The recovery attempt time "
+"may include connection timeouts while trying to communicate with processes "
+"or machines that have crashed or are inaccessible (which is why there are "
+"mechanisms in the recovery system to avoid trying to recover the same "
+"transaction for ever). The total iteration time will affect how long a "
+"resource will remain inaccessible after a failure – "
+"<literal>periodicRecoveryPeriod</literal> should be set accordingly (default "
+"is 120 seconds). The <literal>recoveryBackoffPeriod</literal> can be "
+"comparatively short (default is 10 seconds) – its purpose is mainly to "
+"reduce the number of transactions that are candidates for recovery and which "
+"thus require a “call to the original process to see if they are still in "
+"progress"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"In previous versions of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:206
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <classname>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</classname> interface) are supplied with "
+"JBoss Transactions, 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 properties "
+"that begin with “<classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryExtension</classname>”. These will be invoked on each pass of the "
+"periodic recovery in the sort-order of the property names – it is thus "
+"possible to predict the ordering (but note that a failure in an application "
+"process might occur while a periodic recovery pass is in progress). The "
+"default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+"\n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
+"  com.arjuna.ats.txoj.recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:211
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"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 <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> "
+"interface. Implementations of this interface are loaded by giving the class "
+"name as the value of a property whose name begins with <classname>com.arjuna."
+"ats.arjuna.recovery.expiryScanner</classname>. The RecoveryManager calls the "
+"<command>scan()</command> method on each loaded Expiry Scanner "
+"implementation at an interval determined by the property <classname>com."
+"arjuna.ats.arjuna.recovery.expiryScanInterval</classname>. This value is "
+"given in hours – default is 12. An <classname>expiryScanInterval</classname> "
+"value of zero will suppress any expiry scanning. If the value as supplied is "
+"positive, the first scan is performed when RecoveryManager starts; if the "
+"value is negative, the first scan is delayed until after the first interval "
+"(using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:213
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:214
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses JBoss Transactions – 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 <classname>com.arjuna."
+"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> (in hours "
+"– default is 12, zero means never expire). The expiry time should be greater "
+"than the lifetime of any single JBoss Transactions-using process."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:217
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery."
+"ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:220
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:221
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:224
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"<classname>OutOfMemoryError</classname>) and JBoss Transactions has "
+"attempted to do some cleanup (by running the garbage collector) before re-"
+"throwing the exception. This is probably a transient problem and retrying "
+"the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:227
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:230
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:233
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:236
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:241
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:242
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:245
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the JBoss Transactions "
+"product."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:248
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:252
+#, no-c-format
+msgid ""
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:255
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:258
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaTMImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:261
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaUTImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:265
+#, no-c-format
+msgid ""
+"these settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Feedback.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Feedback.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Feedback.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,34 @@
+# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Feedback.xml:6
+#, no-c-format
+msgid "Feedback"
+msgstr ""
+
+#. Tag: para
+#: Feedback.xml:7
+#, no-c-format
+msgid ""
+"If you spot a typo in this guide, or if you have thought of a way to make "
+"this manual better, we would love to hear from you! Submit a report in "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> against "
+"the Product: JBoss Enterprise Application Platform, Version: "
+"<replaceable>&lt;version&gt;</replaceable>, Component: <emphasis>Doc</"
+"emphasis>. If you have a suggestion for improving the documentation, try to "
+"be as specific as possible. If you have found an error, include the section "
+"number and some of the surrounding text so we can find it easily."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/JBoss_Transactions_Administrators_Guide.po
===================================================================

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Preface.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Preface.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,123 @@
+# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:14
+#, no-c-format
+msgid "What This Guide Contains"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:15
+#, no-c-format
+msgid ""
+"The Administration Guide contains information on how to administer JBoss "
+"Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:17
+#, no-c-format
+msgid "Audience"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:18
+#, no-c-format
+msgid ""
+"This guide is most relevant to engineers who are responsible for "
+"administration of JBoss Transactions API 4.2.3 installations."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:21
+#, no-c-format
+msgid "Prerequisites"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:22
+#, no-c-format
+msgid ""
+"In order to administer JBoss Transactions it is first necessary to "
+"understand that it relies on ArjunaCore for a lot of the transaction "
+"functionality. As such, it is important to read the ArjunaCore "
+"Administration Guide before attempting to administer JBoss Transactions."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:25
+#, no-c-format
+msgid "Organization"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:26
+#, no-c-format
+msgid "This guide contains the following chapters:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:29
+#, no-c-format
+msgid ""
+"Chapter 1, Administration of JBoss Transactions: describes how to administer "
+"JBoss Transactions, mainly by selecting the variant of JTA implementation: "
+"pure local or remote (allowing distributed transactions)."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:34
+#, no-c-format
+msgid "Additional Documentation"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:35
+#, no-c-format
+msgid ""
+"In addition to this guide, the following guides are available in the JBoss "
+"Transactions API 4.2.3 documentation set:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:38
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
+"information about JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:41
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
+"instructions for installing JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:44
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
+"writing applications."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/fr-FR/Revision_History.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: author
+#: Revision_History.xml:9
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/ja-JP/Chapter.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/ja-JP/Chapter.po	2008-06-05 22:46:25 UTC (rev 74211)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/ja-JP/Chapter.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -7,7 +7,7 @@
 msgstr ""
 "Project-Id-Version: Chapter\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-05-12 00:15+0000\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
 "PO-Revision-Date: 2008-05-19 13:04+1000\n"
 "Last-Translator: Noriko Mizumoto <noriko at redhat.com>\n"
 "Language-Team: Japanese <fedora-trans-ja at redhat.com>\n"
@@ -29,7 +29,10 @@
 "Apart from ensuring that the run-time system is executing normally, there is "
 "little continuous administration needed for the JBoss Transactions software. "
 "There are a few points however, that should be made:"
-msgstr "ランタイムシステムが正常に実行していることを確認する他、 JBoss Transactions ソフトウェアには継続的に行う必要のある管理が若干あります。 以下にいくつか注意事項を記します。"
+msgstr ""
+"ランタイムシステムが正常に実行していることを確認する他、 JBoss Transactions "
+"ソフトウェアには継続的に行う必要のある管理が若干あります。 以下にいくつか注意"
+"事項を記します。"
 
 #. Tag: para
 #: Chapter.xml:10
@@ -42,7 +45,14 @@
 "enforce even the limited form of protection that Unix/Windows provides. "
 "There is no checking of user or group IDs on access to objects for either "
 "reading or writing."
-msgstr "JBoss TA の現在の実装はデータの保護やセキュリティは提供しません。 JBoss Transactions オブジェクトストアに格納されるオブジェクトは (一般的に) それを作成したアプリケーションの実行を行ったユーザーに所有されます。 Object Store および Object Manager の機能は、 Unix/Windows が提供する限定形式の保護であってもまったく実施しません。 読み取りまたは書き込みいずれかのためオブジェクトに行われるアクセスに関してユーザーまたはグループの ID によるチェックはありません。"
+msgstr ""
+"JBoss TA の現在の実装はデータの保護やセキュリティは提供しません。 JBoss "
+"Transactions オブジェクトストアに格納されるオブジェクトは (一般的に) それを作"
+"成したアプリケーションの実行を行ったユーザーに所有されます。 Object Store お"
+"よび Object Manager の機能は、 Unix/Windows が提供する限定形式の保護であって"
+"もまったく実施しません。 読み取りまたは書き込みいずれかのためオブジェクトに行"
+"われるアクセスに関してユーザーまたはグループの ID によるチェックはありませ"
+"ん。"
 
 #. Tag: para
 #: Chapter.xml:13
@@ -73,13 +83,23 @@
 "converted to the new representation. The JBoss Transactions software can "
 "neither detect nor correct references to old object state by new operation "
 "versions or vice versa."
-msgstr "クラスの構成が変更になった場合、 データベースの再構成やオブジェクトのバージョン管理に関するサポートは現在ありません。 これは対処していない複雑な研究分野になります。 現時点では、 永続オブジェクトのクラスの定義を変更する場合は、 Object Store 内のオブジェクトの既存インスタンスが新しい表現に変換されるかは確約できませんので必ず確認を行ってください。 JBoss Transactions ソフトウェアは新しいオペレーションバージョンで旧オブジェクトの状態への参照を検出することも修正することもできません、 またこの逆もできません。"
+msgstr ""
+"クラスの構成が変更になった場合、 データベースの再構成やオブジェクトのバージョ"
+"ン管理に関するサポートは現在ありません。 これは対処していない複雑な研究分野に"
+"なります。 現時点では、 永続オブジェクトのクラスの定義を変更する場合は、 "
+"Object Store 内のオブジェクトの既存インスタンスが新しい表現に変換されるかは確"
+"約できませんので必ず確認を行ってください。 JBoss Transactions ソフトウェアは"
+"新しいオペレーションバージョンで旧オブジェクトの状態への参照を検出することも"
+"修正することもできません、 またこの逆もできません。"
 
 #. Tag: para
 #: Chapter.xml:19
 #, no-c-format
-msgid "Object store management is critically important to the transaction service."
-msgstr "オブジェクトストア管理はトランザクションサービスにとって非常に重要となります。"
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+"オブジェクトストア管理はトランザクションサービスにとって非常に重要となりま"
+"す。"
 
 #. Tag: title
 #: Chapter.xml:24
@@ -103,7 +123,18 @@
 "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."
-msgstr "トランザクションサービスのインストール内で、 オブジェクトストアはトランザクションが作成されるとき、 または Java 用の Transactional Objects が使用される場合必ず更新されます。 障害なしの環境では、 オブジェクトストア内に常駐すべきオブジェクトの状態のみが Java API の Transactional Objects で作成されるオブジェクトを表現するものとなります。 ただし、 障害が発生すると、クラッシュリカバリの機能が表しているトランザクションを解決するまでトランザクションログはオブジェクトストア内に残る可能性があります。 このため、 オブジェクトストアの内容は十分な注意を払わずに削除されると疑わしいトランザクション内での解決が不可能となるため、 非常に重要です。 また、 複数のユーザーが同じオブジェクトã!
 ‚¹ãƒˆã‚¢ã‚’共有する場合、 ユーザーはこれをよく認識してリソースは共有されないものとしてオブジェクトストアの内容を削除しないようにすることが重要です。"
+msgstr ""
+"トランザクションサービスのインストール内で、 オブジェクトストアはトランザク"
+"ションが作成されるとき、 または Java 用の Transactional Objects が使用される"
+"場合必ず更新されます。 障害なしの環境では、 オブジェクトストア内に常駐すべき"
+"オブジェクトの状態のみが Java API の Transactional Objects で作成されるオブ"
+"ジェクトを表現するものとなります。 ただし、 障害が発生すると、クラッシュリカ"
+"バリの機能が表しているトランザクションを解決するまでトランザクションログはオ"
+"ブジェクトストア内に残る可能性があります。 このため、 オブジェクトストアの内"
+"容は十分な注意を払わずに削除されると疑わしいトランザクション内での解決が不可"
+"能となるため、 非常に重要です。 また、 複数のユーザーが同じオブジェクトストア"
+"を共有する場合、 ユーザーはこれをよく認識してリソースは共有されないものとして"
+"オブジェクトストアの内容を削除しないようにすることが重要です。"
 
 #. Tag: title
 #: Chapter.xml:28
@@ -119,7 +150,10 @@
 "These classes all provide a single toString method that returns an XML "
 "document representing the configuration information for that module. So, for "
 "example:"
-msgstr "JBoss Transactions を構成する各モジュールは Info と呼ばれるクラスを持っています。 これらのクラスはすべて単一の toString メソッドを提供し、 そのモジュール用の設定情報を表す XML ドキュメントを返します。 たとえば、"
+msgstr ""
+"JBoss Transactions を構成する各モジュールは Info と呼ばれるクラスを持っていま"
+"す。 これらのクラスはすべて単一の toString メソッドを提供し、 そのモジュール"
+"用の設定情報を表す XML ドキュメントを返します。 たとえば、"
 
 #. Tag: programlisting
 #: Chapter.xml:31
@@ -176,13 +210,26 @@
 "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."
-msgstr "JBoss Transactions の障害リカバリサブシステムは、 アプリケーションプロセスやそれをホストしているマシンのいずれかがクラッシュしたりネットワーク接続を失った場合にでも、 トランザクションの結果がトランザクションにより影響されるすべてのリソースに対して常に必ず適用されるようにします。 マシン (システム) のクラッシュやネットワーク障害が発生した場合、 そのシステムまたはネットワークが回復されるまでリカバリは行われませんが、 オリジナルのアプリケーションは起動される必要はありません。 リカバリ処理は Recovery Manager のプロセスに委任されます (以下を参照)。 傷害後のリカバリにはトランザクションとリソースに関する情報が障害を逃れて存続しその後アクセス可能であることが要されます。 ã!
 “の情報は ActionStore に維持され、 これは ObjectStore の一部になります。"
+msgstr ""
+"JBoss Transactions の障害リカバリサブシステムは、 アプリケーションプロセスや"
+"それをホストしているマシンのいずれかがクラッシュしたりネットワーク接続を失っ"
+"た場合にでも、 トランザクションの結果がトランザクションにより影響されるすべて"
+"のリソースに対して常に必ず適用されるようにします。 マシン (システム) のクラッ"
+"シュやネットワーク障害が発生した場合、 そのシステムまたはネットワークが回復さ"
+"れるまでリカバリは行われませんが、 オリジナルのアプリケーションは起動される必"
+"要はありません。 リカバリ処理は Recovery Manager のプロセスに委任されます (以"
+"下を参照)。 傷害後のリカバリにはトランザクションとリソースに関する情報が障害"
+"を逃れて存続しその後アクセス可能であることが要されます。 この情報は "
+"ActionStore に維持され、 これは ObjectStore の一部になります。"
 
 #. Tag: para
 #: Chapter.xml:38
 #, no-c-format
-msgid "If the ObjectStore is destroyed or modified, recovery may not be possible."
-msgstr "ObjectStore が破棄または変更されると、 リカバリができなくなる可能性があります。"
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+"ObjectStore が破棄または変更されると、 リカバリができなくなる可能性がありま"
+"す。"
 
 #. Tag: para
 #: Chapter.xml:41
@@ -194,7 +241,12 @@
 "held by “in-doubt transactions”. For TransactionalObjects for Java "
 "resources, an attempt to activate the Transactional Object (as when trying "
 "to get a lock) will fail."
-msgstr "リカバリの手順が完了するまで、 障害発生時に実行中だったトランザクションによって影響を受けるリソースはアクセスできない可能性があります。 データベースのリソースについては、 “in-doubt transactions” で維持される表または列として報告される可能性があります。 Java の TransactionalObjects リソースについては、 Transactional Object の起動の試行が失敗します (ロック取得試行時)。"
+msgstr ""
+"リカバリの手順が完了するまで、 障害発生時に実行中だったトランザクションによっ"
+"て影響を受けるリソースはアクセスできない可能性があります。 データベースのリ"
+"ソースについては、 “in-doubt transactions” で維持される表または列として報告さ"
+"れる可能性があります。 Java の TransactionalObjects リソースについては、 "
+"Transactional Object の起動の試行が失敗します (ロック取得試行時)。"
 
 #. Tag: title
 #: Chapter.xml:43
@@ -213,7 +265,13 @@
 "file within the package <classname>com.arjuna.ats.arjuna.recovery."
 "RecoveryManager</classname>. To start the Recovery Manager issue the "
 "following command:"
-msgstr "JBoss Transactions の障害リカバリサブシステムは、 スタンドアローンの Recovery Manager プロセスが各 ObjectStore (一般的に JBoss Transactions アプリケーションを実行しているネットワーク上の各ノードに 1 つ) に対して実行している必要があります。 RecoveryManager ファイルは <classname>com.arjuna.ats.arjuna.recovery.RecoveryManager</classname> パッケージ内の arjunacore jar ファイルにあります。 Recovery Manager を起動するには次のコマンドを実行します。"
+msgstr ""
+"JBoss Transactions の障害リカバリサブシステムは、 スタンドアローンの "
+"Recovery Manager プロセスが各 ObjectStore (一般的に JBoss Transactions アプリ"
+"ケーションを実行しているネットワーク上の各ノードに 1 つ) に対して実行している"
+"必要があります。 RecoveryManager ファイルは <classname>com.arjuna.ats.arjuna."
+"recovery.RecoveryManager</classname> パッケージ内の arjunacore jar ファイルに"
+"あります。 Recovery Manager を起動するには次のコマンドを実行します。"
 
 #. Tag: command
 #: Chapter.xml:45
@@ -227,7 +285,9 @@
 msgid ""
 "If the <literal>-test</literal> flag is used with the Recovery Manager then "
 "it will display a “Ready” message when initialised, i.e.,"
-msgstr "Recovery Manager で <literal>-test</literal> フラグが使用される場合、 初期化すると “Ready” メッセージが表示されます。"
+msgstr ""
+"Recovery Manager で <literal>-test</literal> フラグが使用される場合、 初期化"
+"すると “Ready” メッセージが表示されます。"
 
 #. Tag: command
 #: Chapter.xml:47
@@ -252,7 +312,13 @@
 "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."
-msgstr "RecoveryManager は <filename>arjuna.properties</filename> ファイルに定義されるプロパティを読み込み、 また arjuna プロパティファイルを発見した同じディレクトリから <filename>RecoveryManager.properties</filename> プロパティファイルを読み込みます。 RecoveryManager プロパティファイル内のプロパティのエントリはメインの TransactionService プロパティファイル内の同じプロパティのエントリを上書きします。 ほとんどのエントリは Recovery Manager 固有となります。"
+msgstr ""
+"RecoveryManager は <filename>arjuna.properties</filename> ファイルに定義され"
+"るプロパティを読み込み、 また arjuna プロパティファイルを発見した同じディレク"
+"トリから <filename>RecoveryManager.properties</filename> プロパティファイルを"
+"読み込みます。 RecoveryManager プロパティファイル内のプロパティのエントリはメ"
+"インの TransactionService プロパティファイル内の同じプロパティのエントリを上"
+"書きします。 ほとんどのエントリは Recovery Manager 固有となります。"
 
 #. Tag: para
 #: Chapter.xml:52
@@ -264,7 +330,12 @@
 "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)"
-msgstr "<filename>RecoveryManager.properties</filename> のデフォルトバージョンはディストリビューションに同梱されます。 おそらくデバッグ追跡フィールド (以下参照、 「出力」) 以外は変更することなく使用できます。 これ以降、 本セクションではプロパティを他の値に設定する上での問題について説明していきます (ファイルのデフォルトバージョンで表されている順序)。"
+msgstr ""
+"<filename>RecoveryManager.properties</filename> のデフォルトバージョンはディ"
+"ストリビューションに同梱されます。 おそらくデバッグ追跡フィールド (以下参"
+"照、 「出力」) 以外は変更することなく使用できます。 これ以降、 本セクションで"
+"はプロパティを他の値に設定する上での問題について説明していきます (ファイルの"
+"デフォルトバージョンで表されている順序)。"
 
 #. Tag: title
 #: Chapter.xml:54
@@ -285,8 +356,14 @@
 "Commons Logging framework and configuration is assumed to occur through that "
 "framework."
 msgstr ""
-"どのようなリカバリアクティビティが行われたのかの記録を提供するために、 インストールが RecoveryManager からの出力をなんらかの形式で必要とする可能性があります。 "
-"RecoveryManager は Arjuna Common Logging Framework (CLF) によって提供されるログ追跡メカニズムを使用します。 これは Jakarta log4j や JDK 1.4 ロギング API など既存のロギング API 間に存在する違いを隠す高度なレベルのインターフェースを提供します。 CLF は Apache Commons Logging フレームワーク経由ですべてのロギングをインダイレクトするので、 設定はそのフレームワークを通して発生するとみなされます。"
+"どのようなリカバリアクティビティが行われたのかの記録を提供するために、 インス"
+"トールが RecoveryManager からの出力をなんらかの形式で必要とする可能性がありま"
+"す。 RecoveryManager は Arjuna Common Logging Framework (CLF) によって提供さ"
+"れるログ追跡メカニズムを使用します。 これは Jakarta log4j や JDK 1.4 ロギン"
+"グ API など既存のロギング API 間に存在する違いを隠す高度なレベルのインター"
+"フェースを提供します。 CLF は Apache Commons Logging フレームワーク経由ですべ"
+"てのロギングをインダイレクトするので、 設定はそのフレームワークを通して発生す"
+"るとみなされます。"
 
 #. Tag: para
 #: Chapter.xml:58
@@ -300,8 +377,13 @@
 "their integer values as follows: DEBUG &lt; INFO &lt; WARN &lt; ERROR &lt; "
 "FATAL."
 msgstr ""
-"CLF ではアプリケーションはロッガーオブジェクトでロギングのコールを作成します。 ロッガーはロギングの Levels を使って特定のログメッセージに興味があるかを決定することができます。 各ログメッセージはログの Level を関連付け、 これによりログメッセージの重要性や緊急性を与えます。 可能な Log Level のセットは DEBUG、 INFO、 WARN、 ERROR、 FATAL になります。 定義される Level は次のようにその整数値に従って順序付けられます: DEBUG &lt; INFO &lt; WARN &lt; ERROR &lt; "
-"FATAL。"
+"CLF ではアプリケーションはロッガーオブジェクトでロギングのコールを作成しま"
+"す。 ロッガーはロギングの Levels を使って特定のログメッセージに興味があるかを"
+"決定することができます。 各ログメッセージはログの Level を関連付け、 これによ"
+"りログメッセージの重要性や緊急性を与えます。 可能な Log Level のセットは "
+"DEBUG、 INFO、 WARN、 ERROR、 FATAL になります。 定義される Level は次のよう"
+"にその整数値に従って順序付けられます: DEBUG &lt; INFO &lt; WARN &lt; ERROR "
+"&lt; FATAL。"
 
 #. Tag: para
 #: Chapter.xml:61
@@ -311,7 +393,11 @@
 "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."
-msgstr "CLF はアプリケーションが定義する可能性があるより詳細な粒度に従ってロギングメッセージのフィルタを行うため拡張子を提供します。 これは、 ログメッセージが DEBUG レベルでロッガーに提供される場合、 ログメッセージが有効かどうかを判別するため指定できる追加の条件になります。"
+msgstr ""
+"CLF はアプリケーションが定義する可能性があるより詳細な粒度に従ってロギング"
+"メッセージのフィルタを行うため拡張子を提供します。 これは、 ログメッセージが "
+"DEBUG レベルでロッガーに提供される場合、 ログメッセージが有効かどうかを判別す"
+"るため指定できる追加の条件になります。"
 
 #. Tag: para
 #: Chapter.xml:67
@@ -319,13 +405,16 @@
 msgid ""
 "These conditions are applied if and only the DEBUG level is enabled and the "
 "log request performed by the application specifies debugging granularity."
-msgstr "これらの条件は、 DEBUG レベルが有効でアプリケーションによって実行されるログ要求がデバッグの粒度を指定している場合にのみ適用されます。"
+msgstr ""
+"これらの条件は、 DEBUG レベルが有効でアプリケーションによって実行されるログ要"
+"求がデバッグの粒度を指定している場合にのみ適用されます。"
 
 #. Tag: para
 #: Chapter.xml:71
 #, no-c-format
 msgid "When enabled, Debugging is filtered conditionally on three variables:"
-msgstr "有効になると、 Debugging は次の 3 つの変数の条件付きでフィルタされます。"
+msgstr ""
+"有効になると、 Debugging は次の 3 つの変数の条件付きでフィルタされます。"
 
 #. Tag: para
 #: Chapter.xml:74
@@ -333,7 +422,9 @@
 msgid ""
 "Debugging level: this is where the log request with the DEBUG Level is "
 "generated from, e.g., constructors or basic methods."
-msgstr "Debugging レベル: DEBUG Level 月のログ要求が生成される場所です。 例えば、 コンストラクタや基本的なメソッド。"
+msgstr ""
+"Debugging レベル: DEBUG Level 月のログ要求が生成される場所です。 例えば、 コ"
+"ンストラクタや基本的なメソッド。"
 
 #. Tag: para
 #: Chapter.xml:77
@@ -341,7 +432,9 @@
 msgid ""
 "Visibility level: the visibility of the constructor, method, etc. that "
 "generates the debugging."
-msgstr "Visibility レベル: デバッグを生成するコンストラクタ、 メソッドなどの可視性です。"
+msgstr ""
+"Visibility レベル: デバッグを生成するコンストラクタ、 メソッドなどの可視性で"
+"す。"
 
 #. Tag: para
 #: Chapter.xml:80
@@ -349,7 +442,9 @@
 msgid ""
 "Facility code: for instance the package or sub-module within which debugging "
 "is generated, e.g., the object store."
-msgstr "Facility コード: たとえば、 デバッグが生成される場所内のパッケージやサブモジュールです。 例、 オブジェクトストアなど。"
+msgstr ""
+"Facility コード: たとえば、 デバッグが生成される場所内のパッケージやサブモ"
+"ジュールです。 例、 オブジェクトストアなど。"
 
 #. Tag: para
 #: Chapter.xml:83
@@ -363,7 +458,15 @@
 "objects (DEBUG). However, it uses the finer debugging features to disable or "
 "enable debug messages. Finer debugging values used by the JBoss Transactions "
 "are defined below:"
-msgstr "これらの変数にしたがって、 CLF は 3 つのインターフェースを定義します。 特定のプロダクトがそれ自体の詳細な粒度にしたがいそれ自体のクラスを実装することができます。 JBoss Transactions はデフォルトの Debugging レベルおよび CLF によって提供されるデフォルトの Visibility レベルを使用しますが、 それ自体の Facility コードは定義します。 JBoss Transactions はそのロッガーオブジェクト (DEBUG) に割り当てられるデフォルトのレベルを使用します。 ただし、 デバッグメッセージの無効化または有効化にはより詳細なデバッグ機能を使用します。 JBoss Transactions で使用される詳細なデバッグの値は以下のように定義されます。"
+msgstr ""
+"これらの変数にしたがって、 CLF は 3 つのインターフェースを定義します。 特定の"
+"プロダクトがそれ自体の詳細な粒度にしたがいそれ自体のクラスを実装することがで"
+"きます。 JBoss Transactions はデフォルトの Debugging レベルおよび CLF によっ"
+"て提供されるデフォルトの Visibility レベルを使用しますが、 それ自体の "
+"Facility コードは定義します。 JBoss Transactions はそのロッガーオブジェクト "
+"(DEBUG) に割り当てられるデフォルトのレベルを使用します。 ただし、 デバッグ"
+"メッセージの無効化または有効化にはより詳細なデバッグ機能を使用します。 JBoss "
+"Transactions で使用される詳細なデバッグの値は以下のように定義されます。"
 
 #. Tag: para
 #: Chapter.xml:84
@@ -371,7 +474,9 @@
 msgid ""
 "Debugging level – JBoss Transactions uses the default values defined in the "
 "class <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
-msgstr "Debugging レベル – JBoss Transactions はクラス <classname>com.arjuna.common.util.logging.DebugLevel</classname> で定義されるデフォルトの値を使用します。"
+msgstr ""
+"Debugging レベル – JBoss Transactions はクラス <classname>com.arjuna.common."
+"util.logging.DebugLevel</classname> で定義されるデフォルトの値を使用します。"
 
 #. Tag: para
 #: Chapter.xml:87
@@ -379,7 +484,9 @@
 msgid ""
 "NO_DEBUGGING:  No diagnostics. A logger object assigned with this values "
 "discard all debug requests"
-msgstr "NO_DEBUGGING: 診断なしです。 この値を付けて割り当てられるロッガーオブジェクトはすべてのデバッグ要求を破棄します。"
+msgstr ""
+"NO_DEBUGGING: 診断なしです。 この値を付けて割り当てられるロッガーオブジェクト"
+"はすべてのデバッグ要求を破棄します。"
 
 #. Tag: para
 #: Chapter.xml:90
@@ -388,7 +495,10 @@
 "FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
 "allows all debug requests if the facility code and the visibility level "
 "match those allowed by the logger."
-msgstr "FULL_DEBUGGING: 完全診断です。 この値を付けて割り当てられるロッガーオブジェクトは、 facility コードと visibility レベルがそのロッガーで許可されるそれらと一致する場合にすべてのデバッグ要求を許可します。"
+msgstr ""
+"FULL_DEBUGGING: 完全診断です。 この値を付けて割り当てられるロッガーオブジェク"
+"トは、 facility コードと visibility レベルがそのロッガーで許可されるそれらと"
+"一致する場合にすべてのデバッグ要求を許可します。"
 
 #. Tag: para
 #: Chapter.xml:93
@@ -462,7 +572,10 @@
 msgid ""
 "Visibility level – JBoss Transactions uses the default values defined in the "
 "class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
-msgstr "Visibility レベル – JBoss Transactions はクラス <classname>com.arjuna.common.util.logging.VisibilityLevel</classname> で定義されるデフォルトの値を使用します。"
+msgstr ""
+"Visibility レベル – JBoss Transactions はクラス <classname>com.arjuna.common."
+"util.logging.VisibilityLevel</classname> で定義されるデフォルトの値を使用しま"
+"す。"
 
 #. Tag: para
 #: Chapter.xml:129
@@ -490,9 +603,9 @@
 
 #. Tag: para
 #: Chapter.xml:141
-#, no-c-format
-msgid "VIS_JBoss_Transactions_Administrators_Guide   only from package methods."
-msgstr "VIS_JBoss_Transactions_Administrators_Guide  パッケージメソッドからのみです。"
+#, fuzzy, no-c-format
+msgid "VIS_PACKAGE   only from package methods."
+msgstr "VIS_PUBLIC  パブリックメソッドからのみです。"
 
 #. Tag: para
 #: Chapter.xml:144
@@ -506,7 +619,10 @@
 msgid ""
 "Facility Code – JBoss Transactions uses the following values defined in the "
 "class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
-msgstr "Facility コード – JBoss Transactions はクラス <classname>com.arjuna.common.util.logging.VisibilityLevel</classname> で定義される次のような値を使用します。"
+msgstr ""
+"Facility コード – JBoss Transactions はクラス <classname>com.arjuna.common."
+"util.logging.VisibilityLevel</classname> で定義される次のような値を使用しま"
+"す。"
 
 #. Tag: para
 #: Chapter.xml:150
@@ -556,7 +672,9 @@
 msgid ""
 "FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
 "classes)."
-msgstr "FAC_CRASH_RECOVERY = 0x00000800 (クラッシュリカバリモジュールとクラスの詳細なとレース)。"
+msgstr ""
+"FAC_CRASH_RECOVERY = 0x00000800 (クラッシュリカバリモジュールとクラスの詳細な"
+"とレース)。"
 
 #. Tag: para
 #: Chapter.xml:174
@@ -573,8 +691,10 @@
 #. Tag: para
 #: Chapter.xml:180
 #, no-c-format
-msgid "FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
-msgstr "FAC_RECOVERY_NORMAL = 0x00040000 (クラッシュリカバリマネージャの通常出力)。"
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (クラッシュリカバリマネージャの通常出力)。"
 
 #. Tag: para
 #: Chapter.xml:183
@@ -583,7 +703,10 @@
 "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 JBoss Transactions module."
-msgstr "適切な出力を確認するため、 <filename>CommonLogging.xml</filename> ファイルで明示的に詳細なデバッグプロパティをいくつか設定して JBoss Transactions モジュールで発行されるロギングメッセージを有効にする必要があります。"
+msgstr ""
+"適切な出力を確認するため、 <filename>CommonLogging.xml</filename> ファイルで"
+"明示的に詳細なデバッグプロパティをいくつか設定して JBoss Transactions モ"
+"ジュールで発行されるロギングメッセージを有効にする必要があります。"
 
 #. Tag: para
 #: Chapter.xml:184
@@ -595,7 +718,13 @@
 "the following configuration, in the CommonLogging.xml, enables all debug "
 "messages related to the Crash Recovery protocol and issued by the JBoss "
 "Transactions module."
-msgstr "RecoveryManager によって作成される開始と定期的な動作を説明しているメッセージは INFO レベルを使用する出力です。 他のデバッグトレーシングが必要な場合は、 詳細なデバッグレベルを適切に設定されなければなりません。 たとえば、 次の設定の CommonLogging.xml で、 Crash Recovery プロトコルに関連し JBoss Transactions モジュールによって発行されるデバッグメッセージはすべて有効にします。"
+msgstr ""
+"RecoveryManager によって作成される開始と定期的な動作を説明しているメッセージ"
+"は INFO レベルを使用する出力です。 他のデバッグトレーシングが必要な場合は、 "
+"詳細なデバッグレベルを適切に設定されなければなりません。 たとえば、 次の設定"
+"の CommonLogging.xml で、 Crash Recovery プロトコルに関連し JBoss "
+"Transactions モジュールによって発行されるデバッグメッセージはすべて有効にしま"
+"す。"
 
 #. Tag: programlisting
 #: Chapter.xml:186
@@ -625,7 +754,9 @@
 msgid ""
 "Two logger objects are provided, one manages I18N messages and a second does "
 "not."
-msgstr "2 つのロッガーオブジェクトが提供され、 1 つは I18N メッセージを管理し、 2 番目は管理しません。"
+msgstr ""
+"2 つのロッガーオブジェクトが提供され、 1 つは I18N メッセージを管理し、 2 番"
+"目は管理しません。"
 
 #. Tag: para
 #: Chapter.xml:192
@@ -637,7 +768,14 @@
 "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."
-msgstr "通常のリカバリメッセージを INFO レベルに設定すると RecoveryManager が適度なレポーティングレベルを生成することができるようになります。 何も行われていなければ、 エントリをそれぞれの定期的なパスの各モジュールに報告するだけです。 Recovery Manager によって生成される INFO メッセージを無効にするには、 ロギングレベルをより高いレベルの ERROR に設定すると行うことができます。 レベルを ERROR に設定するということは RecoveryManager が error、 warning、 fatal のメッセージしか生成しないということになります。"
+msgstr ""
+"通常のリカバリメッセージを INFO レベルに設定すると RecoveryManager が適度なレ"
+"ポーティングレベルを生成することができるようになります。 何も行われていなけれ"
+"ば、 エントリをそれぞれの定期的なパスの各モジュールに報告するだけです。 "
+"Recovery Manager によって生成される INFO メッセージを無効にするには、 ロギン"
+"グレベルをより高いレベルの ERROR に設定すると行うことができます。 レベルを "
+"ERROR に設定するということは RecoveryManager が error、 warning、 fatal の"
+"メッセージしか生成しないということになります。"
 
 #. Tag: title
 #: Chapter.xml:196
@@ -658,8 +796,13 @@
 "used are dynamically loaded, using properties found in the RecoveryManager "
 "property file."
 msgstr ""
-"RecoveryManager は ObjectStore および情報のその他の場所をスキャンし、 リカバリを要するまたは要する可能性があるトランザクションとリソースを探します。 このスキャンとリカバリ処理は、 トランザクションまたはリソースの特定カテゴリに対する処理責務を有する各リカバリモジュールによって行われます、 (com.arjuna.ats.arjuna.recovery.RecoveryModule インターフェースを実装するクラスのインスタンス)。 使用されるリカバリモジュールのセットは動的にロードされ、 RecoveryManager "
-"property ファイルにあるプロパティを使用します。"
+"RecoveryManager は ObjectStore および情報のその他の場所をスキャンし、 リカバ"
+"リを要するまたは要する可能性があるトランザクションとリソースを探します。 この"
+"スキャンとリカバリ処理は、 トランザクションまたはリソースの特定カテゴリに対す"
+"る処理責務を有する各リカバリモジュールによって行われます、 (com.arjuna.ats."
+"arjuna.recovery.RecoveryModule インターフェースを実装するクラスのインスタン"
+"ス)。 使用されるリカバリモジュールのセットは動的にロードされ、 "
+"RecoveryManager property ファイルにあるプロパティを使用します。"
 
 #. Tag: para
 #: Chapter.xml:198
@@ -678,8 +821,18 @@
 "it is possible the original application process has crashed and the item is "
 "a candidate for recovery."
 msgstr ""
-"インターフェースには <literal>periodicWorkFirstPass</literal> と <literal>periodicWorkSecondPass</literal> の 2 つのメソッドがあります。 ある間隔で (プロパティ <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
-"classname> によって定義される)、 RecoveryManager は各プロパティで 1 番目のパスをコールし、 少しの期間 (プロパティ <classname>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname> によって定義される) 待機してから、 各モジュールの 2 番目のパスをコールします。 一般的には、 1 番目のパスでモジュールは in-doubt (つまり、 コミットメントプロセスの途中) のリソースまたはトランザクションを検索するためスキャンを行います (例、 ObjectStore の関連部分)。 2 番目のパスで、 同じアイテムのいずれかがいまだ in-doubt の場合、 オリジナルのアプリケーションプロセスがクラッシュしていてそのアイテムがリカバリの候補である可能性があります。"
+"インターフェースには <literal>periodicWorkFirstPass</literal> と "
+"<literal>periodicWorkSecondPass</literal> の 2 つのメソッドがあります。 ある"
+"間隔で (プロパティ <classname>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</classname> によって定義される)、 RecoveryManager は各"
+"プロパティで 1 番目のパスをコールし、 少しの期間 (プロパティ <classname>com."
+"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname> によって定義され"
+"る) 待機してから、 各モジュールの 2 番目のパスをコールします。 一般的には、 "
+"1 番目のパスでモジュールは in-doubt (つまり、 コミットメントプロセスの途中) "
+"のリソースまたはトランザクションを検索するためスキャンを行います (例、 "
+"ObjectStore の関連部分)。 2 番目のパスで、 同じアイテムのいずれかがいまだ in-"
+"doubt の場合、 オリジナルのアプリケーションプロセスがクラッシュしていてそのア"
+"イテムがリカバリの候補である可能性があります。"
 
 #. Tag: para
 #: Chapter.xml:199
@@ -697,8 +850,17 @@
 "usually generating a warning. Recovery of such a transaction is the "
 "RecoveryManager’s responsibility)."
 msgstr ""
-"RecoveryManager によるオリジナルのプロセスでいまだ進行中のトランザクションのリカバリ試行は整合性をブレイクする可能性があります。 これに応じて、 リカバリモジュールはオリジナルのプロセスがいまだ生きているのかどうか、 またトランザクションがいまだ進行中であるのかどうかをチェックするメカニズムを使用します (<classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
-"classname> パッケージ内に実装される)。 RecoveryManager はオリジナルのプロセスがなくなってしまった場合、 あるいはいまだ生きているときはトランザクションが完了した場合にのみ開始されます。 (サーバーのプロセスまたはマシンがクラッシュしたがトランザクション開始のプロセスが生き残っている場合、 このトランザクションは完了して通常は警告を生成します。 このようなトランザクションのリカバリが RecoveryManager の役割となります。)"
+"RecoveryManager によるオリジナルのプロセスでいまだ進行中のトランザクションの"
+"リカバリ試行は整合性をブレイクする可能性があります。 これに応じて、 リカバリ"
+"モジュールはオリジナルのプロセスがいまだ生きているのかどうか、 またトランザク"
+"ションがいまだ進行中であるのかどうかをチェックするメカニズムを使用します "
+"(<classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
+"classname> パッケージ内に実装される)。 RecoveryManager はオリジナルのプロセス"
+"がなくなってしまった場合、 あるいはいまだ生きているときはトランザクションが完"
+"了した場合にのみ開始されます。 (サーバーのプロセスまたはマシンがクラッシュし"
+"たがトランザクション開始のプロセスが生き残っている場合、 このトランザクション"
+"は完了して通常は警告を生成します。 このようなトランザクションのリカバリが "
+"RecoveryManager の役割となります。)"
 
 #. Tag: para
 #: Chapter.xml:200
@@ -720,7 +882,21 @@
 "reduce the number of transactions that are candidates for recovery and which "
 "thus require a “call to the original process to see if they are still in "
 "progress"
-msgstr "間隔の期間を適切に設定することが明らかに重要となります。 合計反復時間は全リカバリモジュールの <literal>periodicRecoveryPeriod</literal>、 <literal>recoveryBackoffPeriod</literal>、 およびスキャンをストアし発見した in-doubt トランザクションのリカバリを試行するのにかかる時間の合計になります。リカバリ試行時間にはクラッシュしたあるいはアクセスできないプロセスやマシンとの通信試行をしている間の接続タイムアウトも含まれることがあります (これが同じトランザクションのリカバリ試行を永久に回避するメカニズムがリカバリシステムにある理由です)。 合計反復時間は障害が発生してからリソースがアクセス不能な状態でいる長さに影響します。 応じて <literal>periodicRecoveryPeriod</literal> を設定しなければなりません (デフã!
 ‚©ãƒ«ãƒˆã¯ 120 ç§’)。 <literal>recoveryBackoffPeriod</literal> は比較的短時間で構いません (デフォルトは 10 ç§’)。 目的は主にリカバリの候補となるためいまだ実行中であるかどうかを確認するのにオリジナルのプロセスのコールを必要とするトランザクション数を減らすことです。"
+msgstr ""
+"間隔の期間を適切に設定することが明らかに重要となります。 合計反復時間は全リカ"
+"バリモジュールの <literal>periodicRecoveryPeriod</literal>、 "
+"<literal>recoveryBackoffPeriod</literal>、 およびスキャンをストアし発見した "
+"in-doubt トランザクションのリカバリを試行するのにかかる時間の合計になります。"
+"リカバリ試行時間にはクラッシュしたあるいはアクセスできないプロセスやマシンと"
+"の通信試行をしている間の接続タイムアウトも含まれることがあります (これが同じ"
+"トランザクションのリカバリ試行を永久に回避するメカニズムがリカバリシステムに"
+"ある理由です)。 合計反復時間は障害が発生してからリソースがアクセス不能な状態"
+"でいる長さに影響します。 応じて <literal>periodicRecoveryPeriod</literal> を"
+"設定しなければなりません (デフォルトは 120 秒)。 "
+"<literal>recoveryBackoffPeriod</literal> は比較的短時間で構いません (デフォル"
+"トは 10 秒)。 目的は主にリカバリの候補となるためいまだ実行中であるかどうかを"
+"確認するのにオリジナルのプロセスのコールを必要とするトランザクション数を減ら"
+"すことです。"
 
 #. Tag: para
 #: Chapter.xml:203
@@ -729,7 +905,10 @@
 "In previous versions of JBoss Transactions 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."
-msgstr "JBoss Transactions の以前のバージョンでは、 コンタクトメカニズムがなかったため空中のトランザクションのキャッチを回避するのに backoff 期間をかなり長くしなければなりませんでした。 3.0 からはこのようなリスクがなくなります。"
+msgstr ""
+"JBoss Transactions の以前のバージョンでは、 コンタクトメカニズムがなかったた"
+"め空中のトランザクションのキャッチを回避するのに backoff 期間をかなり長くしな"
+"ければなりませんでした。 3.0 からはこのようなリスクがなくなります。"
 
 #. Tag: para
 #: Chapter.xml:206
@@ -749,8 +928,13 @@
 "default Recovery Extension settings are:"
 msgstr ""
 "JBoss Transactions には 2 つのリカバリモジュール (<classname>com.arjuna.ats."
-"arjuna.recovery.RecoveryModule</classname> インターフェースの実装) が同梱され、 JDBC リカバリなど各種のリカバリに対応しています。 上級ユーザーの場合、 自分のリカバリモジュールを作成して Recovery Manager に登録することが可能です。 リカバリモジュールは “<classname>com.arjuna.ats.arjuna.recovery."
-"RecoveryExtension</classname>” で始まるプロパティを使って RecoveryManager に登録します。 これらはプロパティ名のソート順で定期的なリカバリの各パスで呼び出されます。 したがって、 "
+"arjuna.recovery.RecoveryModule</classname> インターフェースの実装) が同梱さ"
+"れ、 JDBC リカバリなど各種のリカバリに対応しています。 上級ユーザーの場合、 "
+"自分のリカバリモジュールを作成して Recovery Manager に登録することが可能で"
+"す。 リカバリモジュールは “<classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryExtension</classname>” で始まるプロパティを使って RecoveryManager に"
+"登録します。 これらはプロパティ名のソート順で定期的なリカバリの各パスで呼び出"
+"されます。 したがって、 "
 
 #. Tag: programlisting
 #: Chapter.xml:208
@@ -795,9 +979,20 @@
 "value is negative, the first scan is delayed until after the first interval "
 "(using the absolute value)"
 msgstr ""
-"サブシステムのリカバリの実施により、 通常のプログレスでは削除されない ObjectStore 内にエントリがいくつか作成されることになります。 RecoveryManager にはこれらをスキャンして古いアイテムを削除する機能があります。 スキャンと削除は <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> インターフェースの実装で行われます。 このインターフェースの実装は <classname>com.arjuna."
-"ats.arjuna.recovery.expiryScanner</classname> で始まる名前を持つプロパティの値としてクラス名を与えることでロードされます。 RecoveryManager はプロパティ <classname>com."
-"arjuna.ats.arjuna.recovery.expiryScanInterval</classname> で確定される間隔でロードされる Expiry Scanner の各実装で <command>scan()</command> メソッドをコールします。この値は時間単位で与えます。 デフォルトは 12 時間です。 <classname>expiryScanInterval</classname> の値がゼロは失効のスキャンを抑制します。 与えられる値が整数である場合は、 RecoveryManager が起動したときに最初のスキャンが行われます。 値が負数の場合、 最初のスキャンは最初の間隔まで遅延されます (絶対値を使用)。"
+"サブシステムのリカバリの実施により、 通常のプログレスでは削除されない "
+"ObjectStore 内にエントリがいくつか作成されることになります。 RecoveryManager "
+"にはこれらをスキャンして古いアイテムを削除する機能があります。 スキャンと削除"
+"は <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> イン"
+"ターフェースの実装で行われます。 このインターフェースの実装は <classname>com."
+"arjuna.ats.arjuna.recovery.expiryScanner</classname> で始まる名前を持つプロパ"
+"ティの値としてクラス名を与えることでロードされます。 RecoveryManager はプロパ"
+"ティ <classname>com.arjuna.ats.arjuna.recovery.expiryScanInterval</"
+"classname> で確定される間隔でロードされる Expiry Scanner の各実装で "
+"<command>scan()</command> メソッドをコールします。この値は時間単位で与えま"
+"す。 デフォルトは 12 時間です。 <classname>expiryScanInterval</classname> の"
+"値がゼロは失効のスキャンを抑制します。 与えられる値が整数である場合は、 "
+"RecoveryManager が起動したときに最初のスキャンが行われます。 値が負数の場"
+"合、 最初のスキャンは最初の間隔まで遅延されます (絶対値を使用)。"
 
 #. Tag: para
 #: Chapter.xml:213
@@ -818,8 +1013,14 @@
 "– default is 12, zero means never expire). The expiry time should be greater "
 "than the lifetime of any single JBoss Transactions-using process."
 msgstr ""
-"TransactionStatusManager アイテム: JBoss Transactions を使用する全アプリケーションプロセスによってこれらのひとつが作成されます。 RecoveryManager がトランザクションを開始したプロセスがまだ生きているかどうか、 またそのトランザクション状態を確定できるようにする情報が含まれています。 これらの失効時間はプロパティ <classname>com.arjuna."
-"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> で設定されます (時間単位で、 デフォルトは 12 時間、 0 は失効しないという意味)。 失効時間はいずれの単一 JBoss Transactions 使用プロセスの寿命より長くなければなりません。"
+"TransactionStatusManager アイテム: JBoss Transactions を使用する全アプリケー"
+"ションプロセスによってこれらのひとつが作成されます。 RecoveryManager がトラン"
+"ザクションを開始したプロセスがまだ生きているかどうか、 またそのトランザクショ"
+"ン状態を確定できるようにする情報が含まれています。 これらの失効時間はプロパ"
+"ティ <classname>com.arjuna.ats.arjuna.recovery."
+"transactionStatusManagerExpiryTime</classname> で設定されます (時間単位で、 "
+"デフォルトは 12 時間、 0 は失効しないという意味)。 失効時間はいずれの単一 "
+"JBoss Transactions 使用プロセスの寿命より長くなければなりません。"
 
 #. Tag: para
 #: Chapter.xml:215
@@ -852,7 +1053,10 @@
 "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."
-msgstr "本セクションでは、 トランザクショナルアプリケーションの間に投げられたり報告される可能性のあるエラーや例外のタイプについて説明し、 その原因により起こりそうな兆候をあげておきます。"
+msgstr ""
+"本セクションでは、 トランザクショナルアプリケーションの間に投げられたり報告さ"
+"れる可能性のあるエラーや例外のタイプについて説明し、 その原因により起こりそう"
+"な兆候をあげておきます。"
 
 #. Tag: para
 #: Chapter.xml:224
@@ -863,7 +1067,12 @@
 "attempted to do some cleanup (by running the garbage collector) before re-"
 "throwing the exception. This is probably a transient problem and retrying "
 "the invocation should succeed."
-msgstr "NO_MEMORY: アプリケーションの空きメモリがなくなり (<classname>OutOfMemoryError</classname> が投げられる)、 JBoss Transactions が例外を再度投げるまでになんらかのクリーンアップを試行しています (ガーベッジコレクションを実行)。 これはおそらく一時的な問題で呼び出しを再試行すると成功するはずです。"
+msgstr ""
+"NO_MEMORY: アプリケーションの空きメモリがなくなり "
+"(<classname>OutOfMemoryError</classname> が投げられる)、 JBoss Transactions "
+"が例外を再度投げるまでになんらかのクリーンアップを試行しています (ガーベッジ"
+"コレクションを実行)。 これはおそらく一時的な問題で呼び出しを再試行すると成功"
+"するはずです。"
 
 #. Tag: para
 #: Chapter.xml:227
@@ -979,3 +1188,8 @@
 "be specified if the local implementation is required."
 msgstr ""
 
+#~ msgid ""
+#~ "VIS_JBoss_Transactions_Administrators_Guide   only from package methods."
+#~ msgstr ""
+#~ "VIS_JBoss_Transactions_Administrators_Guide  パッケージメソッドからのみで"
+#~ "す。"

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Appendix.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Appendix.pot	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Appendix.pot	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,21 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Author_Group.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Author_Group.pot	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Author_Group.pot	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,30 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "FF0000 Headgear Documentation Group"
+msgstr ""
+
+#. Tag: author
+#: Author_Group.xml:7
+#, no-c-format
+msgid ""
+"<firstname>Dude</firstname> <surname>McDude</surname> <affiliation> "
+"<orgname>My Org</orgname> <orgdiv>Best Div in the place</orgdiv> </"
+"affiliation> <email>dude.mcdude at myorg.org</email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Book_Info.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Book_Info.pot	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Book_Info.pot	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,41 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions API 4.2.3 Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:10
+#, no-c-format
+msgid "JBoss Enterprise Application Platform"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid ""
+"This book is the JBoss Enterprise Application Platform edition of the JBoss "
+"Transactions Administrators Guide"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:22
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Chapter.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Chapter.pot	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Chapter.pot	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,933 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Chapter.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:7
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBoss Transactions software. "
+"There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:10
+#, no-c-format
+msgid ""
+"The present implementation of the JBoss TA system provides no security or "
+"protection for data. The objects stored in the JBoss Transactions object "
+"store are (typically) owned by the user who ran the application that created "
+"them. The Object Store and Object Manager facilities make no attempt to "
+"enforce even the limited form of protection that Unix/Windows provides. "
+"There is no checking of user or group IDs on access to objects for either "
+"reading or writing."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:13
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"StateManager.destroy method is invoked on the object or some application "
+"program explicitly deletes them. This means that the Object Store gradually "
+"accumulates garbage (especially during application development and testing "
+"phases). At present we have no automated garbage collection facility. "
+"Further, we have not addressed the problem of dangling references. That is, "
+"a persistent object, A, may have stored a Uid for another persistent object, "
+"B, in its passive representation on disk. There is nothing to prevent an "
+"application from deleting B even though A still contains a reference to it. "
+"When A is next activated and attempts to access B, a run-time error will "
+"occur."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:16
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The JBoss Transactions software can "
+"neither detect nor correct references to old object state by new operation "
+"versions or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:19
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:24
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:28
+#, no-c-format
+msgid "JBoss Transactions runtime information"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:29
+#, no-c-format
+msgid ""
+"Each module that comprises JBoss Transactions 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:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"&lt;module-info name=\"arjuna\"&gt;\n"
+"        &lt;source-identifier&gt;unknown&lt;/source-identifier&gt;\n"
+"        &lt;build-information&gt;\n"
+"           Arjuna Technologies [mlittle] (Windows 2000 5.0)\n"
+"        &lt;/build-information&gt;\n"
+"        &lt;version&gt;unknown&lt;/version&gt;\n"
+"        &lt;date&gt;2002/06/15 04:06 PM&lt;/date&gt;\n"
+"        &lt;notes&gt;&lt;/notes&gt;\n"
+"        &lt;configuration&gt;\n"
+"                &lt;properties-file dir=\"null\"&gt;arjuna.properties&lt;/"
+"properties-file&gt;\n"
+"                &lt;object-store-root&gt;null&lt;/object-store-root&gt;\n"
+"        &lt;/configuration&gt;\n"
+"&lt;/module-info&gt;"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:34
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:38
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:41
+#, no-c-format
+msgid ""
+"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 “in-doubt transactions”. For TransactionalObjects for Java "
+"resources, an attempt to activate the Transactional Object (as when trying "
+"to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:43
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:44
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions requires that the stand-"
+"alone Recovery Manager process be running for each ObjectStore (typically "
+"one for each node on the network that is running JBoss Transactions "
+"applications). The RecoveryManager file is located in the arjunacore jar "
+"file within the package <classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryManager</classname>. To start the Recovery Manager issue the "
+"following command:"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:45
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:46
+#, no-c-format
+msgid ""
+"If the <literal>-test</literal> flag is used with the Recovery Manager then "
+"it will display a “Ready” message when initialised, i.e.,"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:47
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:50
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:51
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the <filename>arjuna."
+"properties</filename> file and then also reads the property file "
+"<filename>RecoveryManager.properties</filename>, 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:52
+#, no-c-format
+msgid ""
+"A default version of <filename>RecoveryManager.properties</filename> 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)"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:54
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:55
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:58
+#, no-c-format
+msgid ""
+"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 &lt; INFO &lt; WARN &lt; ERROR &lt; "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:61
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:67
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:71
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:74
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, e.g., constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:77
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:80
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, e.g., the object store."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:83
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. JBoss Transactions uses the default Debugging level and the "
+"default Visibility level provided by CLF, but it defines its own Facility "
+"Code. JBoss Transactions 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 JBoss Transactions "
+"are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"Debugging level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:87
+#, no-c-format
+msgid ""
+"NO_DEBUGGING:  No diagnostics. A logger object assigned with this values "
+"discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:90
+#, no-c-format
+msgid ""
+"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
+"allows all debug requests if the facility code and the visibility level "
+"match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:93
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:96
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid "DESTRUCTORS:  Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:102
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid "FUNCTIONS:  Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:108
+#, no-c-format
+msgid "OPERATORS:  Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:114
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:117
+#, no-c-format
+msgid "TRIVIAL_FUNCS:  Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:120
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:123
+#, no-c-format
+msgid "ALL_TRIVIAL:  Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:126
+#, no-c-format
+msgid ""
+"Visibility level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:129
+#, no-c-format
+msgid "VIS_NONE:  No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:132
+#, no-c-format
+msgid "VIS_PRIVATE :  only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:135
+#, no-c-format
+msgid "VIS_PROTECTED  only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:138
+#, no-c-format
+msgid "VIS_PUBLIC   only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:141
+#, no-c-format
+msgid "VIS_PACKAGE   only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:144
+#, no-c-format
+msgid "VIS_ALL:  Full Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:147
+#, no-c-format
+msgid ""
+"Facility Code – JBoss Transactions uses the following values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:150
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:153
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:156
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:159
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:162
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:165
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:174
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:177
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:180
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"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 JBoss Transactions module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:184
+#, no-c-format
+msgid ""
+"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 CommonLogging.xml, enables all debug "
+"messages related to the Crash Recovery protocol and issued by the JBoss "
+"Transactions module."
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:186
+#, no-c-format
+msgid ""
+"&lt;!-- Common logging related properties. --&gt;\n"
+"&lt;property\n"
+"  name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+"  value=\"0x00000000\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:189
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:192
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:196
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:198
+#, no-c-format
+msgid ""
+"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
+"<literal>periodicWorkSecondPass</literal>. At an interval (defined by "
+"property <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
+"classname>), the RecoveryManager will call the first pass method on each "
+"property, then wait for a brief period (defined by property <classname>com."
+"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>), 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:199
+#, no-c-format
+msgid ""
+"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 "
+"<classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
+"classname> 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)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the <literal>periodicRecoveryPeriod</"
+"literal>, <literal>recoveryBackoffPeriod</literal> and the length of time it "
+"takes to scan the stores and to attempt recovery of any in-doubt "
+"transactions found, for all the recovery modules. The recovery attempt time "
+"may include connection timeouts while trying to communicate with processes "
+"or machines that have crashed or are inaccessible (which is why there are "
+"mechanisms in the recovery system to avoid trying to recover the same "
+"transaction for ever). The total iteration time will affect how long a "
+"resource will remain inaccessible after a failure – "
+"<literal>periodicRecoveryPeriod</literal> should be set accordingly (default "
+"is 120 seconds). The <literal>recoveryBackoffPeriod</literal> can be "
+"comparatively short (default is 10 seconds) – its purpose is mainly to "
+"reduce the number of transactions that are candidates for recovery and which "
+"thus require a “call to the original process to see if they are still in "
+"progress"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"In previous versions of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:206
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <classname>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</classname> interface) are supplied with "
+"JBoss Transactions, 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 properties "
+"that begin with “<classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryExtension</classname>”. These will be invoked on each pass of the "
+"periodic recovery in the sort-order of the property names – it is thus "
+"possible to predict the ordering (but note that a failure in an application "
+"process might occur while a periodic recovery pass is in progress). The "
+"default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+"\n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
+"  com.arjuna.ats.txoj.recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:211
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"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 <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> "
+"interface. Implementations of this interface are loaded by giving the class "
+"name as the value of a property whose name begins with <classname>com.arjuna."
+"ats.arjuna.recovery.expiryScanner</classname>. The RecoveryManager calls the "
+"<command>scan()</command> method on each loaded Expiry Scanner "
+"implementation at an interval determined by the property <classname>com."
+"arjuna.ats.arjuna.recovery.expiryScanInterval</classname>. This value is "
+"given in hours – default is 12. An <classname>expiryScanInterval</classname> "
+"value of zero will suppress any expiry scanning. If the value as supplied is "
+"positive, the first scan is performed when RecoveryManager starts; if the "
+"value is negative, the first scan is delayed until after the first interval "
+"(using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:213
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:214
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses JBoss Transactions – 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 <classname>com.arjuna."
+"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> (in hours "
+"– default is 12, zero means never expire). The expiry time should be greater "
+"than the lifetime of any single JBoss Transactions-using process."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:217
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery."
+"ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:220
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:221
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:224
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"<classname>OutOfMemoryError</classname>) and JBoss Transactions has "
+"attempted to do some cleanup (by running the garbage collector) before re-"
+"throwing the exception. This is probably a transient problem and retrying "
+"the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:227
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:230
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:233
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:236
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:241
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:242
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:245
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the JBoss Transactions "
+"product."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:248
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:252
+#, no-c-format
+msgid ""
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:255
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:258
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaTMImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:261
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaUTImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:265
+#, no-c-format
+msgid ""
+"these settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Feedback.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Feedback.pot	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Feedback.pot	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,35 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Feedback.xml:6
+#, no-c-format
+msgid "Feedback"
+msgstr ""
+
+#. Tag: para
+#: Feedback.xml:7
+#, no-c-format
+msgid ""
+"If you spot a typo in this guide, or if you have thought of a way to make "
+"this manual better, we would love to hear from you! Submit a report in "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> against "
+"the Product: JBoss Enterprise Application Platform, Version: "
+"<replaceable>&lt;version&gt;</replaceable>, Component: <emphasis>Doc</"
+"emphasis>. If you have a suggestion for improving the documentation, try to "
+"be as specific as possible. If you have found an error, include the section "
+"number and some of the surrounding text so we can find it easily."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/JBoss_Transactions_Administrators_Guide.pot
===================================================================

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Preface.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Preface.pot	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Preface.pot	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,124 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:14
+#, no-c-format
+msgid "What This Guide Contains"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:15
+#, no-c-format
+msgid ""
+"The Administration Guide contains information on how to administer JBoss "
+"Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:17
+#, no-c-format
+msgid "Audience"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:18
+#, no-c-format
+msgid ""
+"This guide is most relevant to engineers who are responsible for "
+"administration of JBoss Transactions API 4.2.3 installations."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:21
+#, no-c-format
+msgid "Prerequisites"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:22
+#, no-c-format
+msgid ""
+"In order to administer JBoss Transactions it is first necessary to "
+"understand that it relies on ArjunaCore for a lot of the transaction "
+"functionality. As such, it is important to read the ArjunaCore "
+"Administration Guide before attempting to administer JBoss Transactions."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:25
+#, no-c-format
+msgid "Organization"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:26
+#, no-c-format
+msgid "This guide contains the following chapters:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:29
+#, no-c-format
+msgid ""
+"Chapter 1, Administration of JBoss Transactions: describes how to administer "
+"JBoss Transactions, mainly by selecting the variant of JTA implementation: "
+"pure local or remote (allowing distributed transactions)."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:34
+#, no-c-format
+msgid "Additional Documentation"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:35
+#, no-c-format
+msgid ""
+"In addition to this guide, the following guides are available in the JBoss "
+"Transactions API 4.2.3 documentation set:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:38
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
+"information about JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:41
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
+"instructions for installing JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:44
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
+"writing applications."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Revision_History.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Revision_History.pot	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/Revision_History.pot	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,21 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: author
+#: Revision_History.xml:9
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/messages.mo
===================================================================
(Binary files differ)


Property changes on: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pot/messages.mo
___________________________________________________________________
Name: svn:mime-type
   + application/octet-stream

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Appendix.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Appendix.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Author_Group.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Author_Group.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,29 @@
+# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "FF0000 Headgear Documentation Group"
+msgstr ""
+
+#. Tag: author
+#: Author_Group.xml:7
+#, no-c-format
+msgid ""
+"<firstname>Dude</firstname> <surname>McDude</surname> <affiliation> "
+"<orgname>My Org</orgname> <orgdiv>Best Div in the place</orgdiv> </"
+"affiliation> <email>dude.mcdude at myorg.org</email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Book_Info.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Book_Info.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,40 @@
+# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions API 4.2.3 Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:10
+#, no-c-format
+msgid "JBoss Enterprise Application Platform"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid ""
+"This book is the JBoss Enterprise Application Platform edition of the JBoss "
+"Transactions Administrators Guide"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:22
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Chapter.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Chapter.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Chapter.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,932 @@
+# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Chapter.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:7
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBoss Transactions software. "
+"There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:10
+#, no-c-format
+msgid ""
+"The present implementation of the JBoss TA system provides no security or "
+"protection for data. The objects stored in the JBoss Transactions object "
+"store are (typically) owned by the user who ran the application that created "
+"them. The Object Store and Object Manager facilities make no attempt to "
+"enforce even the limited form of protection that Unix/Windows provides. "
+"There is no checking of user or group IDs on access to objects for either "
+"reading or writing."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:13
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"StateManager.destroy method is invoked on the object or some application "
+"program explicitly deletes them. This means that the Object Store gradually "
+"accumulates garbage (especially during application development and testing "
+"phases). At present we have no automated garbage collection facility. "
+"Further, we have not addressed the problem of dangling references. That is, "
+"a persistent object, A, may have stored a Uid for another persistent object, "
+"B, in its passive representation on disk. There is nothing to prevent an "
+"application from deleting B even though A still contains a reference to it. "
+"When A is next activated and attempts to access B, a run-time error will "
+"occur."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:16
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The JBoss Transactions software can "
+"neither detect nor correct references to old object state by new operation "
+"versions or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:19
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:24
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:28
+#, no-c-format
+msgid "JBoss Transactions runtime information"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:29
+#, no-c-format
+msgid ""
+"Each module that comprises JBoss Transactions 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:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"&lt;module-info name=\"arjuna\"&gt;\n"
+"        &lt;source-identifier&gt;unknown&lt;/source-identifier&gt;\n"
+"        &lt;build-information&gt;\n"
+"           Arjuna Technologies [mlittle] (Windows 2000 5.0)\n"
+"        &lt;/build-information&gt;\n"
+"        &lt;version&gt;unknown&lt;/version&gt;\n"
+"        &lt;date&gt;2002/06/15 04:06 PM&lt;/date&gt;\n"
+"        &lt;notes&gt;&lt;/notes&gt;\n"
+"        &lt;configuration&gt;\n"
+"                &lt;properties-file dir=\"null\"&gt;arjuna.properties&lt;/"
+"properties-file&gt;\n"
+"                &lt;object-store-root&gt;null&lt;/object-store-root&gt;\n"
+"        &lt;/configuration&gt;\n"
+"&lt;/module-info&gt;"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:34
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:38
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:41
+#, no-c-format
+msgid ""
+"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 “in-doubt transactions”. For TransactionalObjects for Java "
+"resources, an attempt to activate the Transactional Object (as when trying "
+"to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:43
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:44
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions requires that the stand-"
+"alone Recovery Manager process be running for each ObjectStore (typically "
+"one for each node on the network that is running JBoss Transactions "
+"applications). The RecoveryManager file is located in the arjunacore jar "
+"file within the package <classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryManager</classname>. To start the Recovery Manager issue the "
+"following command:"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:45
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:46
+#, no-c-format
+msgid ""
+"If the <literal>-test</literal> flag is used with the Recovery Manager then "
+"it will display a “Ready” message when initialised, i.e.,"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:47
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:50
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:51
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the <filename>arjuna."
+"properties</filename> file and then also reads the property file "
+"<filename>RecoveryManager.properties</filename>, 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:52
+#, no-c-format
+msgid ""
+"A default version of <filename>RecoveryManager.properties</filename> 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)"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:54
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:55
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:58
+#, no-c-format
+msgid ""
+"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 &lt; INFO &lt; WARN &lt; ERROR &lt; "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:61
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:67
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:71
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:74
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, e.g., constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:77
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:80
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, e.g., the object store."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:83
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. JBoss Transactions uses the default Debugging level and the "
+"default Visibility level provided by CLF, but it defines its own Facility "
+"Code. JBoss Transactions 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 JBoss Transactions "
+"are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"Debugging level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:87
+#, no-c-format
+msgid ""
+"NO_DEBUGGING:  No diagnostics. A logger object assigned with this values "
+"discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:90
+#, no-c-format
+msgid ""
+"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
+"allows all debug requests if the facility code and the visibility level "
+"match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:93
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:96
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid "DESTRUCTORS:  Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:102
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid "FUNCTIONS:  Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:108
+#, no-c-format
+msgid "OPERATORS:  Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:114
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:117
+#, no-c-format
+msgid "TRIVIAL_FUNCS:  Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:120
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:123
+#, no-c-format
+msgid "ALL_TRIVIAL:  Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:126
+#, no-c-format
+msgid ""
+"Visibility level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:129
+#, no-c-format
+msgid "VIS_NONE:  No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:132
+#, no-c-format
+msgid "VIS_PRIVATE :  only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:135
+#, no-c-format
+msgid "VIS_PROTECTED  only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:138
+#, no-c-format
+msgid "VIS_PUBLIC   only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:141
+#, no-c-format
+msgid "VIS_JBoss_Transactions_Administrators_Guide   only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:144
+#, no-c-format
+msgid "VIS_ALL:  Full Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:147
+#, no-c-format
+msgid ""
+"Facility Code – JBoss Transactions uses the following values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:150
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:153
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:156
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:159
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:162
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:165
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:174
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:177
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:180
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"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 JBoss Transactions module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:184
+#, no-c-format
+msgid ""
+"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 CommonLogging.xml, enables all debug "
+"messages related to the Crash Recovery protocol and issued by the JBoss "
+"Transactions module."
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:186
+#, no-c-format
+msgid ""
+"&lt;!-- Common logging related properties. --&gt;\n"
+"&lt;property\n"
+"  name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+"  value=\"0x00000000\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:189
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:192
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:196
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:198
+#, no-c-format
+msgid ""
+"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
+"<literal>periodicWorkSecondPass</literal>. At an interval (defined by "
+"property <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
+"classname>), the RecoveryManager will call the first pass method on each "
+"property, then wait for a brief period (defined by property <classname>com."
+"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>), 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:199
+#, no-c-format
+msgid ""
+"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 "
+"<classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
+"classname> 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)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the <literal>periodicRecoveryPeriod</"
+"literal>, <literal>recoveryBackoffPeriod</literal> and the length of time it "
+"takes to scan the stores and to attempt recovery of any in-doubt "
+"transactions found, for all the recovery modules. The recovery attempt time "
+"may include connection timeouts while trying to communicate with processes "
+"or machines that have crashed or are inaccessible (which is why there are "
+"mechanisms in the recovery system to avoid trying to recover the same "
+"transaction for ever). The total iteration time will affect how long a "
+"resource will remain inaccessible after a failure – "
+"<literal>periodicRecoveryPeriod</literal> should be set accordingly (default "
+"is 120 seconds). The <literal>recoveryBackoffPeriod</literal> can be "
+"comparatively short (default is 10 seconds) – its purpose is mainly to "
+"reduce the number of transactions that are candidates for recovery and which "
+"thus require a “call to the original process to see if they are still in "
+"progress"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"In previous versions of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:206
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <classname>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</classname> interface) are supplied with "
+"JBoss Transactions, 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 properties "
+"that begin with “<classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryExtension</classname>”. These will be invoked on each pass of the "
+"periodic recovery in the sort-order of the property names – it is thus "
+"possible to predict the ordering (but note that a failure in an application "
+"process might occur while a periodic recovery pass is in progress). The "
+"default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+"\n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
+"  com.arjuna.ats.txoj.recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:211
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"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 <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> "
+"interface. Implementations of this interface are loaded by giving the class "
+"name as the value of a property whose name begins with <classname>com.arjuna."
+"ats.arjuna.recovery.expiryScanner</classname>. The RecoveryManager calls the "
+"<command>scan()</command> method on each loaded Expiry Scanner "
+"implementation at an interval determined by the property <classname>com."
+"arjuna.ats.arjuna.recovery.expiryScanInterval</classname>. This value is "
+"given in hours – default is 12. An <classname>expiryScanInterval</classname> "
+"value of zero will suppress any expiry scanning. If the value as supplied is "
+"positive, the first scan is performed when RecoveryManager starts; if the "
+"value is negative, the first scan is delayed until after the first interval "
+"(using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:213
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:214
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses JBoss Transactions – 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 <classname>com.arjuna."
+"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> (in hours "
+"– default is 12, zero means never expire). The expiry time should be greater "
+"than the lifetime of any single JBoss Transactions-using process."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:217
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery."
+"ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:220
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:221
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:224
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"<classname>OutOfMemoryError</classname>) and JBoss Transactions has "
+"attempted to do some cleanup (by running the garbage collector) before re-"
+"throwing the exception. This is probably a transient problem and retrying "
+"the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:227
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:230
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:233
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:236
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:241
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:242
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:245
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the JBoss Transactions "
+"product."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:248
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:252
+#, no-c-format
+msgid ""
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:255
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:258
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaTMImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:261
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaUTImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:265
+#, no-c-format
+msgid ""
+"these settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Feedback.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Feedback.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Feedback.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,34 @@
+# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Feedback.xml:6
+#, no-c-format
+msgid "Feedback"
+msgstr ""
+
+#. Tag: para
+#: Feedback.xml:7
+#, no-c-format
+msgid ""
+"If you spot a typo in this guide, or if you have thought of a way to make "
+"this manual better, we would love to hear from you! Submit a report in "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> against "
+"the Product: JBoss Enterprise Application Platform, Version: "
+"<replaceable>&lt;version&gt;</replaceable>, Component: <emphasis>Doc</"
+"emphasis>. If you have a suggestion for improving the documentation, try to "
+"be as specific as possible. If you have found an error, include the section "
+"number and some of the surrounding text so we can find it easily."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/JBoss_Transactions_Administrators_Guide.po
===================================================================

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Preface.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Preface.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,123 @@
+# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:14
+#, no-c-format
+msgid "What This Guide Contains"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:15
+#, no-c-format
+msgid ""
+"The Administration Guide contains information on how to administer JBoss "
+"Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:17
+#, no-c-format
+msgid "Audience"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:18
+#, no-c-format
+msgid ""
+"This guide is most relevant to engineers who are responsible for "
+"administration of JBoss Transactions API 4.2.3 installations."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:21
+#, no-c-format
+msgid "Prerequisites"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:22
+#, no-c-format
+msgid ""
+"In order to administer JBoss Transactions it is first necessary to "
+"understand that it relies on ArjunaCore for a lot of the transaction "
+"functionality. As such, it is important to read the ArjunaCore "
+"Administration Guide before attempting to administer JBoss Transactions."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:25
+#, no-c-format
+msgid "Organization"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:26
+#, no-c-format
+msgid "This guide contains the following chapters:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:29
+#, no-c-format
+msgid ""
+"Chapter 1, Administration of JBoss Transactions: describes how to administer "
+"JBoss Transactions, mainly by selecting the variant of JTA implementation: "
+"pure local or remote (allowing distributed transactions)."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:34
+#, no-c-format
+msgid "Additional Documentation"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:35
+#, no-c-format
+msgid ""
+"In addition to this guide, the following guides are available in the JBoss "
+"Transactions API 4.2.3 documentation set:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:38
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
+"information about JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:41
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
+"instructions for installing JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:44
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
+"writing applications."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/pt-BR/Revision_History.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: author
+#: Revision_History.xml:9
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Appendix.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Appendix.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Author_Group.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Author_Group.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,29 @@
+# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "FF0000 Headgear Documentation Group"
+msgstr ""
+
+#. Tag: author
+#: Author_Group.xml:7
+#, no-c-format
+msgid ""
+"<firstname>Dude</firstname> <surname>McDude</surname> <affiliation> "
+"<orgname>My Org</orgname> <orgdiv>Best Div in the place</orgdiv> </"
+"affiliation> <email>dude.mcdude at myorg.org</email>"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Book_Info.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Book_Info.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,40 @@
+# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions API 4.2.3 Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:10
+#, no-c-format
+msgid "JBoss Enterprise Application Platform"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid ""
+"This book is the JBoss Enterprise Application Platform edition of the JBoss "
+"Transactions Administrators Guide"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:22
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,932 @@
+# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Chapter.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:7
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBoss Transactions software. "
+"There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:10
+#, no-c-format
+msgid ""
+"The present implementation of the JBoss TA system provides no security or "
+"protection for data. The objects stored in the JBoss Transactions object "
+"store are (typically) owned by the user who ran the application that created "
+"them. The Object Store and Object Manager facilities make no attempt to "
+"enforce even the limited form of protection that Unix/Windows provides. "
+"There is no checking of user or group IDs on access to objects for either "
+"reading or writing."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:13
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"StateManager.destroy method is invoked on the object or some application "
+"program explicitly deletes them. This means that the Object Store gradually "
+"accumulates garbage (especially during application development and testing "
+"phases). At present we have no automated garbage collection facility. "
+"Further, we have not addressed the problem of dangling references. That is, "
+"a persistent object, A, may have stored a Uid for another persistent object, "
+"B, in its passive representation on disk. There is nothing to prevent an "
+"application from deleting B even though A still contains a reference to it. "
+"When A is next activated and attempts to access B, a run-time error will "
+"occur."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:16
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The JBoss Transactions software can "
+"neither detect nor correct references to old object state by new operation "
+"versions or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:19
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:24
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:28
+#, no-c-format
+msgid "JBoss Transactions runtime information"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:29
+#, no-c-format
+msgid ""
+"Each module that comprises JBoss Transactions 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:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"&lt;module-info name=\"arjuna\"&gt;\n"
+"        &lt;source-identifier&gt;unknown&lt;/source-identifier&gt;\n"
+"        &lt;build-information&gt;\n"
+"           Arjuna Technologies [mlittle] (Windows 2000 5.0)\n"
+"        &lt;/build-information&gt;\n"
+"        &lt;version&gt;unknown&lt;/version&gt;\n"
+"        &lt;date&gt;2002/06/15 04:06 PM&lt;/date&gt;\n"
+"        &lt;notes&gt;&lt;/notes&gt;\n"
+"        &lt;configuration&gt;\n"
+"                &lt;properties-file dir=\"null\"&gt;arjuna.properties&lt;/"
+"properties-file&gt;\n"
+"                &lt;object-store-root&gt;null&lt;/object-store-root&gt;\n"
+"        &lt;/configuration&gt;\n"
+"&lt;/module-info&gt;"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:34
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:38
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:41
+#, no-c-format
+msgid ""
+"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 “in-doubt transactions”. For TransactionalObjects for Java "
+"resources, an attempt to activate the Transactional Object (as when trying "
+"to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:43
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:44
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of JBoss Transactions requires that the stand-"
+"alone Recovery Manager process be running for each ObjectStore (typically "
+"one for each node on the network that is running JBoss Transactions "
+"applications). The RecoveryManager file is located in the arjunacore jar "
+"file within the package <classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryManager</classname>. To start the Recovery Manager issue the "
+"following command:"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:45
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:46
+#, no-c-format
+msgid ""
+"If the <literal>-test</literal> flag is used with the Recovery Manager then "
+"it will display a “Ready” message when initialised, i.e.,"
+msgstr ""
+
+#. Tag: command
+#: Chapter.xml:47
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:50
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:51
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the <filename>arjuna."
+"properties</filename> file and then also reads the property file "
+"<filename>RecoveryManager.properties</filename>, 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:52
+#, no-c-format
+msgid ""
+"A default version of <filename>RecoveryManager.properties</filename> 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)"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:54
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:55
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:58
+#, no-c-format
+msgid ""
+"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 &lt; INFO &lt; WARN &lt; ERROR &lt; "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:61
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:67
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:71
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:74
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, e.g., constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:77
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:80
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, e.g., the object store."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:83
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. JBoss Transactions uses the default Debugging level and the "
+"default Visibility level provided by CLF, but it defines its own Facility "
+"Code. JBoss Transactions 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 JBoss Transactions "
+"are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"Debugging level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:87
+#, no-c-format
+msgid ""
+"NO_DEBUGGING:  No diagnostics. A logger object assigned with this values "
+"discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:90
+#, no-c-format
+msgid ""
+"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
+"allows all debug requests if the facility code and the visibility level "
+"match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:93
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:96
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid "DESTRUCTORS:  Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:102
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid "FUNCTIONS:  Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:108
+#, no-c-format
+msgid "OPERATORS:  Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:114
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:117
+#, no-c-format
+msgid "TRIVIAL_FUNCS:  Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:120
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:123
+#, no-c-format
+msgid "ALL_TRIVIAL:  Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:126
+#, no-c-format
+msgid ""
+"Visibility level – JBoss Transactions uses the default values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:129
+#, no-c-format
+msgid "VIS_NONE:  No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:132
+#, no-c-format
+msgid "VIS_PRIVATE :  only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:135
+#, no-c-format
+msgid "VIS_PROTECTED  only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:138
+#, no-c-format
+msgid "VIS_PUBLIC   only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:141
+#, no-c-format
+msgid "VIS_JBoss_Transactions_Administrators_Guide   only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:144
+#, no-c-format
+msgid "VIS_ALL:  Full Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:147
+#, no-c-format
+msgid ""
+"Facility Code – JBoss Transactions uses the following values defined in the "
+"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:150
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:153
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:156
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:159
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:162
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:165
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:174
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:177
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:180
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"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 JBoss Transactions module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:184
+#, no-c-format
+msgid ""
+"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 CommonLogging.xml, enables all debug "
+"messages related to the Crash Recovery protocol and issued by the JBoss "
+"Transactions module."
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:186
+#, no-c-format
+msgid ""
+"&lt;!-- Common logging related properties. --&gt;\n"
+"&lt;property\n"
+"  name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+"  value=\"0x00000000\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;\n"
+"&lt;propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+"  value=\"0xffffffff\"/&gt;"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:189
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:192
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:196
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:198
+#, no-c-format
+msgid ""
+"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
+"<literal>periodicWorkSecondPass</literal>. At an interval (defined by "
+"property <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
+"classname>), the RecoveryManager will call the first pass method on each "
+"property, then wait for a brief period (defined by property <classname>com."
+"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>), 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:199
+#, no-c-format
+msgid ""
+"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 "
+"<classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
+"classname> 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)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the <literal>periodicRecoveryPeriod</"
+"literal>, <literal>recoveryBackoffPeriod</literal> and the length of time it "
+"takes to scan the stores and to attempt recovery of any in-doubt "
+"transactions found, for all the recovery modules. The recovery attempt time "
+"may include connection timeouts while trying to communicate with processes "
+"or machines that have crashed or are inaccessible (which is why there are "
+"mechanisms in the recovery system to avoid trying to recover the same "
+"transaction for ever). The total iteration time will affect how long a "
+"resource will remain inaccessible after a failure – "
+"<literal>periodicRecoveryPeriod</literal> should be set accordingly (default "
+"is 120 seconds). The <literal>recoveryBackoffPeriod</literal> can be "
+"comparatively short (default is 10 seconds) – its purpose is mainly to "
+"reduce the number of transactions that are candidates for recovery and which "
+"thus require a “call to the original process to see if they are still in "
+"progress"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"In previous versions of JBoss Transactions 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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:206
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <classname>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</classname> interface) are supplied with "
+"JBoss Transactions, 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 properties "
+"that begin with “<classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryExtension</classname>”. These will be invoked on each pass of the "
+"periodic recovery in the sort-order of the property names – it is thus "
+"possible to predict the ordering (but note that a failure in an application "
+"process might occur while a periodic recovery pass is in progress). The "
+"default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+"\n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
+"  com.arjuna.ats.txoj.recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:211
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"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 <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> "
+"interface. Implementations of this interface are loaded by giving the class "
+"name as the value of a property whose name begins with <classname>com.arjuna."
+"ats.arjuna.recovery.expiryScanner</classname>. The RecoveryManager calls the "
+"<command>scan()</command> method on each loaded Expiry Scanner "
+"implementation at an interval determined by the property <classname>com."
+"arjuna.ats.arjuna.recovery.expiryScanInterval</classname>. This value is "
+"given in hours – default is 12. An <classname>expiryScanInterval</classname> "
+"value of zero will suppress any expiry scanning. If the value as supplied is "
+"positive, the first scan is performed when RecoveryManager starts; if the "
+"value is negative, the first scan is delayed until after the first interval "
+"(using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:213
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:214
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses JBoss Transactions – 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 <classname>com.arjuna."
+"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> (in hours "
+"– default is 12, zero means never expire). The expiry time should be greater "
+"than the lifetime of any single JBoss Transactions-using process."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: programlisting
+#: Chapter.xml:217
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
+"  com.arjuna.ats.internal.ts.arjuna.recovery."
+"ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:220
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:221
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:224
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"<classname>OutOfMemoryError</classname>) and JBoss Transactions has "
+"attempted to do some cleanup (by running the garbage collector) before re-"
+"throwing the exception. This is probably a transient problem and retrying "
+"the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:227
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:230
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:233
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:236
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:241
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:242
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:245
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the JBoss Transactions "
+"product."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:248
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:252
+#, no-c-format
+msgid ""
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:255
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:258
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaTMImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:261
+#, no-c-format
+msgid ""
+"make sure the property <literal>com.arjuna.ats.jta.jtaUTImplementation</"
+"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:265
+#, no-c-format
+msgid ""
+"these settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Feedback.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Feedback.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Feedback.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,34 @@
+# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Feedback.xml:6
+#, no-c-format
+msgid "Feedback"
+msgstr ""
+
+#. Tag: para
+#: Feedback.xml:7
+#, no-c-format
+msgid ""
+"If you spot a typo in this guide, or if you have thought of a way to make "
+"this manual better, we would love to hear from you! Submit a report in "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> against "
+"the Product: JBoss Enterprise Application Platform, Version: "
+"<replaceable>&lt;version&gt;</replaceable>, Component: <emphasis>Doc</"
+"emphasis>. If you have a suggestion for improving the documentation, try to "
+"be as specific as possible. If you have found an error, include the section "
+"number and some of the surrounding text so we can find it easily."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/JBoss_Transactions_Administrators_Guide.po
===================================================================

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Preface.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Preface.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,123 @@
+# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:14
+#, no-c-format
+msgid "What This Guide Contains"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:15
+#, no-c-format
+msgid ""
+"The Administration Guide contains information on how to administer JBoss "
+"Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:17
+#, no-c-format
+msgid "Audience"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:18
+#, no-c-format
+msgid ""
+"This guide is most relevant to engineers who are responsible for "
+"administration of JBoss Transactions API 4.2.3 installations."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:21
+#, no-c-format
+msgid "Prerequisites"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:22
+#, no-c-format
+msgid ""
+"In order to administer JBoss Transactions it is first necessary to "
+"understand that it relies on ArjunaCore for a lot of the transaction "
+"functionality. As such, it is important to read the ArjunaCore "
+"Administration Guide before attempting to administer JBoss Transactions."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:25
+#, no-c-format
+msgid "Organization"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:26
+#, no-c-format
+msgid "This guide contains the following chapters:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:29
+#, no-c-format
+msgid ""
+"Chapter 1, Administration of JBoss Transactions: describes how to administer "
+"JBoss Transactions, mainly by selecting the variant of JTA implementation: "
+"pure local or remote (allowing distributed transactions)."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:34
+#, no-c-format
+msgid "Additional Documentation"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:35
+#, no-c-format
+msgid ""
+"In addition to this guide, the following guides are available in the JBoss "
+"Transactions API 4.2.3 documentation set:"
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:38
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
+"information about JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:41
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
+"instructions for installing JBoss Transactions API 4.2.3."
+msgstr ""
+
+#. Tag: para
+#: Preface.xml:44
+#, no-c-format
+msgid ""
+"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
+"writing applications."
+msgstr ""

Added: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Revision_History.po	2008-06-05 22:50:43 UTC (rev 74212)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"PO-Revision-Date: 2008-06-05 22:49+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: author
+#: Revision_History.xml:9
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""




More information about the jboss-cvs-commits mailing list