[jboss-svn-commits] JBL Code SVN: r29385 - in labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide: de-DE and 6 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Sep 16 22:36:57 EDT 2009
Author: xhuang at jboss.com
Date: 2009-09-16 22:36:56 -0400 (Wed, 16 Sep 2009)
New Revision: 29385
Modified:
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/Makefile
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Chapter.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Feedback.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Preface.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Chapter.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Feedback.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Preface.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Chapter.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Feedback.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Preface.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Chapter.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Feedback.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Preface.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Author_Group.pot
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Book_Info.pot
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Chapter.pot
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Feedback.pot
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Preface.pot
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Revision_History.pot
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Chapter.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Feedback.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Preface.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Chapter.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Feedback.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Preface.po
labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Revision_History.po
Log:
Generate PO based on v4.3
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/Makefile
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/Makefile 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/Makefile 2009-09-17 02:36:56 UTC (rev 29385)
@@ -5,7 +5,7 @@
BRAND = JBoss
-#OTHER_LANGS = de-DE es-ES fr-FR ja-JP pt-BR zh-CN
+OTHER_LANGS = de-DE es-ES fr-FR ja-JP pt-BR zh-CN
CHUNK_FIRST = 0
CHUNK_SECTION_DEPTH = 1
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Author_Group.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Author_Group.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,3 +1,4 @@
+# translation of Preface.po to
# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
@@ -3,26 +4,18 @@
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Project-Id-Version: Preface\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"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-09-20 15:28+1000\n"
+"Last-Translator: \n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\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 ""
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Book_Info.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Book_Info.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,3 +1,4 @@
+# translation of Preface.po to
# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
@@ -3,37 +4,40 @@
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Project-Id-Version: Preface\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"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-09-20 15:28+1000\n"
+"Last-Translator: \n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Book_Info.xml:6
-#, no-c-format
-msgid "JBoss Transactions API 4.2.3 Administration Guide"
-msgstr ""
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Administrators Guide"
+msgstr "JBoss Transaktions-API 4.2.3 Administrationshandbuch"
#. Tag: subtitle
#: Book_Info.xml:10
-#, no-c-format
-msgid "JBoss Enterprise Application Platform"
-msgstr ""
+#, fuzzy, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 5.0"
+msgstr "JBoss Enterprise Application Platform"
#. Tag: para
-#: Book_Info.xml:13
+#: Book_Info.xml:15
#, no-c-format
msgid ""
"This book is the JBoss Enterprise Application Platform edition of the JBoss "
"Transactions Administrators Guide"
msgstr ""
+"Bei diesem Buch handelt es sich um die JBoss Enterprise Application Platform "
+"Ausgabe des JBoss Transaktions Administrator-Handbuchs"
#. Tag: holder
-#: Book_Info.xml:22
+#: Book_Info.xml:24
#, no-c-format
msgid "&HOLDER;"
-msgstr ""
+msgstr "&HOLDER;"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Chapter.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Chapter.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Chapter.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,3 +1,4 @@
+# translation of Preface.po to
# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
@@ -3,19 +4,20 @@
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Project-Id-Version: Preface\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"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-09-20 15:28+1000\n"
+"Last-Translator: \n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Chapter.xml:6
#, no-c-format
msgid "Introduction"
-msgstr ""
+msgstr "Einführung"
#. Tag: para
@@ -27,6 +29,9 @@
"little continuous administration needed for the JBoss Transactions software. "
"There are a few points however, that should be made:"
msgstr ""
+"Abgesehen davon, dass sichergestellt werden sollte, dass das Runtime-System "
+"normal ausgeführt wird, wird wenig durchgängige Aufsicht für die JBoss "
+"Transaktions-Software benötigt. Ein paar Punkte jedoch sind erforderlich:"
#. Tag: para
#: Chapter.xml:10
@@ -40,6 +45,14 @@
"There is no checking of user or group IDs on access to objects for either "
"reading or writing."
msgstr ""
+"Die aktuelle Implementierung des JBoss TA Systems bietet weder Sicherheit "
+"noch Schutz für Daten. Die im JBoss Transaktions-Objectspeicher "
+"gespeicherten Objekte gehören (in der Regel) demjenigen Benutzer, der die "
+"Anwendung ausgeführt hat bei der diese erzeugt wurden. Die \"Object Store\" "
+"und \"Object Manager\" Facilities unternehmen keinen Versuch auch nur die "
+"recht eingeschränkte Art von Schutz zu bieten, die Unix/Windows bietet. Es "
+"findet keine Prüfung der Benutzer- oder Gruppen-IDs beim Zugriff auf Objekte "
+"zum Lesen oder Schreiben statt."
#. Tag: para
#: Chapter.xml:13
@@ -57,6 +70,18 @@
"When A is next activated and attempts to access B, a run-time error will "
"occur."
msgstr ""
+"Persistente Objekte, die im \"Object Store\" erstellt wurde, bleiben "
+"bestehen, außer die StateManager.destroy Methode wird am Objekt aufgerufen "
+"oder ein Anwendungsprogramm löscht diese explizit. Das bedeutet, dass der "
+"\"Object Store\" nach und nach Müll ansammelt (insbesondere während der "
+"Applikationsentwicklung und Testphasen). Derzeit existiert noch kein "
+"automatisierter Müllbereinigungsmechanismus. Desweiteren wurde das Problem "
+"der Referenzen in Schwebe noch nicht angegangen. Dies bedeutet, ein "
+"persistentes Objekt A, kann die Uid für ein anderes persistentes Objekt B in "
+"seiner passiven Repräsentation auf Disk gespeichert haben. Nichts hindert "
+"eine Anwendung daran B zu löschen, selbst wenn A nach wie vor eine Referenz "
+"darauf enthält. Wird A anschließend aktiviert und versucht auf B "
+"zuzugreifen, so wird ein Runtime-Error gemeldet."
#. Tag: para
#: Chapter.xml:16
@@ -71,24 +96,96 @@
"neither detect nor correct references to old object state by new operation "
"versions or vice versa."
msgstr ""
+"Derzeit existiert kein Support für Versionskontrolle von Objekten oder "
+"Datenban-Rekonfiguration im Falle von Veränderungen von Klassenstrukturen. "
+"Dies ist ein komplexes Forschungsgebiet, auf das wir nicht eingegangen sind. "
+"Momentan ist es so, dass Sie - wenn Sie die Definition einer Klasse "
+"persistenter Objekte ändern - vollständig verantwortlich dafür sind "
+"sicherzustellen, dass bestehend Instanzen des Objekts im Object Store in "
+"eine neue Repräsentation konvertiert werden. Die JBoss Transactions Software "
+"kann Verweise auf alte Objekt-Stati durch neue Operationsversionen und "
+"umgekehrt weder aufspüren noch korrigieren."
#. Tag: para
-#: Chapter.xml:19
+#: Chapter.xml:19 Chapter.xml:62
#, no-c-format
msgid ""
"Object store management is critically important to the transaction service."
msgstr ""
+"\"Object Store\"-Management ist von kritischer Bedeutung für den "
+"Transkations-Service."
#. Tag: title
#: Chapter.xml:24
#, no-c-format
-msgid "ObjectStore management"
+msgid "Starting and Stopping the transaction manager"
msgstr ""
#. Tag: para
#: Chapter.xml:25
#, no-c-format
msgid ""
+"By default the transaction manager starts up in an active state such that "
+"new transactions can be created immediately. If you wish to have more "
+"control over this it is possible to set the <property>com.arjuna.ats.arjuna."
+"coordinator.startDisabled</property> configuration option to <literal>YES</"
+"literal>, in which case no transactions can be created until the transaction "
+"manager is enabled (via a call to <methodname>TxControl.enable</methodname>)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:28
+#, no-c-format
+msgid ""
+"It is possible to stop the creation of new transactions at any time by "
+"calling <methodname>TxControl.disable</methodname>. Transactions that are "
+"currently executing will not be affected. By default recovery will be "
+"allowed to continue and the transaction system will still be available to "
+"manage recovery requests from other instances in a distributed environment. "
+"(See the Failure Recovery Guide for further details). However, if you wish "
+"to disable recovery as well as remove any resources it maintains, then you "
+"can pass true to <methodname>TxControl.disable</methodname>; the default is "
+"to use <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"If you wish to shut the system down completely then it may also be necessary "
+"to terminate the background transaction reaper (see the Programmers Guide "
+"for information about what the reaper does.) In order to do this you may "
+"want to first prevent the creation of new transactions (if you are not "
+"creating transactions with timeouts then this step is not necessary) using "
+"<methodname>TxControl.disable</methodname>. Then you should call "
+"<methodname>TransactionReaper.terminate</methodname>. This method takes a "
+"boolean parameter: if true then the method will wait for the normal timeout "
+"periods associated with any transactions to expire before terminating the "
+"transactions; if false then transactions will be forced to terminate "
+"(rollback or have their outcome set such that they can only ever rollback) "
+"immediately."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"If you intent to restart the recovery manager later after having terminated "
+"it then you <emphasis>must</emphasis> use the <methodname>terminate</"
+"methodname> method with <property>asynchronous behavior</property> set to "
+"<literal>false</literal> when shutting down the recovery manager."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:40
+#, no-c-format
+msgid "ObjectStore management"
+msgstr "ObjectStore-Management"
+
+#. Tag: para
+#: Chapter.xml:41
+#, 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 "
@@ -102,25 +199,787 @@
"is important that they realise this and do not simply delete the contents of "
"the object store assuming it is an exclusive resource."
msgstr ""
+"Innerhalb der Transaktions-Service-Installation wird der \"Object Store\" "
+"regelmäßig aktualisiert wenn Transaktionen erstellt werden oder wenn "
+"transaktionale Objekte für Java verwendet werden. In einer von Fehlern "
+"freien Umgebung sollten die einzigen, innerhalb des \"Object Store\" "
+"befindlichen Objekt-Stati diejenigen sein, die Objekte repräsentieren, die "
+"mit der \"Transactional Objects for Java\"-API erstellt wurden. Falls es "
+"jedoch zu Fehlern kommt, so können Transkationsprotokolle im \"Object Store"
+"\" erhalten bleiben, bis Crash Recovery Facilities die Transaktionen "
+"aufgelöst haben, die sie repräsentieren. Als solches ist es sehr wichtig, "
+"dass die Inhalte des \"Object Store\" nicht ohne die nötige Sorgfalt "
+"gelöscht werden, da es sonst unmöglich wird zweifelhafte Transkationen "
+"aufzulösen. Wenn mehrere Nutzer sich denselben \"Object Store\" teilen ist "
+"es wichtig, dass sie sich dessen bewusst sind und die Inhalte des \"Object "
+"Store\" nicht einfach löschen in der Annahme, dass es sich dabei um eine "
+"exklusive Ressource handelt."
+#. Tag: para
+#: Chapter.xml:42
+#, fuzzy, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBossTS software. There are "
+"a few points however, that should be made:"
+msgstr ""
+"Abgesehen davon, dass sichergestellt werden sollte, dass das Runtime-System "
+"normal ausgeführt wird, wird wenig durchgängige Aufsicht für die JBoss "
+"Transaktions-Software benötigt. Ein paar Punkte jedoch sind erforderlich:"
+
+#. Tag: para
+#: Chapter.xml:47
+#, fuzzy, no-c-format
+msgid ""
+"The present implementation of the JBossTS system provides no security or "
+"protection for data. It is recommended that the objects stored in the "
+"JBossTS are owned by user arjuna. The Object Store and Object Manager "
+"facilities make no attempt to enforce even the limited form of protection "
+"that Unix and Windows provides. There is no checking of user or group IDs on "
+"access to objects for either reading or writing."
+msgstr ""
+"Die aktuelle Implementierung des JBoss TA Systems bietet weder Sicherheit "
+"noch Schutz für Daten. Die im JBoss Transaktions-Objectspeicher "
+"gespeicherten Objekte gehören (in der Regel) demjenigen Benutzer, der die "
+"Anwendung ausgeführt hat bei der diese erzeugt wurden. Die \"Object Store\" "
+"und \"Object Manager\" Facilities unternehmen keinen Versuch auch nur die "
+"recht eingeschränkte Art von Schutz zu bieten, die Unix/Windows bietet. Es "
+"findet keine Prüfung der Benutzer- oder Gruppen-IDs beim Zugriff auf Objekte "
+"zum Lesen oder Schreiben statt."
+
+#. Tag: para
+#: Chapter.xml:52
+#, fuzzy, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> 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 ""
+"Persistente Objekte, die im \"Object Store\" erstellt wurde, bleiben "
+"bestehen, außer die StateManager.destroy Methode wird am Objekt aufgerufen "
+"oder ein Anwendungsprogramm löscht diese explizit. Das bedeutet, dass der "
+"\"Object Store\" nach und nach Müll ansammelt (insbesondere während der "
+"Applikationsentwicklung und Testphasen). Derzeit existiert noch kein "
+"automatisierter Müllbereinigungsmechanismus. Desweiteren wurde das Problem "
+"der Referenzen in Schwebe noch nicht angegangen. Dies bedeutet, ein "
+"persistentes Objekt A, kann die Uid für ein anderes persistentes Objekt B in "
+"seiner passiven Repräsentation auf Disk gespeichert haben. Nichts hindert "
+"eine Anwendung daran B zu löschen, selbst wenn A nach wie vor eine Referenz "
+"darauf enthält. Wird A anschließend aktiviert und versucht auf B "
+"zuzugreifen, so wird ein Runtime-Error gemeldet."
+
+#. Tag: para
+#: Chapter.xml:57
+#, fuzzy, 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 JBossTS software can neither detect "
+"nor correct references to old object state by new operation versions or vice "
+"versa."
+msgstr ""
+"Derzeit existiert kein Support für Versionskontrolle von Objekten oder "
+"Datenban-Rekonfiguration im Falle von Veränderungen von Klassenstrukturen. "
+"Dies ist ein komplexes Forschungsgebiet, auf das wir nicht eingegangen sind. "
+"Momentan ist es so, dass Sie - wenn Sie die Definition einer Klasse "
+"persistenter Objekte ändern - vollständig verantwortlich dafür sind "
+"sicherzustellen, dass bestehend Instanzen des Objekts im Object Store in "
+"eine neue Repräsentation konvertiert werden. Die JBoss Transactions Software "
+"kann Verweise auf alte Objekt-Stati durch neue Operationsversionen und "
+"umgekehrt weder aufspüren noch korrigieren."
+
#. Tag: title
-#: Chapter.xml:28
+#: Chapter.xml:70
#, no-c-format
-msgid "JBoss Transactions runtime information"
+msgid "OTS and J2EE Transaction service management"
msgstr ""
+#. Tag: title
+#: Chapter.xml:72
+#, no-c-format
+msgid "Starting the run-time system"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:29
+#: Chapter.xml:73
#, no-c-format
msgid ""
+"The JBossTS run-time support consists of run-time packages and the OTS "
+"transaction manager server. By default JBossTS does not use a separate "
+"transaction manager server: transaction managers are co-located with each "
+"application process to improve performance and improve application fault-"
+"tolerance (the application is no longer dependant upon another service in "
+"order to function correctly)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:76
+#, no-c-format
+msgid ""
+"When running applications which require a separate transaction manager, you "
+"must set the <varname>com.arjuna.ats.jts.transactionManager</varname> "
+"environment variable to have the value <literal>yes</literal>. The system "
+"will then locate the transaction manager server in a manner specific to the "
+"ORB being used. The server can be located in a number of ways: by being "
+"registered with a name server, added to the ORB’s initial references, via a "
+"JBossTS specific references file, or by the ORB’s specific location "
+"mechanism (if applicable)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:79
+#, no-c-format
+msgid ""
+"It is possible to override the default registration mechanism by using the "
+"<varname>com.arjuna.orbportability.resolveService</varname> environment "
+"variable. This can have one of the following values:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"<literal>CONFIGURATION_FILE</literal>: the default, this causes the system "
+"to use the <filename>CosServices.cfg</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:89
+#, no-c-format
+msgid ""
+"<literal>NAME_SERVICE</literal>: JBossTS will attempt to use a name service "
+"to register the transaction factory. If this is not supported, an exception "
+"will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:94
+#, no-c-format
+msgid ""
+"<literal>BIND_CONNECT</literal>: JBossTS will use the ORB-specific bind "
+"mechanism. If this is not supported, an exception will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid ""
+"<literal>RESOLVE_INITIAL_REFERENCES</literal>: JBossTS will attempt to "
+"register the transaction service with the ORBs initial service references."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid ""
+"This may not be supported on all ORBs. An exception will be thrown in that "
+"case and another option will have to be used."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:110
+#, no-c-format
+msgid "<title>OTS configuration file</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid ""
+"Similar to the resolve_initial_references, JBossTS supports an initial "
+"reference file where references for specific services can be stored and used "
+"at runtime. The file, CosServices.cfg, consists of two columns: the service "
+"name (in the case of the OTS server TransactionService) and the IOR, "
+"separated by a single space. CosServices.cfg normally resides in the etc "
+"directory of the JBossTS installation; the actual location is determined at "
+"runtime by searching the CLASSPATH for an old copy of the file resident "
+"within an etc directory, or, if one is not found, the location of the "
+"TransactionService properties file directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:115
+#, no-c-format
+msgid ""
+"The OTS server will automatically register itself in this file (creating it "
+"if necessary) if this option is being used. Stale information is also "
+"automatically removed. Machines which wish to share the same transaction "
+"server should have access to (or a copy of) this file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:118
+#, no-c-format
+msgid ""
+"The name and location of the file can be overridden using the <property>com."
+"arjuna.orbportability.initialReferencesFile</property> and <property>com."
+"arjuna.orbportability.initialReferencesRoot</property> property variables, "
+"respectively. It is recommended that the <property>com.arjuna.orbportability."
+"initialReferencesRoot</property> variable is set. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Chapter.xml:121
+#, no-c-format
+msgid ""
+"com.arjuna.orbportability.initialReferencesFile=myFile\n"
+"com.arjuna.orbportability.initialReferencesRoot=c:\\\\temp"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:123
+#, no-c-format
+msgid "<title>Name Service</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:124
+#, no-c-format
+msgid ""
+"If the ORB you are using supports a name service, and JBossTS has been "
+"configured to use it, then the transaction manager will automatically be "
+"registered with it. There is no further work required. This option is not "
+"used for JacORB"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:129
+#, no-c-format
+msgid "<title>resolve_initial_references</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:130
+#, no-c-format
+msgid "Currently this option is only supported for JacORB."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:135
+#, no-c-format
+msgid "Resolution service table"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:136
+#, no-c-format
+msgid ""
+"The following table summarizes the different ways in which the OTS "
+"transaction manager may be located on specific ORBs:"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:141
+#, no-c-format
+msgid "Locating the OTS transaction manager server"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:145
+#, no-c-format
+msgid "Resolution Mechanism"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:146
+#, no-c-format
+msgid "<entry>ORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:151
+#, no-c-format
+msgid "<entry>OTS configuration file</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:152
+#, no-c-format
+msgid "All available ORBs"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:155
+#, no-c-format
+msgid "<entry>Name Service</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:156 Chapter.xml:160
+#, no-c-format
+msgid "<entry>JacORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:159
+#, no-c-format
+msgid "<entry>resolve_initial_references</entry>"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:167
+#, no-c-format
+msgid "XA specific management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid ""
+"Each XA Xid that JBossTS creates must have a unique node identifier encoded "
+"within it and JBossTS will only recover transactions and states that match a "
+"specified node identifier. The node identifier to use should be provided to "
+"JBossTS via the <property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property> "
+"property. You must make sure this value is unique across your JBossTS "
+"instances. If you do not provide a value, then JBossTS will fabricate one "
+"and report the value via the logging infrastructure."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"When running XA recovery it is therefore necessary to tell JBossTS which "
+"types of Xid it can recover. Each Xid that JBossTS creates has a unique node "
+"identifier encoded within it and JBossTS will only recover transactions and "
+"states that match a specified node identifier. The node identifier to use "
+"should be provided to JBossTS via a property that starts with the name "
+"<property>com.arjuna.ats.jta.xaRecoveryNode</property>; multiple values may "
+"be provided. A value of <code>*</code> will force JBossTS to recover (and "
+"possibly rollback) all transactions irrespective of their node identifier "
+"and should be used with caution."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:177
+#, no-c-format
+msgid "Web Service Transaction service management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:178
+#, no-c-format
+msgid ""
+"The basic building blocks of a transactional Web Services application are "
+"the application itself, the Web services that the application consumes, the "
+"Transaction Manager, and the transaction participants which support those "
+"Web services. Though it is unlikely in a typical deployment that a single "
+"developer will be expected to support all of these roles, the concepts are "
+"presented here so that a global model can be visualized. It will often be "
+"the case that developers will produce services, or applications that consume "
+"services, whilst system administrators will run the transaction-management "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:182
+#, fuzzy, no-c-format
+msgid "The Transaction Manager"
+msgstr "Der Recovery Manager"
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"The transaction manager is a Web service which coordinates JBossTS "
+"transactions. It is the only software component in JBossTS that is meant to "
+"be run directly as a network service, rather than to support end-user code. "
+"The transaction manager runs as a JAXM request/response Web service."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:187
+#, no-c-format
+msgid ""
+"When starting up an application server instance that has JBossTS deployed "
+"within it, you may see various <emphasis>error</emphasis> messages in the "
+"console or log. For example <code>16:53:38,850 ERROR [STDERR] Message "
+"Listener Service: started, message listener jndi name activationcoordinator</"
+"code>. These are for information purposes only and are not actual errors."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:192
+#, fuzzy, no-c-format
+msgid "Configuring the Transaction Manager"
+msgstr "Konfiguration des Recovery-Managers"
+
+#. Tag: para
+#: Chapter.xml:193
+#, no-c-format
+msgid ""
+"The Transaction Manager and related infrastructure are configured by means "
+"of properties files: <filename>wscf.xml</filename>, <filename>wst.xml</"
+"filename> and <filename>wstx.xml</filename>. These files can be found in the "
+"conf directory and are used for configuring the demo application and the "
+"standalone module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"For the most part the default values in these files need not be altered. "
+"However, the <property>com.arjuna.ats.arjuna.objectstore.objectStoreDir</"
+"property> property determines the location of the persistent store used to "
+"record transaction state. The default value of <filename>C:/temp/"
+"ObjectStore</filename> should be changed to a value appropriate to your "
+"system. For production environments this directory should reside on fault "
+"tolerant media such as a RAID array."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"When a standalone coordinator is being used by an application it is "
+"necessary to enable and modify two further properties in <filename>wstx.xml</"
+"filename>, <property>com.arjuna.mw.wst.coordinatorURL</property> and "
+"<property>com.arjuna.mw.wst.terminatorURL</property>. These contain the URLs "
+"necessary for the client application to contact the standalone coordinator "
+"and should be configured with the correct hostname and port of the "
+"standalone coordinator."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"JBossTS is highly modular so in order to allow for flexible deployment of "
+"individual components, the same property values are sometimes required to "
+"appear in more than one configuration file. For the majority of "
+"configurations, you should maintain consistent values for properties that "
+"are defined in more than one file."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:207
+#, no-c-format
+msgid "Deploying the Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"The JBossTS Web Service Transaction Manager component consists of a number "
+"of JAR files containing the application’s class files, plus Web service "
+"(WAR) files which expose the necessary services. Programmers will typically "
+"include all these components in their application EAR file during "
+"application development, simplifying deployment of the transaction "
+"infrastructure. For production usage the Transaction Manager may be "
+"installed as an application in its own right, allowing for centralized "
+"configuration and management at the server level, independent of specific "
+"applications. The demonstration application shipped with JBossTS provides a "
+"sample deployment descriptor illustrating how the Transaction Manager "
+"components can be included in an application."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"JBossTS 4.0 uses fixed endpoints for its underlying protocol communication. "
+"Therefore, problems may arise if multiple applications using JBossTS are "
+"deployed to the same server concurrently. If you wish to deploy several "
+"transactional applications in the same server, the Transaction Manger must "
+"be deployed as a separate application and not embedded within the deployment "
+"of individual applications."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid ""
+"The coordinator directory in the JBossTS installation has been provided to "
+"assist in the configuration and deployment of a stand-alone transaction "
+"manager. In order to use this, you must:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:220
+#, fuzzy, no-c-format
+msgid "Have JBoss Enterprise Application Platform 5 installed"
+msgstr "JBoss Enterprise Application Platform"
+
+#. Tag: para
+#: Chapter.xml:225
+#, no-c-format
+msgid "Install ant 1.4 or later."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:231
+#, no-c-format
+msgid ""
+"It is important that a separate application server installation be used from "
+"the one that clients and services are deployed into since otherwise "
+"conflicts may occur between the various JBossTS components."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:235
+#, no-c-format
+msgid ""
+"You must then edit the build.xml included with coordinator to point to the "
+"application server installation where the transaction coordinator will be "
+"deployed and the location of the JBossTS installation. The files "
+"<filename>ws-c_jaxm_web-app.xml</filename> and <filename>ws-t_jaxm_web-app."
+"xml</filename> in the <filename>dd</filename> directory of coordinator are "
+"the deployment descriptors for the WS-C and WS-T WAR files. These files "
+"contain templated URLs. During the build phase, ant will substitute the "
+"hostname and port values you specify in the <filename>build.xml</filename> "
+"into these files."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:238
+#, no-c-format
+msgid ""
+"Run <code>ant</code>, with <code>target deploy-weblogic</code>, <code>deploy-"
+"jboss</code> or <code>deploy-webmethods</code>, to create and deploy a new "
+"coordinator into the correct application server installation."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:241
+#, no-c-format
+msgid ""
+"Now all you need to do is point your client at the required coordinator. To "
+"do this, generate the demo application specifying the port and hostname of "
+"the coordinator."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:245
+#, no-c-format
+msgid "Deployment descriptors"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:246
+#, no-c-format
+msgid ""
+"In general, it should not be necessary to change the contents of the various "
+"deployment descriptors used by JBossTS. However, if you do need to modify "
+"them they are all included in the coordinator module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:250
+#, no-c-format
+msgid ""
+"Not all JBossTS components have ready access to the information in the "
+"deployment descriptors. Therefore, if you modify the JNDI names used by any "
+"of the WS-C or WS-T deployment descriptors you may need to inform other "
+"JBossTS components at runtime. This can be accomplished by setting an "
+"appropriate property in the <filename>wstx.xml</filename> configuration file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:253
+#, no-c-format
+msgid ""
+"The following table shows the default JNDI name used by the deployment "
+"descriptors and the corresponding property to set if the default value is "
+"changed."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:257
+#, no-c-format
+msgid "Deployment descriptor values and properties"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:261
+#, no-c-format
+msgid "JNDI Name"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:262
+#, no-c-format
+msgid "Property"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:267
+#, no-c-format
+msgid "Activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:268
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:271
+#, no-c-format
+msgid "Activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:272
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:275
+#, no-c-format
+msgid "Completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:276
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:279
+#, no-c-format
+msgid "Registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:280
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:283
+#, no-c-format
+msgid "durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:284
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:287
+#, no-c-format
+msgid "durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:288
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:291
+#, no-c-format
+msgid "volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:292
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:295
+#, no-c-format
+msgid "volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:296
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:299
+#, no-c-format
+msgid "businessagreementwithparticipantcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:300
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:303
+#, no-c-format
+msgid "businessagreementwithparticipantcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:304
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:307
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:308
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:311
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:312
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccparticipant"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:319
+#, no-c-format
+msgid "JBoss Transactions runtime information"
+msgstr "JBoss Transactions Runtime Informationen"
+
+#. Tag: para
+#: Chapter.xml:320
+#, 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 ""
+"Jedes Modul, aus dem JBoss Transactions besteht, besitzt eine Klasse namens "
+"Info. Diese Klassen liefern eine einzelne toString-Methode, die ein XML-"
+"Dokument wiedergibt, das die Konfigurationsinformationen für dieses Modul "
+"repräsentiert. Also zum Beispiel:"
#. Tag: programlisting
-#: Chapter.xml:31
+#: Chapter.xml:322
#, no-c-format
msgid ""
"<module-info name=\"arjuna\">\n"
@@ -138,15 +997,29 @@
" </configuration>\n"
"</module-info>"
msgstr ""
+"<module-info name=\"arjuna\">\n"
+" <source-identifier>unknown</source-identifier>\n"
+" <build-information>\n"
+" Arjuna Technologies [mlittle] (Windows 2000 5.0)\n"
+" </build-information>\n"
+" <version>unknown</version>\n"
+" <date>2002/06/15 04:06 PM</date>\n"
+" <notes></notes>\n"
+" <configuration>\n"
+" <properties-file dir=\"null\">arjuna.properties</"
+"properties-file>\n"
+" <object-store-root>null</object-store-root>\n"
+" </configuration>\n"
+"</module-info>"
#. Tag: title
-#: Chapter.xml:34
+#: Chapter.xml:325
#, no-c-format
msgid "Failure recovery administration"
-msgstr ""
+msgstr "\"Failure Recovery\"-Administration"
#. Tag: para
-#: Chapter.xml:35
+#: Chapter.xml:326
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions will ensure that "
@@ -161,16 +1034,31 @@
"failure and is accessible afterward: this information is held in the "
"ActionStore, which is part of the ObjectStore."
msgstr ""
+"Das Failure-Recovery Subsystem von JBoss Transactions stellt sicher, dass "
+"Ergebnisse einer Transaktion konsistent an allen betroffenen Ressourcen "
+"durch die Transaktion angewendet werden, selbst wenn Applikationsprozesse "
+"oder die diese hostende Maschine abstürzen oder Netzwerk-Konnektivität "
+"verlieren. Im Falle eines Crashs der Maschine (des Systems) oder "
+"Netzwerkversagens findet die Recovery nicht statt, ehe das System oder "
+"Netzwerk nicht wieder hergestellt sind, aber die ursprüngliche Anwendung "
+"muss nicht neu gestartet werden – Recovery Verantwortlichkeiten werden an "
+"den Recovery Manager Prozess delegiert (siehe unten). Recovery nach "
+"Fehlschlagen erfordert, dass Informationen über die Transaktion und und die "
+"involvierten Ressources das Fehlschlagen überstehen und anschließend "
+"zugänglich sind: Diese Informationen werden im ActionStore aufbewahrt, der "
+"Teil des ObjectStore ist."
#. Tag: para
-#: Chapter.xml:38
+#: Chapter.xml:329
#, no-c-format
msgid ""
"If the ObjectStore is destroyed or modified, recovery may not be possible."
msgstr ""
+"Wird der ObjectStore gelöscht oder bearbeitet, ist eine Recovery eventuell "
+"nicht möglich."
#. Tag: para
-#: Chapter.xml:41
+#: Chapter.xml:332
#, no-c-format
msgid ""
"Until the recovery procedures are complete, resources affected by a "
@@ -180,15 +1068,22 @@
"resources, an attempt to activate the Transactional Object (as when trying "
"to get a lock) will fail."
msgstr ""
+"Bis der Recovery-Vorgang vollständig ist sind Ressourcen, die zum Zeitpunkt "
+"des Fehlschlagens durch eine laufende Transaktion betroffen waren, "
+"möglicherweise unzugänglich. Für Datenbank-Ressourcen kann dies als Tabellen "
+"oder Reihen gemeldet werden, die durch “in-doubt transactions” (zweifelhafte "
+"Transaktionen) gehalten werden. Für TransactionalObjects für Java-Ressourcen "
+"schlägt ein Versuch das transaktionale Objekt (\"Transactional Object\") zu "
+"aktivieren (wie beim Versuch eine Sperre zu erhalten) fehl."
#. Tag: title
-#: Chapter.xml:43
+#: Chapter.xml:334
#, no-c-format
msgid "The Recovery Manager"
-msgstr ""
+msgstr "Der Recovery Manager"
#. Tag: para
-#: Chapter.xml:44
+#: Chapter.xml:335
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions requires that the stand-"
@@ -199,35 +1094,44 @@
"RecoveryManager</classname>. To start the Recovery Manager issue the "
"following command:"
msgstr ""
+"Das Failure-Recovery Subsystem von JBoss Transactions erfordert, dass der "
+"eigenständige Recovery Manager Prozess für jeden ObjectStore läuft (in der "
+"Regel einer für jeden Node im Netzwerk auf dem JBoss Transactions "
+"Applikationen laufen). Die RecoveryManager-Datei befindet sich in der "
+"arjunacore jar-Datei innerhalb des Pakets <classname>com.arjuna.ats.arjuna."
+"recovery.RecoveryManager</classname>. Um den Recovery Manager zu starten, "
+"geben Sie folgenden Befehl ein:"
#. Tag: command
-#: Chapter.xml:45
+#: Chapter.xml:336
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
-msgstr ""
+msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
#. Tag: para
-#: Chapter.xml:46
+#: Chapter.xml:337
#, 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 ""
+"Wird das <literal>-test</literal>-Flag mit dem Recovery Manager benutzt, so "
+"zeigt es eine “Ready”-Nachricht an, wenn initialisiert, d.h."
#. Tag: command
-#: Chapter.xml:47
+#: Chapter.xml:338
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
-msgstr ""
+msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager -Test"
#. Tag: title
-#: Chapter.xml:50
+#: Chapter.xml:341
#, no-c-format
msgid "Configuring the Recovery Manager"
-msgstr ""
+msgstr "Konfiguration des Recovery-Managers"
#. Tag: para
-#: Chapter.xml:51
+#: Chapter.xml:342
#, no-c-format
msgid ""
"The RecoveryManager reads the properties defined in the <filename>arjuna."
@@ -238,9 +1142,16 @@
"in the main TransactionService properties file. Most of the entries are "
"specific to the Recovery Manager."
msgstr ""
+"Der RecoveryManager liest die in der <filename>arjuna.properties</filename>-"
+"Datei definierten Properties und liest dann auch die Property-Datei "
+"<filename>RecoveryManager.properties</filename>, vom selben Verzeichnis wie "
+"in der \"arjuna\" Properties-Datei gefunden. Ein Eintrag für eine Property "
+"in der RecoveryManager Properties-Datei setzt einen Eintrag für dieselbe "
+"Property in der Haupt-TransactionService-Properties-Datei außer Kraft. Die "
+"meisten der Einträge sind spezifisch für den Recovery Manager."
#. Tag: para
-#: Chapter.xml:52
+#: Chapter.xml:343
#, no-c-format
msgid ""
"A default version of <filename>RecoveryManager.properties</filename> is "
@@ -250,15 +1161,21 @@
"other values (in the order of their appearance in the default version of the "
"file)"
msgstr ""
+"Eine Standard-Version der <filename>RecoveryManager.properties</filename> "
+"ist Teil der Distribution – dies kann ohne weitere Bearbeitung verwendet "
+"werden, außer vielleicht die \"Debug Tracing\"-Felder zur Fehlersuche (siehe "
+"unten in der Ausgabe). Der Rest dieses Abschnitts geht auf Themen ein, die "
+"beim Einstellen der Properties auf andere Werte relevant sind (in der "
+"Reihenfolge ihres Auftretens in der Standardversion der Datei)"
#. Tag: title
-#: Chapter.xml:54
+#: Chapter.xml:345
#, no-c-format
msgid "Output"
-msgstr ""
+msgstr "Ausgabe"
#. Tag: para
-#: Chapter.xml:55
+#: Chapter.xml:346
#, no-c-format
msgid ""
"It is likely that installations will want to have some form of output from "
@@ -270,9 +1187,18 @@
"Commons Logging framework and configuration is assumed to occur through that "
"framework."
msgstr ""
+"Es ist wahrscheinlich, dass Installationen irgendeine Form von Ausgabe vom "
+"RecoveryManager fordern werden, um einen Eintrag darüber zu besitzen, welche "
+"Recovery-Aktivität stattgefunden hat. Der RecoveryManager verwendet den "
+"Verfolgungsmechanismus für die Protokollierung, der durch das Arjuna Common "
+"Logging Framework (CLF) bereitgestellt wird und ein High-Level Interface "
+"bietet, das zwischen bestehenden APIs wie Jakarta log4j oder JDK 1.4 "
+"Protokollierungs-API bestehende Differenzen verbirgt. CLF lenkt sämtliche "
+"Protokollierung via dem Apache Commons Logging Framework um, und es wird "
+"angenommen, dass die Konfiguration durch dieses Framework erfolgt."
#. Tag: para
-#: Chapter.xml:58
+#: Chapter.xml:349
#, no-c-format
msgid ""
"With the CLF applications make logging calls on logger objects. Loggers may "
@@ -283,9 +1209,17 @@
"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
"FATAL."
msgstr ""
+"Mit den CLF-Applikationen erfolgen Protokollaufrufe an Logger-Objekte. "
+"Logger können Protokollebenen verwenden, um zu entscheiden, ob sie sich für "
+"eine bestimmte Protokollnachricht interessieren. Jede Protokollnachricht "
+"besitzt eine zugehörige Protokollebene, die die Wichtigkeit und "
+"Dringlichkeit einer Protokollnachricht angibt. Der Satz möglicher "
+"Protokollebenen lautet DEBUG, INFO, WARN, ERROR und FATAL. Definierte Ebenen "
+"werden gemäß ihren ganzzahligen Werten wie folgt geordnet: DEBUG < INFO "
+"< WARN < ERROR < FATAL."
#. Tag: para
-#: Chapter.xml:61
+#: Chapter.xml:352
#, no-c-format
msgid ""
"The CLF provides an extension to filter logging messages according to finer "
@@ -293,47 +1227,63 @@
"provided to the logger with the DEBUG level, additional conditions can be "
"specified to determine if the log message is enabled or not."
msgstr ""
+"Die CLF liefert eine Erweiterung zum Filtern von Protokollnachrichten "
+"entsprechend feinerer Granularität, die eine Anwendung definieren kann. Das "
+"bedeutet, dass wenn dem Logger eine Protokollnachricht mit der DEBUG-Ebene "
+"geliefert wird, zusätzliche Bedingungen festgelegt werden können, um zu "
+"bestimmen, ob die Protokollnachricht aktiviert ist oder nicht. "
#. Tag: para
-#: Chapter.xml:67
+#: Chapter.xml:358
#, 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 ""
+"Diese Bedingungen gelten nur, wenn die DEBUG-Ebene aktiviert ist und die "
+"durch die Anwendung durchgeführte Protokollanfrage Debugging-Granularität "
+"festlegt."
#. Tag: para
-#: Chapter.xml:71
+#: Chapter.xml:362
#, no-c-format
msgid "When enabled, Debugging is filtered conditionally on three variables:"
msgstr ""
+"Wenn aktiviert, wird \"Debugging\" (Fehlersuche) konditional auf drei "
+"Variablen gefiltert:"
#. Tag: para
-#: Chapter.xml:74
+#: Chapter.xml:365
#, 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 ""
+"\"Debugging\"-Ebene: Hier wird die Protokolllierungsanfrage mit der DEBUG-"
+"Ebene generiert, zum Beispiel aus Konstruktoren oder Grundmethoden."
#. Tag: para
-#: Chapter.xml:77
+#: Chapter.xml:368
#, no-c-format
msgid ""
"Visibility level: the visibility of the constructor, method, etc. that "
"generates the debugging."
msgstr ""
+"Sichtbarkeitsebene: Die Sichtbarkeit des Konstruktors, der Methode, usw., "
+"durch die das Debugging generiert wird."
#. Tag: para
-#: Chapter.xml:80
+#: Chapter.xml:371
#, no-c-format
msgid ""
"Facility code: for instance the package or sub-module within which debugging "
"is generated, e.g., the object store."
msgstr ""
+"Facility Code: Zum Beispiel das Paket oder Sub-Modul innerhalb dessen "
+"Debugging generiert wird, zum Beispiel der \"Object Store\"."
#. Tag: para
-#: Chapter.xml:83
+#: Chapter.xml:374
#, no-c-format
msgid ""
"According to these variables the CLF defines three interfaces. A particular "
@@ -345,230 +1295,262 @@
"enable debug messages. Finer debugging values used by the JBoss Transactions "
"are defined below:"
msgstr ""
+"Diesen Variablen nach definiert die CLF drei Interfaces. Ein bestimmtes "
+"Produkt kann seine eigenen Klassen entsprechend seiner eigenen feineren "
+"Granularität implementieren. JBoss Transactions verwenden die durch CLF "
+"bereitgestellte Standard Debugging-Ebene und die Standard "
+"Sichtbarkeitsebene, definieren jedoch ihren eigenen Facility Code. JBoss "
+"Transactions verwendet die seinen Logger Objekten (DEBUG) zugewiesene "
+"Standardebene. Es verwendet jedoch die feineren Debugging Features um Debug-"
+"Nachrichten zu aktivieren oder zu deaktivieren. Feinere Debugging Werte, die "
+"von JBoss Transactions verwendet werden, sind unten definiert:"
#. Tag: para
-#: Chapter.xml:84
+#: Chapter.xml:375
#, 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 ""
+"Debugging-Ebene – JBoss Transactions verwendet die in der <classname>com."
+"arjuna.common.util.logging.DebugLevel</classname>-Klasse definierten "
+"Standardwerte"
#. Tag: para
-#: Chapter.xml:87
+#: Chapter.xml:378
#, no-c-format
msgid ""
"NO_DEBUGGING: No diagnostics. A logger object assigned with this values "
"discard all debug requests"
msgstr ""
+"NO_DEBUGGING: No Diagnostik. Ein Logger-Objekt dem diese Werte zugeordnet "
+"sind verwirft alle Debug-Anfragen"
#. Tag: para
-#: Chapter.xml:90
+#: Chapter.xml:381
#, 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 ""
+"FULL_DEBUGGING: Volle Diagnostik. Ein Logger-Objekt dem diese Werte "
+"zugeordnet sind gestattet alle Debug-Anfragen wenn der Facility-Code und die "
+"Sichtbarkeitsebene mit denen durch den Logger gestatteten übereinstimmen."
#. Tag: para
-#: Chapter.xml:93
+#: Chapter.xml:384
#, no-c-format
msgid "Additional Debugging Values are:"
-msgstr ""
+msgstr "Weitere Debugging-Werte sind:"
#. Tag: para
-#: Chapter.xml:96
+#: Chapter.xml:387
#, no-c-format
msgid "CONSTRUCTORS: Diagnostics from constructors."
-msgstr ""
+msgstr "CONSTRUCTORS: Diagnostik von Konstruktoren."
#. Tag: para
-#: Chapter.xml:99
+#: Chapter.xml:390
#, no-c-format
msgid "DESTRUCTORS: Diagnostics from finalizers."
-msgstr ""
+msgstr "DESTRUCTORS: Diagnostik von Finalizers."
#. Tag: para
-#: Chapter.xml:102
+#: Chapter.xml:393
#, no-c-format
msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
-msgstr ""
+msgstr "CONSTRUCT_AND_DESTRUCT: Diagnostik von Konstruktoren und Finalizers."
#. Tag: para
-#: Chapter.xml:105
+#: Chapter.xml:396
#, no-c-format
msgid "FUNCTIONS: Diagnostics from functions."
-msgstr ""
+msgstr "FUNCTIONS: Diagnostik von Functions."
#. Tag: para
-#: Chapter.xml:108
+#: Chapter.xml:399
#, no-c-format
msgid "OPERATORS: Diagnostics from operators, such as equals."
-msgstr ""
+msgstr "OPERATORS: Diagnostik von Operators, wie etwa \"Equals\"."
#. Tag: para
-#: Chapter.xml:111
+#: Chapter.xml:402
#, no-c-format
msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
-msgstr ""
+msgstr "FUNCS_AND_OPS: Diagnostik von Functions und Operations."
#. Tag: para
-#: Chapter.xml:114
+#: Chapter.xml:405
#, no-c-format
msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
-msgstr ""
+msgstr "ALL_NON_TRIVIAL: Diagnostik von allen nicht-trivialen Operations."
#. Tag: para
-#: Chapter.xml:117
+#: Chapter.xml:408
#, no-c-format
msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
-msgstr ""
+msgstr "TRIVIAL_FUNCS: Diagnostik von trivialen Functions."
#. Tag: para
-#: Chapter.xml:120
+#: Chapter.xml:411
#, no-c-format
msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
-msgstr ""
+msgstr "TRIVIAL_OPERATORS: Diagnostik von trivialen Operations und Operatoren."
#. Tag: para
-#: Chapter.xml:123
+#: Chapter.xml:414
#, no-c-format
msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
-msgstr ""
+msgstr "ALL_TRIVIAL: Diagnostik von allen trivialen Vorgängen."
#. Tag: para
-#: Chapter.xml:126
+#: Chapter.xml:417
#, 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 ""
+"Sichtbarkeitsebene – JBoss Transactions verwendet die in der <classname>com."
+"arjuna.common.util.logging.VisibilityLevel</classname>-Klasse definierten "
+"Standardwerte"
#. Tag: para
-#: Chapter.xml:129
+#: Chapter.xml:420
#, no-c-format
msgid "VIS_NONE: No Diagnostic"
-msgstr ""
+msgstr "VIS_NONE: Keine Diagnostik"
#. Tag: para
-#: Chapter.xml:132
+#: Chapter.xml:423
#, no-c-format
msgid "VIS_PRIVATE : only from private methods."
-msgstr ""
+msgstr "VIS_PRIVATE : Nur von privaten Methoden."
#. Tag: para
-#: Chapter.xml:135
+#: Chapter.xml:426
#, no-c-format
msgid "VIS_PROTECTED only from protected methods."
-msgstr ""
+msgstr "VIS_PROTECTED nur von geschützten Methoden."
#. Tag: para
-#: Chapter.xml:138
+#: Chapter.xml:429
#, no-c-format
msgid "VIS_PUBLIC only from public methods."
-msgstr ""
+msgstr "VIS_PUBLIC nur von öffentlichen Methoden."
#. Tag: para
-#: Chapter.xml:141
-#, no-c-format
-msgid "VIS_JBoss_Transactions_Administrators_Guide only from package methods."
-msgstr ""
+#: Chapter.xml:432
+#, fuzzy, no-c-format
+msgid "VIS_PACKAGE only from package methods."
+msgstr "VIS_PUBLIC nur von öffentlichen Methoden."
#. Tag: para
-#: Chapter.xml:144
+#: Chapter.xml:435
#, no-c-format
msgid "VIS_ALL: Full Diagnostic"
-msgstr ""
+msgstr "VIS_ALL: Volle Diagnostik"
#. Tag: para
-#: Chapter.xml:147
+#: Chapter.xml:438
#, 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 ""
+"Facility Code – JBoss Transactions verwendet die folgenden in der "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>-Klasse "
+"definierten Werte"
#. Tag: para
-#: Chapter.xml:150
+#: Chapter.xml:441
#, no-c-format
msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
-msgstr ""
+msgstr "FAC_ATOMIC_ACTION = 0x0000001 (atomische Aktion Kernmodul)."
#. Tag: para
-#: Chapter.xml:153
+#: Chapter.xml:444
#, no-c-format
msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
msgstr ""
+"FAC_BUFFER_MAN = 0x00000004 (Status-Management (Zwischenspeicher) Klassen)."
#. Tag: para
-#: Chapter.xml:156
+#: Chapter.xml:447
#, no-c-format
msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
-msgstr ""
+msgstr "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
#. Tag: para
-#: Chapter.xml:159
+#: Chapter.xml:450
#, no-c-format
msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
-msgstr ""
+msgstr "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
#. Tag: para
-#: Chapter.xml:162
+#: Chapter.xml:453
#, no-c-format
msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
-msgstr ""
+msgstr "FAC_STATE_MAN = 0x00000020 (Status-Management und StateManager)."
#. Tag: para
-#: Chapter.xml:165
+#: Chapter.xml:456
#, no-c-format
msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
-msgstr ""
+msgstr "FAC_SHMEM = 0x00000040 (geteilte Speicherimplementierungsklassen)."
#. Tag: para
-#: Chapter.xml:168
+#: Chapter.xml:459
#, no-c-format
msgid "FAC_GENERAL = 0x00000080 (general classes)."
-msgstr ""
+msgstr "FAC_GENERAL = 0x00000080 (allgemeine Klassen)."
#. Tag: para
-#: Chapter.xml:171
+#: Chapter.xml:462
#, no-c-format
msgid ""
"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
"classes)."
msgstr ""
+"FAC_CRASH_RECOVERY = 0x00000800 (ausführliches Verfolgen von Crash Recovery "
+"Modul und Klassen)."
#. Tag: para
-#: Chapter.xml:174
+#: Chapter.xml:465
#, no-c-format
msgid "FAC_THREADING = 0x00002000 (threading classes)."
-msgstr ""
+msgstr "FAC_THREADING = 0x00002000 (Threading Klassen)."
#. Tag: para
-#: Chapter.xml:177
+#: Chapter.xml:468
#, no-c-format
msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
-msgstr ""
+msgstr "AC_JDBC = 0x00008000 (JDBC 1.0 und 2.0 Support)."
#. Tag: para
-#: Chapter.xml:180
+#: Chapter.xml:471
#, no-c-format
msgid ""
"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
msgstr ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normale Ausgabe für Crash Recovery "
+"Manager)."
#. Tag: para
-#: Chapter.xml:183
+#: Chapter.xml:474
#, 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 ""
+"Um die ordnungsgemäße Ausgabe zu gewährleisten ist es notwendig einige der "
+"feineren Debug-Properties explizit in der <filename>CommonLogging.xml</"
+"filename>-Datei einzustellen, um durch das JBoss Transactions Modul "
+"herausgegebene Protokollnachrichten zu aktivieren."
#. Tag: para
-#: Chapter.xml:184
+#: Chapter.xml:475
#, no-c-format
msgid ""
"Messages describing the start and the periodical behavior made by the "
@@ -578,9 +1560,16 @@
"messages related to the Crash Recovery protocol and issued by the JBoss "
"Transactions module."
msgstr ""
+"Durch den RecoveryManager gemeldete Nachrichten, die den Start und das "
+"periodische Verhalten beschreiben, werden mittels der INFO-Ebene ausgegeben. "
+"Ist eine andere Debug-Verfolgung gewünscht so sollte die feinkörnigere "
+"Debugging-Ebene entsprechend eingestellt sein. Folgende Konfiguration etwa "
+"in der CommonLogging.xml, aktiviert alle Debug-Nachrichten, die mit dem "
+"Crash Recovery Protokoll zusammenhängen und durch das JBoss Transactions "
+"Modul herausgegeben wurden."
#. Tag: programlisting
-#: Chapter.xml:186
+#: Chapter.xml:477
#, no-c-format
msgid ""
"<!-- Common logging related properties. -->\n"
@@ -592,17 +1581,27 @@
"<propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
" value=\"0xffffffff\"/>"
msgstr ""
+"<!-- Common logging related properties. -->\n"
+"<property\n"
+" name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+" value=\"0x00000000\"/>\n"
+"<propertyname=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+" value=\"0xffffffff\"/>\n"
+"<propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+" value=\"0xffffffff\"/>"
#. Tag: para
-#: Chapter.xml:189
+#: Chapter.xml:480
#, no-c-format
msgid ""
"Two logger objects are provided, one manages I18N messages and a second does "
"not."
msgstr ""
+"Zwei Logger-Objekte werden bereitgestellt, eines davon verwaltet I18N "
+"Nachrichten, das andere nicht."
#. Tag: para
-#: Chapter.xml:192
+#: Chapter.xml:483
#, no-c-format
msgid ""
"Setting the normal recovery messages to the INFO level allows the "
@@ -612,15 +1611,23 @@
"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 ""
+"Das Einstellen der normalen Recovery-Nachrichten auf die INFO-Ebene "
+"gestattet dem RecoveryManager eine bescheidene Ebene der Berichterstattung "
+"zu erstellen. Falls nichts passiert, so meldet es nur den Eintrag in jedes "
+"Modul für jeden periodischen Pass. Um durch den Recovery Manager produzierte "
+"INFO-NAchrichten zu deaktivieren, könnte die Protokollierungsebene auf eine "
+"höhere Ebene gesetzt werden: ERROR. Das Einstellen der Ebene auf ERROR "
+"bedeutet, dass der RecoveryManager nur Error, Warning oder Meldungen zu "
+"unbehebbaren Fehlern produziert."
#. Tag: title
-#: Chapter.xml:196
+#: Chapter.xml:487
#, no-c-format
msgid "Periodic Recovery"
-msgstr ""
+msgstr "Periodische Recovery"
#. Tag: para
-#: Chapter.xml:197
+#: Chapter.xml:488
#, no-c-format
msgid ""
"The RecoveryManager scans the ObjectStore and other locations of "
@@ -632,9 +1639,17 @@
"used are dynamically loaded, using properties found in the RecoveryManager "
"property file."
msgstr ""
+"Der RecoveryManager scant den ObjectStore und andere Speicherorte von "
+"Information und sucht nach Transaktionen und Ressourcen, die Recovery "
+"benötigen oder benötigen könnten. Die Scans und Recovery Durchführung werden "
+"von Recovery Modulen durchgeführt (Instanzen von Klassen, die das com.arjuna."
+"ats.arjuna.recovery.RecoveryModule-Interface implementieren), jedes mit der "
+"Verantwortung für eine bestimmte Kategorie von Transaktion oder Ressource. "
+"Der Satz verwendeter Recovery-Module wird dynamisch geladen, wobei im "
+"RecoveryManager gefundene Properties verwendet werden."
#. Tag: para
-#: Chapter.xml:198
+#: Chapter.xml:489
#, no-c-format
msgid ""
"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
@@ -650,9 +1665,21 @@
"it is possible the original application process has crashed and the item is "
"a candidate for recovery."
msgstr ""
+"Das Interface besitzt zwei Methoden: <literal>periodicWorkFirstPass</"
+"literal> und <literal>periodicWorkSecondPass</literal>. Zu einem Intervall "
+"(definiert durch Property <classname>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</classname>), ruft der RecoveryManager die erste Pass-"
+"Methode an jeder Property auf und wartet dann kurze Zeit (definiert durch "
+"Property <classname>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</"
+"classname>), und ruft dann den zweiten Pass jedes Moduls auf. In der Regel "
+"scant das Modul beim ersten Pass, das Modul scant (z.B. den relevanten Teil "
+"des ObjectStore), um fragliche Transaktionen oder Ressourcen zu finden (d.h "
+"sind Teil des Festschreibungsprozesses). Beim zweiten Pass ist es möglich, "
+"wenn einige dieser Posten nach wie vor fraglich sind, dass der ursprüngliche "
+"Anwendungsprozess gecrasht ist und der Posten ein Kandidat für Recovery ist."
#. Tag: para
-#: Chapter.xml:199
+#: Chapter.xml:490
#, no-c-format
msgid ""
"An attempt, by the RecoveryManager, to recover a transaction that is still "
@@ -667,9 +1694,21 @@
"usually generating a warning. Recovery of such a transaction is the "
"RecoveryManager’s responsibility)."
msgstr ""
+"Ein Versuch durch den RecoveryManager eine noch in dem/den ursprünglichen "
+"Prozess/-en fortschreitende Transaktion wiederherzustellen, wird aller "
+"Wahrscheinlichkeit nach die Konsistenz brechen. Entsprechend verwenden die "
+"Recovery-Module einen Mechanismus (implementiert im <classname>com.arjuna."
+"ats.arjuna.recovery.TransactionStatusManager</classname>-Paket), um zu "
+"überprüfen, ob der ursprüngliche Prozess noch aktiv ist und die Transaktion "
+"noch fortschreitet. Der RecoveryManager fährt nur mit der Recovery fort, "
+"wenn der ursprüngliche Prozess nicht mehr vorhanden ist oder - falls noch "
+"bestehend - die Transktion beendet ist. (Crasht ein Server-Prozess oder eine "
+"Maschine, der Transaktions-initiierende Prozess aber überlebt, so schließt "
+"die Transaktion in der Regel eine Warnung generierend ab. Die Recovery einer "
+"solchen Transaktion obliegt der Verantwortung des RecoveryManagers)."
#. Tag: para
-#: Chapter.xml:200
+#: Chapter.xml:491
#, no-c-format
msgid ""
"It is clearly important to set the interval periods appropriately. The total "
@@ -689,18 +1728,39 @@
"thus require a “call to the original process to see if they are still in "
"progress"
msgstr ""
+"Es ist ganz klar wichtig, die Intervallperioden korrekt einzustellen. Die "
+"gesamte Iterationszeit wird die Summe der <literal>periodicRecoveryPeriod</"
+"literal>, <literal>recoveryBackoffPeriod</literal> und die Länge an Zeit, "
+"die erforderlich ist, die Speicher zu scannen und die Recovery aufgefundener "
+"Transaktionen für sämtliche Recovery-Module zu versuchen. Die für den "
+"Recovery-Versuch aufgewendete Zeit kann Connection-Timeouts während der "
+"Kommunikation mit Prozessen oder Maschinen die abgestürzt sind oder auf die "
+"nicht zugegriffen werden kann beinhalten (weswegen es Mechanismen im "
+"Recovery-System gibt, um zu vermeiden, dass für immer die Recovery derselben "
+"Transaktion erfolgt). Die gesamte Iteration hat Einfluss darauf, wie lange "
+"auf eine Ressource nach dem Fehlschlagen nicht zugegriffen werden kann – "
+"<literal>periodicRecoveryPeriod</literal> sollte entsprechend eingestellt "
+"sein (der Standard ist 120 Sekunden). Die <literal>recoveryBackoffPeriod</"
+"literal> kann vergleichsweise kurz sein (der Standard ist 10 Sekunden) – ihr "
+"Zweck ist hauptsächlich die Anzahl von Transaktionen zu reduzieren, die "
+"Kandidaten für Recovery sind einen Aufruf an den ursprünglichen Prozess "
+"benötigen, um zu sehen, ob sie noch laufen."
#. Tag: para
-#: Chapter.xml:203
+#: Chapter.xml:494
#, 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 ""
+"In früheren Versionen von JBoss Transactions existierte kein "
+"Kontaktmechanismus und der Backoff-Zeitraum musste lang genug sein, damit "
+"Transaktionen nicht \"im Flug\" abgefangen wurden. Ab 3.0 besteht dieses "
+"Risiko nicht mehr."
#. Tag: para
-#: Chapter.xml:206
+#: Chapter.xml:497
#, no-c-format
msgid ""
"Two recovery modules (implementations of the <classname>com.arjuna.ats."
@@ -716,9 +1776,22 @@
"process might occur while a periodic recovery pass is in progress). The "
"default Recovery Extension settings are:"
msgstr ""
+"Zwei Recovery-Module (Implementierungen des <classname>com.arjuna.ats.arjuna."
+"recovery.RecoveryModule</classname>-Interface) werden mit JBoss Transactions "
+"geliefert, und unterstützen verschiedene Aspekte von Transaction Recovery "
+"einschließlich JDBC-Recovery. Fortgeschrittene Benutzer können ihre eigenen "
+"Recovery-Module erstellen und diese beim Recovery Manager registrieren. Die "
+"Recovery-Module werden unter Verwendung von Properties, die mit "
+"“<classname>com.arjuna.ats.arjuna.recovery.RecoveryExtension</classname>” "
+"beginnen beim RecoveryManager registriert. Diese werden bei jedem Pass der "
+"periodischen Recovery in der Sortierordnung der Property-Namen aufgerufen – "
+"es ist daher möglich die Reihenfolge vorauszusagen (aber beachten Sie, dass "
+"es zu einem Fehlschlagen in einem Anwendungsprozess kommen kann, während ein "
+"periodischer Recovery-Pass gerade am Laufen ist). Die Standard Recovery-"
+"Erweiterungseinstellungen lauten:"
#. Tag: programlisting
-#: Chapter.xml:208
+#: Chapter.xml:499
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
@@ -727,15 +1800,20 @@
"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
" com.arjuna.ats.txoj.recovery.TORecoveryModule"
msgstr ""
+"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"
#. Tag: title
-#: Chapter.xml:211
+#: Chapter.xml:502
#, no-c-format
msgid "Expired entry removal"
-msgstr ""
+msgstr "Entfernen nicht mehr gültiger Einträge"
#. Tag: para
-#: Chapter.xml:212
+#: Chapter.xml:503
#, no-c-format
msgid ""
"The operation of the recovery subsystem will cause some entries to be made "
@@ -755,15 +1833,33 @@
"value is negative, the first scan is delayed until after the first interval "
"(using the absolute value)"
msgstr ""
+"Betrieb des Recovery Subsystems wird zu einigen Einträgen im ObjectStore "
+"führen, die im normalen Fortschreiten nicht entfernt werden. Der "
+"RecoveryManager besitzt eine Einrichtung zum Scannen und Entfernen sehr "
+"alter Posten. Scans und Entfernungen werden durch Implementierungen des "
+"<classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname>-"
+"Interface durchgeführt. Implementierungen dieses Interface werden durch "
+"Eingabe des Klassennamens als Wert einer Property, deren Name mit "
+"<classname>com.arjuna.ats.arjuna.recovery.expiryScanner</classname> beginnt, "
+"geladen. Der RecoveryManager ruft die <command>scan()</command>-Methode bei "
+"jeder geladenen Expiry Scanner Implementierung zu einem durch die Property "
+"<classname>com.arjuna.ats.arjuna.recovery.expiryScanInterval</classname> "
+"festgelegten Intervall auf. Dieser Wert wird in Stunden angegeben – der "
+"Standard ist 12. Ein <classname>expiryScanInterval</classname>-Wert von Null "
+"unterdrückt jegliches Expiry-Scanning. Falls der Wert wie geliefert positiv "
+"ist, so wird der erste Scan durchgeführt wenn RecoveryManager startet; ist "
+"der Wert negativ, wird der erste Scan hinausgezögert bis der erste Intervall "
+"vorüber ist (unter Verwendung des absoluten Wertes)"
#. Tag: para
-#: Chapter.xml:213
+#: Chapter.xml:504
#, no-c-format
msgid "The kinds of item that are scanned for expiry are:"
msgstr ""
+"Die Arten von Posten, die nach einem Verfallsdatum gescannt werden sind:"
#. Tag: para
-#: Chapter.xml:214
+#: Chapter.xml:505
#, no-c-format
msgid ""
"TransactionStatusManager items : one of these is created by every "
@@ -775,158 +1871,351 @@
"– 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 Posten: Einer von diesen wird durch jeden "
+"Applikationsprozess erstellt, der JBoss Transactions verwendet – sie "
+"enthalten Informationen, die es dem RecoveryManager gestatten zu bestimmen, "
+"ob der Prozess, der die Transaktion initiiert hat, noch aktiv ist und "
+"welches der Transaktionsstatus ist. Der Verfallszeitpunkt für diese wird "
+"durch die <classname>com.arjuna.ats.arjuna.recovery."
+"transactionStatusManagerExpiryTime</classname>-Property gesetzt (in Stunden "
+"– Standard ist 12, Null bedeutet, dass sie nie verfallen). Der "
+"Verfallszeitpunkt sollte größer als die Lebensdauer eines einzelnen JBoss "
+"Transactions verwendenden Prozesses sein."
#. Tag: para
-#: Chapter.xml:215
+#: Chapter.xml:506
#, no-c-format
msgid "The Expiry Scanner properties for these are:"
-msgstr ""
+msgstr "Die Properties für den Expiry-Scanner für diese sind:"
#. Tag: programlisting
-#: Chapter.xml:217
+#: Chapter.xml:508
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
" com.arjuna.ats.internal.ts.arjuna.recovery."
"ExpiredTransactionStatusManagerScanner"
msgstr ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
+" com.arjuna.ats.internal.ts.arjuna.recovery."
+"ExpiredTransactionStatusManagerScanner"
#. Tag: title
-#: Chapter.xml:220
+#: Chapter.xml:511
#, no-c-format
-msgid "Errors and Exceptions"
+msgid "Selecting the JTA implementation"
+msgstr "Auswahl der JTA-Implementierung"
+
+#. Tag: para
+#: Chapter.xml:512
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
msgstr ""
+"Es werden jetzt zwei Varianten der JTA-Implementierung bereitgestellt und "
+"sind über dasselbe Interface zugänglich. Diese sind:"
#. Tag: para
-#: Chapter.xml:221
+#: Chapter.xml:515
#, 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."
+"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 ""
+"Eine rein lokale JTA, die nur die Ausführung nicht distrubuiter JTA "
+"Transaktionen gestattet. Dieses ist die einzige mit dem JBoss Transactions "
+"Produkt verfügbare Version."
#. Tag: para
-#: Chapter.xml:224
+#: Chapter.xml:518
#, 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."
+"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 ""
+"Eine Remote, CORBA-basierte JTA, die die Ausführung distrubuiter JTA "
+"Transaktionen gestattet. Diese Version ist nur mit dem ArjunaJTS Produkt "
+"verfügbar und erfordert ein CORBA ORB."
#. Tag: para
-#: Chapter.xml:227
+#: Chapter.xml:522
#, 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."
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
msgstr ""
+"beide dieser Implementierungen sind vollständig kompatibel mit dem "
+"transaktionalen JDBC-Driver, der mit JBoss Transactions geliefert wird."
#. Tag: para
-#: Chapter.xml:230
+#: Chapter.xml:525
#, 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."
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
msgstr ""
+"Um die lokale JTA-Implementierung zu wählen, müssen folgende Schritte "
+"durchgeführt werden:"
#. Tag: para
-#: Chapter.xml:233
+#: Chapter.xml:528
#, 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."
+"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 ""
+"vergewissern Sie sich, dass die Property <literal>com.arjuna.ats.jta."
+"jtaTMImplementation</literal> auf <literal>com.arjuna.ats.internal.jta."
+"transaction.arjunacore.TransactionManagerImple</literal> eingestellt ist."
#. Tag: para
-#: Chapter.xml:236
+#: Chapter.xml:531
#, 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."
+"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 ""
+"vergewissern Sie sich, dass die Property <literal>com.arjuna.ats.jta."
+"jtaUTImplementation</literal> auf <literal>com.arjuna.ats.internal.jta."
+"transaction.arjunacore.UserTransactionImple</literal> eingestellt ist."
+#. Tag: para
+#: Chapter.xml:535
+#, 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 ""
+"Diese Einstellungen sind die Standardwerte für die Pproperties und müssen "
+"nicht festgelegt werden, wenn die lokale Implementierung benötigt wird."
+
#. Tag: title
-#: Chapter.xml:241
+#: Chapter.xml:542
#, no-c-format
-msgid "Selecting the JTA implementation"
+msgid "ORB specific configurations"
msgstr ""
+#. Tag: title
+#: Chapter.xml:544
+#, no-c-format
+msgid "<title>JacORB</title>"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:242
+#: Chapter.xml:545
#, no-c-format
msgid ""
-"Two variants of the JTA implementation are now provided and accessible "
-"through the same interface. These are:"
+"For JacORB to function correctly it is necessary to ensure there is a valid "
+"<filename>jacorb.properties</filename> or <filename>.jacorb_properties</"
+"filename> file in one of the following places:"
msgstr ""
#. Tag: para
-#: Chapter.xml:245
+#: Chapter.xml:551
#, no-c-format
+msgid "The classpath."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:556
+#, 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."
+"The home directory of the user running the JBoss Transaction Service. The "
+"home directory is retrieved using <code>System.getProperty( “user.home” );</"
+"code>"
msgstr ""
#. Tag: para
-#: Chapter.xml:248
+#: Chapter.xml:561
#, no-c-format
+msgid "The current directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:566
+#, 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."
+"The <filename>lib</filename> directory of the JDK used to run your "
+"application. This is retrieved using <code>System.getProperty( “java.home” );"
+"</code>"
msgstr ""
#. Tag: para
-#: Chapter.xml:252
+#: Chapter.xml:571
#, no-c-format
msgid ""
-"both of these implementations are fully compatible with the transactional "
-"JDBC driver provided with JBoss Transactions."
+"The above places are searched in the order given. A template "
+"<filename>jacorb.properties</filename> file can be found in the JacORB "
+"installation directory."
msgstr ""
#. Tag: para
-#: Chapter.xml:255
+#: Chapter.xml:574
#, no-c-format
msgid ""
-"In order to select the local JTA implementation it is necessary to perform "
-"the following steps:"
+"Within the JacORB properties file there are two important properties which "
+"must be tailored to suit your application, they are:"
msgstr ""
+#. Tag: property
+#: Chapter.xml:580
+#, no-c-format
+msgid "jacorb.poa.thread_pool_max"
+msgstr ""
+
+#. Tag: property
+#: Chapter.xml:585
+#, no-c-format
+msgid "jacorb.poa.thread_pool_min"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:258
+#: Chapter.xml:589
#, 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>."
+"These properties specify the minimum and maximum number of request "
+"processing threads that JacORB will use in its thread pool. If there aren’t "
+"a sufficient number of threads available in this thread pool then the "
+"application may appear to become deadlocked. For more information on "
+"configuring JacORB please reference the JacORB documentation."
msgstr ""
#. Tag: para
-#: Chapter.xml:261
+#: Chapter.xml:593
#, 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>."
+"JacORB comes with its own implementation of the classes defined in the "
+"<filename>CosTransactions.idl</filename> file. Unfortunately these are "
+"incompatible with the version shipped with JBossTS. Therefore, it is "
+"important that the JBossTS jar files appear in the <code>CLASSPATH</code> "
+"before any JacORB jars."
msgstr ""
#. Tag: para
-#: Chapter.xml:265
+#: Chapter.xml:597
#, 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."
+"When running the recovery manager it is important that it always uses the "
+"same well known port for each machine on which it runs. You should not use "
+"the OAPort property provided by JacORB unless the recovery manager has its "
+"own <filename>jacorb.properties</filename> file or this is provided on the "
+"command line when starting the recovery manager. If the recovery manager and "
+"other components of JBossTS share the same <filename>jacorb.properties</"
+"filename> file, then you should use the <filename>com.arjuna.ats.jts."
+"recoveryManagerPort</filename> and <filename>com.arjuna.ats.jts."
+"recoveryManagerAddress</filename> properties."
msgstr ""
+
+#. Tag: title
+#: Chapter.xml:603
+#, no-c-format
+msgid "Initializing JBossTS applications"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:604
+#, no-c-format
+msgid ""
+"It is important that JBossTS is correctly initialized prior to any "
+"application object being created. In order to guarantee this, the programmer "
+"should use the <methodname>ORB_init</methodname> and <methodname>create_POA</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:609
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr "Fehler und Ausnahmen"
+
+#. Tag: para
+#: Chapter.xml:610
+#, 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 ""
+"In diesem Abschnitt behandeln wir die Fehler und Ausnahmen, die während "
+"einer transaktionalen Anwendung gemeldet werden können, und liefern mögliche "
+"Anzeichen für deren Ursachen."
+
+#. Tag: para
+#: Chapter.xml:613
+#, 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 ""
+"NO_MEMORY: Die Anwendung besitzt nicht mehr genug Speicher (ein "
+"<classname>OutOfMemoryError</classname> wirde gemeldet) und JBoss "
+"Transactions hat versucht, eine Bereinigung durchzuführen (durch Ausführen "
+"des \"Garbage Collector\") ehe die Ausname erneut gemeldet wurde. Es handelt "
+"sich dabei wahrscheinlich um ein vorübergehendes Problem und ein erneuter "
+"Versuch des Aufrufs sollte erfolgreich sein."
+
+#. Tag: para
+#: Chapter.xml:616
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: Ein Fehler ist aufgetreten, was "
+"bedeutet, dass das Transaktionssystem heruntergefahren werden muss. Ehe "
+"dieser Fehler gemeldet wird, wird der Transaktionsdienst sichergestellt "
+"haben, dass alle laufenden Transaktionen zurückgesetzt wurden. Falls "
+"abgefangen, so sollte die Anwendung eine Bereinigung durchführen und "
+"beenden. Wird weitere Arbeit versucht, so ist es möglich, dass die "
+"Anwendundskonsistenz verletzt wird."
+
+#. Tag: para
+#: Chapter.xml:619
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: Es wurde ein Versuch "
+"unternommen, den Transaktionsdienst auf eine Weise zu verwenden, die nicht "
+"konsistent mit der aktuellen Lizenz ist. Der Transaktionsdienst gestattet "
+"kein weiteres Fortschreiten bestehender oder neuer Transaktionen."
+
+#. Tag: para
+#: Chapter.xml:622
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: Es kam zu einem Fehler, "
+"während der Transaktionsdienst versucht hat, den Object Store zu verwenden. "
+"Ein weiteres Fortschreiten ist nicht möglich."
+
+#. Tag: para
+#: Chapter.xml:625
+#, 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 ""
+"Object Store Warnungen zu Zugriffsproblemen auf Stati können während der "
+"normalen Ausführung von Crash Recovery auftreten. Dies ist das Ergebnis "
+"mehrerer gleichzeitiger Versuche eine Recovery an derselben Transaktion "
+"durchzuführen. Sie können gefahrlos ignoriert werden."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Feedback.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Feedback.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Feedback.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,3 +1,4 @@
+# translation of Preface.po to
# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
@@ -3,19 +4,20 @@
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Project-Id-Version: Preface\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"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-09-20 15:28+1000\n"
+"Last-Translator: \n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Feedback.xml:6
#, no-c-format
msgid "Feedback"
-msgstr ""
+msgstr "Feedback"
#. Tag: para
@@ -32,3 +34,13 @@
"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 ""
+"Falls Sie einen Fehler in diesem Handbuch entdecken oder eine Idee dazu "
+"haben, wie wir dieses verbessern können, dann würden wir uns sehr darüber "
+"freuen von Ihnen zu hören! Senden Sie einen Bericht an <ulink url=\"http://"
+"jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> zum Produkt: JBoss "
+"Enterprise Application Platform, Version: <replaceable><version></"
+"replaceable>, Komponente: <emphasis>Doc</emphasis>. Falls Sie einen "
+"Vorschlag zur Verbesserung der Dokumentation haben, versuchen Sie so "
+"spezifisch wie möglich zu sein. Falls Sie einen Fehler gefunden haben, "
+"schließen Sie die Abschnittsnummer mit ein sowie einen Teil des umgebenden "
+"Textes, damit wir diesen leichter finden können."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Preface.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Preface.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,3 +1,4 @@
+# translation of Preface.po to
# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
@@ -3,25 +4,26 @@
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Project-Id-Version: Preface\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"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-09-20 15:28+1000\n"
+"Last-Translator: \n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Preface.xml:6
#, no-c-format
msgid "Preface"
-msgstr ""
+msgstr "Vorwort"
#. Tag: title
#: Preface.xml:14
#, no-c-format
msgid "What This Guide Contains"
-msgstr ""
+msgstr "Inhalte dieses Handbuchs"
#. Tag: para
@@ -32,12 +34,14 @@
"The Administration Guide contains information on how to administer JBoss "
"Transactions API 4.2.3."
msgstr ""
+"Das Handbuch zur Administration enthält Informationen dazu, wie JBoss "
+"Transactions API 4.2.3 gehandhabt wird."
#. Tag: title
#: Preface.xml:17
#, no-c-format
msgid "Audience"
-msgstr ""
+msgstr "Zielgruppe"
#. Tag: para
#: Preface.xml:18
@@ -46,12 +50,15 @@
"This guide is most relevant to engineers who are responsible for "
"administration of JBoss Transactions API 4.2.3 installations."
msgstr ""
+"Dieses Handbuch ist von größtem Nutzen für Ingenieure, die für die "
+"Administration von JBoss Transactions API 4.2.3 Installationen "
+"verantwortlich sind."
#. Tag: title
#: Preface.xml:21
#, no-c-format
msgid "Prerequisites"
-msgstr ""
+msgstr "Voraussetzungen"
#. Tag: para
#: Preface.xml:22
@@ -62,18 +69,23 @@
"functionality. As such, it is important to read the ArjunaCore "
"Administration Guide before attempting to administer JBoss Transactions."
msgstr ""
+"Um JBoss Transactions zu administrieren ist es zunächst notwendig sich "
+"dessen bewusst zu werden, dass dieses hinsichtlich der "
+"Transaktionsfunktionalität stark von ArjunaCore abhängt. Daher ist es "
+"wichtig, das Administrationshandbuch von ArjunaCore zu lesen, ehe Sie sich "
+"an der Administration von JBoss Transactions versuchen."
#. Tag: title
#: Preface.xml:25
#, no-c-format
msgid "Organization"
-msgstr ""
+msgstr "Organisation"
#. Tag: para
#: Preface.xml:26
#, no-c-format
msgid "This guide contains the following chapters:"
-msgstr ""
+msgstr "Dieses Handbuch enthält die folgenden Kapitel:"
#. Tag: para
#: Preface.xml:29
@@ -83,12 +95,16 @@
"JBoss Transactions, mainly by selecting the variant of JTA implementation: "
"pure local or remote (allowing distributed transactions)."
msgstr ""
+"Kapitel 1, Administration von JBoss Transaktionen: Beschreibt die "
+"Administration von JBoss Transaktionen, primär durch Auswahl der Variante "
+"von JTA-Implementierung: rein lokal oder Remote (distribuierte Transaktionen "
+"gestattend)."
#. Tag: title
#: Preface.xml:34
#, no-c-format
msgid "Additional Documentation"
-msgstr ""
+msgstr "Zusätzliche Dokumentation"
#. Tag: para
#: Preface.xml:35
@@ -97,6 +113,8 @@
"In addition to this guide, the following guides are available in the JBoss "
"Transactions API 4.2.3 documentation set:"
msgstr ""
+"Zusätzlich zu diesem Handbuch sind folgende Handbücher im Dokumentationssatz "
+"von JBoss Transactions API 4.2.3 enthalten:"
#. Tag: para
#: Preface.xml:38
@@ -105,6 +123,8 @@
"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
"information about JBoss Transactions API 4.2.3."
msgstr ""
+"JBoss Transactions API 4.2.3 Release Notes: Liefert die letzten und "
+"aktuellsten Information zu JBoss Transactions API 4.2.3."
#. Tag: para
#: Preface.xml:41
@@ -113,6 +133,8 @@
"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
"instructions for installing JBoss Transactions API 4.2.3."
msgstr ""
+"JBoss Transactions API 4.2.3 Installationshandbuch: Dieses Handbuch enthält "
+"Anleitungen zur Installation von JBoss Transactions API 4.2.3."
#. Tag: para
#: Preface.xml:44
@@ -121,3 +143,5 @@
"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
"writing applications."
msgstr ""
+"JBoss Transactions API 4.2.3 Programmer’s Guide: Liefert Richtlinien zum "
+"Schreiben von Anwendungen."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Revision_History.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/de-DE/Revision_History.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,3 +1,4 @@
+# translation of Preface.po to
# Language de-DE translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
@@ -3,17 +4,24 @@
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Project-Id-Version: Preface\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"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-09-20 15:28+1000\n"
+"Last-Translator: \n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "Revisionshistorie"
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
-msgstr ""
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Author_Group.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Author_Group.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,13 +1,13 @@
-# translation of Author_Group.po to
+# translation of Preface.po to
# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
msgid ""
msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: Preface\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-16 13:32+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-20 11:30+1000\n"
"Last-Translator: Angela Garcia\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -15,21 +15,8 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
-#. Tag: corpauthor
-#: Author_Group.xml:6
-#, no-c-format
-msgid "FF0000 Headgear Documentation Group"
-msgstr "Grupo de documentación Headgear FF0000 "
-
#. 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 ""
-"<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>"
-
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Book_Info.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Book_Info.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,13 +1,13 @@
-# translation of Book_Info.po to
+# translation of Preface.po to
# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
msgid ""
msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: Preface\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-16 13:37+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-20 11:30+1000\n"
"Last-Translator: Angela Garcia\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -17,29 +17,28 @@
#. Tag: title
#: Book_Info.xml:6
-#, no-c-format
-msgid "JBoss Transactions API 4.2.3 Administration Guide"
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Administrators Guide"
msgstr "Manual de administración de JBoss Transactions API 4.2.3 "
#. Tag: subtitle
#: Book_Info.xml:10
-#, no-c-format
-msgid "JBoss Enterprise Application Platform"
+#, fuzzy, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 5.0"
msgstr "JBoss Enterprise Application Platform"
#. Tag: para
-#: Book_Info.xml:13
+#: Book_Info.xml:15
#, no-c-format
msgid ""
"This book is the JBoss Enterprise Application Platform edition of the JBoss "
"Transactions Administrators Guide"
msgstr ""
-"Este libro es la edición de JBoss Enterprise Application Platform del manual de administración de JBoss "
-"Transactions "
+"Este libro es la edición de JBoss Enterprise Application Platform del manual "
+"de administración de JBoss Transactions "
#. Tag: holder
-#: Book_Info.xml:22
+#: Book_Info.xml:24
#, no-c-format
msgid "&HOLDER;"
msgstr "&HOLDER;"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Chapter.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Chapter.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Chapter.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,13 +1,13 @@
-# translation of Chapter.po to
+# translation of Preface.po to
# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
msgid ""
msgstr ""
-"Project-Id-Version: Chapter\n"
+"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-06-19 00:13+0000\n"
-"PO-Revision-Date: 2008-06-20 11:40+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-20 11:30+1000\n"
"Last-Translator: Angela Garcia\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -106,9 +106,10 @@
"medio de nuevas versiones de operaciones o viceversa."
#. Tag: para
-#: Chapter.xml:19
+#: Chapter.xml:19 Chapter.xml:62
#, no-c-format
-msgid "Object store management is critically important to the transaction service."
+msgid ""
+"Object store management is critically important to the transaction service."
msgstr ""
"La administración de almacenamiento de objetos es críticamente importante "
"para el servicio de transacciones. "
@@ -116,11 +117,72 @@
#. Tag: title
#: Chapter.xml:24
#, no-c-format
+msgid "Starting and Stopping the transaction manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"By default the transaction manager starts up in an active state such that "
+"new transactions can be created immediately. If you wish to have more "
+"control over this it is possible to set the <property>com.arjuna.ats.arjuna."
+"coordinator.startDisabled</property> configuration option to <literal>YES</"
+"literal>, in which case no transactions can be created until the transaction "
+"manager is enabled (via a call to <methodname>TxControl.enable</methodname>)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:28
+#, no-c-format
+msgid ""
+"It is possible to stop the creation of new transactions at any time by "
+"calling <methodname>TxControl.disable</methodname>. Transactions that are "
+"currently executing will not be affected. By default recovery will be "
+"allowed to continue and the transaction system will still be available to "
+"manage recovery requests from other instances in a distributed environment. "
+"(See the Failure Recovery Guide for further details). However, if you wish "
+"to disable recovery as well as remove any resources it maintains, then you "
+"can pass true to <methodname>TxControl.disable</methodname>; the default is "
+"to use <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"If you wish to shut the system down completely then it may also be necessary "
+"to terminate the background transaction reaper (see the Programmers Guide "
+"for information about what the reaper does.) In order to do this you may "
+"want to first prevent the creation of new transactions (if you are not "
+"creating transactions with timeouts then this step is not necessary) using "
+"<methodname>TxControl.disable</methodname>. Then you should call "
+"<methodname>TransactionReaper.terminate</methodname>. This method takes a "
+"boolean parameter: if true then the method will wait for the normal timeout "
+"periods associated with any transactions to expire before terminating the "
+"transactions; if false then transactions will be forced to terminate "
+"(rollback or have their outcome set such that they can only ever rollback) "
+"immediately."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"If you intent to restart the recovery manager later after having terminated "
+"it then you <emphasis>must</emphasis> use the <methodname>terminate</"
+"methodname> method with <property>asynchronous behavior</property> set to "
+"<literal>false</literal> when shutting down the recovery manager."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:40
+#, no-c-format
msgid "ObjectStore management"
msgstr "Administración de ObjectStore"
#. Tag: para
-#: Chapter.xml:25
+#: Chapter.xml:41
#, no-c-format
msgid ""
"Within the transaction service installation, the object store is updated "
@@ -152,14 +214,756 @@
"borren el contenido del almacenamiento de objetos asumiendo que es un "
"recurso exclusivo. "
+#. Tag: para
+#: Chapter.xml:42
+#, fuzzy, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBossTS software. There are "
+"a few points however, that should be made:"
+msgstr ""
+"Aparte de asegurarse de que el sistema en tiempo de ejecución se encuentra "
+"ejecutando normalmente, se necesita muy poca administración continua para el "
+"software de JBoss Transactions. Sin embargo hay unos pocos puntos a notar:"
+
+#. Tag: para
+#: Chapter.xml:47
+#, fuzzy, no-c-format
+msgid ""
+"The present implementation of the JBossTS system provides no security or "
+"protection for data. It is recommended that the objects stored in the "
+"JBossTS are owned by user arjuna. The Object Store and Object Manager "
+"facilities make no attempt to enforce even the limited form of protection "
+"that Unix and Windows provides. There is no checking of user or group IDs on "
+"access to objects for either reading or writing."
+msgstr ""
+"La implementación presente del sistema de JBoss TA no proporciona seguridad "
+"o protección para datos. Los objetos almacenados en el almacenamiento de "
+"objetos de JBoss Transactions son (usualmente) de propiedad del usuario que "
+"ejecutó la aplicación que los creó. El almacenamiento de objetos y el "
+"administrador de objetos no intentan reforzar ni siquiera la forma limitada "
+"de protección que Unix/Windows proporcionan. No hay verificación de IDs de "
+"usuarios o grupos al acceder los objetos ya esa para leer o escribir."
+
+#. Tag: para
+#: Chapter.xml:52
+#, fuzzy, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> 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 ""
+"Los objetos persistentes creados en el almacenamiento de objetos nunca "
+"desaparecen a menos de que el método StateManager.destroy sea invocado en el "
+"objeto o que alguna aplicación los borre de manera explícita. Esto significa "
+"que el almacenamiento de objetos gradualmente acumula basura (especialmente "
+"durante el desarrollo de la aplicación y las fases de prueba). Hasta el "
+"momento no contamos con una característica de recolección de basura de "
+"manera automatizada. Además no hemos resuelto el problema de referencias "
+"colgantes. Es decir, un objeto persistente, A, puede haber almacenado un Uid "
+"para otro objeto persistente, B, en su representación pasiva en el disco. No "
+"hay nada que evite que una aplicación borre a B aunque A todavía contenga la "
+"referencia a este. Cuando A sea activado e intente acceder a B, tendrá lugar "
+"un error en tiempo de ejecución. "
+
+#. Tag: para
+#: Chapter.xml:57
+#, fuzzy, 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 JBossTS software can neither detect "
+"nor correct references to old object state by new operation versions or vice "
+"versa."
+msgstr ""
+"Hasta el momento no hay soporte para el control de versión de objetos ni la "
+"reconfiguración de bases de datos en el evento de que la estructura de la "
+"clase cambie. Esta es un área de investigación bastante compleja que aún no "
+"hemos abordado. Actualmente si cambia la definición de una clase de objetos "
+"persistentes, es completamente responsable de asegurarse de que las "
+"instancias existentes del objeto en el almacenamiento de objetos sean "
+"convertidas a la nueva representación. El software de JBoss Transactions no "
+"puede detectar ni corregir referencias en estados de objetos viejos por "
+"medio de nuevas versiones de operaciones o viceversa."
+
#. Tag: title
-#: Chapter.xml:28
+#: Chapter.xml:70
#, no-c-format
+msgid "OTS and J2EE Transaction service management"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:72
+#, no-c-format
+msgid "Starting the run-time system"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:73
+#, no-c-format
+msgid ""
+"The JBossTS run-time support consists of run-time packages and the OTS "
+"transaction manager server. By default JBossTS does not use a separate "
+"transaction manager server: transaction managers are co-located with each "
+"application process to improve performance and improve application fault-"
+"tolerance (the application is no longer dependant upon another service in "
+"order to function correctly)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:76
+#, no-c-format
+msgid ""
+"When running applications which require a separate transaction manager, you "
+"must set the <varname>com.arjuna.ats.jts.transactionManager</varname> "
+"environment variable to have the value <literal>yes</literal>. The system "
+"will then locate the transaction manager server in a manner specific to the "
+"ORB being used. The server can be located in a number of ways: by being "
+"registered with a name server, added to the ORB’s initial references, via a "
+"JBossTS specific references file, or by the ORB’s specific location "
+"mechanism (if applicable)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:79
+#, no-c-format
+msgid ""
+"It is possible to override the default registration mechanism by using the "
+"<varname>com.arjuna.orbportability.resolveService</varname> environment "
+"variable. This can have one of the following values:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"<literal>CONFIGURATION_FILE</literal>: the default, this causes the system "
+"to use the <filename>CosServices.cfg</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:89
+#, no-c-format
+msgid ""
+"<literal>NAME_SERVICE</literal>: JBossTS will attempt to use a name service "
+"to register the transaction factory. If this is not supported, an exception "
+"will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:94
+#, no-c-format
+msgid ""
+"<literal>BIND_CONNECT</literal>: JBossTS will use the ORB-specific bind "
+"mechanism. If this is not supported, an exception will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid ""
+"<literal>RESOLVE_INITIAL_REFERENCES</literal>: JBossTS will attempt to "
+"register the transaction service with the ORBs initial service references."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid ""
+"This may not be supported on all ORBs. An exception will be thrown in that "
+"case and another option will have to be used."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:110
+#, no-c-format
+msgid "<title>OTS configuration file</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid ""
+"Similar to the resolve_initial_references, JBossTS supports an initial "
+"reference file where references for specific services can be stored and used "
+"at runtime. The file, CosServices.cfg, consists of two columns: the service "
+"name (in the case of the OTS server TransactionService) and the IOR, "
+"separated by a single space. CosServices.cfg normally resides in the etc "
+"directory of the JBossTS installation; the actual location is determined at "
+"runtime by searching the CLASSPATH for an old copy of the file resident "
+"within an etc directory, or, if one is not found, the location of the "
+"TransactionService properties file directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:115
+#, no-c-format
+msgid ""
+"The OTS server will automatically register itself in this file (creating it "
+"if necessary) if this option is being used. Stale information is also "
+"automatically removed. Machines which wish to share the same transaction "
+"server should have access to (or a copy of) this file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:118
+#, no-c-format
+msgid ""
+"The name and location of the file can be overridden using the <property>com."
+"arjuna.orbportability.initialReferencesFile</property> and <property>com."
+"arjuna.orbportability.initialReferencesRoot</property> property variables, "
+"respectively. It is recommended that the <property>com.arjuna.orbportability."
+"initialReferencesRoot</property> variable is set. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Chapter.xml:121
+#, no-c-format
+msgid ""
+"com.arjuna.orbportability.initialReferencesFile=myFile\n"
+"com.arjuna.orbportability.initialReferencesRoot=c:\\\\temp"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:123
+#, no-c-format
+msgid "<title>Name Service</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:124
+#, no-c-format
+msgid ""
+"If the ORB you are using supports a name service, and JBossTS has been "
+"configured to use it, then the transaction manager will automatically be "
+"registered with it. There is no further work required. This option is not "
+"used for JacORB"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:129
+#, no-c-format
+msgid "<title>resolve_initial_references</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:130
+#, no-c-format
+msgid "Currently this option is only supported for JacORB."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:135
+#, no-c-format
+msgid "Resolution service table"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:136
+#, no-c-format
+msgid ""
+"The following table summarizes the different ways in which the OTS "
+"transaction manager may be located on specific ORBs:"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:141
+#, no-c-format
+msgid "Locating the OTS transaction manager server"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:145
+#, no-c-format
+msgid "Resolution Mechanism"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:146
+#, no-c-format
+msgid "<entry>ORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:151
+#, no-c-format
+msgid "<entry>OTS configuration file</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:152
+#, no-c-format
+msgid "All available ORBs"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:155
+#, no-c-format
+msgid "<entry>Name Service</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:156 Chapter.xml:160
+#, no-c-format
+msgid "<entry>JacORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:159
+#, no-c-format
+msgid "<entry>resolve_initial_references</entry>"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:167
+#, no-c-format
+msgid "XA specific management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid ""
+"Each XA Xid that JBossTS creates must have a unique node identifier encoded "
+"within it and JBossTS will only recover transactions and states that match a "
+"specified node identifier. The node identifier to use should be provided to "
+"JBossTS via the <property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property> "
+"property. You must make sure this value is unique across your JBossTS "
+"instances. If you do not provide a value, then JBossTS will fabricate one "
+"and report the value via the logging infrastructure."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"When running XA recovery it is therefore necessary to tell JBossTS which "
+"types of Xid it can recover. Each Xid that JBossTS creates has a unique node "
+"identifier encoded within it and JBossTS will only recover transactions and "
+"states that match a specified node identifier. The node identifier to use "
+"should be provided to JBossTS via a property that starts with the name "
+"<property>com.arjuna.ats.jta.xaRecoveryNode</property>; multiple values may "
+"be provided. A value of <code>*</code> will force JBossTS to recover (and "
+"possibly rollback) all transactions irrespective of their node identifier "
+"and should be used with caution."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:177
+#, no-c-format
+msgid "Web Service Transaction service management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:178
+#, no-c-format
+msgid ""
+"The basic building blocks of a transactional Web Services application are "
+"the application itself, the Web services that the application consumes, the "
+"Transaction Manager, and the transaction participants which support those "
+"Web services. Though it is unlikely in a typical deployment that a single "
+"developer will be expected to support all of these roles, the concepts are "
+"presented here so that a global model can be visualized. It will often be "
+"the case that developers will produce services, or applications that consume "
+"services, whilst system administrators will run the transaction-management "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:182
+#, fuzzy, no-c-format
+msgid "The Transaction Manager"
+msgstr "El administrador de recuperación "
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"The transaction manager is a Web service which coordinates JBossTS "
+"transactions. It is the only software component in JBossTS that is meant to "
+"be run directly as a network service, rather than to support end-user code. "
+"The transaction manager runs as a JAXM request/response Web service."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:187
+#, no-c-format
+msgid ""
+"When starting up an application server instance that has JBossTS deployed "
+"within it, you may see various <emphasis>error</emphasis> messages in the "
+"console or log. For example <code>16:53:38,850 ERROR [STDERR] Message "
+"Listener Service: started, message listener jndi name activationcoordinator</"
+"code>. These are for information purposes only and are not actual errors."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:192
+#, fuzzy, no-c-format
+msgid "Configuring the Transaction Manager"
+msgstr "Configuración del administrador de recuperación"
+
+#. Tag: para
+#: Chapter.xml:193
+#, no-c-format
+msgid ""
+"The Transaction Manager and related infrastructure are configured by means "
+"of properties files: <filename>wscf.xml</filename>, <filename>wst.xml</"
+"filename> and <filename>wstx.xml</filename>. These files can be found in the "
+"conf directory and are used for configuring the demo application and the "
+"standalone module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"For the most part the default values in these files need not be altered. "
+"However, the <property>com.arjuna.ats.arjuna.objectstore.objectStoreDir</"
+"property> property determines the location of the persistent store used to "
+"record transaction state. The default value of <filename>C:/temp/"
+"ObjectStore</filename> should be changed to a value appropriate to your "
+"system. For production environments this directory should reside on fault "
+"tolerant media such as a RAID array."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"When a standalone coordinator is being used by an application it is "
+"necessary to enable and modify two further properties in <filename>wstx.xml</"
+"filename>, <property>com.arjuna.mw.wst.coordinatorURL</property> and "
+"<property>com.arjuna.mw.wst.terminatorURL</property>. These contain the URLs "
+"necessary for the client application to contact the standalone coordinator "
+"and should be configured with the correct hostname and port of the "
+"standalone coordinator."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"JBossTS is highly modular so in order to allow for flexible deployment of "
+"individual components, the same property values are sometimes required to "
+"appear in more than one configuration file. For the majority of "
+"configurations, you should maintain consistent values for properties that "
+"are defined in more than one file."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:207
+#, no-c-format
+msgid "Deploying the Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"The JBossTS Web Service Transaction Manager component consists of a number "
+"of JAR files containing the application’s class files, plus Web service "
+"(WAR) files which expose the necessary services. Programmers will typically "
+"include all these components in their application EAR file during "
+"application development, simplifying deployment of the transaction "
+"infrastructure. For production usage the Transaction Manager may be "
+"installed as an application in its own right, allowing for centralized "
+"configuration and management at the server level, independent of specific "
+"applications. The demonstration application shipped with JBossTS provides a "
+"sample deployment descriptor illustrating how the Transaction Manager "
+"components can be included in an application."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"JBossTS 4.0 uses fixed endpoints for its underlying protocol communication. "
+"Therefore, problems may arise if multiple applications using JBossTS are "
+"deployed to the same server concurrently. If you wish to deploy several "
+"transactional applications in the same server, the Transaction Manger must "
+"be deployed as a separate application and not embedded within the deployment "
+"of individual applications."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid ""
+"The coordinator directory in the JBossTS installation has been provided to "
+"assist in the configuration and deployment of a stand-alone transaction "
+"manager. In order to use this, you must:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:220
+#, fuzzy, no-c-format
+msgid "Have JBoss Enterprise Application Platform 5 installed"
+msgstr "JBoss Enterprise Application Platform"
+
+#. Tag: para
+#: Chapter.xml:225
+#, no-c-format
+msgid "Install ant 1.4 or later."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:231
+#, no-c-format
+msgid ""
+"It is important that a separate application server installation be used from "
+"the one that clients and services are deployed into since otherwise "
+"conflicts may occur between the various JBossTS components."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:235
+#, no-c-format
+msgid ""
+"You must then edit the build.xml included with coordinator to point to the "
+"application server installation where the transaction coordinator will be "
+"deployed and the location of the JBossTS installation. The files "
+"<filename>ws-c_jaxm_web-app.xml</filename> and <filename>ws-t_jaxm_web-app."
+"xml</filename> in the <filename>dd</filename> directory of coordinator are "
+"the deployment descriptors for the WS-C and WS-T WAR files. These files "
+"contain templated URLs. During the build phase, ant will substitute the "
+"hostname and port values you specify in the <filename>build.xml</filename> "
+"into these files."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:238
+#, no-c-format
+msgid ""
+"Run <code>ant</code>, with <code>target deploy-weblogic</code>, <code>deploy-"
+"jboss</code> or <code>deploy-webmethods</code>, to create and deploy a new "
+"coordinator into the correct application server installation."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:241
+#, no-c-format
+msgid ""
+"Now all you need to do is point your client at the required coordinator. To "
+"do this, generate the demo application specifying the port and hostname of "
+"the coordinator."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:245
+#, no-c-format
+msgid "Deployment descriptors"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:246
+#, no-c-format
+msgid ""
+"In general, it should not be necessary to change the contents of the various "
+"deployment descriptors used by JBossTS. However, if you do need to modify "
+"them they are all included in the coordinator module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:250
+#, no-c-format
+msgid ""
+"Not all JBossTS components have ready access to the information in the "
+"deployment descriptors. Therefore, if you modify the JNDI names used by any "
+"of the WS-C or WS-T deployment descriptors you may need to inform other "
+"JBossTS components at runtime. This can be accomplished by setting an "
+"appropriate property in the <filename>wstx.xml</filename> configuration file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:253
+#, no-c-format
+msgid ""
+"The following table shows the default JNDI name used by the deployment "
+"descriptors and the corresponding property to set if the default value is "
+"changed."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:257
+#, no-c-format
+msgid "Deployment descriptor values and properties"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:261
+#, no-c-format
+msgid "JNDI Name"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:262
+#, no-c-format
+msgid "Property"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:267
+#, no-c-format
+msgid "Activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:268
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:271
+#, no-c-format
+msgid "Activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:272
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:275
+#, no-c-format
+msgid "Completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:276
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:279
+#, no-c-format
+msgid "Registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:280
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:283
+#, no-c-format
+msgid "durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:284
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:287
+#, no-c-format
+msgid "durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:288
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:291
+#, no-c-format
+msgid "volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:292
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:295
+#, no-c-format
+msgid "volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:296
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:299
+#, no-c-format
+msgid "businessagreementwithparticipantcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:300
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:303
+#, no-c-format
+msgid "businessagreementwithparticipantcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:304
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:307
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:308
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:311
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:312
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccparticipant"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:319
+#, no-c-format
msgid "JBoss Transactions runtime information"
msgstr "Información en tiempo de ejecución de JBoss Transactions"
#. Tag: para
-#: Chapter.xml:29
+#: Chapter.xml:320
#, no-c-format
msgid ""
"Each module that comprises JBoss Transactions possesses a class called Info. "
@@ -173,7 +977,7 @@
"módulo. Por ejemplo:"
#. Tag: programlisting
-#: Chapter.xml:31
+#: Chapter.xml:322
#, no-c-format
msgid ""
"<module-info name=\"arjuna\">\n"
@@ -207,13 +1011,13 @@
"</module-info>"
#. Tag: title
-#: Chapter.xml:34
+#: Chapter.xml:325
#, no-c-format
msgid "Failure recovery administration"
msgstr "Administración de recuperación de fallas"
#. Tag: para
-#: Chapter.xml:35
+#: Chapter.xml:326
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions will ensure that "
@@ -229,28 +1033,29 @@
"ActionStore, which is part of the ObjectStore."
msgstr ""
"El subsistema de recuperación de fallas de JBoss Transactions se asegurará "
-"de que los resultados de una transacción se apliquen consistentemente a todos "
-"los recursos afectados por la transacción, incluso si cualquiera de los "
-"procesos de la aplicación o la máquina anfitriona se cuelga o si pierde "
-"conectividad con la red. En el caso en que una máquina (sistema) se cuelgue o "
-"que la red falle, la recuperación no tendrá lugar hasta que el sistema o la "
-"red se reestablezcan, pero la aplicación original no necesita ser reiniciada "
-"- la responsabilidad de la recuperación se delega al proceso administrador "
-"de recuperación (vea a continuación). La recuperación después de una falla "
-"requiere que la información sobre la transacción y los recursos involucrados "
-"sobreviva el fallo y sea accesible después: esta información se encuentra en "
-"el ActionStore, el cual es parte del ObjectStore."
+"de que los resultados de una transacción se apliquen consistentemente a "
+"todos los recursos afectados por la transacción, incluso si cualquiera de "
+"los procesos de la aplicación o la máquina anfitriona se cuelga o si pierde "
+"conectividad con la red. En el caso en que una máquina (sistema) se cuelgue "
+"o que la red falle, la recuperación no tendrá lugar hasta que el sistema o "
+"la red se reestablezcan, pero la aplicación original no necesita ser "
+"reiniciada - la responsabilidad de la recuperación se delega al proceso "
+"administrador de recuperación (vea a continuación). La recuperación después "
+"de una falla requiere que la información sobre la transacción y los recursos "
+"involucrados sobreviva el fallo y sea accesible después: esta información se "
+"encuentra en el ActionStore, el cual es parte del ObjectStore."
#. Tag: para
-#: Chapter.xml:38
+#: Chapter.xml:329
#, no-c-format
-msgid "If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
msgstr ""
"Si el ObjectStore se destruye o se modifica, es posible que no se pueda "
"recuperar."
#. Tag: para
-#: Chapter.xml:41
+#: Chapter.xml:332
#, no-c-format
msgid ""
"Until the recovery procedures are complete, resources affected by a "
@@ -269,13 +1074,13 @@
"bloqueo) fallará. "
#. Tag: title
-#: Chapter.xml:43
+#: Chapter.xml:334
#, no-c-format
msgid "The Recovery Manager"
msgstr "El administrador de recuperación "
#. Tag: para
-#: Chapter.xml:44
+#: Chapter.xml:335
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions requires that the stand-"
@@ -295,13 +1100,13 @@
"iniciar el administrador de recuperación emita el siguiente comando: "
#. Tag: command
-#: Chapter.xml:45
+#: Chapter.xml:336
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
#. Tag: para
-#: Chapter.xml:46
+#: Chapter.xml:337
#, no-c-format
msgid ""
"If the <literal>-test</literal> flag is used with the Recovery Manager then "
@@ -312,19 +1117,19 @@
"cuando se inicializa."
#. Tag: command
-#: Chapter.xml:47
+#: Chapter.xml:338
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
#. Tag: title
-#: Chapter.xml:50
+#: Chapter.xml:341
#, no-c-format
msgid "Configuring the Recovery Manager"
msgstr "Configuración del administrador de recuperación"
#. Tag: para
-#: Chapter.xml:51
+#: Chapter.xml:342
#, no-c-format
msgid ""
"The RecoveryManager reads the properties defined in the <filename>arjuna."
@@ -345,7 +1150,7 @@
"especificas para el administrador de recuperación. "
#. Tag: para
-#: Chapter.xml:52
+#: Chapter.xml:343
#, no-c-format
msgid ""
"A default version of <filename>RecoveryManager.properties</filename> is "
@@ -363,13 +1168,13 @@
"orden de aparición en la versión predeterminada del archivo). "
#. Tag: title
-#: Chapter.xml:54
+#: Chapter.xml:345
#, no-c-format
msgid "Output"
msgstr "Salida"
#. Tag: para
-#: Chapter.xml:55
+#: Chapter.xml:346
#, no-c-format
msgid ""
"It is likely that installations will want to have some form of output from "
@@ -392,7 +1197,7 @@
"ocurre por medio de ese marco de trabajo. "
#. Tag: para
-#: Chapter.xml:58
+#: Chapter.xml:349
#, no-c-format
msgid ""
"With the CLF applications make logging calls on logger objects. Loggers may "
@@ -413,7 +1218,7 @@
"< WARN < ERROR < FATAL."
#. Tag: para
-#: Chapter.xml:61
+#: Chapter.xml:352
#, no-c-format
msgid ""
"The CLF provides an extension to filter logging messages according to finer "
@@ -428,7 +1233,7 @@
"si el mensaje de registro está activado o no. "
#. Tag: para
-#: Chapter.xml:67
+#: Chapter.xml:358
#, no-c-format
msgid ""
"These conditions are applied if and only the DEBUG level is enabled and the "
@@ -439,7 +1244,7 @@
"depuración. "
#. Tag: para
-#: Chapter.xml:71
+#: Chapter.xml:362
#, no-c-format
msgid "When enabled, Debugging is filtered conditionally on three variables:"
msgstr ""
@@ -447,7 +1252,7 @@
"con tres variables:"
#. Tag: para
-#: Chapter.xml:74
+#: Chapter.xml:365
#, no-c-format
msgid ""
"Debugging level: this is where the log request with the DEBUG Level is "
@@ -457,7 +1262,7 @@
"del nivel DEBUG, por ejemplo, métodos básicos o constructores. "
#. Tag: para
-#: Chapter.xml:77
+#: Chapter.xml:368
#, no-c-format
msgid ""
"Visibility level: the visibility of the constructor, method, etc. that "
@@ -467,7 +1272,7 @@
"la depuración. "
#. Tag: para
-#: Chapter.xml:80
+#: Chapter.xml:371
#, no-c-format
msgid ""
"Facility code: for instance the package or sub-module within which debugging "
@@ -477,7 +1282,7 @@
"genera la depuración, por ejemplo, el almacenamiento de objetos. "
#. Tag: para
-#: Chapter.xml:83
+#: Chapter.xml:374
#, no-c-format
msgid ""
"According to these variables the CLF defines three interfaces. A particular "
@@ -500,7 +1305,7 @@
"que JBoss Transactions utiliza están definidos a continuación: "
#. Tag: para
-#: Chapter.xml:84
+#: Chapter.xml:375
#, no-c-format
msgid ""
"Debugging level – JBoss Transactions uses the default values defined in the "
@@ -511,17 +1316,17 @@
"classname>"
#. Tag: para
-#: Chapter.xml:87
+#: Chapter.xml:378
#, no-c-format
msgid ""
"NO_DEBUGGING: No diagnostics. A logger object assigned with this values "
"discard all debug requests"
msgstr ""
-"NO_DEBUGGING: No hay diagnóstico. Un objeto de registro asignado con este valor "
-"descarta todas las peticiones de depuración. "
+"NO_DEBUGGING: No hay diagnóstico. Un objeto de registro asignado con este "
+"valor descarta todas las peticiones de depuración. "
#. Tag: para
-#: Chapter.xml:90
+#: Chapter.xml:381
#, no-c-format
msgid ""
"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
@@ -533,73 +1338,75 @@
"visibilidad coinciden con aquellos permitidos por el registro."
#. Tag: para
-#: Chapter.xml:93
+#: Chapter.xml:384
#, no-c-format
msgid "Additional Debugging Values are:"
msgstr "Los valores de depuración adicionales son: "
#. Tag: para
-#: Chapter.xml:96
+#: Chapter.xml:387
#, no-c-format
msgid "CONSTRUCTORS: Diagnostics from constructors."
msgstr "CONSTRUCTORS: Diagnóstico de los constructores."
#. Tag: para
-#: Chapter.xml:99
+#: Chapter.xml:390
#, no-c-format
msgid "DESTRUCTORS: Diagnostics from finalizers."
msgstr "DESTRUCTORS: Diagnóstico de los finalizadores."
#. Tag: para
-#: Chapter.xml:102
+#: Chapter.xml:393
#, no-c-format
msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
-msgstr "CONSTRUCT_AND_DESTRUCT: Diagnóstico de los constructores y los finalizadores."
+msgstr ""
+"CONSTRUCT_AND_DESTRUCT: Diagnóstico de los constructores y los finalizadores."
#. Tag: para
-#: Chapter.xml:105
+#: Chapter.xml:396
#, no-c-format
msgid "FUNCTIONS: Diagnostics from functions."
msgstr "FUNCTIONS: Diagnóstico desde las funciones."
#. Tag: para
-#: Chapter.xml:108
+#: Chapter.xml:399
#, no-c-format
msgid "OPERATORS: Diagnostics from operators, such as equals."
msgstr "OPERATORS: Diagnóstico desde los operadores como por ejemplo iguales."
#. Tag: para
-#: Chapter.xml:111
+#: Chapter.xml:402
#, no-c-format
msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
msgstr "FUNCS_AND_OPS: Diagnóstico desde las funciones y operaciones."
#. Tag: para
-#: Chapter.xml:114
+#: Chapter.xml:405
#, no-c-format
msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
msgstr "ALL_NON_TRIVIAL: Diagnóstico desde todas las operaciones no triviales."
#. Tag: para
-#: Chapter.xml:117
+#: Chapter.xml:408
#, no-c-format
msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
msgstr "TRIVIAL_FUNCS: Diagnóstico desde las funciones triviales."
#. Tag: para
-#: Chapter.xml:120
+#: Chapter.xml:411
#, no-c-format
msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
-msgstr "TRIVIAL_OPERATORS: Diagnóstico desde operaciones triviales y operadores."
+msgstr ""
+"TRIVIAL_OPERATORS: Diagnóstico desde operaciones triviales y operadores."
#. Tag: para
-#: Chapter.xml:123
+#: Chapter.xml:414
#, no-c-format
msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
msgstr "ALL_TRIVIAL: Diagnóstico desde todas las operaciones triviales."
#. Tag: para
-#: Chapter.xml:126
+#: Chapter.xml:417
#, no-c-format
msgid ""
"Visibility level – JBoss Transactions uses the default values defined in the "
@@ -610,43 +1417,43 @@
"logging.VisibilityLevel</classname>"
#. Tag: para
-#: Chapter.xml:129
+#: Chapter.xml:420
#, no-c-format
msgid "VIS_NONE: No Diagnostic"
msgstr "VIS_NONE: No hay diagnóstico"
#. Tag: para
-#: Chapter.xml:132
+#: Chapter.xml:423
#, no-c-format
msgid "VIS_PRIVATE : only from private methods."
msgstr "VIS_PRIVATE : Sólo desde métodos privados."
#. Tag: para
-#: Chapter.xml:135
+#: Chapter.xml:426
#, no-c-format
msgid "VIS_PROTECTED only from protected methods."
msgstr "VIS_PROTECTED Sólo desde métodos protegidos."
#. Tag: para
-#: Chapter.xml:138
+#: Chapter.xml:429
#, no-c-format
msgid "VIS_PUBLIC only from public methods."
msgstr "VIS_PUBLIC Sólo desde métodos públicos."
#. Tag: para
-#: Chapter.xml:141
+#: Chapter.xml:432
#, no-c-format
msgid "VIS_PACKAGE only from package methods."
msgstr "VIS_PACKAGE Sólo desde métodos de paquetes"
#. Tag: para
-#: Chapter.xml:144
+#: Chapter.xml:435
#, no-c-format
msgid "VIS_ALL: Full Diagnostic"
msgstr "VIS_ALL: Diagnóstico completo"
#. Tag: para
-#: Chapter.xml:147
+#: Chapter.xml:438
#, no-c-format
msgid ""
"Facility Code – JBoss Transactions uses the following values defined in the "
@@ -657,25 +1464,26 @@
"classname>"
#. Tag: para
-#: Chapter.xml:150
+#: Chapter.xml:441
#, no-c-format
msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
msgstr "FAC_ATOMIC_ACTION = 0x0000001 (módulo central de acción atómica)."
#. Tag: para
-#: Chapter.xml:153
+#: Chapter.xml:444
#, no-c-format
msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
-msgstr "FAC_BUFFER_MAN = 0x00000004 (clases (buffer) de administración de estado)."
+msgstr ""
+"FAC_BUFFER_MAN = 0x00000004 (clases (buffer) de administración de estado)."
#. Tag: para
-#: Chapter.xml:156
+#: Chapter.xml:447
#, no-c-format
msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
msgstr "FAC_ABSTRACT_REC = 0x00000008 (registros abstractos)."
#. Tag: para
-#: Chapter.xml:159
+#: Chapter.xml:450
#, no-c-format
msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
msgstr ""
@@ -683,25 +1491,26 @@
"objetos)."
#. Tag: para
-#: Chapter.xml:162
+#: Chapter.xml:453
#, no-c-format
msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
msgstr "FAC_STATE_MAN = 0x00000020 (administración de estado y StateManager)."
#. Tag: para
-#: Chapter.xml:165
+#: Chapter.xml:456
#, no-c-format
msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
-msgstr "FAC_SHMEM = 0x00000040 (clases de implementación de memoria compartida)."
+msgstr ""
+"FAC_SHMEM = 0x00000040 (clases de implementación de memoria compartida)."
#. Tag: para
-#: Chapter.xml:168
+#: Chapter.xml:459
#, no-c-format
msgid "FAC_GENERAL = 0x00000080 (general classes)."
msgstr "FAC_GENERAL = 0x00000080 (clases generales)."
#. Tag: para
-#: Chapter.xml:171
+#: Chapter.xml:462
#, no-c-format
msgid ""
"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
@@ -711,27 +1520,28 @@
"de fallos y clases)."
#. Tag: para
-#: Chapter.xml:174
+#: Chapter.xml:465
#, no-c-format
msgid "FAC_THREADING = 0x00002000 (threading classes)."
msgstr "FAC_THREADING = 0x00002000 (hilos de clases)."
#. Tag: para
-#: Chapter.xml:177
+#: Chapter.xml:468
#, no-c-format
msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
msgstr "AC_JDBC = 0x00008000 (soporte JDBC 1.0 y 2.0)."
#. Tag: para
-#: Chapter.xml:180
+#: Chapter.xml:471
#, no-c-format
-msgid "FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
msgstr ""
"FAC_RECOVERY_NORMAL = 0x00040000 (salida normal para el administrador de "
"recuperación de fallas)."
#. Tag: para
-#: Chapter.xml:183
+#: Chapter.xml:474
#, no-c-format
msgid ""
"To ensure appropriate output, it is necessary to set some of the finer debug "
@@ -744,7 +1554,7 @@
"registro que el módulo JBoss Transactions emite."
#. Tag: para
-#: Chapter.xml:184
+#: Chapter.xml:475
#, no-c-format
msgid ""
"Messages describing the start and the periodical behavior made by the "
@@ -762,7 +1572,7 @@
"el protocolo Crash Recovery y emitido por el módulo JBoss Transactions. "
#. Tag: programlisting
-#: Chapter.xml:186
+#: Chapter.xml:477
#, no-c-format
msgid ""
"<!-- Common logging related properties. -->\n"
@@ -784,7 +1594,7 @@
" value=\"0xffffffff\"/>"
#. Tag: para
-#: Chapter.xml:189
+#: Chapter.xml:480
#, no-c-format
msgid ""
"Two logger objects are provided, one manages I18N messages and a second does "
@@ -794,7 +1604,7 @@
"y el otro no. "
#. Tag: para
-#: Chapter.xml:192
+#: Chapter.xml:483
#, no-c-format
msgid ""
"Setting the normal recovery messages to the INFO level allows the "
@@ -813,13 +1623,13 @@
"mensajes de error, de advertencia o de error fatal. "
#. Tag: title
-#: Chapter.xml:196
+#: Chapter.xml:487
#, no-c-format
msgid "Periodic Recovery"
msgstr "Recuperación periódica"
#. Tag: para
-#: Chapter.xml:197
+#: Chapter.xml:488
#, no-c-format
msgid ""
"The RecoveryManager scans the ObjectStore and other locations of "
@@ -842,7 +1652,7 @@
"propiedades del RecoveryManager."
#. Tag: para
-#: Chapter.xml:198
+#: Chapter.xml:489
#, no-c-format
msgid ""
"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
@@ -864,16 +1674,16 @@
"classname>), el RecoveryManager llamará el primer método pass en cada "
"propiedad y luego espera durante un breve periodo (definido por la propidad "
"<classname>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>) "
-"y luego llama al segundo método pass de cada módulo. Usualmente en el primer método pass, "
-"el módulo escanea (por ejemplo, la parte relevante del ObjectStore) para "
-"encontrar transacciones o recursos que son dudosos (por ejemplo, se "
-"encuentran en cierta parte del proceso de guardado). En el segundo método pass, si "
-"cualquiera de los mismos objetos están en duda, es posible que el proceso de "
-"aplicación original se haya caído y que el objeto sea un candidato para "
-"recuperación."
+"y luego llama al segundo método pass de cada módulo. Usualmente en el primer "
+"método pass, el módulo escanea (por ejemplo, la parte relevante del "
+"ObjectStore) para encontrar transacciones o recursos que son dudosos (por "
+"ejemplo, se encuentran en cierta parte del proceso de guardado). En el "
+"segundo método pass, si cualquiera de los mismos objetos están en duda, es "
+"posible que el proceso de aplicación original se haya caído y que el objeto "
+"sea un candidato para recuperación."
#. Tag: para
-#: Chapter.xml:199
+#: Chapter.xml:490
#, no-c-format
msgid ""
"An attempt, by the RecoveryManager, to recover a transaction that is still "
@@ -888,9 +1698,10 @@
"usually generating a warning. Recovery of such a transaction is the "
"RecoveryManager’s responsibility)."
msgstr ""
-"Un intento del RecoveryManager de recuperar una transacción que aún está en curso en el proceso original con mucha probabilidad romperá la "
-"consistencia. Así mismo, los módulos de recuperación utilizan un mecanismo "
-"(implementado en el paquete <classname>com.arjuna.ats.arjuna.recovery."
+"Un intento del RecoveryManager de recuperar una transacción que aún está en "
+"curso en el proceso original con mucha probabilidad romperá la consistencia. "
+"Así mismo, los módulos de recuperación utilizan un mecanismo (implementado "
+"en el paquete <classname>com.arjuna.ats.arjuna.recovery."
"TransactionStatusManager</classname>) para chequear si el proceso original "
"todavía está vivo y si la transacciín aún se encuentra en progreso. El "
"RecoveryManager sólo procede con la recuperación si el proceso original se "
@@ -901,7 +1712,7 @@
"responsabilidad del RecoveryManager)."
#. Tag: para
-#: Chapter.xml:200
+#: Chapter.xml:491
#, no-c-format
msgid ""
"It is clearly important to set the interval periods appropriately. The total "
@@ -929,19 +1740,19 @@
"todos los módulos de recuperación. El tiempo de intento de recuperación "
"puede incluir la expiración de la conexión mientras que el tratar de "
"comunicarse con procesos o máquinas que se han colgado o que son "
-"inaccesibles (razón por la cual hay mecanismos en el sistema de "
-"recuperación para evitar el tratar de recuperar la misma transacción "
-"indefinidamente). El tiempo de iteración total afectará el tiempo que un "
-"recurso permanecerá inaccesible después de una falla – "
-"<literal>periodicRecoveryPeriod</literal> se debe establecer de acuerdo con "
-"esto (por defecto es 120 segundos). El <literal>recoveryBackoffPeriod</"
-"literal> puede ser comparativamente corto (por defecto es 10 segundos) – su "
-"propósito principal es reducir el número de transacciones que son candidatas "
-"para la recuperación y que por lo tanto requieren una “llamada al proceso "
-"original para ver si aún se encuentran en progreso. "
+"inaccesibles (razón por la cual hay mecanismos en el sistema de recuperación "
+"para evitar el tratar de recuperar la misma transacción indefinidamente). El "
+"tiempo de iteración total afectará el tiempo que un recurso permanecerá "
+"inaccesible después de una falla – <literal>periodicRecoveryPeriod</literal> "
+"se debe establecer de acuerdo con esto (por defecto es 120 segundos). El "
+"<literal>recoveryBackoffPeriod</literal> puede ser comparativamente corto "
+"(por defecto es 10 segundos) – su propósito principal es reducir el número "
+"de transacciones que son candidatas para la recuperación y que por lo tanto "
+"requieren una “llamada al proceso original para ver si aún se encuentran en "
+"progreso. "
#. Tag: para
-#: Chapter.xml:203
+#: Chapter.xml:494
#, no-c-format
msgid ""
"In previous versions of JBoss Transactions there was no contact mechanism, "
@@ -953,7 +1764,7 @@
"evitar las transacciones en vuelo. Desde 3.0 no hay tal riesgo. "
#. Tag: para
-#: Chapter.xml:206
+#: Chapter.xml:497
#, no-c-format
msgid ""
"Two recovery modules (implementations of the <classname>com.arjuna.ats."
@@ -984,7 +1795,7 @@
"predeterminada de Recovery Extension es:"
#. Tag: programlisting
-#: Chapter.xml:208
+#: Chapter.xml:499
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
@@ -1000,13 +1811,13 @@
" com.arjuna.ats.txoj.recovery.TORecoveryModule"
#. Tag: title
-#: Chapter.xml:211
+#: Chapter.xml:502
#, no-c-format
msgid "Expired entry removal"
msgstr "Eliminación de entradas vencidas"
#. Tag: para
-#: Chapter.xml:212
+#: Chapter.xml:503
#, no-c-format
msgid ""
"The operation of the recovery subsystem will cause some entries to be made "
@@ -1029,8 +1840,8 @@
"La operación del subsistema de recuperación hará que se realicen algunas "
"entradas en el ObjectStore que no se eliminarán en el progreso normal. El "
"RecoveryManager tiene una utilidad para escanear estos y para eliminar "
-"objetos que son muy viejos. Los escaneos y las eliminaciones se realizan "
-"por medio de implementaciones de la interfaz <classname>com.arjuna.ats.arjuna."
+"objetos que son muy viejos. Los escaneos y las eliminaciones se realizan por "
+"medio de implementaciones de la interfaz <classname>com.arjuna.ats.arjuna."
"recovery.ExpiryScanner</classname>. Las implementaciones de esta interfaz se "
"cargan dando el nombre de la clase como el valor de una propiedad cuyo "
"nombre empieza por <classname>com.arjuna.ats.arjuna.recovery.expiryScanner</"
@@ -1045,13 +1856,13 @@
"intervalo (utilizando el valor absoluto)."
#. Tag: para
-#: Chapter.xml:213
+#: Chapter.xml:504
#, no-c-format
msgid "The kinds of item that are scanned for expiry are:"
msgstr "Las clases de objetos que se escanean por vencimiento son:"
#. Tag: para
-#: Chapter.xml:214
+#: Chapter.xml:505
#, no-c-format
msgid ""
"TransactionStatusManager items : one of these is created by every "
@@ -1075,13 +1886,13 @@
"Transactions."
#. Tag: para
-#: Chapter.xml:215
+#: Chapter.xml:506
#, no-c-format
msgid "The Expiry Scanner properties for these are:"
msgstr "Las propiedades del Expiry Scanner para estos son: "
#. Tag: programlisting
-#: Chapter.xml:217
+#: Chapter.xml:508
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
@@ -1093,105 +1904,13 @@
"ExpiredTransactionStatusManagerScanner"
#. Tag: title
-#: Chapter.xml:220
+#: Chapter.xml:511
#, no-c-format
-msgid "Errors and Exceptions"
-msgstr "Errores y excepciones"
-
-#. 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 ""
-"En esta sección vamos a cubrir los tipos de errores y excepciones que se "
-"pueden presentar o reportar durante una aplicación transaccional y daremos "
-"indicaciones probables de sus causas."
-
-#. 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 ""
-"NO_MEMORY: la aplication no tiene más memoria (presenta un "
-"<classname>OutOfMemoryError</classname>) y JBoss Transactions ha intentado "
-"realizar alguna limpieza (ejecutando el colector de basura) antes de volver "
-"a presentar la excepción. Probablemente este es un problema transitorio y "
-"con volver a intentar la invocación debe ser suficiente."
-
-#. 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 ""
-"com.arjuna.ats.arjuna.exceptions.FatalError: ha occurrido un error lo cual "
-"significa que el sistema de transacciones se debe apagar. Antes de que este "
-"error se presente el servicio de transacciones se asegurará de que todas las "
-"transacciones ejecutándose se hayan deshecho. Si lo alcanza, la aplicación "
-"debe poner todo en orden y termina. Si se intenta hacer más cosas entonces "
-"la consistencia de la aplicación se puede llegar a violar."
-
-#. 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 ""
-"com.arjuna.ats.arjuna.exceptions.LicenceError: se ha intentado utilizar el "
-"servicio de transacciones de una manera inconsistente con la licencia "
-"actual. El servicio de transacciones no permitirá progresar más alla para "
-"transacciones existentes o nuevas. "
-
-#. 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 ""
-"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: un error ocurrió mientras "
-"el servicio de transacciones intentaba utilizar el almacenamiento de "
-"objectos. No es posible avanzar más allá."
-
-#. 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 ""
-"Las advertencias del almacenamiento de objetos sobre problemas de acceso en "
-"estados pueden ocurrir durante la ejecución normal de recuperación de un "
-"sistema que se ha colgado. Este es el resultado de múltiples intentos "
-"simultáneos para realizar la recuperación en la misma transacción. Se puede "
-"ignorar de manera segura."
-
-#. Tag: title
-#: Chapter.xml:241
-#, no-c-format
msgid "Selecting the JTA implementation"
msgstr "Selección de la implementación JTA"
#. Tag: para
-#: Chapter.xml:242
+#: Chapter.xml:512
#, no-c-format
msgid ""
"Two variants of the JTA implementation are now provided and accessible "
@@ -1201,7 +1920,7 @@
"accesibles a través de la misma interfaz. Estas son:"
#. Tag: para
-#: Chapter.xml:245
+#: Chapter.xml:515
#, no-c-format
msgid ""
"A purely local JTA, which only allows non-distributed JTA transactions to be "
@@ -1213,7 +1932,7 @@
"JBoss Transactions. "
#. Tag: para
-#: Chapter.xml:248
+#: Chapter.xml:518
#, no-c-format
msgid ""
"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
@@ -1225,7 +1944,7 @@
"producto ArjunaJTS y requiere un CORBA ORB soportado."
#. Tag: para
-#: Chapter.xml:252
+#: Chapter.xml:522
#, no-c-format
msgid ""
"both of these implementations are fully compatible with the transactional "
@@ -1235,7 +1954,7 @@
"transaccional que JBoss Transactions proporciona."
#. Tag: para
-#: Chapter.xml:255
+#: Chapter.xml:525
#, no-c-format
msgid ""
"In order to select the local JTA implementation it is necessary to perform "
@@ -1245,7 +1964,7 @@
"los siguientes pasos: "
#. Tag: para
-#: Chapter.xml:258
+#: Chapter.xml:528
#, no-c-format
msgid ""
"make sure the property <literal>com.arjuna.ats.jta.jtaTMImplementation</"
@@ -1257,7 +1976,7 @@
"internal.jta.transaction.arjunacore.TransactionManagerImple</literal>."
#. Tag: para
-#: Chapter.xml:261
+#: Chapter.xml:531
#, no-c-format
msgid ""
"make sure the property <literal>com.arjuna.ats.jta.jtaUTImplementation</"
@@ -1269,7 +1988,7 @@
"internal.jta.transaction.arjunacore.UserTransactionImple</literal>."
#. Tag: para
-#: Chapter.xml:265
+#: Chapter.xml:535
#, no-c-format
msgid ""
"these settings are the default values for the properties and do not need to "
@@ -1278,3 +1997,227 @@
"Esta configuración son los valores predeterminados para las propiedades y no "
"es necesario especificarlos si se requiere la implementación local. "
+#. Tag: title
+#: Chapter.xml:542
+#, no-c-format
+msgid "ORB specific configurations"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:544
+#, no-c-format
+msgid "<title>JacORB</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:545
+#, no-c-format
+msgid ""
+"For JacORB to function correctly it is necessary to ensure there is a valid "
+"<filename>jacorb.properties</filename> or <filename>.jacorb_properties</"
+"filename> file in one of the following places:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:551
+#, no-c-format
+msgid "The classpath."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:556
+#, no-c-format
+msgid ""
+"The home directory of the user running the JBoss Transaction Service. The "
+"home directory is retrieved using <code>System.getProperty( “user.home” );</"
+"code>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:561
+#, no-c-format
+msgid "The current directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:566
+#, no-c-format
+msgid ""
+"The <filename>lib</filename> directory of the JDK used to run your "
+"application. This is retrieved using <code>System.getProperty( “java.home” );"
+"</code>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:571
+#, no-c-format
+msgid ""
+"The above places are searched in the order given. A template "
+"<filename>jacorb.properties</filename> file can be found in the JacORB "
+"installation directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:574
+#, no-c-format
+msgid ""
+"Within the JacORB properties file there are two important properties which "
+"must be tailored to suit your application, they are:"
+msgstr ""
+
+#. Tag: property
+#: Chapter.xml:580
+#, no-c-format
+msgid "jacorb.poa.thread_pool_max"
+msgstr ""
+
+#. Tag: property
+#: Chapter.xml:585
+#, no-c-format
+msgid "jacorb.poa.thread_pool_min"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:589
+#, no-c-format
+msgid ""
+"These properties specify the minimum and maximum number of request "
+"processing threads that JacORB will use in its thread pool. If there aren’t "
+"a sufficient number of threads available in this thread pool then the "
+"application may appear to become deadlocked. For more information on "
+"configuring JacORB please reference the JacORB documentation."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:593
+#, no-c-format
+msgid ""
+"JacORB comes with its own implementation of the classes defined in the "
+"<filename>CosTransactions.idl</filename> file. Unfortunately these are "
+"incompatible with the version shipped with JBossTS. Therefore, it is "
+"important that the JBossTS jar files appear in the <code>CLASSPATH</code> "
+"before any JacORB jars."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:597
+#, no-c-format
+msgid ""
+"When running the recovery manager it is important that it always uses the "
+"same well known port for each machine on which it runs. You should not use "
+"the OAPort property provided by JacORB unless the recovery manager has its "
+"own <filename>jacorb.properties</filename> file or this is provided on the "
+"command line when starting the recovery manager. If the recovery manager and "
+"other components of JBossTS share the same <filename>jacorb.properties</"
+"filename> file, then you should use the <filename>com.arjuna.ats.jts."
+"recoveryManagerPort</filename> and <filename>com.arjuna.ats.jts."
+"recoveryManagerAddress</filename> properties."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:603
+#, no-c-format
+msgid "Initializing JBossTS applications"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:604
+#, no-c-format
+msgid ""
+"It is important that JBossTS is correctly initialized prior to any "
+"application object being created. In order to guarantee this, the programmer "
+"should use the <methodname>ORB_init</methodname> and <methodname>create_POA</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:609
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr "Errores y excepciones"
+
+#. Tag: para
+#: Chapter.xml:610
+#, 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 ""
+"En esta sección vamos a cubrir los tipos de errores y excepciones que se "
+"pueden presentar o reportar durante una aplicación transaccional y daremos "
+"indicaciones probables de sus causas."
+
+#. Tag: para
+#: Chapter.xml:613
+#, 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 ""
+"NO_MEMORY: la aplication no tiene más memoria (presenta un "
+"<classname>OutOfMemoryError</classname>) y JBoss Transactions ha intentado "
+"realizar alguna limpieza (ejecutando el colector de basura) antes de volver "
+"a presentar la excepción. Probablemente este es un problema transitorio y "
+"con volver a intentar la invocación debe ser suficiente."
+
+#. Tag: para
+#: Chapter.xml:616
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: ha occurrido un error lo cual "
+"significa que el sistema de transacciones se debe apagar. Antes de que este "
+"error se presente el servicio de transacciones se asegurará de que todas las "
+"transacciones ejecutándose se hayan deshecho. Si lo alcanza, la aplicación "
+"debe poner todo en orden y termina. Si se intenta hacer más cosas entonces "
+"la consistencia de la aplicación se puede llegar a violar."
+
+#. Tag: para
+#: Chapter.xml:619
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: se ha intentado utilizar el "
+"servicio de transacciones de una manera inconsistente con la licencia "
+"actual. El servicio de transacciones no permitirá progresar más alla para "
+"transacciones existentes o nuevas. "
+
+#. Tag: para
+#: Chapter.xml:622
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: un error ocurrió mientras "
+"el servicio de transacciones intentaba utilizar el almacenamiento de "
+"objectos. No es posible avanzar más allá."
+
+#. Tag: para
+#: Chapter.xml:625
+#, 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 ""
+"Las advertencias del almacenamiento de objetos sobre problemas de acceso en "
+"estados pueden ocurrir durante la ejecución normal de recuperación de un "
+"sistema que se ha colgado. Este es el resultado de múltiples intentos "
+"simultáneos para realizar la recuperación en la misma transacción. Se puede "
+"ignorar de manera segura."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Feedback.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Feedback.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Feedback.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,13 +1,13 @@
-# translation of Feedback.po to
+# translation of Preface.po to
# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
msgid ""
msgstr ""
-"Project-Id-Version: Feedback\n"
+"Project-Id-Version: Preface\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-16 13:42+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-20 11:30+1000\n"
"Last-Translator: Angela Garcia\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -34,7 +34,12 @@
"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 ""
-"Si encuentra algún error de ortografía en este manual o si se le ocurre una manera de mejorar este manual ¡nos encantaría escuchar sus ideas! Llene un reporte en <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> con referencia al Producto: JBoss Enterprise Application Platform, Versión: "
-"<replaceable><version></replaceable>, Componente: <emphasis>Doc</"
-"emphasis>. Si tiene alguna sugerencia para mejorar la documentación trate de ser lo más especifico posible. Si encuentra un error, incluya el número de la sección y algo del contexto para que lo podamos identificar fácilmente. "
-
+"Si encuentra algún error de ortografía en este manual o si se le ocurre una "
+"manera de mejorar este manual ¡nos encantaría escuchar sus ideas! Llene un "
+"reporte en <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</"
+"ulink> con referencia al Producto: JBoss Enterprise Application Platform, "
+"Versión: <replaceable><version></replaceable>, Componente: "
+"<emphasis>Doc</emphasis>. Si tiene alguna sugerencia para mejorar la "
+"documentación trate de ser lo más especifico posible. Si encuentra un error, "
+"incluya el número de la sección y algo del contexto para que lo podamos "
+"identificar fácilmente. "
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Preface.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Preface.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
"PO-Revision-Date: 2008-06-20 11:30+1000\n"
"Last-Translator: Angela Garcia\n"
"Language-Team: <en at li.org>\n"
@@ -34,8 +34,8 @@
"The Administration Guide contains information on how to administer JBoss "
"Transactions API 4.2.3."
msgstr ""
-"El manual de administración contiene información sobre cómo administrar JBoss "
-"Transactions API 4.2.3."
+"El manual de administración contiene información sobre cómo administrar "
+"JBoss Transactions API 4.2.3."
#. Tag: title
#: Preface.xml:17
@@ -49,7 +49,9 @@
msgid ""
"This guide is most relevant to engineers who are responsible for "
"administration of JBoss Transactions API 4.2.3 installations."
-msgstr "Este manual es relevante para aquellos ingenieros responsables de la administración de la instalación de JBoss Transactions API 4.2.3. "
+msgstr ""
+"Este manual es relevante para aquellos ingenieros responsables de la "
+"administración de la instalación de JBoss Transactions API 4.2.3. "
#. Tag: title
#: Preface.xml:21
@@ -65,7 +67,12 @@
"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 "Con el fin de administrar JBoss Transactions primero es necesario comprender que este depende de ArjunaCore para muchas de las funcionalidades relacionadas con las transacciones. Por lo tanto es importante leer el manual de administración de ArjunaCore antes de intentar el administrar JBoss Transactions."
+msgstr ""
+"Con el fin de administrar JBoss Transactions primero es necesario comprender "
+"que este depende de ArjunaCore para muchas de las funcionalidades "
+"relacionadas con las transacciones. Por lo tanto es importante leer el "
+"manual de administración de ArjunaCore antes de intentar el administrar "
+"JBoss Transactions."
#. Tag: title
#: Preface.xml:25
@@ -88,8 +95,9 @@
"pure local or remote (allowing distributed transactions)."
msgstr ""
"Capítulo 1, Administración de JBoss Transactions: describe cómo administrar "
-"JBoss Transactions, principalmente seleccionando la variante de la implementación JTA: "
-"puramente local o remota (permitiendo transacciones distribuidas)."
+"JBoss Transactions, principalmente seleccionando la variante de la "
+"implementación JTA: puramente local o remota (permitiendo transacciones "
+"distribuidas)."
#. Tag: title
#: Preface.xml:34
@@ -104,8 +112,8 @@
"In addition to this guide, the following guides are available in the JBoss "
"Transactions API 4.2.3 documentation set:"
msgstr ""
-"Además de este manual, los siguientes manuales se encuentran disponibles en el grupo de documentación de JBoss "
-"Transactions API 4.2.3: "
+"Además de este manual, los siguientes manuales se encuentran disponibles en "
+"el grupo de documentación de JBoss Transactions API 4.2.3: "
#. Tag: para
#: Preface.xml:38
@@ -113,7 +121,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
"information about JBoss Transactions API 4.2.3."
-msgstr "Notas de lanzamiento de JBoss Transactions API 4.2.3: Proporciona información de última hora con relación a JBoss Transactions API 4.2.3."
+msgstr ""
+"Notas de lanzamiento de JBoss Transactions API 4.2.3: Proporciona "
+"información de última hora con relación a JBoss Transactions API 4.2.3."
#. Tag: para
#: Preface.xml:41
@@ -121,7 +131,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
"instructions for installing JBoss Transactions API 4.2.3."
-msgstr "Manual de instalación de JBoss Transactions API 4.2.3: Este manual proporciona instrucciones para instalar JBoss Transactions API 4.2.3."
+msgstr ""
+"Manual de instalación de JBoss Transactions API 4.2.3: Este manual "
+"proporciona instrucciones para instalar JBoss Transactions API 4.2.3."
#. Tag: para
#: Preface.xml:44
@@ -129,5 +141,6 @@
msgid ""
"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
"writing applications."
-msgstr "Manual del programador de JBoss Transactions API 4.2.3: Proporciona información para escribir aplicaciones."
-
+msgstr ""
+"Manual del programador de JBoss Transactions API 4.2.3: Proporciona "
+"información para escribir aplicaciones."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Revision_History.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/es-ES/Revision_History.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,13 +1,13 @@
-# translation of Revision_History.po to
+# translation of Preface.po to
# Language es-ES translations for JBoss_Transactions_Administrators_Guide package.
# Automatically generated, 2008.
#
msgid ""
msgstr ""
-"Project-Id-Version: Revision_History\n"
+"Project-Id-Version: Preface\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-16 13:43+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-20 11:30+1000\n"
"Last-Translator: Angela Garcia\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -15,9 +15,14 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "Historial de revisiones"
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
msgstr "<firstname></firstname> <surname></surname> <email></email>"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Author_Group.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Author_Group.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Author_Group.po to French
+# translation of Preface.po to French
# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Corina Roe <croe at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: Preface\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-30 12:47+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-07-07 10:52+1000\n"
"Last-Translator: Corina Roe <croe at redhat.com>\n"
"Language-Team: French <i18 at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -16,21 +16,8 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
-#. Tag: corpauthor
-#: Author_Group.xml:6
-#, no-c-format
-msgid "FF0000 Headgear Documentation Group"
-msgstr "Groupe de documentation FF0000 Headgear"
-
#. 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 ""
-"<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>"
-
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Book_Info.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Book_Info.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Book_Info.po to French
+# translation of Preface.po to French
# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Corina Roe <croe at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: Preface\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-30 12:53+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-07-07 10:52+1000\n"
"Last-Translator: Corina Roe <croe at redhat.com>\n"
"Language-Team: French <i18 at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -19,26 +19,27 @@
#. Tag: title
#: Book_Info.xml:6
#, no-c-format
-msgid "JBoss Transactions API 4.2.3 Administration Guide"
-msgstr "Guide d'administration de transactions JBoss API 4.2.3"
+msgid "JBoss Transactions Administrators Guide"
+msgstr "Guide des administrateurs de transactions JBoss"
#. Tag: subtitle
#: Book_Info.xml:10
-#, no-c-format
-msgid "JBoss Enterprise Application Platform"
-msgstr "JBoss Enterprise Application Platform"
+#, fuzzy, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 5.0"
+msgstr "à utiliser avec JBoss Enterprise Application Platform 4.3"
#. Tag: para
-#: Book_Info.xml:13
+#: Book_Info.xml:15
#, no-c-format
msgid ""
"This book is the JBoss Enterprise Application Platform edition of the JBoss "
"Transactions Administrators Guide"
-msgstr "Cet ouvrage est l'édition de JBoss Enterprise Application Platform du Guide des administrateurs de transactions JBoss"
+msgstr ""
+"Cet ouvrage est l'édition de JBoss Enterprise Application Platform du Guide "
+"des administrateurs de transactions JBoss"
#. Tag: holder
-#: Book_Info.xml:22
+#: Book_Info.xml:24
#, no-c-format
msgid "&HOLDER;"
msgstr "&HOLDER;"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Chapter.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Chapter.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Chapter.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Chapter.po to French
+# translation of Preface.po to French
# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Corina Roe <croe at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Chapter\n"
+"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-06-05 22:49+0000\n"
-"PO-Revision-Date: 2008-07-08 09:38+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-07-07 10:52+1000\n"
"Last-Translator: Corina Roe <croe at redhat.com>\n"
"Language-Team: French <i18 at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -30,8 +30,9 @@
"little continuous administration needed for the JBoss Transactions software. "
"There are a few points however, that should be made:"
msgstr ""
-"A part veiller à ce que le système soit exécuté normalement, on n'a pas besoin d'une administration continue pour le logiciel JBoss Transactions. "
-"On doit, cependant, noter les points suivants:"
+"A part veiller à ce que le système soit exécuté normalement, on n'a pas "
+"besoin d'une administration continue pour le logiciel JBoss Transactions. On "
+"doit, cependant, noter les points suivants:"
#. Tag: para
#: Chapter.xml:10
@@ -44,7 +45,15 @@
"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 "L'implémentation actuelle du système JBoss TA n'offre aucune protection des données et pas de sécurité. Les objets stockées dans la base de données d'objets JBoss Transactions, sont (typiquement) la propriété de l'utilisateur qui a exécuté l'application qui les a créés. Les installations Object Manager et Object Store ne tentent pas d'appliquer la protection, même si limitée, offerte par Unix/Windows. Il n'y a pas de vérification des ID du groupe ou des utilisateurs au sujet de l'accès aux objets, que ce soit pour lecture ou pour écriture."
+msgstr ""
+"L'implémentation actuelle du système JBoss TA n'offre aucune protection des "
+"données et pas de sécurité. Les objets stockées dans la base de données "
+"d'objets JBoss Transactions, sont (typiquement) la propriété de "
+"l'utilisateur qui a exécuté l'application qui les a créés. Les installations "
+"Object Manager et Object Store ne tentent pas d'appliquer la protection, "
+"même si limitée, offerte par Unix/Windows. Il n'y a pas de vérification des "
+"ID du groupe ou des utilisateurs au sujet de l'accès aux objets, que ce soit "
+"pour lecture ou pour écriture."
#. Tag: para
#: Chapter.xml:13
@@ -61,7 +70,20 @@
"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 "Les objets persistants créés dans la base de données Objet Store demeurent à cet endroit à moins que la méthode de destruction du StateManager soit invoquée sur l'objet ou bien que quelque programme d'application ne les efface explicitement. Cela signifie que l'Object Store accumule des informations superflues (issues principalement des phases de test ou de développement d'applications). A présent, nous ne possédons pas d'installation pour la récupération de ces informations superflues. De plus, nous n'avons pas résolu le problème des références ambigues. C'est à dire qu'un objet persistant, A, pourrait avoir hébergé un Uid pour un autre objet persistant, B, sous une forme de représentation passive sur un disque. Rien ne peut empêcher une application d'effacer B, même si A contient toujours une référence qui s'y rapporte. Quand A est activé par la suite, et tente d'accéder à B, une erreur d'exécution surgit."
+msgstr ""
+"Les objets persistants créés dans la base de données Objet Store demeurent à "
+"cet endroit à moins que la méthode de destruction du StateManager soit "
+"invoquée sur l'objet ou bien que quelque programme d'application ne les "
+"efface explicitement. Cela signifie que l'Object Store accumule des "
+"informations superflues (issues principalement des phases de test ou de "
+"développement d'applications). A présent, nous ne possédons pas "
+"d'installation pour la récupération de ces informations superflues. De plus, "
+"nous n'avons pas résolu le problème des références ambigues. C'est à dire "
+"qu'un objet persistant, A, pourrait avoir hébergé un Uid pour un autre objet "
+"persistant, B, sous une forme de représentation passive sur un disque. Rien "
+"ne peut empêcher une application d'effacer B, même si A contient toujours "
+"une référence qui s'y rapporte. Quand A est activé par la suite, et tente "
+"d'accéder à B, une erreur d'exécution surgit."
#. Tag: para
#: Chapter.xml:16
@@ -75,22 +97,96 @@
"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 "Il n'existe actuellement pas de prise en charge pour le contrôle de version d'objets ou de la reconfiguration des bases de données dans le cas de changements de structure de classe. Il s'agit d'un domaine de recherche complexe que nous n'avons pas encore traité. A présent, si vous changez la définition d'une classe d'objets persistants, vous serez complètement responsable de veiller à ce que les instances existantes des objets de l'Object Store soient convertis à la nouvelle représentation. Le logiciel des transactions JBoss ne peut ni détecter, ni corriger les références vers des anciens états d'objet par des nouvelles versions d'opérations et vice versa."
+msgstr ""
+"Il n'existe actuellement pas de prise en charge pour le contrôle de version "
+"d'objets ou de la reconfiguration des bases de données dans le cas de "
+"changements de structure de classe. Il s'agit d'un domaine de recherche "
+"complexe que nous n'avons pas encore traité. A présent, si vous changez la "
+"définition d'une classe d'objets persistants, vous serez complètement "
+"responsable de veiller à ce que les instances existantes des objets de "
+"l'Object Store soient convertis à la nouvelle représentation. Le logiciel "
+"des transactions JBoss ne peut ni détecter, ni corriger les références vers "
+"des anciens états d'objet par des nouvelles versions d'opérations et vice "
+"versa."
#. Tag: para
-#: Chapter.xml:19
+#: Chapter.xml:19 Chapter.xml:62
#, no-c-format
-msgid "Object store management is critically important to the transaction service."
-msgstr "La gestion des bases de données Object Store est d'une importance critique pour le service de transaction."
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+"La gestion des bases de données Object Store est d'une importance critique "
+"pour le service de transaction."
#. Tag: title
#: Chapter.xml:24
#, no-c-format
+msgid "Starting and Stopping the transaction manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"By default the transaction manager starts up in an active state such that "
+"new transactions can be created immediately. If you wish to have more "
+"control over this it is possible to set the <property>com.arjuna.ats.arjuna."
+"coordinator.startDisabled</property> configuration option to <literal>YES</"
+"literal>, in which case no transactions can be created until the transaction "
+"manager is enabled (via a call to <methodname>TxControl.enable</methodname>)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:28
+#, no-c-format
+msgid ""
+"It is possible to stop the creation of new transactions at any time by "
+"calling <methodname>TxControl.disable</methodname>. Transactions that are "
+"currently executing will not be affected. By default recovery will be "
+"allowed to continue and the transaction system will still be available to "
+"manage recovery requests from other instances in a distributed environment. "
+"(See the Failure Recovery Guide for further details). However, if you wish "
+"to disable recovery as well as remove any resources it maintains, then you "
+"can pass true to <methodname>TxControl.disable</methodname>; the default is "
+"to use <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"If you wish to shut the system down completely then it may also be necessary "
+"to terminate the background transaction reaper (see the Programmers Guide "
+"for information about what the reaper does.) In order to do this you may "
+"want to first prevent the creation of new transactions (if you are not "
+"creating transactions with timeouts then this step is not necessary) using "
+"<methodname>TxControl.disable</methodname>. Then you should call "
+"<methodname>TransactionReaper.terminate</methodname>. This method takes a "
+"boolean parameter: if true then the method will wait for the normal timeout "
+"periods associated with any transactions to expire before terminating the "
+"transactions; if false then transactions will be forced to terminate "
+"(rollback or have their outcome set such that they can only ever rollback) "
+"immediately."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"If you intent to restart the recovery manager later after having terminated "
+"it then you <emphasis>must</emphasis> use the <methodname>terminate</"
+"methodname> method with <property>asynchronous behavior</property> set to "
+"<literal>false</literal> when shutting down the recovery manager."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:40
+#, no-c-format
msgid "ObjectStore management"
msgstr "Gestion d'ObjectStore"
#. Tag: para
-#: Chapter.xml:25
+#: Chapter.xml:41
#, no-c-format
msgid ""
"Within the transaction service installation, the object store is updated "
@@ -105,26 +201,789 @@
"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 "Dans l'installation du service de transactions, la base de données objet est mise à jour régulièrement au fur et à mesure des transactions, ou quand des objets transactionnels pour Java sont utilisés. Dans un environnement qui ne connaît pas de mises en échec, les seuls états d'objet qui doivent résider dans la base de donnée-objets, sont ceux qui représentent des objets créés dans Objets Transactionnels pour Java API. Cependant, en cas d'échecs, les journaux des transactions doivent demeurer dans la mémoire objet jusqu'à ce que les moyens de recouvrement en cas de crash résolvent les transactions qu'ils représentent. Ainsi, il est très important que les contenus des bases de données-objet ne soient pas supprimées facilement, car il serait impossible de résoudre les opérations précaires. De plus, si plusieurs utilisateurs partagent la même base de donnée-objet, il faut qu'ils le réalisent et qu'ils n'effacent pas les contenus Objet Store,!
assumant qu'il s'agisse d'une ressource exclusive."
+msgstr ""
+"Dans l'installation du service de transactions, la base de données objet est "
+"mise à jour régulièrement au fur et à mesure des transactions, ou quand des "
+"objets transactionnels pour Java sont utilisés. Dans un environnement qui ne "
+"connaît pas de mises en échec, les seuls états d'objet qui doivent résider "
+"dans la base de donnée-objets, sont ceux qui représentent des objets créés "
+"dans Objets Transactionnels pour Java API. Cependant, en cas d'échecs, les "
+"journaux des transactions doivent demeurer dans la mémoire objet jusqu'à ce "
+"que les moyens de recouvrement en cas de crash résolvent les transactions "
+"qu'ils représentent. Ainsi, il est très important que les contenus des bases "
+"de données-objet ne soient pas supprimées facilement, car il serait "
+"impossible de résoudre les opérations précaires. De plus, si plusieurs "
+"utilisateurs partagent la même base de donnée-objet, il faut qu'ils le "
+"réalisent et qu'ils n'effacent pas les contenus Objet Store, assumant qu'il "
+"s'agisse d'une ressource exclusive."
+#. Tag: para
+#: Chapter.xml:42
+#, fuzzy, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBossTS software. There are "
+"a few points however, that should be made:"
+msgstr ""
+"A part veiller à ce que le système soit exécuté normalement, on n'a pas "
+"besoin d'une administration continue pour le logiciel JBoss Transactions. On "
+"doit, cependant, noter les points suivants:"
+
+#. Tag: para
+#: Chapter.xml:47
+#, fuzzy, no-c-format
+msgid ""
+"The present implementation of the JBossTS system provides no security or "
+"protection for data. It is recommended that the objects stored in the "
+"JBossTS are owned by user arjuna. The Object Store and Object Manager "
+"facilities make no attempt to enforce even the limited form of protection "
+"that Unix and Windows provides. There is no checking of user or group IDs on "
+"access to objects for either reading or writing."
+msgstr ""
+"L'implémentation actuelle du système JBoss TA n'offre aucune protection des "
+"données et pas de sécurité. Les objets stockées dans la base de données "
+"d'objets JBoss Transactions, sont (typiquement) la propriété de "
+"l'utilisateur qui a exécuté l'application qui les a créés. Les installations "
+"Object Manager et Object Store ne tentent pas d'appliquer la protection, "
+"même si limitée, offerte par Unix/Windows. Il n'y a pas de vérification des "
+"ID du groupe ou des utilisateurs au sujet de l'accès aux objets, que ce soit "
+"pour lecture ou pour écriture."
+
+#. Tag: para
+#: Chapter.xml:52
+#, fuzzy, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> 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 ""
+"Les objets persistants créés dans la base de données Objet Store demeurent à "
+"cet endroit à moins que la méthode de destruction du StateManager soit "
+"invoquée sur l'objet ou bien que quelque programme d'application ne les "
+"efface explicitement. Cela signifie que l'Object Store accumule des "
+"informations superflues (issues principalement des phases de test ou de "
+"développement d'applications). A présent, nous ne possédons pas "
+"d'installation pour la récupération de ces informations superflues. De plus, "
+"nous n'avons pas résolu le problème des références ambigues. C'est à dire "
+"qu'un objet persistant, A, pourrait avoir hébergé un Uid pour un autre objet "
+"persistant, B, sous une forme de représentation passive sur un disque. Rien "
+"ne peut empêcher une application d'effacer B, même si A contient toujours "
+"une référence qui s'y rapporte. Quand A est activé par la suite, et tente "
+"d'accéder à B, une erreur d'exécution surgit."
+
+#. Tag: para
+#: Chapter.xml:57
+#, fuzzy, 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 JBossTS software can neither detect "
+"nor correct references to old object state by new operation versions or vice "
+"versa."
+msgstr ""
+"Il n'existe actuellement pas de prise en charge pour le contrôle de version "
+"d'objets ou de la reconfiguration des bases de données dans le cas de "
+"changements de structure de classe. Il s'agit d'un domaine de recherche "
+"complexe que nous n'avons pas encore traité. A présent, si vous changez la "
+"définition d'une classe d'objets persistants, vous serez complètement "
+"responsable de veiller à ce que les instances existantes des objets de "
+"l'Object Store soient convertis à la nouvelle représentation. Le logiciel "
+"des transactions JBoss ne peut ni détecter, ni corriger les références vers "
+"des anciens états d'objet par des nouvelles versions d'opérations et vice "
+"versa."
+
#. Tag: title
-#: Chapter.xml:28
+#: Chapter.xml:70
#, no-c-format
+msgid "OTS and J2EE Transaction service management"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:72
+#, no-c-format
+msgid "Starting the run-time system"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:73
+#, no-c-format
+msgid ""
+"The JBossTS run-time support consists of run-time packages and the OTS "
+"transaction manager server. By default JBossTS does not use a separate "
+"transaction manager server: transaction managers are co-located with each "
+"application process to improve performance and improve application fault-"
+"tolerance (the application is no longer dependant upon another service in "
+"order to function correctly)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:76
+#, no-c-format
+msgid ""
+"When running applications which require a separate transaction manager, you "
+"must set the <varname>com.arjuna.ats.jts.transactionManager</varname> "
+"environment variable to have the value <literal>yes</literal>. The system "
+"will then locate the transaction manager server in a manner specific to the "
+"ORB being used. The server can be located in a number of ways: by being "
+"registered with a name server, added to the ORB’s initial references, via a "
+"JBossTS specific references file, or by the ORB’s specific location "
+"mechanism (if applicable)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:79
+#, no-c-format
+msgid ""
+"It is possible to override the default registration mechanism by using the "
+"<varname>com.arjuna.orbportability.resolveService</varname> environment "
+"variable. This can have one of the following values:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"<literal>CONFIGURATION_FILE</literal>: the default, this causes the system "
+"to use the <filename>CosServices.cfg</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:89
+#, no-c-format
+msgid ""
+"<literal>NAME_SERVICE</literal>: JBossTS will attempt to use a name service "
+"to register the transaction factory. If this is not supported, an exception "
+"will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:94
+#, no-c-format
+msgid ""
+"<literal>BIND_CONNECT</literal>: JBossTS will use the ORB-specific bind "
+"mechanism. If this is not supported, an exception will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid ""
+"<literal>RESOLVE_INITIAL_REFERENCES</literal>: JBossTS will attempt to "
+"register the transaction service with the ORBs initial service references."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid ""
+"This may not be supported on all ORBs. An exception will be thrown in that "
+"case and another option will have to be used."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:110
+#, no-c-format
+msgid "<title>OTS configuration file</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid ""
+"Similar to the resolve_initial_references, JBossTS supports an initial "
+"reference file where references for specific services can be stored and used "
+"at runtime. The file, CosServices.cfg, consists of two columns: the service "
+"name (in the case of the OTS server TransactionService) and the IOR, "
+"separated by a single space. CosServices.cfg normally resides in the etc "
+"directory of the JBossTS installation; the actual location is determined at "
+"runtime by searching the CLASSPATH for an old copy of the file resident "
+"within an etc directory, or, if one is not found, the location of the "
+"TransactionService properties file directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:115
+#, no-c-format
+msgid ""
+"The OTS server will automatically register itself in this file (creating it "
+"if necessary) if this option is being used. Stale information is also "
+"automatically removed. Machines which wish to share the same transaction "
+"server should have access to (or a copy of) this file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:118
+#, no-c-format
+msgid ""
+"The name and location of the file can be overridden using the <property>com."
+"arjuna.orbportability.initialReferencesFile</property> and <property>com."
+"arjuna.orbportability.initialReferencesRoot</property> property variables, "
+"respectively. It is recommended that the <property>com.arjuna.orbportability."
+"initialReferencesRoot</property> variable is set. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Chapter.xml:121
+#, no-c-format
+msgid ""
+"com.arjuna.orbportability.initialReferencesFile=myFile\n"
+"com.arjuna.orbportability.initialReferencesRoot=c:\\\\temp"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:123
+#, no-c-format
+msgid "<title>Name Service</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:124
+#, no-c-format
+msgid ""
+"If the ORB you are using supports a name service, and JBossTS has been "
+"configured to use it, then the transaction manager will automatically be "
+"registered with it. There is no further work required. This option is not "
+"used for JacORB"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:129
+#, no-c-format
+msgid "<title>resolve_initial_references</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:130
+#, no-c-format
+msgid "Currently this option is only supported for JacORB."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:135
+#, no-c-format
+msgid "Resolution service table"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:136
+#, no-c-format
+msgid ""
+"The following table summarizes the different ways in which the OTS "
+"transaction manager may be located on specific ORBs:"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:141
+#, no-c-format
+msgid "Locating the OTS transaction manager server"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:145
+#, no-c-format
+msgid "Resolution Mechanism"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:146
+#, no-c-format
+msgid "<entry>ORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:151
+#, no-c-format
+msgid "<entry>OTS configuration file</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:152
+#, no-c-format
+msgid "All available ORBs"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:155
+#, no-c-format
+msgid "<entry>Name Service</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:156 Chapter.xml:160
+#, no-c-format
+msgid "<entry>JacORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:159
+#, no-c-format
+msgid "<entry>resolve_initial_references</entry>"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:167
+#, no-c-format
+msgid "XA specific management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid ""
+"Each XA Xid that JBossTS creates must have a unique node identifier encoded "
+"within it and JBossTS will only recover transactions and states that match a "
+"specified node identifier. The node identifier to use should be provided to "
+"JBossTS via the <property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property> "
+"property. You must make sure this value is unique across your JBossTS "
+"instances. If you do not provide a value, then JBossTS will fabricate one "
+"and report the value via the logging infrastructure."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"When running XA recovery it is therefore necessary to tell JBossTS which "
+"types of Xid it can recover. Each Xid that JBossTS creates has a unique node "
+"identifier encoded within it and JBossTS will only recover transactions and "
+"states that match a specified node identifier. The node identifier to use "
+"should be provided to JBossTS via a property that starts with the name "
+"<property>com.arjuna.ats.jta.xaRecoveryNode</property>; multiple values may "
+"be provided. A value of <code>*</code> will force JBossTS to recover (and "
+"possibly rollback) all transactions irrespective of their node identifier "
+"and should be used with caution."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:177
+#, no-c-format
+msgid "Web Service Transaction service management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:178
+#, no-c-format
+msgid ""
+"The basic building blocks of a transactional Web Services application are "
+"the application itself, the Web services that the application consumes, the "
+"Transaction Manager, and the transaction participants which support those "
+"Web services. Though it is unlikely in a typical deployment that a single "
+"developer will be expected to support all of these roles, the concepts are "
+"presented here so that a global model can be visualized. It will often be "
+"the case that developers will produce services, or applications that consume "
+"services, whilst system administrators will run the transaction-management "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:182
+#, fuzzy, no-c-format
+msgid "The Transaction Manager"
+msgstr "Le gestionnaire de recouvrement"
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"The transaction manager is a Web service which coordinates JBossTS "
+"transactions. It is the only software component in JBossTS that is meant to "
+"be run directly as a network service, rather than to support end-user code. "
+"The transaction manager runs as a JAXM request/response Web service."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:187
+#, no-c-format
+msgid ""
+"When starting up an application server instance that has JBossTS deployed "
+"within it, you may see various <emphasis>error</emphasis> messages in the "
+"console or log. For example <code>16:53:38,850 ERROR [STDERR] Message "
+"Listener Service: started, message listener jndi name activationcoordinator</"
+"code>. These are for information purposes only and are not actual errors."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:192
+#, fuzzy, no-c-format
+msgid "Configuring the Transaction Manager"
+msgstr "Configurer le gestionnaire de recouvrement"
+
+#. Tag: para
+#: Chapter.xml:193
+#, no-c-format
+msgid ""
+"The Transaction Manager and related infrastructure are configured by means "
+"of properties files: <filename>wscf.xml</filename>, <filename>wst.xml</"
+"filename> and <filename>wstx.xml</filename>. These files can be found in the "
+"conf directory and are used for configuring the demo application and the "
+"standalone module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"For the most part the default values in these files need not be altered. "
+"However, the <property>com.arjuna.ats.arjuna.objectstore.objectStoreDir</"
+"property> property determines the location of the persistent store used to "
+"record transaction state. The default value of <filename>C:/temp/"
+"ObjectStore</filename> should be changed to a value appropriate to your "
+"system. For production environments this directory should reside on fault "
+"tolerant media such as a RAID array."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"When a standalone coordinator is being used by an application it is "
+"necessary to enable and modify two further properties in <filename>wstx.xml</"
+"filename>, <property>com.arjuna.mw.wst.coordinatorURL</property> and "
+"<property>com.arjuna.mw.wst.terminatorURL</property>. These contain the URLs "
+"necessary for the client application to contact the standalone coordinator "
+"and should be configured with the correct hostname and port of the "
+"standalone coordinator."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"JBossTS is highly modular so in order to allow for flexible deployment of "
+"individual components, the same property values are sometimes required to "
+"appear in more than one configuration file. For the majority of "
+"configurations, you should maintain consistent values for properties that "
+"are defined in more than one file."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:207
+#, no-c-format
+msgid "Deploying the Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"The JBossTS Web Service Transaction Manager component consists of a number "
+"of JAR files containing the application’s class files, plus Web service "
+"(WAR) files which expose the necessary services. Programmers will typically "
+"include all these components in their application EAR file during "
+"application development, simplifying deployment of the transaction "
+"infrastructure. For production usage the Transaction Manager may be "
+"installed as an application in its own right, allowing for centralized "
+"configuration and management at the server level, independent of specific "
+"applications. The demonstration application shipped with JBossTS provides a "
+"sample deployment descriptor illustrating how the Transaction Manager "
+"components can be included in an application."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"JBossTS 4.0 uses fixed endpoints for its underlying protocol communication. "
+"Therefore, problems may arise if multiple applications using JBossTS are "
+"deployed to the same server concurrently. If you wish to deploy several "
+"transactional applications in the same server, the Transaction Manger must "
+"be deployed as a separate application and not embedded within the deployment "
+"of individual applications."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid ""
+"The coordinator directory in the JBossTS installation has been provided to "
+"assist in the configuration and deployment of a stand-alone transaction "
+"manager. In order to use this, you must:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:220
+#, fuzzy, no-c-format
+msgid "Have JBoss Enterprise Application Platform 5 installed"
+msgstr "à utiliser avec JBoss Enterprise Application Platform 4.3"
+
+#. Tag: para
+#: Chapter.xml:225
+#, no-c-format
+msgid "Install ant 1.4 or later."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:231
+#, no-c-format
+msgid ""
+"It is important that a separate application server installation be used from "
+"the one that clients and services are deployed into since otherwise "
+"conflicts may occur between the various JBossTS components."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:235
+#, no-c-format
+msgid ""
+"You must then edit the build.xml included with coordinator to point to the "
+"application server installation where the transaction coordinator will be "
+"deployed and the location of the JBossTS installation. The files "
+"<filename>ws-c_jaxm_web-app.xml</filename> and <filename>ws-t_jaxm_web-app."
+"xml</filename> in the <filename>dd</filename> directory of coordinator are "
+"the deployment descriptors for the WS-C and WS-T WAR files. These files "
+"contain templated URLs. During the build phase, ant will substitute the "
+"hostname and port values you specify in the <filename>build.xml</filename> "
+"into these files."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:238
+#, no-c-format
+msgid ""
+"Run <code>ant</code>, with <code>target deploy-weblogic</code>, <code>deploy-"
+"jboss</code> or <code>deploy-webmethods</code>, to create and deploy a new "
+"coordinator into the correct application server installation."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:241
+#, no-c-format
+msgid ""
+"Now all you need to do is point your client at the required coordinator. To "
+"do this, generate the demo application specifying the port and hostname of "
+"the coordinator."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:245
+#, no-c-format
+msgid "Deployment descriptors"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:246
+#, no-c-format
+msgid ""
+"In general, it should not be necessary to change the contents of the various "
+"deployment descriptors used by JBossTS. However, if you do need to modify "
+"them they are all included in the coordinator module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:250
+#, no-c-format
+msgid ""
+"Not all JBossTS components have ready access to the information in the "
+"deployment descriptors. Therefore, if you modify the JNDI names used by any "
+"of the WS-C or WS-T deployment descriptors you may need to inform other "
+"JBossTS components at runtime. This can be accomplished by setting an "
+"appropriate property in the <filename>wstx.xml</filename> configuration file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:253
+#, no-c-format
+msgid ""
+"The following table shows the default JNDI name used by the deployment "
+"descriptors and the corresponding property to set if the default value is "
+"changed."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:257
+#, no-c-format
+msgid "Deployment descriptor values and properties"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:261
+#, no-c-format
+msgid "JNDI Name"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:262
+#, no-c-format
+msgid "Property"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:267
+#, no-c-format
+msgid "Activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:268
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:271
+#, no-c-format
+msgid "Activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:272
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:275
+#, no-c-format
+msgid "Completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:276
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:279
+#, no-c-format
+msgid "Registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:280
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:283
+#, no-c-format
+msgid "durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:284
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:287
+#, no-c-format
+msgid "durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:288
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:291
+#, no-c-format
+msgid "volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:292
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:295
+#, no-c-format
+msgid "volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:296
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:299
+#, no-c-format
+msgid "businessagreementwithparticipantcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:300
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:303
+#, no-c-format
+msgid "businessagreementwithparticipantcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:304
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:307
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:308
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:311
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:312
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccparticipant"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:319
+#, no-c-format
msgid "JBoss Transactions runtime information"
msgstr "Information sur le temps d'exécution JBoss Transactions"
#. Tag: para
-#: Chapter.xml:29
+#: Chapter.xml:320
#, 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 "Chaque module compris dans JBoss Transactions comporte une classe intitulée Info. Ces classes procurent toutes une méthode simple toString qui retourne un document XML, représentant les informations de configuration pour ce module. Donc, par exemple:"
+msgstr ""
+"Chaque module compris dans JBoss Transactions comporte une classe intitulée "
+"Info. Ces classes procurent toutes une méthode simple toString qui retourne "
+"un document XML, représentant les informations de configuration pour ce "
+"module. Donc, par exemple:"
#. Tag: programlisting
-#: Chapter.xml:31
+#: Chapter.xml:322
#, no-c-format
msgid ""
"<module-info name=\"arjuna\">\n"
@@ -158,13 +1017,13 @@
"</module-info>"
#. Tag: title
-#: Chapter.xml:34
+#: Chapter.xml:325
#, no-c-format
msgid "Failure recovery administration"
msgstr "Administration du recouvrement en cas d'échec"
#. Tag: para
-#: Chapter.xml:35
+#: Chapter.xml:326
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions will ensure that "
@@ -178,16 +1037,31 @@
"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 "Le sous-système de recouvrement des transactions JBoss assurera que les résultats d'une transaction soient appliqués uniformément à toutes les ressources affectées par cette transaction, même si aucun des processus d'application ou la machine hôte ne se plantent ou perdent la connexion réseau. Dans un cas de plantage de machine (système) ou d'échec de réseau, le recouvrement n'aura pas lieu si le système ou le réseau ne sont pas restaurés, mais l'application d'origine n'a pas besoin d'être relancée - la responsabilité du recouvrement est déléguée au Gestionnaire de recouvrement (voir ci-dessous). Le recouvrement suite à un échec, repose sur le fait que l'information, à propos de la transaction et les ressources qui y sont attachées, survive l'échec et soit accessible par la suite: cette information est contenue dans ActionStore, qui fait partie d'ObjectStore."
+msgstr ""
+"Le sous-système de recouvrement des transactions JBoss assurera que les "
+"résultats d'une transaction soient appliqués uniformément à toutes les "
+"ressources affectées par cette transaction, même si aucun des processus "
+"d'application ou la machine hôte ne se plantent ou perdent la connexion "
+"réseau. Dans un cas de plantage de machine (système) ou d'échec de réseau, "
+"le recouvrement n'aura pas lieu si le système ou le réseau ne sont pas "
+"restaurés, mais l'application d'origine n'a pas besoin d'être relancée - la "
+"responsabilité du recouvrement est déléguée au Gestionnaire de recouvrement "
+"(voir ci-dessous). Le recouvrement suite à un échec, repose sur le fait que "
+"l'information, à propos de la transaction et les ressources qui y sont "
+"attachées, survive l'échec et soit accessible par la suite: cette "
+"information est contenue dans ActionStore, qui fait partie d'ObjectStore."
#. Tag: para
-#: Chapter.xml:38
+#: Chapter.xml:329
#, no-c-format
-msgid "If the ObjectStore is destroyed or modified, recovery may not be possible."
-msgstr "Si l'ObjectStore est détruit ou modifié, les chances de recouvrement sont compromises."
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+"Si l'ObjectStore est détruit ou modifié, les chances de recouvrement sont "
+"compromises."
#. Tag: para
-#: Chapter.xml:41
+#: Chapter.xml:332
#, no-c-format
msgid ""
"Until the recovery procedures are complete, resources affected by a "
@@ -196,16 +1070,23 @@
"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 "Jusqu'à ce que les procédures de recouvrement soient terminées, les ressources affectées par la transaction en progrès au moment de la mise en échec, peuvent être inaccessibles. Pour les ressources de banques de données, cela peut être rapporté sous forme de tables ou de rangées contenues par \"in-doubt transactions\" (transactions précaires). Pour les TransactionalObjects des ressources Java, toute tentative d'activer l'Objet Transactionnel (tout comme toute tentative d'obtenir un verrou) échouera."
+msgstr ""
+"Jusqu'à ce que les procédures de recouvrement soient terminées, les "
+"ressources affectées par la transaction en progrès au moment de la mise en "
+"échec, peuvent être inaccessibles. Pour les ressources de banques de "
+"données, cela peut être rapporté sous forme de tables ou de rangées "
+"contenues par \"in-doubt transactions\" (transactions précaires). Pour les "
+"TransactionalObjects des ressources Java, toute tentative d'activer l'Objet "
+"Transactionnel (tout comme toute tentative d'obtenir un verrou) échouera."
#. Tag: title
-#: Chapter.xml:43
+#: Chapter.xml:334
#, no-c-format
msgid "The Recovery Manager"
msgstr "Le gestionnaire de recouvrement"
#. Tag: para
-#: Chapter.xml:44
+#: Chapter.xml:335
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions requires that the stand-"
@@ -216,37 +1097,46 @@
"RecoveryManager</classname>. To start the Recovery Manager issue the "
"following command:"
msgstr ""
-"Le sous-système de recouvrement, en cas d'échec des transactions JBoss, repose sur le fait que le processus du gestionnaire de recouvrement autonome doit être en cours d'exécution pour chaque ObjectStore (normalement un processus par noeud de réseau exécutant des applications JBoss Transactions). Le fichier du gestionnaire de recouvrement (RecoveryManager) est localisé dans le fichier jar arjunacore situé dans le paquetage <classname>com.arjuna.ats.arjuna.recovery."
-"RecoveryManager</classname>. Pour démarrer le gestionnaire de recouvrement, actionner la commande suivante:"
+"Le sous-système de recouvrement, en cas d'échec des transactions JBoss, "
+"repose sur le fait que le processus du gestionnaire de recouvrement autonome "
+"doit être en cours d'exécution pour chaque ObjectStore (normalement un "
+"processus par noeud de réseau exécutant des applications JBoss "
+"Transactions). Le fichier du gestionnaire de recouvrement (RecoveryManager) "
+"est localisé dans le fichier jar arjunacore situé dans le paquetage "
+"<classname>com.arjuna.ats.arjuna.recovery.RecoveryManager</classname>. Pour "
+"démarrer le gestionnaire de recouvrement, actionner la commande suivante:"
#. Tag: command
-#: Chapter.xml:45
+#: Chapter.xml:336
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
#. Tag: para
-#: Chapter.xml:46
+#: Chapter.xml:337
#, 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 "Si la balise <literal>-test</literal> est utilisée en même temps que le gestionnaire de recouvrement, on verra apparaître un message \"Ready\" (prêt) au moment du démarrage, par ex., "
+msgstr ""
+"Si la balise <literal>-test</literal> est utilisée en même temps que le "
+"gestionnaire de recouvrement, on verra apparaître un message \"Ready"
+"\" (prêt) au moment du démarrage, par ex., "
#. Tag: command
-#: Chapter.xml:47
+#: Chapter.xml:338
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
#. Tag: title
-#: Chapter.xml:50
+#: Chapter.xml:341
#, no-c-format
msgid "Configuring the Recovery Manager"
msgstr "Configurer le gestionnaire de recouvrement"
#. Tag: para
-#: Chapter.xml:51
+#: Chapter.xml:342
#, no-c-format
msgid ""
"The RecoveryManager reads the properties defined in the <filename>arjuna."
@@ -257,11 +1147,17 @@
"in the main TransactionService properties file. Most of the entries are "
"specific to the Recovery Manager."
msgstr ""
-"Le gestionnaire de recouvrement lit les propriétés définies dans le fichier <filename>arjuna."
-"properties</filename> et lit également le fichier de propriété <filename>RecoveryManager.properties</filename>, à partir du même répertoire que celui où il a trouvé dans le fichier des propriétés arjuna. Une saisie de propriété dans le fichier de propriétés du gestionnaire de recouvrement remplacera toute saisie pour cette même propriété dans le fichier de base de propriétés de TransactionService. La plupart des saisies sont spécifiques au gestionnaire de recouvrement."
+"Le gestionnaire de recouvrement lit les propriétés définies dans le fichier "
+"<filename>arjuna.properties</filename> et lit également le fichier de "
+"propriété <filename>RecoveryManager.properties</filename>, à partir du même "
+"répertoire que celui où il a trouvé dans le fichier des propriétés arjuna. "
+"Une saisie de propriété dans le fichier de propriétés du gestionnaire de "
+"recouvrement remplacera toute saisie pour cette même propriété dans le "
+"fichier de base de propriétés de TransactionService. La plupart des saisies "
+"sont spécifiques au gestionnaire de recouvrement."
#. Tag: para
-#: Chapter.xml:52
+#: Chapter.xml:343
#, no-c-format
msgid ""
"A default version of <filename>RecoveryManager.properties</filename> is "
@@ -270,16 +1166,22 @@
"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 "Une version par défaut de <filename>RecoveryManager.properties</filename> est disponible dans la distribution - qui peut être utilisée sans modifications, excepté peut-être les champs de suivi de débogage (voir ci-dessous, Sortie). Le reste de cette section traite des problèmes de configuration des propriétés à des valeurs différentes (en ordre d'apparence dans la version par défaut du fichier)."
+msgstr ""
+"Une version par défaut de <filename>RecoveryManager.properties</filename> "
+"est disponible dans la distribution - qui peut être utilisée sans "
+"modifications, excepté peut-être les champs de suivi de débogage (voir ci-"
+"dessous, Sortie). Le reste de cette section traite des problèmes de "
+"configuration des propriétés à des valeurs différentes (en ordre d'apparence "
+"dans la version par défaut du fichier)."
#. Tag: title
-#: Chapter.xml:54
+#: Chapter.xml:345
#, no-c-format
msgid "Output"
msgstr "Sortie"
#. Tag: para
-#: Chapter.xml:55
+#: Chapter.xml:346
#, no-c-format
msgid ""
"It is likely that installations will want to have some form of output from "
@@ -290,10 +1192,19 @@
"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 "Il est possible que les installations s'attendent à obtenir une certaine forme de sortie du gestionnaire de gestion, en vue de proposer une trace d'enregistrement du genre d'activité de recouvrement qui a eu lieu. Le gestionnaire de recouvrement utilise le mécanisme de traçage de journalisation CLF (Arjuna Common Logging Framework) qui procure un haut niveau d'interface cachant les différences qui existent entre les systèmes de journalisation API comme Jakarta log4j ou JDK 1.4. CLF dirige tout enregistrement par l'infrastructure Apache Commons Logging et la configuration est sensée avoir lieu à travers cette infrastructure."
+msgstr ""
+"Il est possible que les installations s'attendent à obtenir une certaine "
+"forme de sortie du gestionnaire de gestion, en vue de proposer une trace "
+"d'enregistrement du genre d'activité de recouvrement qui a eu lieu. Le "
+"gestionnaire de recouvrement utilise le mécanisme de traçage de "
+"journalisation CLF (Arjuna Common Logging Framework) qui procure un haut "
+"niveau d'interface cachant les différences qui existent entre les systèmes "
+"de journalisation API comme Jakarta log4j ou JDK 1.4. CLF dirige tout "
+"enregistrement par l'infrastructure Apache Commons Logging et la "
+"configuration est sensée avoir lieu à travers cette infrastructure."
#. Tag: para
-#: Chapter.xml:58
+#: Chapter.xml:349
#, no-c-format
msgid ""
"With the CLF applications make logging calls on logger objects. Loggers may "
@@ -303,58 +1214,84 @@
"DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to "
"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
"FATAL."
-msgstr "Pour les applications CLF, effectuez les appels de journalisation sur les objets d'enregistrement chronologique. Les objets d'enregistrement peuvent opérer à différents niveaux et décider s'ils sont intéressés par tel ou tel message. Chaque message de journalisation est associé à un certain niveau de journalisation, qui exprime l'importance et l'urgence d'un message de journalisation. Les configurations possibles sont DEBUG, INFO, WARN, ERROR et FATAL. Des niveaux bien définis sont ordonnés en fonction de leurs valeurs entières relatives comme suit: DEBUG < INFO < WARN < ERROR < FATAL."
+msgstr ""
+"Pour les applications CLF, effectuez les appels de journalisation sur les "
+"objets d'enregistrement chronologique. Les objets d'enregistrement peuvent "
+"opérer à différents niveaux et décider s'ils sont intéressés par tel ou tel "
+"message. Chaque message de journalisation est associé à un certain niveau de "
+"journalisation, qui exprime l'importance et l'urgence d'un message de "
+"journalisation. Les configurations possibles sont DEBUG, INFO, WARN, ERROR "
+"et FATAL. Des niveaux bien définis sont ordonnés en fonction de leurs "
+"valeurs entières relatives comme suit: DEBUG < INFO < WARN < ERROR "
+"< FATAL."
#. Tag: para
-#: Chapter.xml:61
+#: Chapter.xml:352
#, 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 "Le CLF offre une extension pour filtrer les messages de journalisation suivant une granularité plus fine que celle qu'une application puisse définir. Ainsi, lorsqu'un message log est présenté par l'enregistreur chronologique au niveau DEBUG, on peut ajouter des conditions supplémentaires pour déterminer si le message de journalisation est activé ou non."
+msgstr ""
+"Le CLF offre une extension pour filtrer les messages de journalisation "
+"suivant une granularité plus fine que celle qu'une application puisse "
+"définir. Ainsi, lorsqu'un message log est présenté par l'enregistreur "
+"chronologique au niveau DEBUG, on peut ajouter des conditions "
+"supplémentaires pour déterminer si le message de journalisation est activé "
+"ou non."
#. Tag: para
-#: Chapter.xml:67
+#: Chapter.xml:358
#, 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 "Ces conditions s'appliquent si et seulement si le niveau DEBUG est activé et si la demande de journalisation de l'application précise la granularité de débogage."
+msgstr ""
+"Ces conditions s'appliquent si et seulement si le niveau DEBUG est activé et "
+"si la demande de journalisation de l'application précise la granularité de "
+"débogage."
#. Tag: para
-#: Chapter.xml:71
+#: Chapter.xml:362
#, no-c-format
msgid "When enabled, Debugging is filtered conditionally on three variables:"
-msgstr "Une fois activée, la fonction de débogage est filtrée conditionnellement sur trois variables:"
+msgstr ""
+"Une fois activée, la fonction de débogage est filtrée conditionnellement sur "
+"trois variables:"
#. Tag: para
-#: Chapter.xml:74
+#: Chapter.xml:365
#, 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 "Niveau de débogage: c'est quand la demande de journalisation associée à un niveau de débogage est générée par ex. de méthodes de base ou constructeurs."
+msgstr ""
+"Niveau de débogage: c'est quand la demande de journalisation associée à un "
+"niveau de débogage est générée par ex. de méthodes de base ou constructeurs."
#. Tag: para
-#: Chapter.xml:77
+#: Chapter.xml:368
#, no-c-format
msgid ""
"Visibility level: the visibility of the constructor, method, etc. that "
"generates the debugging."
-msgstr "Niveau de visibilité: la visibilité du constructeur, de la méthode, etc. qui génèrent le débogage."
+msgstr ""
+"Niveau de visibilité: la visibilité du constructeur, de la méthode, etc. qui "
+"génèrent le débogage."
#. Tag: para
-#: Chapter.xml:80
+#: Chapter.xml:371
#, no-c-format
msgid ""
"Facility code: for instance the package or sub-module within which debugging "
"is generated, e.g., the object store."
-msgstr "Facility code: par exemple, le paquetage ou le sous-module dans lequel le débogage est généré, par ex., la base de donnée objet."
+msgstr ""
+"Facility code: par exemple, le paquetage ou le sous-module dans lequel le "
+"débogage est généré, par ex., la base de donnée objet."
#. Tag: para
-#: Chapter.xml:83
+#: Chapter.xml:374
#, no-c-format
msgid ""
"According to these variables the CLF defines three interfaces. A particular "
@@ -365,230 +1302,269 @@
"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 "D'après toutes ces variables, le CLF définit trois interfaces. Un produit particulier peut implémenter ses propres classes suivant sa granularité plus fine. JBoss Transactions utilise le niveau de débogage par défaut et le niveau de visibilité par défaut offert par CLF, mais détermine son propre code de fonction. JBoss Transactions utilise le niveau par défaut assigné à ses objets d'enregistreurs chronologiques (DEBUG). Cependant, il utilise des fonctionalités de débogage plus raffinées pour activer ou désactiver les messages de débogage. Des valeurs de débogage plus raffinées, utilisées par les transactions JBoss, sont définies ci-dessous:"
+msgstr ""
+"D'après toutes ces variables, le CLF définit trois interfaces. Un produit "
+"particulier peut implémenter ses propres classes suivant sa granularité plus "
+"fine. JBoss Transactions utilise le niveau de débogage par défaut et le "
+"niveau de visibilité par défaut offert par CLF, mais détermine son propre "
+"code de fonction. JBoss Transactions utilise le niveau par défaut assigné à "
+"ses objets d'enregistreurs chronologiques (DEBUG). Cependant, il utilise des "
+"fonctionalités de débogage plus raffinées pour activer ou désactiver les "
+"messages de débogage. Des valeurs de débogage plus raffinées, utilisées par "
+"les transactions JBoss, sont définies ci-dessous:"
#. Tag: para
-#: Chapter.xml:84
+#: Chapter.xml:375
#, 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 "Niveau de débogage - JBoss Transactions utilise les valeurs par défaut déterminées dans la classe <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+"Niveau de débogage - JBoss Transactions utilise les valeurs par défaut "
+"déterminées dans la classe <classname>com.arjuna.common.util.logging."
+"DebugLevel</classname>"
#. Tag: para
-#: Chapter.xml:87
+#: Chapter.xml:378
#, no-c-format
msgid ""
"NO_DEBUGGING: No diagnostics. A logger object assigned with this values "
"discard all debug requests"
-msgstr "NO_DEBUGGING: No diagnostics. Un objet de journalisation assigné à cette valeur, ignore toutes les demandes de débogage."
+msgstr ""
+"NO_DEBUGGING: No diagnostics. Un objet de journalisation assigné à cette "
+"valeur, ignore toutes les demandes de débogage."
#. Tag: para
-#: Chapter.xml:90
+#: Chapter.xml:381
#, 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 "FULL_DEBUGGING: Full diagnostics. Un objet de journalisation assigné à cette valeur autorise toutes les demandes de débogage si le 'facility code' et le niveau de visibilité correspondent à ceux qui sont autorisés par l'enregistreur chronologique."
+msgstr ""
+"FULL_DEBUGGING: Full diagnostics. Un objet de journalisation assigné à cette "
+"valeur autorise toutes les demandes de débogage si le 'facility code' et le "
+"niveau de visibilité correspondent à ceux qui sont autorisés par "
+"l'enregistreur chronologique."
#. Tag: para
-#: Chapter.xml:93
+#: Chapter.xml:384
#, no-c-format
msgid "Additional Debugging Values are:"
msgstr "Les valeurs de débogage supplémentaires sont:"
#. Tag: para
-#: Chapter.xml:96
+#: Chapter.xml:387
#, no-c-format
msgid "CONSTRUCTORS: Diagnostics from constructors."
msgstr "CONSTRUCTORS: Diagnostiques de la part des constructeurs."
#. Tag: para
-#: Chapter.xml:99
+#: Chapter.xml:390
#, no-c-format
msgid "DESTRUCTORS: Diagnostics from finalizers."
msgstr "DESTRUCTORS: Diagnostiques au niveau des finalizers."
#. Tag: para
-#: Chapter.xml:102
+#: Chapter.xml:393
#, no-c-format
msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
-msgstr "CONSTRUCT_AND_DESTRUCT: Diagnostiques de la part des constructeurs et des finalizers."
+msgstr ""
+"CONSTRUCT_AND_DESTRUCT: Diagnostiques de la part des constructeurs et des "
+"finalizers."
#. Tag: para
-#: Chapter.xml:105
+#: Chapter.xml:396
#, no-c-format
msgid "FUNCTIONS: Diagnostics from functions."
msgstr "FUNCTIONS: Diagnostiques par les fonctions."
#. Tag: para
-#: Chapter.xml:108
+#: Chapter.xml:399
#, no-c-format
msgid "OPERATORS: Diagnostics from operators, such as equals."
msgstr "OPERATORS: Diagnostiques par les opérateurs, comme les equals."
#. Tag: para
-#: Chapter.xml:111
+#: Chapter.xml:402
#, no-c-format
msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
msgstr "FUNCS_AND_OPS: Diagnostiques par les fonctions et les opérations."
#. Tag: para
-#: Chapter.xml:114
+#: Chapter.xml:405
#, no-c-format
msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
msgstr "ALL_NON_TRIVIAL: Diagnostiques par les opérations non-triviales."
#. Tag: para
-#: Chapter.xml:117
+#: Chapter.xml:408
#, no-c-format
msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
msgstr "TRIVIAL_FUNCS: Diagnostiques par les fonctions triviales."
#. Tag: para
-#: Chapter.xml:120
+#: Chapter.xml:411
#, no-c-format
msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
-msgstr "TRIVIAL_OPERATORS: Diagnostiques par les opérations triviales, et les opérateurs."
+msgstr ""
+"TRIVIAL_OPERATORS: Diagnostiques par les opérations triviales, et les "
+"opérateurs."
#. Tag: para
-#: Chapter.xml:123
+#: Chapter.xml:414
#, no-c-format
msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
msgstr "ALL_TRIVIAL: Diagnostiques par les opérations triviales."
#. Tag: para
-#: Chapter.xml:126
+#: Chapter.xml:417
#, 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 "Niveau de visibilité– JBoss Transactions utilise les valeurs par défaut définies dans la classe <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+"Niveau de visibilité– JBoss Transactions utilise les valeurs par défaut "
+"définies dans la classe <classname>com.arjuna.common.util.logging."
+"VisibilityLevel</classname>"
#. Tag: para
-#: Chapter.xml:129
+#: Chapter.xml:420
#, no-c-format
msgid "VIS_NONE: No Diagnostic"
msgstr "VIS_NONE: Pas de diagnostique"
#. Tag: para
-#: Chapter.xml:132
+#: Chapter.xml:423
#, no-c-format
msgid "VIS_PRIVATE : only from private methods."
msgstr "VIS_PRIVATE : seulement par méthodes privées."
#. Tag: para
-#: Chapter.xml:135
+#: Chapter.xml:426
#, no-c-format
msgid "VIS_PROTECTED only from protected methods."
msgstr "VIS_PROTECTED seulement par méthodes protégées."
#. Tag: para
-#: Chapter.xml:138
+#: Chapter.xml:429
#, no-c-format
msgid "VIS_PUBLIC only from public methods."
msgstr "VIS_PUBLIC seulement par méthodes publiques."
#. Tag: para
-#: Chapter.xml:141
+#: Chapter.xml:432
#, no-c-format
-msgid "VIS_JBoss_Transactions_Administrators_Guide only from package methods."
-msgstr "VIS_JBoss_Transactions_Administrators_Guide seulement par méthodes de paquetage."
+msgid "VIS_PACKAGE only from package methods."
+msgstr "VIS_PACKAGE seulement par les méthodes des packages"
#. Tag: para
-#: Chapter.xml:144
+#: Chapter.xml:435
#, no-c-format
msgid "VIS_ALL: Full Diagnostic"
msgstr "VIS_ALL: Diagnostique complet"
#. Tag: para
-#: Chapter.xml:147
+#: Chapter.xml:438
#, 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 "Facility Code – JBoss Transactions utilise les valeurs suivantes définies dans la classe <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+"Facility Code – JBoss Transactions utilise les valeurs suivantes définies "
+"dans la classe <classname>com.arjuna.common.util.logging.VisibilityLevel</"
+"classname>"
#. Tag: para
-#: Chapter.xml:150
+#: Chapter.xml:441
#, no-c-format
msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
msgstr "FAC_ATOMIC_ACTION = 0x0000001 (module de base d'action atomique)."
#. Tag: para
-#: Chapter.xml:153
+#: Chapter.xml:444
#, no-c-format
msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
msgstr "FAC_BUFFER_MAN = 0x00000004 (classes de gestion des états (tampons))."
#. Tag: para
-#: Chapter.xml:156
+#: Chapter.xml:447
#, no-c-format
msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
msgstr "FAC_ABSTRACT_REC = 0x00000008 (enregistrements des abstracts)."
#. Tag: para
-#: Chapter.xml:159
+#: Chapter.xml:450
#, no-c-format
msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
-msgstr "FAC_OBJECT_STORE = 0x00000010 (implementations de bases de données-objet)."
+msgstr ""
+"FAC_OBJECT_STORE = 0x00000010 (implementations de bases de données-objet)."
#. Tag: para
-#: Chapter.xml:162
+#: Chapter.xml:453
#, no-c-format
msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
msgstr "FAC_STATE_MAN = 0x00000020 (gestion des états et StateManager)."
#. Tag: para
-#: Chapter.xml:165
+#: Chapter.xml:456
#, no-c-format
msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
-msgstr "FAC_SHMEM = 0x00000040 (classes d'implémentation de la mémoire partagée)."
+msgstr ""
+"FAC_SHMEM = 0x00000040 (classes d'implémentation de la mémoire partagée)."
#. Tag: para
-#: Chapter.xml:168
+#: Chapter.xml:459
#, no-c-format
msgid "FAC_GENERAL = 0x00000080 (general classes)."
msgstr "FAC_GENERAL = 0x00000080 (classes générales)."
#. Tag: para
-#: Chapter.xml:171
+#: Chapter.xml:462
#, no-c-format
msgid ""
"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
"classes)."
-msgstr "FAC_CRASH_RECOVERY = 0x00000800 (trace détaillée du module de recouvrement en cas de plantage et des classes)."
+msgstr ""
+"FAC_CRASH_RECOVERY = 0x00000800 (trace détaillée du module de recouvrement "
+"en cas de plantage et des classes)."
#. Tag: para
-#: Chapter.xml:174
+#: Chapter.xml:465
#, no-c-format
msgid "FAC_THREADING = 0x00002000 (threading classes)."
msgstr "FAC_THREADING = 0x00002000 (classes de threading)."
#. Tag: para
-#: Chapter.xml:177
+#: Chapter.xml:468
#, no-c-format
msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
msgstr "AC_JDBC = 0x00008000 (prise en charge JDBC 1.0 et 2.0)."
#. Tag: para
-#: Chapter.xml:180
+#: Chapter.xml:471
#, no-c-format
-msgid "FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
-msgstr "FAC_RECOVERY_NORMAL = 0x00040000 (sortie normale pour gestionnaire de recouvrement en cas de plantage)."
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (sortie normale pour gestionnaire de "
+"recouvrement en cas de plantage)."
#. Tag: para
-#: Chapter.xml:183
+#: Chapter.xml:474
#, 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 "Pour garantir les sorties qui conviennent, il faut configurer certaines propriétés de débogage plus raffinées, particulièrement dans le fichier <filename>CommonLogging.xml</filename>, pour activer les messages de journalisation émis par le module de JBoss Transactions."
+msgstr ""
+"Pour garantir les sorties qui conviennent, il faut configurer certaines "
+"propriétés de débogage plus raffinées, particulièrement dans le fichier "
+"<filename>CommonLogging.xml</filename>, pour activer les messages de "
+"journalisation émis par le module de JBoss Transactions."
#. Tag: para
-#: Chapter.xml:184
+#: Chapter.xml:475
#, no-c-format
msgid ""
"Messages describing the start and the periodical behavior made by the "
@@ -597,10 +1573,17 @@
"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 "Les messages qui décrivent le démarrage et le comportement périodique du RecoveryManager (gestionnaire de recouvrement) sont des sorties au niveau INFO. Si on souhaite d'autre traçage de débogage, le niveau de débogage le plus raffiné devra être déterminé en fonction. Par exemple, la configuration suivante,dans CommonLogging.xml, active tous les messages de débogage liés au protocole de recouvrement en cas de plantage et issus par le module JBoss Transactions."
+msgstr ""
+"Les messages qui décrivent le démarrage et le comportement périodique du "
+"RecoveryManager (gestionnaire de recouvrement) sont des sorties au niveau "
+"INFO. Si on souhaite d'autre traçage de débogage, le niveau de débogage le "
+"plus raffiné devra être déterminé en fonction. Par exemple, la configuration "
+"suivante,dans CommonLogging.xml, active tous les messages de débogage liés "
+"au protocole de recouvrement en cas de plantage et issus par le module JBoss "
+"Transactions."
#. Tag: programlisting
-#: Chapter.xml:186
+#: Chapter.xml:477
#, no-c-format
msgid ""
"<!-- Common logging related properties. -->\n"
@@ -622,15 +1605,17 @@
" value=\"0xffffffff\"/>"
#. Tag: para
-#: Chapter.xml:189
+#: Chapter.xml:480
#, no-c-format
msgid ""
"Two logger objects are provided, one manages I18N messages and a second does "
"not."
-msgstr "Deux objets de journalisation sont fournis, un objet gère les messages l18N et le second ne les gère pas."
+msgstr ""
+"Deux objets de journalisation sont fournis, un objet gère les messages l18N "
+"et le second ne les gère pas."
#. Tag: para
-#: Chapter.xml:192
+#: Chapter.xml:483
#, no-c-format
msgid ""
"Setting the normal recovery messages to the INFO level allows the "
@@ -639,16 +1624,24 @@
"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 "Configurer les messages de recouvrement normaux au niveau INFO permet au RecoveryManager de produire un niveau modéré de rapport de journalisation. Si il ne se passe rien, il devra rapporter chaque saisie dans chaque module pour chaque tentative périodique. Pour désactiver les messages INFO produits par le Gestionnaire de recouvrement, le niveau de journalisation pourrait être configuré au plus haut niveau: ERREUR. Configurer le niveau à ERREUR implique que le RecoveryManager ne produira que des messages d'erreur, des messages d'avertissement ou d'erreurs fatales."
+msgstr ""
+"Configurer les messages de recouvrement normaux au niveau INFO permet au "
+"RecoveryManager de produire un niveau modéré de rapport de journalisation. "
+"Si il ne se passe rien, il devra rapporter chaque saisie dans chaque module "
+"pour chaque tentative périodique. Pour désactiver les messages INFO produits "
+"par le Gestionnaire de recouvrement, le niveau de journalisation pourrait "
+"être configuré au plus haut niveau: ERREUR. Configurer le niveau à ERREUR "
+"implique que le RecoveryManager ne produira que des messages d'erreur, des "
+"messages d'avertissement ou d'erreurs fatales."
#. Tag: title
-#: Chapter.xml:196
+#: Chapter.xml:487
#, no-c-format
msgid "Periodic Recovery"
msgstr "Recouvrement périodique"
#. Tag: para
-#: Chapter.xml:197
+#: Chapter.xml:488
#, no-c-format
msgid ""
"The RecoveryManager scans the ObjectStore and other locations of "
@@ -660,11 +1653,18 @@
"used are dynamically loaded, using properties found in the RecoveryManager "
"property file."
msgstr ""
-"Le gestionnaire de recouvrement balaye les ObjectStores et autres locations d'information, dans la recherche de ressources et de transactions qui requièrent ou pourraient requérir un recouvrement. Le processus de balayage et de recouvrement sont opérés par les modules de recouvrement, (instances de classes qui implémentent l'interface com.arjuna.ats."
-"arjuna.recovery.RecoveryModule), comportant chacun une responsabilité pour une catégorie particulière de transaction ou de ressource. L'ensemble des modules de recouvrement est chargé dynamiquement, en utilisant des propriétés que l'on peut trouver dans le fichier de propriétés du RecoveryManager."
+"Le gestionnaire de recouvrement balaye les ObjectStores et autres locations "
+"d'information, dans la recherche de ressources et de transactions qui "
+"requièrent ou pourraient requérir un recouvrement. Le processus de balayage "
+"et de recouvrement sont opérés par les modules de recouvrement, (instances "
+"de classes qui implémentent l'interface com.arjuna.ats.arjuna.recovery."
+"RecoveryModule), comportant chacun une responsabilité pour une catégorie "
+"particulière de transaction ou de ressource. L'ensemble des modules de "
+"recouvrement est chargé dynamiquement, en utilisant des propriétés que l'on "
+"peut trouver dans le fichier de propriétés du RecoveryManager."
#. Tag: para
-#: Chapter.xml:198
+#: Chapter.xml:489
#, no-c-format
msgid ""
"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
@@ -681,12 +1681,22 @@
"a candidate for recovery."
msgstr ""
"L'interface a deux méthodes: <literal>periodicWorkFirstPass</literal> et "
-"<literal>periodicWorkSecondPass</literal>. A un certain interval (défini par la propriété <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
-"classname>), le RecoveryManager fera appel à la première méthode FirstPass sur chaque propriété, attendra un petit moment (défini par la propriété <classname>com."
-"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>), puis fera appel la seconde méthode SecondPass pour chaque module. Normalement, avec la première méthode, FirstPass, le module balaye ( par ex. une partie pertinente de l'ObjectStore) pour trouver des transactions ou des ressources douteuses (par ex. à mi-chemin vers le processus de validation). Avec la seconde, SecondPass, si les doutes subsistent, il est possible que le processus d'application de départ soit planté et que cet élément soit candidat au recouvrement."
+"<literal>periodicWorkSecondPass</literal>. A un certain interval (défini par "
+"la propriété <classname>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</classname>), le RecoveryManager fera appel à la "
+"première méthode FirstPass sur chaque propriété, attendra un petit moment "
+"(défini par la propriété <classname>com.arjuna.ats.arjuna.recovery."
+"recoveryBackoffPeriod</classname>), puis fera appel la seconde méthode "
+"SecondPass pour chaque module. Normalement, avec la première méthode, "
+"FirstPass, le module balaye ( par ex. une partie pertinente de "
+"l'ObjectStore) pour trouver des transactions ou des ressources douteuses "
+"(par ex. à mi-chemin vers le processus de validation). Avec la seconde, "
+"SecondPass, si les doutes subsistent, il est possible que le processus "
+"d'application de départ soit planté et que cet élément soit candidat au "
+"recouvrement."
#. Tag: para
-#: Chapter.xml:199
+#: Chapter.xml:490
#, no-c-format
msgid ""
"An attempt, by the RecoveryManager, to recover a transaction that is still "
@@ -701,11 +1711,21 @@
"usually generating a warning. Recovery of such a transaction is the "
"RecoveryManager’s responsibility)."
msgstr ""
-"Une tentative du RecoveryManager de recouvrement de transaction en cours de dans le(s) processus d'origine, est susceptible d'endommager la cohérence. Par conséquent, les modules de recouvrement utilisent un mécanisme (implémenté dans le paquetage <classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
-"classname>) pour vérifier sur le processus d'origine est toujours actif, et si la transaction progresse toujours. Le RecoveryManager ne continue le processus de recouvrement que si le processus d'origine est terminé, ou, s'il est toujours actif, il patientera que la transaction soit terminée. (Si une processus de serveur ou une machine échouent, mais que le processus d'initiation de la transaction subsiste, la transaction s'achèvera, en générant normalement un avertissement. Le recouvrement d'un telle transaction est du ressort du RecoveryManager)."
+"Une tentative du RecoveryManager de recouvrement de transaction en cours de "
+"dans le(s) processus d'origine, est susceptible d'endommager la cohérence. "
+"Par conséquent, les modules de recouvrement utilisent un mécanisme "
+"(implémenté dans le paquetage <classname>com.arjuna.ats.arjuna.recovery."
+"TransactionStatusManager</classname>) pour vérifier sur le processus "
+"d'origine est toujours actif, et si la transaction progresse toujours. Le "
+"RecoveryManager ne continue le processus de recouvrement que si le processus "
+"d'origine est terminé, ou, s'il est toujours actif, il patientera que la "
+"transaction soit terminée. (Si une processus de serveur ou une machine "
+"échouent, mais que le processus d'initiation de la transaction subsiste, la "
+"transaction s'achèvera, en générant normalement un avertissement. Le "
+"recouvrement d'un telle transaction est du ressort du RecoveryManager)."
#. Tag: para
-#: Chapter.xml:200
+#: Chapter.xml:491
#, no-c-format
msgid ""
"It is clearly important to set the interval periods appropriately. The total "
@@ -725,20 +1745,41 @@
"thus require a “call to the original process to see if they are still in "
"progress"
msgstr ""
-"Il est très important de configurer les intervals périodiques correctement. Le temps d'itération total correspondra à la somme des <literal>periodicRecoveryPeriod</"
-"literal>, <literal>recoveryBackoffPeriod</literal> et à la durée qu'il faut pour balayer les zônes de stockage et tenter le recouvrement de toutes transactions précaires, pour tous les modules de recouvrement. Le temps de tentative de recouvrement peut inclure les délais de connexion au moment des tentatives de communication avec les processus ou des machines qui sont plantées ou qui sont inaccessibles (ce qui explique pourquoi il existe des mécanismes dans le système de recouvrement pour éviter d'essayer de recouvrir la même transaction indéfiniement). Le temps d'itération total va affecter la durée pendant laquelle une ressource pourra demeurer accessible suite à un échec - <literal>periodicRecoveryPeriod</literal> devra être configuré en fonction ( la valeur par défaut est de 120 secondes). Le <literal>recoveryBackoffPeriod</literal> peut, comparativement, être court ( la valeur par défaut est de 10 secondes) - son but est surtout de réduire le nomb!
re de transactions candidates au recouvrement et qui donc requièrent un appel au processus d'origine pour vérifier si elles sont toujours en cours."
+"Il est très important de configurer les intervals périodiques correctement. "
+"Le temps d'itération total correspondra à la somme des "
+"<literal>periodicRecoveryPeriod</literal>, <literal>recoveryBackoffPeriod</"
+"literal> et à la durée qu'il faut pour balayer les zônes de stockage et "
+"tenter le recouvrement de toutes transactions précaires, pour tous les "
+"modules de recouvrement. Le temps de tentative de recouvrement peut inclure "
+"les délais de connexion au moment des tentatives de communication avec les "
+"processus ou des machines qui sont plantées ou qui sont inaccessibles (ce "
+"qui explique pourquoi il existe des mécanismes dans le système de "
+"recouvrement pour éviter d'essayer de recouvrir la même transaction "
+"indéfiniement). Le temps d'itération total va affecter la durée pendant "
+"laquelle une ressource pourra demeurer accessible suite à un échec - "
+"<literal>periodicRecoveryPeriod</literal> devra être configuré en fonction "
+"( la valeur par défaut est de 120 secondes). Le "
+"<literal>recoveryBackoffPeriod</literal> peut, comparativement, être court "
+"( la valeur par défaut est de 10 secondes) - son but est surtout de réduire "
+"le nombre de transactions candidates au recouvrement et qui donc requièrent "
+"un appel au processus d'origine pour vérifier si elles sont toujours en "
+"cours."
#. Tag: para
-#: Chapter.xml:203
+#: Chapter.xml:494
#, 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 "Dans les versions précédentes de JBoss Transactions, il n'y avait pas de mécanisme de contact, et la période de backoff devait être assez longue pour éviter d'intercepter des transactions en cours. A partir de la version 3.0, ce risque a disparu."
+msgstr ""
+"Dans les versions précédentes de JBoss Transactions, il n'y avait pas de "
+"mécanisme de contact, et la période de backoff devait être assez longue pour "
+"éviter d'intercepter des transactions en cours. A partir de la version 3.0, "
+"ce risque a disparu."
#. Tag: para
-#: Chapter.xml:206
+#: Chapter.xml:497
#, no-c-format
msgid ""
"Two recovery modules (implementations of the <classname>com.arjuna.ats."
@@ -754,13 +1795,22 @@
"process might occur while a periodic recovery pass is in progress). The "
"default Recovery Extension settings are:"
msgstr ""
-"On fournit deux modules de recouvrement ( les implémentations d'interfaces <classname>com.arjuna.ats."
-"arjuna.recovery.RecoveryModule</classname>) avec JBoss Transactions, prenant en charge plusieurs aspects de recouvrement de transactions, y compris le recouvrement JDBC. Il est possible pour les utilisateurs avancés de créer leurs propres modules de recouvrement et de les enregistrer dans le RecoveryManager. Les modules de recouvrement sont enregistrés dans le RecoveryManager en utilisant les propriétés qui commencent par “<classname>com.arjuna.ats.arjuna.recovery."
-"RecoveryExtension</classname>”. Elles seront invoquées à chaque "
-"Pass du recouvrement périodique en suivant l'ordre des noms de propriété - il sera donc possible de prédire l'ordonnancement ( mais noter que l'échec d'un processus d'application peut avoir lieu pendant qu'une Pass de recouvrement périodique est en cours). Les paramètres d'extension de recouvrement par défaut sont les suivants:"
+"On fournit deux modules de recouvrement ( les implémentations d'interfaces "
+"<classname>com.arjuna.ats.arjuna.recovery.RecoveryModule</classname>) avec "
+"JBoss Transactions, prenant en charge plusieurs aspects de recouvrement de "
+"transactions, y compris le recouvrement JDBC. Il est possible pour les "
+"utilisateurs avancés de créer leurs propres modules de recouvrement et de "
+"les enregistrer dans le RecoveryManager. Les modules de recouvrement sont "
+"enregistrés dans le RecoveryManager en utilisant les propriétés qui "
+"commencent par “<classname>com.arjuna.ats.arjuna.recovery.RecoveryExtension</"
+"classname>”. Elles seront invoquées à chaque Pass du recouvrement périodique "
+"en suivant l'ordre des noms de propriété - il sera donc possible de prédire "
+"l'ordonnancement ( mais noter que l'échec d'un processus d'application peut "
+"avoir lieu pendant qu'une Pass de recouvrement périodique est en cours). Les "
+"paramètres d'extension de recouvrement par défaut sont les suivants:"
#. Tag: programlisting
-#: Chapter.xml:208
+#: Chapter.xml:499
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
@@ -776,13 +1826,13 @@
" com.arjuna.ats.txoj.recovery.TORecoveryModule"
#. Tag: title
-#: Chapter.xml:211
+#: Chapter.xml:502
#, no-c-format
msgid "Expired entry removal"
msgstr "Suppression des saisies obsolètes"
#. Tag: para
-#: Chapter.xml:212
+#: Chapter.xml:503
#, no-c-format
msgid ""
"The operation of the recovery subsystem will cause some entries to be made "
@@ -802,18 +1852,34 @@
"value is negative, the first scan is delayed until after the first interval "
"(using the absolute value)"
msgstr ""
-"L'opération de recouvrement du sous-système entraînera la saisie de certaines informations dans l'ObjectStore qui ne seront pas normalement supprimées. Le RecoveryManager contient une fonction de balayage de ces informations et pour supprimer celles qui sont trop anciennes. Les opérations de balayage et de suppression sont conduites par les implémentations de l'interface <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname>. Les implémentations de cette interface sont chargées en donnant un nom de classe à la valeur de la propriété dont le nom commence par <classname>com.arjuna."
-"ats.arjuna.recovery.expiryScanner</classname>. Le RecoveryManager appelle la méthode <command>scan()</command> pour chaque implémentation Expiry Scanner (balayage expiré) chargée, dans un intervalle déterminé par la propriété <classname>com."
-"arjuna.ats.arjuna.recovery.expiryScanInterval</classname>. Cette valeur est donnée en heures - la valeur par défaut est 12. Une valeur de zéro pour <classname>expiryScanInterval</classname> supprimera tout Expiry Scanning (balayage expiré). Si la valeur fournie est positive, le premier balayage aura lieu au démarrage du RecoveryManager, si la valeur est négative, le premier balayage sera retardé jusqu'à l'apparition du premier intervalle (en utilisant la valeur absolue)."
+"L'opération de recouvrement du sous-système entraînera la saisie de "
+"certaines informations dans l'ObjectStore qui ne seront pas normalement "
+"supprimées. Le RecoveryManager contient une fonction de balayage de ces "
+"informations et pour supprimer celles qui sont trop anciennes. Les "
+"opérations de balayage et de suppression sont conduites par les "
+"implémentations de l'interface <classname>com.arjuna.ats.arjuna.recovery."
+"ExpiryScanner</classname>. Les implémentations de cette interface sont "
+"chargées en donnant un nom de classe à la valeur de la propriété dont le nom "
+"commence par <classname>com.arjuna.ats.arjuna.recovery.expiryScanner</"
+"classname>. Le RecoveryManager appelle la méthode <command>scan()</command> "
+"pour chaque implémentation Expiry Scanner (balayage expiré) chargée, dans un "
+"intervalle déterminé par la propriété <classname>com.arjuna.ats.arjuna."
+"recovery.expiryScanInterval</classname>. Cette valeur est donnée en heures - "
+"la valeur par défaut est 12. Une valeur de zéro pour "
+"<classname>expiryScanInterval</classname> supprimera tout Expiry Scanning "
+"(balayage expiré). Si la valeur fournie est positive, le premier balayage "
+"aura lieu au démarrage du RecoveryManager, si la valeur est négative, le "
+"premier balayage sera retardé jusqu'à l'apparition du premier intervalle (en "
+"utilisant la valeur absolue)."
#. Tag: para
-#: Chapter.xml:213
+#: Chapter.xml:504
#, no-c-format
msgid "The kinds of item that are scanned for expiry are:"
msgstr "Sortes d'éléments balayés pour expiration:"
#. Tag: para
-#: Chapter.xml:214
+#: Chapter.xml:505
#, no-c-format
msgid ""
"TransactionStatusManager items : one of these is created by every "
@@ -825,17 +1891,24 @@
"– 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 items : l'un d'entre eux est créée par le processus d'application qui utilise JBoss Transactions - ils contiennent l'information qui autorise le RecoveryManager de déterminer si le processus qui initie la transaction est toujours actif, et quel est le statut de transaction. Leur temps d'expiration est déterminé par la propriété <classname>com.arjuna."
-"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> (en heures - la valeur par défaut est 12, zéro signifiant n\"expire jamais). Le temps d'expiration ne devrait jamais être plus élevé que la durée de vie d'un seul processus utilisant-JBoss Transactions."
+"TransactionStatusManager items : l'un d'entre eux est créée par le processus "
+"d'application qui utilise JBoss Transactions - ils contiennent l'information "
+"qui autorise le RecoveryManager de déterminer si le processus qui initie la "
+"transaction est toujours actif, et quel est le statut de transaction. Leur "
+"temps d'expiration est déterminé par la propriété <classname>com.arjuna.ats."
+"arjuna.recovery.transactionStatusManagerExpiryTime</classname> (en heures - "
+"la valeur par défaut est 12, zéro signifiant n\"expire jamais). Le temps "
+"d'expiration ne devrait jamais être plus élevé que la durée de vie d'un seul "
+"processus utilisant-JBoss Transactions."
#. Tag: para
-#: Chapter.xml:215
+#: Chapter.xml:506
#, no-c-format
msgid "The Expiry Scanner properties for these are:"
msgstr "Leurs propriétés Expiry Scanner sont:"
#. Tag: programlisting
-#: Chapter.xml:217
+#: Chapter.xml:508
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
@@ -847,148 +1920,320 @@
"ExpiredTransactionStatusManagerScanner"
#. Tag: title
-#: Chapter.xml:220
+#: Chapter.xml:511
#, no-c-format
-msgid "Errors and Exceptions"
-msgstr "Erreurs et exceptions"
+msgid "Selecting the JTA implementation"
+msgstr "Sélectionner l'implémentation JTA"
#. Tag: para
-#: Chapter.xml:221
+#: Chapter.xml:512
#, 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 "Dans cette section, nous devrons couvrir les types d'erreur et les exceptions qui pourraient être envoyées ou reportées pendant une application transactionelle ou bien tenter de donner des indications sur leurs causes."
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+"Deux variantes de l'implémentation JTA sont maintenant proposées et "
+"accessibles à travers la même interface. Elles sont les suivantes:"
#. Tag: para
-#: Chapter.xml:224
+#: Chapter.xml:515
#, 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 "NO_MEMORY: l'application est à cours de mémoire (<classname>OutOfMemoryError</classname>) et JBoss Transactions a tenté de faire le nettoyage (en exécutant le nettoyeur) avant de renvoyer l'exception. C'est probablement un problème transitoire et retenter l'invocation devrait fonctionner."
+"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 ""
+"Un JTA purement local, qui permet aux transactions JTA non distribuées "
+"d'être exécutées. C'est la seule version disponible avec le produit JBoss "
+"Transactions."
#. Tag: para
-#: Chapter.xml:227
+#: Chapter.xml:518
#, 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 "com.arjuna.ats.arjuna.exceptions.FatalError: apparition d'une erreur qui entraîne la fermeture du système de transactions. Avant l'apparition de cette erreur, le service de transaction devra s'assurer que toutes les transactions en cours sont redressées. Si l'application est coincée, elle doit mettre de l'ordre et sortir. Si on tente de continuer les opérations, on peut endommager la cohérence de l'application."
+"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 ""
+"Un JTA distant basé-CORBA, qui permet d'exécuter les transactions JTA "
+"distribuées. Cette version est seulement disponible avec le produit "
+"ArjunaJTS et requiert un CORBA ORB supporté."
#. Tag: para
-#: Chapter.xml:230
+#: Chapter.xml:522
#, 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 "com.arjuna.ats.arjuna.exceptions.LicenceError: tentative d'utiliser le service de transaction d'une manière non cohérente par rapport à la licence en cours. Le service de transaction ne permettra pas davantage de progrès pour les nouvelles ou pour les transactions existantes."
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr ""
+"ces deux implémentations sont totalement compatibles avec le pilote "
+"transactionnel JDBC qui est fourni avec JBoss Transactions."
#. Tag: para
-#: Chapter.xml:233
+#: Chapter.xml:525
#, 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 "com.arjuna.ats.arjuna.exceptions.ObjectStoreError: erreur au moment où le service transaction a tenté d'utiliser la base de données objet. Impossible de progresser davantage."
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+"En vue de sélectionner une implémentation JTA locale, il est nécessaire de "
+"procéder aux étapes suivantes:"
#. Tag: para
-#: Chapter.xml:236
+#: Chapter.xml:528
#, 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 "Des avertissements de bases de données objet à propos de problèmes d'accès aux états, peuvent survenir au cours d'une exécution normale de recouvrement de plantage. Ceci est le résultat de multiples tentatives concurrentes de tenter un recouvrement sur la même transaction. On peut ignorer ces avertissements."
+"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 ""
+"veillez à ce que la propriété <literal>com.arjuna.ats.jta."
+"jtaTMImplementation</literal> soit configurée ainsi <literal>com.arjuna.ats."
+"internal.jta.transaction.arjunacore.TransactionManagerImple</literal>."
+#. Tag: para
+#: Chapter.xml:531
+#, 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 ""
+"Veillez à ce que la propriété <literal>com.arjuna.ats.jta."
+"jtaUTImplementation</literal> soit configurée ainsi <literal>com.arjuna.ats."
+"internal.jta.transaction.arjunacore.UserTransactionImple</literal>."
+
+#. Tag: para
+#: Chapter.xml:535
+#, 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 ""
+"ces paramètres sont les valeurs par défaut des propriétés et ne pourront pas "
+"être spécifiées si l'implémentation locale est requise."
+
#. Tag: title
-#: Chapter.xml:241
+#: Chapter.xml:542
#, no-c-format
-msgid "Selecting the JTA implementation"
-msgstr "Sélectionner l'implémentation JTA"
+msgid "ORB specific configurations"
+msgstr ""
+#. Tag: title
+#: Chapter.xml:544
+#, no-c-format
+msgid "<title>JacORB</title>"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:242
+#: Chapter.xml:545
#, no-c-format
msgid ""
-"Two variants of the JTA implementation are now provided and accessible "
-"through the same interface. These are:"
-msgstr "Deux variantes de l'implémentation JTA sont maintenant proposées et accessibles à travers la même interface. Elles sont les suivantes:"
+"For JacORB to function correctly it is necessary to ensure there is a valid "
+"<filename>jacorb.properties</filename> or <filename>.jacorb_properties</"
+"filename> file in one of the following places:"
+msgstr ""
#. Tag: para
-#: Chapter.xml:245
+#: Chapter.xml:551
#, no-c-format
+msgid "The classpath."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:556
+#, 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 "Un JTA purement local, qui permet aux transactions JTA non distribuées d'être exécutées. C'est la seule version disponible avec le produit JBoss Transactions."
+"The home directory of the user running the JBoss Transaction Service. The "
+"home directory is retrieved using <code>System.getProperty( “user.home” );</"
+"code>"
+msgstr ""
#. Tag: para
-#: Chapter.xml:248
+#: Chapter.xml:561
#, no-c-format
+msgid "The current directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:566
+#, 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 "Un JTA distant basé-CORBA, qui permet d'exécuter les transactions JTA distribuées. Cette version est seulement disponible avec le produit ArjunaJTS et requiert un CORBA ORB supporté."
+"The <filename>lib</filename> directory of the JDK used to run your "
+"application. This is retrieved using <code>System.getProperty( “java.home” );"
+"</code>"
+msgstr ""
#. Tag: para
-#: Chapter.xml:252
+#: Chapter.xml:571
#, no-c-format
msgid ""
-"both of these implementations are fully compatible with the transactional "
-"JDBC driver provided with JBoss Transactions."
-msgstr "ces deux implémentations sont totalement compatibles avec le pilote transactionnel JDBC qui est fourni avec JBoss Transactions."
+"The above places are searched in the order given. A template "
+"<filename>jacorb.properties</filename> file can be found in the JacORB "
+"installation directory."
+msgstr ""
#. Tag: para
-#: Chapter.xml:255
+#: Chapter.xml:574
#, no-c-format
msgid ""
-"In order to select the local JTA implementation it is necessary to perform "
-"the following steps:"
-msgstr "En vue de sélectionner une implémentation JTA locale, il est nécessaire de procéder aux étapes suivantes:"
+"Within the JacORB properties file there are two important properties which "
+"must be tailored to suit your application, they are:"
+msgstr ""
+#. Tag: property
+#: Chapter.xml:580
+#, no-c-format
+msgid "jacorb.poa.thread_pool_max"
+msgstr ""
+
+#. Tag: property
+#: Chapter.xml:585
+#, no-c-format
+msgid "jacorb.poa.thread_pool_min"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:258
+#: Chapter.xml:589
#, 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>."
+"These properties specify the minimum and maximum number of request "
+"processing threads that JacORB will use in its thread pool. If there aren’t "
+"a sufficient number of threads available in this thread pool then the "
+"application may appear to become deadlocked. For more information on "
+"configuring JacORB please reference the JacORB documentation."
msgstr ""
-"veillez à ce que la propriété <literal>com.arjuna.ats.jta.jtaTMImplementation</"
-"literal> soit configurée ainsi <literal>com.arjuna.ats.internal.jta.transaction."
-"arjunacore.TransactionManagerImple</literal>."
#. Tag: para
-#: Chapter.xml:261
+#: Chapter.xml:593
#, 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>."
+"JacORB comes with its own implementation of the classes defined in the "
+"<filename>CosTransactions.idl</filename> file. Unfortunately these are "
+"incompatible with the version shipped with JBossTS. Therefore, it is "
+"important that the JBossTS jar files appear in the <code>CLASSPATH</code> "
+"before any JacORB jars."
msgstr ""
-"Veillez à ce que la propriété <literal>com.arjuna.ats.jta.jtaUTImplementation</"
-"literal> soit configurée ainsi <literal>com.arjuna.ats.internal.jta.transaction."
-"arjunacore.UserTransactionImple</literal>."
#. Tag: para
-#: Chapter.xml:265
+#: Chapter.xml:597
#, 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 "ces paramètres sont les valeurs par défaut des propriétés et ne pourront pas être spécifiées si l'implémentation locale est requise."
+"When running the recovery manager it is important that it always uses the "
+"same well known port for each machine on which it runs. You should not use "
+"the OAPort property provided by JacORB unless the recovery manager has its "
+"own <filename>jacorb.properties</filename> file or this is provided on the "
+"command line when starting the recovery manager. If the recovery manager and "
+"other components of JBossTS share the same <filename>jacorb.properties</"
+"filename> file, then you should use the <filename>com.arjuna.ats.jts."
+"recoveryManagerPort</filename> and <filename>com.arjuna.ats.jts."
+"recoveryManagerAddress</filename> properties."
+msgstr ""
+#. Tag: title
+#: Chapter.xml:603
+#, no-c-format
+msgid "Initializing JBossTS applications"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:604
+#, no-c-format
+msgid ""
+"It is important that JBossTS is correctly initialized prior to any "
+"application object being created. In order to guarantee this, the programmer "
+"should use the <methodname>ORB_init</methodname> and <methodname>create_POA</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:609
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr "Erreurs et exceptions"
+
+#. Tag: para
+#: Chapter.xml:610
+#, 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 ""
+"Dans cette section, nous devrons couvrir les types d'erreur et les "
+"exceptions qui pourraient être envoyées ou reportées pendant une application "
+"transactionelle ou bien tenter de donner des indications sur leurs causes."
+
+#. Tag: para
+#: Chapter.xml:613
+#, 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 ""
+"NO_MEMORY: l'application est à cours de mémoire "
+"(<classname>OutOfMemoryError</classname>) et JBoss Transactions a tenté de "
+"faire le nettoyage (en exécutant le nettoyeur) avant de renvoyer "
+"l'exception. C'est probablement un problème transitoire et retenter "
+"l'invocation devrait fonctionner."
+
+#. Tag: para
+#: Chapter.xml:616
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: apparition d'une erreur qui "
+"entraîne la fermeture du système de transactions. Avant l'apparition de "
+"cette erreur, le service de transaction devra s'assurer que toutes les "
+"transactions en cours sont redressées. Si l'application est coincée, elle "
+"doit mettre de l'ordre et sortir. Si on tente de continuer les opérations, "
+"on peut endommager la cohérence de l'application."
+
+#. Tag: para
+#: Chapter.xml:619
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: tentative d'utiliser le "
+"service de transaction d'une manière non cohérente par rapport à la licence "
+"en cours. Le service de transaction ne permettra pas davantage de progrès "
+"pour les nouvelles ou pour les transactions existantes."
+
+#. Tag: para
+#: Chapter.xml:622
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: erreur au moment où le "
+"service transaction a tenté d'utiliser la base de données objet. Impossible "
+"de progresser davantage."
+
+#. Tag: para
+#: Chapter.xml:625
+#, 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 ""
+"Des avertissements de bases de données objet à propos de problèmes d'accès "
+"aux états, peuvent survenir au cours d'une exécution normale de recouvrement "
+"de plantage. Ceci est le résultat de multiples tentatives concurrentes de "
+"tenter un recouvrement sur la même transaction. On peut ignorer ces "
+"avertissements."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Feedback.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Feedback.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Feedback.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Feedback.po to French
+# translation of Preface.po to French
# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Corina Roe <croe at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Feedback\n"
+"Project-Id-Version: Preface\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-30 12:58+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-07-07 10:52+1000\n"
"Last-Translator: Corina Roe <croe at redhat.com>\n"
"Language-Team: French <i18 at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -34,5 +34,14 @@
"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 "Si vous décelez une erreur dans ce guide, ou si vous avez des suggestions pour améliorer ce manuel, faites-nous en part! Vous pouvez soumettre un rapport dans <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> dans la section Produit: JBoss Enterprise Application Platform, Version: <replaceable><version></replaceable>, Composant: <emphasis>Doc</emphasis>. Si vous avez une suggestion pour améliorer la documentation, essayez d'être aussi précis que possible. Si vous avez décelé une erreur, n'oubliez pas de préciser le numéro de la section et de transcrire un extrait de texte avoisinant, de façon à ce que nous puissions la retrouver facilement."
-
+msgstr ""
+"Si vous décelez une erreur dans ce guide, ou si vous avez des suggestions "
+"pour améliorer ce manuel, faites-nous en part! Vous pouvez soumettre un "
+"rapport dans <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</"
+"ulink> dans la section Produit: JBoss Enterprise Application Platform, "
+"Version: <replaceable><version></replaceable>, Composant: "
+"<emphasis>Doc</emphasis>. Si vous avez une suggestion pour améliorer la "
+"documentation, essayez d'être aussi précis que possible. Si vous avez décelé "
+"une erreur, n'oubliez pas de préciser le numéro de la section et de "
+"transcrire un extrait de texte avoisinant, de façon à ce que nous puissions "
+"la retrouver facilement."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Preface.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Preface.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
"PO-Revision-Date: 2008-07-07 10:52+1000\n"
"Last-Translator: Corina Roe <croe at redhat.com>\n"
"Language-Team: French <i18 at redhat.com>\n"
@@ -34,7 +34,9 @@
msgid ""
"The Administration Guide contains information on how to administer JBoss "
"Transactions API 4.2.3."
-msgstr "Le guide d'administration contient des informations sur la façon d'administrer les transactions JBoss API 4.2.3."
+msgstr ""
+"Le guide d'administration contient des informations sur la façon "
+"d'administrer les transactions JBoss API 4.2.3."
#. Tag: title
#: Preface.xml:17
@@ -48,7 +50,9 @@
msgid ""
"This guide is most relevant to engineers who are responsible for "
"administration of JBoss Transactions API 4.2.3 installations."
-msgstr "Ce guide est surtout utile aux ingénieurs responsables de l'administration des installations JBoss Transactions API 4.2.3."
+msgstr ""
+"Ce guide est surtout utile aux ingénieurs responsables de l'administration "
+"des installations JBoss Transactions API 4.2.3."
#. Tag: title
#: Preface.xml:21
@@ -64,7 +68,11 @@
"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 "Pour pouvoir administrer les transactions JBoss, il faut tout d'abord comprendre qu'il dépend de ArjunaCore pour de nombreuses fonctionnalités de transactions. Il est donc important de lire le guide d'administration ArjunaCore avant de tenter d'administrer les transactions JBoss."
+msgstr ""
+"Pour pouvoir administrer les transactions JBoss, il faut tout d'abord "
+"comprendre qu'il dépend de ArjunaCore pour de nombreuses fonctionnalités de "
+"transactions. Il est donc important de lire le guide d'administration "
+"ArjunaCore avant de tenter d'administrer les transactions JBoss."
#. Tag: title
#: Preface.xml:25
@@ -85,7 +93,11 @@
"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 "Chapter 1, Administration des transactions JBoss: décrit comment administrer les transactions JBoss, principalement en sélectionnant une variante de l'implémentation JTA purement locale ou distante (permettant les transactions distribuées)."
+msgstr ""
+"Chapter 1, Administration des transactions JBoss: décrit comment administrer "
+"les transactions JBoss, principalement en sélectionnant une variante de "
+"l'implémentation JTA purement locale ou distante (permettant les "
+"transactions distribuées)."
#. Tag: title
#: Preface.xml:34
@@ -99,7 +111,9 @@
msgid ""
"In addition to this guide, the following guides are available in the JBoss "
"Transactions API 4.2.3 documentation set:"
-msgstr "En plus de ce guide, les guides suivants sont disponibles dans la gamme de documentation sur les transactions JBoss API 4.2.3:"
+msgstr ""
+"En plus de ce guide, les guides suivants sont disponibles dans la gamme de "
+"documentation sur les transactions JBoss API 4.2.3:"
#. Tag: para
#: Preface.xml:38
@@ -107,7 +121,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
"information about JBoss Transactions API 4.2.3."
-msgstr "Les notes de mise à jour des transactions JBoss API 4.2.3: offrent les dernières informations à propos des transactions JBoss API 4.2.3."
+msgstr ""
+"Les notes de mise à jour des transactions JBoss API 4.2.3: offrent les "
+"dernières informations à propos des transactions JBoss API 4.2.3."
#. Tag: para
#: Preface.xml:41
@@ -115,7 +131,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
"instructions for installing JBoss Transactions API 4.2.3."
-msgstr "Guide d'installation des transactions JBoss API 4.2.3: Ce guide procure des instuctions pour installer JBoss Transactions API 4.2.3."
+msgstr ""
+"Guide d'installation des transactions JBoss API 4.2.3: Ce guide procure des "
+"instuctions pour installer JBoss Transactions API 4.2.3."
#. Tag: para
#: Preface.xml:44
@@ -123,5 +141,6 @@
msgid ""
"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
"writing applications."
-msgstr "Guide du programmeur des transactions JBoss API 4.2.3: procure des informations sur les applications écriture."
-
+msgstr ""
+"Guide du programmeur des transactions JBoss API 4.2.3: procure des "
+"informations sur les applications écriture."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Revision_History.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/fr-FR/Revision_History.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Revision_History.po to French
+# translation of Preface.po to French
# Language fr-FR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Corina Roe <croe at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Revision_History\n"
+"Project-Id-Version: Preface\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-30 12:59+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-07-07 10:52+1000\n"
"Last-Translator: Corina Roe <croe at redhat.com>\n"
"Language-Team: French <i18 at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -16,9 +16,14 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "Historique de révision"
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
msgstr "<firstname></firstname> <surname></surname> <email></email>"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Author_Group.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Author_Group.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Author_Group.po to Japanese
+# translation of Preface.po to Japanese
# Language ja-JP translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Noriko Mizumoto <noriko at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-05-12 00:15+0000\n"
-"PO-Revision-Date: 2008-05-15 11:17+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-05-15 13:44+1000\n"
"Last-Translator: Noriko Mizumoto <noriko at redhat.com>\n"
"Language-Team: Japanese <fedora-trans-ja at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -16,21 +16,8 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
-#. Tag: corpauthor
-#: Author_Group.xml:6
-#, no-c-format
-msgid "FF0000 Headgear Documentation Group"
-msgstr "FF0000 Headgear Documentation Group"
-
#. 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 ""
-"<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>"
-
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Book_Info.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Book_Info.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Book_Info.po to Japanese
+# translation of Preface.po to Japanese
# Language ja-JP translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Noriko Mizumoto <noriko at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-05-12 00:15+0000\n"
-"PO-Revision-Date: 2008-05-15 11:17+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-05-15 13:44+1000\n"
"Last-Translator: Noriko Mizumoto <noriko at redhat.com>\n"
"Language-Team: Japanese <fedora-trans-ja at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -19,28 +19,27 @@
#. Tag: title
#: Book_Info.xml:6
#, no-c-format
-msgid "JBoss Transactions API 4.2.3 Administration Guide"
-msgstr "JBoss Transactions API 4.2.3 管理ガイド"
+msgid "JBoss Transactions Administrators Guide"
+msgstr "JBoss Transactions Administrators Guide"
#. Tag: subtitle
#: Book_Info.xml:10
-#, no-c-format
-msgid "JBoss Enterprise Application Platform"
-msgstr "JBoss Enterprise Application Platform"
+#, fuzzy, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 5.0"
+msgstr "JBoss Enterprise Application Platform 4.3 対応"
#. Tag: para
-#: Book_Info.xml:13
+#: Book_Info.xml:15
#, no-c-format
msgid ""
"This book is the JBoss Enterprise Application Platform edition of the JBoss "
"Transactions Administrators Guide"
msgstr ""
-"本ガイドは JBoss Enterprise Application Platform 版の JBoss "
-"Transactions 管理ガイドになります。"
+"本ガイドは JBoss Transactions Administrators Guide の JBoss Enterprise "
+"Application Platform 版です。"
#. Tag: holder
-#: Book_Info.xml:22
+#: Book_Info.xml:24
#, no-c-format
msgid "&HOLDER;"
msgstr "&HOLDER;"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Chapter.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Chapter.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Chapter.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Chapter.po to Japanese
+# translation of Preface.po to Japanese
# Language ja-JP translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Noriko Mizumoto <noriko at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Chapter\n"
+"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-06-05 22:49+0000\n"
-"PO-Revision-Date: 2008-05-19 13:04+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-05-15 13:44+1000\n"
"Last-Translator: Noriko Mizumoto <noriko at redhat.com>\n"
"Language-Team: Japanese <fedora-trans-ja at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -51,8 +51,7 @@
"成したアプリケーションの実行を行ったユーザーに所有されます。 Object Store お"
"よび Object Manager の機能は、 Unix/Windows が提供する限定形式の保護であって"
"もまったく実施しません。 読み取りまたは書き込みいずれかのためオブジェクトに行"
-"われるアクセスに関してユーザーまたはグループの ID によるチェックはありませ"
-"ん。"
+"われるアクセスに関してユーザーまたはグループの ID のチェックはありません。"
#. Tag: para
#: Chapter.xml:13
@@ -70,6 +69,16 @@
"When A is next activated and attempts to access B, a run-time error will "
"occur."
msgstr ""
+"Object Store で作成された永続オブジェクトは、StateManager.destroy メソッドが "
+"オブジェクト上で呼び出されない限り、あるいは、あるアプリケーションプログラム"
+"が明示的に それらを削除しない限りは、決して消失することはありません。このこと"
+"は、Object Store が 次第にゴミを集積していることを意味します（特にアプリケー"
+"ション開発中やテスト期間中）。 今のところ、自動のゴミ回収機能は存在しません。"
+"更に、つきまとう参照問題に対処していません。 永続オブジェクト A が別の永続オ"
+"ブジェクト B の為に Uid を ディスク上にパッシブ表現で 保存したような場合、A "
+"がまだその参照を維持しているにもかかわらず、あるアプリケーションが B を削除し"
+"てしまうことを阻止するものがないと言うことです。A が次回にアクティベートされ"
+"て、 B にアクセスを試みた時に、ランタイムエラーが発生します。"
#. Tag: para
#: Chapter.xml:16
@@ -93,7 +102,7 @@
"修正することもできません、 またこの逆もできません。"
#. Tag: para
-#: Chapter.xml:19
+#: Chapter.xml:19 Chapter.xml:62
#, no-c-format
msgid ""
"Object store management is critically important to the transaction service."
@@ -104,11 +113,72 @@
#. Tag: title
#: Chapter.xml:24
#, no-c-format
+msgid "Starting and Stopping the transaction manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"By default the transaction manager starts up in an active state such that "
+"new transactions can be created immediately. If you wish to have more "
+"control over this it is possible to set the <property>com.arjuna.ats.arjuna."
+"coordinator.startDisabled</property> configuration option to <literal>YES</"
+"literal>, in which case no transactions can be created until the transaction "
+"manager is enabled (via a call to <methodname>TxControl.enable</methodname>)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:28
+#, no-c-format
+msgid ""
+"It is possible to stop the creation of new transactions at any time by "
+"calling <methodname>TxControl.disable</methodname>. Transactions that are "
+"currently executing will not be affected. By default recovery will be "
+"allowed to continue and the transaction system will still be available to "
+"manage recovery requests from other instances in a distributed environment. "
+"(See the Failure Recovery Guide for further details). However, if you wish "
+"to disable recovery as well as remove any resources it maintains, then you "
+"can pass true to <methodname>TxControl.disable</methodname>; the default is "
+"to use <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"If you wish to shut the system down completely then it may also be necessary "
+"to terminate the background transaction reaper (see the Programmers Guide "
+"for information about what the reaper does.) In order to do this you may "
+"want to first prevent the creation of new transactions (if you are not "
+"creating transactions with timeouts then this step is not necessary) using "
+"<methodname>TxControl.disable</methodname>. Then you should call "
+"<methodname>TransactionReaper.terminate</methodname>. This method takes a "
+"boolean parameter: if true then the method will wait for the normal timeout "
+"periods associated with any transactions to expire before terminating the "
+"transactions; if false then transactions will be forced to terminate "
+"(rollback or have their outcome set such that they can only ever rollback) "
+"immediately."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"If you intent to restart the recovery manager later after having terminated "
+"it then you <emphasis>must</emphasis> use the <methodname>terminate</"
+"methodname> method with <property>asynchronous behavior</property> set to "
+"<literal>false</literal> when shutting down the recovery manager."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:40
+#, no-c-format
msgid "ObjectStore management"
msgstr "ObjectStore 管理"
#. Tag: para
-#: Chapter.xml:25
+#: Chapter.xml:41
#, no-c-format
msgid ""
"Within the transaction service installation, the object store is updated "
@@ -133,17 +203,754 @@
"ブジェクトストア内に残る可能性があります。 このため、 オブジェクトストアの内"
"容は十分な注意を払わずに削除されると疑わしいトランザクション内での解決が不可"
"能となるため、 非常に重要です。 また、 複数のユーザーが同じオブジェクトストア"
-"を共有する場合、 ユーザーはこれをよく認識してリソースは共有されないものとして"
-"オブジェクトストアの内容を削除しないようにすることが重要です。"
+"を共有する場合、 ユーザーはこれをよく認識してリソースはそれぞれ専有のものとし"
+"てオブジェクトストアの内容を削除しないようにすることが重要です。"
+#. Tag: para
+#: Chapter.xml:42
+#, fuzzy, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBossTS software. There are "
+"a few points however, that should be made:"
+msgstr ""
+"ランタイムシステムが正常に実行していることを確認する他、 JBoss Transactions "
+"ソフトウェアには継続的に行う必要のある管理が若干あります。 以下にいくつか注意"
+"事項を記します。"
+
+#. Tag: para
+#: Chapter.xml:47
+#, fuzzy, no-c-format
+msgid ""
+"The present implementation of the JBossTS system provides no security or "
+"protection for data. It is recommended that the objects stored in the "
+"JBossTS are owned by user arjuna. The Object Store and Object Manager "
+"facilities make no attempt to enforce even the limited form of protection "
+"that Unix and 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 のチェックはありません。"
+
+#. Tag: para
+#: Chapter.xml:52
+#, fuzzy, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> 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 ""
+"Object Store で作成された永続オブジェクトは、StateManager.destroy メソッドが "
+"オブジェクト上で呼び出されない限り、あるいは、あるアプリケーションプログラム"
+"が明示的に それらを削除しない限りは、決して消失することはありません。このこと"
+"は、Object Store が 次第にゴミを集積していることを意味します（特にアプリケー"
+"ション開発中やテスト期間中）。 今のところ、自動のゴミ回収機能は存在しません。"
+"更に、つきまとう参照問題に対処していません。 永続オブジェクト A が別の永続オ"
+"ブジェクト B の為に Uid を ディスク上にパッシブ表現で 保存したような場合、A "
+"がまだその参照を維持しているにもかかわらず、あるアプリケーションが B を削除し"
+"てしまうことを阻止するものがないと言うことです。A が次回にアクティベートされ"
+"て、 B にアクセスを試みた時に、ランタイムエラーが発生します。"
+
+#. Tag: para
+#: Chapter.xml:57
+#, fuzzy, 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 JBossTS software can neither detect "
+"nor correct references to old object state by new operation versions or vice "
+"versa."
+msgstr ""
+"クラスの構成が変更になった場合、 データベースの再構成やオブジェクトのバージョ"
+"ン管理に関するサポートは現在ありません。 これは対処していない複雑な研究分野に"
+"なります。 現時点では、 永続オブジェクトのクラスの定義を変更する場合は、 "
+"Object Store 内のオブジェクトの既存インスタンスが新しい表現に変換されるかは確"
+"約できませんので必ず確認を行ってください。 JBoss Transactions ソフトウェアは"
+"新しいオペレーションバージョンで旧オブジェクトの状態への参照を検出することも"
+"修正することもできません、 またこの逆もできません。"
+
#. Tag: title
-#: Chapter.xml:28
+#: Chapter.xml:70
#, no-c-format
+msgid "OTS and J2EE Transaction service management"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:72
+#, no-c-format
+msgid "Starting the run-time system"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:73
+#, no-c-format
+msgid ""
+"The JBossTS run-time support consists of run-time packages and the OTS "
+"transaction manager server. By default JBossTS does not use a separate "
+"transaction manager server: transaction managers are co-located with each "
+"application process to improve performance and improve application fault-"
+"tolerance (the application is no longer dependant upon another service in "
+"order to function correctly)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:76
+#, no-c-format
+msgid ""
+"When running applications which require a separate transaction manager, you "
+"must set the <varname>com.arjuna.ats.jts.transactionManager</varname> "
+"environment variable to have the value <literal>yes</literal>. The system "
+"will then locate the transaction manager server in a manner specific to the "
+"ORB being used. The server can be located in a number of ways: by being "
+"registered with a name server, added to the ORB’s initial references, via a "
+"JBossTS specific references file, or by the ORB’s specific location "
+"mechanism (if applicable)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:79
+#, no-c-format
+msgid ""
+"It is possible to override the default registration mechanism by using the "
+"<varname>com.arjuna.orbportability.resolveService</varname> environment "
+"variable. This can have one of the following values:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"<literal>CONFIGURATION_FILE</literal>: the default, this causes the system "
+"to use the <filename>CosServices.cfg</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:89
+#, no-c-format
+msgid ""
+"<literal>NAME_SERVICE</literal>: JBossTS will attempt to use a name service "
+"to register the transaction factory. If this is not supported, an exception "
+"will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:94
+#, no-c-format
+msgid ""
+"<literal>BIND_CONNECT</literal>: JBossTS will use the ORB-specific bind "
+"mechanism. If this is not supported, an exception will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid ""
+"<literal>RESOLVE_INITIAL_REFERENCES</literal>: JBossTS will attempt to "
+"register the transaction service with the ORBs initial service references."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid ""
+"This may not be supported on all ORBs. An exception will be thrown in that "
+"case and another option will have to be used."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:110
+#, no-c-format
+msgid "<title>OTS configuration file</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid ""
+"Similar to the resolve_initial_references, JBossTS supports an initial "
+"reference file where references for specific services can be stored and used "
+"at runtime. The file, CosServices.cfg, consists of two columns: the service "
+"name (in the case of the OTS server TransactionService) and the IOR, "
+"separated by a single space. CosServices.cfg normally resides in the etc "
+"directory of the JBossTS installation; the actual location is determined at "
+"runtime by searching the CLASSPATH for an old copy of the file resident "
+"within an etc directory, or, if one is not found, the location of the "
+"TransactionService properties file directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:115
+#, no-c-format
+msgid ""
+"The OTS server will automatically register itself in this file (creating it "
+"if necessary) if this option is being used. Stale information is also "
+"automatically removed. Machines which wish to share the same transaction "
+"server should have access to (or a copy of) this file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:118
+#, no-c-format
+msgid ""
+"The name and location of the file can be overridden using the <property>com."
+"arjuna.orbportability.initialReferencesFile</property> and <property>com."
+"arjuna.orbportability.initialReferencesRoot</property> property variables, "
+"respectively. It is recommended that the <property>com.arjuna.orbportability."
+"initialReferencesRoot</property> variable is set. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Chapter.xml:121
+#, no-c-format
+msgid ""
+"com.arjuna.orbportability.initialReferencesFile=myFile\n"
+"com.arjuna.orbportability.initialReferencesRoot=c:\\\\temp"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:123
+#, no-c-format
+msgid "<title>Name Service</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:124
+#, no-c-format
+msgid ""
+"If the ORB you are using supports a name service, and JBossTS has been "
+"configured to use it, then the transaction manager will automatically be "
+"registered with it. There is no further work required. This option is not "
+"used for JacORB"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:129
+#, no-c-format
+msgid "<title>resolve_initial_references</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:130
+#, no-c-format
+msgid "Currently this option is only supported for JacORB."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:135
+#, no-c-format
+msgid "Resolution service table"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:136
+#, no-c-format
+msgid ""
+"The following table summarizes the different ways in which the OTS "
+"transaction manager may be located on specific ORBs:"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:141
+#, no-c-format
+msgid "Locating the OTS transaction manager server"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:145
+#, no-c-format
+msgid "Resolution Mechanism"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:146
+#, no-c-format
+msgid "<entry>ORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:151
+#, no-c-format
+msgid "<entry>OTS configuration file</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:152
+#, no-c-format
+msgid "All available ORBs"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:155
+#, no-c-format
+msgid "<entry>Name Service</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:156 Chapter.xml:160
+#, no-c-format
+msgid "<entry>JacORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:159
+#, no-c-format
+msgid "<entry>resolve_initial_references</entry>"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:167
+#, no-c-format
+msgid "XA specific management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid ""
+"Each XA Xid that JBossTS creates must have a unique node identifier encoded "
+"within it and JBossTS will only recover transactions and states that match a "
+"specified node identifier. The node identifier to use should be provided to "
+"JBossTS via the <property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property> "
+"property. You must make sure this value is unique across your JBossTS "
+"instances. If you do not provide a value, then JBossTS will fabricate one "
+"and report the value via the logging infrastructure."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"When running XA recovery it is therefore necessary to tell JBossTS which "
+"types of Xid it can recover. Each Xid that JBossTS creates has a unique node "
+"identifier encoded within it and JBossTS will only recover transactions and "
+"states that match a specified node identifier. The node identifier to use "
+"should be provided to JBossTS via a property that starts with the name "
+"<property>com.arjuna.ats.jta.xaRecoveryNode</property>; multiple values may "
+"be provided. A value of <code>*</code> will force JBossTS to recover (and "
+"possibly rollback) all transactions irrespective of their node identifier "
+"and should be used with caution."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:177
+#, no-c-format
+msgid "Web Service Transaction service management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:178
+#, no-c-format
+msgid ""
+"The basic building blocks of a transactional Web Services application are "
+"the application itself, the Web services that the application consumes, the "
+"Transaction Manager, and the transaction participants which support those "
+"Web services. Though it is unlikely in a typical deployment that a single "
+"developer will be expected to support all of these roles, the concepts are "
+"presented here so that a global model can be visualized. It will often be "
+"the case that developers will produce services, or applications that consume "
+"services, whilst system administrators will run the transaction-management "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:182
+#, fuzzy, no-c-format
+msgid "The Transaction Manager"
+msgstr "Recovery Manager"
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"The transaction manager is a Web service which coordinates JBossTS "
+"transactions. It is the only software component in JBossTS that is meant to "
+"be run directly as a network service, rather than to support end-user code. "
+"The transaction manager runs as a JAXM request/response Web service."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:187
+#, no-c-format
+msgid ""
+"When starting up an application server instance that has JBossTS deployed "
+"within it, you may see various <emphasis>error</emphasis> messages in the "
+"console or log. For example <code>16:53:38,850 ERROR [STDERR] Message "
+"Listener Service: started, message listener jndi name activationcoordinator</"
+"code>. These are for information purposes only and are not actual errors."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:192
+#, fuzzy, no-c-format
+msgid "Configuring the Transaction Manager"
+msgstr "Recovery Manager を設定する"
+
+#. Tag: para
+#: Chapter.xml:193
+#, no-c-format
+msgid ""
+"The Transaction Manager and related infrastructure are configured by means "
+"of properties files: <filename>wscf.xml</filename>, <filename>wst.xml</"
+"filename> and <filename>wstx.xml</filename>. These files can be found in the "
+"conf directory and are used for configuring the demo application and the "
+"standalone module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"For the most part the default values in these files need not be altered. "
+"However, the <property>com.arjuna.ats.arjuna.objectstore.objectStoreDir</"
+"property> property determines the location of the persistent store used to "
+"record transaction state. The default value of <filename>C:/temp/"
+"ObjectStore</filename> should be changed to a value appropriate to your "
+"system. For production environments this directory should reside on fault "
+"tolerant media such as a RAID array."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"When a standalone coordinator is being used by an application it is "
+"necessary to enable and modify two further properties in <filename>wstx.xml</"
+"filename>, <property>com.arjuna.mw.wst.coordinatorURL</property> and "
+"<property>com.arjuna.mw.wst.terminatorURL</property>. These contain the URLs "
+"necessary for the client application to contact the standalone coordinator "
+"and should be configured with the correct hostname and port of the "
+"standalone coordinator."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"JBossTS is highly modular so in order to allow for flexible deployment of "
+"individual components, the same property values are sometimes required to "
+"appear in more than one configuration file. For the majority of "
+"configurations, you should maintain consistent values for properties that "
+"are defined in more than one file."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:207
+#, no-c-format
+msgid "Deploying the Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"The JBossTS Web Service Transaction Manager component consists of a number "
+"of JAR files containing the application’s class files, plus Web service "
+"(WAR) files which expose the necessary services. Programmers will typically "
+"include all these components in their application EAR file during "
+"application development, simplifying deployment of the transaction "
+"infrastructure. For production usage the Transaction Manager may be "
+"installed as an application in its own right, allowing for centralized "
+"configuration and management at the server level, independent of specific "
+"applications. The demonstration application shipped with JBossTS provides a "
+"sample deployment descriptor illustrating how the Transaction Manager "
+"components can be included in an application."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"JBossTS 4.0 uses fixed endpoints for its underlying protocol communication. "
+"Therefore, problems may arise if multiple applications using JBossTS are "
+"deployed to the same server concurrently. If you wish to deploy several "
+"transactional applications in the same server, the Transaction Manger must "
+"be deployed as a separate application and not embedded within the deployment "
+"of individual applications."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid ""
+"The coordinator directory in the JBossTS installation has been provided to "
+"assist in the configuration and deployment of a stand-alone transaction "
+"manager. In order to use this, you must:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:220
+#, fuzzy, no-c-format
+msgid "Have JBoss Enterprise Application Platform 5 installed"
+msgstr "JBoss Enterprise Application Platform 4.3 対応"
+
+#. Tag: para
+#: Chapter.xml:225
+#, no-c-format
+msgid "Install ant 1.4 or later."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:231
+#, no-c-format
+msgid ""
+"It is important that a separate application server installation be used from "
+"the one that clients and services are deployed into since otherwise "
+"conflicts may occur between the various JBossTS components."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:235
+#, no-c-format
+msgid ""
+"You must then edit the build.xml included with coordinator to point to the "
+"application server installation where the transaction coordinator will be "
+"deployed and the location of the JBossTS installation. The files "
+"<filename>ws-c_jaxm_web-app.xml</filename> and <filename>ws-t_jaxm_web-app."
+"xml</filename> in the <filename>dd</filename> directory of coordinator are "
+"the deployment descriptors for the WS-C and WS-T WAR files. These files "
+"contain templated URLs. During the build phase, ant will substitute the "
+"hostname and port values you specify in the <filename>build.xml</filename> "
+"into these files."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:238
+#, no-c-format
+msgid ""
+"Run <code>ant</code>, with <code>target deploy-weblogic</code>, <code>deploy-"
+"jboss</code> or <code>deploy-webmethods</code>, to create and deploy a new "
+"coordinator into the correct application server installation."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:241
+#, no-c-format
+msgid ""
+"Now all you need to do is point your client at the required coordinator. To "
+"do this, generate the demo application specifying the port and hostname of "
+"the coordinator."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:245
+#, no-c-format
+msgid "Deployment descriptors"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:246
+#, no-c-format
+msgid ""
+"In general, it should not be necessary to change the contents of the various "
+"deployment descriptors used by JBossTS. However, if you do need to modify "
+"them they are all included in the coordinator module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:250
+#, no-c-format
+msgid ""
+"Not all JBossTS components have ready access to the information in the "
+"deployment descriptors. Therefore, if you modify the JNDI names used by any "
+"of the WS-C or WS-T deployment descriptors you may need to inform other "
+"JBossTS components at runtime. This can be accomplished by setting an "
+"appropriate property in the <filename>wstx.xml</filename> configuration file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:253
+#, no-c-format
+msgid ""
+"The following table shows the default JNDI name used by the deployment "
+"descriptors and the corresponding property to set if the default value is "
+"changed."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:257
+#, no-c-format
+msgid "Deployment descriptor values and properties"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:261
+#, no-c-format
+msgid "JNDI Name"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:262
+#, no-c-format
+msgid "Property"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:267
+#, no-c-format
+msgid "Activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:268
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:271
+#, no-c-format
+msgid "Activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:272
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:275
+#, no-c-format
+msgid "Completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:276
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:279
+#, no-c-format
+msgid "Registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:280
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:283
+#, no-c-format
+msgid "durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:284
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:287
+#, no-c-format
+msgid "durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:288
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:291
+#, no-c-format
+msgid "volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:292
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:295
+#, no-c-format
+msgid "volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:296
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:299
+#, no-c-format
+msgid "businessagreementwithparticipantcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:300
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:303
+#, no-c-format
+msgid "businessagreementwithparticipantcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:304
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:307
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:308
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:311
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:312
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccparticipant"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:319
+#, no-c-format
msgid "JBoss Transactions runtime information"
msgstr "JBoss Transactions ランタイム情報"
#. Tag: para
-#: Chapter.xml:29
+#: Chapter.xml:320
#, no-c-format
msgid ""
"Each module that comprises JBoss Transactions possesses a class called Info. "
@@ -156,7 +963,7 @@
"用の設定情報を表す XML ドキュメントを返します。 たとえば、"
#. Tag: programlisting
-#: Chapter.xml:31
+#: Chapter.xml:322
#, no-c-format
msgid ""
"<module-info name=\"arjuna\">\n"
@@ -190,13 +997,13 @@
"</module-info>"
#. Tag: title
-#: Chapter.xml:34
+#: Chapter.xml:325
#, no-c-format
msgid "Failure recovery administration"
msgstr "障害リカバリ管理"
#. Tag: para
-#: Chapter.xml:35
+#: Chapter.xml:326
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions will ensure that "
@@ -223,7 +1030,7 @@
"ActionStore に維持され、 これは ObjectStore の一部になります。"
#. Tag: para
-#: Chapter.xml:38
+#: Chapter.xml:329
#, no-c-format
msgid ""
"If the ObjectStore is destroyed or modified, recovery may not be possible."
@@ -232,7 +1039,7 @@
"す。"
#. Tag: para
-#: Chapter.xml:41
+#: Chapter.xml:332
#, no-c-format
msgid ""
"Until the recovery procedures are complete, resources affected by a "
@@ -249,13 +1056,13 @@
"Transactional Object の起動の試行が失敗します (ロック取得試行時)。"
#. Tag: title
-#: Chapter.xml:43
+#: Chapter.xml:334
#, no-c-format
msgid "The Recovery Manager"
msgstr "Recovery Manager"
#. Tag: para
-#: Chapter.xml:44
+#: Chapter.xml:335
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions requires that the stand-"
@@ -274,13 +1081,13 @@
"あります。 Recovery Manager を起動するには次のコマンドを実行します。"
#. Tag: command
-#: Chapter.xml:45
+#: Chapter.xml:336
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
#. Tag: para
-#: Chapter.xml:46
+#: Chapter.xml:337
#, no-c-format
msgid ""
"If the <literal>-test</literal> flag is used with the Recovery Manager then "
@@ -290,19 +1097,19 @@
"すると “Ready” メッセージが表示されます。"
#. Tag: command
-#: Chapter.xml:47
+#: Chapter.xml:338
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
#. Tag: title
-#: Chapter.xml:50
+#: Chapter.xml:341
#, no-c-format
msgid "Configuring the Recovery Manager"
msgstr "Recovery Manager を設定する"
#. Tag: para
-#: Chapter.xml:51
+#: Chapter.xml:342
#, no-c-format
msgid ""
"The RecoveryManager reads the properties defined in the <filename>arjuna."
@@ -321,7 +1128,7 @@
"書きします。 ほとんどのエントリは Recovery Manager 固有となります。"
#. Tag: para
-#: Chapter.xml:52
+#: Chapter.xml:343
#, no-c-format
msgid ""
"A default version of <filename>RecoveryManager.properties</filename> is "
@@ -335,16 +1142,16 @@
"ストリビューションに同梱されます。 おそらくデバッグ追跡フィールド (以下参"
"照、 「出力」) 以外は変更することなく使用できます。 これ以降、 本セクションで"
"はプロパティを他の値に設定する上での問題について説明していきます (ファイルの"
-"デフォルトバージョンで表されている順序)。"
+"デフォルトバージョンで表示されている順序)。"
#. Tag: title
-#: Chapter.xml:54
+#: Chapter.xml:345
#, no-c-format
msgid "Output"
msgstr "出力"
#. Tag: para
-#: Chapter.xml:55
+#: Chapter.xml:346
#, no-c-format
msgid ""
"It is likely that installations will want to have some form of output from "
@@ -360,13 +1167,13 @@
"トールが RecoveryManager からの出力をなんらかの形式で必要とする可能性がありま"
"す。 RecoveryManager は Arjuna Common Logging Framework (CLF) によって提供さ"
"れるログ追跡メカニズムを使用します。 これは Jakarta log4j や JDK 1.4 ロギン"
-"グ API など既存のロギング API 間に存在する違いを隠す高度なレベルのインター"
+"グ API など既存のロギング API 間に存在する相違を隠す高度なレベルのインター"
"フェースを提供します。 CLF は Apache Commons Logging フレームワーク経由ですべ"
"てのロギングをインダイレクトするので、 設定はそのフレームワークを通して発生す"
"るとみなされます。"
#. Tag: para
-#: Chapter.xml:58
+#: Chapter.xml:349
#, no-c-format
msgid ""
"With the CLF applications make logging calls on logger objects. Loggers may "
@@ -386,7 +1193,7 @@
"< FATAL。"
#. Tag: para
-#: Chapter.xml:61
+#: Chapter.xml:352
#, no-c-format
msgid ""
"The CLF provides an extension to filter logging messages according to finer "
@@ -400,7 +1207,7 @@
"るため指定できる追加の条件になります。"
#. Tag: para
-#: Chapter.xml:67
+#: Chapter.xml:358
#, no-c-format
msgid ""
"These conditions are applied if and only the DEBUG level is enabled and the "
@@ -410,14 +1217,14 @@
"求がデバッグの粒度を指定している場合にのみ適用されます。"
#. Tag: para
-#: Chapter.xml:71
+#: Chapter.xml:362
#, no-c-format
msgid "When enabled, Debugging is filtered conditionally on three variables:"
msgstr ""
"有効になると、 Debugging は次の 3 つの変数の条件付きでフィルタされます。"
#. Tag: para
-#: Chapter.xml:74
+#: Chapter.xml:365
#, no-c-format
msgid ""
"Debugging level: this is where the log request with the DEBUG Level is "
@@ -427,7 +1234,7 @@
"ンストラクタや基本的なメソッド。"
#. Tag: para
-#: Chapter.xml:77
+#: Chapter.xml:368
#, no-c-format
msgid ""
"Visibility level: the visibility of the constructor, method, etc. that "
@@ -437,7 +1244,7 @@
"す。"
#. Tag: para
-#: Chapter.xml:80
+#: Chapter.xml:371
#, no-c-format
msgid ""
"Facility code: for instance the package or sub-module within which debugging "
@@ -447,7 +1254,7 @@
"ジュールです。 例、 オブジェクトストアなど。"
#. Tag: para
-#: Chapter.xml:83
+#: Chapter.xml:374
#, no-c-format
msgid ""
"According to these variables the CLF defines three interfaces. A particular "
@@ -469,7 +1276,7 @@
"Transactions で使用される詳細なデバッグの値は以下のように定義されます。"
#. Tag: para
-#: Chapter.xml:84
+#: Chapter.xml:375
#, no-c-format
msgid ""
"Debugging level – JBoss Transactions uses the default values defined in the "
@@ -479,7 +1286,7 @@
"util.logging.DebugLevel</classname> で定義されるデフォルトの値を使用します。"
#. Tag: para
-#: Chapter.xml:87
+#: Chapter.xml:378
#, no-c-format
msgid ""
"NO_DEBUGGING: No diagnostics. A logger object assigned with this values "
@@ -489,7 +1296,7 @@
"はすべてのデバッグ要求を破棄します。"
#. Tag: para
-#: Chapter.xml:90
+#: Chapter.xml:381
#, no-c-format
msgid ""
"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
@@ -501,73 +1308,73 @@
"一致する場合にすべてのデバッグ要求を許可します。"
#. Tag: para
-#: Chapter.xml:93
+#: Chapter.xml:384
#, no-c-format
msgid "Additional Debugging Values are:"
msgstr "追加のデバッグ値は次の通りです。"
#. Tag: para
-#: Chapter.xml:96
+#: Chapter.xml:387
#, no-c-format
msgid "CONSTRUCTORS: Diagnostics from constructors."
msgstr "CONSTRUCTORS: コンストラクタからの診断です。"
#. Tag: para
-#: Chapter.xml:99
+#: Chapter.xml:390
#, no-c-format
msgid "DESTRUCTORS: Diagnostics from finalizers."
msgstr "DESTRUCTORS: ファイナライザからの診断です。"
#. Tag: para
-#: Chapter.xml:102
+#: Chapter.xml:393
#, no-c-format
msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
msgstr "CONSTRUCT_AND_DESTRUCT: コンストラクタとファイナライザからの診断です。"
#. Tag: para
-#: Chapter.xml:105
+#: Chapter.xml:396
#, no-c-format
msgid "FUNCTIONS: Diagnostics from functions."
msgstr "FUNCTIONS: 関数からの診断です。"
#. Tag: para
-#: Chapter.xml:108
+#: Chapter.xml:399
#, no-c-format
msgid "OPERATORS: Diagnostics from operators, such as equals."
msgstr "OPERATORS: イコールなどの演算子からの診断です。"
#. Tag: para
-#: Chapter.xml:111
+#: Chapter.xml:402
#, no-c-format
msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
msgstr "FUNCS_AND_OPS: 関数と演算からの診断です。"
#. Tag: para
-#: Chapter.xml:114
+#: Chapter.xml:405
#, no-c-format
msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
msgstr "ALL_NON_TRIVIAL: non-trivial の全演算からの診断です。"
#. Tag: para
-#: Chapter.xml:117
+#: Chapter.xml:408
#, no-c-format
msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
msgstr "TRIVIAL_FUNCS: trivial 関数からの診断です。"
#. Tag: para
-#: Chapter.xml:120
+#: Chapter.xml:411
#, no-c-format
msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
msgstr "TRIVIAL_OPERATORS: trivial 演算と演算子からの診断です。"
#. Tag: para
-#: Chapter.xml:123
+#: Chapter.xml:414
#, no-c-format
msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
msgstr "ALL_TRIVIAL: すべての trivial 演算からの診断です。"
#. Tag: para
-#: Chapter.xml:126
+#: Chapter.xml:417
#, no-c-format
msgid ""
"Visibility level – JBoss Transactions uses the default values defined in the "
@@ -578,43 +1385,43 @@
"す。"
#. Tag: para
-#: Chapter.xml:129
+#: Chapter.xml:420
#, no-c-format
msgid "VIS_NONE: No Diagnostic"
msgstr "VIS_NONE: 診断なしです。"
#. Tag: para
-#: Chapter.xml:132
+#: Chapter.xml:423
#, no-c-format
msgid "VIS_PRIVATE : only from private methods."
msgstr "VIS_PRIVATE : プライベートメソッドからのみです。"
#. Tag: para
-#: Chapter.xml:135
+#: Chapter.xml:426
#, no-c-format
msgid "VIS_PROTECTED only from protected methods."
msgstr "VIS_PROTECTED 保護メソッドからのみです。"
#. Tag: para
-#: Chapter.xml:138
+#: Chapter.xml:429
#, no-c-format
msgid "VIS_PUBLIC only from public methods."
msgstr "VIS_PUBLIC パブリックメソッドからのみです。"
#. Tag: para
-#: Chapter.xml:141
-#, fuzzy, no-c-format
+#: Chapter.xml:432
+#, no-c-format
msgid "VIS_PACKAGE only from package methods."
-msgstr "VIS_PUBLIC パブリックメソッドからのみです。"
+msgstr "VIS_PACKAGE パッケージメソッドからのみです。"
#. Tag: para
-#: Chapter.xml:144
+#: Chapter.xml:435
#, no-c-format
msgid "VIS_ALL: Full Diagnostic"
-msgstr "VIS_ALL: 完全診断です。"
+msgstr "VIS_ALL: 総合診断です。"
#. Tag: para
-#: Chapter.xml:147
+#: Chapter.xml:438
#, no-c-format
msgid ""
"Facility Code – JBoss Transactions uses the following values defined in the "
@@ -625,49 +1432,49 @@
"す。"
#. Tag: para
-#: Chapter.xml:150
+#: Chapter.xml:441
#, no-c-format
msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
msgstr "FAC_ATOMIC_ACTION = 0x0000001 (アトミックアクションコアモジュール)。"
#. Tag: para
-#: Chapter.xml:153
+#: Chapter.xml:444
#, no-c-format
msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
msgstr "FAC_BUFFER_MAN = 0x00000004 (状態管理 (バッファ) クラス)。"
#. Tag: para
-#: Chapter.xml:156
+#: Chapter.xml:447
#, no-c-format
msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
msgstr "FAC_ABSTRACT_REC = 0x00000008 (抽出記録)。"
#. Tag: para
-#: Chapter.xml:159
+#: Chapter.xml:450
#, no-c-format
msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
msgstr "FAC_OBJECT_STORE = 0x00000010 (オブジェクトストア実装)。"
#. Tag: para
-#: Chapter.xml:162
+#: Chapter.xml:453
#, no-c-format
msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
msgstr "FAC_STATE_MAN = 0x00000020 (状態管理と StateManager)。"
#. Tag: para
-#: Chapter.xml:165
+#: Chapter.xml:456
#, no-c-format
msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
msgstr "FAC_SHMEM = 0x00000040 (共有メモリ実装クラス)。"
#. Tag: para
-#: Chapter.xml:168
+#: Chapter.xml:459
#, no-c-format
msgid "FAC_GENERAL = 0x00000080 (general classes)."
msgstr "FAC_GENERAL = 0x00000080 (汎用クラス)。"
#. Tag: para
-#: Chapter.xml:171
+#: Chapter.xml:462
#, no-c-format
msgid ""
"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
@@ -677,19 +1484,19 @@
"とレース)。"
#. Tag: para
-#: Chapter.xml:174
+#: Chapter.xml:465
#, no-c-format
msgid "FAC_THREADING = 0x00002000 (threading classes)."
msgstr "FAC_THREADING = 0x00002000 (スレッディングクラス)。"
#. Tag: para
-#: Chapter.xml:177
+#: Chapter.xml:468
#, no-c-format
msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
msgstr "AC_JDBC = 0x00008000 (JDBC 1.0 および 2.0 サポート)。"
#. Tag: para
-#: Chapter.xml:180
+#: Chapter.xml:471
#, no-c-format
msgid ""
"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
@@ -697,7 +1504,7 @@
"FAC_RECOVERY_NORMAL = 0x00040000 (クラッシュリカバリマネージャの通常出力)。"
#. Tag: para
-#: Chapter.xml:183
+#: Chapter.xml:474
#, no-c-format
msgid ""
"To ensure appropriate output, it is necessary to set some of the finer debug "
@@ -709,7 +1516,7 @@
"ジュールで発行されるロギングメッセージを有効にする必要があります。"
#. Tag: para
-#: Chapter.xml:184
+#: Chapter.xml:475
#, no-c-format
msgid ""
"Messages describing the start and the periodical behavior made by the "
@@ -727,7 +1534,7 @@
"す。"
#. Tag: programlisting
-#: Chapter.xml:186
+#: Chapter.xml:477
#, no-c-format
msgid ""
"<!-- Common logging related properties. -->\n"
@@ -749,7 +1556,7 @@
" value=\"0xffffffff\"/>"
#. Tag: para
-#: Chapter.xml:189
+#: Chapter.xml:480
#, no-c-format
msgid ""
"Two logger objects are provided, one manages I18N messages and a second does "
@@ -759,7 +1566,7 @@
"目は管理しません。"
#. Tag: para
-#: Chapter.xml:192
+#: Chapter.xml:483
#, no-c-format
msgid ""
"Setting the normal recovery messages to the INFO level allows the "
@@ -778,13 +1585,13 @@
"メッセージしか生成しないということになります。"
#. Tag: title
-#: Chapter.xml:196
+#: Chapter.xml:487
#, no-c-format
msgid "Periodic Recovery"
msgstr "定期的なリカバリ"
#. Tag: para
-#: Chapter.xml:197
+#: Chapter.xml:488
#, no-c-format
msgid ""
"The RecoveryManager scans the ObjectStore and other locations of "
@@ -805,7 +1612,7 @@
"RecoveryManager property ファイルにあるプロパティを使用します。"
#. Tag: para
-#: Chapter.xml:198
+#: Chapter.xml:489
#, no-c-format
msgid ""
"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
@@ -835,7 +1642,7 @@
"イテムがリカバリの候補である可能性があります。"
#. Tag: para
-#: Chapter.xml:199
+#: Chapter.xml:490
#, no-c-format
msgid ""
"An attempt, by the RecoveryManager, to recover a transaction that is still "
@@ -863,7 +1670,7 @@
"RecoveryManager の役割となります。)"
#. Tag: para
-#: Chapter.xml:200
+#: Chapter.xml:491
#, no-c-format
msgid ""
"It is clearly important to set the interval periods appropriately. The total "
@@ -899,7 +1706,7 @@
"すことです。"
#. Tag: para
-#: Chapter.xml:203
+#: Chapter.xml:494
#, no-c-format
msgid ""
"In previous versions of JBoss Transactions there was no contact mechanism, "
@@ -911,7 +1718,7 @@
"ければなりませんでした。 3.0 からはこのようなリスクがなくなります。"
#. Tag: para
-#: Chapter.xml:206
+#: Chapter.xml:497
#, no-c-format
msgid ""
"Two recovery modules (implementations of the <classname>com.arjuna.ats."
@@ -937,7 +1744,7 @@
"されます。 したがって、 "
#. Tag: programlisting
-#: Chapter.xml:208
+#: Chapter.xml:499
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
@@ -953,13 +1760,13 @@
" com.arjuna.ats.txoj.recovery.TORecoveryModule"
#. Tag: title
-#: Chapter.xml:211
+#: Chapter.xml:502
#, no-c-format
msgid "Expired entry removal"
msgstr "失効エントリの削除"
#. Tag: para
-#: Chapter.xml:212
+#: Chapter.xml:503
#, no-c-format
msgid ""
"The operation of the recovery subsystem will cause some entries to be made "
@@ -988,20 +1795,20 @@
"ティの値としてクラス名を与えることでロードされます。 RecoveryManager はプロパ"
"ティ <classname>com.arjuna.ats.arjuna.recovery.expiryScanInterval</"
"classname> で確定される間隔でロードされる Expiry Scanner の各実装で "
-"<command>scan()</command> メソッドをコールします。この値は時間単位で与えま"
+"<command>scan()</command> メソッドを呼び出します。この値は時間単位で与えま"
"す。 デフォルトは 12 時間です。 <classname>expiryScanInterval</classname> の"
"値がゼロは失効のスキャンを抑制します。 与えられる値が整数である場合は、 "
"RecoveryManager が起動したときに最初のスキャンが行われます。 値が負数の場"
"合、 最初のスキャンは最初の間隔まで遅延されます (絶対値を使用)。"
#. Tag: para
-#: Chapter.xml:213
+#: Chapter.xml:504
#, no-c-format
msgid "The kinds of item that are scanned for expiry are:"
msgstr "失効のスキャンが行われるアイテムの種類は次の通りです。"
#. Tag: para
-#: Chapter.xml:214
+#: Chapter.xml:505
#, no-c-format
msgid ""
"TransactionStatusManager items : one of these is created by every "
@@ -1023,13 +1830,13 @@
"JBoss Transactions 使用プロセスの寿命より長くなければなりません。"
#. Tag: para
-#: Chapter.xml:215
+#: Chapter.xml:506
#, no-c-format
msgid "The Expiry Scanner properties for these are:"
msgstr "これらの Expiry Scanner プロパティは次の通りです。"
#. Tag: programlisting
-#: Chapter.xml:217
+#: Chapter.xml:508
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
@@ -1041,155 +1848,316 @@
"ExpiredTransactionStatusManagerScanner"
#. Tag: title
-#: Chapter.xml:220
+#: Chapter.xml:511
#, no-c-format
-msgid "Errors and Exceptions"
-msgstr "エラーと例外"
+msgid "Selecting the JTA implementation"
+msgstr "JTA 実装の選択"
#. Tag: para
-#: Chapter.xml:221
+#: Chapter.xml:512
#, 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."
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
msgstr ""
-"本セクションでは、 トランザクショナルアプリケーションの間に投げられたり報告さ"
-"れる可能性のあるエラーや例外のタイプについて説明し、 その原因により起こりそう"
-"な兆候をあげておきます。"
+"JTA 実装の２つの種類が現在提供されており、同じインターフェイスでアクセスが で"
+"きます。以下のものがあります:"
#. Tag: para
-#: Chapter.xml:224
+#: Chapter.xml:515
#, 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."
+"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 ""
-"NO_MEMORY: アプリケーションの空きメモリがなくなり "
-"(<classname>OutOfMemoryError</classname> が投げられる)、 JBoss Transactions "
-"が例外を再度投げるまでになんらかのクリーンアップを試行しています (ガーベッジ"
-"コレクションを実行)。 これはおそらく一時的な問題で呼び出しを再試行すると成功"
-"するはずです。"
+"その１つは純粋にローカルの JTA です。これは非配布の JTA トランザクションのみ"
+"を 実行できるようにします。これは JBoss Transactions 製品で使用可能な唯一の "
+"バージョンです。"
#. Tag: para
-#: Chapter.xml:227
+#: Chapter.xml:518
#, 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."
+"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 ""
+"もう１つは、リモートで、CORBA ベースの JTA です。これは、配布されている JTA "
+"トランザクションを実行できるようにします。このバージョンは ArjunaJTS 製品と "
+"一緒にのみ取得可能でサポート付きの CORBA ORB を必要とします。"
#. Tag: para
-#: Chapter.xml:230
+#: Chapter.xml:522
#, 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."
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
msgstr ""
+"これらの両方の実装は、JBoss Transactions で提供されているトランザクショナル "
+"JDBC と完全な互換性があります。"
#. Tag: para
-#: Chapter.xml:233
+#: Chapter.xml:525
#, 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."
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
msgstr ""
+"ローカル JTA 実装を選択するためには、以下の手順を実行する必要が あります:"
#. Tag: para
-#: Chapter.xml:236
+#: Chapter.xml:528
#, 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."
+"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 ""
+"プロパティ <literal>com.arjuna.ats.jta.jtaTMImplementation</literal> が "
+"<literal>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</literal> にセットしてあることを確認します。"
+#. Tag: para
+#: Chapter.xml:531
+#, 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 ""
+"プロパティ <literal>com.arjuna.ats.jta.jtaUTImplementation</literal> が "
+"<literal>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple</literal> にセットしてあることを確認します。"
+
+#. Tag: para
+#: Chapter.xml:535
+#, 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 ""
+"これらのセッティングはそれぞれのプロパティ用にデフォルトであり、ローカルの 実"
+"装が要求されている場合は、それらの指定は必要ではありません。"
+
#. Tag: title
-#: Chapter.xml:241
+#: Chapter.xml:542
#, no-c-format
-msgid "Selecting the JTA implementation"
+msgid "ORB specific configurations"
msgstr ""
+#. Tag: title
+#: Chapter.xml:544
+#, no-c-format
+msgid "<title>JacORB</title>"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:242
+#: Chapter.xml:545
#, no-c-format
msgid ""
-"Two variants of the JTA implementation are now provided and accessible "
-"through the same interface. These are:"
+"For JacORB to function correctly it is necessary to ensure there is a valid "
+"<filename>jacorb.properties</filename> or <filename>.jacorb_properties</"
+"filename> file in one of the following places:"
msgstr ""
#. Tag: para
-#: Chapter.xml:245
+#: Chapter.xml:551
#, no-c-format
+msgid "The classpath."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:556
+#, 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."
+"The home directory of the user running the JBoss Transaction Service. The "
+"home directory is retrieved using <code>System.getProperty( “user.home” );</"
+"code>"
msgstr ""
#. Tag: para
-#: Chapter.xml:248
+#: Chapter.xml:561
#, no-c-format
+msgid "The current directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:566
+#, 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."
+"The <filename>lib</filename> directory of the JDK used to run your "
+"application. This is retrieved using <code>System.getProperty( “java.home” );"
+"</code>"
msgstr ""
#. Tag: para
-#: Chapter.xml:252
+#: Chapter.xml:571
#, no-c-format
msgid ""
-"both of these implementations are fully compatible with the transactional "
-"JDBC driver provided with JBoss Transactions."
+"The above places are searched in the order given. A template "
+"<filename>jacorb.properties</filename> file can be found in the JacORB "
+"installation directory."
msgstr ""
#. Tag: para
-#: Chapter.xml:255
+#: Chapter.xml:574
#, no-c-format
msgid ""
-"In order to select the local JTA implementation it is necessary to perform "
-"the following steps:"
+"Within the JacORB properties file there are two important properties which "
+"must be tailored to suit your application, they are:"
msgstr ""
+#. Tag: property
+#: Chapter.xml:580
+#, no-c-format
+msgid "jacorb.poa.thread_pool_max"
+msgstr ""
+
+#. Tag: property
+#: Chapter.xml:585
+#, no-c-format
+msgid "jacorb.poa.thread_pool_min"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:258
+#: Chapter.xml:589
#, 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>."
+"These properties specify the minimum and maximum number of request "
+"processing threads that JacORB will use in its thread pool. If there aren’t "
+"a sufficient number of threads available in this thread pool then the "
+"application may appear to become deadlocked. For more information on "
+"configuring JacORB please reference the JacORB documentation."
msgstr ""
#. Tag: para
-#: Chapter.xml:261
+#: Chapter.xml:593
#, 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>."
+"JacORB comes with its own implementation of the classes defined in the "
+"<filename>CosTransactions.idl</filename> file. Unfortunately these are "
+"incompatible with the version shipped with JBossTS. Therefore, it is "
+"important that the JBossTS jar files appear in the <code>CLASSPATH</code> "
+"before any JacORB jars."
msgstr ""
#. Tag: para
-#: Chapter.xml:265
+#: Chapter.xml:597
#, 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."
+"When running the recovery manager it is important that it always uses the "
+"same well known port for each machine on which it runs. You should not use "
+"the OAPort property provided by JacORB unless the recovery manager has its "
+"own <filename>jacorb.properties</filename> file or this is provided on the "
+"command line when starting the recovery manager. If the recovery manager and "
+"other components of JBossTS share the same <filename>jacorb.properties</"
+"filename> file, then you should use the <filename>com.arjuna.ats.jts."
+"recoveryManagerPort</filename> and <filename>com.arjuna.ats.jts."
+"recoveryManagerAddress</filename> properties."
msgstr ""
-#~ msgid ""
-#~ "VIS_JBoss_Transactions_Administrators_Guide only from package methods."
-#~ msgstr ""
-#~ "VIS_JBoss_Transactions_Administrators_Guide パッケージメソッドからのみで"
-#~ "す。"
+#. Tag: title
+#: Chapter.xml:603
+#, no-c-format
+msgid "Initializing JBossTS applications"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:604
+#, no-c-format
+msgid ""
+"It is important that JBossTS is correctly initialized prior to any "
+"application object being created. In order to guarantee this, the programmer "
+"should use the <methodname>ORB_init</methodname> and <methodname>create_POA</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:609
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr "エラーと例外"
+
+#. Tag: para
+#: Chapter.xml:610
+#, 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:613
+#, 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 ""
+"NO_MEMORY: アプリケーションの空きメモリがなくなり "
+"(<classname>OutOfMemoryError</classname> が投げられる)、 JBoss Transactions "
+"が例外を再度投げるまでになんらかのクリーンアップを試行しています (ガーベッジ"
+"コレクションを実行)。 これはおそらく一時的な問題で呼び出しを再試行すると成功"
+"するはずです。"
+
+#. Tag: para
+#: Chapter.xml:616
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: トランザクションシステムがシャッ"
+"トダウンを しなければならない状態のエラーが発生しました。このエラーが送出され"
+"るまでは トランザクションサービスは、全ての実行中トランザクションがロールバッ"
+"クされたことを 確認します。エラーに遭遇した場合は、アプリケーションが片付けを"
+"して終了することになります。 それ以降に作業が試行されると、アプリケーションの"
+"整合性は害を受けます。"
+
+#. Tag: para
+#: Chapter.xml:619
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: 現在のライセンスに適合しない "
+"方法でトランザクションサービスの使用が試行されました。トランザクションサービ"
+"スは 既存のあるいは新規のトランザクションに対しこれ以上の進行を許可しません。"
+
+#. Tag: para
+#: Chapter.xml:622
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: トランザクションサービス"
+"が Object Store の使用を試みた時にエラーが発生しました。これ以上の進行は不可"
+"能です。"
+
+#. Tag: para
+#: Chapter.xml:625
+#, 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 ""
+"アクセス問題に関する Object Store 状態警告は通常のクラッシュリカバリの 実行中"
+"に発生します。これは同じトランザクションでのリカバリの複数並行試行の 結果で"
+"す。これは無視することができます。"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Feedback.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Feedback.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Feedback.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Feedback.po to Japanese
+# translation of Preface.po to Japanese
# Language ja-JP translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Noriko Mizumoto <noriko at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Feedback\n"
+"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-05-12 00:15+0000\n"
-"PO-Revision-Date: 2008-05-15 12:38+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-05-15 13:44+1000\n"
"Last-Translator: Noriko Mizumoto <noriko at redhat.com>\n"
"Language-Team: Japanese <fedora-trans-ja at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -34,5 +34,11 @@
"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 "本ガイドに誤植があった場合、 また本ガイドの改善案に関するご意見をお寄せ頂く場合、 <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> より Product: JBoss Enterprise Application Platform、 Version: <replaceable><version></replaceable>、 Component: <emphasis>Doc</emphasis> にてご報告頂ければ幸いです。 ドキュメントの改善案についてはできるだけ詳細にお願いいたします。 エラーの報告を頂く場合は、 該当するセクション番号および前後の文脈を含めてお知らせ頂けると発見しやすくなります。"
-
+msgstr ""
+"本ガイドに誤植があった場合、 また本ガイドの改善案に関するご意見をお寄せ頂く場"
+"合、 <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> よ"
+"り Product: JBoss Enterprise Application Platform、 Version: "
+"<replaceable><version></replaceable>、 Component: <emphasis>Doc</"
+"emphasis> にてご報告頂ければ幸いです。 ドキュメントの改善案についてはできるだ"
+"け詳細にお願いいたします。 エラーの報告を頂く場合は、 該当するセクション番号"
+"および前後の文脈を含めてお知らせ頂けると発見しやすくなります。"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Preface.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Preface.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-05-12 00:15+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
"PO-Revision-Date: 2008-05-15 13:44+1000\n"
"Last-Translator: Noriko Mizumoto <noriko at redhat.com>\n"
"Language-Team: Japanese <fedora-trans-ja at redhat.com>\n"
@@ -34,7 +34,9 @@
msgid ""
"The Administration Guide contains information on how to administer JBoss "
"Transactions API 4.2.3."
-msgstr "管理ガイドでは JBoss Transactions API 4.2.3 を管理する方法について説明しています。"
+msgstr ""
+"管理ガイドでは JBoss Transactions API 4.2.3 を管理する方法について説明してい"
+"ます。"
#. Tag: title
#: Preface.xml:17
@@ -48,7 +50,9 @@
msgid ""
"This guide is most relevant to engineers who are responsible for "
"administration of JBoss Transactions API 4.2.3 installations."
-msgstr "JBoss Transactions API 4.2.3 のインストールを管理するエンジニアの方に最適なガイドです。"
+msgstr ""
+"JBoss Transactions API 4.2.3 のインストールを管理するエンジニアの方に最適なガ"
+"イドです。"
#. Tag: title
#: Preface.xml:21
@@ -64,7 +68,11 @@
"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 "JBoss Transactions を管理するにはまず JBoss Transactions が多くのトランザクション機能で ArjunaCore に依存していることを理解しておくことが必要になります。 このため ArjunaCore 管理ガイドをよく読んでから JBoss Transactions の管理を開始するのが重要となります。"
+msgstr ""
+"JBoss Transactions を管理するにはまず JBoss Transactions が多くのトランザク"
+"ション機能で ArjunaCore に依存していることを理解しておくことが必要になりま"
+"す。 このため ArjunaCore 管理ガイドをよく読んでから JBoss Transactions の管理"
+"を開始するのが重要となります。"
#. Tag: title
#: Preface.xml:25
@@ -85,7 +93,10 @@
"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 "第 1 章、 JBoss Transactions の管理 では JBoss Transactions の管理方法について説明しています。 主に純粋なローカルまたはリモートなど JTA 実装の種類の選択についてです (配信トランザクションの許可)。"
+msgstr ""
+"第 1 章、 JBoss Transactions の管理 では JBoss Transactions の管理方法につい"
+"て説明しています。 主に純粋なローカルまたはリモートなど JTA 実装の種類の選択"
+"についてです (配信トランザクションの許可)。"
#. Tag: title
#: Preface.xml:34
@@ -99,7 +110,9 @@
msgid ""
"In addition to this guide, the following guides are available in the JBoss "
"Transactions API 4.2.3 documentation set:"
-msgstr "本ガイドの他、 次のようなガイドが JBoss Transactions API 4.2.3 ドキュメントセットにあります。"
+msgstr ""
+"本ガイドの他、 次のようなガイドが JBoss Transactions API 4.2.3 ドキュメント"
+"セットにあります。"
#. Tag: para
#: Preface.xml:38
@@ -107,7 +120,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
"information about JBoss Transactions API 4.2.3."
-msgstr "JBoss Transactions API 4.2.3 Release Notes (リリースノート)、 JBoss Transactions API 4.2.3 に関する最新情報を提供します。"
+msgstr ""
+"JBoss Transactions API 4.2.3 Release Notes (リリースノート)、 JBoss "
+"Transactions API 4.2.3 に関する最新情報を提供します。"
#. Tag: para
#: Preface.xml:41
@@ -115,7 +130,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
"instructions for installing JBoss Transactions API 4.2.3."
-msgstr "JBoss Transactions API 4.2.3 Installation Guide (インストールガイド)、 JBoss Transactions API 4.2.3 のインストール方法について説明しています。"
+msgstr ""
+"JBoss Transactions API 4.2.3 Installation Guide (インストールガイド)、 JBoss "
+"Transactions API 4.2.3 のインストール方法について説明しています。"
#. Tag: para
#: Preface.xml:44
@@ -123,5 +140,6 @@
msgid ""
"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
"writing applications."
-msgstr "JBoss Transactions API 4.2.3 Programmer’s Guide (プログラマーガイド)、 アプリケーションの記述方法についてのガイダンスになります。"
-
+msgstr ""
+"JBoss Transactions API 4.2.3 Programmer’s Guide (プログラマーガイド)、 アプリ"
+"ケーションの記述方法についてのガイダンスになります。"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Revision_History.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/ja-JP/Revision_History.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Revision_History.po to Japanese
+# translation of Preface.po to Japanese
# Language ja-JP translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Noriko Mizumoto <noriko at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Revision_History\n"
+"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-05-12 00:15+0000\n"
-"PO-Revision-Date: 2008-05-15 12:38+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-05-15 13:44+1000\n"
"Last-Translator: Noriko Mizumoto <noriko at redhat.com>\n"
"Language-Team: Japanese <fedora-trans-ja at redhat.com>\n"
"MIME-Version: 1.0\n"
@@ -16,9 +16,14 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "リビジョン履歴"
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
msgstr "<firstname></firstname> <surname></surname> <email></email>"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Author_Group.pot
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Author_Group.pot 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Author_Group.pot 2009-09-17 02:36:56 UTC (rev 29385)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-07-14 01:26+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+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"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Book_Info.pot
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Book_Info.pot 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Book_Info.pot 2009-09-17 02:36:56 UTC (rev 29385)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-07-14 01:26+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+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"
@@ -17,14 +17,13 @@
#. Tag: title
#: Book_Info.xml:6
#, no-c-format
-msgid "JBoss Transactions Administrators Guide CP06"
+msgid "JBoss Transactions Administrators Guide"
msgstr ""
#. Tag: subtitle
#: Book_Info.xml:10
#, no-c-format
-msgid ""
-"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 6"
+msgid "for Use with JBoss Enterprise Application Platform 5.0"
msgstr ""
#. Tag: para
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Chapter.pot
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Chapter.pot 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Chapter.pot 2009-09-17 02:36:56 UTC (rev 29385)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-07-14 01:26+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+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"
@@ -74,7 +74,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:19
+#: Chapter.xml:19 Chapter.xml:62
#, no-c-format
msgid ""
"Object store management is critically important to the transaction service."
@@ -83,13 +83,74 @@
#. Tag: title
#: Chapter.xml:24
#, no-c-format
-msgid "ObjectStore management"
+msgid "Starting and Stopping the transaction manager"
msgstr ""
#. Tag: para
#: Chapter.xml:25
#, no-c-format
msgid ""
+"By default the transaction manager starts up in an active state such that "
+"new transactions can be created immediately. If you wish to have more "
+"control over this it is possible to set the <property>com.arjuna.ats.arjuna."
+"coordinator.startDisabled</property> configuration option to <literal>YES</"
+"literal>, in which case no transactions can be created until the transaction "
+"manager is enabled (via a call to <methodname>TxControl.enable</methodname>)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:28
+#, no-c-format
+msgid ""
+"It is possible to stop the creation of new transactions at any time by "
+"calling <methodname>TxControl.disable</methodname>. Transactions that are "
+"currently executing will not be affected. By default recovery will be "
+"allowed to continue and the transaction system will still be available to "
+"manage recovery requests from other instances in a distributed environment. "
+"(See the Failure Recovery Guide for further details). However, if you wish "
+"to disable recovery as well as remove any resources it maintains, then you "
+"can pass true to <methodname>TxControl.disable</methodname>; the default is "
+"to use <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"If you wish to shut the system down completely then it may also be necessary "
+"to terminate the background transaction reaper (see the Programmers Guide "
+"for information about what the reaper does.) In order to do this you may "
+"want to first prevent the creation of new transactions (if you are not "
+"creating transactions with timeouts then this step is not necessary) using "
+"<methodname>TxControl.disable</methodname>. Then you should call "
+"<methodname>TransactionReaper.terminate</methodname>. This method takes a "
+"boolean parameter: if true then the method will wait for the normal timeout "
+"periods associated with any transactions to expire before terminating the "
+"transactions; if false then transactions will be forced to terminate "
+"(rollback or have their outcome set such that they can only ever rollback) "
+"immediately."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"If you intent to restart the recovery manager later after having terminated "
+"it then you <emphasis>must</emphasis> use the <methodname>terminate</"
+"methodname> method with <property>asynchronous behavior</property> set to "
+"<literal>false</literal> when shutting down the recovery manager."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:40
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:41
+#, 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 "
@@ -104,14 +165,725 @@
"the object store assuming it is an exclusive resource."
msgstr ""
+#. Tag: para
+#: Chapter.xml:42
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBossTS software. There are "
+"a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:47
+#, no-c-format
+msgid ""
+"The present implementation of the JBossTS system provides no security or "
+"protection for data. It is recommended that the objects stored in the "
+"JBossTS are owned by user arjuna. The Object Store and Object Manager "
+"facilities make no attempt to enforce even the limited form of protection "
+"that Unix and 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:52
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> 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:57
+#, 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 JBossTS software can neither detect "
+"nor correct references to old object state by new operation versions or vice "
+"versa."
+msgstr ""
+
#. Tag: title
-#: Chapter.xml:28
+#: Chapter.xml:70
#, no-c-format
+msgid "OTS and J2EE Transaction service management"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:72
+#, no-c-format
+msgid "Starting the run-time system"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:73
+#, no-c-format
+msgid ""
+"The JBossTS run-time support consists of run-time packages and the OTS "
+"transaction manager server. By default JBossTS does not use a separate "
+"transaction manager server: transaction managers are co-located with each "
+"application process to improve performance and improve application fault-"
+"tolerance (the application is no longer dependant upon another service in "
+"order to function correctly)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:76
+#, no-c-format
+msgid ""
+"When running applications which require a separate transaction manager, you "
+"must set the <varname>com.arjuna.ats.jts.transactionManager</varname> "
+"environment variable to have the value <literal>yes</literal>. The system "
+"will then locate the transaction manager server in a manner specific to the "
+"ORB being used. The server can be located in a number of ways: by being "
+"registered with a name server, added to the ORB’s initial references, via a "
+"JBossTS specific references file, or by the ORB’s specific location "
+"mechanism (if applicable)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:79
+#, no-c-format
+msgid ""
+"It is possible to override the default registration mechanism by using the "
+"<varname>com.arjuna.orbportability.resolveService</varname> environment "
+"variable. This can have one of the following values:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"<literal>CONFIGURATION_FILE</literal>: the default, this causes the system "
+"to use the <filename>CosServices.cfg</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:89
+#, no-c-format
+msgid ""
+"<literal>NAME_SERVICE</literal>: JBossTS will attempt to use a name service "
+"to register the transaction factory. If this is not supported, an exception "
+"will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:94
+#, no-c-format
+msgid ""
+"<literal>BIND_CONNECT</literal>: JBossTS will use the ORB-specific bind "
+"mechanism. If this is not supported, an exception will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid ""
+"<literal>RESOLVE_INITIAL_REFERENCES</literal>: JBossTS will attempt to "
+"register the transaction service with the ORBs initial service references."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid ""
+"This may not be supported on all ORBs. An exception will be thrown in that "
+"case and another option will have to be used."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:110
+#, no-c-format
+msgid "<title>OTS configuration file</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid ""
+"Similar to the resolve_initial_references, JBossTS supports an initial "
+"reference file where references for specific services can be stored and used "
+"at runtime. The file, CosServices.cfg, consists of two columns: the service "
+"name (in the case of the OTS server TransactionService) and the IOR, "
+"separated by a single space. CosServices.cfg normally resides in the etc "
+"directory of the JBossTS installation; the actual location is determined at "
+"runtime by searching the CLASSPATH for an old copy of the file resident "
+"within an etc directory, or, if one is not found, the location of the "
+"TransactionService properties file directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:115
+#, no-c-format
+msgid ""
+"The OTS server will automatically register itself in this file (creating it "
+"if necessary) if this option is being used. Stale information is also "
+"automatically removed. Machines which wish to share the same transaction "
+"server should have access to (or a copy of) this file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:118
+#, no-c-format
+msgid ""
+"The name and location of the file can be overridden using the <property>com."
+"arjuna.orbportability.initialReferencesFile</property> and <property>com."
+"arjuna.orbportability.initialReferencesRoot</property> property variables, "
+"respectively. It is recommended that the <property>com.arjuna.orbportability."
+"initialReferencesRoot</property> variable is set. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Chapter.xml:121
+#, no-c-format
+msgid ""
+"com.arjuna.orbportability.initialReferencesFile=myFile\n"
+"com.arjuna.orbportability.initialReferencesRoot=c:\\\\temp"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:123
+#, no-c-format
+msgid "<title>Name Service</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:124
+#, no-c-format
+msgid ""
+"If the ORB you are using supports a name service, and JBossTS has been "
+"configured to use it, then the transaction manager will automatically be "
+"registered with it. There is no further work required. This option is not "
+"used for JacORB"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:129
+#, no-c-format
+msgid "<title>resolve_initial_references</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:130
+#, no-c-format
+msgid "Currently this option is only supported for JacORB."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:135
+#, no-c-format
+msgid "Resolution service table"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:136
+#, no-c-format
+msgid ""
+"The following table summarizes the different ways in which the OTS "
+"transaction manager may be located on specific ORBs:"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:141
+#, no-c-format
+msgid "Locating the OTS transaction manager server"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:145
+#, no-c-format
+msgid "Resolution Mechanism"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:146
+#, no-c-format
+msgid "<entry>ORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:151
+#, no-c-format
+msgid "<entry>OTS configuration file</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:152
+#, no-c-format
+msgid "All available ORBs"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:155
+#, no-c-format
+msgid "<entry>Name Service</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:156 Chapter.xml:160
+#, no-c-format
+msgid "<entry>JacORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:159
+#, no-c-format
+msgid "<entry>resolve_initial_references</entry>"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:167
+#, no-c-format
+msgid "XA specific management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid ""
+"Each XA Xid that JBossTS creates must have a unique node identifier encoded "
+"within it and JBossTS will only recover transactions and states that match a "
+"specified node identifier. The node identifier to use should be provided to "
+"JBossTS via the <property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property> "
+"property. You must make sure this value is unique across your JBossTS "
+"instances. If you do not provide a value, then JBossTS will fabricate one "
+"and report the value via the logging infrastructure."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"When running XA recovery it is therefore necessary to tell JBossTS which "
+"types of Xid it can recover. Each Xid that JBossTS creates has a unique node "
+"identifier encoded within it and JBossTS will only recover transactions and "
+"states that match a specified node identifier. The node identifier to use "
+"should be provided to JBossTS via a property that starts with the name "
+"<property>com.arjuna.ats.jta.xaRecoveryNode</property>; multiple values may "
+"be provided. A value of <code>*</code> will force JBossTS to recover (and "
+"possibly rollback) all transactions irrespective of their node identifier "
+"and should be used with caution."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:177
+#, no-c-format
+msgid "Web Service Transaction service management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:178
+#, no-c-format
+msgid ""
+"The basic building blocks of a transactional Web Services application are "
+"the application itself, the Web services that the application consumes, the "
+"Transaction Manager, and the transaction participants which support those "
+"Web services. Though it is unlikely in a typical deployment that a single "
+"developer will be expected to support all of these roles, the concepts are "
+"presented here so that a global model can be visualized. It will often be "
+"the case that developers will produce services, or applications that consume "
+"services, whilst system administrators will run the transaction-management "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:182
+#, no-c-format
+msgid "The Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"The transaction manager is a Web service which coordinates JBossTS "
+"transactions. It is the only software component in JBossTS that is meant to "
+"be run directly as a network service, rather than to support end-user code. "
+"The transaction manager runs as a JAXM request/response Web service."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:187
+#, no-c-format
+msgid ""
+"When starting up an application server instance that has JBossTS deployed "
+"within it, you may see various <emphasis>error</emphasis> messages in the "
+"console or log. For example <code>16:53:38,850 ERROR [STDERR] Message "
+"Listener Service: started, message listener jndi name activationcoordinator</"
+"code>. These are for information purposes only and are not actual errors."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:192
+#, no-c-format
+msgid "Configuring the Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:193
+#, no-c-format
+msgid ""
+"The Transaction Manager and related infrastructure are configured by means "
+"of properties files: <filename>wscf.xml</filename>, <filename>wst.xml</"
+"filename> and <filename>wstx.xml</filename>. These files can be found in the "
+"conf directory and are used for configuring the demo application and the "
+"standalone module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"For the most part the default values in these files need not be altered. "
+"However, the <property>com.arjuna.ats.arjuna.objectstore.objectStoreDir</"
+"property> property determines the location of the persistent store used to "
+"record transaction state. The default value of <filename>C:/temp/"
+"ObjectStore</filename> should be changed to a value appropriate to your "
+"system. For production environments this directory should reside on fault "
+"tolerant media such as a RAID array."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"When a standalone coordinator is being used by an application it is "
+"necessary to enable and modify two further properties in <filename>wstx.xml</"
+"filename>, <property>com.arjuna.mw.wst.coordinatorURL</property> and "
+"<property>com.arjuna.mw.wst.terminatorURL</property>. These contain the URLs "
+"necessary for the client application to contact the standalone coordinator "
+"and should be configured with the correct hostname and port of the "
+"standalone coordinator."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"JBossTS is highly modular so in order to allow for flexible deployment of "
+"individual components, the same property values are sometimes required to "
+"appear in more than one configuration file. For the majority of "
+"configurations, you should maintain consistent values for properties that "
+"are defined in more than one file."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:207
+#, no-c-format
+msgid "Deploying the Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"The JBossTS Web Service Transaction Manager component consists of a number "
+"of JAR files containing the application’s class files, plus Web service "
+"(WAR) files which expose the necessary services. Programmers will typically "
+"include all these components in their application EAR file during "
+"application development, simplifying deployment of the transaction "
+"infrastructure. For production usage the Transaction Manager may be "
+"installed as an application in its own right, allowing for centralized "
+"configuration and management at the server level, independent of specific "
+"applications. The demonstration application shipped with JBossTS provides a "
+"sample deployment descriptor illustrating how the Transaction Manager "
+"components can be included in an application."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"JBossTS 4.0 uses fixed endpoints for its underlying protocol communication. "
+"Therefore, problems may arise if multiple applications using JBossTS are "
+"deployed to the same server concurrently. If you wish to deploy several "
+"transactional applications in the same server, the Transaction Manger must "
+"be deployed as a separate application and not embedded within the deployment "
+"of individual applications."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid ""
+"The coordinator directory in the JBossTS installation has been provided to "
+"assist in the configuration and deployment of a stand-alone transaction "
+"manager. In order to use this, you must:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:220
+#, no-c-format
+msgid "Have JBoss Enterprise Application Platform 5 installed"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:225
+#, no-c-format
+msgid "Install ant 1.4 or later."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:231
+#, no-c-format
+msgid ""
+"It is important that a separate application server installation be used from "
+"the one that clients and services are deployed into since otherwise "
+"conflicts may occur between the various JBossTS components."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:235
+#, no-c-format
+msgid ""
+"You must then edit the build.xml included with coordinator to point to the "
+"application server installation where the transaction coordinator will be "
+"deployed and the location of the JBossTS installation. The files "
+"<filename>ws-c_jaxm_web-app.xml</filename> and <filename>ws-t_jaxm_web-app."
+"xml</filename> in the <filename>dd</filename> directory of coordinator are "
+"the deployment descriptors for the WS-C and WS-T WAR files. These files "
+"contain templated URLs. During the build phase, ant will substitute the "
+"hostname and port values you specify in the <filename>build.xml</filename> "
+"into these files."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:238
+#, no-c-format
+msgid ""
+"Run <code>ant</code>, with <code>target deploy-weblogic</code>, <code>deploy-"
+"jboss</code> or <code>deploy-webmethods</code>, to create and deploy a new "
+"coordinator into the correct application server installation."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:241
+#, no-c-format
+msgid ""
+"Now all you need to do is point your client at the required coordinator. To "
+"do this, generate the demo application specifying the port and hostname of "
+"the coordinator."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:245
+#, no-c-format
+msgid "Deployment descriptors"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:246
+#, no-c-format
+msgid ""
+"In general, it should not be necessary to change the contents of the various "
+"deployment descriptors used by JBossTS. However, if you do need to modify "
+"them they are all included in the coordinator module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:250
+#, no-c-format
+msgid ""
+"Not all JBossTS components have ready access to the information in the "
+"deployment descriptors. Therefore, if you modify the JNDI names used by any "
+"of the WS-C or WS-T deployment descriptors you may need to inform other "
+"JBossTS components at runtime. This can be accomplished by setting an "
+"appropriate property in the <filename>wstx.xml</filename> configuration file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:253
+#, no-c-format
+msgid ""
+"The following table shows the default JNDI name used by the deployment "
+"descriptors and the corresponding property to set if the default value is "
+"changed."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:257
+#, no-c-format
+msgid "Deployment descriptor values and properties"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:261
+#, no-c-format
+msgid "JNDI Name"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:262
+#, no-c-format
+msgid "Property"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:267
+#, no-c-format
+msgid "Activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:268
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:271
+#, no-c-format
+msgid "Activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:272
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:275
+#, no-c-format
+msgid "Completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:276
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:279
+#, no-c-format
+msgid "Registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:280
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:283
+#, no-c-format
+msgid "durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:284
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:287
+#, no-c-format
+msgid "durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:288
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:291
+#, no-c-format
+msgid "volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:292
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:295
+#, no-c-format
+msgid "volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:296
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:299
+#, no-c-format
+msgid "businessagreementwithparticipantcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:300
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:303
+#, no-c-format
+msgid "businessagreementwithparticipantcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:304
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:307
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:308
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:311
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:312
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccparticipant"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:319
+#, no-c-format
msgid "JBoss Transactions runtime information"
msgstr ""
#. Tag: para
-#: Chapter.xml:29
+#: Chapter.xml:320
#, no-c-format
msgid ""
"Each module that comprises JBoss Transactions possesses a class called Info. "
@@ -121,7 +893,7 @@
msgstr ""
#. Tag: programlisting
-#: Chapter.xml:31
+#: Chapter.xml:322
#, no-c-format
msgid ""
"<module-info name=\"arjuna\">\n"
@@ -141,13 +913,13 @@
msgstr ""
#. Tag: title
-#: Chapter.xml:34
+#: Chapter.xml:325
#, no-c-format
msgid "Failure recovery administration"
msgstr ""
#. Tag: para
-#: Chapter.xml:35
+#: Chapter.xml:326
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions will ensure that "
@@ -164,14 +936,14 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:38
+#: Chapter.xml:329
#, no-c-format
msgid ""
"If the ObjectStore is destroyed or modified, recovery may not be possible."
msgstr ""
#. Tag: para
-#: Chapter.xml:41
+#: Chapter.xml:332
#, no-c-format
msgid ""
"Until the recovery procedures are complete, resources affected by a "
@@ -183,13 +955,13 @@
msgstr ""
#. Tag: title
-#: Chapter.xml:43
+#: Chapter.xml:334
#, no-c-format
msgid "The Recovery Manager"
msgstr ""
#. Tag: para
-#: Chapter.xml:44
+#: Chapter.xml:335
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions requires that the stand-"
@@ -202,13 +974,13 @@
msgstr ""
#. Tag: command
-#: Chapter.xml:45
+#: Chapter.xml:336
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
msgstr ""
#. Tag: para
-#: Chapter.xml:46
+#: Chapter.xml:337
#, no-c-format
msgid ""
"If the <literal>-test</literal> flag is used with the Recovery Manager then "
@@ -216,19 +988,19 @@
msgstr ""
#. Tag: command
-#: Chapter.xml:47
+#: Chapter.xml:338
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
msgstr ""
#. Tag: title
-#: Chapter.xml:50
+#: Chapter.xml:341
#, no-c-format
msgid "Configuring the Recovery Manager"
msgstr ""
#. Tag: para
-#: Chapter.xml:51
+#: Chapter.xml:342
#, no-c-format
msgid ""
"The RecoveryManager reads the properties defined in the <filename>arjuna."
@@ -241,7 +1013,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:52
+#: Chapter.xml:343
#, no-c-format
msgid ""
"A default version of <filename>RecoveryManager.properties</filename> is "
@@ -253,13 +1025,13 @@
msgstr ""
#. Tag: title
-#: Chapter.xml:54
+#: Chapter.xml:345
#, no-c-format
msgid "Output"
msgstr ""
#. Tag: para
-#: Chapter.xml:55
+#: Chapter.xml:346
#, no-c-format
msgid ""
"It is likely that installations will want to have some form of output from "
@@ -273,7 +1045,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:58
+#: Chapter.xml:349
#, no-c-format
msgid ""
"With the CLF applications make logging calls on logger objects. Loggers may "
@@ -286,7 +1058,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:61
+#: Chapter.xml:352
#, no-c-format
msgid ""
"The CLF provides an extension to filter logging messages according to finer "
@@ -296,7 +1068,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:67
+#: Chapter.xml:358
#, no-c-format
msgid ""
"These conditions are applied if and only the DEBUG level is enabled and the "
@@ -304,13 +1076,13 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:71
+#: Chapter.xml:362
#, no-c-format
msgid "When enabled, Debugging is filtered conditionally on three variables:"
msgstr ""
#. Tag: para
-#: Chapter.xml:74
+#: Chapter.xml:365
#, no-c-format
msgid ""
"Debugging level: this is where the log request with the DEBUG Level is "
@@ -318,7 +1090,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:77
+#: Chapter.xml:368
#, no-c-format
msgid ""
"Visibility level: the visibility of the constructor, method, etc. that "
@@ -326,7 +1098,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:80
+#: Chapter.xml:371
#, no-c-format
msgid ""
"Facility code: for instance the package or sub-module within which debugging "
@@ -334,7 +1106,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:83
+#: Chapter.xml:374
#, no-c-format
msgid ""
"According to these variables the CLF defines three interfaces. A particular "
@@ -348,7 +1120,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:84
+#: Chapter.xml:375
#, no-c-format
msgid ""
"Debugging level – JBoss Transactions uses the default values defined in the "
@@ -356,7 +1128,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:87
+#: Chapter.xml:378
#, no-c-format
msgid ""
"NO_DEBUGGING: No diagnostics. A logger object assigned with this values "
@@ -364,7 +1136,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:90
+#: Chapter.xml:381
#, no-c-format
msgid ""
"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
@@ -373,73 +1145,73 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:93
+#: Chapter.xml:384
#, no-c-format
msgid "Additional Debugging Values are:"
msgstr ""
#. Tag: para
-#: Chapter.xml:96
+#: Chapter.xml:387
#, no-c-format
msgid "CONSTRUCTORS: Diagnostics from constructors."
msgstr ""
#. Tag: para
-#: Chapter.xml:99
+#: Chapter.xml:390
#, no-c-format
msgid "DESTRUCTORS: Diagnostics from finalizers."
msgstr ""
#. Tag: para
-#: Chapter.xml:102
+#: Chapter.xml:393
#, no-c-format
msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
msgstr ""
#. Tag: para
-#: Chapter.xml:105
+#: Chapter.xml:396
#, no-c-format
msgid "FUNCTIONS: Diagnostics from functions."
msgstr ""
#. Tag: para
-#: Chapter.xml:108
+#: Chapter.xml:399
#, no-c-format
msgid "OPERATORS: Diagnostics from operators, such as equals."
msgstr ""
#. Tag: para
-#: Chapter.xml:111
+#: Chapter.xml:402
#, no-c-format
msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
msgstr ""
#. Tag: para
-#: Chapter.xml:114
+#: Chapter.xml:405
#, no-c-format
msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
msgstr ""
#. Tag: para
-#: Chapter.xml:117
+#: Chapter.xml:408
#, no-c-format
msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
msgstr ""
#. Tag: para
-#: Chapter.xml:120
+#: Chapter.xml:411
#, no-c-format
msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
msgstr ""
#. Tag: para
-#: Chapter.xml:123
+#: Chapter.xml:414
#, no-c-format
msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
msgstr ""
#. Tag: para
-#: Chapter.xml:126
+#: Chapter.xml:417
#, no-c-format
msgid ""
"Visibility level – JBoss Transactions uses the default values defined in the "
@@ -447,43 +1219,43 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:129
+#: Chapter.xml:420
#, no-c-format
msgid "VIS_NONE: No Diagnostic"
msgstr ""
#. Tag: para
-#: Chapter.xml:132
+#: Chapter.xml:423
#, no-c-format
msgid "VIS_PRIVATE : only from private methods."
msgstr ""
#. Tag: para
-#: Chapter.xml:135
+#: Chapter.xml:426
#, no-c-format
msgid "VIS_PROTECTED only from protected methods."
msgstr ""
#. Tag: para
-#: Chapter.xml:138
+#: Chapter.xml:429
#, no-c-format
msgid "VIS_PUBLIC only from public methods."
msgstr ""
#. Tag: para
-#: Chapter.xml:141
+#: Chapter.xml:432
#, no-c-format
msgid "VIS_PACKAGE only from package methods."
msgstr ""
#. Tag: para
-#: Chapter.xml:144
+#: Chapter.xml:435
#, no-c-format
msgid "VIS_ALL: Full Diagnostic"
msgstr ""
#. Tag: para
-#: Chapter.xml:147
+#: Chapter.xml:438
#, no-c-format
msgid ""
"Facility Code – JBoss Transactions uses the following values defined in the "
@@ -491,49 +1263,49 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:150
+#: Chapter.xml:441
#, no-c-format
msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
msgstr ""
#. Tag: para
-#: Chapter.xml:153
+#: Chapter.xml:444
#, no-c-format
msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
msgstr ""
#. Tag: para
-#: Chapter.xml:156
+#: Chapter.xml:447
#, no-c-format
msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
msgstr ""
#. Tag: para
-#: Chapter.xml:159
+#: Chapter.xml:450
#, no-c-format
msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
msgstr ""
#. Tag: para
-#: Chapter.xml:162
+#: Chapter.xml:453
#, no-c-format
msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
msgstr ""
#. Tag: para
-#: Chapter.xml:165
+#: Chapter.xml:456
#, no-c-format
msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
msgstr ""
#. Tag: para
-#: Chapter.xml:168
+#: Chapter.xml:459
#, no-c-format
msgid "FAC_GENERAL = 0x00000080 (general classes)."
msgstr ""
#. Tag: para
-#: Chapter.xml:171
+#: Chapter.xml:462
#, no-c-format
msgid ""
"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
@@ -541,26 +1313,26 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:174
+#: Chapter.xml:465
#, no-c-format
msgid "FAC_THREADING = 0x00002000 (threading classes)."
msgstr ""
#. Tag: para
-#: Chapter.xml:177
+#: Chapter.xml:468
#, no-c-format
msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
msgstr ""
#. Tag: para
-#: Chapter.xml:180
+#: Chapter.xml:471
#, no-c-format
msgid ""
"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
msgstr ""
#. Tag: para
-#: Chapter.xml:183
+#: Chapter.xml:474
#, no-c-format
msgid ""
"To ensure appropriate output, it is necessary to set some of the finer debug "
@@ -569,7 +1341,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:184
+#: Chapter.xml:475
#, no-c-format
msgid ""
"Messages describing the start and the periodical behavior made by the "
@@ -581,7 +1353,7 @@
msgstr ""
#. Tag: programlisting
-#: Chapter.xml:186
+#: Chapter.xml:477
#, no-c-format
msgid ""
"<!-- Common logging related properties. -->\n"
@@ -595,7 +1367,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:189
+#: Chapter.xml:480
#, no-c-format
msgid ""
"Two logger objects are provided, one manages I18N messages and a second does "
@@ -603,7 +1375,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:192
+#: Chapter.xml:483
#, no-c-format
msgid ""
"Setting the normal recovery messages to the INFO level allows the "
@@ -615,13 +1387,13 @@
msgstr ""
#. Tag: title
-#: Chapter.xml:196
+#: Chapter.xml:487
#, no-c-format
msgid "Periodic Recovery"
msgstr ""
#. Tag: para
-#: Chapter.xml:197
+#: Chapter.xml:488
#, no-c-format
msgid ""
"The RecoveryManager scans the ObjectStore and other locations of "
@@ -635,7 +1407,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:198
+#: Chapter.xml:489
#, no-c-format
msgid ""
"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
@@ -653,7 +1425,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:199
+#: Chapter.xml:490
#, no-c-format
msgid ""
"An attempt, by the RecoveryManager, to recover a transaction that is still "
@@ -670,7 +1442,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:200
+#: Chapter.xml:491
#, no-c-format
msgid ""
"It is clearly important to set the interval periods appropriately. The total "
@@ -692,7 +1464,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:203
+#: Chapter.xml:494
#, no-c-format
msgid ""
"In previous versions of JBoss Transactions there was no contact mechanism, "
@@ -701,7 +1473,7 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:206
+#: Chapter.xml:497
#, no-c-format
msgid ""
"Two recovery modules (implementations of the <classname>com.arjuna.ats."
@@ -719,7 +1491,7 @@
msgstr ""
#. Tag: programlisting
-#: Chapter.xml:208
+#: Chapter.xml:499
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
@@ -730,13 +1502,13 @@
msgstr ""
#. Tag: title
-#: Chapter.xml:211
+#: Chapter.xml:502
#, no-c-format
msgid "Expired entry removal"
msgstr ""
#. Tag: para
-#: Chapter.xml:212
+#: Chapter.xml:503
#, no-c-format
msgid ""
"The operation of the recovery subsystem will cause some entries to be made "
@@ -758,13 +1530,13 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:213
+#: Chapter.xml:504
#, no-c-format
msgid "The kinds of item that are scanned for expiry are:"
msgstr ""
#. Tag: para
-#: Chapter.xml:214
+#: Chapter.xml:505
#, no-c-format
msgid ""
"TransactionStatusManager items : one of these is created by every "
@@ -778,13 +1550,13 @@
msgstr ""
#. Tag: para
-#: Chapter.xml:215
+#: Chapter.xml:506
#, no-c-format
msgid "The Expiry Scanner properties for these are:"
msgstr ""
#. Tag: programlisting
-#: Chapter.xml:217
+#: Chapter.xml:508
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
@@ -793,141 +1565,274 @@
msgstr ""
#. Tag: title
-#: Chapter.xml:220
+#: Chapter.xml:511
#, no-c-format
-msgid "Errors and Exceptions"
+msgid "Selecting the JTA implementation"
msgstr ""
#. Tag: para
-#: Chapter.xml:221
+#: Chapter.xml:512
#, 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."
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
msgstr ""
#. Tag: para
-#: Chapter.xml:224
+#: Chapter.xml:515
#, 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."
+"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:227
+#: Chapter.xml:518
#, 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."
+"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:230
+#: Chapter.xml:522
#, 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."
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
msgstr ""
#. Tag: para
-#: Chapter.xml:233
+#: Chapter.xml:525
#, 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."
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
msgstr ""
#. Tag: para
-#: Chapter.xml:236
+#: Chapter.xml:528
#, 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."
+"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:531
+#, 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:535
+#, 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 ""
+
#. Tag: title
-#: Chapter.xml:241
+#: Chapter.xml:542
#, no-c-format
-msgid "Selecting the JTA implementation"
+msgid "ORB specific configurations"
msgstr ""
+#. Tag: title
+#: Chapter.xml:544
+#, no-c-format
+msgid "<title>JacORB</title>"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:242
+#: Chapter.xml:545
#, no-c-format
msgid ""
-"Two variants of the JTA implementation are now provided and accessible "
-"through the same interface. These are:"
+"For JacORB to function correctly it is necessary to ensure there is a valid "
+"<filename>jacorb.properties</filename> or <filename>.jacorb_properties</"
+"filename> file in one of the following places:"
msgstr ""
#. Tag: para
-#: Chapter.xml:245
+#: Chapter.xml:551
#, no-c-format
+msgid "The classpath."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:556
+#, 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."
+"The home directory of the user running the JBoss Transaction Service. The "
+"home directory is retrieved using <code>System.getProperty( “user.home” );</"
+"code>"
msgstr ""
#. Tag: para
-#: Chapter.xml:248
+#: Chapter.xml:561
#, no-c-format
+msgid "The current directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:566
+#, 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."
+"The <filename>lib</filename> directory of the JDK used to run your "
+"application. This is retrieved using <code>System.getProperty( “java.home” );"
+"</code>"
msgstr ""
#. Tag: para
-#: Chapter.xml:252
+#: Chapter.xml:571
#, no-c-format
msgid ""
-"both of these implementations are fully compatible with the transactional "
-"JDBC driver provided with JBoss Transactions."
+"The above places are searched in the order given. A template "
+"<filename>jacorb.properties</filename> file can be found in the JacORB "
+"installation directory."
msgstr ""
#. Tag: para
-#: Chapter.xml:255
+#: Chapter.xml:574
#, no-c-format
msgid ""
-"In order to select the local JTA implementation it is necessary to perform "
-"the following steps:"
+"Within the JacORB properties file there are two important properties which "
+"must be tailored to suit your application, they are:"
msgstr ""
+#. Tag: property
+#: Chapter.xml:580
+#, no-c-format
+msgid "jacorb.poa.thread_pool_max"
+msgstr ""
+
+#. Tag: property
+#: Chapter.xml:585
+#, no-c-format
+msgid "jacorb.poa.thread_pool_min"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:258
+#: Chapter.xml:589
#, 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>."
+"These properties specify the minimum and maximum number of request "
+"processing threads that JacORB will use in its thread pool. If there aren’t "
+"a sufficient number of threads available in this thread pool then the "
+"application may appear to become deadlocked. For more information on "
+"configuring JacORB please reference the JacORB documentation."
msgstr ""
#. Tag: para
-#: Chapter.xml:261
+#: Chapter.xml:593
#, 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>."
+"JacORB comes with its own implementation of the classes defined in the "
+"<filename>CosTransactions.idl</filename> file. Unfortunately these are "
+"incompatible with the version shipped with JBossTS. Therefore, it is "
+"important that the JBossTS jar files appear in the <code>CLASSPATH</code> "
+"before any JacORB jars."
msgstr ""
#. Tag: para
-#: Chapter.xml:265
+#: Chapter.xml:597
#, 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."
+"When running the recovery manager it is important that it always uses the "
+"same well known port for each machine on which it runs. You should not use "
+"the OAPort property provided by JacORB unless the recovery manager has its "
+"own <filename>jacorb.properties</filename> file or this is provided on the "
+"command line when starting the recovery manager. If the recovery manager and "
+"other components of JBossTS share the same <filename>jacorb.properties</"
+"filename> file, then you should use the <filename>com.arjuna.ats.jts."
+"recoveryManagerPort</filename> and <filename>com.arjuna.ats.jts."
+"recoveryManagerAddress</filename> properties."
msgstr ""
+
+#. Tag: title
+#: Chapter.xml:603
+#, no-c-format
+msgid "Initializing JBossTS applications"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:604
+#, no-c-format
+msgid ""
+"It is important that JBossTS is correctly initialized prior to any "
+"application object being created. In order to guarantee this, the programmer "
+"should use the <methodname>ORB_init</methodname> and <methodname>create_POA</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:609
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:610
+#, 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:613
+#, 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:616
+#, 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:619
+#, 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:622
+#, 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:625
+#, 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 ""
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Feedback.pot
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Feedback.pot 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Feedback.pot 2009-09-17 02:36:56 UTC (rev 29385)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-07-14 01:26+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+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"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Preface.pot
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Preface.pot 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Preface.pot 2009-09-17 02:36:56 UTC (rev 29385)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-07-14 01:26+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+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"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Revision_History.pot
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Revision_History.pot 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pot/Revision_History.pot 2009-09-17 02:36:56 UTC (rev 29385)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-07-14 01:26+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+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"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Author_Group.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Author_Group.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Author_Group.po to Brazilian Portuguese
+# translation of Preface.po to Brazilian Portuguese
# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Leticia de Lima <ldelima at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: Preface\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-16 10:42+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-19 16:13+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -16,21 +16,8 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
-#. Tag: corpauthor
-#: Author_Group.xml:6
-#, no-c-format
-msgid "FF0000 Headgear Documentation Group"
-msgstr "Grupo de Documentação FF0000 Headgear"
-
#. 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 ""
-"<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>"
-
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Book_Info.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Book_Info.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Book_Info.po to Brazilian Portuguese
+# translation of Preface.po to Brazilian Portuguese
# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Leticia de Lima <ldelima at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: Preface\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-16 10:49+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-19 16:13+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -18,27 +18,28 @@
#. Tag: title
#: Book_Info.xml:6
-#, no-c-format
-msgid "JBoss Transactions API 4.2.3 Administration Guide"
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Administrators Guide"
msgstr "Guia de Administração API 4.2.3 de Transações JBoss"
#. Tag: subtitle
#: Book_Info.xml:10
-#, no-c-format
-msgid "JBoss Enterprise Application Platform"
+#, fuzzy, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 5.0"
msgstr "Plataforma de Aplicativo JBoss Enterprise"
#. Tag: para
-#: Book_Info.xml:13
+#: Book_Info.xml:15
#, no-c-format
msgid ""
"This book is the JBoss Enterprise Application Platform edition of the JBoss "
"Transactions Administrators Guide"
-msgstr "Este livro é uma edição da Plataforma de Aplicativo JBoss Enterprise do Guia de Administradores de Transações JBoss"
+msgstr ""
+"Este livro é uma edição da Plataforma de Aplicativo JBoss Enterprise do Guia "
+"de Administradores de Transações JBoss"
#. Tag: holder
-#: Book_Info.xml:22
+#: Book_Info.xml:24
#, no-c-format
msgid "&HOLDER;"
msgstr "&HOLDER;"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Chapter.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Chapter.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Chapter.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Chapter.po to Brazilian Portuguese
+# translation of Preface.po to Brazilian Portuguese
# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Leticia de Lima <ldelima at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Chapter\n"
+"Project-Id-Version: Preface\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-19 15:37+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-19 16:13+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\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 "Existe uma administração contínua e necessária para o software de transações JBoss, fora a garantia de que o sistema de tempo de execução é efetuado normalmente. No entanto, existem alguns pontos que devem ser mencionados:"
+msgstr ""
+"Existe uma administração contínua e necessária para o software de transações "
+"JBoss, fora a garantia de que o sistema de tempo de execução é efetuado "
+"normalmente. No entanto, existem alguns pontos que devem ser mencionados:"
#. 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 "A implementação presente do sistema JBoss TA não fornece segurança ou proteção de dados. Os objetos armazenados no armazenamento de objeto de Transações JBoss pertencem (tipicamente) ao usuário que roda o aplicativo que os criou. As facilidades do Gerenciador de Objeto e Armazenamento de Objeto não se esforçam em reforçar nem mesmo o formulário limitado de proteção que o Unix/Windows fornece. Não há checagem de IDs de usuário ou grupo no acesso a objetos para tanto a leitura ou gravação."
+msgstr ""
+"A implementação presente do sistema JBoss TA não fornece segurança ou "
+"proteção de dados. Os objetos armazenados no armazenamento de objeto de "
+"Transações JBoss pertencem (tipicamente) ao usuário que roda o aplicativo "
+"que os criou. As facilidades do Gerenciador de Objeto e Armazenamento de "
+"Objeto não se esforçam em reforçar nem mesmo o formulário limitado de "
+"proteção que o Unix/Windows fornece. Não há checagem de IDs de usuário ou "
+"grupo no acesso a objetos para tanto a leitura ou gravação."
#. Tag: para
#: Chapter.xml:13
@@ -59,7 +69,19 @@
"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 "Os objetos persistentes criados no Armazenamento do Objeto nunca desaparecerão, a não ser que o método StateManager.destroy seja invocado no objeto ou algum programa de aplicativo explícito deletá-los. Isto significa que o Armazenamento de Objeto acumula gradativamente lixo (especialmente durante as fases de teste e desenvolvimento do aplicativo). No momento, não possuimos a facilidade de coleta de lixo automático. Adicionado a isto, não endereçamos o problema de referências de ligação. Isto quer dizer que, um objeto persistente A pode armazenar um Uid de outro objeto persistente B, em sua representação passiva no disco. Não há nada para evitar que um aplicativo delete o objeto persistente B, mesmo que o A possua referência a isto. Na próxima vez em que o A for ativado e tentar acessar o B, um erro de tempo de execução ocorrerá."
+msgstr ""
+"Os objetos persistentes criados no Armazenamento do Objeto nunca "
+"desaparecerão, a não ser que o método StateManager.destroy seja invocado no "
+"objeto ou algum programa de aplicativo explícito deletá-los. Isto significa "
+"que o Armazenamento de Objeto acumula gradativamente lixo (especialmente "
+"durante as fases de teste e desenvolvimento do aplicativo). No momento, não "
+"possuimos a facilidade de coleta de lixo automático. Adicionado a isto, não "
+"endereçamos o problema de referências de ligação. Isto quer dizer que, um "
+"objeto persistente A pode armazenar um Uid de outro objeto persistente B, em "
+"sua representação passiva no disco. Não há nada para evitar que um "
+"aplicativo delete o objeto persistente B, mesmo que o A possua referência a "
+"isto. Na próxima vez em que o A for ativado e tentar acessar o B, um erro de "
+"tempo de execução ocorrerá."
#. Tag: para
#: Chapter.xml:16
@@ -73,22 +95,94 @@
"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 "Atualmente, não há suporte para o controle de versão de objetos ou reconfiguração de banco de dados, no evento de mudanças de estruturas de classe. Isto é uma área de pesquisa complexa, da qual nós não endereçamos ainda. Caso você mude a definição da classe de objetos persistentes, você será inteiramente responsável em assegurar que instâncias existentes do objeto, no Armazenamento do Objeto, serão convertidas à nova representação. O software de Transações JBoss nunca poderá detectar e nem mesmo corrigir referências para um estado de objeto antigo, pela nova operação."
+msgstr ""
+"Atualmente, não há suporte para o controle de versão de objetos ou "
+"reconfiguração de banco de dados, no evento de mudanças de estruturas de "
+"classe. Isto é uma área de pesquisa complexa, da qual nós não endereçamos "
+"ainda. Caso você mude a definição da classe de objetos persistentes, você "
+"será inteiramente responsável em assegurar que instâncias existentes do "
+"objeto, no Armazenamento do Objeto, serão convertidas à nova representação. "
+"O software de Transações JBoss nunca poderá detectar e nem mesmo corrigir "
+"referências para um estado de objeto antigo, pela nova operação."
#. Tag: para
-#: Chapter.xml:19
+#: Chapter.xml:19 Chapter.xml:62
#, no-c-format
-msgid "Object store management is critically important to the transaction service."
-msgstr "O gerenciamento de armazenamento de objeto é extremamente importante ao serviço de transação."
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+"O gerenciamento de armazenamento de objeto é extremamente importante ao "
+"serviço de transação."
#. Tag: title
#: Chapter.xml:24
#, no-c-format
+msgid "Starting and Stopping the transaction manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"By default the transaction manager starts up in an active state such that "
+"new transactions can be created immediately. If you wish to have more "
+"control over this it is possible to set the <property>com.arjuna.ats.arjuna."
+"coordinator.startDisabled</property> configuration option to <literal>YES</"
+"literal>, in which case no transactions can be created until the transaction "
+"manager is enabled (via a call to <methodname>TxControl.enable</methodname>)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:28
+#, no-c-format
+msgid ""
+"It is possible to stop the creation of new transactions at any time by "
+"calling <methodname>TxControl.disable</methodname>. Transactions that are "
+"currently executing will not be affected. By default recovery will be "
+"allowed to continue and the transaction system will still be available to "
+"manage recovery requests from other instances in a distributed environment. "
+"(See the Failure Recovery Guide for further details). However, if you wish "
+"to disable recovery as well as remove any resources it maintains, then you "
+"can pass true to <methodname>TxControl.disable</methodname>; the default is "
+"to use <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"If you wish to shut the system down completely then it may also be necessary "
+"to terminate the background transaction reaper (see the Programmers Guide "
+"for information about what the reaper does.) In order to do this you may "
+"want to first prevent the creation of new transactions (if you are not "
+"creating transactions with timeouts then this step is not necessary) using "
+"<methodname>TxControl.disable</methodname>. Then you should call "
+"<methodname>TransactionReaper.terminate</methodname>. This method takes a "
+"boolean parameter: if true then the method will wait for the normal timeout "
+"periods associated with any transactions to expire before terminating the "
+"transactions; if false then transactions will be forced to terminate "
+"(rollback or have their outcome set such that they can only ever rollback) "
+"immediately."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"If you intent to restart the recovery manager later after having terminated "
+"it then you <emphasis>must</emphasis> use the <methodname>terminate</"
+"methodname> method with <property>asynchronous behavior</property> set to "
+"<literal>false</literal> when shutting down the recovery manager."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:40
+#, no-c-format
msgid "ObjectStore management"
msgstr "Gerenciamento ObjectStore"
#. Tag: para
-#: Chapter.xml:25
+#: Chapter.xml:41
#, no-c-format
msgid ""
"Within the transaction service installation, the object store is updated "
@@ -103,26 +197,786 @@
"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 "Quando se tratar da instalação do serviço de transação, o armazenamento do objeto é atualizado regularmente toda vez em que as transações são criadas ou toda vez em que os Objetos Transacionais para Java forem usados. Numa falha de ambiente livre, o único objeto que determina o que deve residir com o armazenamento do objeto, são os objetos representantes criados com os Objetos Tradicionais para o Java API. No entanto, se uma falha ocorrer, os logs de transação poderão permanecer num armazenamento de objeto até que as facilidades de recuperação de travamento tenham resolvido as transações que elas representam. Assim como, é bastante importante que os conteúdos do armazenamento do objeto não sejam deletados sem o devido cuidado e atenção, uma vez que isto tornará impossível a resolução de transações suspeitas. Adicionado a isto, caso múltiplos usuários compartilharem o mesmo armazenamento do objeto, será necessário que eles saibam dis!
to e não deletem simplesmente o conteúdo do armazenamento do objeto, assumindo que isto é um recurso exclusivo."
+msgstr ""
+"Quando se tratar da instalação do serviço de transação, o armazenamento do "
+"objeto é atualizado regularmente toda vez em que as transações são criadas "
+"ou toda vez em que os Objetos Transacionais para Java forem usados. Numa "
+"falha de ambiente livre, o único objeto que determina o que deve residir com "
+"o armazenamento do objeto, são os objetos representantes criados com os "
+"Objetos Tradicionais para o Java API. No entanto, se uma falha ocorrer, os "
+"logs de transação poderão permanecer num armazenamento de objeto até que as "
+"facilidades de recuperação de travamento tenham resolvido as transações que "
+"elas representam. Assim como, é bastante importante que os conteúdos do "
+"armazenamento do objeto não sejam deletados sem o devido cuidado e atenção, "
+"uma vez que isto tornará impossível a resolução de transações suspeitas. "
+"Adicionado a isto, caso múltiplos usuários compartilharem o mesmo "
+"armazenamento do objeto, será necessário que eles saibam disto e não deletem "
+"simplesmente o conteúdo do armazenamento do objeto, assumindo que isto é um "
+"recurso exclusivo."
+#. Tag: para
+#: Chapter.xml:42
+#, fuzzy, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBossTS software. There are "
+"a few points however, that should be made:"
+msgstr ""
+"Existe uma administração contínua e necessária para o software de transações "
+"JBoss, fora a garantia de que o sistema de tempo de execução é efetuado "
+"normalmente. No entanto, existem alguns pontos que devem ser mencionados:"
+
+#. Tag: para
+#: Chapter.xml:47
+#, fuzzy, no-c-format
+msgid ""
+"The present implementation of the JBossTS system provides no security or "
+"protection for data. It is recommended that the objects stored in the "
+"JBossTS are owned by user arjuna. The Object Store and Object Manager "
+"facilities make no attempt to enforce even the limited form of protection "
+"that Unix and Windows provides. There is no checking of user or group IDs on "
+"access to objects for either reading or writing."
+msgstr ""
+"A implementação presente do sistema JBoss TA não fornece segurança ou "
+"proteção de dados. Os objetos armazenados no armazenamento de objeto de "
+"Transações JBoss pertencem (tipicamente) ao usuário que roda o aplicativo "
+"que os criou. As facilidades do Gerenciador de Objeto e Armazenamento de "
+"Objeto não se esforçam em reforçar nem mesmo o formulário limitado de "
+"proteção que o Unix/Windows fornece. Não há checagem de IDs de usuário ou "
+"grupo no acesso a objetos para tanto a leitura ou gravação."
+
+#. Tag: para
+#: Chapter.xml:52
+#, fuzzy, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> 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 ""
+"Os objetos persistentes criados no Armazenamento do Objeto nunca "
+"desaparecerão, a não ser que o método StateManager.destroy seja invocado no "
+"objeto ou algum programa de aplicativo explícito deletá-los. Isto significa "
+"que o Armazenamento de Objeto acumula gradativamente lixo (especialmente "
+"durante as fases de teste e desenvolvimento do aplicativo). No momento, não "
+"possuimos a facilidade de coleta de lixo automático. Adicionado a isto, não "
+"endereçamos o problema de referências de ligação. Isto quer dizer que, um "
+"objeto persistente A pode armazenar um Uid de outro objeto persistente B, em "
+"sua representação passiva no disco. Não há nada para evitar que um "
+"aplicativo delete o objeto persistente B, mesmo que o A possua referência a "
+"isto. Na próxima vez em que o A for ativado e tentar acessar o B, um erro de "
+"tempo de execução ocorrerá."
+
+#. Tag: para
+#: Chapter.xml:57
+#, fuzzy, 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 JBossTS software can neither detect "
+"nor correct references to old object state by new operation versions or vice "
+"versa."
+msgstr ""
+"Atualmente, não há suporte para o controle de versão de objetos ou "
+"reconfiguração de banco de dados, no evento de mudanças de estruturas de "
+"classe. Isto é uma área de pesquisa complexa, da qual nós não endereçamos "
+"ainda. Caso você mude a definição da classe de objetos persistentes, você "
+"será inteiramente responsável em assegurar que instâncias existentes do "
+"objeto, no Armazenamento do Objeto, serão convertidas à nova representação. "
+"O software de Transações JBoss nunca poderá detectar e nem mesmo corrigir "
+"referências para um estado de objeto antigo, pela nova operação."
+
#. Tag: title
-#: Chapter.xml:28
+#: Chapter.xml:70
#, no-c-format
+msgid "OTS and J2EE Transaction service management"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:72
+#, no-c-format
+msgid "Starting the run-time system"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:73
+#, no-c-format
+msgid ""
+"The JBossTS run-time support consists of run-time packages and the OTS "
+"transaction manager server. By default JBossTS does not use a separate "
+"transaction manager server: transaction managers are co-located with each "
+"application process to improve performance and improve application fault-"
+"tolerance (the application is no longer dependant upon another service in "
+"order to function correctly)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:76
+#, no-c-format
+msgid ""
+"When running applications which require a separate transaction manager, you "
+"must set the <varname>com.arjuna.ats.jts.transactionManager</varname> "
+"environment variable to have the value <literal>yes</literal>. The system "
+"will then locate the transaction manager server in a manner specific to the "
+"ORB being used. The server can be located in a number of ways: by being "
+"registered with a name server, added to the ORB’s initial references, via a "
+"JBossTS specific references file, or by the ORB’s specific location "
+"mechanism (if applicable)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:79
+#, no-c-format
+msgid ""
+"It is possible to override the default registration mechanism by using the "
+"<varname>com.arjuna.orbportability.resolveService</varname> environment "
+"variable. This can have one of the following values:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"<literal>CONFIGURATION_FILE</literal>: the default, this causes the system "
+"to use the <filename>CosServices.cfg</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:89
+#, no-c-format
+msgid ""
+"<literal>NAME_SERVICE</literal>: JBossTS will attempt to use a name service "
+"to register the transaction factory. If this is not supported, an exception "
+"will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:94
+#, no-c-format
+msgid ""
+"<literal>BIND_CONNECT</literal>: JBossTS will use the ORB-specific bind "
+"mechanism. If this is not supported, an exception will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid ""
+"<literal>RESOLVE_INITIAL_REFERENCES</literal>: JBossTS will attempt to "
+"register the transaction service with the ORBs initial service references."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid ""
+"This may not be supported on all ORBs. An exception will be thrown in that "
+"case and another option will have to be used."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:110
+#, no-c-format
+msgid "<title>OTS configuration file</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid ""
+"Similar to the resolve_initial_references, JBossTS supports an initial "
+"reference file where references for specific services can be stored and used "
+"at runtime. The file, CosServices.cfg, consists of two columns: the service "
+"name (in the case of the OTS server TransactionService) and the IOR, "
+"separated by a single space. CosServices.cfg normally resides in the etc "
+"directory of the JBossTS installation; the actual location is determined at "
+"runtime by searching the CLASSPATH for an old copy of the file resident "
+"within an etc directory, or, if one is not found, the location of the "
+"TransactionService properties file directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:115
+#, no-c-format
+msgid ""
+"The OTS server will automatically register itself in this file (creating it "
+"if necessary) if this option is being used. Stale information is also "
+"automatically removed. Machines which wish to share the same transaction "
+"server should have access to (or a copy of) this file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:118
+#, no-c-format
+msgid ""
+"The name and location of the file can be overridden using the <property>com."
+"arjuna.orbportability.initialReferencesFile</property> and <property>com."
+"arjuna.orbportability.initialReferencesRoot</property> property variables, "
+"respectively. It is recommended that the <property>com.arjuna.orbportability."
+"initialReferencesRoot</property> variable is set. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Chapter.xml:121
+#, no-c-format
+msgid ""
+"com.arjuna.orbportability.initialReferencesFile=myFile\n"
+"com.arjuna.orbportability.initialReferencesRoot=c:\\\\temp"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:123
+#, no-c-format
+msgid "<title>Name Service</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:124
+#, no-c-format
+msgid ""
+"If the ORB you are using supports a name service, and JBossTS has been "
+"configured to use it, then the transaction manager will automatically be "
+"registered with it. There is no further work required. This option is not "
+"used for JacORB"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:129
+#, no-c-format
+msgid "<title>resolve_initial_references</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:130
+#, no-c-format
+msgid "Currently this option is only supported for JacORB."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:135
+#, no-c-format
+msgid "Resolution service table"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:136
+#, no-c-format
+msgid ""
+"The following table summarizes the different ways in which the OTS "
+"transaction manager may be located on specific ORBs:"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:141
+#, no-c-format
+msgid "Locating the OTS transaction manager server"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:145
+#, no-c-format
+msgid "Resolution Mechanism"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:146
+#, no-c-format
+msgid "<entry>ORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:151
+#, no-c-format
+msgid "<entry>OTS configuration file</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:152
+#, no-c-format
+msgid "All available ORBs"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:155
+#, no-c-format
+msgid "<entry>Name Service</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:156 Chapter.xml:160
+#, no-c-format
+msgid "<entry>JacORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:159
+#, no-c-format
+msgid "<entry>resolve_initial_references</entry>"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:167
+#, no-c-format
+msgid "XA specific management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid ""
+"Each XA Xid that JBossTS creates must have a unique node identifier encoded "
+"within it and JBossTS will only recover transactions and states that match a "
+"specified node identifier. The node identifier to use should be provided to "
+"JBossTS via the <property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property> "
+"property. You must make sure this value is unique across your JBossTS "
+"instances. If you do not provide a value, then JBossTS will fabricate one "
+"and report the value via the logging infrastructure."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"When running XA recovery it is therefore necessary to tell JBossTS which "
+"types of Xid it can recover. Each Xid that JBossTS creates has a unique node "
+"identifier encoded within it and JBossTS will only recover transactions and "
+"states that match a specified node identifier. The node identifier to use "
+"should be provided to JBossTS via a property that starts with the name "
+"<property>com.arjuna.ats.jta.xaRecoveryNode</property>; multiple values may "
+"be provided. A value of <code>*</code> will force JBossTS to recover (and "
+"possibly rollback) all transactions irrespective of their node identifier "
+"and should be used with caution."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:177
+#, no-c-format
+msgid "Web Service Transaction service management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:178
+#, no-c-format
+msgid ""
+"The basic building blocks of a transactional Web Services application are "
+"the application itself, the Web services that the application consumes, the "
+"Transaction Manager, and the transaction participants which support those "
+"Web services. Though it is unlikely in a typical deployment that a single "
+"developer will be expected to support all of these roles, the concepts are "
+"presented here so that a global model can be visualized. It will often be "
+"the case that developers will produce services, or applications that consume "
+"services, whilst system administrators will run the transaction-management "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:182
+#, fuzzy, no-c-format
+msgid "The Transaction Manager"
+msgstr "O Gerenciamento de Recuperação"
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"The transaction manager is a Web service which coordinates JBossTS "
+"transactions. It is the only software component in JBossTS that is meant to "
+"be run directly as a network service, rather than to support end-user code. "
+"The transaction manager runs as a JAXM request/response Web service."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:187
+#, no-c-format
+msgid ""
+"When starting up an application server instance that has JBossTS deployed "
+"within it, you may see various <emphasis>error</emphasis> messages in the "
+"console or log. For example <code>16:53:38,850 ERROR [STDERR] Message "
+"Listener Service: started, message listener jndi name activationcoordinator</"
+"code>. These are for information purposes only and are not actual errors."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:192
+#, fuzzy, no-c-format
+msgid "Configuring the Transaction Manager"
+msgstr "Configurando o Gerenciador de Recuperação"
+
+#. Tag: para
+#: Chapter.xml:193
+#, no-c-format
+msgid ""
+"The Transaction Manager and related infrastructure are configured by means "
+"of properties files: <filename>wscf.xml</filename>, <filename>wst.xml</"
+"filename> and <filename>wstx.xml</filename>. These files can be found in the "
+"conf directory and are used for configuring the demo application and the "
+"standalone module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"For the most part the default values in these files need not be altered. "
+"However, the <property>com.arjuna.ats.arjuna.objectstore.objectStoreDir</"
+"property> property determines the location of the persistent store used to "
+"record transaction state. The default value of <filename>C:/temp/"
+"ObjectStore</filename> should be changed to a value appropriate to your "
+"system. For production environments this directory should reside on fault "
+"tolerant media such as a RAID array."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"When a standalone coordinator is being used by an application it is "
+"necessary to enable and modify two further properties in <filename>wstx.xml</"
+"filename>, <property>com.arjuna.mw.wst.coordinatorURL</property> and "
+"<property>com.arjuna.mw.wst.terminatorURL</property>. These contain the URLs "
+"necessary for the client application to contact the standalone coordinator "
+"and should be configured with the correct hostname and port of the "
+"standalone coordinator."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"JBossTS is highly modular so in order to allow for flexible deployment of "
+"individual components, the same property values are sometimes required to "
+"appear in more than one configuration file. For the majority of "
+"configurations, you should maintain consistent values for properties that "
+"are defined in more than one file."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:207
+#, no-c-format
+msgid "Deploying the Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"The JBossTS Web Service Transaction Manager component consists of a number "
+"of JAR files containing the application’s class files, plus Web service "
+"(WAR) files which expose the necessary services. Programmers will typically "
+"include all these components in their application EAR file during "
+"application development, simplifying deployment of the transaction "
+"infrastructure. For production usage the Transaction Manager may be "
+"installed as an application in its own right, allowing for centralized "
+"configuration and management at the server level, independent of specific "
+"applications. The demonstration application shipped with JBossTS provides a "
+"sample deployment descriptor illustrating how the Transaction Manager "
+"components can be included in an application."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"JBossTS 4.0 uses fixed endpoints for its underlying protocol communication. "
+"Therefore, problems may arise if multiple applications using JBossTS are "
+"deployed to the same server concurrently. If you wish to deploy several "
+"transactional applications in the same server, the Transaction Manger must "
+"be deployed as a separate application and not embedded within the deployment "
+"of individual applications."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid ""
+"The coordinator directory in the JBossTS installation has been provided to "
+"assist in the configuration and deployment of a stand-alone transaction "
+"manager. In order to use this, you must:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:220
+#, fuzzy, no-c-format
+msgid "Have JBoss Enterprise Application Platform 5 installed"
+msgstr "Plataforma de Aplicativo JBoss Enterprise"
+
+#. Tag: para
+#: Chapter.xml:225
+#, no-c-format
+msgid "Install ant 1.4 or later."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:231
+#, no-c-format
+msgid ""
+"It is important that a separate application server installation be used from "
+"the one that clients and services are deployed into since otherwise "
+"conflicts may occur between the various JBossTS components."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:235
+#, no-c-format
+msgid ""
+"You must then edit the build.xml included with coordinator to point to the "
+"application server installation where the transaction coordinator will be "
+"deployed and the location of the JBossTS installation. The files "
+"<filename>ws-c_jaxm_web-app.xml</filename> and <filename>ws-t_jaxm_web-app."
+"xml</filename> in the <filename>dd</filename> directory of coordinator are "
+"the deployment descriptors for the WS-C and WS-T WAR files. These files "
+"contain templated URLs. During the build phase, ant will substitute the "
+"hostname and port values you specify in the <filename>build.xml</filename> "
+"into these files."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:238
+#, no-c-format
+msgid ""
+"Run <code>ant</code>, with <code>target deploy-weblogic</code>, <code>deploy-"
+"jboss</code> or <code>deploy-webmethods</code>, to create and deploy a new "
+"coordinator into the correct application server installation."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:241
+#, no-c-format
+msgid ""
+"Now all you need to do is point your client at the required coordinator. To "
+"do this, generate the demo application specifying the port and hostname of "
+"the coordinator."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:245
+#, no-c-format
+msgid "Deployment descriptors"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:246
+#, no-c-format
+msgid ""
+"In general, it should not be necessary to change the contents of the various "
+"deployment descriptors used by JBossTS. However, if you do need to modify "
+"them they are all included in the coordinator module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:250
+#, no-c-format
+msgid ""
+"Not all JBossTS components have ready access to the information in the "
+"deployment descriptors. Therefore, if you modify the JNDI names used by any "
+"of the WS-C or WS-T deployment descriptors you may need to inform other "
+"JBossTS components at runtime. This can be accomplished by setting an "
+"appropriate property in the <filename>wstx.xml</filename> configuration file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:253
+#, no-c-format
+msgid ""
+"The following table shows the default JNDI name used by the deployment "
+"descriptors and the corresponding property to set if the default value is "
+"changed."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:257
+#, no-c-format
+msgid "Deployment descriptor values and properties"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:261
+#, no-c-format
+msgid "JNDI Name"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:262
+#, no-c-format
+msgid "Property"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:267
+#, no-c-format
+msgid "Activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:268
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:271
+#, no-c-format
+msgid "Activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:272
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:275
+#, no-c-format
+msgid "Completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:276
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:279
+#, no-c-format
+msgid "Registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:280
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:283
+#, no-c-format
+msgid "durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:284
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:287
+#, no-c-format
+msgid "durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:288
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:291
+#, no-c-format
+msgid "volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:292
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:295
+#, no-c-format
+msgid "volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:296
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:299
+#, no-c-format
+msgid "businessagreementwithparticipantcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:300
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:303
+#, no-c-format
+msgid "businessagreementwithparticipantcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:304
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:307
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:308
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:311
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:312
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccparticipant"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:319
+#, no-c-format
msgid "JBoss Transactions runtime information"
msgstr "Informação de tempo de execução de Transações JBoss"
#. Tag: para
-#: Chapter.xml:29
+#: Chapter.xml:320
#, 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 "Cada módulo, do qual compromete as Transações JBoss, possui uma classe chamada Info. Todas estas classes fornecem um único método toString, que retorna um documento XML, representando a informação de configuração para aquele módulo. Por exemplo: "
+msgstr ""
+"Cada módulo, do qual compromete as Transações JBoss, possui uma classe "
+"chamada Info. Todas estas classes fornecem um único método toString, que "
+"retorna um documento XML, representando a informação de configuração para "
+"aquele módulo. Por exemplo: "
#. Tag: programlisting
-#: Chapter.xml:31
+#: Chapter.xml:322
#, no-c-format
msgid ""
"<module-info name=\"arjuna\">\n"
@@ -156,13 +1010,13 @@
"</module-info>"
#. Tag: title
-#: Chapter.xml:34
+#: Chapter.xml:325
#, no-c-format
msgid "Failure recovery administration"
msgstr "Administração de recuperação da falha"
#. Tag: para
-#: Chapter.xml:35
+#: Chapter.xml:326
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions will ensure that "
@@ -176,16 +1030,30 @@
"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 "O sub-sistema de recuperação da falha de Transações JBoss irão garantir que os resultados de uma transação serão aplicados constantemente a todos os recursos afetados pela transação, mesmo que qualquer um dos processos de aplicativo, ou a máquina que os hospeda, travar ou perder a conexão da rede. No caso da máquina (sistema) travar ou a rede falhar, a recuperação não tomará lugar até que o sistema ou a rede forem restaurados. Contudo, o aplicativo original não precisa ser restaurado. A responsabilidade da recuperação é delegar o processo Gerenciador de Recuperação (veja abaixo). A recuperação, depois da falha, solicita que a informação sobre a transação e recursos envolvidos sobrevivam a falha e sejam acessíveis mais tarde (esta informação é retida no ActionStore, do qual faz parte do ObjectStore.)"
+msgstr ""
+"O sub-sistema de recuperação da falha de Transações JBoss irão garantir que "
+"os resultados de uma transação serão aplicados constantemente a todos os "
+"recursos afetados pela transação, mesmo que qualquer um dos processos de "
+"aplicativo, ou a máquina que os hospeda, travar ou perder a conexão da rede. "
+"No caso da máquina (sistema) travar ou a rede falhar, a recuperação não "
+"tomará lugar até que o sistema ou a rede forem restaurados. Contudo, o "
+"aplicativo original não precisa ser restaurado. A responsabilidade da "
+"recuperação é delegar o processo Gerenciador de Recuperação (veja abaixo). A "
+"recuperação, depois da falha, solicita que a informação sobre a transação e "
+"recursos envolvidos sobrevivam a falha e sejam acessíveis mais tarde (esta "
+"informação é retida no ActionStore, do qual faz parte do ObjectStore.)"
#. Tag: para
-#: Chapter.xml:38
+#: Chapter.xml:329
#, no-c-format
-msgid "If the ObjectStore is destroyed or modified, recovery may not be possible."
-msgstr "Caso um ObjectStore seja destruído ou modificado, a recuperação talvez não seja disponível."
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+"Caso um ObjectStore seja destruído ou modificado, a recuperação talvez não "
+"seja disponível."
#. Tag: para
-#: Chapter.xml:41
+#: Chapter.xml:332
#, no-c-format
msgid ""
"Until the recovery procedures are complete, resources affected by a "
@@ -195,17 +1063,21 @@
"resources, an attempt to activate the Transactional Object (as when trying "
"to get a lock) will fail."
msgstr ""
-"Até que os processos de recuperação sejam completados, os recursos afetados pela transação, que estava em processo no período da falha, poderão tornar-se inacessíveis. Isto poderá ser relatado como tabelas ou filas retidas pelas “in-doubt transactions” (transações suspeitas). A tentativa de ativar o Objeto transacional (como, por exemplo, tentar obter um travamento) falhará para TransactionalObjects "
-"em recursos Java."
+"Até que os processos de recuperação sejam completados, os recursos afetados "
+"pela transação, que estava em processo no período da falha, poderão tornar-"
+"se inacessíveis. Isto poderá ser relatado como tabelas ou filas retidas "
+"pelas “in-doubt transactions” (transações suspeitas). A tentativa de ativar "
+"o Objeto transacional (como, por exemplo, tentar obter um travamento) "
+"falhará para TransactionalObjects em recursos Java."
#. Tag: title
-#: Chapter.xml:43
+#: Chapter.xml:334
#, no-c-format
msgid "The Recovery Manager"
msgstr "O Gerenciamento de Recuperação"
#. Tag: para
-#: Chapter.xml:44
+#: Chapter.xml:335
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions requires that the stand-"
@@ -216,37 +1088,45 @@
"RecoveryManager</classname>. To start the Recovery Manager issue the "
"following command:"
msgstr ""
-"O sub-sistema de recuperação de falha de Transações JBoss solicita que o processo Gerenciador de Recuperação stand-alone rode para cada ObjectStore (tipicamente, um para cada nó na rede que está rodando os aplicativos de Transações JBoss). O arquivo RecoveryManager está localizado no arquivo de jarra arjunacore com o pacote <classname>com.arjuna.ats.arjuna.recovery."
-"RecoveryManager</classname>. Use o seguinte comando para iniciar o Gerenciador de Recuperação:"
+"O sub-sistema de recuperação de falha de Transações JBoss solicita que o "
+"processo Gerenciador de Recuperação stand-alone rode para cada ObjectStore "
+"(tipicamente, um para cada nó na rede que está rodando os aplicativos de "
+"Transações JBoss). O arquivo RecoveryManager está localizado no arquivo de "
+"jarra arjunacore com o pacote <classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryManager</classname>. Use o seguinte comando para iniciar o "
+"Gerenciador de Recuperação:"
#. Tag: command
-#: Chapter.xml:45
+#: Chapter.xml:336
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
#. Tag: para
-#: Chapter.xml:46
+#: Chapter.xml:337
#, 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 "Caso o aviso <literal>-test</literal> seja usado com o Gerenciador de Recuperação, será exibida uma mensagem “Ready”, uma vez que isto for inicializado: Por exemplo:"
+msgstr ""
+"Caso o aviso <literal>-test</literal> seja usado com o Gerenciador de "
+"Recuperação, será exibida uma mensagem “Ready”, uma vez que isto for "
+"inicializado: Por exemplo:"
#. Tag: command
-#: Chapter.xml:47
+#: Chapter.xml:338
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
#. Tag: title
-#: Chapter.xml:50
+#: Chapter.xml:341
#, no-c-format
msgid "Configuring the Recovery Manager"
msgstr "Configurando o Gerenciador de Recuperação"
#. Tag: para
-#: Chapter.xml:51
+#: Chapter.xml:342
#, no-c-format
msgid ""
"The RecoveryManager reads the properties defined in the <filename>arjuna."
@@ -258,10 +1138,16 @@
"specific to the Recovery Manager."
msgstr ""
"O RecoveryManager lê as propriedades definidas no arquivo <filename>arjuna."
-"properties</filename> e, também, lê o arquivo de propriedade <filename>RecoveryManager.properties</filename>, a partir do mesmo diretório como encontrado no arquivo de propriedade arjuna. Uma entrada para uma propriedade no arquivo de propriedades RecoveryManager irá substituir uma entrada para a mesma propriedade no arquivo principal de propriedades TransactionService. A maioria das entradas estão especificadas no Gerenciador de Recuperação. "
+"properties</filename> e, também, lê o arquivo de propriedade "
+"<filename>RecoveryManager.properties</filename>, a partir do mesmo diretório "
+"como encontrado no arquivo de propriedade arjuna. Uma entrada para uma "
+"propriedade no arquivo de propriedades RecoveryManager irá substituir uma "
+"entrada para a mesma propriedade no arquivo principal de propriedades "
+"TransactionService. A maioria das entradas estão especificadas no "
+"Gerenciador de Recuperação. "
#. Tag: para
-#: Chapter.xml:52
+#: Chapter.xml:343
#, no-c-format
msgid ""
"A default version of <filename>RecoveryManager.properties</filename> is "
@@ -270,16 +1156,22 @@
"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 "A versão padrão do <filename>RecoveryManager.properties</filename> é fornecida com a distribuição (isto pode ser usado sem modificação, com exceção da possibilidade de campos de rastreamento de depuração, veja o exemplo abaixo). O resto desta seção trata dos problemas relevantes de configuração de propriedades para outros valores (em ordem de sua aparência, na versão padrão do arquivo)."
+msgstr ""
+"A versão padrão do <filename>RecoveryManager.properties</filename> é "
+"fornecida com a distribuição (isto pode ser usado sem modificação, com "
+"exceção da possibilidade de campos de rastreamento de depuração, veja o "
+"exemplo abaixo). O resto desta seção trata dos problemas relevantes de "
+"configuração de propriedades para outros valores (em ordem de sua aparência, "
+"na versão padrão do arquivo)."
#. Tag: title
-#: Chapter.xml:54
+#: Chapter.xml:345
#, no-c-format
msgid "Output"
msgstr "Saída"
#. Tag: para
-#: Chapter.xml:55
+#: Chapter.xml:346
#, no-c-format
msgid ""
"It is likely that installations will want to have some form of output from "
@@ -291,12 +1183,17 @@
"Commons Logging framework and configuration is assumed to occur through that "
"framework."
msgstr ""
-"É bem comum que as instalações queiram ter alguma forma de saída do RecoveryManager, para fornecer um registro sobre os acontecimentos da atividade de recuperação. O RecoveryManager usa o mecanismo de rastreamento de log fornecido pelo Arjuna Common Logging Framework (CLF), do qual fornece uma interface de alto nível. Esta esconde diferenças existentes entre o log existente APIs como Jakarta "
-"log4j ou JDK 1.4 logging API. O CLF desvia todos os logs através do framework Apache "
-"Commons Logging e presume-se que a configuração ocorra através daquele framework. "
+"É bem comum que as instalações queiram ter alguma forma de saída do "
+"RecoveryManager, para fornecer um registro sobre os acontecimentos da "
+"atividade de recuperação. O RecoveryManager usa o mecanismo de rastreamento "
+"de log fornecido pelo Arjuna Common Logging Framework (CLF), do qual fornece "
+"uma interface de alto nível. Esta esconde diferenças existentes entre o log "
+"existente APIs como Jakarta log4j ou JDK 1.4 logging API. O CLF desvia todos "
+"os logs através do framework Apache Commons Logging e presume-se que a "
+"configuração ocorra através daquele framework. "
#. Tag: para
-#: Chapter.xml:58
+#: Chapter.xml:349
#, no-c-format
msgid ""
"With the CLF applications make logging calls on logger objects. Loggers may "
@@ -307,11 +1204,16 @@
"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
"FATAL."
msgstr ""
-"Usando os aplicativos CLF, efetue chamadas log nos objetos logger. Os loggers poderão usar os níveis log para decidir se eles estão interessados numa mensagem de log específica. Cada mensagem log possui um Nível log associado, do qual dá a importância e a urgência da mensagem log. O conjunto de possíveis Níveis de Log são DEBUG, INFO, WARN, ERROR e FATAL. Os níveis definidos são ordenados de acordo com os valores íntegros dos mesmos, como segue a seguir: DEBUG < INFO < WARN < ERROR < "
-"FATAL."
+"Usando os aplicativos CLF, efetue chamadas log nos objetos logger. Os "
+"loggers poderão usar os níveis log para decidir se eles estão interessados "
+"numa mensagem de log específica. Cada mensagem log possui um Nível log "
+"associado, do qual dá a importância e a urgência da mensagem log. O conjunto "
+"de possíveis Níveis de Log são DEBUG, INFO, WARN, ERROR e FATAL. Os níveis "
+"definidos são ordenados de acordo com os valores íntegros dos mesmos, como "
+"segue a seguir: DEBUG < INFO < WARN < ERROR < FATAL."
#. Tag: para
-#: Chapter.xml:61
+#: Chapter.xml:352
#, no-c-format
msgid ""
"The CLF provides an extension to filter logging messages according to finer "
@@ -319,49 +1221,62 @@
"provided to the logger with the DEBUG level, additional conditions can be "
"specified to determine if the log message is enabled or not."
msgstr ""
-"O CFL fornece uma extensão para filtrar mensagens de log de acordo com a definição de um aplicativo a respeito do finer "
-"granularity. Isto é, quando uma mensagem log é fornecida para o logger com o nível de DEBUG, condições adicionais poderão ser especificadas para determinar se uma mensagem log é ativada ou não."
+"O CFL fornece uma extensão para filtrar mensagens de log de acordo com a "
+"definição de um aplicativo a respeito do finer granularity. Isto é, quando "
+"uma mensagem log é fornecida para o logger com o nível de DEBUG, condições "
+"adicionais poderão ser especificadas para determinar se uma mensagem log é "
+"ativada ou não."
#. Tag: para
-#: Chapter.xml:67
+#: Chapter.xml:358
#, 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 "Estas condições são aplicadas \"se e apenas\" o nível DEBUG for ativado, e se a solicitação de log executada pelo aplicativo especificar a depuração granulada."
+msgstr ""
+"Estas condições são aplicadas \"se e apenas\" o nível DEBUG for ativado, e "
+"se a solicitação de log executada pelo aplicativo especificar a depuração "
+"granulada."
#. Tag: para
-#: Chapter.xml:71
+#: Chapter.xml:362
#, no-c-format
msgid "When enabled, Debugging is filtered conditionally on three variables:"
-msgstr "Uma vez ativada, a Depuração é filtrada condicionalmente em três variáveis:"
+msgstr ""
+"Uma vez ativada, a Depuração é filtrada condicionalmente em três variáveis:"
#. Tag: para
-#: Chapter.xml:74
+#: Chapter.xml:365
#, 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 "Nível de depuração: é onde a solicitação de log, com o Nível DEBUG, é gerado, por exemplo: construtores ou métodos básicos."
+msgstr ""
+"Nível de depuração: é onde a solicitação de log, com o Nível DEBUG, é "
+"gerado, por exemplo: construtores ou métodos básicos."
#. Tag: para
-#: Chapter.xml:77
+#: Chapter.xml:368
#, no-c-format
msgid ""
"Visibility level: the visibility of the constructor, method, etc. that "
"generates the debugging."
-msgstr "Nível de Visibilidade: a visibilidade do construtor, método, etc. Isto gera a depuração."
+msgstr ""
+"Nível de Visibilidade: a visibilidade do construtor, método, etc. Isto gera "
+"a depuração."
#. Tag: para
-#: Chapter.xml:80
+#: Chapter.xml:371
#, no-c-format
msgid ""
"Facility code: for instance the package or sub-module within which debugging "
"is generated, e.g., the object store."
-msgstr "Código de Facilidade: para instanciar o pacote ou sub-modulo com que a depuração é gerada, por exemplo: o armazenamento do objeto."
+msgstr ""
+"Código de Facilidade: para instanciar o pacote ou sub-modulo com que a "
+"depuração é gerada, por exemplo: o armazenamento do objeto."
#. Tag: para
-#: Chapter.xml:83
+#: Chapter.xml:374
#, no-c-format
msgid ""
"According to these variables the CLF defines three interfaces. A particular "
@@ -372,230 +1287,268 @@
"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 "O CLF define três interfaces de acordo com estas variáveis. Um produto particular poderá implementar a própria classe de acordo com o próprio finer granularity. As Transações JBoss usam o nível de Depuração padrão e o nível de Visibilidade padrão fornecida pelo CLF, porém isto determina o próprio Código de Facilidade. As Transações JBoss usam o nível padrão determinado para seus próprios objetos logger (DEBUG). No entanto, elas usam o recurso de depuração fina para desativar ou ativar as mensagens de depuração. Segue abaixo, os valores definidos de depuração fina usados pelas Transações JBoss:"
+msgstr ""
+"O CLF define três interfaces de acordo com estas variáveis. Um produto "
+"particular poderá implementar a própria classe de acordo com o próprio finer "
+"granularity. As Transações JBoss usam o nível de Depuração padrão e o nível "
+"de Visibilidade padrão fornecida pelo CLF, porém isto determina o próprio "
+"Código de Facilidade. As Transações JBoss usam o nível padrão determinado "
+"para seus próprios objetos logger (DEBUG). No entanto, elas usam o recurso "
+"de depuração fina para desativar ou ativar as mensagens de depuração. Segue "
+"abaixo, os valores definidos de depuração fina usados pelas Transações JBoss:"
#. Tag: para
-#: Chapter.xml:84
+#: Chapter.xml:375
#, 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 "Nível de depuração - as Transações JBoss usam os valores padrões definidos na classe <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+"Nível de depuração - as Transações JBoss usam os valores padrões definidos "
+"na classe <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
#. Tag: para
-#: Chapter.xml:87
+#: Chapter.xml:378
#, no-c-format
msgid ""
"NO_DEBUGGING: No diagnostics. A logger object assigned with this values "
"discard all debug requests"
-msgstr "NO_DEBUGGING: Não há diagnósticos. Um objeto logger determinado com estes valores descarta todas as solicitações de depuração"
+msgstr ""
+"NO_DEBUGGING: Não há diagnósticos. Um objeto logger determinado com estes "
+"valores descarta todas as solicitações de depuração"
#. Tag: para
-#: Chapter.xml:90
+#: Chapter.xml:381
#, 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 "FULL_DEBUGGING: Diagnóstico completo. Um objeto logger determinado com este valor permite todas as solicitações de depuração, no caso do código de facilidade e nível de visibilidade serem compatíveis com aqueles permitidos pelo logger. "
+msgstr ""
+"FULL_DEBUGGING: Diagnóstico completo. Um objeto logger determinado com este "
+"valor permite todas as solicitações de depuração, no caso do código de "
+"facilidade e nível de visibilidade serem compatíveis com aqueles permitidos "
+"pelo logger. "
#. Tag: para
-#: Chapter.xml:93
+#: Chapter.xml:384
#, no-c-format
msgid "Additional Debugging Values are:"
msgstr "Os Valores de Depuração Adicionais são:"
#. Tag: para
-#: Chapter.xml:96
+#: Chapter.xml:387
#, no-c-format
msgid "CONSTRUCTORS: Diagnostics from constructors."
msgstr "CONSTRUCTORS: Diagnósticos a partir de construtores."
#. Tag: para
-#: Chapter.xml:99
+#: Chapter.xml:390
#, no-c-format
msgid "DESTRUCTORS: Diagnostics from finalizers."
msgstr "DESTRUCTORS: Diagnósticos a partir de finalizadores."
#. Tag: para
-#: Chapter.xml:102
+#: Chapter.xml:393
#, no-c-format
msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
-msgstr "CONSTRUCT_AND_DESTRUCT: Diagnósticos a partir de construtores e finalizadores."
+msgstr ""
+"CONSTRUCT_AND_DESTRUCT: Diagnósticos a partir de construtores e "
+"finalizadores."
#. Tag: para
-#: Chapter.xml:105
+#: Chapter.xml:396
#, no-c-format
msgid "FUNCTIONS: Diagnostics from functions."
msgstr "FUNCTIONS: Diagnósticos a partir de funções."
#. Tag: para
-#: Chapter.xml:108
+#: Chapter.xml:399
#, no-c-format
msgid "OPERATORS: Diagnostics from operators, such as equals."
msgstr "OPERATORS: Diagnósticos a partir de operadores, como igualdades."
#. Tag: para
-#: Chapter.xml:111
+#: Chapter.xml:402
#, no-c-format
msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
msgstr "FUNCS_AND_OPS: Diagnósticos a partir de funções e operações."
#. Tag: para
-#: Chapter.xml:114
+#: Chapter.xml:405
#, no-c-format
msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
-msgstr "ALL_NON_TRIVIAL: Diagnósticos a partir de todas operações não-triviais."
+msgstr ""
+"ALL_NON_TRIVIAL: Diagnósticos a partir de todas operações não-triviais."
#. Tag: para
-#: Chapter.xml:117
+#: Chapter.xml:408
#, no-c-format
msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
msgstr "TRIVIAL_FUNCS: Diagnósticos a partir de funções triviais."
#. Tag: para
-#: Chapter.xml:120
+#: Chapter.xml:411
#, no-c-format
msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
-msgstr "TRIVIAL_OPERATORS: Diagnósticos a partir de operações triviais e operadores."
+msgstr ""
+"TRIVIAL_OPERATORS: Diagnósticos a partir de operações triviais e operadores."
#. Tag: para
-#: Chapter.xml:123
+#: Chapter.xml:414
#, no-c-format
msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
msgstr "ALL_TRIVIAL: Diagnósticos a partir de todas operações triviais."
#. Tag: para
-#: Chapter.xml:126
+#: Chapter.xml:417
#, 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 "Nível de Visibilidade - as Transações JBoss usam valores de padrão definido na classe <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+"Nível de Visibilidade - as Transações JBoss usam valores de padrão definido "
+"na classe <classname>com.arjuna.common.util.logging.VisibilityLevel</"
+"classname>"
#. Tag: para
-#: Chapter.xml:129
+#: Chapter.xml:420
#, no-c-format
msgid "VIS_NONE: No Diagnostic"
msgstr "VIS_NONE: Sem Diagnóstico"
#. Tag: para
-#: Chapter.xml:132
+#: Chapter.xml:423
#, no-c-format
msgid "VIS_PRIVATE : only from private methods."
msgstr "VIS_PRIVATE: apenas a partir de métodos privados."
#. Tag: para
-#: Chapter.xml:135
+#: Chapter.xml:426
#, no-c-format
msgid "VIS_PROTECTED only from protected methods."
msgstr "VIS_PROTECTED: apenas a partir de métodos protegidos."
#. Tag: para
-#: Chapter.xml:138
+#: Chapter.xml:429
#, no-c-format
msgid "VIS_PUBLIC only from public methods."
msgstr "VIS_PUBLIC: apenas a partir de métodos públicos."
#. Tag: para
-#: Chapter.xml:141
-#, no-c-format
-msgid "VIS_JBoss_Transactions_Administrators_Guide only from package methods."
-msgstr "VIS_JBoss_Transactions_Administrators_Guide: apenas a partir de métodos de pacote."
+#: Chapter.xml:432
+#, fuzzy, no-c-format
+msgid "VIS_PACKAGE only from package methods."
+msgstr "VIS_PUBLIC: apenas a partir de métodos públicos."
#. Tag: para
-#: Chapter.xml:144
+#: Chapter.xml:435
#, no-c-format
msgid "VIS_ALL: Full Diagnostic"
msgstr "VIS_ALL: Diagnóstico Completo"
#. Tag: para
-#: Chapter.xml:147
+#: Chapter.xml:438
#, 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 "Código de facilidade - as Transações JBoss usam os seguintes valores definidos na classe <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
+msgstr ""
+"Código de facilidade - as Transações JBoss usam os seguintes valores "
+"definidos na classe <classname>com.arjuna.common.util.logging."
+"VisibilityLevel</classname>"
#. Tag: para
-#: Chapter.xml:150
+#: Chapter.xml:441
#, no-c-format
msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
msgstr "FAC_ATOMIC_ACTION = 0x0000001 (código principal de função atômica)."
#. Tag: para
-#: Chapter.xml:153
+#: Chapter.xml:444
#, no-c-format
msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
-msgstr "FAC_BUFFER_MAN = 0x00000004 (classes [buffer] de gerenciamento de estado)."
+msgstr ""
+"FAC_BUFFER_MAN = 0x00000004 (classes [buffer] de gerenciamento de estado)."
#. Tag: para
-#: Chapter.xml:156
+#: Chapter.xml:447
#, no-c-format
msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
msgstr "FAC_ABSTRACT_REC = 0x00000008 (registros abstratos)."
#. Tag: para
-#: Chapter.xml:159
+#: Chapter.xml:450
#, no-c-format
msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
-msgstr "FAC_OBJECT_STORE = 0x00000010 (implementações de armazenamento de objeto)."
+msgstr ""
+"FAC_OBJECT_STORE = 0x00000010 (implementações de armazenamento de objeto)."
#. Tag: para
-#: Chapter.xml:162
+#: Chapter.xml:453
#, no-c-format
msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
msgstr "FAC_STATE_MAN = 0x00000020 (gerenciamento de estado e StateManager)."
#. Tag: para
-#: Chapter.xml:165
+#: Chapter.xml:456
#, no-c-format
msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
-msgstr "FAC_SHMEM = 0x00000040 (classes de implementação de memória compartilhada)."
+msgstr ""
+"FAC_SHMEM = 0x00000040 (classes de implementação de memória compartilhada)."
#. Tag: para
-#: Chapter.xml:168
+#: Chapter.xml:459
#, no-c-format
msgid "FAC_GENERAL = 0x00000080 (general classes)."
msgstr "FAC_GENERAL = 0x00000080 (classes em geral)."
#. Tag: para
-#: Chapter.xml:171
+#: Chapter.xml:462
#, no-c-format
msgid ""
"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
"classes)."
-msgstr "FAC_CRASH_RECOVERY = 0x00000800 (rastreamento detalhado de classes e módulo de recuperação de travamento)."
+msgstr ""
+"FAC_CRASH_RECOVERY = 0x00000800 (rastreamento detalhado de classes e módulo "
+"de recuperação de travamento)."
#. Tag: para
-#: Chapter.xml:174
+#: Chapter.xml:465
#, no-c-format
msgid "FAC_THREADING = 0x00002000 (threading classes)."
msgstr "FAC_THREADING = 0x00002000 (classes de segmentação)."
#. Tag: para
-#: Chapter.xml:177
+#: Chapter.xml:468
#, no-c-format
msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
msgstr "AC_JDBC = 0x00008000 (JDBC 1.0 e suporte 2.0)."
#. Tag: para
-#: Chapter.xml:180
+#: Chapter.xml:471
#, no-c-format
-msgid "FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
-msgstr "FAC_RECOVERY_NORMAL = 0x00040000 (saída normal para gerenciamento de recuperação de travamento)."
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (saída normal para gerenciamento de "
+"recuperação de travamento)."
#. Tag: para
-#: Chapter.xml:183
+#: Chapter.xml:474
#, 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 "Para garantia de uma saída apropriada, é necessário configurar, explicitamente, algumas das propriedades de depuração fina no arquivo <filename>CommonLogging.xml</filename>. Isto tudo, para ativar as mensagens de log emitidas pelo módulo de Transações JBoss."
+msgstr ""
+"Para garantia de uma saída apropriada, é necessário configurar, "
+"explicitamente, algumas das propriedades de depuração fina no arquivo "
+"<filename>CommonLogging.xml</filename>. Isto tudo, para ativar as mensagens "
+"de log emitidas pelo módulo de Transações JBoss."
#. Tag: para
-#: Chapter.xml:184
+#: Chapter.xml:475
#, no-c-format
msgid ""
"Messages describing the start and the periodical behavior made by the "
@@ -604,10 +1557,17 @@
"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 "As mensagens descrevem o início e o comportamento periódico feito pelo RecoveryManager como saída, se utilizarmos o nível de INFO. Caso outro rastreamento de depuração seja requerido, o nível de depuração fina deve ser propriamente configurado. Por exemplo, a configuração seguinte, no CommonLogging.xml, ativa todas as mensagens de depuração, relatadas ao protocolo de Recuperação de Travamento, e emitidas pelo módulo de Transações JBoss."
+msgstr ""
+"As mensagens descrevem o início e o comportamento periódico feito pelo "
+"RecoveryManager como saída, se utilizarmos o nível de INFO. Caso outro "
+"rastreamento de depuração seja requerido, o nível de depuração fina deve ser "
+"propriamente configurado. Por exemplo, a configuração seguinte, no "
+"CommonLogging.xml, ativa todas as mensagens de depuração, relatadas ao "
+"protocolo de Recuperação de Travamento, e emitidas pelo módulo de Transações "
+"JBoss."
#. Tag: programlisting
-#: Chapter.xml:186
+#: Chapter.xml:477
#, no-c-format
msgid ""
"<!-- Common logging related properties. -->\n"
@@ -629,15 +1589,17 @@
" value=\"0xffffffff\"/>"
#. Tag: para
-#: Chapter.xml:189
+#: Chapter.xml:480
#, no-c-format
msgid ""
"Two logger objects are provided, one manages I18N messages and a second does "
"not."
-msgstr "Dois objetos logger são fornecidos, um gerencia as mensagens I18N e o outro não."
+msgstr ""
+"Dois objetos logger são fornecidos, um gerencia as mensagens I18N e o outro "
+"não."
#. Tag: para
-#: Chapter.xml:192
+#: Chapter.xml:483
#, no-c-format
msgid ""
"Setting the normal recovery messages to the INFO level allows the "
@@ -646,16 +1608,23 @@
"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 "A configuração das mensagens de recuperação normal, para o nível INFO, permite um nível moderado de reportagem à Produção RecoveryManager. Caso nada aconteça, isto apenas relata a entrada em cada módulo para cada caminho periódico. Para desativar as mensagens INFO produzidas pelo Gerenciador de Recuperação, o nível log deverá ser configurado num nível mais alto: ERROR. Configurando o nível para ERROR significa que o RecoveryManager irá apenas produzir error, aviso ou mensagens fatais."
+msgstr ""
+"A configuração das mensagens de recuperação normal, para o nível INFO, "
+"permite um nível moderado de reportagem à Produção RecoveryManager. Caso "
+"nada aconteça, isto apenas relata a entrada em cada módulo para cada caminho "
+"periódico. Para desativar as mensagens INFO produzidas pelo Gerenciador de "
+"Recuperação, o nível log deverá ser configurado num nível mais alto: ERROR. "
+"Configurando o nível para ERROR significa que o RecoveryManager irá apenas "
+"produzir error, aviso ou mensagens fatais."
#. Tag: title
-#: Chapter.xml:196
+#: Chapter.xml:487
#, no-c-format
msgid "Periodic Recovery"
msgstr "Recuperação Periódica"
#. Tag: para
-#: Chapter.xml:197
+#: Chapter.xml:488
#, no-c-format
msgid ""
"The RecoveryManager scans the ObjectStore and other locations of "
@@ -667,11 +1636,17 @@
"used are dynamically loaded, using properties found in the RecoveryManager "
"property file."
msgstr ""
-"O RecoveryManager verifica o ObjectStore e outras localidades de informação, buscando por transações e recursos que requerem, ou talvez solicitarão, recuperação. A verificação e processo de recuperação são executados pelos módulos de recuperação (instâncias de classes que implementam a interface com.arjuna.ats."
-"arjuna.recovery.RecoveryModule), cada qual com a responsabilidade para uma categoria particular de transação ou recurso. O conjunto de módulos de recuperação usados estão dinamicamente carregados, usando propriedades encontradas no arquivo de propriedade RecoveryManager."
+"O RecoveryManager verifica o ObjectStore e outras localidades de informação, "
+"buscando por transações e recursos que requerem, ou talvez solicitarão, "
+"recuperação. A verificação e processo de recuperação são executados pelos "
+"módulos de recuperação (instâncias de classes que implementam a interface "
+"com.arjuna.ats.arjuna.recovery.RecoveryModule), cada qual com a "
+"responsabilidade para uma categoria particular de transação ou recurso. O "
+"conjunto de módulos de recuperação usados estão dinamicamente carregados, "
+"usando propriedades encontradas no arquivo de propriedade RecoveryManager."
#. Tag: para
-#: Chapter.xml:198
+#: Chapter.xml:489
#, no-c-format
msgid ""
"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
@@ -688,12 +1663,21 @@
"a candidate for recovery."
msgstr ""
"A interface possui dois métodos: <literal>periodicWorkFirstPass</literal> e "
-"<literal>periodicWorkSecondPass</literal>. Num intervalo, (definido pela propriedade <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
-"classname>) o RecoveryManager chamará o primeiro método de caminho em cada propriedade, e então esperará por um breve período (definido pela propriedade <classname>com."
-"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname>) para então chamar o segundo caminho de cada módulo. Basicamente, no primeiro caminho, o módulo faz a verificação (por exemplo; a parte relevante do ObjectStore) para encontrar transações ou recursos que são duvidosos (por exemplo; são parte do caminho através do processo de comprometimento). Já no segundo caminho, se qualquer um dos mesmos ítens ainda forem suspeitos, é possível que o processo do aplicativo original trave e o ítem seja um candidato para a recuperação. "
+"<literal>periodicWorkSecondPass</literal>. Num intervalo, (definido pela "
+"propriedade <classname>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</classname>) o RecoveryManager chamará o primeiro "
+"método de caminho em cada propriedade, e então esperará por um breve período "
+"(definido pela propriedade <classname>com.arjuna.ats.arjuna.recovery."
+"recoveryBackoffPeriod</classname>) para então chamar o segundo caminho de "
+"cada módulo. Basicamente, no primeiro caminho, o módulo faz a verificação "
+"(por exemplo; a parte relevante do ObjectStore) para encontrar transações ou "
+"recursos que são duvidosos (por exemplo; são parte do caminho através do "
+"processo de comprometimento). Já no segundo caminho, se qualquer um dos "
+"mesmos ítens ainda forem suspeitos, é possível que o processo do aplicativo "
+"original trave e o ítem seja um candidato para a recuperação. "
#. Tag: para
-#: Chapter.xml:199
+#: Chapter.xml:490
#, no-c-format
msgid ""
"An attempt, by the RecoveryManager, to recover a transaction that is still "
@@ -708,11 +1692,21 @@
"usually generating a warning. Recovery of such a transaction is the "
"RecoveryManager’s responsibility)."
msgstr ""
-"A tentativa de recuperar uma transação, pelo RecoveryManager, que ainda está sendo processada no(s) processo(s) original, poderá interromper a consistência. Conseqüentemente, os módulos de recuperação usam um mecanismo (implementado no pacote <classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
-"classname>) para checar se é que o processo original ainda está vivo e se a transação continua em progresso. O RecoveryManager apenas procede com a recuperação se o processo original se foi. Por outro lado, se ele estiver sobrevivido, a transação será completada. (Caso um processo do servidor ou sistema travar, mas o processo de inicialização de transação sobreviver, a transação será completada, normalmente gerando um aviso. A recuperação de tal transação é responsabilidade do RecoveryManager). "
+"A tentativa de recuperar uma transação, pelo RecoveryManager, que ainda está "
+"sendo processada no(s) processo(s) original, poderá interromper a "
+"consistência. Conseqüentemente, os módulos de recuperação usam um mecanismo "
+"(implementado no pacote <classname>com.arjuna.ats.arjuna.recovery."
+"TransactionStatusManager</classname>) para checar se é que o processo "
+"original ainda está vivo e se a transação continua em progresso. O "
+"RecoveryManager apenas procede com a recuperação se o processo original se "
+"foi. Por outro lado, se ele estiver sobrevivido, a transação será "
+"completada. (Caso um processo do servidor ou sistema travar, mas o processo "
+"de inicialização de transação sobreviver, a transação será completada, "
+"normalmente gerando um aviso. A recuperação de tal transação é "
+"responsabilidade do RecoveryManager). "
#. Tag: para
-#: Chapter.xml:200
+#: Chapter.xml:491
#, no-c-format
msgid ""
"It is clearly important to set the interval periods appropriately. The total "
@@ -732,20 +1726,39 @@
"thus require a “call to the original process to see if they are still in "
"progress"
msgstr ""
-"É muito importante configurar os períodos de intervalo propriamente. O período total de interação será a soma do <literal>periodicRecoveryPeriod</"
-"literal>, <literal>recoveryBackoffPeriod</literal> e o período de tempo necessário para verificar os armazenamentos e tentar a recuperação de quaisquer transações encontradas como duvidosas. Isto tudo, para todos os módulos de recuperação. O período de tentativa de recuperação poderá incluir conexões de intervalo enquanto tentando a comunicação com os processos ou sistemas que tenham travado ou estão inacessíveis (sendo este o motivo pelo qual existem mecanismos no mesmo sistema de recuperação para tentar evitar a recuperação de mesma transação para sempre). O período total de interação afetará quanto tempo um recurso permanecerá inacessível, após a falha. O <literal>periodicRecoveryPeriod</literal> deverá ser configurado em concordância (o padrão é 120 segundos). O <literal>recoveryBackoffPeriod</literal> pode ser relativamente menor (o padrão é 10 segundos). Isto tudo, com a principal intenção de reduzir o número de transações qu!
e são candidatas para a recuperação, e desta forma, solicitar uma \"chamada ao processo original para a verificação de que elas ainda estão em progresso\"."
+"É muito importante configurar os períodos de intervalo propriamente. O "
+"período total de interação será a soma do <literal>periodicRecoveryPeriod</"
+"literal>, <literal>recoveryBackoffPeriod</literal> e o período de tempo "
+"necessário para verificar os armazenamentos e tentar a recuperação de "
+"quaisquer transações encontradas como duvidosas. Isto tudo, para todos os "
+"módulos de recuperação. O período de tentativa de recuperação poderá incluir "
+"conexões de intervalo enquanto tentando a comunicação com os processos ou "
+"sistemas que tenham travado ou estão inacessíveis (sendo este o motivo pelo "
+"qual existem mecanismos no mesmo sistema de recuperação para tentar evitar a "
+"recuperação de mesma transação para sempre). O período total de interação "
+"afetará quanto tempo um recurso permanecerá inacessível, após a falha. O "
+"<literal>periodicRecoveryPeriod</literal> deverá ser configurado em "
+"concordância (o padrão é 120 segundos). O <literal>recoveryBackoffPeriod</"
+"literal> pode ser relativamente menor (o padrão é 10 segundos). Isto tudo, "
+"com a principal intenção de reduzir o número de transações que são "
+"candidatas para a recuperação, e desta forma, solicitar uma \"chamada ao "
+"processo original para a verificação de que elas ainda estão em progresso\"."
#. Tag: para
-#: Chapter.xml:203
+#: Chapter.xml:494
#, 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 "Nas versões anteriores de Transações JBoss não havia mecanismo de contato, além de que o período de backoff necessitava ser longo o suficiente para evitar que transações de captura fossem perdidas pelo mundo afora. Este risco não ocorre a partir do 3.0."
+msgstr ""
+"Nas versões anteriores de Transações JBoss não havia mecanismo de contato, "
+"além de que o período de backoff necessitava ser longo o suficiente para "
+"evitar que transações de captura fossem perdidas pelo mundo afora. Este "
+"risco não ocorre a partir do 3.0."
#. Tag: para
-#: Chapter.xml:206
+#: Chapter.xml:497
#, no-c-format
msgid ""
"Two recovery modules (implementations of the <classname>com.arjuna.ats."
@@ -761,12 +1774,22 @@
"process might occur while a periodic recovery pass is in progress). The "
"default Recovery Extension settings are:"
msgstr ""
-"Dois módulos de recuperação (implementações da interface <classname>com.arjuna.ats."
-"arjuna.recovery.RecoveryModule</classname>) são supridos com as Transações JBoss, suportando vários aspectos de recuperação de transação, incluindo a recuperação JDBC. É possível que os usuários mais avançados criem os próprios módulos de recuperação e registrem-os com o Gerenciador de Recuperação. Os módulos de recuperação são registrados como o RecoveryManager usando as propriedades que inicializam com “<classname>com.arjuna.ats.arjuna.recovery."
-"RecoveryExtension</classname>”. Isto será invocado em cada caminho de recuperação periódica em certa ordem de nomes de propriedades - desta forma é possível predizer a ordenação (mas perceba que a falha em um processo de aplicativo poderá ocorrer enquanto o caminho de recuperação periódico estiver em progresso). As configurações de Extensão de recuperação padrão são as seguintes: "
+"Dois módulos de recuperação (implementações da interface <classname>com."
+"arjuna.ats.arjuna.recovery.RecoveryModule</classname>) são supridos com as "
+"Transações JBoss, suportando vários aspectos de recuperação de transação, "
+"incluindo a recuperação JDBC. É possível que os usuários mais avançados "
+"criem os próprios módulos de recuperação e registrem-os com o Gerenciador de "
+"Recuperação. Os módulos de recuperação são registrados como o "
+"RecoveryManager usando as propriedades que inicializam com “<classname>com."
+"arjuna.ats.arjuna.recovery.RecoveryExtension</classname>”. Isto será "
+"invocado em cada caminho de recuperação periódica em certa ordem de nomes de "
+"propriedades - desta forma é possível predizer a ordenação (mas perceba que "
+"a falha em um processo de aplicativo poderá ocorrer enquanto o caminho de "
+"recuperação periódico estiver em progresso). As configurações de Extensão de "
+"recuperação padrão são as seguintes: "
#. Tag: programlisting
-#: Chapter.xml:208
+#: Chapter.xml:499
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
@@ -782,13 +1805,13 @@
" com.arjuna.ats.txoj.recovery.TORecoveryModule"
#. Tag: title
-#: Chapter.xml:211
+#: Chapter.xml:502
#, no-c-format
msgid "Expired entry removal"
msgstr "Remoção da entrada expirada"
#. Tag: para
-#: Chapter.xml:212
+#: Chapter.xml:503
#, no-c-format
msgid ""
"The operation of the recovery subsystem will cause some entries to be made "
@@ -808,18 +1831,31 @@
"value is negative, the first scan is delayed until after the first interval "
"(using the absolute value)"
msgstr ""
-"A operação do sub-sistema de recuperação fará com que algumas entradas sejam feitas no ObjectStore, das quais não serão removidas em progresso normal. O RecoveryManager possui a facilidade de verificação destes e dos ítens removidos, dos quais são bastante antigos. A verificação e remoção são executadas pelas implementações da interface <classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname>. As implementações desta interface são carregadas fornecendo o nome de classe como um valor de uma propriedade pela qual o nome começa com <classname>com.arjuna."
-"ats.arjuna.recovery.expiryScanner</classname>. O RecoveryManager chama o método <command>scan()</command> em cada implementação carregada de Expiry Scanner, no intervalo determinado pela propriedade <classname>com."
-"arjuna.ats.arjuna.recovery.expiryScanInterval</classname>. Este valor é dado em horas - o padrão é 12. Um <classname>expiryScanInterval</classname> de valor zero irá suprir qualquer verificação expirada. Caso o valor fornecido seja positivo, a primeira verificação é impedida até o final do primeiro intervalo (usando o valor absoluto)."
+"A operação do sub-sistema de recuperação fará com que algumas entradas sejam "
+"feitas no ObjectStore, das quais não serão removidas em progresso normal. O "
+"RecoveryManager possui a facilidade de verificação destes e dos ítens "
+"removidos, dos quais são bastante antigos. A verificação e remoção são "
+"executadas pelas implementações da interface <classname>com.arjuna.ats."
+"arjuna.recovery.ExpiryScanner</classname>. As implementações desta interface "
+"são carregadas fornecendo o nome de classe como um valor de uma propriedade "
+"pela qual o nome começa com <classname>com.arjuna.ats.arjuna.recovery."
+"expiryScanner</classname>. O RecoveryManager chama o método <command>scan()</"
+"command> em cada implementação carregada de Expiry Scanner, no intervalo "
+"determinado pela propriedade <classname>com.arjuna.ats.arjuna.recovery."
+"expiryScanInterval</classname>. Este valor é dado em horas - o padrão é 12. "
+"Um <classname>expiryScanInterval</classname> de valor zero irá suprir "
+"qualquer verificação expirada. Caso o valor fornecido seja positivo, a "
+"primeira verificação é impedida até o final do primeiro intervalo (usando o "
+"valor absoluto)."
#. Tag: para
-#: Chapter.xml:213
+#: Chapter.xml:504
#, no-c-format
msgid "The kinds of item that are scanned for expiry are:"
msgstr "Os tipos de ítens que são verificados pela expiração são o seguinte:"
#. Tag: para
-#: Chapter.xml:214
+#: Chapter.xml:505
#, no-c-format
msgid ""
"TransactionStatusManager items : one of these is created by every "
@@ -831,17 +1867,23 @@
"– default is 12, zero means never expire). The expiry time should be greater "
"than the lifetime of any single JBoss Transactions-using process."
msgstr ""
-"Ítens de TransactionStatusManager: um deles é criado por cada processo de aplicativo que usa as Transações JBoss - eles contêm a informação que permite o RecoveryManager a determinar se o processo que inicializou a transação sobreviveu, e qual é o status da transação. O tempo de expiração para isto é configurado pela propriedade <classname>com.arjuna."
-"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname> (em horas - o padrão é 12, zero quer dizer nunca expirado). O tempo de expiração deve ser maior do que o tempo de vida de qualquer Transação JBoss simples, processo de uso."
+"Ítens de TransactionStatusManager: um deles é criado por cada processo de "
+"aplicativo que usa as Transações JBoss - eles contêm a informação que "
+"permite o RecoveryManager a determinar se o processo que inicializou a "
+"transação sobreviveu, e qual é o status da transação. O tempo de expiração "
+"para isto é configurado pela propriedade <classname>com.arjuna.ats.arjuna."
+"recovery.transactionStatusManagerExpiryTime</classname> (em horas - o padrão "
+"é 12, zero quer dizer nunca expirado). O tempo de expiração deve ser maior "
+"do que o tempo de vida de qualquer Transação JBoss simples, processo de uso."
#. Tag: para
-#: Chapter.xml:215
+#: Chapter.xml:506
#, no-c-format
msgid "The Expiry Scanner properties for these are:"
msgstr "As propriedades de Verificação de Expiração são as seguintes:"
#. Tag: programlisting
-#: Chapter.xml:217
+#: Chapter.xml:508
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
@@ -853,148 +1895,319 @@
"ExpiredTransactionStatusManagerScanner"
#. Tag: title
-#: Chapter.xml:220
+#: Chapter.xml:511
#, no-c-format
-msgid "Errors and Exceptions"
-msgstr "Erros e Exceções"
+msgid "Selecting the JTA implementation"
+msgstr "Selecionando a implementação JTA"
#. Tag: para
-#: Chapter.xml:221
+#: Chapter.xml:512
#, 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 "Nesta seção, iremos converter os tipos de erros e exceções que possam ser jogados ou relatados durante um aplicativo transacional, além de fornecer indicações prováveis de suas causas."
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+"Duas variantes da implementação JTA são agora fornecidas e acessíveis "
+"através da mesma interface. Elas são:"
#. Tag: para
-#: Chapter.xml:224
+#: Chapter.xml:515
#, 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 "NO_MEMORY: o aplicativo não possui mais memória (adicione um <classname>OutOfMemoryError</classname>) e as Transações JBoss tentaram realizar uma limpeza (apenas rodando o coletor de lixo) antes de re-adicionar a exceção. Isto é provavelmente um problema transitório e a nova tentativa de invocação deverá ser bem sucedida. "
+"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 ""
+"Um puro JTA local, que apenas permite transações JTA não-distribuídas a "
+"serem executadas. Esta é a única versão disponível com o produto de "
+"Transações JBoss."
#. Tag: para
-#: Chapter.xml:227
+#: Chapter.xml:518
#, 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 "com.arjuna.ats.arjuna.exceptions.FatalError: ocorreu um erro significando que o sistema de transação deve ser desligado. Antes deste erro ser lançado, o serviço de transação irá certificar-se de que todas as transações tenham sido revertidas. Caso detectado, o aplicativo deverá limpar e encerrar o sistema. E, se houver uma tentativa de um futuro trabalho, a consistência do aplicativo poderá ser violada."
+"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 ""
+"Uma remoção, JTA CORBA baseada, que permite transações JTA distribuídas a "
+"serem executadas. Esta versão é apenas disponível com o produto ArjunaJTS e "
+"requer um CORBA ORB suportado."
#. Tag: para
-#: Chapter.xml:230
+#: Chapter.xml:522
#, 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 "com.arjuna.ats.arjuna.exceptions.LicenceError: foi realizada uma tentativa para usar o serviço de transação de uma maneira inconsistente com a licença atual. O serviço de transação não permitirá nenhum progresso futuro para novas ou existentes transações."
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr ""
+"ambas implementações são inteiramente compatíveis com o driver JDBC "
+"transacional fornecido com as Transações JBoss."
#. Tag: para
-#: Chapter.xml:233
+#: Chapter.xml:525
#, 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 "com.arjuna.ats.arjuna.exceptions.ObjectStoreError: um erro foi detectado enquanto o serviço de transação tentava usar o armazenamento do objeto. Não foi possível realizar um progresso."
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+"Para se realizar a seleção da implementação local JTA local, é necessário "
+"executar os seguintes passos:"
#. Tag: para
-#: Chapter.xml:236
+#: Chapter.xml:528
#, 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 "O armazenamento do objeto avisa antecipadamente que os problemas de acesso nos estados poderão ocorrer durante a execução normal da recuperação de travamento. Este é o resultado de tentativas atuais múltiplas para recuperar o desempenho na mesma transação. Isto pode ser facilmente ignorado."
+"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 ""
+"certifique-se de que a propriedade <literal>com.arjuna.ats.jta."
+"jtaTMImplementation</literal> é configurada para <literal>com.arjuna.ats."
+"internal.jta.transaction.arjunacore.TransactionManagerImple</literal>."
+#. Tag: para
+#: Chapter.xml:531
+#, 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 ""
+"certifique-se de que a propriedade <literal>com.arjuna.ats.jta."
+"jtaUTImplementation</literal> é configurada para <literal>com.arjuna.ats."
+"internal.jta.transaction.arjunacore.UserTransactionImple</literal>."
+
+#. Tag: para
+#: Chapter.xml:535
+#, 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 ""
+"estas configurações são valores padrões para as propriedades e não precisam "
+"ser especificadas, caso a implementação local seja requerida."
+
#. Tag: title
-#: Chapter.xml:241
+#: Chapter.xml:542
#, no-c-format
-msgid "Selecting the JTA implementation"
-msgstr "Selecionando a implementação JTA"
+msgid "ORB specific configurations"
+msgstr ""
+#. Tag: title
+#: Chapter.xml:544
+#, no-c-format
+msgid "<title>JacORB</title>"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:242
+#: Chapter.xml:545
#, no-c-format
msgid ""
-"Two variants of the JTA implementation are now provided and accessible "
-"through the same interface. These are:"
-msgstr "Duas variantes da implementação JTA são agora fornecidas e acessíveis através da mesma interface. Elas são:"
+"For JacORB to function correctly it is necessary to ensure there is a valid "
+"<filename>jacorb.properties</filename> or <filename>.jacorb_properties</"
+"filename> file in one of the following places:"
+msgstr ""
#. Tag: para
-#: Chapter.xml:245
+#: Chapter.xml:551
#, no-c-format
+msgid "The classpath."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:556
+#, 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 "Um puro JTA local, que apenas permite transações JTA não-distribuídas a serem executadas. Esta é a única versão disponível com o produto de Transações JBoss."
+"The home directory of the user running the JBoss Transaction Service. The "
+"home directory is retrieved using <code>System.getProperty( “user.home” );</"
+"code>"
+msgstr ""
#. Tag: para
-#: Chapter.xml:248
+#: Chapter.xml:561
#, no-c-format
+msgid "The current directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:566
+#, 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 "Uma remoção, JTA CORBA baseada, que permite transações JTA distribuídas a serem executadas. Esta versão é apenas disponível com o produto ArjunaJTS e requer um CORBA ORB suportado."
+"The <filename>lib</filename> directory of the JDK used to run your "
+"application. This is retrieved using <code>System.getProperty( “java.home” );"
+"</code>"
+msgstr ""
#. Tag: para
-#: Chapter.xml:252
+#: Chapter.xml:571
#, no-c-format
msgid ""
-"both of these implementations are fully compatible with the transactional "
-"JDBC driver provided with JBoss Transactions."
-msgstr "ambas implementações são inteiramente compatíveis com o driver JDBC transacional fornecido com as Transações JBoss."
+"The above places are searched in the order given. A template "
+"<filename>jacorb.properties</filename> file can be found in the JacORB "
+"installation directory."
+msgstr ""
#. Tag: para
-#: Chapter.xml:255
+#: Chapter.xml:574
#, no-c-format
msgid ""
-"In order to select the local JTA implementation it is necessary to perform "
-"the following steps:"
-msgstr "Para se realizar a seleção da implementação local JTA local, é necessário executar os seguintes passos:"
+"Within the JacORB properties file there are two important properties which "
+"must be tailored to suit your application, they are:"
+msgstr ""
+#. Tag: property
+#: Chapter.xml:580
+#, no-c-format
+msgid "jacorb.poa.thread_pool_max"
+msgstr ""
+
+#. Tag: property
+#: Chapter.xml:585
+#, no-c-format
+msgid "jacorb.poa.thread_pool_min"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:258
+#: Chapter.xml:589
#, 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>."
+"These properties specify the minimum and maximum number of request "
+"processing threads that JacORB will use in its thread pool. If there aren’t "
+"a sufficient number of threads available in this thread pool then the "
+"application may appear to become deadlocked. For more information on "
+"configuring JacORB please reference the JacORB documentation."
msgstr ""
-"certifique-se de que a propriedade <literal>com.arjuna.ats.jta.jtaTMImplementation</"
-"literal> é configurada para <literal>com.arjuna.ats.internal.jta.transaction."
-"arjunacore.TransactionManagerImple</literal>."
#. Tag: para
-#: Chapter.xml:261
+#: Chapter.xml:593
#, 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>."
+"JacORB comes with its own implementation of the classes defined in the "
+"<filename>CosTransactions.idl</filename> file. Unfortunately these are "
+"incompatible with the version shipped with JBossTS. Therefore, it is "
+"important that the JBossTS jar files appear in the <code>CLASSPATH</code> "
+"before any JacORB jars."
msgstr ""
-"certifique-se de que a propriedade <literal>com.arjuna.ats.jta.jtaUTImplementation</"
-"literal> é configurada para <literal>com.arjuna.ats.internal.jta.transaction."
-"arjunacore.UserTransactionImple</literal>."
#. Tag: para
-#: Chapter.xml:265
+#: Chapter.xml:597
#, 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 "estas configurações são valores padrões para as propriedades e não precisam ser especificadas, caso a implementação local seja requerida."
+"When running the recovery manager it is important that it always uses the "
+"same well known port for each machine on which it runs. You should not use "
+"the OAPort property provided by JacORB unless the recovery manager has its "
+"own <filename>jacorb.properties</filename> file or this is provided on the "
+"command line when starting the recovery manager. If the recovery manager and "
+"other components of JBossTS share the same <filename>jacorb.properties</"
+"filename> file, then you should use the <filename>com.arjuna.ats.jts."
+"recoveryManagerPort</filename> and <filename>com.arjuna.ats.jts."
+"recoveryManagerAddress</filename> properties."
+msgstr ""
+#. Tag: title
+#: Chapter.xml:603
+#, no-c-format
+msgid "Initializing JBossTS applications"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:604
+#, no-c-format
+msgid ""
+"It is important that JBossTS is correctly initialized prior to any "
+"application object being created. In order to guarantee this, the programmer "
+"should use the <methodname>ORB_init</methodname> and <methodname>create_POA</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:609
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr "Erros e Exceções"
+
+#. Tag: para
+#: Chapter.xml:610
+#, 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 ""
+"Nesta seção, iremos converter os tipos de erros e exceções que possam ser "
+"jogados ou relatados durante um aplicativo transacional, além de fornecer "
+"indicações prováveis de suas causas."
+
+#. Tag: para
+#: Chapter.xml:613
+#, 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 ""
+"NO_MEMORY: o aplicativo não possui mais memória (adicione um "
+"<classname>OutOfMemoryError</classname>) e as Transações JBoss tentaram "
+"realizar uma limpeza (apenas rodando o coletor de lixo) antes de re-"
+"adicionar a exceção. Isto é provavelmente um problema transitório e a nova "
+"tentativa de invocação deverá ser bem sucedida. "
+
+#. Tag: para
+#: Chapter.xml:616
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: ocorreu um erro significando "
+"que o sistema de transação deve ser desligado. Antes deste erro ser lançado, "
+"o serviço de transação irá certificar-se de que todas as transações tenham "
+"sido revertidas. Caso detectado, o aplicativo deverá limpar e encerrar o "
+"sistema. E, se houver uma tentativa de um futuro trabalho, a consistência do "
+"aplicativo poderá ser violada."
+
+#. Tag: para
+#: Chapter.xml:619
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: foi realizada uma tentativa "
+"para usar o serviço de transação de uma maneira inconsistente com a licença "
+"atual. O serviço de transação não permitirá nenhum progresso futuro para "
+"novas ou existentes transações."
+
+#. Tag: para
+#: Chapter.xml:622
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: um erro foi detectado "
+"enquanto o serviço de transação tentava usar o armazenamento do objeto. Não "
+"foi possível realizar um progresso."
+
+#. Tag: para
+#: Chapter.xml:625
+#, 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 ""
+"O armazenamento do objeto avisa antecipadamente que os problemas de acesso "
+"nos estados poderão ocorrer durante a execução normal da recuperação de "
+"travamento. Este é o resultado de tentativas atuais múltiplas para recuperar "
+"o desempenho na mesma transação. Isto pode ser facilmente ignorado."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Feedback.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Feedback.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Feedback.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Feedback.po to Brazilian Portuguese
+# translation of Preface.po to Brazilian Portuguese
# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Leticia de Lima <ldelima at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Feedback\n"
+"Project-Id-Version: Preface\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-18 08:29+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-19 16:13+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -35,6 +35,13 @@
"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 ""
-"Caso você encontre um erro neste guia ou se você pensar numa maneira diferente de fazer este manual ainda melhor, queremos muito de ouvir sua opinião. Por favor, submeta o relatório em <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> em referência ao Produto: Plataforma de Aplicativo JBoss Enterprise, Versão: <replaceable><version></replaceable>, Component: <emphasis>Doc</"
-"emphasis>. Caso tenha alguma sugestão para aperfeiçoamento desta documentação, por favor seja o mais específico possível. E, se você encontrar um erro, inclua o número de seção e algumas partes do texto ao redor, para que possamos localizá-lo com mais facilidade."
-
+"Caso você encontre um erro neste guia ou se você pensar numa maneira "
+"diferente de fazer este manual ainda melhor, queremos muito de ouvir sua "
+"opinião. Por favor, submeta o relatório em <ulink url=\"http://jira.jboss."
+"com/jira/browse/JBPAPP\">JIRA</ulink> em referência ao Produto: Plataforma "
+"de Aplicativo JBoss Enterprise, Versão: <replaceable><version></"
+"replaceable>, Component: <emphasis>Doc</emphasis>. Caso tenha alguma "
+"sugestão para aperfeiçoamento desta documentação, por favor seja o mais "
+"específico possível. E, se você encontrar um erro, inclua o número de seção "
+"e algumas partes do texto ao redor, para que possamos localizá-lo com mais "
+"facilidade."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Preface.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Preface.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
"PO-Revision-Date: 2008-06-19 16:13+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
@@ -34,7 +34,9 @@
msgid ""
"The Administration Guide contains information on how to administer JBoss "
"Transactions API 4.2.3."
-msgstr "O Guia de Administração contém informações de como administrar as Transações JBoss API 4.2.3"
+msgstr ""
+"O Guia de Administração contém informações de como administrar as Transações "
+"JBoss API 4.2.3"
#. Tag: title
#: Preface.xml:17
@@ -48,7 +50,9 @@
msgid ""
"This guide is most relevant to engineers who are responsible for "
"administration of JBoss Transactions API 4.2.3 installations."
-msgstr "Este guia é muito mais relevante para engenheiros, dos quais são responsáveis pela administração das instalações de Transações JBoss 4.2.3."
+msgstr ""
+"Este guia é muito mais relevante para engenheiros, dos quais são "
+"responsáveis pela administração das instalações de Transações JBoss 4.2.3."
#. Tag: title
#: Preface.xml:21
@@ -64,7 +68,11 @@
"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 "Para que se possa administrar as Transações JBoss, é necessário primeiro entender que elas baseiam-se no ArjunaCore, em muitas das funcionalidades da transação. Assim como, é importante ler o Guia Administrativo ArjunaCore antes de tentar administrar as Transações JBoss."
+msgstr ""
+"Para que se possa administrar as Transações JBoss, é necessário primeiro "
+"entender que elas baseiam-se no ArjunaCore, em muitas das funcionalidades da "
+"transação. Assim como, é importante ler o Guia Administrativo ArjunaCore "
+"antes de tentar administrar as Transações JBoss."
#. Tag: title
#: Preface.xml:25
@@ -85,7 +93,10 @@
"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 "Capítulo 1 - Administração das Transações JBoss: descreve como administrar as Transações JBoss, basicamente selecionando a variante de implementação JTA, local limpo ou remoto (permitindo as transações distribuídas)."
+msgstr ""
+"Capítulo 1 - Administração das Transações JBoss: descreve como administrar "
+"as Transações JBoss, basicamente selecionando a variante de implementação "
+"JTA, local limpo ou remoto (permitindo as transações distribuídas)."
#. Tag: title
#: Preface.xml:34
@@ -99,7 +110,9 @@
msgid ""
"In addition to this guide, the following guides are available in the JBoss "
"Transactions API 4.2.3 documentation set:"
-msgstr "Os seguintes guias estão disponíveis no conjunto de documentação das Transações JBoss API 4.2.3:"
+msgstr ""
+"Os seguintes guias estão disponíveis no conjunto de documentação das "
+"Transações JBoss API 4.2.3:"
#. Tag: para
#: Preface.xml:38
@@ -107,7 +120,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
"information about JBoss Transactions API 4.2.3."
-msgstr "Notas de Liberação de Transações JBoss API 4.2.3: Fornece informações recentes sobre Transações JBoss API 4.2.3."
+msgstr ""
+"Notas de Liberação de Transações JBoss API 4.2.3: Fornece informações "
+"recentes sobre Transações JBoss API 4.2.3."
#. Tag: para
#: Preface.xml:41
@@ -115,7 +130,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
"instructions for installing JBoss Transactions API 4.2.3."
-msgstr "Guia de Instalação de Transações JBoss API 4.2.3: Este guia fornece instruções para instalação de Transações JBoss API 4.2.3."
+msgstr ""
+"Guia de Instalação de Transações JBoss API 4.2.3: Este guia fornece "
+"instruções para instalação de Transações JBoss API 4.2.3."
#. Tag: para
#: Preface.xml:44
@@ -123,5 +140,6 @@
msgid ""
"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
"writing applications."
-msgstr "Guia do Programador das Transações JBoss 4.2.3: Fornece instruções para aplicativos escritos."
-
+msgstr ""
+"Guia do Programador das Transações JBoss 4.2.3: Fornece instruções para "
+"aplicativos escritos."
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Revision_History.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/pt-BR/Revision_History.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Revision_History.po to Brazilian Portuguese
+# translation of Preface.po to Brazilian Portuguese
# Language pt-BR translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Leticia de Lima <ldelima at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Revision_History\n"
+"Project-Id-Version: Preface\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-17 14:47+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-19 16:13+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -16,9 +16,14 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "Histórico de Revisão"
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
msgstr "<firstname></firstname> <surname></surname> <email></email>"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Author_Group.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Author_Group.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Author_Group.po to
+# translation of Preface.po to
# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: Preface\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-16 10:36+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-16 11:05+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -16,21 +16,8 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
-#. Tag: corpauthor
-#: Author_Group.xml:6
-#, no-c-format
-msgid "FF0000 Headgear Documentation Group"
-msgstr "FF0000 Headgear Documentation Group"
-
#. 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 ""
-"<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>"
-
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Book_Info.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Book_Info.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Book_Info.po to
+# translation of Preface.po to
# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: Preface\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-16 10:38+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-16 11:05+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -18,18 +18,18 @@
#. Tag: title
#: Book_Info.xml:6
-#, no-c-format
-msgid "JBoss Transactions API 4.2.3 Administration Guide"
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Administrators Guide"
msgstr "JBoss Transactions API 4.2.3 管理员指南"
#. Tag: subtitle
#: Book_Info.xml:10
-#, no-c-format
-msgid "JBoss Enterprise Application Platform"
+#, fuzzy, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 5.0"
msgstr "JBoss 企业级应用程序平台"
#. Tag: para
-#: Book_Info.xml:13
+#: Book_Info.xml:15
#, no-c-format
msgid ""
"This book is the JBoss Enterprise Application Platform edition of the JBoss "
@@ -37,8 +37,7 @@
msgstr "本书是面向 JBoss 企业级应用程序平台的《JBoss Transactions 管理员指南》"
#. Tag: holder
-#: Book_Info.xml:22
+#: Book_Info.xml:24
#, no-c-format
msgid "&HOLDER;"
msgstr "&HOLDER;"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Chapter.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Chapter.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Chapter.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,21 +1,20 @@
-# translation of Chapter.po to
+# translation of Preface.po to
# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Chapter\n"
+"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-06-19 00:36+0000\n"
-"PO-Revision-Date: 2008-06-24 14:07+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-16 11:05+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
-"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
#: Chapter.xml:6
@@ -67,10 +66,13 @@
"When A is next activated and attempts to access B, a run-time error will "
"occur."
msgstr ""
-"除非调用 StateManager.destroy 方法或某个应用程序显性地进行删除，在 Object Store 里创建的持久性对象会永远存在。这意味着 "
-"Object Store 会逐渐地积累垃圾（特别是在程序开发和测试阶段）。目前我们还没有自动的垃圾回收机制。而且，我们也还没解决 dangling "
-"引用的问题：某个持久性对象 A，可能在其磁盘上的 passive representation 里存储了另外一个持久性对象 B 的 "
-"UID。应用程序有可能删除了 B，即使 A 仍然具有对其的引用。之后 A 被激活并试图访问 B 时，就会出现一个运行错误。"
+"除非调用 StateManager.destroy 方法或某个应用程序显性地进行删除，在 Object "
+"Store 里创建的持久性对象会永远存在。这意味着 Object Store 会逐渐地积累垃圾"
+"（特别是在程序开发和测试阶段）。目前我们还没有自动的垃圾回收机制。而且，我们"
+"也还没解决 dangling 引用的问题：某个持久性对象 A，可能在其磁盘上的 passive "
+"representation 里存储了另外一个持久性对象 B 的 UID。应用程序有可能删除了 B，"
+"即使 A 仍然具有对其的引用。之后 A 被激活并试图访问 B 时，就会出现一个运行错"
+"误。"
#. Tag: para
#: Chapter.xml:16
@@ -85,23 +87,87 @@
"neither detect nor correct references to old object state by new operation "
"versions or vice versa."
msgstr ""
-"目前没有对类结构改变时对象或数据库重配置的版本控制的支持。这是我们还没解决的一个复杂的研究领域。目前，如果你修改了持久性对象的类的定义，你需要完全负责确保 "
-"Object Store 里的现存实例转换成新的结构。JBoss Transactions 既不能检测也不能改正通过新的操作版本对旧的对象状态的引用，反之亦然。"
+"目前没有对类结构改变时对象或数据库重配置的版本控制的支持。这是我们还没解决的"
+"一个复杂的研究领域。目前，如果你修改了持久性对象的类的定义，你需要完全负责确"
+"保 Object Store 里的现存实例转换成新的结构。JBoss Transactions 既不能检测也不"
+"能改正通过新的操作版本对旧的对象状态的引用，反之亦然。"
#. Tag: para
-#: Chapter.xml:19
+#: Chapter.xml:19 Chapter.xml:62
#, no-c-format
-msgid "Object store management is critically important to the transaction service."
+msgid ""
+"Object store management is critically important to the transaction service."
msgstr "对于事务服务来说，Object store 的管理至关重要。"
#. Tag: title
#: Chapter.xml:24
#, no-c-format
+msgid "Starting and Stopping the transaction manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:25
+#, no-c-format
+msgid ""
+"By default the transaction manager starts up in an active state such that "
+"new transactions can be created immediately. If you wish to have more "
+"control over this it is possible to set the <property>com.arjuna.ats.arjuna."
+"coordinator.startDisabled</property> configuration option to <literal>YES</"
+"literal>, in which case no transactions can be created until the transaction "
+"manager is enabled (via a call to <methodname>TxControl.enable</methodname>)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:28
+#, no-c-format
+msgid ""
+"It is possible to stop the creation of new transactions at any time by "
+"calling <methodname>TxControl.disable</methodname>. Transactions that are "
+"currently executing will not be affected. By default recovery will be "
+"allowed to continue and the transaction system will still be available to "
+"manage recovery requests from other instances in a distributed environment. "
+"(See the Failure Recovery Guide for further details). However, if you wish "
+"to disable recovery as well as remove any resources it maintains, then you "
+"can pass true to <methodname>TxControl.disable</methodname>; the default is "
+"to use <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:31
+#, no-c-format
+msgid ""
+"If you wish to shut the system down completely then it may also be necessary "
+"to terminate the background transaction reaper (see the Programmers Guide "
+"for information about what the reaper does.) In order to do this you may "
+"want to first prevent the creation of new transactions (if you are not "
+"creating transactions with timeouts then this step is not necessary) using "
+"<methodname>TxControl.disable</methodname>. Then you should call "
+"<methodname>TransactionReaper.terminate</methodname>. This method takes a "
+"boolean parameter: if true then the method will wait for the normal timeout "
+"periods associated with any transactions to expire before terminating the "
+"transactions; if false then transactions will be forced to terminate "
+"(rollback or have their outcome set such that they can only ever rollback) "
+"immediately."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:35
+#, no-c-format
+msgid ""
+"If you intent to restart the recovery manager later after having terminated "
+"it then you <emphasis>must</emphasis> use the <methodname>terminate</"
+"methodname> method with <property>asynchronous behavior</property> set to "
+"<literal>false</literal> when shutting down the recovery manager."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:40
+#, no-c-format
msgid "ObjectStore management"
msgstr "管理 ObjectStore "
#. Tag: para
-#: Chapter.xml:25
+#: Chapter.xml:41
#, no-c-format
msgid ""
"Within the transaction service installation, the object store is updated "
@@ -117,18 +183,750 @@
"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 Object 被使用，object store "
-"就会被更新。在无故障的环境里，唯一应该驻留在 object store 里的对象状态时那些代表用 Java API "
-"然而，如果发生了故障，事务日志可能保留在 object store 里，直到故障恢复机制已经恢复了它们所代表的事务。因此，删除 object store 的内容需要很小心和谨慎，这很重要，因为这会导致无法解决可疑的事务。此外，如果多个用户共享相同的 object store，他们也需明白这一点。他们不能假定 object store 里的内容是独占资源而简单地进行删除。"
+"在事务访问安装里，只要有事务被创建或是用于 Java 的 Transactional Object 被使"
+"用，object store 就会被更新。在无故障的环境里，唯一应该驻留在 object store 里"
+"的对象状态时那些代表用 Java API 然而，如果发生了故障，事务日志可能保留在 "
+"object store 里，直到故障恢复机制已经恢复了它们所代表的事务。因此，删除 "
+"object store 的内容需要很小心和谨慎，这很重要，因为这会导致无法解决可疑的事"
+"务。此外，如果多个用户共享相同的 object store，他们也需明白这一点。他们不能假"
+"定 object store 里的内容是独占资源而简单地进行删除。"
+#. Tag: para
+#: Chapter.xml:42
+#, fuzzy, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the JBossTS software. There are "
+"a few points however, that should be made:"
+msgstr ""
+"为了确保系统的正常运行，你需要对 JBoss Transactions 进行一点持续的管理。下面"
+"是一些需要注意的地方："
+
+#. Tag: para
+#: Chapter.xml:47
+#, fuzzy, no-c-format
+msgid ""
+"The present implementation of the JBossTS system provides no security or "
+"protection for data. It is recommended that the objects stored in the "
+"JBossTS are owned by user arjuna. The Object Store and Object Manager "
+"facilities make no attempt to enforce even the limited form of protection "
+"that Unix and 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 Store 和 Object Manager 机制甚至没有强制 Unix/Windows 所提供的有限"
+"的保护。对这些对象的读和写并不需要检查用户或组的 ID。"
+
+#. Tag: para
+#: Chapter.xml:52
+#, fuzzy, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> 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 ""
+"除非调用 StateManager.destroy 方法或某个应用程序显性地进行删除，在 Object "
+"Store 里创建的持久性对象会永远存在。这意味着 Object Store 会逐渐地积累垃圾"
+"（特别是在程序开发和测试阶段）。目前我们还没有自动的垃圾回收机制。而且，我们"
+"也还没解决 dangling 引用的问题：某个持久性对象 A，可能在其磁盘上的 passive "
+"representation 里存储了另外一个持久性对象 B 的 UID。应用程序有可能删除了 B，"
+"即使 A 仍然具有对其的引用。之后 A 被激活并试图访问 B 时，就会出现一个运行错"
+"误。"
+
+#. Tag: para
+#: Chapter.xml:57
+#, fuzzy, 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 JBossTS software can neither detect "
+"nor correct references to old object state by new operation versions or vice "
+"versa."
+msgstr ""
+"目前没有对类结构改变时对象或数据库重配置的版本控制的支持。这是我们还没解决的"
+"一个复杂的研究领域。目前，如果你修改了持久性对象的类的定义，你需要完全负责确"
+"保 Object Store 里的现存实例转换成新的结构。JBoss Transactions 既不能检测也不"
+"能改正通过新的操作版本对旧的对象状态的引用，反之亦然。"
+
#. Tag: title
-#: Chapter.xml:28
+#: Chapter.xml:70
#, no-c-format
+msgid "OTS and J2EE Transaction service management"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:72
+#, no-c-format
+msgid "Starting the run-time system"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:73
+#, no-c-format
+msgid ""
+"The JBossTS run-time support consists of run-time packages and the OTS "
+"transaction manager server. By default JBossTS does not use a separate "
+"transaction manager server: transaction managers are co-located with each "
+"application process to improve performance and improve application fault-"
+"tolerance (the application is no longer dependant upon another service in "
+"order to function correctly)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:76
+#, no-c-format
+msgid ""
+"When running applications which require a separate transaction manager, you "
+"must set the <varname>com.arjuna.ats.jts.transactionManager</varname> "
+"environment variable to have the value <literal>yes</literal>. The system "
+"will then locate the transaction manager server in a manner specific to the "
+"ORB being used. The server can be located in a number of ways: by being "
+"registered with a name server, added to the ORB’s initial references, via a "
+"JBossTS specific references file, or by the ORB’s specific location "
+"mechanism (if applicable)."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:79
+#, no-c-format
+msgid ""
+"It is possible to override the default registration mechanism by using the "
+"<varname>com.arjuna.orbportability.resolveService</varname> environment "
+"variable. This can have one of the following values:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:84
+#, no-c-format
+msgid ""
+"<literal>CONFIGURATION_FILE</literal>: the default, this causes the system "
+"to use the <filename>CosServices.cfg</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:89
+#, no-c-format
+msgid ""
+"<literal>NAME_SERVICE</literal>: JBossTS will attempt to use a name service "
+"to register the transaction factory. If this is not supported, an exception "
+"will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:94
+#, no-c-format
+msgid ""
+"<literal>BIND_CONNECT</literal>: JBossTS will use the ORB-specific bind "
+"mechanism. If this is not supported, an exception will be thrown."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:99
+#, no-c-format
+msgid ""
+"<literal>RESOLVE_INITIAL_REFERENCES</literal>: JBossTS will attempt to "
+"register the transaction service with the ORBs initial service references."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:105
+#, no-c-format
+msgid ""
+"This may not be supported on all ORBs. An exception will be thrown in that "
+"case and another option will have to be used."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:110
+#, no-c-format
+msgid "<title>OTS configuration file</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:111
+#, no-c-format
+msgid ""
+"Similar to the resolve_initial_references, JBossTS supports an initial "
+"reference file where references for specific services can be stored and used "
+"at runtime. The file, CosServices.cfg, consists of two columns: the service "
+"name (in the case of the OTS server TransactionService) and the IOR, "
+"separated by a single space. CosServices.cfg normally resides in the etc "
+"directory of the JBossTS installation; the actual location is determined at "
+"runtime by searching the CLASSPATH for an old copy of the file resident "
+"within an etc directory, or, if one is not found, the location of the "
+"TransactionService properties file directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:115
+#, no-c-format
+msgid ""
+"The OTS server will automatically register itself in this file (creating it "
+"if necessary) if this option is being used. Stale information is also "
+"automatically removed. Machines which wish to share the same transaction "
+"server should have access to (or a copy of) this file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:118
+#, no-c-format
+msgid ""
+"The name and location of the file can be overridden using the <property>com."
+"arjuna.orbportability.initialReferencesFile</property> and <property>com."
+"arjuna.orbportability.initialReferencesRoot</property> property variables, "
+"respectively. It is recommended that the <property>com.arjuna.orbportability."
+"initialReferencesRoot</property> variable is set. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Chapter.xml:121
+#, no-c-format
+msgid ""
+"com.arjuna.orbportability.initialReferencesFile=myFile\n"
+"com.arjuna.orbportability.initialReferencesRoot=c:\\\\temp"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:123
+#, no-c-format
+msgid "<title>Name Service</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:124
+#, no-c-format
+msgid ""
+"If the ORB you are using supports a name service, and JBossTS has been "
+"configured to use it, then the transaction manager will automatically be "
+"registered with it. There is no further work required. This option is not "
+"used for JacORB"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:129
+#, no-c-format
+msgid "<title>resolve_initial_references</title>"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:130
+#, no-c-format
+msgid "Currently this option is only supported for JacORB."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:135
+#, no-c-format
+msgid "Resolution service table"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:136
+#, no-c-format
+msgid ""
+"The following table summarizes the different ways in which the OTS "
+"transaction manager may be located on specific ORBs:"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:141
+#, no-c-format
+msgid "Locating the OTS transaction manager server"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:145
+#, no-c-format
+msgid "Resolution Mechanism"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:146
+#, no-c-format
+msgid "<entry>ORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:151
+#, no-c-format
+msgid "<entry>OTS configuration file</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:152
+#, no-c-format
+msgid "All available ORBs"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:155
+#, no-c-format
+msgid "<entry>Name Service</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:156 Chapter.xml:160
+#, no-c-format
+msgid "<entry>JacORB</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:159
+#, no-c-format
+msgid "<entry>resolve_initial_references</entry>"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:167
+#, no-c-format
+msgid "XA specific management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:168
+#, no-c-format
+msgid ""
+"Each XA Xid that JBossTS creates must have a unique node identifier encoded "
+"within it and JBossTS will only recover transactions and states that match a "
+"specified node identifier. The node identifier to use should be provided to "
+"JBossTS via the <property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property> "
+"property. You must make sure this value is unique across your JBossTS "
+"instances. If you do not provide a value, then JBossTS will fabricate one "
+"and report the value via the logging infrastructure."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:171
+#, no-c-format
+msgid ""
+"When running XA recovery it is therefore necessary to tell JBossTS which "
+"types of Xid it can recover. Each Xid that JBossTS creates has a unique node "
+"identifier encoded within it and JBossTS will only recover transactions and "
+"states that match a specified node identifier. The node identifier to use "
+"should be provided to JBossTS via a property that starts with the name "
+"<property>com.arjuna.ats.jta.xaRecoveryNode</property>; multiple values may "
+"be provided. A value of <code>*</code> will force JBossTS to recover (and "
+"possibly rollback) all transactions irrespective of their node identifier "
+"and should be used with caution."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:177
+#, no-c-format
+msgid "Web Service Transaction service management"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:178
+#, no-c-format
+msgid ""
+"The basic building blocks of a transactional Web Services application are "
+"the application itself, the Web services that the application consumes, the "
+"Transaction Manager, and the transaction participants which support those "
+"Web services. Though it is unlikely in a typical deployment that a single "
+"developer will be expected to support all of these roles, the concepts are "
+"presented here so that a global model can be visualized. It will often be "
+"the case that developers will produce services, or applications that consume "
+"services, whilst system administrators will run the transaction-management "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:182
+#, fuzzy, no-c-format
+msgid "The Transaction Manager"
+msgstr "Recovery Manager"
+
+#. Tag: para
+#: Chapter.xml:183
+#, no-c-format
+msgid ""
+"The transaction manager is a Web service which coordinates JBossTS "
+"transactions. It is the only software component in JBossTS that is meant to "
+"be run directly as a network service, rather than to support end-user code. "
+"The transaction manager runs as a JAXM request/response Web service."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:187
+#, no-c-format
+msgid ""
+"When starting up an application server instance that has JBossTS deployed "
+"within it, you may see various <emphasis>error</emphasis> messages in the "
+"console or log. For example <code>16:53:38,850 ERROR [STDERR] Message "
+"Listener Service: started, message listener jndi name activationcoordinator</"
+"code>. These are for information purposes only and are not actual errors."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:192
+#, fuzzy, no-c-format
+msgid "Configuring the Transaction Manager"
+msgstr "配置 Recovery Manager"
+
+#. Tag: para
+#: Chapter.xml:193
+#, no-c-format
+msgid ""
+"The Transaction Manager and related infrastructure are configured by means "
+"of properties files: <filename>wscf.xml</filename>, <filename>wst.xml</"
+"filename> and <filename>wstx.xml</filename>. These files can be found in the "
+"conf directory and are used for configuring the demo application and the "
+"standalone module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:197
+#, no-c-format
+msgid ""
+"For the most part the default values in these files need not be altered. "
+"However, the <property>com.arjuna.ats.arjuna.objectstore.objectStoreDir</"
+"property> property determines the location of the persistent store used to "
+"record transaction state. The default value of <filename>C:/temp/"
+"ObjectStore</filename> should be changed to a value appropriate to your "
+"system. For production environments this directory should reside on fault "
+"tolerant media such as a RAID array."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:200
+#, no-c-format
+msgid ""
+"When a standalone coordinator is being used by an application it is "
+"necessary to enable and modify two further properties in <filename>wstx.xml</"
+"filename>, <property>com.arjuna.mw.wst.coordinatorURL</property> and "
+"<property>com.arjuna.mw.wst.terminatorURL</property>. These contain the URLs "
+"necessary for the client application to contact the standalone coordinator "
+"and should be configured with the correct hostname and port of the "
+"standalone coordinator."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:203
+#, no-c-format
+msgid ""
+"JBossTS is highly modular so in order to allow for flexible deployment of "
+"individual components, the same property values are sometimes required to "
+"appear in more than one configuration file. For the majority of "
+"configurations, you should maintain consistent values for properties that "
+"are defined in more than one file."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:207
+#, no-c-format
+msgid "Deploying the Transaction Manager"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:208
+#, no-c-format
+msgid ""
+"The JBossTS Web Service Transaction Manager component consists of a number "
+"of JAR files containing the application’s class files, plus Web service "
+"(WAR) files which expose the necessary services. Programmers will typically "
+"include all these components in their application EAR file during "
+"application development, simplifying deployment of the transaction "
+"infrastructure. For production usage the Transaction Manager may be "
+"installed as an application in its own right, allowing for centralized "
+"configuration and management at the server level, independent of specific "
+"applications. The demonstration application shipped with JBossTS provides a "
+"sample deployment descriptor illustrating how the Transaction Manager "
+"components can be included in an application."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:212
+#, no-c-format
+msgid ""
+"JBossTS 4.0 uses fixed endpoints for its underlying protocol communication. "
+"Therefore, problems may arise if multiple applications using JBossTS are "
+"deployed to the same server concurrently. If you wish to deploy several "
+"transactional applications in the same server, the Transaction Manger must "
+"be deployed as a separate application and not embedded within the deployment "
+"of individual applications."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:215
+#, no-c-format
+msgid ""
+"The coordinator directory in the JBossTS installation has been provided to "
+"assist in the configuration and deployment of a stand-alone transaction "
+"manager. In order to use this, you must:"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:220
+#, fuzzy, no-c-format
+msgid "Have JBoss Enterprise Application Platform 5 installed"
+msgstr "JBoss 企业级应用程序平台"
+
+#. Tag: para
+#: Chapter.xml:225
+#, no-c-format
+msgid "Install ant 1.4 or later."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:231
+#, no-c-format
+msgid ""
+"It is important that a separate application server installation be used from "
+"the one that clients and services are deployed into since otherwise "
+"conflicts may occur between the various JBossTS components."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:235
+#, no-c-format
+msgid ""
+"You must then edit the build.xml included with coordinator to point to the "
+"application server installation where the transaction coordinator will be "
+"deployed and the location of the JBossTS installation. The files "
+"<filename>ws-c_jaxm_web-app.xml</filename> and <filename>ws-t_jaxm_web-app."
+"xml</filename> in the <filename>dd</filename> directory of coordinator are "
+"the deployment descriptors for the WS-C and WS-T WAR files. These files "
+"contain templated URLs. During the build phase, ant will substitute the "
+"hostname and port values you specify in the <filename>build.xml</filename> "
+"into these files."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:238
+#, no-c-format
+msgid ""
+"Run <code>ant</code>, with <code>target deploy-weblogic</code>, <code>deploy-"
+"jboss</code> or <code>deploy-webmethods</code>, to create and deploy a new "
+"coordinator into the correct application server installation."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:241
+#, no-c-format
+msgid ""
+"Now all you need to do is point your client at the required coordinator. To "
+"do this, generate the demo application specifying the port and hostname of "
+"the coordinator."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:245
+#, no-c-format
+msgid "Deployment descriptors"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:246
+#, no-c-format
+msgid ""
+"In general, it should not be necessary to change the contents of the various "
+"deployment descriptors used by JBossTS. However, if you do need to modify "
+"them they are all included in the coordinator module."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:250
+#, no-c-format
+msgid ""
+"Not all JBossTS components have ready access to the information in the "
+"deployment descriptors. Therefore, if you modify the JNDI names used by any "
+"of the WS-C or WS-T deployment descriptors you may need to inform other "
+"JBossTS components at runtime. This can be accomplished by setting an "
+"appropriate property in the <filename>wstx.xml</filename> configuration file."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:253
+#, no-c-format
+msgid ""
+"The following table shows the default JNDI name used by the deployment "
+"descriptors and the corresponding property to set if the default value is "
+"changed."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:257
+#, no-c-format
+msgid "Deployment descriptor values and properties"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:261
+#, no-c-format
+msgid "JNDI Name"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:262
+#, no-c-format
+msgid "Property"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:267
+#, no-c-format
+msgid "Activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:268
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:271
+#, no-c-format
+msgid "Activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:272
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.activationcoordinator"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:275
+#, no-c-format
+msgid "Completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:276
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.completionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:279
+#, no-c-format
+msgid "Registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:280
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.registrationrequester"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:283
+#, no-c-format
+msgid "durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:284
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:287
+#, no-c-format
+msgid "durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:288
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.durable2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:291
+#, no-c-format
+msgid "volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:292
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:295
+#, no-c-format
+msgid "volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:296
+#, no-c-format
+msgid "com.arjuna.mw.wst.at.volatile2pcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:299
+#, no-c-format
+msgid "businessagreementwithparticipantcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:300
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:303
+#, no-c-format
+msgid "businessagreementwithparticipantcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:304
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwpcparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:307
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletiondispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:308
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccdispatcher"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:311
+#, no-c-format
+msgid "businessagreementwithcoordinatorcompletionparticipant"
+msgstr ""
+
+#. Tag: entry
+#: Chapter.xml:312
+#, no-c-format
+msgid "com.arjuna.mw.wst.ba.businessagreementwccparticipant"
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:319
+#, no-c-format
msgid "JBoss Transactions runtime information"
msgstr "JBoss Transactions 的运行信息"
#. Tag: para
-#: Chapter.xml:29
+#: Chapter.xml:320
#, no-c-format
msgid ""
"Each module that comprises JBoss Transactions possesses a class called Info. "
@@ -136,11 +934,11 @@
"document representing the configuration information for that module. So, for "
"example:"
msgstr ""
-"组成 JBoss Transactions 的每个模块都拥有一个名为 info 的类。这些类都提供单一的 toString 方法来返回代表该模块的配置信息的 "
-"XML 文档。例如："
+"组成 JBoss Transactions 的每个模块都拥有一个名为 info 的类。这些类都提供单一"
+"的 toString 方法来返回代表该模块的配置信息的 XML 文档。例如："
#. Tag: programlisting
-#: Chapter.xml:31
+#: Chapter.xml:322
#, no-c-format
msgid ""
"<module-info name=\"arjuna\">\n"
@@ -174,13 +972,13 @@
"</module-info>"
#. Tag: title
-#: Chapter.xml:34
+#: Chapter.xml:325
#, no-c-format
msgid "Failure recovery administration"
msgstr "失效切换管理"
#. Tag: para
-#: Chapter.xml:35
+#: Chapter.xml:326
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions will ensure that "
@@ -195,19 +993,22 @@
"failure and is accessible afterward: this information is held in the "
"ActionStore, which is part of the ObjectStore."
msgstr ""
-"JBoss Transactions "
-"的失效切换子系统将确保在即使应用程序进程或主机崩溃或断开了网络连接的情况下，事务的结果都可以持续地应用到事务所影响的资源里。在主机（系统）崩溃或网络故障时，失效"
-"切换将直到系统或网络恢复时才进行，但原来的应用程序不需要重启 － 切换的责任委托给了 Recovery Manager "
-"进程（请参考下面内容）。失效切换要求和事务和资源相关的信息：这些信息保存在作为 ObjectStore 一部分的 ActionStore 里。"
+"JBoss Transactions 的失效切换子系统将确保在即使应用程序进程或主机崩溃或断开了"
+"网络连接的情况下，事务的结果都可以持续地应用到事务所影响的资源里。在主机（系"
+"统）崩溃或网络故障时，失效切换将直到系统或网络恢复时才进行，但原来的应用程序"
+"不需要重启 － 切换的责任委托给了 Recovery Manager 进程（请参考下面内容）。失"
+"效切换要求和事务和资源相关的信息：这些信息保存在作为 ObjectStore 一部分的 "
+"ActionStore 里。"
#. Tag: para
-#: Chapter.xml:38
+#: Chapter.xml:329
#, no-c-format
-msgid "If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
msgstr "如果 ObjectStore 被销毁或修改，失效切换有可能无法进行。"
#. Tag: para
-#: Chapter.xml:41
+#: Chapter.xml:332
#, no-c-format
msgid ""
"Until the recovery procedures are complete, resources affected by a "
@@ -217,18 +1018,19 @@
"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（尝试获取锁）将失败。"
+"直到失效切换过程完成之前，故障发生时正进行的事务所影响的资源都可能无法访问。"
+"对于数据库资源而言，可能出现表或行被“in-doubt transactions”锁定。对于用于 "
+"Java 资源的 TransactionalObjects，试图激活 Transactional Object（尝试获取锁）"
+"将失败。"
#. Tag: title
-#: Chapter.xml:43
+#: Chapter.xml:334
#, no-c-format
msgid "The Recovery Manager"
msgstr "Recovery Manager"
#. Tag: para
-#: Chapter.xml:44
+#: Chapter.xml:335
#, no-c-format
msgid ""
"The failure recovery subsystem of JBoss Transactions requires that the stand-"
@@ -239,39 +1041,42 @@
"RecoveryManager</classname>. To start the Recovery Manager issue the "
"following command:"
msgstr ""
-"JBoss Transactions 的失效切换（failure recovery）子系统要求为每个 ObjectStore（通常是网络上的每个运行 "
-"JBoss Transactions 应用程序的节点）运行独立的 Recovery Manager 进程。RecoveryManager 文件位于 <"
-"classname>com.arjuna.ats.arjuna.recovery.RecoveryManager</classname> 包里的 "
-"arjunacore jar 中。要启动 Recovery Manager，你可以使用下面的命令："
+"JBoss Transactions 的失效切换（failure recovery）子系统要求为每个 ObjectStore"
+"（通常是网络上的每个运行 JBoss Transactions 应用程序的节点）运行独立的 "
+"Recovery Manager 进程。RecoveryManager 文件位于 <classname>com.arjuna.ats."
+"arjuna.recovery.RecoveryManager</classname> 包里的 arjunacore jar 中。要启动 "
+"Recovery Manager，你可以使用下面的命令："
#. Tag: command
-#: Chapter.xml:45
+#: Chapter.xml:336
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
#. Tag: para
-#: Chapter.xml:46
+#: Chapter.xml:337
#, 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 "如果使用了 <literal>-test</literal> 标签，它将在初始化时显示“Ready”信息，也就是："
+msgstr ""
+"如果使用了 <literal>-test</literal> 标签，它将在初始化时显示“Ready”信息，也就"
+"是："
#. Tag: command
-#: Chapter.xml:47
+#: Chapter.xml:338
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
#. Tag: title
-#: Chapter.xml:50
+#: Chapter.xml:341
#, no-c-format
msgid "Configuring the Recovery Manager"
msgstr "配置 Recovery Manager"
#. Tag: para
-#: Chapter.xml:51
+#: Chapter.xml:342
#, no-c-format
msgid ""
"The RecoveryManager reads the properties defined in the <filename>arjuna."
@@ -282,13 +1087,13 @@
"in the main TransactionService properties file. Most of the entries are "
"specific to the Recovery Manager."
msgstr ""
-"RecoveryManager 读取 <filename>arjuna.properties</filename> "
-"文件里定义的属性，然后读取相同目录下的属性文件 <filename>RecoveryManager.properties</filename>"
-"。RecoveryManager 属性文件里的条目将覆盖 TransactionService 属性文件里相同的条目。大多数条目都是 Recovery "
-"Manager 所专有的。"
+"RecoveryManager 读取 <filename>arjuna.properties</filename> 文件里定义的属"
+"性，然后读取相同目录下的属性文件 <filename>RecoveryManager.properties</"
+"filename>。RecoveryManager 属性文件里的条目将覆盖 TransactionService 属性文件"
+"里相同的条目。大多数条目都是 Recovery Manager 所专有的。"
#. Tag: para
-#: Chapter.xml:52
+#: Chapter.xml:343
#, no-c-format
msgid ""
"A default version of <filename>RecoveryManager.properties</filename> is "
@@ -298,17 +1103,19 @@
"other values (in the order of their appearance in the default version of the "
"file)"
msgstr ""
-"本发行版本提供一个缺省的 <filename>RecoveryManager.properties</filename> 版本 － "
-"它无需修改就可以使用，除了一些调试跟踪的字段（请参考下面的 Output）。本节剩下的内容将讨论将属性设置为其他值所相关的问题（按照在缺省版本里出现的顺序）。"
+"本发行版本提供一个缺省的 <filename>RecoveryManager.properties</filename> 版"
+"本 － 它无需修改就可以使用，除了一些调试跟踪的字段（请参考下面的 Output）。本"
+"节剩下的内容将讨论将属性设置为其他值所相关的问题（按照在缺省版本里出现的顺"
+"序）。"
#. Tag: title
-#: Chapter.xml:54
+#: Chapter.xml:345
#, no-c-format
msgid "Output"
msgstr "Output"
#. Tag: para
-#: Chapter.xml:55
+#: Chapter.xml:346
#, no-c-format
msgid ""
"It is likely that installations will want to have some form of output from "
@@ -320,12 +1127,14 @@
"Commons Logging framework and configuration is assumed to occur through that "
"framework."
msgstr ""
-"很可能安装将希望从 RecoveryManager 里获得某种形式的输出来提供发生恢复的记录。RecoveryManager 使用 Arjuna Common Logging Framework (CLF) 提供的日志跟踪机制，它提供了一个隐藏了现有的 logging API 如 Jakarta "
-"log4j 或 JDK 1.4 logging API 之间的差异的高级别的接口。CLF 通过 Apache "
-"Commons Logging 框架间接处理日志，其配置假定存在于该框架内。"
+"很可能安装将希望从 RecoveryManager 里获得某种形式的输出来提供发生恢复的记录。"
+"RecoveryManager 使用 Arjuna Common Logging Framework (CLF) 提供的日志跟踪机"
+"制，它提供了一个隐藏了现有的 logging API 如 Jakarta log4j 或 JDK 1.4 logging "
+"API 之间的差异的高级别的接口。CLF 通过 Apache Commons Logging 框架间接处理日"
+"志，其配置假定存在于该框架内。"
#. Tag: para
-#: Chapter.xml:58
+#: Chapter.xml:349
#, no-c-format
msgid ""
"With the CLF applications make logging calls on logger objects. Loggers may "
@@ -335,42 +1144,52 @@
"DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to "
"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
"FATAL."
-msgstr "用 CLF 应用程序来调用 logger 对象的日志调用。Logger 可以使用日志级别来决定具体的日志信息。每个日志信息都有一个相关的日志级别来表示重要和紧急程度。日志级别可以是 DEBUG、INFO、WARN、 ERROR 和 FATAL。按整形值的顺序排列为：DEBUG < INFO < WARN < ERROR < FATAL。"
+msgstr ""
+"用 CLF 应用程序来调用 logger 对象的日志调用。Logger 可以使用日志级别来决定具"
+"体的日志信息。每个日志信息都有一个相关的日志级别来表示重要和紧急程度。日志级"
+"别可以是 DEBUG、INFO、WARN、 ERROR 和 FATAL。按整形值的顺序排列为：DEBUG "
+"< INFO < WARN < ERROR < FATAL。"
#. Tag: para
-#: Chapter.xml:61
+#: Chapter.xml:352
#, 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 "CLF 提供按照定义的颗粒度过滤日志消息的扩展。这就是说，当 DEBUG 级别的日志消息被提供给 logger时，你可以指定其他的条件来决定是否启用这个日志消息。"
+msgstr ""
+"CLF 提供按照定义的颗粒度过滤日志消息的扩展。这就是说，当 DEBUG 级别的日志消息"
+"被提供给 logger时，你可以指定其他的条件来决定是否启用这个日志消息。"
#. Tag: para
-#: Chapter.xml:67
+#: Chapter.xml:358
#, 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 "只有启用了 DEBUG 级别且日志请求由应用程序专有的调试颗粒度执行时，才能应用这些条件。"
+msgstr ""
+"只有启用了 DEBUG 级别且日志请求由应用程序专有的调试颗粒度执行时，才能应用这些"
+"条件。"
#. Tag: para
-#: Chapter.xml:71
+#: Chapter.xml:362
#, no-c-format
msgid "When enabled, Debugging is filtered conditionally on three variables:"
msgstr "被启用后，日志消息根据 3 个变量进行有条件地过滤："
#. Tag: para
-#: Chapter.xml:74
+#: Chapter.xml:365
#, 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 "调试级别（Debugging level）：DEBUG 级别的日志请求产生的地方，如构造函数或基本方法。"
+msgstr ""
+"调试级别（Debugging level）：DEBUG 级别的日志请求产生的地方，如构造函数或基本"
+"方法。"
#. Tag: para
-#: Chapter.xml:77
+#: Chapter.xml:368
#, no-c-format
msgid ""
"Visibility level: the visibility of the constructor, method, etc. that "
@@ -378,7 +1197,7 @@
msgstr "可见级别（Visibility level）：产生调试信息的构造函数、方法等的可见性。"
#. Tag: para
-#: Chapter.xml:80
+#: Chapter.xml:371
#, no-c-format
msgid ""
"Facility code: for instance the package or sub-module within which debugging "
@@ -386,7 +1205,7 @@
msgstr "Facility code：例如产生调试信息的包或子模块，如 ObjectStore。"
#. Tag: para
-#: Chapter.xml:83
+#: Chapter.xml:374
#, no-c-format
msgid ""
"According to these variables the CLF defines three interfaces. A particular "
@@ -398,196 +1217,208 @@
"enable debug messages. Finer debugging values used by the JBoss Transactions "
"are defined below:"
msgstr ""
-"根据这些变量，CLF 定义了 3 个接口。特定的产品可以按照需要实现自己的类。JBoss Transactions 使用 CLF 提供的缺省 Debugging level 和 Visibility level，但它定义自己的 Facility "
-"Code。JBoss Transactions 使用分配给 logger 对象的缺省的级别（DEBUG）。然而，它使用 finer debugging 特征来禁用或启用调试消息。JBoss Transactions 使用的 finer debugging 值有："
+"根据这些变量，CLF 定义了 3 个接口。特定的产品可以按照需要实现自己的类。JBoss "
+"Transactions 使用 CLF 提供的缺省 Debugging level 和 Visibility level，但它定"
+"义自己的 Facility Code。JBoss Transactions 使用分配给 logger 对象的缺省的级别"
+"（DEBUG）。然而，它使用 finer debugging 特征来禁用或启用调试消息。JBoss "
+"Transactions 使用的 finer debugging 值有："
#. Tag: para
-#: Chapter.xml:84
+#: Chapter.xml:375
#, 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 "Debugging level – JBoss Transactions 使用 <classname>com.arjuna.common.util.logging.DebugLevel</classname> 类里定义的缺省值"
+msgstr ""
+"Debugging level – JBoss Transactions 使用 <classname>com.arjuna.common.util."
+"logging.DebugLevel</classname> 类里定义的缺省值"
#. Tag: para
-#: Chapter.xml:87
+#: Chapter.xml:378
#, no-c-format
msgid ""
"NO_DEBUGGING: No diagnostics. A logger object assigned with this values "
"discard all debug requests"
-msgstr "NO_DEBUGGING: No diagnostics. 这个值分配的 Logger 对象丢弃所有的调试请求。"
+msgstr ""
+"NO_DEBUGGING: No diagnostics. 这个值分配的 Logger 对象丢弃所有的调试请求。"
#. Tag: para
-#: Chapter.xml:90
+#: Chapter.xml:381
#, 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 "FULL_DEBUGGING: Full diagnostics. 如果 facility code 和 the visibility level 符合 logger 所允许的值，这个值分配的 Logger 对象允许所有的调试请求。"
+msgstr ""
+"FULL_DEBUGGING: Full diagnostics. 如果 facility code 和 the visibility level "
+"符合 logger 所允许的值，这个值分配的 Logger 对象允许所有的调试请求。"
#. Tag: para
-#: Chapter.xml:93
+#: Chapter.xml:384
#, no-c-format
msgid "Additional Debugging Values are:"
msgstr "其他的调试值有："
#. Tag: para
-#: Chapter.xml:96
+#: Chapter.xml:387
#, no-c-format
msgid "CONSTRUCTORS: Diagnostics from constructors."
msgstr "CONSTRUCTORS: Diagnostics from constructors."
#. Tag: para
-#: Chapter.xml:99
+#: Chapter.xml:390
#, no-c-format
msgid "DESTRUCTORS: Diagnostics from finalizers."
msgstr "DESTRUCTORS: Diagnostics from finalizers."
#. Tag: para
-#: Chapter.xml:102
+#: Chapter.xml:393
#, no-c-format
msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
msgstr "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
#. Tag: para
-#: Chapter.xml:105
+#: Chapter.xml:396
#, no-c-format
msgid "FUNCTIONS: Diagnostics from functions."
msgstr "FUNCTIONS: Diagnostics from functions."
#. Tag: para
-#: Chapter.xml:108
+#: Chapter.xml:399
#, no-c-format
msgid "OPERATORS: Diagnostics from operators, such as equals."
msgstr "OPERATORS: Diagnostics from operators, such as equals."
#. Tag: para
-#: Chapter.xml:111
+#: Chapter.xml:402
#, no-c-format
msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
msgstr "FUNCS_AND_OPS: Diagnostics from functions and operations."
#. Tag: para
-#: Chapter.xml:114
+#: Chapter.xml:405
#, no-c-format
msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
msgstr "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
#. Tag: para
-#: Chapter.xml:117
+#: Chapter.xml:408
#, no-c-format
msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
msgstr "TRIVIAL_FUNCS: Diagnostics from trivial functions."
#. Tag: para
-#: Chapter.xml:120
+#: Chapter.xml:411
#, no-c-format
msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
msgstr "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
#. Tag: para
-#: Chapter.xml:123
+#: Chapter.xml:414
#, no-c-format
msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
msgstr "ALL_TRIVIAL: Diagnostics from all trivial operations."
#. Tag: para
-#: Chapter.xml:126
+#: Chapter.xml:417
#, 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 "Visibility level – JBoss Transactions 使用 <classname>com.arjuna.common.util.logging.VisibilityLevel</classname> 类里定义的缺省值"
+msgstr ""
+"Visibility level – JBoss Transactions 使用 <classname>com.arjuna.common.util."
+"logging.VisibilityLevel</classname> 类里定义的缺省值"
#. Tag: para
-#: Chapter.xml:129
+#: Chapter.xml:420
#, no-c-format
msgid "VIS_NONE: No Diagnostic"
msgstr "VIS_NONE: No Diagnostic"
#. Tag: para
-#: Chapter.xml:132
+#: Chapter.xml:423
#, no-c-format
msgid "VIS_PRIVATE : only from private methods."
msgstr "VIS_PRIVATE : only from private methods."
#. Tag: para
-#: Chapter.xml:135
+#: Chapter.xml:426
#, no-c-format
msgid "VIS_PROTECTED only from protected methods."
msgstr "VIS_PROTECTED only from protected methods."
#. Tag: para
-#: Chapter.xml:138
+#: Chapter.xml:429
#, no-c-format
msgid "VIS_PUBLIC only from public methods."
msgstr "VIS_PUBLIC only from public methods."
#. Tag: para
-#: Chapter.xml:141
+#: Chapter.xml:432
#, no-c-format
msgid "VIS_PACKAGE only from package methods."
msgstr "VIS_PACKAGE only from package methods."
#. Tag: para
-#: Chapter.xml:144
+#: Chapter.xml:435
#, no-c-format
msgid "VIS_ALL: Full Diagnostic"
msgstr "VIS_ALL: Full Diagnostic"
#. Tag: para
-#: Chapter.xml:147
+#: Chapter.xml:438
#, 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 "Facility Code – JBoss Transactions 使用 <classname>com.arjuna.common.util.logging.VisibilityLevel</classname> 类定义的下列值"
+msgstr ""
+"Facility Code – JBoss Transactions 使用 <classname>com.arjuna.common.util."
+"logging.VisibilityLevel</classname> 类定义的下列值"
#. Tag: para
-#: Chapter.xml:150
+#: Chapter.xml:441
#, no-c-format
msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
msgstr "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
#. Tag: para
-#: Chapter.xml:153
+#: Chapter.xml:444
#, no-c-format
msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
msgstr "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
#. Tag: para
-#: Chapter.xml:156
+#: Chapter.xml:447
#, no-c-format
msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
msgstr "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
#. Tag: para
-#: Chapter.xml:159
+#: Chapter.xml:450
#, no-c-format
msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
msgstr "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
#. Tag: para
-#: Chapter.xml:162
+#: Chapter.xml:453
#, no-c-format
msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
msgstr "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
#. Tag: para
-#: Chapter.xml:165
+#: Chapter.xml:456
#, no-c-format
msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
msgstr "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
#. Tag: para
-#: Chapter.xml:168
+#: Chapter.xml:459
#, no-c-format
msgid "FAC_GENERAL = 0x00000080 (general classes)."
msgstr "FAC_GENERAL = 0x00000080 (general classes)."
#. Tag: para
-#: Chapter.xml:171
+#: Chapter.xml:462
#, no-c-format
msgid ""
"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
@@ -597,34 +1428,39 @@
"classes)."
#. Tag: para
-#: Chapter.xml:174
+#: Chapter.xml:465
#, no-c-format
msgid "FAC_THREADING = 0x00002000 (threading classes)."
msgstr "FAC_THREADING = 0x00002000 (threading classes)."
#. Tag: para
-#: Chapter.xml:177
+#: Chapter.xml:468
#, no-c-format
msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
msgstr "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
#. Tag: para
-#: Chapter.xml:180
+#: Chapter.xml:471
#, no-c-format
-msgid "FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
-msgstr "FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
#. Tag: para
-#: Chapter.xml:183
+#: Chapter.xml:474
#, 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 "为了保证合适的输出，我们有必要在 <filename>CommonLogging.xml</filename> 文件里对一些调试属性进行更详细的设置，启用 JBoss Transactions 模块登记的日志信息。"
+msgstr ""
+"为了保证合适的输出，我们有必要在 <filename>CommonLogging.xml</filename> 文件"
+"里对一些调试属性进行更详细的设置，启用 JBoss Transactions 模块登记的日志信"
+"息。"
#. Tag: para
-#: Chapter.xml:184
+#: Chapter.xml:475
#, no-c-format
msgid ""
"Messages describing the start and the periodical behavior made by the "
@@ -634,11 +1470,13 @@
"messages related to the Crash Recovery protocol and issued by the JBoss "
"Transactions module."
msgstr ""
-"描述启动和 RecoveryManager 的定期行为的消息使用 INFO 级别的输出。如果需要其他调试跟踪信息，你应该设置更详细的调试级别。例如，下面 CommonLogging.xml 里的配置，启用了和 Crash Recovery 协议相关以及 JBoss "
-"Transactions 产生的所有调试信息。"
+"描述启动和 RecoveryManager 的定期行为的消息使用 INFO 级别的输出。如果需要其他"
+"调试跟踪信息，你应该设置更详细的调试级别。例如，下面 CommonLogging.xml 里的配"
+"置，启用了和 Crash Recovery 协议相关以及 JBoss Transactions 产生的所有调试信"
+"息。"
#. Tag: programlisting
-#: Chapter.xml:186
+#: Chapter.xml:477
#, no-c-format
msgid ""
"<!-- Common logging related properties. -->\n"
@@ -660,15 +1498,16 @@
" value=\"0xffffffff\"/>"
#. Tag: para
-#: Chapter.xml:189
+#: Chapter.xml:480
#, no-c-format
msgid ""
"Two logger objects are provided, one manages I18N messages and a second does "
"not."
-msgstr "这里提供了两个 logger 对象，一个管理 I18N 消息而另外一个则处理其他消息。"
+msgstr ""
+"这里提供了两个 logger 对象，一个管理 I18N 消息而另外一个则处理其他消息。"
#. Tag: para
-#: Chapter.xml:192
+#: Chapter.xml:483
#, no-c-format
msgid ""
"Setting the normal recovery messages to the INFO level allows the "
@@ -677,16 +1516,20 @@
"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 级别。这表示 RecoveryManager 将只产生错误、警告或致命错误信息。"
+msgstr ""
+"把常规恢复消息设置为 INFO 级别允许 RecoveryManager 产生适度的报告。如果没有发"
+"生任何事情，它仅仅报告模块的定期登录。要禁用 Recovery Manager 提供的 INFO 消"
+"息，调试级别可以设为更高的 ERROR 级别。这表示 RecoveryManager 将只产生错误、"
+"警告或致命错误信息。"
#. Tag: title
-#: Chapter.xml:196
+#: Chapter.xml:487
#, no-c-format
msgid "Periodic Recovery"
msgstr "定期恢复"
#. Tag: para
-#: Chapter.xml:197
+#: Chapter.xml:488
#, no-c-format
msgid ""
"The RecoveryManager scans the ObjectStore and other locations of "
@@ -698,11 +1541,13 @@
"used are dynamically loaded, using properties found in the RecoveryManager "
"property file."
msgstr ""
-"RecoveryManager 扫描 ObjectStore 以及信息的其他位置，寻找需要恢复的事务和资源。这个扫描和恢复过程由恢复模块来执行（实现 com.arjuna.ats."
-"arjuna.recovery.RecoveryModule 接口的类的实例），每个都负责特定类别的事务和资源。恢复模块使用 RecoveryManager 属性文件里找到的属性动态地进行加载。"
+"RecoveryManager 扫描 ObjectStore 以及信息的其他位置，寻找需要恢复的事务和资"
+"源。这个扫描和恢复过程由恢复模块来执行（实现 com.arjuna.ats.arjuna.recovery."
+"RecoveryModule 接口的类的实例），每个都负责特定类别的事务和资源。恢复模块使"
+"用 RecoveryManager 属性文件里找到的属性动态地进行加载。"
#. Tag: para
-#: Chapter.xml:198
+#: Chapter.xml:489
#, no-c-format
msgid ""
"The interface has two methods: <literal>periodicWorkFirstPass</literal> and "
@@ -719,12 +1564,17 @@
"a candidate for recovery."
msgstr ""
"这个接口有两个方法：<literal>periodicWorkFirstPass</literal> 和 "
-"<literal>periodicWorkSecondPass</literal>。根据 <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
-"classname> 属性定义的间隔，RecoveryManager 件将在每个属性上调用第一个 pass 方法，然后等待一段短暂的时间（由 <classname>com."
-"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname> 属性定义）。通常，在第一个 pass 方法里，模块通过扫描（例如 ObjectStore 的相关部分）来发现可疑的事务和资源（也就是提交过程进行一部分）。在第二个 pass 方法里，如果任何相同的事务或资源仍然可疑，那么原来的应用程序就有可能已经崩溃，这些事务和资源就需要进行恢复。"
+"<literal>periodicWorkSecondPass</literal>。根据 <classname>com.arjuna.ats."
+"arjuna.recovery.periodicRecoveryPeriod</classname> 属性定义的间隔，"
+"RecoveryManager 件将在每个属性上调用第一个 pass 方法，然后等待一段短暂的时间"
+"（由 <classname>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</"
+"classname> 属性定义）。通常，在第一个 pass 方法里，模块通过扫描（例如 "
+"ObjectStore 的相关部分）来发现可疑的事务和资源（也就是提交过程进行一部分）。"
+"在第二个 pass 方法里，如果任何相同的事务或资源仍然可疑，那么原来的应用程序就"
+"有可能已经崩溃，这些事务和资源就需要进行恢复。"
#. Tag: para
-#: Chapter.xml:199
+#: Chapter.xml:490
#, no-c-format
msgid ""
"An attempt, by the RecoveryManager, to recover a transaction that is still "
@@ -739,11 +1589,16 @@
"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
+#: Chapter.xml:491
#, no-c-format
msgid ""
"It is clearly important to set the interval periods appropriately. The total "
@@ -764,19 +1619,28 @@
"progress"
msgstr ""
"设置合适的时间间隔显然很重要。重复时间将是 <literal>periodicRecoveryPeriod</"
-"literal>、<literal>recoveryBackoffPeriod</literal> 和所有恢复模块扫描 ObjectStore 并试图恢复可疑事务所需时间的总和。恢复时间可能包括试图和已经崩溃或无法访问的进程或主机通信所需的连接超时时间（这是为什么在恢复系统里有机制避免试图恢复相同的事务）。总共的重复时间将影响在发生故障后资源保持无法访问状态的时间 － <literal>periodicRecoveryPeriod</literal> 应该相应地进行设置（缺省是 120 秒）。<literal>recoveryBackoffPeriod</literal> 可以相对较短（缺省是 10 秒） － 它的目的主要是减少事务作为恢复备选对象的次数（这需要访问原始进程，检查事务是否仍在进行）。"
+"literal>、<literal>recoveryBackoffPeriod</literal> 和所有恢复模块扫描 "
+"ObjectStore 并试图恢复可疑事务所需时间的总和。恢复时间可能包括试图和已经崩溃"
+"或无法访问的进程或主机通信所需的连接超时时间（这是为什么在恢复系统里有机制避"
+"免试图恢复相同的事务）。总共的重复时间将影响在发生故障后资源保持无法访问状态"
+"的时间 － <literal>periodicRecoveryPeriod</literal> 应该相应地进行设置（缺省"
+"是 120 秒）。<literal>recoveryBackoffPeriod</literal> 可以相对较短（缺省是 "
+"10 秒） － 它的目的主要是减少事务作为恢复备选对象的次数（这需要访问原始进程，"
+"检查事务是否仍在进行）。"
#. Tag: para
-#: Chapter.xml:203
+#: Chapter.xml:494
#, 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 "JBoss Transactions 之前的版本里没有 contact 机制，你得把 backoff period 设置为足够久来避免缓存事务冲突。从 3.0 版本后，这不再是一个问题。"
+msgstr ""
+"JBoss Transactions 之前的版本里没有 contact 机制，你得把 backoff period 设置"
+"为足够久来避免缓存事务冲突。从 3.0 版本后，这不再是一个问题。"
#. Tag: para
-#: Chapter.xml:206
+#: Chapter.xml:497
#, no-c-format
msgid ""
"Two recovery modules (implementations of the <classname>com.arjuna.ats."
@@ -792,12 +1656,16 @@
"process might occur while a periodic recovery pass is in progress). The "
"default Recovery Extension settings are:"
msgstr ""
-"JBoss Transactions 提供了两个恢复模块（<classname>com.arjuna.ats."
-"arjuna.recovery.RecoveryModule</classname> 接口的实现），它们支持不同的事务恢复（包括 JDBC 恢复）。高级用户有可能创建自己的恢复模块并向 Recovery Manager 注册。恢复模块使用以“<classname>com.arjuna.ats.arjuna.recovery."
-"RecoveryExtension</classname>”开始的属性向 Recovery Manager 注册。它们将按照属性名称的顺序调用其定期恢复的 pass 方法（但请注意在定期恢复的 pass 方法运行时，可能会发生应用程序进程失效）。缺省的 Recovery Extension 设置是："
+"JBoss Transactions 提供了两个恢复模块（<classname>com.arjuna.ats.arjuna."
+"recovery.RecoveryModule</classname> 接口的实现），它们支持不同的事务恢复（包"
+"括 JDBC 恢复）。高级用户有可能创建自己的恢复模块并向 Recovery Manager 注册。"
+"恢复模块使用以“<classname>com.arjuna.ats.arjuna.recovery.RecoveryExtension</"
+"classname>”开始的属性向 Recovery Manager 注册。它们将按照属性名称的顺序调用其"
+"定期恢复的 pass 方法（但请注意在定期恢复的 pass 方法运行时，可能会发生应用程"
+"序进程失效）。缺省的 Recovery Extension 设置是："
#. Tag: programlisting
-#: Chapter.xml:208
+#: Chapter.xml:499
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
@@ -813,13 +1681,13 @@
" com.arjuna.ats.txoj.recovery.TORecoveryModule"
#. Tag: title
-#: Chapter.xml:211
+#: Chapter.xml:502
#, no-c-format
msgid "Expired entry removal"
msgstr "删除过期的条目"
#. Tag: para
-#: Chapter.xml:212
+#: Chapter.xml:503
#, no-c-format
msgid ""
"The operation of the recovery subsystem will cause some entries to be made "
@@ -839,18 +1707,25 @@
"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
+#: Chapter.xml:504
#, no-c-format
msgid "The kinds of item that are scanned for expiry are:"
msgstr "扫描过期的条目类型包括："
#. Tag: para
-#: Chapter.xml:214
+#: Chapter.xml:505
#, no-c-format
msgid ""
"TransactionStatusManager items : one of these is created by every "
@@ -862,17 +1737,21 @@
"– 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-using 进程的生存时间。"
+"TransactionStatusManager 条目：使用 JBoss Transactions 的每个应用程序进程创建"
+"的条目 － 它们包含允许 RecoveryManager 决定初始化事务的进程是否仍然活动、以及"
+"事务状态的信息。过期时间由属性 <classname>com.arjuna.ats.arjuna.recovery."
+"transactionStatusManagerExpiryTime</classname>（以小时为单位 － 缺省为 12，0 "
+"表示永不过期）设置。过期时间应该大于任何单个 JBoss Transactions-using 进程的"
+"生存时间。"
#. Tag: para
-#: Chapter.xml:215
+#: Chapter.xml:506
#, no-c-format
msgid "The Expiry Scanner properties for these are:"
msgstr "Expiry Scanner 属性是："
#. Tag: programlisting
-#: Chapter.xml:217
+#: Chapter.xml:508
#, no-c-format
msgid ""
"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
@@ -884,157 +1763,298 @@
"ExpiredTransactionStatusManagerScanner"
#. Tag: title
-#: Chapter.xml:220
+#: Chapter.xml:511
#, no-c-format
-msgid "Errors and Exceptions"
-msgstr "错误和异常"
+msgid "Selecting the JTA implementation"
+msgstr "选择 JTA 实现"
#. Tag: para
-#: Chapter.xml:221
+#: Chapter.xml:512
#, 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 "本节将涵盖在事务行应用程序运行时可能抛出或报告的错误和异常类型，并给出可能的原因。"
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr "目前可通过相同的接口访问两个 JTA 实现的变种。它们是："
#. Tag: para
-#: Chapter.xml:224
+#: Chapter.xml:515
#, 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."
+"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 ""
-"NO_MEMORY：应用程序已耗尽内存（抛出 <classname>OutOfMemoryError</classname>）且 JBoss "
-"Transactions 在重新抛出这个异常时已经试图进行清理（通过运行 garbage collector）。这可能是一个暂时的问题，重试应该能够成功。"
+"纯本地的 JTA，它只允许执行非分布式的 JTA 事务。JBoss Transactions 产品里只有"
+"这个版本可用。"
#. Tag: para
-#: Chapter.xml:227
+#: Chapter.xml:518
#, 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."
+"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 ""
-"com.arjuna.ats.arjuna.exceptions."
-"FatalError：表示事务系统必须关闭的错误已经发生。在抛出这个错误之前，服务将确保所有的事务都进行了回滚。如果捕获了这个异常，应用程序应该清理并退出。如果"
-"进行进一步尝试，可能会破坏应用程序的一致性。"
+"远程的，基于 CORBA 的 JTA，它允许执行分布式的 JTA 事务。它只在 ArjunaJTS 里可"
+"用且需要对 CORBA ORB 的支持。"
#. Tag: para
-#: Chapter.xml:230
+#: Chapter.xml:522
#, 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."
+"both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with JBoss Transactions."
+msgstr "这两种实现都和 JBoss Transactions 提供的事务性的 JDBC 驱动完全兼容。"
+
+#. Tag: para
+#: Chapter.xml:525
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr "要选择本地的 JTA 实现，你必须执行下面的步骤："
+
+#. Tag: para
+#: Chapter.xml:528
+#, 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 ""
-"com.arjuna.ats.arjuna.exceptions."
-"LicenceError：尝试以和当前许可证不一致的方式使用事务服务。事务服务将不会允许对现有的或新的事务进行进一步的行动。"
+"确保属性 <literal>com.arjuna.ats.jta.jtaTMImplementation</literal> 被设置为 "
+"<literal>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</literal>。"
#. Tag: para
-#: Chapter.xml:233
+#: Chapter.xml:531
#, 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."
+"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 ""
-"com.arjuna.ats.arjuna.exceptions.ObjectStoreError：事务服务试图使用 object store "
-"时产生了错误。进一步的行动不被允许。"
+"确保属性 <literal>com.arjuna.ats.jta.jtaUTImplementation</literal> 被设置为 "
+"<literal>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple</literal>。"
#. Tag: para
-#: Chapter.xml:236
+#: Chapter.xml:535
#, 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 "在失效切换的正常执行过程中，可能出现关于状态访问的 Object store 的警告。这是因为在相同的事务上执行多个并行的失效切换。它可以被忽略而无安全隐患。"
+"these settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr "这些设置都是这些属性的缺省值，如果使用本地实现的话，你不需要进行指定。"
#. Tag: title
-#: Chapter.xml:241
+#: Chapter.xml:542
#, no-c-format
-msgid "Selecting the JTA implementation"
-msgstr "选择 JTA 实现"
+msgid "ORB specific configurations"
+msgstr ""
+#. Tag: title
+#: Chapter.xml:544
+#, no-c-format
+msgid "<title>JacORB</title>"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:242
+#: Chapter.xml:545
#, no-c-format
msgid ""
-"Two variants of the JTA implementation are now provided and accessible "
-"through the same interface. These are:"
-msgstr "目前可通过相同的接口访问两个 JTA 实现的变种。它们是："
+"For JacORB to function correctly it is necessary to ensure there is a valid "
+"<filename>jacorb.properties</filename> or <filename>.jacorb_properties</"
+"filename> file in one of the following places:"
+msgstr ""
#. Tag: para
-#: Chapter.xml:245
+#: Chapter.xml:551
#, no-c-format
+msgid "The classpath."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:556
+#, 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 "纯本地的 JTA，它只允许执行非分布式的 JTA 事务。JBoss Transactions 产品里只有这个版本可用。"
+"The home directory of the user running the JBoss Transaction Service. The "
+"home directory is retrieved using <code>System.getProperty( “user.home” );</"
+"code>"
+msgstr ""
#. Tag: para
-#: Chapter.xml:248
+#: Chapter.xml:561
#, no-c-format
+msgid "The current directory."
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:566
+#, 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 "远程的，基于 CORBA 的 JTA，它允许执行分布式的 JTA 事务。它只在 ArjunaJTS 里可用且需要对 CORBA ORB 的支持。"
+"The <filename>lib</filename> directory of the JDK used to run your "
+"application. This is retrieved using <code>System.getProperty( “java.home” );"
+"</code>"
+msgstr ""
#. Tag: para
-#: Chapter.xml:252
+#: Chapter.xml:571
#, no-c-format
msgid ""
-"both of these implementations are fully compatible with the transactional "
-"JDBC driver provided with JBoss Transactions."
-msgstr "这两种实现都和 JBoss Transactions 提供的事务性的 JDBC 驱动完全兼容。"
+"The above places are searched in the order given. A template "
+"<filename>jacorb.properties</filename> file can be found in the JacORB "
+"installation directory."
+msgstr ""
#. Tag: para
-#: Chapter.xml:255
+#: Chapter.xml:574
#, no-c-format
msgid ""
-"In order to select the local JTA implementation it is necessary to perform "
-"the following steps:"
-msgstr "要选择本地的 JTA 实现，你必须执行下面的步骤："
+"Within the JacORB properties file there are two important properties which "
+"must be tailored to suit your application, they are:"
+msgstr ""
+#. Tag: property
+#: Chapter.xml:580
+#, no-c-format
+msgid "jacorb.poa.thread_pool_max"
+msgstr ""
+
+#. Tag: property
+#: Chapter.xml:585
+#, no-c-format
+msgid "jacorb.poa.thread_pool_min"
+msgstr ""
+
#. Tag: para
-#: Chapter.xml:258
+#: Chapter.xml:589
#, 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>."
+"These properties specify the minimum and maximum number of request "
+"processing threads that JacORB will use in its thread pool. If there aren’t "
+"a sufficient number of threads available in this thread pool then the "
+"application may appear to become deadlocked. For more information on "
+"configuring JacORB please reference the JacORB documentation."
msgstr ""
-"确保属性 <literal>com.arjuna.ats.jta.jtaTMImplementation</literal> 被设置为 <literal>"
-"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple<"
-"/literal>。"
#. Tag: para
-#: Chapter.xml:261
+#: Chapter.xml:593
#, 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>."
+"JacORB comes with its own implementation of the classes defined in the "
+"<filename>CosTransactions.idl</filename> file. Unfortunately these are "
+"incompatible with the version shipped with JBossTS. Therefore, it is "
+"important that the JBossTS jar files appear in the <code>CLASSPATH</code> "
+"before any JacORB jars."
msgstr ""
-"确保属性 <literal>com.arjuna.ats.jta.jtaUTImplementation</literal> 被设置为 <literal>"
-"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple<"
-"/literal>。"
#. Tag: para
-#: Chapter.xml:265
+#: Chapter.xml:597
#, 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 "这些设置都是这些属性的缺省值，如果使用本地实现的话，你不需要进行指定。"
+"When running the recovery manager it is important that it always uses the "
+"same well known port for each machine on which it runs. You should not use "
+"the OAPort property provided by JacORB unless the recovery manager has its "
+"own <filename>jacorb.properties</filename> file or this is provided on the "
+"command line when starting the recovery manager. If the recovery manager and "
+"other components of JBossTS share the same <filename>jacorb.properties</"
+"filename> file, then you should use the <filename>com.arjuna.ats.jts."
+"recoveryManagerPort</filename> and <filename>com.arjuna.ats.jts."
+"recoveryManagerAddress</filename> properties."
+msgstr ""
+#. Tag: title
+#: Chapter.xml:603
+#, no-c-format
+msgid "Initializing JBossTS applications"
+msgstr ""
+
+#. Tag: para
+#: Chapter.xml:604
+#, no-c-format
+msgid ""
+"It is important that JBossTS is correctly initialized prior to any "
+"application object being created. In order to guarantee this, the programmer "
+"should use the <methodname>ORB_init</methodname> and <methodname>create_POA</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Chapter.xml:609
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr "错误和异常"
+
+#. Tag: para
+#: Chapter.xml:610
+#, 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:613
+#, 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 ""
+"NO_MEMORY：应用程序已耗尽内存（抛出 <classname>OutOfMemoryError</classname>）"
+"且 JBoss Transactions 在重新抛出这个异常时已经试图进行清理（通过运行 garbage "
+"collector）。这可能是一个暂时的问题，重试应该能够成功。"
+
+#. Tag: para
+#: Chapter.xml:616
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.FatalError：表示事务系统必须关闭的错误已经发"
+"生。在抛出这个错误之前，服务将确保所有的事务都进行了回滚。如果捕获了这个异"
+"常，应用程序应该清理并退出。如果进行进一步尝试，可能会破坏应用程序的一致性。"
+
+#. Tag: para
+#: Chapter.xml:619
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError：尝试以和当前许可证不一致的方式"
+"使用事务服务。事务服务将不会允许对现有的或新的事务进行进一步的行动。"
+
+#. Tag: para
+#: Chapter.xml:622
+#, 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 ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError：事务服务试图使用 object "
+"store 时产生了错误。进一步的行动不被允许。"
+
+#. Tag: para
+#: Chapter.xml:625
+#, 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 ""
+"在失效切换的正常执行过程中，可能出现关于状态访问的 Object store 的警告。这是"
+"因为在相同的事务上执行多个并行的失效切换。它可以被忽略而无安全隐患。"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Feedback.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Feedback.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Feedback.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Feedback.po to
+# translation of Preface.po to
# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Feedback\n"
+"Project-Id-Version: Preface\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-24 11:47+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-16 11:05+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -35,9 +35,9 @@
"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 ""
-"如果你在本指南里发现了印刷错误，或者你有改进该手册的建议，我们希望听到你的声音！请提交报告到 <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> 并指明：产品：JBoss 企业级应用"
-"程序平台, 版本：<replaceable><version></replaceable>，组件：<emphasis>Doc</"
-"emphasis>。"
-"如果是改进本文档的建议，请尽量具体化；如果是其他错误，请指出章节号以及具体的内容"
-"，这样我们就可以尽快改正。"
-
+"如果你在本指南里发现了印刷错误，或者你有改进该手册的建议，我们希望听到你的声"
+"音！请提交报告到 <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP"
+"\">JIRA</ulink> 并指明：产品：JBoss 企业级应用程序平台, 版本："
+"<replaceable><version></replaceable>，组件：<emphasis>Doc</emphasis>。"
+"如果是改进本文档的建议，请尽量具体化；如果是其他错误，请指出章节号以及具体的"
+"内容，这样我们就可以尽快改正。"
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Preface.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Preface.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Preface\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-06-05 22:49+0000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
"PO-Revision-Date: 2008-06-16 11:05+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
@@ -34,9 +34,7 @@
msgid ""
"The Administration Guide contains information on how to administer JBoss "
"Transactions API 4.2.3."
-msgstr ""
-"《管理员指南》包含如何管理 JBoss "
-"Transactions API 4.2.3 的信息。"
+msgstr "《管理员指南》包含如何管理 JBoss Transactions API 4.2.3 的信息。"
#. Tag: title
#: Preface.xml:17
@@ -66,7 +64,10 @@
"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 "为了管理 JBoss Transactions，你首先必须理解它的很多事务方面的功能依赖于 ArjunaCore。因此，在管理 JBoss Transactions 之前，先阅读《ArjunaCore 管理员指南》是很重要的。"
+msgstr ""
+"为了管理 JBoss Transactions，你首先必须理解它的很多事务方面的功能依赖于 "
+"ArjunaCore。因此，在管理 JBoss Transactions 之前，先阅读《ArjunaCore 管理员指"
+"南》是很重要的。"
#. Tag: title
#: Preface.xml:25
@@ -87,7 +88,9 @@
"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 "第一章，JBoss Transactions 管理：描述如何使用不同的 JTA 实现来管理 JBoss Transactions：纯 local 或 remote 方式（允许分布式事务）。"
+msgstr ""
+"第一章，JBoss Transactions 管理：描述如何使用不同的 JTA 实现来管理 JBoss "
+"Transactions：纯 local 或 remote 方式（允许分布式事务）。"
#. Tag: title
#: Preface.xml:34
@@ -101,9 +104,7 @@
msgid ""
"In addition to this guide, the following guides are available in the JBoss "
"Transactions API 4.2.3 documentation set:"
-msgstr ""
-"除了本指南外， JBoss "
-"Transactions API 4.2.3 的文档集里还有如下的文档："
+msgstr "除了本指南外， JBoss Transactions API 4.2.3 的文档集里还有如下的文档："
#. Tag: para
#: Preface.xml:38
@@ -111,7 +112,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Release Notes: Provides late-breaking "
"information about JBoss Transactions API 4.2.3."
-msgstr "JBoss Transactions API 4.2.3 发行注记：提供 JBoss Transactions API 4.2.3 的最新信息。"
+msgstr ""
+"JBoss Transactions API 4.2.3 发行注记：提供 JBoss Transactions API 4.2.3 的最"
+"新信息。"
#. Tag: para
#: Preface.xml:41
@@ -119,7 +122,9 @@
msgid ""
"JBoss Transactions API 4.2.3 Installation Guide: This guide provides "
"instructions for installing JBoss Transactions API 4.2.3."
-msgstr "JBoss Transactions API 4.2.3 安装指南：提供 JBoss Transactions API 4.2.3 的安装说明。"
+msgstr ""
+"JBoss Transactions API 4.2.3 安装指南：提供 JBoss Transactions API 4.2.3 的安"
+"装说明。"
#. Tag: para
#: Preface.xml:44
@@ -128,4 +133,3 @@
"JBoss Transactions API 4.2.3 Programmer’s Guide: Provides guidance for "
"writing applications."
msgstr "JBoss Transactions API 4.2.3 程序员指南：指导如何编写相关应用程序。"
-
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Revision_History.po 2009-09-17 01:40:06 UTC (rev 29384)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Administrators_Guide/zh-CN/Revision_History.po 2009-09-17 02:36:56 UTC (rev 29385)
@@ -1,14 +1,14 @@
-# translation of Revision_History.po to
+# translation of Preface.po to
# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
#
# Automatically generated, 2008.
# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Revision_History\n"
+"Project-Id-Version: Preface\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-24 11:43+1000\n"
+"POT-Creation-Date: 2009-09-17 01:53+0000\n"
+"PO-Revision-Date: 2008-06-16 11:05+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -16,9 +16,14 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "修订记录"
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
msgstr "<firstname></firstname> <surname></surname> <email></email>"
-
More information about the jboss-svn-commits
mailing list