[jboss-cvs] JBossAS SVN: r78769 - in projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide: de-DE and 5 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Sep 23 02:27:20 EDT 2008
Author: xhuang at jboss.com
Date: 2008-09-23 02:27:19 -0400 (Tue, 23 Sep 2008)
New Revision: 78769
Added:
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/An_Introduction_to_the_JTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Configuring_JBossJTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Examples.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/JBoss_Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/JDBC_and_Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/The_Resource_Manager.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transaction_Recovery.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Using_JBossJTA_in_Application_Servers.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/An_Introduction_to_the_JTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Configuring_JBossJTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Examples.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/JBoss_Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/JDBC_and_Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/The_Resource_Manager.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transaction_Recovery.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Using_JBossJTA_in_Application_Servers.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/An_Introduction_to_the_JTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Configuring_JBossJTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Examples.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/JBoss_Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/JDBC_and_Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/The_Resource_Manager.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transaction_Recovery.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Using_JBossJTA_in_Application_Servers.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/An_Introduction_to_the_JTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Configuring_JBossJTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Examples.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/JBoss_Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/JDBC_and_Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/The_Resource_Manager.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transaction_Recovery.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Using_JBossJTA_in_Application_Servers.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Configuring_JBossJTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Examples.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/JBoss_Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transactions_JTA_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po
Modified:
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/Makefile
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/An_Introduction_to_the_JTA.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Author_Group.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Book_Info.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Configuring_JBossJTA.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Examples.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/JDBC_and_Transactions.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Preface.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Revision_History.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/The_Resource_Manager.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Transaction_Recovery.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Transactions.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Using_JBossJTA_in_Application_Servers.pot
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/messages.mo
Log:
merge
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/Makefile
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/Makefile 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/Makefile 2008-09-23 06:27:19 UTC (rev 78769)
@@ -5,7 +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 = ja-JP
+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: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/An_Introduction_to_the_JTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/An_Introduction_to_the_JTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/An_Introduction_to_the_JTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,111 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr ""
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Appendix.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"PO-Revision-Date: 2008-09-01 00:05+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Author_Group.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Book_Info.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,44 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Configuring_JBossJTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Configuring_JBossJTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Configuring_JBossJTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,135 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Examples.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Examples.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Examples.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,470 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr ""
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/JBoss_Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/JDBC_and_Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/JDBC_and_Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/JDBC_and_Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,750 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Preface.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Revision_History.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,26 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/The_Resource_Manager.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/The_Resource_Manager.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/The_Resource_Manager.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,662 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transaction_Recovery.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transaction_Recovery.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transaction_Recovery.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,329 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:8
+#, no-c-format
+msgid "Failure recovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:9
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:12
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:16
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:20
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:25
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:30
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:36
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:43
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:44
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:48
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:52
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:55
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:56
+#, 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:59
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:65
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:68
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:69
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:74
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:79
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:84
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:90
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:97
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:98
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:103
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:106
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:109
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:112
+#, 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,472 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr ""
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/de-DE/Using_JBossJTA_in_Application_Servers.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,208 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr ""
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/An_Introduction_to_the_JTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/An_Introduction_to_the_JTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/An_Introduction_to_the_JTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,111 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr ""
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Appendix.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"PO-Revision-Date: 2008-09-01 00:05+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Author_Group.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Book_Info.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,44 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Configuring_JBossJTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Configuring_JBossJTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Configuring_JBossJTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,135 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Examples.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Examples.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Examples.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,470 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr ""
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/JBoss_Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/JDBC_and_Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/JDBC_and_Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/JDBC_and_Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,750 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Preface.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Revision_History.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,26 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/The_Resource_Manager.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/The_Resource_Manager.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/The_Resource_Manager.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,662 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transaction_Recovery.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transaction_Recovery.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transaction_Recovery.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,329 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:8
+#, no-c-format
+msgid "Failure recovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:9
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:12
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:16
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:20
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:25
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:30
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:36
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:43
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:44
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:48
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:52
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:55
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:56
+#, 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:59
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:65
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:68
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:69
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:74
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:79
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:84
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:90
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:97
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:98
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:103
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:106
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:109
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:112
+#, 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,472 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr ""
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/es-ES/Using_JBossJTA_in_Application_Servers.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,208 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr ""
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/An_Introduction_to_the_JTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/An_Introduction_to_the_JTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/An_Introduction_to_the_JTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,111 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr ""
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Appendix.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"PO-Revision-Date: 2008-09-01 00:05+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Author_Group.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Book_Info.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,44 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Configuring_JBossJTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Configuring_JBossJTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Configuring_JBossJTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,135 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Examples.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Examples.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Examples.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,470 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr ""
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/JBoss_Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/JDBC_and_Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/JDBC_and_Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/JDBC_and_Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,750 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Preface.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Revision_History.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,26 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/The_Resource_Manager.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/The_Resource_Manager.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/The_Resource_Manager.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,662 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transaction_Recovery.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transaction_Recovery.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transaction_Recovery.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,329 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:8
+#, no-c-format
+msgid "Failure recovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:9
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:12
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:16
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:20
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:25
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:30
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:36
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:43
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:44
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:48
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:52
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:55
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:56
+#, 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:59
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:65
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:68
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:69
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:74
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:79
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:84
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:90
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:97
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:98
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:103
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:106
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:109
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:112
+#, 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,472 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr ""
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/fr-FR/Using_JBossJTA_in_Application_Servers.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,208 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr ""
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/An_Introduction_to_the_JTA.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/An_Introduction_to_the_JTA.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/An_Introduction_to_the_JTA.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: An_Introduction_to_the_JTA.xml:10
+#: An_Introduction_to_the_JTA.xml:8
#, no-c-format
msgid "The Java Transaction API"
msgstr ""
#. Tag: para
-#: An_Introduction_to_the_JTA.xml:11
+#: An_Introduction_to_the_JTA.xml:9
#, no-c-format
msgid ""
"The interfaces specified by the many transaction standards are typically too "
@@ -42,7 +42,7 @@
msgstr ""
#. Tag: para
-#: An_Introduction_to_the_JTA.xml:14
+#: An_Introduction_to_the_JTA.xml:12
#, no-c-format
msgid ""
"With reference to [JTA99], distributed transaction services typically "
@@ -50,7 +50,7 @@
msgstr ""
#. Tag: para
-#: An_Introduction_to_the_JTA.xml:19
+#: An_Introduction_to_the_JTA.xml:17
#, no-c-format
msgid ""
"Application server: which provides the infrastructure required to support "
@@ -59,7 +59,7 @@
msgstr ""
#. Tag: para
-#: An_Introduction_to_the_JTA.xml:24
+#: An_Introduction_to_the_JTA.xml:22
#, no-c-format
msgid ""
"Transaction manager: provides the services and management functions required "
@@ -68,7 +68,7 @@
msgstr ""
#. Tag: para
-#: An_Introduction_to_the_JTA.xml:29
+#: An_Introduction_to_the_JTA.xml:27
#, no-c-format
msgid ""
"Resource manager: (through a resource adapter<footnote> <para> A Resource "
@@ -82,7 +82,7 @@
msgstr ""
#. Tag: para
-#: An_Introduction_to_the_JTA.xml:38
+#: An_Introduction_to_the_JTA.xml:36
#, no-c-format
msgid ""
"A communication resource manager (CRM): supports transaction context "
@@ -91,7 +91,7 @@
msgstr ""
#. Tag: para
-#: An_Introduction_to_the_JTA.xml:43
+#: An_Introduction_to_the_JTA.xml:41
#, no-c-format
msgid ""
"From the transaction manager’s perspective, the actual implementation of the "
@@ -104,7 +104,7 @@
msgstr ""
#. Tag: para
-#: An_Introduction_to_the_JTA.xml:47
+#: An_Introduction_to_the_JTA.xml:45
#, no-c-format
msgid ""
"The JTA support provided by JBossJTA is compliant with the 1.0.1 "
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Author_Group.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Author_Group.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Author_Group.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Book_Info.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Book_Info.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Book_Info.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -17,29 +17,29 @@
#. Tag: title
#: Book_Info.xml:6
#, no-c-format
-msgid "Transactions JTA Programmers Guide"
+msgid "JBoss Transactions JTA Programmers Guide"
msgstr ""
#. Tag: subtitle
#: Book_Info.xml:7
#, no-c-format
-msgid "JBoss Enterprise Application Platform"
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
msgstr ""
#. Tag: para
-#: Book_Info.xml:11
+#: Book_Info.xml:13
#, no-c-format
msgid "This book is about the Transactions JTA from the view of the programmer"
msgstr ""
#. Tag: phrase
-#: Book_Info.xml:19
+#: Book_Info.xml:21
#, no-c-format
msgid "Logo"
msgstr ""
#. Tag: holder
-#: Book_Info.xml:25
+#: Book_Info.xml:27
#, no-c-format
msgid "&HOLDER;"
msgstr ""
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Configuring_JBossJTA.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Configuring_JBossJTA.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Configuring_JBossJTA.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: Configuring_JBossJTA.xml:10
+#: Configuring_JBossJTA.xml:8
#, no-c-format
msgid "Configuring options"
msgstr ""
#. Tag: para
-#: Configuring_JBossJTA.xml:11
+#: Configuring_JBossJTA.xml:9
#, no-c-format
msgid ""
"The following table shows the configuration features, with default values "
@@ -36,49 +36,49 @@
msgstr ""
#. Tag: title
-#: Configuring_JBossJTA.xml:15
+#: Configuring_JBossJTA.xml:13
#, no-c-format
msgid "JBossJTA configuration options."
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:19
+#: Configuring_JBossJTA.xml:17
#, no-c-format
msgid "Configuration Name"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:22
+#: Configuring_JBossJTA.xml:20
#, no-c-format
msgid "Possibile Values"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:25
+#: Configuring_JBossJTA.xml:23
#, no-c-format
msgid "Relevant Section"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:32
+#: Configuring_JBossJTA.xml:30
#, no-c-format
msgid "com.arjuna.ats.jta.supportSubtransactions"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:35
+#: Configuring_JBossJTA.xml:33
#, no-c-format
msgid "YES/NO"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:42
+#: Configuring_JBossJTA.xml:40
#, no-c-format
msgid "com.arjuna.ats.jta.jtaTMImplementation"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:45
+#: Configuring_JBossJTA.xml:43
#, no-c-format
msgid ""
"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple/"
@@ -86,13 +86,13 @@
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:52
+#: Configuring_JBossJTA.xml:50
#, no-c-format
msgid "com.arjuna.ats.jta.jtaUTImplementation"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:55
+#: Configuring_JBossJTA.xml:53
#, no-c-format
msgid ""
"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple/com."
@@ -100,37 +100,37 @@
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:62
+#: Configuring_JBossJTA.xml:60
#, no-c-format
msgid "com.arjuna.ats.jta.xaBackoffPeriod"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:71
+#: Configuring_JBossJTA.xml:69
#, no-c-format
msgid "com.arjuna.ats.jdbc.isolationLevel"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:74
+#: Configuring_JBossJTA.xml:72
#, no-c-format
msgid "Any supported JDBC isolation level."
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:81
+#: Configuring_JBossJTA.xml:79
#, no-c-format
msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:84
+#: Configuring_JBossJTA.xml:82
#, no-c-format
msgid "true/false"
msgstr ""
#. Tag: entry
-#: Configuring_JBossJTA.xml:87
+#: Configuring_JBossJTA.xml:85
#, no-c-format
msgid "Chapter 3"
msgstr ""
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Examples.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Examples.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Examples.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: Examples.xml:10
+#: Examples.xml:8
#, no-c-format
msgid "JDBC example"
msgstr ""
#. Tag: para
-#: Examples.xml:11
+#: Examples.xml:9
#, no-c-format
msgid ""
"The following code illustrates many of the points described above (note that "
@@ -38,7 +38,7 @@
msgstr ""
#. Tag: screen
-#: Examples.xml:14
+#: Examples.xml:12
#, no-c-format
msgid ""
"public class JDBCTest\n"
@@ -200,13 +200,13 @@
msgstr ""
#. Tag: title
-#: Examples.xml:18
+#: Examples.xml:16
#, no-c-format
msgid "Failure recovery example"
msgstr ""
#. Tag: para
-#: Examples.xml:19
+#: Examples.xml:17
#, no-c-format
msgid ""
"This class implements the <interfacename>XAResourceRecovery</interfacename> "
@@ -219,7 +219,7 @@
msgstr ""
#. Tag: para
-#: Examples.xml:23
+#: Examples.xml:21
#, no-c-format
msgid ""
"This is only an <emphasis>example</emphasis> of the sorts of things an "
@@ -232,7 +232,7 @@
msgstr ""
#. Tag: para
-#: Examples.xml:27
+#: Examples.xml:25
#, no-c-format
msgid ""
"The db parameters specified in the property file are assumed to be in the "
@@ -240,37 +240,37 @@
msgstr ""
#. Tag: para
-#: Examples.xml:32
+#: Examples.xml:30
#, no-c-format
msgid "DB_x_DatabaseURL="
msgstr ""
#. Tag: para
-#: Examples.xml:37
+#: Examples.xml:35
#, no-c-format
msgid "DB_x_DatabaseUser="
msgstr ""
#. Tag: para
-#: Examples.xml:42
+#: Examples.xml:40
#, no-c-format
msgid "DB_x_DatabasePassword="
msgstr ""
#. Tag: para
-#: Examples.xml:47
+#: Examples.xml:45
#, no-c-format
msgid "DB_x_DatabaseDynamicClass="
msgstr ""
#. Tag: para
-#: Examples.xml:52
+#: Examples.xml:50
#, no-c-format
msgid "Where x is the number of the connection information."
msgstr ""
#. Tag: para
-#: Examples.xml:56
+#: Examples.xml:54
#, no-c-format
msgid ""
"Some error handling code has been removed from this text for ease of "
@@ -278,7 +278,7 @@
msgstr ""
#. Tag: screen
-#: Examples.xml:60
+#: Examples.xml:58
#, no-c-format
msgid ""
"/*\n"
@@ -461,7 +461,7 @@
msgstr ""
#. Tag: para
-#: Examples.xml:61
+#: Examples.xml:59
#, no-c-format
msgid ""
"The class <classname>com.arjuna.ats.internal.jdbc.recovery."
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/JDBC_and_Transactions.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/JDBC_and_Transactions.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/JDBC_and_Transactions.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:10
+#: JDBC_and_Transactions.xml:8
#, no-c-format
msgid "Using the transactional JDBC driver"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:11
+#: JDBC_and_Transactions.xml:9
#, no-c-format
msgid ""
"JBossJTA supports the construction of both local and distributed "
@@ -38,7 +38,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:14
+#: JDBC_and_Transactions.xml:12
#, no-c-format
msgid ""
"The JDBC 2.0 support has been tested with the following drivers and "
@@ -46,37 +46,37 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:19
+#: JDBC_and_Transactions.xml:17
#, no-c-format
msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:24
+#: JDBC_and_Transactions.xml:22
#, no-c-format
msgid "MS SQL Server 2000 native driver."
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:29
+#: JDBC_and_Transactions.xml:27
#, no-c-format
msgid "In the past we have qualified against:"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:34
+#: JDBC_and_Transactions.xml:32
#, no-c-format
msgid "Merant’s Sequelink 5.1 with Oracle 8.1.6"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:39
+#: JDBC_and_Transactions.xml:37
#, no-c-format
msgid "Cloudscape 3.6 with Cloudscape’s own database."
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:44
+#: JDBC_and_Transactions.xml:42
#, no-c-format
msgid ""
"However, these drivers and databases are no longer part of our supported "
@@ -85,13 +85,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:48
+#: JDBC_and_Transactions.xml:46
#, no-c-format
msgid "Managing transactions"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:49
+#: JDBC_and_Transactions.xml:47
#, no-c-format
msgid ""
"JBossJTA must be able to associate work performed on a JDBC connection with "
@@ -102,13 +102,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:54
+#: JDBC_and_Transactions.xml:52
#, no-c-format
msgid "Restrictions"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:55
+#: JDBC_and_Transactions.xml:53
#, no-c-format
msgid ""
"The following restrictions are imposed by limitations in the JDBC "
@@ -117,7 +117,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:59
+#: JDBC_and_Transactions.xml:57
#, no-c-format
msgid ""
"Nested transactions are not supported by JDBC 2.0. If an attempt is made to "
@@ -128,13 +128,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:65
+#: JDBC_and_Transactions.xml:63
#, no-c-format
msgid "Transactional drivers"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:66
+#: JDBC_and_Transactions.xml:64
#, no-c-format
msgid ""
"The JBossJTA approach to incorporating JDBC connections within transactions "
@@ -149,13 +149,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:70
+#: JDBC_and_Transactions.xml:68
#, no-c-format
msgid "Loading drivers"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:71
+#: JDBC_and_Transactions.xml:69
#, no-c-format
msgid ""
"The driver may be directly instantiated and used within an application. For "
@@ -163,13 +163,13 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:75
+#: JDBC_and_Transactions.xml:73
#, no-c-format
msgid "TransactionalDriver arjunaJDBC2Driver = new TransactionalDriver();"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:76
+#: JDBC_and_Transactions.xml:74
#, no-c-format
msgid ""
"They can be registered with the JDBC driver manager (<code>java.sql."
@@ -180,7 +180,7 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:79
+#: JDBC_and_Transactions.xml:77
#, no-c-format
msgid ""
"/*\n"
@@ -204,7 +204,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:80
+#: JDBC_and_Transactions.xml:78
#, no-c-format
msgid ""
"Alternatively, the <methodname>Class.forName()</methodname> method may be "
@@ -212,13 +212,13 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:83
+#: JDBC_and_Transactions.xml:81
#, no-c-format
msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:84
+#: JDBC_and_Transactions.xml:82
#, no-c-format
msgid ""
"Calling <methodname>Class.forName()</methodname> will automatically register "
@@ -227,7 +227,7 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:87
+#: JDBC_and_Transactions.xml:85
#, no-c-format
msgid ""
"sun.jdbc.odbc.JdbcOdbcDriver drv = new sun.jdbc.odbc.JdbcOdbcDriver();\n"
@@ -236,7 +236,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:88
+#: JDBC_and_Transactions.xml:86
#, no-c-format
msgid ""
"When you have loaded a driver, it is available for making a connection with "
@@ -244,13 +244,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:94
+#: JDBC_and_Transactions.xml:92
#, no-c-format
msgid "Connections"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:95
+#: JDBC_and_Transactions.xml:93
#, no-c-format
msgid ""
"In this section we shall discuss the notion of transactional JDBC "
@@ -259,13 +259,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:99
+#: JDBC_and_Transactions.xml:97
#, no-c-format
msgid "Making the connection"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:100
+#: JDBC_and_Transactions.xml:98
#, no-c-format
msgid ""
"Because JDBC connectivity in JBossJTA works by simply providing a new JDBC "
@@ -275,13 +275,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:105
+#: JDBC_and_Transactions.xml:103
#, no-c-format
msgid "JDBC 2.0"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:106
+#: JDBC_and_Transactions.xml:104
#, no-c-format
msgid ""
"Before describing the JDBC 2.0 support it is necessary to mention that the "
@@ -291,7 +291,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:112
+#: JDBC_and_Transactions.xml:110
#, no-c-format
msgid ""
"<property>userName</property>: the user name to use when attempting to "
@@ -299,7 +299,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:117
+#: JDBC_and_Transactions.xml:115
#, no-c-format
msgid ""
"<property>password</property>: the password to use when attempting to "
@@ -307,7 +307,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:122
+#: JDBC_and_Transactions.xml:120
#, no-c-format
msgid ""
"<property>createDb</property>: if set to true, the driver will attempt to "
@@ -316,7 +316,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:127
+#: JDBC_and_Transactions.xml:125
#, no-c-format
msgid ""
"<property>dynamicClass</property>: this specifies a class to instantiate to "
@@ -324,13 +324,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:133
+#: JDBC_and_Transactions.xml:131
#, no-c-format
msgid "XADataSources"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:134
+#: JDBC_and_Transactions.xml:132
#, no-c-format
msgid ""
"JDBC 2.0 connections are created from appropriate DataSources. Those "
@@ -345,7 +345,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:138
+#: JDBC_and_Transactions.xml:136
#, no-c-format
msgid ""
"There are two ways in which the JBossJTA JDBC 2.0 support can obtain "
@@ -355,13 +355,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:142
+#: JDBC_and_Transactions.xml:140
#, no-c-format
msgid "Java Naming and Directory Interface (JNDI)"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:143
+#: JDBC_and_Transactions.xml:141
#, no-c-format
msgid ""
"In order to allow a JDBC driver to use arbitrary DataSources without having "
@@ -377,7 +377,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:147
+#: JDBC_and_Transactions.xml:145
#, no-c-format
msgid ""
"To get the <classname>TransactionalDriver</classname> class to use a JNDI "
@@ -388,7 +388,7 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:150
+#: JDBC_and_Transactions.xml:148
#, no-c-format
msgid ""
"XADataSource ds = MyXADataSource();\n"
@@ -404,7 +404,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:151
+#: JDBC_and_Transactions.xml:149
#, no-c-format
msgid ""
"Where the <property>Context.INITIAL_CONTEXT_FACTORY</property> property is "
@@ -412,7 +412,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:154
+#: JDBC_and_Transactions.xml:152
#, no-c-format
msgid ""
"Then the application must pass an appropriate connection URL to the JDBC 2.0 "
@@ -420,7 +420,7 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:157
+#: JDBC_and_Transactions.xml:155
#, no-c-format
msgid ""
"Properties dbProps = new Properties();\n"
@@ -434,7 +434,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:158
+#: JDBC_and_Transactions.xml:156
#, no-c-format
msgid ""
"The JNDI URL must be pre-pended with jdbc:arjuna: in order for the "
@@ -443,13 +443,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:162
+#: JDBC_and_Transactions.xml:160
#, no-c-format
msgid "Dynamic class instantiation"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:163
+#: JDBC_and_Transactions.xml:161
#, no-c-format
msgid ""
"Many JDBC 2.0 implementations provide proprietary implementations of "
@@ -468,61 +468,61 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:168
+#: JDBC_and_Transactions.xml:166
#, no-c-format
msgid "Dynamic Class property values for specific databases"
msgstr ""
#. Tag: entry
-#: JDBC_and_Transactions.xml:172
+#: JDBC_and_Transactions.xml:170
#, no-c-format
msgid "Database Type"
msgstr ""
#. Tag: entry
-#: JDBC_and_Transactions.xml:175
+#: JDBC_and_Transactions.xml:173
#, no-c-format
msgid "Property Name"
msgstr ""
#. Tag: entry
-#: JDBC_and_Transactions.xml:182
+#: JDBC_and_Transactions.xml:180
#, no-c-format
msgid "Cloudscape 3.6"
msgstr ""
#. Tag: entry
-#: JDBC_and_Transactions.xml:185
+#: JDBC_and_Transactions.xml:183
#, no-c-format
msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
msgstr ""
#. Tag: entry
-#: JDBC_and_Transactions.xml:190
+#: JDBC_and_Transactions.xml:188
#, no-c-format
msgid "Sequelink 5.1"
msgstr ""
#. Tag: entry
-#: JDBC_and_Transactions.xml:193
+#: JDBC_and_Transactions.xml:191
#, no-c-format
msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
msgstr ""
#. Tag: entry
-#: JDBC_and_Transactions.xml:198
+#: JDBC_and_Transactions.xml:196
#, no-c-format
msgid "Oracle 8.1.6"
msgstr ""
#. Tag: entry
-#: JDBC_and_Transactions.xml:201
+#: JDBC_and_Transactions.xml:199
#, no-c-format
msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:209
+#: JDBC_and_Transactions.xml:207
#, no-c-format
msgid ""
"As mentioned earlier, JBossTS no longer supports Cloudscape or Sequelink as "
@@ -531,7 +531,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:213
+#: JDBC_and_Transactions.xml:211
#, no-c-format
msgid ""
"The application code must specify which dynamic class the "
@@ -540,7 +540,7 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:216
+#: JDBC_and_Transactions.xml:214
#, no-c-format
msgid ""
"Properties dbProps = new Properties();\n"
@@ -556,13 +556,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:218
+#: JDBC_and_Transactions.xml:216
#, no-c-format
msgid "Using the connection"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:219
+#: JDBC_and_Transactions.xml:217
#, no-c-format
msgid ""
"Once the connection has been established (for example, using the "
@@ -574,13 +574,13 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:224
+#: JDBC_and_Transactions.xml:222
#, no-c-format
msgid "JDBC does not support subtransactions."
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:228
+#: JDBC_and_Transactions.xml:226
#, no-c-format
msgid ""
"Transaction timeouts can be used to automatically terminate transactions "
@@ -588,7 +588,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:231
+#: JDBC_and_Transactions.xml:229
#, no-c-format
msgid ""
"JBossJTA connections can be used within multiple different transactions "
@@ -603,7 +603,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:234
+#: JDBC_and_Transactions.xml:232
#, no-c-format
msgid ""
"JBossJTA will automatically register the JDBC driver connection with the "
@@ -614,7 +614,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:237
+#: JDBC_and_Transactions.xml:235
#, no-c-format
msgid ""
"Once created, the driver and any connection can be used in the same way as "
@@ -622,7 +622,7 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:240
+#: JDBC_and_Transactions.xml:238
#, no-c-format
msgid ""
"Statement stmt = conn.createStatement();\n"
@@ -643,13 +643,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:242
+#: JDBC_and_Transactions.xml:240
#, no-c-format
msgid "Connection pooling"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:243
+#: JDBC_and_Transactions.xml:241
#, no-c-format
msgid ""
"For each user name and password, JBossJTA will maintain a single instance of "
@@ -662,13 +662,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:248
+#: JDBC_and_Transactions.xml:246
#, no-c-format
msgid "Reusing connections"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:249
+#: JDBC_and_Transactions.xml:247
#, no-c-format
msgid ""
"Some JDBC drivers allow the reuse of a connection for multiple different "
@@ -682,19 +682,19 @@
msgstr ""
#. Tag: screen
-#: JDBC_and_Transactions.xml:253
+#: JDBC_and_Transactions.xml:251
#, no-c-format
msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:255
+#: JDBC_and_Transactions.xml:253
#, no-c-format
msgid "Terminating the transaction"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:256
+#: JDBC_and_Transactions.xml:254
#, no-c-format
msgid ""
"Whenever a transaction terminates (either explicitly by the application "
@@ -705,13 +705,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:261
+#: JDBC_and_Transactions.xml:259
#, no-c-format
msgid "AutoCommit"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:262
+#: JDBC_and_Transactions.xml:260
#, no-c-format
msgid ""
"If <code>AutoCommit</code> of the <code>java.sql.Connection</code> is set to "
@@ -724,13 +724,13 @@
msgstr ""
#. Tag: title
-#: JDBC_and_Transactions.xml:267
+#: JDBC_and_Transactions.xml:265
#, no-c-format
msgid "Setting isolation levels"
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:268
+#: JDBC_and_Transactions.xml:266
#, no-c-format
msgid ""
"When using the JBossJTA JDBC driver, it may be necessary to set the "
@@ -744,7 +744,7 @@
msgstr ""
#. Tag: para
-#: JDBC_and_Transactions.xml:273
+#: JDBC_and_Transactions.xml:271
#, no-c-format
msgid ""
"At present this property applies to all XA connections created in the JVM."
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Preface.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Preface.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Preface.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Revision_History.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Revision_History.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Revision_History.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -14,8 +14,14 @@
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
msgstr ""
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/The_Resource_Manager.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/The_Resource_Manager.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/The_Resource_Manager.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Transaction_Recovery.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Transaction_Recovery.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Transaction_Recovery.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: Transaction_Recovery.xml:10
+#: Transaction_Recovery.xml:8
#, no-c-format
msgid "Failure recovery"
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:11
+#: Transaction_Recovery.xml:9
#, no-c-format
msgid ""
"During recovery, the Transaction Manager needs to be able to communicate to "
@@ -42,7 +42,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:14
+#: Transaction_Recovery.xml:12
#, no-c-format
msgid ""
"Because <code>XAResource</code> objects are not persistent across system "
@@ -59,7 +59,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:18
+#: Transaction_Recovery.xml:16
#, no-c-format
msgid ""
"When running XA recovery it is necessary to tell JBossTS which types of Xid "
@@ -74,7 +74,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:22
+#: Transaction_Recovery.xml:20
#, no-c-format
msgid ""
"If using the JBossJTA JDBC 2.0 driver, then JBossJTA will take care of all "
@@ -83,7 +83,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:27
+#: Transaction_Recovery.xml:25
#, no-c-format
msgid ""
"If the <code>XAResource</code> is serializable, then the serialized form "
@@ -93,7 +93,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:32
+#: Transaction_Recovery.xml:30
#, no-c-format
msgid ""
"The <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
@@ -104,7 +104,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:38
+#: Transaction_Recovery.xml:36
#, no-c-format
msgid ""
"In JBossTS 3.3 the interface <interfacename>XAConnectionRecovery</"
@@ -113,13 +113,13 @@
msgstr ""
#. Tag: title
-#: Transaction_Recovery.xml:45
+#: Transaction_Recovery.xml:43
#, no-c-format
msgid "Recovering XAConnections"
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:46
+#: Transaction_Recovery.xml:44
#, no-c-format
msgid ""
"When recovering from failures, JBossJTA requires the ability to reconnect to "
@@ -136,7 +136,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:50
+#: Transaction_Recovery.xml:48
#, no-c-format
msgid ""
"If using the transactional JDBC 2.0 driver provided with JBossJTA, then no "
@@ -144,7 +144,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:54
+#: Transaction_Recovery.xml:52
#, no-c-format
msgid ""
"To inform the recovery system about each of the <code>XAResourceRecovery</"
@@ -156,14 +156,14 @@
msgstr ""
#. Tag: screen
-#: Transaction_Recovery.xml:57
+#: Transaction_Recovery.xml:55
#, no-c-format
msgid ""
"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:58
+#: Transaction_Recovery.xml:56
#, no-c-format
msgid ""
"Additional information that will be passed to the instance when it is "
@@ -171,7 +171,7 @@
msgstr ""
#. Tag: screen
-#: Transaction_Recovery.xml:61
+#: Transaction_Recovery.xml:59
#, no-c-format
msgid ""
"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
@@ -179,19 +179,19 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:63
+#: Transaction_Recovery.xml:61
#, no-c-format
msgid "These properties need to go into the JTA section of the property file."
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:67
+#: Transaction_Recovery.xml:65
#, no-c-format
msgid "Any errors will be reported during recovery."
msgstr ""
#. Tag: screen
-#: Transaction_Recovery.xml:70
+#: Transaction_Recovery.xml:68
#, no-c-format
msgid ""
"public interface XAResourceRecovery\n"
@@ -205,13 +205,13 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:71
+#: Transaction_Recovery.xml:69
#, no-c-format
msgid "Each method should return the following information:"
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:76
+#: Transaction_Recovery.xml:74
#, no-c-format
msgid ""
"<methodname>initialise</methodname>: once the instance has been created, any "
@@ -222,7 +222,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:81
+#: Transaction_Recovery.xml:79
#, no-c-format
msgid ""
"<methodname>hasMoreResources</methodname>: each <code>XAResourceRecovery</"
@@ -236,7 +236,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:86
+#: Transaction_Recovery.xml:84
#, no-c-format
msgid ""
"<methodname>getXAResource</methodname>: returns an instance of the "
@@ -249,7 +249,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:92
+#: Transaction_Recovery.xml:90
#, no-c-format
msgid ""
"If you want your <code>XAResourceRecovery</code> instance to be called "
@@ -259,13 +259,13 @@
msgstr ""
#. Tag: title
-#: Transaction_Recovery.xml:99
+#: Transaction_Recovery.xml:97
#, no-c-format
msgid "Shipped XAResourceRecovery implementations"
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:100
+#: Transaction_Recovery.xml:98
#, no-c-format
msgid ""
"Recovery of <interfacename>XA</interfacename> datasources can sometimes be "
@@ -275,7 +275,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:105
+#: Transaction_Recovery.xml:103
#, no-c-format
msgid ""
"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
@@ -285,7 +285,7 @@
msgstr ""
#. Tag: screen
-#: Transaction_Recovery.xml:108
+#: Transaction_Recovery.xml:106
#, no-c-format
msgid ""
"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
@@ -301,7 +301,7 @@
msgstr ""
#. Tag: para
-#: Transaction_Recovery.xml:111
+#: Transaction_Recovery.xml:109
#, no-c-format
msgid ""
"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
@@ -312,7 +312,7 @@
msgstr ""
#. Tag: screen
-#: Transaction_Recovery.xml:114
+#: Transaction_Recovery.xml:112
#, no-c-format
msgid ""
"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Transactions.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Transactions.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Transactions.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: Transactions.xml:10
+#: Transactions.xml:8
#, no-c-format
msgid "The API"
msgstr ""
#. Tag: para
-#: Transactions.xml:11
+#: Transactions.xml:9
#, no-c-format
msgid ""
"The Java Transaction API consists of three elements: a high-level "
@@ -40,7 +40,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:15
+#: Transactions.xml:13
#, no-c-format
msgid ""
"Each Xid that JBossTS creates must have a unique node identifier encoded "
@@ -54,13 +54,13 @@
msgstr ""
#. Tag: title
-#: Transactions.xml:20
+#: Transactions.xml:18
#, no-c-format
msgid "UserTransaction"
msgstr ""
#. Tag: para
-#: Transactions.xml:21
+#: Transactions.xml:19
#, no-c-format
msgid ""
"The <interfacename>UserTransaction</interfacename> interface provides "
@@ -74,7 +74,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:26
+#: Transactions.xml:24
#, no-c-format
msgid ""
"In JBossJTA, UserTransactions can be obtained from the static "
@@ -83,7 +83,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:30
+#: Transactions.xml:28
#, no-c-format
msgid ""
"In order to select the local JTA implementation it is necessary to perform "
@@ -91,7 +91,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:35
+#: Transactions.xml:33
#, no-c-format
msgid ""
"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
@@ -100,7 +100,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:40
+#: Transactions.xml:38
#, no-c-format
msgid ""
"1.make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
@@ -109,13 +109,13 @@
msgstr ""
#. Tag: title
-#: Transactions.xml:46
+#: Transactions.xml:44
#, no-c-format
msgid "TransactionManager"
msgstr ""
#. Tag: para
-#: Transactions.xml:47
+#: Transactions.xml:45
#, no-c-format
msgid ""
"The <interfacename>TransactionManager</interfacename> interface allows the "
@@ -124,7 +124,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:52
+#: Transactions.xml:50
#, no-c-format
msgid ""
"In JBossJTA, transaction manager implementations can be obtained from the "
@@ -133,7 +133,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:56
+#: Transactions.xml:54
#, no-c-format
msgid ""
"The Transaction Manager maintains the transaction context association with "
@@ -144,7 +144,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:59
+#: Transactions.xml:57
#, no-c-format
msgid ""
"Each transaction context is encapsulated by a Transaction object, which can "
@@ -153,7 +153,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:62
+#: Transactions.xml:60
#, no-c-format
msgid ""
"The <methodname>begin</methodname> method of "
@@ -164,7 +164,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:65
+#: Transactions.xml:63
#, no-c-format
msgid ""
"The <methodname>getTransaction</methodname> method returns the Transaction "
@@ -174,7 +174,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:68
+#: Transactions.xml:66
#, no-c-format
msgid ""
"The commit method is used to complete the transaction currently associated "
@@ -188,7 +188,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:71
+#: Transactions.xml:69
#, no-c-format
msgid ""
"The <methodname>rollback</methodname> method is used to rollback the "
@@ -198,7 +198,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:75
+#: Transactions.xml:73
#, no-c-format
msgid ""
"In a multi-threaded environment it is possible that multiple threads are "
@@ -211,13 +211,13 @@
msgstr ""
#. Tag: title
-#: Transactions.xml:80
+#: Transactions.xml:78
#, no-c-format
msgid "Suspending and resuming a transaction"
msgstr ""
#. Tag: para
-#: Transactions.xml:81
+#: Transactions.xml:79
#, no-c-format
msgid ""
"The JTA supports the concept of a thread temporarily suspending and resuming "
@@ -232,7 +232,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:85
+#: Transactions.xml:83
#, no-c-format
msgid ""
"The <methodname>resume</methodname> method associates the specified "
@@ -242,7 +242,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:89
+#: Transactions.xml:87
#, no-c-format
msgid ""
"If <methodname>resume</methodname> is invoked when the calling thread is "
@@ -251,7 +251,7 @@
msgstr ""
#. Tag: screen
-#: Transactions.xml:93
+#: Transactions.xml:91
#, no-c-format
msgid ""
"Transaction tobj = TransactionManager.suspend();\n"
@@ -260,7 +260,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:95
+#: Transactions.xml:93
#, no-c-format
msgid ""
"Some Transaction Manager implementations allow a suspended transaction to be "
@@ -269,7 +269,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:99
+#: Transactions.xml:97
#, no-c-format
msgid ""
"When a transaction is suspended the application server must ensure that the "
@@ -285,13 +285,13 @@
msgstr ""
#. Tag: title
-#: Transactions.xml:103
+#: Transactions.xml:101
#, no-c-format
msgid "The Transaction interface"
msgstr ""
#. Tag: para
-#: Transactions.xml:104
+#: Transactions.xml:102
#, no-c-format
msgid ""
"The <interfacename>Transaction</interfacename> interface allows operations "
@@ -302,31 +302,31 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:110
+#: Transactions.xml:108
#, no-c-format
msgid "Enlist the transactional resources in use by the application."
msgstr ""
#. Tag: para
-#: Transactions.xml:115
+#: Transactions.xml:113
#, no-c-format
msgid "Register for transaction synchronization call backs."
msgstr ""
#. Tag: para
-#: Transactions.xml:120
+#: Transactions.xml:118
#, no-c-format
msgid "Commit or rollback the transaction."
msgstr ""
#. Tag: para
-#: Transactions.xml:125
+#: Transactions.xml:123
#, no-c-format
msgid "Obtain the status of the transaction."
msgstr ""
#. Tag: para
-#: Transactions.xml:130
+#: Transactions.xml:128
#, no-c-format
msgid ""
"The <methodname>commit</methodname> and <methodname>rollback</methodname> "
@@ -338,13 +338,13 @@
msgstr ""
#. Tag: title
-#: Transactions.xml:134
+#: Transactions.xml:132
#, no-c-format
msgid "Resource enlistment"
msgstr ""
#. Tag: para
-#: Transactions.xml:135
+#: Transactions.xml:133
#, no-c-format
msgid ""
"Transactional resources such as database connections are typically managed "
@@ -359,7 +359,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:139
+#: Transactions.xml:137
#, no-c-format
msgid ""
"As stated previously, the JTA is much more closely integrated with the XA "
@@ -372,7 +372,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:142
+#: Transactions.xml:140
#, no-c-format
msgid ""
"The enlistment request results in the transaction manager informing the "
@@ -383,7 +383,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:145
+#: Transactions.xml:143
#, no-c-format
msgid ""
"The <methodname>delistResource</methodname> method is used to disassociate "
@@ -396,7 +396,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:148
+#: Transactions.xml:146
#, no-c-format
msgid ""
"The de-list request results in the transaction manager informing the "
@@ -409,13 +409,13 @@
msgstr ""
#. Tag: title
-#: Transactions.xml:152
+#: Transactions.xml:150
#, no-c-format
msgid "Transaction synchronization"
msgstr ""
#. Tag: para
-#: Transactions.xml:153
+#: Transactions.xml:151
#, no-c-format
msgid ""
"Transaction synchronization allows the application server to be notified "
@@ -425,7 +425,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:159
+#: Transactions.xml:157
#, no-c-format
msgid ""
"The <methodname>beforeCompletion</methodname> method is called prior to the "
@@ -437,7 +437,7 @@
msgstr ""
#. Tag: para
-#: Transactions.xml:164
+#: Transactions.xml:162
#, no-c-format
msgid ""
"The <methodname>afterCompletion</methodname> method is called after the "
@@ -446,13 +446,13 @@
msgstr ""
#. Tag: title
-#: Transactions.xml:170
+#: Transactions.xml:168
#, no-c-format
msgid "Transaction equality"
msgstr ""
#. Tag: para
-#: Transactions.xml:171
+#: Transactions.xml:169
#, no-c-format
msgid ""
"The transaction manager implements the Transaction object’s equals method to "
@@ -462,7 +462,7 @@
msgstr ""
#. Tag: screen
-#: Transactions.xml:175
+#: Transactions.xml:173
#, no-c-format
msgid ""
"Transaction txObj = TransactionManager.getTransaction();\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Using_JBossJTA_in_Application_Servers.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Using_JBossJTA_in_Application_Servers.pot 2008-09-23 06:25:23 UTC (rev 78768)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/Using_JBossJTA_in_Application_Servers.pot 2008-09-23 06:27:19 UTC (rev 78769)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,19 +21,19 @@
msgstr ""
#. Tag: title
-#: Using_JBossJTA_in_Application_Servers.xml:10
+#: Using_JBossJTA_in_Application_Servers.xml:8
#, no-c-format
msgid "JBoss Application Server"
msgstr ""
#. Tag: title
-#: Using_JBossJTA_in_Application_Servers.xml:12
+#: Using_JBossJTA_in_Application_Servers.xml:10
#, no-c-format
msgid "Service Configuration"
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:13
+#: Using_JBossJTA_in_Application_Servers.xml:11
#, no-c-format
msgid ""
"The JBoss Transaction Service is configured primarily via the XML files "
@@ -42,7 +42,7 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:19
+#: Using_JBossJTA_in_Application_Servers.xml:17
#, no-c-format
msgid ""
"TransactionTimeout – The default transaction timeout to be used for new "
@@ -50,7 +50,7 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:24
+#: Using_JBossJTA_in_Application_Servers.xml:22
#, no-c-format
msgid ""
"StatisticsEnabled – This determines whether or not the transaction service "
@@ -60,7 +60,7 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:29
+#: Using_JBossJTA_in_Application_Servers.xml:27
#, no-c-format
msgid ""
"PropagateFullContext – This determines whether a full transactional context "
@@ -70,7 +70,7 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:34
+#: Using_JBossJTA_in_Application_Servers.xml:32
#, no-c-format
msgid ""
"These attributes are specified as MBean attributes in the jboss-service.xml "
@@ -78,7 +78,7 @@
msgstr ""
#. Tag: screen
-#: Using_JBossJTA_in_Application_Servers.xml:37
+#: Using_JBossJTA_in_Application_Servers.xml:35
#, no-c-format
msgid ""
"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
@@ -91,7 +91,7 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:38
+#: Using_JBossJTA_in_Application_Servers.xml:36
#, no-c-format
msgid ""
"The transaction service is configurable also via the standard JBoss "
@@ -100,7 +100,7 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:41
+#: Using_JBossJTA_in_Application_Servers.xml:39
#, no-c-format
msgid ""
"These files can be edited manually or through JMX. Each property file is "
@@ -111,13 +111,13 @@
msgstr ""
#. Tag: title
-#: Using_JBossJTA_in_Application_Servers.xml:45
+#: Using_JBossJTA_in_Application_Servers.xml:43
#, no-c-format
msgid "Logging"
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:46
+#: Using_JBossJTA_in_Application_Servers.xml:44
#, no-c-format
msgid ""
"In order to make JBossTS logging semantically consistent with JBossAS, the "
@@ -133,13 +133,13 @@
msgstr ""
#. Tag: title
-#: Using_JBossJTA_in_Application_Servers.xml:51
+#: Using_JBossJTA_in_Application_Servers.xml:49
#, no-c-format
msgid "The services"
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:52
+#: Using_JBossJTA_in_Application_Servers.xml:50
#, no-c-format
msgid ""
"There is currently one service offered by the JBOSS integration called "
@@ -147,7 +147,7 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:56
+#: Using_JBossJTA_in_Application_Servers.xml:54
#, no-c-format
msgid ""
"The transaction manager service’s main purpose is to ensure the recovery "
@@ -158,13 +158,13 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:59
+#: 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:64
+#: Using_JBossJTA_in_Application_Servers.xml:62
#, no-c-format
msgid ""
"distributed: this uses the JTS enabled transaction manager implementation "
@@ -174,7 +174,7 @@
msgstr ""
#. Tag: para
-#: Using_JBossJTA_in_Application_Servers.xml:69
+#: Using_JBossJTA_in_Application_Servers.xml:67
#, no-c-format
msgid ""
"local: this uses the purely local JTA implementation. To configure this use "
@@ -183,13 +183,13 @@
msgstr ""
#. Tag: title
-#: Using_JBossJTA_in_Application_Servers.xml:75
+#: 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:76
+#: Using_JBossJTA_in_Application_Servers.xml:74
#, no-c-format
msgid ""
"It is possible to coordinate transactions from a coordinator which is not "
@@ -201,7 +201,7 @@
msgstr ""
#. Tag: screen
-#: Using_JBossJTA_in_Application_Servers.xml:80
+#: Using_JBossJTA_in_Application_Servers.xml:78
#, no-c-format
msgid ""
"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pot/messages.mo
===================================================================
(Binary files differ)
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/An_Introduction_to_the_JTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/An_Introduction_to_the_JTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/An_Introduction_to_the_JTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,111 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr ""
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Appendix.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"PO-Revision-Date: 2008-09-01 00:05+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Author_Group.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Book_Info.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,44 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Configuring_JBossJTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Configuring_JBossJTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Configuring_JBossJTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,135 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Examples.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Examples.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Examples.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,470 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr ""
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/JBoss_Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/JDBC_and_Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/JDBC_and_Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/JDBC_and_Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,750 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Preface.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Revision_History.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,26 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/The_Resource_Manager.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/The_Resource_Manager.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/The_Resource_Manager.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,662 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transaction_Recovery.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transaction_Recovery.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transaction_Recovery.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,329 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:8
+#, no-c-format
+msgid "Failure recovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:9
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:12
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:16
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:20
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:25
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:30
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:36
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:43
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:44
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:48
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:52
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:55
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:56
+#, 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:59
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:65
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:68
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:69
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:74
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:79
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:84
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:90
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:97
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:98
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:103
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:106
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:109
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:112
+#, 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,472 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr ""
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/pt-BR/Using_JBossJTA_in_Application_Servers.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,208 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr ""
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,111 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:6
+#, no-c-format
+msgid "An Introduction to the JTA"
+msgstr ""
+
+#. Tag: title
+#: An_Introduction_to_the_JTA.xml:8
+#, no-c-format
+msgid "The Java Transaction API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Appendix.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 00:05+0000\n"
+"PO-Revision-Date: 2008-09-01 00:05+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Author_Group.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Book_Info.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,44 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the Transactions JTA from the view of the programmer"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:21
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Configuring_JBossJTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Configuring_JBossJTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Configuring_JBossJTA.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,135 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Configuring_JBossJTA.xml:6
+#, no-c-format
+msgid "Configuring JBossJTA"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:33
+#, no-c-format
+msgid "YES/NO"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:40
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaTMImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:50
+#, no-c-format
+msgid "com.arjuna.ats.jta.jtaUTImplementation"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:60
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaBackoffPeriod"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:69
+#, no-c-format
+msgid "com.arjuna.ats.jdbc.isolationLevel"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:72
+#, no-c-format
+msgid "Any supported JDBC isolation level."
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:79
+#, no-c-format
+msgid "com.arjuna.ats.jta.xaTransactionTimetouEnabled"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:82
+#, no-c-format
+msgid "true/false"
+msgstr ""
+
+#. Tag: entry
+#: Configuring_JBossJTA.xml:85
+#, no-c-format
+msgid "Chapter 3"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Examples.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Examples.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Examples.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,470 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Examples.xml:6
+#, no-c-format
+msgid "Examples"
+msgstr ""
+
+#. Tag: title
+#: Examples.xml:8
+#, no-c-format
+msgid "JDBC example"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: Examples.xml:35
+#, no-c-format
+msgid "DB_x_DatabaseUser="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:40
+#, no-c-format
+msgid "DB_x_DatabasePassword="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:45
+#, no-c-format
+msgid "DB_x_DatabaseDynamicClass="
+msgstr ""
+
+#. Tag: para
+#: Examples.xml:50
+#, no-c-format
+msgid "Where x is the number of the connection information."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/JBoss_Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,750 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:6
+#, no-c-format
+msgid "JDBC and Transactions"
+msgstr ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:8
+#, no-c-format
+msgid "Using the transactional JDBC driver"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:17
+#, no-c-format
+msgid "Oracle 8.1.6/8.1.7, 9i and 10g thin driver."
+msgstr ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:22
+#, no-c-format
+msgid "MS SQL Server 2000 native driver."
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:37
+#, no-c-format
+msgid "Cloudscape 3.6 with Cloudscape’s own database."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:81
+#, no-c-format
+msgid "Class.forName(\"sun.jdbc.odbc.JdbcOdbcDriver\");"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:103
+#, no-c-format
+msgid "JDBC 2.0"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:131
+#, no-c-format
+msgid "XADataSources"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:140
+#, no-c-format
+msgid "Java Naming and Directory Interface (JNDI)"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:183
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.cloudscape_3_6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:188
+#, no-c-format
+msgid "Sequelink 5.1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:191
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.sequelink_5_1"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:196
+#, no-c-format
+msgid "Oracle 8.1.6"
+msgstr ""
+
+#. Tag: entry
+#: JDBC_and_Transactions.xml:199
+#, no-c-format
+msgid "com.arjuna.ats.internal.jdbc.drivers.oracle_8_1_6"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: para
+#: JDBC_and_Transactions.xml:222
+#, no-c-format
+msgid "JDBC does not support subtransactions."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: JDBC_and_Transactions.xml:251
+#, no-c-format
+msgid "jdbc:arjuna:sequelink://host:port;databaseName=foo;reuseconnection=true"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: JDBC_and_Transactions.xml:259
+#, no-c-format
+msgid "AutoCommit"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Preface.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Revision_History.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,26 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,662 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_Resource_Manager.xml:52
+#, no-c-format
+msgid "Extended XAResource control"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,329 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transaction_Recovery.xml:6
+#, no-c-format
+msgid "Transaction Recovery"
+msgstr ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:8
+#, no-c-format
+msgid "Failure recovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:9
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:12
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:16
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:20
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:25
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:30
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:36
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:43
+#, no-c-format
+msgid "Recovering XAConnections"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:44
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:48
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:52
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:55
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:56
+#, 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:59
+#, no-c-format
+msgid ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:61
+#, no-c-format
+msgid "These properties need to go into the JTA section of the property file."
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:65
+#, no-c-format
+msgid "Any errors will be reported during recovery."
+msgstr ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:68
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:69
+#, no-c-format
+msgid "Each method should return the following information:"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:74
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:79
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:84
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:90
+#, 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 ""
+
+#. Tag: title
+#: Transaction_Recovery.xml:97
+#, no-c-format
+msgid "Shipped XAResourceRecovery implementations"
+msgstr ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:98
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:103
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:106
+#, 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 ""
+
+#. Tag: para
+#: Transaction_Recovery.xml:109
+#, 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 ""
+
+#. Tag: screen
+#: Transaction_Recovery.xml:112
+#, 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,472 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions.xml:6
+#, no-c-format
+msgid "Transactions"
+msgstr ""
+
+#. Tag: title
+#: Transactions.xml:8
+#, no-c-format
+msgid "The API"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:18
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions.xml:44
+#, no-c-format
+msgid "TransactionManager"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Transactions.xml:91
+#, no-c-format
+msgid ""
+"Transaction tobj = TransactionManager.suspend();\n"
+" ..\n"
+"TransactionManager.resume(tobj);"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Transactions_JTA_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po 2008-09-23 06:27:19 UTC (rev 78769)
@@ -0,0 +1,208 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:25+0000\n"
+"PO-Revision-Date: 2008-09-23 06:25+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:6
+#, no-c-format
+msgid "Using JBossJTA in Application Servers"
+msgstr ""
+
+#. Tag: title
+#: Using_JBossJTA_in_Application_Servers.xml:8
+#, no-c-format
+msgid "JBoss Application Server"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: screen
+#: Using_JBossJTA_in_Application_Servers.xml:78
+#, no-c-format
+msgid ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+msgstr ""
More information about the jboss-cvs-commits
mailing list