[jboss-svn-commits] JBL Code SVN: r25678 - in labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide: de-DE and 5 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Mon Mar 16 23:40:33 EDT 2009
Author: mospina
Date: 2009-03-16 23:40:32 -0400 (Mon, 16 Mar 2009)
New Revision: 25678
Added:
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/An_Introduction_to_the_JTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Configuring_JBossJTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Examples.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/JDBC_and_Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Preface.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/The_Resource_Manager.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Transaction_Recovery.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Using_JBossJTA_in_Application_Servers.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/An_Introduction_to_the_JTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Configuring_JBossJTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Examples.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/JDBC_and_Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Preface.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/The_Resource_Manager.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Transaction_Recovery.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Using_JBossJTA_in_Application_Servers.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/An_Introduction_to_the_JTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Configuring_JBossJTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Examples.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/JDBC_and_Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Preface.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/The_Resource_Manager.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Transaction_Recovery.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Using_JBossJTA_in_Application_Servers.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/An_Introduction_to_the_JTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Configuring_JBossJTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Examples.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/JDBC_and_Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Preface.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/The_Resource_Manager.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Transaction_Recovery.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Using_JBossJTA_in_Application_Servers.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/An_Introduction_to_the_JTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Configuring_JBossJTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Examples.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/JDBC_and_Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Preface.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/The_Resource_Manager.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Transaction_Recovery.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Using_JBossJTA_in_Application_Servers.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Author_Group.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Book_Info.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Configuring_JBossJTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Examples.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Preface.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Revision_History.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po
Modified:
labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/Makefile
Log:
PO files updated for OTHER_LANGS
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/Makefile
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/Makefile 2009-03-17 03:15:53 UTC (rev 25677)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/Makefile 2009-03-17 03:40:32 UTC (rev 25678)
@@ -5,6 +5,7 @@
BRAND = JBoss
#OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW
+OTHER_LANGS = de-DE es-ES fr-FR ja-JP pt-BR zh-CN
COMMON_CONFIG = /usr/share/publican
include $(COMMON_CONFIG)/make/Makefile.common
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/An_Introduction_to_the_JTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/An_Introduction_to_the_JTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/An_Introduction_to_the_JTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,154 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr "Eine Einführung in die JTA"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr "Die Java Transaktions-API"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:9
+#, no-c-format
+msgid ""
+"The interfaces specified by the many transaction standards are typically too "
+"low-level for most application programmers. Therefore, Sun Microsystems has "
+"specified higher-level interfaces to assist in the development of "
+"distributed transactional applications. Note, these interfaces are still low-"
+"level, and require, for example, the programmer to be concerned with state "
+"management and concurrency for transactional application. In addition, they "
+"are geared more for applications which require XA resource integration "
+"capabilities, rather than the more general resources which the other APIs "
+"allow."
+msgstr ""
+"Die von den vielen Transaktionsstandards spezifizierten Schnittstellen sind "
+"in der Regel zu low-level für die meisten Anwendungsprogrammierer. Deshalb "
+"hat Sun Microsystems höhere Schnittstellen spezifiziert, um die Entwicklung "
+"verteilter transaktionaler Anwendungen zu unterstützen. Beachten Sie, dass "
+"diese Schnittstellen immer noch low-level sind, und z. B. vom Programmierer "
+"erfordern, sich bei transaktionalen Anwendungen um Zustandsmanagement und "
+"Nebenläufigkeit zu kümmern. Zudem sind sie eher ausgelegt für Anwendungen, "
+"die die Fähigkeit zur Integration von XA-Ressourcen benötigen, statt der "
+"allgemeineren Ressourcen, die andere APIs erlauben."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:12
+#, no-c-format
+msgid ""
+"With reference to [JTA99], distributed transaction services typically "
+"involve a number of participants:"
+msgstr ""
+"In Bezug auf [JTA99], beteiligen verteilte Transaktionsdienste in der Regel "
+"eine Anzahl von Teilnehmern:"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:17
+#, no-c-format
+msgid ""
+"Application server: which provides the infrastructure required to support "
+"the application run-time environment which includes transaction state "
+"management, for example, an EJB server."
+msgstr ""
+"Anwendungsserver: stellt die erforderliche Infrastruktur bereit, um die "
+"Laufzeitumgebung der Anwendung zu unterstützen, dies schließt "
+"Zustandsmanagement für Transaktionen ein, z. B. ein EJB-Server."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:22
+#, no-c-format
+msgid ""
+"Transaction manager: provides the services and management functions required "
+"to support transaction demarcation, transactional resource management, "
+"synchronisation and transaction context propagation."
+msgstr ""
+"Transaktionsmanager: stellt die erforderlichen Dienst- und "
+"Managementfunktionen bereit zum Unterstützen von Transaktionsdemarkation, "
+"Management der Transaktionsressourcen, Synchronisation und Fortpflanzung von "
+"Transaktionskontext."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:27
+#, no-c-format
+msgid ""
+"Resource manager: (through a resource adapter<footnote> <para> A Resource "
+"Adapter is used by an application server or client to connect to a Resource "
+"Manager. JDBC drivers which are used to connect to relational databases are "
+"examples of Resource Adapters. </para> </footnote>) provides the application "
+"with access to resources. The resource manager participates in distributed "
+"transactions by implementing a transaction resource interface used by the "
+"transaction manager to communicate transaction association, transaction "
+"completion and recovery."
+msgstr ""
+"Ressourcenmanager: (mittels eines Ressourcenadapters<footnote> <para> Ein "
+"Ressourcenadapter wird von einem Anwendungsserver oder Client benutzt, um "
+"mit einem Ressourcenmanager zu verbinden. JDBC-Treiber, die zum Verbinden "
+"mit relationalen Datenbanken genutzt werden, sind Beispiele für "
+"Ressourcenadapter. </para> </footnote>) gewährt der Anwendung Zugriff auf "
+"Ressourcen. Der Ressourcenmanager nimmt an verteilten Transaktionen teil "
+"durch Implementierung einer Schnittstelle der Transaktionsressource, welche "
+"verwendet wird vom Transaktionsmanager, um Transaktionsassoziationen, "
+"Transaktionsabschluss und Recovery zu kommunizieren."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:36
+#, no-c-format
+msgid ""
+"A communication resource manager (CRM): supports transaction context "
+"propagation and access to the transaction service for incoming and outgoing "
+"requests."
+msgstr ""
+"Ein Kommunikationsressourcenmanager (communication resource manager, CRM): "
+"unterstützt die Fortpflanzung von Transaktionskontext und Zugriff auf den "
+"Transaktionsdienst für eingehende und ausgehende Anfragen."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:41
+#, no-c-format
+msgid ""
+"From the transaction manager’s perspective, the actual implementation of the "
+"transaction services does not need to be exposed; only high-level interfaces "
+"need to be defined to allow transaction demarcation, resource enlistment, "
+"synchronization and recovery process to be driven from the users of the "
+"transaction services. The JTA is a high-level application interface that "
+"allows a transactional application to demarcate transaction boundaries, and "
+"contains also contains a mapping of the X/Open XA protocol."
+msgstr ""
+"Aus der Perspektive des Transaktionsmanagers braucht die eigentliche "
+"Implementierung des Transaktionsdienstes nicht offengelegt zu werden; es "
+"müssen nur high-level Schnittstellen definiert werden, um das Ausführen von "
+"Transaktionsdemarkation, Ressourceneintragung, Synchronisation und Recovery-"
+"Prozess durch die Benutzer der Transaktionsdienste zu ermöglichen. Die JTA "
+"ist eine high-level Anwendungsschnittstelle, die einer transaktionalen "
+"Anwendung ermöglicht, Transaktionsgrenzen zu setzen und zudem ein Mapping "
+"des X/Open XA-Protokolls beinhaltet."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:45
+#, no-c-format
+msgid ""
+"The JTA support provided by JBossJTA is compliant with the 1.0.1 "
+"specification."
+msgstr ""
+"Die von JBossJTA bereitgestellte JTA-Unterstützung folgt den 1.0.1 "
+"Spezifikationen."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Author_Group.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Author_Group.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,23 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Book_Info.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Book_Info.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,49 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#, fuzzy, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide CP04"
+msgstr "JBoss Transactions JTA Handbuch für Programmierer"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "Für den Gebrauch mit JBoss Enterprise Application Platform 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+"Dieses Handbuch behandelt die Transactions JTA aus Sicht des Programmierers"
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Configuring_JBossJTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Configuring_JBossJTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Configuring_JBossJTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,145 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr "Konfigurierung von JBossJTA"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:8
+#, no-c-format
+msgid "Configuring options"
+msgstr "Konfigurationsoptionen"
+
+#. Tag: para
+#: Configuring_JBossJTA.xml:9
+#, no-c-format
+msgid ""
+"The following table shows the configuration features, with default values "
+"shown in italics. For more detailed information, the relevant section "
+"numbers are provided."
+msgstr ""
+"Die folgende Tabelle zeigt die Konfigurations-Features, Standardwerte sind "
+"kursiv gedruckt. Für detailliertere Informationen sist die Kapitelnummer "
+"angegeben."
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:13
+#, no-c-format
+msgid "JBossJTA configuration options."
+msgstr "JBossJTA Konfigurationsoptionen."
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:17
+#, no-c-format
+msgid "Configuration Name"
+msgstr "Konfigurationsname"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:20
+#, no-c-format
+msgid "Possibile Values"
+msgstr "Mögliche Werte"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:23
+#, no-c-format
+msgid "Relevant Section"
+msgstr "Relevantes Kapitel"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:30
+#, no-c-format
+msgid "com.arjuna.ats.jta.supportSubtransactions"
+msgstr "com.arjuna.ats.jta.supportSubtransactions"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr "YES/NO"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr "com.arjuna.ats.jta.jtaTMImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:43
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr "com.arjuna.ats.jta.jtaUTImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:53
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr "com.arjuna.ats.jta.xaBackoffPeriod"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr "com.arjuna.ats.jdbc.isolationLevel"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr "Jede unterstützte JDBC-Isolationsebene"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr "true/false"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr "Kapitel 3"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Examples.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Examples.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Examples.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,836 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr "Beispiele"
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr "JDBC-Beispiel"
+
+#. Tag: para
+#: Examples.xml:9
+#, no-c-format
+msgid ""
+"The following code illustrates many of the points described above (note that "
+"for simplicity, much error checking code has been remove). This example "
+"assumes that you are using the transactional JDBC driver provided with "
+"JBossTS. For details about how to configure and use this driver see the "
+"previous Chapter."
+msgstr ""
+"Der folgende Code veranschaulicht viele der oben beschriebenen Punkte "
+"(beachten Sie, dass zur besseren Lesbarkeit viel Fehlererkennungs-Code "
+"entfernt wurde). Dies Beispiel nimmt an, dass Sie den transaktionalen JDBC-"
+"Treiber verwenden, der mit JBossTS geliefert wird. Für Einzelheiten zur "
+"Konfiguration und Verwendung dieses Treibers werfen Sie bitte einen Blick "
+"auf das vorherige Kapitel."
+
+#. Tag: screen
+#: Examples.xml:12
+#, no-c-format
+msgid ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+msgstr ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+
+#. Tag: title
+#: Examples.xml:16
+#, no-c-format
+msgid "Failure recovery example"
+msgstr "Failure-Recovery-Beispiel"
+
+#. Tag: para
+#: Examples.xml:17
+#, no-c-format
+msgid ""
+"This class implements the <interfacename>XAResourceRecovery</interfacename> "
+"interface for <code>XAResources</code>. The parameter supplied in "
+"setParameters can contain arbitrary information necessary to initialize the "
+"class once created. In this instance it contains the name of the property "
+"file in which the db connection information is specified, as well as the "
+"number of connections that this file contains information on (separated "
+"by ;)."
+msgstr ""
+"Diese Klasse implementiert die <interfacename>XAResourceRecovery</"
+"interfacename>-Schnittstelle für <code>XAResources</code>. Die in "
+"setParameters angegebenen Parameter können beliebige Informationen "
+"enthalten, die nach der Erstellung der Klasse nötig sind zu ihrer "
+"Initialisierung. In diesem Fall ist der Name der Eigenschaftsdatei "
+"enthalten, in der die db-Verbindungsinformationen spezifiziert sind, sowie "
+"die Anzahl der Verbindungen, für die diese Datei Informationen enthält "
+"(getrennt durch ;)."
+
+#. Tag: para
+#: Examples.xml:21
+#, no-c-format
+msgid ""
+"This is only an <emphasis>example</emphasis> of the sorts of things an "
+"<code>XAResourceRecovery</code> implementer could do. This implementation "
+"uses a property file that is assumed to contain sufficient information to "
+"recreate connections used during the normal run of an application so that we "
+"can perform recovery on them. It is not recommended that information such as "
+"user name and password appear in such a raw text format as it opens up a "
+"potential security hole."
+msgstr ""
+"Dies ist nur ein <emphasis>Beispiel</emphasis> für die Dinge, die ein "
+"<code>XAResourceRecovery</code>-Implementer realisieren kann. Diese "
+"Implementierung nutzt eine Eigenschaftsdatei, von der angenommen wird, dass "
+"sie ausreichend Informationen enthält zum Wiederherstellen von Verbindungen, "
+"die beim normalen Ausführen einer Anwendung verwendet werden, so dass wir "
+"eine Recovery an ihnen durchführen können. Wir raten davon ab, dass "
+"Informationen wie Benutzername und Passwort in einem solchen Rohtextformat "
+"erscheinen, da sich sonst eine mögliche Sicherheitslücke auftut. "
+
+#. Tag: para
+#: Examples.xml:25
+#, no-c-format
+msgid ""
+"The db parameters specified in the property file are assumed to be in the "
+"format:"
+msgstr ""
+"Die in der Eigenschaftsdatei spezifizierten db-Parameter werden in diesem "
+"Format angenommen:"
+
+#. Tag: para
+#: Examples.xml:30
+#, no-c-format
+msgid "DB_x_DatabaseURL="
+msgstr "DB_x_DatabaseURL="
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr "DB_x_DatabaseUser="
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr "DB_x_DatabasePassword="
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr "DB_x_DatabaseDynamicClass="
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr "Wobei X die Nummer der Verbindungsinformation ist."
+
+#. Tag: para
+#: Examples.xml:54
+#, no-c-format
+msgid ""
+"Some error handling code has been removed from this text for ease of "
+"readability purposes."
+msgstr ""
+"Aus diesem Text wurde einiger Fehler-Handling-Code entfernt, um die "
+"Lesbarkeit zu verbessern."
+
+#. Tag: screen
+#: Examples.xml:58
+#, no-c-format
+msgid ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+msgstr ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+
+#. Tag: para
+#: Examples.xml:59
+#, no-c-format
+msgid ""
+"The class <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> may be used to create a new connection "
+"to the database using the same parameters that were used to create the "
+"initial connection."
+msgstr ""
+"Die Klasse <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> kann dazu verwendet werden, eine neue "
+"Verbindung zur Datenbank zu erstellen unter Anwendung derselben Parameter, "
+"die auch zur Erstellung der anfänglichen Verbindung benutzt wurden."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
===================================================================
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/JDBC_and_Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/JDBC_and_Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/JDBC_and_Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,1016 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr "JDBC und Transaktionen"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr "Verwenden des transaktionalen JDBC-Treibers"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:9
+#, no-c-format
+msgid ""
+"JBossJTA supports the construction of both local and distributed "
+"transactional applications which access databases using the JDBC 2.0 APIs. "
+"JDBC 2.0 supports two-phase commit of transactions, and is similar to the XA "
+"X/Open standard. The JDBC 2.0 support is found in the com.arjuna.ats.jdbc "
+"package."
+msgstr ""
+"JBossJTA unterstützt die Konstruktion von sowohl lokalen als auch verteilten "
+"transaktionalen Anwendungen, die unter Verwendung der JDBC 2.0 APIs auf "
+"Datenbanken zugreifen. JDBC 2.0 unterstützt die zwei-Phasen Festschreibung "
+"von Transaktionen und ähnelt dem XA X/Open-Standard. Die JDBC 2.0 "
+"Unterstützung ist im com.arjuna.ats.jdbc-Paket zu finden."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:12
+#, no-c-format
+msgid ""
+"The JDBC 2.0 support has been tested with the following drivers and "
+"databases:"
+msgstr ""
+"Die JDBC 2.0 Unterstützung wurde mit folgenden Treibern und Datenbanken "
+"getestet:"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr "Oracle 8.1.6/8.1.7, 9i und 10g Thin Treiber."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr "MS SQL Server 2000 nativer Treiber."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:27
+#, no-c-format
+msgid "In the past we have qualified against:"
+msgstr "In der Vergangenheit haben wir uns qualifiziert für:"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:32
+#, no-c-format
+msgid "Merant’s Sequelink 5.1 with Oracle 8.1.6"
+msgstr "Merant’s Sequelink 5.1 mit Oracle 8.1.6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr "Cloudscape 3.6 mit Cloudscapes eigener Datenbank."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:42
+#, no-c-format
+msgid ""
+"However, these drivers and databases are no longer part of our supported "
+"platforms. They may continue to work with JBossTS, but we cannot make that "
+"guarantee."
+msgstr ""
+"Diese Treiber und Datenbanken gehören jedoch nicht mehr zu unseren "
+"unterstützten Plattformen. Zwar funktionieren sie evtl. weiterhin mit "
+"JBossTS, aber garantieren können wir dies nicht."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:46
+#, no-c-format
+msgid "Managing transactions"
+msgstr "Steuerung von Transaktionen"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:47
+#, no-c-format
+msgid ""
+"JBossJTA must be able to associate work performed on a JDBC connection with "
+"a specific transaction. Therefore, implicit transaction propagation and/or "
+"indirect transaction management must be used by applications, i.e., for each "
+"JDBC connection it must be possible for JBossJTA to determine the invoking "
+"thread’s current transaction context."
+msgstr ""
+"JBossJTA muss in der Lage sein, die auf einer JDBC-Verbindung ausgeführte "
+"Arbeit mit einer bestimmten Transaktion zu assoziieren. Deshalb muss "
+"implizites Fortpflanzen von Transaktionen und/oder indirektes "
+"Transaktionsmanagment von den Anwendungen verwendet werden, d. h. für jede "
+"JDBC-Verbindung muss es JBossJTA möglich sein, den derzeitigen "
+"Transaktionskontext des aufrufenden Threads zu bestimmen."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:52
+#, no-c-format
+msgid "Restrictions"
+msgstr "Einschränkungen"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:53
+#, no-c-format
+msgid ""
+"The following restrictions are imposed by limitations in the JDBC "
+"specifications and by JBossJTA to ensure that transactional interactions "
+"with JDBC databases can be correctly managed:"
+msgstr ""
+"Die folgenden Einschränkungen sind auferlegt durch Beschränkungen in den "
+"JDBC-Spezifikationen, sowie durch JBossJTA, um sicherzustellen, dass "
+"transaktionale Interaktionen mit JDBC-Datenbanken ordnungsgemäß gesteuert "
+"werden können:"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:57
+#, no-c-format
+msgid ""
+"Nested transactions are not supported by JDBC 2.0. If an attempt is made to "
+"use a JDBC connection within a subtransaction, JBossJTA will throw a "
+"suitable exception and no work will be allowed on that connection. However, "
+"if you wish to have nested transactions, then you can set the <property>com."
+"arjuna.ats.jta.supportSubtransactions</property> property to YES."
+msgstr ""
+"Verschachtelte Transaktionen werden von JDBC 2.0 nicht unterstützt. Falls "
+"versucht wird, eine JDBC-Verbindung innerhalb einer untergeordneten "
+"Transaktion zu nutzen, wird JBossJTA eine passende Ausnahme werfen und keine "
+"Arbeit auf dieser Verbindung erlauben. Wenn Sie jedoch verschachtelte "
+"Transaktionen wünschen, können Sie die <property>com.arjuna.ats.jta."
+"supportSubtransactions</property>-Eigenschaft auf YES setzen."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:63
+#, no-c-format
+msgid "Transactional drivers"
+msgstr "Transaktionale Treiber"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:64
+#, no-c-format
+msgid ""
+"The JBossJTA approach to incorporating JDBC connections within transactions "
+"is to provide transactional JDBC drivers through which all interactions "
+"occur. These drivers intercept all invocations and ensure that they are "
+"registered with, and driven by, appropriate transactions. There is a single "
+"type of transactional driver through which any JDBC driver can be driven; "
+"obviously if the database is not transactional then ACID properties cannot "
+"be guaranteed. This driver is <code>com.arjuna.ats.jdbc.TransactionalDriver</"
+"code>, which implements the <interfacename>java.sql.Driver</interfacename> "
+"interface."
+msgstr ""
+"Die Herangehensweise von JBossJTA an das Einbinden von JDBC-Verbindungen in "
+"Transaktionen ist, transaktionale JDBC-Treiber bereitzustellen, über die "
+"alle Interaktionen erfolgen. Diese Treiber fangen alle Aufrufe ab und "
+"stellen sicher, dass diese bei der passenden Transaktion registriert sind "
+"und von dort ausgeführt werden. Es gibt einen einzelnen transaktionalen "
+"Treibertyp, durch den sämtliche JDBC-Treiber gesteuert werden können; "
+"natürlich können keine ACID-Eigenschaften garantiert werden, falls die "
+"Datenbank nicht transaktional ist. Dieser Treiber ist der <code>com.arjuna."
+"ats.jdbc.TransactionalDriver</code>, welcher die <interfacename>java.sql."
+"Driver</interfacename>-Schnittstelle implementiert."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:68
+#, no-c-format
+msgid "Loading drivers"
+msgstr "Laden von Treibern"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:69
+#, no-c-format
+msgid ""
+"The driver may be directly instantiated and used within an application. For "
+"example:"
+msgstr ""
+"Der Treiber kann direkt instanziert und innerhalb einer Anwendung genutzt "
+"werden. Zum Beispiel:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:73
+#, no-c-format
+msgid "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+msgstr "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:74
+#, no-c-format
+msgid ""
+"They can be registered with the JDBC driver manager (<code>java.sql."
+"DriverManager</code>) by adding them to the Java system properties. The "
+"<property>jdbc.drivers</property> property contains a list of driver class "
+"names, separated by colons, that are loaded by the JDBC driver manager when "
+"it is initialized."
+msgstr ""
+"Diese können beim JDBC-Treibermanager (<code>java.sql.DriverManager</code>) "
+"registriert werden, indem sie zu den Java-Systemeigenschaften hinzugefügt "
+"werden. Die <property>jdbc.drivers</property>-Eigenschaft enthält eine Liste "
+"der Treiberklassennamen, durch Doppelpunkt getrennt, welche vom JDBC-"
+"Treibermanager bei dessen Initialisierung geladen werden."
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:77
+#, no-c-format
+msgid ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+msgstr ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:78
+#, no-c-format
+msgid ""
+"Alternatively, the <methodname>Class.forName()</methodname> method may be "
+"used to load the driver or drivers:"
+msgstr ""
+"Alternativ kann die <methodname>Class.forName()</methodname>-Methode zum "
+"Laden des Treibers bzw. der Treiber verwendet werden:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:82
+#, no-c-format
+msgid ""
+"Calling <methodname>Class.forName()</methodname> will automatically register "
+"the driver with the JDBC driver manager. It is also possible to explicitly "
+"create an instance of the JDBC driver:"
+msgstr ""
+"Der Aufruf <methodname>Class.forName()</methodname> wird den Treiber "
+"automatisch beim JDBC-Treibermanager registrieren. Es ist auch möglich, "
+"explizit eine Instanz des JDBC-Treibers zu erstellen:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:85
+#, no-c-format
+msgid ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+msgstr ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:86
+#, no-c-format
+msgid ""
+"When you have loaded a driver, it is available for making a connection with "
+"a DBMS."
+msgstr ""
+"Wenn Sie einen Treiber geladen haben, steht er zum Herstellen einer "
+"Verbindung zu einem DBMS zur Verfügung."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:92
+#, no-c-format
+msgid "Connections"
+msgstr "Verbindungen"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:93
+#, no-c-format
+msgid ""
+"In this section we shall discuss the notion of transactional JDBC "
+"connections, how they are managed within JBossJTA and the implications on "
+"using them within an application."
+msgstr ""
+"In diesem Abschnitt soll der Begriff der transaktionalen JDBC-Verbindungen "
+"erläutert werden, sowie deren Steuerung innerhalb von JBossJTA und die "
+"Auswirkungen auf ihre Verwendung innerhalb einer Anwendung."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:97
+#, no-c-format
+msgid "Making the connection"
+msgstr "Verbindungsherstellung"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:98
+#, no-c-format
+msgid ""
+"Because JDBC connectivity in JBossJTA works by simply providing a new JDBC "
+"driver, application code can remain relatively the same to that when not "
+"using transactions. Typically, the application programmer need only start "
+"and terminate transactions."
+msgstr ""
+"Da JDBC-Konnektivität in JBossJTA durch die einfache Bereitstellung eines "
+"neuen JDBC-Treibers funktioniert, kann der Anwendungs-Code unverändert "
+"bleiben im Vergleich zum Code, wenn keine Transaktionen genutzt werden. In "
+"der Regel muss der Anwendungsprogrammierer lediglich Transaktionen starten "
+"und beenden."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr "JDBC 2.0"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:104
+#, no-c-format
+msgid ""
+"Before describing the JDBC 2.0 support it is necessary to mention that the "
+"following properties can be set and passed to the JBossJTA driver (they are "
+"all located in the <classname>com.arjuna.ats.jdbc.TransactionalDriver</"
+"classname> class):"
+msgstr ""
+"Bevor die JDBC 2.0 Unterstützung beschrieben wird, ist es notwendig zu "
+"erwähnen, dass die folgenden Eigenschaften eingestellt und an den JBossJTA-"
+"Treiber übergeben werden können (sie befinden sich alle in der "
+"<classname>com.arjuna.ats.jdbc.TransactionalDriver</classname>-Klasse):"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:110
+#, no-c-format
+msgid ""
+"<property>userName</property>: the user name to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>userName</property>: der Benutzername, unter dem das Verbinden mit "
+"der Datenbank versucht werden soll."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:115
+#, no-c-format
+msgid ""
+"<property>password</property>: the password to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>password</property>: das Passwort, mit dem das Verbinden mit der "
+"Datenbank versucht werden soll."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:120
+#, no-c-format
+msgid ""
+"<property>createDb</property>: if set to true, the driver will attempt to "
+"create the database when it connects. This may not be supported by all JDBC "
+"2.0 implementations."
+msgstr ""
+"<property>createDb</property>: wenn auf \"true\" gesetzt, wird der Treiber "
+"versuchen, die Datenbank zu erstellen, wenn er verbindet. Dies wird ggf. "
+"nicht von allen JDBC-Implementierungen unterstützt."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:125
+#, no-c-format
+msgid ""
+"<property>dynamicClass</property>: this specifies a class to instantiate to "
+"connect to the database, rather than using JNDI."
+msgstr ""
+"<property>dynamicClass</property>: dies spezifiziert eine Klasse zum "
+"Instanzieren der Verbindung mit der Datenbank, statt mittels JNDI."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr "XADataSources"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:132
+#, no-c-format
+msgid ""
+"JDBC 2.0 connections are created from appropriate DataSources. Those "
+"connections which must participate within distributed transactions are "
+"obtained from <code>XADataSources</code>. Therefore, when using a JDBC 2.0 "
+"driver, JBossJTA will use the appropriate DataSource whenever a connection "
+"to the database is made. It will then obtain <code>XAResources</code> and "
+"register them with the transaction via the JTA interfaces. It is these "
+"<code>XAResources</code> which the transaction service will use when the "
+"transaction terminates in order to drive the database to either commit or "
+"rollback the changes made via the JDBC connection."
+msgstr ""
+"JDBC 2.0 Verbindungen werden von entsprechenden DataSources erstellt. Diese "
+"Verbindungen, die an verteilten Transaktionen teilnehmen müssen, werden von "
+"<code>XADataSources</code> bezogen. Beim Verwenden von JDBC 2.0 wird "
+"JBossJTA deshalb die entsprechende DataSource verwenden, wann immer eine "
+"Verbindung zur Datenbank hergestellt wird. Es bezieht dann "
+"<code>XAResources</code> und registriert sie bei der Transaktion mittels der "
+"JTA-Schnittstellen. Eben diese <code>XAResources</code> werden während des "
+"Beendens der Transaktion vom Transaktionsdienst verwendet, um die Datenbank "
+"entweder zum Festschreiben oder zum Zurücksetzen der via JDBC-Verbindung "
+"durchgeführten Änderungen zu veranlassen."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:136
+#, no-c-format
+msgid ""
+"There are two ways in which the JBossJTA JDBC 2.0 support can obtain "
+"<code>XADataSources</code>. These will be explained in the following "
+"sections. Note, for simplicity we shall assume that the JDBC 2.0 driver is "
+"instantiated directly by the application."
+msgstr ""
+"Es gibt zwei Wege, auf denen die JBossJTA JDBC 2.0 Unterstützung "
+"<code>XADataSources</code> erhalten kann. Diese werden in den nachfolgenden "
+"Abschnitten erklärt. Beachten Sie, dass zur Vereinfachung angenommen werden "
+"soll, dass der JDBC 2.0 Treiber direkt durch die Anwendung instanziert wird."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr "Java Naming and Directory Interface (JNDI)"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:141
+#, no-c-format
+msgid ""
+"In order to allow a JDBC driver to use arbitrary DataSources without having "
+"to know specific details about their implementations, DataSources are "
+"typically obtained from JNDI. A specific (XA)DataSource can be created and "
+"registered with an appropriate JNDI implementation, and the application (or "
+"JDBC driver) can later bind to and use it. Since JNDI only allows the "
+"application to see the (XA)DataSource as an instance of the interface (for "
+"example, <property>javax.sql.XADataSource</property>) rather than as an "
+"instance of the implementation class (for example, <property>com.mydb."
+"myXADataSource</property>), the application is not tied at build time to "
+"only use a specific (XA)DataSource implementation."
+msgstr ""
+"Um es einem JDBC-Treiber zu ermöglichen, beliebige DataSources zu nutzen, "
+"ohne spezifische Details ihrer Implementierungen kennen zu müssen, werden "
+"DataSources in der Regel von JNDI bezogen. Eine spezifische (XA)DataSource "
+"kann erstellt und registriert werden bei einer passenden JNDI-"
+"Implementierung, und die Anwendung (oder der JDBC-Treiber) kann später an "
+"sie anbinden und sie nutzen. Da JNDI der Anwendung nur erlaubt, die (XA)"
+"DataSource als eine Instanz der Schnittstelle zu betrachten (z. B. "
+"<property>javax.sql.XADataSource</property>), statt als Instanz der "
+"Implementierungsklasse (z. B. <property>com.mydb.myXADataSource</property>), "
+"wird die Anwendung während der Build Time nicht daran gebunden, nur eine "
+"bestimmte (XA)DataSource Implementierung zu verwenden."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:145
+#, no-c-format
+msgid ""
+"To get the <classname>TransactionalDriver</classname> class to use a JNDI "
+"registered <code>XADataSource</code> it is first necessary to create the "
+"<code>XADataSource</code> instance and store it in an appropriate JNDI "
+"implementation. Details of how to do this can be found in the JDBC 2.0 "
+"tutorial available at JavaSoft. An example is show below:"
+msgstr ""
+"Damit die <classname>TransactionalDriver</classname>-Klasse eine JNDI-"
+"registrierte <code>XADataSource</code> verwendet, ist es zunächst nötig, die "
+"<code>XADataSource</code>-Instanz zu erstellen und in einer passenden JNDI-"
+"Implementierung zu speichern. Details zur Durchführung finden Sie im JDBC "
+"2.0 Tutorial, erhältlich bei JavaSoft. Ein Beispiel wird unten gezeigt:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:148
+#, no-c-format
+msgid ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+msgstr ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:149
+#, no-c-format
+msgid ""
+"Where the <property>Context.INITIAL_CONTEXT_FACTORY</property> property is "
+"the JNDI way of specifying the type of JNDI implementation to use."
+msgstr ""
+"Hierbei ist die <property>Context.INITIAL_CONTEXT_FACTORY</property>-"
+"Eigenschaft die Art, auf die JNDI den zu benutzenden Implementierungstyp "
+"spezifiziert."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:152
+#, no-c-format
+msgid ""
+"Then the application must pass an appropriate connection URL to the JDBC 2.0 "
+"driver:"
+msgstr ""
+"Anschließend muss die Anwendung eine passende Verbindungs-URL an den JDBC "
+"2.0 Treiber weitergeben:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:155
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:156
+#, no-c-format
+msgid ""
+"The JNDI URL must be pre-pended with jdbc:arjuna: in order for the "
+"<code>ArjunaJDBC2Driver</code> to recognise that the DataSource must "
+"participate within transactions and be driven accordingly."
+msgstr ""
+"Die JNDI-URL muss vorangestellt werden mit jdbc:arjuna:, damit der "
+"<code>ArjunaJDBC2Driver</code> erkennt, dass die DataSource an Transaktionen "
+"teilnehmen und entsprechend gesteuert werden muss."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:160
+#, no-c-format
+msgid "Dynamic class instantiation"
+msgstr "Dynamische Klasseninstanzierung"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:161
+#, no-c-format
+msgid ""
+"Many JDBC 2.0 implementations provide proprietary implementations of "
+"<interfacename>XADataSources</interfacename> that provide non-standard "
+"extensions to the specification. In order to allow the application to remain "
+"isolated from the actual JDBC 2.0 implementation it is using and yet "
+"continue to be able to use these extensions, JBossJTA hides the details of "
+"these proprietary implementations using dynamic class instantiation. In "
+"addition, the use of JNDI is not required when using this mechanism because "
+"the actual implementation of the <interfacename>XADataSource</interfacename> "
+"will be directly instantiated, albeit in a manner which will not tie an "
+"application or driver to a specific implementation. JBossJTA therefore has "
+"several classes which are for specific JDBC 2.0 implementations, and these "
+"can be selected at runtime by the application setting the "
+"<property>dynamicClass</property> property appropriately:"
+msgstr ""
+"Viele JDBC 2.0 Implementierungen stellen proprietäre Implementierungen von "
+"<interfacename>XADataSources</interfacename> bereit, die nicht "
+"standardgerechte Erweiterungen zu den Spezifikationen liefern. Um der "
+"Anwendung zu erlauben, isoliert von der eigentlichen JDBC 2.0 "
+"Implementierung zu bleiben und dennoch diese Erweiterungen weiterhin nutzen "
+"zu können, verbirgt JBossJTA die Details dieser proprietären "
+"Implementierungen mittels dynamischer Klasseninstanzierung. Zudem ist die "
+"Verwendung von JNDI nicht nötig, wenn dieses Verfahren benutzt wird, da die "
+"eigentliche Implementierung von <interfacename>XADataSource</interfacename> "
+"direkt instanziert wird, obgleich dies in einer Weise geschieht, die eine "
+"Anwendung oder einen Treiber nicht an eine spezifische Implementierung "
+"bindet. JBossJTA besitzt daher mehrere Klassen für spezifische JDBC 2.0 "
+"Implementierungen, die während der Laufzeit ausgewählt werden können, indem "
+"durch die Anwendung die <property>dynamicClass</property>-Eigenschaft "
+"entsprechend einstellt wird:"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:166
+#, no-c-format
+msgid "Dynamic Class property values for specific databases"
+msgstr "Dynamische Klasseneigenschaftswerte für spezifische Datenbanken"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:170
+#, no-c-format
+msgid "Database Type"
+msgstr "Datenbanktyp"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:173
+#, no-c-format
+msgid "Property Name"
+msgstr "Eigenschaftsname"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:180
+#, no-c-format
+msgid "Cloudscape 3.6"
+msgstr "Cloudscape 3.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr "Sequelink 5.1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr "Oracle 8.1.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:207
+#, no-c-format
+msgid ""
+"As mentioned earlier, JBossTS no longer supports Cloudscape or Sequelink as "
+"part of the qualified drivers. Furthermore, we recommend using JNDI to "
+"obtain JDBC classes rather than the direct method described here."
+msgstr ""
+"Wie schon erwähnt, unterstützt JBossTS Cloudscape oder Sequelink nicht mehr "
+"als qualifizierte Treiber. Zudem empfehlen wir die Nutzung von JNDI zum "
+"Beziehen von JDBC-Klassen anstelle des hier beschriebenen, direkten "
+"Verfahrens."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:211
+#, no-c-format
+msgid ""
+"The application code must specify which dynamic class the "
+"<code>TransactionalDriver</code> should instantiate when setting up the "
+"connection:"
+msgstr ""
+"Der Anwendungs-Code muss spezifizieren, welche dynamische Klasse der "
+"<code>TransactionalDriver</code> beim Erstellen der Verbindung initiieren "
+"soll:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:214
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:216
+#, no-c-format
+msgid "Using the connection"
+msgstr "Benutzen der Verbindung"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:217
+#, no-c-format
+msgid ""
+"Once the connection has been established (for example, using the "
+"<methodname>java.sql.DriverManager.getConnection</methodname> method), all "
+"operations on the connection will be monitored by JBossJTA. Note, it is not "
+"necessary to use the transactional connection within transactions. If a "
+"transaction is not present when the connection is used, then operations will "
+"be performed directly on the database."
+msgstr ""
+"Sobald die Verbindung hergestellt ist (z. B. durch die <methodname>java.sql."
+"DriverManager.getConnection</methodname>-Methode), werden alle Operationen "
+"auf der Verbindung durch JBossJTA überwacht. Beachten Sie, dass es nicht "
+"notwendig ist, die transaktionale Verbindung innerhalb von Transaktionen zu "
+"verwenden. Wenn keine Transaktion vorliegt beim Verwenden der Verbindung, "
+"werden Operationen direkt auf der Datenbank durchgeführt."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr "JDBC unterstützt keine untergeordneten Transaktionen."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:226
+#, no-c-format
+msgid ""
+"Transaction timeouts can be used to automatically terminate transactions "
+"should the connection not be terminated within an appropriate period."
+msgstr ""
+"Timeouts von Transaktionen können benutzt werden, um Transaktionen "
+"automatisch zu beenden, sollte die Verbindung nicht innerhalb einer "
+"angemessenen Zeitspanne terminiert werden."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:229
+#, no-c-format
+msgid ""
+"JBossJTA connections can be used within multiple different transactions "
+"simultaneously, for instance, different threads, with different notions of "
+"the current transaction, may use the same JDBC connection. JBossJTA does "
+"connection pooling for each transaction within the JDBC connection. So, "
+"although multiple threads may use the same instance of the JDBC connection, "
+"internally this may be using a different connection instance per "
+"transaction. With the exception of close, all operations performed on the "
+"connection at the application level will only be performed on this "
+"transaction-specific connection."
+msgstr ""
+"JBossJTA-Verbindungen können innerhalb mehrerer verschiedener Transaktionen "
+"gleichzeitig verwendet werden, z. B. können verschiedene Threads mit "
+"verschiedenen Begriffen von der aktuellen Transaktion dieselbe JDBC-"
+"Verbindung nutzen. JBossJTA führt Verbindungs-Pooling aus für jede "
+"Transaktion innerhalb der JDBC-Verbindung. Obwohl also ggf. mehrere Threads "
+"dieselbe Instanz der JDBC-Verbindung verwenden, kann diese intern "
+"unterschiedliche Verbindungsinstanzen für jede Transaktion verwenden. Mit "
+"Ausnahme von \"close\" werden alle Operationen, die auf der Verbindung auf "
+"Anwendungsebene duchgeführt werden, ausschließlich auf dieser "
+"transaktionsspezifischen Verbindung ausgeführt."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:232
+#, no-c-format
+msgid ""
+"JBossJTA will automatically register the JDBC driver connection with the "
+"transaction via an appropriate resource . When the transaction terminates, "
+"this resource will be responsible for either committing or rolling back any "
+"changes made to the underlying database via appropriate calls on the JDBC "
+"driver."
+msgstr ""
+"JBossJTA wird die JDBC-Treiberverbindung automatisch bei der Transaktion "
+"registrieren mittels einer passenden Ressource. Wenn die Transaktion endet, "
+"ist diese Ressource verantwortlich für das Festschreiben oder Zurücksetzen "
+"jeglicher Änderungen an der zugrunde liegenden Datenbank, mittels "
+"entsprechender Aufrufe an den JDBC-Treiber."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:235
+#, no-c-format
+msgid ""
+"Once created, the driver and any connection can be used in the same way as "
+"any other JDBC driver or connection."
+msgstr ""
+"Einmal erstellt, kann der Treiber und alle Verbindungen in gleicher Weise "
+"benutzt werden, wie jede(r) andere(r) JDBC-Treiber oder -Verbindung auch."
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:238
+#, no-c-format
+msgid ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+msgstr ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:240
+#, no-c-format
+msgid "Connection pooling"
+msgstr "Verbindungs-Pooling"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:241
+#, no-c-format
+msgid ""
+"For each user name and password, JBossJTA will maintain a single instance of "
+"each connection for as long as that connection is in use. Subsequent "
+"requests for the same connection will get a reference to the originally "
+"created connection, rather than a new instance. Attempts to close the "
+"connection are allowed, but the connection will only actually be closed when "
+"all users (including transactions) have either finished with the connection, "
+"or issued close calls."
+msgstr ""
+"Für jeden Benutzernamen und Passwort bewahrt JBossJTA eine einzelne Instanz "
+"jeder Verbindung, solange diese Verbindung benutzt wird. Nachfolgende "
+"Anfragen für dieselbe Verbindung bekommen statt einer neuen Instanz vielmehr "
+"eine Referenz auf die ursprünglich erstellte Verbindung. Versuche, die "
+"Verbindung zu schließen, sind zwar erlaubt. Doch wird die Verbindung nur "
+"dann tatsächlich geschlossen, wenn alle Benutzer (inklusive Transaktionen) "
+"entweder die Verbindung nicht mehr benötigen, oder Aufrufe zum Schließen "
+"ausgegeben haben."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:246
+#, no-c-format
+msgid "Reusing connections"
+msgstr "Verbindungen wiederverwenden"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:247
+#, no-c-format
+msgid ""
+"Some JDBC drivers allow the reuse of a connection for multiple different "
+"transactions once a given transaction has completed. Unfortunately this is "
+"not a common feature, and other drivers require a new connection to be "
+"obtained for each new transaction. By default, the JBossJTA transactional "
+"driver will always obtain a new connection for each new transaction. "
+"However, if an existing connection is available and is currently unused, it "
+"is possible to make JBossJTA reuse this connection. In order to do this, the "
+"reuseconnection=true option must be specified on the JDBC URL. For example:"
+msgstr ""
+"Manche JDBC-Treiber erlauben die Wiederverwendung einer Verbindung für "
+"mehrere verschiedene Transaktionen, sobald die jeweilige Transaktion "
+"abgeschlossen wurde. Leider ist dies kein verbreitetes Feature, und andere "
+"Treiber benötigen den Erhalt einer neuen Verbindung für jede neue "
+"Transaktion. Standardmäßig bezieht der JBossJTA transaktionale Treiber für "
+"jede neue Transaktion eine neue Verbindung. Falls jedoch eine bestehende "
+"Verbindung verfügbar und zur Zeit unbenutzt ist, kann JBossJTA diese "
+"Verbindung wiederverwenden, falls gewünscht. Dafür muss die Option "
+"\"reuseconnection=true\" spezifiziert werden in der JDBC-URL. Zum Beispiel:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+"jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:253
+#, no-c-format
+msgid "Terminating the transaction"
+msgstr "Beenden der Transaktion"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:254
+#, no-c-format
+msgid ""
+"Whenever a transaction terminates (either explicitly by the application "
+"programmer, or implicitly when any associated transaction timeout expires) "
+"that has a JDBC connection registered with it, JBossJTA will drive the "
+"database (via the JDBC driver) to either commit or roll back any changes "
+"made to it. This happens transparently to the application."
+msgstr ""
+"Wenn eine Transaktion beendet wird (entweder explizit durch den "
+"Anwendungsprogrammierer, oder implizit wenn ein assoziierter Transaktions-"
+"Timeout abläuft), bei der eine JDBC-Verbindung registriert ist, wird "
+"JBossJTA die Datenbank dazu bringen (via JDBC-Treiber), jegliche an ihr "
+"durchgeführte Änderungen festzuschreiben oder zurückzusetzen. Dies erfolgt "
+"transparent für die Anwendung."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr "AutoCommit"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:260
+#, no-c-format
+msgid ""
+"If <code>AutoCommit</code> of the <code>java.sql.Connection</code> is set to "
+"true for JDBC 1.0 then the execution of every SQL statement is a separate "
+"top-level transaction, and grouping multiple statements to be managed within "
+"a single OTS transaction is not possible. Therefore, JBossJTA will disable "
+"<code>AutoCommit</code> on JDBC 1.0 connections before they can be used. If "
+"auto commit is subsequently set to true by the application, JBossJTA will "
+"raise the <code>java.sql.SQLException</code>."
+msgstr ""
+"Wenn <code>AutoCommit</code> der <code>java.sql.Connection</code> auf \"true"
+"\" gesetzt ist für JDBC 1.0, ist die Ausführung jeder SQL-Anweisung eine "
+"separate Transaktion oberster Ebene, und das Gruppieren mehrerer Anweisungen "
+"zum Steuern innerhalb einer einzigen OTS-Transaktion ist nicht möglich. "
+"Deshalb deaktiviert JBossJTA <code>AutoCommit</code> auf JDBC 1.0 "
+"Verbindungen, bevor diese eingesetzt werden können. Falls \"auto commit\" "
+"nachträglich durch die Anwendung auf \"true\" gesetzt wird, gibt JBossJTA "
+"die <code>java.sql.SQLException</code> aus."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:265
+#, no-c-format
+msgid "Setting isolation levels"
+msgstr "Isolationsebenen einstellen"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:266
+#, no-c-format
+msgid ""
+"When using the JBossJTA JDBC driver, it may be necessary to set the "
+"underlying transaction isolation level on the XA connection. By default, "
+"this is set to <code>TRANSACTION_SERIALIZABLE</code>, but you may want to "
+"set this to something more appropriate for your application. In order to do "
+"this, set the <property>com.arjuna.ats.jdbc.isolationLevel</property> "
+"property to the appropriate isolation level in string form, for example, "
+"<code>TRANSACTION_READ_COMMITTED</code>, or "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+msgstr ""
+"Beim Verwenden des JBossJTA JDBC-Treibers kann es nötig sein, die zugrunde "
+"liegende Isolationsebene der Transaktion auf der XA-Verbindung einzustellen. "
+"Standardmäßig ist sie auf <code>TRANSACTION_SERIALIZABLE</code> eingestellt, "
+"aber ggf. möchten Sie diese Einstellung ändern, um Ihrer Anwendung eher "
+"gerecht zu werden. Dazu setzen Sie die <property>com.arjuna.ats.jdbc."
+"isolationLevel</property>-Eigenschaft auf die gewünschte Isolationsebene in "
+"Stringform, z. B. <code>TRANSACTION_READ_COMMITTED</code>, oder "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:271
+#, no-c-format
+msgid ""
+"At present this property applies to all XA connections created in the JVM."
+msgstr ""
+"Derzeit wird diese Eigenschaft auf alle in JVM erstellte XA-Verbindungen "
+"angewendet."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Preface.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Preface.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,23 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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 "Vorwort"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Revision_History.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Revision_History.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,29 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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 "Revisionsgeschichte"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/The_Resource_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/The_Resource_Manager.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/The_Resource_Manager.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,970 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#: The_Resource_Manager.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "Test"
+
+#. Tag: para
+#: The_Resource_Manager.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "Dies ist ein Testabsatz"
+
+#. Tag: title
+#: The_Resource_Manager.xml:11
+#, no-c-format
+msgid "The XAResource Interface"
+msgstr "Die XAResouce-Schnittstelle"
+
+#. Tag: para
+#: The_Resource_Manager.xml:12
+#, no-c-format
+msgid ""
+"Whereas some transaction specifications and systems define a generic "
+"resource which can be used to register arbitrary resources with a "
+"transaction, the JTA is much more XA specific. The <interfacename>javax."
+"transaction.xa.XAResource</interfacename> interface is a Java mapping of the "
+"<interfacename>XA</interfacename> interface. The <interfacename>XAResource</"
+"interfacename> interface defines the contract between a Resource Manager and "
+"a Transaction Manager in a distributed transaction processing environment. A "
+"resource adapter for a resource manager implements the "
+"<interfacename>XAResource</interfacename> interface to support association "
+"of a top-level transaction to a resource such as a relational database."
+msgstr ""
+"Während manche Transaktionsspezifikationen und -systeme eine generische "
+"Ressource definieren, die benutzt werden kann, um beliebige Ressourcen bei "
+"der Transaktion zu registrieren, ist JTA dagegen sehr viel XA-spezifischer. "
+"Die <interfacename>javax.transaction.xa.XAResource</interfacename>-"
+"Schnittstelle ist ein Java-Mapping der <interfacename>XA</interfacename>-"
+"Schnittstelle. Die <interfacename>XAResource</interfacename>-Schnittstelle "
+"definiert den Kontrakt zwischen einem Ressourcenmanager und einem "
+"Transaktionsmanager in einer Umgebung zum Verarbeiten von verteilten "
+"Transaktionen. Ein Ressourcenadapter für einen Ressourcenmanager "
+"implementiert die <interfacename>XAResource</interfacename>-Schnittstelle, "
+"um die Assoziation einer Transaktion oberster Ebene mit einer Ressource wie "
+"einer relationalen Datenbank zu unterstützen."
+
+#. Tag: para
+#: The_Resource_Manager.xml:15
+#, no-c-format
+msgid ""
+"The <interfacename>XAResource</interfacename> interface can be supported by "
+"any transactional resource adapter that is intended to be used in an "
+"environment where transactions are controlled by an external transaction "
+"manager, for example, a database management system. An application may "
+"access data through multiple database connections. Each database connection "
+"is associated with an <code>XAResource</code> object that serves as a proxy "
+"object to the underlying resource manager instance. The transaction manager "
+"obtains an <code>XAResource</code> for each resource manager participating "
+"in a top-level transaction. It uses the start method to associate the "
+"transaction with the resource, and it uses the end method to disassociate "
+"the transaction from the resource."
+msgstr ""
+"Die <interfacename>XAResource</interfacename>-Schnittstelle kann von jedem "
+"transaktionalen Ressourcenadapter unterstützt werden, der dafür ausgelegt "
+"ist, in einer Umgebung verwendet zu werden, in der Transaktionen von einem "
+"externen Transaktionsmanager kontrolliert werden, z. B. einem "
+"Datenbankmanagementsystem. Eine Anwendung kann auf Daten über verschiedene "
+"Datenbankverbindungen zugreifen. Jede Datenbankverbindung ist mit einem "
+"<code>XAResource</code>-Objekt assoziiert, das als Proxy-Objekt fungiert für "
+"die zugrunde liegende Ressourcenmanagerinstanz. Der Transaktionsmanager "
+"erhält eine <code>XAResource</code> für jeden Ressourcenmanager, der an "
+"einer Transaktion oberster Ebene teilnimmt. Er verwendet die \"start\"-"
+"Methode, um die Transaktion mit der Ressource zu assoziieren, und die \"end"
+"\"-Methode, um die Transaktion von der Ressource zu disassoziieren."
+
+#. Tag: para
+#: The_Resource_Manager.xml:18
+#, no-c-format
+msgid ""
+"The resource manager is responsible for associating the transaction with all "
+"work performed on its data between the start and end invocations. At "
+"transaction commit time, these transactional resource managers are informed "
+"by the transaction manager to prepare, commit, or rollback the transaction "
+"according to the two-phase commit protocol."
+msgstr ""
+"Es obliegt dem Ressourcenmanager, die Transaktion mit jeglicher Arbeit zu "
+"assoziieren, die zwischen Start- und End-Aufruf an den Daten ausgeführt "
+"wurde. Zum Zeitpunkt der Transaktionsfestschreibung werden diese "
+"transaktionalen Ressourcenmanager vom Transaktionsmanager dazu aufgefordert, "
+"sich vorzubereiten und die Transaktion festzuschreiben bzw. zurückzusetzen "
+"entsprechend des zwei-Phasen Festschreibungsprotokolls."
+
+#. Tag: para
+#: The_Resource_Manager.xml:21
+#, no-c-format
+msgid ""
+"In order to be better integrated with Java, the <interfacename>XAResource</"
+"interfacename> differs from the standard <interfacename>XA</interfacename> "
+"interface in the following ways:"
+msgstr ""
+"Um besser integriert zu sein mit Java, unterscheidet sich die "
+"<interfacename>XAResource</interfacename> von der Standard-"
+"<interfacename>XA</interfacename>-Schnittstelle wie folgt:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:26
+#, no-c-format
+msgid ""
+"The resource manager initialization is done implicitly by the resource "
+"adapter when the resource (connection) is acquired. There is no "
+"<code>xa_open</code> equivalent."
+msgstr ""
+"Die Initialisierung des Ressourcenmanagers wird implizit durch den "
+"Ressourcenadapter durchgeführt, wenn die Ressource (Verbindung) bezogen "
+"wird. Es existiert kein Äquivalent zu <code>xa_open</code>."
+
+#. Tag: para
+#: The_Resource_Manager.xml:31
+#, no-c-format
+msgid ""
+"<code>Rmid</code> is not passed as an argument. Each <code>Rmid</code> is "
+"represented by a separate <code>XAResource</code> object."
+msgstr ""
+"<code>Rmid</code> wird nicht als Argument übergeben. Jede <code>Rmid</code> "
+"wird durch ein separates <code>XAResource</code>-Objekt repräsentiert."
+
+#. Tag: para
+#: The_Resource_Manager.xml:36
+#, no-c-format
+msgid ""
+"Asynchronous operations are not supported because Java supports multi-"
+"threaded processing and most databases do not support asynchronous "
+"operations."
+msgstr ""
+"Asynchrone Operationen werden nicht unterstützt, denn Java unterstützt Multi-"
+"Thread-Prozesse, und die meisten Datenbanken unterstützen asynchrone "
+"Operationen nicht."
+
+#. Tag: para
+#: The_Resource_Manager.xml:41
+#, no-c-format
+msgid ""
+"Error return values that are caused by the transaction manager’s improper "
+"handling of the <code>XAResource</code> object are mapped to Java exceptions "
+"via the <classname>XAException</classname> class."
+msgstr ""
+"Fehlerausgabewerte, die verursacht werden durch die unsachgemäße Handhabung "
+"des <code>XAResource</code>-Objekts durch den Transaktionsmanager, werden "
+"Java-Ausnahmen zugewiesen durch die <classname>XAException</classname>-"
+"Klasse."
+
+#. Tag: para
+#: The_Resource_Manager.xml:46
+#, no-c-format
+msgid ""
+"The DTP concept of <emphasis>Thread of Control</emphasis> maps to all Java "
+"threads that are given access to the <code>XAResource</code> and "
+"<code>Connection</code> objects. For example, it is legal for two different "
+"threads to perform the start and end operations on the same "
+"<code>XAResource</code> object."
+msgstr ""
+"Das DTP-Konzept der <emphasis>Kontroll-Threads</emphasis> ist allen Java-"
+"Threads zugewiesen, die Zugriff auf <code>XAResource</code>- und "
+"<code>Connection</code>-Objekte haben. Zum Beispiel ist es zulässig, dass "
+"zwei verschiedene Threads die Start- und End-Operationen auf demselben "
+"<code>XAResource</code>-Objekt ausführen."
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr "Erweiterte XAResource-Kontrolle"
+
+#. Tag: para
+#: The_Resource_Manager.xml:53
+#, no-c-format
+msgid ""
+"By default, whenever an <code>XAResource</code> object is registered with a "
+"JTA compliant transaction service, you have no control over the order in "
+"which it will be invoked during the two-phase commit protocol, with respect "
+"to other <code>XAResource</code> objects. In JBossTS, however, there is "
+"support for controlling the order via the two interfaces <interfacename>com."
+"arjuna.ats.jta.resources.StartXAResource</interfacename> and "
+"<interfacename>com.arjuna.ats.jta.resources.EndXAResource</interfacename>. "
+"By inheriting your <code>XAResource</code> instance from either of these "
+"interfaces, you control whether an instance of your class will be invoked "
+"first or last, respectively."
+msgstr ""
+"Wann immer ein <code>XAResource</code>-Objekt bei einem JTA-konformen "
+"Transaktionsdienst registriert wird, haben Sie standardmäßig keine Kontrolle "
+"über die Reihenfolge, in der es während des zwei-Phasen "
+"Festschreibungsprotokolls im Vergleich zu anderen <code>XAResource</code>-"
+"Objekten aufgerufen wird. In JBossTS dagegen existiert Unterstützung zur "
+"Kontrolle der Reihenfolge mittels der zwei Schnittstellen <interfacename>com."
+"arjuna.ats.jta.resources.StartXAResource</interfacename> und "
+"<interfacename>com.arjuna.ats.jta.resources.EndXAResource</interfacename>. "
+"Durch Erben Ihrer <code>XAResource</code>-Instanz von einer dieser "
+"Schnittstellen kontrollieren Sie, ob eine Instanz Ihrer Klasse zuerst bzw. "
+"zuletzt aufgerufen wird."
+
+#. Tag: para
+#: The_Resource_Manager.xml:58
+#, no-c-format
+msgid ""
+"Only one instance of each interface type may be registered with a specific "
+"transaction."
+msgstr ""
+"Nur eine Instanz je Schnittstellentyp kann bei einer spezifischen "
+"Transaktion registriert werden."
+
+#. Tag: para
+#: The_Resource_Manager.xml:62
+#, no-c-format
+msgid ""
+"In the TxCore manual we discussed the Last Resource Commit optimization "
+"(LRCO), whereby a single resource that is only one-phase aware (does not "
+"support prepare), can be enlisted with a transaction that is manipulating "
+"two-phase aware participants. This optimization is also supported within the "
+"JTA aspects of JBossTS."
+msgstr ""
+"Im TxCore-Handbuch erläuterten wir die \"Last Resource Commit\" Optimierung "
+"(LRCO), wonach eine einzelne Ressource, die nur ein-Phasen-sicher ist "
+"(unterstützt die Vorbereitungsphase nicht), bei einer Transaktion "
+"eingetragen werden kann, die zwei-Phasen-sichere Teilnehmer beeinflusst. "
+"Diese Optimierung wird auch in den JTA-Aspekten von JBossTS unterstützt."
+
+#. Tag: para
+#: The_Resource_Manager.xml:65
+#, no-c-format
+msgid ""
+"In order to use the LRCO, your <interfacename>XAResource</interfacename> "
+"implementation must extend the <interfacename>com.arjuna.ats.jta.resources."
+"LastResourceCommitOptimisation</interfacename> marker interface (it provides "
+"no methods). When enlisting the resource via Transaction.enlistResource, "
+"JBossTS will ensure that only a single instance of this type of participant "
+"is used within each transaction. Your resource will be driven last in the "
+"commit protocol: no invocation of prepare will occur."
+msgstr ""
+"Um die LRCO zu verwenden, muss Ihre <interfacename>XAResource</"
+"interfacename>-Implementierung die <interfacename>com.arjuna.ats.jta."
+"resources.LastResourceCommitOptimisation</interfacename>-Markerschnittstelle "
+"(sie liefert keine Methoden) erweitern. Beim Eintragen der Ressource via "
+"Transaction.enlistResource stellt JBossTS sicher, dass nur eine einzige "
+"Instanz dieses Teilnehmertyps in jeder Transaktion vergewendet wird. Ihre "
+"Ressource wird als letztes im Festschreibungsprotokoll berücksichtigt "
+"werden: Ein \"prepare\"-Aufruf wird nicht erfolgen."
+
+#. Tag: para
+#: The_Resource_Manager.xml:69
+#, no-c-format
+msgid ""
+"By default an attempt to enlist more than one instance of a "
+"<classname>LastResourceCommitOptimisation</classname> class will fail and "
+"false will be returned from <methodname>Transaction.enlistResource</"
+"methodname>. This behaviour can be overridden by setting the <property>com."
+"arjuna.ats.jta.allowMultipleLastResources</property> to true. However, "
+"before doing so you should read the Section on enlisting multiple one-phase "
+"aware resources."
+msgstr ""
+"Der Versuch, mehr als eine Instanz einer "
+"<classname>LastResourceCommitOptimisation</classname>-Klasse einzutragen, "
+"wird standardmäßig scheitern, und von <methodname>Transaction."
+"enlistResource</methodname> wird \"false\" zurückgegeben. Diese "
+"Verhaltensweise kann außer Kraft gesetzt werden, indem <property>com.arjuna."
+"ats.jta.allowMultipleLastResources</property> auf \"true\" gesetzt wird. "
+"Bevor Sie dies jedoch tun, sollten Sie den Abschnitt über das Eintragen "
+"mehrerer ein-Phasen-sicherer Ressourcen lesen."
+
+#. Tag: para
+#: The_Resource_Manager.xml:73
+#, no-c-format
+msgid ""
+"In order to utilize the LRCO in a distributed environment, it is necessary "
+"to disable interposition support. It is still possible to use implicit "
+"context propagation."
+msgstr ""
+"Um die LRCO in einer verteilten Umgebung anzuwenden, ist es notwendig, die "
+"Unterstützung für Interposition zu deaktivieren. Es ist weiterhin möglich, "
+"implizite Kontextfortpflanzung zu verwenden."
+
+#. Tag: title
+#: The_Resource_Manager.xml:77
+#, no-c-format
+msgid "Enlisting multiple one-phase aware resources"
+msgstr "Eintragen mehrerer ein-Phasen-sicherer Ressourcen"
+
+#. Tag: para
+#: The_Resource_Manager.xml:78
+#, no-c-format
+msgid ""
+"As discussed in the Transaction Core documentation, in order to guarantee "
+"consistency (atomicity) of outcome between multiple participants (resources) "
+"within the same transaction, the two-phase commit protocol is used with a "
+"durable transaction log. In the case of possessing a single one-phase aware "
+"resource, it is still possible to achieve an atomic (all of nothing) outcome "
+"across resources by utilizing the Last Resource Commit Optimization, as "
+"explained earlier."
+msgstr ""
+"Wie in der Transaction-Core-Dokumentation erläutert, wird das zwei-Phasen "
+"Festschreibungsprotokoll mit einem dauerhaften Transaktionsprotokoll "
+"verwendet, um die Ergebniskonsistenz (Atomarität) zwischen mehreren "
+"Teilnehmern (Ressourcen) innerhalb derselben Transaktion zu garantieren. "
+"Falls eine einzelne ein-Phasen-sichere Ressource vorhanden ist, ist es immer "
+"noch möglich, ein atomisches (alles oder nichts) Ergebnis über mehrere "
+"Ressourcen hinweg zu erreichen, indem die Last-Resource-Commit-Optimierung "
+"angewendet wird, wie bereits erläutert."
+
+#. Tag: para
+#: The_Resource_Manager.xml:82
+#, no-c-format
+msgid ""
+"However, there may be situations where multiple one-phase aware resources "
+"are enlisted within the same transaction. For example, a legacy database "
+"running within the same transaction as a legacy JMS implementation. In these "
+"situations it is not possible to achieve atomicity of transaction outcome "
+"across multiple resources because none of them enter the prepare (waiting "
+"for final outcome) state: they commit or rollback immediately when "
+"instructed by the transaction coordinator, without knowledge of other "
+"resource states and without any way of undoing should subsequent resources "
+"make a different choice. This can result in data corruption or heuristic "
+"outcomes."
+msgstr ""
+"Es können jedoch Situationen auftreten, in denen mehrere ein-Phasen-sichere "
+"Ressourcen in derselben Transaktion eingetragen sind. Zum Beispiel eine "
+"veraltete Datenbank, die in derselben Transaktion läuft wie eine veraltete "
+"JMS-Implementierung. In diesen Situtationen ist es nicht möglich, Atomarität "
+"des Transaktionsergebnisses über mehrere Ressourcen hinweg zu erreichen, "
+"weil keine von ihnen in den Vorbereitungsstatus (warten auf das Endergebnis) "
+"eintritt: Sie schreiben sofort fest oder setzen sofort zurück, wenn sie vom "
+"Transaktionskoordinator aufgefordert werden, ohne Kenntnis über Zustände "
+"anderer Ressourcen, und ohne jegliche Möglichkeit zum Zurücksetzen, sollten "
+"nachfolgende Ressourcen eine andere Wahl treffen. Korrumpierte Daten oder "
+"heuristische Ergebnisse können die Folge sein."
+
+#. Tag: para
+#: The_Resource_Manager.xml:85
+#, no-c-format
+msgid "In these situations we recommend one of the following approaches:"
+msgstr ""
+"In diesen Situationen empfehlen wir eine der folgenden Herangehensweisen:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:90
+#, no-c-format
+msgid ""
+"Wrap the resources in compensating transactions. See the Web Services "
+"transactions guides for further details."
+msgstr ""
+"Ummanteln der Ressourcen in kompensierende Transaktionen. Einzelheiten "
+"hierzu finden Sie im Web Services Transaktionen Handbuch."
+
+#. Tag: para
+#: The_Resource_Manager.xml:95
+#, no-c-format
+msgid "Migrate the legacy implementations to two-phase aware equivalents."
+msgstr ""
+"Migrieren der veralteten Implementierungen auf zwei-Phasen-sichere "
+"Äquivalente."
+
+#. Tag: para
+#: The_Resource_Manager.xml:100
+#, no-c-format
+msgid ""
+"In the cases where neither of these options are viable, JBossTS does support "
+"the enlistment of multiple one-phase aware resources within the same "
+"transaction. In order to do this, see the section on the Last Resource "
+"Commit Optimization."
+msgstr ""
+"Für Fälle, in denen keine dieser Möglichkeiten gangbar ist, unterstützt "
+"JBossTS das Eintragen mehrerer ein-Phasen-sicherer Ressourcen in derselben "
+"Transaktion. Lesen Sie bitte den Abschnitt über die Last-Resource-Commit-"
+"Optimierung für Informationen zur Durchführung."
+
+#. Tag: para
+#: The_Resource_Manager.xml:104
+#, no-c-format
+msgid ""
+"Even when this support is enabled, JBossTS will issue warnings when it "
+"detects that the option has been enabled (\"You have chosen to enable "
+"multiple last resources in the transaction manager. This is transactionally "
+"unsafe and should not be relied upon.”) and when multiple one-phase "
+"resources are enlisted within the transaction (“This is transactionally "
+"unsafe and should not be relied on.”)."
+msgstr ""
+"Selbst wenn diese Unterstützung aktiviert ist, wird JBossTS Warnungen "
+"ausgeben, sobald es entdeckt, dass diese Option aktiviert wurde (\"Sie haben "
+"multiple letzte Ressourcen im Transaktionsmanager aktiviert. Dies ist "
+"transaktional unsicher und u. U. nicht verlässlich\"), und sobald mehrere "
+"ein-Phasen-sichere Ressourcen in der Transaktion eingetragen werden (\"Dies "
+"ist transaktional unsicher und u. U. nicht verlässlich\")."
+
+#. Tag: title
+#: The_Resource_Manager.xml:111
+#, no-c-format
+msgid "Opening a Resource Manager"
+msgstr "Öffnen eines Ressourcenmanagers"
+
+#. Tag: para
+#: The_Resource_Manager.xml:112
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface requires that the "
+"transaction manager initialize a resource manager (xa_open) prior to any "
+"other xa_ calls. JTA requires initialization of a resource manager to be "
+"embedded within the resource adapter that represents the resource manager. "
+"The transaction manager does not need to know how to initialize a resource "
+"manager; it is only responsible for informing the resource manager about "
+"when to start and end work associated with a transaction and when to "
+"complete the transaction. The resource adapter is responsible for opening "
+"(initializing) the resource manager when the connection to the resource "
+"manager is established."
+msgstr ""
+"Die X/Open <interfacename>XA</interfacename>-Schnittstelle erfordert vom "
+"Transaktionsmanager die Initialisierung eines Ressourcenmanagers (xa_open) "
+"vor allen anderen xa_-Aufrufen. JTA erfordert, dass die Initialisierung "
+"eines Ressourcenmanagers eingebettet ist im Ressourcenadapter, der den "
+"Ressourcenmanager repräsentiert. Der Transaktionsmanager braucht nicht zu "
+"wissen, wie ein Ressourcenmanager initialisiert wird; er ist nur zuständig "
+"dafür, den Ressourcenmanager darüber zu informieren, wann die Arbeit an "
+"einer assoziierten Transaktion zu starten oder zu beenden ist, und wann die "
+"Transaktion abzuschließen ist. Der Ressourcenadapter ist verantwortlich für "
+"das Öffnen (Initialisieren) des Ressourcenmanagers, wenn die Verbindung zum "
+"Ressourcenmanager hergestellt wurde."
+
+#. Tag: title
+#: The_Resource_Manager.xml:118
+#, no-c-format
+msgid "Closing a Resource Manager"
+msgstr "Schließen eines Ressourcenmanagers"
+
+#. Tag: para
+#: The_Resource_Manager.xml:119
+#, no-c-format
+msgid ""
+"A resource manager is closed by the resource adapter as a result of "
+"destroying the transactional resource. A transaction resource at the "
+"resource adapter level is comprised of two separate objects:"
+msgstr ""
+"Ein Ressourcenmanager wird durch den Ressourcenadapter geschlossen, infolge "
+"der Zerstörung der transaktionalen Ressource. Eine transaktionale Ressource "
+"auf Ebene des Ressourcenadapters setzt sich zusammen aus zwei separaten "
+"Objekten:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:124
+#, no-c-format
+msgid ""
+"An <code>XAResource</code> object that allows the transaction manager to "
+"start and end the transaction association with the resource in use and to "
+"coordinate transaction completion process."
+msgstr ""
+"Ein <code>XAResource</code>-Objekt, welches dem Transaktionsmanager erlaubt, "
+"die Assoziation einer Transaktion mit der verwendeten Ressource zu starten "
+"oder zu beenden, und den Prozess zum Abschließen der Transaktion zu "
+"koordinieren."
+
+#. Tag: para
+#: The_Resource_Manager.xml:129
+#, no-c-format
+msgid ""
+"A connection object that allows the application to perform operations on the "
+"underlying resource (for example, JDBC operations on an RDBMS)."
+msgstr ""
+"Ein Verbindungsobjekt, das der Anwendung erlaubt, Operationen auf der "
+"zugrunde liegenden Ressource auszuführen (z. B. JDBC-Operationen auf einem "
+"RDBMS)."
+
+#. Tag: para
+#: The_Resource_Manager.xml:134
+#, no-c-format
+msgid ""
+"Once opened, the resource manager is kept open until the resource is "
+"released (closed) explicitly. When the application invokes the connection’s "
+"close method, the resource adapter invalidates the connection object "
+"reference that was held by the application and notifies the application "
+"server about the close. The transaction manager should invoke the "
+"<methodname>XAResource.end</methodname> method to disassociate the "
+"transaction from that connection."
+msgstr ""
+"Einmal geöffnet, wird der Ressourcenmanager offen gehalten, bis die "
+"Ressource wieder explizit freigegeben (geschlossen) wird. Wenn die Anwendung "
+"die \"close\"-Methode der Verbindung aufruft, macht der Ressourcenadapter "
+"die von der Anwendung gehaltene Verbindungsobjektreferenz ungültig und setzt "
+"den Anwendungsserver über die Schließung in Kenntnis. Der "
+"Transaktionsmanager sollte die <methodname>XAResource.end</methodname>-"
+"Methode aufrufen, um die Transaktion von der Verbindung zu disassoziieren."
+
+#. Tag: para
+#: The_Resource_Manager.xml:137
+#, no-c-format
+msgid ""
+"The close notification allows the application server to perform any "
+"necessary cleanup work and to mark the physical XA connection as free for "
+"reuse, if connection pooling is in place."
+msgstr ""
+"Die \"close\"-Benachrichtigung ermöglicht es dem Anwendungsserver, ggf. "
+"nötige Bereinigungen durchzuführen und die physikalische XA-Verbindung als "
+"verfügbar für Wiederverwendung zu markieren, falls Verbindungs-Pooling "
+"eingesetzt wird."
+
+#. Tag: title
+#: The_Resource_Manager.xml:143
+#, no-c-format
+msgid "Threads of control"
+msgstr "Kontroll-Threads"
+
+#. Tag: para
+#: The_Resource_Manager.xml:144
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface specifies that the "
+"transaction association related xa calls must be invoked from the same "
+"thread context. This thread-of-control requirement is not applicable to the "
+"object-oriented component-based application run-time environment, in which "
+"application threads are dispatched dynamically at method invocation time. "
+"Different threads may be using the same connection resource to access the "
+"resource manager if the connection spans multiple method invocation. "
+"Depending on the implementation of the application server, different threads "
+"may be involved with the same <code>XAResource</code> object. The resource "
+"context and the transaction context may be operated independent of thread "
+"context. This means that it is possible for different threads to be invoking "
+"the start and end methods."
+msgstr ""
+"Die X/Open <interfacename>XA</interfacename>-Schnittstelle spezifiziert, "
+"dass xa-Aufrufe in Bezug auf Transaktionsassoziation von demselben Thread-"
+"Kontext aufgerufen werden müssen. Diese Kontroll-Thread-Anforderung gilt "
+"nicht für die objektorientierte, komponentenbasierte Laufzeitumgebung der "
+"Anwendung, in der Anwendungs-Threads dynamisch gesendet werden zum Zeitpunkt "
+"des Methodenaufrufs. Verschiedene Threads können dieselbe "
+"Verbindungsressource verwenden, um auf den Ressourcenmanager zuzugreifen, "
+"falls die Verbindung mehrere Methodenaufrufe umfasst. Abhängig von der "
+"Implementierung des Anwendungsservers können verschiedene Threads an "
+"demselben <code>XAResource</code>-Objekt beteiligt sein. Der "
+"Ressourcenkontext und der Transaktionskontext können unabhängig vom Thread-"
+"Kontext gesteuert werden. Das bedeutet, dass es verschiedenen Threads "
+"möglich ist, die Start- und End-Methoden aufzurufen."
+
+#. Tag: para
+#: The_Resource_Manager.xml:147
+#, no-c-format
+msgid ""
+"If the application server allows multiple threads to use a single "
+"<code>XAResource</code> object and the associated connection to the resource "
+"manager, it is the responsibility of the application server to ensure that "
+"there is only one transaction context associated with the resource at any "
+"point of time. Thus the <interfacename>XAResource</interfacename> interface "
+"requires that the resource managers be able to support the two-phase commit "
+"protocol from any thread context."
+msgstr ""
+"Falls der Anwendungsserver mehreren Threads erlaubt, ein einzelnes "
+"<code>XAResource</code>-Objekt und die assoziierte Verbindung zum "
+"Ressourcenmanager zu benutzen, dann liegt es in der Verantwortung des "
+"Anwendungsservers sicherzustellen, dass zu jeder Zeit nur ein "
+"Transaktionskontext mit der Ressource assoziiert ist. Aus diesem Grund "
+"erfordert die <interfacename>XAResource</interfacename>-Schnittstelle, dass "
+"der Ressourcenmanager das zwei-Phasen-Festschreibungsprotokoll von jedem "
+"Thread-Kontext unterstützen kann."
+
+#. Tag: title
+#: The_Resource_Manager.xml:153
+#, no-c-format
+msgid "Transaction association"
+msgstr "Transaktionsassoziation"
+
+#. Tag: para
+#: The_Resource_Manager.xml:154
+#, no-c-format
+msgid ""
+"Transactions are associated with a transactional resource via the start "
+"method, and disassociated from the resource via the <methodname>end</"
+"methodname> method. The resource adapter is responsible for internally "
+"maintaining an association between the resource connection object and the "
+"<code>XAResource</code> object. At any given time, a connection is "
+"associated with a single transaction, or it is not associated with any "
+"transaction at all. Because JTA does not support nested transactions it is "
+"an error for the start method to be invoked on a connection that is "
+"currently associated with a different transaction."
+msgstr ""
+"Transaktionen werden mithilfe der \"start\"-Methode mit einer "
+"transaktionalen Ressource assoziiert, und von der Ressource disassoziiert "
+"mithilfe der <methodname>end</methodname>-Methode. Der Ressourcenadapter ist "
+"zuständig dafür, intern eine Assoziation zu bewahren zwischen dem "
+"Ressourcenverbindungsobjekt und dem <code>XAResource</code>-Objekt. Zu jeder "
+"Zeit ist eine Verbindung mit einer einzelnen Transaktion assoziiert, oder "
+"aber sie ist mit überhaupt keiner Transaktion assoziiert. Da JTA keine "
+"verschachtelten Transaktionen unterstützt, stellt es für die \"start\"-"
+"Methode einen Fehler dar, wenn sie auf einer Verbindung aufgerufen wird, die "
+"aktuell mit einer anderen Transaktion assoziiert ist."
+
+#. Tag: para
+#: The_Resource_Manager.xml:157
+#, no-c-format
+msgid ""
+"Interleaving multiple transaction contexts using the same resource may be "
+"done by the transaction manager as long as start and end are invoked "
+"properly for each transaction context switch. Each time the resource is used "
+"with a different transaction, the method end must be invoked for the "
+"previous transaction that was associated with the resource, and start must "
+"be invoked for the current transaction context."
+msgstr ""
+"Verschränkung (\"Interleaving\") mehrerer Transaktionskontexte, die dieselbe "
+"Ressource verwenden, kann durch den Transaktionsmanager angewendet werden, "
+"solange Start und Ende für jeden Transaktionskontextwechsel ordnungsgemäß "
+"aufgerufen werden. Jedesmal, wenn die Ressource mit einer anderen "
+"Transaktion verwendet wird, muss die \"end\"-Methode für die vorherige "
+"Transaktion aufgerufen werden, die mit der Ressource assoziiert war, und die "
+"\"start\"-Methode muss für den aktuellen Transaktionskontext aufgerufen "
+"werden."
+
+#. Tag: title
+#: The_Resource_Manager.xml:163
+#, no-c-format
+msgid "Externally controlled connections"
+msgstr "Extern kontrollierte Verbindungen"
+
+#. Tag: para
+#: The_Resource_Manager.xml:164
+#, no-c-format
+msgid ""
+"For transactional application whose transaction states are managed by an "
+"application server, its resources must also be managed by the application "
+"server so that transaction association is performed properly. If an "
+"application is associated with a transaction, it is an error for the "
+"application to perform transactional work through the connection without "
+"having the connection’s resource object already associated with the global "
+"transaction. The application server must ensure that the <code>XAResource</"
+"code> object in use is associated with the transaction. This is done by "
+"invoking the <methodname>Transaction.enlistResource</methodname> method."
+msgstr ""
+"Bei transaktionalen Anwendungen, deren Transaktionszustände von einem "
+"Anwendungsserver gesteuert werden, müssen auch seine Ressourcen vom "
+"Anwendungsserver gesteuert werden, damit die Transaktionsassoziation "
+"ordnungsgemäß ausgeführt wird. Wenn eine Anwendung mit einer Transaktion "
+"assoziiert ist, stellt es für die Anwendung einen Fehler dar, transaktionale "
+"Arbeit über die Verbindung auszuführen, ohne das Ressourcenobjekt der "
+"Verbindung bereits mit der globalen Transaktion assoziiert zu haben. Der "
+"Anwendungsserver muss sicherstellen, dass das verwendete <code>XAResource</"
+"code>-Objekt mit der Transaktion assoziiert ist. Dies wird erreicht durch "
+"Aufrufen der <methodname>Transaction.enlistResource</methodname>-Methode."
+
+#. Tag: para
+#: The_Resource_Manager.xml:167
+#, no-c-format
+msgid ""
+"If a server side transactional application retains its database connection "
+"across multiple client requests, the application server must ensure that "
+"before dispatching a client request to the application thread, the resource "
+"is enlisted with the application’s current transaction context. This implies "
+"that the application server manages the connection resource usage status "
+"across multiple method invocations."
+msgstr ""
+"Wenn eine Server-seitige transaktionale Anwendung ihre Datenbankverbindung "
+"über mehrere Client-Anfragen hinweg beibehält, muss der Anwendungsserver "
+"sicherstellen, dass die Ressource im aktuellen Transaktionskontext der "
+"Anwendung eingetragen ist, bevor eine Client-Anfrage an einen Anwendungs-"
+"Thread geschickt wird. Dies impliziert, dass der Anwendungsserver den "
+"Nutzungsstatus der Verbindungsressource über mehrere Methodenaufrufe hinweg "
+"steuert."
+
+#. Tag: title
+#: The_Resource_Manager.xml:173
+#, no-c-format
+msgid "Resource sharing"
+msgstr "Teilen von Ressourcen"
+
+#. Tag: para
+#: The_Resource_Manager.xml:174
+#, no-c-format
+msgid ""
+"When the same transactional resource is used to interleave multiple "
+"transactions, it is the responsibility of the application server to ensure "
+"that only one transaction is enlisted with the resource at any given time. "
+"To initiate the transaction commit process, the transaction manager is "
+"allowed to use any of the resource objects connected to the same resource "
+"manager instance. The resource object used for the two-phase commit protocol "
+"does not need to have been involved with the transaction being completed."
+msgstr ""
+"Wenn dieselbe transaktionale Ressource genutzt wird, um mehrere "
+"Transaktionen zu verschränken, obliegt es dem Anwendungsserver "
+"sicherzustellen, dass zu jeder Zeit nur eine Transaktion bei der Ressource "
+"eingetragen ist. Um den Prozess zur Transaktionsfestschreibung zu "
+"initiieren, darf der Transaktionsmanager jedes der Ressourcenobjekte nutzen, "
+"die mit derselben Ressourcenmanagerinstanz verbunden sind. Das "
+"Ressourcenobjekt, welches für die zwei-Phasen Festschreibung verwendet wird, "
+"braucht nicht an der abzuschließenden Transaktion beteiligt gewesen zu sein."
+
+#. Tag: para
+#: The_Resource_Manager.xml:177
+#, no-c-format
+msgid ""
+"The resource adapter must be able to handle multiple threads invoking the "
+"<interfacename>XAResource</interfacename> methods concurrently for "
+"transaction commit processing. For example, with reference to the code "
+"below, suppose we have a transactional resource <code>r1</code>. Global "
+"transaction <code>xid1</code> was started and ended with <code>r1</code>. "
+"Then a different global transaction <code>xid2</code> is associated with "
+"<code>r1</code>. In the meanwhile, the transaction manager may start the two "
+"phase commit process for <code>xid1</code> using <code>r1</code> or any "
+"other transactional resource connected to the same resource manager. The "
+"resource adapter needs to allow the commit process to be executed while the "
+"resource is currently associated with a different global transaction."
+msgstr ""
+"Der Ressourcenadapter muss damit umgehen können, dass mehrere Threads "
+"gleichzeitig die <interfacename>XAResource</interfacename>-Methoden aufrufen "
+"zur Verarbeitung der Transaktionsfestschreibung. Nehmen wir beispielsweise "
+"an, im Hinblick auf den Code unten, dass wir die transaktionale Ressource "
+"<code>r1</code> haben. Die globale Transaktion <code>xid1</code> wurde "
+"gestartet und mit <code>r1</code> beendet. Anschließend wird eine andere "
+"globale Transaktion <code>xid2</code> mit <code>r1</code> assoziiert. In der "
+"Zwischenzeit startet der Transaktionsmanager ggf. den zwei-Phasen "
+"Festschreibungsprozess für <code>xid1</code> unter Verwendung von <code>r1</"
+"code> oder einer anderen transaktionalen Ressource, die mit demselben "
+"Ressourcenmanager verbunden ist. Der Ressourcenadapter muss die Ausführung "
+"des Festschreibungsprozesses erlauben, während die Ressource aktuell mit "
+"einer anderen globalen Transaktion assoziiert ist."
+
+#. Tag: screen
+#: The_Resource_Manager.xml:180
+#, no-c-format
+msgid ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+msgstr ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+
+#. Tag: title
+#: The_Resource_Manager.xml:184
+#, no-c-format
+msgid "Local and global transactions"
+msgstr "Lokale und globale Transaktionen"
+
+#. Tag: para
+#: The_Resource_Manager.xml:185
+#, no-c-format
+msgid ""
+"The resource adapter must support the usage of both local and global "
+"transactions within the same transactional connection. Local transactions "
+"are transactions that are started and coordinated by the resource manager "
+"internally. The <interfacename>XAResource</interfacename> interface is not "
+"used for local transactions. When using the same connection to perform both "
+"local and global transactions, the following rules apply:"
+msgstr ""
+"Der Ressourcenadapter muss die Nutzung von sowohl lokalen als auch globalen "
+"Transaktionen innerhalb derselben Transaktionsverbindung unterstützen. "
+"Lokale Transaktionen sind Transaktionen, die vom Ressourcenmanager intern "
+"gestartet und koordiniert werden. Die <interfacename>XAResource</"
+"interfacename>-Schnittstelle wird nicht für lokale Transaktionen verwendet. "
+"Wenn dieselbe Verbindung für die Durchführung sowohl lokaler als auch "
+"globaler Transaktionen verwendet wird, gelten die folgenden Regeln:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:190
+#, no-c-format
+msgid ""
+"The local transaction must be committed (or rolled back) before starting a "
+"global transaction in the connection."
+msgstr ""
+"Die lokale Transaktion muss festgeschrieben (oder zurückgesetzt) werden, "
+"bevor eine globale Transaktion in der Verbindung gestartet wird."
+
+#. Tag: para
+#: The_Resource_Manager.xml:195
+#, no-c-format
+msgid ""
+"The global transaction must be disassociated from the connection before any "
+"local transaction is started."
+msgstr ""
+"Die globale Transaktion muss von der Verbindung disassoziiert werden, bevor "
+"eine lokale Transaktion gestartet wird."
+
+#. Tag: title
+#: The_Resource_Manager.xml:203
+#, no-c-format
+msgid "Transaction timeouts"
+msgstr "Transaktions-Timeouts"
+
+#. Tag: para
+#: The_Resource_Manager.xml:204
+#, no-c-format
+msgid ""
+"Timeout values can be associated with transactions in order to control their "
+"lifetime. If a transaction has not terminated (committed or rolled back) "
+"before the timeout value elapses, the transaction system will automatically "
+"roll it back. The <interfacename>XAResource</interfacename> interface "
+"supports a operation, which allows the timeout associated with the current "
+"transaction to be propagated to the resource manager and if supported, will "
+"override any default timeout associated with the resource manager. This can "
+"be useful when long running transactions may have lifetimes that would "
+"exceed the default and in which case, if the timeout were not altered, the "
+"resource manager would rollback before the transaction terminated and "
+"subsequently cause the transaction to roll back as well."
+msgstr ""
+"Transaktionen können Timout-Werte zugewiesen werden, um ihre Lebenszeit zu "
+"kontrollieren. Wenn eine Transaktion vor Ablauf des Timeout-Werts nicht "
+"beendet ist (festgeschrieben oder zurückgesetzt), wird das "
+"Transaktionssystem sie automatisch zurücksetzen. Die "
+"<interfacename>XAResource</interfacename>-Schnittstelle unterstützt eine "
+"Operation, durch die der Timout-Wert der aktuellen Transaktion fortgepflanzt "
+"wird zum Ressourcenmanager und dort, falls unterstützt, den Standard-Timeout-"
+"Wert des Ressourcenmanagers außer Kraft setzt. Dies kann nützlich sein, wenn "
+"langlaufende Transaktionen evtl. Lebenszeiten haben, die den Standard "
+"überschreiten könnten. Würde der Timeout-Wert nicht geändert, so würde in "
+"diesem Fall der Ressourcenmanager zurücksetzen, bevor die Transaktion "
+"abgeschlossen wurde, und infolgedessen auch das Zurücksetzen der Transaktion "
+"verursachen."
+
+#. Tag: para
+#: The_Resource_Manager.xml:207
+#, no-c-format
+msgid ""
+"If no timeout value is explicitly set for a transaction, or a value of 0 is "
+"specified, then an implementation specific default value may be used. In the "
+"case of JBossTS, how this default value is set depends upon which JTA "
+"implementation you are using."
+msgstr ""
+"Wenn für eine Transaktion explizit kein Timeout-Wert eingestellt ist, oder "
+"der Wert 0 angegeben ist, wird ggf. ein implementierungsspezifischer "
+"Standardwert verwendet. Im Fall von JBossTS hängt der eingestellte "
+"Standardwert von der von Ihnen verwendeten Implementierung ab."
+
+#. Tag: para
+#: The_Resource_Manager.xml:212
+#, no-c-format
+msgid ""
+"Local JTA: use the <property>com.arjuna.ats.arjuna.coordinator."
+"defaultTimeout</property> property value and give a timeout in seconds. The "
+"default value is 60 seconds."
+msgstr ""
+"Lokale JTA: Benutzen Sie den <property>com.arjuna.ats.arjuna.coordinator."
+"defaultTimeout</property>-Eigenschaftswert und geben einen Timout in "
+"Sekunden an. Der Standardwert ist 60 Sekunden."
+
+#. Tag: para
+#: The_Resource_Manager.xml:217
+#, no-c-format
+msgid ""
+"JTS: use the <property>com.arjuna.ats.jts.defaultTimeout</property> property "
+"value and give a timeout in seconds. The default value is 0, for instance, "
+"transactions do not timeout."
+msgstr ""
+"JTS: Benutzen Sie den <property>com.arjuna.ats.jts.defaultTimeout</"
+"property>-Eigenschaftswert und geben einen Timout in Sekunden an. Ist der "
+"Standardwert z. B. 0 Sekunden, verfallen Transaktionen nicht."
+
+#. Tag: para
+#: The_Resource_Manager.xml:222
+#, no-c-format
+msgid ""
+"Unfortunately there are situations where imposing the same timeout as the "
+"transaction on a resource manager may not be appropriate. For example, if "
+"the system administrator wishes to have control over the lifetimes on "
+"resource managers and does not want to (or cannot) allow that control to be "
+"passed to some external entity. At present JBossTS supports an all-or-"
+"nothing approach to whether or not <methodname>setTransactionTimeout</"
+"methodname> is called on <interfacename>XAResource</interfacename> instances."
+msgstr ""
+"Leider gibt es Situationen, in denen es ggf. nicht angebracht ist, denselben "
+"Timout-Wert einer Transaktion auch dem Ressourcenmanager aufzuerlegen, z. B. "
+"wenn der Systemadministrator Kontrolle über die Lebenszeit von "
+"Ressourcenmanagern haben möchte, und nicht erlauben will (oder kann), dass "
+"diese Kontrolle an externe Entitys übergeben wird. JBossTS unterstützt "
+"derzeit eine Alles-oder-Nichts-Herangehensweise im Hinblick darauf, ob "
+"<methodname>setTransactionTimeout</methodname> auf "
+"<interfacename>XAResource</interfacename>-Instanzen aufgerufen wird, oder "
+"nicht."
+
+#. Tag: para
+#: The_Resource_Manager.xml:225
+#, no-c-format
+msgid ""
+"If the <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> "
+"property is set to true (the default) then it will be called on all "
+"instances. Alternatively, the <methodname>setXATransactionTimeoutEnabled</"
+"methodname> method of <classname>com.arjuna.ats.jta.common.Configuration</"
+"classname> can be used."
+msgstr ""
+"Wenn die <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property>-"
+"Eigenschaft auf \"true\" gesetzt ist (Standard), dann wird sie auf allen "
+"Instanzen aufgerufen. Alternativ kann die "
+"<methodname>setXATransactionTimeoutEnabled</methodname>-Methode von "
+"<classname>com.arjuna.ats.jta.common.Configuration</classname> verwendet "
+"werden."
+
+#. Tag: title
+#: The_Resource_Manager.xml:231
+#, no-c-format
+msgid "Dynamic Registration"
+msgstr "Dynamische Registrierung"
+
+#. Tag: para
+#: The_Resource_Manager.xml:232
+#, no-c-format
+msgid ""
+"Dynamic registration is not supported in <interfacename>XAResource</"
+"interfacename> because of the following reasons:"
+msgstr ""
+"Dynamische Registrierung wird in <interfacename>XAResource</interfacename> "
+"nicht unterstützt, aus den folgenden Gründen:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:237
+#, no-c-format
+msgid ""
+"In the Java component-based application server environment, connections to "
+"the resource manager are acquired dynamically when the application "
+"explicitly requests a connection. These resources are enlisted with the "
+"transaction manager on a needed basis."
+msgstr ""
+"In der komponenten-basierten Java-Anwendungsserverumgebung werden "
+"Verbindungen zum Ressourcenmanager dynamisch bezogen, wenn die Anwendung "
+"explizit eine Verbindung anfordert. Diese Ressourcen sind beim "
+"Transaktionsmanager eingetragen basierend auf Bedarf."
+
+#. Tag: para
+#: The_Resource_Manager.xml:242
+#, no-c-format
+msgid ""
+"If a resource manager requires a way to dynamically register its work to the "
+"global transaction, the implementation can be done at the resource adapter "
+"level via a private interface between the resource adapter and the "
+"underlying resource manager."
+msgstr ""
+"Falls ein Ressourcenmanager eine Möglichkeit benötigt, seine Arbeit "
+"dynamisch bei der globalen Transaktion zu registrieren, kann die "
+"Implementierung auf Ebene des Ressourcenadapters erfolgen mittels einer "
+"privaten Schnittstelle zwischen Ressourcenadapter und dem zugrunde liegenden "
+"Ressourcenmanager."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Transaction_Recovery.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Transaction_Recovery.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Transaction_Recovery.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,481 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr "Transaktions-Recovery"
+
+#. Tag: title
+#: Transaction_Recovery.xml:10
+#, no-c-format
+msgid "Failure recovery"
+msgstr "Failure Recovery"
+
+#. Tag: para
+#: Transaction_Recovery.xml:11
+#, no-c-format
+msgid ""
+"During recovery, the Transaction Manager needs to be able to communicate to "
+"all resource managers that are in use by the applications in the system. For "
+"each resource manager, the Transaction Manager uses the "
+"<methodname>XAResource.recover</methodname> method to retrieve the list of "
+"transactions that are currently in a prepared or heuristically completed "
+"state. Typically, the system administrator configures all transactional "
+"resource factories that are used by the applications deployed on the system. "
+"An example of such a resource factory is the JDBC <code>XADataSource</code> "
+"object, which is a factory for the JDBC <code>XAConnection</code> objects."
+msgstr ""
+"Während einer Recovery muss der Transaktionsmanager mit allen "
+"Ressourcenmanagern kommunizieren können, die von der Anwendung im System "
+"benutzt werden. Für jeden Ressourcenmanager wendet der Transaktionsmanager "
+"die <methodname>XAResource.recover</methodname>-Methode an, um eine Liste "
+"aller Transaktionen abzufragen, die sich aktuell in einem \"prepared\"- oder "
+"heuristischem \"completed\"-Zustand befinden. In der Regel konfiguriert der "
+"Systemadministrator alle transaktionalen Ressourcen-Factorys, die von den "
+"auf dem System eingesetzten Anwendungen genutzt werden sollen. Ein Bespiel "
+"für eine solche Ressourcen-Factory ist das JDBC <code>XADataSource</code>-"
+"Objekt, welches eine Factory für die JDBC <code>XAConnection</code>-Objekte "
+"ist."
+
+#. Tag: para
+#: Transaction_Recovery.xml:14
+#, no-c-format
+msgid ""
+"Because <code>XAResource</code> objects are not persistent across system "
+"failures, the Transaction Manager needs to have some way to acquire the "
+"<code>XAResource</code> objects that represent the resource managers which "
+"might have participated in the transactions prior to the system failure. For "
+"example, a Transaction Manager might, through the use of JNDI lookup "
+"mechanism, acquire a connection from each of the transactional resource "
+"factories, and then obtain the corresponding <code>XAResource</code> object "
+"for each connection. The Transaction Manager then invokes the "
+"<methodname>XAResource.recover</methodname> method to ask each resource "
+"manager to return the transactions that are currently in a prepared or "
+"heuristically completed state."
+msgstr ""
+"Weil <code>XAResource</code>-Objekte nicht persistent sind bei "
+"Systemausfällen, braucht der Transaktionsmanager eine Möglichkeit, "
+"<code>XAResource</code>-Objekte zu beziehen, welche diejenigen "
+"Ressourcenmanager repräsentieren, die vor Systemausfall evtl. an den "
+"Transaktionen teilgenommen haben. Zum Beispiel kann ein Transaktionsmanager "
+"mithilfe des JNDI-Lookup-Verfahrens eine Verbindung beziehen von jeder der "
+"transaktionalen Ressourcen-Factorys, und dann das entsprechende "
+"<code>XAResource</code>-Objekt für jede Verbindung erhalten. Der "
+"Transaktionsmanager ruft dann die <methodname>XAResource.recover</"
+"methodname>-Methode auf, um jeden Ressourcenmanager aufzufordern, diejenigen "
+"Transaktionen zurückzugeben, die sich derzeit in einem \"prepared\"- oder "
+"heuristischem \"completed\"-Zustand befinden."
+
+#. Tag: para
+#: Transaction_Recovery.xml:18
+#, no-c-format
+msgid ""
+"When running XA recovery it is 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 ‘*’ will force JBossTS to recover (and possibly rollback) all "
+"transactions irrespective of their node identifier and should be used with "
+"caution."
+msgstr ""
+"Beim Ausführen von XA-Recovery ist es notwendig, JBossTS mitzuteilen, welche "
+"Typen von Xid es wiederherstellen kann. Jede von JBossTS erstellte Xid hat "
+"einen eindeutigen Knoten-Identifier in sich enkodiert, und JBossTS wird nur "
+"diejenigen Transaktionen und Zustände versuchen wiederherzustellen, die auf "
+"einen spezifizierten Knoten-Identifier passen. Der zu verwendende Knoten-"
+"Identifier sollte JBossTS geliefert werden mittels einer Eigenschaft, die "
+"mit dem Namen <property>com.arjuna.ats.jta.xaRecoveryNode</property> "
+"beginnt; mehrere Werte können angegeben sein. Der Wert ‘*’ zwingt JBossTS "
+"zum Wiederherstellen (und möglicherweise Zurücksetzen) aller Transaktionen "
+"ungeachtet ihrer Knoten-Identifier, und sollte daher mit Bedacht verwendet "
+"werden."
+
+#. Tag: para
+#: Transaction_Recovery.xml:22
+#, no-c-format
+msgid ""
+"If using the JBossJTA JDBC 2.0 driver, then JBossJTA will take care of all "
+"<interfacename>XAResource</interfacename> crash recovery automatically. "
+"Otherwise one of the following recovery mechanisms will be used:"
+msgstr ""
+"Falls der JBossJTA JDBC 2.0 Treiber benutzt wird, erledigt JBossJTA jegliche "
+"<interfacename>XAResource</interfacename> Crash Recovery automatisch. "
+"Andernfalls wird eine der folgenden Verfahren zur Recovery verwendet:"
+
+#. Tag: para
+#: Transaction_Recovery.xml:27
+#, no-c-format
+msgid ""
+"If the <code>XAResource</code> is serializable, then the serialized form "
+"will be saved during transaction commitment, and used during recovery. It is "
+"assumed that the recreated <code>XAResource</code> is valid and can be used "
+"to drive recovery on the associated database."
+msgstr ""
+"Wenn die <code>XAResource</code> serialisierbar ist, wird die serialisierte "
+"Form während der Transaktionsfestschreibung gespeichert und bei der Recovery "
+"verwendet. Es wird angenommen, dass die wiederhergestellte <code>XAResource</"
+"code> gültig ist und verwendet werden kann, um Recovery auf der assoziierten "
+"Datenbank zu betreiben."
+
+#. Tag: para
+#: Transaction_Recovery.xml:32
+#, no-c-format
+msgid ""
+"The <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, <interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> and <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> interfaces are used. These "
+"are documented in the JDBC chapters on failure recovery."
+msgstr ""
+"Die Schnittstellen <interfacename>com.arjuna.ats.jta.recovery."
+"XAResourceRecovery</interfacename>, <interfacename>com.arjuna.ats.jta."
+"recovery.XARecoveryResourceManager</interfacename> und <interfacename>com."
+"arjuna.ats.jta.recovery.XARecoveryResource</interfacename> werden verwendet. "
+"Diese sind dokumentiert in den JDBC-Kapiteln über Failure Recovery."
+
+#. Tag: para
+#: Transaction_Recovery.xml:38
+#, no-c-format
+msgid ""
+"In JBossTS 3.3 the interface <interfacename>XAConnectionRecovery</"
+"interfacename> was deprecated in favor of <interfacename>XAResourceRecovery</"
+"interfacename>. Users are encouraged to move to his new interface."
+msgstr ""
+"In JBossTS 3.3 wurde die Schnittstelle <interfacename>XAConnectionRecovery</"
+"interfacename> missbilligt zugunsten der <interfacename>XAResourceRecovery</"
+"interfacename>. Benutzer werden ermutigt, zu dieser neuen Schnittstelle zu "
+"wechseln."
+
+#. Tag: title
+#: Transaction_Recovery.xml:45
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr "Wiederherstellen von XAConnections"
+
+#. Tag: para
+#: Transaction_Recovery.xml:46
+#, no-c-format
+msgid ""
+"When recovering from failures, JBossJTA requires the ability to reconnect to "
+"databases that were in use prior to the failures in order to resolve any "
+"outstanding transactions. Most connection information will be saved by the "
+"transaction service during its normal execution, and can be used during "
+"recovery to recreate the connection. However, it is possible that not all "
+"such information will have been saved prior to a failure (for example, a "
+"failure occurs before such information can be saved, but after the database "
+"connection is used). In order to recreate those connections it is necessary "
+"to provide implementations of the following JBossJTA interface "
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, one for each database that may be used by an application."
+msgstr ""
+"Beim Wiederherstellen nach Ausfällen benötigt JBossJTA die Fähigkeit, sich "
+"wieder mit Datenbanken zu verbinden, die vor dem Ausfall verwendet wurden, "
+"damit jegliche ausstehende Transaktionen aufgelöst werden können. Der "
+"Großteil der Verbindungsinformationen wird vom Transaktionsdienst während "
+"dessen normaler Ausführung gespeichert und kann während der Recovery zum "
+"Wiederherstellen der Verbindung genutzt werden. Allerdings ist es möglich, "
+"dass nicht alle dieser Informationen vor einem Ausfall gespeichert wurden "
+"(z. B. wenn ein Ausfall auftritt, bevor diese Informationen gespeichert "
+"werden können, aber nachdem die Datenbankverbindung benutzt wurde). Um diese "
+"Verbindungen wiederherzustellen, ist es nötig, Implementierungen der "
+"folgenden JBossJTA-Schnittstelle bereitzustellen <interfacename>com.arjuna."
+"ats.jta.recovery.XAResourceRecovery</interfacename>, eine für jede "
+"Datenbank, die ggf. von einer Anwendung verwendet werden könnte."
+
+#. Tag: para
+#: Transaction_Recovery.xml:50
+#, no-c-format
+msgid ""
+"If using the transactional JDBC 2.0 driver provided with JBossJTA, then no "
+"additional work is necessary in order to ensure that recovery occurs."
+msgstr ""
+"Falls der von JBossJTA gelieferte transaktionale JDBC 2.0 Treiber verwendet "
+"wird, sind keine zusätzlichen Maßnahmen nötig, um das Durchführen der "
+"Recovery zu gewährleisten."
+
+#. Tag: para
+#: Transaction_Recovery.xml:54
+#, no-c-format
+msgid ""
+"To inform the recovery system about each of the <code>XAResourceRecovery</"
+"code> instances, it is necessary to specify their class names through "
+"property variables. Any property variable found in the properties file, or "
+"registered at runtime, which starts with the name <property>com.arjuna.ats."
+"jta.recovery.XAResourceRecovery</property> will be assumed to represent one "
+"of these instances, and its value should be the class name. For example:"
+msgstr ""
+"Um das Recovery-System über jede der <code>XAResourceRecovery</code>-"
+"Instanzen zu informieren, ist es notwendig, deren Klassennamen durch "
+"Eigenschaftsvariablen zu spezifizieren. Von jeder Eigenschaftsvariablen, die "
+"in der Eigenschaftsdatei gefunden wird oder zur Laufzeit registriert wird "
+"und mit dem Namen <property>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"property> beginnt, wird angenommen, dass sie eine dieser Instanzen "
+"repräsentiert, und ihr Wert sollte der Klassenname sein. Zum Beispiel:"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:57
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+
+#. Tag: para
+#: Transaction_Recovery.xml:58
+#, no-c-format
+msgid ""
+"Additional information that will be passed to the instance when it is "
+"created may be specified after a semicolon:"
+msgstr ""
+"Zusätzliche Informationen, die an die Instanz übergeben werden bei deren "
+"Erstellung, kann nach einem Semikolon spezifiziert werden:"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+
+#. Tag: para
+#: Transaction_Recovery.xml:63
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr "Diese Eigenschaften gehören in den JTA-Bereich der Eigenschaftdatei."
+
+#. Tag: para
+#: Transaction_Recovery.xml:67
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr "Jegliche Fehler werden während der Recovery gemeldet."
+
+#. Tag: screen
+#: Transaction_Recovery.xml:70
+#, no-c-format
+msgid ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+msgstr ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+
+#. Tag: para
+#: Transaction_Recovery.xml:71
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr "Jede Methode sollte die folgenden Informationen zurückgeben:"
+
+#. Tag: para
+#: Transaction_Recovery.xml:76
+#, no-c-format
+msgid ""
+"<methodname>initialise</methodname>: once the instance has been created, any "
+"additional information which occurred on the property value (anything found "
+"after the first semi-colon) will be passed to the object. The object can "
+"then use this information in an implementation specific manner to initialise "
+"itself, for example."
+msgstr ""
+"<methodname>initialise</methodname>: Sobald die Instanz erstellt wurde, "
+"werden alle zusätzlichen Informationen auf dem Eigenschaftswert (alles nach "
+"dem ersten Semikolon) weitergegeben an das Objekt. Das Objekt kann diese "
+"Informationen dann auf implementierungsspezifische Weise verwenden, z. B. um "
+"sich selbst zu initialisieren."
+
+#. Tag: para
+#: Transaction_Recovery.xml:81
+#, no-c-format
+msgid ""
+"<methodname>hasMoreResources</methodname>: each <code>XAResourceRecovery</"
+"code> implementation may provide multiple <code>XAResource</code> instances. "
+"Before any call to <methodname>getXAResource</methodname> is made, "
+"<methodname>hasMoreResources</methodname> is called to determine whether "
+"there are any further connections to be obtained. If this returns false, "
+"<methodname>getXAResource</methodname> will not be called again during this "
+"recovery sweep and the instance will not be used further until the next "
+"recovery scan."
+msgstr ""
+"<methodname>hasMoreResources</methodname>: Jede <code>XAResourceRecovery</"
+"code>-Implementierung kann mehrere <code>XAResource</code>-Instanzen "
+"liefern. Bevor der Aufruf <methodname>getXAResource</methodname> erfolgt, "
+"wird <methodname>hasMoreResources</methodname> aufgerufen um festzustellen, "
+"ob es noch mehr Verbindungen gibt, die zu beziehen sind. Falls dies \"false"
+"\" zurückgibt, wird <methodname>getXAResource</methodname> während dieses "
+"Recovery-Durchlaufs nicht wieder aufgerufen, und die Instanz wird nicht mehr "
+"verwendet werden bis zum nächsten Recovery Scan."
+
+#. Tag: para
+#: Transaction_Recovery.xml:86
+#, no-c-format
+msgid ""
+"<methodname>getXAResource</methodname>: returns an instance of the "
+"<code>XAResource</code> object. How this is created (and how the parameters "
+"to its constructors are obtained) is up to the <code>XAResourceRecovery</"
+"code> implementation. The parameters to the constructors of this class "
+"should be similar to those used when creating the initial driver or data "
+"source, and should obviously be sufficient to create new <code>XAResources</"
+"code> that can be used to drive recovery."
+msgstr ""
+"<methodname>getXAResource</methodname>: Gibt eine Instanz des "
+"<code>XAResource</code>-Objekts zurück. Wie diese erstellt wird (und wie die "
+"Parameter zu ihren Kontruktoren erhalten werden), hängt von der "
+"<code>XAResourceRecovery</code>-Implementierung ab. Die Parameter zu den "
+"Konstruktoren dieser Klasse sollten denen ähneln, die benutzt werden zur "
+"Erstellung der initialen Treiber- oder Datenquelle, und sollten "
+"offensichtlich ausreichend sein, um neue <code>XAResources</code> zu "
+"erstellen, die zum Ausführen der Recovery verwendet werden können."
+
+#. Tag: para
+#: Transaction_Recovery.xml:92
+#, no-c-format
+msgid ""
+"If you want your <code>XAResourceRecovery</code> instance to be called "
+"during each sweep of the recovery manager then you should ensure that once "
+"<methodname>hasMoreResources</methodname> returns false to indicate the end "
+"of work for the current scan it then returns true for the next recovery scan."
+msgstr ""
+"Falls Sie wünschen, dass Ihre <code>XAResourceRecovery</code>-Instanz bei "
+"jedem Durchlauf des Recovery-Managers aufgerufen wird, sollten Sie "
+"sicherstellen, dass, sobald <methodname>hasMoreResources</methodname> \"false"
+"\" zurückgibt, um das Ende der Arbeit für den aktuellen Scan anzuzeigen, es "
+"danach \"true\" zurückgibt für den nächsten Recovery Scan."
+
+#. Tag: title
+#: Transaction_Recovery.xml:99
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr "Mitgelieferte XAResourceRecovery-Implementierungen"
+
+#. Tag: para
+#: Transaction_Recovery.xml:100
+#, no-c-format
+msgid ""
+"Recovery of <interfacename>XA</interfacename> datasources can sometimes be "
+"implementation dependant, requiring developers to provide their own "
+"<interfacename>XAResourceRecovery</interfacename> instances. However, "
+"JBossTS ships with several out-of-the-box implementations that may be useful."
+msgstr ""
+"Recovery von <interfacename>XA</interfacename>-Datenquellen kann manchmal "
+"implementierungsabhängig sein, und von Entwicklern erfordern, ihre eigenen "
+"<interfacename>XAResourceRecovery</interfacename>-Instanzen bereitzustellen. "
+"JBossTS liefert jedoch mehrere Standardimplementierungen mit, die nützlich "
+"sein können."
+
+#. Tag: para
+#: Transaction_Recovery.xml:105
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: this expects an XML property file to be specified upon "
+"creation and from which it will read the database URL, username and "
+"password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: Dies erwartet, dass eine XML-Eigenschaftsdatei bei der "
+"Erstellung spezifiziert wird, aus der es die Datenbank-URL, Benutzernamen "
+"und Passwort auslesen wird. Zum Beispiel:"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:108
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+
+#. Tag: para
+#: Transaction_Recovery.xml:111
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: this recovery implementation should work on any datasource "
+"that is exposed via JNDI. It expects an XML property file to be specified "
+"upon creation and from which it will read the database JNDI name, username "
+"and password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: Diese Recovery-Implementierung sollte auf jeder Datenquelle "
+"funktionieren, die via JNDI offengelegt ist. Sie erwartet, dass eine XML-"
+"Eigenschaftsdatei bei der Erstellung spezifiziert wird, aus der es den "
+"Datenbank-JNDI-Namen, Benutzernamen und Passwort auslesen wird. Zum Beispiel:"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:114
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,672 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr "Transaktionen"
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr "Die API"
+
+#. Tag: para
+#: Transactions.xml:9
+#, no-c-format
+msgid ""
+"The Java Transaction API consists of three elements: a high-level "
+"application transaction demarcation interface, a high-level transaction "
+"manager interface intended for application server, and a standard Java "
+"mapping of the X/Open XA protocol intended for transactional resource "
+"manager. All of the JTA classes and interfaces occur within the "
+"<package>javax.transaction</package> package, and the corresponding JBossJTA "
+"implementations within the <package>com.arjuna.ats.jta</package> package."
+msgstr ""
+"Die Java-Transaktions-API besteht aus drei Elementen: Einer high-level "
+"Schnittstelle zur Demarkation von Anwendungstransaktionen, einer high-level "
+"Transaktionsmanagerschnittstelle für Anwendungsserver, und einem Standard-"
+"Java-Mapping des X/Open XA-Protokolls für den transaktionalen "
+"Ressourcenmanager. Alle JTA-Klassen und -Schnittstellen liegen im "
+"<package>javax.transaction</package>-Paket, und die entsprechenden JBossJTA-"
+"Implementierungen im <package>com.arjuna.ats.jta</package>-Paket."
+
+#. Tag: para
+#: Transactions.xml:13
+#, no-c-format
+msgid ""
+"Each 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. The contents of this "
+"should be alphanumeric."
+msgstr ""
+"Jede von JBossTS erstellte Xid muss in sich enkodiert einen eindeutigen "
+"Knoten-Identifier besitzen, und JBossTS wird nur Transaktionen und Zustände "
+"wiederherstellen, die auf einen spezifizierten Knoten-Identifier passen. Der "
+"zu nutzende Knoten-Identifier sollte JBossTS mittels der <property>com."
+"arjuna.ats.arjuna.xa.nodeIdentifier</property>-Eigenschaft geliefert werden. "
+"Stellen Sie sicher, dass dieser Wert eindeutig ist über Ihre JBossTS-"
+"Instanzen hinweg. Falls Sie keinen Wert angeben, wird JBossTS einen Wert "
+"generieren und ihn via der Protokollinfrastruktur melden. Dieser Wert sollte "
+"alphanumerisch sein."
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: Transactions.xml:19
+#, no-c-format
+msgid ""
+"The <interfacename>UserTransaction</interfacename> interface provides "
+"applications with the ability to control transaction boundaries. It has "
+"methods for beginning, committing, and rolling back top-level transactions: "
+"nested transactions are not supported, and begin throws the "
+"<code>NotSupportedException</code> when the calling thread is already "
+"associated with a transaction. <interfacename>UserTransaction</"
+"interfacename> automatically associates newly created transactions with the "
+"invoking thread."
+msgstr ""
+"Die <interfacename>UserTransaction</interfacename>-Schnittstelle erlaubt es "
+"Anwendungen, Transaktionsgrenzen zu kontrollieren. Sie besitzt Methoden zum "
+"Beginnen, Festschreiben und Zurücksetzen von Transaktionen oberster Ebene: "
+"Verschachtelte Transaktionen werden nicht unterstützt, und die \"begin\"-"
+"Methode wirft die <code>NotSupportedException</code>, wenn der aufrufende "
+"Thread bereits mit einer Transaktion assoziiert ist. "
+"<interfacename>UserTransaction</interfacename> assoziiert automatisch neu "
+"erstellte Transaktionen mit dem aufrufenden Thread."
+
+#. Tag: para
+#: Transactions.xml:24
+#, no-c-format
+msgid ""
+"In JBossJTA, UserTransactions can be obtained from the static "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname> method."
+msgstr ""
+"In JBossJTA können UserTransactions von der statischen <methodname>com."
+"arjuna.ats.jta.UserTransaction.userTransaction()</methodname>-Methode "
+"erhalten werden."
+
+#. Tag: para
+#: Transactions.xml:28
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+"Um die lokale JTA-Implementierung auszuwählen, müssen folgende Schritte "
+"ausgeführt werden:"
+
+#. Tag: para
+#: Transactions.xml:33
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</property>."
+msgstr ""
+"Stellen Sie sicher, dass die Eigenschaft <property>com.arjuna.ats.jta."
+"jtaTMImplementation</property> auf <property>com.arjuna.ats.internal.jta."
+"transaction.arjunacore.TransactionManagerImple</property> gesetzt ist."
+
+#. Tag: para
+#: Transactions.xml:38
+#, no-c-format
+msgid ""
+"1.make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</property>."
+msgstr ""
+"Stellen Sie sicher, dass die Eigenschaft <property>com.arjuna.ats.jta."
+"jtaUTImplementation</property> auf <property>com.arjuna.ats.internal.jta."
+"transaction.arjunacore.UserTransactionImple</property> gesetzt ist."
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr "Transaktionsmanager"
+
+#. Tag: para
+#: Transactions.xml:45
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface allows the "
+"application server to control transaction boundaries on behalf of the "
+"application being managed."
+msgstr ""
+"Die <interfacename>TransactionManager</interfacename>-Schnittstelle erlaubt "
+"dem Anwendungsserver, Transaktionsgrenzen im Auftrag der laufenden Anwendung "
+"zu kontrollieren."
+
+#. Tag: para
+#: Transactions.xml:50
+#, no-c-format
+msgid ""
+"In JBossJTA, transaction manager implementations can be obtained from the "
+"static <methodname>com.arjuna.ats.jta.TransactionManager.transactionManager</"
+"methodname> method."
+msgstr ""
+"In JBossJTA können Implementierungen des Transaktionsmanagers von der "
+"statischen <methodname>com.arjuna.ats.jta.TransactionManager."
+"transactionManager</methodname>-Methode erhalten werden."
+
+#. Tag: para
+#: Transactions.xml:54
+#, no-c-format
+msgid ""
+"The Transaction Manager maintains the transaction context association with "
+"threads as part of its internal data structure. A thread’s transaction "
+"context is either null or it refers to a specific global transaction. "
+"Multiple threads may be associated with the same global transaction. As "
+"noted above, nested transactions are not supported."
+msgstr ""
+"Der Transaktionsmanager bewahrt die Assoziation des Transaktionskontextes "
+"mit Threads als Teil seiner internen Datenstruktur. Der Transaktionskontext "
+"eines Threads ist entweder Null, oder er verweist auf eine spezifische "
+"globale Transaktion. Mehrere Threads können mit derselben globalen "
+"Transaktion assoziiert sein. Wie oben bereits erwähnt, werden verschachtelte "
+"Transaktionen nicht unterstützt."
+
+#. Tag: para
+#: Transactions.xml:57
+#, no-c-format
+msgid ""
+"Each transaction context is encapsulated by a Transaction object, which can "
+"be used to perform operations which are specific to the target transaction, "
+"regardless of the calling thread’s transaction context."
+msgstr ""
+"Jeder Transaktionskontext ist gekapselt durch ein Transaktionsobjekt, "
+"welches zum Ausführen von Operationen benutzt werden kann, die spezifisch "
+"für die Zieltransaktion sind, ungeachtet des Transaktionskontextes des "
+"aufrufenden Threads."
+
+#. Tag: para
+#: Transactions.xml:60
+#, no-c-format
+msgid ""
+"The <methodname>begin</methodname> method of "
+"<interfacename>TransactionManager</interfacename> starts a new top-level "
+"transaction and associates the transaction context with the calling thread. "
+"If the calling thread is already associated with a transaction then it "
+"throws the <code>NotSupportedException</code>."
+msgstr ""
+"Die <methodname>begin</methodname>-Methode des "
+"<interfacename>TransactionManagers</interfacename> startet eine neue "
+"Transaktion oberster Ebene, und assoziiert den Transaktionskontext mit dem "
+"aufrufenden Thread. Falls der aufrufende Thread bereits mit einer "
+"Transaktion assoziiert ist, wird die <code>NotSupportedException</code> "
+"geworfen."
+
+#. Tag: para
+#: Transactions.xml:63
+#, no-c-format
+msgid ""
+"The <methodname>getTransaction</methodname> method returns the Transaction "
+"object that represents the transaction context currently associated with the "
+"calling thread. This object can be used to perform various operations on the "
+"target transaction, described later."
+msgstr ""
+"Die <methodname>getTransaction</methodname>-Methode gibt das "
+"Transaktionsobjekt zurück, welches den Transaktionskontext repräsentiert, "
+"der derzeit mit dem aufrufenden Thread assoziiert ist. Dieses Objekt kann "
+"verwendet werden, um verschiedene Operationen auf der Zieltransaktion "
+"auszuführen, wie später beschrieben."
+
+#. Tag: para
+#: Transactions.xml:66
+#, no-c-format
+msgid ""
+"The commit method is used to complete the transaction currently associated "
+"with the calling thread. After it returns, the calling thread is associated "
+"with no transaction. If commit is called when the thread is not associated "
+"with any transaction context, the TM throws an exception. In some "
+"implementation, the commit operation is restricted to the transaction "
+"originator only. If the calling thread is not allowed to commit the "
+"transaction, the TM throws an exception. JBossJTA does not currently impose "
+"any restriction on the ability of threads to terminate transactions."
+msgstr ""
+"Die \"commit\"-Methode wird verwendet, um die derzeit mit dem aufrufenden "
+"Thread assoziierte Transaktion abzuschließen. Nach Rückkehr ist der "
+"aufrufende Thread mit keinem Transaktionkontext assoziiert. Falls \"commit\" "
+"aufgerufen wird, wenn der Thread mit keinem Transaktionskontext assoziiert "
+"ist, wirft der Transaktionsmanager eine Ausnahme. In manchen "
+"Implementierungen ist die \"commit\"-Operation ausschließlich beschränkt auf "
+"den Originator der Transaktion. Falls der aufrufende Thread die Transaktion "
+"nicht festschreiben darf, wirft der Transaktionsmanager eine Ausnahme. "
+"JBossJTA beschränkt derzeit nicht die Fähigkeit von Threads, Transaktionen "
+"abzuschließen."
+
+#. Tag: para
+#: Transactions.xml:69
+#, no-c-format
+msgid ""
+"The <methodname>rollback</methodname> method is used to rollback the "
+"transaction associated with the current thread. After the "
+"<methodname>rollback</methodname> method completes, the thread is associated "
+"with no transaction."
+msgstr ""
+"Die <methodname>rollback</methodname>-Methode wird verwendet, um eine mit "
+"dem aktuellen Thread assoziierte Transaktion zurückzusetzen. Nachdem die "
+"<methodname>rollback</methodname>-Methode abgeschlossen wurde, ist der "
+"Thread mit keiner Transaktion assoziiert."
+
+#. Tag: para
+#: Transactions.xml:73
+#, no-c-format
+msgid ""
+"In a multi-threaded environment it is possible that multiple threads are "
+"active within the same transaction. If checked transaction semantics have "
+"been disabled, or the transaction times out, then it is possible for a "
+"transaction to be terminated by a thread other than the one that created it. "
+"In this case, it is often important that this information is communicated to "
+"the creator. JBossTS does this during commit or rollback by throwing "
+"<code>IllegalStateException</code>."
+msgstr ""
+"In einer Multi-Thread-Umgebung ist es möglich, dass mehrere Threads "
+"innerhalb derselben Transaktion aktiv sind. Falls das Prüfen der "
+"Transaktionssemantik deaktiviert wurde, oder die Transaktion den Timeout "
+"überschreitet, ist es möglich, dass eine Transaktion durch einen anderen "
+"Thread beendet wird, als durch den, der sie erstellt hat. In diesem Fall ist "
+"es oft wichtig, dass diese Information dem Urheber mitgeteilt wird. JBossTS "
+"tut dies während des Festschreibens oder Zurücksetzens durch Werfen einer "
+"<code>IllegalStateException</code>."
+
+#. Tag: title
+#: Transactions.xml:78
+#, no-c-format
+msgid "Suspending and resuming a transaction"
+msgstr "Anhalten und Fortsetzen einer Transaktion"
+
+#. Tag: para
+#: Transactions.xml:79
+#, no-c-format
+msgid ""
+"The JTA supports the concept of a thread temporarily suspending and resuming "
+"transactions to enable it to perform non-transactional work. The suspend "
+"method is called to temporarily suspend the current transaction that is "
+"associated with the calling thread, i.e., so that the thread is no longer "
+"operating within its scope. If the thread is not associated with any "
+"transaction, a null object reference is returned; otherwise, a valid "
+"<code>Transaction</code> object is returned. The <code>Transaction</code> "
+"object can later be passed to the resume method to reinstate the transaction "
+"context."
+msgstr ""
+"Die JTA unterstützt das Konzept eines Threads, der Transaktionen "
+"vorübergehend anhält und fortsetzt, um ihm das Ausführen von nicht-"
+"transaktionaler Arbeit zu ermöglichen. Die \"suspend\"-Methode wird "
+"aufgerufen, um die aktuelle, mit dem aufrufenden Thread assoziierte "
+"Transaktion vorübergehend anzuhalten, so dass der Thread nicht länger "
+"innerhalb ihres Scopes operiert. Falls der Thread mit keiner Transaktion "
+"assoziiert ist, wird eine Null-Objekt-Referenz zurückgegeben, andernfalls "
+"wird ein gültiges <code>Transaction</code>-Objekt zurückgegeben. Das "
+"<code>Transaction</code>-Objekt kann später an die \"resume\"-Methode "
+"übergeben werden, um den Transaktionskontext wieder weiterzuführen."
+
+#. Tag: para
+#: Transactions.xml:83
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method associates the specified "
+"transaction context with the calling thread. If the transaction specified is "
+"a valid transaction, the transaction context is associated with the calling "
+"thread; otherwise, the thread is associated with no transaction."
+msgstr ""
+"Die <methodname>resume</methodname>-Methode assoziiert den spezifizierten "
+"Transaktionskontext mit dem aufrufenden Thread. Falls die spezifizierte "
+"Transaktion eine gültige Transaktion ist, wird der Transaktionskontext mit "
+"dem aufrufenden Thread assoziiert, andernfalls wird der Thread mit keiner "
+"Transaktion assoziiert."
+
+#. Tag: para
+#: Transactions.xml:87
+#, no-c-format
+msgid ""
+"If <methodname>resume</methodname> is invoked when the calling thread is "
+"already associated with another transaction, the Transaction Manager throws "
+"the <code>IllegalStateException</code> exception."
+msgstr ""
+"Falls <methodname>resume</methodname> aufgerufen wird, wenn der aufrufende "
+"Thread bereits mit einer anderen Transaktion assoziiert ist, wirft der "
+"Transaktionsmanager die <code>IllegalStateException</code>-Ausnahme."
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+
+#. Tag: para
+#: Transactions.xml:93
+#, no-c-format
+msgid ""
+"Some Transaction Manager implementations allow a suspended transaction to be "
+"resumed by a different thread. This feature is not required by JTA, but "
+"JBossJTA does support this."
+msgstr ""
+"Manche Implementierungen von Transaktionsmanagern erlauben das Fortsetzen "
+"einer angehaltenen Transaktion durch einen anderen Thread. Dieses Feature "
+"wird von JTA nicht benötigt, wird aber von JBossJTA unterstützt."
+
+#. Tag: para
+#: Transactions.xml:97
+#, no-c-format
+msgid ""
+"When a transaction is suspended the application server must ensure that the "
+"resources in use by the application are no longer registered with the "
+"suspended transaction. When a resource is de-listed this triggers the "
+"Transaction Manager to inform the resource manager to disassociate the "
+"transaction from the specified resource object. When the application’s "
+"transaction context is resumed, the application server must ensure that the "
+"resources in use by the application are again enlisted with the transaction. "
+"Enlisting a resource as a result of resuming a transaction triggers the "
+"Transaction Manager to inform the resource manager to re-associate the "
+"resource object with the resumed transaction."
+msgstr ""
+"Wenn eine Transaktion angehalten wird, muss der Anwendungsserver "
+"sicherstellen, dass die von der Anwendung verwendeten Ressourcen nicht mehr "
+"bei der angehaltenen Transaktion registriert sind. Wenn eine Ressource "
+"ausgetragen wird, veranlasst dies den Transaktionsmanager dazu, den "
+"Ressourcenmanager dazu aufzufordern, die Transaktion vom spezifizierten "
+"Ressourcenobjekt zu disassoziieren. Wenn der Transaktionskontext einer "
+"Anwendung fortgesetzt wird, muss der Anwendungsserver sicherstellen, dass "
+"die von der Anwendung genutzten Ressourcen wieder bei der Transaktion "
+"eingetragen sind. Das Eintragen einer Ressource infolge des Fortsetzens "
+"einer Transaktion veranlasst den Transaktionsmanager dazu, den "
+"Ressourcenmanager dazu aufzufordern, das Ressourcenobjekt wieder mit der "
+"fortgesetzten Transaktion zu assoziieren."
+
+#. Tag: title
+#: Transactions.xml:101
+#, no-c-format
+msgid "The Transaction interface"
+msgstr "Die Transaktionsschnittstelle"
+
+#. Tag: para
+#: Transactions.xml:102
+#, no-c-format
+msgid ""
+"The <interfacename>Transaction</interfacename> interface allows operations "
+"to be performed on the transaction associated with the target object. Every "
+"top-level transaction is associated with one <code>Transaction</code> object "
+"when the transaction is created. The <code>Transaction</code> object can be "
+"used to:"
+msgstr ""
+"Die <interfacename>Transaction</interfacename>-Schnittstelle ermöglicht das "
+"Ausführen von Operationen auf der mit dem Zielobjekt assoziierten "
+"Transaktion. Jede Transaktion oberster Ebene wird mit einem "
+"<code>Transaction</code>-Objekt assoziiert, wenn die Transaktion erstellt "
+"wird. Das <code>Transaction</code>-Objekt kann verwendet werden zum:"
+
+#. Tag: para
+#: Transactions.xml:108
+#, no-c-format
+msgid "Enlist the transactional resources in use by the application."
+msgstr ""
+"Eintragen der transaktionalen Ressourcen, die von der Anwendung verwendet "
+"werden."
+
+#. Tag: para
+#: Transactions.xml:113
+#, no-c-format
+msgid "Register for transaction synchronization call backs."
+msgstr "Registrieren für Call Backs zur Transaktionssynchronisation."
+
+#. Tag: para
+#: Transactions.xml:118
+#, no-c-format
+msgid "Commit or rollback the transaction."
+msgstr "Festschreiben oder Zurücksetzen der Transaktion."
+
+#. Tag: para
+#: Transactions.xml:123
+#, no-c-format
+msgid "Obtain the status of the transaction."
+msgstr "Beziehen des Transaktionszustands."
+
+#. Tag: para
+#: Transactions.xml:128
+#, no-c-format
+msgid ""
+"The <methodname>commit</methodname> and <methodname>rollback</methodname> "
+"methods allow the target object to be committed or rolled back. The calling "
+"thread is not required to have the same transaction associated with the "
+"thread. If the calling thread is not allowed to commit the transaction, the "
+"transaction manager throws an exception. At present JBossJTA does not impose "
+"restrictions on threads terminating transactions."
+msgstr ""
+"Die <methodname>commit</methodname> und <methodname>rollback</methodname>-"
+"Methoden ermöglichen ein Festschreiben oder Zurücksetzen des Zielobjekts. Es "
+"ist nicht notwendig, dass der aufrufende Thread dieselbe Transaktion mit dem "
+"Thread assoziiert hat. Falls der aufrufende Thread die Transaktion nicht "
+"festschreiben darf, wirft der Transaktionsmanager eine Ausnahme. JBossJTA "
+"beschränkt derzeit nicht die Fähigkeit von Threads, Transaktionen "
+"abzuschließen."
+
+#. Tag: title
+#: Transactions.xml:132
+#, no-c-format
+msgid "Resource enlistment"
+msgstr "Eintragen von Ressourcen"
+
+#. Tag: para
+#: Transactions.xml:133
+#, no-c-format
+msgid ""
+"Transactional resources such as database connections are typically managed "
+"by the application server in conjunction with some resource adapter and "
+"optionally with connection pooling optimization. In order for an external "
+"transaction manager to co-ordinate transactional work performed by the "
+"resource managers, the application server must enlist and de-list the "
+"resources used in the transaction. These resources (participants) are "
+"enlisted with the transaction so that they can be informed when the "
+"transaction terminates, for example, are driven through the two-phase commit "
+"protocol."
+msgstr ""
+"Transaktionale Ressourcen wie Datenbankverbindungen werden in der Regel "
+"gesteuert durch den Anwendungsserver in Verbindung mit einem "
+"Ressourcenadapter sowie optional mit Verbinduns-Pooling-Optimierung. Damit "
+"ein externer Transaktionsmanager transaktionale, vom Ressourcenmanager "
+"ausgeführte Arbeit koordiniert, muss der Anwendungsserver die in der "
+"Transaktion genutzten Ressourcen ein- und austragen. Diese Ressourcen "
+"(Teilnehmer) werden bei der Transaktion eingetragen, so dass sie darüber "
+"informiert werden können, wenn die Transaktion abschließt und z. B. durch "
+"das zwei-Phasen Festschreibungsprotokoll geführt werden können."
+
+#. Tag: para
+#: Transactions.xml:137
+#, no-c-format
+msgid ""
+"As stated previously, the JTA is much more closely integrated with the XA "
+"concept of resources than the arbitrary objects. For each resource in-use by "
+"the application, the application server invokes the "
+"<methodname>enlistResource</methodname> method with an <code>XAResource</"
+"code> object which identifies the resource in use. See for details on how "
+"the implementation of the <code>XAResource</code> can affect recovery in the "
+"event of a failure."
+msgstr ""
+"Wie zuvor erwähnt, ist JTA viel enger integriert mit dem XA-Konzept von "
+"Ressourcen als die arbiträren Objekte. Für jede von der Anwendung benutzte "
+"Ressource ruft der Anwendungsserver die <methodname>enlistResource</"
+"methodname>-Methode auf mit einem <code>XAResource</code>-Objekt, welches "
+"die verwendete Ressource identifiziert. Konsultieren Sie die das Handbuch "
+"für Einzelheiten darüber, wie sich eine Implementierung der "
+"<code>XAResource</code> auf die Recovery im Fehlerfall auswirken kann."
+
+#. Tag: para
+#: Transactions.xml:140
+#, no-c-format
+msgid ""
+"The enlistment request results in the transaction manager informing the "
+"resource manager to start associating the transaction with the work "
+"performed through the corresponding resource. The transaction manager is "
+"responsible for passing the appropriate flag in its <methodname>XAResource."
+"start</methodname> method call to the resource manager."
+msgstr ""
+"Die Anfrage zum Eintragen veranlasst den Transaktionsmanager dazu, den "
+"Ressourcenmanager aufzufordern, die Transaktion mit der Arbeit zu "
+"assoziieren, die durch die entsprechende Ressource ausgeführt wird. Der "
+"Transaktionsmanager ist dafür verantwortlich, das passende Flag in seinem "
+"<methodname>XAResource.start</methodname>-Methodenaufruf an den "
+"Ressourcenmanager zu übergeben."
+
+#. Tag: para
+#: Transactions.xml:143
+#, no-c-format
+msgid ""
+"The <methodname>delistResource</methodname> method is used to disassociate "
+"the specified resource from the transaction context in the target object. "
+"The application server invokes the method with the two parameters: the "
+"<code>XAResource</code> object that represents the resource, and a flag to "
+"indicate whether the operation is due to the transaction being suspended "
+"(TMSUSPEND), a portion of the work has failed (TMFAIL), or a normal resource "
+"release by the application (TMSUCCESS)."
+msgstr ""
+"Die <methodname>delistResource</methodname>-Methode wird verwendet, um die "
+"spezifizierte Ressource vom Transaktionskontext des Zielobjekts zu "
+"disassoziieren. Der Anwendungsserver ruft die Methode auf mit zwei "
+"Parametern: dem <code>XAResource</code>-Objekt, das die Ressource "
+"repräsentiert, und einem Flag um anzuzeigen, ob die Operation ausgeführt "
+"wird aufgrund eines Anhaltens der Transaktion (TMSUSPEND), weil ein Teil der "
+"Arbeit fehlschlug (TMFAIL), oder wegen einer normalen Freigabe der Ressource "
+"durch die Anwendung (TMSUCCESS)."
+
+#. Tag: para
+#: Transactions.xml:146
+#, no-c-format
+msgid ""
+"The de-list request results in the transaction manager informing the "
+"resource manager to end the association of the transaction with the target "
+"<code>XAResource</code>. The flag value allows the application server to "
+"indicate whether it intends to come back to the same resource whereby the "
+"resource states must be kept intact. The transaction manager passes the "
+"appropriate flag value in its <methodname>XAResource.end</methodname> method "
+"call to the underlying resource manager."
+msgstr ""
+"Der Aufruf zum Austragen veranlasst den Transaktionsmanager dazu, den "
+"Ressourcenmanager dazu aufzufordern, die Assoziierung der Transaktion mit "
+"dem Ziel <code>XAResource</code> zu beenden. Der Flag-Wert ermöglicht es der "
+"Anwendung anzuzeigen, ob es beabsichtigt zu derselben Ressource "
+"zurückzukehren, in welchem Fall die Ressourcenzustände intakt gehalten "
+"werden müssten. Der Transaktionsmanager übergibt den entsprechenden Flag-"
+"Wert in seinem <methodname>XAResource.end</methodname>-Methodenaufruf an den "
+"zugrunde liegenden Ressourcenmanager."
+
+#. Tag: title
+#: Transactions.xml:150
+#, no-c-format
+msgid "Transaction synchronization"
+msgstr "Transaktionssynchronisation"
+
+#. Tag: para
+#: Transactions.xml:151
+#, no-c-format
+msgid ""
+"Transaction synchronization allows the application server to be notified "
+"before and after the transaction completes. For each transaction started, "
+"the application server may optionally register a Synchronization call back "
+"object to be invoked by the transaction manager:"
+msgstr ""
+"Transaktionssynchronisation erlaubt es dem Anwendungsserver, benachrichtigt "
+"zu werden, bevor und nachdem die Transaktion abschließt. Für jede gestartete "
+"Transaktion kann der Anwendungsserver optional ein Call-Back-Objekt zur "
+"Synchronisation registrieren, welches vom Transaktionsmanager aufgerufen "
+"wird:"
+
+#. Tag: para
+#: Transactions.xml:157
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method is called prior to the "
+"start of the two-phase transaction complete process. This call is executed "
+"in the same transaction context of the caller who initiates the "
+"<methodname>TransactionManager.commit</methodname> or the call is executed "
+"with no transaction context if <methodname>Transaction.commit</methodname> "
+"is used."
+msgstr ""
+"Die <methodname>beforeCompletion</methodname>-Methode wird aufgerufen vor "
+"dem Start des zwei-Phasen Transaktionsabschlussprozesses. Dieser Aufruf wird "
+"im selben Transaktionskontext des Aufrufers ausgeführt, der den "
+"<methodname>TransactionManager.commit</methodname> initiiert hat, oder der "
+"Aufruf wird ohne Transaktionskontext ausgeführt, falls "
+"<methodname>Transaction.commit</methodname> verwendet wird."
+
+#. Tag: para
+#: Transactions.xml:162
+#, no-c-format
+msgid ""
+"The <methodname>afterCompletion</methodname> method is called after the "
+"transaction has completed. The status of the transaction is supplied in the "
+"parameter. This method is executed without a transaction context."
+msgstr ""
+"Die <methodname>afterCompletion</methodname>-Methode wird aufgerufen, "
+"nachdem die Transaktion abgeschlossen wurde. Der Zustand der Transaktion "
+"wird im Parameter geliefert. Diese Methode wird ohne Transaktionskontext "
+"ausgeführt."
+
+#. Tag: title
+#: Transactions.xml:168
+#, no-c-format
+msgid "Transaction equality"
+msgstr "Gleichheit von Transaktionen"
+
+#. Tag: para
+#: Transactions.xml:169
+#, no-c-format
+msgid ""
+"The transaction manager implements the Transaction object’s equals method to "
+"allow comparison between the target object and another Transaction object. "
+"The equals method should return true if the target object and the parameter "
+"object both refer to the same global transaction."
+msgstr ""
+"Der Transaktionsmanager implementiert die \"equals\"-Methode des "
+"Transaktionsobjekts, um einen Vergleich zwischen dem Zielobjekt und einem "
+"anderen Transaktionsobjekt zu ermöglichen. Die \"equals\"-Methode sollte "
+"\"true\" zurückgeben, wenn das Zielobjekt und das Parameterobjekt beide auf "
+"dieselbe globale Transaktion verweisen."
+
+#. Tag: screen
+#: Transactions.xml:173
+#, no-c-format
+msgid ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
+msgstr ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/de-DE/Using_JBossJTA_in_Application_Servers.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,283 @@
+# translation of Author_Group.po to
+# Language de-DE translations for package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-15 18:10+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \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
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr "Benutzung von JBossJTA in Anwendungsservern"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr "JBoss Anwendungsserver"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:10
+#, no-c-format
+msgid "Service Configuration"
+msgstr "Dienstekonfiguration"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:11
+#, no-c-format
+msgid ""
+"The JBoss Transaction Service is configured primarily via the XML files "
+"stored in the etc directory, but when run as a JBOSS service there are a "
+"number of configurable attributes available. They are as follows:"
+msgstr ""
+"Der JBoss-Transaktionsdienst wird hauptsächlich mittels der XML-Dateien "
+"konfiguriert, welche im etc-Verzeichnis gespeichert sind, aber wenn er als "
+"JBOSS-Dienst betrieben wird, ist eine Anzahl von konfigurierbaren Attributen "
+"verfügbar. Diese lauten wie folgt:"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:17
+#, no-c-format
+msgid ""
+"TransactionTimeout – The default transaction timeout to be used for new "
+"transactions. Specified as an integer in seconds."
+msgstr ""
+"TransactionTimeout – Der Standard-Transaktions-Timeout, der auf neue "
+"Transaktionen angewendet wird, angegeben als ganzzahliger Wert in Sekunden."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:22
+#, no-c-format
+msgid ""
+"StatisticsEnabled – This determines whether or not the transaction service "
+"should gather statistical information. This information can then be viewed "
+"using the PerformanceStatistics MBean. Specified as a Boolean. The default "
+"is to not gather this information."
+msgstr ""
+"StatisticsEnabled – Dies legt fest, ob der Transaktionsdienst statistische "
+"Informationen sammeln soll, oder nicht. Diese Informationen können "
+"anschließend eingesehen werden mittels der PerformanceStatistics MBean. "
+"Angegeben als Boolscher Wert. Standardmäßig werden keine Informationen "
+"gesammelt."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:27
+#, no-c-format
+msgid ""
+"PropagateFullContext – This determines whether a full transactional context "
+"is propagated by context importer/exporter. If set to false only the current "
+"transaction context is propagated. If set to true the full transaction "
+"context (including parent transactions) is propagated."
+msgstr ""
+"PropagateFullContext – Dies legt fest, ob ein vollständiger "
+"Transaktionskontext fortgepflanzt wird durch Kontext-Importer/-Exporter. "
+"Falls auf \"false\" gesetzt, wird nur der aktuelle Transaktionskontext "
+"fortgepflanzt. Falls auf \"true\" gesetzt, wird der vollständige "
+"Transaktionskontext (inklusive Parent-Transaktionen) fortgepflanzt."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:32
+#, no-c-format
+msgid ""
+"These attributes are specified as MBean attributes in the jboss-service.xml "
+"file located in the server/all/conf directory, for example:"
+msgstr ""
+"Diese Attribute werden als MBean-Attribute in der jboss-service.xml-Datei "
+"spezifiziert, die sich im Verzeichnis server/all/conf befindet, z. B.:"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:35
+#, no-c-format
+msgid ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+msgstr ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:36
+#, no-c-format
+msgid ""
+"The transaction service is configurable also via the standard JBoss "
+"Transaction Service property files. These are located in the JBossTS install "
+"location under the etc sub-directory."
+msgstr ""
+"Der Transaktionsdienst ist ebenfalls konfigurierbar mithilfe der "
+"Standardeigenschaftsdateien des JBoss-Transaktionsdienstes. Diese befinden "
+"sich im JBossTS-Installationsverzeichnis unter dem etc-Unterverzeichnis."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:39
+#, no-c-format
+msgid ""
+"These files can be edited manually or through JMX. Each property file is "
+"exposed via an object with the name <code>com.arjuna.ts.properties</code> "
+"and an attribute of module where module is equal to the name of the module "
+"to be configured, for example, <code>com.arjuna.ts.properties:module=arjuna</"
+"code>."
+msgstr ""
+"Diese Dateien können manuell bearbeitet werden oder durch JMX. Jede "
+"Eigenschaftsdatei ist offengelegt mittels eines Objekts namens <code>com."
+"arjuna.ts.properties</code> und einem Attribut von Modul, wobei Modul gleich "
+"dem Namen des zu konfigurierenden Moduls ist, z. B. <code>com.arjuna.ts."
+"properties:module=arjuna</code>."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:43
+#, no-c-format
+msgid "Logging"
+msgstr "Protokollierung"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:44
+#, no-c-format
+msgid ""
+"In order to make JBossTS logging semantically consistent with JBossAS, the "
+"TransactionManagerService modifies the level of some log messages. This is "
+"achieved by overriding the value of the <property>com.arjuna.common.util."
+"logger</property> property given in the <filename>jbossjta-properties.xml</"
+"filename> file. Therefore, the value of this property will have no effect on "
+"the logging behaviour when running embedded in JBossAS. By forcing use of "
+"the log4j_releveler logger, the TransactionManagerService causes all INFO "
+"level messages in the transaction code to be modified to behave as DEBUG "
+"messages. Therefore, these messages will not appear in log files if the "
+"filter level is INFO. All other log messages behave as normal."
+msgstr ""
+"Damit JBossTS-Protokollierung semantisch konsistent mit JBossAS sein kann, "
+"modifiziert der Transaktionsmanagerdienst die Ebene einiger "
+"Protokollnachrichten. Dies wird erreicht, indem der in der "
+"<filename>jbossjta-properties.xml</filename>-Datei gelieferte Wert für die "
+"<property>com.arjuna.common.util.logger</property>-Eigenschaft außer Kraft "
+"gesetzt wird. Deshalb hat der Wert dieser Eigenschaft keine Auswirkung auf "
+"das Protokollierungsverhalten, wenn es in JBossAS eingebettet ausgeführt "
+"wird. Indem die Nutzung des log4j_releveler Logger erzwungen wird, bewirkt "
+"der Transaktionsmanagerdienst eine Modifikation aller Nachrichten auf INFO-"
+"Ebene im Transaktions-Code, so dass diese sich wie DEBUG-Nachrichten "
+"verhalten. Aus diesem Grund erscheinen diese Nachrichten nicht in den "
+"Protokolldateien, wenn die Filterebene INFO eingestellt ist. Alle anderen "
+"Protokollnachrichten verhalten sich normal."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:49
+#, no-c-format
+msgid "The services"
+msgstr "Die Dienste"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:50
+#, no-c-format
+msgid ""
+"There is currently one service offered by the JBOSS integration called "
+"TransactionManagerService. Here we shall discuss what this service does."
+msgstr ""
+"Es existiert derzeit ein von der JBOSS-Integration angebotener Dienst namens "
+"Transaktionsmanagerdienst. Hier soll erläutert werden, was dieser Dienst "
+"macht."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:54
+#, no-c-format
+msgid ""
+"The transaction manager service’s main purpose is to ensure the recovery "
+"manager is started. It also binds the JBossTS JTA transaction manager to "
+"java:/TransactionManager name with the JNDI provider. This service depends "
+"upon the existence of the CORBA ORB Service and it must be using JacORB as "
+"the underlying ORB implementation."
+msgstr ""
+"Der Hauptzweck des Transaktionsmanagerdienstes ist es sicherzustellen, dass "
+"der Recovery-Manager gestartet ist. Auch bindet er den JBossTS JTA-"
+"Transaktionsmanager an java:/TransactionManager-Namen mit dem JNDI-Provider. "
+"Dieser Dienst ist davon abhängig, dass der CORBA ORB-Dienst vorhanden ist, "
+"und muss JacORB als die zugrunde liegende ORB-Implementierung verwenden."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:57
+#, no-c-format
+msgid "There are two instances of this service:"
+msgstr "Es gibt zwei Instanzen dieses Dienstes:"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:62
+#, no-c-format
+msgid ""
+"distributed: this uses the JTS enabled transaction manager implementation "
+"and hence supports distributed transactions and recovery. To configure this "
+"use the <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname> class. This is the default configuration."
+msgstr ""
+"verteilt: dies verwendet die JTS-aktivierte "
+"Transaktionsmanagerimplementierung und unterstützt somit verteilte "
+"Transaktionen und Recovery. Um dies zu konfigurieren, verwenden Sie die "
+"<classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</classname>-"
+"Klasse. Dies ist die Standardkonfiguration."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:67
+#, no-c-format
+msgid ""
+"local: this uses the purely local JTA implementation. To configure this use "
+"the <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
+"classname> class."
+msgstr ""
+"lokal: dies verwendet die ausschließlich lokale JTA-Implementierung. Um dies "
+"zu konfigurieren, verwenden Sie die <classname>com.arjuna.ats.jbossatx.jta."
+"TransactionManagerService</classname>-Klasse."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:73
+#, no-c-format
+msgid "Ensuring Transactional Context is Propagated to the Server"
+msgstr ""
+"Sicherstellen der Fortpflanzung von transaktionalem Kontext an den Server"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:74
+#, no-c-format
+msgid ""
+"It is possible to coordinate transactions from a coordinator which is not "
+"located within the JBoss server (e.g. using transactions created by an "
+"external OTS server). To ensure the transaction context is propagated via "
+"JRMP invocations to the server, the transaction propagation context factory "
+"needs to be explicitly set for the JRMP invoker proxy. This is done as "
+"follows:"
+msgstr ""
+"Es ist möglich, Transaktionen zu koordinieren von einem Koordinator, der "
+"nicht innerhalb des JBoss-Servers liegt (z. B. beim Verwenden von "
+"Transaktionen, die von einem externen OTS-Server erstellt wurden). Um "
+"sicherzustellen, dass der Transaktionskontext via JRMP-Aufrufe an den Server "
+"fortgepflanzt wird, muss die Kontext-Factory der Transaktionsfortpflanzung "
+"explizit eingestellt sein für den JRMP Invoker Proxy. Dies wird wie folgt "
+"vorgenommen:"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/An_Introduction_to_the_JTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/An_Introduction_to_the_JTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/An_Introduction_to_the_JTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,154 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr "Introducción a JTA"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr "API de transacciones Java"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:9
+#, no-c-format
+msgid ""
+"The interfaces specified by the many transaction standards are typically too "
+"low-level for most application programmers. Therefore, Sun Microsystems has "
+"specified higher-level interfaces to assist in the development of "
+"distributed transactional applications. Note, these interfaces are still low-"
+"level, and require, for example, the programmer to be concerned with state "
+"management and concurrency for transactional application. In addition, they "
+"are geared more for applications which require XA resource integration "
+"capabilities, rather than the more general resources which the other APIs "
+"allow."
+msgstr ""
+"Las interfaces especificadas por muchos de los estándares de transacciones "
+"usualmente son de un nivel muy bajo para la mayoría de los programadores de "
+"aplicaciones. Por lo tanto, Sun Microsystems ha especificado interfaces de "
+"alto nivel para ayudar en el desarrollo de aplicaciones transaccionales "
+"distribuidas. Observe que esas interfaces aún son de bajo nivel y por lo "
+"tanto requieren, por ejemplo, que el programador se preocupe de la "
+"administración del estado y de la concurrencia para la aplicación "
+"transaccional. Además, están orientados para aquellas aplicaciones que "
+"requieren capacidades de integración de recursosXA, en lugar de recursos más "
+"generales, los cuales son permitidos por otras APIs. "
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:12
+#, no-c-format
+msgid ""
+"With reference to [JTA99], distributed transaction services typically "
+"involve a number of participants:"
+msgstr ""
+"Con referencia a [JTA99], los servicios de transacciones distribuidas "
+"usualmente involucran un número de participantes: "
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:17
+#, no-c-format
+msgid ""
+"Application server: which provides the infrastructure required to support "
+"the application run-time environment which includes transaction state "
+"management, for example, an EJB server."
+msgstr ""
+"Servidor de aplicaciones: proporciona la infraestructura requerida para "
+"soportar el entorno en tiempo de ejecución de la aplicación, el cual incluye "
+"la administració de estado de transacciones, por ejemplo, un servidor EJB. "
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:22
+#, no-c-format
+msgid ""
+"Transaction manager: provides the services and management functions required "
+"to support transaction demarcation, transactional resource management, "
+"synchronisation and transaction context propagation."
+msgstr ""
+"Administrador de transacciones: brinda los servicios y las funciones de "
+"administración requeridas para soportar la demarcación de transacciones, la "
+"administración de recursos transaccionales, sincronización y propagación de "
+"contextos de transacciones."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:27
+#, no-c-format
+msgid ""
+"Resource manager: (through a resource adapter<footnote> <para> A Resource "
+"Adapter is used by an application server or client to connect to a Resource "
+"Manager. JDBC drivers which are used to connect to relational databases are "
+"examples of Resource Adapters. </para> </footnote>) provides the application "
+"with access to resources. The resource manager participates in distributed "
+"transactions by implementing a transaction resource interface used by the "
+"transaction manager to communicate transaction association, transaction "
+"completion and recovery."
+msgstr ""
+"Administrador de recursos: (por medio de un adaptador de recursos <footnote> "
+"<para> Un adaptador de recursos es utilizado por un servidor de aplicaciones "
+"o un cliente para conectarse al administrador de recursos. Los controladores "
+"JDBC que se utilizan para conectarse a las bases de datos relacionales son "
+"ejemplos de adaptadores de recursos. </para> </footnote>) proporciona a la "
+"aplicación acceso a los recursos. El administrador de recursos participa en "
+"transacciones distribuidas implementando una interfaz de recursos de "
+"transacción que el administrador de transacciones utiliza para comunicar la "
+"asociación, recuperación y finalización de transacciónes. "
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:36
+#, no-c-format
+msgid ""
+"A communication resource manager (CRM): supports transaction context "
+"propagation and access to the transaction service for incoming and outgoing "
+"requests."
+msgstr ""
+"Administrador de recursos de comunicación: soporta la propagación del "
+"contexto de transacciones y el acceso al servicio de transacciones para "
+"peticiones entrantes y salientes. "
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:41
+#, no-c-format
+msgid ""
+"From the transaction manager’s perspective, the actual implementation of the "
+"transaction services does not need to be exposed; only high-level interfaces "
+"need to be defined to allow transaction demarcation, resource enlistment, "
+"synchronization and recovery process to be driven from the users of the "
+"transaction services. The JTA is a high-level application interface that "
+"allows a transactional application to demarcate transaction boundaries, and "
+"contains also contains a mapping of the X/Open XA protocol."
+msgstr ""
+"Desde la perspectiva de un administrador de transacciones, no es necesario "
+"exponer la implementación real de los servicios de transacciones; solo "
+"necesitan estar definidas las interfaces de alto nivel para permitir la "
+"demarcación de transacciones, el listado de recursos, la sincronización y "
+"recuperación de procesos para que sean dirigidos por los usuarios de los "
+"servicios de transacciones. El JTA es una interfaz de aplicación de alto "
+"nivel que le permite a una aplicación transaccional el demarcar límites de "
+"transacciones y también contiene un mapeo del protocolo XA X/Open. "
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:45
+#, no-c-format
+msgid ""
+"The JTA support provided by JBossJTA is compliant with the 1.0.1 "
+"specification."
+msgstr ""
+"El soporte JTA que JBossJTA proporciona cumple con los requerimientos de la "
+"especificación 1.0.1."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Author_Group.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Author_Group.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,22 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Book_Info.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Book_Info.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,49 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#, fuzzy, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide CP04"
+msgstr "Manual de programadores JTA de transacciones JBoss"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "para uso con JBoss Enterprise Application Platform 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+"Este libro aborda las transacciones JTA desde el punto de vista del "
+"programador"
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Configuring_JBossJTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Configuring_JBossJTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Configuring_JBossJTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,144 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr "Configuración de JBossJTA"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:8
+#, no-c-format
+msgid "Configuring options"
+msgstr "Opciones de configuración"
+
+#. Tag: para
+#: Configuring_JBossJTA.xml:9
+#, no-c-format
+msgid ""
+"The following table shows the configuration features, with default values "
+"shown in italics. For more detailed information, the relevant section "
+"numbers are provided."
+msgstr ""
+"La siguiente tabla muestra las características de la configuración y los "
+"valores predeterminados aparecen en letra cursiva. Allí encontrará los "
+"números relevantes para cada sección para obtener información más detallada. "
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:13
+#, no-c-format
+msgid "JBossJTA configuration options."
+msgstr "Opciones de configuración de JBossJTA "
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:17
+#, no-c-format
+msgid "Configuration Name"
+msgstr "Nombre de la configuración"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:20
+#, no-c-format
+msgid "Possibile Values"
+msgstr "Valores posibles"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:23
+#, no-c-format
+msgid "Relevant Section"
+msgstr "Sección relevante"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:30
+#, no-c-format
+msgid "com.arjuna.ats.jta.supportSubtransactions"
+msgstr "com.arjuna.ats.jta.supportSubtransactions"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr "YES/NO"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr "com.arjuna.ats.jta.jtaTMImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:43
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr "com.arjuna.ats.jta.jtaUTImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:53
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr "com.arjuna.ats.jta.xaBackoffPeriod"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr "com.arjuna.ats.jdbc.isolationLevel"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr "Cualquier nivel de aislamiento JDBC soportado. "
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr "true/false"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr "Capítulo 3"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Examples.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Examples.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Examples.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,834 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr "Ejemplos"
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr "Ejemplo de JDBC"
+
+#. Tag: para
+#: Examples.xml:9
+#, no-c-format
+msgid ""
+"The following code illustrates many of the points described above (note that "
+"for simplicity, much error checking code has been remove). This example "
+"assumes that you are using the transactional JDBC driver provided with "
+"JBossTS. For details about how to configure and use this driver see the "
+"previous Chapter."
+msgstr ""
+"El siguiente código ilustra muchos de los puntos descritos anteriormente "
+"(observe que por simplicidad se ha eliminado el código de verificación de "
+"errores). Este ejemplo asume que está utilizando el controlador JDBC "
+"transaccional que JBossTS proporciona. Para obtener mayores detalles sobre "
+"cómo configurar y cómo utilizar este controlador consulte el capítulo "
+"anterior. "
+
+#. Tag: screen
+#: Examples.xml:12
+#, no-c-format
+msgid ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+msgstr ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+
+#. Tag: title
+#: Examples.xml:16
+#, no-c-format
+msgid "Failure recovery example"
+msgstr "Ejemplo de recuperación de fallos"
+
+#. Tag: para
+#: Examples.xml:17
+#, no-c-format
+msgid ""
+"This class implements the <interfacename>XAResourceRecovery</interfacename> "
+"interface for <code>XAResources</code>. The parameter supplied in "
+"setParameters can contain arbitrary information necessary to initialize the "
+"class once created. In this instance it contains the name of the property "
+"file in which the db connection information is specified, as well as the "
+"number of connections that this file contains information on (separated "
+"by ;)."
+msgstr ""
+"Esta clase implementa la interfaz <interfacename>XAResourceRecovery</"
+"interfacename> para <code>XAResources</code>. El parámetro que se "
+"proporciona en setParameters puede contener información arbitraria necesaria "
+"para inicializar la clase una vez creada. Esta instancia contiene el nombre "
+"del archivo de propiedades en el cual se especifica la información sobre la "
+"conexión de la base de datos, así como el número de conexiones sobre las "
+"cuales este archivo contiene información (separados por ;)."
+
+#. Tag: para
+#: Examples.xml:21
+#, no-c-format
+msgid ""
+"This is only an <emphasis>example</emphasis> of the sorts of things an "
+"<code>XAResourceRecovery</code> implementer could do. This implementation "
+"uses a property file that is assumed to contain sufficient information to "
+"recreate connections used during the normal run of an application so that we "
+"can perform recovery on them. It is not recommended that information such as "
+"user name and password appear in such a raw text format as it opens up a "
+"potential security hole."
+msgstr ""
+"Este es solo un <emphasis>ejemplo</emphasis> del tipo de cosa que un "
+"implementador <code>XAResourceRecovery</code> puede hacer. Esta "
+"implementación utiliza un archivo de propiedades que se asume que contiene "
+"suficiente información para recrear conexiones utilizadas durante la "
+"ejecución normal de una aplicación de manera que podamos realizar la "
+"recuperación en ellos. No se recomienda que información tal como el nombre "
+"de usuario y la contraseña aparezcan en formato de texto crudo ya que "
+"representa un potencial riesgo de seguridad."
+
+#. Tag: para
+#: Examples.xml:25
+#, no-c-format
+msgid ""
+"The db parameters specified in the property file are assumed to be in the "
+"format:"
+msgstr ""
+"Se asume que los parámetros de la base de datos especificados en el archivo "
+"de propiedades están en el formato: "
+
+#. Tag: para
+#: Examples.xml:30
+#, no-c-format
+msgid "DB_x_DatabaseURL="
+msgstr "DB_x_DatabaseURL="
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr "DB_x_DatabaseUser="
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr "DB_x_DatabasePassword="
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr "DB_x_DatabaseDynamicClass="
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr "En donde x es el número de la información de la conexión. "
+
+#. Tag: para
+#: Examples.xml:54
+#, no-c-format
+msgid ""
+"Some error handling code has been removed from this text for ease of "
+"readability purposes."
+msgstr ""
+"Para facilitar la lectura hemos eliminado algo del código de manejo de "
+"errores. "
+
+#. Tag: screen
+#: Examples.xml:58
+#, no-c-format
+msgid ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+msgstr ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+
+#. Tag: para
+#: Examples.xml:59
+#, no-c-format
+msgid ""
+"The class <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> may be used to create a new connection "
+"to the database using the same parameters that were used to create the "
+"initial connection."
+msgstr ""
+"La clase <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> se puede utilizar para crear una nueva "
+"conexión a la base de datos utilizando los mismos parámetros que se "
+"utilizaron para crear la conexión inicial."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
===================================================================
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/JDBC_and_Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/JDBC_and_Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/JDBC_and_Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,1011 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr "JDBC y transacciones"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr "Uso del controlador JDBC transaccional "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:9
+#, no-c-format
+msgid ""
+"JBossJTA supports the construction of both local and distributed "
+"transactional applications which access databases using the JDBC 2.0 APIs. "
+"JDBC 2.0 supports two-phase commit of transactions, and is similar to the XA "
+"X/Open standard. The JDBC 2.0 support is found in the com.arjuna.ats.jdbc "
+"package."
+msgstr ""
+"JBossJTA spporta la construcción de aplicaciones transaccionales locales y "
+"distribuidas, las cuales acceden a las bases de datos utilizando las APIs "
+"JDBC 2.0. JDBC 2.0 soporta el guardar los cambios de transacciones en dos "
+"fases y es similar al estándar XA X/Open. El soporte JDBC 2.0 se encuentra "
+"en el paquete com.arjuna.ats.jdbc."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:12
+#, no-c-format
+msgid ""
+"The JDBC 2.0 support has been tested with the following drivers and "
+"databases:"
+msgstr ""
+"El soporte JDBC 2.0 ha sido probado con los siguientes controladores y bases "
+"de datos:"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr "Oracle 8.1.6/8.1.7, 9i y el controlador 10g."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr "Controlador nativo MS SQL Server 2000."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:27
+#, no-c-format
+msgid "In the past we have qualified against:"
+msgstr "Anteriormente hemos calificado frente a: "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:32
+#, no-c-format
+msgid "Merant’s Sequelink 5.1 with Oracle 8.1.6"
+msgstr "Sequelink 5.1 de Merant con Oracle 8.1.6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr "Cloudscape 3.6 con la base de datos de Cloudscape."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:42
+#, no-c-format
+msgid ""
+"However, these drivers and databases are no longer part of our supported "
+"platforms. They may continue to work with JBossTS, but we cannot make that "
+"guarantee."
+msgstr ""
+"Sin embargo, estos controladores y bases de datos ya no son parte de "
+"nuestras plataformas soportadas. Pueda que sigan funcionando con JBossTS, "
+"pero no lo podemos garantizar. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:46
+#, no-c-format
+msgid "Managing transactions"
+msgstr "Administración de transacciones"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:47
+#, no-c-format
+msgid ""
+"JBossJTA must be able to associate work performed on a JDBC connection with "
+"a specific transaction. Therefore, implicit transaction propagation and/or "
+"indirect transaction management must be used by applications, i.e., for each "
+"JDBC connection it must be possible for JBossJTA to determine the invoking "
+"thread’s current transaction context."
+msgstr ""
+"JBossJTA debe poder asociar el trabajo realizado en una conexión JDBC con "
+"una transacción en especifico. Por lo tanto, las aplicaciones deben utilizar "
+"la propagación implícita de transacciones y/o la administración indirecta de "
+"transacciones, por ejemplo, para cada conexión JDBC debe ser posible para "
+"JBossJTA el poder determinar el contexto de transacción actual del hilo "
+"invocador. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:52
+#, no-c-format
+msgid "Restrictions"
+msgstr "Restricciones"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:53
+#, no-c-format
+msgid ""
+"The following restrictions are imposed by limitations in the JDBC "
+"specifications and by JBossJTA to ensure that transactional interactions "
+"with JDBC databases can be correctly managed:"
+msgstr ""
+"Las siguientes restricciones son impuestas por limitaciones en las "
+"especificaciones JDBC y por JBossJTA para asegurarse de que las "
+"interacciones transaccionales con bases de datos JDBC se puedan administrar "
+"correctamente:"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:57
+#, no-c-format
+msgid ""
+"Nested transactions are not supported by JDBC 2.0. If an attempt is made to "
+"use a JDBC connection within a subtransaction, JBossJTA will throw a "
+"suitable exception and no work will be allowed on that connection. However, "
+"if you wish to have nested transactions, then you can set the <property>com."
+"arjuna.ats.jta.supportSubtransactions</property> property to YES."
+msgstr ""
+"JDBC 2.0 no soporta las transacciones anidadas. Si trata de utilizar una "
+"conexión JDBC dentro de una subtransacción, JBossJTA presentará la excepción "
+"apropiada y no se permitirá ningún trabajo en esa conexión. Sin embargo, si "
+"desea tener transacciones anidadas entonces puede configurar la propiedad "
+"<property>com.arjuna.ats.jta.supportSubtransactions</property> como YES."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:63
+#, no-c-format
+msgid "Transactional drivers"
+msgstr "Controladores transaccionales"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:64
+#, no-c-format
+msgid ""
+"The JBossJTA approach to incorporating JDBC connections within transactions "
+"is to provide transactional JDBC drivers through which all interactions "
+"occur. These drivers intercept all invocations and ensure that they are "
+"registered with, and driven by, appropriate transactions. There is a single "
+"type of transactional driver through which any JDBC driver can be driven; "
+"obviously if the database is not transactional then ACID properties cannot "
+"be guaranteed. This driver is <code>com.arjuna.ats.jdbc.TransactionalDriver</"
+"code>, which implements the <interfacename>java.sql.Driver</interfacename> "
+"interface."
+msgstr ""
+"El enfoque de JBossJTA para incorporar conexiones JDBC dentro de "
+"transacciones es el proporcionar controladores JDBC transaccionales por "
+"medio de los cuales tengan lugar todas las interacciones. Estos "
+"controladores interceptan todas las invocaciones y se aseguran de que están "
+"registradas y dirigidas por transacciones apropiadas. Solo hay un tipo de "
+"controlador transaccional por medio del cual se puede dirigir cualquier "
+"controlador JDBC; obviamente si la base de datos no es transaccional "
+"entonces no se pueden garantizar las propiedades ACID. Este controlador es "
+"<code>com.arjuna.ats.jdbc.TransactionalDriver</code>, el cual implementa la "
+"interfaz <interfacename>java.sql.Driver</interfacename>."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:68
+#, no-c-format
+msgid "Loading drivers"
+msgstr "Carga de controladores"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:69
+#, no-c-format
+msgid ""
+"The driver may be directly instantiated and used within an application. For "
+"example:"
+msgstr ""
+"El controlador se puede instanciar y utilizar directamente dentro de una "
+"aplicación. Por ejemplo: "
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:73
+#, no-c-format
+msgid "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+msgstr "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:74
+#, no-c-format
+msgid ""
+"They can be registered with the JDBC driver manager (<code>java.sql."
+"DriverManager</code>) by adding them to the Java system properties. The "
+"<property>jdbc.drivers</property> property contains a list of driver class "
+"names, separated by colons, that are loaded by the JDBC driver manager when "
+"it is initialized."
+msgstr ""
+"Pueden ser registrados con el administrador de controladores JDBC "
+"(<code>java.sql.DriverManager</code>) añadiéndolos a las propiedades del "
+"sistema Java. La propiedad <property>jdbc.drivers</property> contiene una "
+"lista de nombres de clase de controladores, separados por comas, que el "
+"administrador de controladores JDBC carga cuando es incializado. "
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:77
+#, no-c-format
+msgid ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+msgstr ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:78
+#, no-c-format
+msgid ""
+"Alternatively, the <methodname>Class.forName()</methodname> method may be "
+"used to load the driver or drivers:"
+msgstr ""
+"Opcionalmente, puede utilizar el método <methodname>Class.forName()</"
+"methodname> para cargar el o los controladores: "
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:82
+#, no-c-format
+msgid ""
+"Calling <methodname>Class.forName()</methodname> will automatically register "
+"the driver with the JDBC driver manager. It is also possible to explicitly "
+"create an instance of the JDBC driver:"
+msgstr ""
+"El llamar a <methodname>Class.forName()</methodname> registrará "
+"automáticamente el controlador con el administrador de controladores JDBC. "
+"Es posible el crear explícitamente una instancia del controlador JDBC:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:85
+#, no-c-format
+msgid ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+msgstr ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:86
+#, no-c-format
+msgid ""
+"When you have loaded a driver, it is available for making a connection with "
+"a DBMS."
+msgstr ""
+"Cuando haya cargado un controlador, está disponible para realizar una "
+"conexión con un DBMS. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:92
+#, no-c-format
+msgid "Connections"
+msgstr "Conexiones"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:93
+#, no-c-format
+msgid ""
+"In this section we shall discuss the notion of transactional JDBC "
+"connections, how they are managed within JBossJTA and the implications on "
+"using them within an application."
+msgstr ""
+"En esta sección vamos a discutir la noción de las conexiones JDBC "
+"transaccionales, la manera en que son administradas dentro de JBossJTA y las "
+"implicaciones al utilizarlas dentro de una aplicación. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:97
+#, no-c-format
+msgid "Making the connection"
+msgstr "Realizar la conexión"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:98
+#, no-c-format
+msgid ""
+"Because JDBC connectivity in JBossJTA works by simply providing a new JDBC "
+"driver, application code can remain relatively the same to that when not "
+"using transactions. Typically, the application programmer need only start "
+"and terminate transactions."
+msgstr ""
+"Ya que la conectividad JDBC en JBossJTA trabaja con simplemente proporcionar "
+"un nuevo controlador JDBC, el código de la aplicación puede permanecer "
+"relativamente igual al de cuando no se utilizan transacciones. Usualmente, "
+"el programador de aplicaciones solo necesita iniciar y terminar las "
+"transacciones. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr "JDBC 2.0"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:104
+#, no-c-format
+msgid ""
+"Before describing the JDBC 2.0 support it is necessary to mention that the "
+"following properties can be set and passed to the JBossJTA driver (they are "
+"all located in the <classname>com.arjuna.ats.jdbc.TransactionalDriver</"
+"classname> class):"
+msgstr ""
+"Antes de describir el soporte JDBC 2.0 es necesario mencionar que se pueden "
+"configurar y pasar las siguientes propiedades al controlador JBossJTA (se "
+"encuentran en la clase <classname>com.arjuna.ats.jdbc.TransactionalDriver</"
+"classname>):"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:110
+#, no-c-format
+msgid ""
+"<property>userName</property>: the user name to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>userName</property>: el nombre de usuario a utilizar al tratar de "
+"conectarse a la base de datos."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:115
+#, no-c-format
+msgid ""
+"<property>password</property>: the password to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>password</property>: la contraseña a utilizar al tratar de "
+"conectarse a la base de datos."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:120
+#, no-c-format
+msgid ""
+"<property>createDb</property>: if set to true, the driver will attempt to "
+"create the database when it connects. This may not be supported by all JDBC "
+"2.0 implementations."
+msgstr ""
+"<property>createDb</property>: si se configura como verdadero, el "
+"controlador tratará de crear la base de datos cuando se conecta. Puede que "
+"esto no sea soportado por todas las implementaciones JDBC 2.0."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:125
+#, no-c-format
+msgid ""
+"<property>dynamicClass</property>: this specifies a class to instantiate to "
+"connect to the database, rather than using JNDI."
+msgstr ""
+"<property>dynamicClass</property>: esta especifica una clase a instanciar "
+"para conectarse a la base de datos en vez de utilizar JNDI."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr "XADataSources"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:132
+#, no-c-format
+msgid ""
+"JDBC 2.0 connections are created from appropriate DataSources. Those "
+"connections which must participate within distributed transactions are "
+"obtained from <code>XADataSources</code>. Therefore, when using a JDBC 2.0 "
+"driver, JBossJTA will use the appropriate DataSource whenever a connection "
+"to the database is made. It will then obtain <code>XAResources</code> and "
+"register them with the transaction via the JTA interfaces. It is these "
+"<code>XAResources</code> which the transaction service will use when the "
+"transaction terminates in order to drive the database to either commit or "
+"rollback the changes made via the JDBC connection."
+msgstr ""
+"Las conexiones JDBC 2.0 se crean de DataSources apropiadas. Esas conexiones, "
+"las cuales deben participar dentro de las transacciones distribuidas se "
+"obtienen de <code>XADataSources</code>. Por lo tanto, cuando se utiliza un "
+"controlador JDBC 2.0, JBossJTA utilizará el DataSource apropiado cuando se "
+"realice una conexión a la base de datos. Luego obtendrá <code>XAResources</"
+"code> y los registrará con la transacción por medio de las interfaces JTA. "
+"Estos <code>XAResources</code> son los que utilizará el servicio de "
+"transacciones cuando la transacción termine con el fin de dirigir la base de "
+"datos a que guarde o a que deshaga los cambios realizados a través de la "
+"conexión JDBC."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:136
+#, no-c-format
+msgid ""
+"There are two ways in which the JBossJTA JDBC 2.0 support can obtain "
+"<code>XADataSources</code>. These will be explained in the following "
+"sections. Note, for simplicity we shall assume that the JDBC 2.0 driver is "
+"instantiated directly by the application."
+msgstr ""
+"Hay dos manera en las que el soporte JBossJTA JDBC 2.0 puede obtener "
+"<code>XADataSources</code>. Las explicaremos más adelante en las siguientes "
+"secciones. Observe que por simplicidad vamos a asumir que el controlador "
+"JDBC 2.0 es instanciado directamente por la aplicación. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr "Interfaz de nombrado y directorio Java (JNDI)"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:141
+#, no-c-format
+msgid ""
+"In order to allow a JDBC driver to use arbitrary DataSources without having "
+"to know specific details about their implementations, DataSources are "
+"typically obtained from JNDI. A specific (XA)DataSource can be created and "
+"registered with an appropriate JNDI implementation, and the application (or "
+"JDBC driver) can later bind to and use it. Since JNDI only allows the "
+"application to see the (XA)DataSource as an instance of the interface (for "
+"example, <property>javax.sql.XADataSource</property>) rather than as an "
+"instance of the implementation class (for example, <property>com.mydb."
+"myXADataSource</property>), the application is not tied at build time to "
+"only use a specific (XA)DataSource implementation."
+msgstr ""
+"Con el fin de permitirle a un controlador JDBC que utilice DataSources "
+"arbitrarios sin tener que saber detalles especificos sobre sus "
+"implementaciones, los DataSources usualmente se obtienen de JNDI. Se puede "
+"crear y registrar un (XA)DataSource especifico con una implementación JNDI "
+"apropiada y la aplicación (o controlador JDBC) se puede vincular y "
+"utilizarlo. Ya que JNDI solo permite que la aplicación vea el (XA)DataSource "
+"como una instancia de la interfaz (por ejemplo, <property>javax.sql."
+"XADataSource</property>) en vez de una instancia de la clase de "
+"implementación (por ejemplo, <property>com.mydb.myXADataSource</property>), "
+"la aplicación no está amarrada en tiempo de contrucción a solo tener que "
+"utilizar una implementación (XA)DataSource específica. "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:145
+#, no-c-format
+msgid ""
+"To get the <classname>TransactionalDriver</classname> class to use a JNDI "
+"registered <code>XADataSource</code> it is first necessary to create the "
+"<code>XADataSource</code> instance and store it in an appropriate JNDI "
+"implementation. Details of how to do this can be found in the JDBC 2.0 "
+"tutorial available at JavaSoft. An example is show below:"
+msgstr ""
+"Para hacer que la clase <classname>TransactionalDriver</classname> utilice "
+"un JNDI registrado <code>XADataSource</code> primero es necesario crear la "
+"instancia <code>XADataSource</code> y almacenarla en una implementación JNDI "
+"apropiada. Encontrará más detalles de cómo lograr esto en el tutorial de "
+"JDBC 2.0 disponible en JavaSoft. Este es un ejemplo:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:148
+#, no-c-format
+msgid ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+msgstr ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:149
+#, no-c-format
+msgid ""
+"Where the <property>Context.INITIAL_CONTEXT_FACTORY</property> property is "
+"the JNDI way of specifying the type of JNDI implementation to use."
+msgstr ""
+"En donde la propiedad <property>Context.INITIAL_CONTEXT_FACTORY</property> "
+"es la forma JNDI de especificar el tipo de implementación JNDI a utilizar."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:152
+#, no-c-format
+msgid ""
+"Then the application must pass an appropriate connection URL to the JDBC 2.0 "
+"driver:"
+msgstr ""
+"Luego la aplicación debe pasar una URL de conexión apropiada al controlador "
+"JDBC 2.0:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:155
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:156
+#, no-c-format
+msgid ""
+"The JNDI URL must be pre-pended with jdbc:arjuna: in order for the "
+"<code>ArjunaJDBC2Driver</code> to recognise that the DataSource must "
+"participate within transactions and be driven accordingly."
+msgstr ""
+"A la URL JNDI se le debe poner antes jdbc:arjuna: para que "
+"<code>ArjunaJDBC2Driver</code> pueda reconocer que el DataSource debe "
+"participar dentro de transactions y se le debe dirigir como corresponde."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:160
+#, no-c-format
+msgid "Dynamic class instantiation"
+msgstr "Instanciación de clase dinámica"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:161
+#, no-c-format
+msgid ""
+"Many JDBC 2.0 implementations provide proprietary implementations of "
+"<interfacename>XADataSources</interfacename> that provide non-standard "
+"extensions to the specification. In order to allow the application to remain "
+"isolated from the actual JDBC 2.0 implementation it is using and yet "
+"continue to be able to use these extensions, JBossJTA hides the details of "
+"these proprietary implementations using dynamic class instantiation. In "
+"addition, the use of JNDI is not required when using this mechanism because "
+"the actual implementation of the <interfacename>XADataSource</interfacename> "
+"will be directly instantiated, albeit in a manner which will not tie an "
+"application or driver to a specific implementation. JBossJTA therefore has "
+"several classes which are for specific JDBC 2.0 implementations, and these "
+"can be selected at runtime by the application setting the "
+"<property>dynamicClass</property> property appropriately:"
+msgstr ""
+"Muchas de las implementaciones JDBC 2.0 proporcionan implementaciones de "
+"marcas registradas de <interfacename>XADataSources</interfacename> que "
+"proporcionan extensiones no-estándares para la especificación. Con el fin de "
+"permitir que la aplicación permanezca aislada de la implementación JDBC 2.0 "
+"que está utilizando y aún poder continuar utilizando estas extensiones, "
+"JBossJTA esconde los detalles de estas implementaciones de marcas "
+"registradas utilizando la instanciación de clase dinámica. Además el uso de "
+"JNDI no se requiere cuando utiliza este mecanismo ya que la implementación "
+"real del <interfacename>XADataSource</interfacename> se instanciará "
+"directamente, aunque de una manera la cual no amarrará una aplicación o "
+"controlador con una implementación especifica. Por lo tanto JBossJTA tiene "
+"varias clases las cuales son para implementaciones JDBC 2.0 especificas y "
+"estas se pueden seleccionar en tiempo de ejecución por la aplicación "
+"configurando la propiedad <property>dynamicClass</property> apropiadamente:"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:166
+#, no-c-format
+msgid "Dynamic Class property values for specific databases"
+msgstr "Valores de la propiedad clase dinámica para bases de datos especificas"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:170
+#, no-c-format
+msgid "Database Type"
+msgstr "Tipo de base de datos"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:173
+#, no-c-format
+msgid "Property Name"
+msgstr "Nombre de la propiedad"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:180
+#, no-c-format
+msgid "Cloudscape 3.6"
+msgstr "Cloudscape 3.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr "Sequelink 5.1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr "Oracle 8.1.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:207
+#, no-c-format
+msgid ""
+"As mentioned earlier, JBossTS no longer supports Cloudscape or Sequelink as "
+"part of the qualified drivers. Furthermore, we recommend using JNDI to "
+"obtain JDBC classes rather than the direct method described here."
+msgstr ""
+"Como lo mecionamos anteriormente, JBossTS ya no soporta Cloudscape o "
+"Sequelink como parte de los controladores calificados. Además, le "
+"recomendamos utilizar JNDI para obtener clases JDBC en lugar del método "
+"directo descrito aquí. "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:211
+#, no-c-format
+msgid ""
+"The application code must specify which dynamic class the "
+"<code>TransactionalDriver</code> should instantiate when setting up the "
+"connection:"
+msgstr ""
+"El código de la aplicación debe especificar la clase dinámica que el "
+"<code>TransactionalDriver</code> debe instanciar al establecer la conexión: "
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:214
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:216
+#, no-c-format
+msgid "Using the connection"
+msgstr "Uso de la conexión"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:217
+#, no-c-format
+msgid ""
+"Once the connection has been established (for example, using the "
+"<methodname>java.sql.DriverManager.getConnection</methodname> method), all "
+"operations on the connection will be monitored by JBossJTA. Note, it is not "
+"necessary to use the transactional connection within transactions. If a "
+"transaction is not present when the connection is used, then operations will "
+"be performed directly on the database."
+msgstr ""
+"Una vez se ha establecido la conexión (por ejemplo, utilizando el método "
+"<methodname>java.sql.DriverManager.getConnection</methodname>), todas las "
+"operaciones en la conexión serán monitoreadas por JBossJTA. Observe que no "
+"es necesario utilizar la conexión transaccional dentro de las transacciones. "
+"Si una transacción no está presente cuando se utiliza la conexión entonces "
+"las operaciones se realizarán directamente en la base de datos. "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr "JDBC no suporta subtransacciones."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:226
+#, no-c-format
+msgid ""
+"Transaction timeouts can be used to automatically terminate transactions "
+"should the connection not be terminated within an appropriate period."
+msgstr ""
+"El tiempo de expiración de las transacciones se pueden utilizar para "
+"terminar las transacciones de manera automática en caso de que la conexión "
+"no sea terminada dentro de un periodo apropiado. "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:229
+#, no-c-format
+msgid ""
+"JBossJTA connections can be used within multiple different transactions "
+"simultaneously, for instance, different threads, with different notions of "
+"the current transaction, may use the same JDBC connection. JBossJTA does "
+"connection pooling for each transaction within the JDBC connection. So, "
+"although multiple threads may use the same instance of the JDBC connection, "
+"internally this may be using a different connection instance per "
+"transaction. With the exception of close, all operations performed on the "
+"connection at the application level will only be performed on this "
+"transaction-specific connection."
+msgstr ""
+"Las conexiones JBossJTA se pueden utilizar dentro de múltiples transacciones "
+"diferentes de manera simultánea, por ejemplo, diferentes hilos, con "
+"diferentes nociones de la transacción actual pueden utilizar la misma "
+"conexión JDBC. JBossJTA hace pool de conexiones para cada transacción dentro "
+"de la conexión JDBC. Así que aunque múltiples hilos pueden utilizar la misma "
+"instancia de la conexión JDBC, internamente esta puede estar utilizando una "
+"instancia de conexión diferente por transacción. Con la excepción de close, "
+"todas las operaciones realizadas en la conexión a nivel de la aplicación "
+"sólo se realizarán en esta conexión especifica de la transacción."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:232
+#, no-c-format
+msgid ""
+"JBossJTA will automatically register the JDBC driver connection with the "
+"transaction via an appropriate resource . When the transaction terminates, "
+"this resource will be responsible for either committing or rolling back any "
+"changes made to the underlying database via appropriate calls on the JDBC "
+"driver."
+msgstr ""
+"JBossJTA registrará automáticamente la conexión del controlador JDBC con la "
+"transacción por medio de un recurso apropiado. Cuando la transacción "
+"termina, este recurso será el responsable de guardar o deshacer los cambios "
+"realizados a la base de datos subyacente por medio de llamadas apropiadas al "
+"controlador JDBC."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:235
+#, no-c-format
+msgid ""
+"Once created, the driver and any connection can be used in the same way as "
+"any other JDBC driver or connection."
+msgstr ""
+"Una vez creado, se puede utilizar el controlador y cualquier conexión de la "
+"misma manera que cualquier otro controlador JDBC o conexión. "
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:238
+#, no-c-format
+msgid ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+msgstr ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:240
+#, no-c-format
+msgid "Connection pooling"
+msgstr "Pool de conexiones"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:241
+#, no-c-format
+msgid ""
+"For each user name and password, JBossJTA will maintain a single instance of "
+"each connection for as long as that connection is in use. Subsequent "
+"requests for the same connection will get a reference to the originally "
+"created connection, rather than a new instance. Attempts to close the "
+"connection are allowed, but the connection will only actually be closed when "
+"all users (including transactions) have either finished with the connection, "
+"or issued close calls."
+msgstr ""
+"Para cada nombre de usuario y contraseña, JBossJTA mantendrá una sola "
+"instancia de cada conexión en tanto esa conexión se encuentre en uso. Las "
+"peticiones posteriores para la misma conexión obtendrán una referencia a la "
+"conexión creada originalmente en lugar de una nueva instancia. Se permiten "
+"intentos para cerrar la conexión pero la conexión sólo se cerrará en "
+"realidad cuando todos los usuarios (incluyendo las transacciones) hayan "
+"terminado con la conexión o hayan emitido llamadas para cerrarlas. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:246
+#, no-c-format
+msgid "Reusing connections"
+msgstr "Reutilización de conexiones"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:247
+#, no-c-format
+msgid ""
+"Some JDBC drivers allow the reuse of a connection for multiple different "
+"transactions once a given transaction has completed. Unfortunately this is "
+"not a common feature, and other drivers require a new connection to be "
+"obtained for each new transaction. By default, the JBossJTA transactional "
+"driver will always obtain a new connection for each new transaction. "
+"However, if an existing connection is available and is currently unused, it "
+"is possible to make JBossJTA reuse this connection. In order to do this, the "
+"reuseconnection=true option must be specified on the JDBC URL. For example:"
+msgstr ""
+"Algunos controladores JDBC permiten la re-utilización de una conexión para "
+"múltiples transacciones diferentes una vez que una transacción dada se ha "
+"completado. Desafortunadamente esta no es una funcionalidad común y otros "
+"controladores requieren que se obtenga una nueva conexión para cada nueva "
+"transacción. Por defecto, el controlador transaccional JBossJTA siempre "
+"obtendrá una nueva conexión para cada nueva transacción. Sin embargo, si una "
+"conexión existente se encuentra disponible y actualmente no se está "
+"utilizando entonces es posible hacer que JBossJTA re-utilice esta conexión. "
+"Con el fin de lograr esto, se debe especificar la opción "
+"reuseconnection=true en la URL JDBC. Por ejemplo:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+"jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:253
+#, no-c-format
+msgid "Terminating the transaction"
+msgstr "Terminar la transacción"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:254
+#, no-c-format
+msgid ""
+"Whenever a transaction terminates (either explicitly by the application "
+"programmer, or implicitly when any associated transaction timeout expires) "
+"that has a JDBC connection registered with it, JBossJTA will drive the "
+"database (via the JDBC driver) to either commit or roll back any changes "
+"made to it. This happens transparently to the application."
+msgstr ""
+"Cuando una transacción termina (ya sea explícitamente por el programador de "
+"la aplicación o implícitamente cuando cualquier tiempo de expiración de la "
+"transacción asociada expira) que tiene una conexión JDBC registrada con "
+"este, JBossJTA dirigirá la base de datos (por medio del controlador JDBC) "
+"para que guarde o para que deshaga los cambios que se realizaron. Esto "
+"sucede de manera transparente en la aplicación. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr "AutoCommit"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:260
+#, no-c-format
+msgid ""
+"If <code>AutoCommit</code> of the <code>java.sql.Connection</code> is set to "
+"true for JDBC 1.0 then the execution of every SQL statement is a separate "
+"top-level transaction, and grouping multiple statements to be managed within "
+"a single OTS transaction is not possible. Therefore, JBossJTA will disable "
+"<code>AutoCommit</code> on JDBC 1.0 connections before they can be used. If "
+"auto commit is subsequently set to true by the application, JBossJTA will "
+"raise the <code>java.sql.SQLException</code>."
+msgstr ""
+"Si <code>AutoCommit</code> del <code>java.sql.Connection</code> se configura "
+"como verdadero para JDBC 1.0 entonces la ejecución para toda declaración SQL "
+"es una transacción a nivel superior separada y no es posible el agrupar "
+"múltiples declaraciones para que sean administradas dentro de una sola "
+"transacción OTS. Por lo tanto, JBossJTA deshabilitará <code>AutoCommit</"
+"code> en conexiones JDBC 1.0 antes de poderlas utilizar. Si después la "
+"aplicación configura el auto commit como verdadero entonces JBossJTA "
+"presentará la excepción <code>java.sql.SQLException</code>."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:265
+#, no-c-format
+msgid "Setting isolation levels"
+msgstr "Configuración de los niveles de aislamiento"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:266
+#, no-c-format
+msgid ""
+"When using the JBossJTA JDBC driver, it may be necessary to set the "
+"underlying transaction isolation level on the XA connection. By default, "
+"this is set to <code>TRANSACTION_SERIALIZABLE</code>, but you may want to "
+"set this to something more appropriate for your application. In order to do "
+"this, set the <property>com.arjuna.ats.jdbc.isolationLevel</property> "
+"property to the appropriate isolation level in string form, for example, "
+"<code>TRANSACTION_READ_COMMITTED</code>, or "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+msgstr ""
+"Al utilizar el controlador JDBC JBossJTA puede que sea necesario el "
+"configurar el nivel de aislamiento de la transacción subyacente en la "
+"conexión XA. Por defecto, se configura como <code>TRANSACTION_SERIALIZABLE</"
+"code>, pero puede que usted quiera configurar esto de manera más apropiada "
+"para su aplicación. Con el fin de lograr esto, configure la propiedad "
+"<property>com.arjuna.ats.jdbc.isolationLevel</property> al nivel de "
+"aislamiento apropiado con cadenas, por ejemplo, "
+"<code>TRANSACTION_READ_COMMITTED</code> o <code>TRANSACTION_REPEATABLE_READ</"
+"code>."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:271
+#, no-c-format
+msgid ""
+"At present this property applies to all XA connections created in the JVM."
+msgstr ""
+"En este momento esta propiedad aplica a todas las conexiones XA creadas en "
+"la MVJ. "
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Preface.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Preface.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,22 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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 "Prefacio"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Revision_History.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Revision_History.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,28 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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 "Historial de revisiones"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/The_Resource_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/The_Resource_Manager.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/The_Resource_Manager.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,962 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#: The_Resource_Manager.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "Test"
+
+#. Tag: para
+#: The_Resource_Manager.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "Este es un parrafo de prueba"
+
+#. Tag: title
+#: The_Resource_Manager.xml:11
+#, no-c-format
+msgid "The XAResource Interface"
+msgstr "La interfaz XAResource"
+
+#. Tag: para
+#: The_Resource_Manager.xml:12
+#, no-c-format
+msgid ""
+"Whereas some transaction specifications and systems define a generic "
+"resource which can be used to register arbitrary resources with a "
+"transaction, the JTA is much more XA specific. The <interfacename>javax."
+"transaction.xa.XAResource</interfacename> interface is a Java mapping of the "
+"<interfacename>XA</interfacename> interface. The <interfacename>XAResource</"
+"interfacename> interface defines the contract between a Resource Manager and "
+"a Transaction Manager in a distributed transaction processing environment. A "
+"resource adapter for a resource manager implements the "
+"<interfacename>XAResource</interfacename> interface to support association "
+"of a top-level transaction to a resource such as a relational database."
+msgstr ""
+"Mientras que algunas especificaciones de los sistemas y las transacciones "
+"definen un recurso genérico, el cual se puede utilizar para registrar "
+"recursos arbitrarios con una transacción, JTA es mucho más especifico para "
+"XA. La interfaz <interfacename>javax.transaction.xa.XAResource</"
+"interfacename> es un mapeo Java de la interfaz <interfacename>XA</"
+"interfacename>. La interfaz <interfacename>XAResource</interfacename> define "
+"el contrato entre un administrador de recursos y un administrador de "
+"transacciones en un entorno de procesamiento de transacciones distribuidas. "
+"Un adaptador de recursos para un administrador de recursos implementa la "
+"interfaz <interfacename>XAResource</interfacename> para soportar la "
+"asociación de una transacción a nivel superior con un recurso tal como una "
+"base de datos relacional. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:15
+#, no-c-format
+msgid ""
+"The <interfacename>XAResource</interfacename> interface can be supported by "
+"any transactional resource adapter that is intended to be used in an "
+"environment where transactions are controlled by an external transaction "
+"manager, for example, a database management system. An application may "
+"access data through multiple database connections. Each database connection "
+"is associated with an <code>XAResource</code> object that serves as a proxy "
+"object to the underlying resource manager instance. The transaction manager "
+"obtains an <code>XAResource</code> for each resource manager participating "
+"in a top-level transaction. It uses the start method to associate the "
+"transaction with the resource, and it uses the end method to disassociate "
+"the transaction from the resource."
+msgstr ""
+"La interfaz <interfacename>XAResource</interfacename> la puede soportar "
+"cualquier adaptador de recursos transaccional que tenga el propósito de ser "
+"utiilizado en un entorno en donde las transacciones sean controladas por un "
+"administrador de transacciones externo, por ejemplo, un sistema de "
+"administración de bases de datos. Una aplicación puede acceder datos por "
+"medio de múltiples conexiones de base de datos. Cada conexión de base de "
+"datos está asociada con un objeto <code>XAResource</code> que sirve como "
+"objeto proxy para la instancia administradora de recursos subyacente. El "
+"administrador de transacciones obtiene un <code>XAResource</code> para cada "
+"administrador de recursos participando en una transacción a nivel superior. "
+"Utiliza el método start para asociar la transaccióncon el recurso y utiliza "
+"el método end para desasociar la transacción del recurso."
+
+#. Tag: para
+#: The_Resource_Manager.xml:18
+#, no-c-format
+msgid ""
+"The resource manager is responsible for associating the transaction with all "
+"work performed on its data between the start and end invocations. At "
+"transaction commit time, these transactional resource managers are informed "
+"by the transaction manager to prepare, commit, or rollback the transaction "
+"according to the two-phase commit protocol."
+msgstr ""
+"El administrador de recursos es el reponsable de asociar la transacción con "
+"todo el trabajo realizado en sus datos entre las invocaciones de inicio y de "
+"final. En el momento de guardar los cambios de la transacción, el "
+"administrador de transacciones le informa a estos administradores de "
+"recursos transaccionales que prepare, guarde o deshaga los cambios de la "
+"transacción de acuerdo con el protocolo para guardar los cambios en dos "
+"fases. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:21
+#, no-c-format
+msgid ""
+"In order to be better integrated with Java, the <interfacename>XAResource</"
+"interfacename> differs from the standard <interfacename>XA</interfacename> "
+"interface in the following ways:"
+msgstr ""
+"Con el fin de integrarse mejor con Java, la <interfacename>XAResource</"
+"interfacename> difiere de la interfaz estándar <interfacename>XA</"
+"interfacename> de la siguiente manera: "
+
+#. Tag: para
+#: The_Resource_Manager.xml:26
+#, no-c-format
+msgid ""
+"The resource manager initialization is done implicitly by the resource "
+"adapter when the resource (connection) is acquired. There is no "
+"<code>xa_open</code> equivalent."
+msgstr ""
+"La inicialización del administrador de recursos es realizada implíctamente "
+"por el adaptador de recursos cuando el recurso (conexión) se adquiere. No "
+"hay un equivalente <code>xa_open</code>. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:31
+#, no-c-format
+msgid ""
+"<code>Rmid</code> is not passed as an argument. Each <code>Rmid</code> is "
+"represented by a separate <code>XAResource</code> object."
+msgstr ""
+"<code>Rmid</code> no se pasa como un argumento. Cada <code>Rmid</code> es "
+"representada por un objeto <code>XAResource</code> separado."
+
+#. Tag: para
+#: The_Resource_Manager.xml:36
+#, no-c-format
+msgid ""
+"Asynchronous operations are not supported because Java supports multi-"
+"threaded processing and most databases do not support asynchronous "
+"operations."
+msgstr ""
+"No se soportan las operaciones asincrónicas ya que Java soporta "
+"procesamiento multi-hilos y la mayoría de las bases de datos no soportan "
+"operaciones asincrónicas. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:41
+#, no-c-format
+msgid ""
+"Error return values that are caused by the transaction manager’s improper "
+"handling of the <code>XAResource</code> object are mapped to Java exceptions "
+"via the <classname>XAException</classname> class."
+msgstr ""
+"Los valores de retorno error son causados por el manejo incorrecto del "
+"administrador de transacciones del objeto <code>XAResource</code> y se "
+"mapean a las excepciones Java por medio del la clase <classname>XAException</"
+"classname>. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:46
+#, no-c-format
+msgid ""
+"The DTP concept of <emphasis>Thread of Control</emphasis> maps to all Java "
+"threads that are given access to the <code>XAResource</code> and "
+"<code>Connection</code> objects. For example, it is legal for two different "
+"threads to perform the start and end operations on the same "
+"<code>XAResource</code> object."
+msgstr ""
+"El concepto DTP de <emphasis>control de hilos</emphasis> mapea a todos los "
+"hilos Java a los que se les da acceso a los objetos <code>XAResource</code> "
+"y <code>Connection</code>. Por ejemplo, es legal para dos hilos diferentes "
+"el realizar las operaciones de inicio y de final en el mismo objeto "
+"<code>XAResource</code>."
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr "Control extendido XAResource"
+
+#. Tag: para
+#: The_Resource_Manager.xml:53
+#, no-c-format
+msgid ""
+"By default, whenever an <code>XAResource</code> object is registered with a "
+"JTA compliant transaction service, you have no control over the order in "
+"which it will be invoked during the two-phase commit protocol, with respect "
+"to other <code>XAResource</code> objects. In JBossTS, however, there is "
+"support for controlling the order via the two interfaces <interfacename>com."
+"arjuna.ats.jta.resources.StartXAResource</interfacename> and "
+"<interfacename>com.arjuna.ats.jta.resources.EndXAResource</interfacename>. "
+"By inheriting your <code>XAResource</code> instance from either of these "
+"interfaces, you control whether an instance of your class will be invoked "
+"first or last, respectively."
+msgstr ""
+"Por defecto, cuando un objeto <code>XAResource</code> es registrado con un "
+"servicio de transacciones que cumple con los requerimientos de JTA, no tiene "
+"control sobre el orden en el cual será invocado durante el protocolo para "
+"guardar los cambios en dos fases, con respecto con los otros objetos "
+"<code>XAResource</code>. Sin embargo, en JBossTS hay soporte para controlar "
+"el orden por medio de las dos interfaces <interfacename>com.arjuna.ats.jta."
+"resources.StartXAResource</interfacename> y <interfacename>com.arjuna.ats."
+"jta.resources.EndXAResource</interfacename>. Al heredar su instancia "
+"<code>XAResource</code> de cualquiera de estas interfaces, puede controlar "
+"si una instancia de su clase será invocada de primero o de último "
+"respectivamente."
+
+#. Tag: para
+#: The_Resource_Manager.xml:58
+#, no-c-format
+msgid ""
+"Only one instance of each interface type may be registered with a specific "
+"transaction."
+msgstr ""
+"Solo se puede registrar una instancia de cada tipo de interfaz con una "
+"transacción en especifico. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:62
+#, no-c-format
+msgid ""
+"In the TxCore manual we discussed the Last Resource Commit optimization "
+"(LRCO), whereby a single resource that is only one-phase aware (does not "
+"support prepare), can be enlisted with a transaction that is manipulating "
+"two-phase aware participants. This optimization is also supported within the "
+"JTA aspects of JBossTS."
+msgstr ""
+"En el manual TxCore, discutimos la optimización para guardar los cambios del "
+"último recurso (LRCO del inglés Last Resource Commit optimization), en donde "
+"un solo recurso que es conciente de una sola fase (no soporta prepare) se "
+"puede listar con una transacción que esté manipulado participantes "
+"concientes de dos fases. Esta optimización también es soportada dentro de "
+"los aspectos JTA de JBossTS."
+
+#. Tag: para
+#: The_Resource_Manager.xml:65
+#, no-c-format
+msgid ""
+"In order to use the LRCO, your <interfacename>XAResource</interfacename> "
+"implementation must extend the <interfacename>com.arjuna.ats.jta.resources."
+"LastResourceCommitOptimisation</interfacename> marker interface (it provides "
+"no methods). When enlisting the resource via Transaction.enlistResource, "
+"JBossTS will ensure that only a single instance of this type of participant "
+"is used within each transaction. Your resource will be driven last in the "
+"commit protocol: no invocation of prepare will occur."
+msgstr ""
+"Con el fin de utilizar el LRCO, su implementación <interfacename>XAResource</"
+"interfacename> debe extender la interfaz marcadora <interfacename>com.arjuna."
+"ats.jta.resources.LastResourceCommitOptimisation</interfacename> (no "
+"proporciona métodos). Cuando lista el recurso por medio de Transaction."
+"enlistResource, JBossTS se asegura de que solo una instancia de este tipo de "
+"participante se utilice dentro de cada transacción. Su recurso será el "
+"último en el protocolo commit: no tendrá lugar una invocación prepare. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:69
+#, no-c-format
+msgid ""
+"By default an attempt to enlist more than one instance of a "
+"<classname>LastResourceCommitOptimisation</classname> class will fail and "
+"false will be returned from <methodname>Transaction.enlistResource</"
+"methodname>. This behaviour can be overridden by setting the <property>com."
+"arjuna.ats.jta.allowMultipleLastResources</property> to true. However, "
+"before doing so you should read the Section on enlisting multiple one-phase "
+"aware resources."
+msgstr ""
+"Por defecto, el tratar de listar más de una instancia de una clase "
+"<classname>LastResourceCommitOptimisation</classname> fallará y se retornará "
+"false de <methodname>Transaction.enlistResource</methodname>. Este "
+"comportamiento se puede sobreescribir configurando <property>com.arjuna.ats."
+"jta.allowMultipleLastResources</property> como verdadero. Sin embargo, antes "
+"de hacerlo debe leer la sección sobre el listado de múltiples recursos "
+"concientes de una fase. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:73
+#, no-c-format
+msgid ""
+"In order to utilize the LRCO in a distributed environment, it is necessary "
+"to disable interposition support. It is still possible to use implicit "
+"context propagation."
+msgstr ""
+"Con el fin de utilizar el LCRO en un entorno distribuido, es necesario "
+"deshabilitar el soporte de interposición. Aún es posible el utilizar la "
+"propagación de contexto implícito. "
+
+#. Tag: title
+#: The_Resource_Manager.xml:77
+#, no-c-format
+msgid "Enlisting multiple one-phase aware resources"
+msgstr "Listado de múltiples recursos concientes de una fase"
+
+#. Tag: para
+#: The_Resource_Manager.xml:78
+#, no-c-format
+msgid ""
+"As discussed in the Transaction Core documentation, in order to guarantee "
+"consistency (atomicity) of outcome between multiple participants (resources) "
+"within the same transaction, the two-phase commit protocol is used with a "
+"durable transaction log. In the case of possessing a single one-phase aware "
+"resource, it is still possible to achieve an atomic (all of nothing) outcome "
+"across resources by utilizing the Last Resource Commit Optimization, as "
+"explained earlier."
+msgstr ""
+"Como lo discutimos en la documentación principal sobre transacciones, con el "
+"fin de garantizar consistencia (atomicidad) de resultados entre múltiples "
+"participantes (recursos) dentro de la misma transacción, se utiliza el "
+"protocolo para guardar cambios en dos fases con un registro durable de "
+"transacciones. En el caso de poseer un recurso conciente de solo una fase, "
+"aún es posible el lograr un resultado atómico através de los recursos "
+"utilizando LRCO como lo explicamos anteriormente. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:82
+#, no-c-format
+msgid ""
+"However, there may be situations where multiple one-phase aware resources "
+"are enlisted within the same transaction. For example, a legacy database "
+"running within the same transaction as a legacy JMS implementation. In these "
+"situations it is not possible to achieve atomicity of transaction outcome "
+"across multiple resources because none of them enter the prepare (waiting "
+"for final outcome) state: they commit or rollback immediately when "
+"instructed by the transaction coordinator, without knowledge of other "
+"resource states and without any way of undoing should subsequent resources "
+"make a different choice. This can result in data corruption or heuristic "
+"outcomes."
+msgstr ""
+"Sin embargo, puede haber situaciones en donde múltiples recursos concientes "
+"de una fase, se listen dentro de la misma transacción. Por ejemplo, una base "
+"de datos heredada ejecutando dentro de la misma transacción como una "
+"implementación JMS heredada. En estas situaciones no es posible lograr la "
+"atomicidad del resultado de la transacción a través de múltiples recursos ya "
+"que ninguno de ellos entran en el estado prepare (en espera por el resultado "
+"final): guardan o deshacen los cambios inmediatamente cuando el coordinador "
+"de transacciones lo ordena, sin conocer el estado de otros recursos y sin "
+"manera de deshacer en caso de que recursos posteriores tomen una decisión "
+"diferente. Esto puede llegar a corromper los datos o puede generar "
+"resultados heurísticos. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:85
+#, no-c-format
+msgid "In these situations we recommend one of the following approaches:"
+msgstr "En estas situaciones le recomendamos uno de los siguientes enfoques: "
+
+#. Tag: para
+#: The_Resource_Manager.xml:90
+#, no-c-format
+msgid ""
+"Wrap the resources in compensating transactions. See the Web Services "
+"transactions guides for further details."
+msgstr ""
+"Envuelva los recursos en transacciones de compensación. Consulte los "
+"manuales sobre transacciones de servicios web para obtener mayores detalles. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:95
+#, no-c-format
+msgid "Migrate the legacy implementations to two-phase aware equivalents."
+msgstr ""
+"Migre las implementaciones heredadas a equivalentes concientes de dos fases. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:100
+#, no-c-format
+msgid ""
+"In the cases where neither of these options are viable, JBossTS does support "
+"the enlistment of multiple one-phase aware resources within the same "
+"transaction. In order to do this, see the section on the Last Resource "
+"Commit Optimization."
+msgstr ""
+"En los casos en donde ninguna de estas opciones son viables, JBossTS soporta "
+"el listado de múltiples recursos concientes de una fase dentro de la misma "
+"transacción. Con el fin de lograr esto, consulte la sección que aborda LRCO. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:104
+#, no-c-format
+msgid ""
+"Even when this support is enabled, JBossTS will issue warnings when it "
+"detects that the option has been enabled (\"You have chosen to enable "
+"multiple last resources in the transaction manager. This is transactionally "
+"unsafe and should not be relied upon.”) and when multiple one-phase "
+"resources are enlisted within the transaction (“This is transactionally "
+"unsafe and should not be relied on.”)."
+msgstr ""
+"Incluso cuando este soporte se encuentra habilitado, JBossTS emitirá "
+"advertencias cuando detecte que la opción ha sido habilitada (\"You have "
+"chosen to enable multiple last resources in the transaction manager. This is "
+"transactionally unsafe and should not be relied upon.” Esto no es seguro "
+"transaccionalmente y no se debe confiar en esto) y cuando múltiples recursos "
+"de una fase sean listados dentro de la transacción (“This is transactionally "
+"unsafe and should not be relied on.” - Esto no es seguro transaccionalmente "
+"y no se debe confiar en esto)."
+
+#. Tag: title
+#: The_Resource_Manager.xml:111
+#, no-c-format
+msgid "Opening a Resource Manager"
+msgstr "Abrir un administrador de recursos"
+
+#. Tag: para
+#: The_Resource_Manager.xml:112
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface requires that the "
+"transaction manager initialize a resource manager (xa_open) prior to any "
+"other xa_ calls. JTA requires initialization of a resource manager to be "
+"embedded within the resource adapter that represents the resource manager. "
+"The transaction manager does not need to know how to initialize a resource "
+"manager; it is only responsible for informing the resource manager about "
+"when to start and end work associated with a transaction and when to "
+"complete the transaction. The resource adapter is responsible for opening "
+"(initializing) the resource manager when the connection to the resource "
+"manager is established."
+msgstr ""
+"La interfaz <interfacename>XA</interfacename> X/Open requiere que el "
+"administrador de transacciones inicialice un administrador de recursos "
+"(xa_open) antes de cualquier otra llamada xa_. JTA requiere la "
+"inicialización de un administrador de recursos para que sea incluido dentro "
+"del adaptador de recursos que representa el administrador de recursos. El "
+"administrador de transacciones no necesita saber cómo inicializar un "
+"administrador de recursos; sólo es responsable de informar el administrador "
+"de recursos sobre cuándo iniciar y finalizar el trabajo asociado con una "
+"transacción y cuando completar la transacción. El adaptador de recursos es "
+"el responsable de abrir (inicializar) el administrador de recursos cuando se "
+"establece la conexión al administrador de recursos. "
+
+#. Tag: title
+#: The_Resource_Manager.xml:118
+#, no-c-format
+msgid "Closing a Resource Manager"
+msgstr "Cerrar un administrador de recursos"
+
+#. Tag: para
+#: The_Resource_Manager.xml:119
+#, no-c-format
+msgid ""
+"A resource manager is closed by the resource adapter as a result of "
+"destroying the transactional resource. A transaction resource at the "
+"resource adapter level is comprised of two separate objects:"
+msgstr ""
+"El adaptador de recursos cierra un administrador de recursos como resultado "
+"de la destrucción del recurso transaccional. Un recurso de transacción a "
+"nivel del adaptador de recursos comprende dos objetos separados: "
+
+#. Tag: para
+#: The_Resource_Manager.xml:124
+#, no-c-format
+msgid ""
+"An <code>XAResource</code> object that allows the transaction manager to "
+"start and end the transaction association with the resource in use and to "
+"coordinate transaction completion process."
+msgstr ""
+"Un objeto <code>XAResource</code> que le permite al administrador de "
+"transacciones el iniciar y terminar la asociación de transacciones con el "
+"recurso en uso y permite el coordinar el proceso para completar "
+"transacciones."
+
+#. Tag: para
+#: The_Resource_Manager.xml:129
+#, no-c-format
+msgid ""
+"A connection object that allows the application to perform operations on the "
+"underlying resource (for example, JDBC operations on an RDBMS)."
+msgstr ""
+"Un objeto conexión que le permite a la aplicación el realizar operaciones en "
+"el recurso subyacente (por ejemplo, operaciones JDBC en un RDBMS). "
+
+#. Tag: para
+#: The_Resource_Manager.xml:134
+#, no-c-format
+msgid ""
+"Once opened, the resource manager is kept open until the resource is "
+"released (closed) explicitly. When the application invokes the connection’s "
+"close method, the resource adapter invalidates the connection object "
+"reference that was held by the application and notifies the application "
+"server about the close. The transaction manager should invoke the "
+"<methodname>XAResource.end</methodname> method to disassociate the "
+"transaction from that connection."
+msgstr ""
+"Una vez se abre, el administrador de recursos se mantiene abierto hasta que "
+"el recurso sea liberado (cerrado) explícitamente. Cuando la aplicación "
+"invoca el método close de la conexión, el adaptador de recursos invalida la "
+"referencia del objeto de conexión que la aplicación tenía y notifica al "
+"servidor de aplicaciones sobre el cierre. El administrador de transacciones "
+"debe invocar el método <methodname>XAResource.end</methodname> para "
+"desasociar la transacción de esa conexión. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:137
+#, no-c-format
+msgid ""
+"The close notification allows the application server to perform any "
+"necessary cleanup work and to mark the physical XA connection as free for "
+"reuse, if connection pooling is in place."
+msgstr ""
+"La notificación close le permite al servidor de aplicaciones el realizar "
+"cualquier trabajo de limpieza y marcar como libre la conexión XA física para "
+"poderla volver a utilizar, si el pool de conexiones está funcionando. "
+
+#. Tag: title
+#: The_Resource_Manager.xml:143
+#, no-c-format
+msgid "Threads of control"
+msgstr "Hilos de control"
+
+#. Tag: para
+#: The_Resource_Manager.xml:144
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface specifies that the "
+"transaction association related xa calls must be invoked from the same "
+"thread context. This thread-of-control requirement is not applicable to the "
+"object-oriented component-based application run-time environment, in which "
+"application threads are dispatched dynamically at method invocation time. "
+"Different threads may be using the same connection resource to access the "
+"resource manager if the connection spans multiple method invocation. "
+"Depending on the implementation of the application server, different threads "
+"may be involved with the same <code>XAResource</code> object. The resource "
+"context and the transaction context may be operated independent of thread "
+"context. This means that it is possible for different threads to be invoking "
+"the start and end methods."
+msgstr ""
+"La interfaz <interfacename>XA</interfacename> X/Open especifica que las "
+"llamadas xa relacionadas con la asociación de transacciones se debe invocar "
+"desde el mismo contexto de hilos. Este requerimiento de hilo-de-control no "
+"es aplicable al entorno en tiempo de ejecución de la aplicación con base en "
+"componentes orientada a objetos, en la cual los hilos de aplicaciones se "
+"despachan dinámicamente en el momento de invocación del método. Diferentes "
+"hilos puede utilizar el mismo recurso de conexión para acceder el "
+"administrador de recursos si la conexión abarca múltiples invocaciones de "
+"método. Dependiendo de la implementación del servidor de aplicaciones, se "
+"pueden involucrar diferentes hilos con el mismo objeto <code>XAResource</"
+"code>. El contexto de recursos y el contexto de transacciones se puede "
+"operar independientemente del contexto del hilo. Esto significa que es "
+"posible para diferentes hilos el invocar los métodos de inicio y de "
+"finalización."
+
+#. Tag: para
+#: The_Resource_Manager.xml:147
+#, no-c-format
+msgid ""
+"If the application server allows multiple threads to use a single "
+"<code>XAResource</code> object and the associated connection to the resource "
+"manager, it is the responsibility of the application server to ensure that "
+"there is only one transaction context associated with the resource at any "
+"point of time. Thus the <interfacename>XAResource</interfacename> interface "
+"requires that the resource managers be able to support the two-phase commit "
+"protocol from any thread context."
+msgstr ""
+"Si el servidor de aplicaciones permite que múltiples hilos utilicen un solo "
+"objeto <code>XAResource</code> y la conexión asociada al administrador de "
+"recursos, es la responsabilidad del servidor de aplicaciones el asegurarse "
+"de que solo hay un contexto de transacción asociado con el recurso en "
+"cualquier momento dado. Por lo tanto, la interfaz <interfacename>XAResource</"
+"interfacename> requiere que los administradores de recursos puedan soportar "
+"el protocolo para guardar los cambios en dos fases desde cualquier contexto "
+"de hilo."
+
+#. Tag: title
+#: The_Resource_Manager.xml:153
+#, no-c-format
+msgid "Transaction association"
+msgstr "Asociación de transacciones "
+
+#. Tag: para
+#: The_Resource_Manager.xml:154
+#, no-c-format
+msgid ""
+"Transactions are associated with a transactional resource via the start "
+"method, and disassociated from the resource via the <methodname>end</"
+"methodname> method. The resource adapter is responsible for internally "
+"maintaining an association between the resource connection object and the "
+"<code>XAResource</code> object. At any given time, a connection is "
+"associated with a single transaction, or it is not associated with any "
+"transaction at all. Because JTA does not support nested transactions it is "
+"an error for the start method to be invoked on a connection that is "
+"currently associated with a different transaction."
+msgstr ""
+"Las transacciones se asocian con un recurso transaccional por medio del "
+"método start y se desasocian del recurso a través del método "
+"<methodname>end</methodname>. El adaptador de recursos es el responsable de "
+"mantener internamente una asociación entre el objeto de conexión de recursos "
+"y el objeto <code>XAResource</code>. En cualquier momento dado, una conexión "
+"se asocia con una sola transacción o no se asocia con ninguna transacción. "
+"Ya que JTA no soporta transacciones anidadas es un error el invocar el "
+"método start en una conexión que se encuentra asociada actualmente con una "
+"transacción diferente."
+
+#. Tag: para
+#: The_Resource_Manager.xml:157
+#, no-c-format
+msgid ""
+"Interleaving multiple transaction contexts using the same resource may be "
+"done by the transaction manager as long as start and end are invoked "
+"properly for each transaction context switch. Each time the resource is used "
+"with a different transaction, the method end must be invoked for the "
+"previous transaction that was associated with the resource, and start must "
+"be invoked for the current transaction context."
+msgstr ""
+"El administrador de transacciones puede entretejer múltiples contextos de "
+"transacciones utilizando el mismo recurso en tanto se invoquen "
+"apropiadamente start y end para cada cambio de contexto de transacción. Cada "
+"vez que se utiliza el recurso con una transacción diferente se debe invocar "
+"al método end para la transacción anterior que se asoció con el recurso y "
+"también se debe invocar start para el contexto de transacción actual. "
+
+#. Tag: title
+#: The_Resource_Manager.xml:163
+#, no-c-format
+msgid "Externally controlled connections"
+msgstr "Conexiones controladas externamente "
+
+#. Tag: para
+#: The_Resource_Manager.xml:164
+#, no-c-format
+msgid ""
+"For transactional application whose transaction states are managed by an "
+"application server, its resources must also be managed by the application "
+"server so that transaction association is performed properly. If an "
+"application is associated with a transaction, it is an error for the "
+"application to perform transactional work through the connection without "
+"having the connection’s resource object already associated with the global "
+"transaction. The application server must ensure that the <code>XAResource</"
+"code> object in use is associated with the transaction. This is done by "
+"invoking the <methodname>Transaction.enlistResource</methodname> method."
+msgstr ""
+"Para la aplicación transaccional cuyos estados son administrados por un "
+"servidor de aplicaciones, sus recursos también deben ser administrados por "
+"el servidor de aplicaciones para que la asociación de transacciones se "
+"realice apropiadamente. Si una aplicación se asocia con una transacción, es "
+"un error para la aplicación el realizar trabajo transaccional a través de la "
+"conexión sin tener el objeto recurso de la conexión ya asociado con la "
+"transacción global. El servidor de aplicaciones se debe asegurar de que el "
+"objeto <code>XAResource</code> en uso está asociado con la transacción. Esto "
+"se logra invocando el método <methodname>Transaction.enlistResource</"
+"methodname>. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:167
+#, no-c-format
+msgid ""
+"If a server side transactional application retains its database connection "
+"across multiple client requests, the application server must ensure that "
+"before dispatching a client request to the application thread, the resource "
+"is enlisted with the application’s current transaction context. This implies "
+"that the application server manages the connection resource usage status "
+"across multiple method invocations."
+msgstr ""
+"Si una aplicación transaccional del lado del servidor retiene su conexión de "
+"base de datos a través de múltiples peticiones de clientes, el servidor de "
+"aplicaciones debe asegurarse de que antes de despachar una petición de un "
+"cliente al hilo de la aplicación, el recurso sea listado con el contexto de "
+"transacción de la transacción actual de la aplicación. Esto implica que el "
+"servidor de aplicaciones administra el estatus del uso de los recursos de "
+"conexión a través de múltiples invocaciones de método. "
+
+#. Tag: title
+#: The_Resource_Manager.xml:173
+#, no-c-format
+msgid "Resource sharing"
+msgstr "Recursos compartidos"
+
+#. Tag: para
+#: The_Resource_Manager.xml:174
+#, no-c-format
+msgid ""
+"When the same transactional resource is used to interleave multiple "
+"transactions, it is the responsibility of the application server to ensure "
+"that only one transaction is enlisted with the resource at any given time. "
+"To initiate the transaction commit process, the transaction manager is "
+"allowed to use any of the resource objects connected to the same resource "
+"manager instance. The resource object used for the two-phase commit protocol "
+"does not need to have been involved with the transaction being completed."
+msgstr ""
+"Cuando el mismo recurso transaccional se utiliza para entretejer múltiples "
+"transacciones, es la responsabilidad del servidor de aplicaciones de "
+"asegurarse de que solo una transacción se liste con el recurso en un momento "
+"dado. Para iniciar el proceso para guardar los cambios de una transacción, "
+"se le permite al administrador de transacciones el utilizar cualquiera de "
+"los objetos de recursos conectados para la misma instancia del administrador "
+"de recursos. No es necesario que el objeto de recurso utilizado para el "
+"protocolo para guardar los cambios en dos fases se haya involucrado al "
+"completar la transacción."
+
+#. Tag: para
+#: The_Resource_Manager.xml:177
+#, no-c-format
+msgid ""
+"The resource adapter must be able to handle multiple threads invoking the "
+"<interfacename>XAResource</interfacename> methods concurrently for "
+"transaction commit processing. For example, with reference to the code "
+"below, suppose we have a transactional resource <code>r1</code>. Global "
+"transaction <code>xid1</code> was started and ended with <code>r1</code>. "
+"Then a different global transaction <code>xid2</code> is associated with "
+"<code>r1</code>. In the meanwhile, the transaction manager may start the two "
+"phase commit process for <code>xid1</code> using <code>r1</code> or any "
+"other transactional resource connected to the same resource manager. The "
+"resource adapter needs to allow the commit process to be executed while the "
+"resource is currently associated with a different global transaction."
+msgstr ""
+"El adaptador de recursos debe poder manejar múltiples hilos invocando los "
+"métodos <interfacename>XAResource</interfacename> de manera simultánea para "
+"el procesamiento para guardar los cambios de transacciones. Por ejemplo, con "
+"referencia al código a continuación, suponga que tenemos un recurso "
+"transaccional <code>r1</code>. La transacción global <code>xid1</code> se "
+"inició y se finalizó con <code>r1</code>. Luego se asoció una transacción "
+"global diferente <code>xid2</code> con <code>r1</code>. Mientras tanto el "
+"administrador de transacciones puede iniciar los procesos para guardar los "
+"cambios en dos fases para <code>xid1</code> utilizando <code>r1</code> o "
+"cualquier otro recurso transaccional conectado al mismo administrador de "
+"recursos. El adaptador de recursos necesita permitir que se ejecute el "
+"proceso para guardar los cambios mientras que el recurso está asociado "
+"actualmente con una transacción global diferente. "
+
+#. Tag: screen
+#: The_Resource_Manager.xml:180
+#, no-c-format
+msgid ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+msgstr ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+
+#. Tag: title
+#: The_Resource_Manager.xml:184
+#, no-c-format
+msgid "Local and global transactions"
+msgstr "Transacciones globales y locales"
+
+#. Tag: para
+#: The_Resource_Manager.xml:185
+#, no-c-format
+msgid ""
+"The resource adapter must support the usage of both local and global "
+"transactions within the same transactional connection. Local transactions "
+"are transactions that are started and coordinated by the resource manager "
+"internally. The <interfacename>XAResource</interfacename> interface is not "
+"used for local transactions. When using the same connection to perform both "
+"local and global transactions, the following rules apply:"
+msgstr ""
+"El adaptador de recursos debe soportar el uso de transacciones locales y "
+"globales dentro de la misma conexión transaccional. Las transacciones "
+"locales son transacciones que el administrador de recursos inicia y coordina "
+"internamente. La interfaz <interfacename>XAResource</interfacename> no se "
+"utiliza para transacciones locales. Cuando se utiliza la misma conexión para "
+"realizar transacciones globales y locales, las siguientes reglas aplican: "
+
+#. Tag: para
+#: The_Resource_Manager.xml:190
+#, no-c-format
+msgid ""
+"The local transaction must be committed (or rolled back) before starting a "
+"global transaction in the connection."
+msgstr ""
+"Se deben guardar los cambios (o deshacerlos) de la transacción local antes "
+"de iniciar una transacción glocal en la conexión. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:195
+#, no-c-format
+msgid ""
+"The global transaction must be disassociated from the connection before any "
+"local transaction is started."
+msgstr ""
+"La transacción global debe ser desasociada de la conexión antes de iniciar "
+"cualquier transacción local. "
+
+#. Tag: title
+#: The_Resource_Manager.xml:203
+#, no-c-format
+msgid "Transaction timeouts"
+msgstr "Tiempo de expiración de las transacciones"
+
+#. Tag: para
+#: The_Resource_Manager.xml:204
+#, no-c-format
+msgid ""
+"Timeout values can be associated with transactions in order to control their "
+"lifetime. If a transaction has not terminated (committed or rolled back) "
+"before the timeout value elapses, the transaction system will automatically "
+"roll it back. The <interfacename>XAResource</interfacename> interface "
+"supports a operation, which allows the timeout associated with the current "
+"transaction to be propagated to the resource manager and if supported, will "
+"override any default timeout associated with the resource manager. This can "
+"be useful when long running transactions may have lifetimes that would "
+"exceed the default and in which case, if the timeout were not altered, the "
+"resource manager would rollback before the transaction terminated and "
+"subsequently cause the transaction to roll back as well."
+msgstr ""
+"Los valores del tiempo de expiración se pueden asociar con las transacciones "
+"para poder controlar su tiempo de vida. Si una transacción no ha terminado "
+"(de guardar o de deshacer los cambios) antes de que transcurra el valor del "
+"tiempo de expiración entonces el sistema de transacciones automáticamente la "
+"deshará. La interfaz <interfacename>XAResource</interfacename> soporta una "
+"operación, la cual permite que el tiempo de expiración asociado con la "
+"transacción actual sea propagado al administrador de recursos y si es "
+"soportado entonces sobreescribirá cualquier tiempo de expiración "
+"predeterminado asociado con el administrador de recursos. Esto puede ser "
+"útil cuando transacciones largas tienen un tiempo de expiración que excede "
+"el predeterminado, en cuyo caso si el tiempo de expiración no se altera, el "
+"administrador de recursos deshace los cambios antes de que se termine la "
+"transacción y posteriormente hará que la transacción también se deshaga. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:207
+#, no-c-format
+msgid ""
+"If no timeout value is explicitly set for a transaction, or a value of 0 is "
+"specified, then an implementation specific default value may be used. In the "
+"case of JBossTS, how this default value is set depends upon which JTA "
+"implementation you are using."
+msgstr ""
+"Si no se establece un tiempo de expiración explícitamente para una "
+"transacción o si se especifica un valor de cero entonces se utiliza el valor "
+"predeterminado especificado. En el caso de JBossTS, la manera en que este "
+"valor predeterminado se configura depende de la implementación JTA que se "
+"esté utilizando. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:212
+#, no-c-format
+msgid ""
+"Local JTA: use the <property>com.arjuna.ats.arjuna.coordinator."
+"defaultTimeout</property> property value and give a timeout in seconds. The "
+"default value is 60 seconds."
+msgstr ""
+"Local JTA: utilice el valor de la propiedad <property>com.arjuna.ats.arjuna."
+"coordinator.defaultTimeout</property> y de un tiempo de expiración en "
+"segundos. El valor predeterminado es 60 segundos."
+
+#. Tag: para
+#: The_Resource_Manager.xml:217
+#, no-c-format
+msgid ""
+"JTS: use the <property>com.arjuna.ats.jts.defaultTimeout</property> property "
+"value and give a timeout in seconds. The default value is 0, for instance, "
+"transactions do not timeout."
+msgstr ""
+"JTS: utilice el valor de la propiedad <property>com.arjuna.ats.jts."
+"defaultTimeout</property> y proporcione un tiempo de expiración en segundos. "
+"El valor predeterminado es 0, por ejemplo, las transacciones no expiran. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:222
+#, no-c-format
+msgid ""
+"Unfortunately there are situations where imposing the same timeout as the "
+"transaction on a resource manager may not be appropriate. For example, if "
+"the system administrator wishes to have control over the lifetimes on "
+"resource managers and does not want to (or cannot) allow that control to be "
+"passed to some external entity. At present JBossTS supports an all-or-"
+"nothing approach to whether or not <methodname>setTransactionTimeout</"
+"methodname> is called on <interfacename>XAResource</interfacename> instances."
+msgstr ""
+"Desafortunadamente hay situaciones en las que pueda que no se apropiado el "
+"imponer el mismo tiempo de expiración que la transacción en un administrador "
+"de recursos. Por ejemplo, si el administrador del sistema desea tener "
+"control sobre el tiempo de vida en los administradores de recursos y no "
+"quiere (o no puede) permitir que ese control se pase a alguna entidad "
+"externa. Actualmente JBossTS soporta un enfoque todo-o-nada para que "
+"<methodname>setTransactionTimeout</methodname> se llame o no en instancias "
+"<interfacename>XAResource</interfacename>."
+
+#. Tag: para
+#: The_Resource_Manager.xml:225
+#, no-c-format
+msgid ""
+"If the <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> "
+"property is set to true (the default) then it will be called on all "
+"instances. Alternatively, the <methodname>setXATransactionTimeoutEnabled</"
+"methodname> method of <classname>com.arjuna.ats.jta.common.Configuration</"
+"classname> can be used."
+msgstr ""
+"Si la propiedad <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</"
+"property> se configura como verdadera (el valor predeterminado) entonces se "
+"llamará en todas las instancias. Opcionalmente, se puede utilizar el método "
+"<methodname>setXATransactionTimeoutEnabled</methodname> de <classname>com."
+"arjuna.ats.jta.common.Configuration</classname>."
+
+#. Tag: title
+#: The_Resource_Manager.xml:231
+#, no-c-format
+msgid "Dynamic Registration"
+msgstr "Inscripción dinámica"
+
+#. Tag: para
+#: The_Resource_Manager.xml:232
+#, no-c-format
+msgid ""
+"Dynamic registration is not supported in <interfacename>XAResource</"
+"interfacename> because of the following reasons:"
+msgstr ""
+"La inscripción dinámica no está soportada en <interfacename>XAResource</"
+"interfacename> debido a las siguientes razones: "
+
+#. Tag: para
+#: The_Resource_Manager.xml:237
+#, no-c-format
+msgid ""
+"In the Java component-based application server environment, connections to "
+"the resource manager are acquired dynamically when the application "
+"explicitly requests a connection. These resources are enlisted with the "
+"transaction manager on a needed basis."
+msgstr ""
+"En el entorno del servidor de aplicaciones basada en componentes Java, las "
+"conexiones al administrador de recursos se adquieren de manera dinámica "
+"cuando la aplicación solicita explícitamente una conexión. Estos recursos "
+"están listados con el administrador de transacciones de acuerdo a su "
+"necesidad. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:242
+#, no-c-format
+msgid ""
+"If a resource manager requires a way to dynamically register its work to the "
+"global transaction, the implementation can be done at the resource adapter "
+"level via a private interface between the resource adapter and the "
+"underlying resource manager."
+msgstr ""
+"Si un administrador de recursos requiere una manera de inscribir "
+"dinámicamente su trabajo para la transacción global entonces la "
+"implementación se puede realizar a nivel del adaptador de recursos a través "
+"de una interfaz privada entre el adaptador de recursos y el administrador de "
+"recursos subyacente. "
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Transaction_Recovery.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Transaction_Recovery.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Transaction_Recovery.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,483 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr "Recuperación de transacciones"
+
+#. Tag: title
+#: Transaction_Recovery.xml:10
+#, no-c-format
+msgid "Failure recovery"
+msgstr "Recuperación de fallos"
+
+#. Tag: para
+#: Transaction_Recovery.xml:11
+#, no-c-format
+msgid ""
+"During recovery, the Transaction Manager needs to be able to communicate to "
+"all resource managers that are in use by the applications in the system. For "
+"each resource manager, the Transaction Manager uses the "
+"<methodname>XAResource.recover</methodname> method to retrieve the list of "
+"transactions that are currently in a prepared or heuristically completed "
+"state. Typically, the system administrator configures all transactional "
+"resource factories that are used by the applications deployed on the system. "
+"An example of such a resource factory is the JDBC <code>XADataSource</code> "
+"object, which is a factory for the JDBC <code>XAConnection</code> objects."
+msgstr ""
+"Durante la recuperación, el administrador de transacciones necesita poder "
+"comunicarse con todos los administradores de recursos que las aplicaciones "
+"en el sistema están utilizando. Para cada administrador de recursos, el "
+"administrador de transacciones utiliza el método <methodname>XAResource."
+"recover</methodname> para recuperar la lista de transacciones que "
+"actualmente se encuentran en un estado de preparación o se han completado "
+"heurísticamente. Usualmente el administrador del sistema configura todas las "
+"fábricas de recursos transaccionales que son utilizadas por las aplicaciones "
+"desplegadas en el sistema. Un ejemplo de tal fábrica de recursos es el "
+"objeto <code>XADataSource</code> JDBC, el cual es una fábrica para los "
+"objetos <code>XAConnection</code> JDBC. "
+
+#. Tag: para
+#: Transaction_Recovery.xml:14
+#, no-c-format
+msgid ""
+"Because <code>XAResource</code> objects are not persistent across system "
+"failures, the Transaction Manager needs to have some way to acquire the "
+"<code>XAResource</code> objects that represent the resource managers which "
+"might have participated in the transactions prior to the system failure. For "
+"example, a Transaction Manager might, through the use of JNDI lookup "
+"mechanism, acquire a connection from each of the transactional resource "
+"factories, and then obtain the corresponding <code>XAResource</code> object "
+"for each connection. The Transaction Manager then invokes the "
+"<methodname>XAResource.recover</methodname> method to ask each resource "
+"manager to return the transactions that are currently in a prepared or "
+"heuristically completed state."
+msgstr ""
+"Ya que los objetos <code>XAResource</code> no son persistentes a través de "
+"fallas del sistema, el administrador de transacciones necesita tener alguna "
+"manera de adquirir los objetos <code>XAResource</code> que representan los "
+"administradores de recursos, los cuales pueden haber participado en las "
+"transacciones antes de la falla en el sistema. Por ejemplo, puede que un "
+"administrador de transacciones, por medio del uso del mecanismo de búsqueda "
+"JNDI, adquiera una conexión de cada una de las fábricas de recursos "
+"transaccionales y luego obtenga el objeto <code>XAResource</code> "
+"correspondiente para cada conexión. Luego el administrador de transacciones "
+"invoca el método <methodname>XAResource.recover</methodname> para pedirle a "
+"cada administrador de recursos que retorne las transacciones que se "
+"encuentren actualmente en un estado prepare o en un estado completado "
+"heurísticamente."
+
+#. Tag: para
+#: Transaction_Recovery.xml:18
+#, no-c-format
+msgid ""
+"When running XA recovery it is 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 ‘*’ will force JBossTS to recover (and possibly rollback) all "
+"transactions irrespective of their node identifier and should be used with "
+"caution."
+msgstr ""
+"Al ejecutar la recuperación XA es necesario decirle a JBossTS que tipos de "
+"Xid puede recuperar. Cada Xid que JBossTS crea tiene un identificador de "
+"nodo único codificado dentro de sí y JBossTS sólo recuperará transacciones y "
+"estados que conicidan con un identificador de nodo especifico. El "
+"identificador de nodo a utilizar lo debe proporcionar JBossTS por medio de "
+"una propiedad que inicia con el nombre <property>com.arjuna.ats.jta."
+"xaRecoveryNode</property>; se pueden proporcionar múltiples valores. Un "
+"valor de ‘*’ forzará a que JBossTS recupere (y posiblemente deshaga) todas "
+"las transacciones independientemente de su identificador de nodo y por lo "
+"tanto se debe utilizar con precaución. "
+
+#. Tag: para
+#: Transaction_Recovery.xml:22
+#, no-c-format
+msgid ""
+"If using the JBossJTA JDBC 2.0 driver, then JBossJTA will take care of all "
+"<interfacename>XAResource</interfacename> crash recovery automatically. "
+"Otherwise one of the following recovery mechanisms will be used:"
+msgstr ""
+"Si está utilizando el controlador JBossJTA JDBC 2.0 entonces JBossJTA se "
+"encargará de todas las recuperaciones en caso de fallo "
+"<interfacename>XAResource</interfacename> de manera automática. De otra "
+"manera se utilizará uno de los siguientes mecanismos de recuperación:"
+
+#. Tag: para
+#: Transaction_Recovery.xml:27
+#, no-c-format
+msgid ""
+"If the <code>XAResource</code> is serializable, then the serialized form "
+"will be saved during transaction commitment, and used during recovery. It is "
+"assumed that the recreated <code>XAResource</code> is valid and can be used "
+"to drive recovery on the associated database."
+msgstr ""
+"Si el <code>XAResource</code> es serializable entonces la forma serializada "
+"se guardará cuando se guarde la transacción y se utilizará durante la "
+"recuperación. Se asume que el <code>XAResource</code> recreado es válido y "
+"se puede utilizar para dirigir la recuperación en la base de datos asociada."
+
+#. Tag: para
+#: Transaction_Recovery.xml:32
+#, no-c-format
+msgid ""
+"The <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, <interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> and <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> interfaces are used. These "
+"are documented in the JDBC chapters on failure recovery."
+msgstr ""
+"Se utilizan las interfaces <interfacename>com.arjuna.ats.jta.recovery."
+"XAResourceRecovery</interfacename>, <interfacename>com.arjuna.ats.jta."
+"recovery.XARecoveryResourceManager</interfacename> y <interfacename>com."
+"arjuna.ats.jta.recovery.XARecoveryResource</interfacename>. Estas están "
+"documentadas en los capítulos sobre JDBC que abordan la recuperación de "
+"fallas."
+
+#. Tag: para
+#: Transaction_Recovery.xml:38
+#, no-c-format
+msgid ""
+"In JBossTS 3.3 the interface <interfacename>XAConnectionRecovery</"
+"interfacename> was deprecated in favor of <interfacename>XAResourceRecovery</"
+"interfacename>. Users are encouraged to move to his new interface."
+msgstr ""
+"En JBossTS 3.3 la interfaz <interfacename>XAConnectionRecovery</"
+"interfacename> fue depreciada a favor de <interfacename>XAResourceRecovery</"
+"interfacename>. Le recomendamos a los usuarios que utilicen su nueva "
+"interfaz."
+
+#. Tag: title
+#: Transaction_Recovery.xml:45
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr "Recuperación de XAConnections"
+
+#. Tag: para
+#: Transaction_Recovery.xml:46
+#, no-c-format
+msgid ""
+"When recovering from failures, JBossJTA requires the ability to reconnect to "
+"databases that were in use prior to the failures in order to resolve any "
+"outstanding transactions. Most connection information will be saved by the "
+"transaction service during its normal execution, and can be used during "
+"recovery to recreate the connection. However, it is possible that not all "
+"such information will have been saved prior to a failure (for example, a "
+"failure occurs before such information can be saved, but after the database "
+"connection is used). In order to recreate those connections it is necessary "
+"to provide implementations of the following JBossJTA interface "
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, one for each database that may be used by an application."
+msgstr ""
+"Al recuperarse de fallos, JBossJTA requiere la habilidad para reconectarse a "
+"las bases de datos que estaban en uso antes de la falla con el fin de "
+"resolver cualquier transacción que falte. La mayoría de la información sobre "
+"la conexión la guardará el servicio de transacciones durante su ejecución "
+"normal y se puede utilizar durante la recuperación para recrear la conexión. "
+"Sin embargo, es posible que no se haya guardado toda la información antes de "
+"la falla (por ejemplo, una falla tiene lugar antes de que tal información se "
+"pueda guardar, pero después de que se utiliza la conexión de la base de "
+"datos). Con el fin de recrear esas conexiones es necesario proporcionar "
+"implementaciones de la siguiente interfaz JBossJTA <interfacename>com.arjuna."
+"ats.jta.recovery.XAResourceRecovery</interfacename>, una para cada base de "
+"datos que una aplicación puede utilizar. "
+
+#. Tag: para
+#: Transaction_Recovery.xml:50
+#, no-c-format
+msgid ""
+"If using the transactional JDBC 2.0 driver provided with JBossJTA, then no "
+"additional work is necessary in order to ensure that recovery occurs."
+msgstr ""
+"Si está utilizando el controlador JDBC 2.0 transaccional con JBossJTA "
+"entonces no necesita trabajo adicional para asegurarse de que la "
+"recuperación ocurra."
+
+#. Tag: para
+#: Transaction_Recovery.xml:54
+#, no-c-format
+msgid ""
+"To inform the recovery system about each of the <code>XAResourceRecovery</"
+"code> instances, it is necessary to specify their class names through "
+"property variables. Any property variable found in the properties file, or "
+"registered at runtime, which starts with the name <property>com.arjuna.ats."
+"jta.recovery.XAResourceRecovery</property> will be assumed to represent one "
+"of these instances, and its value should be the class name. For example:"
+msgstr ""
+"Para informar al sistema de recuperación sobre cada una de las instancias "
+"<code>XAResourceRecovery</code> es necesario especificar los nombres de "
+"clase por medio de las variables de propiedades. Se asume que cualquier "
+"variable de propiedades que se encuentra en el archivo de propiedades o que "
+"se registre en tiempo de ejecución que empiece con el nombre <property>com."
+"arjuna.ats.jta.recovery.XAResourceRecovery</property> representa una de "
+"estas instancias y su valor debe ser el nombre de la clase. Por ejemplo: "
+
+#. Tag: screen
+#: Transaction_Recovery.xml:57
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+
+#. Tag: para
+#: Transaction_Recovery.xml:58
+#, no-c-format
+msgid ""
+"Additional information that will be passed to the instance when it is "
+"created may be specified after a semicolon:"
+msgstr ""
+"La información adicional que se le pasa a la instancia cuando es creada se "
+"puede especificar después de un punto y coma: "
+
+#. Tag: screen
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+
+#. Tag: para
+#: Transaction_Recovery.xml:63
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr ""
+"Estas propiedades necesitan ir en la sección JTA del archivo de propiedades."
+
+#. Tag: para
+#: Transaction_Recovery.xml:67
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr "Cualquier error se reportará durante la recuperación. "
+
+#. Tag: screen
+#: Transaction_Recovery.xml:70
+#, no-c-format
+msgid ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+msgstr ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+
+#. Tag: para
+#: Transaction_Recovery.xml:71
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr "Cada método debe retornar la siguiente información: "
+
+#. Tag: para
+#: Transaction_Recovery.xml:76
+#, no-c-format
+msgid ""
+"<methodname>initialise</methodname>: once the instance has been created, any "
+"additional information which occurred on the property value (anything found "
+"after the first semi-colon) will be passed to the object. The object can "
+"then use this information in an implementation specific manner to initialise "
+"itself, for example."
+msgstr ""
+"<methodname>initialise</methodname>: una vez que la instancia ha sido "
+"creada, cualquier información adicional que tuvo lugar en el valor de la "
+"propiedad (cualquier cosa que se encuentre después del primer punto y coma) "
+"se le pasará al objeto. Luego el objeto puede utilizar esta información de "
+"una manera especifica para la implementación, por ejemplo, para "
+"inicializarse a sí mismo."
+
+#. Tag: para
+#: Transaction_Recovery.xml:81
+#, no-c-format
+msgid ""
+"<methodname>hasMoreResources</methodname>: each <code>XAResourceRecovery</"
+"code> implementation may provide multiple <code>XAResource</code> instances. "
+"Before any call to <methodname>getXAResource</methodname> is made, "
+"<methodname>hasMoreResources</methodname> is called to determine whether "
+"there are any further connections to be obtained. If this returns false, "
+"<methodname>getXAResource</methodname> will not be called again during this "
+"recovery sweep and the instance will not be used further until the next "
+"recovery scan."
+msgstr ""
+"<methodname>hasMoreResources</methodname>: cada implementación "
+"<code>XAResourceRecovery</code> puede proporcionar múltiples instancias "
+"<code>XAResource</code>. Antes de realizar cualquier llamada a "
+"<methodname>getXAResource</methodname>, se llama a "
+"<methodname>hasMoreResources</methodname> para determinar si hay más "
+"conexiones a obtener. Si retorna falso entonces no se llamará de nuevo a "
+"<methodname>getXAResource</methodname> durante este barrido de recuperación "
+"y no se utilizará la instancia más hasta el próximo escaneo de recuperación."
+
+#. Tag: para
+#: Transaction_Recovery.xml:86
+#, no-c-format
+msgid ""
+"<methodname>getXAResource</methodname>: returns an instance of the "
+"<code>XAResource</code> object. How this is created (and how the parameters "
+"to its constructors are obtained) is up to the <code>XAResourceRecovery</"
+"code> implementation. The parameters to the constructors of this class "
+"should be similar to those used when creating the initial driver or data "
+"source, and should obviously be sufficient to create new <code>XAResources</"
+"code> that can be used to drive recovery."
+msgstr ""
+"<methodname>getXAResource</methodname>: retorna una instancia del objeto "
+"<code>XAResource</code>. La manera en que es creada (y la manera en que se "
+"obtienen los parámetros y sus constructores) depende de la implementación "
+"<code>XAResourceRecovery</code>. Los parámetros para los constructores de "
+"esta clase deben ser similares a los que se utilizan cuando se crea el "
+"controlador inicial o la fuente de datos y obviamente debe ser suficiente "
+"para crear nuevos <code>XAResources</code> que se pueden utilizar para la "
+"recuperación."
+
+#. Tag: para
+#: Transaction_Recovery.xml:92
+#, no-c-format
+msgid ""
+"If you want your <code>XAResourceRecovery</code> instance to be called "
+"during each sweep of the recovery manager then you should ensure that once "
+"<methodname>hasMoreResources</methodname> returns false to indicate the end "
+"of work for the current scan it then returns true for the next recovery scan."
+msgstr ""
+"Si quiere que se llame a su instancia <code>XAResourceRecovery</code> "
+"durante cada barrido del administrador de recuperación entonces debe "
+"asegurarse de que una vez que <methodname>hasMoreResources</methodname> "
+"retorne falso para indicar el final del trabajo para el escaneo actual, "
+"entonces retorne verdadero para el próximo escaneo de recuperación."
+
+#. Tag: title
+#: Transaction_Recovery.xml:99
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr "Implementaciones XAResourceRecovery incluidas"
+
+#. Tag: para
+#: Transaction_Recovery.xml:100
+#, no-c-format
+msgid ""
+"Recovery of <interfacename>XA</interfacename> datasources can sometimes be "
+"implementation dependant, requiring developers to provide their own "
+"<interfacename>XAResourceRecovery</interfacename> instances. However, "
+"JBossTS ships with several out-of-the-box implementations that may be useful."
+msgstr ""
+"La recuperación de fuentes de datos <interfacename>XA</interfacename> "
+"algunas veces puede depender de la implementación, requiriendo que los "
+"desarrolladores proporcionen sus propias instancias "
+"<interfacename>XAResourceRecovery</interfacename>. Sin embargo, JBossTS se "
+"envía junto con varias implementaciones que pueden llegar a ser útiles."
+
+#. Tag: para
+#: Transaction_Recovery.xml:105
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: this expects an XML property file to be specified upon "
+"creation and from which it will read the database URL, username and "
+"password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: este espera que se especifique un archivo de propiedades XML "
+"en la creación y desde este se leerá la URL de la base de datos, el nombre "
+"de usuario y la contraseña. Por ejemplo:"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:108
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+
+#. Tag: para
+#: Transaction_Recovery.xml:111
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: this recovery implementation should work on any datasource "
+"that is exposed via JNDI. It expects an XML property file to be specified "
+"upon creation and from which it will read the database JNDI name, username "
+"and password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: esta implementación de recuperación debe funcionar en "
+"cualquier fuente de datos a la que esté expuesta a través de JNDI. Espera "
+"que se especifique un archivo de propiedades XML en la creación y desde el "
+"cual se leerá el nombre de la base de datos JNDI, el nombre de usuario y la "
+"contraseña. Por ejemplo:"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:114
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,669 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr "Transacciones"
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr "La API"
+
+#. Tag: para
+#: Transactions.xml:9
+#, no-c-format
+msgid ""
+"The Java Transaction API consists of three elements: a high-level "
+"application transaction demarcation interface, a high-level transaction "
+"manager interface intended for application server, and a standard Java "
+"mapping of the X/Open XA protocol intended for transactional resource "
+"manager. All of the JTA classes and interfaces occur within the "
+"<package>javax.transaction</package> package, and the corresponding JBossJTA "
+"implementations within the <package>com.arjuna.ats.jta</package> package."
+msgstr ""
+"La API de transacción Java consiste de tres elementos: una interfaz de "
+"demarcación de transacciones de aplicación de alto nivel, una interfaz "
+"administradora de transacciones a alto nivel para el servidor de "
+"aplicaciones y un mapeo Java estándar del protocolo X/Open XA previsto para "
+"el administrador de recursos transaccionales. Todas las clases JTA e "
+"interfaces tienen lugar dentro del paquete <package>javax.transaction</"
+"package> y las implementaciones JBossJTA correspondientes dentro del paquete "
+"<package>com.arjuna.ats.jta</package>."
+
+#. Tag: para
+#: Transactions.xml:13
+#, no-c-format
+msgid ""
+"Each 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. The contents of this "
+"should be alphanumeric."
+msgstr ""
+"Cada Xid que JBossTS crea debe tener un identificador de nodo único "
+"codificado dentro de este y JBossTS solo recuperará transacciones y estados "
+"que coincidan con un identificador de nodo especificado. El identificador de "
+"nodo a utilizar se le debe proporcionar a JBossTS por medio de la propiedad "
+"<property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property>. Debe "
+"asegurarse de que este valor es único a través de sus instancias JBossTS. Si "
+"no proporciona un valor entonces JBossTS fabricará uno y reportará el valor "
+"por medio de la infraestructura de registro. Su contenido debe ser "
+"alfanumérico."
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: Transactions.xml:19
+#, no-c-format
+msgid ""
+"The <interfacename>UserTransaction</interfacename> interface provides "
+"applications with the ability to control transaction boundaries. It has "
+"methods for beginning, committing, and rolling back top-level transactions: "
+"nested transactions are not supported, and begin throws the "
+"<code>NotSupportedException</code> when the calling thread is already "
+"associated with a transaction. <interfacename>UserTransaction</"
+"interfacename> automatically associates newly created transactions with the "
+"invoking thread."
+msgstr ""
+"La interfaz <interfacename>UserTransaction</interfacename> proporciona "
+"aplicaciones con la habilidad de controlar los límites de las transacciones. "
+"Tiene métodos para iniciar, guardar y deshacer transacciones a nivel "
+"superior: no se soportan las transacciones anidadas y begin presenta la "
+"excepción <code>NotSupportedException</code> cuando se llama al hilo que ya "
+"está asociado con una transacción. <interfacename>UserTransaction</"
+"interfacename> asocia de manera automática las transacciones recién creadas "
+"con el hilo invocador."
+
+#. Tag: para
+#: Transactions.xml:24
+#, no-c-format
+msgid ""
+"In JBossJTA, UserTransactions can be obtained from the static "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname> method."
+msgstr ""
+"En JBossJTA, las UserTransactions se pueden obtener del método estatico "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname>."
+
+#. Tag: para
+#: Transactions.xml:28
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+"Con el fin de seleccionar la implementación JTA local es necesario realizar "
+"los siguientes pasos: "
+
+#. Tag: para
+#: Transactions.xml:33
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</property>."
+msgstr ""
+"asegúrese de que la propiedad <property>com.arjuna.ats.jta."
+"jtaTMImplementation</property> está configurada como <property>com.arjuna."
+"ats.internal.jta.transaction.arjunacore.TransactionManagerImple</property>."
+
+#. Tag: para
+#: Transactions.xml:38
+#, no-c-format
+msgid ""
+"1.make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</property>."
+msgstr ""
+"1. asegúrese de que la propiedad <property>com.arjuna.ats.jta."
+"jtaUTImplementation</property> está configurada como <property>com.arjuna."
+"ats.internal.jta.transaction.arjunacore.UserTransactionImple</property>."
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: Transactions.xml:45
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface allows the "
+"application server to control transaction boundaries on behalf of the "
+"application being managed."
+msgstr ""
+"La interfaz <interfacename>TransactionManager</interfacename> le permite al "
+"servidor de aplicaciones el controlar los límites de las transacciones de "
+"parte de la aplicación que se está administrando."
+
+#. Tag: para
+#: Transactions.xml:50
+#, no-c-format
+msgid ""
+"In JBossJTA, transaction manager implementations can be obtained from the "
+"static <methodname>com.arjuna.ats.jta.TransactionManager.transactionManager</"
+"methodname> method."
+msgstr ""
+"En JBossJTA, las implementaciones del administrador de transacciones se "
+"pueden obtener del método estático <methodname>com.arjuna.ats.jta."
+"TransactionManager.transactionManager</methodname>."
+
+#. Tag: para
+#: Transactions.xml:54
+#, no-c-format
+msgid ""
+"The Transaction Manager maintains the transaction context association with "
+"threads as part of its internal data structure. A thread’s transaction "
+"context is either null or it refers to a specific global transaction. "
+"Multiple threads may be associated with the same global transaction. As "
+"noted above, nested transactions are not supported."
+msgstr ""
+"El administrador de transacciones mantiene la asociación del contexto de "
+"transacciones con hilos como parte de su estructura de datos internos. El "
+"contexto de transacción de un hilo puede ser nulo o puede referirse a una "
+"transacción global en especifico. Múltiples hilos pueden estar asociados con "
+"la misma transacción global. Como se notó anteriormente, no se soportan las "
+"transacciones anidadas. "
+
+#. Tag: para
+#: Transactions.xml:57
+#, no-c-format
+msgid ""
+"Each transaction context is encapsulated by a Transaction object, which can "
+"be used to perform operations which are specific to the target transaction, "
+"regardless of the calling thread’s transaction context."
+msgstr ""
+"Cada contexto de transacción es encapsulado por un objeto transacción, el "
+"cual se puede utilizar para realizar operaciones, las cuales son especificas "
+"para la transacción de destino, sin importar el contexto de transacción del "
+"hilo."
+
+#. Tag: para
+#: Transactions.xml:60
+#, no-c-format
+msgid ""
+"The <methodname>begin</methodname> method of "
+"<interfacename>TransactionManager</interfacename> starts a new top-level "
+"transaction and associates the transaction context with the calling thread. "
+"If the calling thread is already associated with a transaction then it "
+"throws the <code>NotSupportedException</code>."
+msgstr ""
+"El método <methodname>begin</methodname> de "
+"<interfacename>TransactionManager</interfacename> inicia una nueva "
+"transacción a nivel superior y asocia el contexto de transacción con el hilo "
+"que realiza la llamada. Si este hilo que realiza la llamada ya está asociado "
+"con una transacción entonces presenta la excepción "
+"<code>NotSupportedException</code>."
+
+#. Tag: para
+#: Transactions.xml:63
+#, no-c-format
+msgid ""
+"The <methodname>getTransaction</methodname> method returns the Transaction "
+"object that represents the transaction context currently associated with the "
+"calling thread. This object can be used to perform various operations on the "
+"target transaction, described later."
+msgstr ""
+"El método <methodname>getTransaction</methodname> retorna el objeto "
+"transacción que representa el contexto de transacción actualmente asociado "
+"con el hilo que realiza la llamada. Este objeto se puede utilizar para "
+"realizar varias operaciones en la transacción de destino que describiremos "
+"más adelante."
+
+#. Tag: para
+#: Transactions.xml:66
+#, no-c-format
+msgid ""
+"The commit method is used to complete the transaction currently associated "
+"with the calling thread. After it returns, the calling thread is associated "
+"with no transaction. If commit is called when the thread is not associated "
+"with any transaction context, the TM throws an exception. In some "
+"implementation, the commit operation is restricted to the transaction "
+"originator only. If the calling thread is not allowed to commit the "
+"transaction, the TM throws an exception. JBossJTA does not currently impose "
+"any restriction on the ability of threads to terminate transactions."
+msgstr ""
+"El método commit se utiliza para completar la transacción actualmente "
+"asociada con el hilo que realiza la llamada. Después de que retorna, el hilo "
+"que realiza la llamada no se asocia con ninguna transacción. Si se llama a "
+"commit cuando el hilo no está asociado con ningun contexto de transacción "
+"entonces el administrador de transacciones presenta una excepción. En "
+"algunas implementaciones, la operación commit está restringida solo para la "
+"transacción originadora. Si no se le permite guardar la transacción al hilo "
+"que realiza la llamada entonces el administrador de transacciones presenta "
+"una excepción. Actualmente JBossJTA no impone ninguna restricción en la "
+"habilidad de los hilos para terminar las transacciones. "
+
+#. Tag: para
+#: Transactions.xml:69
+#, no-c-format
+msgid ""
+"The <methodname>rollback</methodname> method is used to rollback the "
+"transaction associated with the current thread. After the "
+"<methodname>rollback</methodname> method completes, the thread is associated "
+"with no transaction."
+msgstr ""
+"El método <methodname>rollback</methodname> se utiliza para deshacer la "
+"transacción asociada con el hilo actual. Después de que el método "
+"<methodname>rollback</methodname> completa entonces el hilo no se asocia con "
+"ninguna transacción."
+
+#. Tag: para
+#: Transactions.xml:73
+#, no-c-format
+msgid ""
+"In a multi-threaded environment it is possible that multiple threads are "
+"active within the same transaction. If checked transaction semantics have "
+"been disabled, or the transaction times out, then it is possible for a "
+"transaction to be terminated by a thread other than the one that created it. "
+"In this case, it is often important that this information is communicated to "
+"the creator. JBossTS does this during commit or rollback by throwing "
+"<code>IllegalStateException</code>."
+msgstr ""
+"En un entorno multi-hilos es posible que múltiples hilos estén activos "
+"dentro de la misma transacción. Si se ha deshabilitado el chequeo de la "
+"semántica en las transacciones o si la transacción expira entonces es "
+"posible que una transacción sea finalizada por un hilo diferente al que la "
+"creó. En este caso, es importante que esta información se le comunique al "
+"creador, JBossTS lo hace al guardar o al deshacer los cambios presentando "
+"una <code>IllegalStateException</code>."
+
+#. Tag: title
+#: Transactions.xml:78
+#, no-c-format
+msgid "Suspending and resuming a transaction"
+msgstr "Suspender y retomar una transacción"
+
+#. Tag: para
+#: Transactions.xml:79
+#, no-c-format
+msgid ""
+"The JTA supports the concept of a thread temporarily suspending and resuming "
+"transactions to enable it to perform non-transactional work. The suspend "
+"method is called to temporarily suspend the current transaction that is "
+"associated with the calling thread, i.e., so that the thread is no longer "
+"operating within its scope. If the thread is not associated with any "
+"transaction, a null object reference is returned; otherwise, a valid "
+"<code>Transaction</code> object is returned. The <code>Transaction</code> "
+"object can later be passed to the resume method to reinstate the transaction "
+"context."
+msgstr ""
+"JTA soporta el concepto de un hilo suspendiendo y retomando transacciones de "
+"manera temporal para habilitarlo a realizar trabajo no transaccional. Se "
+"llama al método suspend para suspender de manera temporal la transacción "
+"actual que esté asociada con el hilo que realiza la llamada, por ejemplo, "
+"para que el hilo ya no esté operando dentro de su ámbito. Si el hilo no está "
+"asociado con ninguna transacción entonces se retorna una referencia de "
+"objeto nulo; de otra manera se retorna un objeto <code>Transaction</code> "
+"válido. Luego el objeto <code>Transaction</code> se puede pasar al método "
+"resume para restituir el contexto de la transacción. "
+
+#. Tag: para
+#: Transactions.xml:83
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method associates the specified "
+"transaction context with the calling thread. If the transaction specified is "
+"a valid transaction, the transaction context is associated with the calling "
+"thread; otherwise, the thread is associated with no transaction."
+msgstr ""
+"El método <methodname>resume</methodname> asocia el contexto de transacción "
+"especificado con el hilo que realiza la llamada. Si la transacción "
+"especificada es una transacción válida entonces el contexto de transacción "
+"está asociado con el hilo que realiza la llamada; de otra manera, el hilo no "
+"se asocia con ninguna transacción."
+
+#. Tag: para
+#: Transactions.xml:87
+#, no-c-format
+msgid ""
+"If <methodname>resume</methodname> is invoked when the calling thread is "
+"already associated with another transaction, the Transaction Manager throws "
+"the <code>IllegalStateException</code> exception."
+msgstr ""
+"Si se invoca a <methodname>resume</methodname> cuando el hilo que realiza la "
+"llamada ya está asociado con otra transacción entonces el administrador de "
+"transacciones presenta la excepción <code>IllegalStateException</code>. "
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+
+#. Tag: para
+#: Transactions.xml:93
+#, no-c-format
+msgid ""
+"Some Transaction Manager implementations allow a suspended transaction to be "
+"resumed by a different thread. This feature is not required by JTA, but "
+"JBossJTA does support this."
+msgstr ""
+"Algunas implementaciones del administrador de transacciones permiten que un "
+"hilo diferente retorme una transacción suspendida. JTA no requiere esta "
+"funcionalidad pero JBossJTA la soporta. "
+
+#. Tag: para
+#: Transactions.xml:97
+#, no-c-format
+msgid ""
+"When a transaction is suspended the application server must ensure that the "
+"resources in use by the application are no longer registered with the "
+"suspended transaction. When a resource is de-listed this triggers the "
+"Transaction Manager to inform the resource manager to disassociate the "
+"transaction from the specified resource object. When the application’s "
+"transaction context is resumed, the application server must ensure that the "
+"resources in use by the application are again enlisted with the transaction. "
+"Enlisting a resource as a result of resuming a transaction triggers the "
+"Transaction Manager to inform the resource manager to re-associate the "
+"resource object with the resumed transaction."
+msgstr ""
+"Cuando una transacción es suspendida el servidor de aplicaciones debe "
+"asegurarse de que los recursos que la aplicación utiliza ya no estén "
+"registrados con la transacción suspendida. Cuando un recurso es des-listado "
+"esto dispara que el administrador de transacciones le informe al "
+"administrador de recursos que desasocie la transacción del objeto de recurso "
+"especificado. Cuando de retoma el contexto de transacción de la aplicación, "
+"el servidor de aplicaciones debe asegurarse de que los recursos que la "
+"aplicación está utilizando se listen de nuevo con la transacción. El listar "
+"un recurso como resultado de retomar una transacción dispara que el "
+"administrador de transacciones le informe al administrador de recursos que "
+"re-asocie el objeto recurso con la transacción retomada. "
+
+#. Tag: title
+#: Transactions.xml:101
+#, no-c-format
+msgid "The Transaction interface"
+msgstr "La interfaz de la transacción"
+
+#. Tag: para
+#: Transactions.xml:102
+#, no-c-format
+msgid ""
+"The <interfacename>Transaction</interfacename> interface allows operations "
+"to be performed on the transaction associated with the target object. Every "
+"top-level transaction is associated with one <code>Transaction</code> object "
+"when the transaction is created. The <code>Transaction</code> object can be "
+"used to:"
+msgstr ""
+"La interfaz <interfacename>Transaction</interfacename> permite realizar "
+"operaciones en la transacción asociada con el objeto destino. Toda "
+"transacción a nivel superior se asocia con un objeto <code>Transaction</"
+"code> cuando se crea la transacción. El objeto <code>Transaction</code> se "
+"puede utilizar para: "
+
+#. Tag: para
+#: Transactions.xml:108
+#, no-c-format
+msgid "Enlist the transactional resources in use by the application."
+msgstr ""
+"Listar los recursos transaccionales que la aplicación está utilizando. "
+
+#. Tag: para
+#: Transactions.xml:113
+#, no-c-format
+msgid "Register for transaction synchronization call backs."
+msgstr "Registrar llamadas para la sincronización de transacciones."
+
+#. Tag: para
+#: Transactions.xml:118
+#, no-c-format
+msgid "Commit or rollback the transaction."
+msgstr "Guardar o deshacer la transacción."
+
+#. Tag: para
+#: Transactions.xml:123
+#, no-c-format
+msgid "Obtain the status of the transaction."
+msgstr "Obtener el estatus de la transacción. "
+
+#. Tag: para
+#: Transactions.xml:128
+#, no-c-format
+msgid ""
+"The <methodname>commit</methodname> and <methodname>rollback</methodname> "
+"methods allow the target object to be committed or rolled back. The calling "
+"thread is not required to have the same transaction associated with the "
+"thread. If the calling thread is not allowed to commit the transaction, the "
+"transaction manager throws an exception. At present JBossJTA does not impose "
+"restrictions on threads terminating transactions."
+msgstr ""
+"Los métodos <methodname>commit</methodname> y <methodname>rollback</"
+"methodname> le permiten guardar o deshacer los cambios del objeto de "
+"destino. No se requiere que el hilo que realiza la llamada tenga la misma "
+"transacción asociada con el hilo. Si no se le permite guardar la transacción "
+"al hilo que realiza la llamada entonces el administrador de transacciones "
+"presenta una excepción. Actualmente JBossJTA no impone restricciones en que "
+"los hilos terminen transacciones."
+
+#. Tag: title
+#: Transactions.xml:132
+#, no-c-format
+msgid "Resource enlistment"
+msgstr "Listado de recursos"
+
+#. Tag: para
+#: Transactions.xml:133
+#, no-c-format
+msgid ""
+"Transactional resources such as database connections are typically managed "
+"by the application server in conjunction with some resource adapter and "
+"optionally with connection pooling optimization. In order for an external "
+"transaction manager to co-ordinate transactional work performed by the "
+"resource managers, the application server must enlist and de-list the "
+"resources used in the transaction. These resources (participants) are "
+"enlisted with the transaction so that they can be informed when the "
+"transaction terminates, for example, are driven through the two-phase commit "
+"protocol."
+msgstr ""
+"Los recursos transaccionales tal como las conexiones de bases de datos "
+"usualmente son administradas por el servidor de aplicaciones en conjunto con "
+"algunos adaptadores de recursos y opcionalmente con optimización de pool de "
+"conexiones. Con el fin de que un administrador de transacciones externo "
+"coordine el trabajo transaccional realizado por los administradores de "
+"recursos, el servidor de aplicaciones debe listar y des-listar los recursos "
+"utilizados en la transacción. Estos recursos (participantes) se listan con "
+"la transacción de manera que se les pueda informar cuando la transacción "
+"termine, por ejemplo, se les conduce por el protocolo para guardar los "
+"cambios en dos fases."
+
+#. Tag: para
+#: Transactions.xml:137
+#, no-c-format
+msgid ""
+"As stated previously, the JTA is much more closely integrated with the XA "
+"concept of resources than the arbitrary objects. For each resource in-use by "
+"the application, the application server invokes the "
+"<methodname>enlistResource</methodname> method with an <code>XAResource</"
+"code> object which identifies the resource in use. See for details on how "
+"the implementation of the <code>XAResource</code> can affect recovery in the "
+"event of a failure."
+msgstr ""
+"Como lo mencionamos anteriormente, JTA está mucho más integrado con el "
+"concepto XA de los recursos que los objetos arbitrarios. Para cada recurso "
+"que la aplicación esté utilizando, el servidor de aplicaciones invoca el "
+"método <methodname>enlistResource</methodname> con un objeto "
+"<code>XAResource</code> el cual identifica el recurso en uso. Consulte los "
+"manuales para obtener más detalles sobre la manera en que la implementación "
+"del <code>XAResource</code> puede afectar la recuperación en caso de una "
+"falla. "
+
+#. Tag: para
+#: Transactions.xml:140
+#, no-c-format
+msgid ""
+"The enlistment request results in the transaction manager informing the "
+"resource manager to start associating the transaction with the work "
+"performed through the corresponding resource. The transaction manager is "
+"responsible for passing the appropriate flag in its <methodname>XAResource."
+"start</methodname> method call to the resource manager."
+msgstr ""
+"La petición de listado hace que el administrador de transacciones le informe "
+"al administrador de recursos que empiece a asociar la transacción con el "
+"trabajo realizado por medio del recurso correspondiente. El administrador de "
+"transacciones es el responsable de pasar la etiqueta apropiada en su llamada "
+"de método <methodname>XAResource.start</methodname> al administrador de "
+"recursos. "
+
+#. Tag: para
+#: Transactions.xml:143
+#, no-c-format
+msgid ""
+"The <methodname>delistResource</methodname> method is used to disassociate "
+"the specified resource from the transaction context in the target object. "
+"The application server invokes the method with the two parameters: the "
+"<code>XAResource</code> object that represents the resource, and a flag to "
+"indicate whether the operation is due to the transaction being suspended "
+"(TMSUSPEND), a portion of the work has failed (TMFAIL), or a normal resource "
+"release by the application (TMSUCCESS)."
+msgstr ""
+"El método <methodname>delistResource</methodname> se utiliza para desasociar "
+"el recurso especificado del contexto de la transacción en el objeto de "
+"destino. El servidor de aplicaciones invoca el método con los dos "
+"parámetros: el objeto <code>XAResource</code> que representa el recurso y "
+"una bandera para indicar si la operación se debe a que la transacción está "
+"suspendida (TMSUSPEND), una parte del trabajo ha fallado (TMFAIL), o que la "
+"aplicación ha liberado un recurso normal (TMSUCCESS)."
+
+#. Tag: para
+#: Transactions.xml:146
+#, no-c-format
+msgid ""
+"The de-list request results in the transaction manager informing the "
+"resource manager to end the association of the transaction with the target "
+"<code>XAResource</code>. The flag value allows the application server to "
+"indicate whether it intends to come back to the same resource whereby the "
+"resource states must be kept intact. The transaction manager passes the "
+"appropriate flag value in its <methodname>XAResource.end</methodname> method "
+"call to the underlying resource manager."
+msgstr ""
+"La petición para des-listar hace que el administrador de transacciones le "
+"informe al administrador de recursos que termine la asociación de la "
+"transacción con el <code>XAResource</code> de destino. El valor de la "
+"etiqueta le permite al servidor de aplicaciones que indique si pretende "
+"regresar al mismo recurso y que por lo tanto los estados de los recursos se "
+"deben mantener intactos. El administrador de transacciones pasa el valor "
+"apropiado de la etiqueta en su llamada de método <methodname>XAResource.end</"
+"methodname> al administrador de recursos subyacente. "
+
+#. Tag: title
+#: Transactions.xml:150
+#, no-c-format
+msgid "Transaction synchronization"
+msgstr "Sincronización de transacciones"
+
+#. Tag: para
+#: Transactions.xml:151
+#, no-c-format
+msgid ""
+"Transaction synchronization allows the application server to be notified "
+"before and after the transaction completes. For each transaction started, "
+"the application server may optionally register a Synchronization call back "
+"object to be invoked by the transaction manager:"
+msgstr ""
+"La sincronización de transacciones permite notificar al servidor de "
+"aplicaciones antes y después de que la transacción se completa. Para cada "
+"transacción que se inicia, el servidor de aplicaciones registra de manera "
+"opcional un objeto de llamada de sincronización que el administrador de "
+"transacciones va a invocar: "
+
+#. Tag: para
+#: Transactions.xml:157
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method is called prior to the "
+"start of the two-phase transaction complete process. This call is executed "
+"in the same transaction context of the caller who initiates the "
+"<methodname>TransactionManager.commit</methodname> or the call is executed "
+"with no transaction context if <methodname>Transaction.commit</methodname> "
+"is used."
+msgstr ""
+"Se llama al método <methodname>beforeCompletion</methodname> antes de "
+"iniciar el proceso para completar transacciones en dos fases. Esta llamada "
+"se ejecuta en el mismo contexto de transacción del que realiza la llamada "
+"que inicia el <methodname>TransactionManager.commit</methodname> o la "
+"llamada es ejecutada sin contexto de transacción si se utiliza "
+"<methodname>Transaction.commit</methodname>."
+
+#. Tag: para
+#: Transactions.xml:162
+#, no-c-format
+msgid ""
+"The <methodname>afterCompletion</methodname> method is called after the "
+"transaction has completed. The status of the transaction is supplied in the "
+"parameter. This method is executed without a transaction context."
+msgstr ""
+"Después de que se ha completado la transacción entonces se llama al método "
+"<methodname>afterCompletion</methodname>. El parámetro proporciona el "
+"estatus de la transacción. Este método es ejecutado sin un contexto de "
+"transacción."
+
+#. Tag: title
+#: Transactions.xml:168
+#, no-c-format
+msgid "Transaction equality"
+msgstr "Igualdad de transacciones"
+
+#. Tag: para
+#: Transactions.xml:169
+#, no-c-format
+msgid ""
+"The transaction manager implements the Transaction object’s equals method to "
+"allow comparison between the target object and another Transaction object. "
+"The equals method should return true if the target object and the parameter "
+"object both refer to the same global transaction."
+msgstr ""
+"El administrador de transacciones implementa el método de igualdad del "
+"objeto transacción para permitir la comparación entre el objeto de destino y "
+"otro objeto transacción. El método de igualdad debe retornar verdadero si el "
+"objeto destino y el objeto parámetro se refieren a la misma transacción "
+"global. "
+
+#. Tag: screen
+#: Transactions.xml:173
+#, no-c-format
+msgid ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
+msgstr ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/es-ES/Using_JBossJTA_in_Application_Servers.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,281 @@
+# translation of Author_Group.po to
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2009-01-21 15:41+1000\n"
+"Last-Translator: Angela Garcia\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
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr "Uso de JBossJTA en servidores de aplicaciones"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr "Servidor de aplicaciones de JBoss"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:10
+#, no-c-format
+msgid "Service Configuration"
+msgstr "Configuración del servicio"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:11
+#, no-c-format
+msgid ""
+"The JBoss Transaction Service is configured primarily via the XML files "
+"stored in the etc directory, but when run as a JBOSS service there are a "
+"number of configurable attributes available. They are as follows:"
+msgstr ""
+"El servicio de transacciones de JBoss se configura principalmente por medio "
+"de los archivos XML almacenados en el directorio etc, pero cuando ejecuta "
+"como un servicio JBOSS hay un número de atributos configurables disponibles. "
+"Son los siguientes: "
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:17
+#, no-c-format
+msgid ""
+"TransactionTimeout – The default transaction timeout to be used for new "
+"transactions. Specified as an integer in seconds."
+msgstr ""
+"TransactionTimeout – El tiempo de expiración predeterminado de la "
+"transacción a utilizar para las nuevas transacciones. Se especifica como un "
+"número entero en segundos."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:22
+#, no-c-format
+msgid ""
+"StatisticsEnabled – This determines whether or not the transaction service "
+"should gather statistical information. This information can then be viewed "
+"using the PerformanceStatistics MBean. Specified as a Boolean. The default "
+"is to not gather this information."
+msgstr ""
+"StatisticsEnabled – Este determina si el servicio de transacciones debe "
+"recolectar información estadística. Luego esta información se puede ver "
+"utilizando el MBean PerformanceStatistics. Especificado como un valor "
+"Boolean. El valor predeterminado es no recolectar esta información."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:27
+#, no-c-format
+msgid ""
+"PropagateFullContext – This determines whether a full transactional context "
+"is propagated by context importer/exporter. If set to false only the current "
+"transaction context is propagated. If set to true the full transaction "
+"context (including parent transactions) is propagated."
+msgstr ""
+"PropagateFullContext – Este determina si un contexto transaccional completo "
+"se propaga por contexto importador/exportador. Si se configura como falso "
+"entonces solo se propaga el contexto de transacción actual. Si se configura "
+"como verdadero entonces se propaga el contexto de transacción completo "
+"(incluyendo las transacciones padres)."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:32
+#, no-c-format
+msgid ""
+"These attributes are specified as MBean attributes in the jboss-service.xml "
+"file located in the server/all/conf directory, for example:"
+msgstr ""
+"Estos atributos se especifican como atributos MBean en el archivo jboss-"
+"service.xml que se encuentra en el directorio server/all/conf, por ejemplo:"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:35
+#, no-c-format
+msgid ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+msgstr ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:36
+#, no-c-format
+msgid ""
+"The transaction service is configurable also via the standard JBoss "
+"Transaction Service property files. These are located in the JBossTS install "
+"location under the etc sub-directory."
+msgstr ""
+"El servicio de transacciones es configurable también por medio de los "
+"archivos de propiedades estándares del servicio de transacciones de JBoss. "
+"Estos se encuentran en el lugar de instalación de JBossTS bajo el "
+"subdirectorio etc. "
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:39
+#, no-c-format
+msgid ""
+"These files can be edited manually or through JMX. Each property file is "
+"exposed via an object with the name <code>com.arjuna.ts.properties</code> "
+"and an attribute of module where module is equal to the name of the module "
+"to be configured, for example, <code>com.arjuna.ts.properties:module=arjuna</"
+"code>."
+msgstr ""
+"Estos archivos se pueden modificar manualmente o por medio de JMX. Cada "
+"archivo de propiedades se expone a través de un objeto con el nombre "
+"<code>com.arjuna.ts.properties</code> y un atributo del módulo en donde el "
+"módulo es igual al nombre del módulo a configurar, por ejemplo, <code>com."
+"arjuna.ts.properties:module=arjuna</code>."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:43
+#, no-c-format
+msgid "Logging"
+msgstr "Registros"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:44
+#, no-c-format
+msgid ""
+"In order to make JBossTS logging semantically consistent with JBossAS, the "
+"TransactionManagerService modifies the level of some log messages. This is "
+"achieved by overriding the value of the <property>com.arjuna.common.util."
+"logger</property> property given in the <filename>jbossjta-properties.xml</"
+"filename> file. Therefore, the value of this property will have no effect on "
+"the logging behaviour when running embedded in JBossAS. By forcing use of "
+"the log4j_releveler logger, the TransactionManagerService causes all INFO "
+"level messages in the transaction code to be modified to behave as DEBUG "
+"messages. Therefore, these messages will not appear in log files if the "
+"filter level is INFO. All other log messages behave as normal."
+msgstr ""
+"Con el fin de hacer los registros de JBossTS semánticamente consistentes con "
+"JBossAS, el TransactionManagerService modifica el nivel de algunos de los "
+"mensajes de registros. Esto se logra sobreescribiendo el valor de la "
+"propiedad <property>com.arjuna.common.util.logger</property> dado en el "
+"archivo <filename>jbossjta-properties.xml</filename>. Por lo tanto, el valor "
+"de esta propiedad no tendrá efecto en el comportamiento de los registros "
+"cuando se ejecuta como parte de JBossAS. Al forzar el uso del registro "
+"log4j_releveler, el TransactionManagerService hace que todos los mensajes a "
+"nivel INFO en el código de transacción sean modificados para que se "
+"comporten como mensajes DEBUG. Por lo tanto, estos mensajes no aparecerán en "
+"los archivos de registros si el filtro tiene un nivel INFO. Todos los demás "
+"mensajes de registro se comportan de manera normal. "
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:49
+#, no-c-format
+msgid "The services"
+msgstr "Los servicios"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:50
+#, no-c-format
+msgid ""
+"There is currently one service offered by the JBOSS integration called "
+"TransactionManagerService. Here we shall discuss what this service does."
+msgstr ""
+"Actualmente hay un servicio ofrecido por la integración JBOSS llamado "
+"TransactionManagerService. Aquí vamos a discutir lo que este sistema hace. "
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:54
+#, no-c-format
+msgid ""
+"The transaction manager service’s main purpose is to ensure the recovery "
+"manager is started. It also binds the JBossTS JTA transaction manager to "
+"java:/TransactionManager name with the JNDI provider. This service depends "
+"upon the existence of the CORBA ORB Service and it must be using JacORB as "
+"the underlying ORB implementation."
+msgstr ""
+"El propósito principal del servicio administrador de transacciones es "
+"asegurarse de iniciar el administrador de recuperación. También vincula el "
+"administrador de transacciones JBossTS JTA al nombre java:/"
+"TransactionManager con el proveedor JNDI. Este servicio depende de la "
+"existencia del servicio CORBA ORB y debe utilizar JacORB como la "
+"implementación ORB subyacente. "
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:57
+#, no-c-format
+msgid "There are two instances of this service:"
+msgstr "Hay dos instancias de este servicio: "
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:62
+#, no-c-format
+msgid ""
+"distributed: this uses the JTS enabled transaction manager implementation "
+"and hence supports distributed transactions and recovery. To configure this "
+"use the <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname> class. This is the default configuration."
+msgstr ""
+"distribuido: este utiliza la implementación del administrador de "
+"transacciones habilitado JTS y por lo tanto soporta recuperación y "
+"transacciones distribuidas. Para configurarlo utilice la clase "
+"<classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname>. Esta es la configuración predeterminada."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:67
+#, no-c-format
+msgid ""
+"local: this uses the purely local JTA implementation. To configure this use "
+"the <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
+"classname> class."
+msgstr ""
+"local: este utiliza sólamente la implementación local JTA. Para configurarlo "
+"utilice la clase <classname>com.arjuna.ats.jbossatx.jta."
+"TransactionManagerService</classname>."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:73
+#, no-c-format
+msgid "Ensuring Transactional Context is Propagated to the Server"
+msgstr ""
+"Asegurarse de que el contexto transaccional es propagado en el servidor"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:74
+#, no-c-format
+msgid ""
+"It is possible to coordinate transactions from a coordinator which is not "
+"located within the JBoss server (e.g. using transactions created by an "
+"external OTS server). To ensure the transaction context is propagated via "
+"JRMP invocations to the server, the transaction propagation context factory "
+"needs to be explicitly set for the JRMP invoker proxy. This is done as "
+"follows:"
+msgstr ""
+"Es posible el coordinar transacciones de un coordinador que no se encuentre "
+"dentro del servidor JBoss (por ejemplo, usando transacciones creadas por un "
+"servidor OTS externo). Para asegurarse de que el contexto de transacción es "
+"propagado por medio de invocaciones JRPM al servidor, la fábrica del "
+"contexto de propagación de transacciones necesita ser configurado "
+"explícitamente para el proxy invocador JRPM. Esto se hace así: "
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/An_Introduction_to_the_JTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/An_Introduction_to_the_JTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/An_Introduction_to_the_JTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,156 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr "Une introduction à JTA"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr "L'API de transaction Java"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:9
+#, no-c-format
+msgid ""
+"The interfaces specified by the many transaction standards are typically too "
+"low-level for most application programmers. Therefore, Sun Microsystems has "
+"specified higher-level interfaces to assist in the development of "
+"distributed transactional applications. Note, these interfaces are still low-"
+"level, and require, for example, the programmer to be concerned with state "
+"management and concurrency for transactional application. In addition, they "
+"are geared more for applications which require XA resource integration "
+"capabilities, rather than the more general resources which the other APIs "
+"allow."
+msgstr ""
+"Les interfaces spécifiées par la plupart des standards de transaction sont "
+"normalement trop basiques pour la plupart des programmeurs d'applications. "
+"De ce fait, Sun Microsystems spécifie des interfaces de haut niveau pour "
+"assister le développement d'applications transactionnelles distribuées. "
+"Notez que ces interfaces sont toujours basiques, et exigent, par exemple, "
+"que le programmeur s'inquiète de la concurrence et de la gestion des états "
+"pour les applications transactionnelles. De plus, elles sont conçues surtout "
+"pour des applications qui nécessitent des capacités d'intégration de "
+"ressources XA, plutôt que des ressources plus généralement autorisées par "
+"les autres API."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:12
+#, no-c-format
+msgid ""
+"With reference to [JTA99], distributed transaction services typically "
+"involve a number of participants:"
+msgstr ""
+"Si on se réfère à [JTA99], les services de transactions distribuées "
+"impliquent en général un certain nombre de participants :"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:17
+#, no-c-format
+msgid ""
+"Application server: which provides the infrastructure required to support "
+"the application run-time environment which includes transaction state "
+"management, for example, an EJB server."
+msgstr ""
+"Serveur d'application : qui fournit l'infrastructure nécessaire pour prendre "
+"en charge l'environnement d'exécution de l'application, comprenant la "
+"gestion de l'état de la transaction, comme par exemple, un serveur EJB."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:22
+#, no-c-format
+msgid ""
+"Transaction manager: provides the services and management functions required "
+"to support transaction demarcation, transactional resource management, "
+"synchronisation and transaction context propagation."
+msgstr ""
+"Le gestionnaire de transaction : fournit des fonctions de gestion et de "
+"services qui sont utiles au support de la démarcation de la transaction, à "
+"la gestion des ressources transactionnelles, à la propagation du contexte de "
+"transaction et à la synchronisation."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:27
+#, no-c-format
+msgid ""
+"Resource manager: (through a resource adapter<footnote> <para> A Resource "
+"Adapter is used by an application server or client to connect to a Resource "
+"Manager. JDBC drivers which are used to connect to relational databases are "
+"examples of Resource Adapters. </para> </footnote>) provides the application "
+"with access to resources. The resource manager participates in distributed "
+"transactions by implementing a transaction resource interface used by the "
+"transaction manager to communicate transaction association, transaction "
+"completion and recovery."
+msgstr ""
+"Le gestionnaire de ressources : ( à travers un adaptateur de ressources "
+"<footnote><para> Un adaptateur de ressources est utilisé par un serveur "
+"d'applications ou par un client pour connecter à un gestionnaire de "
+"ressources. Les pilotes JDBC qui sont utilisés pour connecter aux bases de "
+"données relationnelles constituent des exemples d'adaptateurs de ressources. "
+"</para> </footnote>) fournit une application ayant accès à la ressource. Le "
+"gestionnaire de ressources participe aux transactions distribuées en "
+"implémentant une interface de ressource de transactions utilisée par le "
+"gestionnaire de transactions pour communiquer une association de "
+"transaction, la fin d'une transaction et pendant son recouvrement."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:36
+#, no-c-format
+msgid ""
+"A communication resource manager (CRM): supports transaction context "
+"propagation and access to the transaction service for incoming and outgoing "
+"requests."
+msgstr ""
+"Un CRM (Communication Resource Manager / Gestionnaire de ressources de "
+"communication) : prend en charge la propagation du contexte de transaction "
+"et accède au service de transactions pour les demandes internes ou externes."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:41
+#, no-c-format
+msgid ""
+"From the transaction manager’s perspective, the actual implementation of the "
+"transaction services does not need to be exposed; only high-level interfaces "
+"need to be defined to allow transaction demarcation, resource enlistment, "
+"synchronization and recovery process to be driven from the users of the "
+"transaction services. The JTA is a high-level application interface that "
+"allows a transactional application to demarcate transaction boundaries, and "
+"contains also contains a mapping of the X/Open XA protocol."
+msgstr ""
+"Du côté du gestionnaire de transactions, l'implémentation des services de "
+"transactions n'a pas besoin d'être exposée, seuls les interfaces de haut "
+"niveau ont besoin d'être définies pour permettre la démarcation de la "
+"transaction, la liste des ressources, la synchronisation et le processus de "
+"recouvrement initiés par les utilisateurs des services de transaction. JTA "
+"est une interface d'application de haut niveau qui permet à une application "
+"transactionnelle de fixer des limites de transaction, et qui contient aussi "
+"un mappage du protocole X/Open XA."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:45
+#, no-c-format
+msgid ""
+"The JTA support provided by JBossJTA is compliant with the 1.0.1 "
+"specification."
+msgstr ""
+"Le support JTA fourni par JBossJTA est compatible avec la spécification "
+"1.0.1."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Author_Group.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Author_Group.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,23 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Book_Info.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Book_Info.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,49 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#, fuzzy, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide CP04"
+msgstr "Guide des programmeurs de transactions JTA JBoss"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "à utiliser avec JBoss Enterprise Application Platform 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+"Cet ouvrage aborde les transactions JTA pour le bénéfice du programmeur"
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Configuring_JBossJTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Configuring_JBossJTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Configuring_JBossJTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,145 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr "Configurer JBossJTA"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:8
+#, no-c-format
+msgid "Configuring options"
+msgstr "Options de configuration"
+
+#. Tag: para
+#: Configuring_JBossJTA.xml:9
+#, no-c-format
+msgid ""
+"The following table shows the configuration features, with default values "
+"shown in italics. For more detailed information, the relevant section "
+"numbers are provided."
+msgstr ""
+"La table suivante montre les possibilités de configuration, avec les valeurs "
+"par défaut en italique. Pour davantage d'informations, vous trouverez les "
+"numéros de sections pertinents."
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:13
+#, no-c-format
+msgid "JBossJTA configuration options."
+msgstr "Options de configuration JBossJTA."
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:17
+#, no-c-format
+msgid "Configuration Name"
+msgstr "Nom de configuration"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:20
+#, no-c-format
+msgid "Possibile Values"
+msgstr "Valeurs possibles"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:23
+#, no-c-format
+msgid "Relevant Section"
+msgstr "Section pertinente"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:30
+#, no-c-format
+msgid "com.arjuna.ats.jta.supportSubtransactions"
+msgstr "com.arjuna.ats.jta.supportSubtransactions"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr "OUI/NON"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr "com.arjuna.ats.jta.jtaTMImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:43
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr "com.arjuna.ats.jta.jtaUTImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:53
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr "com.arjuna.ats.jta.xaBackoffPeriod"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr "com.arjuna.ats.jdbc.isolationLevel"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr "N'importe quel niveau d'isolation JDBC pris en charge."
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr "vrai/faux"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr "Chapitre 3"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Examples.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Examples.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Examples.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,834 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr "Exemples"
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr "Exemple JDBC"
+
+#. Tag: para
+#: Examples.xml:9
+#, no-c-format
+msgid ""
+"The following code illustrates many of the points described above (note that "
+"for simplicity, much error checking code has been remove). This example "
+"assumes that you are using the transactional JDBC driver provided with "
+"JBossTS. For details about how to configure and use this driver see the "
+"previous Chapter."
+msgstr ""
+"Le code suivant illustre de nombreux points décrits ci-dessus (notez que par "
+"souci de simplification, la plupart des codes de vérification ont été "
+"supprimés). Cet exemple assume que vous utilisez le pilote JDBC "
+"transactionnel fourni avec JBossTS. Pour des informations sur la façon de "
+"configurer ou d'utiliser ce pilote, voir le chapitre précédent."
+
+#. Tag: screen
+#: Examples.xml:12
+#, no-c-format
+msgid ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+msgstr ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+
+#. Tag: title
+#: Examples.xml:16
+#, no-c-format
+msgid "Failure recovery example"
+msgstr "Exemple de mise en échec de recouvrement"
+
+#. Tag: para
+#: Examples.xml:17
+#, no-c-format
+msgid ""
+"This class implements the <interfacename>XAResourceRecovery</interfacename> "
+"interface for <code>XAResources</code>. The parameter supplied in "
+"setParameters can contain arbitrary information necessary to initialize the "
+"class once created. In this instance it contains the name of the property "
+"file in which the db connection information is specified, as well as the "
+"number of connections that this file contains information on (separated "
+"by ;)."
+msgstr ""
+"Cette classe implémente l'interface <interfacename>XAResourceRecovery</"
+"interfacename> de <code>XAResources</code>. Le paramètre fourni dans "
+"setParameters peut contenir des informations arbitraires utiles pour "
+"initialiser la classe une fois qu'elle est créée. Dans ce cas, il contient "
+"les nom du fichier de propriétés dans lequel l'information de connexion db "
+"est indiquée, ainsi que le nombre de connexions pour lequelle ce fichier "
+"possède des informations (separées par ;)."
+
+#. Tag: para
+#: Examples.xml:21
+#, no-c-format
+msgid ""
+"This is only an <emphasis>example</emphasis> of the sorts of things an "
+"<code>XAResourceRecovery</code> implementer could do. This implementation "
+"uses a property file that is assumed to contain sufficient information to "
+"recreate connections used during the normal run of an application so that we "
+"can perform recovery on them. It is not recommended that information such as "
+"user name and password appear in such a raw text format as it opens up a "
+"potential security hole."
+msgstr ""
+"Il s'agit juste d'un <emphasis>exemple</emphasis> du genre de choses qu'un "
+"ingénieur d'applications <code>XAResourceRecovery</code> peut réaliser. "
+"Cette implémentation utilise un fichier de propriétés qui est censé contenir "
+"suffisamment d'informations pour recréer les connexions qui sont utilisées "
+"au cours normal de l'éxécution d'une application pour qu'on puisse effectuer "
+"un recouvrement dessus. On ne conseille pas que les informations comme le "
+"nom d'utilisation ou le mot de passe apparaissent sous forme de texte brut "
+"car c'est la porte ouverte à des lésions au niveau de la sécurité."
+
+#. Tag: para
+#: Examples.xml:25
+#, no-c-format
+msgid ""
+"The db parameters specified in the property file are assumed to be in the "
+"format:"
+msgstr ""
+"Les paramètres db précisés dans le fichier de propriétés doivent être du "
+"format suivant :"
+
+#. Tag: para
+#: Examples.xml:30
+#, no-c-format
+msgid "DB_x_DatabaseURL="
+msgstr "DB_x_DatabaseURL="
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr "DB_x_DatabaseUser="
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr "DB_x_DatabasePassword="
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr "DB_x_DatabaseDynamicClass="
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr "Quand x correspond au nombre d'informations de connexion."
+
+#. Tag: para
+#: Examples.xml:54
+#, no-c-format
+msgid ""
+"Some error handling code has been removed from this text for ease of "
+"readability purposes."
+msgstr ""
+"Un code de gestion des erreurs a été supprimé de ce texte pour en faciliter "
+"la lecture."
+
+#. Tag: screen
+#: Examples.xml:58
+#, no-c-format
+msgid ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+msgstr ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+
+#. Tag: para
+#: Examples.xml:59
+#, no-c-format
+msgid ""
+"The class <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> may be used to create a new connection "
+"to the database using the same parameters that were used to create the "
+"initial connection."
+msgstr ""
+"La classe <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> peut être utilisée pour créer une "
+"nouvelle connexion sur la base de données en utilisant les mêmes paramètres "
+"qui on été utilisés pour créer la connexion initiale."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
===================================================================
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/JDBC_and_Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/JDBC_and_Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/JDBC_and_Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,1022 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr "JDBC et Transactions"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr "Utilisation du pilote transactionnel JDBC"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:9
+#, no-c-format
+msgid ""
+"JBossJTA supports the construction of both local and distributed "
+"transactional applications which access databases using the JDBC 2.0 APIs. "
+"JDBC 2.0 supports two-phase commit of transactions, and is similar to the XA "
+"X/Open standard. The JDBC 2.0 support is found in the com.arjuna.ats.jdbc "
+"package."
+msgstr ""
+"JBossJTA prend en charge la construction des applications transactionnelles "
+"distribuées et locales dotées de bases de données utilisant les API JDBC "
+"2.0. JDBC 2.0 prend en charge des transactions validées en deux-étapes, et "
+"est semblable au standard XA X/Open. Le support JDBC 2.0 est présent dans le "
+"paquet com.arjuna.ats.jdbc ."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:12
+#, no-c-format
+msgid ""
+"The JDBC 2.0 support has been tested with the following drivers and "
+"databases:"
+msgstr ""
+"Le support JDBC 2.0 a été testé par les pilotes et par les bases de données "
+"suivantes :"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr "Oracle 8.1.6/8.1.7, 9i et pilote mince 10g."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr "Pilote natif MS SQL Server 2000."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:27
+#, no-c-format
+msgid "In the past we have qualified against:"
+msgstr "Dans le passé, nous nous sommes qualifiés pour :"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:32
+#, no-c-format
+msgid "Merant’s Sequelink 5.1 with Oracle 8.1.6"
+msgstr "Sequelink 5.1 de Merant avec Oracle 8.1.6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr "Cloudscape 3.6 avec la propre base de données de Cloudscape."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:42
+#, no-c-format
+msgid ""
+"However, these drivers and databases are no longer part of our supported "
+"platforms. They may continue to work with JBossTS, but we cannot make that "
+"guarantee."
+msgstr ""
+"Cependant, ces pilotes et ces bases de données ne font plus partie de nos "
+"plate-formes prises en charge. Ils peuvent peut-être toujours fonctionner "
+"avec JBossTS, mais nous ne pouvons le garantir."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:46
+#, no-c-format
+msgid "Managing transactions"
+msgstr "Gérer des transactions"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:47
+#, no-c-format
+msgid ""
+"JBossJTA must be able to associate work performed on a JDBC connection with "
+"a specific transaction. Therefore, implicit transaction propagation and/or "
+"indirect transaction management must be used by applications, i.e., for each "
+"JDBC connection it must be possible for JBossJTA to determine the invoking "
+"thread’s current transaction context."
+msgstr ""
+"JBossJTA devrait pouvoir associer une tâche effectuée sur une connexion JDBC "
+"avec une transaction spécifique. Ainsi, la propagation de transactions "
+"implicites et/ou la gestion de transactions indirectes doivent être "
+"utilisées par des applications, par exemple, pour chaque connexion JDBC, il "
+"doit être possible pour JBossJTA de déterminer le contexte de transaction "
+"courant du thread qui l'invoque."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:52
+#, no-c-format
+msgid "Restrictions"
+msgstr "Restrictions"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:53
+#, no-c-format
+msgid ""
+"The following restrictions are imposed by limitations in the JDBC "
+"specifications and by JBossJTA to ensure that transactional interactions "
+"with JDBC databases can be correctly managed:"
+msgstr ""
+"Les restrictions suivantes imposent les limites des spécifications JDBC et "
+"JBossJTA dans le but de veiller à ce que les interactions transactionnelles "
+"avec les bases de données JDBC soient gérées correctement."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:57
+#, no-c-format
+msgid ""
+"Nested transactions are not supported by JDBC 2.0. If an attempt is made to "
+"use a JDBC connection within a subtransaction, JBossJTA will throw a "
+"suitable exception and no work will be allowed on that connection. However, "
+"if you wish to have nested transactions, then you can set the <property>com."
+"arjuna.ats.jta.supportSubtransactions</property> property to YES."
+msgstr ""
+"Les transactions imbriquées ne sont pas supportées par JDBC 2.0. Si on tente "
+"d'utiliser une connexion JDBC au sein d'une sous-transaction, JBoss JTA "
+"lancera une exception correspondante et aucune tâche ne sera autorisée sur "
+"cette connexion. Cependant, si vous souhaitez avoir des transactions "
+"imbriquées, vous pouvez configurer la propriété <property>com.arjuna.ats.jta."
+"supportSubtransactions</property> à OUI."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:63
+#, no-c-format
+msgid "Transactional drivers"
+msgstr "Pilotes transactionnels"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:64
+#, no-c-format
+msgid ""
+"The JBossJTA approach to incorporating JDBC connections within transactions "
+"is to provide transactional JDBC drivers through which all interactions "
+"occur. These drivers intercept all invocations and ensure that they are "
+"registered with, and driven by, appropriate transactions. There is a single "
+"type of transactional driver through which any JDBC driver can be driven; "
+"obviously if the database is not transactional then ACID properties cannot "
+"be guaranteed. This driver is <code>com.arjuna.ats.jdbc.TransactionalDriver</"
+"code>, which implements the <interfacename>java.sql.Driver</interfacename> "
+"interface."
+msgstr ""
+"L'approche JBossJTA qui consiste à incorporer les connexions JDBC au sein "
+"des transactions, a pour but de fournir des pilotes JDBC transactionnels à "
+"travers lesquels toutes les transactions puissent être effectuées. Ces "
+"pilotes interceptent toutes les invocations et veillent à ce qu'elles soient "
+"enregistrées, et actionnées par les transactions qu'il faut. Il existe un "
+"seul type de pilote transactionnel qui puisse actionner n'importe quel "
+"pilote JDBC. Si la base de données n'est pas transactionnelle, alors les "
+"propriétés ACID ne peuvent pas être garanties. Le pilote est <code>com."
+"arjuna.ats.jdbc.TransactionalDriver</code>, qui implémente l'interface "
+"<interfacename>java.sql.Driver</interfacename> ."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:68
+#, no-c-format
+msgid "Loading drivers"
+msgstr "Pilotes de chargement"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:69
+#, no-c-format
+msgid ""
+"The driver may be directly instantiated and used within an application. For "
+"example:"
+msgstr ""
+"Le pilote peut être directement instancié et utilisé dans une application. "
+"Par exemple :"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:73
+#, no-c-format
+msgid "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+msgstr "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:74
+#, no-c-format
+msgid ""
+"They can be registered with the JDBC driver manager (<code>java.sql."
+"DriverManager</code>) by adding them to the Java system properties. The "
+"<property>jdbc.drivers</property> property contains a list of driver class "
+"names, separated by colons, that are loaded by the JDBC driver manager when "
+"it is initialized."
+msgstr ""
+"Ils peuvent être enregistrés par le gestionnaire du pilote JDBC (<code>java."
+"sql.DriverManager</code>) en les ajoutant aux propriétés du système Java. La "
+"propriété <property>jdbc.drivers</property> contient une liste de noms de "
+"classe de pilotes, séparés par des virgules, qui sont chargés par le "
+"gestionnaire du pilote JDBC quand il est initialisé."
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:77
+#, no-c-format
+msgid ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+msgstr ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:78
+#, no-c-format
+msgid ""
+"Alternatively, the <methodname>Class.forName()</methodname> method may be "
+"used to load the driver or drivers:"
+msgstr ""
+"Ou bien, on peut utiliser la méthode <methodname>Class.forName()</"
+"methodname> pour charger le ou les pilotes :"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:82
+#, no-c-format
+msgid ""
+"Calling <methodname>Class.forName()</methodname> will automatically register "
+"the driver with the JDBC driver manager. It is also possible to explicitly "
+"create an instance of the JDBC driver:"
+msgstr ""
+"Appeler <methodname>Class.forName()</methodname> va automatiquement "
+"enregistrer le pilote auprès du gestionnaire du pilote JDBC. Il est "
+"également possible de créer explicitement une instance du pilote JDBC :"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:85
+#, no-c-format
+msgid ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+msgstr ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:86
+#, no-c-format
+msgid ""
+"When you have loaded a driver, it is available for making a connection with "
+"a DBMS."
+msgstr ""
+"Quand vous aurez chargé un pilote, il sera disponible pour pouvoir effectuer "
+"une connexion avec un DBMS."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:92
+#, no-c-format
+msgid "Connections"
+msgstr "Connexions"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:93
+#, no-c-format
+msgid ""
+"In this section we shall discuss the notion of transactional JDBC "
+"connections, how they are managed within JBossJTA and the implications on "
+"using them within an application."
+msgstr ""
+"Dans cette section, nous allons discuter la notion de connexions JDBC "
+"transactionnelles, la façon dont elles sont gérées dans JBossJTA et les "
+"implications de leur utilisation au sein d'une application."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:97
+#, no-c-format
+msgid "Making the connection"
+msgstr "Effectuer des connexions"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:98
+#, no-c-format
+msgid ""
+"Because JDBC connectivity in JBossJTA works by simply providing a new JDBC "
+"driver, application code can remain relatively the same to that when not "
+"using transactions. Typically, the application programmer need only start "
+"and terminate transactions."
+msgstr ""
+"Comme la connectivité JDBC de JBossJTA fonctionne tout simplement en "
+"fournissant un nouveau pilote JDBC, le code d'application peut rester "
+"relativement le même que celui qui existe lorsqu'on n'utilise pas de "
+"transactions. Typiquement, le programmateur d'applications n'est là que pour "
+"démarrer ou pour terminer les transactions."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr "JDBC 2.0"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:104
+#, no-c-format
+msgid ""
+"Before describing the JDBC 2.0 support it is necessary to mention that the "
+"following properties can be set and passed to the JBossJTA driver (they are "
+"all located in the <classname>com.arjuna.ats.jdbc.TransactionalDriver</"
+"classname> class):"
+msgstr ""
+"Avant de décrire la prise en charge JDBC 2.0, il semble utile de mentionner "
+"que les propriétés suivantes peuvent être déterminées et passées au pilote "
+"JBossJTA (elles sont toutes situées dans la classe <classname>com.arjuna.ats."
+"jdbc.TransactionalDriver</classname> ) :"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:110
+#, no-c-format
+msgid ""
+"<property>userName</property>: the user name to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>userName</property>: le nom d'utilisateur pour tenter de connecter "
+"à la base de données."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:115
+#, no-c-format
+msgid ""
+"<property>password</property>: the password to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>password</property>: le mot de passe à utiliser pour tenter de "
+"connecter à la base de données."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:120
+#, no-c-format
+msgid ""
+"<property>createDb</property>: if set to true, the driver will attempt to "
+"create the database when it connects. This may not be supported by all JDBC "
+"2.0 implementations."
+msgstr ""
+"<property>createDb</property>: s'il est configuré sur 'True' (vrai), le "
+"pilote tentera de créer la base de données lorsqu'il connecte. Ceci n'est "
+"pas pris en charge par toutes les implémentations JDBC 2.0."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:125
+#, no-c-format
+msgid ""
+"<property>dynamicClass</property>: this specifies a class to instantiate to "
+"connect to the database, rather than using JNDI."
+msgstr ""
+"<property>dynamicClass</property>: spécifie une classe à instancier pour se "
+"connecter à la base de données, plutôt que d'utiliser JNDI."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr "XADataSources"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:132
+#, no-c-format
+msgid ""
+"JDBC 2.0 connections are created from appropriate DataSources. Those "
+"connections which must participate within distributed transactions are "
+"obtained from <code>XADataSources</code>. Therefore, when using a JDBC 2.0 "
+"driver, JBossJTA will use the appropriate DataSource whenever a connection "
+"to the database is made. It will then obtain <code>XAResources</code> and "
+"register them with the transaction via the JTA interfaces. It is these "
+"<code>XAResources</code> which the transaction service will use when the "
+"transaction terminates in order to drive the database to either commit or "
+"rollback the changes made via the JDBC connection."
+msgstr ""
+"Les connexions JDBC 2.0 sont créées à partir des DataSources qui "
+"conviennent. Ces connexions, qui doivent participer au sein des transactions "
+"distribuées, sont obtenues à partir du code <code>XADataSources</code>. "
+"Ainsi, lorsque vous utilisez un pilote JDBC 2.0, JBossJTA utilisera la "
+"DataSource appropriée à chaque fois qu'on effectue une connexion vers la "
+"base de données. JBossJTA obtiendra alors <code>XAResources</code> et les "
+"enregistrera avec la transaction par les interfaces JTA. Ce sont ces "
+"<code>XAResources</code> que le service de transaction va utiliser quand la "
+"transaction se termine en vue d'entraîner la base de donnée à valider ou "
+"bien à renvoyer les changements effectués via la connexion JDBC."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:136
+#, no-c-format
+msgid ""
+"There are two ways in which the JBossJTA JDBC 2.0 support can obtain "
+"<code>XADataSources</code>. These will be explained in the following "
+"sections. Note, for simplicity we shall assume that the JDBC 2.0 driver is "
+"instantiated directly by the application."
+msgstr ""
+"Il existe deux façons par lesquelles la prise en charge JBossJTA JDBC 2.0 "
+"puisse obtenir <code>XAResources</code>. Elles seront toutes deux expliquées "
+"dans les sections suivantes. Notez bien, que dans un souci de "
+"simplification, nous assumerons que le pilote JDBC 2.0 est instancié "
+"directement par l'application."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr ""
+"JNDI (Java Naming and Directory Interface / Nommage Java et Interface "
+"Répertoire)"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:141
+#, no-c-format
+msgid ""
+"In order to allow a JDBC driver to use arbitrary DataSources without having "
+"to know specific details about their implementations, DataSources are "
+"typically obtained from JNDI. A specific (XA)DataSource can be created and "
+"registered with an appropriate JNDI implementation, and the application (or "
+"JDBC driver) can later bind to and use it. Since JNDI only allows the "
+"application to see the (XA)DataSource as an instance of the interface (for "
+"example, <property>javax.sql.XADataSource</property>) rather than as an "
+"instance of the implementation class (for example, <property>com.mydb."
+"myXADataSource</property>), the application is not tied at build time to "
+"only use a specific (XA)DataSource implementation."
+msgstr ""
+"Pour pouvoir permettre à un pilote JDBC d'utiliser arbitrairement "
+"DataSources sans avoir à connaître des détails spécifiques sur leurs "
+"implémentations, DataSources proviennent normalement de JNDI. Une (XA)"
+"DataSource particulière peut être créée et enregistrée par une "
+"implémentation JNDI qui convient, et l'application (ou le pilote JDBC) peut "
+"plus tard s'y attacher et l'utiliser. Comme JNDI autorise uniquement "
+"l'application qui permet de considérer (XA)DataSource en tant qu'instance de "
+"l'interface (par exemple, <property>javax.sql.XADataSource</property>) "
+"plutôt qu'une instance de la classe d'implémentation (par exemple, "
+"<property>com.mydb.myXADataSource</property>), l'application n'est pas "
+"forcée d'utiliser uniquement une implémentation (XA)DataSource particulière "
+"au moment de la construction."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:145
+#, no-c-format
+msgid ""
+"To get the <classname>TransactionalDriver</classname> class to use a JNDI "
+"registered <code>XADataSource</code> it is first necessary to create the "
+"<code>XADataSource</code> instance and store it in an appropriate JNDI "
+"implementation. Details of how to do this can be found in the JDBC 2.0 "
+"tutorial available at JavaSoft. An example is show below:"
+msgstr ""
+"Pour obtenir une classe <classname>TransactionalDriver</classname> en vue "
+"d'utiliser une <code>XADataSource</code> enregistrée JNDI, il faut tout "
+"d'abord créer l'instance <code>XADataSource</code> et la sauvegarder dans "
+"une implémentation JNDI qui convient. On peut trouver des détails sur la "
+"façon de procéder dans le tutoriel JDBC 2.0 disponible à JavaSoft. En voici "
+"un exemple :"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:148
+#, no-c-format
+msgid ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+msgstr ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:149
+#, no-c-format
+msgid ""
+"Where the <property>Context.INITIAL_CONTEXT_FACTORY</property> property is "
+"the JNDI way of specifying the type of JNDI implementation to use."
+msgstr ""
+"Quand la propriété <property>Context.INITIAL_CONTEXT_FACTORY</property> "
+"correspond à la façon dont JNDI puisse spécifier le type d'implémentation "
+"JNDI à utiliser."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:152
+#, no-c-format
+msgid ""
+"Then the application must pass an appropriate connection URL to the JDBC 2.0 "
+"driver:"
+msgstr ""
+"Alors, l'application doit passer une connexion URL qui convient au pilote "
+"JDBC 2.0 :"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:155
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:156
+#, no-c-format
+msgid ""
+"The JNDI URL must be pre-pended with jdbc:arjuna: in order for the "
+"<code>ArjunaJDBC2Driver</code> to recognise that the DataSource must "
+"participate within transactions and be driven accordingly."
+msgstr ""
+"L'URL JNDI devra être ajouté en préfixe avec jdbc.arjuna: de façon à ce que "
+"<code>ArjunaJDBC2Driver</code> reconnaisse que DataSource doive participer "
+"aux transactions et être actionné en fonction."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:160
+#, no-c-format
+msgid "Dynamic class instantiation"
+msgstr "Instanciation de classes dynamiques"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:161
+#, no-c-format
+msgid ""
+"Many JDBC 2.0 implementations provide proprietary implementations of "
+"<interfacename>XADataSources</interfacename> that provide non-standard "
+"extensions to the specification. In order to allow the application to remain "
+"isolated from the actual JDBC 2.0 implementation it is using and yet "
+"continue to be able to use these extensions, JBossJTA hides the details of "
+"these proprietary implementations using dynamic class instantiation. In "
+"addition, the use of JNDI is not required when using this mechanism because "
+"the actual implementation of the <interfacename>XADataSource</interfacename> "
+"will be directly instantiated, albeit in a manner which will not tie an "
+"application or driver to a specific implementation. JBossJTA therefore has "
+"several classes which are for specific JDBC 2.0 implementations, and these "
+"can be selected at runtime by the application setting the "
+"<property>dynamicClass</property> property appropriately:"
+msgstr ""
+"De nombreuses implémentations JDBC 2.0 fournissent des implémentations "
+"propriétaires de <interfacename>XADataSources</interfacename> qui "
+"fournissent des extensions non-standards à la spécification. Pour permettre "
+"à l'application de demeurer isolée par rapport à l'implémentation JDBC 2.0 "
+"actuelle, elle utilise et est toujours en mesure d'utiliser ces extensions. "
+"JBossJTA cache les détails d'implémentations propriétaires en utilisant "
+"l'instanciation de classes dynamiques. De plus, l'utilisation de JNDI n'est "
+"pas exigée lorsqu'on utilise ce mécanisme car l'implémentation de "
+"<interfacename>XADataSources</interfacename> sera directement instanciée, "
+"albeit sans pour autant attacher à une application ou à un pilote à une "
+"implémentation particulière. JBossJTA comprend ainsi de nombreuses classes "
+"qui correspondent à des implémentations JDBC 2.0 particulières et elles "
+"peuvent être sélectionnées en cours d'exécution par l'application qui fixe "
+"la propriété <property>dynamicClass</property> qui convient :"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:166
+#, no-c-format
+msgid "Dynamic Class property values for specific databases"
+msgstr ""
+"Valeurs de propriété de classes dynamiques applicables à des bases de "
+"données particulières"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:170
+#, no-c-format
+msgid "Database Type"
+msgstr "Type de bases de données"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:173
+#, no-c-format
+msgid "Property Name"
+msgstr "Nom de propriété"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:180
+#, no-c-format
+msgid "Cloudscape 3.6"
+msgstr "Cloudscape 3.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr "Sequelink 5.1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr "Oracle 8.1.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:207
+#, no-c-format
+msgid ""
+"As mentioned earlier, JBossTS no longer supports Cloudscape or Sequelink as "
+"part of the qualified drivers. Furthermore, we recommend using JNDI to "
+"obtain JDBC classes rather than the direct method described here."
+msgstr ""
+"Comme mentionné plus haut, JBossTS ne prend plus en charge Cloudscape ou "
+"Sequelink en tant que pilotes qualifiés. De plus, nous recommandons "
+"d'utiliser JNDI pour obtenir les classes JDBC plutôt que la méthode directe "
+"décrite ici."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:211
+#, no-c-format
+msgid ""
+"The application code must specify which dynamic class the "
+"<code>TransactionalDriver</code> should instantiate when setting up the "
+"connection:"
+msgstr ""
+"Le code de l'application doit spécifier quelle classe dynamique "
+"<code>TransactionalDriver</code> doit instancier lorsqu'il configure la "
+"connexion :"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:214
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:216
+#, no-c-format
+msgid "Using the connection"
+msgstr "Utiliser la connexion"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:217
+#, no-c-format
+msgid ""
+"Once the connection has been established (for example, using the "
+"<methodname>java.sql.DriverManager.getConnection</methodname> method), all "
+"operations on the connection will be monitored by JBossJTA. Note, it is not "
+"necessary to use the transactional connection within transactions. If a "
+"transaction is not present when the connection is used, then operations will "
+"be performed directly on the database."
+msgstr ""
+"Une fois que la connexion a été établie (par exemple, en utilisant la "
+"méthode <methodname>java.sql.DriverManager.getConnection</methodname> ), "
+"toutes les opérations sur cette connexion seront contrôlées par JBossJTA. "
+"Notez qu'il n'est pas nécessaire d'utiliser la connexion transactionnelle au "
+"sein des transactions elles-mêmes. Si une transaction n'est pas présente au "
+"moment où une connexion est utilisée, alors les opérations seront effectuées "
+"directement sur la base de données."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr "JDBC ne prend pas en charge des sous-transactions."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:226
+#, no-c-format
+msgid ""
+"Transaction timeouts can be used to automatically terminate transactions "
+"should the connection not be terminated within an appropriate period."
+msgstr ""
+"Les délais d'attente de transactions peuvent être utilisés pour terminer "
+"automatiquement des transactions, si la connexion n'est pas terminée dans un "
+"lapse de temps approprié."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:229
+#, no-c-format
+msgid ""
+"JBossJTA connections can be used within multiple different transactions "
+"simultaneously, for instance, different threads, with different notions of "
+"the current transaction, may use the same JDBC connection. JBossJTA does "
+"connection pooling for each transaction within the JDBC connection. So, "
+"although multiple threads may use the same instance of the JDBC connection, "
+"internally this may be using a different connection instance per "
+"transaction. With the exception of close, all operations performed on the "
+"connection at the application level will only be performed on this "
+"transaction-specific connection."
+msgstr ""
+"Les connexions JBossJTA peuvent être utilisées au sein de multiples "
+"transactions séparées en simultané, comme par exemple, des threads "
+"différents, des notions différentes de transaction en cours, tout en "
+"utilisant la même connexion JDBC. JBossJTA procède au regroupement des "
+"connexions pour toute transaction au sein de la connexion JDBC. Donc, même "
+"si des threads multiples utilisent la même instance que la connexion JDBC, "
+"au niveau interne, cela pourrait correspondre à une instance de connexion "
+"différente par transaction. Avec 'fermeture' pour exception, toutes les "
+"opérations effectuées sur la connexion au niveau de l'application, ne "
+"pourront être effectuées que sur cette connexion spécifique-transaction."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:232
+#, no-c-format
+msgid ""
+"JBossJTA will automatically register the JDBC driver connection with the "
+"transaction via an appropriate resource . When the transaction terminates, "
+"this resource will be responsible for either committing or rolling back any "
+"changes made to the underlying database via appropriate calls on the JDBC "
+"driver."
+msgstr ""
+"JBossJTA va automatiquement enregistrer la connexion du pilote JDBC dans la "
+"transaction par l'intermédiaire de la ressource qui convient. Quand la "
+"transaction se termine, cette ressource sera responsable de la validation ou "
+"du rejet de tout changement effectué dans la base de données sous-jacente "
+"grâce aux appels nécessaires sur le pilote JDBC."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:235
+#, no-c-format
+msgid ""
+"Once created, the driver and any connection can be used in the same way as "
+"any other JDBC driver or connection."
+msgstr ""
+"Une fois créée, le pilote et n'importe quelle connexion peut être utilisée "
+"de la même façon que n'importe quel pilote ou connexion JDBC."
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:238
+#, no-c-format
+msgid ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+msgstr ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:240
+#, no-c-format
+msgid "Connection pooling"
+msgstr "Regroupement de connexions"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:241
+#, no-c-format
+msgid ""
+"For each user name and password, JBossJTA will maintain a single instance of "
+"each connection for as long as that connection is in use. Subsequent "
+"requests for the same connection will get a reference to the originally "
+"created connection, rather than a new instance. Attempts to close the "
+"connection are allowed, but the connection will only actually be closed when "
+"all users (including transactions) have either finished with the connection, "
+"or issued close calls."
+msgstr ""
+"Pour chaque nom d'utilisateur ou mot de passe, JBossJTA conservera une seule "
+"instance pour chaque connexion pour autant de temps que la connexion est "
+"utilisée. Les demandes suivantes pour cette même connexion auront une "
+"référence reliée à la connexion créée d'origine, plutôt qu'une nouvelle "
+"instance. Les tentatives de fermeture des connexions sont permises, mais la "
+"connexion ne pourra être fermée que quand tous les utilisateurs (y compris "
+"les transactions) auront soit terminé la connexion, soit émis des appels "
+"fermés."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:246
+#, no-c-format
+msgid "Reusing connections"
+msgstr "Réutilisation des connexions"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:247
+#, no-c-format
+msgid ""
+"Some JDBC drivers allow the reuse of a connection for multiple different "
+"transactions once a given transaction has completed. Unfortunately this is "
+"not a common feature, and other drivers require a new connection to be "
+"obtained for each new transaction. By default, the JBossJTA transactional "
+"driver will always obtain a new connection for each new transaction. "
+"However, if an existing connection is available and is currently unused, it "
+"is possible to make JBossJTA reuse this connection. In order to do this, the "
+"reuseconnection=true option must be specified on the JDBC URL. For example:"
+msgstr ""
+"Certains pilotes JDBC permettent la réutilisation d'une connexion pour des "
+"transactions multiples diverses, une fois que la transaction est terminée. "
+"Malheureusement, ce n'est pas une fonctionnalité courante, et d'autres "
+"pilotes ont besoin d'une nouvelle connexion pour chaque transaction "
+"nouvelle. Par défaut, le pilote transactionnel JBossJTA obtiendra toujours "
+"une nouvelle connexion pour chaque nouvelle transaction. Cependant, si une "
+"connexion existante est disponible, il est possible d'obliger JBossJTA à "
+"réutiliser cette connexion. Dans ce but, l'option reuseconnection=true devra "
+"être spécifiée sur l'URL JDBC. Par exemple :"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+"jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:253
+#, no-c-format
+msgid "Terminating the transaction"
+msgstr "Terminer la transaction"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:254
+#, no-c-format
+msgid ""
+"Whenever a transaction terminates (either explicitly by the application "
+"programmer, or implicitly when any associated transaction timeout expires) "
+"that has a JDBC connection registered with it, JBossJTA will drive the "
+"database (via the JDBC driver) to either commit or roll back any changes "
+"made to it. This happens transparently to the application."
+msgstr ""
+"Quand une transaction se termine (soit explicitement par le programmateur de "
+"l'application, ou implicitement quand tout délai de transaction associé "
+"expire) associée à une connexion JDBC, JBossJTA incitera la base de données "
+"(via pilote JDBC) à valider ou bien à rejeter tout changement. Ceci "
+"s'applique à la transaction de façon transparente."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr "AutoCommit"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:260
+#, no-c-format
+msgid ""
+"If <code>AutoCommit</code> of the <code>java.sql.Connection</code> is set to "
+"true for JDBC 1.0 then the execution of every SQL statement is a separate "
+"top-level transaction, and grouping multiple statements to be managed within "
+"a single OTS transaction is not possible. Therefore, JBossJTA will disable "
+"<code>AutoCommit</code> on JDBC 1.0 connections before they can be used. If "
+"auto commit is subsequently set to true by the application, JBossJTA will "
+"raise the <code>java.sql.SQLException</code>."
+msgstr ""
+"Si <code>AutoCommit</code> du code <code>java.sql.Connection</code> est "
+"configuré à true (vrai) pour JDBC 1.0, alors toute exécution de chaque "
+"énoncé SQL est une transaction séparée de haut niveau, et il n'est pas "
+"possible de regrouper des énoncés multiples à gérer au sein d'une seule "
+"transaction OTS. Ainsi, JBossJTA désactivera <code>AutoCommit</code> sur les "
+"connexions JDBC 1. avant qu'elles puissent être utilisées. Si auto commit "
+"est ensuite configuré à 'True' (vrai) par l'application, alors JBossJTA "
+"émettra <code>java.sql.SQLException</code>."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:265
+#, no-c-format
+msgid "Setting isolation levels"
+msgstr "Configurer les niveaux d'isolation"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:266
+#, no-c-format
+msgid ""
+"When using the JBossJTA JDBC driver, it may be necessary to set the "
+"underlying transaction isolation level on the XA connection. By default, "
+"this is set to <code>TRANSACTION_SERIALIZABLE</code>, but you may want to "
+"set this to something more appropriate for your application. In order to do "
+"this, set the <property>com.arjuna.ats.jdbc.isolationLevel</property> "
+"property to the appropriate isolation level in string form, for example, "
+"<code>TRANSACTION_READ_COMMITTED</code>, or "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+msgstr ""
+"Quand vous utilisez le pilote JBossJTA JDBC, il serait utile de déterminer "
+"le niveau d'isolation de la transaction sous-jacente sur la connexion XA. La "
+"configuration par défaut est <code>TRANSACTION_SERIALIZABLE</code>, mais "
+"vous souhaitez peut être configurer cela à quelque chose de plus "
+"personnalisé en fonction de votre application. Dans ce but, configurer la "
+"propriété <property>com.arjuna.ats.jdbc.isolationLevel</property> au niveau "
+"d'isolation qui convient sous forme de chaîne, comme par exemple "
+"<code>TRANSACTION_READ_COMMITTED</code>, ou bien "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:271
+#, no-c-format
+msgid ""
+"At present this property applies to all XA connections created in the JVM."
+msgstr ""
+"Actuellement cette propriété s'applique à toutes les connexions XA créées "
+"dans JVM."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Preface.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Preface.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,23 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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 "Préface"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Revision_History.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Revision_History.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,29 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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 "Historique de révision"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/The_Resource_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/The_Resource_Manager.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/The_Resource_Manager.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,960 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#: The_Resource_Manager.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "Test"
+
+#. Tag: para
+#: The_Resource_Manager.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "Il s'agit d'un paragraphe test"
+
+#. Tag: title
+#: The_Resource_Manager.xml:11
+#, no-c-format
+msgid "The XAResource Interface"
+msgstr "L'interface XAResource"
+
+#. Tag: para
+#: The_Resource_Manager.xml:12
+#, no-c-format
+msgid ""
+"Whereas some transaction specifications and systems define a generic "
+"resource which can be used to register arbitrary resources with a "
+"transaction, the JTA is much more XA specific. The <interfacename>javax."
+"transaction.xa.XAResource</interfacename> interface is a Java mapping of the "
+"<interfacename>XA</interfacename> interface. The <interfacename>XAResource</"
+"interfacename> interface defines the contract between a Resource Manager and "
+"a Transaction Manager in a distributed transaction processing environment. A "
+"resource adapter for a resource manager implements the "
+"<interfacename>XAResource</interfacename> interface to support association "
+"of a top-level transaction to a resource such as a relational database."
+msgstr ""
+"Alors que certains systèmes et certaines spécifications définissent une "
+"ressource générique qui puisse être utilisée pour enregistrer des ressources "
+"arbitraires dans une transaction, le JTA est plus spécifique au XA. "
+"L'interface <interfacename>javax.transaction.xa.XAResource</interfacename> "
+"est un mappage Java de l'interface <interfacename>XA</interfacename>. "
+"L'interface <interfacename>XAResource</interfacename> définit le contrat "
+"entre un gestionnaire de ressources et un gestionnaire de transactions dans "
+"un environnement de traitement de transactions distribuées. Un adaptateur de "
+"ressources implémente l'interface <interfacename>XAResource</interfacename> "
+"pour supporter l'association d'une transaction à haut-niveau à une ressource "
+"du genre base de données relationnelle."
+
+#. Tag: para
+#: The_Resource_Manager.xml:15
+#, no-c-format
+msgid ""
+"The <interfacename>XAResource</interfacename> interface can be supported by "
+"any transactional resource adapter that is intended to be used in an "
+"environment where transactions are controlled by an external transaction "
+"manager, for example, a database management system. An application may "
+"access data through multiple database connections. Each database connection "
+"is associated with an <code>XAResource</code> object that serves as a proxy "
+"object to the underlying resource manager instance. The transaction manager "
+"obtains an <code>XAResource</code> for each resource manager participating "
+"in a top-level transaction. It uses the start method to associate the "
+"transaction with the resource, and it uses the end method to disassociate "
+"the transaction from the resource."
+msgstr ""
+"L'interface <interfacename>XAResource</interfacename> peut être supportée "
+"par n'importe quel adaptateur de ressources transactionnelles destiné à être "
+"utilisé dans un environnement pour lequel les transactions sont contrôlées "
+"par un gestionnaire de transactions externe, par exemple, un système de "
+"gestion de bases de données. Une application est en mesure d'accéder aux "
+"données par des connexions à la base de donnée multiples. Chaque connexion à "
+"la base de donnée est associée à un objet <code>XAResource</code> qui sert "
+"d'objet proxy à l'instance du gestionnaire de ressources sous-jacent. Le "
+"gestionnaire de transactions obtient un <code>XAResource</code> pour chaque "
+"gestionnaire de ressource participant à une transaction de haut-niveau. Il "
+"utilise la méthode start pour associer la transaction à la ressource, et il "
+"utilise la méthode end pour désassocier la transaction de la ressource."
+
+#. Tag: para
+#: The_Resource_Manager.xml:18
+#, no-c-format
+msgid ""
+"The resource manager is responsible for associating the transaction with all "
+"work performed on its data between the start and end invocations. At "
+"transaction commit time, these transactional resource managers are informed "
+"by the transaction manager to prepare, commit, or rollback the transaction "
+"according to the two-phase commit protocol."
+msgstr ""
+"Le gestionnaire de ressource est chargé d'associer la transaction à tous les "
+"travaux effectués à partir de ses données entre les invocations de départ et "
+"de fin. Au moment de comiter/valider la transaction, ces gestionnaires de "
+"ressources transactionnelles sont informés par le gestionnaire de "
+"transaction de préparer, de valider, ou de renvoyer la transaction en "
+"suivant un protocole de validation en deux temps."
+
+#. Tag: para
+#: The_Resource_Manager.xml:21
+#, no-c-format
+msgid ""
+"In order to be better integrated with Java, the <interfacename>XAResource</"
+"interfacename> differs from the standard <interfacename>XA</interfacename> "
+"interface in the following ways:"
+msgstr ""
+"Dans un souci d'intégration avec Java, <interfacename>XAResource</"
+"interfacename> diffère de l'interface standard <interfacename>XA</"
+"interfacename> des façons suivantes :"
+
+#. Tag: para
+#: The_Resource_Manager.xml:26
+#, no-c-format
+msgid ""
+"The resource manager initialization is done implicitly by the resource "
+"adapter when the resource (connection) is acquired. There is no "
+"<code>xa_open</code> equivalent."
+msgstr ""
+"L'initialisation du gestionnaire de ressources est effectuée de façon "
+"implicite par l'adaptateur de ressources au moment ou la ressource "
+"(connexion) est obtenue. Il n'existe pas d'équivalent <code>xa_open</code>."
+
+#. Tag: para
+#: The_Resource_Manager.xml:31
+#, no-c-format
+msgid ""
+"<code>Rmid</code> is not passed as an argument. Each <code>Rmid</code> is "
+"represented by a separate <code>XAResource</code> object."
+msgstr ""
+"<code>Rmid</code> n'est pas passé comme argument. Chaque <code>Rmid</code> "
+"est représenté par un objet <code>XAResource</code> séparé."
+
+#. Tag: para
+#: The_Resource_Manager.xml:36
+#, no-c-format
+msgid ""
+"Asynchronous operations are not supported because Java supports multi-"
+"threaded processing and most databases do not support asynchronous "
+"operations."
+msgstr ""
+"Les opérations asynchrones ne sont pas prises en charge car Java supporte "
+"des traitements multi-thread et la plupart des bases de données ne "
+"supportent pas les opérations asynchrones."
+
+#. Tag: para
+#: The_Resource_Manager.xml:41
+#, no-c-format
+msgid ""
+"Error return values that are caused by the transaction manager’s improper "
+"handling of the <code>XAResource</code> object are mapped to Java exceptions "
+"via the <classname>XAException</classname> class."
+msgstr ""
+"'Erreur' retourne des valeurs qui apparaissent suite à des mauvaises "
+"manipulations de l'objet <code>XAResource</code> par le gestionnaire de "
+"transactions, sont mappées dans les exceptions Java par la classe "
+"<classname>XAException</classname>."
+
+#. Tag: para
+#: The_Resource_Manager.xml:46
+#, no-c-format
+msgid ""
+"The DTP concept of <emphasis>Thread of Control</emphasis> maps to all Java "
+"threads that are given access to the <code>XAResource</code> and "
+"<code>Connection</code> objects. For example, it is legal for two different "
+"threads to perform the start and end operations on the same "
+"<code>XAResource</code> object."
+msgstr ""
+"Le concepte <emphasis>Thread of Control</emphasis> mappe vers tous les "
+"threads Java qui ont accès aux objets <code>XAResource</code> et "
+"<code>Connection</code>. Ainsi, il est tout à fait légal pour deux threads "
+"différents d'effectuer les opérations de départ et fin sur le même objet "
+"<code>XAResource</code>."
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr "Extension du contrôle XAResource "
+
+#. Tag: para
+#: The_Resource_Manager.xml:53
+#, no-c-format
+msgid ""
+"By default, whenever an <code>XAResource</code> object is registered with a "
+"JTA compliant transaction service, you have no control over the order in "
+"which it will be invoked during the two-phase commit protocol, with respect "
+"to other <code>XAResource</code> objects. In JBossTS, however, there is "
+"support for controlling the order via the two interfaces <interfacename>com."
+"arjuna.ats.jta.resources.StartXAResource</interfacename> and "
+"<interfacename>com.arjuna.ats.jta.resources.EndXAResource</interfacename>. "
+"By inheriting your <code>XAResource</code> instance from either of these "
+"interfaces, you control whether an instance of your class will be invoked "
+"first or last, respectively."
+msgstr ""
+"Par défaut, à chaque fois qu'un objet <code>XAResource</code> est enregistré "
+"dans un service de transaction compatible JTA, vous ne pouvez pas contrôler "
+"dans quel ordre il sera invoqué pendant le protocole de validation en deux-"
+"phases. Dans JBossTS, cependant, il existe un support de contrôle de cet "
+"ordre par l'intermédiaire des deux interfaces <interfacename>com.arjuna.ats."
+"jta.resources.StartXAResource</interfacename> et <interfacename>com.arjuna."
+"ats.jta.resources.EndXAResource</interfacename>. En héritant votre instance "
+"<code>XAResource</code> à partir de n'importe quelle de ces interfaces, vous "
+"contrôlez si une instance de votre classe sera ou non invoquée au début ou à "
+"la fin, respectivement."
+
+#. Tag: para
+#: The_Resource_Manager.xml:58
+#, no-c-format
+msgid ""
+"Only one instance of each interface type may be registered with a specific "
+"transaction."
+msgstr ""
+"Une seule instance pour chaque type d'interface peut être enregistrée pour "
+"chaque transaction particulière."
+
+#. Tag: para
+#: The_Resource_Manager.xml:62
+#, no-c-format
+msgid ""
+"In the TxCore manual we discussed the Last Resource Commit optimization "
+"(LRCO), whereby a single resource that is only one-phase aware (does not "
+"support prepare), can be enlisted with a transaction that is manipulating "
+"two-phase aware participants. This optimization is also supported within the "
+"JTA aspects of JBossTS."
+msgstr ""
+"Dans le manuel TxCore, nous avons discuté l'optimisation LRCO (Last Resource "
+"Commit Optimization), pour laquelle une simple ressource en une seule étape "
+"(qui ne supporte pas 'prepare')peut être engagée dans une transaction qui "
+"manipule des participants en deux étapes. Cette optimisation est également "
+"prise en charge dans les aspects JTA de JBossTS."
+
+#. Tag: para
+#: The_Resource_Manager.xml:65
+#, no-c-format
+msgid ""
+"In order to use the LRCO, your <interfacename>XAResource</interfacename> "
+"implementation must extend the <interfacename>com.arjuna.ats.jta.resources."
+"LastResourceCommitOptimisation</interfacename> marker interface (it provides "
+"no methods). When enlisting the resource via Transaction.enlistResource, "
+"JBossTS will ensure that only a single instance of this type of participant "
+"is used within each transaction. Your resource will be driven last in the "
+"commit protocol: no invocation of prepare will occur."
+msgstr ""
+"Pour utiliser le LRCO, votre implémentaiton <interfacename>XAResource</"
+"interfacename> devra venir en extension de l'interface de marquage "
+"<interfacename>com.arjuna.ats.jta.resources.LastResourceCommitOptimisation</"
+"interfacename> (aucune méthode n'est indiquée). Lorsque vous engagez la "
+"ressource par Transaction.enlistResource, JBossTS vérifiera qu'une seule "
+"instance de ce type de participant soit utilisé dans chaque transaction. "
+"Votre ressource sera la dernière à être prise en considération dans votre "
+"protocole de validation : il n'y aura pas d'invocation de 'prepare'."
+
+#. Tag: para
+#: The_Resource_Manager.xml:69
+#, no-c-format
+msgid ""
+"By default an attempt to enlist more than one instance of a "
+"<classname>LastResourceCommitOptimisation</classname> class will fail and "
+"false will be returned from <methodname>Transaction.enlistResource</"
+"methodname>. This behaviour can be overridden by setting the <property>com."
+"arjuna.ats.jta.allowMultipleLastResources</property> to true. However, "
+"before doing so you should read the Section on enlisting multiple one-phase "
+"aware resources."
+msgstr ""
+"Par défaut, toute tentative d'engager plus d'une instance de la classe "
+"<classname>LastResourceCommitOptimisation</classname> échouera et 'false' "
+"retournera de <methodname>Transaction.enlistResource</methodname>. Ce "
+"comportement pourra être modifié si vous configurez <property>com.arjuna.ats."
+"jta.allowMultipleLastResources</property> à 'vrai'. Cependant, avant de "
+"procéder, vous devriez lire la Section 'Enlisting multiple one-phase aware "
+"resource' sur la façon d'engager des ressources multiples en une-étape."
+
+#. Tag: para
+#: The_Resource_Manager.xml:73
+#, no-c-format
+msgid ""
+"In order to utilize the LRCO in a distributed environment, it is necessary "
+"to disable interposition support. It is still possible to use implicit "
+"context propagation."
+msgstr ""
+"Pour utiliser le LRCO dans un environnement distribué, il faut désactiver le "
+"support interposition. Il est possible d'utiliser la propagation du contexte "
+"implicite."
+
+#. Tag: title
+#: The_Resource_Manager.xml:77
+#, no-c-format
+msgid "Enlisting multiple one-phase aware resources"
+msgstr "Engager des ressources multiples en une-étape"
+
+#. Tag: para
+#: The_Resource_Manager.xml:78
+#, no-c-format
+msgid ""
+"As discussed in the Transaction Core documentation, in order to guarantee "
+"consistency (atomicity) of outcome between multiple participants (resources) "
+"within the same transaction, the two-phase commit protocol is used with a "
+"durable transaction log. In the case of possessing a single one-phase aware "
+"resource, it is still possible to achieve an atomic (all of nothing) outcome "
+"across resources by utilizing the Last Resource Commit Optimization, as "
+"explained earlier."
+msgstr ""
+"Comme nous l'avons expliqué dans la documentation Transaction Core, pour "
+"pouvoir garantir l'homogénéité (atomicité) des résultats entre les divers "
+"participants (ressources) au sein d'une même transaction, le protocole de "
+"validation en deux-étapes est utilisé en conjonction avec un système de "
+"journalisation de transaction durable. Si vous ne possédez qu'une seule "
+"ressource en une-étape, il est toujours possible de réaliser un résultat "
+"atomique (tout ou rien) à travers les ressources en utilisant LRCO, comme "
+"expliqué plus haut."
+
+#. Tag: para
+#: The_Resource_Manager.xml:82
+#, no-c-format
+msgid ""
+"However, there may be situations where multiple one-phase aware resources "
+"are enlisted within the same transaction. For example, a legacy database "
+"running within the same transaction as a legacy JMS implementation. In these "
+"situations it is not possible to achieve atomicity of transaction outcome "
+"across multiple resources because none of them enter the prepare (waiting "
+"for final outcome) state: they commit or rollback immediately when "
+"instructed by the transaction coordinator, without knowledge of other "
+"resource states and without any way of undoing should subsequent resources "
+"make a different choice. This can result in data corruption or heuristic "
+"outcomes."
+msgstr ""
+"Cependant, vous pourriez rencontrer des situations pour lesquelles des "
+"ressources multiples en une-étape soient engagées au sein d'une même "
+"transaction, comme par exemple, une base de donnée héritée exécutée dans la "
+"même transaction que l'implémentation JMS héritée. Dans de tels cas, il "
+"n'est pas possible de réussir l'atomicité du résultat de la transaction à "
+"travers des ressources multiples car aucune d'entre elles ne peut atteindre "
+"l'état 'prepare' (en attendant le résultat final) : elles sont validées ou "
+"bien rejetées immédiatement sur les ordres du coordinateur de transaction, "
+"sans connaître les autres états de ressource et sans possibilité d'annuler "
+"si des ressources suivantes optent pour un choix différent. Cela aboutit à "
+"des altérations de données ou à des résultats heuristiques."
+
+#. Tag: para
+#: The_Resource_Manager.xml:85
+#, no-c-format
+msgid "In these situations we recommend one of the following approaches:"
+msgstr ""
+"Dans de telles situations, il est conseillé d'adopter une des approches "
+"suivantes :"
+
+#. Tag: para
+#: The_Resource_Manager.xml:90
+#, no-c-format
+msgid ""
+"Wrap the resources in compensating transactions. See the Web Services "
+"transactions guides for further details."
+msgstr ""
+"Renvoyer les ressources dans des transactions de substitution. Voir les "
+"guides de transaction des services Web pour davantage d'information."
+
+#. Tag: para
+#: The_Resource_Manager.xml:95
+#, no-c-format
+msgid "Migrate the legacy implementations to two-phase aware equivalents."
+msgstr "Migrer les implémentations héritées en équivalents à deux-étapes."
+
+#. Tag: para
+#: The_Resource_Manager.xml:100
+#, no-c-format
+msgid ""
+"In the cases where neither of these options are viable, JBossTS does support "
+"the enlistment of multiple one-phase aware resources within the same "
+"transaction. In order to do this, see the section on the Last Resource "
+"Commit Optimization."
+msgstr ""
+"Dans les cas où aucune de ces options n'est viable, JBossTS ne prend pas en "
+"charge l'engagement de ressources multiples en une-étape pour la même "
+"transaction. Pour cela, consultez la section sur LRCO."
+
+#. Tag: para
+#: The_Resource_Manager.xml:104
+#, no-c-format
+msgid ""
+"Even when this support is enabled, JBossTS will issue warnings when it "
+"detects that the option has been enabled (\"You have chosen to enable "
+"multiple last resources in the transaction manager. This is transactionally "
+"unsafe and should not be relied upon.”) and when multiple one-phase "
+"resources are enlisted within the transaction (“This is transactionally "
+"unsafe and should not be relied on.”)."
+msgstr ""
+"Même quand ce support est activé, JBossTS émettra des avertissements quand "
+"il détecte qu'une option a été activée (Vous avez choisi d'activer les "
+"dernière ressources multiples dans le gestionnaire de transactions. Ce n'est "
+"pas sécurisé au niveau des transactions et on ne peut s'y fier.) et quand "
+"des ressources multiples en une-étape sont engagées dans une transaction (ce "
+"n'est pas sécurisé au niveau des transactions et on ne peut s'y fier)."
+
+#. Tag: title
+#: The_Resource_Manager.xml:111
+#, no-c-format
+msgid "Opening a Resource Manager"
+msgstr "Ouvrir un gestionnaire de ressources"
+
+#. Tag: para
+#: The_Resource_Manager.xml:112
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface requires that the "
+"transaction manager initialize a resource manager (xa_open) prior to any "
+"other xa_ calls. JTA requires initialization of a resource manager to be "
+"embedded within the resource adapter that represents the resource manager. "
+"The transaction manager does not need to know how to initialize a resource "
+"manager; it is only responsible for informing the resource manager about "
+"when to start and end work associated with a transaction and when to "
+"complete the transaction. The resource adapter is responsible for opening "
+"(initializing) the resource manager when the connection to the resource "
+"manager is established."
+msgstr ""
+"L'interface X/Open <interfacename>XA</interfacename> requiert que le "
+"gestionnaire de transactions initialise un gestionnaire de ressources "
+"(xa_open) avant tout appel xa_calls. JTA requiert que l'initialisation d'un "
+"gestionnaire de ressources soit intégrée dans l'adaptateur de ressources qui "
+"représente le gestionnaire de ressources. Le gestionnaire de transactions ne "
+"sait pas comment initialiser le gestionnaire de ressources; il est "
+"uniquement responsable d'informer le gestionnaire de ressources quand "
+"commencer ou terminer des tâches associées à la transaction et quand "
+"terminer la transaction. L'adaptateur de ressources est chargé d'ouvrir "
+"(d'initialiser) le gestionnaire de ressources quand la connexion au "
+"gestionnaire de ressources est établie."
+
+#. Tag: title
+#: The_Resource_Manager.xml:118
+#, no-c-format
+msgid "Closing a Resource Manager"
+msgstr "Fermer le gestionnaire de ressources"
+
+#. Tag: para
+#: The_Resource_Manager.xml:119
+#, no-c-format
+msgid ""
+"A resource manager is closed by the resource adapter as a result of "
+"destroying the transactional resource. A transaction resource at the "
+"resource adapter level is comprised of two separate objects:"
+msgstr ""
+"Un gestionnaire de ressources est fermé par un adaptateur de ressources "
+"suite à la destruction de la ressource transactionnelle. Une ressource de "
+"transaction au niveau adaptateur de ressources est constitué de deux objets "
+"distincts :"
+
+#. Tag: para
+#: The_Resource_Manager.xml:124
+#, no-c-format
+msgid ""
+"An <code>XAResource</code> object that allows the transaction manager to "
+"start and end the transaction association with the resource in use and to "
+"coordinate transaction completion process."
+msgstr ""
+"Un objet <code>XAResource</code> qui permet au gestionnaire de transaction "
+"de commencer ou de terminer l'association de transaction avec la ressource "
+"utilisée et de coordonner de processus de complétion de la transaction."
+
+#. Tag: para
+#: The_Resource_Manager.xml:129
+#, no-c-format
+msgid ""
+"A connection object that allows the application to perform operations on the "
+"underlying resource (for example, JDBC operations on an RDBMS)."
+msgstr ""
+"Un objet de connexion qui permet à l'application d'effectuer des opérations "
+"sur les ressources sous-jacentes (par exemple, les opérations JDBC sur un "
+"RDBMS)."
+
+#. Tag: para
+#: The_Resource_Manager.xml:134
+#, no-c-format
+msgid ""
+"Once opened, the resource manager is kept open until the resource is "
+"released (closed) explicitly. When the application invokes the connection’s "
+"close method, the resource adapter invalidates the connection object "
+"reference that was held by the application and notifies the application "
+"server about the close. The transaction manager should invoke the "
+"<methodname>XAResource.end</methodname> method to disassociate the "
+"transaction from that connection."
+msgstr ""
+"Une fois ouvert, le gestionnaire de ressources le demeure jusqu'à ce que la "
+"ressource soit libérée (fermée) explicitement. Quand l'application invoque "
+"la méthode close de la connexion, l'adaptateur de la ressource invalide la "
+"référence de l'objet de connexion qui était détenu par l'application et "
+"informe le serveur de cette application de cette fermeture. Le gestionnaire "
+"de transaction devrait évoquer la méthode <methodname>XAResource.end</"
+"methodname> pour dissocier la transaction de cette connexion."
+
+#. Tag: para
+#: The_Resource_Manager.xml:137
+#, no-c-format
+msgid ""
+"The close notification allows the application server to perform any "
+"necessary cleanup work and to mark the physical XA connection as free for "
+"reuse, if connection pooling is in place."
+msgstr ""
+"La notification 'close' permet au serveur de l'application de procéder au "
+"travail de nettoyage et d'indiquer 'free' sur la connexion physique XA pour "
+"réutilisation, si le regroupement des connexions est en place."
+
+#. Tag: title
+#: The_Resource_Manager.xml:143
+#, no-c-format
+msgid "Threads of control"
+msgstr "Threads de contrôle"
+
+#. Tag: para
+#: The_Resource_Manager.xml:144
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface specifies that the "
+"transaction association related xa calls must be invoked from the same "
+"thread context. This thread-of-control requirement is not applicable to the "
+"object-oriented component-based application run-time environment, in which "
+"application threads are dispatched dynamically at method invocation time. "
+"Different threads may be using the same connection resource to access the "
+"resource manager if the connection spans multiple method invocation. "
+"Depending on the implementation of the application server, different threads "
+"may be involved with the same <code>XAResource</code> object. The resource "
+"context and the transaction context may be operated independent of thread "
+"context. This means that it is possible for different threads to be invoking "
+"the start and end methods."
+msgstr ""
+"L'interface X/Open <interfacename>XA</interfacename> spécifie que les appels "
+"xa liés à l'association de transaction, doivent être invoqués à partir du "
+"même contexte thread. Ce prérequis thread-de-contrôle n'est pas applicable "
+"dans l'environnement d'exécution de l'application basée-composant et "
+"orientée-objet, dans lequel les threads de l'application sont distribués "
+"dynamiquement au moment de l'invocation de la méthode. Suivant "
+"l'implémentation du serveur d'application, divers threads pourraient être "
+"impliqués dans le même objet <code>XAResource</code>. Le contexte de "
+"ressource et le contexte de transaction peuvent être opérés indépendamment "
+"du contexte de threads. Cela signifie qu'il est possible pour différents "
+"threads d'invoquer les méthodes 'start' et 'end'."
+
+#. Tag: para
+#: The_Resource_Manager.xml:147
+#, no-c-format
+msgid ""
+"If the application server allows multiple threads to use a single "
+"<code>XAResource</code> object and the associated connection to the resource "
+"manager, it is the responsibility of the application server to ensure that "
+"there is only one transaction context associated with the resource at any "
+"point of time. Thus the <interfacename>XAResource</interfacename> interface "
+"requires that the resource managers be able to support the two-phase commit "
+"protocol from any thread context."
+msgstr ""
+"Si le serveur d'application permet à plusieurs threads d'utiliser un seul "
+"objet <code>XAResource</code> et la connexion associée au gestionnaire de "
+"ressources, c'est la responsabilité du serveur d'application de veiller à ce "
+"qu'il n'y ait qu'un contexte de transaction qui soit associé à la ressource "
+"à tout moment. Ainsi l'interface <interfacename>XAResource</interfacename> "
+"exige que les gestionnaires de ressources soient en mesure de prendre en "
+"charge le protocole de validation en deux-phases à partir de n'importe quel "
+"contexte de thread."
+
+#. Tag: title
+#: The_Resource_Manager.xml:153
+#, no-c-format
+msgid "Transaction association"
+msgstr "Association de transactions"
+
+#. Tag: para
+#: The_Resource_Manager.xml:154
+#, no-c-format
+msgid ""
+"Transactions are associated with a transactional resource via the start "
+"method, and disassociated from the resource via the <methodname>end</"
+"methodname> method. The resource adapter is responsible for internally "
+"maintaining an association between the resource connection object and the "
+"<code>XAResource</code> object. At any given time, a connection is "
+"associated with a single transaction, or it is not associated with any "
+"transaction at all. Because JTA does not support nested transactions it is "
+"an error for the start method to be invoked on a connection that is "
+"currently associated with a different transaction."
+msgstr ""
+"Les transactions sont associées à une ressource transactionnelle par la "
+"méthode 'start', et elles sont dissociées de la ressource par la méthode "
+"<interfacename>XAResource</interfacename>. L'adaptateur de ressources est "
+"chargé de la maintenance interne d'une association entre l'objet de "
+"connexion de la ressource et l'objet <code>XAResource</code>. A tout moment, "
+"chaque connexion est associée à une transaction unique, ou bien elle n'est "
+"associée à aucune transaction. Comme JTA ne prend pas en charge les "
+"transactions intégrées, c'est une erreur d'invoquer la méthode 'start' sur "
+"une connexion qui n'est pas actuellement associée à une transaction "
+"différente."
+
+#. Tag: para
+#: The_Resource_Manager.xml:157
+#, no-c-format
+msgid ""
+"Interleaving multiple transaction contexts using the same resource may be "
+"done by the transaction manager as long as start and end are invoked "
+"properly for each transaction context switch. Each time the resource is used "
+"with a different transaction, the method end must be invoked for the "
+"previous transaction that was associated with the resource, and start must "
+"be invoked for the current transaction context."
+msgstr ""
+"L'imbrication de contextes de transaction multiples utilisant la même "
+"ressource peut être réalisée par le gestionnaire de la transaction tant que "
+"'start' et 'end' sont invoqués correctement pour chaque changement de "
+"contexte de transaction. A chaque fois que la ressource est utilisée dans "
+"une transaction différente, la méthode 'end' doit être invoquée pour la "
+"transaction précédente qui était associée à la ressource, et 'start' doit "
+"être invoqué pour le contexte actuel de la transaction."
+
+#. Tag: title
+#: The_Resource_Manager.xml:163
+#, no-c-format
+msgid "Externally controlled connections"
+msgstr "Connexions contrôlées externellement"
+
+#. Tag: para
+#: The_Resource_Manager.xml:164
+#, no-c-format
+msgid ""
+"For transactional application whose transaction states are managed by an "
+"application server, its resources must also be managed by the application "
+"server so that transaction association is performed properly. If an "
+"application is associated with a transaction, it is an error for the "
+"application to perform transactional work through the connection without "
+"having the connection’s resource object already associated with the global "
+"transaction. The application server must ensure that the <code>XAResource</"
+"code> object in use is associated with the transaction. This is done by "
+"invoking the <methodname>Transaction.enlistResource</methodname> method."
+msgstr ""
+"Pour les applications transactionnelles dont les états de transaction sont "
+"gérés par un serveur d'application, leurs ressources doivent être gérées "
+"également par le serveur d'applications de façon à ce que l'association de "
+"transactions soit effectuée correctement. Si une application est associée à "
+"une transaction, c'est une erreur de la part de l'application d'effectuer "
+"des tâches transactionnelles à travers la connexion sans avoir l'objet de "
+"ressource de la connexion déjà associé à la transaction globale. Le serveur "
+"d'applications doit veiller à ce que l'objet <code>XAResource</code> utilisé "
+"soit associé à la transaction. Cela est effectué en invoquant la méthode "
+"<methodname>Transaction.enlistResource</methodname>."
+
+#. Tag: para
+#: The_Resource_Manager.xml:167
+#, no-c-format
+msgid ""
+"If a server side transactional application retains its database connection "
+"across multiple client requests, the application server must ensure that "
+"before dispatching a client request to the application thread, the resource "
+"is enlisted with the application’s current transaction context. This implies "
+"that the application server manages the connection resource usage status "
+"across multiple method invocations."
+msgstr ""
+"Si une application transactionnelle côté serveur conserve sa connexion base "
+"de données pour des demandes multiples de la part des clients, le serveur "
+"d'applications doit veiller à ce qu'avant d'associer une demande d'un client "
+"à un thread d'application, la ressource soit engagée dans le contexte de "
+"transaction courant de l'application. Cela implique que le serveur "
+"d'applications puisse gérer le statut d'utilisation de la ressource de "
+"connexion pour des invocations de méthodes diverses."
+
+#. Tag: title
+#: The_Resource_Manager.xml:173
+#, no-c-format
+msgid "Resource sharing"
+msgstr "Partage des ressources"
+
+#. Tag: para
+#: The_Resource_Manager.xml:174
+#, no-c-format
+msgid ""
+"When the same transactional resource is used to interleave multiple "
+"transactions, it is the responsibility of the application server to ensure "
+"that only one transaction is enlisted with the resource at any given time. "
+"To initiate the transaction commit process, the transaction manager is "
+"allowed to use any of the resource objects connected to the same resource "
+"manager instance. The resource object used for the two-phase commit protocol "
+"does not need to have been involved with the transaction being completed."
+msgstr ""
+"Quand une même ressource transactionnelle est utilisée pour imbriquer des "
+"transactions multiples, c'est le rôle du serveur d'application de veiller à "
+"ce qu'une seule transaction soit engagée en association à la ressource à "
+"tout moment. Pour initier le processus de validation de la transaction, le "
+"gestionnaire de transaction est autorisé à utiliser tout objet de ressource "
+"connecté à la même instance de gestionnaire de ressources. L'objet de "
+"ressource utilisé pour le protocole de validation en deux-phases, n'a pas "
+"besoin d'avoir été impliquée dans la complétion de la transaction."
+
+#. Tag: para
+#: The_Resource_Manager.xml:177
+#, no-c-format
+msgid ""
+"The resource adapter must be able to handle multiple threads invoking the "
+"<interfacename>XAResource</interfacename> methods concurrently for "
+"transaction commit processing. For example, with reference to the code "
+"below, suppose we have a transactional resource <code>r1</code>. Global "
+"transaction <code>xid1</code> was started and ended with <code>r1</code>. "
+"Then a different global transaction <code>xid2</code> is associated with "
+"<code>r1</code>. In the meanwhile, the transaction manager may start the two "
+"phase commit process for <code>xid1</code> using <code>r1</code> or any "
+"other transactional resource connected to the same resource manager. The "
+"resource adapter needs to allow the commit process to be executed while the "
+"resource is currently associated with a different global transaction."
+msgstr ""
+"L'adaptateur de ressource doit être en mesure de gérer des threads multiples "
+"invoquant les méthodes <interfacename>XAResource</interfacename> "
+"concurremment pour le traitement de la validation de la transaction. Ainsi, "
+"si on se réfère au code ci-dessous, qu'on a une transaction de ressource "
+"<code>r1</code>, et que la transaction globale <code>xid1</code> ait "
+"commencé et ait terminé par <code>xid1</code>, alors une nouvelle "
+"transaction globale <code>xid2</code> sera associée à <code>r1</code>. "
+"Pendant ce temps là, le gestionnaire de transactions peut commencer le "
+"processus de validation 'start' en deux-étapes pour <code>xid1</code> en "
+"utilisant <code>r1</code> ou n'importe quelle ressource transactionnelle "
+"connectée au même gestionnaire de ressources. L'adaptateur de ressource doit "
+"permettre au processus de validation d'être exécuté tandis que la ressource "
+"est associée à une transaction globale différente."
+
+#. Tag: screen
+#: The_Resource_Manager.xml:180
+#, no-c-format
+msgid ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+msgstr ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+
+#. Tag: title
+#: The_Resource_Manager.xml:184
+#, no-c-format
+msgid "Local and global transactions"
+msgstr "Transactions globales et locales"
+
+#. Tag: para
+#: The_Resource_Manager.xml:185
+#, no-c-format
+msgid ""
+"The resource adapter must support the usage of both local and global "
+"transactions within the same transactional connection. Local transactions "
+"are transactions that are started and coordinated by the resource manager "
+"internally. The <interfacename>XAResource</interfacename> interface is not "
+"used for local transactions. When using the same connection to perform both "
+"local and global transactions, the following rules apply:"
+msgstr ""
+"L'adaptateur de ressources doit prendre en charge à la fois l'utilisation "
+"des transactions locales et globales au sein de la même connexion "
+"transactionnelle. Les transactions locales sont des transactions qui sont "
+"démarrées et coordonnées par le gestionnaire de ressources en interne. "
+"L'interface <interfacename>XAResource</interfacename> n'est pas utilisée "
+"pour les transactions locales. Lorsque vous utilisez la même connexion pour "
+"effectuer à la fois les transactions locales et les transactions globales, "
+"les règles suivantes s'appliquent :"
+
+#. Tag: para
+#: The_Resource_Manager.xml:190
+#, no-c-format
+msgid ""
+"The local transaction must be committed (or rolled back) before starting a "
+"global transaction in the connection."
+msgstr ""
+"La transaction locale doit être validée (ou rejetée) avant d'initier une "
+"transaction globale dans la connexion."
+
+#. Tag: para
+#: The_Resource_Manager.xml:195
+#, no-c-format
+msgid ""
+"The global transaction must be disassociated from the connection before any "
+"local transaction is started."
+msgstr ""
+"La transaction globale doit être dissociée de la connexion avant que toute "
+"transaction locale ne soit initiée."
+
+#. Tag: title
+#: The_Resource_Manager.xml:203
+#, no-c-format
+msgid "Transaction timeouts"
+msgstr "Délais d'attente de transactions"
+
+#. Tag: para
+#: The_Resource_Manager.xml:204
+#, no-c-format
+msgid ""
+"Timeout values can be associated with transactions in order to control their "
+"lifetime. If a transaction has not terminated (committed or rolled back) "
+"before the timeout value elapses, the transaction system will automatically "
+"roll it back. The <interfacename>XAResource</interfacename> interface "
+"supports a operation, which allows the timeout associated with the current "
+"transaction to be propagated to the resource manager and if supported, will "
+"override any default timeout associated with the resource manager. This can "
+"be useful when long running transactions may have lifetimes that would "
+"exceed the default and in which case, if the timeout were not altered, the "
+"resource manager would rollback before the transaction terminated and "
+"subsequently cause the transaction to roll back as well."
+msgstr ""
+"Les valeurs de temporisation peuvent être associées à des transactions en "
+"vue de contrôler leur durée de vie. Si une transaction n'est pas terminée "
+"(validée ou bien rejetée) avant que le délai ne s'écoule, le système de "
+"transaction va la rejeter automatiquement. L'interface "
+"<interfacename>XAResource</interfacename> supporte une opération, qui permet "
+"au délai associé à la transaction courante d'être propagé vers le "
+"gestionnaire de ressources et qui, si supportée, remplacera toute valeur de "
+"temporisation par défaut, associée au gestionnaire de ressources. Cela peut "
+"être utile dans le cas de transactions longues qui ont des durées de vie qui "
+"pourraient être supérieures à la valeur par défaut, dans lequel cas, si le "
+"délai n'était pas altéré, le gestionnaire de ressources serait rejeté avant "
+"que la transaction ne soit terminée et donc entraînerait le rejet de la "
+"transaction également."
+
+#. Tag: para
+#: The_Resource_Manager.xml:207
+#, no-c-format
+msgid ""
+"If no timeout value is explicitly set for a transaction, or a value of 0 is "
+"specified, then an implementation specific default value may be used. In the "
+"case of JBossTS, how this default value is set depends upon which JTA "
+"implementation you are using."
+msgstr ""
+"Si aucune valeur n'est déterminée explicitement pour la transaction, ou si "
+"elle est égale à 0, alors on utilise une valeur par défaut spécifique à "
+"l'implémentation. Dans le cas de JBossTS, la façon dont cette valeur par "
+"défaut est déterminée dépendra de l'implémentation que vous utlisez."
+
+#. Tag: para
+#: The_Resource_Manager.xml:212
+#, no-c-format
+msgid ""
+"Local JTA: use the <property>com.arjuna.ats.arjuna.coordinator."
+"defaultTimeout</property> property value and give a timeout in seconds. The "
+"default value is 60 seconds."
+msgstr ""
+"JTA local : utilisez la valeur de la propriété <property>com.arjuna.ats."
+"arjuna.coordinator.defaultTimeout</property> et indiquez le délai en "
+"secondes. La valeur par défaut est de 60 secondes."
+
+#. Tag: para
+#: The_Resource_Manager.xml:217
+#, no-c-format
+msgid ""
+"JTS: use the <property>com.arjuna.ats.jts.defaultTimeout</property> property "
+"value and give a timeout in seconds. The default value is 0, for instance, "
+"transactions do not timeout."
+msgstr ""
+"JTS : utilisez la valeur de la propriété <property>com.arjuna.ats.jts."
+"defaultTimeout</property> et indiquez un délai en secondes. Si la valeur par "
+"défaut est de 0, par exemple, les transactions n'ont pas de contrainte de "
+"temps."
+
+#. Tag: para
+#: The_Resource_Manager.xml:222
+#, no-c-format
+msgid ""
+"Unfortunately there are situations where imposing the same timeout as the "
+"transaction on a resource manager may not be appropriate. For example, if "
+"the system administrator wishes to have control over the lifetimes on "
+"resource managers and does not want to (or cannot) allow that control to be "
+"passed to some external entity. At present JBossTS supports an all-or-"
+"nothing approach to whether or not <methodname>setTransactionTimeout</"
+"methodname> is called on <interfacename>XAResource</interfacename> instances."
+msgstr ""
+"Malheureusement, il existe des situations pour lesquelles il n'est pas "
+"approprié d'imposer la même temporisation que celle associée à la "
+"transaction sur un gestionnaire de ressources. Ainsi, si l'administrateur "
+"des systèmes souhaite avoir le contrôle des durées de vie des gestionnaires "
+"de ressources, et ne veuille pas (ou ne puisse pas) que ce contrôle puisse "
+"être passé à une entité externe. Actuellement JBossTS supporte une approche "
+"tout-ou-rien que <methodname>setTransactionTimeout</methodname> soit appelé "
+"ou non sur les instances <interfacename>XAResource</interfacename>."
+
+#. Tag: para
+#: The_Resource_Manager.xml:225
+#, no-c-format
+msgid ""
+"If the <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> "
+"property is set to true (the default) then it will be called on all "
+"instances. Alternatively, the <methodname>setXATransactionTimeoutEnabled</"
+"methodname> method of <classname>com.arjuna.ats.jta.common.Configuration</"
+"classname> can be used."
+msgstr ""
+"Si la propriété <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</"
+"property> est configurée à 'true' (valeur par défaut) alors elle sera "
+"appelée sur toutes les instances. Sinon, la méthode "
+"<methodname>setXATransactionTimeoutEnabled</methodname> de <classname>com."
+"arjuna.ats.jta.common.Configuration</classname> pourra être utilisée."
+
+#. Tag: title
+#: The_Resource_Manager.xml:231
+#, no-c-format
+msgid "Dynamic Registration"
+msgstr "Enregistrements dynamiques"
+
+#. Tag: para
+#: The_Resource_Manager.xml:232
+#, no-c-format
+msgid ""
+"Dynamic registration is not supported in <interfacename>XAResource</"
+"interfacename> because of the following reasons:"
+msgstr ""
+"Les enregistrements dynamiques ne sont pas pris en charge par "
+"<interfacename>XAResource</interfacename> pour les raisons suivantes :"
+
+#. Tag: para
+#: The_Resource_Manager.xml:237
+#, no-c-format
+msgid ""
+"In the Java component-based application server environment, connections to "
+"the resource manager are acquired dynamically when the application "
+"explicitly requests a connection. These resources are enlisted with the "
+"transaction manager on a needed basis."
+msgstr ""
+"Dans l'environnement de serveur d'application basé-composant Java, les "
+"connexions au gestionnaire de ressources sont acquises dynamiquement quand "
+"l'application formule une demande de connexion explicitement. Ces ressources "
+"sont listées dans le gestionnaire de transaction en fonction des besoins."
+
+#. Tag: para
+#: The_Resource_Manager.xml:242
+#, no-c-format
+msgid ""
+"If a resource manager requires a way to dynamically register its work to the "
+"global transaction, the implementation can be done at the resource adapter "
+"level via a private interface between the resource adapter and the "
+"underlying resource manager."
+msgstr ""
+"Si le gestionnaire de ressources requiert une façon d'enregistrer "
+"dynamiquement son travail sur la transaction globale, l'implémentation peut "
+"être faite au niveau de l'adaptateur de ressource via une interface privée "
+"entre l'adaptateur de ressources et le gestionnaire de ressources sous-"
+"jacent."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Transaction_Recovery.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Transaction_Recovery.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Transaction_Recovery.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,485 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr "Recouvrement de transaction"
+
+#. Tag: title
+#: Transaction_Recovery.xml:10
+#, no-c-format
+msgid "Failure recovery"
+msgstr "Recouvrement en cas d'échec"
+
+#. Tag: para
+#: Transaction_Recovery.xml:11
+#, no-c-format
+msgid ""
+"During recovery, the Transaction Manager needs to be able to communicate to "
+"all resource managers that are in use by the applications in the system. For "
+"each resource manager, the Transaction Manager uses the "
+"<methodname>XAResource.recover</methodname> method to retrieve the list of "
+"transactions that are currently in a prepared or heuristically completed "
+"state. Typically, the system administrator configures all transactional "
+"resource factories that are used by the applications deployed on the system. "
+"An example of such a resource factory is the JDBC <code>XADataSource</code> "
+"object, which is a factory for the JDBC <code>XAConnection</code> objects."
+msgstr ""
+"Pendant le recouvrement, le gestionnaire de transaction a besoin de "
+"communiquer à tous les gestionnaires de ressources en cours d'utilisation "
+"dans l'application dans le système. Pour chaque gestionnaire de ressource, "
+"le gestionnaire de transactions utilise la méthode <methodname>XAResource."
+"recover</methodname> pour extraire la liste de transactions qui sont "
+"actuellement dans un état préparé ou heuristique. Normalement, "
+"l'administrateur de systèmes configure toutes les usines de ressources "
+"transactionnelles qui sont utilisées par les applications déployées sur le "
+"système. L'objet JDBC <code>XADataSource</code> est un exemple d'une telle "
+"usine de ressources, et c'est aussi une usine d'objets JDBC "
+"<code>XAConnection</code>."
+
+#. Tag: para
+#: Transaction_Recovery.xml:14
+#, no-c-format
+msgid ""
+"Because <code>XAResource</code> objects are not persistent across system "
+"failures, the Transaction Manager needs to have some way to acquire the "
+"<code>XAResource</code> objects that represent the resource managers which "
+"might have participated in the transactions prior to the system failure. For "
+"example, a Transaction Manager might, through the use of JNDI lookup "
+"mechanism, acquire a connection from each of the transactional resource "
+"factories, and then obtain the corresponding <code>XAResource</code> object "
+"for each connection. The Transaction Manager then invokes the "
+"<methodname>XAResource.recover</methodname> method to ask each resource "
+"manager to return the transactions that are currently in a prepared or "
+"heuristically completed state."
+msgstr ""
+"Comme les objets <code>XAResource</code> ne sont pas persistants en cas "
+"d'échec, le gestionnaire de transactions a besoin de trouver un moyen "
+"d'acquérir les objets <code>XAResource</code> qui représentent les "
+"gestionnaires de ressources qui auraient pu avoir participé dans les "
+"transactions avec l'échec du système. Par exemple, un gestionnaire de "
+"transaction pourrait, en utilisant le mécanisme de recherche JNDI, acquérir "
+"une connexion de chaque usine de ressource transactionnelle, puis obtenir "
+"l'objet <code>XAResource</code> correspondant pour chaque connexion. Le "
+"gestionnaire de transactions invoque alors la méthode <methodname>XAResource."
+"recover</methodname> pour demander à chaque gestionnaire de ressource de "
+"retourner les transactions qui sont actuellement dans un état 'préparé' ou "
+"'heuristique'."
+
+#. Tag: para
+#: Transaction_Recovery.xml:18
+#, no-c-format
+msgid ""
+"When running XA recovery it is 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 ‘*’ will force JBossTS to recover (and possibly rollback) all "
+"transactions irrespective of their node identifier and should be used with "
+"caution."
+msgstr ""
+"Lorsqu'on exécute le recouvrement XA, il est important d'indiquer à JBossTS "
+"quel type de Xid il peut recouvrer. Chaque Xid créé par JBossTS comprend un "
+"identifiant de noeud unique encodé à l'intérieur et JBossTS ne recouvrera "
+"que des transactions et des états qui correspondent à un identifiant de "
+"noeud spécifié. L'identifiant du noeud à utiliser devrait être fourni à "
+"JBossTS grâce à la propriété qui commence par <property>com.arjuna.ats.jta."
+"xaRecoveryNode</property>; probablement avec des valeurs multiples. Une "
+"valeur '*' forcera JBossTS à recouvrir (et peut-être renvoyer) toutes les "
+"transactions quel que soit l'identifiant de leur noeud et devraient être "
+"utilisé avec caution."
+
+#. Tag: para
+#: Transaction_Recovery.xml:22
+#, no-c-format
+msgid ""
+"If using the JBossJTA JDBC 2.0 driver, then JBossJTA will take care of all "
+"<interfacename>XAResource</interfacename> crash recovery automatically. "
+"Otherwise one of the following recovery mechanisms will be used:"
+msgstr ""
+"Si vous utilisez le pilote JBossJTA JDBC 2.0, alors JBossJTA prendra en "
+"charge tous les recouvrements <interfacename>XAResource</interfacename> "
+"automatiquement. Sinon, on pourra utiliser un des mécanismes suivants :"
+
+#. Tag: para
+#: Transaction_Recovery.xml:27
+#, no-c-format
+msgid ""
+"If the <code>XAResource</code> is serializable, then the serialized form "
+"will be saved during transaction commitment, and used during recovery. It is "
+"assumed that the recreated <code>XAResource</code> is valid and can be used "
+"to drive recovery on the associated database."
+msgstr ""
+"Si <code>XAResource</code> est sérialisable, alors la forme sérialisable "
+"sera sauvegardée pendant la phase de validation de la transaction, et "
+"utilisée pendant le recouvrement. On assume que le code <code>XAResource</"
+"code> recréé est valide et peut être utilisé pour actionner le recouvrement "
+"sur la base de données associée."
+
+#. Tag: para
+#: Transaction_Recovery.xml:32
+#, no-c-format
+msgid ""
+"The <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, <interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> and <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> interfaces are used. These "
+"are documented in the JDBC chapters on failure recovery."
+msgstr ""
+"Les interfaces <interfacename>com.arjuna.ats.jta.recovery."
+"XAResourceRecovery</interfacename>, <interfacename>com.arjuna.ats.jta."
+"recovery.XARecoveryResourceManager</interfacename> et <interfacename>com."
+"arjuna.ats.jta.recovery.XARecoveryResource</interfacename> sont utilisées. "
+"Elles sont documentées dans les chapitres JDBC sur le recouvrement en cas "
+"d'échec."
+
+#. Tag: para
+#: Transaction_Recovery.xml:38
+#, no-c-format
+msgid ""
+"In JBossTS 3.3 the interface <interfacename>XAConnectionRecovery</"
+"interfacename> was deprecated in favor of <interfacename>XAResourceRecovery</"
+"interfacename>. Users are encouraged to move to his new interface."
+msgstr ""
+"Dans JBossTS 3.3, l'interface <interfacename>XAConnectionRecovery</"
+"interfacename> était dépréciée en faveur de "
+"<interfacename>XAResourceRecovery</interfacename>. Les utilisateurs sont "
+"encouragés à adopter cette nouvelle interface."
+
+#. Tag: title
+#: Transaction_Recovery.xml:45
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr "Recouvrement des XAConnections"
+
+#. Tag: para
+#: Transaction_Recovery.xml:46
+#, no-c-format
+msgid ""
+"When recovering from failures, JBossJTA requires the ability to reconnect to "
+"databases that were in use prior to the failures in order to resolve any "
+"outstanding transactions. Most connection information will be saved by the "
+"transaction service during its normal execution, and can be used during "
+"recovery to recreate the connection. However, it is possible that not all "
+"such information will have been saved prior to a failure (for example, a "
+"failure occurs before such information can be saved, but after the database "
+"connection is used). In order to recreate those connections it is necessary "
+"to provide implementations of the following JBossJTA interface "
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, one for each database that may be used by an application."
+msgstr ""
+"En cours de recouvrement, JBossJTA requiert la possibilité de reconnecter "
+"vers des bases de données qui étaient utilisées avant les mises en échec "
+"pour résoudre des transactions restantes. Le gros de l'information sur les "
+"connexions sera sauvegardé par le service de transaction pendant l'exécution "
+"normale, et pourra être utilisé pendant le recouvrement pour recréer la "
+"connexion. Cependant, il est possible que toutes les informations n'ont peut-"
+"être pas pu être sauvegardées avant la mise en échec (par exemple, un échec "
+"peut survenir avant que de telles informations aient pu être sauvegradées, "
+"mais après la connexion à la base de données). Pour pouvoir créer ces "
+"connexions, il faut fournir les implémentations de l'interface JBossJTA "
+"suivante <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, une pour chaque base de données qui pourrait être utilisée "
+"par une application."
+
+#. Tag: para
+#: Transaction_Recovery.xml:50
+#, no-c-format
+msgid ""
+"If using the transactional JDBC 2.0 driver provided with JBossJTA, then no "
+"additional work is necessary in order to ensure that recovery occurs."
+msgstr ""
+"Si vous utilisez un pilote transactionnel JDBC 2.0 fourni par JBossJTA, "
+"alors vous n'avez pas besoin d'effectuer de travail supplémentaire pour que "
+"le recouvrement ait lieu."
+
+#. Tag: para
+#: Transaction_Recovery.xml:54
+#, no-c-format
+msgid ""
+"To inform the recovery system about each of the <code>XAResourceRecovery</"
+"code> instances, it is necessary to specify their class names through "
+"property variables. Any property variable found in the properties file, or "
+"registered at runtime, which starts with the name <property>com.arjuna.ats."
+"jta.recovery.XAResourceRecovery</property> will be assumed to represent one "
+"of these instances, and its value should be the class name. For example:"
+msgstr ""
+"Pour informer le système de recouvrement de chaque instance "
+"<code>XAResourceRecovery</code>, il faut vous faut préciser leur nom de "
+"classe par l'intermédiaire des variables de propriété. Toute variable de "
+"propriété présente dans le fichier de propriété, ou enregistrée en cours "
+"d'exécution, commençant par le nom <property>com.arjuna.ats.jta.recovery."
+"XAResourceRecovery</property> sera sensée représenter une de ces instances, "
+"et sa valeur devra correspondre au nom de la classe. Ainsi :"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:57
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+
+#. Tag: para
+#: Transaction_Recovery.xml:58
+#, no-c-format
+msgid ""
+"Additional information that will be passed to the instance when it is "
+"created may be specified after a semicolon:"
+msgstr ""
+"Les informations supplémentaires, passées à l'instance quand elle sera "
+"créée, pourraient être spécifiées après un point virgule :"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+
+#. Tag: para
+#: Transaction_Recovery.xml:63
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr ""
+"Ces propriétés ont besoin d'aller dans la section JTA du fichier de "
+"propriété."
+
+#. Tag: para
+#: Transaction_Recovery.xml:67
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr "Toute erreur sera reportée pendant la phase de recouvrement."
+
+#. Tag: screen
+#: Transaction_Recovery.xml:70
+#, no-c-format
+msgid ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+msgstr ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+
+#. Tag: para
+#: Transaction_Recovery.xml:71
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr "Chaque méthode devra retourner les informations suivantes :"
+
+#. Tag: para
+#: Transaction_Recovery.xml:76
+#, no-c-format
+msgid ""
+"<methodname>initialise</methodname>: once the instance has been created, any "
+"additional information which occurred on the property value (anything found "
+"after the first semi-colon) will be passed to the object. The object can "
+"then use this information in an implementation specific manner to initialise "
+"itself, for example."
+msgstr ""
+"<methodname>initialise</methodname>: une fois que l'instance a été créée, "
+"toute information supplémentaire apposée à la valeur de la propriété (tout "
+"ce qui suit le point virgule) sera passée à l'objet. L'objet pourra alors "
+"utiliser cette information d'une manière particulière à l'implémentation "
+"pour s'initialiser lui-même, par exemple."
+
+#. Tag: para
+#: Transaction_Recovery.xml:81
+#, no-c-format
+msgid ""
+"<methodname>hasMoreResources</methodname>: each <code>XAResourceRecovery</"
+"code> implementation may provide multiple <code>XAResource</code> instances. "
+"Before any call to <methodname>getXAResource</methodname> is made, "
+"<methodname>hasMoreResources</methodname> is called to determine whether "
+"there are any further connections to be obtained. If this returns false, "
+"<methodname>getXAResource</methodname> will not be called again during this "
+"recovery sweep and the instance will not be used further until the next "
+"recovery scan."
+msgstr ""
+"<methodname>hasMoreResources</methodname>: chaque implémentation "
+"<code>XAResourceRecovery</code> peut fournir des instances <code>XAResource</"
+"code> multiples. Avant d'appeler <methodname>getXAResource</methodname>, "
+"<methodname>hasMoreResources</methodname> est appelé pour déterminer s'il "
+"n'y a pas davantage de connexions à obtenir. S'il retourne 'false'. "
+"<methodname>getXAResource</methodname> ne sera pas rappelé à nouveau pendant "
+"cette session de recouvrement et l'instance ne sera plus utilisée avant le "
+"prochain balayage de recouvrement."
+
+#. Tag: para
+#: Transaction_Recovery.xml:86
+#, no-c-format
+msgid ""
+"<methodname>getXAResource</methodname>: returns an instance of the "
+"<code>XAResource</code> object. How this is created (and how the parameters "
+"to its constructors are obtained) is up to the <code>XAResourceRecovery</"
+"code> implementation. The parameters to the constructors of this class "
+"should be similar to those used when creating the initial driver or data "
+"source, and should obviously be sufficient to create new <code>XAResources</"
+"code> that can be used to drive recovery."
+msgstr ""
+"<methodname>getXAResource</methodname>: retourne une instance de l'objet "
+"<code>XAResource</code>. La façon dont cela est créé (et la façon dont les "
+"paramètres de ses constructeurs sont obtenus) est du ressort de "
+"l'implémentation <code>XAResourceRecovery</code>. Les paramètres des "
+"constructeurs de cette classe devraient être semblables à ceux qui sont "
+"utilisés au moment de la création du pilote initial ou de la source de "
+"données, et devraient évidemment être suffisants pour créer un nouveau "
+"<code>XAResources</code> qui pourrait être utilisé pour actionner le "
+"recouvrement."
+
+#. Tag: para
+#: Transaction_Recovery.xml:92
+#, no-c-format
+msgid ""
+"If you want your <code>XAResourceRecovery</code> instance to be called "
+"during each sweep of the recovery manager then you should ensure that once "
+"<methodname>hasMoreResources</methodname> returns false to indicate the end "
+"of work for the current scan it then returns true for the next recovery scan."
+msgstr ""
+"SI vous souhaitez que votre instance <code>XAResourceRecovery</code> soit "
+"appelée à chaque balayage du gestionnaire de recouvrement, alors vous devrez "
+"veiller à ce qu'une fois que <methodname>hasMoreResources</methodname> "
+"retourne 'false' pour indiquer la fin du travail du balayage en cours, il "
+"retourne alors 'true' pour le prochain balayage de recouvrement."
+
+#. Tag: title
+#: Transaction_Recovery.xml:99
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr "Les implémentations XAResourceRecovery expédiées"
+
+#. Tag: para
+#: Transaction_Recovery.xml:100
+#, no-c-format
+msgid ""
+"Recovery of <interfacename>XA</interfacename> datasources can sometimes be "
+"implementation dependant, requiring developers to provide their own "
+"<interfacename>XAResourceRecovery</interfacename> instances. However, "
+"JBossTS ships with several out-of-the-box implementations that may be useful."
+msgstr ""
+"Le recouvrement des bases de données <interfacename>XA</interfacename> peut "
+"parfois dépendre de l'implémentation, obligeant les développeurs à fournir "
+"leurs propres instances <interfacename>XAResourceRecovery</interfacename>. "
+"Cependant, JBossTS est présenté avec plusieurs implémentations standard qui "
+"peuvent être utiles."
+
+#. Tag: para
+#: Transaction_Recovery.xml:105
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: this expects an XML property file to be specified upon "
+"creation and from which it will read the database URL, username and "
+"password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: s'attend à ce qu'un fichier de propriété XML soit spécifié "
+"au moment de la création et dans lequel on lira l'URL de la base de données, "
+"le nom d'utilisateur et le mot de passe. Par exemple :"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:108
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+
+#. Tag: para
+#: Transaction_Recovery.xml:111
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: this recovery implementation should work on any datasource "
+"that is exposed via JNDI. It expects an XML property file to be specified "
+"upon creation and from which it will read the database JNDI name, username "
+"and password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: cette implémentation de recouvrement devrait fonctionner sur "
+"n'importe quelle source de données qui est exposée via JNDI. Elle s'attend à "
+"ce qu'un fichier de propriété XML soit spécifié au moment de sa création et "
+"à partir duquel il lira le nom JNDI de la base de données, le nom "
+"d'utilisateur et le mot de passe. Ainsi :"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:114
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,664 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr "Transactions"
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr "L'API"
+
+#. Tag: para
+#: Transactions.xml:9
+#, no-c-format
+msgid ""
+"The Java Transaction API consists of three elements: a high-level "
+"application transaction demarcation interface, a high-level transaction "
+"manager interface intended for application server, and a standard Java "
+"mapping of the X/Open XA protocol intended for transactional resource "
+"manager. All of the JTA classes and interfaces occur within the "
+"<package>javax.transaction</package> package, and the corresponding JBossJTA "
+"implementations within the <package>com.arjuna.ats.jta</package> package."
+msgstr ""
+"L'API de transaction Java consite en trois éléments : une interface de "
+"démarcation de transaction d'application de haut-niveau, d'une interface de "
+"gestionnaire de transaction de haut-niveau, et un mappage Java standard du "
+"protocole XA X/Open destiné au gestionnaire de ressources transactionnelles. "
+"Toutes les interfaces et les classes JTA ont lieu dans le paquet "
+"<package>javax.transaction</package> et les implémentations JBossJTA "
+"correspondantes ont lieu dans le paquet <package>com.arjuna.ats.jta</"
+"package>."
+
+#. Tag: para
+#: Transactions.xml:13
+#, no-c-format
+msgid ""
+"Each 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. The contents of this "
+"should be alphanumeric."
+msgstr ""
+"Chaque Xid que JBossTS crée doit comporter un identifiant unique codé à "
+"l'intérieur, et JBossTS ne recouvrera que les transactions et les états qui "
+"correspondent à un identifiant de noeud spécifié. L'identifiant du noeud à "
+"utiliser devra être fourni à JBossTS via la propriété <property>com.arjuna."
+"ats.arjuna.xa.nodeIdentifier</property>. Vous devez veiller à ce que cette "
+"valeur soit unique pour toutes les instances JBossTS. Si vous ne présentez "
+"pas de valeur, alors JBossTS en créera une et la reportera par "
+"l'infrastructure de journalisation. Son contenu sera alphanumérique. "
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: Transactions.xml:19
+#, no-c-format
+msgid ""
+"The <interfacename>UserTransaction</interfacename> interface provides "
+"applications with the ability to control transaction boundaries. It has "
+"methods for beginning, committing, and rolling back top-level transactions: "
+"nested transactions are not supported, and begin throws the "
+"<code>NotSupportedException</code> when the calling thread is already "
+"associated with a transaction. <interfacename>UserTransaction</"
+"interfacename> automatically associates newly created transactions with the "
+"invoking thread."
+msgstr ""
+"L'interface <interfacename>UserTransaction</interfacename> permettent aux "
+"applications de contrôler les limites des transactions. Elle a des méthodes "
+"pour commencer, valider et rejeter les transactions à haut-niveau : les "
+"transactions intégrées ne sont pas prises en charge, et 'begin' lance "
+"<code>NotSupportedException</code> quand le thread d'appel est déjà associé "
+"à une transaction. <interfacename>UserTransaction</interfacename> associe "
+"automatiquement des transactions nouvellement créées dans le thread "
+"invoquant."
+
+#. Tag: para
+#: Transactions.xml:24
+#, no-c-format
+msgid ""
+"In JBossJTA, UserTransactions can be obtained from the static "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname> method."
+msgstr ""
+"Dans JBossJTA, UserTransaction peut être obtenu à partir de la méthode "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname>."
+
+#. Tag: para
+#: Transactions.xml:28
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+"Pour sélectionner l'implémentation JTA locale, il est nécessaire de procéder "
+"aux étapes suivantes :"
+
+#. Tag: para
+#: Transactions.xml:33
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</property>."
+msgstr ""
+"veillez bien à ce que la propriété <property>com.arjuna.ats.jta."
+"jtaTMImplementation</property> soit configurée sur <property>com.arjuna.ats."
+"internal.jta.transaction.arjunacore.TransactionManagerImple</property>."
+
+#. Tag: para
+#: Transactions.xml:38
+#, no-c-format
+msgid ""
+"1.make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</property>."
+msgstr ""
+"1. Veillez à ce que la propriété <property>com.arjuna.ats.jta."
+"jtaUTImplementation</property> soit configurée sur <property>com.arjuna.ats."
+"internal.jta.transaction.arjunacore.UserTransactionImple</property>."
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: Transactions.xml:45
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface allows the "
+"application server to control transaction boundaries on behalf of the "
+"application being managed."
+msgstr ""
+"L'interface <interfacename>TransactionManager</interfacename> permet au "
+"serveur d'application de contrôler les limites de la transaction pour le "
+"compte de l'application en cours."
+
+#. Tag: para
+#: Transactions.xml:50
+#, no-c-format
+msgid ""
+"In JBossJTA, transaction manager implementations can be obtained from the "
+"static <methodname>com.arjuna.ats.jta.TransactionManager.transactionManager</"
+"methodname> method."
+msgstr ""
+"Dans JBossJTA, les implémentations du gestionnaire de transactions peuvent "
+"être obtenues à partir de la méthode <methodname>com.arjuna.ats.jta."
+"TransactionManager.transactionManager</methodname> ."
+
+#. Tag: para
+#: Transactions.xml:54
+#, no-c-format
+msgid ""
+"The Transaction Manager maintains the transaction context association with "
+"threads as part of its internal data structure. A thread’s transaction "
+"context is either null or it refers to a specific global transaction. "
+"Multiple threads may be associated with the same global transaction. As "
+"noted above, nested transactions are not supported."
+msgstr ""
+"Le gestionnaire de transactions maintient l'association du contexte de "
+"transaction aux threads dans le cadre de sa structure de données interne. Le "
+"contexte de transaction d'un thread est soit nul, soit il se réfère à une "
+"transaction globale spécifique. Les threads multiples peuvent être associés "
+"à une même transaction globale. Comme mentionné ci-dessus, les transactions "
+"intégrées ne sont pas prises en charge."
+
+#. Tag: para
+#: Transactions.xml:57
+#, no-c-format
+msgid ""
+"Each transaction context is encapsulated by a Transaction object, which can "
+"be used to perform operations which are specific to the target transaction, "
+"regardless of the calling thread’s transaction context."
+msgstr ""
+"Chaque contexte de transaction est encapsulé par un objet de transaction, "
+"qui peut être utilisé pour effectuer des opérations spécifiques à une "
+"transaction cible, quelque soit le contexte de transaction du thread "
+"appelant."
+
+#. Tag: para
+#: Transactions.xml:60
+#, no-c-format
+msgid ""
+"The <methodname>begin</methodname> method of "
+"<interfacename>TransactionManager</interfacename> starts a new top-level "
+"transaction and associates the transaction context with the calling thread. "
+"If the calling thread is already associated with a transaction then it "
+"throws the <code>NotSupportedException</code>."
+msgstr ""
+"La méthode <methodname>begin</methodname> de "
+"<interfacename>TransactionManager</interfacename> débute une nouvelle "
+"transaction du niveau supérieur et associe le contexte de transaction au "
+"thread appelant. Si le thread appelant est déjà associé à la transaction, "
+"alors il lance une <code>NotSupportedException</code>."
+
+#. Tag: para
+#: Transactions.xml:63
+#, no-c-format
+msgid ""
+"The <methodname>getTransaction</methodname> method returns the Transaction "
+"object that represents the transaction context currently associated with the "
+"calling thread. This object can be used to perform various operations on the "
+"target transaction, described later."
+msgstr ""
+"La méthode <methodname>getTransaction</methodname> retourne l'objet "
+"Transaction qui représente le contexte de transaction couramment associé au "
+"thread appelant. Cet objet peut être utilisé pour effectuer plusieurs "
+"opérations sur la transaction ciblée, décrite plus loin."
+
+#. Tag: para
+#: Transactions.xml:66
+#, no-c-format
+msgid ""
+"The commit method is used to complete the transaction currently associated "
+"with the calling thread. After it returns, the calling thread is associated "
+"with no transaction. If commit is called when the thread is not associated "
+"with any transaction context, the TM throws an exception. In some "
+"implementation, the commit operation is restricted to the transaction "
+"originator only. If the calling thread is not allowed to commit the "
+"transaction, the TM throws an exception. JBossJTA does not currently impose "
+"any restriction on the ability of threads to terminate transactions."
+msgstr ""
+"La méthode de validation est utilisées pour achever la transaction "
+"actuellement associée au thread appelant. Après son retour, le thread "
+"appelant n'est pas associé à une transaction. Si 'commit' est appelé quand "
+"le thread n'est associé à aucun contexte de transaction, le TM lance une "
+"exception. Dans certaines implémentations, l'opération 'commit' est limitée "
+"à l'expéditeur uniquement. Si le thread appelant n'est pas autorisé à "
+"valider la transaction, le TM envoie une exception. JBossJTA n'impose pas "
+"actuellement de restrictions sur la capacité des threads à terminer des "
+"transactions."
+
+#. Tag: para
+#: Transactions.xml:69
+#, no-c-format
+msgid ""
+"The <methodname>rollback</methodname> method is used to rollback the "
+"transaction associated with the current thread. After the "
+"<methodname>rollback</methodname> method completes, the thread is associated "
+"with no transaction."
+msgstr ""
+"La méthode <methodname>rollback</methodname> est utilisée pour rejeter la "
+"transaction associée au thread courant. Après que la méthode "
+"<methodname>rollback</methodname> soit terminée, le thread n'est plus "
+"associé à une transaction."
+
+#. Tag: para
+#: Transactions.xml:73
+#, no-c-format
+msgid ""
+"In a multi-threaded environment it is possible that multiple threads are "
+"active within the same transaction. If checked transaction semantics have "
+"been disabled, or the transaction times out, then it is possible for a "
+"transaction to be terminated by a thread other than the one that created it. "
+"In this case, it is often important that this information is communicated to "
+"the creator. JBossTS does this during commit or rollback by throwing "
+"<code>IllegalStateException</code>."
+msgstr ""
+"Dans un environnement multi-thread, il est possible que des threads "
+"multiples soient actifs au sein d'une même transaction. Si les sémantiques "
+"de transaction vérifiées ont été désactivées, ou que la transaction est "
+"suspendue, alors il est possible que la transaction soit terminée par un "
+"thread distinct de celui qui l'a créé. Dans ce cas, il est souvent important "
+"que cette information soit communiquée au créateur. JBossTS effectue cela au "
+"moment de la validation ou du rejet en lançant <code>IllegalStateException</"
+"code>."
+
+#. Tag: title
+#: Transactions.xml:78
+#, no-c-format
+msgid "Suspending and resuming a transaction"
+msgstr "Suspendre et terminer une transaction"
+
+#. Tag: para
+#: Transactions.xml:79
+#, no-c-format
+msgid ""
+"The JTA supports the concept of a thread temporarily suspending and resuming "
+"transactions to enable it to perform non-transactional work. The suspend "
+"method is called to temporarily suspend the current transaction that is "
+"associated with the calling thread, i.e., so that the thread is no longer "
+"operating within its scope. If the thread is not associated with any "
+"transaction, a null object reference is returned; otherwise, a valid "
+"<code>Transaction</code> object is returned. The <code>Transaction</code> "
+"object can later be passed to the resume method to reinstate the transaction "
+"context."
+msgstr ""
+"JTA supporte le concept qu'un thread puisse être suspendu temporairement et "
+"puisse terminer des transactions pour leur permettre d'effectuer des tâches "
+"non-transactionnelles. La méthode de suspension est appelée pour interrompre "
+"temporairement la transaction en cours associée au thread appelant, c'est à "
+"dire, que le thread n'y opère plus. Si le thread n'est associé à aucune "
+"transaction, une référence objet nulle est retournée, sinon, un objet valide "
+"<code>Transaction</code> est retourné. L'objet <code>Transaction</code> "
+"pourra plus tard être passé à la méthode 'resume' pour rétablir le contexte "
+"de transaction."
+
+#. Tag: para
+#: Transactions.xml:83
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method associates the specified "
+"transaction context with the calling thread. If the transaction specified is "
+"a valid transaction, the transaction context is associated with the calling "
+"thread; otherwise, the thread is associated with no transaction."
+msgstr ""
+"La méthode <methodname>resume</methodname> associe le contexte de "
+"transaction spécifié au thread appelant. Si la transaction spécifiée est une "
+"transaction valide, le contexte de transaction sera associé au thread "
+"appelant, sinon, le thread ne sera pas associé à une transaction."
+
+#. Tag: para
+#: Transactions.xml:87
+#, no-c-format
+msgid ""
+"If <methodname>resume</methodname> is invoked when the calling thread is "
+"already associated with another transaction, the Transaction Manager throws "
+"the <code>IllegalStateException</code> exception."
+msgstr ""
+"Si <methodname>resume</methodname> est invoqué quand le thread appelant est "
+"déjà associé à une autre transaction, le gestionnaire de transactions lance "
+"l'exception <code>IllegalStateException</code>. "
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+
+#. Tag: para
+#: Transactions.xml:93
+#, no-c-format
+msgid ""
+"Some Transaction Manager implementations allow a suspended transaction to be "
+"resumed by a different thread. This feature is not required by JTA, but "
+"JBossJTA does support this."
+msgstr ""
+"Certaines implémentations de gestionnaires de transactions permettent qu'une "
+"transaction soit terminée par un thread différent. Cette fonctionnalité "
+"n'est pas requise par JTA, mais JBossJTA la supporte."
+
+#. Tag: para
+#: Transactions.xml:97
+#, no-c-format
+msgid ""
+"When a transaction is suspended the application server must ensure that the "
+"resources in use by the application are no longer registered with the "
+"suspended transaction. When a resource is de-listed this triggers the "
+"Transaction Manager to inform the resource manager to disassociate the "
+"transaction from the specified resource object. When the application’s "
+"transaction context is resumed, the application server must ensure that the "
+"resources in use by the application are again enlisted with the transaction. "
+"Enlisting a resource as a result of resuming a transaction triggers the "
+"Transaction Manager to inform the resource manager to re-associate the "
+"resource object with the resumed transaction."
+msgstr ""
+"Quand une transaction est interrompue, le serveur d'application doit veiller "
+"à ce que les ressources utilisées par l'application ne soient plus "
+"enregistrées dans la transaction interrompue. Quand une ressource est de-"
+"listée, cela amène le gestionnaire de transaction à informer le gestionnaire "
+"de ressources à dissocier la transaction de l'objet ressource spécifié. "
+"Quand le contexte de transaction de l'application est terminé, le serveur de "
+"l'application doit veiller à ce que les ressources utilisées par "
+"l'application soient à nouveau engagées dans la transaction. Engager une "
+"ressource suite à la fin d'une transaction entraîne le gestionnaire de "
+"transaction à informer le gestionnaire de ressources d'associer à nouveau "
+"l'objet ressource à la transaction qui vient de se terminer."
+
+#. Tag: title
+#: Transactions.xml:101
+#, no-c-format
+msgid "The Transaction interface"
+msgstr "L'interface de transaction"
+
+#. Tag: para
+#: Transactions.xml:102
+#, no-c-format
+msgid ""
+"The <interfacename>Transaction</interfacename> interface allows operations "
+"to be performed on the transaction associated with the target object. Every "
+"top-level transaction is associated with one <code>Transaction</code> object "
+"when the transaction is created. The <code>Transaction</code> object can be "
+"used to:"
+msgstr ""
+"L'interface <interfacename>Transaction</interfacename> permet à des "
+"opérations d'être effectuées sur la transaction associée à l'objet ciblé. "
+"Chaque transaction de haut-niveau est associée à une objet de "
+"<code>Transaction</code> quand la transaction est créée. L'objet "
+"<code>Transaction</code> peut être utilisé pour :"
+
+#. Tag: para
+#: Transactions.xml:108
+#, no-c-format
+msgid "Enlist the transactional resources in use by the application."
+msgstr "Engager les ressources transactionnelles utilisées par l'application."
+
+#. Tag: para
+#: Transactions.xml:113
+#, no-c-format
+msgid "Register for transaction synchronization call backs."
+msgstr ""
+"S'enregistrer pour les rappels automatiques de synchronisation de "
+"transactions."
+
+#. Tag: para
+#: Transactions.xml:118
+#, no-c-format
+msgid "Commit or rollback the transaction."
+msgstr "Valider ou rejeter la transaction."
+
+#. Tag: para
+#: Transactions.xml:123
+#, no-c-format
+msgid "Obtain the status of the transaction."
+msgstr "Obtenir le statut de la transaction."
+
+#. Tag: para
+#: Transactions.xml:128
+#, no-c-format
+msgid ""
+"The <methodname>commit</methodname> and <methodname>rollback</methodname> "
+"methods allow the target object to be committed or rolled back. The calling "
+"thread is not required to have the same transaction associated with the "
+"thread. If the calling thread is not allowed to commit the transaction, the "
+"transaction manager throws an exception. At present JBossJTA does not impose "
+"restrictions on threads terminating transactions."
+msgstr ""
+"Les méthodes <methodname>commit</methodname> et <methodname>rollback</"
+"methodname> permettent à l'objet-cible d'être validé ou rejeté. Le thread "
+"appelant n'a pas besoin d'avoir la même transaction associée au thread. Si "
+"le thread appelant n'est pas autorisé à valider la transaction, le "
+"gestionnaire de transactions lance une exception. Pour l'instant, JBossJTA "
+"n'impose pas de restrictions sur les threads qui terminent des transactions."
+
+#. Tag: title
+#: Transactions.xml:132
+#, no-c-format
+msgid "Resource enlistment"
+msgstr "Engagement de ressources"
+
+#. Tag: para
+#: Transactions.xml:133
+#, no-c-format
+msgid ""
+"Transactional resources such as database connections are typically managed "
+"by the application server in conjunction with some resource adapter and "
+"optionally with connection pooling optimization. In order for an external "
+"transaction manager to co-ordinate transactional work performed by the "
+"resource managers, the application server must enlist and de-list the "
+"resources used in the transaction. These resources (participants) are "
+"enlisted with the transaction so that they can be informed when the "
+"transaction terminates, for example, are driven through the two-phase commit "
+"protocol."
+msgstr ""
+"Les ressources transactionnelles comme les connexions de bases de données "
+"sont normalement gérées par le serveur d'applications en conjonction à "
+"certains adaptateurs de ressources et optionnellement, avec l'optimisation "
+"de regroupement des connexions. Pour qu'un gestionnaire de transactions "
+"externe puisse coordonner le travail transactionnel effectué par les "
+"gestionnaires de ressources, le serveur d'applications doit engager et de-"
+"lister les ressources utilisées dans la transaction. Ces ressources "
+"(participants) sont engagés dans la transaction de façon à ce qu'ils "
+"puissent être informés quand la transaction est terminée, et, par exemple, "
+"peuvent être envoyés vers le protocole de validation en deux-étapes."
+
+#. Tag: para
+#: Transactions.xml:137
+#, no-c-format
+msgid ""
+"As stated previously, the JTA is much more closely integrated with the XA "
+"concept of resources than the arbitrary objects. For each resource in-use by "
+"the application, the application server invokes the "
+"<methodname>enlistResource</methodname> method with an <code>XAResource</"
+"code> object which identifies the resource in use. See for details on how "
+"the implementation of the <code>XAResource</code> can affect recovery in the "
+"event of a failure."
+msgstr ""
+"Comme expliqué plus haut, le JTA est intégré de bien plus prêt au concept XA "
+"de ressources que les objets arbitraires. Pour chaque ressource utilisée par "
+"l'application, le serveur d'applications invoque la méthode "
+"<methodname>enlistResource</methodname> avec un objet <code>XAResource</"
+"code> qui identifie la ressource utilisée. Voir des détails sur la façon "
+"dont on implémente la <code>XAResource</code> peut affecter le recouvrement "
+"en cas d'échec."
+
+#. Tag: para
+#: Transactions.xml:140
+#, no-c-format
+msgid ""
+"The enlistment request results in the transaction manager informing the "
+"resource manager to start associating the transaction with the work "
+"performed through the corresponding resource. The transaction manager is "
+"responsible for passing the appropriate flag in its <methodname>XAResource."
+"start</methodname> method call to the resource manager."
+msgstr ""
+"Les résultats de la demande d'engagement dans le gestionnaire de "
+"transactions informant le gestionnaire de ressources de commencer à associer "
+"la transaction au travail effectué par la ressource correspondante. Le "
+"gestionnaire de transactions est responsable de passer le drapeau qui "
+"convient dans sa méthode call <methodname>XAResource.start</methodname> vers "
+"le gestionnaire de ressources."
+
+#. Tag: para
+#: Transactions.xml:143
+#, no-c-format
+msgid ""
+"The <methodname>delistResource</methodname> method is used to disassociate "
+"the specified resource from the transaction context in the target object. "
+"The application server invokes the method with the two parameters: the "
+"<code>XAResource</code> object that represents the resource, and a flag to "
+"indicate whether the operation is due to the transaction being suspended "
+"(TMSUSPEND), a portion of the work has failed (TMFAIL), or a normal resource "
+"release by the application (TMSUCCESS)."
+msgstr ""
+"La méthode <methodname>delistResource</methodname> est utilisée pour "
+"désassocier la ressource spécifiée à partir d'un contexte de transaction "
+"dans l'objet ciblé. Le serveur d'application invoque la méthode avec les "
+"deux paramètres : l'objet <code>XAResource</code> qui représente la "
+"ressource, et le drapeau qui indique si l'opération est due au fait que la "
+"transaction soit interrompue (TMSUSPEND), qu'une portion du travail ait "
+"échoué (TMFAIL), ou à une sortie de ressources habituelle par l'application "
+"(TMSUCCESS)."
+
+#. Tag: para
+#: Transactions.xml:146
+#, no-c-format
+msgid ""
+"The de-list request results in the transaction manager informing the "
+"resource manager to end the association of the transaction with the target "
+"<code>XAResource</code>. The flag value allows the application server to "
+"indicate whether it intends to come back to the same resource whereby the "
+"resource states must be kept intact. The transaction manager passes the "
+"appropriate flag value in its <methodname>XAResource.end</methodname> method "
+"call to the underlying resource manager."
+msgstr ""
+"Les résultats de demande de-list du gestionnaire de transaction informant le "
+"gestionnaire de ressources de mettre fin à l'association de la transaction "
+"avec la cible <code>XAResource</code>. La valeur du drapeau permet au "
+"serveur de l'application d'indiquer s'il a l'intention de revenir à la "
+"ressource pour laquelle les états des ressources doivent être gardées "
+"intactes. Le gestionnaire de transactions passe la valeur du drapeau qui "
+"convient à la méthode call <methodname>XAResource.end</methodname> vers le "
+"gestionnaire de ressources sous-jacent."
+
+#. Tag: title
+#: Transactions.xml:150
+#, no-c-format
+msgid "Transaction synchronization"
+msgstr "Synchronisation de transactions"
+
+#. Tag: para
+#: Transactions.xml:151
+#, no-c-format
+msgid ""
+"Transaction synchronization allows the application server to be notified "
+"before and after the transaction completes. For each transaction started, "
+"the application server may optionally register a Synchronization call back "
+"object to be invoked by the transaction manager:"
+msgstr ""
+"La synchronisation de transactions permet au serveur de l'application d'être "
+"notifié avant et après que la transaction soit terminée. Pour chaque début "
+"de transaction, le serveur d'applications peut enregistrer un objet de "
+"rappel de Synchronisation qui doit être invoqué par le gestionnaire de "
+"transactions :"
+
+#. Tag: para
+#: Transactions.xml:157
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method is called prior to the "
+"start of the two-phase transaction complete process. This call is executed "
+"in the same transaction context of the caller who initiates the "
+"<methodname>TransactionManager.commit</methodname> or the call is executed "
+"with no transaction context if <methodname>Transaction.commit</methodname> "
+"is used."
+msgstr ""
+"La méthode <methodname>beforeCompletion</methodname> est appelée avant le "
+"début du processus total de transaction en deux-étapes. Cet appel est "
+"exécuté dans le même contexte de transaction que l'appelant qui initie "
+"<methodname>TransactionManager.commit</methodname> ou l'appel est exécuté "
+"sans contexte de transaction si <methodname>Transaction.commit</methodname> "
+"est utilisé."
+
+#. Tag: para
+#: Transactions.xml:162
+#, no-c-format
+msgid ""
+"The <methodname>afterCompletion</methodname> method is called after the "
+"transaction has completed. The status of the transaction is supplied in the "
+"parameter. This method is executed without a transaction context."
+msgstr ""
+"La méthode <methodname>afterCompletion</methodname> est appelée après que la "
+"transaction soit terminée. Le statut de la transaction est exprimé à travers "
+"le paramètre. Cette méthode est exécutée sans contexte de transaction."
+
+#. Tag: title
+#: Transactions.xml:168
+#, no-c-format
+msgid "Transaction equality"
+msgstr "Egalité de transaction"
+
+#. Tag: para
+#: Transactions.xml:169
+#, no-c-format
+msgid ""
+"The transaction manager implements the Transaction object’s equals method to "
+"allow comparison between the target object and another Transaction object. "
+"The equals method should return true if the target object and the parameter "
+"object both refer to the same global transaction."
+msgstr ""
+"Le gestionnaire de transaction implémente la méthode equals de l'objet "
+"Transaction afin de permettre une comparaison entre l'objet ciblé et un "
+"autre objet Transaction. La méthode equals doit retourner 'true' si l'objet "
+"ciblé et l'objet paramètre réfèrent tous deux à la même transaction globale."
+
+#. Tag: screen
+#: Transactions.xml:173
+#, no-c-format
+msgid ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
+msgstr ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/fr-FR/Using_JBossJTA_in_Application_Servers.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,284 @@
+# translation of Author_Group.po to French
+# Language fr-FR translations for package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-19 11:03+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\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
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr "Utiliser JBossJTA dans les serveurs d'application"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr "Serveur d'application JBoss"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:10
+#, no-c-format
+msgid "Service Configuration"
+msgstr "Configuration du service"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:11
+#, no-c-format
+msgid ""
+"The JBoss Transaction Service is configured primarily via the XML files "
+"stored in the etc directory, but when run as a JBOSS service there are a "
+"number of configurable attributes available. They are as follows:"
+msgstr ""
+"Le service de transaction JBoss est configuré principalement par les "
+"fichiers XML stockés dans le répertoire etc, mais lorsqu'il est exécuté en "
+"tant que service JBoss, on compte un certain nombre d'attributs de "
+"disponibles. Les voici :"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:17
+#, no-c-format
+msgid ""
+"TransactionTimeout – The default transaction timeout to be used for new "
+"transactions. Specified as an integer in seconds."
+msgstr ""
+"TransactionTimeout – Le temps mort de transaction par défaut à utiliser pour "
+"les nouvelles transactions. Déterminé en tant qu'entier relatif et exprimé "
+"en secondes."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:22
+#, no-c-format
+msgid ""
+"StatisticsEnabled – This determines whether or not the transaction service "
+"should gather statistical information. This information can then be viewed "
+"using the PerformanceStatistics MBean. Specified as a Boolean. The default "
+"is to not gather this information."
+msgstr ""
+"StatisticsEnabled – détermine si oui ou non le service de transactions doit "
+"collecter des informations statistiques. Cette information peut être "
+"visualisée en utilisant PerformanceStatistics MBean. Spécifié en tant que "
+"Boolean. Par défaut, on ne collecte pas cette information."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:27
+#, no-c-format
+msgid ""
+"PropagateFullContext – This determines whether a full transactional context "
+"is propagated by context importer/exporter. If set to false only the current "
+"transaction context is propagated. If set to true the full transaction "
+"context (including parent transactions) is propagated."
+msgstr ""
+"PropagateFullContext – détermine si le contexte transactionnel dans son "
+"ensemble est propagé par l'importateur/ou l'exportateur du contexte. S'il "
+"est configuré à 'False' (faux), le contexte transactionnel courant "
+"uniquement est propagé. S'il est configuré à 'True' (vrai), le contexte "
+"transactionnel dans sa totalité (y compris les transactions parent) est "
+"propagé."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:32
+#, no-c-format
+msgid ""
+"These attributes are specified as MBean attributes in the jboss-service.xml "
+"file located in the server/all/conf directory, for example:"
+msgstr ""
+"Ces attributs sont spécifiés en tant qu'attributs MBean dans le fichier "
+"jboss-service.xml qui est situé dans le répertoire server/all/conf, par "
+"exemple :"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:35
+#, no-c-format
+msgid ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+msgstr ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:36
+#, no-c-format
+msgid ""
+"The transaction service is configurable also via the standard JBoss "
+"Transaction Service property files. These are located in the JBossTS install "
+"location under the etc sub-directory."
+msgstr ""
+"Le service de transaction est également configurable à travers les fichiers "
+"de propriété standard de JBoss Transaction Service. Ils sont situés dans "
+"JBossTS install dans le sous-répertoire etc."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:39
+#, no-c-format
+msgid ""
+"These files can be edited manually or through JMX. Each property file is "
+"exposed via an object with the name <code>com.arjuna.ts.properties</code> "
+"and an attribute of module where module is equal to the name of the module "
+"to be configured, for example, <code>com.arjuna.ts.properties:module=arjuna</"
+"code>."
+msgstr ""
+"Ces fichiers peuvent être modifiés manuellement ou bien à travers JMX. "
+"Chaque fichier de propriété est exposé par un objet du nom <code>com.arjuna."
+"ts.properties</code> et par un attribut de module pour lequel chaque module "
+"est égal au nom du module à configurer, par exemple, <code>com.arjuna.ts."
+"properties:module=arjuna</code>."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:43
+#, no-c-format
+msgid "Logging"
+msgstr "Logging"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:44
+#, no-c-format
+msgid ""
+"In order to make JBossTS logging semantically consistent with JBossAS, the "
+"TransactionManagerService modifies the level of some log messages. This is "
+"achieved by overriding the value of the <property>com.arjuna.common.util."
+"logger</property> property given in the <filename>jbossjta-properties.xml</"
+"filename> file. Therefore, the value of this property will have no effect on "
+"the logging behaviour when running embedded in JBossAS. By forcing use of "
+"the log4j_releveler logger, the TransactionManagerService causes all INFO "
+"level messages in the transaction code to be modified to behave as DEBUG "
+"messages. Therefore, these messages will not appear in log files if the "
+"filter level is INFO. All other log messages behave as normal."
+msgstr ""
+"Pour que JBossTS logging puisse être sémantiquement consistant avec JBossAS, "
+"le TransactionManagerService modifie le niveau de certains messages log. "
+"Cela est effectué en remplaçant la valeur de la propriété <property>com."
+"arjuna.common.util.logger</property> donnée dans le fichier "
+"<filename>jbossjta-properties.xml</filename>. Ainsi, la valeur de cette "
+"propriété n'aura aucun effet sur le comportement de logging en cours "
+"d'exécution, lorsqu'elle est intégrée dans JBossAS. en forçant l'utilisation "
+"du log4j_releveler logger, le TransactionManagerService cause la "
+"modification de tous les messages au niveau INFO du code de transaction à "
+"être modifiés pour qu'ils se comportent comme des messages DEBUG. Ainsi, ces "
+"messages n'apparaîtront pas dans des fichiers de journalisation si le niveau "
+"du filtre est INFO. Tous les autres messages de journalisation se comportent "
+"normalement."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:49
+#, no-c-format
+msgid "The services"
+msgstr "Les services "
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:50
+#, no-c-format
+msgid ""
+"There is currently one service offered by the JBOSS integration called "
+"TransactionManagerService. Here we shall discuss what this service does."
+msgstr ""
+"Il existe actuellement un service offert par l'intégration JBOSS qui "
+"s'appelle TransactionManagerService. Nous allons parler de ce que ce service "
+"fait."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:54
+#, no-c-format
+msgid ""
+"The transaction manager service’s main purpose is to ensure the recovery "
+"manager is started. It also binds the JBossTS JTA transaction manager to "
+"java:/TransactionManager name with the JNDI provider. This service depends "
+"upon the existence of the CORBA ORB Service and it must be using JacORB as "
+"the underlying ORB implementation."
+msgstr ""
+"Le but principal du service du gestionnaire de transaction est de veiller à "
+"ce que le gestionnaire de recouvrement soit démarré. Il lie également le "
+"gestionnaire de transactions JBossTS JTA au nom java:/TransactionManager "
+"avec le fournisseur JNDI. Ce service dépend de l'existence du Service CORBA "
+"ORB et doit utiliser JacORB en tant qu'implémentation ORB."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:57
+#, no-c-format
+msgid "There are two instances of this service:"
+msgstr "Il existe deux instances de ce service :"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:62
+#, no-c-format
+msgid ""
+"distributed: this uses the JTS enabled transaction manager implementation "
+"and hence supports distributed transactions and recovery. To configure this "
+"use the <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname> class. This is the default configuration."
+msgstr ""
+"Distribuée : cela utilise l'implémentation du gestionnaire de transaction "
+"activé JTS et prend en charge ainsi le recouvrement et les transactions "
+"distribuées. Pour le configurer, utiliser la classe <classname>com.arjuna."
+"ats.jbossatx.jts.TransactionManagerService</classname>. C'est la classe par "
+"défaut de configuration."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:67
+#, no-c-format
+msgid ""
+"local: this uses the purely local JTA implementation. To configure this use "
+"the <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
+"classname> class."
+msgstr ""
+"local : cela utilise l'implémentation JTA purement locale. Pour la "
+"configurer, utiliser la classe <classname>com.arjuna.ats.jbossatx.jta."
+"TransactionManagerService</classname>."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:73
+#, no-c-format
+msgid "Ensuring Transactional Context is Propagated to the Server"
+msgstr "Veiller à ce que le contexte transactionnel soit propagé au serveur"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:74
+#, no-c-format
+msgid ""
+"It is possible to coordinate transactions from a coordinator which is not "
+"located within the JBoss server (e.g. using transactions created by an "
+"external OTS server). To ensure the transaction context is propagated via "
+"JRMP invocations to the server, the transaction propagation context factory "
+"needs to be explicitly set for the JRMP invoker proxy. This is done as "
+"follows:"
+msgstr ""
+"Il est possible de coordonner des transactions à partir d'un coordinateur "
+"qui ne soit pas situé dans le serveur JBoss (par ex. en utilisant des "
+"transactions créées par un serveur OTS externe). Pour s'assurer que le "
+"contexte de transaction soit propagé par les invocations JRMP vers le "
+"serveur, l'usine de contexte de propagation de la transaction a besoin "
+"d'être explicitement configuré pour l'invoqueur proxy JRMP. Cela est "
+"effectué de la façon suivante :"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/An_Introduction_to_the_JTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/An_Introduction_to_the_JTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/An_Introduction_to_the_JTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,146 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr "JTA について"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr "Java トランザクション API"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:9
+#, no-c-format
+msgid ""
+"The interfaces specified by the many transaction standards are typically too "
+"low-level for most application programmers. Therefore, Sun Microsystems has "
+"specified higher-level interfaces to assist in the development of "
+"distributed transactional applications. Note, these interfaces are still low-"
+"level, and require, for example, the programmer to be concerned with state "
+"management and concurrency for transactional application. In addition, they "
+"are geared more for applications which require XA resource integration "
+"capabilities, rather than the more general resources which the other APIs "
+"allow."
+msgstr ""
+"多くのトランザクション基準で指定されているインターフェイスは、アプリケーショ"
+"ンプログラマーにとって低レベルであるものがほとんどです。そのため、Sun "
+"Microsystems は分散トランザクションアプリケーションの開発をサポートするより高"
+"いレベルのインターフェイスを指定しています。しかし、Sun が指定するインター"
+"フェイスも十分なレベルではないため、プログラマーはトランザクションアプリケー"
+"ションの状態管理や並行性などに注意する必要があります。また、これらのインター"
+"フェイスはアプリケーション向けであるため、その他の API が対応できる一般的なリ"
+"ソースではなく、XA リソースの統合能力が必要となります。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:12
+#, no-c-format
+msgid ""
+"With reference to [JTA99], distributed transaction services typically "
+"involve a number of participants:"
+msgstr ""
+"[JTA99] の通り、分散トランザクションサービスには、通常複数の参加者が関与しま"
+"す："
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:17
+#, no-c-format
+msgid ""
+"Application server: which provides the infrastructure required to support "
+"the application run-time environment which includes transaction state "
+"management, for example, an EJB server."
+msgstr ""
+"アプリケーションサーバー：トランザクション状態管理を含むアプリケーション実行"
+"時環境をサポートするために必要なインフラストラクチャを提供します（例：EJB "
+"サーバー）。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:22
+#, no-c-format
+msgid ""
+"Transaction manager: provides the services and management functions required "
+"to support transaction demarcation, transactional resource management, "
+"synchronisation and transaction context propagation."
+msgstr ""
+"トランザクションマネージャ：トランザクション区分、トランザクションリソース管"
+"理、同期化、トランザクションコンテキスト伝搬をサポートするために必要なサービ"
+"スおよび管理機能を提供します。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:27
+#, no-c-format
+msgid ""
+"Resource manager: (through a resource adapter<footnote> <para> A Resource "
+"Adapter is used by an application server or client to connect to a Resource "
+"Manager. JDBC drivers which are used to connect to relational databases are "
+"examples of Resource Adapters. </para> </footnote>) provides the application "
+"with access to resources. The resource manager participates in distributed "
+"transactions by implementing a transaction resource interface used by the "
+"transaction manager to communicate transaction association, transaction "
+"completion and recovery."
+msgstr ""
+"リソースマネージャ：(リソースアダプタを介する<footnote> <para> リソースアダプ"
+"タは、Resource Manager に接続するためアプリケーションサーバーまたはクライアン"
+"トによって使用されます。リレーショナルデータベースに接続するため使用される "
+"JDBC ドライバが、リソースアダプタの一例です。</para> </footnote>) は、リソー"
+"スへアクセスできるアプリケーションを提供します。リソースマネージャは、トラン"
+"ザクションマネージャが使用するトランザクションリソースインターフェイスを実装"
+"することで分散トランザクションに参加し、トランザクションの関連付け、トランザ"
+"クションの完了やリカバリについて通信します。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:36
+#, no-c-format
+msgid ""
+"A communication resource manager (CRM): supports transaction context "
+"propagation and access to the transaction service for incoming and outgoing "
+"requests."
+msgstr ""
+"通信リソースマネージャ (CRM)：トランザクションコンテキストの伝搬や、着信およ"
+"び送信要求に対するトランザクションサービスへのアクセスをサポートします。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:41
+#, no-c-format
+msgid ""
+"From the transaction manager’s perspective, the actual implementation of the "
+"transaction services does not need to be exposed; only high-level interfaces "
+"need to be defined to allow transaction demarcation, resource enlistment, "
+"synchronization and recovery process to be driven from the users of the "
+"transaction services. The JTA is a high-level application interface that "
+"allows a transactional application to demarcate transaction boundaries, and "
+"contains also contains a mapping of the X/Open XA protocol."
+msgstr ""
+"トランザクションマネージャの観点では、実際のトランザクションサービスの実装を"
+"公開する必要はありません。トランザクションサービスのユーザーによるトランザク"
+"ション区分、リソース参加、同期化、回復処理を実現するため、ハイレベルなイン"
+"ターフェイスのみ定義する必要があります。JTA は、トランザクションアプリケー"
+"ションがトランザクション境界を区別できるようにするハイレベルなアプリケーショ"
+"ンインターフェイスで、X/Open XA プロトコルのマッピングも含んでいます。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:45
+#, no-c-format
+msgid ""
+"The JTA support provided by JBossJTA is compliant with the 1.0.1 "
+"specification."
+msgstr "JBossJTA が提供する JTA のサポートは、1.0.1 の仕様に準拠しています。"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Author_Group.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Author_Group.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,23 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Book_Info.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Book_Info.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,50 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#, fuzzy, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide CP04"
+msgstr "JBoss トランザクション JTA プログラマーガイド"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "JBoss Enterprise Application Platform 4.3 向け"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+"本文書は、プログラマーの観点から見たトランザクション JTA について説明していま"
+"す。"
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr "ロゴ"
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Configuring_JBossJTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Configuring_JBossJTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Configuring_JBossJTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,144 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr "JBossJTA の設定"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:8
+#, no-c-format
+msgid "Configuring options"
+msgstr "設定オプション"
+
+#. Tag: para
+#: Configuring_JBossJTA.xml:9
+#, no-c-format
+msgid ""
+"The following table shows the configuration features, with default values "
+"shown in italics. For more detailed information, the relevant section "
+"numbers are provided."
+msgstr ""
+"設定オプションは以下の表の通りです。デフォルト値は斜字体で示されています。詳"
+"細は、関連セクション欄の記載を参照してください。"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:13
+#, no-c-format
+msgid "JBossJTA configuration options."
+msgstr "JBossJTA 設定オプション"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:17
+#, no-c-format
+msgid "Configuration Name"
+msgstr "設定名"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:20
+#, no-c-format
+msgid "Possibile Values"
+msgstr "可能な値"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:23
+#, no-c-format
+msgid "Relevant Section"
+msgstr "関連セクション"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:30
+#, no-c-format
+msgid "com.arjuna.ats.jta.supportSubtransactions"
+msgstr "com.arjuna.ats.jta.supportSubtransactions"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr "YES/NO"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr "com.arjuna.ats.jta.jtaTMImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:43
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr "com.arjuna.ats.jta.jtaUTImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:53
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr "com.arjuna.ats.jta.xaBackoffPeriod"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr "com.arjuna.ats.jdbc.isolationLevel"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr "JDBC 分離レベルがサポートされる値"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr "true/false"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr "第 3 章"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Examples.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Examples.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Examples.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,826 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr "用例"
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr "JDBC の例"
+
+#. Tag: para
+#: Examples.xml:9
+#, no-c-format
+msgid ""
+"The following code illustrates many of the points described above (note that "
+"for simplicity, much error checking code has been remove). This example "
+"assumes that you are using the transactional JDBC driver provided with "
+"JBossTS. For details about how to configure and use this driver see the "
+"previous Chapter."
+msgstr ""
+"次のコードは前に説明した多くのポイントを表しています（注意：簡素化するため、"
+"エラー確認コードの多くは省略されています）。この例は、JBossTS で提供されるト"
+"ランザクション JDBC ドライバを使用することを前提としています。設定方法やドラ"
+"イバの使用方法の詳細は、前の章をご覧ください。"
+
+#. Tag: screen
+#: Examples.xml:12
+#, no-c-format
+msgid ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+msgstr ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+
+#. Tag: title
+#: Examples.xml:16
+#, no-c-format
+msgid "Failure recovery example"
+msgstr "障害リカバリの例"
+
+#. Tag: para
+#: Examples.xml:17
+#, no-c-format
+msgid ""
+"This class implements the <interfacename>XAResourceRecovery</interfacename> "
+"interface for <code>XAResources</code>. The parameter supplied in "
+"setParameters can contain arbitrary information necessary to initialize the "
+"class once created. In this instance it contains the name of the property "
+"file in which the db connection information is specified, as well as the "
+"number of connections that this file contains information on (separated "
+"by ;)."
+msgstr ""
+"このクラスは、<code>XAResources</code> の <interfacename>XAResourceRecovery</"
+"interfacename> を実装します。setParameters で提供されるパラメータは、作成後に"
+"クラスを初期化するために必要な任意の情報を含むことができます。このインスタン"
+"スでは、db 接続の情報が指定されるプロパティファイルの名前と、このファイルが情"
+"報を格納する接続数（; で区切られる）が含まれています。"
+
+#. Tag: para
+#: Examples.xml:21
+#, no-c-format
+msgid ""
+"This is only an <emphasis>example</emphasis> of the sorts of things an "
+"<code>XAResourceRecovery</code> implementer could do. This implementation "
+"uses a property file that is assumed to contain sufficient information to "
+"recreate connections used during the normal run of an application so that we "
+"can perform recovery on them. It is not recommended that information such as "
+"user name and password appear in such a raw text format as it opens up a "
+"potential security hole."
+msgstr ""
+"これは、<code>XAResourceRecovery</code> インプリメンタで実現できる例の 1 つで"
+"す。この実装はプロパティファイルを使用しますが、そのプロパティファイルはアプ"
+"リケーションの実行中に使用される接続を再度作成するために必要な情報を格納する"
+"ことを前提とします。そのため、接続に対してリカバリを実行することができます。"
+"ユーザー名やパスワードなどの情報を生のテキスト形式で表示することは、セキュリ"
+"ティーホールを生み出すことになるため推奨しません。"
+
+#. Tag: para
+#: Examples.xml:25
+#, no-c-format
+msgid ""
+"The db parameters specified in the property file are assumed to be in the "
+"format:"
+msgstr ""
+"プロパティファイルに指定される db パラメータは次のフォーマットであることを仮"
+"定します："
+
+#. Tag: para
+#: Examples.xml:30
+#, no-c-format
+msgid "DB_x_DatabaseURL="
+msgstr "DB_x_DatabaseURL="
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr "DB_x_DatabaseUser="
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr "DB_x_DatabasePassword="
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr "DB_x_DatabaseDynamicClass="
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr "x は接続情報の数に置き換えます。"
+
+#. Tag: para
+#: Examples.xml:54
+#, no-c-format
+msgid ""
+"Some error handling code has been removed from this text for ease of "
+"readability purposes."
+msgstr "読みやすくするため、エラー処理コードの一部は省略されています。"
+
+#. Tag: screen
+#: Examples.xml:58
+#, no-c-format
+msgid ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+msgstr ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+
+#. Tag: para
+#: Examples.xml:59
+#, no-c-format
+msgid ""
+"The class <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> may be used to create a new connection "
+"to the database using the same parameters that were used to create the "
+"initial connection."
+msgstr ""
+"<classname>com.arjuna.ats.internal.jdbc.recovery.JDBC2RecoveryConnection</"
+"classname> クラスを使用すると、初期接続の作成に使用されたパラメータを使用して"
+"データベースへの新しい接続を作成することができます。"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
===================================================================
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/JDBC_and_Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/JDBC_and_Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/JDBC_and_Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,978 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr "JDBC とトランザクション"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr "トランザクション JDBC ドライバの使用"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:9
+#, no-c-format
+msgid ""
+"JBossJTA supports the construction of both local and distributed "
+"transactional applications which access databases using the JDBC 2.0 APIs. "
+"JDBC 2.0 supports two-phase commit of transactions, and is similar to the XA "
+"X/Open standard. The JDBC 2.0 support is found in the com.arjuna.ats.jdbc "
+"package."
+msgstr ""
+"JBossJTA は、JDBC 2.0 API を使用してデータベースにアクセスするローカルおよび"
+"分散トランザクションアプリケーションの構成をサポートします。JDBC 2.0 は、トラ"
+"ンザクションの 2 フェーズコミットをサポートし、XA X/Open と似ています。JDBC "
+"2.0 のサポートは、com.arjuna.ats.jdbc パッケージにあります。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:12
+#, no-c-format
+msgid ""
+"The JDBC 2.0 support has been tested with the following drivers and "
+"databases:"
+msgstr ""
+"JDBC 2.0 のサポートは、次のドライバとデータベースによってテスト済みです："
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr "Oracle 8.1.6/8.1.7、9i、10g thin ドライバ"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr "MS SQL Server 2000 ネイティブドライバ"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:27
+#, no-c-format
+msgid "In the past we have qualified against:"
+msgstr "過去に確認されたドライバとデータベースは次の通りです："
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:32
+#, no-c-format
+msgid "Merant’s Sequelink 5.1 with Oracle 8.1.6"
+msgstr "Merant Sequelink 5.1 と Oracle 8.1.6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr "Cloudscape 3.6 と Cloudscape 独自のデータベース"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:42
+#, no-c-format
+msgid ""
+"However, these drivers and databases are no longer part of our supported "
+"platforms. They may continue to work with JBossTS, but we cannot make that "
+"guarantee."
+msgstr ""
+"上記のドライバやデータベースは、現在プラットフォームとしてサポートされておら"
+"ず、JBossTS で動作するかは保証できません。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:46
+#, no-c-format
+msgid "Managing transactions"
+msgstr "トランザクションの管理"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:47
+#, no-c-format
+msgid ""
+"JBossJTA must be able to associate work performed on a JDBC connection with "
+"a specific transaction. Therefore, implicit transaction propagation and/or "
+"indirect transaction management must be used by applications, i.e., for each "
+"JDBC connection it must be possible for JBossJTA to determine the invoking "
+"thread’s current transaction context."
+msgstr ""
+"JBossJTA は、JDBC 接続で実行された作業を特定のトランザクションに関連付けでき"
+"なければなりません。そのため、暗黙的なトランザクション伝搬や間接的なトランザ"
+"クション管理はアプリケーションによって使用されなければなりません（例：各 "
+"JDBC 接続に対し、JBossJTA は呼び出しスレッドの現トランザクションコンテキスト"
+"を判断できなければなりません）。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:52
+#, no-c-format
+msgid "Restrictions"
+msgstr "制限"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:53
+#, no-c-format
+msgid ""
+"The following restrictions are imposed by limitations in the JDBC "
+"specifications and by JBossJTA to ensure that transactional interactions "
+"with JDBC databases can be correctly managed:"
+msgstr ""
+"JDBC データベースとのトランザクション対話が正しく管理されるようにするため、"
+"JDBC の仕様および JBossJTA の制限によって以下が制限されます："
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:57
+#, no-c-format
+msgid ""
+"Nested transactions are not supported by JDBC 2.0. If an attempt is made to "
+"use a JDBC connection within a subtransaction, JBossJTA will throw a "
+"suitable exception and no work will be allowed on that connection. However, "
+"if you wish to have nested transactions, then you can set the <property>com."
+"arjuna.ats.jta.supportSubtransactions</property> property to YES."
+msgstr ""
+"JDBC 2.0 はネストされたトランザクションをサポートしません。サブトランザクショ"
+"ン内で JDBC 接続の使用を試みると、JBossJTA は適切な例外をスローし、その接続で"
+"の作業を許可しません。しかし、ネストされたトランザクションが必要な場合は、"
+"<property>com.arjuna.ats.jta.supportSubtransactions</property> プロパティを "
+"YES に設定します。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:63
+#, no-c-format
+msgid "Transactional drivers"
+msgstr "トランザクションドライバ"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:64
+#, no-c-format
+msgid ""
+"The JBossJTA approach to incorporating JDBC connections within transactions "
+"is to provide transactional JDBC drivers through which all interactions "
+"occur. These drivers intercept all invocations and ensure that they are "
+"registered with, and driven by, appropriate transactions. There is a single "
+"type of transactional driver through which any JDBC driver can be driven; "
+"obviously if the database is not transactional then ACID properties cannot "
+"be guaranteed. This driver is <code>com.arjuna.ats.jdbc.TransactionalDriver</"
+"code>, which implements the <interfacename>java.sql.Driver</interfacename> "
+"interface."
+msgstr ""
+"JBoss JTA は、トランザクション内で JDBC 接続を取り込むため、すべての対話が発"
+"生するトランザクション JDBC ドライバを提供します。これらのドライバはすべての"
+"呼び出しをインターセプトし、適切なトランザクションへ登録され、適切なトランザ"
+"クションによって実行されるようにします。すべての JDBC ドライバが実行される単"
+"一のトランザクションドライバがありますが、トランザクションのないデータベース"
+"の場合、ACID プロパティは保証されません。このドライバは <code>com.arjuna.ats."
+"jdbc.TransactionalDriver</code> で、<interfacename>java.sql.Driver</"
+"interfacename> インターフェイスを実装します。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:68
+#, no-c-format
+msgid "Loading drivers"
+msgstr "ロードするドライバ"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:69
+#, no-c-format
+msgid ""
+"The driver may be directly instantiated and used within an application. For "
+"example:"
+msgstr ""
+"ドライバは直接インスタンス化され、アプリケーション内で使用されます。例は次の"
+"通りです："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:73
+#, no-c-format
+msgid "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+msgstr "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:74
+#, no-c-format
+msgid ""
+"They can be registered with the JDBC driver manager (<code>java.sql."
+"DriverManager</code>) by adding them to the Java system properties. The "
+"<property>jdbc.drivers</property> property contains a list of driver class "
+"names, separated by colons, that are loaded by the JDBC driver manager when "
+"it is initialized."
+msgstr ""
+"これらのドライバは、Java システムプロパティに追加することで JDBC ドライバマ"
+"ネージャ (<code>java.sql.DriverManager</code>) に登録できます。"
+"<property>jdbc.drivers</property> プロパティには、初期化の際に JDBC ドライバ"
+"によってロードされるドライバクラス名のコンマ区切りのリストが含まれています。"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:77
+#, no-c-format
+msgid ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+msgstr ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:78
+#, no-c-format
+msgid ""
+"Alternatively, the <methodname>Class.forName()</methodname> method may be "
+"used to load the driver or drivers:"
+msgstr ""
+"<methodname>Class.forName()</methodname> メソッドを使用してドライバをロードす"
+"ることもできます："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:82
+#, no-c-format
+msgid ""
+"Calling <methodname>Class.forName()</methodname> will automatically register "
+"the driver with the JDBC driver manager. It is also possible to explicitly "
+"create an instance of the JDBC driver:"
+msgstr ""
+"<methodname>Class.forName()</methodname> が呼び出されると、自動的にドライバ"
+"が JDBC ドライバマネージャに登録されます。JDBC ドライバのインスタンスを明示的"
+"に作成することも可能です："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:85
+#, no-c-format
+msgid ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+msgstr ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:86
+#, no-c-format
+msgid ""
+"When you have loaded a driver, it is available for making a connection with "
+"a DBMS."
+msgstr ""
+"ドライバをロードした後、ドライバを使用して DBMS への接続を確立できます。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:92
+#, no-c-format
+msgid "Connections"
+msgstr "接続"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:93
+#, no-c-format
+msgid ""
+"In this section we shall discuss the notion of transactional JDBC "
+"connections, how they are managed within JBossJTA and the implications on "
+"using them within an application."
+msgstr ""
+"ここでは、トランザクション JDBC 接続の概念や JBossJTA 内での管理方法、アプリ"
+"ケーション内で使用するための実装について説明します。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:97
+#, no-c-format
+msgid "Making the connection"
+msgstr "接続の確立"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:98
+#, no-c-format
+msgid ""
+"Because JDBC connectivity in JBossJTA works by simply providing a new JDBC "
+"driver, application code can remain relatively the same to that when not "
+"using transactions. Typically, the application programmer need only start "
+"and terminate transactions."
+msgstr ""
+"新しい JDBC ドライバを提供するだけで JBossJTA における JDBC の接続性を維持で"
+"きるため、アプリケーションコードはトランザクションを使用しない場合とあまり変"
+"わりません。通常、アプリケーションプログラマにとって必要なことは、トランザク"
+"ションの開始および終了のみになります。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr "JDBC 2.0"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:104
+#, no-c-format
+msgid ""
+"Before describing the JDBC 2.0 support it is necessary to mention that the "
+"following properties can be set and passed to the JBossJTA driver (they are "
+"all located in the <classname>com.arjuna.ats.jdbc.TransactionalDriver</"
+"classname> class):"
+msgstr ""
+"JDBC 2.0 サポートについて説明する前に、プロパティについて説明しなければなりま"
+"せん。設定し、JBossJTA ドライバに渡すことができるプロパティは次の通りです (す"
+"べて <classname>com.arjuna.ats.jdbc.TransactionalDriver</classname> クラスに"
+"あります):"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:110
+#, no-c-format
+msgid ""
+"<property>userName</property>: the user name to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>userName</property>: データベースに接続する際に使用するユーザー名。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:115
+#, no-c-format
+msgid ""
+"<property>password</property>: the password to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>password</property>: データベースに接続するために使用するパスワー"
+"ド。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:120
+#, no-c-format
+msgid ""
+"<property>createDb</property>: if set to true, the driver will attempt to "
+"create the database when it connects. This may not be supported by all JDBC "
+"2.0 implementations."
+msgstr ""
+"<property>createDb</property>: true に設定された場合、接続の際にドライバが"
+"データベースを作成します。このプロパティをサポートしていない JDBC 2.0 実装も"
+"あります。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:125
+#, no-c-format
+msgid ""
+"<property>dynamicClass</property>: this specifies a class to instantiate to "
+"connect to the database, rather than using JNDI."
+msgstr ""
+"<property>dynamicClass</property>: JNDI を使用する代わりに、データベースに接"
+"続するためインスタンス化するクラスを指定します。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr "XADataSources"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:132
+#, no-c-format
+msgid ""
+"JDBC 2.0 connections are created from appropriate DataSources. Those "
+"connections which must participate within distributed transactions are "
+"obtained from <code>XADataSources</code>. Therefore, when using a JDBC 2.0 "
+"driver, JBossJTA will use the appropriate DataSource whenever a connection "
+"to the database is made. It will then obtain <code>XAResources</code> and "
+"register them with the transaction via the JTA interfaces. It is these "
+"<code>XAResources</code> which the transaction service will use when the "
+"transaction terminates in order to drive the database to either commit or "
+"rollback the changes made via the JDBC connection."
+msgstr ""
+"JDBC 2.0 接続は適切な DataSources より作成されます。分散トランザクション内で"
+"参加しなければならない JDBC 2.0 接続は、<code>XADataSources</code> より取得で"
+"きます。よって、JDBC 2.0 ドライバを使用している場合、データベースへの接続が確"
+"立される度に JBossJTA は適切な DataSource を使用します。その後、"
+"<code>XAResources</code> を取得し、JTA インターフェイスより取得した "
+"<code>XAResources</code> をトランザクションへ登録します。JDBC 接続を介した変"
+"更をデータベースがコミットまたはロールバックするためトランザクションが終了す"
+"ると、トランザクションサービスは <code>XAResources</code> を使用します。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:136
+#, no-c-format
+msgid ""
+"There are two ways in which the JBossJTA JDBC 2.0 support can obtain "
+"<code>XADataSources</code>. These will be explained in the following "
+"sections. Note, for simplicity we shall assume that the JDBC 2.0 driver is "
+"instantiated directly by the application."
+msgstr ""
+"JBossJTA JDBC 2.0 サポートが <code>XADataSources</code> を取得する方法は 2 つ"
+"ありますが、後の項で説明します。簡素化するため、JDBC 2.0 ドライバはアプリケー"
+"ションによって直接インスタンス化されることを前提としていますので注意してくだ"
+"さい。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr "Java Naming and Directory Interface (JNDI)"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:141
+#, no-c-format
+msgid ""
+"In order to allow a JDBC driver to use arbitrary DataSources without having "
+"to know specific details about their implementations, DataSources are "
+"typically obtained from JNDI. A specific (XA)DataSource can be created and "
+"registered with an appropriate JNDI implementation, and the application (or "
+"JDBC driver) can later bind to and use it. Since JNDI only allows the "
+"application to see the (XA)DataSource as an instance of the interface (for "
+"example, <property>javax.sql.XADataSource</property>) rather than as an "
+"instance of the implementation class (for example, <property>com.mydb."
+"myXADataSource</property>), the application is not tied at build time to "
+"only use a specific (XA)DataSource implementation."
+msgstr ""
+"JDBC ドライバが実装の詳細を認識しなくても任意の DataSources を使用できるよう"
+"にするため、DataSources は通常 JNDI より取得されます。適切な JNDI 実装で特定"
+"の (XA)DataSource の作成や登録が行えます。また、アプリケーション（または "
+"JDBC ドライバ）は後でバインドしたり使用することができます。JNDI では、アプリ"
+"ケーションは (XA)DataSource を実装クラスのインスタンス (例：<property>com."
+"mydb.myXADataSource</property>) としてではなく、インターフェイスのインスタン"
+"ス (例：<property>javax.sql.XADataSource</property>) としてのみ見なすため、ア"
+"プリケーションはビルド時に拘束されず特定の (XA)DataSource 実装のみを使用でき"
+"ます。 "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:145
+#, no-c-format
+msgid ""
+"To get the <classname>TransactionalDriver</classname> class to use a JNDI "
+"registered <code>XADataSource</code> it is first necessary to create the "
+"<code>XADataSource</code> instance and store it in an appropriate JNDI "
+"implementation. Details of how to do this can be found in the JDBC 2.0 "
+"tutorial available at JavaSoft. An example is show below:"
+msgstr ""
+"<classname>TransactionalDriver</classname> クラスを取得して、JNDI に登録され"
+"た <code>XADataSource</code> を使用するには、<code>XADataSource</code> インス"
+"タンスを作成し、適切な JNDI 実装に保存する必要があります。この詳細について"
+"は、JavaSoft の JDBC 2.0 チュートリアルを参照してください。例は次の通りです。"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:148
+#, no-c-format
+msgid ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+msgstr ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:149
+#, no-c-format
+msgid ""
+"Where the <property>Context.INITIAL_CONTEXT_FACTORY</property> property is "
+"the JNDI way of specifying the type of JNDI implementation to use."
+msgstr ""
+"JNDI では <property>Context.INITIAL_CONTEXT_FACTORY</property> プロパティに使"
+"用する JNDI 実装のタイプを指定します。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:152
+#, no-c-format
+msgid ""
+"Then the application must pass an appropriate connection URL to the JDBC 2.0 "
+"driver:"
+msgstr ""
+"アプリケーションは適切な接続 URL を JDBC 2.0 ドライバに渡さなければなりませ"
+"ん："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:155
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:156
+#, no-c-format
+msgid ""
+"The JNDI URL must be pre-pended with jdbc:arjuna: in order for the "
+"<code>ArjunaJDBC2Driver</code> to recognise that the DataSource must "
+"participate within transactions and be driven accordingly."
+msgstr ""
+"DataSource はトランザクション内で参加し、それに応じて実行されなければならない"
+"ことを <code>ArjunaJDBC2Driver</code> に認識させるため、JNDI のURL の先頭に "
+"jdbc:arjuna: を追加しなければなりません。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:160
+#, no-c-format
+msgid "Dynamic class instantiation"
+msgstr "動的なクラスのインスタンス化"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:161
+#, no-c-format
+msgid ""
+"Many JDBC 2.0 implementations provide proprietary implementations of "
+"<interfacename>XADataSources</interfacename> that provide non-standard "
+"extensions to the specification. In order to allow the application to remain "
+"isolated from the actual JDBC 2.0 implementation it is using and yet "
+"continue to be able to use these extensions, JBossJTA hides the details of "
+"these proprietary implementations using dynamic class instantiation. In "
+"addition, the use of JNDI is not required when using this mechanism because "
+"the actual implementation of the <interfacename>XADataSource</interfacename> "
+"will be directly instantiated, albeit in a manner which will not tie an "
+"application or driver to a specific implementation. JBossJTA therefore has "
+"several classes which are for specific JDBC 2.0 implementations, and these "
+"can be selected at runtime by the application setting the "
+"<property>dynamicClass</property> property appropriately:"
+msgstr ""
+"多くの JDBC 2.0 実装が非標準の拡張を仕様に提供する "
+"<interfacename>XADataSources</interfacename> のプロプリエタリな実装を提供して"
+"います。使用している実際の JDBC 2.0 実装からアプリケーションを分離しながら、"
+"拡張を使用できるようにするため、JBossJTA は動的クラスのインスタンス化を使用"
+"し、プロプラエタリ実装の詳細を隠します。また、特定の実装にアプリケーションや"
+"ドライバを拘束することなく <interfacename>XADataSource</interfacename> の実装"
+"は直接インスタンス化されるため、このメカニズムを使用する場合は JNDI を使用す"
+"る必要はありません。よって、JBossJTA は JDBC 2.0 実装に固有するクラスを複数"
+"持っており、これらのクラスは <property>dynamicClass</property> プロパティを適"
+"切に設定するアプリケーションによってランタイム時に選択することができます："
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:166
+#, no-c-format
+msgid "Dynamic Class property values for specific databases"
+msgstr "特定データベースの Dynamic Class プロパティ"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:170
+#, no-c-format
+msgid "Database Type"
+msgstr "データベースのタイプ"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:173
+#, no-c-format
+msgid "Property Name"
+msgstr "プロパティ名"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:180
+#, no-c-format
+msgid "Cloudscape 3.6"
+msgstr "Cloudscape 3.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr "Sequelink 5.1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr "Oracle 8.1.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:207
+#, no-c-format
+msgid ""
+"As mentioned earlier, JBossTS no longer supports Cloudscape or Sequelink as "
+"part of the qualified drivers. Furthermore, we recommend using JNDI to "
+"obtain JDBC classes rather than the direct method described here."
+msgstr ""
+"前述の通り、JBossTS は現在 Cloudscape や Sequelink を認定ドライバとしてサポー"
+"トしていません。また、ここで説明する直接的なメソッドではなく、JNDI を使用し"
+"て JDBC クラスを取得することを推奨します。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:211
+#, no-c-format
+msgid ""
+"The application code must specify which dynamic class the "
+"<code>TransactionalDriver</code> should instantiate when setting up the "
+"connection:"
+msgstr ""
+"アプリケーションは接続を設定する際に <code>TransactionalDriver</code> がイン"
+"スタンス化する動的クラスを指定しなければなりません："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:214
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:216
+#, no-c-format
+msgid "Using the connection"
+msgstr "接続の使用"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:217
+#, no-c-format
+msgid ""
+"Once the connection has been established (for example, using the "
+"<methodname>java.sql.DriverManager.getConnection</methodname> method), all "
+"operations on the connection will be monitored by JBossJTA. Note, it is not "
+"necessary to use the transactional connection within transactions. If a "
+"transaction is not present when the connection is used, then operations will "
+"be performed directly on the database."
+msgstr ""
+"接続が確立されると (<methodname>java.sql.DriverManager.getConnection</"
+"methodname> メソッドなどを使用して)、接続上のすべての操作が JBossJTA によって"
+"監視されます。トランザクション内でトランザクション接続を使用する必要はありま"
+"せん。接続を使用する際にトランザクションが存在しない場合、操作は直接データ"
+"ベース上で実行されます。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr "JDBC はサブトランザクションをサポートしません。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:226
+#, no-c-format
+msgid ""
+"Transaction timeouts can be used to automatically terminate transactions "
+"should the connection not be terminated within an appropriate period."
+msgstr ""
+"接続が適切な時間内に終了しない場合、トランザクションタイムアウトを使用して自"
+"動的にトランザクションを終了することができます。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:229
+#, no-c-format
+msgid ""
+"JBossJTA connections can be used within multiple different transactions "
+"simultaneously, for instance, different threads, with different notions of "
+"the current transaction, may use the same JDBC connection. JBossJTA does "
+"connection pooling for each transaction within the JDBC connection. So, "
+"although multiple threads may use the same instance of the JDBC connection, "
+"internally this may be using a different connection instance per "
+"transaction. With the exception of close, all operations performed on the "
+"connection at the application level will only be performed on this "
+"transaction-specific connection."
+msgstr ""
+"JBossJTA 接続は、複数の異なるトランザクション内で同時に使用することができま"
+"す。例えば、現トランザクションの異なる概念を持つ複数のスレッドが同じ JDBC 接"
+"続を使用することができます。JBossJTA は JDBC 接続内で各トランザクションに対し"
+"て接続プーリングを実行します。そのため、複数のスレッドが JDBC 接続の同じイン"
+"スタンスを使用しても、内部的にはトランザクション毎に異なる接続インスタンスを"
+"使用することができます。アプリケーションレベルの接続上で実行される close 以外"
+"の操作は、このトランザクション固有の接続上でのみ実行できます。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:232
+#, no-c-format
+msgid ""
+"JBossJTA will automatically register the JDBC driver connection with the "
+"transaction via an appropriate resource . When the transaction terminates, "
+"this resource will be responsible for either committing or rolling back any "
+"changes made to the underlying database via appropriate calls on the JDBC "
+"driver."
+msgstr ""
+"JBossJTA は適切なリソースを介して自動的に JDBC ドライバ接続をトランザクション"
+"に登録します。トランザクションが終了すると、このリソースは JDBC ドライバ上で"
+"適切な呼び出しを行い、基礎データベースの変更をコミットまたはロールバックしま"
+"す。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:235
+#, no-c-format
+msgid ""
+"Once created, the driver and any connection can be used in the same way as "
+"any other JDBC driver or connection."
+msgstr ""
+"JDBC ドライバや接続は、作成後に他の JDBC ドライバや接続と同じように使用できま"
+"す。"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:238
+#, no-c-format
+msgid ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+msgstr ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:240
+#, no-c-format
+msgid "Connection pooling"
+msgstr "接続プーリング"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:241
+#, no-c-format
+msgid ""
+"For each user name and password, JBossJTA will maintain a single instance of "
+"each connection for as long as that connection is in use. Subsequent "
+"requests for the same connection will get a reference to the originally "
+"created connection, rather than a new instance. Attempts to close the "
+"connection are allowed, but the connection will only actually be closed when "
+"all users (including transactions) have either finished with the connection, "
+"or issued close calls."
+msgstr ""
+"JBossJTA は、接続が使用中である間、各ユーザー名およびパスワードに対してその接"
+"続の単一のインスタンスを維持します。同じ接続に対して後続する要求があった場"
+"合、新しいインスタンスではなく、最初に作成された接続の参照を取得します。接続"
+"の終了を試みることはできますが、すべてのユーザー（トランザクションを含む）が"
+"接続を終了した場合と、close の呼び出しを実行した場合のみ実際に接続が終了しま"
+"す。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:246
+#, no-c-format
+msgid "Reusing connections"
+msgstr "接続の再使用"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:247
+#, no-c-format
+msgid ""
+"Some JDBC drivers allow the reuse of a connection for multiple different "
+"transactions once a given transaction has completed. Unfortunately this is "
+"not a common feature, and other drivers require a new connection to be "
+"obtained for each new transaction. By default, the JBossJTA transactional "
+"driver will always obtain a new connection for each new transaction. "
+"However, if an existing connection is available and is currently unused, it "
+"is possible to make JBossJTA reuse this connection. In order to do this, the "
+"reuseconnection=true option must be specified on the JDBC URL. For example:"
+msgstr ""
+"JDBC ドライバによっては、トランザクションが終了した後、複数の異なるトランザク"
+"ションに対する接続が再使用できるものがあります。この機能は一般的ではありませ"
+"んが、この機能がないドライバは新しいトランザクションに対して新しい接続を取得"
+"する必要があります。デフォルトでは、JBossJTA トランザクションドライバは常に新"
+"しいトランザクションに対して新しい接続を取得しますが、現在使用されていない既"
+"存の接続がある場合に再使用するよう指定できます。接続の再使用を有効にするに"
+"は、reuseconnection=true オプションを JDBC URL で指定します。例は次の通りで"
+"す。"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+"jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:253
+#, no-c-format
+msgid "Terminating the transaction"
+msgstr "トランザクションの終了"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:254
+#, no-c-format
+msgid ""
+"Whenever a transaction terminates (either explicitly by the application "
+"programmer, or implicitly when any associated transaction timeout expires) "
+"that has a JDBC connection registered with it, JBossJTA will drive the "
+"database (via the JDBC driver) to either commit or roll back any changes "
+"made to it. This happens transparently to the application."
+msgstr ""
+"JDBC 接続が登録されたトランザクションが終了すると（アプリケーションプログラマ"
+"による明示的な終了または関連するトランザクションタイムアウトの満了による暗黙"
+"的な終了）、JBossJTA は JDBC ドライバを介してデータベースに変更をコミットまた"
+"はロールバックするよう指示します。この処理はアプリケーションに対して透過的に"
+"行われます。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr "AutoCommit"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:260
+#, no-c-format
+msgid ""
+"If <code>AutoCommit</code> of the <code>java.sql.Connection</code> is set to "
+"true for JDBC 1.0 then the execution of every SQL statement is a separate "
+"top-level transaction, and grouping multiple statements to be managed within "
+"a single OTS transaction is not possible. Therefore, JBossJTA will disable "
+"<code>AutoCommit</code> on JDBC 1.0 connections before they can be used. If "
+"auto commit is subsequently set to true by the application, JBossJTA will "
+"raise the <code>java.sql.SQLException</code>."
+msgstr ""
+"<code>java.sql.Connection</code> の <code>AutoCommit</code> が JDBC 1.0 に対"
+"して true に設定されている場合、各 SQL ステートメントの実行は個別の最上位トラ"
+"ンザクションとなるため、複数のステートメントをグループ化して単一の OTS トラン"
+"ザクション内で管理することはできなくなります。そのため、JBossJTA は JDBC 1.0 "
+"接続上の <code>AutoCommit</code> を使用前に無効にします。その後、アプリケー"
+"ションによって <code>AutoCommit</code> が true に設定されると、<code>java."
+"sql.SQLException</code> が発生します。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:265
+#, no-c-format
+msgid "Setting isolation levels"
+msgstr "分離レベルの設定"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:266
+#, no-c-format
+msgid ""
+"When using the JBossJTA JDBC driver, it may be necessary to set the "
+"underlying transaction isolation level on the XA connection. By default, "
+"this is set to <code>TRANSACTION_SERIALIZABLE</code>, but you may want to "
+"set this to something more appropriate for your application. In order to do "
+"this, set the <property>com.arjuna.ats.jdbc.isolationLevel</property> "
+"property to the appropriate isolation level in string form, for example, "
+"<code>TRANSACTION_READ_COMMITTED</code>, or "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+msgstr ""
+"JBossJTA の JDBC ドライバを使用する場合、XA 接続における基礎のトランザクショ"
+"ン分離レベルを設定する必要があります。デフォルトでは、"
+"<code>TRANSACTION_SERIALIZABLE</code> に設定されますが、アプリケーションに応"
+"じて設定を変更することができます。設定を変更するには、<property>com.arjuna."
+"ats.jdbc.isolationLevel</property> プロパティに "
+"<code>TRANSACTION_READ_COMMITTED</code> や "
+"<code>TRANSACTION_REPEATABLE_READ</code> など適切な分離レベルをストリング形式"
+"で指定します。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:271
+#, no-c-format
+msgid ""
+"At present this property applies to all XA connections created in the JVM."
+msgstr ""
+"現在、このプロパティは JVM 内に作成されたすべてのXA 接続に対して適応されま"
+"す。"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Preface.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Preface.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,23 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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 "はじめに"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Revision_History.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Revision_History.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,29 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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 "改訂履歴"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/The_Resource_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/The_Resource_Manager.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/The_Resource_Manager.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,915 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: The_Resource_Manager.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "テスト"
+
+#. Tag: para
+#: The_Resource_Manager.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "これはテスト文です"
+
+#. Tag: title
+#: The_Resource_Manager.xml:11
+#, no-c-format
+msgid "The XAResource Interface"
+msgstr "XAResource インターフェイス"
+
+#. Tag: para
+#: The_Resource_Manager.xml:12
+#, no-c-format
+msgid ""
+"Whereas some transaction specifications and systems define a generic "
+"resource which can be used to register arbitrary resources with a "
+"transaction, the JTA is much more XA specific. The <interfacename>javax."
+"transaction.xa.XAResource</interfacename> interface is a Java mapping of the "
+"<interfacename>XA</interfacename> interface. The <interfacename>XAResource</"
+"interfacename> interface defines the contract between a Resource Manager and "
+"a Transaction Manager in a distributed transaction processing environment. A "
+"resource adapter for a resource manager implements the "
+"<interfacename>XAResource</interfacename> interface to support association "
+"of a top-level transaction to a resource such as a relational database."
+msgstr ""
+"トランザクションの仕様やシステムによっては、任意のリソースをトランザクション"
+"へ登録するために使用する汎用リソースを定義するものもありますが、JTA はより "
+"XA に固有しています。<interfacename>javax.transaction.xa.XAResource</"
+"interfacename> インターフェイスは <interfacename>XA</interfacename> インター"
+"フェイスの Java マッピングです。<interfacename>XAResource</interfacename> イ"
+"ンターフェイスは、分散トランザクション処理環境における Resource Manager と "
+"Transaction Manager のコントラクトを定義します。リソースマネージャのリソース"
+"アダプタは、最上位トランザクションとリソース（例：リレーショナルデータベー"
+"ス）への関連付けをサポートするため、<interfacename>XAResource</"
+"interfacename> インターフェイスを実装します。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:15
+#, no-c-format
+msgid ""
+"The <interfacename>XAResource</interfacename> interface can be supported by "
+"any transactional resource adapter that is intended to be used in an "
+"environment where transactions are controlled by an external transaction "
+"manager, for example, a database management system. An application may "
+"access data through multiple database connections. Each database connection "
+"is associated with an <code>XAResource</code> object that serves as a proxy "
+"object to the underlying resource manager instance. The transaction manager "
+"obtains an <code>XAResource</code> for each resource manager participating "
+"in a top-level transaction. It uses the start method to associate the "
+"transaction with the resource, and it uses the end method to disassociate "
+"the transaction from the resource."
+msgstr ""
+"<interfacename>XAResource</interfacename> インターフェイスは、データベース管"
+"理システムなど外部トランザクションマネージャによってトランザクションが制御さ"
+"れる環境内で使用されるトランザクションリソースアダプタによってサポートされま"
+"す。アプリケーションは複数のデータベース接続よりデータにアクセスすることがで"
+"きます。各データベース接続は、基礎のリソースマネージャインスタンスへのプロキ"
+"シオブジェクトとなる <code>XAResource</code> オブジェクトへ関連付けられます。"
+"トランザクションマネージャは、最上位トランザクションに参加する各リソースマ"
+"ネージャに対して <code>XAResource</code> を取得します。start メソッドを使用し"
+"てトランザクションをリソースに関連付けし、end メソッドを使用してトランザク"
+"ションのリソースへの関連付けを解消します。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:18
+#, no-c-format
+msgid ""
+"The resource manager is responsible for associating the transaction with all "
+"work performed on its data between the start and end invocations. At "
+"transaction commit time, these transactional resource managers are informed "
+"by the transaction manager to prepare, commit, or rollback the transaction "
+"according to the two-phase commit protocol."
+msgstr ""
+"リソースマネージャは、start 呼び出しと end 呼び出しの間にデータで実行された全"
+"ての作業へトランザクションを関連付けます。トランザクションのコミット時に、2 "
+"フェーズコミットプロトコルに応じてトランザクションを prepare または commit、"
+"rollback するようトランザクションマネージャがトランザクションリソースマネー"
+"ジャに伝えます。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:21
+#, no-c-format
+msgid ""
+"In order to be better integrated with Java, the <interfacename>XAResource</"
+"interfacename> differs from the standard <interfacename>XA</interfacename> "
+"interface in the following ways:"
+msgstr ""
+"Java とより良く統合させるため、<interfacename>XAResource</interfacename> は次"
+"のような点で標準の <interfacename>XA</interfacename> インターフェイスとは異"
+"なっています："
+
+#. Tag: para
+#: The_Resource_Manager.xml:26
+#, no-c-format
+msgid ""
+"The resource manager initialization is done implicitly by the resource "
+"adapter when the resource (connection) is acquired. There is no "
+"<code>xa_open</code> equivalent."
+msgstr ""
+"リソース（接続）が取得されると、リソースアダプタによってリソースマネージャの"
+"初期化が暗黙的に行われます。<code>xa_open</code> と同等なものはありません。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:31
+#, no-c-format
+msgid ""
+"<code>Rmid</code> is not passed as an argument. Each <code>Rmid</code> is "
+"represented by a separate <code>XAResource</code> object."
+msgstr ""
+"<code>Rmid</code> は引数として渡されません。各 <code>Rmid</code> は個別の "
+"<code>XAResource</code> オブジェクトによって表されます。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:36
+#, no-c-format
+msgid ""
+"Asynchronous operations are not supported because Java supports multi-"
+"threaded processing and most databases do not support asynchronous "
+"operations."
+msgstr ""
+"Java はマルチスレッド処理をサポートし、ほとんどのデータベースは非同期操作をサ"
+"ポートしていないため、非同期操作はサポートされません。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:41
+#, no-c-format
+msgid ""
+"Error return values that are caused by the transaction manager’s improper "
+"handling of the <code>XAResource</code> object are mapped to Java exceptions "
+"via the <classname>XAException</classname> class."
+msgstr ""
+"トランザクションマネージャが <code>XAResource</code> オブジェクトを適切に処理"
+"しなかったため返されたエラー値は、<classname>XAException</classname> クラスを"
+"介して Java 例外にマップされます。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:46
+#, no-c-format
+msgid ""
+"The DTP concept of <emphasis>Thread of Control</emphasis> maps to all Java "
+"threads that are given access to the <code>XAResource</code> and "
+"<code>Connection</code> objects. For example, it is legal for two different "
+"threads to perform the start and end operations on the same "
+"<code>XAResource</code> object."
+msgstr ""
+"制御スレッドの DTP 概念は、<code>XAResource</code> オブジェクトおよび "
+"<code>Connection</code> オブジェクトにアクセスできるすべての Java スレッドを"
+"マップします。例えば、異なる 2 つのスレッドは、同じ <code>XAResource</code> "
+"オブジェクトで start および end 操作を実行できます。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr "拡張 XAResource 制御"
+
+#. Tag: para
+#: The_Resource_Manager.xml:53
+#, no-c-format
+msgid ""
+"By default, whenever an <code>XAResource</code> object is registered with a "
+"JTA compliant transaction service, you have no control over the order in "
+"which it will be invoked during the two-phase commit protocol, with respect "
+"to other <code>XAResource</code> objects. In JBossTS, however, there is "
+"support for controlling the order via the two interfaces <interfacename>com."
+"arjuna.ats.jta.resources.StartXAResource</interfacename> and "
+"<interfacename>com.arjuna.ats.jta.resources.EndXAResource</interfacename>. "
+"By inheriting your <code>XAResource</code> instance from either of these "
+"interfaces, you control whether an instance of your class will be invoked "
+"first or last, respectively."
+msgstr ""
+"デフォルトでは、<code>XAResource</code> オブジェクトが JTA 準拠のトランザク"
+"ションサービスに登録されると、2 フェーズコミットプロトコルの間に他の "
+"<code>XAResource</code> オブジェクトが呼び出される順番の制御はできません。し"
+"かし、JBossTS では <interfacename>com.arjuna.ats.jta.resources."
+"StartXAResource</interfacename> と <interfacename>com.arjuna.ats.jta."
+"resources.EndXAResource</interfacename> の 2 つのインターフェイスによってこの"
+"順番の制御をサポートしています。どちらかのインターフェイスから "
+"<code>XAResource</code> インスタンスを継承することで、クラスのインスタンスが"
+"最初または最後に呼び出されるかを制御します。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:58
+#, no-c-format
+msgid ""
+"Only one instance of each interface type may be registered with a specific "
+"transaction."
+msgstr ""
+"各インターフェイスタイプの 1 つのインスタンスのみを特定のトランザクションに登"
+"録することができます。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:62
+#, no-c-format
+msgid ""
+"In the TxCore manual we discussed the Last Resource Commit optimization "
+"(LRCO), whereby a single resource that is only one-phase aware (does not "
+"support prepare), can be enlisted with a transaction that is manipulating "
+"two-phase aware participants. This optimization is also supported within the "
+"JTA aspects of JBossTS."
+msgstr ""
+"TxCore マニュアルでは、最後のリソースコミットの最適化 (Last Resource Commit "
+"Optimization：LRCO) について説明しました。この最適化では、1 フェーズのみ対応"
+"する単一のリソース（prepare をサポートしない）を 2 フェーズに対応する参加者を"
+"操作するトランザクションへ参加させることができ、JBossTS の JTA アスペクト内で"
+"もサポートされます。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:65
+#, no-c-format
+msgid ""
+"In order to use the LRCO, your <interfacename>XAResource</interfacename> "
+"implementation must extend the <interfacename>com.arjuna.ats.jta.resources."
+"LastResourceCommitOptimisation</interfacename> marker interface (it provides "
+"no methods). When enlisting the resource via Transaction.enlistResource, "
+"JBossTS will ensure that only a single instance of this type of participant "
+"is used within each transaction. Your resource will be driven last in the "
+"commit protocol: no invocation of prepare will occur."
+msgstr ""
+"LRCO を使用するには、<interfacename>XAResource</interfacename> 実装が "
+"<interfacename>com.arjuna.ats.jta.resources.LastResourceCommitOptimisation</"
+"interfacename> マーカーインターフェイス（メソッドは提供しない）を拡張しなけれ"
+"ばなりません。Transaction.enlistResource を介してリソースを参加させる際、"
+"JBossTS は各トランザクション内でこのタイプの参加者の単一インスタンスのみが使"
+"用されるようにします。リソースはコミットプロトコルの最後に実行され、prepare "
+"は呼び出されません。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:69
+#, no-c-format
+msgid ""
+"By default an attempt to enlist more than one instance of a "
+"<classname>LastResourceCommitOptimisation</classname> class will fail and "
+"false will be returned from <methodname>Transaction.enlistResource</"
+"methodname>. This behaviour can be overridden by setting the <property>com."
+"arjuna.ats.jta.allowMultipleLastResources</property> to true. However, "
+"before doing so you should read the Section on enlisting multiple one-phase "
+"aware resources."
+msgstr ""
+"デフォルトでは、<classname>LastResourceCommitOptimisation</classname> クラス"
+"のインスタンスを複数参加させようとすると失敗し、<methodname>Transaction."
+"enlistResource</methodname> より false が返されます。この動作を変更するには、"
+"<property>com.arjuna.ats.jta.allowMultipleLastResources</property> を true に"
+"設定しますが、参加させる複数の 1 フェーズ対応リソースのSection を読んでから変"
+"更するようにしてください。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:73
+#, no-c-format
+msgid ""
+"In order to utilize the LRCO in a distributed environment, it is necessary "
+"to disable interposition support. It is still possible to use implicit "
+"context propagation."
+msgstr ""
+"LRCO を分散環境で使用するには、インターポジションのサポートを無効にする必要が"
+"ありますが、暗黙的なコンテキスト伝搬の使用は可能です。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:77
+#, no-c-format
+msgid "Enlisting multiple one-phase aware resources"
+msgstr "複数の 1 フェーズ対応リソースを参加させる"
+
+#. Tag: para
+#: The_Resource_Manager.xml:78
+#, no-c-format
+msgid ""
+"As discussed in the Transaction Core documentation, in order to guarantee "
+"consistency (atomicity) of outcome between multiple participants (resources) "
+"within the same transaction, the two-phase commit protocol is used with a "
+"durable transaction log. In the case of possessing a single one-phase aware "
+"resource, it is still possible to achieve an atomic (all of nothing) outcome "
+"across resources by utilizing the Last Resource Commit Optimization, as "
+"explained earlier."
+msgstr ""
+"Transaction Core 関連の文書で説明した通り、同じトランザクションにおける複数参"
+"加者（リソース）間の一貫性（原子性）を保証するため、2 フェーズコミットプロト"
+"コルは永続トランザクションログに使用されます。単一の 1 フェーズ対応リソースを"
+"処理する場合、前述のように LRCO を利用してリソース間で原子的な結果を実現する"
+"ことが可能です。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:82
+#, no-c-format
+msgid ""
+"However, there may be situations where multiple one-phase aware resources "
+"are enlisted within the same transaction. For example, a legacy database "
+"running within the same transaction as a legacy JMS implementation. In these "
+"situations it is not possible to achieve atomicity of transaction outcome "
+"across multiple resources because none of them enter the prepare (waiting "
+"for final outcome) state: they commit or rollback immediately when "
+"instructed by the transaction coordinator, without knowledge of other "
+"resource states and without any way of undoing should subsequent resources "
+"make a different choice. This can result in data corruption or heuristic "
+"outcomes."
+msgstr ""
+"複数の 1 フェーズ対応リソースが同じトランザクション内に参加する場合も考えられ"
+"ます。同じトランザクション内でレガシーな JMS 実装として稼働しているレガシーな"
+"データベースがその例です。このような場合、prepare 状態（最終結果待ち）になら"
+"ないため、複数のリソース間でトランザクションの結果の原子性を実現することがで"
+"きません。他のリソース状態を認識することなく、また継続のリソースが異なる選択"
+"をした場合でもそれを取り消すことなくトランザクションコーディネータの指示によ"
+"り即座にコミットまたはロールバックします。そのため、データの破損やヒューリス"
+"ティックな結果が発生することがあります。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:85
+#, no-c-format
+msgid "In these situations we recommend one of the following approaches:"
+msgstr "このような場合、以下のいづれかの方法を実行するよう推奨します："
+
+#. Tag: para
+#: The_Resource_Manager.xml:90
+#, no-c-format
+msgid ""
+"Wrap the resources in compensating transactions. See the Web Services "
+"transactions guides for further details."
+msgstr ""
+"補正トランザクション (compensating transactions) のリソースをラップします。詳"
+"細は、ウェブサービストランザクションガイドを参照してください。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:95
+#, no-c-format
+msgid "Migrate the legacy implementations to two-phase aware equivalents."
+msgstr "レガシーな実装を 2 フェーズ対応と同等なものに移行する。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:100
+#, no-c-format
+msgid ""
+"In the cases where neither of these options are viable, JBossTS does support "
+"the enlistment of multiple one-phase aware resources within the same "
+"transaction. In order to do this, see the section on the Last Resource "
+"Commit Optimization."
+msgstr ""
+"上記が実行可能でない場合、JBossTS は同じトランザクション内における複数の 1 "
+"フェース対応リソースの参加をサポートしません。これを実行するには、最後のリ"
+"ソースコミットの最適化（LRCO）を参照してください。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:104
+#, no-c-format
+msgid ""
+"Even when this support is enabled, JBossTS will issue warnings when it "
+"detects that the option has been enabled (\"You have chosen to enable "
+"multiple last resources in the transaction manager. This is transactionally "
+"unsafe and should not be relied upon.”) and when multiple one-phase "
+"resources are enlisted within the transaction (“This is transactionally "
+"unsafe and should not be relied on.”)."
+msgstr ""
+"サポートが有効な場合でも、このオプションが有効なっていることを JBossTS が探知"
+"すると警告を発行します (\"You have chosen to enable multiple last resources "
+"in the transaction manager. This is transactionally unsafe and should not be "
+"relied upon.”)。また、複数の 1 フェーズリソースがトランザクション内に参加して"
+"いる場合も警告を発行します (“This is transactionally unsafe and should not "
+"be relied on.”)。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:111
+#, no-c-format
+msgid "Opening a Resource Manager"
+msgstr "リソースマネージャを開く"
+
+#. Tag: para
+#: The_Resource_Manager.xml:112
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface requires that the "
+"transaction manager initialize a resource manager (xa_open) prior to any "
+"other xa_ calls. JTA requires initialization of a resource manager to be "
+"embedded within the resource adapter that represents the resource manager. "
+"The transaction manager does not need to know how to initialize a resource "
+"manager; it is only responsible for informing the resource manager about "
+"when to start and end work associated with a transaction and when to "
+"complete the transaction. The resource adapter is responsible for opening "
+"(initializing) the resource manager when the connection to the resource "
+"manager is established."
+msgstr ""
+"X/Open <interfacename>XA</interfacename> インターフェイスでは、トランザクショ"
+"ンマネージャが他の xa_ 呼び出しの前にリソースマネージャ (xa_open) を初期化す"
+"る必要があります。JTA では、リソースマネージャを示すリソースアダプタ内にリ"
+"ソースマネージャの初期化を組み込む必要があります。トランザクションマネージャ"
+"はリソースマネージャの初期化方法を知る必要はありません。トランザクションマ"
+"ネージャはトランザクションに関連付けられている作業をいつ開始し終了するか、い"
+"つトランザクションを完了するかをリソースマネージャに伝えます。リソースアダプ"
+"タは、リソースマネージャへの接続が確立された際にリソースマネージャを開きます"
+"（初期化します）。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:118
+#, no-c-format
+msgid "Closing a Resource Manager"
+msgstr "リソースマネージャを閉じる"
+
+#. Tag: para
+#: The_Resource_Manager.xml:119
+#, no-c-format
+msgid ""
+"A resource manager is closed by the resource adapter as a result of "
+"destroying the transactional resource. A transaction resource at the "
+"resource adapter level is comprised of two separate objects:"
+msgstr ""
+"トランザクションリソースが破損すると、リソースアダプタはリソースマネージャを"
+"閉じます。リソースアダプタレベルのトランザクションリソースは個別の 2 つのオブ"
+"ジェクトによって構成されます："
+
+#. Tag: para
+#: The_Resource_Manager.xml:124
+#, no-c-format
+msgid ""
+"An <code>XAResource</code> object that allows the transaction manager to "
+"start and end the transaction association with the resource in use and to "
+"coordinate transaction completion process."
+msgstr ""
+"<code>XAResource</code> オブジェクト：使用中リソースへのトランザクションの関"
+"連付けをトランザクションマネージャが開始および終了できるようにし、トランザク"
+"ション終了プロセスのコーディネートを可能にします。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:129
+#, no-c-format
+msgid ""
+"A connection object that allows the application to perform operations on the "
+"underlying resource (for example, JDBC operations on an RDBMS)."
+msgstr ""
+"接続オブジェクト：アプリケーションが基礎のリソース上で操作を実行できるように"
+"します（例：RDBMS 上の JDBC 操作）。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:134
+#, no-c-format
+msgid ""
+"Once opened, the resource manager is kept open until the resource is "
+"released (closed) explicitly. When the application invokes the connection’s "
+"close method, the resource adapter invalidates the connection object "
+"reference that was held by the application and notifies the application "
+"server about the close. The transaction manager should invoke the "
+"<methodname>XAResource.end</methodname> method to disassociate the "
+"transaction from that connection."
+msgstr ""
+"開いたリソースマネージャは、リソースが明示的にリリースされるまで（閉じるま"
+"で）開いた状態を維持します。アプリケーションが接続の close メソッドを呼び出す"
+"と、リソースアダプタはアプリケーションが保持する接続オブジェクトの参照を無効"
+"にし、アプリケーションサーバーに close について通知します。トランザクションマ"
+"ネージャは <methodname>XAResource.end</methodname> メソッドを呼び出し、トラン"
+"ザクションの接続への関連付けを解消します。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:137
+#, no-c-format
+msgid ""
+"The close notification allows the application server to perform any "
+"necessary cleanup work and to mark the physical XA connection as free for "
+"reuse, if connection pooling is in place."
+msgstr ""
+"close の通知により、アプリケーションサーバーは必要なクリーンアップ作業を行"
+"い、接続プーリングが有効な場合は物理 XA 接続を再使用できるようにします。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:143
+#, no-c-format
+msgid "Threads of control"
+msgstr "制御スレッド"
+
+#. Tag: para
+#: The_Resource_Manager.xml:144
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface specifies that the "
+"transaction association related xa calls must be invoked from the same "
+"thread context. This thread-of-control requirement is not applicable to the "
+"object-oriented component-based application run-time environment, in which "
+"application threads are dispatched dynamically at method invocation time. "
+"Different threads may be using the same connection resource to access the "
+"resource manager if the connection spans multiple method invocation. "
+"Depending on the implementation of the application server, different threads "
+"may be involved with the same <code>XAResource</code> object. The resource "
+"context and the transaction context may be operated independent of thread "
+"context. This means that it is possible for different threads to be invoking "
+"the start and end methods."
+msgstr ""
+"X/Open <interfacename>XA</interfacename> インターフェイスは、xa の呼び出しに"
+"関係するトランザクションの関連付けが同じスレッドコンテキストより呼び出される"
+"よう指定します。メソッドの呼び出し時にアプリケーションスレッドが動的にディス"
+"パッチされるオブジェクト指向のコンポーネントベースアプリケーションランタイム"
+"環境には、この制御スレッドの要件は適応されません。接続が複数のメソッドの呼び"
+"出しに及ぶ場合、異なるスレッドが同じ接続リソースを使用してリソースマネージャ"
+"にアクセスすることができます。アプリケーションサーバーの実装によっては、異な"
+"るスレッドが同じ <code>XAResource</code> オブジェクトに関与することがありま"
+"す。リソースコンテキストとトランザクションコンテキストは、スレッドコンテキス"
+"トから独立して操作できます。そのため、異なるスレッドによる start および end "
+"メソッドの呼び出しが可能です。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:147
+#, no-c-format
+msgid ""
+"If the application server allows multiple threads to use a single "
+"<code>XAResource</code> object and the associated connection to the resource "
+"manager, it is the responsibility of the application server to ensure that "
+"there is only one transaction context associated with the resource at any "
+"point of time. Thus the <interfacename>XAResource</interfacename> interface "
+"requires that the resource managers be able to support the two-phase commit "
+"protocol from any thread context."
+msgstr ""
+"アプリケーションサーバーが、複数スレッドによる単一の <code>XAResource</code> "
+"オブジェクトの使用やリソースマネージャへ関連付けられた接続の使用を許可する場"
+"合、常時 1 つのみのトランザクションコンテキストがリソースに関連付けられるよう"
+"にするのはアプリケーションサーバーの役目です。そのため、"
+"<interfacename>XAResource</interfacename> インターフェイスでは、リソースマ"
+"ネージャはスレッドコンテキストからの 2 フェーズコミットプロトコルをサポートで"
+"きなければなりません。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:153
+#, no-c-format
+msgid "Transaction association"
+msgstr "トランザクションの関連付け"
+
+#. Tag: para
+#: The_Resource_Manager.xml:154
+#, no-c-format
+msgid ""
+"Transactions are associated with a transactional resource via the start "
+"method, and disassociated from the resource via the <methodname>end</"
+"methodname> method. The resource adapter is responsible for internally "
+"maintaining an association between the resource connection object and the "
+"<code>XAResource</code> object. At any given time, a connection is "
+"associated with a single transaction, or it is not associated with any "
+"transaction at all. Because JTA does not support nested transactions it is "
+"an error for the start method to be invoked on a connection that is "
+"currently associated with a different transaction."
+msgstr ""
+"トランザクションは start メソッドにてトランザクションリソースへ関連付けられ、"
+"<methodname>end</methodname> メソッドにてリソースへの関連付けが解消されます。"
+"リソース接続オブジェクトと <code>XAResource</code> オブジェクトとの関連を内部"
+"的に維持するのはリソースアダプタです。接続は必ず単一のトランザクションに関連"
+"付けられている状態か、どのトランザクションにも関連付けられていない状態かのい"
+"づれかになります。JTA はネストされたトランザクションをサポートしないため、異"
+"なるトランザクションに関連付けられた接続で start メソッドが呼び出されるとエ"
+"ラーが発生します。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:157
+#, no-c-format
+msgid ""
+"Interleaving multiple transaction contexts using the same resource may be "
+"done by the transaction manager as long as start and end are invoked "
+"properly for each transaction context switch. Each time the resource is used "
+"with a different transaction, the method end must be invoked for the "
+"previous transaction that was associated with the resource, and start must "
+"be invoked for the current transaction context."
+msgstr ""
+"トランザクションマネージャにて同じリソースを使用して複数のトランザクションコ"
+"ンテキストをインターリーブすることができますが、各トランザクションコンテキス"
+"トスイッチに対して適切に start と end が呼び出されなければなりません。リソー"
+"スが異なるトランザクションによって使用される度に、そのリソースに関連付けられ"
+"ていた前のトランザクションに対しては end メソッド、現トランザクションコンテキ"
+"ストに対しては start メソッドが呼び出されなければなりません。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:163
+#, no-c-format
+msgid "Externally controlled connections"
+msgstr "外部で制御される接続"
+
+#. Tag: para
+#: The_Resource_Manager.xml:164
+#, no-c-format
+msgid ""
+"For transactional application whose transaction states are managed by an "
+"application server, its resources must also be managed by the application "
+"server so that transaction association is performed properly. If an "
+"application is associated with a transaction, it is an error for the "
+"application to perform transactional work through the connection without "
+"having the connection’s resource object already associated with the global "
+"transaction. The application server must ensure that the <code>XAResource</"
+"code> object in use is associated with the transaction. This is done by "
+"invoking the <methodname>Transaction.enlistResource</methodname> method."
+msgstr ""
+"トランザクションの状態がアプリケーションサーバーによって管理されるトランザク"
+"ションアプリケーションは、トランザクションの関連付けが適切に行われるようにす"
+"るため、そのリソースもアプリケーションサーバーによって管理されなければなりま"
+"せん。アプリケーションがトランザクションに関連付けられている場合、接続のリ"
+"ソースオブジェクトがグローバルトランザクションに関連付けられていない状態でア"
+"プリケーションが接続を介してトランザクション作業を実行するとエラーが発生しま"
+"す。アプリケーションサーバーは、使用中の <code>XAResource</code> オブジェクト"
+"がトランザクションに関連付けられていることを確認しなければなりません。これを"
+"実現するには、<methodname>Transaction.enlistResource</methodname> メソッドを"
+"呼び出します。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:167
+#, no-c-format
+msgid ""
+"If a server side transactional application retains its database connection "
+"across multiple client requests, the application server must ensure that "
+"before dispatching a client request to the application thread, the resource "
+"is enlisted with the application’s current transaction context. This implies "
+"that the application server manages the connection resource usage status "
+"across multiple method invocations."
+msgstr ""
+"サーバーサイドのトランザクションアプリケーションが複数のクライアント要求間で"
+"データベース接続を保持する場合、アプリケーションサーバーはクライアント要求を"
+"アプリケーションスレッドにディスパッチする前に、リソースがアプリケーションの"
+"現トランザクションコンテキストに参加していることを確認しなければなりません。"
+"これは、アプリケーションサーバーが複数のメソッド呼び出し間で接続リソースの使"
+"用状態を管理することを意味します。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:173
+#, no-c-format
+msgid "Resource sharing"
+msgstr "リソースの共有"
+
+#. Tag: para
+#: The_Resource_Manager.xml:174
+#, no-c-format
+msgid ""
+"When the same transactional resource is used to interleave multiple "
+"transactions, it is the responsibility of the application server to ensure "
+"that only one transaction is enlisted with the resource at any given time. "
+"To initiate the transaction commit process, the transaction manager is "
+"allowed to use any of the resource objects connected to the same resource "
+"manager instance. The resource object used for the two-phase commit protocol "
+"does not need to have been involved with the transaction being completed."
+msgstr ""
+"同じトランザクションリソースを使用して複数のトランザクションをインターリーブ"
+"する場合、アプリケーションサーバーによって常時 1 つのトランザクションのみがリ"
+"ソースに参加するようにします。トランザクションのコミットプロセスを起動するた"
+"め、トランザクションマネージャは同じリソースマネージャインスタンスに接続する"
+"リソースオブジェクトをすべて使用することができます。2 フェーズコミットプロト"
+"コルで使用されるリソースオブジェクトは、終了したトランザクションに関与してい"
+"なくても構いません。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:177
+#, no-c-format
+msgid ""
+"The resource adapter must be able to handle multiple threads invoking the "
+"<interfacename>XAResource</interfacename> methods concurrently for "
+"transaction commit processing. For example, with reference to the code "
+"below, suppose we have a transactional resource <code>r1</code>. Global "
+"transaction <code>xid1</code> was started and ended with <code>r1</code>. "
+"Then a different global transaction <code>xid2</code> is associated with "
+"<code>r1</code>. In the meanwhile, the transaction manager may start the two "
+"phase commit process for <code>xid1</code> using <code>r1</code> or any "
+"other transactional resource connected to the same resource manager. The "
+"resource adapter needs to allow the commit process to be executed while the "
+"resource is currently associated with a different global transaction."
+msgstr ""
+"リソースアダプタは、トランザクションコミットプロセスで "
+"<interfacename>XAResource</interfacename> メソッドを並行して呼び出す複数のス"
+"レッドに対応できなければなりません。例えば下記コードの場合、トランザクション"
+"リソース <code>r1</code> を持っていると、グローバルトランザクション "
+"<code>xid1</code> は <code>r1</code> で起動し終了します。そして別のグローバル"
+"トランザクションである <code>xid2</code>が <code>r1</code> に関連付けられま"
+"す。一方で、トランザクションマネージャは <code>r1</code> または同じリソースマ"
+"ネージャに接続する他のトランザクションリソースを使用して <code>xid1</code> に"
+"対し 2 フェーズコミットプロセスを開始します。リソースアダプタは、リソースが異"
+"なるグローバルトランザクションに関連付けられている間、コミットプロセスが実行"
+"できるようにしなければなりません。"
+
+#. Tag: screen
+#: The_Resource_Manager.xml:180
+#, no-c-format
+msgid ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+msgstr ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+
+#. Tag: title
+#: The_Resource_Manager.xml:184
+#, no-c-format
+msgid "Local and global transactions"
+msgstr "ローカルおよびグローバルトランザクション"
+
+#. Tag: para
+#: The_Resource_Manager.xml:185
+#, no-c-format
+msgid ""
+"The resource adapter must support the usage of both local and global "
+"transactions within the same transactional connection. Local transactions "
+"are transactions that are started and coordinated by the resource manager "
+"internally. The <interfacename>XAResource</interfacename> interface is not "
+"used for local transactions. When using the same connection to perform both "
+"local and global transactions, the following rules apply:"
+msgstr ""
+"リソースアダプタは、同じトランザクション接続内のローカルおよびグローバルトラ"
+"ンザクションの使用をサポートしなければなりません。ローカルトランザクションと"
+"は、リソースマネージャによって内部で起動およびコーディネートされるトランザク"
+"ションのことです。<interfacename>XAResource</interfacename> インターフェイス"
+"はローカルトランザクションには使用されません。同じ接続を使用してローカルおよ"
+"びグローバルトランザクションの両方を実行する場合、次のルールが適応されます。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:190
+#, no-c-format
+msgid ""
+"The local transaction must be committed (or rolled back) before starting a "
+"global transaction in the connection."
+msgstr ""
+"接続でグローバルトランザクションを開始する前にローカルトランザクションをコ"
+"ミット（またはロールバック）しなければなりません。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:195
+#, no-c-format
+msgid ""
+"The global transaction must be disassociated from the connection before any "
+"local transaction is started."
+msgstr ""
+"ローカルトランザクションを開始する前に、グローバルトランザクションの接続への"
+"関連付けを解消しなければなりません。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:203
+#, no-c-format
+msgid "Transaction timeouts"
+msgstr "トランザクションのタイムアウト"
+
+#. Tag: para
+#: The_Resource_Manager.xml:204
+#, no-c-format
+msgid ""
+"Timeout values can be associated with transactions in order to control their "
+"lifetime. If a transaction has not terminated (committed or rolled back) "
+"before the timeout value elapses, the transaction system will automatically "
+"roll it back. The <interfacename>XAResource</interfacename> interface "
+"supports a operation, which allows the timeout associated with the current "
+"transaction to be propagated to the resource manager and if supported, will "
+"override any default timeout associated with the resource manager. This can "
+"be useful when long running transactions may have lifetimes that would "
+"exceed the default and in which case, if the timeout were not altered, the "
+"resource manager would rollback before the transaction terminated and "
+"subsequently cause the transaction to roll back as well."
+msgstr ""
+"トランザクションの存続期間を制御するため、タイムアウト値をトランザクションに"
+"関連付けることができます。タイムアウト値の経過前にトランザクションが終了（コ"
+"ミットまたはロールバック）しない場合、トランザクションシステムは自動的にロー"
+"ルバックを実行します。<interfacename>XAResource</interfacename> インターフェ"
+"イスは、現トランザクションに関連付けられたタイムアウトをリソースマネージャに"
+"伝搬する操作をサポートします。また、サポートされている場合はリソースマネー"
+"ジャに関連付けられたデフォルトのタイムアウトを変更します。長時間実行している"
+"トランザクションの存続期間がデフォルトよりも長い場合、タイムアウトが変更され"
+"ないとトランザクションが終了する前にリソースマネージャがロールバックするた"
+"め、結果的にトランザクションもロールバックすることになります。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:207
+#, no-c-format
+msgid ""
+"If no timeout value is explicitly set for a transaction, or a value of 0 is "
+"specified, then an implementation specific default value may be used. In the "
+"case of JBossTS, how this default value is set depends upon which JTA "
+"implementation you are using."
+msgstr ""
+"トランザクションに対してタイムアウト値が明示的に設定されていない場合や値に 0 "
+"が指定されている場合、実装固有のデフォルト値が使用されます。JBossTS の場合、"
+"設定されるデフォルト値は使用している JTA 実装によって異なります。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:212
+#, no-c-format
+msgid ""
+"Local JTA: use the <property>com.arjuna.ats.arjuna.coordinator."
+"defaultTimeout</property> property value and give a timeout in seconds. The "
+"default value is 60 seconds."
+msgstr ""
+"ローカル JTA: <property>com.arjuna.ats.arjuna.coordinator.defaultTimeout</"
+"property> プロパティの値を使用し、秒単位でタイムアウトが指定されます。デフォ"
+"ルト値は 60 秒です。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:217
+#, no-c-format
+msgid ""
+"JTS: use the <property>com.arjuna.ats.jts.defaultTimeout</property> property "
+"value and give a timeout in seconds. The default value is 0, for instance, "
+"transactions do not timeout."
+msgstr ""
+"JTS: <property>com.arjuna.ats.jts.defaultTimeout</property> プロパティの値を"
+"使用し、秒単位でタイムアウトが指定されます。デフォルト値は 0 で、トランザク"
+"ションはタイムアウトしません。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:222
+#, no-c-format
+msgid ""
+"Unfortunately there are situations where imposing the same timeout as the "
+"transaction on a resource manager may not be appropriate. For example, if "
+"the system administrator wishes to have control over the lifetimes on "
+"resource managers and does not want to (or cannot) allow that control to be "
+"passed to some external entity. At present JBossTS supports an all-or-"
+"nothing approach to whether or not <methodname>setTransactionTimeout</"
+"methodname> is called on <interfacename>XAResource</interfacename> instances."
+msgstr ""
+"場合によっては、リソースマネージャのトランザクションと同じタイムアウト値を指"
+"定するのは適切でないことがあります。例えば、システム管理者がリソースマネー"
+"ジャの存続期間を制御し、同じ外部エンティティに制御を渡したくない（渡せない）"
+"場合などが該当します。現在 JBossTS では、<interfacename>XAResource</"
+"interfacename> インスタンスで <methodname>setTransactionTimeout</methodname> "
+"を呼び出すかどうかに関しては、全か無か (オールオアナッシング) の方法を取って"
+"います。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:225
+#, no-c-format
+msgid ""
+"If the <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> "
+"property is set to true (the default) then it will be called on all "
+"instances. Alternatively, the <methodname>setXATransactionTimeoutEnabled</"
+"methodname> method of <classname>com.arjuna.ats.jta.common.Configuration</"
+"classname> can be used."
+msgstr ""
+"<property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> プロパ"
+"ティが true に設定されている場合（デフォルト）、すべてのインスタンスで呼び出"
+"されます。代わりに、<classname>com.arjuna.ats.jta.common.Configuration</"
+"classname> の <methodname>setXATransactionTimeoutEnabled</methodname> メソッ"
+"ドも使用できます。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:231
+#, no-c-format
+msgid "Dynamic Registration"
+msgstr "動的な登録"
+
+#. Tag: para
+#: The_Resource_Manager.xml:232
+#, no-c-format
+msgid ""
+"Dynamic registration is not supported in <interfacename>XAResource</"
+"interfacename> because of the following reasons:"
+msgstr ""
+"以下の理由により、動的な登録は <interfacename>XAResource</interfacename> でサ"
+"ポートされていません："
+
+#. Tag: para
+#: The_Resource_Manager.xml:237
+#, no-c-format
+msgid ""
+"In the Java component-based application server environment, connections to "
+"the resource manager are acquired dynamically when the application "
+"explicitly requests a connection. These resources are enlisted with the "
+"transaction manager on a needed basis."
+msgstr ""
+"Java コンポーネントベースのアプリケーションサーバー環境では、アプリケーション"
+"が明示的に接続を要求すると、リソースマネージャへの接続が動的に取得されます。"
+"これらのリソースは必要になるとトランザクションマネージャに参加されます。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:242
+#, no-c-format
+msgid ""
+"If a resource manager requires a way to dynamically register its work to the "
+"global transaction, the implementation can be done at the resource adapter "
+"level via a private interface between the resource adapter and the "
+"underlying resource manager."
+msgstr ""
+"リソースマネージャの作業を動的にグローバルトランザクションに登録する方法が必"
+"要な場合、リソースアダプタと基礎のリソースマネージャ間のプライベートインター"
+"フェイスを介してリソースアダプタレベルで実装することができます。"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Transaction_Recovery.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Transaction_Recovery.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Transaction_Recovery.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,463 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr "トランザクションのリカバリ"
+
+#. Tag: title
+#: Transaction_Recovery.xml:10
+#, no-c-format
+msgid "Failure recovery"
+msgstr "障害のリカバリ"
+
+#. Tag: para
+#: Transaction_Recovery.xml:11
+#, no-c-format
+msgid ""
+"During recovery, the Transaction Manager needs to be able to communicate to "
+"all resource managers that are in use by the applications in the system. For "
+"each resource manager, the Transaction Manager uses the "
+"<methodname>XAResource.recover</methodname> method to retrieve the list of "
+"transactions that are currently in a prepared or heuristically completed "
+"state. Typically, the system administrator configures all transactional "
+"resource factories that are used by the applications deployed on the system. "
+"An example of such a resource factory is the JDBC <code>XADataSource</code> "
+"object, which is a factory for the JDBC <code>XAConnection</code> objects."
+msgstr ""
+"リカバリ中、Transaction Manager はシステムのアプリケーションによって使用され"
+"るすべてのリソースマネージャと通信できなければなりません。Transaction "
+"Manager は各リソースマネージャに対して <methodname>XAResource.recover</"
+"methodname> メソッドを使用し、現在準備済みまたはヒューリスティックな終了状態"
+"にあるトランザクションの一覧を読み出します。通常、システムにデプロイされたア"
+"プリケーションが使用するトランザクションリソースファクトリはすべてシステム管"
+"理者が設定します。このようなリソースファクトリの 1 つが、JDBC "
+"<code>XAConnection</code> オブジェクトのファクトリである JDBC "
+"<code>XADataSource</code> オブジェクトです。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:14
+#, no-c-format
+msgid ""
+"Because <code>XAResource</code> objects are not persistent across system "
+"failures, the Transaction Manager needs to have some way to acquire the "
+"<code>XAResource</code> objects that represent the resource managers which "
+"might have participated in the transactions prior to the system failure. For "
+"example, a Transaction Manager might, through the use of JNDI lookup "
+"mechanism, acquire a connection from each of the transactional resource "
+"factories, and then obtain the corresponding <code>XAResource</code> object "
+"for each connection. The Transaction Manager then invokes the "
+"<methodname>XAResource.recover</methodname> method to ask each resource "
+"manager to return the transactions that are currently in a prepared or "
+"heuristically completed state."
+msgstr ""
+"<code>XAResource</code> オブジェクトはシステム障害全体で永続的ではないため、"
+"システム障害が発生する前にトランザクションに参加していた可能性があるリソース"
+"マネージャを表す <code>XAResource</code> オブジェクトを取得する方法が "
+"Transaction Manager に必要になります。例えば、Transaction Manager は JNDI "
+"ルックアップメカニズムを利用して各トランザクションリソースファクトリより接続"
+"を取得し、各接続に対応する <code>XAResource</code> オブジェクトを取得すること"
+"ができます。その後 Transaction Manager は <methodname>XAResource.recover</"
+"methodname> メソッドを呼び出し、各リソースマネージャに対して現在準備済みまた"
+"はヒューリスティックな終了状態にあるトランザクションを返すよう要求します。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:18
+#, no-c-format
+msgid ""
+"When running XA recovery it is 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 ‘*’ will force JBossTS to recover (and possibly rollback) all "
+"transactions irrespective of their node identifier and should be used with "
+"caution."
+msgstr ""
+"XA リカバリを実行する際、JBossTS にリカバリ可能な Xid タイプを伝える必要があ"
+"ります。JBossTS が作成する各 Xid はエンコードされた固有のノード識別子を持って"
+"います。JBossTS は指定のノード識別子と一致するトランザクションや状態のみをリ"
+"カバリします。使用するノード識別子は、名前が <property>com.arjuna.ats.jta."
+"xaRecoveryNode</property> で始まるプロパティを介して JBossTS に提供しなければ"
+"なりません（複数の値を提供できます）。値に「*」を指定すると、JBossTS はノード"
+"識別子に関係なくすべてのトランザクションをリカバリ（場合によってはロールバッ"
+"ク）するため、「*」は注意して使用するようにしてください。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:22
+#, no-c-format
+msgid ""
+"If using the JBossJTA JDBC 2.0 driver, then JBossJTA will take care of all "
+"<interfacename>XAResource</interfacename> crash recovery automatically. "
+"Otherwise one of the following recovery mechanisms will be used:"
+msgstr ""
+"JBossJTA JDBC 2.0 ドライバを使用している場合、JBossJTA は自動的にすべての "
+"<interfacename>XAResource</interfacename> クラッシュリカバリを処理します。"
+"JBossJTA JDBC 2.0 ドライバを使用していない場合は、下記のリカバリメカニズムの "
+"1 つが使用されます。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:27
+#, no-c-format
+msgid ""
+"If the <code>XAResource</code> is serializable, then the serialized form "
+"will be saved during transaction commitment, and used during recovery. It is "
+"assumed that the recreated <code>XAResource</code> is valid and can be used "
+"to drive recovery on the associated database."
+msgstr ""
+"<code>XAResource</code> がシリアライズ可能な場合、トランザクションのコミット"
+"中にシリアライズされたものが保存され、リカバリ時に使用されます。再作成された "
+"<code>XAResource</code> は有効で、関連するデータベースのリカバリ実行に使用で"
+"きることが前提となります。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:32
+#, no-c-format
+msgid ""
+"The <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, <interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> and <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> interfaces are used. These "
+"are documented in the JDBC chapters on failure recovery."
+msgstr ""
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename> インターフェイスや <interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> インターフェイス、"
+"<interfacename>com.arjuna.ats.jta.recovery.XARecoveryResource</"
+"interfacename> インターフェイスが使用されます。これらのインターフェイスについ"
+"ては、JDBC 章の障害リカバリに関する文書を参照してください。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:38
+#, no-c-format
+msgid ""
+"In JBossTS 3.3 the interface <interfacename>XAConnectionRecovery</"
+"interfacename> was deprecated in favor of <interfacename>XAResourceRecovery</"
+"interfacename>. Users are encouraged to move to his new interface."
+msgstr ""
+"JBossTS 3.3 では、<interfacename>XAResourceRecovery</interfacename> インター"
+"フェイスが推奨され、<interfacename>XAConnectionRecovery</interfacename> は非"
+"推奨のインターフェイスとなっています。ユーザーは新しいインターフェイスを使用"
+"するようにしてください。"
+
+#. Tag: title
+#: Transaction_Recovery.xml:45
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr "XAConnections のリカバリ"
+
+#. Tag: para
+#: Transaction_Recovery.xml:46
+#, no-c-format
+msgid ""
+"When recovering from failures, JBossJTA requires the ability to reconnect to "
+"databases that were in use prior to the failures in order to resolve any "
+"outstanding transactions. Most connection information will be saved by the "
+"transaction service during its normal execution, and can be used during "
+"recovery to recreate the connection. However, it is possible that not all "
+"such information will have been saved prior to a failure (for example, a "
+"failure occurs before such information can be saved, but after the database "
+"connection is used). In order to recreate those connections it is necessary "
+"to provide implementations of the following JBossJTA interface "
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, one for each database that may be used by an application."
+msgstr ""
+"障害をリカバリする際、問題のあるトランザクションを解決するため JBossJTA は障"
+"害が発生する前に使用されていたデータベースに再接続できなければなりません。ほ"
+"とんどの接続情報は正常実行中にトランザクションサービスによって保存され、リカ"
+"バリの際に接続を再作成するために使用できます。しかし、障害の前にすべての情報"
+"が保存されていない可能性があります（例えば、データベースを使用した後、情報が"
+"保存される前に障害が発生した場合）。このような接続を再作成するには、JBossJTA "
+"インターフェイスである <interfacename>com.arjuna.ats.jta.recovery."
+"XAResourceRecovery</interfacename> の実装を、アプリケーションによって使用され"
+"るデータベースごとに提供する必要があります。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:50
+#, no-c-format
+msgid ""
+"If using the transactional JDBC 2.0 driver provided with JBossJTA, then no "
+"additional work is necessary in order to ensure that recovery occurs."
+msgstr ""
+"JBossJTA で提供されるトランザクション JDBC 2.0 ドライバを使用する場合、リカバ"
+"リの実行を確実にするための作業は発生しません。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:54
+#, no-c-format
+msgid ""
+"To inform the recovery system about each of the <code>XAResourceRecovery</"
+"code> instances, it is necessary to specify their class names through "
+"property variables. Any property variable found in the properties file, or "
+"registered at runtime, which starts with the name <property>com.arjuna.ats."
+"jta.recovery.XAResourceRecovery</property> will be assumed to represent one "
+"of these instances, and its value should be the class name. For example:"
+msgstr ""
+"各 <code>XAResourceRecovery</code> インスタンスについてリカバリシステムへ通知"
+"するには、プロパティ変数にてインスタンスのクラス名を指定する必要があります。"
+"名前が <property>com.arjuna.ats.jta.recovery.XAResourceRecovery</property> で"
+"始まるプロパティファイルのプロパティ変数や実行時に登録されるプロパティ変数"
+"は、<code>XAResourceRecovery</code> インスタンスの 1 つを示すことを前提としま"
+"す。また、その値はクラス名でなければなりません。例は次の通りです。"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:57
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+
+#. Tag: para
+#: Transaction_Recovery.xml:58
+#, no-c-format
+msgid ""
+"Additional information that will be passed to the instance when it is "
+"created may be specified after a semicolon:"
+msgstr ""
+"インスタンスの作成時に渡される追加情報は、セミコロン (;) の後に指定することが"
+"できます。"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+
+#. Tag: para
+#: Transaction_Recovery.xml:63
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr ""
+"これらのプロパティはプロパティファイルの JTA セクションになければなりません。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:67
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr "発生したエラーはリカバリ中に報告されます。"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:70
+#, no-c-format
+msgid ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+msgstr ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+
+#. Tag: para
+#: Transaction_Recovery.xml:71
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr "各メソッドは次の情報を返さなければなりません："
+
+#. Tag: para
+#: Transaction_Recovery.xml:76
+#, no-c-format
+msgid ""
+"<methodname>initialise</methodname>: once the instance has been created, any "
+"additional information which occurred on the property value (anything found "
+"after the first semi-colon) will be passed to the object. The object can "
+"then use this information in an implementation specific manner to initialise "
+"itself, for example."
+msgstr ""
+"<methodname>initialise</methodname>: インスタンスが作成されると、プロパティ値"
+"にある追加情報（最初のセミコロンの後にある情報）がオブジェクトに渡されます。"
+"その後、オブジェクトは実装固有の方法でこの情報を使用し、オブジェクト自体を初"
+"期化できます。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:81
+#, no-c-format
+msgid ""
+"<methodname>hasMoreResources</methodname>: each <code>XAResourceRecovery</"
+"code> implementation may provide multiple <code>XAResource</code> instances. "
+"Before any call to <methodname>getXAResource</methodname> is made, "
+"<methodname>hasMoreResources</methodname> is called to determine whether "
+"there are any further connections to be obtained. If this returns false, "
+"<methodname>getXAResource</methodname> will not be called again during this "
+"recovery sweep and the instance will not be used further until the next "
+"recovery scan."
+msgstr ""
+"<methodname>hasMoreResources</methodname>: 各 <code>XAResourceRecovery</"
+"code> 実装は複数の <code>XAResource</code> インスタンスを提供することができま"
+"す。<methodname>getXAResource</methodname> への呼び出しが実行される前、"
+"<methodname>hasMoreResources</methodname> が呼び出され、他に取得する接続がな"
+"いか判断します。false が返された場合、このリカバリスイープの間は "
+"<methodname>getXAResource</methodname> が再度呼び出されず、次のリカバリスキャ"
+"ンまでインスタンスは使用されません。 "
+
+#. Tag: para
+#: Transaction_Recovery.xml:86
+#, no-c-format
+msgid ""
+"<methodname>getXAResource</methodname>: returns an instance of the "
+"<code>XAResource</code> object. How this is created (and how the parameters "
+"to its constructors are obtained) is up to the <code>XAResourceRecovery</"
+"code> implementation. The parameters to the constructors of this class "
+"should be similar to those used when creating the initial driver or data "
+"source, and should obviously be sufficient to create new <code>XAResources</"
+"code> that can be used to drive recovery."
+msgstr ""
+"<methodname>getXAResource</methodname>: <code>XAResource</code> オブジェクト"
+"のインスタンスを返します。作成方法（およびコンストラクタへのパラメータの取得"
+"方法）は、<code>XAResourceRecovery</code> の実装により決まります。このクラス"
+"のコンストラクタへのパラメータは、初期ドライバやデータソースの作成時に使用し"
+"したパラメータと同様で、リカバリを実行するために使用する新しい "
+"<code>XAResources</code> を作成できなければなりません。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:92
+#, no-c-format
+msgid ""
+"If you want your <code>XAResourceRecovery</code> instance to be called "
+"during each sweep of the recovery manager then you should ensure that once "
+"<methodname>hasMoreResources</methodname> returns false to indicate the end "
+"of work for the current scan it then returns true for the next recovery scan."
+msgstr ""
+"リカバリマネージャの各スイープ時に <code>XAResourceRecovery</code> インスタン"
+"スが呼び出されるようにするには、<methodname>hasMoreResources</methodname> が "
+"false を返して現在のスキャンの終了を示した後、次のリカバリスキャンに対して "
+"true を返すようにしなければなりません。"
+
+#. Tag: title
+#: Transaction_Recovery.xml:99
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr "同梱の XAResourceRecovery 実装"
+
+#. Tag: para
+#: Transaction_Recovery.xml:100
+#, no-c-format
+msgid ""
+"Recovery of <interfacename>XA</interfacename> datasources can sometimes be "
+"implementation dependant, requiring developers to provide their own "
+"<interfacename>XAResourceRecovery</interfacename> instances. However, "
+"JBossTS ships with several out-of-the-box implementations that may be useful."
+msgstr ""
+"<interfacename>XA</interfacename> データソースのリカバリは実装に依存すること"
+"があり、その場合は開発者が独自の <interfacename>XAResourceRecovery</"
+"interfacename> インスタンスを提供する必要があります。しかし、JBossTS はすぐに"
+"使用可能な実装を複数同梱しているため便利です。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:105
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: this expects an XML property file to be specified upon "
+"creation and from which it will read the database URL, username and "
+"password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: 作成時における XML プロパティファイルの指定を前提とし、そのプ"
+"ロパティファイルよりデータベース URL やユーザー名、パスワードを読み込みます。"
+"例は次の通りです。"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:108
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+
+#. Tag: para
+#: Transaction_Recovery.xml:111
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: this recovery implementation should work on any datasource "
+"that is exposed via JNDI. It expects an XML property file to be specified "
+"upon creation and from which it will read the database JNDI name, username "
+"and password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: このリカバリ実装は、JNDI 経由で公開されるすべてのデータソース"
+"上で動作するはずです。作成時に XML プロパティファイルを指定することを前提と"
+"し、そのプロパティファイルよりデータベース JNDI 名やユーザー名、パスワードを"
+"読み込みます。例は次の通りです。"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:114
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,643 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr "トランザクション"
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr "API"
+
+#. Tag: para
+#: Transactions.xml:9
+#, no-c-format
+msgid ""
+"The Java Transaction API consists of three elements: a high-level "
+"application transaction demarcation interface, a high-level transaction "
+"manager interface intended for application server, and a standard Java "
+"mapping of the X/Open XA protocol intended for transactional resource "
+"manager. All of the JTA classes and interfaces occur within the "
+"<package>javax.transaction</package> package, and the corresponding JBossJTA "
+"implementations within the <package>com.arjuna.ats.jta</package> package."
+msgstr ""
+"Java トランザクション API は、ハイレベルなアプリケーショントランザクション区"
+"分インターフェイス、アプリケーションサーバー向けのハイレベルなトランザクショ"
+"ンマネージャインターフェイス、トランザクションリソースマネージャ向け X/Open "
+"XA プロトコルの標準 Java マッピングの 3 つの要素から構成されています。JTA ク"
+"ラスとインターフェイスのすべては <package>javax.transaction</package> パッ"
+"ケージ内に存在し、対応する JBossJTA 実装は <package>com.arjuna.ats.jta</"
+"package> パッケージ内に存在します。"
+
+#. Tag: para
+#: Transactions.xml:13
+#, no-c-format
+msgid ""
+"Each 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. The contents of this "
+"should be alphanumeric."
+msgstr ""
+"JBossTS が作成する各 Xid は、エンコードされた固有のノード識別子を持たなければ"
+"なりません。また、JBossTS は特定のノード識別子と一致するトランザクションや状"
+"態のみをリカバリします。使用するノード識別子は、<property>com.arjuna.ats."
+"arjuna.xa.nodeIdentifier</property> プロパティより JBossTS に提供しなければな"
+"りません。ノード識別子の値は、JBossTS インスタンス全体で固有になるようにして"
+"ください。値の指定がない場合、JBossTS は 1 つの値を割り当て、その値をロギング"
+"インフラストラクチャを介して報告します。この値には英数字を使用しなければなり"
+"ません。"
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: Transactions.xml:19
+#, no-c-format
+msgid ""
+"The <interfacename>UserTransaction</interfacename> interface provides "
+"applications with the ability to control transaction boundaries. It has "
+"methods for beginning, committing, and rolling back top-level transactions: "
+"nested transactions are not supported, and begin throws the "
+"<code>NotSupportedException</code> when the calling thread is already "
+"associated with a transaction. <interfacename>UserTransaction</"
+"interfacename> automatically associates newly created transactions with the "
+"invoking thread."
+msgstr ""
+"<interfacename>UserTransaction</interfacename> インターフェイスは、トランザク"
+"ション境界を制御できるアプリケーションを提供します。このインターフェイスは、"
+"トップレベルのトランザクションを開始、コミット、ロールバックするメソッドを"
+"持っています。ネストされたトランザクションはサポートされません。begin (開始) "
+"の場合、呼び出しスレッドが既にトランザクションに関連付けられていると "
+"<code>NotSupportedException</code> をスローします。"
+"<interfacename>UserTransaction</interfacename> は、新しく作成されたトランザク"
+"ションを自動的に呼び出されたスレッドに関連付けます。"
+
+#. Tag: para
+#: Transactions.xml:24
+#, no-c-format
+msgid ""
+"In JBossJTA, UserTransactions can be obtained from the static "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname> method."
+msgstr ""
+"JBossJTA では、静的な <methodname>com.arjuna.ats.jta.UserTransaction."
+"userTransaction()</methodname> メソッドから UserTransactions を取得することが"
+"できます。"
+
+#. Tag: para
+#: Transactions.xml:28
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr "ローカルの JTA 実装を選択するには、次の手順を実行する必要があります。"
+
+#. Tag: para
+#: Transactions.xml:33
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</property>."
+msgstr ""
+"<property>com.arjuna.ats.jta.jtaTMImplementation</property> プロパティが "
+"<property>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</property> に設定されていることを確認します。"
+
+#. Tag: para
+#: Transactions.xml:38
+#, no-c-format
+msgid ""
+"1.make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</property>."
+msgstr ""
+"1. <property>com.arjuna.ats.jta.jtaTMImplementation</property> プロパティが "
+"<property>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</property> に設定されていることを確認します。"
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: Transactions.xml:45
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface allows the "
+"application server to control transaction boundaries on behalf of the "
+"application being managed."
+msgstr ""
+"<interfacename>TransactionManager</interfacename> インターフェイスは、管理さ"
+"れているアプリケーションの代わりにアプリケーションサーバーがトランザクション"
+"境界を制御できるようにします。"
+
+#. Tag: para
+#: Transactions.xml:50
+#, no-c-format
+msgid ""
+"In JBossJTA, transaction manager implementations can be obtained from the "
+"static <methodname>com.arjuna.ats.jta.TransactionManager.transactionManager</"
+"methodname> method."
+msgstr ""
+"JBossJTA では、トランザクションマネージャの実装を静的な <methodname>com."
+"arjuna.ats.jta.TransactionManager.transactionManager</methodname> メソッドよ"
+"り取得することができます。"
+
+#. Tag: para
+#: Transactions.xml:54
+#, no-c-format
+msgid ""
+"The Transaction Manager maintains the transaction context association with "
+"threads as part of its internal data structure. A thread’s transaction "
+"context is either null or it refers to a specific global transaction. "
+"Multiple threads may be associated with the same global transaction. As "
+"noted above, nested transactions are not supported."
+msgstr ""
+"Transaction Manager は、内部データ構造の一部としてトランザクションコンテキス"
+"トのスレッドへの関係付けを維持します。スレッドのトランザクションコンテキスト"
+"は、null または特定のグローバルトランザクションを参照します。同じグローバルト"
+"ランザクションに複数のスレッドが関連付けられることもあります。前述の通り、ネ"
+"ストされたトランザクションはサポートされません。"
+
+#. Tag: para
+#: Transactions.xml:57
+#, no-c-format
+msgid ""
+"Each transaction context is encapsulated by a Transaction object, which can "
+"be used to perform operations which are specific to the target transaction, "
+"regardless of the calling thread’s transaction context."
+msgstr ""
+"各トランザクションコンテキストは、呼び出しスレッドのトランザクションコンテキ"
+"ストに関係なく、ターゲットトランザクション固有の操作を実行するため使用可能な"
+"トランザクションオブジェクトによってカプセル化されます。"
+
+#. Tag: para
+#: Transactions.xml:60
+#, no-c-format
+msgid ""
+"The <methodname>begin</methodname> method of "
+"<interfacename>TransactionManager</interfacename> starts a new top-level "
+"transaction and associates the transaction context with the calling thread. "
+"If the calling thread is already associated with a transaction then it "
+"throws the <code>NotSupportedException</code>."
+msgstr ""
+"<interfacename>TransactionManager</interfacename> の <methodname>begin</"
+"methodname> メソッドは、新しい最上位のトランザクションを開始し、トランザク"
+"ションコンテキストを呼び出しスレッドに関連付けます。呼び出しスレッドが既にト"
+"ランザクションへ関連付けられている場合、<code>NotSupportedException</code> を"
+"スローします。"
+
+#. Tag: para
+#: Transactions.xml:63
+#, no-c-format
+msgid ""
+"The <methodname>getTransaction</methodname> method returns the Transaction "
+"object that represents the transaction context currently associated with the "
+"calling thread. This object can be used to perform various operations on the "
+"target transaction, described later."
+msgstr ""
+"<methodname>getTransaction</methodname> メソッドは、現在呼び出しスレッドに関"
+"連付けられているトランザクションコンテキストを表すトランザクションオブジェク"
+"トを返します。このオブジェクトを使用して、ターゲットトランザクションに対して"
+"さまざまな操作を実行できますが、詳細は追って説明します。"
+
+#. Tag: para
+#: Transactions.xml:66
+#, no-c-format
+msgid ""
+"The commit method is used to complete the transaction currently associated "
+"with the calling thread. After it returns, the calling thread is associated "
+"with no transaction. If commit is called when the thread is not associated "
+"with any transaction context, the TM throws an exception. In some "
+"implementation, the commit operation is restricted to the transaction "
+"originator only. If the calling thread is not allowed to commit the "
+"transaction, the TM throws an exception. JBossJTA does not currently impose "
+"any restriction on the ability of threads to terminate transactions."
+msgstr ""
+"commit メソッドは、現在呼び出しスレッドに関連付けられているトランザクションを"
+"完了するために使用されます。このメソッドが返された後は、呼び出しスレッドに関"
+"連付けられるトランザクションはありません。スレッドがトランザクションコンテキ"
+"ストに関連付けられていない状態で commit が呼び出されると、TM が例外をスローし"
+"ます。実装によっては、commit 操作がトランザクションオリジネータのみに限定され"
+"る場合があります。呼び出しスレッドによるトランザクションの commit が許可され"
+"ていない場合、TM は例外をスローします。現在 JBossJTA は、スレッドによるトラン"
+"ザクションの終了を制限していません。"
+
+#. Tag: para
+#: Transactions.xml:69
+#, no-c-format
+msgid ""
+"The <methodname>rollback</methodname> method is used to rollback the "
+"transaction associated with the current thread. After the "
+"<methodname>rollback</methodname> method completes, the thread is associated "
+"with no transaction."
+msgstr ""
+"<methodname>rollback</methodname> メソッドは、現在のスレッドに関連付けられて"
+"いるトランザクションをロールバックするために使用されます。"
+"<methodname>rollback</methodname> メソッドが完了した後、スレッドに関連付けら"
+"れるトランザクションはありません。"
+
+#. Tag: para
+#: Transactions.xml:73
+#, no-c-format
+msgid ""
+"In a multi-threaded environment it is possible that multiple threads are "
+"active within the same transaction. If checked transaction semantics have "
+"been disabled, or the transaction times out, then it is possible for a "
+"transaction to be terminated by a thread other than the one that created it. "
+"In this case, it is often important that this information is communicated to "
+"the creator. JBossTS does this during commit or rollback by throwing "
+"<code>IllegalStateException</code>."
+msgstr ""
+"マルチスレッド環境では、同じトランザクション内で複数のスレッドがアクティブに"
+"なることがあります。チェックされたトランザクションセマンティクスが無効になっ"
+"たり、トランザクションがタイムアウトになった場合、作成したスレッド以外のス"
+"レッドによってトランザクションが終了される場合があります。このような場合、情"
+"報を作成者に伝えることが重要となりますが、JBossTS では、commit または "
+"rollback の際に <code>IllegalStateException</code> がスローされます。"
+
+#. Tag: title
+#: Transactions.xml:78
+#, no-c-format
+msgid "Suspending and resuming a transaction"
+msgstr "トランザクションの一時停止および再開"
+
+#. Tag: para
+#: Transactions.xml:79
+#, no-c-format
+msgid ""
+"The JTA supports the concept of a thread temporarily suspending and resuming "
+"transactions to enable it to perform non-transactional work. The suspend "
+"method is called to temporarily suspend the current transaction that is "
+"associated with the calling thread, i.e., so that the thread is no longer "
+"operating within its scope. If the thread is not associated with any "
+"transaction, a null object reference is returned; otherwise, a valid "
+"<code>Transaction</code> object is returned. The <code>Transaction</code> "
+"object can later be passed to the resume method to reinstate the transaction "
+"context."
+msgstr ""
+"JTA は、非トランザクション的な処理の実行を可能にするため、スレッドによるトラ"
+"ンザクションの一時停止および再開の概念をサポートしています。呼び出しスレッド"
+"と関連付けられている現トランザクションを一時停止するために suspend メソッドが"
+"呼び出されます (スレッドが範囲内で操作しないようになります）。スレッドに関連"
+"付けられているトランザクションがない場合、null オブジェクト参照が返されます"
+"が、それ以外の場合は有効な <code>Transaction</code> オブジェクトが返されま"
+"す。その後、トランザクションコンテキストを回復するため、<code>Transaction</"
+"code> オブジェクトは resume メソッドに渡されます。"
+
+#. Tag: para
+#: Transactions.xml:83
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method associates the specified "
+"transaction context with the calling thread. If the transaction specified is "
+"a valid transaction, the transaction context is associated with the calling "
+"thread; otherwise, the thread is associated with no transaction."
+msgstr ""
+"<methodname>resume</methodname> メソッドは、指定のトランザクションコンテキス"
+"トを呼び出しスレッドへ関連付けます。指定のトランザクションが有効なトランザク"
+"ションである場合、トランザクションコンテキストが呼び出しスレッドへ関連付けら"
+"れますい。有効なトランザクションでない場合は、スレッドはトランザクションへ関"
+"連付けられません。"
+
+#. Tag: para
+#: Transactions.xml:87
+#, no-c-format
+msgid ""
+"If <methodname>resume</methodname> is invoked when the calling thread is "
+"already associated with another transaction, the Transaction Manager throws "
+"the <code>IllegalStateException</code> exception."
+msgstr ""
+"呼び出しスレッドが他のトランザクションに関連付けられている状態で "
+"<methodname>resume</methodname> を呼び出すと、Transaction Manager が "
+"<code>IllegalStateException</code> 例外をスローします。"
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+
+#. Tag: para
+#: Transactions.xml:93
+#, no-c-format
+msgid ""
+"Some Transaction Manager implementations allow a suspended transaction to be "
+"resumed by a different thread. This feature is not required by JTA, but "
+"JBossJTA does support this."
+msgstr ""
+"Transaction Manager によっては、一時停止されたトランザクションを異なるスレッ"
+"ドで再開できます。これは JTA の必須機能ではありませんが、JBossJTA はサポート"
+"しています。"
+
+#. Tag: para
+#: Transactions.xml:97
+#, no-c-format
+msgid ""
+"When a transaction is suspended the application server must ensure that the "
+"resources in use by the application are no longer registered with the "
+"suspended transaction. When a resource is de-listed this triggers the "
+"Transaction Manager to inform the resource manager to disassociate the "
+"transaction from the specified resource object. When the application’s "
+"transaction context is resumed, the application server must ensure that the "
+"resources in use by the application are again enlisted with the transaction. "
+"Enlisting a resource as a result of resuming a transaction triggers the "
+"Transaction Manager to inform the resource manager to re-associate the "
+"resource object with the resumed transaction."
+msgstr ""
+"トランザクションが一時停止された際、アプリケーションサーバーはアプリケーショ"
+"ンによって使用されるリソースが停止されたトランザクションに登録されないように"
+"しなければなりません。リソースの参加が解除されると、Transaction Manager はト"
+"ランザクションと指定のリソースオブジェクトの関連付けを解除するようリソースマ"
+"ネージャに伝えます。アプリケーションのトランザクションコンテキストが再開され"
+"た際、アプリケーションサーバーはアプリケーションによって使用されるリソースを"
+"再度トランザクションに参加させなければなりません。トランザクションの再開に"
+"よってリソースが参加されると、Transaction Manager はリソースオブジェクトと再"
+"開されたトランザクションを再度関連付けるようリソースマネージャに伝えます。"
+
+#. Tag: title
+#: Transactions.xml:101
+#, no-c-format
+msgid "The Transaction interface"
+msgstr "Transaction インターフェイス"
+
+#. Tag: para
+#: Transactions.xml:102
+#, no-c-format
+msgid ""
+"The <interfacename>Transaction</interfacename> interface allows operations "
+"to be performed on the transaction associated with the target object. Every "
+"top-level transaction is associated with one <code>Transaction</code> object "
+"when the transaction is created. The <code>Transaction</code> object can be "
+"used to:"
+msgstr ""
+"<interfacename>Transaction</interfacename> インターフェイスは、ターゲットオブ"
+"ジェクトに関連付けられているトランザクション上で操作を実行できるようにしま"
+"す。各最上位トランザクションは、作成されると 1 つの <code>Transaction</code> "
+"オブジェクトに関連付けられます。<code>Transaction</code> オブジェクトは以下の"
+"目的で使用されます："
+
+#. Tag: para
+#: Transactions.xml:108
+#, no-c-format
+msgid "Enlist the transactional resources in use by the application."
+msgstr ""
+"アプリケーションによって使用されるトランザクションリソースを参加させる。"
+
+#. Tag: para
+#: Transactions.xml:113
+#, no-c-format
+msgid "Register for transaction synchronization call backs."
+msgstr "トランザクション同期化のコールバックを登録する。"
+
+#. Tag: para
+#: Transactions.xml:118
+#, no-c-format
+msgid "Commit or rollback the transaction."
+msgstr "トランザクションをコミットまたはロールバックする。"
+
+#. Tag: para
+#: Transactions.xml:123
+#, no-c-format
+msgid "Obtain the status of the transaction."
+msgstr "トランザクションの状態を取得する。"
+
+#. Tag: para
+#: Transactions.xml:128
+#, no-c-format
+msgid ""
+"The <methodname>commit</methodname> and <methodname>rollback</methodname> "
+"methods allow the target object to be committed or rolled back. The calling "
+"thread is not required to have the same transaction associated with the "
+"thread. If the calling thread is not allowed to commit the transaction, the "
+"transaction manager throws an exception. At present JBossJTA does not impose "
+"restrictions on threads terminating transactions."
+msgstr ""
+"<methodname>commit</methodname> および <methodname>rollback</methodname> メ"
+"ソッドは、ターゲットオブジェクトをコミットまたはロールバックできるようにしま"
+"す。呼び出しスレッドはスレッドに関連付けられている同じトランザクションを持つ"
+"必要はありません。呼び出しスレッドがトランザクションをコミットできない場合、"
+"トランザクションマネージャは例外をスローします。現在、JBossJTA はスレッドによ"
+"るトランザクションの終了を制限していません。"
+
+#. Tag: title
+#: Transactions.xml:132
+#, no-c-format
+msgid "Resource enlistment"
+msgstr "リソース参加"
+
+#. Tag: para
+#: Transactions.xml:133
+#, no-c-format
+msgid ""
+"Transactional resources such as database connections are typically managed "
+"by the application server in conjunction with some resource adapter and "
+"optionally with connection pooling optimization. In order for an external "
+"transaction manager to co-ordinate transactional work performed by the "
+"resource managers, the application server must enlist and de-list the "
+"resources used in the transaction. These resources (participants) are "
+"enlisted with the transaction so that they can be informed when the "
+"transaction terminates, for example, are driven through the two-phase commit "
+"protocol."
+msgstr ""
+"データベース接続などのトランザクションリソースは、通常リソースアダプタやオプ"
+"ションの接続プーリング最適化と共にアプリケーションサーバーによって管理されま"
+"す。外部トランザクションマネージャによってリソースマネージャが実行するトラン"
+"ザクションを調整できるようにするため、アプリケーションサーバーはトランザク"
+"ションで使用するリソースを参加させたり参加を解除しなければなりません。リソー"
+"ス（参加者）はトランザクションへ参加するため、トランザクションが終了すると通"
+"知されます（例：2 フェーズコミットプロトコルを介した場合など）。"
+
+#. Tag: para
+#: Transactions.xml:137
+#, no-c-format
+msgid ""
+"As stated previously, the JTA is much more closely integrated with the XA "
+"concept of resources than the arbitrary objects. For each resource in-use by "
+"the application, the application server invokes the "
+"<methodname>enlistResource</methodname> method with an <code>XAResource</"
+"code> object which identifies the resource in use. See for details on how "
+"the implementation of the <code>XAResource</code> can affect recovery in the "
+"event of a failure."
+msgstr ""
+"前述の通り、JTA は任意オブジェクトよりも XA 概念のリソースにより深く統合され"
+"ています。アプリケーションサーバーはアプリケーションによって使用される各リ"
+"ソースに対して、使用中のリソースを特定する <code>XAResource</code> を持つ "
+"<methodname>enlistResource</methodname> メソッドを呼び出します。障害が発生し"
+"た時、<code>XAResource</code> の実装がどのようにリカバリに影響するか注意して"
+"ください。"
+
+#. Tag: para
+#: Transactions.xml:140
+#, no-c-format
+msgid ""
+"The enlistment request results in the transaction manager informing the "
+"resource manager to start associating the transaction with the work "
+"performed through the corresponding resource. The transaction manager is "
+"responsible for passing the appropriate flag in its <methodname>XAResource."
+"start</methodname> method call to the resource manager."
+msgstr ""
+"トランザクションマネージャは参加要求があると、対応するリソースを介して実行さ"
+"れる処理にトランザクションを関連付けるようリソースマネージャに伝えます。トラ"
+"ンザクションマネージャは、リソースマネージャに対する <methodname>XAResource."
+"start</methodname> メソッドの呼び出しで適切なフラグを渡します。"
+
+#. Tag: para
+#: Transactions.xml:143
+#, no-c-format
+msgid ""
+"The <methodname>delistResource</methodname> method is used to disassociate "
+"the specified resource from the transaction context in the target object. "
+"The application server invokes the method with the two parameters: the "
+"<code>XAResource</code> object that represents the resource, and a flag to "
+"indicate whether the operation is due to the transaction being suspended "
+"(TMSUSPEND), a portion of the work has failed (TMFAIL), or a normal resource "
+"release by the application (TMSUCCESS)."
+msgstr ""
+"<methodname>delistResource</methodname> メソッドは、ターゲットオブジェクトの"
+"トランザクションコンテキストと特定リソースとの関連付けを解除するために使用さ"
+"れます。アプリケーションサーバーは、2 つのパラメータを用いてこのメソッドを呼"
+"び出します。この 2 つのパラメータは、リソースを表す <code>XAResource</code> "
+"オブジェクトおよびフラグ (トランザクションが一時停止したことを示す "
+"TMSUSPEND、処理の一部が失敗したことを示す TMFAIL、アプリケーションによる正常"
+"なリソースの開放を示す TMSUCCESS ) になります。"
+
+#. Tag: para
+#: Transactions.xml:146
+#, no-c-format
+msgid ""
+"The de-list request results in the transaction manager informing the "
+"resource manager to end the association of the transaction with the target "
+"<code>XAResource</code>. The flag value allows the application server to "
+"indicate whether it intends to come back to the same resource whereby the "
+"resource states must be kept intact. The transaction manager passes the "
+"appropriate flag value in its <methodname>XAResource.end</methodname> method "
+"call to the underlying resource manager."
+msgstr ""
+"トランザクションマネージャは参加解除の要求があると、トランザクションとター"
+"ゲット <code>XAResource</code> の関連付けを解除するようリソースマネージャに伝"
+"えます。フラグの値により、アプリケーションサーバーはリソースの状態を維持しな"
+"ければならない同じリソースに戻るかを示すことができます。トランザクションマ"
+"ネージャは、リソースマネージャへの <methodname>XAResource.end</methodname> メ"
+"ソッド呼び出しで適切なフラグ値を渡します。"
+
+#. Tag: title
+#: Transactions.xml:150
+#, no-c-format
+msgid "Transaction synchronization"
+msgstr "トランザクションの同期化"
+
+#. Tag: para
+#: Transactions.xml:151
+#, no-c-format
+msgid ""
+"Transaction synchronization allows the application server to be notified "
+"before and after the transaction completes. For each transaction started, "
+"the application server may optionally register a Synchronization call back "
+"object to be invoked by the transaction manager:"
+msgstr ""
+"トランザクションの同期化により、アプリケーションサーバーはトランザクション終"
+"了の前と後に通知を受けます。アプリケーションサーバーはトランザクションマネー"
+"ジャによって呼び出される同期化コールバックオブジェクトを開始した各トランザク"
+"ションに対してオプションで登録することができます："
+
+#. Tag: para
+#: Transactions.xml:157
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method is called prior to the "
+"start of the two-phase transaction complete process. This call is executed "
+"in the same transaction context of the caller who initiates the "
+"<methodname>TransactionManager.commit</methodname> or the call is executed "
+"with no transaction context if <methodname>Transaction.commit</methodname> "
+"is used."
+msgstr ""
+"<methodname>beforeCompletion</methodname> メソッドは、2 フェーズトランザク"
+"ションの完了処理を開始する前に呼び出されます。この呼び出しは、"
+"<methodname>TransactionManager.commit</methodname> を開始した呼び出し元と同じ"
+"トランザクションコンテキストで実行されます。<methodname>Transaction.commit</"
+"methodname> が使用された場合、呼び出しはトランザクションコンテキストなしで実"
+"行されます。"
+
+#. Tag: para
+#: Transactions.xml:162
+#, no-c-format
+msgid ""
+"The <methodname>afterCompletion</methodname> method is called after the "
+"transaction has completed. The status of the transaction is supplied in the "
+"parameter. This method is executed without a transaction context."
+msgstr ""
+"<methodname>afterCompletion</methodname> メソッドは、トランザクションが終了し"
+"た後呼び出されます。トランザクションの状態はパラメータ内に提供されます。この"
+"メソッドはトランザクションコンテキストなしで実行されます。"
+
+#. Tag: title
+#: Transactions.xml:168
+#, no-c-format
+msgid "Transaction equality"
+msgstr "トランザクションの等価性"
+
+#. Tag: para
+#: Transactions.xml:169
+#, no-c-format
+msgid ""
+"The transaction manager implements the Transaction object’s equals method to "
+"allow comparison between the target object and another Transaction object. "
+"The equals method should return true if the target object and the parameter "
+"object both refer to the same global transaction."
+msgstr ""
+"トランザクションマネージャは、Transaction オブジェクトの equals メソッドを実"
+"装し、ターゲットオブジェクトと別の Transaction オブジェクトを比較できるように"
+"します。ターゲットオブジェクトとパラメータオブジェクトの両方が同じグローバル"
+"トランザクションを参照する場合、equals メソッドは true を返します。"
+
+#. Tag: screen
+#: Transactions.xml:173
+#, no-c-format
+msgid ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
+msgstr ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/ja-JP/Using_JBossJTA_in_Application_Servers.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,270 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Transactions_JTA_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-09-01 10:34+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr "アプリケーションサーバーで JBossJTA を使用する"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr "JBoss Application Server"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:10
+#, no-c-format
+msgid "Service Configuration"
+msgstr "サービスの設定"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:11
+#, no-c-format
+msgid ""
+"The JBoss Transaction Service is configured primarily via the XML files "
+"stored in the etc directory, but when run as a JBOSS service there are a "
+"number of configurable attributes available. They are as follows:"
+msgstr ""
+"JBoss Transaction Service は 主に etc ディレクトリに保存された XML ファイルよ"
+"り設定しますが、JBOSS サービスとして実行する際、設定可能な属性が複数ありま"
+"す。設定可能な属性は次の通りです。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:17
+#, no-c-format
+msgid ""
+"TransactionTimeout – The default transaction timeout to be used for new "
+"transactions. Specified as an integer in seconds."
+msgstr ""
+"TransactionTimeout – 新しいトランザクションに適応するデフォルトのトランザク"
+"ションタイムアウトです。整数値で秒数を指定します。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:22
+#, no-c-format
+msgid ""
+"StatisticsEnabled – This determines whether or not the transaction service "
+"should gather statistical information. This information can then be viewed "
+"using the PerformanceStatistics MBean. Specified as a Boolean. The default "
+"is to not gather this information."
+msgstr ""
+"StatisticsEnabled – トランザクションサービスによる統計情報収集の有無を指定し"
+"ます。この情報は PerformanceStatistics MBean を使用して表示できます。ブール変"
+"数で指定します。デフォルトの設定では統計情報は収集しません。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:27
+#, no-c-format
+msgid ""
+"PropagateFullContext – This determines whether a full transactional context "
+"is propagated by context importer/exporter. If set to false only the current "
+"transaction context is propagated. If set to true the full transaction "
+"context (including parent transactions) is propagated."
+msgstr ""
+"PropagateFullContext – 完全なトランザクションコンテキストをテキストインポータ"
+"およびエクスポータで伝搬するかを指定します。false を設定すると、現トランザク"
+"ションコンテキストのみ伝搬されます。true を設定すると、完全なトランザクション"
+"コンテキスト（親トランザクションを含む）が伝搬されます。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:32
+#, no-c-format
+msgid ""
+"These attributes are specified as MBean attributes in the jboss-service.xml "
+"file located in the server/all/conf directory, for example:"
+msgstr ""
+"これらの属性は MBean 属性として server/all/conf ディレクトリにある jboss-"
+"service.xml ファイルに指定されています。例は次の通りです。"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:35
+#, no-c-format
+msgid ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+msgstr ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:36
+#, no-c-format
+msgid ""
+"The transaction service is configurable also via the standard JBoss "
+"Transaction Service property files. These are located in the JBossTS install "
+"location under the etc sub-directory."
+msgstr ""
+"トランザクションサービスは、標準の JBoss Transaction Service プロパティファイ"
+"ルより設定することもできます。これらのファイルは etc サブディレクトリ以下の "
+"JBoss TS インストールの場所にあります。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:39
+#, no-c-format
+msgid ""
+"These files can be edited manually or through JMX. Each property file is "
+"exposed via an object with the name <code>com.arjuna.ts.properties</code> "
+"and an attribute of module where module is equal to the name of the module "
+"to be configured, for example, <code>com.arjuna.ts.properties:module=arjuna</"
+"code>."
+msgstr ""
+"これらのファイルは手作業または JMX で編集できます。<code>com.arjuna.ts."
+"properties</code> という名前のオブジェクトや設定されるモジュール名と同じであ"
+"るモジュールの属性（例：<code>com.arjuna.ts.properties:module=arjuna</code>）"
+"により各プロパティファイルは公開されます。"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:43
+#, no-c-format
+msgid "Logging"
+msgstr "ロギング"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:44
+#, no-c-format
+msgid ""
+"In order to make JBossTS logging semantically consistent with JBossAS, the "
+"TransactionManagerService modifies the level of some log messages. This is "
+"achieved by overriding the value of the <property>com.arjuna.common.util."
+"logger</property> property given in the <filename>jbossjta-properties.xml</"
+"filename> file. Therefore, the value of this property will have no effect on "
+"the logging behaviour when running embedded in JBossAS. By forcing use of "
+"the log4j_releveler logger, the TransactionManagerService causes all INFO "
+"level messages in the transaction code to be modified to behave as DEBUG "
+"messages. Therefore, these messages will not appear in log files if the "
+"filter level is INFO. All other log messages behave as normal."
+msgstr ""
+"JBossTS のロギングをセマンティック的に JBossAS と整合するため、"
+"TransactionManagerService は一部のログメッセージのレベルを変更します。これ"
+"は、<filename>jbossjta-properties.xml</filename> ファイルにある "
+"<property>com.arjuna.common.util.logger</property> プロパティの値を変更して実"
+"現します。そのため、JBossAS で組み込みとして実行する際、このプロパティの値は"
+"ロギングの動作に影響を与えません。log4j_releveler ロガーの使用を強制すると、"
+"TransactionManagerService によってトランザクションコードの INFO レベルのメッ"
+"セージはすべて DEBUG メッセージとして動作するよう変更されます。そのため、フィ"
+"ルタレベルが INFO の場合、これらのメッセージはログファイルに表示されません。"
+"その他のログメッセージはすべて通常通り動作します。"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:49
+#, no-c-format
+msgid "The services"
+msgstr "サービス"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:50
+#, no-c-format
+msgid ""
+"There is currently one service offered by the JBOSS integration called "
+"TransactionManagerService. Here we shall discuss what this service does."
+msgstr ""
+"現在、TransactionManagerService という 1 つのサービスが JBOSS の統合より提供"
+"されます。ここでは、このサービスについて説明します。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:54
+#, no-c-format
+msgid ""
+"The transaction manager service’s main purpose is to ensure the recovery "
+"manager is started. It also binds the JBossTS JTA transaction manager to "
+"java:/TransactionManager name with the JNDI provider. This service depends "
+"upon the existence of the CORBA ORB Service and it must be using JacORB as "
+"the underlying ORB implementation."
+msgstr ""
+"トランザクションマネージャサービスの主な目的は、リカバリマネージャを確実に開"
+"始させることです。また、JNDI プロバイダにて JBossTS の JTA トランザクションマ"
+"ネージャを java:/TransactionManager の名前にバインドします。このサービスは "
+"CORBA ORB サービスの存在に依存し、JacORB を基礎の ORB 実装として使用しなけれ"
+"ばなりません。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:57
+#, no-c-format
+msgid "There are two instances of this service:"
+msgstr "このサービスには 2 つのインスタンスがあります："
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:62
+#, no-c-format
+msgid ""
+"distributed: this uses the JTS enabled transaction manager implementation "
+"and hence supports distributed transactions and recovery. To configure this "
+"use the <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname> class. This is the default configuration."
+msgstr ""
+"分散：JTS が使用可能なトランザクションマネージャ実装を使用するため、分散トラ"
+"ンザクションおよびリカバリをサポートします。<classname>com.arjuna.ats."
+"jbossatx.jts.TransactionManagerService</classname> クラスを使用して設定しま"
+"す。これがデフォルトの設定になります。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:67
+#, no-c-format
+msgid ""
+"local: this uses the purely local JTA implementation. To configure this use "
+"the <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
+"classname> class."
+msgstr ""
+"ローカル：ローカルの JTA 実装を使用します。<classname>com.arjuna.ats."
+"jbossatx.jta.TransactionManagerService</classname> クラスを使用して設定しま"
+"す。"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:73
+#, no-c-format
+msgid "Ensuring Transactional Context is Propagated to the Server"
+msgstr "トランザクションコンテキストがサーバーへ伝搬されるようにする"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:74
+#, no-c-format
+msgid ""
+"It is possible to coordinate transactions from a coordinator which is not "
+"located within the JBoss server (e.g. using transactions created by an "
+"external OTS server). To ensure the transaction context is propagated via "
+"JRMP invocations to the server, the transaction propagation context factory "
+"needs to be explicitly set for the JRMP invoker proxy. This is done as "
+"follows:"
+msgstr ""
+"JBoss サーバー内に存在しないコーディネータからトランザクションをコーディネー"
+"トすることは可能です（例：外部の OTS サーバーによって作成されたトランザクショ"
+"ンを使用）。トランザクションコンテキストが JRMP 呼び出しを介してサーバーに伝"
+"搬されるようにするため、JRMP 呼び出し側のプロキシに対してトランザクション伝搬"
+"のコンテキストファクトリを次のように明示的に設定する必要があります。"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/An_Introduction_to_the_JTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/An_Introduction_to_the_JTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/An_Introduction_to_the_JTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,153 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr "Uma introdução para o JTA"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr "O API da Transação Java"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:9
+#, no-c-format
+msgid ""
+"The interfaces specified by the many transaction standards are typically too "
+"low-level for most application programmers. Therefore, Sun Microsystems has "
+"specified higher-level interfaces to assist in the development of "
+"distributed transactional applications. Note, these interfaces are still low-"
+"level, and require, for example, the programmer to be concerned with state "
+"management and concurrency for transactional application. In addition, they "
+"are geared more for applications which require XA resource integration "
+"capabilities, rather than the more general resources which the other APIs "
+"allow."
+msgstr ""
+"As interfaces especificadas por muitas transações padrões são tipicamente de "
+"um nível bem baixo para programadores de aplicativo. Portanto, os Micro-"
+"sistemas possuem interfaces de alto nível especificadas para assistir no "
+"desenvolvimento dos aplicativos transacionais distribuídos. Perceba que "
+"estas interfaces continuam a possuir um nível baixo e solicitam, por "
+"exemplo, que o programador se preocupe com o gerenciamento e simultaneidade "
+"de estado para o aplicativo transacional. Adicionado a isto, elas são mais "
+"adequadas para aplicativos que requerem as capacidades de integração do "
+"recurso XA, ao invés de recursos mais gerais do que outros APIs "
+"permitiriam. "
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:12
+#, no-c-format
+msgid ""
+"With reference to [JTA99], distributed transaction services typically "
+"involve a number of participants:"
+msgstr ""
+"Normalmente, os serviços de transação distribuída envolvem um número de "
+"participantes com a referência ao [JTA99]:"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:17
+#, no-c-format
+msgid ""
+"Application server: which provides the infrastructure required to support "
+"the application run-time environment which includes transaction state "
+"management, for example, an EJB server."
+msgstr ""
+"Servidor do Aplicativo: que fornece a infra-estrutura solicitada para "
+"suportar o ambiente do período de execução do aplicativo que inclui o "
+"gerenciamento do estado de transação, como por exemplo: um servidor EJB."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:22
+#, no-c-format
+msgid ""
+"Transaction manager: provides the services and management functions required "
+"to support transaction demarcation, transactional resource management, "
+"synchronisation and transaction context propagation."
+msgstr ""
+"Gerenciador da Transação: fornece as funções de gerenciamento e serviços "
+"solicitadas para suportar a demarcação da transação, o gerenciamento do "
+"recurso transacional, sincronização e propagação do contexto transacional."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:27
+#, no-c-format
+msgid ""
+"Resource manager: (through a resource adapter<footnote> <para> A Resource "
+"Adapter is used by an application server or client to connect to a Resource "
+"Manager. JDBC drivers which are used to connect to relational databases are "
+"examples of Resource Adapters. </para> </footnote>) provides the application "
+"with access to resources. The resource manager participates in distributed "
+"transactions by implementing a transaction resource interface used by the "
+"transaction manager to communicate transaction association, transaction "
+"completion and recovery."
+msgstr ""
+"Gerenciador de recurso: (através de um adaptador de recurso<footnote> "
+"<para>O Adaptador de Recurso é usado por um servidor de aplicativo ou "
+"cliente para conectar-se a um Gerenciador de Recurso. Os JDBC drivers, que "
+"são usados para conectar os bancos de dados relacionais, são exemplos dos "
+"Adaptadores de Recursos. </para> </footnote>) fornece o aplicativo com "
+"acesso aos recursos. O gerenciador de recurso participa nas transações "
+"distribuídas pela implementação de uma interface de recurso de transação "
+"usada pelo gerenciador da transação para comunicar-se com a associação, "
+"finalização e recuperação."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:36
+#, no-c-format
+msgid ""
+"A communication resource manager (CRM): supports transaction context "
+"propagation and access to the transaction service for incoming and outgoing "
+"requests."
+msgstr ""
+"O gerenciador de recurso de comunicação communication resource manager "
+"(CRM): suporta a propagação do contexto de transação e acessa o serviço de "
+"transação para solicitações de chegada e saída."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:41
+#, no-c-format
+msgid ""
+"From the transaction manager’s perspective, the actual implementation of the "
+"transaction services does not need to be exposed; only high-level interfaces "
+"need to be defined to allow transaction demarcation, resource enlistment, "
+"synchronization and recovery process to be driven from the users of the "
+"transaction services. The JTA is a high-level application interface that "
+"allows a transactional application to demarcate transaction boundaries, and "
+"contains also contains a mapping of the X/Open XA protocol."
+msgstr ""
+"A partir da perspectiva do gerenciador de transação, a implementação atual "
+"dos serviços de transação não precisam estar expostos, apenas as interfaces "
+"de alto nível precisam estar definidas para permitir a demarcação da "
+"transação, alistamento de recurso, sincronização e processo de recuperação "
+"para serem dirigidas a partir dos usuários dos serviços de transação. O JTA "
+"é uma interface do aplicativo de alto nível que permite o aplicativo "
+"transacional a demarcar os limites da transação e contém também um "
+"mapeamento do protocolo X/Open XA."
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:45
+#, no-c-format
+msgid ""
+"The JTA support provided by JBossJTA is compliant with the 1.0.1 "
+"specification."
+msgstr ""
+"O suporte JTA fornecido pelo JBOssJTA é complacente à especificação 1.0.1."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Author_Group.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Author_Group.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,23 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Book_Info.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Book_Info.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,50 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"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
+#, fuzzy, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide CP04"
+msgstr "Guia dos Programadores JTA das Transações do JBoss"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "para Uso com a Plataforma do Aplicativo do JBoss Enterprise 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+"Este livro fala a respeito das Transações JTA a partir da visualização do "
+"programador."
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Configuring_JBossJTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Configuring_JBossJTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Configuring_JBossJTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,145 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr "Configuração do JBossJTA"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:8
+#, no-c-format
+msgid "Configuring options"
+msgstr "Opções de Configuração"
+
+#. Tag: para
+#: Configuring_JBossJTA.xml:9
+#, no-c-format
+msgid ""
+"The following table shows the configuration features, with default values "
+"shown in italics. For more detailed information, the relevant section "
+"numbers are provided."
+msgstr ""
+"A seguinte tabela apresenta os recursos da configuração, com os valores "
+"padrões apresentados em itálico. Para uma melhor informação, os números da "
+"seção relevante são fornecidas."
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:13
+#, no-c-format
+msgid "JBossJTA configuration options."
+msgstr "Opções de configuração JBossJTA."
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:17
+#, no-c-format
+msgid "Configuration Name"
+msgstr "Nome da Configuração"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:20
+#, no-c-format
+msgid "Possibile Values"
+msgstr "Valores Possíveis"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:23
+#, no-c-format
+msgid "Relevant Section"
+msgstr "Seção Relevante"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:30
+#, no-c-format
+msgid "com.arjuna.ats.jta.supportSubtransactions"
+msgstr "com.arjuna.ats.jta.supportSubtransactions"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr "SIM/NÃO"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr "com.arjuna.ats.jta.jtaTMImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:43
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr "com.arjuna.ats.jta.jtaUTImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:53
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr "com.arjuna.ats.jta.xaBackoffPeriod"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr "com.arjuna.ats.jdbc.isolationLevel"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr "Qualquer nível de isolação JDBC suportado."
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr "verdadeiro/falso"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr "Capítulo 3"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Examples.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Examples.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Examples.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,834 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr "Exemplos"
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr "Exemplo JDBC"
+
+#. Tag: para
+#: Examples.xml:9
+#, no-c-format
+msgid ""
+"The following code illustrates many of the points described above (note that "
+"for simplicity, much error checking code has been remove). This example "
+"assumes that you are using the transactional JDBC driver provided with "
+"JBossTS. For details about how to configure and use this driver see the "
+"previous Chapter."
+msgstr ""
+"O seguinte código ilustra muitos pontos descritos acima (perceba que para "
+"simplicidade, a maioria do código de checagem de erro foi removido). Este "
+"exemplo assume que você está usando o driver JDBC transacional fornecido com "
+"o JBossTS. Para maiores detalhes em como configurar e usar este driver, por "
+"favor consulte o Capítulo anterior."
+
+#. Tag: screen
+#: Examples.xml:12
+#, no-c-format
+msgid ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+msgstr ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+
+#. Tag: title
+#: Examples.xml:16
+#, no-c-format
+msgid "Failure recovery example"
+msgstr "Exemplo de recuperação de falha"
+
+#. Tag: para
+#: Examples.xml:17
+#, no-c-format
+msgid ""
+"This class implements the <interfacename>XAResourceRecovery</interfacename> "
+"interface for <code>XAResources</code>. The parameter supplied in "
+"setParameters can contain arbitrary information necessary to initialize the "
+"class once created. In this instance it contains the name of the property "
+"file in which the db connection information is specified, as well as the "
+"number of connections that this file contains information on (separated "
+"by ;)."
+msgstr ""
+"Esta classe implementa a interface <interfacename>XAResourceRecovery</"
+"interfacename> para <code>XAResources</code>. O parâmetro fornecido no "
+"setParameters pode conter uma informação necessária para inicializar a "
+"classe uma vez que for criada. Nesta instância contém o nome do arquivo da "
+"propriedade em que a informação da conexão db é especificada, assim como o "
+"número de conexões que este arquivo contém informação (separado por ponto e "
+"vírgula). "
+
+#. Tag: para
+#: Examples.xml:21
+#, no-c-format
+msgid ""
+"This is only an <emphasis>example</emphasis> of the sorts of things an "
+"<code>XAResourceRecovery</code> implementer could do. This implementation "
+"uses a property file that is assumed to contain sufficient information to "
+"recreate connections used during the normal run of an application so that we "
+"can perform recovery on them. It is not recommended that information such as "
+"user name and password appear in such a raw text format as it opens up a "
+"potential security hole."
+msgstr ""
+"Este é apenas um <emphasis>exemplo</emphasis> de todos os tipos do "
+"implementador <code>XAResourceRecovery</code> pode realizar. Esta "
+"implementação usa o arquivo de propriedade que é assumido a conter "
+"informação suficiente para recriar conexões usadas durante a execução normal "
+"de um aplicativo. Desta maneira, podemos executar a recuperação nas mesmas. "
+"Não recomendamos que a informação como o nome do usuário e a senha neste "
+"tipo de formato de texto cru uma vez que isto abre um potencial espaço de "
+"segurança."
+
+#. Tag: para
+#: Examples.xml:25
+#, no-c-format
+msgid ""
+"The db parameters specified in the property file are assumed to be in the "
+"format:"
+msgstr ""
+"Presume-se que os parâmetros db especificados no arquivo de propriedade "
+"estão no seguinte formato:"
+
+#. Tag: para
+#: Examples.xml:30
+#, no-c-format
+msgid "DB_x_DatabaseURL="
+msgstr "DB_x_DatabaseURL="
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr "DB_x_DatabaseUser="
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr "DB_x_DatabasePassword="
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr "DB_x_DatabaseDynamicClass="
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr "Onde x é o número da informação de conexão."
+
+#. Tag: para
+#: Examples.xml:54
+#, no-c-format
+msgid ""
+"Some error handling code has been removed from this text for ease of "
+"readability purposes."
+msgstr ""
+"Alguns erros no código de manuseio foram removidos deste texto para "
+"facilitar os propósitos de readaptação."
+
+#. Tag: screen
+#: Examples.xml:58
+#, no-c-format
+msgid ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+msgstr ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+
+#. Tag: para
+#: Examples.xml:59
+#, no-c-format
+msgid ""
+"The class <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> may be used to create a new connection "
+"to the database using the same parameters that were used to create the "
+"initial connection."
+msgstr ""
+"A classe <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> pode ser usada para criar uma nova "
+"conexão ao banco de dados usando os mesmos parâmetros dos utilizados para "
+"criação da conexão inicial."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
===================================================================
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/JDBC_and_Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/JDBC_and_Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/JDBC_and_Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,1005 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr "JDBC e Transações"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr "Usando o driver JDBC transacional"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:9
+#, no-c-format
+msgid ""
+"JBossJTA supports the construction of both local and distributed "
+"transactional applications which access databases using the JDBC 2.0 APIs. "
+"JDBC 2.0 supports two-phase commit of transactions, and is similar to the XA "
+"X/Open standard. The JDBC 2.0 support is found in the com.arjuna.ats.jdbc "
+"package."
+msgstr ""
+"O JBossJTA suporta a construção de ambos aplicativos transacional e "
+"distribuídos que acessam os bancos de dados usando o JDBC 2.0 APIs. O JDBC "
+"2.0 suporta as transações de confirmação de duas fases e é parecido ao "
+"padrão XA X/Open. O suporte JDBC 2.0 é encontrado no pacote com.arjuna.ats."
+"jdbc. "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:12
+#, no-c-format
+msgid ""
+"The JDBC 2.0 support has been tested with the following drivers and "
+"databases:"
+msgstr "O suporte JDBC foi testado com os seguintes drivers e banco de dados:"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr "Oracle 8.1.6/8.1.7, 9i e 10g thin driver."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr "MS SQL Server 2000 native driver."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:27
+#, no-c-format
+msgid "In the past we have qualified against:"
+msgstr "Antes nós éramos qualificados em referência ao:"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:32
+#, no-c-format
+msgid "Merant’s Sequelink 5.1 with Oracle 8.1.6"
+msgstr "Merant’s Sequelink 5.1 com Oracle 8.1.6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr "Cloudscape 3.6 com o próprio banco de dados do Cloudscape."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:42
+#, no-c-format
+msgid ""
+"However, these drivers and databases are no longer part of our supported "
+"platforms. They may continue to work with JBossTS, but we cannot make that "
+"guarantee."
+msgstr ""
+"No entanto, estes drivers e banco de dados não fazem mais parte de nossas "
+"plataformas suportadas. Eles continuam a trabalhar com o JBossTS, mas não "
+"podemos garantir isto."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:46
+#, no-c-format
+msgid "Managing transactions"
+msgstr "Gerenciamento de transações"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:47
+#, no-c-format
+msgid ""
+"JBossJTA must be able to associate work performed on a JDBC connection with "
+"a specific transaction. Therefore, implicit transaction propagation and/or "
+"indirect transaction management must be used by applications, i.e., for each "
+"JDBC connection it must be possible for JBossJTA to determine the invoking "
+"thread’s current transaction context."
+msgstr ""
+"O JBossJTA deve estar associado ao trabalho desempenhado na conexão JDBC com "
+"a transação específica. Portanto, a propagação da transação implícita e/ou o "
+"gerenciamento da transação indireta deve ser usado pelos aplicativos, por "
+"exemplo: para cada conexão JDBC deve ser possível para o JBossJTA determinar "
+"o contexto de transação atual da invocação do segmento."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:52
+#, no-c-format
+msgid "Restrictions"
+msgstr "Restrições"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:53
+#, no-c-format
+msgid ""
+"The following restrictions are imposed by limitations in the JDBC "
+"specifications and by JBossJTA to ensure that transactional interactions "
+"with JDBC databases can be correctly managed:"
+msgstr ""
+"As seguintes restrições são impostas pelas limitações nas especificações "
+"JDBC e pelo JBossJTA, para garantia que as interações transacionais com os "
+"bancos de dados JDBC podem ser corretamente gerenciadas:"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:57
+#, no-c-format
+msgid ""
+"Nested transactions are not supported by JDBC 2.0. If an attempt is made to "
+"use a JDBC connection within a subtransaction, JBossJTA will throw a "
+"suitable exception and no work will be allowed on that connection. However, "
+"if you wish to have nested transactions, then you can set the <property>com."
+"arjuna.ats.jta.supportSubtransactions</property> property to YES."
+msgstr ""
+"As transações aninhadas não são suportadas pelo JDBC 2.0. Caso uma tentativa "
+"seja realizada para usar a conexão JDBC com a sub-transação, o JBossJTA "
+"lançará uma exceção adequada e nenhum trabalho será permitido naquela "
+"conexão. No entanto, caso você deseje ter transações aninhadas, você poderá "
+"configurar a propriedade <property>com.arjuna.ats.jta."
+"supportSubtransactions</property> para SIM."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:63
+#, no-c-format
+msgid "Transactional drivers"
+msgstr "Drivers Transacionais"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:64
+#, no-c-format
+msgid ""
+"The JBossJTA approach to incorporating JDBC connections within transactions "
+"is to provide transactional JDBC drivers through which all interactions "
+"occur. These drivers intercept all invocations and ensure that they are "
+"registered with, and driven by, appropriate transactions. There is a single "
+"type of transactional driver through which any JDBC driver can be driven; "
+"obviously if the database is not transactional then ACID properties cannot "
+"be guaranteed. This driver is <code>com.arjuna.ats.jdbc.TransactionalDriver</"
+"code>, which implements the <interfacename>java.sql.Driver</interfacename> "
+"interface."
+msgstr ""
+"A abordagem JBossJTA para incorporação das conexões JDBC com as transações, "
+"é para fornecer drivers JDBC transacionais pelos quais todas as interações "
+"ocorreram. Estes drivers interceptam todas as invocações e garantem que elas "
+"são registradas e dirigidas pelas transações apropriadas. Existe um tipo "
+"único de driver de transação pelo qual qualquer driver JDBC pode ser "
+"dirigido. E, caso o banco de dados não seja transacional, as propriedades "
+"não podem ser garantidas. Este drive é o <code>com.arjuna.ats.jdbc."
+"TransactionalDriver</code>, do qual implementa a interface "
+"<interfacename>java.sql.Driver</interfacename>."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:68
+#, no-c-format
+msgid "Loading drivers"
+msgstr "Carregamento de drivers"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:69
+#, no-c-format
+msgid ""
+"The driver may be directly instantiated and used within an application. For "
+"example:"
+msgstr ""
+"O driver pode ser diretamente instanciado e usado com um aplicativo. Por "
+"exemplo:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:73
+#, no-c-format
+msgid "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+msgstr "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:74
+#, no-c-format
+msgid ""
+"They can be registered with the JDBC driver manager (<code>java.sql."
+"DriverManager</code>) by adding them to the Java system properties. The "
+"<property>jdbc.drivers</property> property contains a list of driver class "
+"names, separated by colons, that are loaded by the JDBC driver manager when "
+"it is initialized."
+msgstr ""
+"Eles podem ser registrados com o gerenciador de driver JDBC (<code>java.sql."
+"DriverManager</code>) pela adição dos mesmos às propriedades do sistema "
+"Java. A propriedade <property>jdbc.drivers</property> contém uma lista de "
+"nomes de classes do driver, separada por dois pontos, do quais estão "
+"carregados pelo carregador do driver JDBC quando isto for inicializado."
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:77
+#, no-c-format
+msgid ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+msgstr ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:78
+#, no-c-format
+msgid ""
+"Alternatively, the <methodname>Class.forName()</methodname> method may be "
+"used to load the driver or drivers:"
+msgstr ""
+"Alternativamente, o método <methodname>Class.forName()</methodname> pode ser "
+"usado para carregar o driver e drivers:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:82
+#, no-c-format
+msgid ""
+"Calling <methodname>Class.forName()</methodname> will automatically register "
+"the driver with the JDBC driver manager. It is also possible to explicitly "
+"create an instance of the JDBC driver:"
+msgstr ""
+"A chamada do <methodname>Class.forName()</methodname> registrará "
+"automaticamente o driver com o gerenciador do driver JDBC. É possível também "
+"criar explicitamente uma instância do driver JDBC:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:85
+#, no-c-format
+msgid ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+msgstr ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:86
+#, no-c-format
+msgid ""
+"When you have loaded a driver, it is available for making a connection with "
+"a DBMS."
+msgstr ""
+"Quando você houver carregado um driver, ele estará disponível para "
+"realização de uma conexão com um DBMS."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:92
+#, no-c-format
+msgid "Connections"
+msgstr "Conexões"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:93
+#, no-c-format
+msgid ""
+"In this section we shall discuss the notion of transactional JDBC "
+"connections, how they are managed within JBossJTA and the implications on "
+"using them within an application."
+msgstr ""
+"Nós discutiremos nesta seção a noção das conexões JDBC transacionais, como "
+"elas são gerenciadas com o JBossJTA e as implicações de uso das mesmas com "
+"um aplicativo."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:97
+#, no-c-format
+msgid "Making the connection"
+msgstr "Realizando uma conexão"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:98
+#, no-c-format
+msgid ""
+"Because JDBC connectivity in JBossJTA works by simply providing a new JDBC "
+"driver, application code can remain relatively the same to that when not "
+"using transactions. Typically, the application programmer need only start "
+"and terminate transactions."
+msgstr ""
+"Devido à conectividade no JBossJTA fornecendo apenas um novo driver JDBC, o "
+"código do aplicativo pode manter-se relativamente o mesmo àquele, quando não "
+"estiver utilizado as transações. Tipicamente, o programador do aplicativo "
+"precisa apenas inicializar e terminar as transações."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr "JDBC 2.0"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:104
+#, no-c-format
+msgid ""
+"Before describing the JDBC 2.0 support it is necessary to mention that the "
+"following properties can be set and passed to the JBossJTA driver (they are "
+"all located in the <classname>com.arjuna.ats.jdbc.TransactionalDriver</"
+"classname> class):"
+msgstr ""
+"Antes de descrevermos o suporte JDBC 2.0, é necessário mencionar que as "
+"propriedades podem ser configuradas e passadas ao driver JBossJTA (elas "
+"estão todas localizadas na classe <classname>com.arjuna.ats.jdbc."
+"TransactionalDriver</classname>):"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:110
+#, no-c-format
+msgid ""
+"<property>userName</property>: the user name to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>userName</property>: o nome do usuário quando tentando conectar-se "
+"ao banco de dados."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:115
+#, no-c-format
+msgid ""
+"<property>password</property>: the password to use when attempting to "
+"connect to the database."
+msgstr ""
+"<property>password</property>: a senha de uso quando tentando conectar-se ao "
+"banco de dados."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:120
+#, no-c-format
+msgid ""
+"<property>createDb</property>: if set to true, the driver will attempt to "
+"create the database when it connects. This may not be supported by all JDBC "
+"2.0 implementations."
+msgstr ""
+"<property>createDb</property>: caso configurado para verdadeiro, o driver "
+"tentará criar o banco de dados quando conectado. Isto poderá não ser "
+"suportado por todas as implementações 2.0."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:125
+#, no-c-format
+msgid ""
+"<property>dynamicClass</property>: this specifies a class to instantiate to "
+"connect to the database, rather than using JNDI."
+msgstr ""
+"<property>dynamicClass</property>: isto especifica a classe para instanciar "
+"a conexão ao banco de dados, ao invés de utilizar JNDI."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr "XADataSources"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:132
+#, no-c-format
+msgid ""
+"JDBC 2.0 connections are created from appropriate DataSources. Those "
+"connections which must participate within distributed transactions are "
+"obtained from <code>XADataSources</code>. Therefore, when using a JDBC 2.0 "
+"driver, JBossJTA will use the appropriate DataSource whenever a connection "
+"to the database is made. It will then obtain <code>XAResources</code> and "
+"register them with the transaction via the JTA interfaces. It is these "
+"<code>XAResources</code> which the transaction service will use when the "
+"transaction terminates in order to drive the database to either commit or "
+"rollback the changes made via the JDBC connection."
+msgstr ""
+"As conexões 2.0 são criadas a partir de Fontes de Dados especiais. Estas "
+"conexões, que devem participar com as transações distribuídas, são obtidas a "
+"partir dos <code>XADataSources</code>. Portanto, quando usando um driver "
+"JDBC 2.0, o JBossJTA usará a apropriada Fonte de Dados quando uma conexão ao "
+"banco de dados é efetuada. Isto então obterá o <code>XAResources</code> e "
+"registrará os mesmos com a transação através das interfaces JTA. Isto é, "
+"estes <code>XAResources</code> que o serviço de transação usará quando a "
+"transação for encerrada, de maneira que o driver do banco de dados tanto "
+"confirmar ou reverter as alterações realizadas através da conexão JDBC."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:136
+#, no-c-format
+msgid ""
+"There are two ways in which the JBossJTA JDBC 2.0 support can obtain "
+"<code>XADataSources</code>. These will be explained in the following "
+"sections. Note, for simplicity we shall assume that the JDBC 2.0 driver is "
+"instantiated directly by the application."
+msgstr ""
+"Existem duas maneiras em que o suporte JBossJTA JDBC 2.0 pode obter o "
+"<code>XADataSources</code>. Isto será explicado nas seguintes seções. "
+"Perceba que devemos assumir que o driver JDBC 2.0 é instanciado diretamente "
+"pelo aplicativo, para maior facilidade."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr "Nomeação Java e Interface do Diretório (JNDI)"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:141
+#, no-c-format
+msgid ""
+"In order to allow a JDBC driver to use arbitrary DataSources without having "
+"to know specific details about their implementations, DataSources are "
+"typically obtained from JNDI. A specific (XA)DataSource can be created and "
+"registered with an appropriate JNDI implementation, and the application (or "
+"JDBC driver) can later bind to and use it. Since JNDI only allows the "
+"application to see the (XA)DataSource as an instance of the interface (for "
+"example, <property>javax.sql.XADataSource</property>) rather than as an "
+"instance of the implementation class (for example, <property>com.mydb."
+"myXADataSource</property>), the application is not tied at build time to "
+"only use a specific (XA)DataSource implementation."
+msgstr ""
+"Com a finalidade de permitir um driver JDBC a usar uma Fonte de Dados "
+"adequada sem conhecer detalhes específicos sobre as implementações dos "
+"mesmos, as Fontes de Dados são normalmente obtidas a partir do JNDI. Um (XA)"
+"DataSource específico pode ser criado e registrado com uma implementação "
+"JNDI apropriada e a implicação (ou driver JDBC) pode mais tarde vincular e "
+"usar isto. Uma vez que o JNDI apenas permite o aplicativo a verificar o (XA)"
+"DataSource como uma instância da interface (por exemplo: <property>javax.sql."
+"XADataSource</property>) ao invés de uma instância de classe de "
+"implementação (por exemplo: <property>com.mydb.myXADataSource</property>), o "
+"aplicativo não é amarrado no período de construção para usar apenas uma "
+"implementação (XA)DataSource específica."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:145
+#, no-c-format
+msgid ""
+"To get the <classname>TransactionalDriver</classname> class to use a JNDI "
+"registered <code>XADataSource</code> it is first necessary to create the "
+"<code>XADataSource</code> instance and store it in an appropriate JNDI "
+"implementation. Details of how to do this can be found in the JDBC 2.0 "
+"tutorial available at JavaSoft. An example is show below:"
+msgstr ""
+"Para obter a classe <classname>TransactionalDriver</classname> para usar o "
+"JNDI registrado <code>XADataSource</code>, é primeiramente necessário criar "
+"a instância <code>XADataSource</code> e armazenar isto numa apropriada JNDI. "
+"Detalhes de como realizar isto podem ser encontrados no tutorial JDBC 2.0 "
+"disponível no JavaSoft. Confira o exemplo abaixo:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:148
+#, no-c-format
+msgid ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+msgstr ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:149
+#, no-c-format
+msgid ""
+"Where the <property>Context.INITIAL_CONTEXT_FACTORY</property> property is "
+"the JNDI way of specifying the type of JNDI implementation to use."
+msgstr ""
+"Onde a propriedade <property>Context.INITIAL_CONTEXT_FACTORY</property> é o "
+"caminho JNDI de especificação do tipo de implementação JNDI para uso."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:152
+#, no-c-format
+msgid ""
+"Then the application must pass an appropriate connection URL to the JDBC 2.0 "
+"driver:"
+msgstr ""
+"Então o aplicativo deve passar uma conexão URL apropriada para o driver JDBC "
+"2.0:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:155
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:156
+#, no-c-format
+msgid ""
+"The JNDI URL must be pre-pended with jdbc:arjuna: in order for the "
+"<code>ArjunaJDBC2Driver</code> to recognise that the DataSource must "
+"participate within transactions and be driven accordingly."
+msgstr ""
+"O JNDI URL deve ser pré-aguardado pelo jdbc:arjuna: com a finalidade do "
+"<code>ArjunaJDBC2Driver</code> reconhecer que a Fonte de Dados deve "
+"participar com as transações e ser dirigida de acordo."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:160
+#, no-c-format
+msgid "Dynamic class instantiation"
+msgstr "Instanciação da classe dinâmica"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:161
+#, no-c-format
+msgid ""
+"Many JDBC 2.0 implementations provide proprietary implementations of "
+"<interfacename>XADataSources</interfacename> that provide non-standard "
+"extensions to the specification. In order to allow the application to remain "
+"isolated from the actual JDBC 2.0 implementation it is using and yet "
+"continue to be able to use these extensions, JBossJTA hides the details of "
+"these proprietary implementations using dynamic class instantiation. In "
+"addition, the use of JNDI is not required when using this mechanism because "
+"the actual implementation of the <interfacename>XADataSource</interfacename> "
+"will be directly instantiated, albeit in a manner which will not tie an "
+"application or driver to a specific implementation. JBossJTA therefore has "
+"several classes which are for specific JDBC 2.0 implementations, and these "
+"can be selected at runtime by the application setting the "
+"<property>dynamicClass</property> property appropriately:"
+msgstr ""
+"Muitas implementações JDBC 2.0 fornecem implementações de propriedades das "
+"<interfacename>XADataSources</interfacename> que fornecem extensões não-"
+"padrões para a especificação. Com a finalidade de permitir o aplicativo a "
+"permanecer isolado da implementação JDBC 2.0 atual está usando e continuar "
+"apto a usar estas extensões, o JBossJTA oculta estes detalhes destas "
+"implementações de propriedade usando a instanciação da classe dinâmica. "
+"Adicionado a isto, o uso do JNDI não é requerido quando usando este "
+"mecanismo devido a implementação atual do <interfacename>XADataSource</"
+"interfacename> ser diretamente instanciada, embora seja numa maneira que não "
+"amarrará um aplicativo ou driver a uma implementação específica. Portanto, o "
+"JBossJTA possui diversas classes que são para implementações JDBC 2.0 "
+"específicas e isto pode ser selecionado no período de execução pelo "
+"aplicativo configurando a propriedade <property>dynamicClass</property> "
+"apropriada:"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:166
+#, no-c-format
+msgid "Dynamic Class property values for specific databases"
+msgstr ""
+"Valores de Propriedades de Classe Dinâmica para banco de dados específicos"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:170
+#, no-c-format
+msgid "Database Type"
+msgstr "Tipo de Banco de Dados"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:173
+#, no-c-format
+msgid "Property Name"
+msgstr "Nome da Propriedade"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:180
+#, no-c-format
+msgid "Cloudscape 3.6"
+msgstr "Cloudscape 3.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr "Sequelink 5.1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr "Oracle 8.1.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:207
+#, no-c-format
+msgid ""
+"As mentioned earlier, JBossTS no longer supports Cloudscape or Sequelink as "
+"part of the qualified drivers. Furthermore, we recommend using JNDI to "
+"obtain JDBC classes rather than the direct method described here."
+msgstr ""
+"Conforme mencionado anteriormente, o JBossTS não suporta mais o Cloudscape "
+"ou Sequelink como parte dos drivers qualificados. Além disso, recomendamos o "
+"uso do JNDI para obter as classes JDBC ao invés de método direto específico "
+"descrito aqui."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:211
+#, no-c-format
+msgid ""
+"The application code must specify which dynamic class the "
+"<code>TransactionalDriver</code> should instantiate when setting up the "
+"connection:"
+msgstr ""
+"O código do aplicativo deve especificar qual classe de dinâmica o "
+"<code>TransactionalDriver</code> deve instanciar quando configurando a "
+"conexão:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:214
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:216
+#, no-c-format
+msgid "Using the connection"
+msgstr "Usando a conexão"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:217
+#, no-c-format
+msgid ""
+"Once the connection has been established (for example, using the "
+"<methodname>java.sql.DriverManager.getConnection</methodname> method), all "
+"operations on the connection will be monitored by JBossJTA. Note, it is not "
+"necessary to use the transactional connection within transactions. If a "
+"transaction is not present when the connection is used, then operations will "
+"be performed directly on the database."
+msgstr ""
+"Uma vez que a conexão é estabelecida (por exemplo, usando o método "
+"<methodname>java.sql.DriverManager.getConnection</methodname>), todas as "
+"operações na conexão serão monitoradas pelo JBossJTA. Perceba que não é "
+"necessário usar a conexão transacional com as transações. Caso uma transação "
+"não esteja presente quando uma conexão é usada, as operações serão "
+"desempenhadas diretamente no banco de dados. "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr "O JDBC não suporta as sub-transações."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:226
+#, no-c-format
+msgid ""
+"Transaction timeouts can be used to automatically terminate transactions "
+"should the connection not be terminated within an appropriate period."
+msgstr ""
+"Os intervalos das transações podem ser usadas para finalizar automaticamente "
+"as transações, caso a transação não seja finalizada com um período "
+"apropriado."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:229
+#, no-c-format
+msgid ""
+"JBossJTA connections can be used within multiple different transactions "
+"simultaneously, for instance, different threads, with different notions of "
+"the current transaction, may use the same JDBC connection. JBossJTA does "
+"connection pooling for each transaction within the JDBC connection. So, "
+"although multiple threads may use the same instance of the JDBC connection, "
+"internally this may be using a different connection instance per "
+"transaction. With the exception of close, all operations performed on the "
+"connection at the application level will only be performed on this "
+"transaction-specific connection."
+msgstr ""
+"As conexões JBossJTA podem ser usadas com transações múltiplas diferentes "
+"simultaneamente. Por exemplo: segmentações diferentes, com diferentes noções "
+"da transação atual, pode ser usada a conexão JDBC. O JBossJTA realiza o pool "
+"de conexão para cada transação com a conexão JDBC. Desta forma, mesmo que "
+"múltiplos segmentações sejam usadas com a mesma instância da conexão JDBC, "
+"internamente ela pode estar usando uma instância de conexão diferente por "
+"transação. Com a exceção próxima, todas as operações executadas na conexão "
+"no nível do aplicativo será apenas executada nesta conexão de transação "
+"especificada. "
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:232
+#, no-c-format
+msgid ""
+"JBossJTA will automatically register the JDBC driver connection with the "
+"transaction via an appropriate resource . When the transaction terminates, "
+"this resource will be responsible for either committing or rolling back any "
+"changes made to the underlying database via appropriate calls on the JDBC "
+"driver."
+msgstr ""
+"O JBossJTA irá automaticamente registrar a conexão do driver JDBC com a "
+"transação através de um recurso apropriado. Quando a transação for "
+"finalizada, este recurso será responsável por tanto a confirmação ou "
+"reversão de qualquer alteração feita no banco de dados adjacente através das "
+"chamadas apropriadas no driver JDBC."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:235
+#, no-c-format
+msgid ""
+"Once created, the driver and any connection can be used in the same way as "
+"any other JDBC driver or connection."
+msgstr ""
+"Uma vez criado, o driver e qualquer conexão podem ser usados da mesma "
+"maneira que outras conexões ou drivers JDBC."
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:238
+#, no-c-format
+msgid ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+msgstr ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:240
+#, no-c-format
+msgid "Connection pooling"
+msgstr "Pool de conexão"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:241
+#, no-c-format
+msgid ""
+"For each user name and password, JBossJTA will maintain a single instance of "
+"each connection for as long as that connection is in use. Subsequent "
+"requests for the same connection will get a reference to the originally "
+"created connection, rather than a new instance. Attempts to close the "
+"connection are allowed, but the connection will only actually be closed when "
+"all users (including transactions) have either finished with the connection, "
+"or issued close calls."
+msgstr ""
+"Para cada nome do usuário e senha, o JBossJTA manterá uma única instância de "
+"cada conexão pelo período em que a conexão estiver em uso. As solicitações "
+"subseqüentes para a mesma conexão obterão a referência à conexão original "
+"criada, ao invés de uma nova instância. As tentativas de encerrar a conexão "
+"são permitidas, mas a conexão será encerrada apenas quando todos os usuários "
+"(incluindo as transações) tenham finalizado com a conexão ou emitido "
+"chamadas próximas. "
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:246
+#, no-c-format
+msgid "Reusing connections"
+msgstr "Re-utilizando conexões"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:247
+#, no-c-format
+msgid ""
+"Some JDBC drivers allow the reuse of a connection for multiple different "
+"transactions once a given transaction has completed. Unfortunately this is "
+"not a common feature, and other drivers require a new connection to be "
+"obtained for each new transaction. By default, the JBossJTA transactional "
+"driver will always obtain a new connection for each new transaction. "
+"However, if an existing connection is available and is currently unused, it "
+"is possible to make JBossJTA reuse this connection. In order to do this, the "
+"reuseconnection=true option must be specified on the JDBC URL. For example:"
+msgstr ""
+"Alguns drivers JDBC permitem a re-utilização de uma conexão para transações "
+"múltiplas diferentes, uma vez que a transação gerada for completada. "
+"Infelizmente, isto não é um recurso comum e outros drivers solicitam uma "
+"nova conexão a ser obtida para cada nova transação. Pelo padrão, o driver "
+"transacional JBOssJTA irá sempre obter uma nova conexão para cada nova "
+"transação. No entanto, caso uma conexão atual não for utilizada, ela "
+"possivelmente fará com que o JBossJTA re-utilize esta conexão. Com a "
+"finalidade de realizar isto, a opção reuseconnection=true deve ser "
+"especificada no JDBC URL. Por exemplo:"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+"jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:253
+#, no-c-format
+msgid "Terminating the transaction"
+msgstr "Encerrando a transação"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:254
+#, no-c-format
+msgid ""
+"Whenever a transaction terminates (either explicitly by the application "
+"programmer, or implicitly when any associated transaction timeout expires) "
+"that has a JDBC connection registered with it, JBossJTA will drive the "
+"database (via the JDBC driver) to either commit or roll back any changes "
+"made to it. This happens transparently to the application."
+msgstr ""
+"A qualquer instante em que a transação encerrar (tanto explicitamente pelo "
+"programador do aplicativo ou implicitamente quando qualquer intervalo da "
+"transação associada expirar), da qual possui uma conexão registrada com "
+"isto, o JBossJTA dirigirá o banco de dados (através do driver JDBC) para "
+"tanto a confirmação ou reversão de qualquer alteração realizada nisto. Isto "
+"acontece claramente para o aplicativo."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr "AutoCommit"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:260
+#, no-c-format
+msgid ""
+"If <code>AutoCommit</code> of the <code>java.sql.Connection</code> is set to "
+"true for JDBC 1.0 then the execution of every SQL statement is a separate "
+"top-level transaction, and grouping multiple statements to be managed within "
+"a single OTS transaction is not possible. Therefore, JBossJTA will disable "
+"<code>AutoCommit</code> on JDBC 1.0 connections before they can be used. If "
+"auto commit is subsequently set to true by the application, JBossJTA will "
+"raise the <code>java.sql.SQLException</code>."
+msgstr ""
+"Caso o <code>AutoCommit</code> do <code>java.sql.Connection</code> seja "
+"configurado para verdadeiro no JDBC 1.0, a execução de cada expressão SQL é "
+"separada na transação de nível top e o agrupamento em expressões múltiplas a "
+"serem gerenciadas com a transação OTS única não será possível. Portanto, o "
+"JBossJTA desabilitará o <code>AutoCommit</code> nas conexões JDBS 1.0 antes "
+"delas serão utilizadas. Caso a confirmação automática for subseqüentemente "
+"configurada para verdadeiro pelo aplicativo, o JBossJTA irá levantar a "
+"<code>java.sql.SQLException</code>."
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:265
+#, no-c-format
+msgid "Setting isolation levels"
+msgstr "Configuração dos Níveis de Isolação"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:266
+#, no-c-format
+msgid ""
+"When using the JBossJTA JDBC driver, it may be necessary to set the "
+"underlying transaction isolation level on the XA connection. By default, "
+"this is set to <code>TRANSACTION_SERIALIZABLE</code>, but you may want to "
+"set this to something more appropriate for your application. In order to do "
+"this, set the <property>com.arjuna.ats.jdbc.isolationLevel</property> "
+"property to the appropriate isolation level in string form, for example, "
+"<code>TRANSACTION_READ_COMMITTED</code>, or "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+msgstr ""
+"Quando utilizando o driver JBossJTA, isto será necessário configurar o nível "
+"de isolação da transação na conexão XA. Pelo padrão, isto é configurado para "
+"<code>TRANSACTION_SERIALIZABLE</code>, mas você poderá configurar isto para "
+"algo mais apropriado para seu aplicativo. Com a finalidade de realizar isto, "
+"configure a propriedade <property>com.arjuna.ats.jdbc.isolationLevel</"
+"property> ao apropriado nível de isolação na forma de seqüência, por "
+"exemplo: <code>TRANSACTION_READ_COMMITTED</code> ou "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:271
+#, no-c-format
+msgid ""
+"At present this property applies to all XA connections created in the JVM."
+msgstr ""
+"No momento esta propriedade aplica-se a todas as conexões criadas no JVM."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Preface.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Preface.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,23 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"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 "Prefácio"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Revision_History.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Revision_History.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,29 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"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 "Histórico de Revisão"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/The_Resource_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/The_Resource_Manager.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/The_Resource_Manager.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,952 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: The_Resource_Manager.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "Teste"
+
+#. Tag: para
+#: The_Resource_Manager.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "Este é um paragrafo de teste."
+
+#. Tag: title
+#: The_Resource_Manager.xml:11
+#, no-c-format
+msgid "The XAResource Interface"
+msgstr "A Interface XAResource"
+
+#. Tag: para
+#: The_Resource_Manager.xml:12
+#, no-c-format
+msgid ""
+"Whereas some transaction specifications and systems define a generic "
+"resource which can be used to register arbitrary resources with a "
+"transaction, the JTA is much more XA specific. The <interfacename>javax."
+"transaction.xa.XAResource</interfacename> interface is a Java mapping of the "
+"<interfacename>XA</interfacename> interface. The <interfacename>XAResource</"
+"interfacename> interface defines the contract between a Resource Manager and "
+"a Transaction Manager in a distributed transaction processing environment. A "
+"resource adapter for a resource manager implements the "
+"<interfacename>XAResource</interfacename> interface to support association "
+"of a top-level transaction to a resource such as a relational database."
+msgstr ""
+"Enquanto que algumas especificações de transação e sistemas definem um "
+"recurso genérico que pode ser usado para registrar recursos arbitrários com "
+"a transação, o JTA é muito mais do que um específico XA. A interface "
+"<interfacename>javax.transaction.xa.XAResource</interfacename> é um "
+"mapeamento Java da interface <interfacename>XA</interfacename>. A interface "
+"<interfacename>XAResource</interfacename> define o contrato entre um "
+"Gerenciador de Recurso e um Gerenciador de Transação numa transação "
+"distribuída processando o ambiente. O adaptador de recurso para o "
+"gerenciador de recurso implementa a interface <interfacename>XAResource</"
+"interfacename> para suportar a associação de uma transação de nível top a um "
+"recurso tal como um banco de dados relacional."
+
+#. Tag: para
+#: The_Resource_Manager.xml:15
+#, no-c-format
+msgid ""
+"The <interfacename>XAResource</interfacename> interface can be supported by "
+"any transactional resource adapter that is intended to be used in an "
+"environment where transactions are controlled by an external transaction "
+"manager, for example, a database management system. An application may "
+"access data through multiple database connections. Each database connection "
+"is associated with an <code>XAResource</code> object that serves as a proxy "
+"object to the underlying resource manager instance. The transaction manager "
+"obtains an <code>XAResource</code> for each resource manager participating "
+"in a top-level transaction. It uses the start method to associate the "
+"transaction with the resource, and it uses the end method to disassociate "
+"the transaction from the resource."
+msgstr ""
+"A interface <interfacename>XAResource</interfacename> pode ser suportada por "
+"qualquer adaptador de recurso transacional que possui por intenção o uso num "
+"ambiente onde as transações são controladas por um gerenciador de transação "
+"externo, por exemplo: um sistema de gerenciamento de banco de dados. Um "
+"aplicativo poderá acessar os dados através de conexões múltiplas de banco de "
+"dados. Cada conexão de banco de dados é associada com um objeto "
+"<code>XAResource</code> que serve como um objeto Proxy à instância de "
+"gerenciador de recurso sublinhado. O gerenciador da transação obtém um "
+"<code>XAResource</code> para cada gerenciador de recurso participando numa "
+"transação de nível top. Isto usa o método inicial para associar a transação "
+"ao recurso e este usa o método final para desassociar a transação a partir "
+"do recurso."
+
+#. Tag: para
+#: The_Resource_Manager.xml:18
+#, no-c-format
+msgid ""
+"The resource manager is responsible for associating the transaction with all "
+"work performed on its data between the start and end invocations. At "
+"transaction commit time, these transactional resource managers are informed "
+"by the transaction manager to prepare, commit, or rollback the transaction "
+"according to the two-phase commit protocol."
+msgstr ""
+"O gerenciador de recurso é responsável pela associação da transação com "
+"todos os trabalhos executados no próprio banco de dados entre a "
+"inicialização e as invocações finalizadas. No período de confirmação da "
+"transação, estes gerenciadores de recurso transacional são informados pelo "
+"gerenciador da transação para preparar, confirmar ou reverter a transação de "
+"acordo ao protocolo de confirmação de duas fases."
+
+#. Tag: para
+#: The_Resource_Manager.xml:21
+#, no-c-format
+msgid ""
+"In order to be better integrated with Java, the <interfacename>XAResource</"
+"interfacename> differs from the standard <interfacename>XA</interfacename> "
+"interface in the following ways:"
+msgstr ""
+"Com o objetivo de estar melhor integrado com Java, o "
+"<interfacename>XAResource</interfacename> difere-se da interface "
+"<interfacename>XA</interfacename> padrão nas seguintes maneiras:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:26
+#, no-c-format
+msgid ""
+"The resource manager initialization is done implicitly by the resource "
+"adapter when the resource (connection) is acquired. There is no "
+"<code>xa_open</code> equivalent."
+msgstr ""
+"A inicialização do gerenciador de recurso é feita implicitamente pelo "
+"adaptador de recurso quando o recurso (conexão) for adquirido. Não existe "
+"<code>xa_open</code> equivalente."
+
+#. Tag: para
+#: The_Resource_Manager.xml:31
+#, no-c-format
+msgid ""
+"<code>Rmid</code> is not passed as an argument. Each <code>Rmid</code> is "
+"represented by a separate <code>XAResource</code> object."
+msgstr ""
+"O <code>Rmid</code> não é passado como um argumento. Cada <code>Rmid</code> "
+"é representado por um objeto <code>XAResource</code> separado."
+
+#. Tag: para
+#: The_Resource_Manager.xml:36
+#, no-c-format
+msgid ""
+"Asynchronous operations are not supported because Java supports multi-"
+"threaded processing and most databases do not support asynchronous "
+"operations."
+msgstr ""
+"As operações assíncronas não são suportadas uma vez que o Java suporta o "
+"processamento multi-segmentado e a maioria dos bancos de dados não suportam "
+"as operações assíncronas."
+
+#. Tag: para
+#: The_Resource_Manager.xml:41
+#, no-c-format
+msgid ""
+"Error return values that are caused by the transaction manager’s improper "
+"handling of the <code>XAResource</code> object are mapped to Java exceptions "
+"via the <classname>XAException</classname> class."
+msgstr ""
+"Os valores de retorno que são causados pelo manuseio impróprio do "
+"gerenciador da transação do objeto <code>XAResource</code> são mapeados às "
+"exceções Java através da classe <classname>XAException</classname>."
+
+#. Tag: para
+#: The_Resource_Manager.xml:46
+#, no-c-format
+msgid ""
+"The DTP concept of <emphasis>Thread of Control</emphasis> maps to all Java "
+"threads that are given access to the <code>XAResource</code> and "
+"<code>Connection</code> objects. For example, it is legal for two different "
+"threads to perform the start and end operations on the same "
+"<code>XAResource</code> object."
+msgstr ""
+"O conceito DTP do <emphasis>Controle de Segmentação</emphasis> mapeia todas "
+"as segmentações Java que concedem acesso aos objetos <code>XAResource</code> "
+"e <code>Connection</code>. Por exemplo, é permitido para duas segmentações "
+"diferentes executarem a inicialização e finalização de operações no mesmo "
+"objeto <code>XAResource</code>."
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr "Controle XAResource Extendido"
+
+#. Tag: para
+#: The_Resource_Manager.xml:53
+#, no-c-format
+msgid ""
+"By default, whenever an <code>XAResource</code> object is registered with a "
+"JTA compliant transaction service, you have no control over the order in "
+"which it will be invoked during the two-phase commit protocol, with respect "
+"to other <code>XAResource</code> objects. In JBossTS, however, there is "
+"support for controlling the order via the two interfaces <interfacename>com."
+"arjuna.ats.jta.resources.StartXAResource</interfacename> and "
+"<interfacename>com.arjuna.ats.jta.resources.EndXAResource</interfacename>. "
+"By inheriting your <code>XAResource</code> instance from either of these "
+"interfaces, you control whether an instance of your class will be invoked "
+"first or last, respectively."
+msgstr ""
+"Pelo padrão, a todo instante em que o objeto é registrado com um serviço de "
+"transação complacente JTA, você não possuirá controle sobre a ordem em que "
+"isto é invocado durante o protocolo de confirmação de duas fases, "
+"respeitando os outros objetos <code>XAResource</code>. No entanto, existe um "
+"suporte para controle da ordem através das duas interfaces "
+"<interfacename>com.arjuna.ats.jta.resources.StartXAResource</interfacename> "
+"e <interfacename>com.arjuna.ats.jta.resources.EndXAResource</interfacename> "
+"no JBossTS. Você pode controlar se é que uma instância de sua classe será "
+"invocada primeiramente ou por último respectivamente, pela herança de sua "
+"instância <code>XAResource</code>. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:58
+#, no-c-format
+msgid ""
+"Only one instance of each interface type may be registered with a specific "
+"transaction."
+msgstr ""
+"Apenas uma instância de cada tipo de interface pode ser registrada com a "
+"transação específica."
+
+#. Tag: para
+#: The_Resource_Manager.xml:62
+#, no-c-format
+msgid ""
+"In the TxCore manual we discussed the Last Resource Commit optimization "
+"(LRCO), whereby a single resource that is only one-phase aware (does not "
+"support prepare), can be enlisted with a transaction that is manipulating "
+"two-phase aware participants. This optimization is also supported within the "
+"JTA aspects of JBossTS."
+msgstr ""
+"No manual TxCore, discutimos a otimização da Confirmação do Último recurso "
+"(LRCO), segundo qual um recurso único que é apenas ciente de uma fase (não "
+"suporta o preparo), pode ser alistado com a transação que está manipulando "
+"os participantes cientes de duas fases. A otimização é também suportada com "
+"os aspectos JTA do JBossTS."
+
+#. Tag: para
+#: The_Resource_Manager.xml:65
+#, no-c-format
+msgid ""
+"In order to use the LRCO, your <interfacename>XAResource</interfacename> "
+"implementation must extend the <interfacename>com.arjuna.ats.jta.resources."
+"LastResourceCommitOptimisation</interfacename> marker interface (it provides "
+"no methods). When enlisting the resource via Transaction.enlistResource, "
+"JBossTS will ensure that only a single instance of this type of participant "
+"is used within each transaction. Your resource will be driven last in the "
+"commit protocol: no invocation of prepare will occur."
+msgstr ""
+"Com a finalidade de se usar o LRCO, sua implementação "
+"<interfacename>XAResource</interfacename> deve estender a interface de "
+"realização <interfacename>com.arjuna.ats.jta.resources."
+"LastResourceCommitOptimisation</interfacename> (isto não fornece métodos). "
+"Quando listando o recurso através da Transaction.enlistResource, o JBossTS "
+"garantirá que apenas uma única instância deste tipo de participante é "
+"utilizada com cada transação. O seu recurso será dirigido por último no "
+"protocolo de confirmação: nenhuma invocação de preparo ocorrerá."
+
+#. Tag: para
+#: The_Resource_Manager.xml:69
+#, no-c-format
+msgid ""
+"By default an attempt to enlist more than one instance of a "
+"<classname>LastResourceCommitOptimisation</classname> class will fail and "
+"false will be returned from <methodname>Transaction.enlistResource</"
+"methodname>. This behaviour can be overridden by setting the <property>com."
+"arjuna.ats.jta.allowMultipleLastResources</property> to true. However, "
+"before doing so you should read the Section on enlisting multiple one-phase "
+"aware resources."
+msgstr ""
+"Pelo padrão, a tentativa de listagem de mais de uma instância da classe "
+"<classname>LastResourceCommitOptimisation</classname> falhará e será "
+"retornada como falsa a partir do <methodname>Transaction.enlistResource</"
+"methodname>. Este comportamento pode ser substituído pela configuração da "
+"<property>com.arjuna.ats.jta.allowMultipleLastResources</property> para "
+"verdadeiro. No entanto, antes de realizar isto, você deverá ler a Seção na "
+"listagem dos recursos cientes de uma fase."
+
+#. Tag: para
+#: The_Resource_Manager.xml:73
+#, no-c-format
+msgid ""
+"In order to utilize the LRCO in a distributed environment, it is necessary "
+"to disable interposition support. It is still possible to use implicit "
+"context propagation."
+msgstr ""
+"Com o objetivo de se utilizar o LRCO num ambiente distribuído, é necessário "
+"desativar o suporte de inter-posição. É ainda possível o uso da propagação "
+"do contexto implícito."
+
+#. Tag: title
+#: The_Resource_Manager.xml:77
+#, no-c-format
+msgid "Enlisting multiple one-phase aware resources"
+msgstr "Listagem dos recursos cientes de uma fase múltiplos"
+
+#. Tag: para
+#: The_Resource_Manager.xml:78
+#, no-c-format
+msgid ""
+"As discussed in the Transaction Core documentation, in order to guarantee "
+"consistency (atomicity) of outcome between multiple participants (resources) "
+"within the same transaction, the two-phase commit protocol is used with a "
+"durable transaction log. In the case of possessing a single one-phase aware "
+"resource, it is still possible to achieve an atomic (all of nothing) outcome "
+"across resources by utilizing the Last Resource Commit Optimization, as "
+"explained earlier."
+msgstr ""
+"Conforme discutido na Documentação Principal da Transação, com o objetivo de "
+"garantir consistência (atomicidade) de resultado entre múltiplos "
+"participantes (recursos) com a mesma transação, o protocolo de confirmação "
+"de duas fases é usado com o log de transação durável. No caso de possessão "
+"de um único recurso ciente de uma fase, é ainda possível atingir um "
+"resultado atômico através dos recursos pela utilização da Otimização da "
+"Confirmação do Último Recurso, conforme explicado anteriormente."
+
+#. Tag: para
+#: The_Resource_Manager.xml:82
+#, no-c-format
+msgid ""
+"However, there may be situations where multiple one-phase aware resources "
+"are enlisted within the same transaction. For example, a legacy database "
+"running within the same transaction as a legacy JMS implementation. In these "
+"situations it is not possible to achieve atomicity of transaction outcome "
+"across multiple resources because none of them enter the prepare (waiting "
+"for final outcome) state: they commit or rollback immediately when "
+"instructed by the transaction coordinator, without knowledge of other "
+"resource states and without any way of undoing should subsequent resources "
+"make a different choice. This can result in data corruption or heuristic "
+"outcomes."
+msgstr ""
+"No entanto, podem existir outras situações onde recursos cientes de uma fase "
+"múltiplos são listados com a mesma transação. Por exemplo: um banco de dados "
+"de legação rodando com a mesma transação como uma implementação JMS de "
+"legação. Nestas situações não é possível atingir atomicidade do resultado da "
+"transação através dos recursos múltiplos, pois nenhum deles entra o estado "
+"preparado (na espera por resultado final): eles confirmam ou revertem "
+"imediatamente quando instruídos pelo coordenador de transação, sem o "
+"conhecimento de outros estados de recursos e sem qualquer maneira de "
+"desfazer isto, sendo que os recursos subseqüentes fazem uma escolha "
+"diferente. Isto pode resultar em dados de resultado heurístico ou de "
+"corrupção. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:85
+#, no-c-format
+msgid "In these situations we recommend one of the following approaches:"
+msgstr "Nestas situações recomendamos uma das seguintes abordagens:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:90
+#, no-c-format
+msgid ""
+"Wrap the resources in compensating transactions. See the Web Services "
+"transactions guides for further details."
+msgstr ""
+"Envolva os recursos compensando transações. Cheque os guias de transações "
+"dos Serviços da Web para maiores detalhes."
+
+#. Tag: para
+#: The_Resource_Manager.xml:95
+#, no-c-format
+msgid "Migrate the legacy implementations to two-phase aware equivalents."
+msgstr ""
+"Migração das implementações de legação para as cientes de duas fases "
+"equivalentes. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:100
+#, no-c-format
+msgid ""
+"In the cases where neither of these options are viable, JBossTS does support "
+"the enlistment of multiple one-phase aware resources within the same "
+"transaction. In order to do this, see the section on the Last Resource "
+"Commit Optimization."
+msgstr ""
+"No caso em que nenhuma destas opções sejam viáveis, o JBossTS não suporta a "
+"listagem de múltiplos recursos cientes de uma fase com a mesma transação. "
+"Com a finalidade de realizar isto, consulte a seção de Otimização de "
+"Confirmação do Último Recurso."
+
+#. Tag: para
+#: The_Resource_Manager.xml:104
+#, no-c-format
+msgid ""
+"Even when this support is enabled, JBossTS will issue warnings when it "
+"detects that the option has been enabled (\"You have chosen to enable "
+"multiple last resources in the transaction manager. This is transactionally "
+"unsafe and should not be relied upon.”) and when multiple one-phase "
+"resources are enlisted within the transaction (“This is transactionally "
+"unsafe and should not be relied on.”)."
+msgstr ""
+"Mesmo quando este suporte é ativado, o JBossTS emitirá avisos quando isto "
+"detectar que a opção foi ativada (\"Você escolheu ativar os últimos recursos "
+"múltiplos neste gerenciador de transação. Isto é transacionalmente perigoso "
+"e não deve ser levado em conta. ”) e quando os recursos de uma fase "
+"múltiplos são listados com a transação. (“Isto é transacionalmente perigoso "
+"e não deve ser levado em conta.”)"
+
+#. Tag: title
+#: The_Resource_Manager.xml:111
+#, no-c-format
+msgid "Opening a Resource Manager"
+msgstr "Abrindo um Gerenciador de Recurso"
+
+#. Tag: para
+#: The_Resource_Manager.xml:112
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface requires that the "
+"transaction manager initialize a resource manager (xa_open) prior to any "
+"other xa_ calls. JTA requires initialization of a resource manager to be "
+"embedded within the resource adapter that represents the resource manager. "
+"The transaction manager does not need to know how to initialize a resource "
+"manager; it is only responsible for informing the resource manager about "
+"when to start and end work associated with a transaction and when to "
+"complete the transaction. The resource adapter is responsible for opening "
+"(initializing) the resource manager when the connection to the resource "
+"manager is established."
+msgstr ""
+"A interface <interfacename>XA</interfacename> X/Open solicita que um "
+"gerenciador de transação inicialize um gerenciador de recurso (xa_open) "
+"antecedente a quaisquer outras xa_ calls. O JTA solicita a inicialização de "
+"um gerenciador de recurso a ser implementado com o adaptador de recurso que "
+"representa o gerenciador de recurso. O gerenciador de transação não precisa "
+"saber como inicializar um gerenciador de recurso. Isto é apenas responsável "
+"em informar o gerenciador de recurso a respeito da inicialização e "
+"finalização do trabalho associado com a transação e quando completar a "
+"transação. O adaptador de recurso é responsável em abrir (inicializar) o "
+"gerenciador de recurso quando a conexão para o gerenciador de recurso é "
+"estabelecida. "
+
+#. Tag: title
+#: The_Resource_Manager.xml:118
+#, no-c-format
+msgid "Closing a Resource Manager"
+msgstr "Encerrando um Gerenciador de Recurso"
+
+#. Tag: para
+#: The_Resource_Manager.xml:119
+#, no-c-format
+msgid ""
+"A resource manager is closed by the resource adapter as a result of "
+"destroying the transactional resource. A transaction resource at the "
+"resource adapter level is comprised of two separate objects:"
+msgstr ""
+"Um gerenciador de recurso é encerrado pelo adaptador de recurso como um "
+"resultado de destruição do recurso transacional. O recurso de transação no "
+"nível do adaptador de recurso é compreendido de dois objetos separados:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:124
+#, no-c-format
+msgid ""
+"An <code>XAResource</code> object that allows the transaction manager to "
+"start and end the transaction association with the resource in use and to "
+"coordinate transaction completion process."
+msgstr ""
+"Um objeto <code>XAResource</code> que permite o gerenciador de transação a "
+"inicializar e finalizar a transação associando com o recurso em uso e para "
+"coordenar o processo de finalização da transação."
+
+#. Tag: para
+#: The_Resource_Manager.xml:129
+#, no-c-format
+msgid ""
+"A connection object that allows the application to perform operations on the "
+"underlying resource (for example, JDBC operations on an RDBMS)."
+msgstr ""
+"Um objeto de conexão que permite o aplicativo a executar operações no "
+"recurso subjacente. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:134
+#, no-c-format
+msgid ""
+"Once opened, the resource manager is kept open until the resource is "
+"released (closed) explicitly. When the application invokes the connection’s "
+"close method, the resource adapter invalidates the connection object "
+"reference that was held by the application and notifies the application "
+"server about the close. The transaction manager should invoke the "
+"<methodname>XAResource.end</methodname> method to disassociate the "
+"transaction from that connection."
+msgstr ""
+"Uma vez aberto, o gerenciador de recurso é mantido aberto até que o recurso "
+"seja liberado (encerrado) explicitamente. Quando o aplicativo invoca o "
+"método de encerramento de conexão, o adaptador de recurso invalida a "
+"referência do objeto de conexão que estava mantido pelo aplicativo e "
+"notifica o servidor do aplicativo sobre o encerramento. O gerenciador de "
+"transação deve invocar o método para desassociar a transação a partir "
+"daquela conexão."
+
+#. Tag: para
+#: The_Resource_Manager.xml:137
+#, no-c-format
+msgid ""
+"The close notification allows the application server to perform any "
+"necessary cleanup work and to mark the physical XA connection as free for "
+"reuse, if connection pooling is in place."
+msgstr ""
+"A notificação encerrada permite que o servidor do aplicativo a executar "
+"qualquer limpeza de trabalho necessária e marcar a conexão XA física com "
+"livre para a re-utilização, caso o pool de conexão estiver em funcionamento."
+
+#. Tag: title
+#: The_Resource_Manager.xml:143
+#, no-c-format
+msgid "Threads of control"
+msgstr "Segmentações de controle"
+
+#. Tag: para
+#: The_Resource_Manager.xml:144
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface specifies that the "
+"transaction association related xa calls must be invoked from the same "
+"thread context. This thread-of-control requirement is not applicable to the "
+"object-oriented component-based application run-time environment, in which "
+"application threads are dispatched dynamically at method invocation time. "
+"Different threads may be using the same connection resource to access the "
+"resource manager if the connection spans multiple method invocation. "
+"Depending on the implementation of the application server, different threads "
+"may be involved with the same <code>XAResource</code> object. The resource "
+"context and the transaction context may be operated independent of thread "
+"context. This means that it is possible for different threads to be invoking "
+"the start and end methods."
+msgstr ""
+"A interface <interfacename>XA</interfacename> X/Open especifica que as "
+"chamadas xa de associação relacionadas da transação devem ser invocadas a "
+"partir do mesmo contexto. Esta solicitação de segmentação-de-controle não é "
+"aplicada ao mesmo ambiente de período de execução do aplicativo do "
+"componente baseado de objeto orientado, em que as segmentações do aplicativo "
+"são despachadas dinamicamente no período de invocação do método. Diferentes "
+"segmentações podem ser usadas com o mesmo recurso de conexão para acessar o "
+"gerenciador de recurso, caso a conexão realize o spam na invocação de método "
+"múltiplo. Dependendo da implementação do servidor do aplicativo, segmentos "
+"diferentes podem ser envolvidos com o mesmo objeto <code>XAResource</code>. "
+"O contexto do recurso e o contexto de transação podem ser operados "
+"independemente do contexto de segmentação. Isto significa que é possível que "
+"diferentes segmentações invoquem os métodos inicializar e finalizar."
+
+#. Tag: para
+#: The_Resource_Manager.xml:147
+#, no-c-format
+msgid ""
+"If the application server allows multiple threads to use a single "
+"<code>XAResource</code> object and the associated connection to the resource "
+"manager, it is the responsibility of the application server to ensure that "
+"there is only one transaction context associated with the resource at any "
+"point of time. Thus the <interfacename>XAResource</interfacename> interface "
+"requires that the resource managers be able to support the two-phase commit "
+"protocol from any thread context."
+msgstr ""
+"Caso o servidor do aplicativo permita que segmentações múltiplas usem um "
+"objeto <code>XAResource</code> único e a conexão associada a um gerenciador "
+"de recurso, é responsabilidade do aplicativo do servidor garantir que não há "
+"apenas um contexto associado com o recurso em qualquer instante. Desta "
+"forma, a interface <interfacename>XAResource</interfacename> solicita que os "
+"gerenciadores de recurso estejam aptos a suportar o protocolo de confirmação "
+"de duas fases a partir de qualquer contexto de segmentação."
+
+#. Tag: title
+#: The_Resource_Manager.xml:153
+#, no-c-format
+msgid "Transaction association"
+msgstr "Associação de Transação"
+
+#. Tag: para
+#: The_Resource_Manager.xml:154
+#, no-c-format
+msgid ""
+"Transactions are associated with a transactional resource via the start "
+"method, and disassociated from the resource via the <methodname>end</"
+"methodname> method. The resource adapter is responsible for internally "
+"maintaining an association between the resource connection object and the "
+"<code>XAResource</code> object. At any given time, a connection is "
+"associated with a single transaction, or it is not associated with any "
+"transaction at all. Because JTA does not support nested transactions it is "
+"an error for the start method to be invoked on a connection that is "
+"currently associated with a different transaction."
+msgstr ""
+"As transações são associadas com o recurso transacional através do método "
+"inicializar e desassociação a partir do recurso através do método "
+"<methodname>end</methodname>. O adaptador de recurso é responsável por "
+"manter internamente uma associação entre o objeto de conexão de recurso e um "
+"objeto <code>XAResource</code>. A qualquer instante dado, a conexão é "
+"associada com uma úncia transação ou ela não é associada com nenhuma "
+"transação. Uma vez que o JTA não suporta as transações aninhadas, não é "
+"correto que o método inicializar seja invocado numa conexão que é atualmente "
+"associada com uma transação diferente."
+
+#. Tag: para
+#: The_Resource_Manager.xml:157
+#, no-c-format
+msgid ""
+"Interleaving multiple transaction contexts using the same resource may be "
+"done by the transaction manager as long as start and end are invoked "
+"properly for each transaction context switch. Each time the resource is used "
+"with a different transaction, the method end must be invoked for the "
+"previous transaction that was associated with the resource, and start must "
+"be invoked for the current transaction context."
+msgstr ""
+"Os contextos de transação múltipla intercalados usando o mesmo recurso podem "
+"ser realizados pelo gerenciador de transação contanto que a inicialização e "
+"finalização sejam invocadas apropriadamente para cada troca de contexto de "
+"transação. A cada instante o recurso é usado com uma transação diferente, o "
+"método finalizar deve ser invocado para a transação prévia que foi associada "
+"com o recurso e a inicialização deve ser invocada com o contexto de "
+"transação atual."
+
+#. Tag: title
+#: The_Resource_Manager.xml:163
+#, no-c-format
+msgid "Externally controlled connections"
+msgstr "Conexões controladas externamente"
+
+#. Tag: para
+#: The_Resource_Manager.xml:164
+#, no-c-format
+msgid ""
+"For transactional application whose transaction states are managed by an "
+"application server, its resources must also be managed by the application "
+"server so that transaction association is performed properly. If an "
+"application is associated with a transaction, it is an error for the "
+"application to perform transactional work through the connection without "
+"having the connection’s resource object already associated with the global "
+"transaction. The application server must ensure that the <code>XAResource</"
+"code> object in use is associated with the transaction. This is done by "
+"invoking the <methodname>Transaction.enlistResource</methodname> method."
+msgstr ""
+"Para o aplicativo transacional, do qual os estados de transação estão "
+"gerenciados pelo servidor do aplicativo, os recursos dos mesmos também devem "
+"ser gerenciados pelo servidor do aplicativo de forma que a associação de "
+"transação é executada de maneira correta. Caso um aplicativo seja associado "
+"com uma transação para executar o trabalho transacional através da conexão "
+"sem possuir objetos de recursos de conexão já associada com a transação "
+"global. O servidor do aplicativo deve garantir que o objeto "
+"<code>XAResource</code> em uso é associado com a transação. Isto é feito "
+"pela invocação do método <methodname>Transaction.enlistResource</methodname>."
+
+#. Tag: para
+#: The_Resource_Manager.xml:167
+#, no-c-format
+msgid ""
+"If a server side transactional application retains its database connection "
+"across multiple client requests, the application server must ensure that "
+"before dispatching a client request to the application thread, the resource "
+"is enlisted with the application’s current transaction context. This implies "
+"that the application server manages the connection resource usage status "
+"across multiple method invocations."
+msgstr ""
+"Caso o aplicativo transacional ao lado do servidor reter a própria conexão "
+"do banco de dados através de solicitações de clientes múltiplos, o servidor "
+"do aplicativo deverá garantir que antes de despachar uma solicitação de "
+"cliente à segmentação do aplicativo, o recurso é listado com o contexto "
+"transacional atual do aplicativo. Isto significa que servidor do aplicativo "
+"gerencie o estado de uso do recurso de conexão através de invocações do "
+"método múltiplo. "
+
+#. Tag: title
+#: The_Resource_Manager.xml:173
+#, no-c-format
+msgid "Resource sharing"
+msgstr "Compartilhamento de Recurso"
+
+#. Tag: para
+#: The_Resource_Manager.xml:174
+#, no-c-format
+msgid ""
+"When the same transactional resource is used to interleave multiple "
+"transactions, it is the responsibility of the application server to ensure "
+"that only one transaction is enlisted with the resource at any given time. "
+"To initiate the transaction commit process, the transaction manager is "
+"allowed to use any of the resource objects connected to the same resource "
+"manager instance. The resource object used for the two-phase commit protocol "
+"does not need to have been involved with the transaction being completed."
+msgstr ""
+"Quando o mesmo recurso transacional é usado para transações múltiplas "
+"intercaladas, é responsabilidade do servidor do aplicativo garantir que "
+"apenas uma transação é listada com o recurso a qualquer período gerado. Para "
+"inicializar o processo de confirmação da transação, o gerenciador da "
+"transação possui a permissão para usar qualquer um dos objetos de recurso "
+"conectados à mesma instância do gerenciador de recurso. O objeto de recurso "
+"usado para o protocolo de confirmação de duas fases não precisa estar "
+"envolvido com a finalização da transação."
+
+#. Tag: para
+#: The_Resource_Manager.xml:177
+#, no-c-format
+msgid ""
+"The resource adapter must be able to handle multiple threads invoking the "
+"<interfacename>XAResource</interfacename> methods concurrently for "
+"transaction commit processing. For example, with reference to the code "
+"below, suppose we have a transactional resource <code>r1</code>. Global "
+"transaction <code>xid1</code> was started and ended with <code>r1</code>. "
+"Then a different global transaction <code>xid2</code> is associated with "
+"<code>r1</code>. In the meanwhile, the transaction manager may start the two "
+"phase commit process for <code>xid1</code> using <code>r1</code> or any "
+"other transactional resource connected to the same resource manager. The "
+"resource adapter needs to allow the commit process to be executed while the "
+"resource is currently associated with a different global transaction."
+msgstr ""
+"O adaptador de recurso deve estar apto a manusear invocações múltiplas "
+"invocando os métodos <interfacename>XAResource</interfacename> atuais para o "
+"processamento de confirmação da transação. Por exemplo: a referência ao "
+"código abaixo, vamos supor que nós possuimos um recurso transacional "
+"<code>r1</code>. A transação global <code>xid1</code> foi inicializada e "
+"finalizada com o <code>r1</code>. Então, uma transação diferente global "
+"<code>xid2</code> é associada com o <code>r1</code>. Enquanto isto, o "
+"gerenciador de transação pode inicializar o processo de confirmação de duas "
+"fases para o <code>xid1</code> usando o <code>r1</code> ou qualquer outro "
+"recurso transacional conectado ao mesmo gerenciador de recurso. O adaptador "
+"de recurso precisa permitir que o processo seja executado, enquanto o "
+"recurso é atualmente associado com uma transação globla diferente."
+
+#. Tag: screen
+#: The_Resource_Manager.xml:180
+#, no-c-format
+msgid ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+msgstr ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+
+#. Tag: title
+#: The_Resource_Manager.xml:184
+#, no-c-format
+msgid "Local and global transactions"
+msgstr "Transações globais e locais"
+
+#. Tag: para
+#: The_Resource_Manager.xml:185
+#, no-c-format
+msgid ""
+"The resource adapter must support the usage of both local and global "
+"transactions within the same transactional connection. Local transactions "
+"are transactions that are started and coordinated by the resource manager "
+"internally. The <interfacename>XAResource</interfacename> interface is not "
+"used for local transactions. When using the same connection to perform both "
+"local and global transactions, the following rules apply:"
+msgstr ""
+"O adaptador de recurso deve suportar o uso de ambas transações globais e "
+"locais com a mesma conexão transacional. As transações locais são "
+"transacionais, das quais são inicializadas e coordenadas pelo gerenciador de "
+"recurso internamente. A interface <interfacename>XAResource</interfacename> "
+"não é usada para transações locais. Quando utilizando a mesma conexão para "
+"executar ambas transações locais e globais, as seguintes regras serão "
+"aplicadas:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:190
+#, no-c-format
+msgid ""
+"The local transaction must be committed (or rolled back) before starting a "
+"global transaction in the connection."
+msgstr ""
+"A transação local deve ser confirmada (ou revertida) antes de inicializar "
+"uma transação global na conexão."
+
+#. Tag: para
+#: The_Resource_Manager.xml:195
+#, no-c-format
+msgid ""
+"The global transaction must be disassociated from the connection before any "
+"local transaction is started."
+msgstr ""
+"A transação global deve ser desassociada a partir da conexão antes de "
+"qualquer transação ser inicializada."
+
+#. Tag: title
+#: The_Resource_Manager.xml:203
+#, no-c-format
+msgid "Transaction timeouts"
+msgstr "Intervalos de transação"
+
+#. Tag: para
+#: The_Resource_Manager.xml:204
+#, no-c-format
+msgid ""
+"Timeout values can be associated with transactions in order to control their "
+"lifetime. If a transaction has not terminated (committed or rolled back) "
+"before the timeout value elapses, the transaction system will automatically "
+"roll it back. The <interfacename>XAResource</interfacename> interface "
+"supports a operation, which allows the timeout associated with the current "
+"transaction to be propagated to the resource manager and if supported, will "
+"override any default timeout associated with the resource manager. This can "
+"be useful when long running transactions may have lifetimes that would "
+"exceed the default and in which case, if the timeout were not altered, the "
+"resource manager would rollback before the transaction terminated and "
+"subsequently cause the transaction to roll back as well."
+msgstr ""
+"Os valores do intervalo podem ser associados com as transações com o "
+"objetivo de controlar o tempo de vida deles. Caso uma transação não tenha "
+"sido finalizada (confirmada ou revertida) antes do valor do intervalo "
+"exceder, o sistema de transação irá automaticamente reverter isto de volta. "
+"A interface <interfacename>XAResource</interfacename> suporta a operação, "
+"que permite o intervalo associado com a transação atual a ser propagada ao "
+"gerenciador de recurso e se suportada, substituirá qualquer intervalo padrão "
+"associado com o gerenciador de recurso. Isto pode ser útil quando as "
+"transações de exceção longa possam possuir um ciclo de vida que poderá "
+"exceder o padrão e neste caso, se o intervalo não for alterado, o "
+"gerenciador de recurso reverterá antes da transação ser finalizada e, "
+"subseqüentemente causará a reversão."
+
+#. Tag: para
+#: The_Resource_Manager.xml:207
+#, no-c-format
+msgid ""
+"If no timeout value is explicitly set for a transaction, or a value of 0 is "
+"specified, then an implementation specific default value may be used. In the "
+"case of JBossTS, how this default value is set depends upon which JTA "
+"implementation you are using."
+msgstr ""
+"Caso o valor de intervalo seja explicitamente configurado para a transação "
+"ou um valor de 0 for especificado, então uma implementação de valor "
+"específico poderá ser usada. No caso do JBossTS, uma vez que este valor "
+"padrão será configurado, dependerá de qual implementação JTA você estará "
+"usando. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:212
+#, no-c-format
+msgid ""
+"Local JTA: use the <property>com.arjuna.ats.arjuna.coordinator."
+"defaultTimeout</property> property value and give a timeout in seconds. The "
+"default value is 60 seconds."
+msgstr ""
+"JTA local: utiliza o valor da propriedade <property>com.arjuna.ats.arjuna."
+"coordinator.defaultTimeout</property> e concede um intervalo em segundos. O "
+"valor padrão é de 60 segundos."
+
+#. Tag: para
+#: The_Resource_Manager.xml:217
+#, no-c-format
+msgid ""
+"JTS: use the <property>com.arjuna.ats.jts.defaultTimeout</property> property "
+"value and give a timeout in seconds. The default value is 0, for instance, "
+"transactions do not timeout."
+msgstr ""
+"JTS: usa o valor da propriedade <property>com.arjuna.ats.jts.defaultTimeout</"
+"property> e concede um intervalo em segundos. O valor padrão é 0, por "
+"exemplo, as transações não possuem intervalo."
+
+#. Tag: para
+#: The_Resource_Manager.xml:222
+#, no-c-format
+msgid ""
+"Unfortunately there are situations where imposing the same timeout as the "
+"transaction on a resource manager may not be appropriate. For example, if "
+"the system administrator wishes to have control over the lifetimes on "
+"resource managers and does not want to (or cannot) allow that control to be "
+"passed to some external entity. At present JBossTS supports an all-or-"
+"nothing approach to whether or not <methodname>setTransactionTimeout</"
+"methodname> is called on <interfacename>XAResource</interfacename> instances."
+msgstr ""
+"Infelizmente existem situações onde a imposição do mesmo intervalo com a "
+"transação no gerenciador de recurso não será apropriada. Por exemplo: se um "
+"administrador de sistema deseja ter controle sobre os ciclos de vida dos "
+"gerenciadores de recurso e não quer (ou não pode) permitir que o controle "
+"seja passado à alguma entidade externa. Atualmente, o JBossTS suporta uma "
+"abordagem tudo-ou-nada para que o <methodname>setTransactionTimeout</"
+"methodname> seja ou não chamado nas instâncias do <interfacename>XAResource</"
+"interfacename>. "
+
+#. Tag: para
+#: The_Resource_Manager.xml:225
+#, no-c-format
+msgid ""
+"If the <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> "
+"property is set to true (the default) then it will be called on all "
+"instances. Alternatively, the <methodname>setXATransactionTimeoutEnabled</"
+"methodname> method of <classname>com.arjuna.ats.jta.common.Configuration</"
+"classname> can be used."
+msgstr ""
+"Caso a propriedade <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</"
+"property> seja configurada para verdadeiro (o padrão), ela chamará todas as "
+"instâncias. Alternativamente, o método "
+"<methodname>setXATransactionTimeoutEnabled</methodname> da <classname>com."
+"arjuna.ats.jta.common.Configuration</classname> poderá ser usado."
+
+#. Tag: title
+#: The_Resource_Manager.xml:231
+#, no-c-format
+msgid "Dynamic Registration"
+msgstr "Registro da Dinâmica"
+
+#. Tag: para
+#: The_Resource_Manager.xml:232
+#, no-c-format
+msgid ""
+"Dynamic registration is not supported in <interfacename>XAResource</"
+"interfacename> because of the following reasons:"
+msgstr ""
+"O registro da dinâmica não é suportado em <interfacename>XAResource</"
+"interfacename>, devido as seguintes razões:"
+
+#. Tag: para
+#: The_Resource_Manager.xml:237
+#, no-c-format
+msgid ""
+"In the Java component-based application server environment, connections to "
+"the resource manager are acquired dynamically when the application "
+"explicitly requests a connection. These resources are enlisted with the "
+"transaction manager on a needed basis."
+msgstr ""
+"No ambiente do servidor do aplicativo de componente baseado Java, as "
+"conexões para gerenciar o recurso são adquiridas dinamicamente quando o "
+"aplicativo solicita explicitamente uma conexão. Estes recursos são listados "
+"com o gerenciador de transação baseando-se na necessidade dos mesmos."
+
+#. Tag: para
+#: The_Resource_Manager.xml:242
+#, no-c-format
+msgid ""
+"If a resource manager requires a way to dynamically register its work to the "
+"global transaction, the implementation can be done at the resource adapter "
+"level via a private interface between the resource adapter and the "
+"underlying resource manager."
+msgstr ""
+"Caso um gerenciador de recurso solicite uma maneira para registrar "
+"dinamicamente o próprio trabalho à transação global, a implementação poderá "
+"ser feita no nível do adaptador de recurso através da interface privada "
+"entre o adaptador de recurso e o gerenciador de recurso adjacente."
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Transaction_Recovery.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Transaction_Recovery.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Transaction_Recovery.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,476 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr "Recuperação de Transação"
+
+#. Tag: title
+#: Transaction_Recovery.xml:10
+#, no-c-format
+msgid "Failure recovery"
+msgstr "Recuperação de Falha"
+
+#. Tag: para
+#: Transaction_Recovery.xml:11
+#, no-c-format
+msgid ""
+"During recovery, the Transaction Manager needs to be able to communicate to "
+"all resource managers that are in use by the applications in the system. For "
+"each resource manager, the Transaction Manager uses the "
+"<methodname>XAResource.recover</methodname> method to retrieve the list of "
+"transactions that are currently in a prepared or heuristically completed "
+"state. Typically, the system administrator configures all transactional "
+"resource factories that are used by the applications deployed on the system. "
+"An example of such a resource factory is the JDBC <code>XADataSource</code> "
+"object, which is a factory for the JDBC <code>XAConnection</code> objects."
+msgstr ""
+"Durante a recuperação, o Gerenciador da Transação precisa estar apto a "
+"comunicar-se com todos os gerenciadores de recurso que estão em uso pelos "
+"aplicativos no sistema. Para cada gerenciador de recurso, o Gerenciador de "
+"Transação usa o método <methodname>XAResource.recover</methodname> para "
+"recuperar a lista de transações que estão atualmente num estado preparado ou "
+"heurístico preparado. Normalmente, o administrador de sistema configura "
+"todas as criações de recurso transacional que são usadas pelos aplicativos "
+"implementados no sistema. Um exemplo de tal criação de recurso é o objeto "
+"<code>XADataSource</code>, que é a criação para os objetos "
+"<code>XAConnection</code>."
+
+#. Tag: para
+#: Transaction_Recovery.xml:14
+#, no-c-format
+msgid ""
+"Because <code>XAResource</code> objects are not persistent across system "
+"failures, the Transaction Manager needs to have some way to acquire the "
+"<code>XAResource</code> objects that represent the resource managers which "
+"might have participated in the transactions prior to the system failure. For "
+"example, a Transaction Manager might, through the use of JNDI lookup "
+"mechanism, acquire a connection from each of the transactional resource "
+"factories, and then obtain the corresponding <code>XAResource</code> object "
+"for each connection. The Transaction Manager then invokes the "
+"<methodname>XAResource.recover</methodname> method to ask each resource "
+"manager to return the transactions that are currently in a prepared or "
+"heuristically completed state."
+msgstr ""
+"Uma vez que os objetos não são persistentes através das falhas do sistema, o "
+"Gerenciador de Transação precisa ter alguma maneira de adquirir os objetos "
+"<code>XAResource</code> que representam os gerenciadores de recurso que "
+"possam ter participado da transação antes da falha do sistema. Por exemplo: "
+"um Gerenciador de Transação pode, através do uso do mecanismo de observação "
+"JNDI, adquirir uma conexão de cada criação de recurso transacional e obter o "
+"objeto <code>XAResource</code> correspondente para cada conexão. Em seguida, "
+"o Gerenciador de Transação invoca o método <methodname>XAResource.recover</"
+"methodname> para pedir a cada gerenciador de recurso para retornar as "
+"transações que estão, no momento, num estado preparado ou heurístico "
+"completo."
+
+#. Tag: para
+#: Transaction_Recovery.xml:18
+#, no-c-format
+msgid ""
+"When running XA recovery it is 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 ‘*’ will force JBossTS to recover (and possibly rollback) all "
+"transactions irrespective of their node identifier and should be used with "
+"caution."
+msgstr ""
+"Quando rodando a recuperação XA é necessário informar ao JBossTS os tipos de "
+"Xid que isto pode recuperar. Cada Xid que o JBossTS cria possui um "
+"identificador de nó único codificado com isto e o JBossTS irá apenas "
+"recuperar as transações e estados que combinam um identificador de nó "
+"especificado. O identificador de nó a ser usado deve ser fornecido ao "
+"JBossTS através de uma propriedade que inicializa com o nome <property>com."
+"arjuna.ats.jta.xaRecoveryNode</property>. Os valores múltiplos poderão ser "
+"fornecidos. Um valor de ‘*’ forçará o JBossTS a recuperação (e possivelmente "
+"a reversão) de todas as transações irrespectivamente de nosso identificador "
+"de nó e deve ser usado com cuidado."
+
+#. Tag: para
+#: Transaction_Recovery.xml:22
+#, no-c-format
+msgid ""
+"If using the JBossJTA JDBC 2.0 driver, then JBossJTA will take care of all "
+"<interfacename>XAResource</interfacename> crash recovery automatically. "
+"Otherwise one of the following recovery mechanisms will be used:"
+msgstr ""
+"Caso usando o JBossJTA JDBC 2.0 driver, o JBossJTA cuidará de todas as "
+"recuperações de interrupção <interfacename>XAResource</interfacename> "
+"automaticamente. Do contrário, um dos seguintes mecanismos de recuperação "
+"serão utilizados:"
+
+#. Tag: para
+#: Transaction_Recovery.xml:27
+#, no-c-format
+msgid ""
+"If the <code>XAResource</code> is serializable, then the serialized form "
+"will be saved during transaction commitment, and used during recovery. It is "
+"assumed that the recreated <code>XAResource</code> is valid and can be used "
+"to drive recovery on the associated database."
+msgstr ""
+"Caso o <code>XAResource</code> seja serializado, a forma serializada será "
+"salva durante a confirmação da transação e usada durante a recuperação. "
+"Assume-se que a recriação do <code>XAResource</code> é válida e pode ser "
+"usada para a recuperação de drive no banco de dados associado."
+
+#. Tag: para
+#: Transaction_Recovery.xml:32
+#, no-c-format
+msgid ""
+"The <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, <interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> and <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> interfaces are used. These "
+"are documented in the JDBC chapters on failure recovery."
+msgstr ""
+"As interfaces <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, <interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> e <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> são utilizadas. Isto está "
+"documentado nos capítulos JDBC sob recuperação de falha."
+
+#. Tag: para
+#: Transaction_Recovery.xml:38
+#, no-c-format
+msgid ""
+"In JBossTS 3.3 the interface <interfacename>XAConnectionRecovery</"
+"interfacename> was deprecated in favor of <interfacename>XAResourceRecovery</"
+"interfacename>. Users are encouraged to move to his new interface."
+msgstr ""
+"No JBossTS 3.3, a interface <interfacename>XAConnectionRecovery</"
+"interfacename> foi contrária ao uso do <interfacename>XAResourceRecovery</"
+"interfacename>. Encorajamos os usuários a mudar para suas novas interfaces."
+
+#. Tag: title
+#: Transaction_Recovery.xml:45
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr "Recuperação de XAConnections"
+
+#. Tag: para
+#: Transaction_Recovery.xml:46
+#, no-c-format
+msgid ""
+"When recovering from failures, JBossJTA requires the ability to reconnect to "
+"databases that were in use prior to the failures in order to resolve any "
+"outstanding transactions. Most connection information will be saved by the "
+"transaction service during its normal execution, and can be used during "
+"recovery to recreate the connection. However, it is possible that not all "
+"such information will have been saved prior to a failure (for example, a "
+"failure occurs before such information can be saved, but after the database "
+"connection is used). In order to recreate those connections it is necessary "
+"to provide implementations of the following JBossJTA interface "
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, one for each database that may be used by an application."
+msgstr ""
+"Quando recuperando-se da falha, o JBossJTA requer a habilidade de reconectar "
+"aos bancos de dados que estão em uso antes das falhas, com objetivo de "
+"resolver qualquer transação considerável. A maioria da informação da conexão "
+"será salva pelo serviço da transação durante a própria execução normal e "
+"pode ser usada durante a recuperação para recriar a conexão. No entanto, é "
+"possível que nem todas as informações sejam salvas antes da falha (por "
+"exemplo: a falha ocorre antes de tal informação ser salva, mas após a "
+"conexão do banco de dados for usada). Com a finalidade de recriar aquelas "
+"conexões, é necessário fornecer implementações da interface JBossJTA "
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, uma para cada banco de dados que poderá ser usado pelo "
+"aplicativo."
+
+#. Tag: para
+#: Transaction_Recovery.xml:50
+#, no-c-format
+msgid ""
+"If using the transactional JDBC 2.0 driver provided with JBossJTA, then no "
+"additional work is necessary in order to ensure that recovery occurs."
+msgstr ""
+"Caso usando o driver JDBC 2.0 transacional fornecido com o JBossJTA, não "
+"haverá necessidade de trabalho adicional para a garantia de que a "
+"recuperação ocorrerá."
+
+#. Tag: para
+#: Transaction_Recovery.xml:54
+#, no-c-format
+msgid ""
+"To inform the recovery system about each of the <code>XAResourceRecovery</"
+"code> instances, it is necessary to specify their class names through "
+"property variables. Any property variable found in the properties file, or "
+"registered at runtime, which starts with the name <property>com.arjuna.ats."
+"jta.recovery.XAResourceRecovery</property> will be assumed to represent one "
+"of these instances, and its value should be the class name. For example:"
+msgstr ""
+"Para informar que o sistema de recuperação de cada uma das instâncias "
+"<code>XAResourceRecovery</code>, é necessário especificar os nomes de "
+"classes das mesmas através das variáveis de propriedade. Assume-se que "
+"qualquer variável de propriedade encontrada no arquivo de propriedade ou "
+"registrado no período de execução, que inicializa com o nome <property>com."
+"arjuna.ats.jta.recovery.XAResourceRecovery</property>, representará uma "
+"destas instâncias e seu valor deve ser o nome da classe. Por exemplo:"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:57
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+
+#. Tag: para
+#: Transaction_Recovery.xml:58
+#, no-c-format
+msgid ""
+"Additional information that will be passed to the instance when it is "
+"created may be specified after a semicolon:"
+msgstr ""
+"A informação adicional que será passada à instância quando isto é criada, "
+"pode ser especificada após o ponto-e-vírgula:"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+
+#. Tag: para
+#: Transaction_Recovery.xml:63
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr "Estas propriedades precisam estar na seção do arquivo de propriedade."
+
+#. Tag: para
+#: Transaction_Recovery.xml:67
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr "Quaisquer erros poderão ser relatados durante a recuperação."
+
+#. Tag: screen
+#: Transaction_Recovery.xml:70
+#, no-c-format
+msgid ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+msgstr ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+
+#. Tag: para
+#: Transaction_Recovery.xml:71
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr "Cada método deve retornar a seguinte informação:"
+
+#. Tag: para
+#: Transaction_Recovery.xml:76
+#, no-c-format
+msgid ""
+"<methodname>initialise</methodname>: once the instance has been created, any "
+"additional information which occurred on the property value (anything found "
+"after the first semi-colon) will be passed to the object. The object can "
+"then use this information in an implementation specific manner to initialise "
+"itself, for example."
+msgstr ""
+"<methodname>initialise</methodname>: uma vez que a instância foi criada, "
+"qualquer informação adicional que ocorrer no valor da propriedade (qualquer "
+"coisa encontrada após o primeiro ponto-e-vírgula) será passado ao objeto. O "
+"objeto poderá então usar esta informação numa maneira específica de "
+"implementação para inicializar-se, por exemplo."
+
+#. Tag: para
+#: Transaction_Recovery.xml:81
+#, no-c-format
+msgid ""
+"<methodname>hasMoreResources</methodname>: each <code>XAResourceRecovery</"
+"code> implementation may provide multiple <code>XAResource</code> instances. "
+"Before any call to <methodname>getXAResource</methodname> is made, "
+"<methodname>hasMoreResources</methodname> is called to determine whether "
+"there are any further connections to be obtained. If this returns false, "
+"<methodname>getXAResource</methodname> will not be called again during this "
+"recovery sweep and the instance will not be used further until the next "
+"recovery scan."
+msgstr ""
+"<methodname>hasMoreResources</methodname>: cada implementação "
+"<code>XAResourceRecovery</code> pode fornecer instâncias <code>XAResource</"
+"code> múltiplas. Antes de qualquer chamada ser feita ao "
+"<methodname>getXAResource</methodname>, o <methodname>hasMoreResources</"
+"methodname> é chamado para determinar se é que existem quaisquer conexões "
+"futuras a serem obtidas. Caso isto retorne como falso, o "
+"<methodname>getXAResource</methodname> não será chamado novamente durante "
+"este movimento de recuperação e a instância não será mais usada até o "
+"próximo scan de recuperação."
+
+#. Tag: para
+#: Transaction_Recovery.xml:86
+#, no-c-format
+msgid ""
+"<methodname>getXAResource</methodname>: returns an instance of the "
+"<code>XAResource</code> object. How this is created (and how the parameters "
+"to its constructors are obtained) is up to the <code>XAResourceRecovery</"
+"code> implementation. The parameters to the constructors of this class "
+"should be similar to those used when creating the initial driver or data "
+"source, and should obviously be sufficient to create new <code>XAResources</"
+"code> that can be used to drive recovery."
+msgstr ""
+"<methodname>getXAResource</methodname>: retorna uma instância do objeto "
+"<code>XAResource</code>. A maneira com que isto é criado ( e como os "
+"parâmetros para seus construtores são obtidos) ficará a critério da "
+"implementação <code>XAResourceRecovery</code>. Os parâmetros aos "
+"construtores desta classe deve ser parecido aqueles usados quando criando o "
+"driver inicial ou fonte de dados, além de ser suficiente para criar um novo "
+"<code>XAResources</code>, que pode ser usado para a recuperação do drive."
+
+#. Tag: para
+#: Transaction_Recovery.xml:92
+#, no-c-format
+msgid ""
+"If you want your <code>XAResourceRecovery</code> instance to be called "
+"during each sweep of the recovery manager then you should ensure that once "
+"<methodname>hasMoreResources</methodname> returns false to indicate the end "
+"of work for the current scan it then returns true for the next recovery scan."
+msgstr ""
+"Caso você deseje que sua instância <code>XAResourceRecovery</code> seja "
+"chamada durante cada movimento do gerenciador de recuperação, então você "
+"deve garantir que uma vez que o <methodname>hasMoreResources</methodname> "
+"retorna como falso para indicar o encerramento de um trabalho para o scan "
+"atual, ele retornará verdadeiro para o próximo scan de recuperação."
+
+#. Tag: title
+#: Transaction_Recovery.xml:99
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr "Implementações XAResourceRecovery lançadas"
+
+#. Tag: para
+#: Transaction_Recovery.xml:100
+#, no-c-format
+msgid ""
+"Recovery of <interfacename>XA</interfacename> datasources can sometimes be "
+"implementation dependant, requiring developers to provide their own "
+"<interfacename>XAResourceRecovery</interfacename> instances. However, "
+"JBossTS ships with several out-of-the-box implementations that may be useful."
+msgstr ""
+"A recuperação do banco de dados <interfacename>XA</interfacename> pode, às "
+"vezes, ser uma implementação dependente, solicitando desenvolvedores a "
+"fornecerem as próprias instâncias <interfacename>XAResourceRecovery</"
+"interfacename>. No entanto, o JBossTS lança diversas implementações fora-da-"
+"caixa que podem ser úteis."
+
+#. Tag: para
+#: Transaction_Recovery.xml:105
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: this expects an XML property file to be specified upon "
+"creation and from which it will read the database URL, username and "
+"password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: isto espera que um arquivo de propriedade XML seja "
+"especificado até a criação e a partir do qual ele lerá o URL de banco de "
+"dados, nome do usuário e senha. Por exemplo: "
+
+#. Tag: screen
+#: Transaction_Recovery.xml:108
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+
+#. Tag: para
+#: Transaction_Recovery.xml:111
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: this recovery implementation should work on any datasource "
+"that is exposed via JNDI. It expects an XML property file to be specified "
+"upon creation and from which it will read the database JNDI name, username "
+"and password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: esta implementação de recuperação deve trabalhar em qualquer "
+"banco de dados que está exposto através do JNDI. Isto espera que um arquivo "
+"de propriedade XML seja especificado até a criação e a partir do qual ele "
+"lerá o URL de banco de dados, nome do usuário e senha. Por exemplo: "
+
+#. Tag: screen
+#: Transaction_Recovery.xml:114
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,653 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr "Transações"
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr "O API"
+
+#. Tag: para
+#: Transactions.xml:9
+#, no-c-format
+msgid ""
+"The Java Transaction API consists of three elements: a high-level "
+"application transaction demarcation interface, a high-level transaction "
+"manager interface intended for application server, and a standard Java "
+"mapping of the X/Open XA protocol intended for transactional resource "
+"manager. All of the JTA classes and interfaces occur within the "
+"<package>javax.transaction</package> package, and the corresponding JBossJTA "
+"implementations within the <package>com.arjuna.ats.jta</package> package."
+msgstr ""
+"O API de Transação Java é constituído por três elementos: uma interface de "
+"demarcação de transação de aplicativo de alto nível, uma interface de "
+"gerenciador de transação direcionado ao servidor do aplicativo e um "
+"mapeamento Java padrão do protocolo X/Open XA direcionado ao gerenciador de "
+"recurso transacional. Todas as classes JTA interfaces ocorrem com o pacote "
+"<package>javax.transaction</package> e as implementações JBossJTA "
+"correspondentes com o pacote <package>com.arjuna.ats.jta</package>."
+
+#. Tag: para
+#: Transactions.xml:13
+#, no-c-format
+msgid ""
+"Each 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. The contents of this "
+"should be alphanumeric."
+msgstr ""
+"Cada Xid que o JBossTS cria deve possuir um identificador de nó codificado "
+"com isto e o JBossTS apenas recuperará as transações e estados que combinam "
+"com o identificador de nó especificado. O identificador de nó para uso deve "
+"ser fornecido ao JBossTS através da propriedade <property>com.arjuna.ats."
+"arjuna.xa.nodeIdentifier</property>. Você deverá certificar-se que este "
+"valor é único em suas instâncias JBossTS. Caso você não forneça um valor, o "
+"JBossTS fabricará um e relatará o valor através da infra-estrutura de "
+"conexão. Estes conteúdos devem ser em ordem alfabética."
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: Transactions.xml:19
+#, no-c-format
+msgid ""
+"The <interfacename>UserTransaction</interfacename> interface provides "
+"applications with the ability to control transaction boundaries. It has "
+"methods for beginning, committing, and rolling back top-level transactions: "
+"nested transactions are not supported, and begin throws the "
+"<code>NotSupportedException</code> when the calling thread is already "
+"associated with a transaction. <interfacename>UserTransaction</"
+"interfacename> automatically associates newly created transactions with the "
+"invoking thread."
+msgstr ""
+"A interface <interfacename>UserTransaction</interfacename> fornece "
+"aplicativos com a habilidade de controlar as transações de limite. Isto "
+"possui métodos para as transações de nível top de inicialização, confirmação "
+"e reversão: as transações aninhadas não estão suportadas e começam a lançar "
+"o <code>NotSupportedException</code>, quando a segmentação de chamada já "
+"estiver associada com a transação. A <interfacename>UserTransaction</"
+"interfacename> automaticamente associa as transações recentemente criadas "
+"com a segmentação invocada."
+
+#. Tag: para
+#: Transactions.xml:24
+#, no-c-format
+msgid ""
+"In JBossJTA, UserTransactions can be obtained from the static "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname> method."
+msgstr ""
+"No JBossJTA, as UserTransactions podem ser obtidas a partir do método "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname>."
+
+#. Tag: para
+#: Transactions.xml:28
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+"Com a finalidade de selecionar a implementação JTA local, é necessário "
+"executar os seguintes passos:"
+
+#. Tag: para
+#: Transactions.xml:33
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</property>."
+msgstr ""
+"certifique-se que a propriedade <property>com.arjuna.ats.jta."
+"jtaTMImplementation</property> é configurada para <property>com.arjuna.ats."
+"internal.jta.transaction.arjunacore.TransactionManagerImple</property>."
+
+#. Tag: para
+#: Transactions.xml:38
+#, no-c-format
+msgid ""
+"1.make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</property>."
+msgstr ""
+"1. certifique-se que a propriedade <property>com.arjuna.ats.jta."
+"jtaUTImplementation</property> é configurada para <property>com.arjuna.ats."
+"internal.jta.transaction.arjunacore.UserTransactionImple</property>."
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: Transactions.xml:45
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface allows the "
+"application server to control transaction boundaries on behalf of the "
+"application being managed."
+msgstr ""
+"A interface <interfacename>TransactionManager</interfacename> permite que o "
+"servidor do aplicativo controle os limites das transações em nome do "
+"aplicativo sendo gerenciado."
+
+#. Tag: para
+#: Transactions.xml:50
+#, no-c-format
+msgid ""
+"In JBossJTA, transaction manager implementations can be obtained from the "
+"static <methodname>com.arjuna.ats.jta.TransactionManager.transactionManager</"
+"methodname> method."
+msgstr ""
+"No JBossJTA, as implementações do gerenciador de transação podem ser obtidas "
+"a partir do método <methodname>com.arjuna.ats.jta.TransactionManager."
+"transactionManager</methodname> estatístico."
+
+#. Tag: para
+#: Transactions.xml:54
+#, no-c-format
+msgid ""
+"The Transaction Manager maintains the transaction context association with "
+"threads as part of its internal data structure. A thread’s transaction "
+"context is either null or it refers to a specific global transaction. "
+"Multiple threads may be associated with the same global transaction. As "
+"noted above, nested transactions are not supported."
+msgstr ""
+"O Gerenciador de Transação mantém a associação do contexto de transação com "
+"as segmentações como parte desta estrutura de dados internos. O contexto de "
+"transação da segmentação é tanto nulo ou isto refere-se à transação global "
+"específica. As segmentações múltiplas podem ser associadas com a mesma "
+"transação global. Conforme citado anteriormente, as transações aninhadas não "
+"são suportadas."
+
+#. Tag: para
+#: Transactions.xml:57
+#, no-c-format
+msgid ""
+"Each transaction context is encapsulated by a Transaction object, which can "
+"be used to perform operations which are specific to the target transaction, "
+"regardless of the calling thread’s transaction context."
+msgstr ""
+"Cada contexto de transação é encapsulado pelo objeto de Transação, pelo qual "
+"pode ser usado para executar operações que são específicas à transação de "
+"destinação, independente do contexto de transação da segmentação de chamada."
+
+#. Tag: para
+#: Transactions.xml:60
+#, no-c-format
+msgid ""
+"The <methodname>begin</methodname> method of "
+"<interfacename>TransactionManager</interfacename> starts a new top-level "
+"transaction and associates the transaction context with the calling thread. "
+"If the calling thread is already associated with a transaction then it "
+"throws the <code>NotSupportedException</code>."
+msgstr ""
+"O método <methodname>begin</methodname> da interface "
+"<interfacename>TransactionManager</interfacename> inicializa uma nova "
+"transação de nível top e associa o contexto da transação com a segmentação "
+"da chamada. Caso a segmentação da chamada já esteja associada com a "
+"transação, então isto lançará o <code>NotSupportedException</code>."
+
+#. Tag: para
+#: Transactions.xml:63
+#, no-c-format
+msgid ""
+"The <methodname>getTransaction</methodname> method returns the Transaction "
+"object that represents the transaction context currently associated with the "
+"calling thread. This object can be used to perform various operations on the "
+"target transaction, described later."
+msgstr ""
+"O método <methodname>getTransaction</methodname> retorna o objeto da "
+"Transação que representa o contexto de transação atualmente associado com a "
+"segmentação de chamada. Este objeto pode ser usado para executar diversas "
+"operações na transação de destinação, que será descrita adiante."
+
+#. Tag: para
+#: Transactions.xml:66
+#, no-c-format
+msgid ""
+"The commit method is used to complete the transaction currently associated "
+"with the calling thread. After it returns, the calling thread is associated "
+"with no transaction. If commit is called when the thread is not associated "
+"with any transaction context, the TM throws an exception. In some "
+"implementation, the commit operation is restricted to the transaction "
+"originator only. If the calling thread is not allowed to commit the "
+"transaction, the TM throws an exception. JBossJTA does not currently impose "
+"any restriction on the ability of threads to terminate transactions."
+msgstr ""
+"O método de confirmação é usado para completar a transação atual associada "
+"com a segmentação de chamada. Após isto retornar, a segmentação da chamada é "
+"associada sem transação. "
+
+#. Tag: para
+#: Transactions.xml:69
+#, no-c-format
+msgid ""
+"The <methodname>rollback</methodname> method is used to rollback the "
+"transaction associated with the current thread. After the "
+"<methodname>rollback</methodname> method completes, the thread is associated "
+"with no transaction."
+msgstr ""
+"O método <methodname>rollback</methodname> é usado para reverter a transação "
+"associada com a segmentação atual. Após o método <methodname>rollback</"
+"methodname> ser completado, a segmentação é associada sem transação."
+
+#. Tag: para
+#: Transactions.xml:73
+#, no-c-format
+msgid ""
+"In a multi-threaded environment it is possible that multiple threads are "
+"active within the same transaction. If checked transaction semantics have "
+"been disabled, or the transaction times out, then it is possible for a "
+"transaction to be terminated by a thread other than the one that created it. "
+"In this case, it is often important that this information is communicated to "
+"the creator. JBossTS does this during commit or rollback by throwing "
+"<code>IllegalStateException</code>."
+msgstr ""
+"Num ambiente multi-segmentado é possível que múltiplas segmentações estejam "
+"ativas com a mesma transação. Caso as semânticas de transação checadas "
+"tenham sido desativadas ou a transação expirar, será possível que uma "
+"transação seja finalizada por uma segmentação, ao invés daquela que criou "
+"isto. Neste caso, é freqüentemente importante que esta informação faça "
+"comunicação com o criador. O JBossTS realiza isto durante a confirmação ou "
+"reversão pelo lançamento da <code>IllegalStateException</code>."
+
+#. Tag: title
+#: Transactions.xml:78
+#, no-c-format
+msgid "Suspending and resuming a transaction"
+msgstr "Suspendendo e resumindo uma transação"
+
+#. Tag: para
+#: Transactions.xml:79
+#, no-c-format
+msgid ""
+"The JTA supports the concept of a thread temporarily suspending and resuming "
+"transactions to enable it to perform non-transactional work. The suspend "
+"method is called to temporarily suspend the current transaction that is "
+"associated with the calling thread, i.e., so that the thread is no longer "
+"operating within its scope. If the thread is not associated with any "
+"transaction, a null object reference is returned; otherwise, a valid "
+"<code>Transaction</code> object is returned. The <code>Transaction</code> "
+"object can later be passed to the resume method to reinstate the transaction "
+"context."
+msgstr ""
+"O JTA suporta o conceito de uma segmentação temporária suspendendo e "
+"resumindo transações para permitir que as mesmas executem um trabalho não-"
+"transacional. O método suspenso é chamado para suspender temporariamente a "
+"transação atual que é associada com a segmentação de chamada, de forma que a "
+"segmentação não está mais operando com o próprio escopo. Caso uma "
+"segmentação não é associada com qualquer transação, uma referência de objeto "
+"nulo é retornada. Do contrário, um objeto da <code>Transaction</code> válido "
+"é retornado. O objeto de <code>Transaction</code> poderá ser passado mais "
+"tarde ao método de resumo para reintegrar o contexto de transação. "
+
+#. Tag: para
+#: Transactions.xml:83
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method associates the specified "
+"transaction context with the calling thread. If the transaction specified is "
+"a valid transaction, the transaction context is associated with the calling "
+"thread; otherwise, the thread is associated with no transaction."
+msgstr ""
+"O método <methodname>resume</methodname> associa o contexto da transação "
+"especificada com a segmentação de chamada. Caso a transação especificada for "
+"uma transação válida, o contexto de transação será associado com a "
+"segmentação de chamada, do contrário, a segmentação é associada sem "
+"transação."
+
+#. Tag: para
+#: Transactions.xml:87
+#, no-c-format
+msgid ""
+"If <methodname>resume</methodname> is invoked when the calling thread is "
+"already associated with another transaction, the Transaction Manager throws "
+"the <code>IllegalStateException</code> exception."
+msgstr ""
+"Caso o <methodname>resume</methodname> seja invocado quando a segmentação de "
+"chamada já estiver associada com outra transação, o Gerenciador de Transação "
+"lança a exceção <code>IllegalStateException</code>."
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+
+#. Tag: para
+#: Transactions.xml:93
+#, no-c-format
+msgid ""
+"Some Transaction Manager implementations allow a suspended transaction to be "
+"resumed by a different thread. This feature is not required by JTA, but "
+"JBossJTA does support this."
+msgstr ""
+"Algumas implementações do Gerenciador de transação permitem que uma "
+"transação suspensa seja resumida por uma segmentação diferente. Este recurso "
+"não é solicitado pelo JTA, mas o JBossJTA o suporta."
+
+#. Tag: para
+#: Transactions.xml:97
+#, no-c-format
+msgid ""
+"When a transaction is suspended the application server must ensure that the "
+"resources in use by the application are no longer registered with the "
+"suspended transaction. When a resource is de-listed this triggers the "
+"Transaction Manager to inform the resource manager to disassociate the "
+"transaction from the specified resource object. When the application’s "
+"transaction context is resumed, the application server must ensure that the "
+"resources in use by the application are again enlisted with the transaction. "
+"Enlisting a resource as a result of resuming a transaction triggers the "
+"Transaction Manager to inform the resource manager to re-associate the "
+"resource object with the resumed transaction."
+msgstr ""
+"Quando a transação é suspensa o servidor do aplicativo deve certificar-se de "
+"que os recursos em uso pelo aplicativo não estão mais registrados com a "
+"transação suspensa. Quando um recurso é removido da lista, ele realiza o "
+"trigger no Gerenciador de Transação para informar o gerenciador de recurso a "
+"desassociar a transação do objeto de recurso especificado. Quando o contexto "
+"da transação do aplicativo for resumido, o servidor do aplicativo deverá "
+"garantir que os recursos em uso pelo aplicativo serão novamente listados com "
+"a transação. A listagem de um recurso como resultado de um resumo de "
+"transação, realiza os triggers no Gerenciador da Transação para informar que "
+"o gerenciador de recurso para re-associar o objeto de recurso com a "
+"transação resumida."
+
+#. Tag: title
+#: Transactions.xml:101
+#, no-c-format
+msgid "The Transaction interface"
+msgstr "A interface da Transação"
+
+#. Tag: para
+#: Transactions.xml:102
+#, no-c-format
+msgid ""
+"The <interfacename>Transaction</interfacename> interface allows operations "
+"to be performed on the transaction associated with the target object. Every "
+"top-level transaction is associated with one <code>Transaction</code> object "
+"when the transaction is created. The <code>Transaction</code> object can be "
+"used to:"
+msgstr ""
+"A interface da <interfacename>Transaction</interfacename> permite que "
+"operações sejam executadas numa transação associada com o objeto de "
+"destinação. Cada transação de nível top é associada com um objeto de "
+"<code>Transaction</code> quando a transação é criada. O objeto de "
+"<code>Transaction</code> pode ser usado para:"
+
+#. Tag: para
+#: Transactions.xml:108
+#, no-c-format
+msgid "Enlist the transactional resources in use by the application."
+msgstr "Realizar a listagem de recursos transacional em uso pelo aplicativo."
+
+#. Tag: para
+#: Transactions.xml:113
+#, no-c-format
+msgid "Register for transaction synchronization call backs."
+msgstr "Registrar os retornos de chamada de sincronização de transação."
+
+#. Tag: para
+#: Transactions.xml:118
+#, no-c-format
+msgid "Commit or rollback the transaction."
+msgstr "Confirmar ou reverter a transação."
+
+#. Tag: para
+#: Transactions.xml:123
+#, no-c-format
+msgid "Obtain the status of the transaction."
+msgstr "Obter o status da transação."
+
+#. Tag: para
+#: Transactions.xml:128
+#, no-c-format
+msgid ""
+"The <methodname>commit</methodname> and <methodname>rollback</methodname> "
+"methods allow the target object to be committed or rolled back. The calling "
+"thread is not required to have the same transaction associated with the "
+"thread. If the calling thread is not allowed to commit the transaction, the "
+"transaction manager throws an exception. At present JBossJTA does not impose "
+"restrictions on threads terminating transactions."
+msgstr ""
+"Os métodos <methodname>commit</methodname> e <methodname>rollback</"
+"methodname> permitem o objeto de destinação a ser confirmado ou revertido. A "
+"segmentação da chamada não é solicitada para possuir a mesma transação "
+"associada com a segmentação. Caso uma segmentação de chamada não seja "
+"autorizada a confirmar a transação, o gerenciador de transação lançará uma "
+"exceção. O JBossJTA não impõe restrições em segmentações finalizando "
+"transações."
+
+#. Tag: title
+#: Transactions.xml:132
+#, no-c-format
+msgid "Resource enlistment"
+msgstr "Listagem de recurso"
+
+#. Tag: para
+#: Transactions.xml:133
+#, no-c-format
+msgid ""
+"Transactional resources such as database connections are typically managed "
+"by the application server in conjunction with some resource adapter and "
+"optionally with connection pooling optimization. In order for an external "
+"transaction manager to co-ordinate transactional work performed by the "
+"resource managers, the application server must enlist and de-list the "
+"resources used in the transaction. These resources (participants) are "
+"enlisted with the transaction so that they can be informed when the "
+"transaction terminates, for example, are driven through the two-phase commit "
+"protocol."
+msgstr ""
+"Os recursos transacionais tais como conexões de banco de dados são "
+"tipicamente gerenciados pelo servidor do aplicativo em conjunção com alguns "
+"adaptadores de recurso e opcionalmente com a otimização do pool de conexão. "
+"Com o objetivo de que um gerenciador de recurso externo coordene o trabalho "
+"transacional executado pelos gerenciadores de recurso, o servidor do "
+"aplicativo deve listar e e remover da lista os recursos usados na transação. "
+"Estes recursos (participantes) estão listados com a transação de forma que "
+"eles podem ser informados quando as transações são finalizadas, por exemplo, "
+"são dirigidos através do protocolo de conformação de duas fases."
+
+#. Tag: para
+#: Transactions.xml:137
+#, no-c-format
+msgid ""
+"As stated previously, the JTA is much more closely integrated with the XA "
+"concept of resources than the arbitrary objects. For each resource in-use by "
+"the application, the application server invokes the "
+"<methodname>enlistResource</methodname> method with an <code>XAResource</"
+"code> object which identifies the resource in use. See for details on how "
+"the implementation of the <code>XAResource</code> can affect recovery in the "
+"event of a failure."
+msgstr ""
+"Conforme mencionado anteriormente, o JTA está muito mais integrado com o "
+"conceito XA de recursos do que os objetos arbitrários. Para cada recurso em "
+"uso pelo aplicativo, o servidor do aplicativo invoca o método "
+"<methodname>enlistResource</methodname> com um objeto <code>XAResource</"
+"code> que identifica o recurso em uso. Consulte os detalhes sobre como a "
+"implementação do <code>XAResource</code> pode afetar a recuperação num "
+"evento de falha."
+
+#. Tag: para
+#: Transactions.xml:140
+#, no-c-format
+msgid ""
+"The enlistment request results in the transaction manager informing the "
+"resource manager to start associating the transaction with the work "
+"performed through the corresponding resource. The transaction manager is "
+"responsible for passing the appropriate flag in its <methodname>XAResource."
+"start</methodname> method call to the resource manager."
+msgstr ""
+"Os resultados da solicitação de listagem no gerenciador de transação "
+"informando o gerenciador de recurso para inicializar a associação de "
+"transação com o trabalho executado através do recurso correspondente. O "
+"gerenciador de transação é responsável em passar a sinalização apropriada na "
+"própria chamada de método <methodname>XAResource.start</methodname> para o "
+"gerenciador de recurso."
+
+#. Tag: para
+#: Transactions.xml:143
+#, no-c-format
+msgid ""
+"The <methodname>delistResource</methodname> method is used to disassociate "
+"the specified resource from the transaction context in the target object. "
+"The application server invokes the method with the two parameters: the "
+"<code>XAResource</code> object that represents the resource, and a flag to "
+"indicate whether the operation is due to the transaction being suspended "
+"(TMSUSPEND), a portion of the work has failed (TMFAIL), or a normal resource "
+"release by the application (TMSUCCESS)."
+msgstr ""
+"O método <methodname>delistResource</methodname> é usado para desassociar o "
+"recurso especificado a partir do contexto de transação no objeto de "
+"destinação. O servidor do aplicativo invoca o método com os dois parâmetros. "
+"O objeto <code>XAResource</code> representa o recurso e o sinalizador indica "
+"se é que ou não a operação está expirando o prazo para que a transação seja "
+"suspensa (TMSUSPEND), uma porção de trabalho tenha falhado (TMFAIL) ou uma "
+"liberação de recurso normal pelo aplicativo (TMSUCCESS)."
+
+#. Tag: para
+#: Transactions.xml:146
+#, no-c-format
+msgid ""
+"The de-list request results in the transaction manager informing the "
+"resource manager to end the association of the transaction with the target "
+"<code>XAResource</code>. The flag value allows the application server to "
+"indicate whether it intends to come back to the same resource whereby the "
+"resource states must be kept intact. The transaction manager passes the "
+"appropriate flag value in its <methodname>XAResource.end</methodname> method "
+"call to the underlying resource manager."
+msgstr ""
+"Os resultados de solicitação de remoção da lista no gerenciador de transação "
+"informam o gerenciador de recurso para finalizar a associação da transação "
+"com o <code>XAResource</code> de destinação. O valor sinalizador permite que "
+"o servidor do aplicativo indique se é que ou não isto possui por intenção "
+"retornar ao mesmo recurso que os estados de recurso devem ser mantidos "
+"intactos. O gerenciador de transação passa o valor de sinalizador apropriado "
+"na própria chamada do método <methodname>XAResource.end</methodname> ao "
+"gerenciador de recurso subjacente."
+
+#. Tag: title
+#: Transactions.xml:150
+#, no-c-format
+msgid "Transaction synchronization"
+msgstr "Sincronização da Transação"
+
+#. Tag: para
+#: Transactions.xml:151
+#, no-c-format
+msgid ""
+"Transaction synchronization allows the application server to be notified "
+"before and after the transaction completes. For each transaction started, "
+"the application server may optionally register a Synchronization call back "
+"object to be invoked by the transaction manager:"
+msgstr ""
+"A sincronização de recurso permite que o servidor do aplicativo seja "
+"notificado antes e depois que a transação seja finalizada. Para cada "
+"transação inicializada, o servidor do aplicativo poderá opcionalmente "
+"registrar um objeto de retorno de chamada de Sincronização a ser invocado "
+"pelo gerenciador de transação:"
+
+#. Tag: para
+#: Transactions.xml:157
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method is called prior to the "
+"start of the two-phase transaction complete process. This call is executed "
+"in the same transaction context of the caller who initiates the "
+"<methodname>TransactionManager.commit</methodname> or the call is executed "
+"with no transaction context if <methodname>Transaction.commit</methodname> "
+"is used."
+msgstr ""
+"O método <methodname>beforeCompletion</methodname> é chamado antes de "
+"começar o processo de finalização de transação de duas fases. Esta chamada é "
+"executada no mesmo contexto de transação do chamador que inicializa o "
+"<methodname>TransactionManager.commit</methodname> ou a chamada é executada "
+"sem o contexto de transação, caso o <methodname>Transaction.commit</"
+"methodname> seja usado."
+
+#. Tag: para
+#: Transactions.xml:162
+#, no-c-format
+msgid ""
+"The <methodname>afterCompletion</methodname> method is called after the "
+"transaction has completed. The status of the transaction is supplied in the "
+"parameter. This method is executed without a transaction context."
+msgstr ""
+"O método <methodname>afterCompletion</methodname> é chamado após a transação "
+"ser completada. O status da transação é suprido no parâmetro. Este método é "
+"executado sem o contexto de transação."
+
+#. Tag: title
+#: Transactions.xml:168
+#, no-c-format
+msgid "Transaction equality"
+msgstr "Igualdade da Transação"
+
+#. Tag: para
+#: Transactions.xml:169
+#, no-c-format
+msgid ""
+"The transaction manager implements the Transaction object’s equals method to "
+"allow comparison between the target object and another Transaction object. "
+"The equals method should return true if the target object and the parameter "
+"object both refer to the same global transaction."
+msgstr ""
+"O gerenciador de transação implementa o método de igualdade do objeto de "
+"Transação para permitir a comparação entre o objeto de destinação e outro "
+"objeto de Transação. O método de igualdade retorna verdadeiro, caso ambos "
+"objeto de destinação e o objeto de parâmetro referem-se à mesma transação "
+"global."
+
+#. Tag: screen
+#: Transactions.xml:173
+#, no-c-format
+msgid ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
+msgstr ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/pt-BR/Using_JBossJTA_in_Application_Servers.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,277 @@
+# translation of Author_Group.po to Brazilian Portuguese
+# Language pt-BR translations for package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-10-29 15:58+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"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr "Usando o JBossJTA em Servidores de Aplicativo"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr "Servidor do Aplicativo JBoss"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:10
+#, no-c-format
+msgid "Service Configuration"
+msgstr "Configuração do Serviço"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:11
+#, no-c-format
+msgid ""
+"The JBoss Transaction Service is configured primarily via the XML files "
+"stored in the etc directory, but when run as a JBOSS service there are a "
+"number of configurable attributes available. They are as follows:"
+msgstr ""
+"O Serviço de Transação JBoss é configurado através dos arquivos XML "
+"armazenados no diretório etc, mas quando for rodado como um serviço JBOSS, "
+"existe um número de atributos configuráveis disponíveis. Eles são os "
+"seguintes:"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:17
+#, no-c-format
+msgid ""
+"TransactionTimeout – The default transaction timeout to be used for new "
+"transactions. Specified as an integer in seconds."
+msgstr ""
+"TransactionTimeout – O intervalo da transação padrão a ser usado para a nova "
+"transação. Especificado como íntegro em segundos."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:22
+#, no-c-format
+msgid ""
+"StatisticsEnabled – This determines whether or not the transaction service "
+"should gather statistical information. This information can then be viewed "
+"using the PerformanceStatistics MBean. Specified as a Boolean. The default "
+"is to not gather this information."
+msgstr ""
+"StatisticsEnabled – Isto determina se é que ou não o serviço de transação "
+"deve acumular informação de estatística. A informação pode então ser "
+"visualizada usando o PerformanceStatistics MBean. Ela é especificada como um "
+"Boolean. O padrão é para não acumular esta informação."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:27
+#, no-c-format
+msgid ""
+"PropagateFullContext – This determines whether a full transactional context "
+"is propagated by context importer/exporter. If set to false only the current "
+"transaction context is propagated. If set to true the full transaction "
+"context (including parent transactions) is propagated."
+msgstr ""
+"PropagateFullContext – Isto determina se é que ou não um contexto "
+"transacional completo é propagado pelo contexto importador/exportador. Caso "
+"configurado para falso, apenas o contexto de transação atual é propagado. "
+"Caso configurado para verdadeiro o contexto de transação completo (incluindo "
+"as transações parent) é propagado."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:32
+#, no-c-format
+msgid ""
+"These attributes are specified as MBean attributes in the jboss-service.xml "
+"file located in the server/all/conf directory, for example:"
+msgstr ""
+"Estes atributos são especificados como atributos MBean no arquivo jboss-"
+"service.xml localizado no diretório erver/all/conf, como o exemplo abaixo:"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:35
+#, no-c-format
+msgid ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+msgstr ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:36
+#, no-c-format
+msgid ""
+"The transaction service is configurable also via the standard JBoss "
+"Transaction Service property files. These are located in the JBossTS install "
+"location under the etc sub-directory."
+msgstr ""
+"O serviço de transação é configurável através dos arquivos da propriedade do "
+"Serviço de Transação. Eles estão localizados na localização de instalação do "
+"JBossTS sob o sub-diretório etc."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:39
+#, no-c-format
+msgid ""
+"These files can be edited manually or through JMX. Each property file is "
+"exposed via an object with the name <code>com.arjuna.ts.properties</code> "
+"and an attribute of module where module is equal to the name of the module "
+"to be configured, for example, <code>com.arjuna.ts.properties:module=arjuna</"
+"code>."
+msgstr ""
+"Estes arquivos podem ser editados manualmente ou através do JMX. Cada "
+"arquivo de propriedade é exposto através de um objeto com o nome <code>com."
+"arjuna.ts.properties</code> e um atributo do módulo onde o módulo é igual ao "
+"nome do módulo a ser configurado, por exemplo: <code>com.arjuna.ts."
+"properties:module=arjuna</code>."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:43
+#, no-c-format
+msgid "Logging"
+msgstr "Logging"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:44
+#, no-c-format
+msgid ""
+"In order to make JBossTS logging semantically consistent with JBossAS, the "
+"TransactionManagerService modifies the level of some log messages. This is "
+"achieved by overriding the value of the <property>com.arjuna.common.util."
+"logger</property> property given in the <filename>jbossjta-properties.xml</"
+"filename> file. Therefore, the value of this property will have no effect on "
+"the logging behaviour when running embedded in JBossAS. By forcing use of "
+"the log4j_releveler logger, the TransactionManagerService causes all INFO "
+"level messages in the transaction code to be modified to behave as DEBUG "
+"messages. Therefore, these messages will not appear in log files if the "
+"filter level is INFO. All other log messages behave as normal."
+msgstr ""
+"Com o objetivo de realizar uma consistente semântica conexão do JBossTS com "
+"o JBossAS, o TransactionManagerService modifica o nível de algumas mensagens "
+"de log. Isto é atingido pela substituição do valor da propriedade "
+"<property>com.arjuna.common.util.logger</property> gerada no arquivo "
+"<filename>jbossjta-properties.xml</filename>. Portanto, o valor desta "
+"propriedade não terá efeito no comportamento de conexão quando rodando a "
+"implementação no JBossAS. O TransactionManagerService causa a modificação de "
+"todas as mensagens de nível INFO no código de transação a ser modificado "
+"para comportar-se como mensagens DEBUG, quando forçando o uso do "
+"log4j_releveler logger. Portanto, estas mensagens não aparecerão nos "
+"arquivos log, caso o nível do filtro é INFO. Todas as demais mensagens log "
+"comportam-se com normalmente."
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:49
+#, no-c-format
+msgid "The services"
+msgstr "Os serviços"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:50
+#, no-c-format
+msgid ""
+"There is currently one service offered by the JBOSS integration called "
+"TransactionManagerService. Here we shall discuss what this service does."
+msgstr ""
+"Atualmente, existe um serviço oferecido pela integração do JBOSS chamada "
+"TransactionManagerService. Iremos descrever as funções deste serviço."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:54
+#, no-c-format
+msgid ""
+"The transaction manager service’s main purpose is to ensure the recovery "
+"manager is started. It also binds the JBossTS JTA transaction manager to "
+"java:/TransactionManager name with the JNDI provider. This service depends "
+"upon the existence of the CORBA ORB Service and it must be using JacORB as "
+"the underlying ORB implementation."
+msgstr ""
+"O propósito principal do serviço do gerenciador de transação é garantir que "
+"o gerenciador de recuperação seja inicializado. Isto vincula também o "
+"gerenciador de transação do JBossTS JTA para o nome do java:/"
+"TransactionManager com o provedor JNDI. Este serviço depende da existência "
+"do Serviço CORBA ORB e deve usar o JacORB como a implementação ORB adjacente."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:57
+#, no-c-format
+msgid "There are two instances of this service:"
+msgstr "Existem duas instâncias deste serviço:"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:62
+#, no-c-format
+msgid ""
+"distributed: this uses the JTS enabled transaction manager implementation "
+"and hence supports distributed transactions and recovery. To configure this "
+"use the <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname> class. This is the default configuration."
+msgstr ""
+"distribuído: isto usa a implementação do gerenciador de transação do JTS "
+"ativado e, portanto, suporta as transações distribuídas e recuperação. Para "
+"configurar isto, use a classe <classname>com.arjuna.ats.jbossatx.jts."
+"TransactionManagerService</classname>. Esta é a configuração padrão."
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:67
+#, no-c-format
+msgid ""
+"local: this uses the purely local JTA implementation. To configure this use "
+"the <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
+"classname> class."
+msgstr ""
+"local: usa a pura implementação JTA local. Para configurar isto, use a "
+"classe <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
+"classname>. "
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:73
+#, no-c-format
+msgid "Ensuring Transactional Context is Propagated to the Server"
+msgstr "Garantindo que o Contexto Transacional é Propagado ao Servidor"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:74
+#, no-c-format
+msgid ""
+"It is possible to coordinate transactions from a coordinator which is not "
+"located within the JBoss server (e.g. using transactions created by an "
+"external OTS server). To ensure the transaction context is propagated via "
+"JRMP invocations to the server, the transaction propagation context factory "
+"needs to be explicitly set for the JRMP invoker proxy. This is done as "
+"follows:"
+msgstr ""
+"É possível coordenar transações a partir de um coordenador que não está "
+"localizado com o servidor do JBoss (por exemplo: usando transações criadas "
+"por um servidor OTS externo). Para garantir que o contexto de transação é "
+"propagado através das invocações JRMP ao servidor, a criação do contexto de "
+"propagação de transação precisa ser claramente configurada para o proxy "
+"invocador JRMP. Isto é feito conforme segue abaixo:"
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,130 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr "JTA 简介"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr "Java Transaction API"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:9
+#, no-c-format
+msgid ""
+"The interfaces specified by the many transaction standards are typically too "
+"low-level for most application programmers. Therefore, Sun Microsystems has "
+"specified higher-level interfaces to assist in the development of "
+"distributed transactional applications. Note, these interfaces are still low-"
+"level, and require, for example, the programmer to be concerned with state "
+"management and concurrency for transactional application. In addition, they "
+"are geared more for applications which require XA resource integration "
+"capabilities, rather than the more general resources which the other APIs "
+"allow."
+msgstr ""
+"对于程序员来说，许多事务标准指定的接口通常都过于涉及底层细节。因此，Sun "
+"Microsystems 已经设计了更高级别的接口来开发分布式事务性应用程序。请注意，这些"
+"接口仍然面向较低级别，要求程序员处理状态管理和并发性。此外，它们更适合需要 "
+"XA 资源集成能力而不是其他 API 允许的普通资源的应用程序。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:12
+#, no-c-format
+msgid ""
+"With reference to [JTA99], distributed transaction services typically "
+"involve a number of participants:"
+msgstr "根据 [JTA99] 协议，分布式事务服务通常涉及许多参与者："
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:17
+#, no-c-format
+msgid ""
+"Application server: which provides the infrastructure required to support "
+"the application run-time environment which includes transaction state "
+"management, for example, an EJB server."
+msgstr ""
+"应用服务器：它提供支持运行环境（包括事务状态管理）所需的基础结构，如 EJB 服务"
+"器。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:22
+#, no-c-format
+msgid ""
+"Transaction manager: provides the services and management functions required "
+"to support transaction demarcation, transactional resource management, "
+"synchronisation and transaction context propagation."
+msgstr ""
+"事务管理者：提供支持事务限界、事务性资源管理、同步和事务上下文传递所需的服务"
+"和管理功能。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:27
+#, no-c-format
+msgid ""
+"Resource manager: (through a resource adapter<footnote> <para> A Resource "
+"Adapter is used by an application server or client to connect to a Resource "
+"Manager. JDBC drivers which are used to connect to relational databases are "
+"examples of Resource Adapters. </para> </footnote>) provides the application "
+"with access to resources. The resource manager participates in distributed "
+"transactions by implementing a transaction resource interface used by the "
+"transaction manager to communicate transaction association, transaction "
+"completion and recovery."
+msgstr ""
+"资源管理者：（通过资源适配器<footnote> <para> 应用服务器或客户端使用资源适配"
+"器（Resource Adapter）来连接资源管理者。其中一个例子是用于连接关系型数据库的 "
+"JDBC 驱动。</para> </footnote>）为应用程序提供对资源的访问。资源管理者通过实"
+"现事务资源接口来管理事务关联、完成和切换。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:36
+#, no-c-format
+msgid ""
+"A communication resource manager (CRM): supports transaction context "
+"propagation and access to the transaction service for incoming and outgoing "
+"requests."
+msgstr ""
+"通信资源管理者（CRM）：支持转入和转出请求的事务上下文传递以及对事务服务的访"
+"问。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:41
+#, no-c-format
+msgid ""
+"From the transaction manager’s perspective, the actual implementation of the "
+"transaction services does not need to be exposed; only high-level interfaces "
+"need to be defined to allow transaction demarcation, resource enlistment, "
+"synchronization and recovery process to be driven from the users of the "
+"transaction services. The JTA is a high-level application interface that "
+"allows a transactional application to demarcate transaction boundaries, and "
+"contains also contains a mapping of the X/Open XA protocol."
+msgstr ""
+"从事务管理者的角度来看，并不需要开放实际的事务服务实现；只需要定义高级别的接"
+"口来允许用户驱动事务限界、资源征用、同步和切换。JTA 是一个高级别的应用程序接"
+"口，它允许事务性应用程序限定事务边界并包含 X/Open XA 协议的映射。"
+
+#. Tag: para
+#: An_Introduction_to_the_JTA.xml:45
+#, no-c-format
+msgid ""
+"The JTA support provided by JBossJTA is compliant with the 1.0.1 "
+"specification."
+msgstr "JBossJTA 提供的 JTA 支持兼容 1.0.1 规格。"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Author_Group.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Author_Group.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,22 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Book_Info.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Book_Info.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,47 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#, fuzzy, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide CP04"
+msgstr "JBoss Transactions JTA 程序员指南"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "用于 JBoss 企业级应用程序平台 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr "本书从程序员的角度讨论 Transactions JTA"
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Configuring_JBossJTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Configuring_JBossJTA.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Configuring_JBossJTA.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,143 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr "配置 JBossJTA"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:8
+#, no-c-format
+msgid "Configuring options"
+msgstr "配置选项"
+
+#. Tag: para
+#: Configuring_JBossJTA.xml:9
+#, no-c-format
+msgid ""
+"The following table shows the configuration features, with default values "
+"shown in italics. For more detailed information, the relevant section "
+"numbers are provided."
+msgstr ""
+"下表显示了配置特性，其中斜体为缺省值。更多的信息，请参考相关章节号指明的章"
+"节。"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:13
+#, no-c-format
+msgid "JBossJTA configuration options."
+msgstr "JBossJTA 配置选项。"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:17
+#, no-c-format
+msgid "Configuration Name"
+msgstr "配置名称"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:20
+#, no-c-format
+msgid "Possibile Values"
+msgstr "可选值"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:23
+#, no-c-format
+msgid "Relevant Section"
+msgstr "相关章节"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:30
+#, no-c-format
+msgid "com.arjuna.ats.jta.supportSubtransactions"
+msgstr "com.arjuna.ats.jta.supportSubtransactions"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr "YES/NO"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr "com.arjuna.ats.jta.jtaTMImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:43
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
+"com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr "com.arjuna.ats.jta.jtaUTImplementation"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:53
+#, no-c-format
+msgid ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+msgstr ""
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
+"arjuna.ats.internal.jta.transaction.jts.UserTransactionImple"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr "com.arjuna.ats.jta.xaBackoffPeriod"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr "com.arjuna.ats.jdbc.isolationLevel"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr "所支持的任何 JDBC 隔离级别。"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr "true/false"
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr "第 3 章"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Examples.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Examples.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Examples.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,818 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr "示例"
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr "JDBC 示例"
+
+#. Tag: para
+#: Examples.xml:9
+#, no-c-format
+msgid ""
+"The following code illustrates many of the points described above (note that "
+"for simplicity, much error checking code has been remove). This example "
+"assumes that you are using the transactional JDBC driver provided with "
+"JBossTS. For details about how to configure and use this driver see the "
+"previous Chapter."
+msgstr ""
+"下面的代码解释了上述的大部分要点（为简单起见，我们删除了许多错误检查代码）。"
+"这个例子假设你使用的是 JBossTS 提供的事务性 JDBC 驱动。关于如何配置和使用这些"
+"驱动的细节，请参考前一章的内容。"
+
+#. Tag: screen
+#: Examples.xml:12
+#, no-c-format
+msgid ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+msgstr ""
+"public class JDBCTest\n"
+"{\n"
+"public static void main (String[] args)\n"
+"{\n"
+" /*\n"
+" */\n"
+" \n"
+" Connection conn = null;\n"
+" Connection conn2 = null;\n"
+" Statement stmt = null; // non-tx statement\n"
+" Statement stmtx = null; // will be a tx-statement\n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"\\nCreating connection to database: "
+"\"+url);\n"
+" \n"
+" /*\n"
+" * Create conn and conn2 so that they are bound to the "
+"JBossTS\n"
+" * transactional JDBC driver. The details of how to do this "
+"will\n"
+" * depend on your environment, the database you wish to use "
+"and\n"
+" * whether or not you want to use the Direct or JNDI "
+"approach. See\n"
+" * the appropriate chapter in the JTA Programmers Guide.\n"
+" */\n"
+" \n"
+" stmt = conn.createStatement(); // non-tx statement\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"DROP TABLE test_table\");\n"
+" stmt.executeUpdate(\"DROP TABLE test_table2\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" // assume not in database.\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a "
+"INTEGER,b INTEGER)\");\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table2 (a "
+"INTEGER,b INTEGER)\");\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" System.out.println(\"Starting top-level transaction."
+"\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement(); // will be a tx-"
+"statement\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 1."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table (a, b) "
+"VALUES (1,2)\");\n"
+" \n"
+" ResultSet res1 = null;\n"
+" \n"
+" System.out.println(\"\\nInspecting table 1.\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nAdding entries to table 2."
+"\");\n"
+" \n"
+" stmtx.executeUpdate(\"INSERT INTO test_table2 (a, b) "
+"VALUES (3,4)\");\n"
+" \n"
+" res1 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" \n"
+" System.out.println(\"\\nInspecting table 2.\");\n"
+" \n"
+" while (res1.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res1.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res1.getInt"
+"(2));\n"
+" }\n"
+" System.out.print(\"\\nNow attempting to rollback "
+"changes.\");\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"rollback();\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"begin();\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" ResultSet res2 = null;\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"1.\");\n"
+" \n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" System.out.println(\"\\nNow checking state of table "
+"2.\");\n"
+" \n"
+" stmtx = conn.createStatement();\n"
+" res2 = stmtx.executeQuery(\"SELECT * FROM test_table2"
+"\");\n"
+" while (res2.next())\n"
+" {\n"
+" System.out.println(\"Column 1: \"+res2.getInt"
+"(1));\n"
+" System.out.println(\"Column 2: \"+res2.getInt"
+"(2));\n"
+" }\n"
+" \n"
+" com.arjuna.ats.jta.UserTransaction.userTransaction()."
+"commit(true);\n"
+" }\n"
+" catch (Exception ex)\n"
+" {\n"
+" ex.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+" }\n"
+" catch (Exception sysEx)\n"
+" {\n"
+" sysEx.printStackTrace();\n"
+" System.exit(0);\n"
+" }\n"
+"}"
+
+#. Tag: title
+#: Examples.xml:16
+#, no-c-format
+msgid "Failure recovery example"
+msgstr "失效切换示例"
+
+#. Tag: para
+#: Examples.xml:17
+#, no-c-format
+msgid ""
+"This class implements the <interfacename>XAResourceRecovery</interfacename> "
+"interface for <code>XAResources</code>. The parameter supplied in "
+"setParameters can contain arbitrary information necessary to initialize the "
+"class once created. In this instance it contains the name of the property "
+"file in which the db connection information is specified, as well as the "
+"number of connections that this file contains information on (separated "
+"by ;)."
+msgstr ""
+"这个类实现了 <code>XAResources</code> 的 <interfacename>XAResourceRecovery</"
+"interfacename> 接口。setParameters 提供的参数可以包含初始化类的任何信息。在这"
+"个例子里，它包含指定了数据库连接信息的属性文件的名称，以及这个文件的信息涉及"
+"的连接的序号（以 ; 隔开）。"
+
+#. Tag: para
+#: Examples.xml:21
+#, no-c-format
+msgid ""
+"This is only an <emphasis>example</emphasis> of the sorts of things an "
+"<code>XAResourceRecovery</code> implementer could do. This implementation "
+"uses a property file that is assumed to contain sufficient information to "
+"recreate connections used during the normal run of an application so that we "
+"can perform recovery on them. It is not recommended that information such as "
+"user name and password appear in such a raw text format as it opens up a "
+"potential security hole."
+msgstr ""
+"<code>XAResourceRecovery</code> 实现执行只是一些<emphasis>示例</emphasis>功"
+"能。它使用一个包含重新创建在正常运行时的连接所需的足够信息的属性文件，这样我"
+"们就可以根据它执行切换。我们不推荐在这样一个明码文本文件里出现用户名和密码等"
+"信息，因为这可能导致安全漏洞。"
+
+#. Tag: para
+#: Examples.xml:25
+#, no-c-format
+msgid ""
+"The db parameters specified in the property file are assumed to be in the "
+"format:"
+msgstr "我们假定属性文件里指定的数据库参数具有下列的格式："
+
+#. Tag: para
+#: Examples.xml:30
+#, no-c-format
+msgid "DB_x_DatabaseURL="
+msgstr "DB_x_DatabaseURL="
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr "DB_x_DatabaseUser="
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr "DB_x_DatabasePassword="
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr "DB_x_DatabaseDynamicClass="
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr "这里的 x 是连接信息的序号。"
+
+#. Tag: para
+#: Examples.xml:54
+#, no-c-format
+msgid ""
+"Some error handling code has been removed from this text for ease of "
+"readability purposes."
+msgstr "出于易读性考虑，我们删除了一些错误处理代码。"
+
+#. Tag: screen
+#: Examples.xml:58
+#, no-c-format
+msgid ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+msgstr ""
+"/*\n"
+" * Some XAResourceRecovery implementations will do their startup work here,\n"
+" * and then do little or nothing in setDetails. Since this one needs to "
+"know\n"
+" * dynamic class name, the constructor does nothing.\n"
+" */\n"
+" \n"
+"public BasicXARecovery () throws SQLException\n"
+"{\n"
+" numberOfConnections = 1;\n"
+" connectionIndex = 0;\n"
+" props = null;\n"
+"}\n"
+" \n"
+"/*\n"
+" * The recovery module will have chopped off this class name already. The\n"
+" * parameter should specify a property file from which the url, user name,\n"
+" * password, etc. can be read.\n"
+" * \n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.initexp An exception\n"
+" * occurred during initialisation.\n"
+" */\n"
+" \n"
+"public boolean initialise (String parameter) throws SQLException\n"
+"{\n"
+" if (parameter == null) \n"
+" return true;\n"
+" \n"
+" int breakPosition = parameter.indexOf(BREAKCHARACTER);\n"
+" String fileName = parameter;\n"
+" \n"
+" if (breakPosition != -1)\n"
+" {\n"
+" fileName = parameter.substring(0, breakPosition - 1);\n"
+" \n"
+" try\n"
+" {\n"
+" numberOfConnections = Integer.parseInt(parameter."
+"substring(breakPosition + 1));\n"
+" }\n"
+" catch (NumberFormatException e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" }\n"
+" \n"
+" try\n"
+" {\n"
+" String uri = com.arjuna.common.util.FileLocator.locateFile"
+"(fileName);\n"
+" jdbcPropertyManager.propertyManager.load(XMLFilePlugin.class."
+"getName(), uri);\n"
+" \n"
+" props = jdbcPropertyManager.propertyManager.getProperties"
+"();\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" return false;\n"
+" }\n"
+" \n"
+" return true;\n"
+"}\n"
+" \n"
+"/*\n"
+" * @message com.arjuna.ats.internal.jdbc.recovery.xarec {0} could not find\n"
+" * information for connection!\n"
+" */\n"
+" \n"
+"public synchronized XAResource getXAResource () throws SQLException\n"
+"{\n"
+" JDBC2RecoveryConnection conn = null;\n"
+" \n"
+" if (hasMoreResources())\n"
+" {\n"
+" connectionIndex++;\n"
+" \n"
+" conn = getStandardConnection();\n"
+" \n"
+" if (conn == null) conn = getJNDIConnection();\n"
+" }\n"
+" \n"
+" return conn.recoveryConnection().getConnection()."
+"getXAResource();\n"
+"}\n"
+" \n"
+"public synchronized boolean hasMoreResources ()\n"
+"{\n"
+" if (connectionIndex == numberOfConnections) \n"
+" return false;\n"
+" else\n"
+" return true;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getStandardConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + number + urlTag);\n"
+" String password = new String(dbTag + number + passwordTag);\n"
+" String user = new String(dbTag + number + userTag);\n"
+" String dynamicClass = new String(dbTag + number + dynamicClassTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" String dc = props.getProperty(dynamicClass);\n"
+" \n"
+" if (dc != null)\n"
+" dbProperties.put(TransactionalDriver.dynamicClass, "
+"dc);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private final JDBC2RecoveryConnection getJNDIConnection ()\n"
+" throws SQLException\n"
+"{\n"
+" String number = new String(\"\" + connectionIndex);\n"
+" String url = new String(dbTag + jndiTag + number + urlTag);\n"
+" String password = new String(dbTag + jndiTag + number + "
+"passwordTag);\n"
+" String user = new String(dbTag + jndiTag + number + userTag);\n"
+" \n"
+" Properties dbProperties = new Properties();\n"
+" \n"
+" String theUser = props.getProperty(user);\n"
+" String thePassword = props.getProperty(password);\n"
+" \n"
+" if (theUser != null)\n"
+" {\n"
+" dbProperties.put(TransactionalDriver.userName, theUser);\n"
+" dbProperties.put(TransactionalDriver.password, "
+"thePassword);\n"
+" \n"
+" return new JDBC2RecoveryConnection(url, dbProperties);\n"
+" }\n"
+" else\n"
+" return null;\n"
+"}\n"
+" \n"
+"private int numberOfConnections;\n"
+"private int connectionIndex;\n"
+"private Properties props;\n"
+"private static final String dbTag = \"DB_\";\n"
+"private static final String urlTag = \"_DatabaseURL\";\n"
+"private static final String passwordTag = \"_DatabasePassword\";\n"
+"private static final String userTag = \"_DatabaseUser\";\n"
+"private static final String dynamicClassTag = \"_DatabaseDynamicClass\";\n"
+"private static final String jndiTag = \"JNDI_\";\n"
+" \n"
+"/*\n"
+" * Example:\n"
+" * \n"
+" * DB2_DatabaseURL=jdbc\\:arjuna\\:sequelink\\://qa02\\:20001\n"
+" * DB2_DatabaseUser=tester2 DB2_DatabasePassword=tester\n"
+" * DB2_DatabaseDynamicClass=com.arjuna.ats.internal.jdbc.drivers."
+"sequelink_5_1\n"
+" * \n"
+" * DB_JNDI_DatabaseURL=jdbc\\:arjuna\\:jndi DB_JNDI_DatabaseUser=tester1\n"
+" * DB_JNDI_DatabasePassword=tester DB_JNDI_DatabaseName=empay\n"
+" * DB_JNDI_Host=qa02 DB_JNDI_Port=20000\n"
+" */\n"
+"\n"
+" private static final char BREAKCHARACTER = ';'; // delimiter for "
+"parameters"
+
+#. Tag: para
+#: Examples.xml:59
+#, no-c-format
+msgid ""
+"The class <classname>com.arjuna.ats.internal.jdbc.recovery."
+"JDBC2RecoveryConnection</classname> may be used to create a new connection "
+"to the database using the same parameters that were used to create the "
+"initial connection."
+msgstr ""
+"<classname>com.arjuna.ats.internal.jdbc.recovery.JDBC2RecoveryConnection</"
+"classname> 类可根据创建初始连接的参数创建新的连接。"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/JBoss_Transactions_JTA_Programmers_Guide_CP04.po
===================================================================
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,919 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr "JDBC 和事务"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr "使用事务性的 JDBC 驱动"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:9
+#, no-c-format
+msgid ""
+"JBossJTA supports the construction of both local and distributed "
+"transactional applications which access databases using the JDBC 2.0 APIs. "
+"JDBC 2.0 supports two-phase commit of transactions, and is similar to the XA "
+"X/Open standard. The JDBC 2.0 support is found in the com.arjuna.ats.jdbc "
+"package."
+msgstr ""
+"JBossJTA 支持构建本地和分布式的用 JDBC 2.0 API 访问数据库的事务性应用程序。"
+"JDBC 2.0 支持两阶段的事务提交，这和 XA X/Open 标准类似。在 com.arjuna.ats."
+"jdbc 包里有相关的 JDBC 2.0 内容。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:12
+#, no-c-format
+msgid ""
+"The JDBC 2.0 support has been tested with the following drivers and "
+"databases:"
+msgstr "我们已经针对下列的驱动和数据库测试了对 JDBC 2.0 的支持："
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr "Oracle 8.1.6/8.1.7, 9i 和 10g thin driver"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr "MS SQL Server 2000 native driver"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:27
+#, no-c-format
+msgid "In the past we have qualified against:"
+msgstr "过去我们已经认证了："
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:32
+#, no-c-format
+msgid "Merant’s Sequelink 5.1 with Oracle 8.1.6"
+msgstr "Merant 的 Sequelink 5.1 和 Oracle 8.1.6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr "Cloudscape 3.6（附带自己的数据库）"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:42
+#, no-c-format
+msgid ""
+"However, these drivers and databases are no longer part of our supported "
+"platforms. They may continue to work with JBossTS, but we cannot make that "
+"guarantee."
+msgstr ""
+"然而，这些驱动和数据库不再是我们支持的平台。它们可能可以继续和 JBossTS 一起使"
+"用，但我们并不保证这一点。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:46
+#, no-c-format
+msgid "Managing transactions"
+msgstr "管理事务"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:47
+#, no-c-format
+msgid ""
+"JBossJTA must be able to associate work performed on a JDBC connection with "
+"a specific transaction. Therefore, implicit transaction propagation and/or "
+"indirect transaction management must be used by applications, i.e., for each "
+"JDBC connection it must be possible for JBossJTA to determine the invoking "
+"thread’s current transaction context."
+msgstr ""
+"JBossJTA 必须能够将在 JDBC 连接上进行的操作和特定的事务相关联。因此，应用程序"
+"必须使用隐性的事务传递和/或间接的事务管理，那就是说，对于每个 JDBC 连接，"
+"JBossJTA 都必须能够获得调用线程的当前事务上下文。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:52
+#, no-c-format
+msgid "Restrictions"
+msgstr "限制"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:53
+#, no-c-format
+msgid ""
+"The following restrictions are imposed by limitations in the JDBC "
+"specifications and by JBossJTA to ensure that transactional interactions "
+"with JDBC databases can be correctly managed:"
+msgstr ""
+"JDBC 规格和 JBossJTA 强加了下列的限制来确保正确管理和 JDBC 数据库的事务性交"
+"互。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:57
+#, no-c-format
+msgid ""
+"Nested transactions are not supported by JDBC 2.0. If an attempt is made to "
+"use a JDBC connection within a subtransaction, JBossJTA will throw a "
+"suitable exception and no work will be allowed on that connection. However, "
+"if you wish to have nested transactions, then you can set the <property>com."
+"arjuna.ats.jta.supportSubtransactions</property> property to YES."
+msgstr ""
+"JDBC 2.0 不支持嵌套事务。如果试图在子事务里使用 JDBC 连接，JBossJTA 将抛出相"
+"应的异常，该连接也不会允许任何操作。然而，如果你希望使用嵌套的事务，你可以设"
+"置 <property>com.arjuna.ats.jta.supportSubtransactions</property> 为 YES。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:63
+#, no-c-format
+msgid "Transactional drivers"
+msgstr "事务性驱动"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:64
+#, no-c-format
+msgid ""
+"The JBossJTA approach to incorporating JDBC connections within transactions "
+"is to provide transactional JDBC drivers through which all interactions "
+"occur. These drivers intercept all invocations and ensure that they are "
+"registered with, and driven by, appropriate transactions. There is a single "
+"type of transactional driver through which any JDBC driver can be driven; "
+"obviously if the database is not transactional then ACID properties cannot "
+"be guaranteed. This driver is <code>com.arjuna.ats.jdbc.TransactionalDriver</"
+"code>, which implements the <interfacename>java.sql.Driver</interfacename> "
+"interface."
+msgstr ""
+"JBossJTA 把 JDBC 连接合并在事务里来提供所有交互都涉及的事务性 JDBC 驱动。这些"
+"驱动拦截所有的调用，确保它们向合适的事务注册并由之驱动。明显地，如果数据库不"
+"是事务性的，那么 ACID 属性也不能被保证。这个驱动是 <code>com.arjuna.ats.jdbc."
+"TransactionalDriver</code>，它实现了 <interfacename>java.sql.Driver</"
+"interfacename> 接口。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:68
+#, no-c-format
+msgid "Loading drivers"
+msgstr "加载驱动"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:69
+#, no-c-format
+msgid ""
+"The driver may be directly instantiated and used within an application. For "
+"example:"
+msgstr "这个驱动可以直接初始化或在应用程序内部使用。例如："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:73
+#, no-c-format
+msgid "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+msgstr "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:74
+#, no-c-format
+msgid ""
+"They can be registered with the JDBC driver manager (<code>java.sql."
+"DriverManager</code>) by adding them to the Java system properties. The "
+"<property>jdbc.drivers</property> property contains a list of driver class "
+"names, separated by colons, that are loaded by the JDBC driver manager when "
+"it is initialized."
+msgstr ""
+"把它们添加到 Java 系统属性里就可以注册到 JDBC 驱动管理者（<code>java.sql."
+"DriverManager</code>）。<property>jdbc.drivers</property> 属性有一个以冒号隔"
+"开的驱动类名的列表，它在初始化时由 JDBC 驱动管理者加载。"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:77
+#, no-c-format
+msgid ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+msgstr ""
+"/*\n"
+" * Register the driver via the system properties variable\n"
+" * \"jdbc.drivers\"\n"
+" */ \n"
+" \n"
+"Properties p = System.getProperties(); \n"
+" \n"
+"switch (dbType)\n"
+"{\n"
+"case MYSQL:\n"
+" p.put(\"jdbc.drivers\", \"org.gjt.mm.mysql.Driver\"); \n"
+" break;\n"
+"case CLOUDSCAPE:\n"
+" p.put(\"jdbc.drivers\", \"COM.cloudscape.core.JDBCDriver\"); \n"
+" break;\n"
+"}\n"
+" \n"
+"System.setProperties(p);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:78
+#, no-c-format
+msgid ""
+"Alternatively, the <methodname>Class.forName()</methodname> method may be "
+"used to load the driver or drivers:"
+msgstr "此外，<methodname>Class.forName()</methodname> 方法也可用来加载驱动："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:82
+#, no-c-format
+msgid ""
+"Calling <methodname>Class.forName()</methodname> will automatically register "
+"the driver with the JDBC driver manager. It is also possible to explicitly "
+"create an instance of the JDBC driver:"
+msgstr ""
+"调用 <methodname>Class.forName()</methodname> 将自动把这个驱动注册到 JDBC 驱"
+"动管理者。你也可以显性地创建这个 JDBC 驱动的实例："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:85
+#, no-c-format
+msgid ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+msgstr ""
+"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
+" \n"
+"DriverManager.registerDriver(drv);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:86
+#, no-c-format
+msgid ""
+"When you have loaded a driver, it is available for making a connection with "
+"a DBMS."
+msgstr "当你加载了驱动后，它就可用来和 DBMS 建立连接。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:92
+#, no-c-format
+msgid "Connections"
+msgstr "连接"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:93
+#, no-c-format
+msgid ""
+"In this section we shall discuss the notion of transactional JDBC "
+"connections, how they are managed within JBossJTA and the implications on "
+"using them within an application."
+msgstr ""
+"本节我们将讨论事务性 JDBC 连接、JBossJTA 如何管理它们以及在应用程序里如何使"
+"用。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:97
+#, no-c-format
+msgid "Making the connection"
+msgstr "建立连接"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:98
+#, no-c-format
+msgid ""
+"Because JDBC connectivity in JBossJTA works by simply providing a new JDBC "
+"driver, application code can remain relatively the same to that when not "
+"using transactions. Typically, the application programmer need only start "
+"and terminate transactions."
+msgstr ""
+"因为只需提供新的 JDBC 驱动，JBossJTA 里的 JDBC 连接性就可以工作，程序代码可以"
+"和不使用事务的代码保持基本相同。通常，程序员只需要启动和终止事务。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr "JDBC 2.0"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:104
+#, no-c-format
+msgid ""
+"Before describing the JDBC 2.0 support it is necessary to mention that the "
+"following properties can be set and passed to the JBossJTA driver (they are "
+"all located in the <classname>com.arjuna.ats.jdbc.TransactionalDriver</"
+"classname> class):"
+msgstr ""
+"在描述对 JDBC 2.0 的支持之前，需要提及的是，你可以设置下列的属性并传递给 "
+"JBossJTA 驱动（它们位于 <classname>com.arjuna.ats.jdbc.TransactionalDriver</"
+"classname> 类里）："
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:110
+#, no-c-format
+msgid ""
+"<property>userName</property>: the user name to use when attempting to "
+"connect to the database."
+msgstr "<property>userName</property>：连接数据库所用的用户名。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:115
+#, no-c-format
+msgid ""
+"<property>password</property>: the password to use when attempting to "
+"connect to the database."
+msgstr "<property>password</property>：连接数据库时所用的密码。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:120
+#, no-c-format
+msgid ""
+"<property>createDb</property>: if set to true, the driver will attempt to "
+"create the database when it connects. This may not be supported by all JDBC "
+"2.0 implementations."
+msgstr ""
+"<property>createDb</property>：如果为 true，驱动在连接时将试图创建数据库。不"
+"是所有的 JDBC 2.0 实现都支持这个属性。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:125
+#, no-c-format
+msgid ""
+"<property>dynamicClass</property>: this specifies a class to instantiate to "
+"connect to the database, rather than using JNDI."
+msgstr ""
+"<property>dynamicClass</property>：指定连接数据库时实例化类，而不是使用 "
+"JNDI。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr "XADataSources"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:132
+#, no-c-format
+msgid ""
+"JDBC 2.0 connections are created from appropriate DataSources. Those "
+"connections which must participate within distributed transactions are "
+"obtained from <code>XADataSources</code>. Therefore, when using a JDBC 2.0 "
+"driver, JBossJTA will use the appropriate DataSource whenever a connection "
+"to the database is made. It will then obtain <code>XAResources</code> and "
+"register them with the transaction via the JTA interfaces. It is these "
+"<code>XAResources</code> which the transaction service will use when the "
+"transaction terminates in order to drive the database to either commit or "
+"rollback the changes made via the JDBC connection."
+msgstr ""
+"JDBC 2.0 连接根据合适的数据源创建。必须参与分布式事务的连接根据 "
+"<code>XADataSources</code> 创建。因此，当使用 JDBC 2.0 驱动时，每当创建一个数"
+"据库连接 JBossJTA 都将使用合适的数据源。它将获得 <code>XAResources</code> 并"
+"通过 JTA 接口向事务注册。事务终止时，事务服务将使用这些 <code>XAResources</"
+"code> 来驱动数据库对通过 JDBC 连接进行的修改执行提交或回滚。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:136
+#, no-c-format
+msgid ""
+"There are two ways in which the JBossJTA JDBC 2.0 support can obtain "
+"<code>XADataSources</code>. These will be explained in the following "
+"sections. Note, for simplicity we shall assume that the JDBC 2.0 driver is "
+"instantiated directly by the application."
+msgstr ""
+"JBossJTA 的 JDBC 2.0 支持可以两种方式获取 <code>XADataSources</code>。我们将"
+"在后续章节里进行解释。请注意，为了简单起见，我们假设 JDBC 2.0 驱动是应用程序"
+"直接实例化的。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr "Java 名称和目录接口（Java Naming and Directory Interface，JNDI）"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:141
+#, no-c-format
+msgid ""
+"In order to allow a JDBC driver to use arbitrary DataSources without having "
+"to know specific details about their implementations, DataSources are "
+"typically obtained from JNDI. A specific (XA)DataSource can be created and "
+"registered with an appropriate JNDI implementation, and the application (or "
+"JDBC driver) can later bind to and use it. Since JNDI only allows the "
+"application to see the (XA)DataSource as an instance of the interface (for "
+"example, <property>javax.sql.XADataSource</property>) rather than as an "
+"instance of the implementation class (for example, <property>com.mydb."
+"myXADataSource</property>), the application is not tied at build time to "
+"only use a specific (XA)DataSource implementation."
+msgstr ""
+"为了允许 JDBC 驱动使用任意的数据源而不需知道相关实现的细节，数据源通常通过 "
+"JNDI 获取。专有的 (XA)DataSource 可以用合适的 JNDI 实现创建和注册，之后应用程"
+"序（或 JDBC 驱动）可以绑定并使用它。既然 JNDI 只允许应用程序把 (XA)"
+"DataSource 作为接口实例（如 <property>javax.sql.XADataSource</property>）而不"
+"是实现类的实例（ <property>com.mydb.myXADataSource</property>）对待，应用程序"
+"就不会在构建时只使用专门的 (XA)DataSource 实现。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:145
+#, no-c-format
+msgid ""
+"To get the <classname>TransactionalDriver</classname> class to use a JNDI "
+"registered <code>XADataSource</code> it is first necessary to create the "
+"<code>XADataSource</code> instance and store it in an appropriate JNDI "
+"implementation. Details of how to do this can be found in the JDBC 2.0 "
+"tutorial available at JavaSoft. An example is show below:"
+msgstr ""
+"为了获取 <classname>TransactionalDriver</classname> 类来使用已注册 JNDI 的 "
+"<code>XADataSource</code>，你首先得创建一个 <code>XADataSource</code> 并将其"
+"存储在合适的 JNDI 实现里。相关细节可以在 JavaSoft 的 JDBC 2.0 教程里找到。下"
+"面是一个例子："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:148
+#, no-c-format
+msgid ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+msgstr ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:149
+#, no-c-format
+msgid ""
+"Where the <property>Context.INITIAL_CONTEXT_FACTORY</property> property is "
+"the JNDI way of specifying the type of JNDI implementation to use."
+msgstr ""
+"这里的 <property>Context.INITIAL_CONTEXT_FACTORY</property> 属性以 JNDI 凡是"
+"指定使用的 JNDI 实现的类型。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:152
+#, no-c-format
+msgid ""
+"Then the application must pass an appropriate connection URL to the JDBC 2.0 "
+"driver:"
+msgstr "然后应用程序必须传递合适的连接 URL 给 JDBC 2.0 驱动："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:155
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:jdbc/foo\", "
+"dbProps);"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:156
+#, no-c-format
+msgid ""
+"The JNDI URL must be pre-pended with jdbc:arjuna: in order for the "
+"<code>ArjunaJDBC2Driver</code> to recognise that the DataSource must "
+"participate within transactions and be driven accordingly."
+msgstr ""
+"JNDI URL 必须以 jdbc:arjuna: 开头，这样 <code>ArjunaJDBC2Driver</code> 才能够"
+"知道这个数据源必须参与事务并相应地被驱动。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:160
+#, no-c-format
+msgid "Dynamic class instantiation"
+msgstr "动态的类实例化"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:161
+#, no-c-format
+msgid ""
+"Many JDBC 2.0 implementations provide proprietary implementations of "
+"<interfacename>XADataSources</interfacename> that provide non-standard "
+"extensions to the specification. In order to allow the application to remain "
+"isolated from the actual JDBC 2.0 implementation it is using and yet "
+"continue to be able to use these extensions, JBossJTA hides the details of "
+"these proprietary implementations using dynamic class instantiation. In "
+"addition, the use of JNDI is not required when using this mechanism because "
+"the actual implementation of the <interfacename>XADataSource</interfacename> "
+"will be directly instantiated, albeit in a manner which will not tie an "
+"application or driver to a specific implementation. JBossJTA therefore has "
+"several classes which are for specific JDBC 2.0 implementations, and these "
+"can be selected at runtime by the application setting the "
+"<property>dynamicClass</property> property appropriately:"
+msgstr ""
+"许多 JDBC 2.0 实现都提供 <interfacename>XADataSources</interfacename> 的私有"
+"实现，从而实现规格的非标准扩展。为了允许应用程序和它使用的实际的 JDBC 2.0 实"
+"现隔离，并能够使用这些非标准扩展，JBossJTA 用动态类实例化隐藏了这些私有实现的"
+"细节。此外，使用这个机制也不要求使用 JNDI，因为 <interfacename>XADataSource</"
+"interfacename> 的实际实现不会被直接地实例化，从而不会把应用程序或驱动捆绑到专"
+"门的实现上。因此，JBossJTA 拥有几个用于专有的 JDBC 2.0 实现的类，这些类可以通"
+"过设置 <property>dynamicClass</property> 属性在运行时选定："
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:166
+#, no-c-format
+msgid "Dynamic Class property values for specific databases"
+msgstr "专有数据库的动态类属性值"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:170
+#, no-c-format
+msgid "Database Type"
+msgstr "数据库类型"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:173
+#, no-c-format
+msgid "Property Name"
+msgstr "属性名"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:180
+#, no-c-format
+msgid "Cloudscape 3.6"
+msgstr "Cloudscape 3.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr "Sequelink 5.1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr "Oracle 8.1.6"
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:207
+#, no-c-format
+msgid ""
+"As mentioned earlier, JBossTS no longer supports Cloudscape or Sequelink as "
+"part of the qualified drivers. Furthermore, we recommend using JNDI to "
+"obtain JDBC classes rather than the direct method described here."
+msgstr ""
+"如果前面所提及的，JBossTS 不再把 Cloudscape 和 Sequelink 作为认证的驱动来支"
+"持。而且，我们推荐使用 JNDI 来获取 JDBC 类而不是采用这里描述的直接方法。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:211
+#, no-c-format
+msgid ""
+"The application code must specify which dynamic class the "
+"<code>TransactionalDriver</code> should instantiate when setting up the "
+"connection:"
+msgstr ""
+"应用程序代码必须指定在建立连接时 <code>TransactionalDriver</code> 应该实例化"
+"哪个动态类："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:214
+#, no-c-format
+msgid ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+msgstr ""
+"Properties dbProps = new Properties();\n"
+" \n"
+"dbProps.setProperty(TransactionalDriver.userName, \"user\");\n"
+"dbProps.setProperty(TransactionalDriver.password, \"password\");\n"
+"dbProps.setProperty(TransactionalDriver.dynamicClass,\n"
+"\"com.arjuna.ats.internal.jdbc.drivers.sequelink_5_0\");\n"
+" \n"
+"TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();\n"
+"Connection connection = arjunaJDBC2Driver.connect(\"jdbc:arjuna:sequelink://"
+"host:port;databaseName=foo\",dbProperties);"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:216
+#, no-c-format
+msgid "Using the connection"
+msgstr "使用连接"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:217
+#, no-c-format
+msgid ""
+"Once the connection has been established (for example, using the "
+"<methodname>java.sql.DriverManager.getConnection</methodname> method), all "
+"operations on the connection will be monitored by JBossJTA. Note, it is not "
+"necessary to use the transactional connection within transactions. If a "
+"transaction is not present when the connection is used, then operations will "
+"be performed directly on the database."
+msgstr ""
+"一旦建立了连接（例如，使用 <methodname>java.sql.DriverManager.getConnection</"
+"methodname> 方法），JBossJTA 将监控该连接上的所有操作。请注意，在事务里使用事"
+"务性连接并非必需的。如果使用连接时，而事务并未启动，相关操作将直接在数据库上"
+"进行。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr "JDBC 不支持子事务。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:226
+#, no-c-format
+msgid ""
+"Transaction timeouts can be used to automatically terminate transactions "
+"should the connection not be terminated within an appropriate period."
+msgstr "如果连接在某段时间内没有终止，系统将根据事务超时时间自动终止这个事务。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:229
+#, no-c-format
+msgid ""
+"JBossJTA connections can be used within multiple different transactions "
+"simultaneously, for instance, different threads, with different notions of "
+"the current transaction, may use the same JDBC connection. JBossJTA does "
+"connection pooling for each transaction within the JDBC connection. So, "
+"although multiple threads may use the same instance of the JDBC connection, "
+"internally this may be using a different connection instance per "
+"transaction. With the exception of close, all operations performed on the "
+"connection at the application level will only be performed on this "
+"transaction-specific connection."
+msgstr ""
+"JBossJTA 连接可以在多个不同的事务里同时使用，例如，在不同的线程里使用和当前事"
+"务不同的标记就可能使用相同的 JDBC 连接。JBossJTA 为 JDBC 连接里的每个事务使用"
+"连接池。所以，虽然多个线程可能使用相同的 JDBC 连接实例，但在内部可能为每个事"
+"务都使用了不同的连接实例。除了关闭操作，连接上的应用程序级别的所有操作都只在"
+"该事务专有的连接上进行。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:232
+#, no-c-format
+msgid ""
+"JBossJTA will automatically register the JDBC driver connection with the "
+"transaction via an appropriate resource . When the transaction terminates, "
+"this resource will be responsible for either committing or rolling back any "
+"changes made to the underlying database via appropriate calls on the JDBC "
+"driver."
+msgstr ""
+"JBossJTA 将通过合适的资源自动向事务注册 JDBC 驱动连接。当事务终止时，这个资源"
+"将通过合适的 JDBC 驱动调用负责提交或回滚任何对底层数据库的修改。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:235
+#, no-c-format
+msgid ""
+"Once created, the driver and any connection can be used in the same way as "
+"any other JDBC driver or connection."
+msgstr ""
+"一旦被创建，这个驱动和任何连接可以和其他任何 JDBC 驱动或连接一样地使用。"
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:238
+#, no-c-format
+msgid ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+msgstr ""
+"Statement stmt = conn.createStatement();\n"
+" \n"
+"try\n"
+"{\n"
+" stmt.executeUpdate(\"CREATE TABLE test_table (a INTEGER,b INTEGER)"
+"\");\n"
+"}\n"
+"catch (SQLException e)\n"
+"{\n"
+" // table already exists\n"
+"}\n"
+" \n"
+"stmt.executeUpdate(\"INSERT INTO test_table (a, b) VALUES (1,2)\");\n"
+" \n"
+"ResultSet res1 = stmt.executeQuery(\"SELECT * FROM test_table\");"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:240
+#, no-c-format
+msgid "Connection pooling"
+msgstr "连接池"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:241
+#, no-c-format
+msgid ""
+"For each user name and password, JBossJTA will maintain a single instance of "
+"each connection for as long as that connection is in use. Subsequent "
+"requests for the same connection will get a reference to the originally "
+"created connection, rather than a new instance. Attempts to close the "
+"connection are allowed, but the connection will only actually be closed when "
+"all users (including transactions) have either finished with the connection, "
+"or issued close calls."
+msgstr ""
+"对于每个用户名和密码，只要连接仍在使用，JBossJTA 将维护每个连接的单一实例。随"
+"后对相同连接的请求将获得原始连接的引用，而不是创建一个新的实例。关闭这个连接"
+"是允许的，但连接只有在所有的用户（包括事务）已经完成了对它的使用或执行 close "
+"调用后才真正被关闭。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:246
+#, no-c-format
+msgid "Reusing connections"
+msgstr "连接重用"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:247
+#, no-c-format
+msgid ""
+"Some JDBC drivers allow the reuse of a connection for multiple different "
+"transactions once a given transaction has completed. Unfortunately this is "
+"not a common feature, and other drivers require a new connection to be "
+"obtained for each new transaction. By default, the JBossJTA transactional "
+"driver will always obtain a new connection for each new transaction. "
+"However, if an existing connection is available and is currently unused, it "
+"is possible to make JBossJTA reuse this connection. In order to do this, the "
+"reuseconnection=true option must be specified on the JDBC URL. For example:"
+msgstr ""
+"在给定的事务结束后，某些 JDBC 驱动允许将连接重用于其他不同的事务。可惜的是，"
+"这并非是共有的功能，有些驱动要求对每个新事务都使用新的连接。在缺省情况下，"
+"JBossJTA 事务性驱动将为每个新事务获取一个新的连接。然而，如果存在空闲的可用现"
+"有连接，JBossJTA 就有可能重用这个连接。为了实现这一点，在 JDBC URL 上必须指"
+"定 reuseconnection=true 选项。例如："
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+"jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:253
+#, no-c-format
+msgid "Terminating the transaction"
+msgstr "终止事务"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:254
+#, no-c-format
+msgid ""
+"Whenever a transaction terminates (either explicitly by the application "
+"programmer, or implicitly when any associated transaction timeout expires) "
+"that has a JDBC connection registered with it, JBossJTA will drive the "
+"database (via the JDBC driver) to either commit or roll back any changes "
+"made to it. This happens transparently to the application."
+msgstr ""
+"每当有 JDBC 连接注册的事务终止时（显性地通过程序或关联的事务过期时），"
+"JBossJTA 将驱动数据库（通过这个 JDBC 驱动）来提交或回滚任何修改。这对于应用程"
+"序来说是透明的。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr "AutoCommit"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:260
+#, no-c-format
+msgid ""
+"If <code>AutoCommit</code> of the <code>java.sql.Connection</code> is set to "
+"true for JDBC 1.0 then the execution of every SQL statement is a separate "
+"top-level transaction, and grouping multiple statements to be managed within "
+"a single OTS transaction is not possible. Therefore, JBossJTA will disable "
+"<code>AutoCommit</code> on JDBC 1.0 connections before they can be used. If "
+"auto commit is subsequently set to true by the application, JBossJTA will "
+"raise the <code>java.sql.SQLException</code>."
+msgstr ""
+"对于 JDBC 1.0 来说，如果 <code>java.sql.Connection</code> 的 "
+"<code>AutoCommit</code> 设置为 true，那么每个 SQL 语句的执行都是单独的顶层事"
+"务，你不可能把多个语句分组来并在单一的 OTS 事务里进行管理。因此，JBossJTA 将"
+"禁用 JDBC 1.0 连接的 <code>AutoCommit</code>。之后如果在程序里把它设置为 "
+"true，JBossJTA 将抛出 <code>java.sql.SQLException</code>。"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:265
+#, no-c-format
+msgid "Setting isolation levels"
+msgstr "设置隔离级别"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:266
+#, no-c-format
+msgid ""
+"When using the JBossJTA JDBC driver, it may be necessary to set the "
+"underlying transaction isolation level on the XA connection. By default, "
+"this is set to <code>TRANSACTION_SERIALIZABLE</code>, but you may want to "
+"set this to something more appropriate for your application. In order to do "
+"this, set the <property>com.arjuna.ats.jdbc.isolationLevel</property> "
+"property to the appropriate isolation level in string form, for example, "
+"<code>TRANSACTION_READ_COMMITTED</code>, or "
+"<code>TRANSACTION_REPEATABLE_READ</code>."
+msgstr ""
+"当使用 JBossJTA JDBC 驱动时，你需要设置 XA 连接的底层事务隔离级别。在缺省情况"
+"下，它的值为 <code>TRANSACTION_SERIALIZABLE</code>，但你可能希望设置其为更合"
+"适的值。为了实现这一点，你可以以字符串的形式把 <property>com.arjuna.ats.jdbc."
+"isolationLevel</property> 设置为想要的隔离级别，例如，"
+"<code>TRANSACTION_READ_COMMITTED</code> 或 "
+"<code>TRANSACTION_REPEATABLE_READ</code>。"
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:271
+#, no-c-format
+msgid ""
+"At present this property applies to all XA connections created in the JVM."
+msgstr "目前，这个属性适用于 JVM 里创建的所有 XA 连接。"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Preface.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Preface.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,22 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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 "序言"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Revision_History.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Revision_History.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,28 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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 "修订历史记录"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,826 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#: The_Resource_Manager.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "测试"
+
+#. Tag: para
+#: The_Resource_Manager.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "This is a test paragraph"
+
+#. Tag: title
+#: The_Resource_Manager.xml:11
+#, no-c-format
+msgid "The XAResource Interface"
+msgstr "XAResource 接口"
+
+#. Tag: para
+#: The_Resource_Manager.xml:12
+#, no-c-format
+msgid ""
+"Whereas some transaction specifications and systems define a generic "
+"resource which can be used to register arbitrary resources with a "
+"transaction, the JTA is much more XA specific. The <interfacename>javax."
+"transaction.xa.XAResource</interfacename> interface is a Java mapping of the "
+"<interfacename>XA</interfacename> interface. The <interfacename>XAResource</"
+"interfacename> interface defines the contract between a Resource Manager and "
+"a Transaction Manager in a distributed transaction processing environment. A "
+"resource adapter for a resource manager implements the "
+"<interfacename>XAResource</interfacename> interface to support association "
+"of a top-level transaction to a resource such as a relational database."
+msgstr ""
+"虽然一些事务规格和系统定义了可用在事务里注册任意资源的通用资源，JTA 更依赖于 "
+"XA。<interfacename>javax.transaction.xa.XAResource</interfacename> 接口是一"
+"个 <interfacename>XA</interfacename> 接口的 Java 映射。"
+"<interfacename>XAResource</interfacename> 接口定义了分布式事务处理环境里的资"
+"源管理者和事务管理者之间的合约。资源关联自和的资源适配器实现 "
+"<interfacename>XAResource</interfacename> 接口来支持底层事务和关系型数据库等"
+"资源间的关联。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:15
+#, no-c-format
+msgid ""
+"The <interfacename>XAResource</interfacename> interface can be supported by "
+"any transactional resource adapter that is intended to be used in an "
+"environment where transactions are controlled by an external transaction "
+"manager, for example, a database management system. An application may "
+"access data through multiple database connections. Each database connection "
+"is associated with an <code>XAResource</code> object that serves as a proxy "
+"object to the underlying resource manager instance. The transaction manager "
+"obtains an <code>XAResource</code> for each resource manager participating "
+"in a top-level transaction. It uses the start method to associate the "
+"transaction with the resource, and it uses the end method to disassociate "
+"the transaction from the resource."
+msgstr ""
+"任何想在外部事务管理者控制事务的环境里使用的事务性资源适配器都可以支持 "
+"<interfacename>XAResource</interfacename> 接口，例如，数据库管理系统。应用程"
+"序可以通过多个数据库连接来访问数据。每个数据库连接都和作为底层资源管理者实例"
+"的代理对象的 <code>XAResource</code> 对象关联。事务管理者为每个参与顶层事务的"
+"资源管理者获取一个 <code>XAResource</code> 对象。它使用 start 方法来关联事务"
+"和资源，并使用 end 方法来把事务从资源里分离。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:18
+#, no-c-format
+msgid ""
+"The resource manager is responsible for associating the transaction with all "
+"work performed on its data between the start and end invocations. At "
+"transaction commit time, these transactional resource managers are informed "
+"by the transaction manager to prepare, commit, or rollback the transaction "
+"according to the two-phase commit protocol."
+msgstr ""
+"资源管理者负责把事务和所有在 start 和 end 调用之间在其数据上执行的工作相关"
+"联。在事务提交的时候，事务管理者这些事务性资源管理者安装两阶段提交协议准备、"
+"提交或回滚事务。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:21
+#, no-c-format
+msgid ""
+"In order to be better integrated with Java, the <interfacename>XAResource</"
+"interfacename> differs from the standard <interfacename>XA</interfacename> "
+"interface in the following ways:"
+msgstr ""
+"为了更好地和 Java 集成，<interfacename>XAResource</interfacename> 和标准的 "
+"<interfacename>XA</interfacename> 接口有如下的不同："
+
+#. Tag: para
+#: The_Resource_Manager.xml:26
+#, no-c-format
+msgid ""
+"The resource manager initialization is done implicitly by the resource "
+"adapter when the resource (connection) is acquired. There is no "
+"<code>xa_open</code> equivalent."
+msgstr ""
+"当需要资源（连接）时，资源适配器隐性地完成资源管理者的初始化。这里不需要和 "
+"<code>xa_open</code> 相等的方法。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:31
+#, no-c-format
+msgid ""
+"<code>Rmid</code> is not passed as an argument. Each <code>Rmid</code> is "
+"represented by a separate <code>XAResource</code> object."
+msgstr ""
+"<code>Rmid</code> 不作为参数传递。每个 <code>Rmid</code> 都由单独的 "
+"<code>XAResource</code> 对象代表。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:36
+#, no-c-format
+msgid ""
+"Asynchronous operations are not supported because Java supports multi-"
+"threaded processing and most databases do not support asynchronous "
+"operations."
+msgstr ""
+"因为 Java 支持多线程处理而大多数数据库不支持异步操作，所以这里也不支持异步操"
+"作。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:41
+#, no-c-format
+msgid ""
+"Error return values that are caused by the transaction manager’s improper "
+"handling of the <code>XAResource</code> object are mapped to Java exceptions "
+"via the <classname>XAException</classname> class."
+msgstr ""
+"事务管理者不正确处理 <code>XAResource</code> 对象引起的错误返回值通过 "
+"<classname>XAException</classname> 类映射到 Java 异常。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:46
+#, no-c-format
+msgid ""
+"The DTP concept of <emphasis>Thread of Control</emphasis> maps to all Java "
+"threads that are given access to the <code>XAResource</code> and "
+"<code>Connection</code> objects. For example, it is legal for two different "
+"threads to perform the start and end operations on the same "
+"<code>XAResource</code> object."
+msgstr ""
+"<emphasis>Thread of Control</emphasis> DTP 概念适用于所有获得 "
+"<code>XAResource</code> 和 <code>Connection</code> 对象访问权限的 Java 线程。"
+"例如，两个不同的线程在相同的 <code>XAResource</code> 对象上执行 start 和 end "
+"操作是合法的。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr "扩展的 XAResource 控制"
+
+#. Tag: para
+#: The_Resource_Manager.xml:53
+#, no-c-format
+msgid ""
+"By default, whenever an <code>XAResource</code> object is registered with a "
+"JTA compliant transaction service, you have no control over the order in "
+"which it will be invoked during the two-phase commit protocol, with respect "
+"to other <code>XAResource</code> objects. In JBossTS, however, there is "
+"support for controlling the order via the two interfaces <interfacename>com."
+"arjuna.ats.jta.resources.StartXAResource</interfacename> and "
+"<interfacename>com.arjuna.ats.jta.resources.EndXAResource</interfacename>. "
+"By inheriting your <code>XAResource</code> instance from either of these "
+"interfaces, you control whether an instance of your class will be invoked "
+"first or last, respectively."
+msgstr ""
+"在缺省情况下，每当 <code>XAResource</code> 对象向兼容 JTA 的事务访问注册时，"
+"你都不能控制在两阶段提交协议中的对其他 <code>XAResource</code> 对象的调用顺"
+"序。然而，JBossTS 通过两个接口 <interfacename>com.arjuna.ats.jta.resources."
+"StartXAResource</interfacename> 和 <interfacename>com.arjuna.ats.jta."
+"resources.EndXAResource</interfacename> 来支持对这种顺序的控制。通过从这些接"
+"口继承 <code>XAResource</code> 实例，你可以控制最先还是最后调用某个实例。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:58
+#, no-c-format
+msgid ""
+"Only one instance of each interface type may be registered with a specific "
+"transaction."
+msgstr "在特定的事务里，每个接口类型只有有一个实例可以注册。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:62
+#, no-c-format
+msgid ""
+"In the TxCore manual we discussed the Last Resource Commit optimization "
+"(LRCO), whereby a single resource that is only one-phase aware (does not "
+"support prepare), can be enlisted with a transaction that is manipulating "
+"two-phase aware participants. This optimization is also supported within the "
+"JTA aspects of JBossTS."
+msgstr ""
+"在 TxCore 手册里，我们讨论了 Last Resource Commit optimization (LRCO)，由此一"
+"阶段的资源（不支持 prepare 阶段）也可以向操作两阶段参与者的事务登记。JBossTS "
+"的 JTA 组件也支持这种优化。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:65
+#, no-c-format
+msgid ""
+"In order to use the LRCO, your <interfacename>XAResource</interfacename> "
+"implementation must extend the <interfacename>com.arjuna.ats.jta.resources."
+"LastResourceCommitOptimisation</interfacename> marker interface (it provides "
+"no methods). When enlisting the resource via Transaction.enlistResource, "
+"JBossTS will ensure that only a single instance of this type of participant "
+"is used within each transaction. Your resource will be driven last in the "
+"commit protocol: no invocation of prepare will occur."
+msgstr ""
+"为了使用 LRCO，你的 <interfacename>XAResource</interfacename> 实现必须继承 "
+"<interfacename>com.arjuna.ats.jta.resources.LastResourceCommitOptimisation</"
+"interfacename> marker 接口（它没有提供任何方法）。当通过 Transaction."
+"enlistResource 登记资源时，JBossTS 将确保该类型参与者只有一个实例在每个事务里"
+"使用。在提交协议里你的资源将最后被驱动：不会发生 prepare 调用。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:69
+#, no-c-format
+msgid ""
+"By default an attempt to enlist more than one instance of a "
+"<classname>LastResourceCommitOptimisation</classname> class will fail and "
+"false will be returned from <methodname>Transaction.enlistResource</"
+"methodname>. This behaviour can be overridden by setting the <property>com."
+"arjuna.ats.jta.allowMultipleLastResources</property> to true. However, "
+"before doing so you should read the Section on enlisting multiple one-phase "
+"aware resources."
+msgstr ""
+"在缺省情况下，登记多个 <classname>LastResourceCommitOptimisation</classname> "
+"实例会失败且 <methodname>Transaction.enlistResource</methodname> 将返回 "
+"false。设置 <property>com.arjuna.ats.jta.allowMultipleLastResources</"
+"property> 可以覆盖这种行为。然而，你应该先阅读关于登记多个一阶段资源的章节。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:73
+#, no-c-format
+msgid ""
+"In order to utilize the LRCO in a distributed environment, it is necessary "
+"to disable interposition support. It is still possible to use implicit "
+"context propagation."
+msgstr ""
+"为了在分布式环境里使用 LRCO，我们有必要禁用 interposition 支持。使用隐性的上"
+"下文传递仍然是可能的。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:77
+#, no-c-format
+msgid "Enlisting multiple one-phase aware resources"
+msgstr "登记多个一阶段资源"
+
+#. Tag: para
+#: The_Resource_Manager.xml:78
+#, no-c-format
+msgid ""
+"As discussed in the Transaction Core documentation, in order to guarantee "
+"consistency (atomicity) of outcome between multiple participants (resources) "
+"within the same transaction, the two-phase commit protocol is used with a "
+"durable transaction log. In the case of possessing a single one-phase aware "
+"resource, it is still possible to achieve an atomic (all of nothing) outcome "
+"across resources by utilizing the Last Resource Commit Optimization, as "
+"explained earlier."
+msgstr ""
+"如 Transaction 核心文档里所讨论的，为了保证相同事务里的多个参与者（资源）的一"
+"致性（原子性），带有持久的事务日志的两阶段提交协议被使用。如之前所解释的，在"
+"处理单个的一阶段资源时，利用 Last Resource Commit Optimization 仍然可能实现跨"
+"资源的原子的结果。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:82
+#, no-c-format
+msgid ""
+"However, there may be situations where multiple one-phase aware resources "
+"are enlisted within the same transaction. For example, a legacy database "
+"running within the same transaction as a legacy JMS implementation. In these "
+"situations it is not possible to achieve atomicity of transaction outcome "
+"across multiple resources because none of them enter the prepare (waiting "
+"for final outcome) state: they commit or rollback immediately when "
+"instructed by the transaction coordinator, without knowledge of other "
+"resource states and without any way of undoing should subsequent resources "
+"make a different choice. This can result in data corruption or heuristic "
+"outcomes."
+msgstr ""
+"然而，有时候多个一阶段可能资源在相同事务里登记。例如，作为旧的 JMS 实现运行在"
+"相同事务里的旧的数据库。在这种情况下，实现跨资源的事务结果的原子性是不可能"
+"的，因为它们都没有进入 prepare（等待最后结果）状态；当事务协调者指示时，它们"
+"马上提交或回滚而不顾其他资源状态，且如果最后的资源作出不同选择时也不能取消操"
+"作。这会导致数据崩溃或启发式结果。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:85
+#, no-c-format
+msgid "In these situations we recommend one of the following approaches:"
+msgstr "在这些情况下，我们推荐下列的方法之一："
+
+#. Tag: para
+#: The_Resource_Manager.xml:90
+#, no-c-format
+msgid ""
+"Wrap the resources in compensating transactions. See the Web Services "
+"transactions guides for further details."
+msgstr "在补充性事务里包裹资源。更多细节请参考《Web Services 事务指南》"
+
+#. Tag: para
+#: The_Resource_Manager.xml:95
+#, no-c-format
+msgid "Migrate the legacy implementations to two-phase aware equivalents."
+msgstr "把旧的实现移植到识别两阶段提交协议的资源。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:100
+#, no-c-format
+msgid ""
+"In the cases where neither of these options are viable, JBossTS does support "
+"the enlistment of multiple one-phase aware resources within the same "
+"transaction. In order to do this, see the section on the Last Resource "
+"Commit Optimization."
+msgstr ""
+"当这些选项都不可用时，JBossTS 支持在相同的事务里登记多个只识别一阶段提交的资"
+"源。相关实现方法请参考 Last Resource Commit Optimization 章节。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:104
+#, no-c-format
+msgid ""
+"Even when this support is enabled, JBossTS will issue warnings when it "
+"detects that the option has been enabled (\"You have chosen to enable "
+"multiple last resources in the transaction manager. This is transactionally "
+"unsafe and should not be relied upon.”) and when multiple one-phase "
+"resources are enlisted within the transaction (“This is transactionally "
+"unsafe and should not be relied on.”)."
+msgstr ""
+"甚至当启用了这种支持时，JBossTS 仍然会在检测到启用了该选项时发出警告信息"
+"（\"You have chosen to enable multiple last resources in the transaction "
+"manager. This is transactionally unsafe and should not be relied upon.”）和在"
+"多个一阶段资源在事务里登记发出（“This is transactionally unsafe and should "
+"not be relied on.”）。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:111
+#, no-c-format
+msgid "Opening a Resource Manager"
+msgstr "打开资源管理者"
+
+#. Tag: para
+#: The_Resource_Manager.xml:112
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface requires that the "
+"transaction manager initialize a resource manager (xa_open) prior to any "
+"other xa_ calls. JTA requires initialization of a resource manager to be "
+"embedded within the resource adapter that represents the resource manager. "
+"The transaction manager does not need to know how to initialize a resource "
+"manager; it is only responsible for informing the resource manager about "
+"when to start and end work associated with a transaction and when to "
+"complete the transaction. The resource adapter is responsible for opening "
+"(initializing) the resource manager when the connection to the resource "
+"manager is established."
+msgstr ""
+"X/Open <interfacename>XA</interfacename> 接口要求事务管理者在任何 xa_ 调用前"
+"初始化资源管理者（xa_open）。JTA 要求资源管理者的初始化嵌入在代表资源管理者的"
+"资源适配器里。事务管理者不需要知道怎样初始化资源管理者；它只负责通知资源管理"
+"者什么时候启动和结束和事务相关的工作以及什么时候结束事务。资源适配器负责在建"
+"立到资源管理者的连接时打开（初始化）资源管理者。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:118
+#, no-c-format
+msgid "Closing a Resource Manager"
+msgstr "关闭资源管理者"
+
+#. Tag: para
+#: The_Resource_Manager.xml:119
+#, no-c-format
+msgid ""
+"A resource manager is closed by the resource adapter as a result of "
+"destroying the transactional resource. A transaction resource at the "
+"resource adapter level is comprised of two separate objects:"
+msgstr ""
+"在资源适配器销毁了事务性资源后，资源管理者将被关闭。资源适配器级别的事务资源"
+"由两个独立的对象组成："
+
+#. Tag: para
+#: The_Resource_Manager.xml:124
+#, no-c-format
+msgid ""
+"An <code>XAResource</code> object that allows the transaction manager to "
+"start and end the transaction association with the resource in use and to "
+"coordinate transaction completion process."
+msgstr ""
+"<code>XAResource</code> 对象允许事务管理者启动和结束事务和资源的关联并协调事"
+"务的完成。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:129
+#, no-c-format
+msgid ""
+"A connection object that allows the application to perform operations on the "
+"underlying resource (for example, JDBC operations on an RDBMS)."
+msgstr ""
+"connection 对象允许应用程序在底层资源（例如 RDBMS 上的 JDBC 操作）执行操作。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:134
+#, no-c-format
+msgid ""
+"Once opened, the resource manager is kept open until the resource is "
+"released (closed) explicitly. When the application invokes the connection’s "
+"close method, the resource adapter invalidates the connection object "
+"reference that was held by the application and notifies the application "
+"server about the close. The transaction manager should invoke the "
+"<methodname>XAResource.end</methodname> method to disassociate the "
+"transaction from that connection."
+msgstr ""
+"在启动后，资源管理者保持开启状态直到资源被显性地释放（关闭）。当应用程序调用"
+"连接的 close 方法，资源适配器使应用程序持有的 connection 对象引用失效并将关闭"
+"动作通知应用服务器。事务管理者应该调用 <methodname>XAResource.end</"
+"methodname> 方法来使事务和这个连接分离。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:137
+#, no-c-format
+msgid ""
+"The close notification allows the application server to perform any "
+"necessary cleanup work and to mark the physical XA connection as free for "
+"reuse, if connection pooling is in place."
+msgstr ""
+"关于关闭的通知允许应用服务器执行必需的清理工作并把实际的 XA 连接标记为空闲且"
+"可重用（如果使用了连接池）。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:143
+#, no-c-format
+msgid "Threads of control"
+msgstr "控制线程"
+
+#. Tag: para
+#: The_Resource_Manager.xml:144
+#, no-c-format
+msgid ""
+"The X/Open <interfacename>XA</interfacename> interface specifies that the "
+"transaction association related xa calls must be invoked from the same "
+"thread context. This thread-of-control requirement is not applicable to the "
+"object-oriented component-based application run-time environment, in which "
+"application threads are dispatched dynamically at method invocation time. "
+"Different threads may be using the same connection resource to access the "
+"resource manager if the connection spans multiple method invocation. "
+"Depending on the implementation of the application server, different threads "
+"may be involved with the same <code>XAResource</code> object. The resource "
+"context and the transaction context may be operated independent of thread "
+"context. This means that it is possible for different threads to be invoking "
+"the start and end methods."
+msgstr ""
+"X/Open <interfacename>XA</interfacename> 接口指定和事务关联相关的调用必须从相"
+"同的线程上下文中进行调用。这个控制线程的要求不适用于面向对象的基于组件的应用"
+"程序运行环境，此时应用程序线程在方法调用的时候动态地进行调遣。如果连接跨越多"
+"个方法调用，不同的线程可以使用相同的连接资源来访问资源管理器。不同的线程可以"
+"用相同的 <code>XAResource</code> 对象进行调用，这取决于应用服务器的实现。资源"
+"上下文和事务上下文可以不依赖于线程上下文进行操作。这意味着不同的线程有可能调"
+"用相同的 start 和 end 方法。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:147
+#, no-c-format
+msgid ""
+"If the application server allows multiple threads to use a single "
+"<code>XAResource</code> object and the associated connection to the resource "
+"manager, it is the responsibility of the application server to ensure that "
+"there is only one transaction context associated with the resource at any "
+"point of time. Thus the <interfacename>XAResource</interfacename> interface "
+"requires that the resource managers be able to support the two-phase commit "
+"protocol from any thread context."
+msgstr ""
+"如果应用服务器允许多个线程使用相同的 <code>XAResource</code> 对象以及和资源管"
+"理者相关联的连接，应用服务器要确保在任何时刻只有一个事务上下文和该资源相关"
+"联。因此，<interfacename>XAResource</interfacename> 接口要求资源管理者能够支"
+"持任何线程上下文中的两阶段提交协议。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:153
+#, no-c-format
+msgid "Transaction association"
+msgstr "事务关联"
+
+#. Tag: para
+#: The_Resource_Manager.xml:154
+#, no-c-format
+msgid ""
+"Transactions are associated with a transactional resource via the start "
+"method, and disassociated from the resource via the <methodname>end</"
+"methodname> method. The resource adapter is responsible for internally "
+"maintaining an association between the resource connection object and the "
+"<code>XAResource</code> object. At any given time, a connection is "
+"associated with a single transaction, or it is not associated with any "
+"transaction at all. Because JTA does not support nested transactions it is "
+"an error for the start method to be invoked on a connection that is "
+"currently associated with a different transaction."
+msgstr ""
+"事务通过 start 方法和事务性资源现关联并通过 <methodname>end</methodname> 方法"
+"进行分离。资源适配器负责在内部维护资源连接对象和 <code>XAResource</code> 对象"
+"之间的关联。在任何时候，连接都和单一的事务关联，或者不和任何事务关联。因为 "
+"JTA 不支持嵌套的事务，对当前和不同事务关联的连接调用 start 方法会产生错误。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:157
+#, no-c-format
+msgid ""
+"Interleaving multiple transaction contexts using the same resource may be "
+"done by the transaction manager as long as start and end are invoked "
+"properly for each transaction context switch. Each time the resource is used "
+"with a different transaction, the method end must be invoked for the "
+"previous transaction that was associated with the resource, and start must "
+"be invoked for the current transaction context."
+msgstr ""
+"只要对每个事务上下文正确地调用了 start 和 end 方法，使用相同的资源对多个事务"
+"上下文进行交错是可能的。每次资源和不同的事务一起使用时，对和资源关联的前一事"
+"务必须调用 end 方法，且必须对当前的事务上下文调用 start 方法。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:163
+#, no-c-format
+msgid "Externally controlled connections"
+msgstr "外部控制的连接"
+
+#. Tag: para
+#: The_Resource_Manager.xml:164
+#, no-c-format
+msgid ""
+"For transactional application whose transaction states are managed by an "
+"application server, its resources must also be managed by the application "
+"server so that transaction association is performed properly. If an "
+"application is associated with a transaction, it is an error for the "
+"application to perform transactional work through the connection without "
+"having the connection’s resource object already associated with the global "
+"transaction. The application server must ensure that the <code>XAResource</"
+"code> object in use is associated with the transaction. This is done by "
+"invoking the <methodname>Transaction.enlistResource</methodname> method."
+msgstr ""
+"对于事务状态由应用服务器管理的事务性应用程序，它的资源也必须由应用服务器管理"
+"才能争取执行事务关联。如果某个应用程序和事务相关联，这个应用程序通过连接而没"
+"有使该连接的资源对象和全局事务关联执行事务性任务会产生错误。应用服务器必须确"
+"保使用的 <code>XAResource</code> 对象和事务相关联。这是通过 "
+"<methodname>Transaction.enlistResource</methodname> 方法完成的。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:167
+#, no-c-format
+msgid ""
+"If a server side transactional application retains its database connection "
+"across multiple client requests, the application server must ensure that "
+"before dispatching a client request to the application thread, the resource "
+"is enlisted with the application’s current transaction context. This implies "
+"that the application server manages the connection resource usage status "
+"across multiple method invocations."
+msgstr ""
+"如果服务器端的应用程序和多个客户端请求保持数据库连接，应用服务器必须确保在把"
+"客户端请求分发给相应线程前，资源应该在当前的事务上下文里登记。这暗示着应用服"
+"务器管理多个方法调用间的连接资源的使用状态。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:173
+#, no-c-format
+msgid "Resource sharing"
+msgstr "资源共享"
+
+#. Tag: para
+#: The_Resource_Manager.xml:174
+#, no-c-format
+msgid ""
+"When the same transactional resource is used to interleave multiple "
+"transactions, it is the responsibility of the application server to ensure "
+"that only one transaction is enlisted with the resource at any given time. "
+"To initiate the transaction commit process, the transaction manager is "
+"allowed to use any of the resource objects connected to the same resource "
+"manager instance. The resource object used for the two-phase commit protocol "
+"does not need to have been involved with the transaction being completed."
+msgstr ""
+"当相同的事务性资源被用来对多个事务进行交错时，应用服务器要确保在任何时刻只有"
+"一个事务在资源里进行登记。要初始化事务提交过程，事务管理者被允许使用和相同资"
+"源管理者实例连接的任何资源对象。用于两阶段提交协议的资源对象不需要和正完成的"
+"事务有关联。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:177
+#, no-c-format
+msgid ""
+"The resource adapter must be able to handle multiple threads invoking the "
+"<interfacename>XAResource</interfacename> methods concurrently for "
+"transaction commit processing. For example, with reference to the code "
+"below, suppose we have a transactional resource <code>r1</code>. Global "
+"transaction <code>xid1</code> was started and ended with <code>r1</code>. "
+"Then a different global transaction <code>xid2</code> is associated with "
+"<code>r1</code>. In the meanwhile, the transaction manager may start the two "
+"phase commit process for <code>xid1</code> using <code>r1</code> or any "
+"other transactional resource connected to the same resource manager. The "
+"resource adapter needs to allow the commit process to be executed while the "
+"resource is currently associated with a different global transaction."
+msgstr ""
+"资源适配器必须能够处理为事务提交过程并发调用 <interfacename>XAResource</"
+"interfacename> 方法的多个线程。如下面的代码所示，假设我们有一个事务性资源 "
+"<code>r1</code>。全局事务 <code>xid1</code> 和 <code>r1</code> 一起被启动和结"
+"束。然后，另外一个全局事务 <code>xid2</code> 和 <code>r1</code> 相关联。同"
+"时，事务管理者可以用 <code>r1</code> 或者任何其他连接到相同资源管理者的事务性"
+"资源为 <code>xid1</code> 启动两阶段提交过程。当资源正和不同的全局事务相关联"
+"时，资源适配器需要允许提交过程的执行。"
+
+#. Tag: screen
+#: The_Resource_Manager.xml:180
+#, no-c-format
+msgid ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+msgstr ""
+"XAResource xares = r1.getXAResource();\n"
+" \n"
+"xares.start(xid1); // associate xid1 to the connection\n"
+" \n"
+"..\n"
+"xares.end(xid1); // disassociate xid1 to the connection\n"
+"..\n"
+"xares.start(xid2); // associate xid2 to the connection\n"
+"..\n"
+"// While the connection is associated with xid2,\n"
+"// the TM starts the commit process for xid1\n"
+"status = xares.prepare(xid1);\n"
+"..\n"
+"xares.commit(xid1, false);"
+
+#. Tag: title
+#: The_Resource_Manager.xml:184
+#, no-c-format
+msgid "Local and global transactions"
+msgstr "本地和全局事务"
+
+#. Tag: para
+#: The_Resource_Manager.xml:185
+#, no-c-format
+msgid ""
+"The resource adapter must support the usage of both local and global "
+"transactions within the same transactional connection. Local transactions "
+"are transactions that are started and coordinated by the resource manager "
+"internally. The <interfacename>XAResource</interfacename> interface is not "
+"used for local transactions. When using the same connection to perform both "
+"local and global transactions, the following rules apply:"
+msgstr ""
+"资源适配器必须支持在相同的事务性连接里使用本地和全局事务。本地事务是资源管理"
+"者在内部启动和协调的事务。<interfacename>XAResource</interfacename> 接口不用"
+"于本地事务。当使用相同的连接来执行本地和全局事务时，将应用下列的规则："
+
+#. Tag: para
+#: The_Resource_Manager.xml:190
+#, no-c-format
+msgid ""
+"The local transaction must be committed (or rolled back) before starting a "
+"global transaction in the connection."
+msgstr "本地事务必须在启动连接里的全局事务前提交（或回滚）。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:195
+#, no-c-format
+msgid ""
+"The global transaction must be disassociated from the connection before any "
+"local transaction is started."
+msgstr "全局事务必须在启动任何本地事务前和连接进行分离。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:203
+#, no-c-format
+msgid "Transaction timeouts"
+msgstr "事务超时"
+
+#. Tag: para
+#: The_Resource_Manager.xml:204
+#, no-c-format
+msgid ""
+"Timeout values can be associated with transactions in order to control their "
+"lifetime. If a transaction has not terminated (committed or rolled back) "
+"before the timeout value elapses, the transaction system will automatically "
+"roll it back. The <interfacename>XAResource</interfacename> interface "
+"supports a operation, which allows the timeout associated with the current "
+"transaction to be propagated to the resource manager and if supported, will "
+"override any default timeout associated with the resource manager. This can "
+"be useful when long running transactions may have lifetimes that would "
+"exceed the default and in which case, if the timeout were not altered, the "
+"resource manager would rollback before the transaction terminated and "
+"subsequently cause the transaction to roll back as well."
+msgstr ""
+"事务可以和超时时间关联，这是为了控制生存时间。如果在超过超时时间后事务还未终"
+"止（提交或回滚），事务系统将自动将其回滚。<interfacename>XAResource</"
+"interfacename> 接口支持这样一个操作，它允许和当前事务关联的超时时间传递给资源"
+"管理者，并在被支持的情况下覆盖资源管理者关联的任何缺省超时时间。当长期运行的"
+"使用可能具有超过缺省值的生存时间时，这很有用，在这种情况下，如果没有修改超时"
+"时间，资源管理者将在事务终止前回滚并导致事务回滚。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:207
+#, no-c-format
+msgid ""
+"If no timeout value is explicitly set for a transaction, or a value of 0 is "
+"specified, then an implementation specific default value may be used. In the "
+"case of JBossTS, how this default value is set depends upon which JTA "
+"implementation you are using."
+msgstr ""
+"如果没有显性地为事务指定超时时间，或者是指定的值为 0，那么实现专有的缺省值将"
+"被使用。在 JBossTS 里，这个缺省值的设置取决于所使用的 JTA 实现。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:212
+#, no-c-format
+msgid ""
+"Local JTA: use the <property>com.arjuna.ats.arjuna.coordinator."
+"defaultTimeout</property> property value and give a timeout in seconds. The "
+"default value is 60 seconds."
+msgstr ""
+"本地 JTA：使用 <property>com.arjuna.ats.arjuna.coordinator.defaultTimeout</"
+"property> 属性值并给出以秒为单位的超时时间。缺省值为 60 秒。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:217
+#, no-c-format
+msgid ""
+"JTS: use the <property>com.arjuna.ats.jts.defaultTimeout</property> property "
+"value and give a timeout in seconds. The default value is 0, for instance, "
+"transactions do not timeout."
+msgstr ""
+"JTS：使用 <property>com.arjuna.ats.jts.defaultTimeout</property> 属性值并给出"
+"以秒为单位的超时时间。缺省值为 0，也就是事务永不超时。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:222
+#, no-c-format
+msgid ""
+"Unfortunately there are situations where imposing the same timeout as the "
+"transaction on a resource manager may not be appropriate. For example, if "
+"the system administrator wishes to have control over the lifetimes on "
+"resource managers and does not want to (or cannot) allow that control to be "
+"passed to some external entity. At present JBossTS supports an all-or-"
+"nothing approach to whether or not <methodname>setTransactionTimeout</"
+"methodname> is called on <interfacename>XAResource</interfacename> instances."
+msgstr ""
+"可惜的是，有时候为资源管理者指定和事务相同的超时时间是不合适的。例如，如果系"
+"统管理员希望控制资源管理者的生存时间且并不希望（或不能）允许这个控制权转给外"
+"部的实体。目前，对于是否对 <interfacename>XAResource</interfacename> 实例调"
+"用 <methodname>setTransactionTimeout</methodname>，JBossTS 支持 all-or-"
+"nothing 方法。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:225
+#, no-c-format
+msgid ""
+"If the <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> "
+"property is set to true (the default) then it will be called on all "
+"instances. Alternatively, the <methodname>setXATransactionTimeoutEnabled</"
+"methodname> method of <classname>com.arjuna.ats.jta.common.Configuration</"
+"classname> can be used."
+msgstr ""
+"如果 <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> 属性"
+"为 true（缺省值），那对于每个实例它都将被调用。或者可使用 <classname>com."
+"arjuna.ats.jta.common.Configuration</classname> 的 "
+"<methodname>setXATransactionTimeoutEnabled</methodname> 方法。"
+
+#. Tag: title
+#: The_Resource_Manager.xml:231
+#, no-c-format
+msgid "Dynamic Registration"
+msgstr "动态注册"
+
+#. Tag: para
+#: The_Resource_Manager.xml:232
+#, no-c-format
+msgid ""
+"Dynamic registration is not supported in <interfacename>XAResource</"
+"interfacename> because of the following reasons:"
+msgstr ""
+"<interfacename>XAResource</interfacename> 不支持动态注册，这是因为以下原因："
+
+#. Tag: para
+#: The_Resource_Manager.xml:237
+#, no-c-format
+msgid ""
+"In the Java component-based application server environment, connections to "
+"the resource manager are acquired dynamically when the application "
+"explicitly requests a connection. These resources are enlisted with the "
+"transaction manager on a needed basis."
+msgstr ""
+"在基于 Java 组件的应用服务器环境里，当应用程序显性地请求连接时将动态获取和资"
+"源管理者的连接。这些资源根据需要在事务管理者里进行登记。"
+
+#. Tag: para
+#: The_Resource_Manager.xml:242
+#, no-c-format
+msgid ""
+"If a resource manager requires a way to dynamically register its work to the "
+"global transaction, the implementation can be done at the resource adapter "
+"level via a private interface between the resource adapter and the "
+"underlying resource manager."
+msgstr ""
+"如果资源管理者要求动态地注册到全局事务里，你可以在资源适配器级别通过资源适配"
+"器和底层资源管理者之间的私有接口实现。"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,432 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr "事务恢复"
+
+#. Tag: title
+#: Transaction_Recovery.xml:10
+#, no-c-format
+msgid "Failure recovery"
+msgstr "失效切换"
+
+#. Tag: para
+#: Transaction_Recovery.xml:11
+#, no-c-format
+msgid ""
+"During recovery, the Transaction Manager needs to be able to communicate to "
+"all resource managers that are in use by the applications in the system. For "
+"each resource manager, the Transaction Manager uses the "
+"<methodname>XAResource.recover</methodname> method to retrieve the list of "
+"transactions that are currently in a prepared or heuristically completed "
+"state. Typically, the system administrator configures all transactional "
+"resource factories that are used by the applications deployed on the system. "
+"An example of such a resource factory is the JDBC <code>XADataSource</code> "
+"object, which is a factory for the JDBC <code>XAConnection</code> objects."
+msgstr ""
+"在切换过程中，事务管理者需要和应用程序使用的所有资源管理者通信。对于每个资源"
+"管理者，事务管理者使用 <methodname>XAResource.recover</methodname> 方法来获取"
+"当前处于准备或即将完成状态的事务列表。通常，相同管理者配置素有的应用程序使用"
+"的事务性资源工厂。资源工厂的一个例子是 JDBC <code>XADataSource</code> 对象，"
+"它是用于 JDBC <code>XAConnection</code> 对象的工厂。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:14
+#, no-c-format
+msgid ""
+"Because <code>XAResource</code> objects are not persistent across system "
+"failures, the Transaction Manager needs to have some way to acquire the "
+"<code>XAResource</code> objects that represent the resource managers which "
+"might have participated in the transactions prior to the system failure. For "
+"example, a Transaction Manager might, through the use of JNDI lookup "
+"mechanism, acquire a connection from each of the transactional resource "
+"factories, and then obtain the corresponding <code>XAResource</code> object "
+"for each connection. The Transaction Manager then invokes the "
+"<methodname>XAResource.recover</methodname> method to ask each resource "
+"manager to return the transactions that are currently in a prepared or "
+"heuristically completed state."
+msgstr ""
+"因为在系统失效时 <code>XAResource</code> 对象不是持久的，事务管理者需要获得代"
+"表资源管理者并在失效前已经参与事务的 <code>XAResource</code> 对象。例如，事务"
+"管理者可以通过使用 JNDI 查找机制来从每个事务资源工厂获取连接，然后再为每个连"
+"接获取相应的 <code>XAResource</code> 对象。事务管理者然后调用 "
+"<methodname>XAResource.recover</methodname> 方法来请求每个资源管理者目前处于"
+"准备或即将完成状态的事务。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:18
+#, no-c-format
+msgid ""
+"When running XA recovery it is 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 ‘*’ will force JBossTS to recover (and possibly rollback) all "
+"transactions irrespective of their node identifier and should be used with "
+"caution."
+msgstr ""
+"运行 XA 切换有必要告诉 JBossTS 它可以切换的 XID 的类型。JBossTS 创建的每个 "
+"XID 都有一个唯一的节点标识符，JBossTS 将只切换符合指定标识符的事务和状态。节"
+"点标识符应该通过名称以 <property>com.arjuna.ats.jta.xaRecoveryNode</"
+"property> 开始的属性提供给 JBossTS，这也可以是多个值。\"*\" 将使 JBossTS 恢复"
+"（或者回滚）所有的事务而管其节点标识符，这要谨慎使用。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:22
+#, no-c-format
+msgid ""
+"If using the JBossJTA JDBC 2.0 driver, then JBossJTA will take care of all "
+"<interfacename>XAResource</interfacename> crash recovery automatically. "
+"Otherwise one of the following recovery mechanisms will be used:"
+msgstr ""
+"如果使用 JBossJTA JDBC 2.0 驱动，JBossJTA 将自动处理所有 "
+"<interfacename>XAResource</interfacename> 崩溃切换。否则将使用下列的切换机制"
+"中的一个："
+
+#. Tag: para
+#: Transaction_Recovery.xml:27
+#, no-c-format
+msgid ""
+"If the <code>XAResource</code> is serializable, then the serialized form "
+"will be saved during transaction commitment, and used during recovery. It is "
+"assumed that the recreated <code>XAResource</code> is valid and can be used "
+"to drive recovery on the associated database."
+msgstr ""
+"如果 <code>XAResource</code> 是可序列化的，在事务提交时序列化格式将被保存并在"
+"切换时使用。我们假设重新创建的 <code>XAResource</code> 是有效的且可用来驱动相"
+"关联的数据库的切换。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:32
+#, no-c-format
+msgid ""
+"The <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, <interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> and <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> interfaces are used. These "
+"are documented in the JDBC chapters on failure recovery."
+msgstr ""
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>、<interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> 和 <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> 接口被使用。这些在失效切换的 "
+"JDBC 章节里提交。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:38
+#, no-c-format
+msgid ""
+"In JBossTS 3.3 the interface <interfacename>XAConnectionRecovery</"
+"interfacename> was deprecated in favor of <interfacename>XAResourceRecovery</"
+"interfacename>. Users are encouraged to move to his new interface."
+msgstr ""
+"在 JBossTS 3.3，<interfacename>XAConnectionRecovery</interfacename> 接口被替"
+"代为 <interfacename>XAResourceRecovery</interfacename>。我们鼓励用户使用新的"
+"接口。"
+
+#. Tag: title
+#: Transaction_Recovery.xml:45
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr "切换 XA 连接"
+
+#. Tag: para
+#: Transaction_Recovery.xml:46
+#, no-c-format
+msgid ""
+"When recovering from failures, JBossJTA requires the ability to reconnect to "
+"databases that were in use prior to the failures in order to resolve any "
+"outstanding transactions. Most connection information will be saved by the "
+"transaction service during its normal execution, and can be used during "
+"recovery to recreate the connection. However, it is possible that not all "
+"such information will have been saved prior to a failure (for example, a "
+"failure occurs before such information can be saved, but after the database "
+"connection is used). In order to recreate those connections it is necessary "
+"to provide implementations of the following JBossJTA interface "
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>, one for each database that may be used by an application."
+msgstr ""
+"当进行失效切换时，JBossJTA 要求有在失效前重新连接数据库的能力，这样才能解决未"
+"决的事务。大多数连接信息在正常执行过程中将由事务服务保存，并在重新创建连接时"
+"使用。然而，不是所有这样的信息都会在失效前被保存（例如，失效可能发生在保存之"
+"前而在数据库连接使用之后）。为了重新创建这些连接，为应用程序使用的每个数据库"
+"提供 JBossJTA 接口 <interfacename>com.arjuna.ats.jta.recovery."
+"XAResourceRecovery</interfacename> 的实现是必需的。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:50
+#, no-c-format
+msgid ""
+"If using the transactional JDBC 2.0 driver provided with JBossJTA, then no "
+"additional work is necessary in order to ensure that recovery occurs."
+msgstr ""
+"如果使用 JBossJTA 提供的事务性的 JDBC 2.0 驱动，确保切换发生则不需要任何其他"
+"设置。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:54
+#, no-c-format
+msgid ""
+"To inform the recovery system about each of the <code>XAResourceRecovery</"
+"code> instances, it is necessary to specify their class names through "
+"property variables. Any property variable found in the properties file, or "
+"registered at runtime, which starts with the name <property>com.arjuna.ats."
+"jta.recovery.XAResourceRecovery</property> will be assumed to represent one "
+"of these instances, and its value should be the class name. For example:"
+msgstr ""
+"为了将每个 <code>XAResourceRecovery</code> 实例通知切换系统，你需要通过属性变"
+"量指定其类名。我们假设属性文件里找到的或者在运行时注册的、名称以 "
+"<property>com.arjuna.ats.jta.recovery.XAResourceRecovery</property> 开始的任"
+"何变量将代表这些实例，其值应该为类名。例如："
+
+#. Tag: screen
+#: Transaction_Recovery.xml:57
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+
+#. Tag: para
+#: Transaction_Recovery.xml:58
+#, no-c-format
+msgid ""
+"Additional information that will be passed to the instance when it is "
+"created may be specified after a semicolon:"
+msgstr "在实例创建时将被传递给实例的其他信息也可在分号后指定："
+
+#. Tag: screen
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+
+#. Tag: para
+#: Transaction_Recovery.xml:63
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr "这些属性需要在属性文件的 JTA 部分设置。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:67
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr "切换过程任何错误将被报告。"
+
+#. Tag: screen
+#: Transaction_Recovery.xml:70
+#, no-c-format
+msgid ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+msgstr ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
+
+#. Tag: para
+#: Transaction_Recovery.xml:71
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr "每个方法应该返回下列的信息："
+
+#. Tag: para
+#: Transaction_Recovery.xml:76
+#, no-c-format
+msgid ""
+"<methodname>initialise</methodname>: once the instance has been created, any "
+"additional information which occurred on the property value (anything found "
+"after the first semi-colon) will be passed to the object. The object can "
+"then use this information in an implementation specific manner to initialise "
+"itself, for example."
+msgstr ""
+"<methodname>initialise</methodname>：一旦实例被创建，关于属性值的任何其他信息"
+"（在第一个分号之后的任何设置）将被传递给这个对象。然后它可以以实现专有的形式"
+"使用这些信息来初始化自己，例如："
+
+#. Tag: para
+#: Transaction_Recovery.xml:81
+#, no-c-format
+msgid ""
+"<methodname>hasMoreResources</methodname>: each <code>XAResourceRecovery</"
+"code> implementation may provide multiple <code>XAResource</code> instances. "
+"Before any call to <methodname>getXAResource</methodname> is made, "
+"<methodname>hasMoreResources</methodname> is called to determine whether "
+"there are any further connections to be obtained. If this returns false, "
+"<methodname>getXAResource</methodname> will not be called again during this "
+"recovery sweep and the instance will not be used further until the next "
+"recovery scan."
+msgstr ""
+"<methodname>hasMoreResources</methodname>：每个 <code>XAResourceRecovery</"
+"code> 实现可以提供多个 <code>XAResource</code> 实例。在对 "
+"<methodname>getXAResource</methodname> 进行任何调用之前，"
+"<methodname>hasMoreResources</methodname> 被调用来决定是否需要获取更多的连"
+"接。如果返回 false，在这个切换过程中 <methodname>getXAResource</methodname> "
+"将不会再被调用，在下一次切换扫描之前这个实例也不会被使用。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:86
+#, no-c-format
+msgid ""
+"<methodname>getXAResource</methodname>: returns an instance of the "
+"<code>XAResource</code> object. How this is created (and how the parameters "
+"to its constructors are obtained) is up to the <code>XAResourceRecovery</"
+"code> implementation. The parameters to the constructors of this class "
+"should be similar to those used when creating the initial driver or data "
+"source, and should obviously be sufficient to create new <code>XAResources</"
+"code> that can be used to drive recovery."
+msgstr ""
+"<methodname>getXAResource</methodname>：返回 <code>XAResource</code> 对象的一"
+"个实例。它怎样被创建的（构造函数的参数是如何获得的）取决于 "
+"<code>XAResourceRecovery</code> 实现。这个类的构造函数的参数应该和在创建初始"
+"驱动或数据源时使用的那些类的参数类似，且足够来创建用于驱动切换的新的 "
+"<code>XAResources</code>。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:92
+#, no-c-format
+msgid ""
+"If you want your <code>XAResourceRecovery</code> instance to be called "
+"during each sweep of the recovery manager then you should ensure that once "
+"<methodname>hasMoreResources</methodname> returns false to indicate the end "
+"of work for the current scan it then returns true for the next recovery scan."
+msgstr ""
+"如果你希望在切换管理者扫描过程中调用 <code>XAResourceRecovery</code> 实例，你"
+"应该确保一旦 <methodname>hasMoreResources</methodname> 返回 false 来指明当前"
+"扫描的结束，它应该返回 true 来进行下一次切换扫描。"
+
+#. Tag: title
+#: Transaction_Recovery.xml:99
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr "附带的 XAResourceRecovery 实现"
+
+#. Tag: para
+#: Transaction_Recovery.xml:100
+#, no-c-format
+msgid ""
+"Recovery of <interfacename>XA</interfacename> datasources can sometimes be "
+"implementation dependant, requiring developers to provide their own "
+"<interfacename>XAResourceRecovery</interfacename> instances. However, "
+"JBossTS ships with several out-of-the-box implementations that may be useful."
+msgstr ""
+"<interfacename>XA</interfacename> 数据源的切换有时候可能依赖于相关的实现，要"
+"求开发者提供自己的<interfacename>XAResourceRecovery</interfacename> 实例。然"
+"而，JBossTS 带有几个可能有用的实现。"
+
+#. Tag: para
+#: Transaction_Recovery.xml:105
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>: this expects an XML property file to be specified upon "
+"creation and from which it will read the database URL, username and "
+"password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>：它期望在创建时指定 XML 属性文件，从中它可以读取数据库 URL、用"
+"户名和密码。例如："
+
+#. Tag: screen
+#: Transaction_Recovery.xml:108
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
+
+#. Tag: para
+#: Transaction_Recovery.xml:111
+#, no-c-format
+msgid ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>: this recovery implementation should work on any datasource "
+"that is exposed via JNDI. It expects an XML property file to be specified "
+"upon creation and from which it will read the database JNDI name, username "
+"and password. For example:"
+msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>：这个切换实现应该可用于任何通过 JNDI 开放的数据源。它期望在创"
+"建时指定 XML 属性文件，从中它可以读取数据库 URL、用户名和密码。例如："
+
+#. Tag: screen
+#: Transaction_Recovery.xml:114
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
+msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,583 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr "事务"
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr "应用程序接口（API ）"
+
+#. Tag: para
+#: Transactions.xml:9
+#, no-c-format
+msgid ""
+"The Java Transaction API consists of three elements: a high-level "
+"application transaction demarcation interface, a high-level transaction "
+"manager interface intended for application server, and a standard Java "
+"mapping of the X/Open XA protocol intended for transactional resource "
+"manager. All of the JTA classes and interfaces occur within the "
+"<package>javax.transaction</package> package, and the corresponding JBossJTA "
+"implementations within the <package>com.arjuna.ats.jta</package> package."
+msgstr ""
+"Java Transaction API 由三个元素组成：高级别的应用程序事务限界接口、用于应用服"
+"务器的高级别事务管理者接口、用于事务性资源管理者的 X/Open XA 协议的标准 Java "
+"映射。所有 JTA 类和接口都包含在 <package>javax.transaction</package> 包里，"
+"而 <package>com.arjuna.ats.jta</package> 包包含相应 JBossJTA 实现。"
+
+#. Tag: para
+#: Transactions.xml:13
+#, no-c-format
+msgid ""
+"Each 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. The contents of this "
+"should be alphanumeric."
+msgstr ""
+"JBossTS 创建的每个 XID 都必须有唯一的节点标识符，而 JBossTS 将只切换符合指定"
+"的节点标识符的事务和状态。这个节点标识符应该通过 <property>com.arjuna.ats."
+"arjuna.xa.nodeIdentifier</property> 属性提供给 JBossTS。你必须确保这个值在 "
+"JBossTS 实例中是唯一的。如果你没有提供这个值，JBossTS 将生成一个并在日志里报"
+"告这个值。它的内容应该只包含字母和数字。"
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: Transactions.xml:19
+#, no-c-format
+msgid ""
+"The <interfacename>UserTransaction</interfacename> interface provides "
+"applications with the ability to control transaction boundaries. It has "
+"methods for beginning, committing, and rolling back top-level transactions: "
+"nested transactions are not supported, and begin throws the "
+"<code>NotSupportedException</code> when the calling thread is already "
+"associated with a transaction. <interfacename>UserTransaction</"
+"interfacename> automatically associates newly created transactions with the "
+"invoking thread."
+msgstr ""
+"<interfacename>UserTransaction</interfacename> 接口为应用程序提供控制事务边界"
+"的能力。它具有开始、提交和回滚顶层事务的方法：它不支持嵌套事务，如果调用线程"
+"已经和事务关联，begin 方法会抛出 <code>NotSupportedException</code>。"
+"<interfacename>UserTransaction</interfacename> 自动和调用线程最新创建的事务相"
+"关联。"
+
+#. Tag: para
+#: Transactions.xml:24
+#, no-c-format
+msgid ""
+"In JBossJTA, UserTransactions can be obtained from the static "
+"<methodname>com.arjuna.ats.jta.UserTransaction.userTransaction()</"
+"methodname> method."
+msgstr ""
+"在 JBossJTA 里，UserTransactions 可通过静态的 <methodname>com.arjuna.ats.jta."
+"UserTransaction.userTransaction()</methodname> 方法获得。"
+
+#. Tag: para
+#: Transactions.xml:28
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr "为了选择本地 JTA 实现，有必要执行下列步骤："
+
+#. Tag: para
+#: Transactions.xml:33
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.TransactionManagerImple</property>."
+msgstr ""
+"确保 <property>com.arjuna.ats.jta.jtaTMImplementation</property> 属性被设置"
+"为 <property>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</property>。"
+
+#. Tag: para
+#: Transactions.xml:38
+#, no-c-format
+msgid ""
+"1.make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <property>com.arjuna.ats.internal.jta.transaction."
+"arjunacore.UserTransactionImple</property>."
+msgstr ""
+"1. 确保把属性 <property>com.arjuna.ats.jta.jtaUTImplementation</property> 设"
+"置为 <property>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple</property>。"
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: Transactions.xml:45
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface allows the "
+"application server to control transaction boundaries on behalf of the "
+"application being managed."
+msgstr ""
+"<interfacename>TransactionManager</interfacename> 接口允许应用服务器代替被管"
+"理的应用程序来控制事务边界。"
+
+#. Tag: para
+#: Transactions.xml:50
+#, no-c-format
+msgid ""
+"In JBossJTA, transaction manager implementations can be obtained from the "
+"static <methodname>com.arjuna.ats.jta.TransactionManager.transactionManager</"
+"methodname> method."
+msgstr ""
+"在 JBossJTA 里，事务管理者实现可以通过静态的 <methodname>com.arjuna.ats.jta."
+"TransactionManager.transactionManager</methodname> 方法获得。"
+
+#. Tag: para
+#: Transactions.xml:54
+#, no-c-format
+msgid ""
+"The Transaction Manager maintains the transaction context association with "
+"threads as part of its internal data structure. A thread’s transaction "
+"context is either null or it refers to a specific global transaction. "
+"Multiple threads may be associated with the same global transaction. As "
+"noted above, nested transactions are not supported."
+msgstr ""
+"事务管理者把和线程关联的事务上下文作为内部的数据结构进行维护。线程的事务上下"
+"文为空或指向专门的全局事务。多个线程可以和相同的全局事务相关联。如前所述，它"
+"不支持嵌套的事务。"
+
+#. Tag: para
+#: Transactions.xml:57
+#, no-c-format
+msgid ""
+"Each transaction context is encapsulated by a Transaction object, which can "
+"be used to perform operations which are specific to the target transaction, "
+"regardless of the calling thread’s transaction context."
+msgstr ""
+"每个事务上下文都用一个 Transaction 对象进行封装，它可以用来执行目标事务专有的"
+"操作，而不用管调用线程的事务上下文是什么。"
+
+#. Tag: para
+#: Transactions.xml:60
+#, no-c-format
+msgid ""
+"The <methodname>begin</methodname> method of "
+"<interfacename>TransactionManager</interfacename> starts a new top-level "
+"transaction and associates the transaction context with the calling thread. "
+"If the calling thread is already associated with a transaction then it "
+"throws the <code>NotSupportedException</code>."
+msgstr ""
+"<interfacename>TransactionManager</interfacename> 的 <methodname>begin</"
+"methodname> 方法启动新的顶层事务并将事务上下文和调用线程关联。如果调用线程已"
+"经和事务关联，那么它将抛出 <code>NotSupportedException</code>。"
+
+#. Tag: para
+#: Transactions.xml:63
+#, no-c-format
+msgid ""
+"The <methodname>getTransaction</methodname> method returns the Transaction "
+"object that represents the transaction context currently associated with the "
+"calling thread. This object can be used to perform various operations on the "
+"target transaction, described later."
+msgstr ""
+"<methodname>getTransaction</methodname> 方法返回代表当前和调用线程相关联的事"
+"务上下文的 Transaction 对象。这个对象可用来执行目标事务上的不同操作，我们在后"
+"会进行讨论。"
+
+#. Tag: para
+#: Transactions.xml:66
+#, no-c-format
+msgid ""
+"The commit method is used to complete the transaction currently associated "
+"with the calling thread. After it returns, the calling thread is associated "
+"with no transaction. If commit is called when the thread is not associated "
+"with any transaction context, the TM throws an exception. In some "
+"implementation, the commit operation is restricted to the transaction "
+"originator only. If the calling thread is not allowed to commit the "
+"transaction, the TM throws an exception. JBossJTA does not currently impose "
+"any restriction on the ability of threads to terminate transactions."
+msgstr ""
+"commit 方法用于结束当前和调用线程相关联的事务。在它返回后，调用线程将不再和任"
+"何事务关联。如果当线程没有和任何线程关联时调用 commit，TM 将抛出异常。在某些"
+"实现里，commit 操作只限于事务发起者。如果调用线程不被允许提交事务，TM 将抛出"
+"异常。目前 JBossJTA 不强加任何限制在线程终止事务的能力上。"
+
+#. Tag: para
+#: Transactions.xml:69
+#, no-c-format
+msgid ""
+"The <methodname>rollback</methodname> method is used to rollback the "
+"transaction associated with the current thread. After the "
+"<methodname>rollback</methodname> method completes, the thread is associated "
+"with no transaction."
+msgstr ""
+"<methodname>rollback</methodname> 方法用于回滚和当前线程相关联的事务。在 "
+"<methodname>rollback</methodname> 方法调用结束后，线程不再和任何事务相关联。"
+
+#. Tag: para
+#: Transactions.xml:73
+#, no-c-format
+msgid ""
+"In a multi-threaded environment it is possible that multiple threads are "
+"active within the same transaction. If checked transaction semantics have "
+"been disabled, or the transaction times out, then it is possible for a "
+"transaction to be terminated by a thread other than the one that created it. "
+"In this case, it is often important that this information is communicated to "
+"the creator. JBossTS does this during commit or rollback by throwing "
+"<code>IllegalStateException</code>."
+msgstr ""
+"在多线程环境里，多个线程有可能存在于相同的事务里。如果禁用了事务语义检查，或"
+"事务超时，那么事务就可能由不是创建它的线程终止。此时，将这个信息通知创建者通"
+"常是很重要的。JBossTS 在提交或回滚时通过抛出 <code>IllegalStateException</"
+"code> 来实现这一点。"
+
+#. Tag: title
+#: Transactions.xml:78
+#, no-c-format
+msgid "Suspending and resuming a transaction"
+msgstr "暂停和恢复事务"
+
+#. Tag: para
+#: Transactions.xml:79
+#, no-c-format
+msgid ""
+"The JTA supports the concept of a thread temporarily suspending and resuming "
+"transactions to enable it to perform non-transactional work. The suspend "
+"method is called to temporarily suspend the current transaction that is "
+"associated with the calling thread, i.e., so that the thread is no longer "
+"operating within its scope. If the thread is not associated with any "
+"transaction, a null object reference is returned; otherwise, a valid "
+"<code>Transaction</code> object is returned. The <code>Transaction</code> "
+"object can later be passed to the resume method to reinstate the transaction "
+"context."
+msgstr ""
+"JTA 支持线程临时暂停和恢复事务来执行非事务性任务的概念。调用 suspend 方法来临"
+"时暂停和当前调用线程相关的当前事务，也就是说，该线程不再在这个作用域内操作。"
+"如果线程没有和任何事务关联，空对象引用将被返回；否则将返回有效的 "
+"<code>Transaction</code> 对象。之后 <code>Transaction</code> 对象可以传递给 "
+"resume 方法来恢复事务上下文。"
+
+#. Tag: para
+#: Transactions.xml:83
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method associates the specified "
+"transaction context with the calling thread. If the transaction specified is "
+"a valid transaction, the transaction context is associated with the calling "
+"thread; otherwise, the thread is associated with no transaction."
+msgstr ""
+"<methodname>resume</methodname> 方法将指定的事务上下文和调用线程关联。如果指"
+"定的事务是一个有效事务，事务上下文将和调用线程进行关联；否则，调用线程将不和"
+"任何事务关联。"
+
+#. Tag: para
+#: Transactions.xml:87
+#, no-c-format
+msgid ""
+"If <methodname>resume</methodname> is invoked when the calling thread is "
+"already associated with another transaction, the Transaction Manager throws "
+"the <code>IllegalStateException</code> exception."
+msgstr ""
+"如果调用线程已经和其他事务关联时调用<methodname>resume</methodname>，事务管理"
+"者将抛出 <code>IllegalStateException</code> 异常。"
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+
+#. Tag: para
+#: Transactions.xml:93
+#, no-c-format
+msgid ""
+"Some Transaction Manager implementations allow a suspended transaction to be "
+"resumed by a different thread. This feature is not required by JTA, but "
+"JBossJTA does support this."
+msgstr ""
+"有些事务管理者实现允许其他线程恢复暂停的事务。虽然 JTA 并不要求实现这个功能，"
+"但 JBossJTA 支持它。 "
+
+#. Tag: para
+#: Transactions.xml:97
+#, no-c-format
+msgid ""
+"When a transaction is suspended the application server must ensure that the "
+"resources in use by the application are no longer registered with the "
+"suspended transaction. When a resource is de-listed this triggers the "
+"Transaction Manager to inform the resource manager to disassociate the "
+"transaction from the specified resource object. When the application’s "
+"transaction context is resumed, the application server must ensure that the "
+"resources in use by the application are again enlisted with the transaction. "
+"Enlisting a resource as a result of resuming a transaction triggers the "
+"Transaction Manager to inform the resource manager to re-associate the "
+"resource object with the resumed transaction."
+msgstr ""
+"当事务被暂停时，应用服务器必须确保使用的资源不再在该事务里注册。资源取消注册"
+"会触发事务管理者通知资源管理者取消指定资源对象和事务的关联。当恢复应用程序的"
+"事务上下文时，应用服务器必须确保使用的资源再次在事务里注册。恢复事务的结果是"
+"将资源登记为参与者，这触发了事务管理者通知资源管理者将指定资源对象和事务重新"
+"关联。"
+
+#. Tag: title
+#: Transactions.xml:101
+#, no-c-format
+msgid "The Transaction interface"
+msgstr "Transaction 接口"
+
+#. Tag: para
+#: Transactions.xml:102
+#, no-c-format
+msgid ""
+"The <interfacename>Transaction</interfacename> interface allows operations "
+"to be performed on the transaction associated with the target object. Every "
+"top-level transaction is associated with one <code>Transaction</code> object "
+"when the transaction is created. The <code>Transaction</code> object can be "
+"used to:"
+msgstr ""
+"<interfacename>Transaction</interfacename> 接口允许在和目标对象关联的事务上执"
+"行操作。当事务被创建时，每个顶层的事务都和一个 <code>Transaction</code> 对象"
+"相关联。<code>Transaction</code> 对象可以被用来："
+
+#. Tag: para
+#: Transactions.xml:108
+#, no-c-format
+msgid "Enlist the transactional resources in use by the application."
+msgstr "登记应用程序使用的事务性资源。"
+
+#. Tag: para
+#: Transactions.xml:113
+#, no-c-format
+msgid "Register for transaction synchronization call backs."
+msgstr "注册事务同步的回调方法。"
+
+#. Tag: para
+#: Transactions.xml:118
+#, no-c-format
+msgid "Commit or rollback the transaction."
+msgstr "提交或回滚事务。"
+
+#. Tag: para
+#: Transactions.xml:123
+#, no-c-format
+msgid "Obtain the status of the transaction."
+msgstr "获取事务的状态。"
+
+#. Tag: para
+#: Transactions.xml:128
+#, no-c-format
+msgid ""
+"The <methodname>commit</methodname> and <methodname>rollback</methodname> "
+"methods allow the target object to be committed or rolled back. The calling "
+"thread is not required to have the same transaction associated with the "
+"thread. If the calling thread is not allowed to commit the transaction, the "
+"transaction manager throws an exception. At present JBossJTA does not impose "
+"restrictions on threads terminating transactions."
+msgstr ""
+"<methodname>commit</methodname> 和 <methodname>rollback</methodname> 方法允许"
+"提交或回滚目标对象。它不要求调用线程具有和线程关联的相同事务。如果调用线程不"
+"被允许提交事务，事务管理者将抛出异常。目前，JBossJTA 不强加对线程终止事务的限"
+"制。"
+
+#. Tag: title
+#: Transactions.xml:132
+#, no-c-format
+msgid "Resource enlistment"
+msgstr "资源登记"
+
+#. Tag: para
+#: Transactions.xml:133
+#, no-c-format
+msgid ""
+"Transactional resources such as database connections are typically managed "
+"by the application server in conjunction with some resource adapter and "
+"optionally with connection pooling optimization. In order for an external "
+"transaction manager to co-ordinate transactional work performed by the "
+"resource managers, the application server must enlist and de-list the "
+"resources used in the transaction. These resources (participants) are "
+"enlisted with the transaction so that they can be informed when the "
+"transaction terminates, for example, are driven through the two-phase commit "
+"protocol."
+msgstr ""
+"事务性资源如数据库连接通常都是由应用服务器和一些资源适配器来管理，它也可以使"
+"用连接池优化。为了让外部的事务管理者和资源管理者执行的事务性工作进行协调，应"
+"用服务器必须登记和取消事务里使用的资源。这些资源（参与者）都在事务里进行了登"
+"记，这样在事务结束时它们就可以得到通知，例如，通过两阶段提交协议进行驱动。"
+
+#. Tag: para
+#: Transactions.xml:137
+#, no-c-format
+msgid ""
+"As stated previously, the JTA is much more closely integrated with the XA "
+"concept of resources than the arbitrary objects. For each resource in-use by "
+"the application, the application server invokes the "
+"<methodname>enlistResource</methodname> method with an <code>XAResource</"
+"code> object which identifies the resource in use. See for details on how "
+"the implementation of the <code>XAResource</code> can affect recovery in the "
+"event of a failure."
+msgstr ""
+"如前所述，JTA 比任何对象都更加紧密地和资源的 XA 切面进行了集成。对于应用程序"
+"使用的每个资源，应用服务器调用 <methodname>enlistResource</methodname> 和表示"
+"所使用的资源的 <code>XAResource</code>。请参考失效时 <code>XAResource</code> "
+"实现如何影响切换的详细情况。"
+
+#. Tag: para
+#: Transactions.xml:140
+#, no-c-format
+msgid ""
+"The enlistment request results in the transaction manager informing the "
+"resource manager to start associating the transaction with the work "
+"performed through the corresponding resource. The transaction manager is "
+"responsible for passing the appropriate flag in its <methodname>XAResource."
+"start</methodname> method call to the resource manager."
+msgstr ""
+"登记请求导致事务管理者通知资源管理者启动事务和通过相应资源执行的工作的关联。"
+"事务管理者负责把合适的标记传递给对资源管理者的 <methodname>XAResource.start</"
+"methodname> 方法调用。"
+
+#. Tag: para
+#: Transactions.xml:143
+#, no-c-format
+msgid ""
+"The <methodname>delistResource</methodname> method is used to disassociate "
+"the specified resource from the transaction context in the target object. "
+"The application server invokes the method with the two parameters: the "
+"<code>XAResource</code> object that represents the resource, and a flag to "
+"indicate whether the operation is due to the transaction being suspended "
+"(TMSUSPEND), a portion of the work has failed (TMFAIL), or a normal resource "
+"release by the application (TMSUCCESS)."
+msgstr ""
+"<methodname>delistResource</methodname> 方法用于取消指定资源和目标对象里的事"
+"务上下文的关联。应用服务器用两个参数调用这个方法：代表这个资源的 "
+"<code>XAResource</code> 对象，和指出该操作产生的原因，如由于事务被暂停所引起"
+"（TMSUSPEND）、部分工作失败（TMFAIL）或资源释放了普通的资源（TMSUCCESS）。"
+
+#. Tag: para
+#: Transactions.xml:146
+#, no-c-format
+msgid ""
+"The de-list request results in the transaction manager informing the "
+"resource manager to end the association of the transaction with the target "
+"<code>XAResource</code>. The flag value allows the application server to "
+"indicate whether it intends to come back to the same resource whereby the "
+"resource states must be kept intact. The transaction manager passes the "
+"appropriate flag value in its <methodname>XAResource.end</methodname> method "
+"call to the underlying resource manager."
+msgstr ""
+"取消登记的请求导致事务管理者通知资源管理者结束事务和目标 <code>XAResource</"
+"code> 的关联。flag 的值允许应用服务器指出它是否要返回相同的资源，因此资源状态"
+"必须保持不变。事务管理者把合适的 flag 值传递到对底层资源管理者的 "
+"<methodname>XAResource.end</methodname> 方法调用里。"
+
+#. Tag: title
+#: Transactions.xml:150
+#, no-c-format
+msgid "Transaction synchronization"
+msgstr "事务同步"
+
+#. Tag: para
+#: Transactions.xml:151
+#, no-c-format
+msgid ""
+"Transaction synchronization allows the application server to be notified "
+"before and after the transaction completes. For each transaction started, "
+"the application server may optionally register a Synchronization call back "
+"object to be invoked by the transaction manager:"
+msgstr ""
+"事务同步允许应用服务器在事务完成之前和之后收到通知。对于每个启动的事务，应用"
+"服务器都可以注册一个事务管理者调用的 Synchronization 回调对象："
+
+#. Tag: para
+#: Transactions.xml:157
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method is called prior to the "
+"start of the two-phase transaction complete process. This call is executed "
+"in the same transaction context of the caller who initiates the "
+"<methodname>TransactionManager.commit</methodname> or the call is executed "
+"with no transaction context if <methodname>Transaction.commit</methodname> "
+"is used."
+msgstr ""
+"<methodname>beforeCompletion</methodname> 方法在两阶段事务完成过程开始前被调"
+"用。这个调用在初始 <methodname>TransactionManager.commit</methodname> 的调用"
+"者的相同事务上下文里执行，或者在使用了 <methodname>Transaction.commit</"
+"methodname> 的情况下不带事务上下文执行。"
+
+#. Tag: para
+#: Transactions.xml:162
+#, no-c-format
+msgid ""
+"The <methodname>afterCompletion</methodname> method is called after the "
+"transaction has completed. The status of the transaction is supplied in the "
+"parameter. This method is executed without a transaction context."
+msgstr ""
+"<methodname>afterCompletion</methodname> 方法在事务结束后被调用。这个事务的状"
+"态在参数里提供。这个方法执行时不带有事务上下文。"
+
+#. Tag: title
+#: Transactions.xml:168
+#, no-c-format
+msgid "Transaction equality"
+msgstr "事务比较"
+
+#. Tag: para
+#: Transactions.xml:169
+#, no-c-format
+msgid ""
+"The transaction manager implements the Transaction object’s equals method to "
+"allow comparison between the target object and another Transaction object. "
+"The equals method should return true if the target object and the parameter "
+"object both refer to the same global transaction."
+msgstr ""
+"事务管理者实现了 Transaction 对象的 equals 方法来允许比较目标对象和其他 "
+"Transaction 对象。如果目标对象和参数对象都引用了相同的全局事务，equals 方法应"
+"该返回 true。"
+
+#. Tag: screen
+#: Transactions.xml:173
+#, no-c-format
+msgid ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
+msgstr ""
+"Transaction txObj = TransactionManager.getTransaction();\n"
+"Transaction someOtherTxObj = ..\n"
+" ..\n"
+" \n"
+"boolean isSame = txObj.equals(someOtherTxObj);"
Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po 2009-03-17 03:40:32 UTC (rev 25678)
@@ -0,0 +1,255 @@
+# translation of Author_Group.po to
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 03:33+0000\n"
+"PO-Revision-Date: 2008-11-04 10:05+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
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr "在应用服务器里使用 JBossJTA"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr "JBoss 应用服务器"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:10
+#, no-c-format
+msgid "Service Configuration"
+msgstr "服务配置"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:11
+#, no-c-format
+msgid ""
+"The JBoss Transaction Service is configured primarily via the XML files "
+"stored in the etc directory, but when run as a JBOSS service there are a "
+"number of configurable attributes available. They are as follows:"
+msgstr ""
+"JBoss 事务服务主要通过 etc 目录下的 XML 文件进行配置，但它如果作为 JBoss 服务"
+"运行，它还可以使用许多可配置属性。例如："
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:17
+#, no-c-format
+msgid ""
+"TransactionTimeout – The default transaction timeout to be used for new "
+"transactions. Specified as an integer in seconds."
+msgstr ""
+"TransactionTimeout – 用于新事务的缺省事务超时时间。它是以秒为单位的整型值。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:22
+#, no-c-format
+msgid ""
+"StatisticsEnabled – This determines whether or not the transaction service "
+"should gather statistical information. This information can then be viewed "
+"using the PerformanceStatistics MBean. Specified as a Boolean. The default "
+"is to not gather this information."
+msgstr ""
+"StatisticsEnabled – 它决定事务服务是否应该收集统计信息。这些信息可以用 "
+"PerformanceStatistics MBean 进行查看。它的值为布尔型，缺省为 false，也就是不"
+"收集统计信息。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:27
+#, no-c-format
+msgid ""
+"PropagateFullContext – This determines whether a full transactional context "
+"is propagated by context importer/exporter. If set to false only the current "
+"transaction context is propagated. If set to true the full transaction "
+"context (including parent transactions) is propagated."
+msgstr ""
+"PropagateFullContext – 它决定上下文导入者/导出者是否传递完整的事务性上下文。"
+"如果为 false，只传递当前的事务性上下文。如果为 true，整个事务上下文（包括父事"
+"务）将被传递。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:32
+#, no-c-format
+msgid ""
+"These attributes are specified as MBean attributes in the jboss-service.xml "
+"file located in the server/all/conf directory, for example:"
+msgstr ""
+"这些属性在 server/all/conf 目录里的 jboss-service.xml 文件里作为 MBean 属性指"
+"定，例如："
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:35
+#, no-c-format
+msgid ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+msgstr ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:36
+#, no-c-format
+msgid ""
+"The transaction service is configurable also via the standard JBoss "
+"Transaction Service property files. These are located in the JBossTS install "
+"location under the etc sub-directory."
+msgstr ""
+"事务服务也可以通过标准的 JBoss 事务服务属性文件进行配置。这些文件位于 "
+"JBossTS 安装目录下的 etc 子目录下。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:39
+#, no-c-format
+msgid ""
+"These files can be edited manually or through JMX. Each property file is "
+"exposed via an object with the name <code>com.arjuna.ts.properties</code> "
+"and an attribute of module where module is equal to the name of the module "
+"to be configured, for example, <code>com.arjuna.ts.properties:module=arjuna</"
+"code>."
+msgstr ""
+"这些文件可以手工或通过 JMX 进行编辑。每个属性文件都通过名为 <code>com.arjuna."
+"ts.properties</code> 的对象和要配置的模块名称进行开放，如 <code>com.arjuna."
+"ts.properties:module=arjuna</code>。"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:43
+#, no-c-format
+msgid "Logging"
+msgstr "日志"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:44
+#, no-c-format
+msgid ""
+"In order to make JBossTS logging semantically consistent with JBossAS, the "
+"TransactionManagerService modifies the level of some log messages. This is "
+"achieved by overriding the value of the <property>com.arjuna.common.util."
+"logger</property> property given in the <filename>jbossjta-properties.xml</"
+"filename> file. Therefore, the value of this property will have no effect on "
+"the logging behaviour when running embedded in JBossAS. By forcing use of "
+"the log4j_releveler logger, the TransactionManagerService causes all INFO "
+"level messages in the transaction code to be modified to behave as DEBUG "
+"messages. Therefore, these messages will not appear in log files if the "
+"filter level is INFO. All other log messages behave as normal."
+msgstr ""
+"为了使 JBossTS 日志和 JBossAS 语义上一致，TransactionManagerService 修改了某"
+"些日志消息的级别。这是通过覆盖 <filename>jbossjta-properties.xml</filename> "
+"文件里的 <property>com.arjuna.common.util.logger</property> 属性来实现的。因"
+"此，当嵌入地运行在 JBossAS 里时，这个属性的值将不会影响日志行为。通过强制使"
+"用 log4j_releveler logger，TransactionManagerService 导致所有 INFO 级别的消息"
+"都修改为 DEBUG 级别。因此，如果过滤器级别为 INFO，这些消息不会出现在日志文件"
+"里。所有其他日志消息都不受影响。"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:49
+#, no-c-format
+msgid "The services"
+msgstr "服务"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:50
+#, no-c-format
+msgid ""
+"There is currently one service offered by the JBOSS integration called "
+"TransactionManagerService. Here we shall discuss what this service does."
+msgstr ""
+"JBOSS 集成目前提供一个名为 TransactionManagerService 的服务。下面我们对其进行"
+"讨论。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:54
+#, no-c-format
+msgid ""
+"The transaction manager service’s main purpose is to ensure the recovery "
+"manager is started. It also binds the JBossTS JTA transaction manager to "
+"java:/TransactionManager name with the JNDI provider. This service depends "
+"upon the existence of the CORBA ORB Service and it must be using JacORB as "
+"the underlying ORB implementation."
+msgstr ""
+"事务管理者的主要目的是确保启动切换管理者（Recovery Manager）。它也把 JBossTS "
+"JTA 事务管理者在 JNDI 提供者里绑定为 java:/TransactionManager。这个服务依赖"
+"于 CORBA ORB 服务的扩展，它必须把 JacORB 作为底层的 ORB 实现来使用。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:57
+#, no-c-format
+msgid "There are two instances of this service:"
+msgstr "这个服务有两个模式："
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:62
+#, no-c-format
+msgid ""
+"distributed: this uses the JTS enabled transaction manager implementation "
+"and hence supports distributed transactions and recovery. To configure this "
+"use the <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname> class. This is the default configuration."
+msgstr ""
+"distributed：它使用启用 JTS 的事务管理者实现，因此它支持分布式事务和切换。你"
+"可以用 <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname> 类配置它。这是缺省的模式。"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:67
+#, no-c-format
+msgid ""
+"local: this uses the purely local JTA implementation. To configure this use "
+"the <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
+"classname> class."
+msgstr ""
+"local：它使用纯本地的 JTA 实现。你可以用 <classname>com.arjuna.ats.jbossatx."
+"jta.TransactionManagerService</classname> 类配置它。"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:73
+#, no-c-format
+msgid "Ensuring Transactional Context is Propagated to the Server"
+msgstr "确保事务性上下文被传递到服务器里"
+
+#. Tag: para
+#: Using_JBossJTA_in_Application_Servers.xml:74
+#, no-c-format
+msgid ""
+"It is possible to coordinate transactions from a coordinator which is not "
+"located within the JBoss server (e.g. using transactions created by an "
+"external OTS server). To ensure the transaction context is propagated via "
+"JRMP invocations to the server, the transaction propagation context factory "
+"needs to be explicitly set for the JRMP invoker proxy. This is done as "
+"follows:"
+msgstr ""
+"通过 JBoss 服务器外部的协调者协调事务是可能的（如使用外部 OTS 服务器创建的事"
+"务）。要确保通过 JRMP 调用把事务上下文传递到服务器里，事务传递上下文工厂需要"
+"为 JRMP 调用者代理显性地进行设置。如："
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
More information about the jboss-svn-commits
mailing list