[jboss-svn-commits] JBL Code SVN: r25676 - in labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide: de-DE and 5 other directories.

[jboss-svn-commits at lists.jboss.org]

Author: mospina
Date: 2009-03-16 22:41:09 -0400 (Mon, 16 Mar 2009)
New Revision: 25676

Added:
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Author_Group.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Book_Info.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Getting_Started.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Introduction.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Participants.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Preface.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Revision_History.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Stand-alone_Coordinator.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/The_XTS_API.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Transactional_Web_Services.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Author_Group.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Book_Info.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Getting_Started.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Introduction.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Participants.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Preface.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Revision_History.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Stand-alone_Coordinator.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/The_XTS_API.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Transactional_Web_Services.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Author_Group.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Book_Info.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Getting_Started.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Introduction.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Participants.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Preface.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Revision_History.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Stand-alone_Coordinator.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/The_XTS_API.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactional_Web_Services.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Author_Group.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Book_Info.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Getting_Started.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Introduction.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Participants.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Preface.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Revision_History.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Stand-alone_Coordinator.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/The_XTS_API.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactional_Web_Services.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactions_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Author_Group.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Book_Info.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Getting_Started.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Introduction.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Participants.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Preface.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Revision_History.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Stand-alone_Coordinator.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/The_XTS_API.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactional_Web_Services.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Author_Group.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Book_Info.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Getting_Started.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Introduction.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Participants.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Preface.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Revision_History.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Stand-alone_Coordinator.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/The_XTS_API.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactional_Web_Services.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Overview.po
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
Modified:
   labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/Makefile
Log:
PO files updated for OTHER_LANGS

Modified: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/Makefile
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/Makefile	2009-03-17 01:04:39 UTC (rev 25675)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/Makefile	2009-03-17 02:41:09 UTC (rev 25676)
@@ -5,6 +5,7 @@
 BRAND		= JBoss
 
 #OTHER_LANGS	= as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW
+OTHER_LANGS	= de-DE es-ES fr-FR ja-JP pt-BR zh-CN
 
 COMMON_CONFIG  = /usr/share/publican
 include $(COMMON_CONFIG)/make/Makefile.common

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Author_Group.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Author_Group.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Book_Info.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Book_Info.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,49 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide CP04"
+msgstr "JBoss Transactions Web Services Handbuch für Programmierer"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "Für den Gebrauch mit JBoss Enterprise Application Platform 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr ""
+"Dieses Handbuch behandelt die Programmierung für Transaction Web Services"
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Getting_Started.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Getting_Started.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Getting_Started.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,265 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Getting_Started.xml:6
+#, no-c-format
+msgid "Getting Started"
+msgstr "Erste Schritte"
+
+#. Tag: title
+#: Getting_Started.xml:8
+#, no-c-format
+msgid "Creating and deploying participants"
+msgstr "Erstellung und Einsatz von Teilnehmern"
+
+#. Tag: para
+#: Getting_Started.xml:9
+#, no-c-format
+msgid ""
+"A participant is a software entity which is driven by the transaction "
+"manager on behalf of a Web service. The creation of participants is non-"
+"trivial since they ultimately reflect the state of a Web service’s back-end "
+"processing facilities which is a function of an enterprise’s own IT "
+"infrastructure. The most that can be said about the implementation of a "
+"participant without getting into detail about the back-end systems it "
+"represents, or the details of the underlying transaction protocol is that "
+"implementations must implement one of the following interfaces, depending "
+"upon the protocol it will participate within: <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code>, or, <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+msgstr ""
+"Ein Teilnehmer ist eine Software-Entity, die vom Transaktionsmanager im "
+"Auftrag eines Web Services betrieben wird. Die Erstellung von Teilnehmern "
+"ist nicht trivial, denn letztendlich reflektieren sie den Zustand von "
+"Anlagen der Backend-Verarbeitung eines Web Services, was eine Funktion der "
+"unternehmenseigenen IT-Infrastruktur ist. Alles was über die Implementierung "
+"eines Teilnehmers gesagt werden kann (ohne ins Detail zu gehen über die von "
+"ihm repräsentierten Backend-Systeme oder über das zugrunde liegende "
+"Transaktionsprotokoll), ist, dass die Implementierungen eine der folgenden "
+"Schnittstellen implementieren muss, abhängig vom Protokoll, an dem es "
+"teilnehmen wird: <code>com.arjuna.wst.Durable2PCParticipant</code>, "
+"<code>com.arjuna.wst.Volatile2PCParticipant</code>, oder <code>com.arjuna."
+"wst.BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+
+#. Tag: title
+#: Getting_Started.xml:15
+#, no-c-format
+msgid "Creating Client Applications"
+msgstr "Erstellung von Client-Anwendungen"
+
+#. Tag: para
+#: Getting_Started.xml:16
+#, no-c-format
+msgid ""
+"There are two aspects to a client application using XTS. The first is the "
+"transaction declaration aspects and the second is the business logic that "
+"the client application performs. The transaction declaration aspects are "
+"taken care of automatically with XTS’s client API. This API provides simple "
+"transaction directives like begin, commit, and rollback which the client "
+"application can use to initialize, manage, and terminate transactions. Under "
+"the covers, this API invokes (via SOAP) operations on the transaction "
+"manager."
+msgstr ""
+"Es gibt zwei Aspekte einer XTS-verwendenden Client-Anwendung. Der erste ist "
+"der Aspekt der Transaktionsdeklaration, der zweite ist die Business-Logik, "
+"welche die Client-Anwendung ausführt. Der Aspekt der Transaktionsdeklaration "
+"wird automatisch erledigt mittels der Client-API von XTS. Diese API bietet "
+"einfache Transaktionsdirektiven wie \"begin\", \"commit\" und \"rollback\", "
+"welche die Client-Anwendung nutzen kann zum Initialisieren, Verwalten und "
+"Beenden von Transaktionen. Im Hintergrund ruft die API (via SOAP) "
+"Operationen auf im Transaktionsmanager."
+
+#. Tag: para
+#: Getting_Started.xml:19
+#, no-c-format
+msgid ""
+"When the client application performs invocations on business logic Web "
+"services, then XTS does not dictate an API for that purpose. However, there "
+"is a requirement that whatever API is chosen, the XTS context be inserted "
+"onto outgoing messages, and extracted and associated with the current thread "
+"for incoming messages. To make the user’s life easier, the XTS software "
+"comes complete with three sets of “filters” which can perform the task "
+"automatically. These filters are designed to work with JAX-RPC and "
+"webMethods client libraries."
+msgstr ""
+"Wenn die Client-Anwendung Aufrufe auf die Business-Logik Web Services "
+"tätigt, dann schreibt XTS keine API für diesen Zweck vor. Es gibt jedoch die "
+"Anforderung - egal welche API gewählt wird - dass der XTS-Kontext in "
+"ausgehende Nachrichten eingefügt wird, sowie extrahiert und mit dem Thread "
+"verknüpft wird für eingehende Nachrichten. Als Vereinfachung für den "
+"Benutzer ist die XTS-Software komplett mit drei \"Filtern\" ausgestattet, "
+"welche diese Aufgabe automatisiert ausführen. Diese Filter sind dafür "
+"entworfen, mit JAX-RPC und webMehods Client-Bibliotheken zu arbeiten."
+
+#. Tag: para
+#: Getting_Started.xml:23
+#, no-c-format
+msgid ""
+"If the user chooses to use a different SOAP client infrastructure, then the "
+"onus to perform client-side header processing rests with them. XTS does not "
+"provide client-side infrastructure for anything other than JAX-RPC or "
+"webMethods for this release."
+msgstr ""
+"Falls der Benutzer sich dazu entschließt, eine andere SOAP-Client-"
+"Infrastruktur zu verwenden, dann liegt die Verpflichtung, client-seitige "
+"Header-Verarbeitung auszuführen, bei ihm. XTS bietet in dieser Release keine "
+"client-seitige Infrastruktur außer für JAX-RPC oder webMethods."
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr "JAX-RPC Kontext-Handler"
+
+#. Tag: para
+#: Getting_Started.xml:29
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC server-side context handler with the "
+"deployed web services, a handler chain must be included in the web services "
+"deployment descriptor. Please refer to the demo application <filename>jboss/"
+"webservices.xml</filename> deployment descriptor for an example of how this "
+"can be achieved."
+msgstr ""
+"Um den JAX-RPC server-seitigen Kontext-Handler bei den eingesetzten Web "
+"Services anzumelden, muss eine Handler Chain in den Deployment-Deskriptor "
+"des Web Services eingefügt werden. Bitte werfen Sie einen Blick auf den "
+"Deployment-Deskriptor der Demo-Anwendung <filename>jboss/webservices.xml</"
+"filename> für ein Beispiel zur Durchführung."
+
+#. Tag: para
+#: Getting_Started.xml:33
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC client-side context handler used by the "
+"client applications, a handler chain must be included in the definition of "
+"the service-ref in the client web.xml deployment descriptor. Please refer to "
+"the demo application <filename>jboss/client-web-app.xml</filename> for an "
+"example of how this can be achieved."
+msgstr ""
+"Um den JAX-RPC client-seitigen Kontext-Handler anzumelden, der von den "
+"Client-Anwendungen verwendet wird, muss eine Handler Chain in die Definition "
+"des service-ref im web.xml Deployment-Deskriptor des Clients eingefügt "
+"werden. Bitte werfen Sie einen Blick auf die Demo-Anwendung <filename>jboss/"
+"webservices.xml</filename> für ein Beispiel zur Durchführung."
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr "webMethods Kontext-Handler"
+
+#. Tag: para
+#: Getting_Started.xml:38
+#, no-c-format
+msgid ""
+"In order to register the webMethods server-side context handler with the "
+"deployed web services, the inbound and outbound interceptors must be "
+"configured in the web services deployment descriptor. An example of how this "
+"can be configured can be found in the demo application, for example, the "
+"<filename>RestaurantServiceAT.xml</filename>."
+msgstr ""
+"Um den webMethods server-seitigen Kontext-Handler bei den eingesetzten Web "
+"Services anzumelden, müssen die Inbound- und Outbound-Interzeptoren im "
+"Deployment-Deskriptor des Web Services konfiguriert werden. Ein Beispiel zur "
+"möglichen Konfigurierung ist in der Demo-Anwendung zu finden, z. B. in der "
+"<filename>RestaurantServiceAT.xml</filename>."
+
+#. Tag: para
+#: Getting_Started.xml:42
+#, no-c-format
+msgid ""
+"In order to register the webMethods client-side context handler, the inbound "
+"and outbound interceptors must be configured in the <filename>glue-config."
+"xml</filename> deployment descriptor. Please refer to the soap interceptor "
+"section of the demo application glue-config.xml for an example of how this "
+"can be achieved."
+msgstr ""
+"Um den webMethods client-seitigen Kontext-Handler anzumelden, müssen die "
+"Inbound- und Outbound-Interzeptoren im <filename>glue-config.xml</filename> "
+"Deployment-Deskriptor konfiguriert werden. Werfen Sie bitte einen Blick auf "
+"den Abschnitt zum SOAP-Interzeptor in der Demo-Anwendung application glue-"
+"config.xml für ein Beispiel zur Durchführung."
+
+#. Tag: title
+#: Getting_Started.xml:48
+#, no-c-format
+msgid "Hints and tips"
+msgstr "Tipps und Tricks"
+
+#. Tag: para
+#: Getting_Started.xml:49
+#, no-c-format
+msgid ""
+"If you want to create multiple JBoss deploys on the same machine, then you "
+"may wish to look at <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/"
+"MultipleInstances.htm\"><emphasis>Setting up multiple instances</emphasis></"
+"ulink> for information on what is required."
+msgstr ""
+"Falls Sie mehrere JBoss-Deploys auf derselben Maschine erstellen möchten, "
+"sollten Sie unter <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/"
+"MultipleInstances.htm\"><emphasis>Setting up multiple instances</emphasis></"
+"ulink> nachlesen, was dafür erforderlich ist."
+
+#. Tag: title
+#: Getting_Started.xml:55
+#, no-c-format
+msgid "Summary"
+msgstr "Zusammenfassung"
+
+#. Tag: para
+#: Getting_Started.xml:56
+#, no-c-format
+msgid ""
+"This chapter has provided a high-level overview of how to use each of the "
+"major software pieces of the Web Services transactions component of JBossTS. "
+"The Web Services transaction manager provided by JBossTS is the hub of the "
+"architecture and is the only piece of software that users’ software does not "
+"bind to directly. XTS provides header processing infrastructure for dealing "
+"with Web Services transactions contexts for both users’ client applications "
+"and Web services. For developing transaction participants, XTS provides a "
+"simple interface plus the necessary document handling code."
+msgstr ""
+"Dieses Kapitel gab einen sehr guten Überblick darüber, wie die wichtigsten "
+"Softwarebestandteile der Web Services Transaktionskomponente von JBossTS "
+"anzuwenden sind. Der von JBossTS bereitgestellte Web Services "
+"Transaktionsmanager ist das Kernstück der Architektur und die einzige "
+"Software, an den die Software des Benutzers nicht direkt angebunden wird. "
+"XTS bietet die Infrastruktur für die Header-Verarbeitung beim Arbeiten mit "
+"Web Services Transaktionskontexten, sowohl für Client-Anwendungen des "
+"Benutzers, als auch für Web Services. Zum Entwickeln von "
+"Transaktionsteilnehmern bietet XTS eine simple Schnittstelle mitsamt "
+"notwendigem Document Handling Code."
+
+#. Tag: para
+#: Getting_Started.xml:59
+#, no-c-format
+msgid ""
+"This chapter is meant as an overview only, and is unlikely to answer "
+"questions on more difficult and subtle aspects. For fuller explanations of "
+"the components, please refer to the appropriate chapter elsewhere in this "
+"document."
+msgstr ""
+"Dieses Kapitel ist nur als Überblick gemeint und beantwortet wahrscheinlich "
+"keine Fragen zu schwierigeren und subtileren Aspekten. Für umfassendere "
+"Erklärung der Komponenten lesen Sie bitte das entsprechende Kapitel an "
+"anderer Stelle dieses Dokuments."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Introduction.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Introduction.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Introduction.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,411 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr "Einführung"
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr "JBossTS Web Services Transaktionen im Überblick"
+
+#. Tag: para
+#: Introduction.xml:9
+#, no-c-format
+msgid ""
+"The XML transaction service component of JBossTS (shorthand referred to as "
+"XTS) supports the coordination of private and public Web services in a "
+"business transaction. Therefore, to understand XTS, you must be familiar "
+"with Web services, and also understand a little about transactions. This "
+"chapter introduces XTS and provides a brief overview of the technologies "
+"that form the Web services standard. Additionally, this chapter explores "
+"some of the fundamentals of transactioning technology and how it can be "
+"applied to Web services. Much of the content presented in this chapter is "
+"detailed throughout this guide; however, only overview information about Web "
+"services is provided. If you are new to creating Web services, please see "
+"consult your Web services platform documentation."
+msgstr ""
+"Die XML-Transaktionsdienstkomponente von JBossTS (kurz XTS) unterstützt die "
+"Koordination privater und öffentlicher Web Services in einer geschäftlichen "
+"Transaktion. Um XTS zu verstehen, müssen Sie daher vertraut sein mit Web "
+"Services sowie etwas Verständnis von Transaktionen mitbringen. Dieses "
+"Kapitel stellt XTS vor und gewährt einen kurzen Überblick über die "
+"Technologien, die den Web Services Standard formen. Zusätzlich untersucht "
+"dieses Kapitel einige Grundlagen der Transaktionstechnologie und deren "
+"Anwendung auf Web Services. Viele der hier vorgestellten Inhalte werden "
+"später im Handbuch noch vertieft, Informationen über Web Services sind "
+"jedoch nur als Überblick enthalten. Wenn Ihnen das Erstellen von Web "
+"Services noch neu ist, konsultieren Sie bitte die Dokumentation Ihrer Web "
+"Services Plattform."
+
+#. Tag: para
+#: Introduction.xml:12
+#, no-c-format
+msgid ""
+"JBossTS provides as the XTS component a transaction solution for Web "
+"services. Using XTS, business partners can coordinate complex business "
+"transactions in a controlled and reliable manner. The JBossTS Web Services "
+"API supports a transactional coordination model based on the WS-C, WS-Atomic "
+"Transaction and WS-Business Activity specifications. WS-C is a generic "
+"coordination framework developed by IBM, Microsoft and BEA, WS-Atomic "
+"Transaction and WS-Business Activity are transaction protocols that utilize "
+"this framework."
+msgstr ""
+"JBossTS bietet mit der XTS-Komponente eine Transaktionslösung für Web "
+"Services. Mittels XTS können Geschäftspartner komplexe "
+"Geschäftstransaktionen auf kontrollierte und zuverlässe Weise koordinieren. "
+"Die JBossTS Web Services API unterstützt ein Modell zur transaktionalen "
+"Koordination basierend auf den Spezifikationen von WS-C, WS-Atomic "
+"Transaction und WS-Business Activity. WS-C ist ein von IBM, Microsoft und "
+"BEA entwickeltes generisches Framework; WS-Atomic Transaction und WS-"
+"Business Activity sind Transaktionsprotokolle, die dieses Framwork nutzen."
+
+#. Tag: para
+#: Introduction.xml:15
+#, no-c-format
+msgid ""
+"Web services are modular, reusable software components that are created by "
+"exposing business functionality through a Web service interface. Web "
+"services communicate directly with other Web services using standards-based "
+"technologies such as SOAP and HTTP. These standards-based communication "
+"technologies allow Web services to be accessed by customers, suppliers, and "
+"trading partners, independent of hardware operation system or programming "
+"environment. The result is a vastly improved collaboration environment as "
+"compared to today&#39;s EDI and business-to-business (B2B) solutions—an "
+"environment where businesses can expose their current and future business "
+"applications as Web services that can be easily discovered and accessed by "
+"external partners."
+msgstr ""
+"Web Services sind modulare, wiederverwendbare Softwarekomponenten, die "
+"kreirt werden, indem Geschäftsfunktionalität mittels einer Web Service "
+"Schnittstelle offengelegt wird. Web Services kommunizieren direkt mit "
+"anderen Web Services mithilfe standardisierter Technologien wie SOAP und "
+"HTTP. Diese standardisierten Kommunikationstechnologien ermöglichen einen "
+"Zugriff auf Web Services durch Kunden, Zulieferer und Handelspartner, "
+"unabhängig von Hardware, Betriebssystem oder der Programmierungsumgebung. "
+"Das Ergebnis ist eine sehr viel bessere Umgebung zur Zusammenarbeit im "
+"Vergleich zu heutigen EDI und Business-To-Business (B2B) -Lösungen – eine "
+"Umgebung, in der Unternehmen ihre aktuellen und zukünftigen "
+"Geschäftsanwendungen als Web Services offengelegen können, die von externen "
+"Partnern einfach gefunden und genutzt werden können."
+
+#. Tag: para
+#: Introduction.xml:18
+#, no-c-format
+msgid ""
+"Web services, by themselves, are not fault tolerant. In fact, some of the "
+"reasons that make it an attractive development solution are also the same "
+"reasons that service-based applications may have drawbacks:"
+msgstr ""
+"Web Services selbst sind nicht fehlertolerant. Tatsächlich sind einige der "
+"Gründe, die sie zu attraktiven Entwicklungslösungen machen auch jene Gründe, "
+"die in Service-basierten Anwendungen zu Nachteilen führen:"
+
+#. Tag: para
+#: Introduction.xml:23
+#, no-c-format
+msgid ""
+"Application components that are exposed as Web services may be owned by "
+"third parties, which provides benefits in terms of cost of maintenance, but "
+"drawbacks in terms of having exclusive control over their behavior;"
+msgstr ""
+"Anwendungskomponenten, die als Web Services offengelegt sind, gehören evtl. "
+"Drittanbietern, was zwar einen Vorteil bringt bezüglich der Wartungskosten, "
+"allerdings einen Nachteil hat in Bezug auf exklusive Kontrolle über deren "
+"Verhaltensweisen;"
+
+#. Tag: para
+#: Introduction.xml:28
+#, no-c-format
+msgid ""
+"Web services are usually remotely located which increases risk of failure "
+"due to increased network travel for invocations."
+msgstr ""
+"Web Services sind normalerweise entfernt gelegen, was das Fehlerrisiko "
+"aufgrund längerer Netzübertragungszeiten der Aufrufe erhöht."
+
+#. Tag: para
+#: Introduction.xml:33
+#, no-c-format
+msgid ""
+"Applications that have high dependability requirements, must find a method "
+"of minimizing the effects of errors that may occur when an application "
+"consumes Web services. One method of safeguarding against such failures is "
+"to interact with an application’s Web services within the context of a "
+"transaction. A transaction is simply a unit of work which is completed "
+"entirely, or in the case of failures is reversed to some agreed consistent "
+"state – normally to appear as if the work had never occurred in the first "
+"place. With XTS, transactions can span multiple Web services which mean that "
+"work performed across multiple enterprises can be managed with transactional "
+"support."
+msgstr ""
+"Anwendungen, die hohe Zuverlässigkeit erfordern, müssen einen Weg finden zur "
+"Minimierung der Fehlerfolgen, die beim Konsumieren von Web Services durch "
+"Anwendungen auftreten können. Eine Methode zum Schutz vor solchen Fehlern "
+"ist, mit den Web Services einer Anwendung im Kontext einer Transaktion zu "
+"interagieren. Eine Transaktion ist einfach ausgedrückt eine Einheit von "
+"Arbeit, welche entweder vollständig ausgeführt wird, oder im Fehlerfall "
+"zurückgesetzt wird auf einen festgelegten, konsistenten Zustand – in der "
+"Regel so, als ob die Arbeit nie stattgefunden hätte. Mit XTS können "
+"Transaktionen mehrere Web Services umspannen, das heißt, dass über mehrere "
+"Unternehmen hinweg ausgeführte Arbeit mit transaktionaler Unterstützung "
+"gesteuert werden kann."
+
+#. Tag: title
+#: Introduction.xml:37
+#, no-c-format
+msgid "Managing Service-Based Processes"
+msgstr "Steuerung Service-basierter Prozesse"
+
+#. Tag: para
+#: Introduction.xml:38
+#, no-c-format
+msgid ""
+"XTS allows you to create transactions that drive complex business processes "
+"spanning multiple Web services. Current Web services standards do not "
+"address the requirements for a high-level coordination of services since in "
+"today’s Web services applications, which use single request/receive "
+"interactions, coordination is typically not a problem. However, for "
+"applications that engage multiple services among multiple business partners, "
+"coordinating and controlling the resulting interactions is essential. This "
+"becomes even more apparent when you realize that you generally have little "
+"in the way of formal guarantees when interacting with third-party Web "
+"services."
+msgstr ""
+"XTS ermöglicht Ihnen die Erstellung von Transaktionen, die komplexe "
+"Geschäftsprozesse über mehrere Web Services betreiben. Derzeitige Standards "
+"für Web Services gehen nicht auf die Anforderungen für eine hohe "
+"Koordination der Services ein, denn in heutigen Web Services Anwendungen, "
+"die einzelne Anfrage/Antwort-Interaktionen nutzen, ist Koordination "
+"normalerweise kein Problem. Für Anwendungen, welche verschiedene Services "
+"mehrerer Geschäftspartner einbinden, ist die Koordination und Kontrolle der "
+"daraus resultierenden Interaktionen jedoch entscheidend. Dies wird umso "
+"deutlicher, wenn Sie sich darüber bewusst werden, dass Sie über wenig "
+"formale Garantien verfügen im Umgang mit Web Services von Drittanbietern."
+
+#. Tag: para
+#: Introduction.xml:42
+#, no-c-format
+msgid ""
+"XTS provides the infrastructure for coordinating services during a business "
+"process. By organizing processes as transactions, business partners can "
+"collaborate on complex business interactions in a reliable manner, insuring "
+"the integrity of their data - usually represented by multiple changes to a "
+"database – but without the usual overheads and drawbacks of directly "
+"exposing traditional transaction-processing engines directly onto the web. "
+"The following example demonstrates how an application may manage service-"
+"based processes as transactions:"
+msgstr ""
+"XTS stellt die Infrastruktur zur Koordination von Services während eines "
+"Geschäftsprozesses bereit. Indem Prozesse als Transaktionen organisiert "
+"werden, können Geschäftspartner in komplexen Geschäftsbeziehungen auf "
+"zuverlässige Weise zusammenarbeiten. Dabei sichern sie die Integrität ihrer "
+"Daten – gewöhnlich repräsentiert durch multiple Änderungen in einer "
+"Datenbank – ohne den Overhead und die Nachteile, die es mit sich bringen "
+"würde, wenn sie traditionelle transaktionsverarbeitende Engines im Web "
+"offenlegten. Das folgende Beispiel veranschaulicht, wie eine Anwendung "
+"Service-basierte Prozesse als Transaktionen steuern kann:"
+
+#. Tag: para
+#: Introduction.xml:45
+#, no-c-format
+msgid ""
+"The application in question allows a user to plan a social evening. This "
+"application is responsible for reserving a table at a restaurant, and "
+"reserving tickets to a show. Both activities are paid for using a credit "
+"card. In this example, each service represents exposed Web services provided "
+"by different service providers. XTS is used to envelop the interactions "
+"between the theater and restaurant services into a single (potentially) long-"
+"running business transaction. The business transaction must insure that "
+"seats are reserved both at the restaurant and the theater. If one event "
+"fails the user has the ability to decline both events, thus returning both "
+"services back to their original state. If both events are successful, the "
+"user’s credit card is charged and both seats are booked. As you may expect, "
+"the interaction between the services must be controlled in a reliable manner "
+"over a period of time. In addition, management must span several third-party "
+"services that are remotely deployed."
+msgstr ""
+"Die fragliche Anwendung ermöglicht einem Benutzer die Planung eines "
+"geselligen Abends. Die Anwendung ist verantwortlich für die Reservierung "
+"eines Tischs in einem Restaurant und für die Reservierung von "
+"Eintrittskarten zu einer Aufführung. Beides wird mit einer Kreditkarte "
+"bezahlt. In diesem Beispiel repräsentiert jeder Service einen offengelegten "
+"Web Service von jeweils verschiedenen Anbietern. XTS wird dazu benutzt, die "
+"Interaktionen zwischen dem Theater- und dem Restaurant-Service in eine "
+"einzige, (möglicherweise) langlaufende Geschäftstransaktion "
+"zusammenzufassen. Die Geschäftstransaktion muss sicherstellen, dass sowohl "
+"Plätze im Restaurant als auch im Theater reserviert werden. Falls eine der "
+"beiden Vorgänge fehlschlägt, hat der Benutzer die Möglichkeit, beide "
+"Unternehmungen abzulehnen und somit beide Services auf ihren ursprünglichen "
+"Zustand zurückzusetzen. Falls beide Vorgänge erfolgreich sind, wird die "
+"Kreditkarte des Benutzers belastet und beide Plätze gebucht. Wie Sie sich "
+"sicher denken können, müssen die Interaktionen zwischen den Services auf "
+"zuverlässige Weise über bestimmte Zeit hinweg gesteuert werden. Zusätztlich "
+"muss die Steuerung auch Services von Drittanbietern umfassen, welche "
+"entfernt eingesetzt werden."
+
+#. Tag: para
+#: Introduction.xml:49
+#, no-c-format
+msgid ""
+"Without the backing of a transaction, an undesirable outcome may occur. For "
+"example, the user credit card may be charged, even though one or both of the "
+"bookings may have failed."
+msgstr ""
+"Ohne Hilfestellung durch eine Transaktion können unerwünschte Ergebnisse die "
+"Folge sein, z. B. kann die Kreditkarte des Benutzers belastet werden, obwohl "
+"eine oder beide Buchungen fehlschlugen."
+
+#. Tag: para
+#: Introduction.xml:53
+#, no-c-format
+msgid ""
+"This simple example describes the situations where XTS excels at supporting "
+"business processes across multiple enterprises. This example is further "
+"refined throughout this guide, and appears as a standard demonstrator "
+"(including source code) with the XTS distribution."
+msgstr ""
+"Dieses einfache Beispiel beschreibt die Situtationen, in denen XTS "
+"hervorragend eingesetzt werden kann zur Unterstützung von Geschäftsprozessen "
+"über mehrere Unternehmen hinweg. Dies Beispiel wird im Laufe dieses "
+"Handbuchs noch weiter verfeinert, und erscheint als Standard-Demo (inklusive "
+"Quellcode) in der XTS-Distribution."
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr "Servlets"
+
+#. Tag: para
+#: Introduction.xml:58
+#, no-c-format
+msgid ""
+"The WS-C, WS-Atomic Transaction and WS-Business Activity protocols are based "
+"on one-way interactions of entities rather than traditional synchronous "
+"request/response RPC style interactions. Entities (for example, transaction "
+"participants) invoke operations on other entities (for example, the "
+"transaction coordinator) in order to return responses to requests. What this "
+"means is that the programming model is based on peer-to-peer relationships, "
+"with the result that all services, whether they are participants, "
+"coordinators or clients, must have an active component that allows them to "
+"receive unsolicited messages."
+msgstr ""
+"Die WS-C, WS-Atomic Transaction und WS-Business Activity Protokolle basieren "
+"auf einseitigen Interaktionen von Entitys, nicht auf traditionellen, "
+"synchronen Anfrage/Antwort-RPC-Interaktionen. Entitys (z. B. "
+"Transaktionsteilnehmer) rufen Operationen auf anderen Entitys (z. B. des "
+"Transaktionskoordinators) auf, um Antworten auf Anfragen zurückzugeben. Das "
+"bedeutet, dass das Programmierungsmodell auf Peer-to-Peer Beziehungen "
+"basiert, weshalb alle Services, ob Teilnehmer, Koordinatoren oder Clients, "
+"eine aktive Komponente besitzen müssen, die ihnen dem Empfang von "
+"unaufgeforderten Nachrichten erlaubt."
+
+#. Tag: para
+#: Introduction.xml:62
+#, no-c-format
+msgid ""
+"In the current implementation of XTS, the active component is achieved "
+"through the use of Java servlet technology. Each endpoint that can be "
+"communicated with via SOAP/XML is represented as a servlet (and published "
+"within JNDI). Fortunately for the developer, this use of servlets occurs "
+"transparently. The only drawback is that (currently) clients must reside "
+"within a domain capable of hosting servlets, i.e., an application server. It "
+"is our intention that future versions of XTS will provide configurable "
+"deployment options, allowing servlets where required, but not mandating them."
+msgstr ""
+"In der aktuellen Implementierung von XTS wird die aktive Komponente durch "
+"die Nutzung von Java-Servlet-Technologie erreicht. Jeder Endpunkt, mit dem "
+"via SOAP/XML kommuniziert werden kann, wird durch ein Servlet repräsentiert "
+"(und veröffentlicht in JNDI). Zum Glück für den Entwickler erfolgt dieser "
+"Gebrauch von Servlets transparent. Der einzige Nachteil ist, dass Clients "
+"(derzeit) innerhalb einer Domain liegen müssen, die fähig ist, Servlets zu "
+"hosten, z. B. ein Anwendungsserver. Wir beabsichtigen, zukünftige Versionen "
+"von XTS mit konfigurierbaren Deployment-Optionen auszustatten, somit "
+"Servlets wo nötig zu ermöglichen, aber nicht vorzuschreiben."
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr "SOAP"
+
+#. Tag: para
+#: Introduction.xml:67
+#, no-c-format
+msgid ""
+"SOAP has emerged as the de-facto message format for XML-based communication "
+"in the Web services arena. It is a lightweight protocol that allows the user "
+"to define the content of a message and to provide hints as to how recipients "
+"should process that message."
+msgstr ""
+"SOAP hat sich als das de-facto Nachrichtenformat für XML-basierte "
+"Kommunikation in der Web Services Arena herausgebildet. Es ist ein schlankes "
+"Protokoll, das es dem Benutzer ermöglicht, den Inhalt einer Nachricht zu "
+"definieren und Hinweise darauf zu geben, wie Empfänger die Nachricht "
+"verarbeiten sollten."
+
+#. Tag: para
+#: Introduction.xml:71
+#, no-c-format
+msgid ""
+"SOAP messages can be divided into two main categories: Remote Procedure Call "
+"(RPC) and Document Exchange (DE). The primary difference between the two "
+"categories is that the SOAP specification defines encoding rules and "
+"conventions for RPC. The document exchange model allows the exchange of "
+"arbitrary XML documents - a key ingredient of B2B document exchange. XTS is "
+"based on the loosely coupled document-exchange style, yet it can support "
+"transactions spanning Web service that use either document-exchange or RPC."
+msgstr ""
+"SOAP-Nachrichten können in zwei Hauptkategorien unterteilt werden: Remote "
+"Procedure Call (RPC) und Document Exchange (DE). Der grundlegende "
+"Unterschied dieser zwei Kategorien ist der, dass die SOAP-Spezifikationen "
+"Encoding-Regeln und Konventionen für RPC definieren. Das Document Exchange "
+"Modell erlaubt den Austausch beliebiger XML-Dokumente – ein Schlüssel-"
+"Element von B2B-Dokumentenaustausch. XTS basiert auf dem lose gekoppelten "
+"Document Exchange Typ, kann aber Transaktionen unterstützen, welche Web "
+"Services umfassen, die Document Exchange oder RPC verwenden."
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr "Web Services Description Language (WSDL)"
+
+#. Tag: para
+#: Introduction.xml:76
+#, no-c-format
+msgid ""
+"WSDL is an XML-based language used to define Web service interfaces. An "
+"application that consumes a Web service parses the service’s WSDL document "
+"to discover the location of the service, the operations that the service "
+"supports, the protocol bindings the service supports (SOAP, HTTP, etc), and "
+"how to access them (for each operation, WSDL describes the format that the "
+"client must follow)."
+msgstr ""
+"WSDL ist eine XML-basierte Sprache, die zum Definieren von Web Services "
+"Schnittstellen genutzt wird. Eine Anwendung, die einen Web Service "
+"konsumiert, analysiert das WSDL-Dokument des Services, um Informationen "
+"herauszufinden über die Adresse des Services, die vom Service unterstützten "
+"Operationen und Protokollbindungen (SOAP, HTTP etc.), sowie darüber, wie auf "
+"sie zugegriffen werden kann (für jede Operation beschreibt WSDL das Format, "
+"dem der Client folgen muss)."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
===================================================================

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Participants.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Participants.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Participants.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,634 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Participants.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "Test"
+
+#. Tag: para
+#: Participants.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "Dies ist ein Testabsatz"
+
+#. Tag: title
+#: Participants.xml:11
+#, no-c-format
+msgid "The Participant: an Overview"
+msgstr "Der Teilnehmer: Ein Überblick"
+
+#. Tag: para
+#: Participants.xml:12
+#, no-c-format
+msgid ""
+"The participant is the entity that performs the work pertaining to "
+"transaction management on behalf of the business services involved in an "
+"application. The Web service (for example, a theatre booking system) "
+"contains some business logic for reserving a seat, enquiring availability "
+"etc, but it will need to be supported by something that maintains "
+"information in a durable manner. Typically this will be a database, but it "
+"could be a file system, NVRAM, etc. Now, although the service may talk to "
+"the back-end database directly, it cannot commit or undo any changes it (the "
+"services) makes, since these are ultimately under the control of the "
+"transaction that scoped the work. In order for the transaction to be able to "
+"exercise this control, it must have some contact with the database. In XTS "
+"this is accomplished by the participant, and the role played by the "
+"participant between the transaction and back-end transaction processing "
+"infrastructure is shown in the following figure."
+msgstr ""
+"Der Teilnehmer ist eine Entity, die (das Transaktionsmanagement betreffende) "
+"Arbeiten ausführt, im Auftrag eines an einer Anwendung beteiligten Geschäfts-"
+"Services. Der Web Service (z. B. ein Buchungssystem eines Theaters) enthält "
+"zwar Business-Logik für Sitzplatzreservierung, Verfügbarkeitsanfragen etc., "
+"muss aber unterstützt werden durch etwas, was Informationen dauerhaft "
+"speichert. In der Regel ist dies eine Datenbank, aber es könnte auch ein "
+"Dateisystem, NVRAM, usw. sein. Obwohl der Service direkt mit der Backend-"
+"Datenbank kommunizieren kann, kann der Service jedoch keine Änderungen "
+"festschreiben oder zurücksetzen, denn diese obliegen letztlich der Kontrolle "
+"der betreffenden Transaktion. Damit die Transaktion diese Kontrolle ausüben "
+"kann, muss sie gewissen Kontakt zur Datenbank haben. In XTS wird dies durch "
+"den Teilnehmer erreicht; die Rolle, die dieser Teilnehmer spielt zwischen "
+"der Transaktion und der Infrastruktur zur Transaktionsverarbeitung im "
+"Backend, wird in der folgenden Abbildung veranschaulicht."
+
+#. Tag: caption
+#: Participants.xml:19
+#, no-c-format
+msgid "Transactions, Participants, and Back-End Transaction Control"
+msgstr "Transaktionen, Teilnehmer, und Transaktionskontrolle im Backend"
+
+#. Tag: para
+#: Participants.xml:21
+#, no-c-format
+msgid ""
+"Each participant in XTS is related to either the Atomic Transaction or "
+"Business Activity protocols. In the following sections we’ll consider both "
+"protocols and their respective participants."
+msgstr ""
+"Jeder Teilnehmer in XTS ist verbunden entweder mit dem Atomic Transaction "
+"oder dem Business Activity Protokoll. Der folgende Abschnitt beschäftigt "
+"sich mit den beiden Protokollen und ihren jeweiligen Teilnehmern."
+
+#. Tag: title
+#: Participants.xml:25
+#, no-c-format
+msgid "Atomic Transaction"
+msgstr "Atomic Transaction"
+
+#. Tag: para
+#: Participants.xml:26
+#, no-c-format
+msgid ""
+"All Atomic Transaction participants are instances of one of the following "
+"interfaces."
+msgstr ""
+"Alle Atomic Transaction Teilnehmer sind Instanzen einer der folgenden "
+"Schnittstellen."
+
+#. Tag: title
+#: Participants.xml:31
+#, no-c-format
+msgid "Durable2PCParticipant"
+msgstr "Durable2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:32
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Durable2PC protocol with "
+"the following signatures, as per the <interfacename>com.arjuna.wst."
+"Durable2Participant</interfacename> interface:"
+msgstr ""
+"Dieser Teilnehmer unterstützt das WS-Atomic Transaction Durable2PC-Protokoll "
+"mit den folgenden Signaturen, gemäß der <interfacename>com.arjuna.wst."
+"Durable2Participant</interfacename>-Schnittstelle."
+
+#. Tag: para
+#: Participants.xml:38
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the <code>com.arjuna.wst."
+"Vote</code>. Values are: <code>ReadOnly</code>, indicating the participant "
+"does not need to be informed of the transaction outcome as no state updates "
+"were made; Prepared, indicating the participant is prepared to commit or "
+"rollback depending on the final transaction outcome, and it has made "
+"sufficient state updates persistent to accomplish this; and Aborted, "
+"indicating the participant has aborted and the transaction should also "
+"attempt to do so."
+msgstr ""
+"<emphasis>prepare</emphasis>: Der Teilnehmer sollte alle Arbeiten ausführen, "
+"die nötig sind, ihm das Festschreiben bzw. Zurücksetzen der vom Web Service "
+"im Scope der Transaktion durchgeführten Arbeit zu ermöglichen. Die "
+"Implementierung darf alles Notwendige unternehmen, um den impliziten Vertrag "
+"zwischen ihr und dem Koordinator zu erfüllen. Vom Teilnehmer wird erwartet "
+"anzuzeigen, ob er sich vorbereiten kann, indem er eine Instanz von <code>com."
+"arjuna.wst.Vote</code> zurückgibt. Werte sind: <code>ReadOnly</code>, was "
+"anzeigt, dass der Teilnehmer nicht über das Ergebnis der Transaktion "
+"informiert werden muss, da keine Zustandsänderungen vorgenommen wurden; "
+"\"Prepared\", was anzeigt, dass der Teilnehmer darauf vorbereitet ist "
+"festzuschreiben oder zurückzusetzen, abhängig vom Endergebnis der "
+"Transaktion, und dass ausreichend Zustandsänderungen persistent gemacht "
+"wurden, um dies zu erreichen; sowie \"Aborted\", was anzeigt, dass der "
+"Teilnehmer abbrach und die Transaktion dies ebenfalls versuchen sollte."
+
+#. Tag: para
+#: Participants.xml:43 Participants.xml:81
+#, no-c-format
+msgid ""
+"<emphasis>commit</emphasis>: the participant should make permanent the work "
+"that it controls. What it does will depend upon its implementation, for "
+"example, commit the reservation of the theatre ticket. The participant will "
+"then return an indication of whether or not it succeeded."
+msgstr ""
+"<emphasis>commit</emphasis>: Der Teilnehmer sollte die Arbeit, die er "
+"kontrolliert, dauerhaft machen. Was dies bewirkt, hängt von der "
+"Implementierung ab, z. B. wird die Reservierung der Theaterkarten "
+"abgeschlossen. Der Teilnehmer wird anschließend einen Meldung zurückgeben, "
+"ob er erfolgreich war oder nicht."
+
+#. Tag: para
+#: Participants.xml:48 Participants.xml:86
+#, no-c-format
+msgid ""
+"<emphasis>rollback</emphasis>: the participant should undo the work that it "
+"controls. The participant will then return an indication of whether or not "
+"it succeeded."
+msgstr ""
+"<emphasis>rollback</emphasis>: Der Teilnehmer sollte die Arbeit, die er "
+"kontrolliert, zurücksetzen (rückgängig machen). Der Teilnehmer wird "
+"anschließend eine Meldung zurückgeben, ob er erfolgreich war oder nicht."
+
+#. Tag: para
+#: Participants.xml:53 Participants.xml:91
+#, no-c-format
+msgid ""
+"<emphasis>commitOnePhase</emphasis>: if there is only a single "
+"TwoPCParticipant registered with the transaction, then the coordinator can "
+"optimize the protocol and simply tell the participant to commit: there is no "
+"need for a preparatory phase since consensus is implicit."
+msgstr ""
+"<emphasis>commitOnePhase</emphasis>: Falls nur ein einziger TwoPCParticipant "
+"bei der Transaktion registriert ist, kann der Koordinator das Protokoll "
+"optimieren und den Teilnehmer einfach anweisen abzuschließen: Eine "
+"Vorbereitungsphase ist unnötig, da die Zustimmung implizit ist."
+
+#. Tag: para
+#: Participants.xml:58 Participants.xml:96
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: during recovery the participant can inquire as "
+"to the status of the transaction it was registered with. If that transaction "
+"is no longer available (has rolled back) then this operation will be invoked "
+"by the coordination service."
+msgstr ""
+"<emphasis>unknown</emphasis>: Während der Recovery kann der Teilnehmer den "
+"Zustand der Transaktion anfragen, bei der er registriert wurde. Ist diese "
+"Transaktion nicht länger verfügbar (weil zurückgesetzt), dann wird diese "
+"Operation vom Koordinationsdienst aufgerufen."
+
+#. Tag: para
+#: Participants.xml:63 Participants.xml:101
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: during recovery the participant can enquire as "
+"to the status of the transaction it was registered with. If an error occurs "
+"(for example, the transaction service is unavailable) then this operation "
+"will be invoked."
+msgstr ""
+"<emphasis>error</emphasis>: Während der Recovery kann der Teilnehmer den "
+"Zustand der Transaktion anfragen, bei der er registriert wurde. Falls ein "
+"Fehler auftritt (z. B. der Transaktionsdienst ist nicht verfügbar), wird "
+"diese Operation aufgerufen."
+
+#. Tag: title
+#: Participants.xml:69
+#, no-c-format
+msgid "Volatile2PCParticipant"
+msgstr "Volatile2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:70
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Volatile2PC protocol "
+"with the following signatures, as per the <interfacename>com.arjuna.wst."
+"Volatile2Participant</interfacename> interface:"
+msgstr ""
+"Dieser Teilnehmer unterstützt das WS-Atomic Transaction Volatile2PC-"
+"Protokoll mit den folgenden Signaturen, gemäß der <interfacename>com.arjuna."
+"wst.Volatile2Participant</interfacename>-Schnittstelle:"
+
+#. Tag: para
+#: Participants.xml:76
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the com.arjuna.wst.Vote. "
+"Values are: ReadOnly, indicating the participant does not need to be "
+"informed of the transaction outcome as no state updates were made; Prepared, "
+"indicating the participant is prepared to commit or rollback depending on "
+"the final transaction outcome, and it has made sufficient state updates "
+"persistent to accomplish this; and Aborted, indicating the participant has "
+"aborted and the transaction should also attempt to do so."
+msgstr ""
+"<emphasis>prepare</emphasis>: Der Teilnehmer sollte alle Arbeiten ausführen, "
+"die nötig sind, ihm das Festschreiben bzw. Zurücksetzen der vom Web Service "
+"im Rahmen der Transaktion durchgeführten Arbeit zu ermöglichen. Die "
+"Implementierung darf alles Notwendige unternehmen, um den impliziten Vertrag "
+"zwischen ihr und dem Koordinator zu erfüllen. Vom Teilnehmer wird erwartet "
+"anzuzeigen, ob er sich vorbereiten kann, indem er eine Instanz des com."
+"arjuna.wst.Vote zurückgibt. Werte sind: \"ReadOnly\", was anzeigt, dass der "
+"Teilnehmer nicht über das Ergebnis der Transaktion informiert werden muss, "
+"da keine Zustandsänderungen vorgenommen wurden; \"Prepared\", was anzeigt, "
+"dass der Teilnehmer darauf vorbereitet ist, festzuschreiben oder "
+"zurückzusetzen, abhängig vom Endergebnis der Transaktion, und dass "
+"ausreichend Zustandsänderungen persistent gemacht wurden, um dies zu "
+"erreichen; und \"Aborted\", was anzeigt, dass der Teilnehmer abbrach und die "
+"Transaktion dies ebenfalls versuchen sollte."
+
+#. Tag: title
+#: Participants.xml:107
+#, no-c-format
+msgid "Business Activity"
+msgstr "Business Activity"
+
+#. Tag: para
+#: Participants.xml:108
+#, no-c-format
+msgid ""
+"All Business Activity participants are instances of the following interfaces."
+msgstr ""
+"Alle Teilnehmer einer Business Activity sind Instanzen der folgenden "
+"Schnittstellen:"
+
+#. Tag: title
+#: Participants.xml:113
+#, no-c-format
+msgid "BusinessAgreementWithParticipantCompletion"
+msgstr "BusinessAgreementWithParticipantCompletion"
+
+#. Tag: para
+#: Participants.xml:114
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"Dieser Teilnehmer unterstützt das WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code>-Protokoll mit den "
+"folgenden Signaturen, gemäß der <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename>-"
+"Schnittstelle."
+
+#. Tag: para
+#: Participants.xml:120 Participants.xml:158
+#, no-c-format
+msgid ""
+"<emphasis>close</emphasis>: the transaction has completed successfully. The "
+"participant previously informed the coordinator that it was ready to "
+"complete."
+msgstr ""
+"<emphasis>close</emphasis>: Die Transaktion wurde erfolgreich abgeschlossen. "
+"Der Teilnehmer hat zuvor den Koordinator darüber informiert, dass er bereit "
+"war zum Abschluss."
+
+#. Tag: para
+#: Participants.xml:125
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work. The participant cannot have informed the "
+"coordinator that it has completed."
+msgstr ""
+"<emphasis>cancel</emphasis>: Die Transaktion wurde abgebrochen und der "
+"Teilnehmer sollte jegliche Arbeiten rückgängig machen. Der Teilnehmer konnte "
+"den Koordinator nicht darüber informiert haben, dass er abgeschlossen hat."
+
+#. Tag: para
+#: Participants.xml:130 Participants.xml:168
+#, no-c-format
+msgid ""
+"<emphasis>compensate</emphasis>: the transaction has canceled. The "
+"participant previously informed the coordinator that it had finished work "
+"but could compensate later if required, so it is now requested to do so."
+msgstr ""
+"<emphasis>compensate</emphasis>: Die Transaktion wurde abgebrochen. Der "
+"Teilnehmer hat zuvor den Koordinator darüber informiert, dass er die Arbeit "
+"abgeschlossen hat, aber später kompensieren könnte wenn nötig; nun wurde er "
+"also aufgefordert, dies zu tun."
+
+#. Tag: para
+#: Participants.xml:135 Participants.xml:178
+#, no-c-format
+msgid "<emphasis>status</emphasis>: return the status of the participant."
+msgstr "<emphasis>status</emphasis>: Gibt den Zustand des Teilnehmers zurück."
+
+#. Tag: para
+#: Participants.xml:140 Participants.xml:183
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: if the participant inquires as to the status "
+"of the transaction it was registered with and that transaction is no longer "
+"available (has rolled back) then this operation will be invoked by the "
+"coordination service."
+msgstr ""
+"<emphasis>unknown</emphasis>: Falls der Teilnehmer den Zustand einer "
+"Transaktion anfragt, bei der er registriert wurde, diese ist jedoch nicht "
+"länger verfügbar (weil zurückgesetzt), dann wird diese Operation vom "
+"Koordinationsdienst aufgerufen."
+
+#. Tag: para
+#: Participants.xml:145 Participants.xml:188
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: if the participant enquired as to the status of "
+"the transaction it was registered with and an error occurs (for example, the "
+"transaction service is unavailable) then this operation will be invoked."
+msgstr ""
+"<emphasis>error</emphasis>: Falls der Teilnehmer den Zustand einer "
+"Transaktion anfragt, bei der er registriert wurde, und es tritt ein Fehler "
+"auf (z. B. der Transaktionsservice ist nicht verfügbar), wird diese "
+"Operation aufgerufen."
+
+#. Tag: title
+#: Participants.xml:151
+#, no-c-format
+msgid "BusinessAgreementWithCoordinatorCompletion"
+msgstr "BusinessAgreementWithCoordinatorCompletion"
+
+#. Tag: para
+#: Participants.xml:152
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"Dieser Teilnehmer unterstützt das WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>-Protokoll mit den "
+"folgenden Signaturen, gemäß der <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename>-"
+"Schnittstelle:"
+
+#. Tag: para
+#: Participants.xml:163
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work."
+msgstr ""
+"<emphasis>cancel</emphasis>: Die Transaktion wurde abgebrochen, und der "
+"Teilnehmer sollte jegliche Arbeit rückgängig machen."
+
+#. Tag: para
+#: Participants.xml:173
+#, no-c-format
+msgid ""
+"<emphasis>complete</emphasis>: the coordinator is informing the participant "
+"that all work it needs to do within the scope of this business activity has "
+"been received."
+msgstr ""
+"<emphasis>complete</emphasis>: Der Koordinator informiert den Teilnehmer, "
+"dass alle im Scope dieser Business Activity nötigen Arbeiten empfangen "
+"wurden."
+
+#. Tag: title
+#: Participants.xml:194
+#, no-c-format
+msgid "BAParticipantManager"
+msgstr "BAParticipantManager"
+
+#. Tag: para
+#: Participants.xml:195
+#, no-c-format
+msgid ""
+"In order for the Business Activity protocol to work correctly, the "
+"participants must be able to autonomously signal the coordinator that they "
+"have left the activity (exited) or are ready to complete and (if necessary) "
+"compensate (completed). Unlike the Atomic Transaction protocol, where all "
+"interactions between the coordinator and participants are instigated by the "
+"coordinator when the transaction terminates, this interaction pattern "
+"requires the participant to be able to talk to the coordinator at any time "
+"during the lifetime of the business activity."
+msgstr ""
+"Damit das Business Activity Protokoll ordnungsgemäß funktioniert, müssen die "
+"Teilnehmer dem Koordinator eigenständig signalisieren können, dass sie die "
+"Activity verlassen haben (\"exited\"), oder sie bereit sind zum Abschließen "
+"und (falls nötig) Kompensieren (\"completed\"). Im Unterschied zum Atomic "
+"Transaction Protokoll, wo alle Interaktionen zwischen Koordinator und "
+"Teilnehmern vom Koordinator veranlasst werden, wenn die Transaktion "
+"abschließt, erfordert dieses Interaktionsmodell von den Teilnehmern die "
+"Fähigkeit, jederzeit während der Lebenszeit der Business Activity mit dem "
+"Koordinator zu kommunizieren."
+
+#. Tag: para
+#: Participants.xml:199
+#, no-c-format
+msgid ""
+"As such, whenever a participant is registered with a business activity, it "
+"receives a handle on the coordinator. This handle is an instance of the "
+"<interfacename>BAParticipantManager</interfacename> interface, located in "
+"<code>com.arjuna.wst.BAParticipantManager</code>, with the following methods:"
+msgstr ""
+"Immer wenn ein Teilnehmer bei einer Business Activity registriert wird, "
+"erhält dieser daher einen Handle auf den Koordinator. Dieser Handle ist eine "
+"Instanz der <interfacename>BAParticipantManager</interfacename>-"
+"Schnittstelle, und befindet sich in <code>com.arjuna.wst."
+"BAParticipantManager</code>, mit den folgenden Methoden:"
+
+#. Tag: para
+#: Participants.xml:204
+#, no-c-format
+msgid ""
+"<emphasis>exit</emphasis>: the participant has exited the business activity. "
+"The participant uses this to inform the coordinator that is has left the "
+"activity. It will not be informed when (and how) the business activity "
+"terminates."
+msgstr ""
+"<emphasis>exit</emphasis>: Der Teilnehmer hat die Business Activity "
+"verlassen. Der Teilnehmer verwendet dies, um den Koordinator darüber zu "
+"informieren, dass er die Activity verlassen hat. Er wird nicht informiert, "
+"wann (und wie) die Business Activity endet."
+
+#. Tag: para
+#: Participants.xml:209
+#, no-c-format
+msgid ""
+"<emphasis>completed</emphasis>: the participant has completed it works, but "
+"wishes to continue in the business activity, so that it will eventually be "
+"told when (and how) the activity terminates. The participant may later be "
+"asked to compensate for the work it has done."
+msgstr ""
+"<emphasis>completed</emphasis>: Der Teilnehmer hat seine Arbeit "
+"abgeschlossen, möchte aber die Business Activity fortsetzen, so dass ihm "
+"schließlich mitgeteilt wird, wann (und wie) die Activity endet. Der "
+"Teilnehmer wird evtl. später dazu aufgefordert, die ausgeführte Arbeit zu "
+"kompensieren."
+
+#. Tag: para
+#: Participants.xml:214
+#, no-c-format
+msgid ""
+"<emphasis>fault</emphasis>: the participant encountered an error during "
+"normal activation and has compensated. This places the business activity "
+"into a mandatory cancel-only mode."
+msgstr ""
+"<emphasis>fault</emphasis>: Der Teilnehmer traf auf einen Fehler während der "
+"normalen Aktivierung und hat kompensiert. Dies versetzt die Business "
+"Activity in einen zwingenden \"cancel-only\"-Modus."
+
+#. Tag: title
+#: Participants.xml:222
+#, no-c-format
+msgid "Participant Creation and Deployment"
+msgstr "Erstellung und Einsatz von Teilnehmern"
+
+#. Tag: para
+#: Participants.xml:223
+#, no-c-format
+msgid ""
+"As has been shown, the participant provides the plumbing that drives the "
+"transactional aspects of the service. This section discusses the specifics "
+"of Participant programming and usage."
+msgstr ""
+"Wie gezeigt wurde, liefert der Teilnehmer die Verbindungen, die die "
+"transaktionalen Aspekte des Services steuern. Dieser Abschnitt erläutert nun "
+"die Einzelheiten der Teilnehmerprogrammierung und -anwendung."
+
+#. Tag: title
+#: Participants.xml:227
+#, no-c-format
+msgid "Implementing Participants"
+msgstr "Implementierung von Teilnehmern"
+
+#. Tag: para
+#: Participants.xml:228
+#, no-c-format
+msgid ""
+"Implementing a participant is, in theory, a relatively straightforward task, "
+"though depending on the complexity of the transactional infrastructure that "
+"the participant is to manage, the actual size and complexity of a "
+"participant will vary. The participant interfaces can be found under "
+"<code>com.arjuna.wst</code>. Your implementation must implement one of these "
+"interfaces."
+msgstr ""
+"Die Implementierung eines Teilnehmers ist theoretisch eine relativ "
+"überschaubare Aufgabe, aber abhängig von der Komplexität der transaktionalen "
+"Infrastruktur, welche der Teilnehmer zu steuern hat, kann die tatsächliche "
+"Größe und Komplexität eines Teilnehmers variieren. Die "
+"Teilnehmerschnittstellen sind unter <code>com.arjuna.wst</code> zu finden. "
+"Ihre Implementierung muss eine dieser Schnittstellen implementieren."
+
+#. Tag: title
+#: Participants.xml:233
+#, no-c-format
+msgid "Deploying Participants"
+msgstr "Einsatz von Teilnehmern"
+
+#. Tag: para
+#: Participants.xml:234
+#, no-c-format
+msgid ""
+"In order to allow Participants to be located remote from the Transaction "
+"Manager, XTS includes transparent message routing functionality. The "
+"Participant classes are not exposed directly as web services, but rather "
+"registered with a web service which receives messages from the Transaction "
+"Manager and maps them to appropriate method invocations on the relevant "
+"Participant instance. Transactional web services will typically enroll a new "
+"Participant instance of the desired type for each new transaction. A unique "
+"identifier must be provided at enrollment time and will be used to map "
+"transaction protocol messages to the appropriate participant instance. Note "
+"that Participant method invocations do not occur in a specific transaction "
+"context. Therefore, if your Participant implementation requires knowledge of "
+"the transaction context (for example, to look up state information in a "
+"persistent store) then you should provide this to the Participant instance, "
+"typically as an argument to the constructor function. Sample Participant "
+"implementations and usage can be found in the demonstration application "
+"included with XTS."
+msgstr ""
+"Um es Teilnehmern zu ermöglichen, sich entfernt vom Transaktionsmanager "
+"zubefinden, beinhaltet XTS eine transparente Funktionalität zum Nachrichten-"
+"Routing. Die Teilnehmerklassen werden nicht direkt als Web Services "
+"offengelegt, sondern vielmehr bei einem Web Service registriert, der "
+"Nachrichten vom Transaktionsmanager empfängt und entsprechenden "
+"Methodenaufrufen auf den relevanten Teilnehmerinstanzen zuweist. "
+"Transaktionale Web Services registrieren in der Regel eine neue "
+"Teilnehmerinstanz vom gewünschten Typ für jede neue Transaktion. Ein "
+"eindeutiger Identifier muss beim Anmelden geliefert werden, der beim "
+"Zuweisen von Transaktionsprotokollnachrichten zu den entsprechenden "
+"Teilnehmerinstanzen verwendet werden wird. Beachten Sie, dass "
+"Teilnehmermethodenaufrufe nicht in einem spezifischen Transaktionskontext "
+"auftreten. Falls Ihre Teilnehmerimplementierung die Kenntnis des "
+"Transaktionskontextes erfordert (z. B. Zustandsinformationen in einem "
+"persistenten Speicher), dann sollten Sie dies deshalb der Teilnehmerinstanz "
+"zur Verfügung stellen, in der Regel als ein Argument zur "
+"Konstruktorfunktion. Beispiele für die Teilnehmerimplementierungen und deren "
+"Nutzung finden Sie in der Demo-Anwendung, die in XTS enthalten ist."
+
+#. Tag: para
+#: Participants.xml:238
+#, no-c-format
+msgid ""
+"Any application code which creates and enrolls Participants must be deployed "
+"along with the parts of XTS necessary for receiving and processing incoming "
+"messages from the Transaction Manager. This typically means including the "
+"appropriate XTS .jar, .wsr and .war files in your application. If you are "
+"deploying your application only a server which does not already contain a "
+"Transaction Manger installation, you will also need to deploy the XTS "
+"configuration files."
+msgstr ""
+"Jeglicher Anwendungs-Code, der Teilnehmer erstellt und anmeldet, muss "
+"deployt werden samt der XTS-Teile, die nötig sind zum Empfang und zur "
+"Verarbeitung eingehender Nachrichten vom Transaktionsmanager. Dies bedeutet "
+"in der Regel das Einbinden der entsprechenden XTS .jar, .wsr und .war-"
+"Dateien in Ihre Anwendung. Falls Sie Ihre Anwendung auf einem Server "
+"einsetzen, der noch keine Installation eines Transaktionsmangers enthält, "
+"müssen Sie auch die XTS-Konfigurationsdateien deployen."
+
+#. Tag: para
+#: Participants.xml:242
+#, no-c-format
+msgid ""
+"In early access releases of the XTS product, the Transaction Manager and "
+"participant management functions are not provided as separable components. "
+"Configuration and deployment of the participant infrastructure is therefore "
+"as in the Transaction Manger section above. More flexible deployment of the "
+"XTS components will be available in the final release."
+msgstr ""
+"In Vorabversionen des XTS-Produkts werden die Funktionen des "
+"Transaktionsmanagers und des Teilnehmermanagements nicht als teilbare "
+"Komponenten geliefert. Konfiguration und Einsatz der Teilnehmerinfrastruktur "
+"erfolgt daher wie im obigen Abschnitt über den Transaktionsmanager. Ein "
+"flexiblerer Einsatz der XTS-Komponenten wird in der finalen Release "
+"verfügbar sein."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Preface.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Preface.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr "Vorwort"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Revision_History.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Revision_History.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,29 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "Revisionsgeschichte"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Stand-alone_Coordinator.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Stand-alone_Coordinator.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Stand-alone_Coordinator.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,40 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:6
+#, no-c-format
+msgid "Stand-alone Coordinator"
+msgstr "Eigenständiger Koordinator"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Einführung"
+
+#. Tag: para
+#: Stand-alone_Coordinator.xml:9
+#, no-c-format
+msgid ""
+"For configuring a stand-alone Web Services transaction coordinator, see the "
+"relevant chapter in the System Administrator’s Guide."
+msgstr ""
+"Zum Konfigurieren eines eigenständigen (\"stand-alone\") Web Services "
+"Transaktionskoordinators lesen Sie bitte das entsprechende Kapitel im "
+"Handbuch für Systemadministratoren."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/The_XTS_API.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/The_XTS_API.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/The_XTS_API.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,777 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr "Die XTS-API"
+
+#. Tag: title
+#: The_XTS_API.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Einführung"
+
+#. Tag: para
+#: The_XTS_API.xml:9
+#, no-c-format
+msgid ""
+"This chapter shows how to use the XTS API. This is of use both at the client-"
+"side where applications consume transactional Web services, and at the "
+"service/participant side where transactions need to be coordinated with back-"
+"end systems."
+msgstr ""
+"Dieses Kapitel veranschaulicht die Benutzung der XTS-API. Dies ist nützlich "
+"sowohl auf Client-Seite, wo Anwendungen transaktionale Web Services "
+"konsumieren, als auch auf Service/Teilnehmer-Seite, wo Transaktionen mit "
+"Backend-Systemen koordiniert werden müssen."
+
+#. Tag: title
+#: The_XTS_API.xml:15
+#, no-c-format
+msgid "API for the Atomic Transaction protocol"
+msgstr "API für das Atomic Transaction Protokoll"
+
+#. Tag: para
+#: The_XTS_API.xml:16
+#, no-c-format
+msgid ""
+"The following classes and interfaces are located within the <package>com."
+"arjuna.wst or com.arjuna.mw.wst</package> packages and sub-packages."
+msgstr ""
+"Die folgenden Klassen und Schnittstellen befinden sich in den <package>com."
+"arjuna.wst or com.arjuna.mw.wst</package>-Paketen und Unterpaketen."
+
+#. Tag: title
+#: The_XTS_API.xml:20
+#, no-c-format
+msgid "Vote"
+msgstr "Abstimmung"
+
+#. Tag: para
+#: The_XTS_API.xml:21
+#, no-c-format
+msgid ""
+"During the two-phase commit protocol, a participant will be asked to vote on "
+"whether or not it can prepare to confirm the work that it controls. It must "
+"return one of the following subtypes of <code>com.arjuna.wst.Vote</code>:"
+msgstr ""
+"Während des zwei-Phasen Festschreibungsprotokolls wird ein Teilnehmer "
+"aufgefordert abzustimmen, ob er sich darauf vorbeiten kann, die von ihm "
+"kontrollierte Arbeit abzuschließen, oder nicht. Er muss eine der folgenden "
+"Untertypen von <code>com.arjuna.wst.Vote</code> zurückgeben:"
+
+#. Tag: para
+#: The_XTS_API.xml:27
+#, no-c-format
+msgid ""
+"<emphasis>Prepared</emphasis>: the participant indicates that it can prepare "
+"if asked to by the coordinator. It will not have committed at this stage "
+"however, since it does not know what the final outcome will be."
+msgstr ""
+"<emphasis>Prepared</emphasis>: Der Teilnehmer zeigt an, dass er sich "
+"vorbereiten kann, falls vom Koordinator dazu aufgefordert. Er wird jedoch zu "
+"diesem Zeitpunkt noch nicht festgeschrieben haben, denn er weiß nicht, wie "
+"das Endergebnis ausfallen wird."
+
+#. Tag: para
+#: The_XTS_API.xml:32
+#, no-c-format
+msgid ""
+"<emphasis>Aborted</emphasis>: the participant indicates that it cannot "
+"prepare and has in fact rolled back. The participant should not expect to "
+"get a second phase message."
+msgstr ""
+"<emphasis>Aborted</emphasis>: Der Teilnehmer zeigt an, dass er sich nicht "
+"vorbereiten kann, sondern zurückgesetzt hat. Der Teilnehmer sollte nicht "
+"erwarten, eine Meldung der zweiten Phase zu bekommen."
+
+#. Tag: para
+#: The_XTS_API.xml:37
+#, no-c-format
+msgid ""
+"<emphasis>ReadOnly</emphasis>: the participant indicates that the work it "
+"controls has not made any changes to state that require it to be informed of "
+"the final outcome of the transaction. Essentially the participant is "
+"resigning from the transaction."
+msgstr ""
+"<emphasis>ReadOnly</emphasis>: Der Teilnehmer zeigt an, dass die von ihm "
+"kontrollierte Arbeit keinerlei Änderungen am Zustand vorgenommen haben, die "
+"es erfordern würden, über das Endergebnis der Transaktion informiert zu "
+"werden. Der Teilnehmer tritt aus der Transaktion aus."
+
+#. Tag: para
+#: The_XTS_API.xml:42
+#, no-c-format
+msgid ""
+"Thus a possible implementation of a 2PC participant’s prepare method may "
+"resemble the following:"
+msgstr ""
+"Demnach kann eine mögliche Implementierung einer Methode zur 2PC-"
+"Teilnehmervorbereitung ähnlich der folgenden aussehen:"
+
+#. Tag: screen
+#: The_XTS_API.xml:45
+#, no-c-format
+msgid ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+msgstr ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+
+#. Tag: title
+#: The_XTS_API.xml:47
+#, no-c-format
+msgid "The transaction context"
+msgstr "Der Transaktionskontext"
+
+#. Tag: para
+#: The_XTS_API.xml:48
+#, no-c-format
+msgid ""
+"A transaction is typically represented by some unique identifier and a "
+"reference to the coordinator which manages the transaction, for example, a "
+"URL. XTS allows transactions to be nested such that a transaction hierarchy "
+"(tree) may be formed. Thus, a transaction context may be a set of "
+"transactions, with the top-most transaction the root parent (superior)."
+msgstr ""
+"Eine Transaktion wird in der Regel repräsentiert durch eindeutige Identifier "
+"und eines Referenz zum Koordinator, der die Transaktion steuert, z. B. eine "
+"URL. XTS erlaubt verschachtelte Transaktionen, so dass eine "
+"Transaktionshierarchie (Baum) gebildet werden kann. Demnach kann ein "
+"Transaktionskontext eine Gruppe von Transaktionen sein, wobei die oberste "
+"Transaktion der Root Parent-Knoten (Superior) ist."
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr "TxContext"
+
+#. Tag: para
+#: The_XTS_API.xml:54
+#, no-c-format
+msgid ""
+"<code>com.arjuna.mw.wst.TxContext</code> is an opaque representation of a "
+"transaction context."
+msgstr ""
+"<code>com.arjuna.mw.wst.TxContext</code> ist eine nicht einsehbare (\"opaque"
+"\") Repräsentation eines Transaktionskontextes."
+
+#. Tag: para
+#: The_XTS_API.xml:60
+#, no-c-format
+msgid ""
+"<emphasis>valid</emphasis>: this indicates whether or not the contents are "
+"valid."
+msgstr ""
+"<emphasis>valid</emphasis>: Dies zeigt an, ob die Inhalte gültig sind oder "
+"nicht."
+
+#. Tag: para
+#: The_XTS_API.xml:65
+#, no-c-format
+msgid "<emphasis>equals</emphasis>: can be used to compare two instances."
+msgstr ""
+"<emphasis>equals</emphasis>: Kann zum Vergleich zweier Instanzen verwendet "
+"werden."
+
+#. Tag: title
+#: The_XTS_API.xml:71
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: The_XTS_API.xml:72
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserTransaction</classname> is the class that "
+"most users (for example, clients and services) will see. This isolates them "
+"from the underlying protocol-specific aspects of the XTS implementation. "
+"Importantly, a UserTransaction does not represent a specific transaction, "
+"but rather is responsible for providing access to an implicit per-thread "
+"transaction context; it is similar to the UserTransaction in the JTA "
+"specification. Therefore, all of the UserTransaction methods implicitly act "
+"on the current thread of control."
+msgstr ""
+"Die <classname>com.arjuna.wst.UserTransaction</classname> ist diejenige "
+"Klasse, die die meisten Benutzer (z. B. Clients and Services) sehen werden. "
+"Dies isoliert sie von den zugrunde liegenden, protokollspezifischen Aspekten "
+"der XTS-Implementation. Beachten Sie, dass eine UserTransaction keine "
+"spezifische Transaktion repräsentiert, sondern dafür verantwortlich ist, "
+"Zugang zu ermöglichen zu einem impliziten Transaktionskontext pro Thread; es "
+"ist der UserTransaction in den JTA-Spezifikationen ähnlich. Aus diesem Grund "
+"handeln implizit alle UserTransaction-Methoden nach dem aktuellen Kontroll-"
+"Thread."
+
+#. Tag: para
+#: The_XTS_API.xml:76
+#, no-c-format
+msgid ""
+"A new transaction is begun and associated with the invoking thread by using "
+"the begin method. If there is already a transaction associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created transaction with the "
+"current thread."
+msgstr ""
+"Eine neue Transaktion wird begonnen und durch Verwendung der \"begin\"-"
+"Methode mit dem aufrufenden Thread assoziiert. Falls es bereits eine an "
+"diesem Thread beteiligte Transaktion gibt, wird die "
+"<code>WrongStateException</code>-Ausnahme geworfen. Bei Erfolg beteiligt "
+"diese Operation die neu erstellte Transaktion am aktuellen Thread."
+
+#. Tag: para
+#: The_XTS_API.xml:79
+#, no-c-format
+msgid ""
+"The transaction is committed by the commit method. This will execute the "
+"Volatile2PC and Durable2PC protocols prior to returning. If there is no "
+"transaction associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. If the transaction "
+"ultimately rolls back then the <code>TransactionRolledBackException</code> "
+"is thrown. When complete, this operation disassociates the transaction from "
+"the current thread such that it becomes associated with no transaction."
+msgstr ""
+"Die Transaktion wird festgeschrieben mit der \"commit\"-Methode. Diese wird "
+"vor der Ausgabe die Protokolle Volatile2PC und Durable2PC ausführen. Falls "
+"es keine Transaktion gibt, die an dem ausführenden Thread beteiligt ist, "
+"wird die Ausnahme <code>UnknownTransactionException</code> geworfen. Falls "
+"die Transaktion letztlich zurückgesetzt wird, wird die "
+"<code>TransactionRolledBackException</code>-Ausnahme geworfen. Falls "
+"abgeschlossen, trennt diese Operation die Transaktion vom aktuellen Thread, "
+"so dass er mit keiner Transaktion mehr verbunden ist. "
+
+#. Tag: para
+#: The_XTS_API.xml:82
+#, no-c-format
+msgid ""
+"The <code>rollback</code> operation will terminate the transaction and "
+"return normally if it succeeded, while throwing an appropriate exception if "
+"it didn’t. If there is no transaction associated with the invoking thread "
+"then <code>UnknownTransactionException</code> is thrown."
+msgstr ""
+"Die <code>rollback</code>-Operation beendet die Transaktion und antwortet "
+"normal, wenn sie erfolgreich war, wird aber eine entsprechende Ausnahme "
+"werfen, wenn nicht. Falls keine Transaktion am aufrufenden Thread beiteiligt "
+"ist, wird die Ausnahme <code>UnknownTransactionException</code> geworfen."
+
+#. Tag: title
+#: The_XTS_API.xml:86
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr "UserTransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+"UserTransactions werden von einer <code>UserTransactionFactory</code> "
+"bezogen."
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: The_XTS_API.xml:93
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface represents "
+"the service/container/participant’s (service-side users) typical way in "
+"which to interact with the underlying transaction service implementation. As "
+"with <interfacename>UserTransaction</interfacename> a "
+"<interfacename>TransactionManager</interfacename> does not represent a "
+"specific transaction, but rather is responsible for providing access to an "
+"implicit per-thread transaction context."
+msgstr ""
+"Die <interfacename>TransactionManager</interfacename>-Schnittstelle "
+"repräsentiert die typische Art von Services/Containern/Teilnehmern (service-"
+"seitige Benutzer) für Interaktion mit den zugrunde liegenden "
+"Transaktionsdienstimplementierungen. Wie auch "
+"<interfacename>UserTransaction</interfacename> repräsentiert ein "
+"<interfacename>TransactionManager</interfacename> nicht eine spezifische "
+"Transaktion, sondern ist vielmehr dafür verantwortlich, Zugang zu einem "
+"impliziten Transaktionskontext pro Thread zu gewähren."
+
+#. Tag: para
+#: The_XTS_API.xml:97
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific transaction. In "
+"order to do this it is necessary to disassociate the thread from any "
+"transactions. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the transaction. The "
+"thread is then no longer associated with any transaction."
+msgstr ""
+"Ein Kontroll-Thread kann Perioden von Nicht-Transaktionalität erfodern, so "
+"dass er Arbeiten ausführen kann, die nicht an einer spezifischen Transaktion "
+"beteiligt sind. Dafür ist es notwendig, den Thread von jeglichen "
+"Transaktionen loszulösen. Dies wird erreicht durch die \"suspend\"-Methode, "
+"die eine <code>TxContext</code> Instanz zurückgibt, welche ein Handle ist "
+"für die Transaktion. Der Thread ist dann nicht länger an einer Transaktion "
+"beteiligt."
+
+#. Tag: para
+#: The_XTS_API.xml:100
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with a transaction(s) via its <code>TxContext</code>. Prior to "
+"association, the thread is disassociated with any transaction(s) with which "
+"it may be currently associated. If the <code>TxContext</code> is null, then "
+"the thread is associated with no transaction. The "
+"<code>UnknownTransactionException</code> exception is thrown if the "
+"transaction that the <code>TxContext</code> refers to is invalid in the "
+"scope of the invoking thread."
+msgstr ""
+"Die <methodname>resume</methodname>-Methode kann verwendet werden, um einen "
+"Thread (wieder) zu assoziieren mit einer Transaktion via seinem "
+"<code>TxContext</code>. Vor Assoziierung wird der Thread getrennt von allen "
+"Transaktionen, an denen er möglicherweise aktuell beteiligt ist. Falls der "
+"<code>TxContext</code> gleich Null ist, dann ist der Thread an keiner "
+"Transaktion beteiligt. Die <code>UnknownTransactionException</code>-Ausnahme "
+"wird geworfen, falls die Transaktion, auf die der <code>TxContext</code> "
+"verweist, ungültig ist im Scope des aufrufenden Threads."
+
+#. Tag: para
+#: The_XTS_API.xml:103
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current transaction, or null if there is "
+"none. Unlike suspend, this method does not disassociate the current thread "
+"from the transaction(s). This can be used to enable multiple threads to "
+"execute within the scope of the same transaction."
+msgstr ""
+"Die <methodname>currentTransaction</methodname>-Methode gibt den "
+"<code>TxContext</code> zurück für die aktuelle Transaktion, oder Null falls "
+"keine vorhanden ist. Anders als \"suspend\" trennt diese Methode den "
+"aktuellen Thread nicht von dem bzw. den Transaktion(en). Dies kann verwendet "
+"werden, um mehreren Threads das Ausführen innerhalb des Scopes derselben "
+"Transaktion zu ermöglichen."
+
+#. Tag: para
+#: The_XTS_API.xml:106
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a transaction, the "
+"container or participant must use:"
+msgstr ""
+"Zum Registrieren und Austreten von Teilnehmer bei einer Transaktion muss der "
+"Container oder Teilnehmer folgendes anwenden:"
+
+#. Tag: para
+#: The_XTS_API.xml:111
+#, no-c-format
+msgid ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"Volatile2PC protocol; a unique identifier for the participant is also "
+"required. If there is no transaction associated with the invoking thread "
+"then the <code>UnknownTransactionException</code> exception is thrown. If "
+"the coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: Anmelden des aktuellen "
+"Teilnehmers bei der aktuellen Transaktion, so dass er am Volatile2PC-"
+"Protokoll teilnehmen wird; ein eindeutiger Identifier für den Teilnehmer ist "
+"ebenfalls nötig. Wenn keine Transaktion beteiligt ist am aufrufenden Thread, "
+"wird die <code>UnknownTransactionException</code>-Ausnahme geworfen. Falls "
+"der Koordinator bereits einen angemeldeten Teilnehmer mit demselben "
+"Identifier besitzt, wird die <code>AlreadyRegisteredException</code>-"
+"Ausnahme geworfen. Falls die Transaktion sich nicht in einem Zustand "
+"befindet, in dem neue Teilnehmer angemeldet werden können (z. B. sie wird "
+"beendet), wird die Ausnahme <code>WrongStateException</code> geworfen."
+
+#. Tag: para
+#: The_XTS_API.xml:116
+#, no-c-format
+msgid ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"2PC protocol; a unique identifier for the participant is also required. If "
+"there is no transaction associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: Anmelden des aktuellen "
+"Teilnehmers bei der aktuellen Transaktion, so dass er am 2PC-Protokoll "
+"teilnehmen wird; ein eindeutiger Identifier für den Teilnehmer ist ebenfalls "
+"nötig. Wenn keine Transaktion beteiligt ist am aufrufenden Thread, wird die "
+"<code>UnknownTransactionException</code>-Ausnahme geworfen. Falls der "
+"Koordinator bereits einen angemeldeten Teilnehmer mit demselben Identifier "
+"besitzt, wird die <code>AlreadyRegisteredException</code>-Ausnahme geworfen. "
+"Falls die Transaktion sich nicht in einem Zustand befindet, in dem neue "
+"Teilnehmer angemeldet werden können (z. B. sie wird beendet), wird die "
+"Ausnahme <code>WrongStateException</code> geworfen."
+
+#. Tag: title
+#: The_XTS_API.xml:122
+#, no-c-format
+msgid "TransactionFactory"
+msgstr "TransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+"Transaktionsmanager werden von einer <code>TransactionFactory</code> bezogen."
+
+#. Tag: title
+#: The_XTS_API.xml:130
+#, no-c-format
+msgid "API for the Business Activity protocol"
+msgstr "API für das Business Activity Protokoll"
+
+#. Tag: title
+#: The_XTS_API.xml:132
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr "UserBusinessActivity"
+
+#. Tag: para
+#: The_XTS_API.xml:133
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserBusinessActivity</classname> is the class "
+"that most users (for example, clients and services) will see. This isolates "
+"them from the underlying protocol-specific aspects of the XTS "
+"implementation. Importantly, a <code>UserBusinessActivity</code> does not "
+"represent a specific business activity, but rather is responsible for "
+"providing access to an implicit per-thread activity. Therefore, all of the "
+"<code>UserBusinessActivity</code> methods implicitly act on the current "
+"thread of control."
+msgstr ""
+"Die <classname>com.arjuna.wst.UserBusinessActivity</classname> ist diejenige "
+"Klasse, die die meisten Benutzer (z. B. Clients and Services) sehen werden. "
+"Dies isoliert von den zugrunde liegenden, protokollspezifischen Aspekten der "
+"XTS-Implementation. Beachten Sie, dass eine <code>UserBusinessActivity</"
+"code> keine spezifische Business Activity repräsentiert, sondern vielmehr "
+"dafür verantwortlich ist, Zugang zu ermöglichen zu einer impliziten Activity "
+"pro Thread. Aus diesem Grund handeln implizit alle UserTransaction-Methoden "
+"nach dem aktuellen Kontroll-Thread."
+
+#. Tag: para
+#: The_XTS_API.xml:137
+#, no-c-format
+msgid ""
+"A new business activity is begun and associated with the invoking thread by "
+"using the begin method. If there is already an activity associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created activity with the "
+"current thread."
+msgstr ""
+"Eine neue Business Activity wird begonnen und durch Verwendung der \"begin\"-"
+"Methode mit dem aufrufenden Thread assoziiert. Falls es bereits eine an "
+"diesem Thread beteiligte Transaktion gibt, wird die "
+"<code>WrongStateException</code>-Ausnahme geworfen. Bei Erfolg assoziiert "
+"diese Operation die neu erstellte Activity mit dem aktuellen Thread."
+
+#. Tag: para
+#: The_XTS_API.xml:140
+#, no-c-format
+msgid ""
+"The business activity is completed successfully by the close method. This "
+"will execute the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol prior to returning. If there is no activity associated with the "
+"invoking thread then <code>UnknownTransactionException</code> is thrown. If "
+"the activity ultimately cancels then the "
+"<code>TransactionRolledBackException</code> is thrown. When complete, this "
+"operation disassociates the business activity from the current thread such "
+"that it becomes associated with no activity."
+msgstr ""
+"Die Business Activity wird erfolgreich abgeschlossen mit der \"commit\"-"
+"Methode. Diese wird vor der Ausgabe das "
+"<code>BusinessAgreementWithParticipantCompletion</code>-Protokoll ausführen. "
+"Falls es keine Activity gibt, die an dem ausführenden Thread beteiligt ist, "
+"wird die Ausnahme <code>UnknownTransactionException</code> geworfen. Falls "
+"die Activity letztlich zurückgesetzt wird, wird die "
+"<code>TransactionRolledBackException</code>-Ausnahme geworfen. Falls "
+"abgeschlossen, trennt diese Operation die Business Activity vom aktuellen "
+"Thread, so dass er mit keiner Activity mehr assoziiert ist."
+
+#. Tag: para
+#: The_XTS_API.xml:143
+#, no-c-format
+msgid ""
+"The cancel operation will terminate the business activity and return "
+"normally if it succeeded, while throwing an appropriate exception if it "
+"didn’t. If there is no activity associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. Any participants that "
+"had previously completed will be informed to compensate for their work."
+msgstr ""
+"Die \"cancel\"-Operation beendet die Business Activity und antwortet normal, "
+"wenn sie erfolgreich war, wird aber eine entsprechende Ausnahme werfen, wenn "
+"nicht. Falls keine Activity am aufrufenden Thread beiteiligt ist, wird die "
+"Ausnahme <code>UnknownTransactionException</code> geworfen. Jegliche "
+"Teilnehmer, die vorher bereits erfolgreich abgeschlossen hatten, werden nun "
+"darüber informiert, ihre Arbeit zu kompensieren."
+
+#. Tag: para
+#: The_XTS_API.xml:146
+#, no-c-format
+msgid ""
+"Some participants may have registered for the "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol, which "
+"requires the coordinator or application to inform them when all work that "
+"they need to do within the scope of a business activity has been performed. "
+"The application should therefore use the complete method to inform these "
+"participants."
+msgstr ""
+"Einige Teilnehmer sind evtl. beim "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>-Protokoll "
+"registriert, welches vom Koordinator oder von der Anwendung erfordert, sie "
+"darüber zu informieren, wenn sie alle Arbeiten ausgeführt haben, die "
+"innerhalb des Scopes einer Business Activity nötig sind. Die Anwendung "
+"sollte deshalb die \"complete\"-Methode verwenden, um diese Teilnehmer zu "
+"informieren."
+
+#. Tag: title
+#: The_XTS_API.xml:150
+#, no-c-format
+msgid "UserBusinessActivityFactory"
+msgstr "UserBusinessActivityFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+"UserBusinessActivities werden von der <code>UserBusinessActivityFactory</"
+"code> bezogen."
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr "BusinessActivityManager"
+
+#. Tag: para
+#: The_XTS_API.xml:157
+#, no-c-format
+msgid ""
+"The <interfacename>BusinessActivityManager</interfacename> interface "
+"represents the service/container/participant’s (service-side users) typical "
+"way in which to interact with the underlying business activity service "
+"implementation. As with <interfacename>UserBusinessActivity</interfacename> "
+"a <interfacename>BusinessActivityManager</interfacename> does not represent "
+"a specific activity, but rather is responsible for providing access to an "
+"implicit per-thread activity."
+msgstr ""
+"Die <interfacename>BusinessActivityManager</interfacename>-Schnittstelle "
+"repräsentiert die typische Art von Services/Containern/Teilnehmern (service-"
+"seitige Benutzer) für Interaktion mit den zugrunde liegenden "
+"BusinessActivity Service-Implementierungen. Wie auch "
+"<interfacename>UserTransaction</interfacename> repräsentiert ein "
+"<interfacename>BusinessActivityManager</interfacename> nicht eine "
+"spezifische Activity, sondern ist vielmehr dafür verantwortlich, Zugang zu "
+"einer impliziten Activity pro Thread zu gewähren."
+
+#. Tag: para
+#: The_XTS_API.xml:161
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific activity. In order "
+"to do this it is necessary to disassociate the thread from any business "
+"activities. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the activity. The "
+"thread is then no longer associated with any activity."
+msgstr ""
+"Ein Kontroll-Thread kann Perioden von Nicht-Transaktionalität erfodern, so "
+"dass er Arbeiten ausführen kann, die nicht an einer spezifischen Activity "
+"beteiligt sind. Dafür ist es notwendig, den Thread von jeglichen Business "
+"Activitys loszulösen. Dies wird erreicht durch die \"suspend\"-Methode, die "
+"eine <code>TxContext</code> Instanz zurückgibt, welche ein Handle ist für "
+"die Activity. Der Thread ist dann nicht länger an einer Activity beteiligt."
+
+#. Tag: para
+#: The_XTS_API.xml:164
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with an activity (or activities) via its TxContext. Prior to "
+"association, the thread is disassociated with any activity with which it may "
+"be currently associated. If the <code>TxContext</code> is null, then the "
+"thread is associated with no activity. The "
+"<code>UnknownTransactionException</code> exception is thrown if the business "
+"activity that the TxContext refers to is invalid in the scope of the "
+"invoking thread."
+msgstr ""
+"Die <methodname>resume</methodname>-Methode kann verwendet werden, um einen "
+"Thread (wieder) zu assoziieren mit einer Activity via seinem TxContext. Vor "
+"Assoziierung wird der Thread getrennt von allen Activitys, an denen er "
+"möglicherweise aktuell beteiligt ist. Falls der <code>TxContext</code> "
+"gleich Null ist, dann ist der Thread an keiner Activity beteiligt. Die "
+"<code>UnknownTransactionException</code>-Ausnahme wird geworfen falls die "
+"Business Activity, auf die der TxContext verweist, ungültig ist im Scope des "
+"aufrufenden Threads."
+
+#. Tag: para
+#: The_XTS_API.xml:167
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current business activity, or null if there "
+"is none. Unlike suspend, this method does not disassociate the current "
+"thread from the activity. This can be used to enable multiple threads to "
+"execute within the scope of the same business activity."
+msgstr ""
+"Die <methodname>currentTransaction</methodname>-Methode gibt den "
+"<code>TxContext</code> zurück für die aktuelle Business Activity, oder Null "
+"falls keine vorhanden ist. Anders als \"suspend\" trennt diese Methode den "
+"aktuellen Thread nicht von der Activity. Dies kann verwendet werden, um "
+"mehreren Threads das Ausführen innerhalb des Scopes derselben Business "
+"Activity zu ermöglichen."
+
+#. Tag: para
+#: The_XTS_API.xml:170
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a business activity, the "
+"container or participant must use:"
+msgstr ""
+"Zum Registrieren und Austreten von Business Activitys bei einer Transaktion "
+"muss der Container oder Teilnehmer folgendes anwenden:"
+
+#. Tag: para
+#: The_XTS_API.xml:175
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"enlist the specified participant with current business activity such that it "
+"will participate in the <code>BusinessAgreementWithParticipantCompletion</"
+"code> protocol; a unique identifier for the participant is also required. If "
+"there is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"Anmelden des spezifizierten Teilnehmers bei der aktuellen Business Activity, "
+"so dass er am <code>BusinessAgreementWithParticipantCompletion</code>-"
+"Protokoll teilnehmen wird; ein eindeutiger Identifier für den Teilnehmer ist "
+"ebenfalls nötig. Wenn keine Business Activity beteiligt ist am aufrufenden "
+"Thread, wird die <code>UnknownTransactionException</code>-Ausnahme geworfen. "
+"Falls der Koordinator bereits einen angemeldeten Teilnehmer mit demselben "
+"Identifier besitzt, wird die <code>AlreadyRegisteredException</code>-"
+"Ausnahme geworfen. Falls die Activity sich nicht in einem Zustand befindet, "
+"in dem neue Teilnehmer angemeldet werden können (z. B. sie wird beendet), "
+"wird die Ausnahme <code>WrongStateException</code> geworfen."
+
+#. Tag: para
+#: The_XTS_API.xml:180
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"enlist the specified participant with current activity such that it will "
+"participate in the <code>BusinessAgreementWithCoordinatorCompletion</code> "
+"protocol; a unique identifier for the participant is also required. If there "
+"is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"Anmelden des spezifizierten Teilnehmers bei der aktuellen Activity, so dass "
+"er am <code>BusinessAgreementWithCoordinatorCompletion</code>-Protokoll "
+"teilnehmen wird; ein eindeutiger Identifier für den Teilnehmer ist ebenfalls "
+"nötig. Wenn keine Business Activity beteiligt ist am aufrufenden Thread, "
+"wird die <code>UnknownTransactionException</code>-Ausnahme geworfen. Falls "
+"der Koordinator bereits einen angemeldeten Teilnehmer mit demselben "
+"Identifier besitzt, wird die <code>AlreadyRegisteredException</code>-"
+"Ausnahme geworfen. Falls die Activity sich nicht in einem Zustand befindet, "
+"in dem neue Teilnehmer angemeldet werden können (z. B. sie wird beendet), "
+"wird die Ausnahme <code>WrongStateException</code> geworfen."
+
+#. Tag: title
+#: The_XTS_API.xml:186
+#, no-c-format
+msgid "BusinessActivityManagerFactory"
+msgstr "BusinessActivityManagerFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
+"BusinessActivityManagers werden von einer "
+"<code>BusinessActivityManagerFactory</code> bezogen."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Transactional_Web_Services.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Transactional_Web_Services.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Transactional_Web_Services.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,146 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr "Transaktionale Web Services"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Einführung"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:9
+#, no-c-format
+msgid ""
+"This chapter describes how to provide transactional support for new and "
+"existing Web services using the service-side facilities of XTS. It shows how "
+"new services can be made transactional with no additional programming, and "
+"how existing services can be made WS-T transaction-aware in a non-invasive "
+"fashion."
+msgstr ""
+"Dieses Kapitel beschreibt, wie transaktionale Unterstützung für neue und "
+"bestehende Web Services bereitgestellt werden kann, unter Verwendung der "
+"server-seitigen Möglichkeiten von XTS. Es zeigt, wie neue Services "
+"transaktional gemacht werden können ohne zusätzliche Programmierung, und wie "
+"vorhandene Services auf nicht-invasive Weise WS-T transaktionssicher gemacht "
+"werden können."
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr "Ein transaktionaler Web Service"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:16
+#, no-c-format
+msgid ""
+"A Web service is a business-level entity. It encapsulates application logic "
+"needed to perform some domain-specific task, or is designed to delegate to a "
+"back-end system which executes that logic. Given it is part of application "
+"code, such non-functional requirements as transactionality should not "
+"impinge on its construction."
+msgstr ""
+"Ein Web Service ist eine Entity auf Geschäftsebene. Er kapselt die nötige "
+"Anwendungslogik, um domain-spezifische Aufgaben auszuführen, oder wurde "
+"dafür entworfen, an ein Backend-System zu delegieren, welches diese Logik "
+"ausführt. Da er Teil des Anwendungs-Codes ist, sollten solche nicht-"
+"funktionalen Anforderungen wie Transaktionalität nicht mit seiner "
+"Konstruktion kollidieren."
+
+#. Tag: para
+#: Transactional_Web_Services.xml:19
+#, no-c-format
+msgid ""
+"To support this notion, XTS provides a suite of components designed to work "
+"at the SOAP stack level, which deal with transactional matters on behalf of "
+"a Web service without requiring any changes to that service. In XTS two "
+"context handling components are registered with the SOAP server and deal "
+"with context management on behalf of the service without the service having "
+"to worry about context propagation issues itself. This is shown in the "
+"following figure."
+msgstr ""
+"Um diesen Begriff zu unterstützen, bietet XTS ein Komponenten-Set entworfen "
+"für die Arbeit auf Ebene des SOAP-Stapels, die transaktionale "
+"Angelegenheiten bearbeiten im Auftrag eines Web Services, ohne jegliche "
+"Änderungen an diesem Service zu erfordern. In XTS sind zwei Kontext-Handling-"
+"Komponenten beim SOAP-Server registriert und erledigen das Kontextmanagement "
+"im Auftrag des Services, ohne dass sich der Service selbst um "
+"Kontextfortpflanzung kümmern muss. Dies wird in der folgenden Abbildung "
+"dargestellt."
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr "Beim SOAP-Server registrierte Kontext-Handler"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:28
+#, no-c-format
+msgid ""
+"The detail of the context management that the context processor performs is "
+"unimportant to the Web service application logic, and is orthogonal to any "
+"work performed by any other protocol-specific context handlers too. However "
+"back-end systems which the Web service application logic uses (such as "
+"databases) are often interested in the front-end transaction context such "
+"that any operations invoked within its scope can be mapped onto a back-end "
+"transaction context. This is typically achieved at the back-end by wrapping "
+"a database driver in a veneer which implements both the interface of the "
+"original driver and hooks into the service-side API to access the "
+"transaction context details. The general architecture for this pattern is "
+"shown in the figure below."
+msgstr ""
+"Die Details des Kontextmanagements, die der Kontextprozessor durchführt, "
+"sind nicht wichtig für die Anwendunslogik eines Web Services, und sind "
+"orthogonal zu jeglicher ausgeführter Arbeit von beliebigen anderen "
+"protokollspezifischen Kontext-Handlern. Allerdings sind Backend-Systeme, die "
+"von der Anwendungslogik des Web Services verwendet werden (wie z. B. "
+"Datenbanken), oft interessiert am Frontend-Transaktionskontext, damit jede "
+"Operation, die in dessen Scope aufgerufen wird, einem Backend-"
+"Transaktionskontext zugewiesen werden kann. Dies wird in der Regel im "
+"Backend erreicht durch das Ummanteln eines Datenbanktreibers in eine Art "
+"\"Hülle\", welche sowohl die Schnittstelle des Originaltreibers "
+"implementiert, als auch sich einklinkt in die service-seitige API, um auf "
+"die Details des Transaktionskontexts zuzugreifen. Die allgemeine Architektur "
+"für dieses Modell ist in der Abbildung unten dargestellt."
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:35
+#, no-c-format
+msgid "General Pattern for Back-End Integration, Service Side"
+msgstr "Allgemeines Modell zur Backend-Integration, service-seitig"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:37
+#, no-c-format
+msgid ""
+"The missing element from this is the commit protocol which finally allows "
+"back-end work to be made durable or not at the end of a transaction. This is "
+"covered in the participant chapter where the participant/back-end relation "
+"is explored further."
+msgstr ""
+"Das fehlende Element ist das \"commit\"-Protokoll, welches letztendlich "
+"ermöglicht, die Arbeit im Backend beim Beenden einer Transaktion entweder "
+"dauerhaft zu machen oder nicht. Dies wird abgedeckt im Kapitel \"Teilnehmer"
+"\", wo die Teilnehmer/Backend-Beziehung weiter erläutert wird."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,920 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactions_Overview.xml:6
+#, no-c-format
+msgid "Transactions Overview"
+msgstr "Übersicht über Transaktionen"
+
+#. Tag: para
+#: Transactions_Overview.xml:7
+#, no-c-format
+msgid ""
+"Transactions have emerged as the dominant paradigm for coordinating "
+"interactions between parties in a distributed system, and in particular to "
+"manage applications that require concurrent access to shared data. Much of "
+"the JBossTS Web Service API is based on contemporary transaction APIs whose "
+"familiarity will enhance developer productivity and lessen the learning "
+"curve. While the following section provides the essential information that "
+"you should know before starting to use XTS for building transactional Web "
+"Services, it should not be treated as a definitive reference to all "
+"transactional technology."
+msgstr ""
+"Transaktionen bildeten sich heraus als vorherrschendes Paradigma zur "
+"Koordination von Interaktionen zwischen Parteien in einem verteilten System, "
+"insbesondere zur Steuerung von Anwendungen, die gleichzeitigen Zugriff auf "
+"gemeinsam genutzte Daten benötigen. Die JBossTS Web Service API basiert viel "
+"auf heutigen Transaktions-APIs, deren Bekanntheit die Produktivität von "
+"Entwicklern steigern und die Lernkurve verringern wird. Auch wenn der "
+"folgende Abschnitt grundlegende Informationen liefert, die Sie vor der "
+"Nutzung von XTS zum Erstellen von transaktionalen Web Services kennen "
+"sollten, so sollte dieser Abschnitt doch nicht als definitive Referenz für "
+"alle transaktionale Technologie betrachtet werden."
+
+#. Tag: para
+#: Transactions_Overview.xml:10
+#, no-c-format
+msgid ""
+"A classic transaction is a unit of work that either completely succeeds, or "
+"fails with all partially completed work being undone. When a transaction is "
+"committed, all changes made by the associated requests are made durable, "
+"normally by committing the results of the work to a database. If a "
+"transaction should fail and is rolled back, all changes made by the "
+"associated work are undone. Transactions in distributed systems typically "
+"require the use of a transaction manager that is responsible for "
+"coordinating all of the participants that are part of the transaction."
+msgstr ""
+"Eine klassische Transaktion ist eine Einheit von Arbeit, welche entweder "
+"vollständig erfolgreich abgeschlossen wird, oder fehlschlägt und alle nur "
+"teilweise erledigten Arbeiten zurücksetzt. Wenn eine Transaktion "
+"festgeschrieben wird, werden alle von den beteiligten Aufrufen getätigten "
+"Änderungen dauerhaft gemacht, in der Regel durch die Festschreibung des "
+"Arbeitsergebnisses in einer Datenbank. Falls eine Transaktion scheitert und "
+"zurückgesetzt wird, werden alle von den zugehörigen Arbeiten getätigten "
+"Änderungen zurückgesetzt. Transaktionen in verteilten Systemen erfordern in "
+"der Regel den Einsatz eines Transaktionsmanagers, der verantwortlich ist für "
+"die Koordination aller Teilnehmer, die Teil der Transaktion sind."
+
+#. Tag: para
+#: Transactions_Overview.xml:13
+#, no-c-format
+msgid ""
+"The main components involved in using and defining transactional Web "
+"Services using XTS are illustrated in Figure 1."
+msgstr ""
+"Die wichtigsten Komponenten, die beteiligt sind an der Nutzung und "
+"Definierung von Web Services mittels XTS, sind in Abbildung 1 dargestellt."
+
+#. Tag: para
+#: Transactions_Overview.xml:18
+#, no-c-format
+msgid ""
+"A Transaction Service: The Transaction Service captures the model of the "
+"underlying transaction protocol and coordinates parties affiliated with the "
+"transaction according to that model."
+msgstr ""
+"Ein Transaktionsdienst: Der Transaktionsdienst erfasst das Modell des "
+"zugrunde liegenden Transaktionsprotokolls und koordiniert zur Transaktion "
+"gehörige Parteien entsprechend dieses Modells."
+
+#. Tag: para
+#: Transactions_Overview.xml:23
+#, no-c-format
+msgid ""
+"A Transaction API: Provides an interface for transaction demarcation and the "
+"registration of participants."
+msgstr ""
+"Eine Transaktions-API: Eine Schnittstelle für Transaktionsdemarkation und "
+"die Registrierung von Teilnehmern."
+
+#. Tag: para
+#: Transactions_Overview.xml:28
+#, no-c-format
+msgid ""
+"A Participant: The entity that cooperates with the transaction service on "
+"behalf of its associated business logic."
+msgstr ""
+"Ein Teilnehmer: Die Entity, die mit dem Transaktionsdienst kooperiert im "
+"Auftrag der beteiligten Business-Logik."
+
+#. Tag: para
+#: Transactions_Overview.xml:33
+#, no-c-format
+msgid ""
+"The Context: Captures the necessary details of the transaction such that "
+"participants can enlist within its scope."
+msgstr ""
+"Der Kontext: Erfasst die notwendigen Details der Transaktion, so dass "
+"Teilnehmer sich innerhalb ihres Scopes anmelden können."
+
+#. Tag: caption
+#: Transactions_Overview.xml:42
+#, no-c-format
+msgid "Web Services and XTS"
+msgstr "Web Services und XTS"
+
+#. Tag: title
+#: Transactions_Overview.xml:45
+#, no-c-format
+msgid "The Coordinator"
+msgstr "Der Koordinator"
+
+#. Tag: para
+#: Transactions_Overview.xml:46
+#, no-c-format
+msgid ""
+"Associated with every transaction is a coordinator, which is responsible for "
+"governing the outcome of the transaction. The coordinator may be implemented "
+"as a separate service or may be co-located with the user for improved "
+"performance. Each coordinator is created by the transaction manager service, "
+"which is in effect a factory for those coordinators."
+msgstr ""
+"Mit jeder Transaktion ist ein Koordinator assoziiert, der verantwortlich für "
+"das Steuern des Transaktionsergebnisses ist. Der Koordinator kann als "
+"separater Dienst implementiert werden, oder er kann beim Benutzer "
+"angesiedelt werden für bessere Leistung. Jeder Koordinator wird vom "
+"Transaktionsmanagerdienst erstellt, der in der Tat die Factory für solche "
+"Koordinatoren ist."
+
+#. Tag: para
+#: Transactions_Overview.xml:50
+#, no-c-format
+msgid ""
+"A coordinator communicates with enrolled participants to inform them of the "
+"desired termination requirements, for instance, whether they should accept "
+"(for example, confirm) or reject (for example, cancel) the work done within "
+"the scope of the given transaction. For example, whether to purchase the "
+"(provisionally reserved) flight tickets for the user or to release them. An "
+"application/client may wish to terminate a transaction in a number of "
+"different ways (for example, confirm or cancel). However, although the "
+"coordinator will attempt to terminate in a manner consistent with that "
+"desired by the client, it is ultimately the interactions between the "
+"coordinator and the participants that will determine the actual final "
+"outcome."
+msgstr ""
+"Ein Koordinator kommuniziert mit angemeldeten Teilnehmern und informiert sie "
+"über die gewünschten Terminierungsanforderungen, z. B. ob sie die im Scope "
+"der fraglichen Transaktion erledigte Arbeit akzeptieren (z. B. \"confirm\") "
+"oder ablehnen (z. B. \"cancel\") sollen; beispielsweise, ob die (vorläufig "
+"reservierten) Flugtickets für den Benutzer gekauft oder wieder freigegeben "
+"werden sollen. Eine Anwendung bzw. ein Benutzer kann die Transaktion auf "
+"verschiedenste Weisen beenden wollen (z. B. bestätigen \"confirm\" oder "
+"abbrechen \"cancel\"). Obwohl der Koordinator versuchen wird, auf eine Weise "
+"zu beenden, die konsistent ist mit der vom Client gewünschten, so sind es "
+"doch letztendlich die Interaktionen zwischen dem Koordinator und den "
+"Teilnehmern, die das Endergebnis bestimmen."
+
+#. Tag: para
+#: Transactions_Overview.xml:53
+#, no-c-format
+msgid ""
+"A transaction manager is typically responsible for managing coordinators for "
+"many transactions. The initiator of the transaction (for example, the "
+"client) communicates with a transaction manager and asks it to start a new "
+"transaction and associate a coordinator with the transaction. Once created, "
+"the context can be propagated to Web services in order for them to associate "
+"their work with the transaction."
+msgstr ""
+"Ein Transaktionsmanager ist normalerweise verantwortlich für die Steuerung "
+"von Koodinatoren vieler Transaktionen. Der Initiator der Transaktion (z. B. "
+"der Client) kommuniziert mit einem Transaktionsmanager und fordert ihn dazu "
+"auf, eine neue Transaktion zu starten und einen Koordinator mit der "
+"Transaktion zu assoziieren. Einmal erstellt, kann der Kontext an Web "
+"Services fortgepflanzt werden, damit diese ihre Arbeit mit der Transaktion "
+"assoziieren können."
+
+#. Tag: title
+#: Transactions_Overview.xml:57
+#, no-c-format
+msgid "The Transaction Context"
+msgstr "Der Transaktionskontext"
+
+#. Tag: para
+#: Transactions_Overview.xml:58
+#, no-c-format
+msgid ""
+"In order for a transaction to span a number of services, certain information "
+"has to be shared between those services in order to propagate information "
+"about the transaction. This information is known as the Context. Using XTS, "
+"the context is automatically propagated and processed by transaction-aware "
+"components of an application. Though XTS removes most of the work associated "
+"with propagating contexts, it is still instructive to understand what "
+"information is captured in a context:"
+msgstr ""
+"Damit sich eine Transaktion über eine Reihe von Services erstrecken kann, "
+"müssen bestimmte Informationen von diesen Services gemeinsam genutzt werden, "
+"um Informationen über die Transaktion fortzupflanzen. Diese Information ist "
+"bekannt als der Kontext. Wird XTS verwendet, so wird der Kontext automatisch "
+"fortgepflanzt und verarbeitet von transaktionssicheren Komponenten einer "
+"Anwendung. Obwohl XTS den Großteil der mit der Fortpflanzung von Kontexten "
+"verbundenen Arbeit abnimmt, ist es dennoch aufschlussreich zu verstehen, "
+"welche Informationen in einem Kontext erfasst sind:"
+
+#. Tag: para
+#: Transactions_Overview.xml:64
+#, no-c-format
+msgid ""
+"A transaction identifier which guarantees global uniqueness for an "
+"individual transaction;"
+msgstr ""
+"Ein Transaktions-Identifier, der globale Eindeutigkeit garantiert für eine "
+"individuelle Transaktion;"
+
+#. Tag: para
+#: Transactions_Overview.xml:69
+#, no-c-format
+msgid ""
+"The transaction coordinator location or endpoint address so participants can "
+"be enrolled."
+msgstr ""
+"Die Adresse des Transaktionskoordinators oder die Endpunktadresse, so dass "
+"Teilnehmer angemeldet werden können."
+
+#. Tag: caption
+#: Transactions_Overview.xml:78
+#, no-c-format
+msgid "Web Services and Context Flow"
+msgstr "Web Services und Kontextfluss"
+
+#. Tag: para
+#: Transactions_Overview.xml:80
+#, no-c-format
+msgid ""
+"As shown in Figure 2, whenever an application message is sent, the XTS "
+"Client API automatically creates a context and embeds it into the message. "
+"Similarly, any transaction-aware services are able to extract that context "
+"using the XTS service-side infrastructure and use it to perform work within "
+"the context of a particular transaction – even though that transaction was "
+"initiated elsewhere on the Web! The value of this approach is that the "
+"business logic contained within the client application and services are not "
+"peppered with transaction-processing code."
+msgstr ""
+"Wie in Abbildung 2 dargestellt, erstellt die XTS Client API automatisch "
+"einen Kontext und bettet ihn in eine Nachricht ein, sobald eine "
+"Anwendungsnachricht gesendet wird. Ebenso können jegliche "
+"transaktionssicheren Services den Kontext extrahieren mittels der XTS server-"
+"seitigen Infrastruktur und diesen nutzen für Arbeiten innerhalb des "
+"Kontextes einer bestimmten Transaktion – und das, obwohl die Transaktion an "
+"ganz anderer Stelle im Web initiiert wurde. Der Vorteil dieser "
+"Herangehensweise ist, dass die in der Client-Anwendung und den Services "
+"enthaltene Business-Logik nicht mit transaktionsverarbeitendem Code übersät "
+"wird."
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr "ACID-Transaktionen"
+
+#. Tag: para
+#: Transactions_Overview.xml:85
+#, no-c-format
+msgid ""
+"Traditionally, transaction processing systems support ACID properties. ACID "
+"is an acronym for Atomic, Consistent, Isolated, and Durable. A unit of work "
+"has traditionally been considered transactional only if the ACID properties "
+"are maintained:"
+msgstr ""
+"Traditionell unterstützen transaktionsverarbeitende Systeme ACID-"
+"Eigenschaften. ACID steht für \"Atomic\", \"Consistent\", \"Isolated\", und "
+"\"Durable\". Eine Einheit von Arbeiten wurde traditionell nur dann als "
+"Transaktion betrachtet, wenn die ACID-Eigenschaften aufrecht erhalten wurden:"
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr ""
+"Atomarität: Die Transaktion wird vollständig ausgeführt oder gar nicht."
+
+#. Tag: para
+#: Transactions_Overview.xml:96
+#, no-c-format
+msgid ""
+"Consistency: The effects of the transaction preserve the internal "
+"consistency of an underlying data structure."
+msgstr ""
+"Konsistenz: Die Auswirkungen der Transaktion erhalten die interne Konsistenz "
+"einer zugrunde liegenden Datenstruktur."
+
+#. Tag: para
+#: Transactions_Overview.xml:101
+#, no-c-format
+msgid ""
+"Isolated: The transaction runs as if it were running alone with no other "
+"transactions running and is not visible to other transactions."
+msgstr ""
+"Isolation: Die Transaktion läuft so, als sei es die einzig laufende ohne "
+"andere laufende Transaktionen, und sie ist nicht sichtbar für andere "
+"Transaktionen."
+
+#. Tag: para
+#: Transactions_Overview.xml:106
+#, no-c-format
+msgid ""
+"Durable: the transaction’s results will not be lost in the event of a "
+"failure."
+msgstr ""
+"Dauerhaftigkeit: Die Ergebnisse der Transaktion werden im Falle eines "
+"Fehlers nicht verloren gehen."
+
+#. Tag: title
+#: Transactions_Overview.xml:112
+#, no-c-format
+msgid "Two-Phase Commit"
+msgstr "Zwei-Phasen Festschreibung"
+
+#. Tag: para
+#: Transactions_Overview.xml:113
+#, no-c-format
+msgid ""
+"The classical two-phase commit approach is the bedrock of JBossTS (and more "
+"generally of Web Services transactions). Two-phase commit provides "
+"coordination of parties that are involved in a transaction. In general, the "
+"flow of a two-phase commit transaction is as follows:"
+msgstr ""
+"Die klassische Herangehensweise der zwei-Phasen Festschreibung (\"two-phase "
+"commit\", kurz 2PC) ist der Grundstein von JBossTS (und allgemein für Web "
+"Services Transaktionen). Zwei-Phasen Festschreibung liefert die Koordination "
+"von Parteien, die an einer Transaktion beteiligt sind. Generell verläuft "
+"eine zwei-Phasen Festschreibungstransaktion wie folgt:"
+
+#. Tag: para
+#: Transactions_Overview.xml:119
+#, no-c-format
+msgid "A transaction is started, and some work is performed."
+msgstr "Eine Transaktion wird gestartet und einige Arbeiten werden ausgeführt."
+
+#. Tag: para
+#: Transactions_Overview.xml:124
+#, no-c-format
+msgid "Once the work is finished, the two-phase commit begins."
+msgstr "Sobald die Arbeit beendet ist, beginnt die zwei-Phasen Festschreibung."
+
+#. Tag: para
+#: Transactions_Overview.xml:129
+#, no-c-format
+msgid ""
+"The coordinator (transaction manager) of the transaction asks each resource "
+"taking part in the transaction whether it is prepared to commit."
+msgstr ""
+"Der Koordinator (Transaktionsmanager) der Transaktion fragt jede an der "
+"Transaktion beteiligte Ressource, ob sie bereit ist festzuschreiben."
+
+#. Tag: para
+#: Transactions_Overview.xml:134
+#, no-c-format
+msgid ""
+"If all resources respond positively, the coordinator instructs all work "
+"performed to be made durable (usually committed to a database)."
+msgstr ""
+"Falls alle Ressourcen positiv antworten, weist der Koordinator an, alle "
+"ausgeführten Arbeiten dauerhaft zu machen (in der Regel festschreiben in "
+"einer Datenbank)."
+
+#. Tag: para
+#: Transactions_Overview.xml:139
+#, no-c-format
+msgid ""
+"If not, all work performed is rolled back (undone) such that the underlying "
+"data structures are in their original states."
+msgstr ""
+"Falls nicht, werden alle ausgeführten Arbeiten zurückgesetzt (rückgängig "
+"gemacht, \"rollback\"), so dass die zugrunde liegende Datenstrukturen in "
+"ihrem ursprünglichen Zustand sind."
+
+#. Tag: caption
+#: Transactions_Overview.xml:148
+#, no-c-format
+msgid "The Two-Phase Commit Protocol"
+msgstr "Das zwei-Phasen Festschreibungsprotokoll"
+
+#. Tag: para
+#: Transactions_Overview.xml:151
+#, no-c-format
+msgid ""
+"During two-phase commit transactions, coordinators and resources keep track "
+"of activity in non-volatile data stores so that they can recover in the case "
+"of a failure."
+msgstr ""
+"Während zwei-Phasen Festschreibungstransaktionen verfolgen Koordinatoren und "
+"Ressourcen die Aktivität in nicht-volatilen Datenspeichern nach, so dass sie "
+"im Fehlerfall wiederherstellen können."
+
+#. Tag: title
+#: Transactions_Overview.xml:156
+#, no-c-format
+msgid "The synchronization protocol"
+msgstr "Das Synchronisationsprotokoll"
+
+#. Tag: para
+#: Transactions_Overview.xml:157
+#, no-c-format
+msgid ""
+"As well as the two-phase commit protocol, traditional transaction processing "
+"systems employ an additional protocol, often referred to as the "
+"synchronization protocol. If you recall the original ACID properties, then "
+"you’ll remember that Durability is important in the case where state changes "
+"have to be available despite failures. What this means is that applications "
+"interact with a persistence store of some kind (e.g., a database) and this "
+"can impose a significant overhead – disk access is orders of magnitude "
+"slower than access to main computer memory."
+msgstr ""
+"Neben dem zwei-Phasen Festschreibungsprotokoll benutzen traditionelle "
+"transaktionsverarbeitende Systeme ein zusätzliches Protokoll, oft "
+"Synchronisationsprotokoll genannt. Wenn Sie sich die ACID-Eigenschaften "
+"wieder ins Gedächtnis rufen, dann werden sie sich erinnern, dass "
+"Dauerhaftigkeit wichtig ist für den Fall, dass Zustandsänderungen trotz "
+"Fehlern verfügbar sein müssen. Das bedeutet, dass Anwendungen mit einer Form "
+"persistenten Speichers (z. B. einer Datenbank) interagieren und dies einen "
+"signifikanten Overhead verursachen kann – der Plattenzugriff ist um "
+"Größenordnungen langsamer als der Zugriff auf den Hauptspeicher des "
+"Computers."
+
+#. Tag: para
+#: Transactions_Overview.xml:161
+#, no-c-format
+msgid ""
+"One apparently obvious solution to this problem would be to cache the state "
+"in main memory and only operate on that for the duration of a transaction. "
+"Unfortunately you’d then need some way of being able to flush the state back "
+"to the persistent store before the transaction terminates, or risk losing "
+"the full ACID properties. This is what the synchronization protocol does, "
+"with Synchronization participants."
+msgstr ""
+"Eine scheinbar offensichtliche Lösung dieses Problems wäre, den Zustand im "
+"Hauptspeicher zwischenzuspeichern, und für die Dauer der Transaktion nur "
+"damit zu operieren. Allerdings benötigen Sie dann einen Weg, den Zustand im "
+"persistenten Speicher zurückzuschreiben (\"flush\"), bevor die Transaktion "
+"endet, oder Sie riskieren den Verlust sämtlicher ACID-Eigenschaften. Genau "
+"das übernimmt das Synchronisationsprotokoll mit Synchronisationsteilnehmern."
+
+#. Tag: para
+#: Transactions_Overview.xml:164
+#, no-c-format
+msgid ""
+"Synchronizations are informed that a transaction is about to commit, so they "
+"can, for example, flush cached state, which may be being used to improve "
+"performance of an application, to a durable representation prior to the "
+"transaction committing. They are then informed when the transaction has "
+"completed and in what state it completed."
+msgstr ""
+"Synchronisationen werden darüber informiert, dass eine Transaktion im "
+"Begriff ist festzuschreiben, woraufhin sie den zwischengespeicherten Zustand "
+"zurückschreiben können (was dazu benutzt werden kann, die Leistung einer "
+"Anwendung zu verbessern) in eine dauerhafte Repräsentation, bevor die "
+"Transaktion festschreibt. Sie werden anschließend darüber informiert, dass "
+"und in welchem Zustand die Transaktion abgeschlossen wurde."
+
+#. Tag: para
+#: Transactions_Overview.xml:169
+#, no-c-format
+msgid ""
+"Synchronizations essentially turn the two-phase commit protocol into a four-"
+"phase protocol:"
+msgstr ""
+"Synchronisationen machen aus dem zwei-Phasen Festschreibungsprotokoll "
+"tatsächlich ein vier-Phasen Protokoll:"
+
+#. Tag: para
+#: Transactions_Overview.xml:174
+#, no-c-format
+msgid ""
+"Before the transaction starts the two-phase commit, all registered "
+"Synchronizations are informed. Any failure at this point will cause the "
+"transaction to roll back."
+msgstr ""
+"Bevor die Transaktion die zwei-Phasen Festschreibung startet, werden alle "
+"registrierten Synchronisationen informiert. Jedweder Fehler an diesem Punkt "
+"wird zum Zurücksetzen der Transaktion führen."
+
+#. Tag: para
+#: Transactions_Overview.xml:179
+#, no-c-format
+msgid "The coordinator then conducts the normal two-phase commit protocol."
+msgstr ""
+"Der Koordinator führt anschließend das normale zwei-Phasen Protokoll aus."
+
+#. Tag: para
+#: Transactions_Overview.xml:184
+#, no-c-format
+msgid ""
+"Once the transaction has terminated, all registered Synchronizations are "
+"informed. However, this is a courtesy invocation because any failures at "
+"this stage are ignored: the transaction has terminated so there’s nothing to "
+"affect."
+msgstr ""
+"Sobald die Transaktion beendet wurde, werden alle registrierten "
+"Synchronisationen informiert. Allerdings ist dies nur ein \"Höflichkeits-"
+"Aufruf\", denn etwaige Fehler zu diesem Zeitpunkt werden ignoriert: Die "
+"Transaktion wurde beendet, kann also nicht mehr beeinflusst werden."
+
+#. Tag: para
+#: Transactions_Overview.xml:189
+#, no-c-format
+msgid ""
+"Unlike the two-phase commit protocol, the synchronization protocol does not "
+"have the same failure requirements. For example, Synchronization "
+"participants don’t need to make sure they can recover in the event of "
+"failures; this is because any failure before the two-phase commit protocol "
+"completes means the transaction will roll back, and failures after it has "
+"completed can’t affect the data the Synchronization participants were "
+"managing."
+msgstr ""
+"Anders als das zwei-Phasen Festschreibungsprotokoll hat das "
+"Synchronisationsprotokoll nicht dieselben Fehleranforderungen. So müssen "
+"Synchronisationsteilnehmer beispielsweise nicht sicherstellen, dass sie im "
+"Fehlerfall wiederherstellen können, denn jeder Fehler vor Abschluss der zwei-"
+"Phasen Festschreibung bedeutet, dass die Transaktion zurückgesetzt wird, und "
+"Fehler nach deren Abschluss haben keine Auswirkungen mehr auf die vom "
+"Synchronisationsteilnehmer gesteuerten Daten."
+
+#. Tag: title
+#: Transactions_Overview.xml:193
+#, no-c-format
+msgid "Optimizations to the protocol"
+msgstr "Optimierungen des Protokolls"
+
+#. Tag: para
+#: Transactions_Overview.xml:194
+#, no-c-format
+msgid ""
+"There are several variants to the standard two-phase commit protocol that "
+"are worth knowing about because they can have an impact on performance and "
+"failure recovery. We shall briefly describe those that are the most common "
+"variants on the protocol:"
+msgstr ""
+"Es gibt mehrere Varianten zum Standard des zwei-Phasen "
+"Festschreibungsprotokolls, die Sie kennen sollten, denn sie haben "
+"Auswirkungen auf die Leistung und die Recovery bei Fehlern. Wir werden hier "
+"kurz die am weitesten verbreiteten Varianten des Protokolls beschreiben:"
+
+#. Tag: para
+#: Transactions_Overview.xml:200
+#, no-c-format
+msgid ""
+"Presumed abort: if a transaction is going to roll back then it may simply "
+"record this information locally and tell all enlisted participants. Failure "
+"to contact a participant has no affect on the transaction outcome; the "
+"transaction is effectively informing participants as a courtesy. Once all "
+"participants have been contacted the information about the transaction can "
+"be removed. If a subsequent request for the status of the transaction occurs "
+"there will be no information available and the requestor can assume that the "
+"transaction has aborted (rolled back). This optimization has the benefit "
+"that no information about participants need be made persistent until the "
+"transaction has decided to commit (i.e., progressed to the end of the "
+"prepare phase), since any failure prior to this point will be assumed to be "
+"an abort of the transaction."
+msgstr ""
+"Presumed Abort: Wenn eine Transaktion zurückgesetzt werden wird, kann sie "
+"diese Information einfach lokal speichern und allen angemeldeten Teilnehmern "
+"mitteilen. Kann ein Teilnehmer nicht erreicht werden, so hat dies keine "
+"Auswirkungen auf das Ergebnis der Transaktion; die Transaktion informiert "
+"die Teilnehmer nur aus \"Höflichkeit\". Sobald alle Teilnehmer kontaktiert "
+"wurden, kann die Information über die Transaktion gelöscht werden. Falls "
+"eine nachfolgende Anfrage zum Zustand der Transaktion eingeht, wird keine "
+"Information mehr verfügbar sein, und der Anfrager kann annehmen, dass die "
+"Transaktion abgebrochen (zurückgesetzt) wurde. Diese Optimierung hat den "
+"Vorteil, dass keine Information über Teilnehmer persistent gemacht werden "
+"muss, bevor die Transaktion entschieden hat festzuschreiben (sie also bis "
+"zum Ende der Vorbereitungsphase fortgeschritten ist), denn jeglicher Fehler "
+"vor diesem Zeitpunkt wird als Abbruch der Transaktion angenommen."
+
+#. Tag: para
+#: Transactions_Overview.xml:205
+#, no-c-format
+msgid ""
+"One-phase: if there is only a single participant involved in the "
+"transaction, the coordinator need not drive it through the prepare phase. "
+"Thus, the participant will simply be told to commit and the coordinator need "
+"not record information about the decision since the outcome of the "
+"transaction is solely down to the participant."
+msgstr ""
+"Eine-Phase: Wenn nur ein Teilnehmer an einer Transaktion beteiligt ist, "
+"braucht der Koordinator ihn nicht durch die Vorbereitungsphase zu führen. "
+"Folglich wird der Teilnehmer einfach aufgefordert festzuschreiben, und der "
+"Koordinator braucht keine Informationen zu speichern über die Entscheidung, "
+"denn das Ergebnis der Transaktion hängt allein von diesem einen Teilnehmer "
+"ab."
+
+#. Tag: para
+#: Transactions_Overview.xml:210
+#, no-c-format
+msgid ""
+"Read-only: when a participant is asked to prepare, it can indicate to the "
+"coordinator that no information or data that it controls has been modified "
+"during the transaction. Such a participant does not need to be informed "
+"about the outcome of the transaction since the fate of the participant has "
+"no affect on the transaction. As such, a read-only participant can be "
+"omitted from the second phase of the commit protocol."
+msgstr ""
+"Read-Only: Wenn ein Teilnehmer aufgefordert wird sich vorzubereiten, kann er "
+"dem Koordinator anzeigen, dass keine von ihm kontrollierten Informationen "
+"oder Daten verändert wurden während der Transaktion. Solch ein Teilnehmer "
+"muss nicht über das Ergebnis der Transaktion informiert werden, da das "
+"Schicksal des Teilnehmers keinen Einfluss hat auf die Transaktion. Aus "
+"diesem Grund kann ein Read-Only Teilnehmer ab der zweiten Phase des "
+"Festschreibungsprotokolls ausgelassen werden."
+
+#. Tag: title
+#: Transactions_Overview.xml:216
+#, no-c-format
+msgid "Non-atomic transactions and heuristic outcomes"
+msgstr "Nicht-atomische Transaktionen und heuristische Ergebnisse"
+
+#. Tag: para
+#: Transactions_Overview.xml:217
+#, no-c-format
+msgid ""
+"In order to guarantee atomicity, the two-phase commit protocol is "
+"necessarily blocking. What this means is that as a result of failures, "
+"participants may remain blocked for an indefinite period of time even if "
+"failure recovery mechanisms exist. Some applications and participants simply "
+"cannot tolerate this blocking."
+msgstr ""
+"Um Atomarität zu gewährleisten, muss das zwei-Phasen "
+"Festschreibungsprotokoll notwendigerweise sperren. Dies bedeutet, dass als "
+"Folge von Fehlern Teilnehmer für unbestimmte Zeit gesperrt bleiben können, "
+"selbst wenn ein Mechanismus zur Fehler-Recovery existiert. Einige "
+"Anwendungen und Teilnehmer können diese Sperre einfach nicht tolerieren."
+
+#. Tag: para
+#: Transactions_Overview.xml:221
+#, no-c-format
+msgid ""
+"To break this blocking nature, participants that have got past the prepare "
+"phase are allowed to make autonomous decisions as to whether they commit or "
+"rollback: such a participant must record this decision in case it is "
+"eventually contacted to complete the original transaction. If the "
+"coordinator eventually informs the participant of the transaction outcome "
+"and it is the same as the choice the participant made, then there’s no "
+"problem. However, if it is contrary, then a non-atomic outcome has obviously "
+"happened: a heuristic outcome."
+msgstr ""
+"Um das Problem dieser Sperren zu umgehen, wird es Teilnehmern, welche die "
+"Vorbereitungsphase passiert haben, gestattet, autonome Entscheidungen zu "
+"treffen, ob sie festschreiben oder zurücksetzen: Solch ein Teilnehmer muss "
+"diese Entscheidung aufzeichnen für den Fall, dass er aufgefordert wird, die "
+"ursprüngliche Transaktion abzuschließen. Wenn der Koordinator den Teilnehmer "
+"schließlich über das Ergebnis der Transaktion informiert, und es dasselbe "
+"Ergebnis ist wie auch das vom Teilnehmer gewählte, dann besteht kein "
+"Problem. Wenn die Entscheidung jedoch gegenteilig ausfiel, ist "
+"offensichtlich ein nicht-atomisches Ergebnis aufgetreten: ein heuristisches "
+"Ergebnis."
+
+#. Tag: para
+#: Transactions_Overview.xml:224
+#, no-c-format
+msgid ""
+"How this heuristic outcome is reported to the application and resolved is "
+"usually the domain of complex, manually driven system administration tools, "
+"since in order to attempt an automatic resolution requires semantic "
+"information about the nature of participants involved in the transactions."
+msgstr ""
+"Wie dieses heuristische Ergebnis an die Anwendung gemeldet und aufgelöst "
+"wird, ist in der Regel die Domäne von komplexen, manuell gesteuerten "
+"Administrations-Tools, denn der Versuch einer automatisierten Lösung würde "
+"semantische Informationen über die Art der an den Transaktionen beteiligten "
+"Teilnehmer erfordern."
+
+#. Tag: para
+#: Transactions_Overview.xml:227
+#, no-c-format
+msgid ""
+"Precisely when a participant makes a heuristic decision is obviously "
+"implementation dependant. Likewise, the choice the participant makes (to "
+"commit or to roll back) will depend upon the implementation and possibly the "
+"application/environment in which it finds itself. The possible heuristic "
+"outcomes are:"
+msgstr ""
+"Wann genau ein Teilnehmer eine heuristische Entscheidung trifft ist "
+"selbstverständlich abhängig von der Implementierung. Ebenso hängt auch die "
+"vom Teilnehmer getroffene Wahl (festzuschreiben oder zurückzusetzen) ab von "
+"der Implementierung sowie möglicherweise von der Anwendung/Umgebung, in der "
+"er sich befindet. Die möglichen heuristischen Ergebnisse sind:"
+
+#. Tag: para
+#: Transactions_Overview.xml:232
+#, no-c-format
+msgid ""
+"Heuristic rollback: the commit operation failed because some or all of the "
+"participants unilaterally rolled back the transaction."
+msgstr ""
+"Heuristisches Zurücksetzen: Die Festschreibungsoperation schlug fehl, weil "
+"einige oder alle Teilnehmer die Transaktion einseitig zurückgesetzt haben."
+
+#. Tag: para
+#: Transactions_Overview.xml:237
+#, no-c-format
+msgid ""
+"Heuristic commit: an attempted rollback operation failed because all of the "
+"participants unilaterally committed. This may happen if, for example, the "
+"coordinator was able to successfully prepare the transaction but then "
+"decided to roll it back (for example, it could not update its log) but in "
+"the meanwhile the participants decided to commit."
+msgstr ""
+"Heuristisches Festschreiben: Eine versuchte Operation zum Zurücksetzen "
+"schlug fehl, weil alle Teilnehmer einseitig festgeschrieben haben. Dies kann "
+"passieren, wenn z. B. der Koordinator erfolgreich die Transaktion "
+"vorbereiten konnte, dann aber entschied, sie zurückzusetzen (z. B. konnte er "
+"sein Protokoll nicht aktualisieren), während jedoch in der Zwischenzeit die "
+"Teilnehmer sich dazu entschieden festzuschreiben."
+
+#. Tag: para
+#: Transactions_Overview.xml:242
+#, no-c-format
+msgid ""
+"Heuristic mixed: some updates (participants) were committed while others "
+"were rolled back."
+msgstr ""
+"Heuristischer Mix: Einige Aktualisierungen (Teilnehmer) wurden "
+"festgeschrieben, während andere zurückgesetzt wurden."
+
+#. Tag: para
+#: Transactions_Overview.xml:247
+#, no-c-format
+msgid ""
+"Heuristic hazard: the disposition of some of the updates is unknown. For "
+"those which are known, they have either all been committed or all rolled "
+"back."
+msgstr ""
+"Heuristische Gefahr: Die Art einiger Aktualisierungen ist unbekannt. "
+"Diejenigen, die bekannt sind, wurden entweder alle festgeschrieben oder alle "
+"zurückgesetzt."
+
+#. Tag: para
+#: Transactions_Overview.xml:252
+#, no-c-format
+msgid ""
+"Heuristic decisions should be used with care and only in exceptional "
+"circumstances since there is the possibility that the decision will differ "
+"from that determined by the transaction service and will thus lead to a loss "
+"of integrity in the system. Having to perform resolution of heuristics is "
+"something you should try to avoid, either by working with services/"
+"participants that don’t cause heuristics, or by using a transaction service "
+"that provides assistance in the resolution process."
+msgstr ""
+"Heuristische Entscheidungen sollten mit Vorsicht und nur unter "
+"außergewöhnlichen Umständen verwendet werden, da die Möglichkeit besteht, "
+"dass die Entscheidung sich unterscheidet von jener, die durch den "
+"Transaktionsdienst bestimmt wurde, und es infolgedessen zum Verlust der "
+"Integrität im System führen kann. Das Auflösen von Heuristiken ist etwas, "
+"was Sie versuchen sollten zu vermeiden, entweder durch den Einsatz von "
+"Services/Teilnehmern, die keine Heuristiken verursachen, oder indem Sie "
+"einen Transaktionsdienst verwenden, der Hilfestellung anbietet beim Prozess "
+"des Auflösens."
+
+#. Tag: title
+#: Transactions_Overview.xml:256
+#, no-c-format
+msgid "A New Transaction Protocol"
+msgstr "Ein neues Transaktionsprotokoll"
+
+#. Tag: para
+#: Transactions_Overview.xml:257
+#, no-c-format
+msgid ""
+"Many component technologies offer mechanisms for coordinating ACID "
+"transactions based on two-phase commit semantics (i.e., CORBA/OTS, JTS/JTA, "
+"MTS/MSDTC). ACID transactions are not suitable for all Web services "
+"transactions since:"
+msgstr ""
+"Viele Komponententechnologien bieten Mechanismen zur Koordination von ACID-"
+"Transaktionen basierend auf zwei-Phasen Festschreibungssemantik (d. h. CORBA/"
+"OTS, JTS/JTA, MTS/MSDTC). ACID-Transaktionen sind nicht für alle Web "
+"Services Transaktionen geeignet, denn:"
+
+#. Tag: para
+#: Transactions_Overview.xml:263
+#, no-c-format
+msgid ""
+"Classic ACID transactions are predicated on the idea that an organization "
+"that develops and deploys applications does so using their own "
+"infrastructure, typically an Intranet. Ownership meant transactions operated "
+"in a trusted and predictable manner. To assure ACIDity, potentially long-"
+"lived locks could be kept on underlying data structures during two-phase "
+"commit. Resources could be used for any period of time and released when the "
+"transaction was complete. In the Web services arena, these assumptions are "
+"no longer valid. One obvious reason is that the owners of data exposed "
+"through a Web service will refuse to allow their data to be locked for "
+"extended periods since to allow such locks invites denial-of-service."
+msgstr ""
+"Klassische ACID-Transaktionen gründen auf der Annahme, dass eine "
+"Organisation, die Anwendungen entwickelt und einsetzt, dies unter der "
+"Verwendung ihrer eigenen Infrastruktur tut, typischerweise ein Intranet. "
+"Eigentümerschaft bedeutete, dass Transaktionen auf zuverlässige und "
+"vorhersehbare Weise operierten. Um die ACID-Eigenschaften zu gewährleisten, "
+"konnten potenziell langlebige Sperren auf zugrunde liegenden Datenstrukturen "
+"beibehalten werden während der zwei-Phasen-Festschreibung. Ressourcen "
+"konnten beliebig lange genutzt werden und nach Abschluss der Transaktion "
+"wieder freigegeben werden. In der Web Services Arena sind diese Annahmen "
+"nicht länger gültig. Ein offensichtlicher Grund ist, dass die Besitzer der "
+"(durch einen Web Service offengelegten) Daten eine längere Sperrung seiner "
+"Daten ablehnen wird, denn solche Sperren zu erlauben, kann einen Denial-of-"
+"Service ermöglichen."
+
+#. Tag: para
+#: Transactions_Overview.xml:268
+#, no-c-format
+msgid ""
+"All application infrastructures are generally owned by a single party, "
+"systems using classical ACID transactions normally assume that participants "
+"in a transaction will obey the will of the transaction manager and only "
+"infrequently decide to make unilateral decisions which will hamper other "
+"participants in a transaction. On the contrary, Web services participating "
+"in a transaction can effectively decide to resign from the transaction at "
+"any time, and the consumer of the service generally has little in the way of "
+"quality of service guarantees to prevent this."
+msgstr ""
+"Alle Anwendungsinfrastrukturen gehören in der Regel einer einzigen Partei. "
+"Systeme, die klassische ACID-Transaktionen verwenden, nehmen normalerweise "
+"an, dass Teilnehmer einer Transaktion dem Willen des Transaktionsmanagers "
+"gehorchen und nur selten einseitige Entscheidungen treffen, welche andere "
+"Teilnehmer in einer Transaktion behindern. Im Gegensatz dazu können an einer "
+"Transaktion beteiligte Web Services effektiv jederzeit entscheiden, aus "
+"einer Transaktion auszutreten, und der Konsument des Services hat nur wenig "
+"Handhabe im Sinne von Service-Qualitätsgarantien um dies zu verhindern."
+
+#. Tag: title
+#: Transactions_Overview.xml:274
+#, no-c-format
+msgid "Adressing the Problems of Transactioning in Loosely Coupled Systems"
+msgstr "Angehen von Problemen bei Transaktionen in lose gekoppelten Systemen"
+
+#. Tag: para
+#: Transactions_Overview.xml:275
+#, no-c-format
+msgid ""
+"Though extended transaction models which relax the ACID properties have been "
+"proposed over the years, to implement these concepts for the Web services "
+"architecture WS-T provides a new transaction protocol. XTS is designed to "
+"accommodate four underlying requirements inherent in any loosely coupled "
+"architecture like Web services:"
+msgstr ""
+"Obwohl über die Jahre erweiterte Transaktionsmodelle vorgeschlagen wurden, "
+"die die ACID-Eigenschaften lockern, liefert WS-T ein neues "
+"Transaktionsprotokoll, welches diese Konzepte für die Web Services "
+"Architektur implementieren. XTS wurde entworfen, vier zugrunde liegenden "
+"Anforderungen Rechnung zu tragen, die allen lose gekoppelten Architekturen "
+"wie Web Services gemein sind:"
+
+#. Tag: para
+#: Transactions_Overview.xml:281
+#, no-c-format
+msgid ""
+"Ability to handle multiple successful outcomes to a transaction, with the "
+"ability to involve operations whose effects may not be isolated or durable;"
+msgstr ""
+"Fähigkeit, mit mehreren erfolgreichen Ergebnissen für eine Transaktion "
+"umzugehen, mit der Fähigkeit Operationen einzubeziehen, deren Auswirkungen "
+"ggf. nicht isoliert oder dauerhaft sind;"
+
+#. Tag: para
+#: Transactions_Overview.xml:286
+#, no-c-format
+msgid ""
+"Coordination of autonomous parties whose relationships are governed by "
+"contracts rather than the dictates of a central design authority;"
+msgstr ""
+"Koordination autonomer Parteien, deren Beziehungen gesteuert werden durch "
+"Verträge, und nicht durch das Diktakt einer zentralen Entwicklungsautorität;"
+
+#. Tag: para
+#: Transactions_Overview.xml:291
+#, no-c-format
+msgid ""
+"Discontinuous service, where parties are anticipated to suffer outages "
+"during their lifetime, and coordinated work must be able to survive such "
+"outages;"
+msgstr ""
+"Ausgesetzter Service, wobei mit Parteien gerechnet wird, die während ihrer "
+"Lebenszeit Ausfälle erleiden werden; koordinierte Arbeiten müssen fähig "
+"sein, solche Ausfälle zu verkraften;"
+
+#. Tag: para
+#: Transactions_Overview.xml:296
+#, no-c-format
+msgid ""
+"Interoperation using XML over multiple communication protocols – XTS chooses "
+"to use SOAP encoding carried over HTTP for the first release and other SOAP-"
+"friendly transports for future releases."
+msgstr ""
+"Zusammenarbeit mittels XML über multiple Kommunikationsprotokolle hinweg – "
+"XTS wählt SOAP-Encoding über HTTP für das erste Release, und andere SOAP-"
+"freundliche Transporte für zukünftige Releases."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/de-DE/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,1421 @@
+# translation of Stand-alone_Coordinator.po to
+# Language de-DE translations for  package.
+#
+# Automatically generated, 2008.
+# Hedda Peters <hpeters at redhat.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-16 16:35+1000\n"
+"Last-Translator: Hedda Peters <hpeters at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:6
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Overview"
+msgstr "WS-C, WS-Atomic Transaction und WS-Business Activity im Überblick"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Einführung"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:9
+#, no-c-format
+msgid ""
+"This section provides fundamental concepts associated with WS-C, WS-Atomic "
+"Transaction and WS-Business Activity. All of these concepts are defined in "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. WS-"
+"C, WS-Atomic Transaction and WS-Business Activity principles are discussed "
+"throughout this guide."
+msgstr ""
+"Dieser Abschnitt liefert fundamentale Konzepte in Bezug auf WS-C, WS-Atomic "
+"Transaction und WS-Business Activity. Jedes dieser Konzepte ist definiert in "
+"den WS-C, WS-Atomic Transaction und WS-Business Activity Spezifikationen. "
+"Die Prinzipien von WS-C, WS-Atomic Transaction und WS-Business Activity "
+"werden in diesem Handbuch erläutert."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:13
+#, no-c-format
+msgid ""
+"If you are well versed in the WS-C, WS-Atomic Transaction and WS-Business "
+"Activity specifications then you may want to just skim through this part of "
+"the manual."
+msgstr ""
+"Falls Sie sich mit den WS-C, WS-Atomic Transaction und WS-Business Activity "
+"Spezifikationen bereits gut auskennen, können Sie diesen Teil des Handbuches "
+"überfliegen."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr "WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:21
+#, no-c-format
+msgid ""
+"In general terms, coordination is the act of one entity (known as the "
+"coordinator) disseminating information to a number of participants for some "
+"domain-specific reason. This reason could be in order to reach consensus on "
+"a decision like in a distributed transaction protocol, or simply to "
+"guarantee that all participants obtain a specific message, as occurs in a "
+"reliable multicast environment. When parties are being coordinated, "
+"information known as the coordination context is propagated to tie together "
+"operations which are logically part of the same coordinated work or "
+"activity. This context information may flow with normal application "
+"messages, or may be an explicit part of a message exchange and is specific "
+"to the type of coordination being performed."
+msgstr ""
+"Allgemein gesprochen ist Koordination die Handlung einer Entity (bekannt als "
+"der Koordinator), Informationen an eine Reihe von Teilnehmern zu leiten aus "
+"einem domain-spezifischem Grund. Dieser Grund könnte sein, zu einer "
+"Übereinkunft bezüglich einer Entscheidung zu kommen wie in einem verteilten "
+"Transaktionsprotokoll, oder einfach um zu gewährleisten, dass alle "
+"Teilnehmer eine bestimmte Nachricht erhalten, wie es in einer zuverlässigen "
+"Multicast-Umgebung vorkommt. Wenn Parteien koordiniert werden, werden "
+"Informationen – bekannt als der Koordinationskontext – fortgepflanzt, um "
+"Operationen zusammenzufassen, welche logisch Teil derselben koordinierten "
+"Arbeit oder derselben Activity sind. Diese Kontextinformation kann mit den "
+"normalen Anwendungsnachrichten fließen, oder kann ein expliziter Teil eines "
+"Nachrichtenaustauschs sein, und ist spezifisch für den ausgeführten "
+"Koordinationstyp."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:24
+#, no-c-format
+msgid ""
+"The fundamental idea underpinning WS-Coordination is that there is a generic "
+"need for a coordination infrastructure in a Web services environment. The WS-"
+"Coordination specification defines a framework that allows different "
+"coordination protocols to be plugged-in to coordinate work between clients, "
+"services and participants, as shown in Figure 4."
+msgstr ""
+"Die fundamentale Annahme, die WS-Coordination zugrunde liegt, ist, dass es "
+"eine generische Notwendigkeit für eine Koordinationsinfrastruktur in einer "
+"Web Services Umgebung gibt. Die Spezifikationen für WS-Coordination "
+"definieren ein Framework, welches es ermöglicht, verschiedene "
+"Koordinationsprotokolle in koordinierte Arbeiten einzuhängen zwischen "
+"Clients, Services und Teilnehmern, wie in Abbildung 4 dargestellt."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:27
+#, no-c-format
+msgid ""
+"At this level, an activity is minimally specified and is simply created, "
+"made to run, and then completed."
+msgstr ""
+"Derzeit ist eine Activity nur minimal spezifiziert und wird einfach "
+"erstellt, zum Laufen gebracht, und dann abgeschlossen."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:34
+#, no-c-format
+msgid "WS-C architecture"
+msgstr "WS-C Architektur"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:36
+#, no-c-format
+msgid ""
+"Whatever coordination protocol is used, and in whatever domain it is "
+"deployed, the same generic requirements are present:"
+msgstr ""
+"Egal welches Koordinationsprotokoll verwendet wird, und egal in welcher "
+"Domain es eingesetzt wird, es liegen die gleichen generischen Anforderungen "
+"vor:"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:41
+#, no-c-format
+msgid ""
+"Instantiation (or activation) of a new coordinator for the specific "
+"coordination protocol, for a particular application instance;"
+msgstr ""
+"Instanzierung (oder Aktivierung) eines neuen Koordinators für das "
+"spezifische Koordinationsprotokoll, für eine bestimmte Anwendungsinstanz;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:46
+#, no-c-format
+msgid ""
+"Registration of participants with the coordinator, such that they will "
+"receive that coordinator’s protocol messages during (some part of) the "
+"application’s lifetime;"
+msgstr ""
+"Registrierung von Teilnehmern beim Koordinator, so dass sie die "
+"Protokollnachrichten des Koordinators während (eines Teils der) "
+"Anwendungslaufzeit empfängt;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:51
+#, no-c-format
+msgid ""
+"Propagation of contextual information between Web services that comprise the "
+"application;"
+msgstr ""
+"Fortpflanzung (\"Propagation\") von Kontextinformationen zwischen Web "
+"Services, die die Anwendung beinhalten;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:56
+#, no-c-format
+msgid "An entity to drive the coordination protocol through to completion."
+msgstr "Eine Entity zum Ausführen des Koordinationsprotokolls bis Abschluss."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:61
+#, no-c-format
+msgid ""
+"The first three of these points are directly the concern of WS-Coordination "
+"while the fourth is the responsibility of a third-party entity, usually the "
+"client application that controls the application as a whole. These four WS-"
+"Coordination roles and their interrelationships are shown in Figure 5."
+msgstr ""
+"Die ersten drei dieser Punkte sind direkte Verantwortlichkeiten der WS-"
+"Coordination, während der vierte in der Verantwortlichkeit einer Dritt-"
+"Entity liegt, in der Regel ist das die Client-Anwendung, welche die "
+"Anwendung als Ganzes steuert. Diese vier Rollen der WS-Coordination und ihre "
+"Beziehungen untereinander werden in Abbildung 5 gezeigt."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr "WS-C Infrastruktur"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:71
+#, no-c-format
+msgid "Activation"
+msgstr "Aktivierung"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:72
+#, no-c-format
+msgid ""
+"The WS-Coordination framework exposes an Activation Service which supports "
+"the creation of coordinators for specific protocols and their associated "
+"contexts. The process of invoking an activation service is done "
+"asynchronously, and so the specification defines both the interface of the "
+"activation service itself, and that of the invoking service, so that the "
+"activation service can call back to deliver the results of the activation – "
+"namely a context that identifies the protocol type and coordinator location. "
+"These interfaces are presented in Figure 6, where the activation service has "
+"a one-way operation that expects to receive a "
+"<code>CreateCoordinationContext</code> message and correspondingly the "
+"service that sent the <code>CreateCoordinationContext</code> message expects "
+"to be called back with a <code>CreateCoordinationContextResponse</code> "
+"message, or informed of a problem via an <code>Error</code> message."
+msgstr ""
+"Das Framework der WS-Coordination legt einen Aktivierungsdienst offen, der "
+"die Erstellung von Koordinatoren für spezifische Protokolle und ihren "
+"zugehörigen Kontexten unterstützt. Der Prozess des Aufrufens eines "
+"Aktivierungsdienstes wird asynchron ausgeführt, weshalb die Spezifikationen "
+"sowohl die Schnittstelle des Aktivierungsdienstes selbst definieren, als "
+"auch die des aufrufenden Services. Dadurch kann der Aktivierungsdienst "
+"zurückrufen, um das Ergebnis der Aktivierung zu liefern – nämlich einen "
+"Kontext, der den Protokolltyp und die Adresse des Koordinators "
+"identifiziert. Diese Schnittstellen sind in Abbildung 6 dargestellt, in der "
+"der Aktivierungsdienst eine einseitige Operation besitzt, welche den Empfang "
+"einer <code>CreateCoordinationContext</code>-Nachricht erwartet. "
+"Entsprechend erwartet der Dienst, der die <code>CreateCoordinationContext</"
+"code>-Nachricht gesendet hat, nun einen Rückruf mit einer "
+"<code>CreateCoordinationContextResponse</code>-Nachricht oder mit einer "
+"<code>Error</code>-Nachricht, um über Fehler informiert zu werden."
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:76
+#, no-c-format
+msgid ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+msgstr ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:78
+#, no-c-format
+msgid "Registration"
+msgstr "Registrierung"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:79
+#, no-c-format
+msgid ""
+"Once a coordinator has been instantiated and a corresponding context created "
+"by the activation service, a Registration Service is created and exposed. "
+"This service allows participants to register to receive protocol messages "
+"associated with a particular coordinator. Like the activation service, the "
+"registration service assumes asynchronous communication and so specifies "
+"WSDL for both registration service and registration requester, as shown "
+"below."
+msgstr ""
+"Sobald ein Koordinator instanziert und ein entsprechender Kontext erstellt "
+"wurde durch den Aktivierungsdienst, wird ein Registrierungsdienst erstellt "
+"und offengelegt. Dieser Dienst erlaubt es Teilnehmern, sich für den Empfang "
+"von Protokollnachrichten zu registrieren, die mit einem bestimten "
+"Koordinator assoziiert sind. Wie auch der Aktivierungsdienst nimmt der "
+"Registrierungsdienst asynchrone Kommunikation an, und spezifiziert daher "
+"WSDL für Registrierungsdienst und Registrierungsanfrager, wie unten gezeigt."
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:83
+#, no-c-format
+msgid ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+msgstr ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:84
+#, no-c-format
+msgid ""
+"When a participant is registered with a coordinator through the registration "
+"service, it receives messages that the coordinator sends (for example, "
+"“prepare to complete” and “complete” messages if a two-phase protocol is "
+"used); where the coordinator’s protocol supports it, participants can also "
+"send messages back to the coordinator."
+msgstr ""
+"Wenn ein Teilnehmer durch den Registrierungsdienst bei einem Koordinator "
+"angemeldet ist, empfängt er vom Koordinator versandte Nachrichten (z. B. "
+"\"prepare to complete\"- und \"complete\"-Nachrichten wenn ein zwei-Phasen "
+"Protokoll verwendet wird). Wo das Protokoll des Koordinators es unterstützt, "
+"können Teilnehmer auch Nachrichten an den Koordinator zurücksenden."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:88
+#, no-c-format
+msgid "Completion"
+msgstr "Abschluss"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:89
+#, no-c-format
+msgid ""
+"The role of terminator is generally played by the client application, which "
+"at an appropriate point will ask the coordinator to perform its particular "
+"coordination function with any registered participants – to drive the "
+"protocol through to its completion. On completion, the client application "
+"may be informed of an outcome for the activity which may vary from simple "
+"succeeded/failed notification through to complex structured data detailing "
+"the activity’s status."
+msgstr ""
+"Die Rolle des Terminators wird in der Regel von der Client-Anwendung "
+"übernommen, die zu einem angemessenen Zeitpunkt den Koordinator auffordern "
+"wird, seine Koordinationsfunktion an jeglichen beteiligten Teilnehmern "
+"auszuführen – das Protokoll abzuwickeln bis zu seinem Abschluss. Nach "
+"Abschluss kann die Client-Anwendung über das Ergebnis für die Activity "
+"informiert werden, was von simplen \"succeeded\"/\"failed\"-"
+"Benachrichtigungen bis hin zu komplex strukturierten Daten mit detailliertem "
+"Activity-Zustand reichen kann."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:96
+#, no-c-format
+msgid "WS-Transaction"
+msgstr "WS-Transaction"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:97
+#, no-c-format
+msgid ""
+"In the past, making traditional transaction systems talk to one another was "
+"a holy grail that was rarely achieved. With the advent of Web services, "
+"there is an opportunity to leverage an unparalleled interoperability "
+"technology to splice together existing transaction processing systems that "
+"already form the backbone of enterprise level applications."
+msgstr ""
+"In der Vergangenheit war es eine hohe Kunst und selten erfolgreich, "
+"traditionelle Transaktionssysteme dazu zu bringen, miteinander zu "
+"kommunizieren. Mit dem Aufkommen von Web Services besteht nun die "
+"Möglichkeit, eine unvergleichliche Technologie für Interoperabilität "
+"wirkungsvoll einzusetzen, und dadurch die existierenden "
+"transaktionsverarbeitenden Systeme zusammenzufügen, welche bereits das "
+"Rückgrat der Anwendungen auf Unternehmensebene bilden."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:101
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr "Grundlagen der WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:102
+#, no-c-format
+msgid ""
+"An important aspect of WS-Transaction that differentiates it from "
+"traditional transaction protocols is that a synchronous request/response "
+"model is not assumed. This model derives from the fact that WS-Transaction "
+"is, as shown in the figure below, layered upon the WS-Coordination protocol "
+"whose own communication patterns are asynchronous by default."
+msgstr ""
+"Ein wichtiger Aspekt der WS-Transaction, der sie von traditionellen "
+"Transaktionsprotokollen unterscheidet, ist, dass kein synchrones Anfrage/"
+"Anwort-Modell angenommen wird. Dieses Modell rührt von der Tatsache her, "
+"dass die WS-Transaction dem WS-Coordination Protokoll nachgelagert ist (wie "
+"in der Abbildung unten gezeigt), dessen eigenes Kommunikationsmodell "
+"standardmäßig asynchron ist."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:110
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr "WS-Coordination, WS-Atomic Transaction und WS-Business Activity"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:112
+#, no-c-format
+msgid ""
+"Web Services Coordination provides a generic framework for specific "
+"coordination protocols, like WS-Transaction, to be plugged in. Recall that "
+"WS-Coordination provides only context management – it allows contexts to be "
+"created and activities to be registered with those contexts. WS-Transaction "
+"leverages the context management framework provided by WS-Coordination in "
+"two ways. Firstly it extends the WS-Coordination context to create a "
+"transaction context. Secondly, it augments the activation and registration "
+"services with a number of additional services (Completion, "
+"CompletionWithAck, PhaseZero, 2PC, OutcomeNotification, BusinessAgreement, "
+"and BusinessAgreementWithComplete) and two protocol message sets (one for "
+"each of the transaction models supported in WS-Transaction) to build a fully-"
+"fledged transaction coordinator on top the WS-Coordination protocol "
+"infrastructure."
+msgstr ""
+"Web Services Coordination stellt ein generisches Framework bereit zum "
+"Einbringen bestimmter Koordinationsprotokolle, wie WS-Transaction. Sie "
+"erinnern sich, dass WS-Coordination nur Kontextmanagement bietet – es "
+"ermöglicht die Erstellung von Kontexten und die Registrierung von "
+"Aktivitäten bei diesen Kontexten. WS-Transaction setzt das von WS-"
+"Coordination gelieferte Kontextmanagement-Framework auf zwei Arten ein. "
+"Erstens erweitert es den WS-Coordination Kontext, um einen "
+"Transaktionskontext zu erstellen. Zweitens erweitert es die Aktivierungs- "
+"und Registrierungsdienste um eine Reihe zusätzlicher Dienste (Completion, "
+"CompletionWithAck, PhaseZero, 2PC, OutcomeNotification, BusinessAgreement, "
+"und BusinessAgreementWithComplete) und zwei Sets von Protokollnachrichten "
+"(eine für jede in WS-Transaction unterstützte Transaktionsmethode), um einen "
+"vollständig unterstützten Transaktionskoordinator zu bauen über die WS-"
+"Coordination Protokollinfrastruktur hinaus."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:116
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr "WS-Transaction Architektur"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:117
+#, no-c-format
+msgid ""
+"WS-Transaction supports the notion of the service and participant as "
+"distinct roles, making the distinction between a transaction-aware service "
+"and the participants that act on behalf of the service during a transaction: "
+"transactional services deal with business-level protocols, while the "
+"participants handle the underlying WS-Transaction protocols, as shown above."
+msgstr ""
+"WS-Transaction unterstützt den Begriff von Service und Teilnehmer als klar "
+"verschiedene Rollen, und unterscheidet zwischen einem transaktionssicheren "
+"Service, und den Teilnehmern, die während einer Transaktion im Auftrag des "
+"Services handeln: Transaktionale Services haben mit Protokollen auf "
+"Geschäftsebene zu tun, während Teilnehmer die zugrunde liegenden WS-"
+"Transaction Protokolle handhaben, wie oben gezeigt."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:125
+#, no-c-format
+msgid "WS-Transaction Global View"
+msgstr "WS-Transaction Globale Sicht"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:127
+#, no-c-format
+msgid ""
+"A transaction-aware service encapsulates the business logic or work that is "
+"required to be conducted within the scope of a transaction. This work cannot "
+"be confirmed by the application unless the transaction also commits and so "
+"control is ultimately removed from the application and placed into the "
+"transaction’s domain."
+msgstr ""
+"Ein transaktionssicherer Service kapselt die Business-Logik oder Arbeiten, "
+"deren Ausführung innerhalb des Scopes einer Transaktion erforderlich ist. "
+"Diese Arbeit kann nicht von der Anwendung bestätigt werden, es sei denn, die "
+"Transaktion schreibt auch fest, so dass die Kontrolle letztlich der "
+"Anwendung entzogen und in den Bereich der Transaktion übertragen wird."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:130
+#, no-c-format
+msgid ""
+"The participant is the entity that, under the dictates of the transaction "
+"coordinator, controls the outcome of the work performed by the transaction-"
+"aware Web service. In the figure above each service is shown with one "
+"associated participant that manages the transaction protocol messages on "
+"behalf of its service, while in the figure below, there is a close-up view "
+"of a single service, and a client application with their associated "
+"participants."
+msgstr ""
+"Der Teilnehmer ist eine Entity, die unter dem Diktat des "
+"Transaktionskoordinators das Ergebnis der Arbeiten kontrolliert, die von dem "
+"transaktionssicheren Web Service ausgeführt wurden. In der obigen Abbildung "
+"ist jeder Service gezeigt mit einem assoziierten Teilnehmer, der die "
+"Transaktionsprotokollnachrichten im Auftrag seines Services steuert; während "
+"in der Abbildung unten eine Detailansicht gezeigt wird von einem einzelnen "
+"Service und einer Client-Anwendung mit seinen zugehörigen Teilnehmern."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:137
+#, no-c-format
+msgid "Transactional Service and Participant"
+msgstr "Transaktionaler Service und Teilnehmer"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:139
+#, no-c-format
+msgid ""
+"The transaction-aware Web service and its participant both serve a shared "
+"transactional resource, and there is a control relationship between them "
+"through some API - which on the Java platform is JAXTX. In the example shown "
+"in the figure above, it is assumed that the database is accessed through a "
+"transactional JDBC database driver, where SQL statements are sent to the "
+"database for processing via that driver, but where those statements will be "
+"tentative and only commit if the transaction does. In order to do this, the "
+"driver/database will associate a participant with the transaction which will "
+"inform the database of the transaction outcome. Since all transactional "
+"invocations on the Web service carry a transaction context, the participant "
+"working with the database is able to identify the work that the "
+"transactional service did within the scope of a specific transaction and "
+"either commit or rollback the work."
+msgstr ""
+"Der transaktionssichere Web Service und seine Teilnehmer dienen beide einer "
+"gemeinsam benutzten transaktionalen Ressource, und es gibt zwischen ihnen "
+"eine Kontrollbeziehung durch eine API – auf der Java-Plattform ist dies "
+"JAXTX. In dem gezeigten Beispiel der Abbildung oben wird angenommen, dass "
+"auf die Datenbank durch einen transaktionalen JDBC-Datenbanktreiber "
+"zugegriffen wird, wobei SQL-Anweisungen an die Datenbank gesendet werden zur "
+"Verarbeitung durch den Treiber, wobei aber diese Anweisungen vorläufig sind "
+"und nur festschreiben, wenn auch die Transaktion festschreibt. Zu diesem "
+"Zweck wird der Treiber bzw. die Datenbank einen Teilnehmer mit der "
+"Transaktion assoziieren, der die Datenbank das über Ergebnis der Transaktion "
+"informieren wird. Da alle transaktionalen Aufrufe auf einem Web Service "
+"einen Transaktionskontext beinhalten, kann der mit der Datenbank "
+"arbeitendeTeilnehmer die Arbeit identifizieren, die der transaktionale "
+"Service innerhalb des Scopes einer bestimmten Transaktion ausgeführt hat, "
+"und diese Arbeit entweder festschreiben oder zurücksetzen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:142
+#, no-c-format
+msgid ""
+"At the client end, things are less complex. Through its API, the client "
+"application registers a participant with the transaction through which it "
+"controls transaction termination."
+msgstr ""
+"Auf Client-Seite sind die Dinge weniger komplex. Mithilfe ihrer API "
+"registriert eine Client-Anwendung einen Teilnehmer bei der Transaktion, "
+"wodurch sie das Beenden der Transaktion kontrolliert."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:146
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr "WS-Transaction Modelle"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:147
+#, no-c-format
+msgid ""
+"Given that traditional transaction models are not appropriate for Web "
+"services, the following question must be posed, “what type of model or "
+"protocol is appropriate?” The answer to that question is that that no one "
+"specific protocol is likely to be sufficient, given the wide range of "
+"situations that Web service transactions are likely to be deployed within. "
+"Hence the WS-Transaction specification proposes two distinct models, where "
+"each supports the semantics of a particular kind of B2B interaction. The "
+"following sections shall discuss these two WS-Transaction models."
+msgstr ""
+"In Anbetracht der Tatsache, dass traditionelle Transaktionsmodelle nicht für "
+"Web Services geeignet sind, muss man sich die Frage stellen, \"welche Art "
+"von Modell oder Protokoll ist stattdessen geeignet?\" Die Antwort auf diese "
+"Frage ist, dass wahrscheinlich kein einzelnes, spezifisches Protokoll "
+"ausreicht angesichts der vielfältigen Situationen, in denen Web Services "
+"Transaktionen wahrscheinlich eingesetzt werden. Aus diesem Grund schlagen "
+"die Spezifikationen der WS-Transaction zwei unterschiedliche Modelle vor, "
+"wobei jedes die Semantik einer bestimmten Art von B2B-Interaktionen "
+"unterstützt. Der folgende Abschnitt erläutert diese zwei WS-Transaction "
+"Modelle."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:152
+#, no-c-format
+msgid ""
+"As with WS-Coordination, the two WS-Transaction models are extensible "
+"allowing implementations to tailor the protocols as they see fit (for "
+"example, to suit their deployment environments)."
+msgstr ""
+"Wie auch WS-Coordination sind die zwei WS-Transaction Modelle erweiterbar, "
+"so dass Implementierungen die Protokolle wunschgemäß anpassen können (z. B. "
+"zum Anpassen an ihre Einsatzumgebung)."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:157
+#, no-c-format
+msgid "Atomic Transactions (AT)"
+msgstr "Atomic Transactions (AT)"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:158
+#, no-c-format
+msgid ""
+"An atomic transaction or AT is similar to traditional ACID transactions and "
+"intended to support short-duration interactions where ACID semantics are "
+"appropriate. Within the scope of an AT, services typically enroll "
+"transaction-aware resources, such as databases and message queues, "
+"indirectly as participants under the control of the transaction. When the "
+"transaction terminates, the outcome decision of the AT is then propagated to "
+"each enlisted resource via the participant, and the appropriate commit or "
+"rollback actions are taken by each."
+msgstr ""
+"Eine \"Atomic Transaction\" oder AT ähnelt den traditionellen ACID-"
+"Transaktionen und ist für die Unterstützung von kurzlaufenden Interaktionen "
+"gedacht, bei denen die ACID-Semantik angebracht ist. Innerhalb des Scopes "
+"einer AT registrieren die Services in der Regel transaktionssichere "
+"Ressourcen, wie Datenbanken und Nachrichten-Queues, indirekt als Teilnehmer "
+"unter der Kontrolle der Transaktion. Wenn die Transaktion endet, wird die "
+"Entscheidung zum Ergebnis der AT via dem Teilnehmer fortgepflanzt an jede "
+"angemeldete Ressource, welche dann jeweils die entsprechenden Maßnahmen zur "
+"Festschreibung oder zum Zurücksetzen ergreifen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:162
+#, no-c-format
+msgid ""
+"This protocol is very similar to those employed by traditional transaction "
+"systems that already form the backbone of an enterprise. It is assumed that "
+"all services (and associated participants) provide ACID semantics and that "
+"any use of atomic transactions occurs in environments and situations where "
+"this is appropriate: in a trusted domain, over short durations."
+msgstr ""
+"Dieses Protokoll ähnelt stark denen, die von traditionellen "
+"Transaktionssystemen verwendet werden, welche bereits das Rückgrat eines "
+"Unternehmens bilden. Es wird angenommen, dass alle Services (und "
+"dazugehörige Teilnehmer) ACID-Semantik bieten, und dass jegliche Verwendung "
+"von Atomic Transactions in Umgebungen und Situationen erfolgt, in denen dies "
+"angemessen ist: in einer vertrauenswürdigen Domain, über kurze Zeitspannen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:165
+#, no-c-format
+msgid ""
+"To begin an atomic transaction, the client application firstly locates a WS-"
+"Coordination coordinator Web service that supports WS-Transaction. Once "
+"located, the client sends a WS-Coordination CreateCoordinationContext "
+"message to the activation service specifying http://schemas.xmlsoap.org/"
+"ws/2004/10/wsat as its coordination type and will get back an appropriate WS-"
+"Transaction context from the activation service. The response to the "
+"CreateCoordinationContext message, the transaction context, has its "
+"CoordinationType element set to the WS-Atomic Transaction namespace, http://"
+"schemas.xmlsoap.org/ws/2004/10/wsat, and also contains a reference to the "
+"atomic transaction coordinator endpoint (the WS-Coordination registration "
+"service) where participants can be enlisted."
+msgstr ""
+"Um eine Atomic Transaction zu beginnen, lokalisiert die Client-Anwendung "
+"zunächst einen WS-Coordination Web Service, der WS-Transaction unterstützt. "
+"Ist dieser gefunden, sendet der Client eine WS-Coordination "
+"\"CreateCoordinationContext\"-Nachricht an den Aktivierungsdienst, "
+"spezifiziert http://schemas.xmlsoap.org/ws/2004/10/wsat als seinen "
+"Koordinationstyp, und wird einen entsprechenden WS-Transaction Kontext vom "
+"Aktivierungsdienst erhalten. Die Antwort auf die CreateCoordinationContext-"
+"Nachricht, der Transaktionskontext, hat sein CoordinationType-Element "
+"gesetzt im WS-Atomic Transaction Namensraum, http://schemas.xmlsoap.org/"
+"ws/2004/10/wsat, und enthält außerdem eine Referenz auf den Endpunkt des "
+"Atomic Transaction Koordinators (der WS-Coordination Registrierungsdienst), "
+"an dem Teilnehmer angemeldet weden können."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:168
+#, no-c-format
+msgid ""
+"After obtaining a transaction context from the coordinator, the client "
+"application then proceeds to interact with Web services to accomplish its "
+"business-level work. With each invocation on a business Web service, the "
+"client inserts the transaction context into a SOAP header block, such that "
+"each invocation is implicitly scoped by the transaction – the toolkits that "
+"support WS-Atomic Transaction-aware Web services provide facilities to "
+"correlate contexts found in SOAP header blocks with back-end operations."
+msgstr ""
+"Nach Erhalt eines Transaktionskontextes vom Koordinator führt die Client-"
+"Anwendung anschließend die Interaktion mit Web Services fort, um ihre Arbeit "
+"auf Geschäftsebene abzuschließen. Mit jedem Aufruf auf einem geschäftlichen "
+"Web Service fügt der Client den Transaktionskontext in einen SOAP-Header-"
+"Block ein, so dass jeder Aufruf indirekt im Scope der Transaktion liegt – "
+"die Toolkits, die WS-Atomic transaktionssichere Web Services unterstützen, "
+"stellen Hilfsmittel bereit zum Korrelieren von in SOAP-Header-Blöcken "
+"gefundenen Kontexten mit Backend-Operationen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:171
+#, no-c-format
+msgid ""
+"Once all the necessary application level work has been completed, the client "
+"can terminate the transaction, with the intent of making any changes to the "
+"service state permanent. To do this, the client application first registers "
+"its own participant for the Completion protocol. Once registered, the "
+"participant can instruct the coordinator either to try to commit or rollback "
+"the transaction. When the commit or rollback operation has completed, a "
+"status is returned to the participant to indicate the outcome of the "
+"transaction."
+msgstr ""
+"Sobald alle nötigen Arbeiten auf Anwendungsebene abgeschlossen wurden, kann "
+"der Client die Transaktion beenden mit der Absicht, jegliche Änderungen am "
+"Zustand des Services permanent zu machen. Zu diesem Zweck registriert die "
+"Client-Anwendung zunächst ihren eigenen Teilnehmer beim Completion-"
+"Protokoll. Ist er registriert, kann der Teilnehmer den Koordinator anweisen, "
+"entweder zu versuchen die Transaktion festzuschreiben oder zurückzusetzen. "
+"Wenn die Festschreibungs- oder Rücksetzungsoperation abgeschlossen ist, wird "
+"dem Teilnehmer ein Zustand zurückgegeben, um das Ergebnis der Transaktion "
+"anzuzeigen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:174
+#, no-c-format
+msgid ""
+"While the completion protocol is straightforward, they hide the fact that in "
+"order to resolve to an outcome that several other protocols need to be "
+"executed."
+msgstr ""
+"Obwohl das Completion-Protokoll überschaubar ist, so versteckt es doch die "
+"Tatsache, dass zum Beschließen eines Ergebnisses mehrere andere Protokolle "
+"ausgeführt werden müssen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:177
+#, no-c-format
+msgid ""
+"The first of these protocols is the optional Volatile2PC. The Volatile2PC "
+"protocol is the WS-Atomic Transaction equivalent of the synchronization "
+"protocol we discussed earlier. It is typically executed where a Web service "
+"needs to flush volatile (cached) state, which may be being used to improve "
+"performance of an application, to a database prior to the transaction "
+"committing. Once flushed, the data will then be controlled by a two-phase "
+"aware participant."
+msgstr ""
+"Das erste dieser Protokolle ist das optionale Volatile2PC. Das Volatile2PC-"
+"Protokoll ist das WS-Atomic Transaction Äquivalent zum "
+"Synchronisationsprotokoll, welches wir bereits erläutert haben. Es wird in "
+"der Regel dort ausgeführt, wo ein Web Service einen volatilen "
+"(zwischengespeicherten) Zustand in eine Datenbank zurückschreiben muss (was "
+"dazu benutzt werden kann, die Leistung einer Anwendung zu verbessern), bevor "
+"die Transaktion festgeschieben wird. Sobald zurückgeschrieben, werden die "
+"Daten von einem zwei-Phasen-sicheren Teilnehmer kontrolliert."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:180
+#, no-c-format
+msgid ""
+"All Volatile2PC participants are told that the transaction is about to "
+"complete (via the prepare message) and they can respond with either the "
+"prepared, aborted or readonly message; any failures at this stage will cause "
+"the transaction to rollback."
+msgstr ""
+"Allen Volatile2PC-Teilnehmern wird mitgeteilt, dass die Transaktion im "
+"Begriff ist abschließen (via der \"Prepare\"-Nachricht), und sie können "
+"entweder mit der \"Prepared\"-, \"Aborted\"- oder der \"Readonly\"-Nachricht "
+"antworten. Jegliche Fehler zu diesem Zeitpunkt verursachen ein Zurücksetzen "
+"der Transaktion."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:183
+#, no-c-format
+msgid ""
+"After Volatile2PC prepare, the next protocol to execute in WS-Atomic "
+"Transaction is Durable2PC. The Durable2PC (an abbreviation of the term two-"
+"phase commit) protocol is at the very heart of WS-Atomic Transaction and is "
+"used to bring about the necessary consensus between participants in a "
+"transaction such that the transaction can safely be terminated."
+msgstr ""
+"Nach der Vorbereitung von Volatile2PC ist das nächste in WS-Atomic "
+"Transaction ausgeführte Protokoll Durable2PC. Das Durable2PC (eine Abkürzung "
+"für den Ausdruck \"two-phase commit\", zwei-Phasen Festschreibung) -"
+"Protokoll steht im Zentrum der WS-Atomic Transaction und wird benutzt zum "
+"Herbeiführen der nötigen Übereinkunft zwischen Teilnehmern einer "
+"Transaktion, so dass die Transaktion sicher beendet werden kann."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:186
+#, no-c-format
+msgid ""
+"The two-phase commit protocol is used to ensure atomicity between "
+"participants, and is based on the classic two-phase commit with presumed "
+"abort technique. During the first phase, when the coordinator sends the "
+"prepare message, a participant must make durable any state changes that "
+"occurred during the scope of the transaction, such that these changes can "
+"either be rolled back or committed later. That is, any original state must "
+"not be lost at this point as the atomic transaction could still roll back. "
+"If the participant cannot prepare then it must inform the coordinator (via "
+"the aborted message) and the transaction will ultimately roll back. If the "
+"participant is responsible for a service that did not do any work during the "
+"course of the transaction, or at least did not do any work that modified any "
+"state, it can return the readonly message and it will be omitted from the "
+"second phase of the commit protocol. Otherwise, the prepared message is sent "
+"by the participant."
+msgstr ""
+"Das zwei-Phasen Festschreibungsprotokoll wird verwendet, um Atomarität "
+"zwischen Teilnehmern zu gewährleisten; es basiert auf der klassischen zwei-"
+"Phasen Festschreibung mit der Technologie des angenommenen Abruchs "
+"(\"presumed abort\"). Während der ersten Phase, wenn der Koordinator eine "
+"\"Prepare\"-Nachricht sendet, muss der Teilnehmer alle Zustandsänderungen "
+"dauerhaft machen, die im Scope der Transaktion durchgeführt wurden, damit "
+"diese Änderungen später entweder zurückgesetzt oder festgeschrieben werden "
+"können. Das heißt, an diesem Punkt darf kein Originalzustand verloren gehen, "
+"da die Atomic Transaction immer noch zurückgesetzt werden könnte. Falls sich "
+"der Teilnehmer nicht vorbereiten kann, muss er den Koordinator informieren "
+"(via der \"aborted\"-Nachricht), und die Transaktion wird schließlich "
+"zurückgesetzt. Falls der Teilnehmer verantwortlich ist für einen Service, "
+"der im Laufe der Transaktion keine Arbeit ausgeführt hat, oder zumindest "
+"keine zustandsverändernde Arbeit, kann er die \"Readonly\"-Nachricht "
+"zurückgeben und wird bei der zweiten Phase des Festschreibungsprotokolls "
+"ausgelassen. Andernfalls wird vom Teilnehmer die \"Prepared\"-Nachricht "
+"gesendet."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:189
+#, no-c-format
+msgid ""
+"Assuming no failures occurred during the first phase, in the second phase "
+"the coordinator sends the commit message to participants, who will make "
+"permanent the tentative work done by their associated services."
+msgstr ""
+"Vorausgesetzt es traten keinerlei Fehler in der ersten Phase auf, sendet der "
+"Koordinator in der zweiten Phase die \"Commit\"-Nachricht an die Teilnehmer, "
+"welche daraufhin die vorläufige Arbeit ihrer assoziierten Services permanent "
+"machen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:192
+#, no-c-format
+msgid ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
+msgstr ""
+"Falls eine Transaktion nur einen einzigen Teilnehmer umfasst, unterstützt WS-"
+"Atomic Transaction eine ein-Phasen Festschreibungsoptimierung. Weil es nur "
+"einen Teilnehmer gibt, ist die Übereinkunft über Entscheidungen impliziert, "
+"so dass der Koordinator die Transaktion nicht durch beide Phasen zu führen "
+"braucht. Im optimalen Fall wird der Teilnehmer einfach dazu aufgefordert "
+"festzuschreiben, und der Transaktionskoordinator braucht keine Informationen "
+"zu speichern über die Entscheidung, denn das Ergebnis der Transaktion hängt "
+"allein vom diesem einen Teilnehmer ab."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:195
+#, no-c-format
+msgid ""
+"The figure below<footnote> <para> Redrawn from the WS-Atomic Transaction "
+"specification. </para> </footnote> shows the state transitions of a WS-"
+"Atomic Transaction and the message exchanges between coordinator and "
+"participant; the coordinator generated messages are shown in the solid line, "
+"whereas the participant messages are shown by dashed lines."
+msgstr ""
+"Die Abbildung unten<footnote> <para> Auszug aus den WS-Atomic Transaction "
+"Spezifikationen. </para> </footnote> zeigt die Zustandsänderungen einer WS-"
+"Atomic Transaction sowie den Nachrichtenaustausch zwischen Koordinator und "
+"Teilnehmer; die vom Koordinator generierten Nachrichten werden mit "
+"durchgehenden Linien dargestellt, die vom Teilnehmer generierten Nachrichten "
+"mit gestrichelten Linien."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:206
+#, no-c-format
+msgid "Two-Phase Commit State Transitions"
+msgstr "Zustandsänderungen bei zwei-Phasen Festschreibung"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:208
+#, no-c-format
+msgid ""
+"Once the 2PC protocol has finished, the Completion protocol that originally "
+"began the termination of the transaction can complete, and inform the client "
+"application whether the transaction was committed or rolled back. "
+"Additionally, the Volatile2PC protocol may complete."
+msgstr ""
+"Sobald das 2PC-Protokoll abgeschlossen ist, kann das Completion-Protokoll, "
+"das ursprünglich das Beenden der Transaktion begonnen hat, abschließen und "
+"die Client-Anwendung darüber informieren, ob die Transaktion festgeschrieben "
+"oder zurückgesetzt wurde. Zusätzlich kann das Volatile2PC-Protokoll "
+"abschließen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:211
+#, no-c-format
+msgid ""
+"Like the prepare phase of Volatile2PC, the final phase is optional and can "
+"be used to inform participants when the transaction has completed, typically "
+"so that they can release resources (for example, put a database connection "
+"back into the pool of connections)."
+msgstr ""
+"Wie auch die Vorbereitungsphase von Volatile2PC ist die finale Phase "
+"optional und kann benutzt werden, um die Teilnehmer zu informieren, wenn die "
+"Transaktion abgeschlossen wurde, normalerweise damit sie Ressourcen wieder "
+"freigeben können (z. B. die Datenbankverbindung zurück in den Verbindungs-"
+"Pool legen)."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:214
+#, no-c-format
+msgid ""
+"Any registered Volatile2PC participants are invoked after the transaction "
+"has terminated and are told the state in which the transaction completed "
+"(the coordinator sends either the Committed or Aborted message). Since the "
+"transaction has terminated, any failures of participants at this stage are "
+"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
+"the transaction."
+msgstr ""
+"Jeder registrierte Volatile2PC-Teilnehmer wird nach Beendigung der "
+"Transaktion aufgerufen und informiert über den Zustand, in der die "
+"Transaktion beendet wurde (der Koordinator sendet entweder die \"Commited\"- "
+"oder \"Aborted\"-Nachricht). Da die Transaktion beendet ist, werden etwaige "
+"Fehler von Teilnehmern zu diesem Zeitpunkt ignoriert – es ist im Prinzip nur "
+"eine \"Höflichkeit\", und hat keinerlei Auswirkung auf das Ergebnis der "
+"Transaktion."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:217
+#, no-c-format
+msgid ""
+"Finally, after having gone through each of the stages in an AT, it is "
+"possible to see the intricate interweaving of individual protocols that goes "
+"to make up the AT as a whole in the following figure."
+msgstr ""
+"Endlich, nachdem wir jede Phase einer AT durchgegangen sind, ist es nun "
+"möglich, die feine Verwebung der einzelnen Protokolle in der folgenden "
+"Abbildung zu erkennen, die eine AT im Ganzen ausmachen."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:224
+#, no-c-format
+msgid "The AT Model"
+msgstr "Das AT-Modell"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:227
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr "Business Activitys (BA)"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:228
+#, no-c-format
+msgid ""
+"Most business-to-business applications require transactional support in "
+"order to guarantee consistent outcome and correct execution. These "
+"applications often involve long running computations, loosely coupled "
+"systems and components that do not share data, location, or administration "
+"and it is difficult to incorporate atomic transactions within such "
+"architectures. For example, an online bookshop may reserve books for an "
+"individual for a specific period of time, but if the individual does not "
+"purchase the books within that period they will be “put back onto the shelf” "
+"for others to buy. Furthermore, because it is not possible for anyone to "
+"have an infinite supply of stock, some online shops may appear to users to "
+"reserve items for them, but in fact may allow others to pre-empt that "
+"reservation (for instance, the same book may be “reserved” for multiple "
+"users concurrently); a user may subsequently find that the item is no longer "
+"available, or may have to be reordered specially for them."
+msgstr ""
+"Die meisten Business-to-Business-Anwendungen erfordern transaktionale "
+"Unterstützung, um konsistente Ergebnisse und fehlerfreie Ausführung zu "
+"garantieren. Diese Anwendungen beeinhalten oft langwierige Berechnungen, "
+"lose gekoppelte Systeme und Komponenten ohne gemeinsame Daten, Orte oder "
+"Verwaltung, und es ist schwierig, Atomic Transactions in einer solchen "
+"Architektur einzubinden. Zum Beispiel kann ein Online-Buchladen ein Buch "
+"eine bestimmte Zeit lang für jemanden reservieren, aber falls die Person das "
+"Buch nicht innerhalb dieser Zeit kauft, wird das Buch wieder \"ins Regal "
+"zurückgestellt\", um von anderen gekauft werden zu können. Weil es niemandem "
+"möglich ist, ein unbegrenztes Warenlager zu haben, scheinen einige Online-"
+"Shops zwar Posten für den Benutzer zu reservieren, erlaubt es anderen "
+"jedoch, dieser Reservierung zuvorzukommen (z. B. kann das gleiche Buch für "
+"mehrere Benutzer gleichzeitig \"reserviert\" sein), infolgedessen muss der "
+"Benutzer ggf. feststellen, dass der Posten nicht länger verfügbar ist oder "
+"speziell für ihn bestellt werden muss."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:232
+#, no-c-format
+msgid ""
+"A business activity or BA is designed specifically for these kinds of long-"
+"duration interactions, where exclusively locking resources is impossible or "
+"impractical. In this model services are requested to do work, and where "
+"those services have the ability to undo any work, they inform the BA such "
+"that if the BA later decides the cancel the work (for instance if the "
+"business activity suffers a failure), it can instruct the service to execute "
+"its undo behavior. The key point for Business Activities is that how "
+"services do their work and provide compensation mechanisms is not the domain "
+"of the WS-Business Activity specification, but an implementation decision "
+"for the service provider."
+msgstr ""
+"Eine Business Activity oder BA ist speziell für diese Art der langlaufenden "
+"Interaktion entworfen, in denen exklusive Sperrung von Ressourcen unmöglich "
+"oder unpraktikabel ist. In diesem Modell werden Services aufgefordert "
+"Arbeiten auszuführen, und wenn die Services fähig sind Arbeiten rückgängig "
+"zu machen, informieren sie die BA. Dadurch kann die BA, falls sie später "
+"entschließt die Arbeit abzubrechen (z. B. wenn in der Business Activity ein "
+"Fehler auftritt), den Service anweisen, seinen Mechanismus zum Zurücksetzen "
+"auszuführen. Der entscheidende Punkt bei Business Activitys ist, dass die "
+"Art und Weise, wie Services ihre Arbeit verrichten und "
+"Kompensationsmechanismen liefern, nicht die Domäne der WS-Business Activity "
+"Spezifikation ist, sondern eine Frage der Implementierung für den Service "
+"Provider."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:235
+#, no-c-format
+msgid ""
+"The WS- Business Activity simply defines a protocol for Web services-based "
+"applications to enable existing business processing and workflow systems to "
+"wrap their proprietary mechanisms and interoperate across implementations "
+"and business boundaries."
+msgstr ""
+"Die WS Business Activity definiert einfach ein Protokoll für Web Service "
+"basierte Anwendungen, das es existierenden Geschäftsprozess- und Workflow-"
+"Systemen ermöglicht, ihre proprietären Mechanismen einzubinden und über "
+"Implementierungen und Geschäftsgrenzen hinweg zusammenzuarbeiten."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:238
+#, no-c-format
+msgid ""
+"A business activity may be partitioned into scopes, where a scope is a "
+"business task or unit of work using a collection of Web services. Such "
+"scopes can be nested to arbitrary degrees, forming parent and child "
+"relationships, where a parent scope has the ability to select which child "
+"tasks are to be included in the overall outcome protocol for a specific "
+"business activity, and so clearly non-atomic outcomes are possible. In a "
+"similar manner to traditional nested transactions, if a child task "
+"experiences an error, it can be caught by the parent who may be able to "
+"compensate and continue processing."
+msgstr ""
+"Eine Business Activity kann in Scopes unterteilt werden, wobei ein Scope "
+"einen Business Task darstellt, oder eine Einheit von Arbeit, die eine Reihe "
+"von Web Services nutzt. Solche Scopes können beliebig tief verschachtelt "
+"werden und Parent-Child-Beziehungen formen, wobei ein Parent Scope die "
+"Fähigkeit hat zu entscheiden, welche Child Tasks in dem übergreifenden "
+"Ergebnisprotokoll einer Business Activity enthalten sein sollen, wodurch "
+"natürlich nicht-atomische Ergebnisse möglich sind. Auf eine ähnliche Weise "
+"wie traditionell verschachtelte Transaktionen kann ein Child Task, der einen "
+"Fehler feststellt, vom Parent Task aufgefangen werden, welcher "
+"möglicherweise kompensieren und die Arbeit fortsetzen kann."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:241
+#, no-c-format
+msgid ""
+"When a child task completes it can either leave the business activity or "
+"signal to the parent that the work it has done can be compensated later. In "
+"the latter case, the compensation task may be called by the parent should it "
+"ultimately need to undo the work performed by the child."
+msgstr ""
+"Wenn ein Child Task abschließt, kann er entweder die Business Activity "
+"verlassen oder dem Parent Task signalisieren, dass die von ihm ausgeführte "
+"Arbeit später kompensiert werden kann. Im letzteren Fall kann der "
+"Kompensierungs-Task vom Parent aufgerufen werden, sollte er letztlich die "
+"vom Child durchgeführte Arbeit rückgängig machen müssen."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:244
+#, no-c-format
+msgid ""
+"Unlike the WS-Atomic Transaction protocol model, where participants inform "
+"the coordinator of their state only when asked, a task within a business "
+"activity can specify its outcome to the parent directly without waiting for "
+"a request. This feature is useful when tasks fail such that the notification "
+"can be used by business activity exception handler to modify the goals and "
+"drive processing forward without having to meekly wait until the end of the "
+"transaction to admit to having failed – a well designed Business Activities "
+"should be proactive, if it is to perform well."
+msgstr ""
+"Anders als beim Modell des WS-Atomic Transaction Protokolls, in dem "
+"Teilnehmer den Koordinator nur über ihren Zustand informieren, wenn sie "
+"danach gefragt werden, kann ein Task innerhalb einer Business Activity sein "
+"Ergebnis dem Parent Task mitteilen, ohne eine Anfrage abzuwarten. Dieses "
+"Feature ist nützlich, wenn Tasks fehlschlagen, so dass die Benachrichtigung "
+"vom Business Activity Ausnahmen-Handler benutzt werden kann, um die Ziele zu "
+"modifizieren und so die Verarbeitung fortzusetzen, ohne auf das Ende der "
+"Transaktion und die Fehlerbenachrichtigung warten zu müssen – eine gut "
+"entworfene Business Activity sollte proaktiv sein, wenn sie leistungsstark "
+"sein soll."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:247
+#, no-c-format
+msgid "Underpinning all of this are three fundamental assumptions:"
+msgstr "Alldem liegen drei fundamentale Annahmen zugrunde:"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:252
+#, no-c-format
+msgid ""
+"All state transitions are reliably recorded, including application state and "
+"coordination metadata (the record of sent and received messages);"
+msgstr ""
+"Alle Zustandsänderungen werden zuverlässig aufgezeichnet, inklusive "
+"Anwendungszustand und Koordinationsmetadaten (die Aufzeichnungen von "
+"gesendeten und empfangenen Nachrichten);"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:257
+#, no-c-format
+msgid ""
+"All request messages are acknowledged, so that problems are detected as "
+"early as possible. This avoids executing unnecessary tasks and can also "
+"detect a problem earlier when rectifying it is simpler and less expensive;"
+msgstr ""
+"Alle Anfragenachrichten werden bestätigt, so dass Probleme so früh wie "
+"möglich entdeckt werden. Dies vermeidet das Ausführen unnötiger Tasks, und "
+"kann zudem ein Problem frühzeitig entdecken, wenn dessen Behebung noch "
+"einfacher und billiger ist;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:262
+#, no-c-format
+msgid ""
+"As with atomic transactions, a response is defined as a separate operation "
+"and not as the output of the request. Message input-output implementations "
+"will typically have timeouts that are too short for some business activity "
+"responses. If the response is not received after a timeout, it is resent. "
+"This is repeated until a response is received. The request receiver discards "
+"all but one identical request received."
+msgstr ""
+"Wie bei Atomic Transactions wird eine Antwort als separate Operation "
+"definiert, und nicht als Ausgabe der Anfrage. Nachrichten-Eingabe/Ausgabe "
+"Implementierungen haben in der Regel Timeouts, die für manche Business "
+"Activity Antworten zu kurz sind. Wenn eine Antwort nach einem Timeout nicht "
+"empfangen wird, wird sie noch einmal gesendet. Dies wird solange wiederholt, "
+"bis eine Antwort empfangen wird. Der Anfrageempfänger löscht alle "
+"identischen empfangenen Anfragen bis auf eine."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:267
+#, no-c-format
+msgid ""
+"As with atomic transactions, the business activity model has multiple "
+"protocols: <code>BusinessAgreementWithParticipantCompletion</code> and "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. However, unlike the "
+"AT protocol which is driven from the coordinator down to participants, this "
+"protocol is driven much more from the participants upwards."
+msgstr ""
+"Wie auch Atomic Transactions hat das Modell der Business Activity mehrere "
+"Protokolle: <code>BusinessAgreementWithParticipantCompletion</code> und "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. Anders als das AT "
+"Protokoll, welches vom Koordinator abwärts in Richtung der Teilnehmer "
+"ausgeführt wird, wird dieses Protokoll dagegen vielmehr von den Teilnehmern "
+"aufwärts ausgeführt."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
+#, no-c-format
+msgid ""
+"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
+"a child activity is initially created in the Active state; if it finishes "
+"the work it was created to do and no more participation is required within "
+"the scope of the BA (such as when the activity operates on immutable data), "
+"then the child can unilaterally send an exited message to the parent. "
+"However, if the child task finishes and wishes to continue in the BA then it "
+"must be able to compensate for the work it has performed. In this case it "
+"sends a completed message to the parent and waits to receive the final "
+"outcome of the BA from the parent. This outcome will either be a close "
+"message, meaning the BA has completed successfully or a compensate message "
+"indicating that the parent activity requires that the child task reverse its "
+"work."
+msgstr ""
+"Unter dem <code>BusinessAgreementWithParticipantCompletion</code>-Protokoll "
+"wird eine Child Activity zunächst im Active-Zustand erstellt. Wenn sie die "
+"Arbeit, für die sie erstellt wurde, abschließt und keine weitere Teilnahme "
+"innerhalb des Scopes der BA erforderlich ist (z. B. wenn die Activity mit "
+"unveränderlichen Daten arbeitet), dann kann der Child einseitig eine Excited-"
+"Nachricht an den Parent senden. Wenn jedoch der Child Task abschließt und in "
+"der BA weitermachen möchte, muss er fähig sein, die durchgeführten Arbeiten "
+"zu kompensieren. In diesem Fall sendet er eine Completed-Nachricht an den "
+"Parent und wartet auf Empfang des Endergebnisses der BA vom Parent. Dieses "
+"Ergebnis wird entweder eine Close-Nachricht sein, was bedeutet, dass die BA "
+"erfolgreich abgeschlossen wurde, oder eine Compensate-Nachricht, die "
+"anzeigt, dass der Parent Task ein Rückgängigmachen vom Child Task für dessen "
+"ausgeführte Arbeit fordert."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
+#, no-c-format
+msgid ""
+"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
+"identical to the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol with the exception that the child cannot autonomously decide to end "
+"its participation in the business activity, even if it can be compensated. "
+"Rather the child task relies upon the parent to inform it when the child has "
+"received all requests for it to perform work which the parent does by "
+"sending the complete message to the child. The child then acts as it does in "
+"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
+msgstr ""
+"Das <code>BusinessAgreementWithCoordinatorCompletion</code>-Protokol ist "
+"identisch zum <code>BusinessAgreementWithParticipantCompletion</code>-"
+"Protokoll, abgesehen davon, dass der Child nicht autonom entscheiden kann, "
+"seine Teilnahme an der Business Activity zu beenden, selbst wenn kompensiert "
+"werden kann. Vielmehr verlässt sich der Child auf den Parent, dass dieser "
+"ihm mitteilt, wenn der Child alle Anfragen zur Ausführung von Arbeiten "
+"empfangen hat. Der Parent tut dies durch Senden der Complete-Nachricht an "
+"den Child. Der Child handelt anschließend wie im "
+"<code>BusinessAgreementWithParticipantCompletion</code>-Protokoll."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:276
+#, no-c-format
+msgid ""
+"The crux of the BA model compared to the AT model is that is allows the "
+"participation of services that cannot or will not lock resources for "
+"extended periods."
+msgstr ""
+"Die Crux des BA-Modells im Vergleich zum AT-Modell ist, dass es die "
+"Teilnahme von Services erlaubt, die Ressourcen nicht für längere Zeit "
+"sperren wollen oder können."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:279
+#, no-c-format
+msgid ""
+"While the full ACID semantics are not maintained by a BA, consistency can "
+"still be maintained through compensation, though the task of writing correct "
+"compensating actions (and thus overall system consistency) is delegated to "
+"the developers of the services under control of the BA. Such compensations "
+"may use backward error recovery, but will typically employ forward recovery."
+msgstr ""
+"Auch wenn die volle ACID-Semantik nicht von einer BA eingehalten wird, kann "
+"dennoch die Konsistenz erhalten werden durch Kompensation, obwohl die "
+"Aufgabe, korrekte Aktionen zur Kompensation (und somit zur Konsistenz des "
+"gesamten Systems) zu schreiben, delegiert wird an die Entwickler des "
+"Services unter Kontrolle der BA. Solche Kompensationen können "
+"rückwärtsgerichtete Fehlerbehebung nutzen, setzen in der Regel aber "
+"vorwärtsgerichtete Fehlerbehebung ein."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:283
+#, no-c-format
+msgid "Application Messages"
+msgstr "Anwendungsnachrichten"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:284
+#, no-c-format
+msgid ""
+"Application messages are the requests and responses that are sent between "
+"parties that constitute the work of a business process. Any such messages "
+"are considered opaque by XTS, and there is no mandatory message format, "
+"protocol binding, or encoding style so the developer is free to use any "
+"appropriate Web services protocol. In XTS, the transaction context is "
+"propagated within the headers of SOAP messages."
+msgstr ""
+"Anwendungsnachrichten sind die Anfragen und Antworten, welche zwischen den "
+"Parteien gesendet werden, die die Arbeit eines Geschäftsprozesses bilden. "
+"Alle dieser Nachrichten werden von XTS als \"opaque\" (nicht einsehbar) "
+"betrachtet, und es gibt kein vorgeschriebenes Nachrichtenformat, "
+"Protokollbindung oder Encoding-Stil, so dass es dem Entwickler freisteht, "
+"welches passende Web Services Protokoll er verwendet. In XTS wird der "
+"Transaktionskontext im Header der SOAP-Nachrichten übermittelt."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:289
+#, no-c-format
+msgid ""
+"XTS provides out-of-box support for service developers building WS-T-aware "
+"services on the JBoss, Weblogic and Glue platforms1. The provision of "
+"interceptors for automatic context handling at both client and service "
+"significantly simplifies the developer’s workload, allowing the developer to "
+"concentrate on writing the business logic without having to worry about the "
+"transactional infrastructure getting in the way. The interceptors simply add "
+"and remove context elements to application messages without altering the "
+"semantics of those messages. Any service which understands what to do with a "
+"WS-C context can use it, services which do not understand the context (those "
+"services that are not WS-C, WS-Atomic Transaction and WS-Business Activity-"
+"aware) may ignore the context; the important point here is that XTS manages "
+"contexts without user intervention."
+msgstr ""
+"XTS bietet \"out-of-box\"-Unterstützung für Diensteentwickler an, die WS-T-"
+"sichere Dienste auf JBoss, Weblogic und Glue platform1 bauen. Das "
+"Bereitstellen von Interzeptoren für automatisches Kontext-Handling bei "
+"Client und Dienst verringert deutlich den Arbeitsaufwand für Entwickler, was "
+"es ihm ermöglicht, sich auf das Schreiben der Business-Logik zu "
+"konzentrieren, ohne sich um darum zu sorgen, ob die transaktionale "
+"Infrastruktur im Weg steht. Die Interzeptoren können einfach Kontextelemente "
+"in Anwendungsnachrichten hinzufügen oder entfernen, ohne die Semantik der "
+"Nachrichten zu verändern. Jeder Dienst, der versteht, was mit einer WS-C "
+"Kontextnachricht zu tun ist, kann diese verwenden; Dienste, die dies nicht "
+"verstehen (solche die WS-C, WS-Atomic Transaction und WS-Business Activity "
+"nicht beherrschen), können den Kontext ignorieren. Der wichtige Punkt hier "
+"ist, dass XTS Kontexte ohne Benutzerintervention verwaltet."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:294
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr "WS-C, WS-Atomic Transaction und WS-Business Activity Nachrichten"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:295
+#, no-c-format
+msgid ""
+"Although the application or service developer rarely sees or is interested "
+"in the messages exchanged by the transactional infrastructure (the "
+"transaction manager and any participants), it is useful to understand what "
+"kinds of exchanges occur so that the underlying model can be fitted in to an "
+"overall architecture."
+msgstr ""
+"Obwohl ein Entwickler von Anwendungen oder Diensten selten die Nachrichten "
+"sieht oder überhaupt an ihnen interessiert ist, die in der transaktionalen "
+"Infrastruktur (Transaktionsmanager und alle Teilnehmer) ausgetauscht werden, "
+"ist es doch sinnvoll zu verstehen, welche Art von Austausch erfolgt, so dass "
+"das zugrunde liegende Modell in eine Gesamtarchitektur eingepasst werden "
+"kann."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:299
+#, no-c-format
+msgid ""
+"In XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific "
+"messages are transported using SOAP messaging over HTTP. The types of "
+"messages that are propagated include instructions to perform standard "
+"transaction operations like begin, prepare."
+msgstr ""
+"XTS, WS-C, WS-Atomic Transaction und WS-Business Activity -spezifische "
+"Nachrichten werden mittels SOAP-Nachrichten über HTTP transportiert. Die "
+"Typen der fortgepflanzten Nachrichten enthalten Anweisungen zur Durchführung "
+"von Standardtransaktionsoperationen wie \"begin\" oder \"prepare\"."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:303
+#, no-c-format
+msgid ""
+"XTS messages do not interfere in any way, shape, or form, with the "
+"application messages, and nor is there any requirement for an application to "
+"use the same transport as the transaction-specific messages. For example, it "
+"is quite reasonable for a client application to deliver its application-"
+"specific messages using SOAP RPC over SMTP even though under the covers the "
+"XTS messages are delivered using a different mechanism."
+msgstr ""
+"XTS-Nachrichten beeinflussen in keinster Weise die Anwendungsnachrichten, "
+"und es gibt für eine Anwendung auch keine Erfordernis, den gleichen "
+"Transport zu nutzen wie transaktionsspezifische Nachrichten. Beispielsweise "
+"ist es für eine Client-Anwendung durchaus vernünftig, seine "
+"anwendungsspezifischen Nachrichten mittels SOAP RPC über SMTP zu versenden, "
+"obwohl darunter verdeckt die XTS-Nachrichten unter Verwendung eines anderen "
+"Mechanismus übermittelt werden."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:310
+#, no-c-format
+msgid "Summary"
+msgstr "Zusammenfassung"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:311
+#, no-c-format
+msgid ""
+"XTS provides a coordination infrastructure designed to allow transactions to "
+"run between enterprises across the Internet. That infrastructure is based on "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. It "
+"supports two kinds of transactions: atomic transactions and business "
+"activities, which can be combined in arbitrary ways to map elegantly onto "
+"the transactional requirements of the underlying problem. The use of the "
+"whole infrastructure is simple due to the fact that its functionality is "
+"exposed through a simple transactioning API. Furthermore XTS provides all of "
+"the necessary plumbing to keep application and transactional aspects of an "
+"application separate, and to ensure that the transactionality of a system "
+"does not interfere with the functional aspects of the system itself."
+msgstr ""
+"XTS bietet eine Koordinationsinfrastruktur, entworfen um das Abwickeln von "
+"Transaktionen zwischen Unternehmen über das Internet zu ermöglichen. Diese "
+"Infrastruktur basiert auf WS-C, WS-Atomic Transaction und WS-Business "
+"Activity Spezifikationen. Es unterstützt zwei Arten von Transaktionen: "
+"Atomic Transactions und Business Activitys, die beliebig kombiniert werden "
+"können, um elegant auf die Transaktionsanforderungen des zugrunde liegenden "
+"Problems angepasst zu werden. Die Nutzung der gesamten Infrastruktur ist "
+"einfach, denn seine Funktionalität ist offengelegt durch eine simple "
+"transaktionelle API. Darüberhinaus bietet XTS die nötige Tiefe, um die "
+"Anwendung von transaktionalen Aspekten der Anwendung getrennt zu halten, und "
+"um zu gewährleisten, dass die Transaktionalität eines Systems nicht mit den "
+"funktionalen Aspekten des Systems selbst kollidiert."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Author_Group.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Author_Group.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,22 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Book_Info.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Book_Info.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,47 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide CP04"
+msgstr "Manual de programadores de servicios web de JBoss Transactions"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "para uso con JBoss Enterprise Application Platform 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr "Este libro trata la programación para servicios web de transacciones"
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Getting_Started.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Getting_Started.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Getting_Started.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,265 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Getting_Started.xml:6
+#, no-c-format
+msgid "Getting Started"
+msgstr "Manual de inicio"
+
+#. Tag: title
+#: Getting_Started.xml:8
+#, no-c-format
+msgid "Creating and deploying participants"
+msgstr "Crear y desplegar participantes"
+
+#. Tag: para
+#: Getting_Started.xml:9
+#, no-c-format
+msgid ""
+"A participant is a software entity which is driven by the transaction "
+"manager on behalf of a Web service. The creation of participants is non-"
+"trivial since they ultimately reflect the state of a Web service’s back-end "
+"processing facilities which is a function of an enterprise’s own IT "
+"infrastructure. The most that can be said about the implementation of a "
+"participant without getting into detail about the back-end systems it "
+"represents, or the details of the underlying transaction protocol is that "
+"implementations must implement one of the following interfaces, depending "
+"upon the protocol it will participate within: <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code>, or, <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+msgstr ""
+"Un participante es una entidad software, la cual es dirigida por el "
+"administrador de transacciones de parte de un servicio web. La creación de "
+"participantes no es nada trivial ya que ultimadamente reflejan el estado "
+"final de las funciones de procesamiento de un servicio web, el cual es una "
+"función de la infraestructura tecnológica de la compañia. Sin abordar "
+"detalles sobre la implementación de un participante podemos decir que las "
+"implementación deben desplegar una de las siguientes interfaces, dependiendo "
+"del protocolo dentro del cual participará: <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code> o <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+
+#. Tag: title
+#: Getting_Started.xml:15
+#, no-c-format
+msgid "Creating Client Applications"
+msgstr "Creación de aplicaciones clientes"
+
+#. Tag: para
+#: Getting_Started.xml:16
+#, no-c-format
+msgid ""
+"There are two aspects to a client application using XTS. The first is the "
+"transaction declaration aspects and the second is the business logic that "
+"the client application performs. The transaction declaration aspects are "
+"taken care of automatically with XTS’s client API. This API provides simple "
+"transaction directives like begin, commit, and rollback which the client "
+"application can use to initialize, manage, and terminate transactions. Under "
+"the covers, this API invokes (via SOAP) operations on the transaction "
+"manager."
+msgstr ""
+"Hay dos aspectos a tener en cuenta para una aplicación cliente utilizando "
+"XTS. El primero es los aspectos de declaración de transacciones y el segundo "
+"es la lógica empresarial que la aplicación cliente realiza. La API cliente "
+"de XTS se encarga automáticamente de los aspectos de declaración de "
+"transacciones. Esta API proporciona directivas simples de transacción como "
+"iniciar, guardar cambios y deshacer, las cuales las puede utilizar la "
+"aplicación cliente para inicializar, administrar y terminar transacciones. "
+"Por debajo de la mesa, esta API invoca (por medio de SOAP) operaciones en el "
+"administrador de transacciones. "
+
+#. Tag: para
+#: Getting_Started.xml:19
+#, no-c-format
+msgid ""
+"When the client application performs invocations on business logic Web "
+"services, then XTS does not dictate an API for that purpose. However, there "
+"is a requirement that whatever API is chosen, the XTS context be inserted "
+"onto outgoing messages, and extracted and associated with the current thread "
+"for incoming messages. To make the user’s life easier, the XTS software "
+"comes complete with three sets of “filters” which can perform the task "
+"automatically. These filters are designed to work with JAX-RPC and "
+"webMethods client libraries."
+msgstr ""
+"Cuando la aplicación cliente realiza invocaciones en los servicios web de la "
+"lógica empresarial entonces XTS no dicta una API para ese propósito. Sin "
+"embargo, hay un requerimiento en el que cualquier API que se escoja, el "
+"contexto XTS se inserta en los mensajes salientes y se extrae y se asocia "
+"con el hilo actual para los mensajes entrantes. Para hacer más fácil la vida "
+"del usuario, el software XTS viene completo con tres grupos de 'filtros', "
+"los cuales pueden llevar la tarea acabo de manera automática. Estos filtros "
+"están diseñados para trabajar con JAX-RPC y las bibliotecas de clientes "
+"webMethods. "
+
+#. Tag: para
+#: Getting_Started.xml:23
+#, no-c-format
+msgid ""
+"If the user chooses to use a different SOAP client infrastructure, then the "
+"onus to perform client-side header processing rests with them. XTS does not "
+"provide client-side infrastructure for anything other than JAX-RPC or "
+"webMethods for this release."
+msgstr ""
+"Si el usuario decide utilizar una infraestructura de cliente SOAP diferente "
+"entonces la responsabilidad de realizar el procesamiento de encabezado del "
+"lado del cliente queda con ellos. XTS no proporciona infraestructura del "
+"lado del cliente sino solo para JAX-RPC o webMethods en este lanzamiento. "
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr "Manejadores de Contexto JAX-RPC "
+
+#. Tag: para
+#: Getting_Started.xml:29
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC server-side context handler with the "
+"deployed web services, a handler chain must be included in the web services "
+"deployment descriptor. Please refer to the demo application <filename>jboss/"
+"webservices.xml</filename> deployment descriptor for an example of how this "
+"can be achieved."
+msgstr ""
+"Con el fin de registrar el manejador de contexto del lado del servidor JAX-"
+"RPC con los servicios web desplegados, se debe incluir una cadena manejadora "
+"en el descriptor de despliegue de servicios web. Consulte la aplicación de "
+"demonstración del descriptor de despliegue <filename>jboss/webservices.xml</"
+"filename> y allí verá un ejemplo de cómo lograr esto. "
+
+#. Tag: para
+#: Getting_Started.xml:33
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC client-side context handler used by the "
+"client applications, a handler chain must be included in the definition of "
+"the service-ref in the client web.xml deployment descriptor. Please refer to "
+"the demo application <filename>jboss/client-web-app.xml</filename> for an "
+"example of how this can be achieved."
+msgstr ""
+"Con el fin de registrar el manejador de contexto del lado del cliente JAX-"
+"RPC que las aplicaciones cliente utilizan, se debe incluir una cadena "
+"manejadora en la definición del service-ref en el descriptor de despliegue "
+"web.xml cliente. Consulte la aplicación de demonstración <filename>jboss/"
+"client-web-app.xml</filename> para poder ver un ejemplo de como lograr esto. "
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr "Manejadores de contexto webMethods"
+
+#. Tag: para
+#: Getting_Started.xml:38
+#, no-c-format
+msgid ""
+"In order to register the webMethods server-side context handler with the "
+"deployed web services, the inbound and outbound interceptors must be "
+"configured in the web services deployment descriptor. An example of how this "
+"can be configured can be found in the demo application, for example, the "
+"<filename>RestaurantServiceAT.xml</filename>."
+msgstr ""
+"Con el fin de registrar el manejador de contexto del lado del servidor "
+"webMethods con los servicios web desplegados, se deben configurar los "
+"interceptores de entrada y salida en el descriptor de despliegue de "
+"servicios web. Puede encontrar un ejemplo de la configuración en la "
+"aplicación de demonstración tal como <filename>RestaurantServiceAT.xml</"
+"filename>."
+
+#. Tag: para
+#: Getting_Started.xml:42
+#, no-c-format
+msgid ""
+"In order to register the webMethods client-side context handler, the inbound "
+"and outbound interceptors must be configured in the <filename>glue-config."
+"xml</filename> deployment descriptor. Please refer to the soap interceptor "
+"section of the demo application glue-config.xml for an example of how this "
+"can be achieved."
+msgstr ""
+"Con el fin de registrar el manejador de contexto del lado del cliente "
+"webMethods, los interceptores de entrada y salida deben estar configurados "
+"en el descriptor de despliegue <filename>glue-config.xml</filename>. "
+"Consulte la sección del interceptor soap de la aplicación de demonstración "
+"glue-config.xml y allí encontrará un ejemplo de cómo lograr esto. "
+
+#. Tag: title
+#: Getting_Started.xml:48
+#, no-c-format
+msgid "Hints and tips"
+msgstr "Consejos"
+
+#. Tag: para
+#: Getting_Started.xml:49
+#, no-c-format
+msgid ""
+"If you want to create multiple JBoss deploys on the same machine, then you "
+"may wish to look at <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/"
+"MultipleInstances.htm\"><emphasis>Setting up multiple instances</emphasis></"
+"ulink> for information on what is required."
+msgstr ""
+"Si quiere crear múltiples despliegues de JBoss en la misma máquina entonces "
+"consulte <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/MultipleInstances."
+"htm\"><emphasis>Configuración de múltiples instancias</emphasis></ulink> "
+"allí encontrará información sobre los requerimientos."
+
+#. Tag: title
+#: Getting_Started.xml:55
+#, no-c-format
+msgid "Summary"
+msgstr "Resumen"
+
+#. Tag: para
+#: Getting_Started.xml:56
+#, no-c-format
+msgid ""
+"This chapter has provided a high-level overview of how to use each of the "
+"major software pieces of the Web Services transactions component of JBossTS. "
+"The Web Services transaction manager provided by JBossTS is the hub of the "
+"architecture and is the only piece of software that users’ software does not "
+"bind to directly. XTS provides header processing infrastructure for dealing "
+"with Web Services transactions contexts for both users’ client applications "
+"and Web services. For developing transaction participants, XTS provides a "
+"simple interface plus the necessary document handling code."
+msgstr ""
+"Este capítulo brinda una sinopsis a nivel general de cómo utilizar cada una "
+"de las partes más importantes de software del componente de transacciones de "
+"servicios web de JBossTS. El administrador de transacciones de servicios web "
+"que JBossTS brinda es la parte central de la arquitectura y es la única "
+"parte de software a la cual no se vinculan directamente los usuarios del "
+"software. XTS proporciona infraestructura de procesamiento de encabezado "
+"para tratar con contextos de transacciones de servicios web para los "
+"servicios web y las aplicaciones clientes del usuario. Para desarrollar "
+"participantes de transacciones, XTS brinda una interfaz simple ademas del "
+"código de manejo de documentos necesario."
+
+#. Tag: para
+#: Getting_Started.xml:59
+#, no-c-format
+msgid ""
+"This chapter is meant as an overview only, and is unlikely to answer "
+"questions on more difficult and subtle aspects. For fuller explanations of "
+"the components, please refer to the appropriate chapter elsewhere in this "
+"document."
+msgstr ""
+"Este capítulo tiene el propósito de brindar solo una sinopsis y muy "
+"posiblemente no responderá todas las preguntas. Consulte los capítulos "
+"pertinentes de este documento y allí encontrará explicaciones más completas."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Introduction.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Introduction.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Introduction.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,408 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr "Introducción"
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr "Sinopsis de JBossTS Web Services transactions"
+
+#. Tag: para
+#: Introduction.xml:9
+#, no-c-format
+msgid ""
+"The XML transaction service component of JBossTS (shorthand referred to as "
+"XTS) supports the coordination of private and public Web services in a "
+"business transaction. Therefore, to understand XTS, you must be familiar "
+"with Web services, and also understand a little about transactions. This "
+"chapter introduces XTS and provides a brief overview of the technologies "
+"that form the Web services standard. Additionally, this chapter explores "
+"some of the fundamentals of transactioning technology and how it can be "
+"applied to Web services. Much of the content presented in this chapter is "
+"detailed throughout this guide; however, only overview information about Web "
+"services is provided. If you are new to creating Web services, please see "
+"consult your Web services platform documentation."
+msgstr ""
+"El componente del servicio de transacciones XML de JBossTS (nos referimos a "
+"este como XTS) soporta la coordinación de servicios web públicos y privados "
+"en una transacción empresarial. Por lo tanto, para comprender XTS, debe "
+"estar familiarizado con los servicios web y también debe comprender un poco "
+"con relación a las transacciones. Este capítulo introduce XTS y brinda una "
+"pequeña sinopsis de las tecnologías que conforman los servicios web "
+"estándares. Además, este capítulo explora algunos de los fundamentos de la "
+"tecnología de transaccionamiento y la manera en que se puede aplicar a los "
+"servicios web. Mucho del contenido presentado en este capítulo se aborda en "
+"más detalle en este manual; sin embargo, solo brindamos una breve sinopsis "
+"sobre los servicios web. Si está aprendiendo a crear servicios web, consulte "
+"la documentación de la plataforma de servicios web. "
+
+#. Tag: para
+#: Introduction.xml:12
+#, no-c-format
+msgid ""
+"JBossTS provides as the XTS component a transaction solution for Web "
+"services. Using XTS, business partners can coordinate complex business "
+"transactions in a controlled and reliable manner. The JBossTS Web Services "
+"API supports a transactional coordination model based on the WS-C, WS-Atomic "
+"Transaction and WS-Business Activity specifications. WS-C is a generic "
+"coordination framework developed by IBM, Microsoft and BEA, WS-Atomic "
+"Transaction and WS-Business Activity are transaction protocols that utilize "
+"this framework."
+msgstr ""
+"JBossTS proporciona como el componente XTS una solución de transacción para "
+"los servicios web. Al utilizar XTS, los socios pueden coordinar complejas "
+"transacciones empresariales de una manera controlada y confiable. La API "
+"JBossTS Web Services soporta un modelo de coordinación transaccional basado "
+"en las especificaciones WS-C, WS-Atomic Transaction y WS-Business Activity. "
+"WS-C es un marco de trabajo genérico de coordinación desarrollado por IBM, "
+"Microsoft y BEA, WS-Atomic Transaction y WS-Business Activity son protocolos "
+"de transacción que utilizan este marco de trabajo."
+
+#. Tag: para
+#: Introduction.xml:15
+#, no-c-format
+msgid ""
+"Web services are modular, reusable software components that are created by "
+"exposing business functionality through a Web service interface. Web "
+"services communicate directly with other Web services using standards-based "
+"technologies such as SOAP and HTTP. These standards-based communication "
+"technologies allow Web services to be accessed by customers, suppliers, and "
+"trading partners, independent of hardware operation system or programming "
+"environment. The result is a vastly improved collaboration environment as "
+"compared to today&#39;s EDI and business-to-business (B2B) solutions—an "
+"environment where businesses can expose their current and future business "
+"applications as Web services that can be easily discovered and accessed by "
+"external partners."
+msgstr ""
+"Los servicios web son modulares, componentes software reutilizables que son "
+"creados al exponer funcionalidades empresariales a través de una interfaz "
+"del servicio web. Los servicios web se comunican directamente con otros "
+"servicios web utilizando tecnologías basadas en estandares tal como SOAP y "
+"HTTP. Estas tecnologías de comunicación con base en estándares le permiten a "
+"los clientes, proveedores y socios acceder a servicios web de manera "
+"independiente del entorno de programación y del sistema de operación del "
+"hardware. El resultado es un entorno de colaboración mejorado comparado con "
+"las soluciones business-to-business (B2B) y EDI de hoy en día - un entorno "
+"en donde las compañias pueden exponer sus aplicaciones empresariales "
+"actuales y futuras como servicios web que socios externos las pueden "
+"descubrir y acceder fácilmente. "
+
+#. Tag: para
+#: Introduction.xml:18
+#, no-c-format
+msgid ""
+"Web services, by themselves, are not fault tolerant. In fact, some of the "
+"reasons that make it an attractive development solution are also the same "
+"reasons that service-based applications may have drawbacks:"
+msgstr ""
+"Los servicios web en sí no toleran faltas. De hecho, algunas de las razones "
+"por las cuales son una solución de desarrollo atractiva son también razones "
+"por las que las aplicaciones basadas en servicios tienen desventajas: "
+
+#. Tag: para
+#: Introduction.xml:23
+#, no-c-format
+msgid ""
+"Application components that are exposed as Web services may be owned by "
+"third parties, which provides benefits in terms of cost of maintenance, but "
+"drawbacks in terms of having exclusive control over their behavior;"
+msgstr ""
+"Los componentes de aplicaciones que se exponen como servicios web pueden ser "
+"de propiedad de terceros, lo cual proporciona beneficios en términos de "
+"costo de mantenimiento pero genera desventajas en términos de tener control "
+"exclusivo sobre su comportamiento; "
+
+#. Tag: para
+#: Introduction.xml:28
+#, no-c-format
+msgid ""
+"Web services are usually remotely located which increases risk of failure "
+"due to increased network travel for invocations."
+msgstr ""
+"Los servicios web usualmente se encuentran ubicados remotamente, lo cual "
+"incrementa el riesgo de fallo debido a un incremento de las invocaciones en "
+"la red. "
+
+#. Tag: para
+#: Introduction.xml:33
+#, no-c-format
+msgid ""
+"Applications that have high dependability requirements, must find a method "
+"of minimizing the effects of errors that may occur when an application "
+"consumes Web services. One method of safeguarding against such failures is "
+"to interact with an application’s Web services within the context of a "
+"transaction. A transaction is simply a unit of work which is completed "
+"entirely, or in the case of failures is reversed to some agreed consistent "
+"state – normally to appear as if the work had never occurred in the first "
+"place. With XTS, transactions can span multiple Web services which mean that "
+"work performed across multiple enterprises can be managed with transactional "
+"support."
+msgstr ""
+"Las aplicaciones que tienen requerimientos de alta confiabilidad, deben "
+"encontrar un método de minimizar los efectos de los errores que puedan "
+"llegar a ocurrir cuando una aplicación consume los servicios web. Un método "
+"de salvaguardarse frente a tales fallos es el interactuar con los servicios "
+"web de una aplicación dentro del contexto de una transacción. Una "
+"transacción es simplemente una unidad de trabajo, la cual se completa "
+"totalmente, o en el caso de una falla se reversa a un estado consistente "
+"acordado - normalmente para aparecer como si el trabajo nunca hubiese "
+"ocurrido en primer lugar. Con XTS, las transacciones pueden abarcar "
+"múltiples servicios web, lo que significa que el trabajo realizado a través "
+"de múltiples compañias se puede administrar con soporte transaccional. "
+
+#. Tag: title
+#: Introduction.xml:37
+#, no-c-format
+msgid "Managing Service-Based Processes"
+msgstr "Administración de procesos basados en servicios"
+
+#. Tag: para
+#: Introduction.xml:38
+#, no-c-format
+msgid ""
+"XTS allows you to create transactions that drive complex business processes "
+"spanning multiple Web services. Current Web services standards do not "
+"address the requirements for a high-level coordination of services since in "
+"today’s Web services applications, which use single request/receive "
+"interactions, coordination is typically not a problem. However, for "
+"applications that engage multiple services among multiple business partners, "
+"coordinating and controlling the resulting interactions is essential. This "
+"becomes even more apparent when you realize that you generally have little "
+"in the way of formal guarantees when interacting with third-party Web "
+"services."
+msgstr ""
+"XTS le permite crear transacciones que dirigen procesos empresariales "
+"complejos que abarcan múltiples servicios web. Los estándares de servicios "
+"web actuales no abordan los requerimientos para una coordinación de "
+"servicios de alto nivel ya que en las aplicaciones de servicios web de hoy "
+"en día, la coordinación usualmente no es un problema. Sin embargo, para las "
+"aplicaciones que ocupan múltiples servicios entre múltiples socios, la "
+"coordinación y control de las interacciones resultantes es esencial. Esto es "
+"mucho más aparente cuando se da cuenta de que generalmente tiene pocas "
+"garantías al interactuar con servicios web de terceros. "
+
+#. Tag: para
+#: Introduction.xml:42
+#, no-c-format
+msgid ""
+"XTS provides the infrastructure for coordinating services during a business "
+"process. By organizing processes as transactions, business partners can "
+"collaborate on complex business interactions in a reliable manner, insuring "
+"the integrity of their data - usually represented by multiple changes to a "
+"database – but without the usual overheads and drawbacks of directly "
+"exposing traditional transaction-processing engines directly onto the web. "
+"The following example demonstrates how an application may manage service-"
+"based processes as transactions:"
+msgstr ""
+"XTS proporciona la infraestructura para coordinar servicios durante un "
+"proceso empresarial. Al organizar los procesos como transacciones, los "
+"socios pueden colaborar en interacciones empresariales complejas de una "
+"manera confiable, asegurando la integridad de sus datos - usualmente "
+"representada por múltiples cambios a una base de datos - pero sin los costos "
+"y desventajas de exponer directamente máquinas tradicionales de "
+"procesamiento de transacciones de manera directa en la web. El siguiente "
+"ejemplo demuestra la manera en que una aplicación puede administrar procesos "
+"basados en servicios como transacciones: "
+
+#. Tag: para
+#: Introduction.xml:45
+#, no-c-format
+msgid ""
+"The application in question allows a user to plan a social evening. This "
+"application is responsible for reserving a table at a restaurant, and "
+"reserving tickets to a show. Both activities are paid for using a credit "
+"card. In this example, each service represents exposed Web services provided "
+"by different service providers. XTS is used to envelop the interactions "
+"between the theater and restaurant services into a single (potentially) long-"
+"running business transaction. The business transaction must insure that "
+"seats are reserved both at the restaurant and the theater. If one event "
+"fails the user has the ability to decline both events, thus returning both "
+"services back to their original state. If both events are successful, the "
+"user’s credit card is charged and both seats are booked. As you may expect, "
+"the interaction between the services must be controlled in a reliable manner "
+"over a period of time. In addition, management must span several third-party "
+"services that are remotely deployed."
+msgstr ""
+"La aplicación en cuestión le permite al usuario planear una noche social. "
+"Esta aplicación es responsable de reservar una mesa en un restaurante y de "
+"reservar los boletos para un show. Ambas actividades se pagan con tarjeta de "
+"crédito. En este ejemplo, cada servicio representa servicios web expuestos "
+"brindados por diferentes proveedores de servicios. XTS se utiliza para "
+"envolver las interacciones entre el teatro y el restaurante en una sola "
+"(potencialmente) y larga transacción empresarial. La transacción empresarial "
+"debe asegurar que los asientos están reservados en el restaurante y en el "
+"teatro. Si un evento falla el usuario tiene la habilidad para rechazar ambos "
+"eventos y por lo tanto retornar ambos servicios de regreso a su estado "
+"original. Si ambos eventos tienen éxito, se carga la tarjeta de crédito del "
+"usuario y se reservan ambos asientos. Como se puede esperar, la interacción "
+"entre los servicios debe ser controlada de una manera confiable durante un "
+"periodo de tiempo. Además, la administración debe abarcar varios servicios "
+"de terceros que se despliegan remotamente. "
+
+#. Tag: para
+#: Introduction.xml:49
+#, no-c-format
+msgid ""
+"Without the backing of a transaction, an undesirable outcome may occur. For "
+"example, the user credit card may be charged, even though one or both of the "
+"bookings may have failed."
+msgstr ""
+"Sin el respaldo de una transacción, puede que se genere un resultado no "
+"deseado. Por ejemplo, puede que se cargue la tarjeta de crédito del usuario "
+"incluso si una o más de las reservas han fallado. "
+
+#. Tag: para
+#: Introduction.xml:53
+#, no-c-format
+msgid ""
+"This simple example describes the situations where XTS excels at supporting "
+"business processes across multiple enterprises. This example is further "
+"refined throughout this guide, and appears as a standard demonstrator "
+"(including source code) with the XTS distribution."
+msgstr ""
+"Este simple ejemplo describe las situaciones en donde XTS se destaca "
+"soportando procesos empresariales a través de múltiples compañias. Este "
+"ejemplo se perfecciona aún más en este manual y aparece como un demostrador "
+"estándar (incluyendo el código fuente) con la distribución XTS. "
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr "Servlets"
+
+#. Tag: para
+#: Introduction.xml:58
+#, no-c-format
+msgid ""
+"The WS-C, WS-Atomic Transaction and WS-Business Activity protocols are based "
+"on one-way interactions of entities rather than traditional synchronous "
+"request/response RPC style interactions. Entities (for example, transaction "
+"participants) invoke operations on other entities (for example, the "
+"transaction coordinator) in order to return responses to requests. What this "
+"means is that the programming model is based on peer-to-peer relationships, "
+"with the result that all services, whether they are participants, "
+"coordinators or clients, must have an active component that allows them to "
+"receive unsolicited messages."
+msgstr ""
+"Los protocolos WS-C, WS-Atomic Transaction y WS-Business Activity se basan "
+"en interacciones de una sola vía de entidades en vez de interacciones del "
+"estilo RPC petición/respuesta sincrónica tradicional. Las entidades (por "
+"ejemplo, participantes de transacciones) invocan operaciones en otras "
+"entidades (por ejemplo, el coordinador de transacciones) con el fin de "
+"retornar respuestas a peticiones. Lo que esto significa es que el modelo de "
+"programación se basa en relaciones compañero-a-compañero, con el resultado "
+"que todos los servicios, ya sean participantes, coordinadores o clientes, "
+"deben tener un componente activo que les permite recibir mensajes no "
+"solicitados. "
+
+#. Tag: para
+#: Introduction.xml:62
+#, no-c-format
+msgid ""
+"In the current implementation of XTS, the active component is achieved "
+"through the use of Java servlet technology. Each endpoint that can be "
+"communicated with via SOAP/XML is represented as a servlet (and published "
+"within JNDI). Fortunately for the developer, this use of servlets occurs "
+"transparently. The only drawback is that (currently) clients must reside "
+"within a domain capable of hosting servlets, i.e., an application server. It "
+"is our intention that future versions of XTS will provide configurable "
+"deployment options, allowing servlets where required, but not mandating them."
+msgstr ""
+"En la implementación actual de XTS, el componente activo se logra por medio "
+"del uso de la tecnología servlet Java. Cada punto final que se comunica por "
+"medio de SOAP/XML se representa como un servlet (y se publica dentro de "
+"JNDI). Afortunadamente para el desarrollador, este uso de servlets ocurre de "
+"manera transparente. La única desventaja es que (actualmente) los clientes "
+"deben residir dentro de un dominio capaz de ser host para servlets, por "
+"ejemplo, un servidor de aplicaciones. Es nuestra intención que las versiones "
+"futuras de XTS proporcionen opciones de despliegue configurables, "
+"permitiendo servlets cuando se necesite pero sin mandatos."
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr "SOAP"
+
+#. Tag: para
+#: Introduction.xml:67
+#, no-c-format
+msgid ""
+"SOAP has emerged as the de-facto message format for XML-based communication "
+"in the Web services arena. It is a lightweight protocol that allows the user "
+"to define the content of a message and to provide hints as to how recipients "
+"should process that message."
+msgstr ""
+"SOAP ha surgido como el formato de-facto de mensajes para la comunicación "
+"basada en XML en el campo de los servicios web. Es un protocolo ligero que "
+"le permite al usuario definir el contenido de un mensaje y le permite "
+"proporcionar claves de cómo los recipientes deben procesar ese mensaje. "
+
+#. Tag: para
+#: Introduction.xml:71
+#, no-c-format
+msgid ""
+"SOAP messages can be divided into two main categories: Remote Procedure Call "
+"(RPC) and Document Exchange (DE). The primary difference between the two "
+"categories is that the SOAP specification defines encoding rules and "
+"conventions for RPC. The document exchange model allows the exchange of "
+"arbitrary XML documents - a key ingredient of B2B document exchange. XTS is "
+"based on the loosely coupled document-exchange style, yet it can support "
+"transactions spanning Web service that use either document-exchange or RPC."
+msgstr ""
+"Los mensajes SOAP se pueden dividir en dos categorias principales: llamada "
+"de procedimiento remoto (RPC del inglés Remote Procedure Call) e intercambio "
+"de documentos (DE del inglés Document Exchange). La diferencia principal "
+"entre las dos categorias es que la especificación SOAP define las reglas de "
+"codificación y las convenciones para RPC. El modelo de intercambio de "
+"documentos permite el intercambio de documentos XML arbitrarios - un "
+"ingrediente clave del intercambio de documentos B2B. XTS se basa en el "
+"estilo de intercambio de documentos con acoplamiento débil pero puede "
+"soportar transacciones que abarcan servicios web que utilizan intercambio de "
+"documentos o RPC. "
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr "Lenguaje de descripción de servicios web "
+
+#. Tag: para
+#: Introduction.xml:76
+#, no-c-format
+msgid ""
+"WSDL is an XML-based language used to define Web service interfaces. An "
+"application that consumes a Web service parses the service’s WSDL document "
+"to discover the location of the service, the operations that the service "
+"supports, the protocol bindings the service supports (SOAP, HTTP, etc), and "
+"how to access them (for each operation, WSDL describes the format that the "
+"client must follow)."
+msgstr ""
+"WSDL es un lenguaje basado en XML que se utiliza para definir interfaces de "
+"servicios web. Una aplicación que consume un servicio web analiza "
+"sintácticamente el documento WSDL del servicio para descubrir la ubicación "
+"del servicio, las operaciones que el servicio soporta, los vinculos de "
+"protocolo que el servicio soporta (SOAP, HTTP, etc) y la manera de "
+"accederlos (para cada operación, WSDL describe el formato que el cliente "
+"debe seguir). "

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
===================================================================

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Participants.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Participants.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Participants.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,627 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Participants.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "Test"
+
+#. Tag: para
+#: Participants.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "This is a test paragraph"
+
+#. Tag: title
+#: Participants.xml:11
+#, no-c-format
+msgid "The Participant: an Overview"
+msgstr "El participante: sinopsis"
+
+#. Tag: para
+#: Participants.xml:12
+#, no-c-format
+msgid ""
+"The participant is the entity that performs the work pertaining to "
+"transaction management on behalf of the business services involved in an "
+"application. The Web service (for example, a theatre booking system) "
+"contains some business logic for reserving a seat, enquiring availability "
+"etc, but it will need to be supported by something that maintains "
+"information in a durable manner. Typically this will be a database, but it "
+"could be a file system, NVRAM, etc. Now, although the service may talk to "
+"the back-end database directly, it cannot commit or undo any changes it (the "
+"services) makes, since these are ultimately under the control of the "
+"transaction that scoped the work. In order for the transaction to be able to "
+"exercise this control, it must have some contact with the database. In XTS "
+"this is accomplished by the participant, and the role played by the "
+"participant between the transaction and back-end transaction processing "
+"infrastructure is shown in the following figure."
+msgstr ""
+"El participante es la entidad que realiza el trabajo en relación con la "
+"administración de transacciones de parte de los servicios empresariales "
+"involucrados en una aplicación. El servicio web (por ejemplo, un sistema de "
+"reservas de un teatro) contiene una lógica empresarial para reservar un "
+"asiento, para preguntar por la disponiblidad, etc pero es necesario que esté "
+"soportada por algo que mantenga la información de una manera durable. "
+"Usualmente la base de datos cumple esta función pero también puede ser un "
+"sistema de archivos, NVRAM, etc. Aunque el servicio le hable a la base de "
+"datos back-end directamente, no puede realizar cambios ni guardarlos ya que "
+"ultimadamente están bajo el control de la transacción que realizó el "
+"trabajo. Para que la transacción pueda ejercer este control debe tener "
+"contacto con la base de datos. En XTS esto lo logra el participante y la "
+"siguiente figura muestra el papel que tiene el participante entre la "
+"transacción y la infraestructura de procesamiento de transacciones. "
+
+#. Tag: caption
+#: Participants.xml:19
+#, no-c-format
+msgid "Transactions, Participants, and Back-End Transaction Control"
+msgstr "Transacciones, participantes y control de transacciones"
+
+#. Tag: para
+#: Participants.xml:21
+#, no-c-format
+msgid ""
+"Each participant in XTS is related to either the Atomic Transaction or "
+"Business Activity protocols. In the following sections we’ll consider both "
+"protocols and their respective participants."
+msgstr ""
+"Cada participante en XTS está relacionado ya sea con los protocolos de "
+"actividad empresarial o con el de transacción atómica. En las siguiente "
+"secciones vamos a considerar ambos protocolos y sus participantes "
+"respectivos. "
+
+#. Tag: title
+#: Participants.xml:25
+#, no-c-format
+msgid "Atomic Transaction"
+msgstr "Transacción atómica"
+
+#. Tag: para
+#: Participants.xml:26
+#, no-c-format
+msgid ""
+"All Atomic Transaction participants are instances of one of the following "
+"interfaces."
+msgstr ""
+"Todos los participantes transacción atómica son instancias de las siguientes "
+"interfaces. "
+
+#. Tag: title
+#: Participants.xml:31
+#, no-c-format
+msgid "Durable2PCParticipant"
+msgstr "Durable2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:32
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Durable2PC protocol with "
+"the following signatures, as per the <interfacename>com.arjuna.wst."
+"Durable2Participant</interfacename> interface:"
+msgstr ""
+"Este participante soporta el protocolo Transaction Durable2PC WS-Atomic con "
+"las siguientes firmas de acuerdo con la interfaz <interfacename>com.arjuna."
+"wst.Durable2Participant</interfacename>: "
+
+#. Tag: para
+#: Participants.xml:38
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the <code>com.arjuna.wst."
+"Vote</code>. Values are: <code>ReadOnly</code>, indicating the participant "
+"does not need to be informed of the transaction outcome as no state updates "
+"were made; Prepared, indicating the participant is prepared to commit or "
+"rollback depending on the final transaction outcome, and it has made "
+"sufficient state updates persistent to accomplish this; and Aborted, "
+"indicating the participant has aborted and the transaction should also "
+"attempt to do so."
+msgstr ""
+"<emphasis>prepare</emphasis>: el participante debe realizar cualquier "
+"trabajo necesario para permitirle guardar o deshacer los cambios realizados "
+"por el servicio web bajo el ámbito de la transacción. La implementación es "
+"libre de hacer lo que necesite hacer con el fin de llevar a cabo el contrato "
+"implícito entre este y el coordinador. Se espera que el participante indique "
+"si puede preparar o no retornando una instancia del <code>com.arjuna.wst."
+"Vote</code>. Los valores son: <code>ReadOnly</code>, indica que el "
+"participante no necesita ser informado del resultado de la transacción ya "
+"que no se realizaron actualizaciones en el estado; Prepared, indica que el "
+"participante está preparado para guardar o deshacer cambios dependiendo del "
+"resultado final de la transacción y ha realizado suficientes actualizaciones "
+"persistentes en el estado para lograr esto; y Aborted, indica que el "
+"participante ha abortado y la transacción también debe tratar de hacerlo."
+
+#. Tag: para
+#: Participants.xml:43 Participants.xml:81
+#, no-c-format
+msgid ""
+"<emphasis>commit</emphasis>: the participant should make permanent the work "
+"that it controls. What it does will depend upon its implementation, for "
+"example, commit the reservation of the theatre ticket. The participant will "
+"then return an indication of whether or not it succeeded."
+msgstr ""
+"<emphasis>commit</emphasis>: el participante debe hacer permanente el "
+"trabajo que controla. Lo que hace dependerá de su implementación, por "
+"ejemplo, guarde los cambios de la reservación del tiquete del teatro. Luego "
+"el participanto retornará una indicación de si tuvo éxito o no."
+
+#. Tag: para
+#: Participants.xml:48 Participants.xml:86
+#, no-c-format
+msgid ""
+"<emphasis>rollback</emphasis>: the participant should undo the work that it "
+"controls. The participant will then return an indication of whether or not "
+"it succeeded."
+msgstr ""
+"<emphasis>rollback</emphasis>: el participante debe deshacer el trabajo que "
+"controla. Luego el participante retornará una indicación de si tuvo éxito o "
+"no."
+
+#. Tag: para
+#: Participants.xml:53 Participants.xml:91
+#, no-c-format
+msgid ""
+"<emphasis>commitOnePhase</emphasis>: if there is only a single "
+"TwoPCParticipant registered with the transaction, then the coordinator can "
+"optimize the protocol and simply tell the participant to commit: there is no "
+"need for a preparatory phase since consensus is implicit."
+msgstr ""
+"<emphasis>commitOnePhase</emphasis>: si hay un solo TwoPCParticipant "
+"registrado con la transacción entonces el coordinator puede optimizar el "
+"protocolo y simplemente decirle al participante que guarde los cambios: no "
+"hay necesidad de una fase preparatoria ya que el consenso está implícito."
+
+#. Tag: para
+#: Participants.xml:58 Participants.xml:96
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: during recovery the participant can inquire as "
+"to the status of the transaction it was registered with. If that transaction "
+"is no longer available (has rolled back) then this operation will be invoked "
+"by the coordination service."
+msgstr ""
+"<emphasis>unknown</emphasis>: durante la recuperación el participante puede "
+"preguntar por el estatus de la transacción con la que due registrada. Si esa "
+"transacción ya no está disponible (se ha deshecho) entonces esta operación "
+"será invocada por el servicio de coordinación."
+
+#. Tag: para
+#: Participants.xml:63 Participants.xml:101
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: during recovery the participant can enquire as "
+"to the status of the transaction it was registered with. If an error occurs "
+"(for example, the transaction service is unavailable) then this operation "
+"will be invoked."
+msgstr ""
+"<emphasis>error</emphasis>: durante la recuperación el participante puede "
+"preguntar sobre el estatus de la transacción con la que fue registrada. Si "
+"se presenta un error (por ejemplo, el servicio de transacción no está "
+"disponible) entonces se invocará esta operación. "
+
+#. Tag: title
+#: Participants.xml:69
+#, no-c-format
+msgid "Volatile2PCParticipant"
+msgstr "Volatile2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:70
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Volatile2PC protocol "
+"with the following signatures, as per the <interfacename>com.arjuna.wst."
+"Volatile2Participant</interfacename> interface:"
+msgstr ""
+"Este participante soporta el protocolo WS-Atomic Transaction Volatile2PC con "
+"las siguientes firmas de acuerdo con la interfaz <interfacename>com.arjuna."
+"wst.Volatile2Participant</interfacename>:"
+
+#. Tag: para
+#: Participants.xml:76
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the com.arjuna.wst.Vote. "
+"Values are: ReadOnly, indicating the participant does not need to be "
+"informed of the transaction outcome as no state updates were made; Prepared, "
+"indicating the participant is prepared to commit or rollback depending on "
+"the final transaction outcome, and it has made sufficient state updates "
+"persistent to accomplish this; and Aborted, indicating the participant has "
+"aborted and the transaction should also attempt to do so."
+msgstr ""
+"<emphasis>prepare</emphasis>: el participante debe realizar cualquier "
+"trabajo necesario para permitirle guardar o deshacer los cambios realizados "
+"por el servicio Web bajo el ámbito de la transacción. La implementación es "
+"libre de hacer lo que necesite para llevar acabo el contrato implícito entre "
+"este y el coordinador. Se espera que el participante indique si puede "
+"preparar o no retornando una instancia del com.arjuna.wst.Vote. Los valores "
+"son: ReadOnly, indica que el participante no necesitar estar informado del "
+"resultado de la transacción ya que no se realizaron actualizaciones; "
+"Prepared, indica que el participante está preparado para guardar o deshacer "
+"los cambios dependiendo del resultado final de la transacción y ha realizado "
+"suficientes actualizaciones persistentes de estado para lograr esto; y "
+"Aborted, indica que el participante ha abortado y la transacción también "
+"debe intentar hacerlo."
+
+#. Tag: title
+#: Participants.xml:107
+#, no-c-format
+msgid "Business Activity"
+msgstr "Actividad empresarial"
+
+#. Tag: para
+#: Participants.xml:108
+#, no-c-format
+msgid ""
+"All Business Activity participants are instances of the following interfaces."
+msgstr ""
+"Todos los participantes de una actividad empresarial son instancias de las "
+"siguientes interfaces. "
+
+#. Tag: title
+#: Participants.xml:113
+#, no-c-format
+msgid "BusinessAgreementWithParticipantCompletion"
+msgstr "BusinessAgreementWithParticipantCompletion"
+
+#. Tag: para
+#: Participants.xml:114
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"Este participante soporta el protocolo WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> con las siguientes "
+"firmas de acuerdo con la interfaz <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename>:"
+
+#. Tag: para
+#: Participants.xml:120 Participants.xml:158
+#, no-c-format
+msgid ""
+"<emphasis>close</emphasis>: the transaction has completed successfully. The "
+"participant previously informed the coordinator that it was ready to "
+"complete."
+msgstr ""
+"<emphasis>close</emphasis>: la transacción se ha completado con éxito. El "
+"participante informó previamente al coordinador que estaba listo para "
+"completar."
+
+#. Tag: para
+#: Participants.xml:125
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work. The participant cannot have informed the "
+"coordinator that it has completed."
+msgstr ""
+"<emphasis>cancel</emphasis>: la transacción ha sido cancelada y el "
+"participante debe deshacer cualquier trabajo que se haya realizado. El "
+"participante no pudo haber informado al coordinador de que se ha completado."
+
+#. Tag: para
+#: Participants.xml:130 Participants.xml:168
+#, no-c-format
+msgid ""
+"<emphasis>compensate</emphasis>: the transaction has canceled. The "
+"participant previously informed the coordinator that it had finished work "
+"but could compensate later if required, so it is now requested to do so."
+msgstr ""
+"<emphasis>compensate</emphasis>: la transacción ha sido cancelada. El "
+"participante informó previamente al coordinador que había terminado de "
+"trabajar pero que podía compensar más tarde si era necesario así que ahora "
+"se le piede que lo haga."
+
+#. Tag: para
+#: Participants.xml:135 Participants.xml:178
+#, no-c-format
+msgid "<emphasis>status</emphasis>: return the status of the participant."
+msgstr "<emphasis>status</emphasis>: retorna el estatus del participante."
+
+#. Tag: para
+#: Participants.xml:140 Participants.xml:183
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: if the participant inquires as to the status "
+"of the transaction it was registered with and that transaction is no longer "
+"available (has rolled back) then this operation will be invoked by the "
+"coordination service."
+msgstr ""
+"<emphasis>unknown</emphasis>: si el participante pregunta sobre el estatus "
+"de la transacción con la que fue registrado y esa transacción ya no está "
+"disponible (se han deshecho los cambios) entonces el servicio de "
+"coordinación inovocará esta operación."
+
+#. Tag: para
+#: Participants.xml:145 Participants.xml:188
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: if the participant enquired as to the status of "
+"the transaction it was registered with and an error occurs (for example, the "
+"transaction service is unavailable) then this operation will be invoked."
+msgstr ""
+"<emphasis>error</emphasis>: si el participante pregunta sobre el estatus de "
+"la transacción con la que fue registrado y se presenta un error (por "
+"ejemplo, el servicio de transacciones no se encuentra disponible) entonces "
+"se invocará esta operación."
+
+#. Tag: title
+#: Participants.xml:151
+#, no-c-format
+msgid "BusinessAgreementWithCoordinatorCompletion"
+msgstr "BusinessAgreementWithCoordinatorCompletion"
+
+#. Tag: para
+#: Participants.xml:152
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"Este participante soporta el protocolo WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> con las siguientes "
+"firmas de acuerdo con la interfaz <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename>:"
+
+#. Tag: para
+#: Participants.xml:163
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work."
+msgstr ""
+"<emphasis>cancel</emphasis>: la transacción ha sido cancelada y el "
+"participante debe deshacer cualquier trabajo."
+
+#. Tag: para
+#: Participants.xml:173
+#, no-c-format
+msgid ""
+"<emphasis>complete</emphasis>: the coordinator is informing the participant "
+"that all work it needs to do within the scope of this business activity has "
+"been received."
+msgstr ""
+"<emphasis>complete</emphasis>: el coordinador le está informando al "
+"participante que ha recibido todo el trabajo que necesita realizar dentro "
+"del ámbito de esta actividad empresarial."
+
+#. Tag: title
+#: Participants.xml:194
+#, no-c-format
+msgid "BAParticipantManager"
+msgstr "BAParticipantManager"
+
+#. Tag: para
+#: Participants.xml:195
+#, no-c-format
+msgid ""
+"In order for the Business Activity protocol to work correctly, the "
+"participants must be able to autonomously signal the coordinator that they "
+"have left the activity (exited) or are ready to complete and (if necessary) "
+"compensate (completed). Unlike the Atomic Transaction protocol, where all "
+"interactions between the coordinator and participants are instigated by the "
+"coordinator when the transaction terminates, this interaction pattern "
+"requires the participant to be able to talk to the coordinator at any time "
+"during the lifetime of the business activity."
+msgstr ""
+"Para que el protocolo de la actividad empresarial funcione correctamente, "
+"los participantes deben poder señalar de manera autónoma al coordinador de "
+"que han dejado la actividad (han salido) o de que están listos para "
+"completar y (si es necesario) compensar (competar). De manera opuesta al "
+"protocolo de transacción atómica en donde todas las interacciones entre el "
+"coordinador y los participantes son instigadas por el coordinador cuando la "
+"transacción termina, este patrón de interacción requiere que el participante "
+"pueda hablarle al coordinador en cualquier momento durante el tiempo de vida "
+"de la actividad empresarial. "
+
+#. Tag: para
+#: Participants.xml:199
+#, no-c-format
+msgid ""
+"As such, whenever a participant is registered with a business activity, it "
+"receives a handle on the coordinator. This handle is an instance of the "
+"<interfacename>BAParticipantManager</interfacename> interface, located in "
+"<code>com.arjuna.wst.BAParticipantManager</code>, with the following methods:"
+msgstr ""
+"Como tal cuando un participante es registrado con una actividad empresarial, "
+"recibe una manija en el coordinador. Esta manija es una instancia de la "
+"interfaz <interfacename>BAParticipantManager</interfacename> que se "
+"encuentra en <code>com.arjuna.wst.BAParticipantManager</code>, con los "
+"siguientes métodos:"
+
+#. Tag: para
+#: Participants.xml:204
+#, no-c-format
+msgid ""
+"<emphasis>exit</emphasis>: the participant has exited the business activity. "
+"The participant uses this to inform the coordinator that is has left the "
+"activity. It will not be informed when (and how) the business activity "
+"terminates."
+msgstr ""
+"<emphasis>exit</emphasis>: el participante ha salido de la actividad "
+"empresarial. El participante utiliza esto para informarle al coordinador de "
+"que ha dejado la actividad. No se le informará cuándo (y cómo) se termina la "
+"actividad empresarial."
+
+#. Tag: para
+#: Participants.xml:209
+#, no-c-format
+msgid ""
+"<emphasis>completed</emphasis>: the participant has completed it works, but "
+"wishes to continue in the business activity, so that it will eventually be "
+"told when (and how) the activity terminates. The participant may later be "
+"asked to compensate for the work it has done."
+msgstr ""
+"<emphasis>completed</emphasis>: el participante ha completado su trabajo "
+"pero desea continuar en la actividad empresarial asi que eventualmente se le "
+"dirá cuándo (y cómo) se termina la actividad. Puede que más adelante se le "
+"pida al participante que compense el trabajo que ha realizado."
+
+#. Tag: para
+#: Participants.xml:214
+#, no-c-format
+msgid ""
+"<emphasis>fault</emphasis>: the participant encountered an error during "
+"normal activation and has compensated. This places the business activity "
+"into a mandatory cancel-only mode."
+msgstr ""
+"<emphasis>fault</emphasis>: el participante encontró un error durante la "
+"activación normal y ha compensado. Esto pone la actividad empresarial en un "
+"solo modo obligatorio de cancelar."
+
+#. Tag: title
+#: Participants.xml:222
+#, no-c-format
+msgid "Participant Creation and Deployment"
+msgstr "Creación y despliegue de participantes"
+
+#. Tag: para
+#: Participants.xml:223
+#, no-c-format
+msgid ""
+"As has been shown, the participant provides the plumbing that drives the "
+"transactional aspects of the service. This section discusses the specifics "
+"of Participant programming and usage."
+msgstr ""
+"Como se mostró anteriormente, el participante proporciona la tubería que "
+"lleva los aspectos transaccionales del servicio. Esta sección discute los "
+"aspectos especificos del uso y programación de los participantes."
+
+#. Tag: title
+#: Participants.xml:227
+#, no-c-format
+msgid "Implementing Participants"
+msgstr "Implementación de participantes"
+
+#. Tag: para
+#: Participants.xml:228
+#, no-c-format
+msgid ""
+"Implementing a participant is, in theory, a relatively straightforward task, "
+"though depending on the complexity of the transactional infrastructure that "
+"the participant is to manage, the actual size and complexity of a "
+"participant will vary. The participant interfaces can be found under "
+"<code>com.arjuna.wst</code>. Your implementation must implement one of these "
+"interfaces."
+msgstr ""
+"En teoria la implementación de un participante es una tarea relativamente "
+"sencilla, aunque depende de la complejidad de la infraestructura "
+"transaccional que el participante administrará. Las interfaces del "
+"participante se pueden encontrar bajo <code>com.arjuna.wst</code>. Su "
+"implementación debe implementar unoa de estas interfaces. "
+
+#. Tag: title
+#: Participants.xml:233
+#, no-c-format
+msgid "Deploying Participants"
+msgstr "Implementación de participantes"
+
+#. Tag: para
+#: Participants.xml:234
+#, no-c-format
+msgid ""
+"In order to allow Participants to be located remote from the Transaction "
+"Manager, XTS includes transparent message routing functionality. The "
+"Participant classes are not exposed directly as web services, but rather "
+"registered with a web service which receives messages from the Transaction "
+"Manager and maps them to appropriate method invocations on the relevant "
+"Participant instance. Transactional web services will typically enroll a new "
+"Participant instance of the desired type for each new transaction. A unique "
+"identifier must be provided at enrollment time and will be used to map "
+"transaction protocol messages to the appropriate participant instance. Note "
+"that Participant method invocations do not occur in a specific transaction "
+"context. Therefore, if your Participant implementation requires knowledge of "
+"the transaction context (for example, to look up state information in a "
+"persistent store) then you should provide this to the Participant instance, "
+"typically as an argument to the constructor function. Sample Participant "
+"implementations and usage can be found in the demonstration application "
+"included with XTS."
+msgstr ""
+"Con el fin de permitir localizar a los participantes de manera remota desde "
+"el administrador de transacciones, XTS incluye funcionalidad de enrutamiento "
+"transparente de mensajes. Las clases Participant no están expuestas "
+"directamente como servicios web si no más bien son registradas con un "
+"servicio web el cual recibe mensajes del administrador de transacciones y "
+"los mapea a las invocaciones de método apropiadas en la instancia "
+"Participant relevante. Los servicios web transaccionales usualmente "
+"inscribirán una nueva instancia participante del tipo deseado para cada "
+"nueva transacción. En el momento de inscripción se debe proporcionar un "
+"identificador único y este se utilizará para mapear los mensajes del "
+"protocolo de transacciones a la instancia participante apropiada. Observe "
+"que las invocaciones de método Participant no ocurren en un contexto de "
+"transacción en especifico. Por lo tanto si su implementación Participant "
+"requiere conocimiento del contexto de transacción (por ejemplo, buscar "
+"información de estado en un almacenamiento persistente) entonces debe "
+"proporcionar esto a la instancia Participant, usualmente como un argumento "
+"para la función constructora. En la aplicación de demonstración incluída con "
+"XTS encontrará las implementaciones Participant de ejemplo. "
+
+#. Tag: para
+#: Participants.xml:238
+#, no-c-format
+msgid ""
+"Any application code which creates and enrolls Participants must be deployed "
+"along with the parts of XTS necessary for receiving and processing incoming "
+"messages from the Transaction Manager. This typically means including the "
+"appropriate XTS .jar, .wsr and .war files in your application. If you are "
+"deploying your application only a server which does not already contain a "
+"Transaction Manger installation, you will also need to deploy the XTS "
+"configuration files."
+msgstr ""
+"Cualquier código de aplicación que cree e inscriba participantes se debe "
+"desplegar junto con las partes de XTS necesarias para recibir y procesar "
+"mensajes entrantes del administrador de transacciones. Usualmente esto "
+"significa que debe incluir los archivos XTS apropiados .jar, .wsr y .war en "
+"su aplicación. Si está desplegando su aplicación en un servidor que todavía "
+"no tiene una instalación del administrador de transacciones también "
+"necesitará desplegar los archivos de configuración XTS. "
+
+#. Tag: para
+#: Participants.xml:242
+#, no-c-format
+msgid ""
+"In early access releases of the XTS product, the Transaction Manager and "
+"participant management functions are not provided as separable components. "
+"Configuration and deployment of the participant infrastructure is therefore "
+"as in the Transaction Manger section above. More flexible deployment of the "
+"XTS components will be available in the final release."
+msgstr ""
+"En los primeros lanzamientos del producto XTS, el administrador de "
+"transacciones y las funciones de administración del participante no se "
+"proporcionan como componentes separables. Por lo tanto el despliegue y "
+"configuración de la insfraestructura participante es como la del "
+"administrador de transacciones de la sección anterior. El lanzamiento final "
+"contará con un despliegue más flexible de los componentes XTS."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Preface.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Preface.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,22 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr "Prefacio"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Revision_History.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Revision_History.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,28 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "Historial de revisiones"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Stand-alone_Coordinator.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Stand-alone_Coordinator.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Stand-alone_Coordinator.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,38 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:6
+#, no-c-format
+msgid "Stand-alone Coordinator"
+msgstr "Coordinador autónomo"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introducción"
+
+#. Tag: para
+#: Stand-alone_Coordinator.xml:9
+#, no-c-format
+msgid ""
+"For configuring a stand-alone Web Services transaction coordinator, see the "
+"relevant chapter in the System Administrator’s Guide."
+msgstr ""
+"Para configurar un coordinador de transacciones de servicios web autónomo "
+"consulte el capítulo relevante en el manual del administrador del sistema. "

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/The_XTS_API.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/The_XTS_API.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/The_XTS_API.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,762 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr "La API XTS"
+
+#. Tag: title
+#: The_XTS_API.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introducción"
+
+#. Tag: para
+#: The_XTS_API.xml:9
+#, no-c-format
+msgid ""
+"This chapter shows how to use the XTS API. This is of use both at the client-"
+"side where applications consume transactional Web services, and at the "
+"service/participant side where transactions need to be coordinated with back-"
+"end systems."
+msgstr ""
+"Este capítulo muestra como utilizar la API XTS. Esta se utiliza en el lado "
+"del cliente en donde las aplicaciones consumen servicios web transaccionales "
+"y en el lado del servicio/participante en donde es necesario coordinar las "
+"transacciones con sistemas back-end. "
+
+#. Tag: title
+#: The_XTS_API.xml:15
+#, no-c-format
+msgid "API for the Atomic Transaction protocol"
+msgstr "API para el protocolo de transacción atómica "
+
+#. Tag: para
+#: The_XTS_API.xml:16
+#, no-c-format
+msgid ""
+"The following classes and interfaces are located within the <package>com."
+"arjuna.wst or com.arjuna.mw.wst</package> packages and sub-packages."
+msgstr ""
+"Las siguientes clases e interfaces se encuentran dentro de los paquetes y "
+"subpaquetes <package>com.arjuna.wst or com.arjuna.mw.wst</package>."
+
+#. Tag: title
+#: The_XTS_API.xml:20
+#, no-c-format
+msgid "Vote"
+msgstr "Vote"
+
+#. Tag: para
+#: The_XTS_API.xml:21
+#, no-c-format
+msgid ""
+"During the two-phase commit protocol, a participant will be asked to vote on "
+"whether or not it can prepare to confirm the work that it controls. It must "
+"return one of the following subtypes of <code>com.arjuna.wst.Vote</code>:"
+msgstr ""
+"Durante el protocolo de dos fases, se le pedirá a un participante que vote "
+"por si puede o no preparase para confirmar el trabajo que controla. Debe "
+"retornar uno de los siguiente subtipos de <code>com.arjuna.wst.Vote</code>:"
+
+#. Tag: para
+#: The_XTS_API.xml:27
+#, no-c-format
+msgid ""
+"<emphasis>Prepared</emphasis>: the participant indicates that it can prepare "
+"if asked to by the coordinator. It will not have committed at this stage "
+"however, since it does not know what the final outcome will be."
+msgstr ""
+"<emphasis>Prepared</emphasis>: el participante indica que se puede preparar "
+"si se lo pide el coordinador. Sin embargo en este punto no habrá guardado "
+"los cambios, ya que no conoce el resultado final."
+
+#. Tag: para
+#: The_XTS_API.xml:32
+#, no-c-format
+msgid ""
+"<emphasis>Aborted</emphasis>: the participant indicates that it cannot "
+"prepare and has in fact rolled back. The participant should not expect to "
+"get a second phase message."
+msgstr ""
+"<emphasis>Aborted</emphasis>: el participante indica que no se puede "
+"preparar y de hecho ha deshecho los cambios. El participante no debe esperar "
+"el obtener un mensaje de segunda fase."
+
+#. Tag: para
+#: The_XTS_API.xml:37
+#, no-c-format
+msgid ""
+"<emphasis>ReadOnly</emphasis>: the participant indicates that the work it "
+"controls has not made any changes to state that require it to be informed of "
+"the final outcome of the transaction. Essentially the participant is "
+"resigning from the transaction."
+msgstr ""
+"<emphasis>ReadOnly</emphasis>: el participante indica que el trabajo que "
+"controla no ha realizado ningún cambio que establezca que requiere ser "
+"informado del resultado final de la transacción. Esencialmente el "
+"participante está renunciando de la transacción."
+
+#. Tag: para
+#: The_XTS_API.xml:42
+#, no-c-format
+msgid ""
+"Thus a possible implementation of a 2PC participant’s prepare method may "
+"resemble the following:"
+msgstr ""
+"Por lo tanto una implementación posible del método prepare de un "
+"participante 2PC puede verse así: "
+
+#. Tag: screen
+#: The_XTS_API.xml:45
+#, no-c-format
+msgid ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+msgstr ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+
+#. Tag: title
+#: The_XTS_API.xml:47
+#, no-c-format
+msgid "The transaction context"
+msgstr "El contexto de transacción"
+
+#. Tag: para
+#: The_XTS_API.xml:48
+#, no-c-format
+msgid ""
+"A transaction is typically represented by some unique identifier and a "
+"reference to the coordinator which manages the transaction, for example, a "
+"URL. XTS allows transactions to be nested such that a transaction hierarchy "
+"(tree) may be formed. Thus, a transaction context may be a set of "
+"transactions, with the top-most transaction the root parent (superior)."
+msgstr ""
+"Una transacción usualmente es representada por algún identificador único y "
+"una referencia al coordinador que administra la transacción, por ejemplo, "
+"una URL. XTS permite anidar transacciones de manera que se pueda formar una "
+"jerarquía de transacciones (un árbol). Por lo tanto, un contexto de "
+"transacciones puede ser un grupo de transacciones, con la transacción "
+"superior siendo el padre raíz (superior). "
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr "TxContext"
+
+#. Tag: para
+#: The_XTS_API.xml:54
+#, no-c-format
+msgid ""
+"<code>com.arjuna.mw.wst.TxContext</code> is an opaque representation of a "
+"transaction context."
+msgstr ""
+"<code>com.arjuna.mw.wst.TxContext</code> es una representación opaca de un "
+"contexto de transacción."
+
+#. Tag: para
+#: The_XTS_API.xml:60
+#, no-c-format
+msgid ""
+"<emphasis>valid</emphasis>: this indicates whether or not the contents are "
+"valid."
+msgstr "<emphasis>valid</emphasis>: indica si el contenido es válido o no."
+
+#. Tag: para
+#: The_XTS_API.xml:65
+#, no-c-format
+msgid "<emphasis>equals</emphasis>: can be used to compare two instances."
+msgstr ""
+"<emphasis>equals</emphasis>: se puede utilizar para comparar dos instancias."
+
+#. Tag: title
+#: The_XTS_API.xml:71
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: The_XTS_API.xml:72
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserTransaction</classname> is the class that "
+"most users (for example, clients and services) will see. This isolates them "
+"from the underlying protocol-specific aspects of the XTS implementation. "
+"Importantly, a UserTransaction does not represent a specific transaction, "
+"but rather is responsible for providing access to an implicit per-thread "
+"transaction context; it is similar to the UserTransaction in the JTA "
+"specification. Therefore, all of the UserTransaction methods implicitly act "
+"on the current thread of control."
+msgstr ""
+"El <classname>com.arjuna.wst.UserTransaction</classname> es la clase que la "
+"mayoría de los usuarios (por ejemplo, clientes y servicios) verán. Esto los "
+"aisla de los aspectos subyacentes especificos del protocolo de la "
+"implementación XTS. Es importante mencionar que un UserTransaction no "
+"representa una transacción especifica, si no que es responsable de "
+"proporcionar acceso a un contexto de transacción implícito por-hilo; es "
+"similar al UserTransaction en la especificación JTA. Por lo tanto, todos los "
+"métodos UserTransaction actúan implícitamente en el hilo actual de control."
+
+#. Tag: para
+#: The_XTS_API.xml:76
+#, no-c-format
+msgid ""
+"A new transaction is begun and associated with the invoking thread by using "
+"the begin method. If there is already a transaction associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created transaction with the "
+"current thread."
+msgstr ""
+"Se inicia una nueva transacción y se asocia con el hilo invocador utilizando "
+"el método begin. Si ya hay una transacción asociada con el hilo entonces se "
+"presenta la excepción <code>WrongStateException</code>. Cuando tiene éxito, "
+"esta operación asocia la nueva transacción con el hilo actual. "
+
+#. Tag: para
+#: The_XTS_API.xml:79
+#, no-c-format
+msgid ""
+"The transaction is committed by the commit method. This will execute the "
+"Volatile2PC and Durable2PC protocols prior to returning. If there is no "
+"transaction associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. If the transaction "
+"ultimately rolls back then the <code>TransactionRolledBackException</code> "
+"is thrown. When complete, this operation disassociates the transaction from "
+"the current thread such that it becomes associated with no transaction."
+msgstr ""
+"El método commit guarda los cambios de la transacción. Esto ejecutará los "
+"protocolos Volatile2PC y Durable2PC antes de retornar. Si no hay "
+"transacciones asociadas con el hilo invocador entonces se presenta una "
+"<code>UnknownTransactionException</code>. Si la transacción ultimadamente "
+"deshace los cambios entonces se presenta una "
+"<code>TransactionRolledBackException</code>. Cuando completa, esta operación "
+"desasocia la transacción del hilo actual de tal manera que termina sin "
+"asociación a ninguna transacción. "
+
+#. Tag: para
+#: The_XTS_API.xml:82
+#, no-c-format
+msgid ""
+"The <code>rollback</code> operation will terminate the transaction and "
+"return normally if it succeeded, while throwing an appropriate exception if "
+"it didn’t. If there is no transaction associated with the invoking thread "
+"then <code>UnknownTransactionException</code> is thrown."
+msgstr ""
+"La operación <code>rollback</code> terminará la transacción y retornará de "
+"manera normal si tuvo éxito, y presentará la excepción apropiada si no tuvo "
+"éxito. Si no hay una transacción asociada con el hilo invocador entonces se "
+"presenta una <code>UnknownTransactionException</code>."
+
+#. Tag: title
+#: The_XTS_API.xml:86
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr "UserTransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+"UserTransactions se obtienen de un <code>UserTransactionFactory</code>."
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: The_XTS_API.xml:93
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface represents "
+"the service/container/participant’s (service-side users) typical way in "
+"which to interact with the underlying transaction service implementation. As "
+"with <interfacename>UserTransaction</interfacename> a "
+"<interfacename>TransactionManager</interfacename> does not represent a "
+"specific transaction, but rather is responsible for providing access to an "
+"implicit per-thread transaction context."
+msgstr ""
+"La interfaz <interfacename>TransactionManager</interfacename> representa la "
+"manera típica del servicio/contenedor/participante (usuarios del lado del "
+"servicio) en la cual interactúa con la implementación del servicio de "
+"transacciones subyacente. Como con <interfacename>UserTransaction</"
+"interfacename> un <interfacename>TransactionManager</interfacename> no "
+"representa una transacción especifica, sino que es responsable de "
+"proporcionar acceso a un contexto de transacción implícito por-hilo."
+
+#. Tag: para
+#: The_XTS_API.xml:97
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific transaction. In "
+"order to do this it is necessary to disassociate the thread from any "
+"transactions. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the transaction. The "
+"thread is then no longer associated with any transaction."
+msgstr ""
+"Un hilo de control puede requerir periodos de no-transaccionalidad de manera "
+"que pueda realizar trabajo que no esté asociado con una transacción en "
+"específico. Con el fin de lograr esto es necesario desasociar el hilo de "
+"cualquier transacción. El método suspend logra esto, retornando una "
+"instancia <code>TxContext</code>, la cual es una manija en la transacción. "
+"Por lo tanto el hilo ya no está asociado con ninguna transacción. "
+
+#. Tag: para
+#: The_XTS_API.xml:100
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with a transaction(s) via its <code>TxContext</code>. Prior to "
+"association, the thread is disassociated with any transaction(s) with which "
+"it may be currently associated. If the <code>TxContext</code> is null, then "
+"the thread is associated with no transaction. The "
+"<code>UnknownTransactionException</code> exception is thrown if the "
+"transaction that the <code>TxContext</code> refers to is invalid in the "
+"scope of the invoking thread."
+msgstr ""
+"Se puede utilizar el método <methodname>resume</methodname> para (re-)"
+"asociar un hilo con una transacción(es) por medio de su <code>TxContext</"
+"code>. Antes de la asociación, el hilo es desasociado con cualquier "
+"transacción(es) con las que puede estar actualmente asociado. Si el "
+"<code>TxContext</code> es nulo entonces el hilo no se asocia con ninguna "
+"transacción. Se presenta la excepción <code>UnknownTransactionException</"
+"code> si la transacción a la que se refiere el <code>TxContext</code> es "
+"inválida en el ámbito del hilo invocador."
+
+#. Tag: para
+#: The_XTS_API.xml:103
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current transaction, or null if there is "
+"none. Unlike suspend, this method does not disassociate the current thread "
+"from the transaction(s). This can be used to enable multiple threads to "
+"execute within the scope of the same transaction."
+msgstr ""
+"El método <methodname>currentTransaction</methodname> retorna el "
+"<code>TxContext</code> para la transacción actual, o nulo si no hay ninguna. "
+"De manera opuesta a suspend, este método no desasocia el hilo actual de la "
+"transacción(es). Esto se puede utilizar para habilitar hilos múltiples para "
+"ejecutar dentro del ámbito de la misma transacción."
+
+#. Tag: para
+#: The_XTS_API.xml:106
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a transaction, the "
+"container or participant must use:"
+msgstr ""
+"Con el fin de registrar y renunciar participantes con una transacción, el "
+"contenedor o el particpante deben utilizar: "
+
+#. Tag: para
+#: The_XTS_API.xml:111
+#, no-c-format
+msgid ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"Volatile2PC protocol; a unique identifier for the participant is also "
+"required. If there is no transaction associated with the invoking thread "
+"then the <code>UnknownTransactionException</code> exception is thrown. If "
+"the coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: lista el participante "
+"especificado con la transacción actual de tal manera que participará en el "
+"protocolo Volatile2PC; también se requiere un identificador único para el "
+"participante. Si no hay una transacción asociada con el hilo de invocación "
+"entonces se presenta la excepción <code>UnknownTransactionException</code>. "
+"Si el coordinador ya tiene un participante inscrito con el mismo "
+"identificador entonces se presentará una <code>AlreadyRegisteredException</"
+"code>. Si la transacción no se encuentra en un estado en donde los "
+"participantes se puedan inscribir (por ejemplo, está terminando) entonces se "
+"presentará una <code>WrongStateException</code>."
+
+#. Tag: para
+#: The_XTS_API.xml:116
+#, no-c-format
+msgid ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"2PC protocol; a unique identifier for the participant is also required. If "
+"there is no transaction associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: lista el participante "
+"especificado con la transacción actual de tal manera que participará en el "
+"protocolo 2PC; también se requiere un identificador único para el "
+"participante. Si no hay una transacción asociada con el hilo invocador "
+"entonces se presenta la excepción <code>UnknownTransactionException</code>. "
+"Si el coordinador ya tiene un participante inscrito con el mismo "
+"identificador, entonces se presentará una <code>AlreadyRegisteredException</"
+"code>. Si la transacción no está en un estado en donde los participantes se "
+"pueden inscribir (por ejemplo, está terminando) entonces se presentará una "
+"<code>WrongStateException</code>."
+
+#. Tag: title
+#: The_XTS_API.xml:122
+#, no-c-format
+msgid "TransactionFactory"
+msgstr "TransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr "TransactionManagers se obtienen de un <code>TransactionFactory</code>."
+
+#. Tag: title
+#: The_XTS_API.xml:130
+#, no-c-format
+msgid "API for the Business Activity protocol"
+msgstr "API para el protocolo de actividad empresarial"
+
+#. Tag: title
+#: The_XTS_API.xml:132
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr "UserBusinessActivity"
+
+#. Tag: para
+#: The_XTS_API.xml:133
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserBusinessActivity</classname> is the class "
+"that most users (for example, clients and services) will see. This isolates "
+"them from the underlying protocol-specific aspects of the XTS "
+"implementation. Importantly, a <code>UserBusinessActivity</code> does not "
+"represent a specific business activity, but rather is responsible for "
+"providing access to an implicit per-thread activity. Therefore, all of the "
+"<code>UserBusinessActivity</code> methods implicitly act on the current "
+"thread of control."
+msgstr ""
+"La <classname>com.arjuna.wst.UserBusinessActivity</classname> es la clase "
+"que la mayoría de los usuarios (por ejemplo, clientes y servicios) verán. "
+"Esto los aisla de los aspectos subyacentes especificos del protocolo de la "
+"implementación XTS. Es importante mencionar que un "
+"<code>UserBusinessActivity</code> no representa una actividad empresarial "
+"especifica sino que es responsable de proporcionar acceso a una actividad "
+"implícita por-hilo. Por lo tanto, todos los métodos "
+"<code>UserBusinessActivity</code> actúan de manera implícita en el hilo "
+"actual de control."
+
+#. Tag: para
+#: The_XTS_API.xml:137
+#, no-c-format
+msgid ""
+"A new business activity is begun and associated with the invoking thread by "
+"using the begin method. If there is already an activity associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created activity with the "
+"current thread."
+msgstr ""
+"Se inicia una nueva actividad empresarial y se asocia con el hilo de "
+"invocación utilizando el método begin. Si ya hay una actividad asociada con "
+"el hilo entonces se presenta la excepción <code>WrongStateException</code>. "
+"Al tener éxito, esta operación asocia la actividad recién creada con el hilo "
+"actual. "
+
+#. Tag: para
+#: The_XTS_API.xml:140
+#, no-c-format
+msgid ""
+"The business activity is completed successfully by the close method. This "
+"will execute the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol prior to returning. If there is no activity associated with the "
+"invoking thread then <code>UnknownTransactionException</code> is thrown. If "
+"the activity ultimately cancels then the "
+"<code>TransactionRolledBackException</code> is thrown. When complete, this "
+"operation disassociates the business activity from the current thread such "
+"that it becomes associated with no activity."
+msgstr ""
+"El método close completa de manera éxitosa la actividad empresarial. Este "
+"ejecutará el protocolo <code>BusinessAgreementWithParticipantCompletion</"
+"code> antes de retornar. Si no hay una actividad asociada con el hilo de "
+"invocación entonces se presenta una <code>UnknownTransactionException</"
+"code>. Si ultimadamente la actividad cancela entonces se presenta una "
+"<code>TransactionRolledBackException</code>. Cuando completa, esta operación "
+"desasocia la actividad empresarial del hilo actual de tal manera que no se "
+"asocia con ninguna actividad. "
+
+#. Tag: para
+#: The_XTS_API.xml:143
+#, no-c-format
+msgid ""
+"The cancel operation will terminate the business activity and return "
+"normally if it succeeded, while throwing an appropriate exception if it "
+"didn’t. If there is no activity associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. Any participants that "
+"had previously completed will be informed to compensate for their work."
+msgstr ""
+"La operación cancel terminará la actividad empresarial y retornará de manera "
+"normal si tiene éxito y presentará una excepción apropiada si no tuvo éxito. "
+"Si no hay una actividad asociada con el hilo invocador entonces se presenta "
+"una <code>UnknownTransactionException</code>. Se le informará a cualquier "
+"participante que haya completado previamente para que compensen su trabajo. "
+
+#. Tag: para
+#: The_XTS_API.xml:146
+#, no-c-format
+msgid ""
+"Some participants may have registered for the "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol, which "
+"requires the coordinator or application to inform them when all work that "
+"they need to do within the scope of a business activity has been performed. "
+"The application should therefore use the complete method to inform these "
+"participants."
+msgstr ""
+"Puede que algunos participantes se hayan registrado para el protocolo "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>, el cual requiere "
+"que el coordinador o la aplicación les informe cuando se haya realizado todo "
+"el trabajo que necesitaban hacer dentro del ámbito de una actividad "
+"empresarial. Por lo tanto, la aplicación debe utilizar el método complete "
+"para informarle a estos participantes. "
+
+#. Tag: title
+#: The_XTS_API.xml:150
+#, no-c-format
+msgid "UserBusinessActivityFactory"
+msgstr "UserBusinessActivityFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+"UserBusinessActivities se obtienen de un <code>UserBusinessActivityFactory</"
+"code>."
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr "BusinessActivityManager"
+
+#. Tag: para
+#: The_XTS_API.xml:157
+#, no-c-format
+msgid ""
+"The <interfacename>BusinessActivityManager</interfacename> interface "
+"represents the service/container/participant’s (service-side users) typical "
+"way in which to interact with the underlying business activity service "
+"implementation. As with <interfacename>UserBusinessActivity</interfacename> "
+"a <interfacename>BusinessActivityManager</interfacename> does not represent "
+"a specific activity, but rather is responsible for providing access to an "
+"implicit per-thread activity."
+msgstr ""
+"La interfaz <interfacename>BusinessActivityManager</interfacename> "
+"representa la manera típica del servicio/contenedor/participante (usuarios "
+"del lado del servicio) en que interactúan con la implementación del servicio "
+"de la actividad empresarial subyacente. Así como con "
+"<interfacename>UserBusinessActivity</interfacename> un "
+"<interfacename>BusinessActivityManager</interfacename> no representa una "
+"actividad especifica sino que es responsable de proporcionar acceso a una "
+"actividad implícita por-hilo."
+
+#. Tag: para
+#: The_XTS_API.xml:161
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific activity. In order "
+"to do this it is necessary to disassociate the thread from any business "
+"activities. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the activity. The "
+"thread is then no longer associated with any activity."
+msgstr ""
+"Un hilo de control puede requerir periodos de no-transaccionalidad de manera "
+"que pueda realizar el trabajo que no esté asociado con una actividad "
+"especifica. Con el fin de lograr esto es necesario des-asociar el hilo de "
+"cualquier actividad empresarial. El método suspend logra esto, retornando "
+"una instancia <code>TxContext</code>, la cual es una manija en la actividad. "
+"Por lo tanto el hilo ya no está asociado con ninguna actividad. "
+
+#. Tag: para
+#: The_XTS_API.xml:164
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with an activity (or activities) via its TxContext. Prior to "
+"association, the thread is disassociated with any activity with which it may "
+"be currently associated. If the <code>TxContext</code> is null, then the "
+"thread is associated with no activity. The "
+"<code>UnknownTransactionException</code> exception is thrown if the business "
+"activity that the TxContext refers to is invalid in the scope of the "
+"invoking thread."
+msgstr ""
+"El método <methodname>resume</methodname> se puede utilizar para (re-)"
+"asociar un hilo con una actividad (o actividades) por medio de su TxContext. "
+"Antes de la asociación, el hilo es desasociado con cualquier actividad con "
+"la que pueda estar actualmente asociado. Si el <code>TxContext</code> es "
+"nulo entonces el hilo no es asociado con ninguna actividad. Se presenta la "
+"excepción <code>UnknownTransactionException</code> si la actividad "
+"empresarial a la cual se refiere el TxContext es inválida en el ámbito del "
+"hilo de invocación."
+
+#. Tag: para
+#: The_XTS_API.xml:167
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current business activity, or null if there "
+"is none. Unlike suspend, this method does not disassociate the current "
+"thread from the activity. This can be used to enable multiple threads to "
+"execute within the scope of the same business activity."
+msgstr ""
+"El método <methodname>currentTransaction</methodname> retorna el "
+"<code>TxContext</code> para la actividad empresarial actual, o retorna nulo "
+"si no hay ninguno. De manera opuesta a suspend, este método no desasocia el "
+"hilo actual de la actividad. Esto se puede utilizar para habilitar múltiples "
+"hilos para ejecutar dentro del ámbito de la misma actividad empresarial."
+
+#. Tag: para
+#: The_XTS_API.xml:170
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a business activity, the "
+"container or participant must use:"
+msgstr ""
+"Con el fin de registrar y renunciar participantes con una actividad "
+"empresarial, el contenedor o participante debe utilizar:"
+
+#. Tag: para
+#: The_XTS_API.xml:175
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"enlist the specified participant with current business activity such that it "
+"will participate in the <code>BusinessAgreementWithParticipantCompletion</"
+"code> protocol; a unique identifier for the participant is also required. If "
+"there is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"lista el participante especificado con la actividad empresarial actual de "
+"tal manera que participará en el protocolo "
+"<code>BusinessAgreementWithParticipantCompletion</code>; también se requiere "
+"un identificador único para el participante. Si no hay una actividad "
+"empresarial asociada con el hilo de invocación entonces se presenta la "
+"excepción <code>UnknownTransactionException</code>. Si el coordinador ya "
+"tiene un participante inscrito con el mismo identificador, entonces se "
+"presentará una <code>AlreadyRegisteredException</code>. Si la actividad no "
+"está en un estado en donde los participantes se pueden inscribir (por "
+"ejemplo, está terminando) entonces se presentará un "
+"<code>WrongStateException</code>."
+
+#. Tag: para
+#: The_XTS_API.xml:180
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"enlist the specified participant with current activity such that it will "
+"participate in the <code>BusinessAgreementWithCoordinatorCompletion</code> "
+"protocol; a unique identifier for the participant is also required. If there "
+"is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"lista el participante especificado con la actividad actual de tal manera que "
+"participará en el protocolo "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>; también se requiere "
+"un identificador único para el participante. Si no hay una actividad "
+"empresarial asociada con el hilo de invocación entonces se presenta una "
+"<code>UnknownTransactionException</code>. Si el coordinador ya tiene un "
+"participante inscrito con el mismo identificador, entonces se presentará una "
+"<code>AlreadyRegisteredException</code>. Si la actividad no se encuentra en "
+"un estado en donde los participantes se puedan inscribir (por ejemplo, está "
+"terminando) entonces se presentará una <code>WrongStateException</code>."
+
+#. Tag: title
+#: The_XTS_API.xml:186
+#, no-c-format
+msgid "BusinessActivityManagerFactory"
+msgstr "BusinessActivityManagerFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
+"Los BusinessActivityManagers se obtienen de un "
+"<code>BusinessActivityManagerFactory</code>."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Transactional_Web_Services.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Transactional_Web_Services.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Transactional_Web_Services.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,144 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr "Servicios web transaccionales"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introducción"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:9
+#, no-c-format
+msgid ""
+"This chapter describes how to provide transactional support for new and "
+"existing Web services using the service-side facilities of XTS. It shows how "
+"new services can be made transactional with no additional programming, and "
+"how existing services can be made WS-T transaction-aware in a non-invasive "
+"fashion."
+msgstr ""
+"Este capítulo describe la manera de proporcionar soporte transaccional para "
+"servicios web existentes y nuevos utilizando las utilidades del lado del "
+"servicio de XTS. Muestra cómo se pueden hacer que los nuevos servicios sean "
+"transaccionales sin tener que utilizar programación adicional y la manera en "
+"que se puede hacer que los servicios existentes sean concientes de "
+"transacciones WS-T de una manera no invasiva. "
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr "Un servicio web transaccional"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:16
+#, no-c-format
+msgid ""
+"A Web service is a business-level entity. It encapsulates application logic "
+"needed to perform some domain-specific task, or is designed to delegate to a "
+"back-end system which executes that logic. Given it is part of application "
+"code, such non-functional requirements as transactionality should not "
+"impinge on its construction."
+msgstr ""
+"Un servicio web es una entidad a nivel empresarial. Encapsula la lógica de "
+"la aplicación para realizar alguna tarea especifica del dominio o está "
+"diseñada para delegar a un sistema back-end que ejecuta esa lógica. Dado que "
+"es parte del código de la aplicación, tales requerimientos no funcionales "
+"como transaccionalidad no deben afectar su construcción. "
+
+#. Tag: para
+#: Transactional_Web_Services.xml:19
+#, no-c-format
+msgid ""
+"To support this notion, XTS provides a suite of components designed to work "
+"at the SOAP stack level, which deal with transactional matters on behalf of "
+"a Web service without requiring any changes to that service. In XTS two "
+"context handling components are registered with the SOAP server and deal "
+"with context management on behalf of the service without the service having "
+"to worry about context propagation issues itself. This is shown in the "
+"following figure."
+msgstr ""
+"Para soportar esta noción, XTS proporciona una suite de componentes "
+"diseñados para trabajar a nivel de pila SOAP, la cual se encarga de los "
+"asuntos transaccionales de parte de un servicio web sin requerir ningun "
+"cambio a ese servicio. En XTS se registran dos componentes de manejo de "
+"contexto con el servidor SOAP y se encargan de la administración de contexto "
+"de parte del servicio sin que el servicio se tenga que preocupar de los "
+"problemas de propagación del contexto. Esto se muestra en la siguiente "
+"figura: "
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr "Manejadores de contexto registrados con el servidor SOAP"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:28
+#, no-c-format
+msgid ""
+"The detail of the context management that the context processor performs is "
+"unimportant to the Web service application logic, and is orthogonal to any "
+"work performed by any other protocol-specific context handlers too. However "
+"back-end systems which the Web service application logic uses (such as "
+"databases) are often interested in the front-end transaction context such "
+"that any operations invoked within its scope can be mapped onto a back-end "
+"transaction context. This is typically achieved at the back-end by wrapping "
+"a database driver in a veneer which implements both the interface of the "
+"original driver and hooks into the service-side API to access the "
+"transaction context details. The general architecture for this pattern is "
+"shown in the figure below."
+msgstr ""
+"Los detalles de la administración de contexto que el procesador de contexto "
+"realiza no son importantes para la lógica de la aplicacón de servicios web y "
+"es ortogonal para cualquier trabajo realizado por otros manejadores de "
+"contexto especificos de cierto protocolo. Sin embargo, los sistemas back-end "
+"que la lógica de aplicación del servicio web utiliza (tal como las bases de "
+"datos) con frecuencia están interesadas en el contexto de transacción front-"
+"end de tal manera que cualquier operación invocada dentro de su ámbito se "
+"pueda mapear a un contexto de transacción back-end. Usualmente esto se logra "
+"en el back-end envolviendo un controlador de base de datos en un enchapado "
+"que implemente tanto la interfaz del controlador original y se enganche en "
+"la API del lado del servicio para acceder los detalles de contexto de la "
+"transacción. La arquitectura general para este patrón aparece en la figura a "
+"continuación."
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:35
+#, no-c-format
+msgid "General Pattern for Back-End Integration, Service Side"
+msgstr "Patrón general de la integración back-end, lado del servicio"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:37
+#, no-c-format
+msgid ""
+"The missing element from this is the commit protocol which finally allows "
+"back-end work to be made durable or not at the end of a transaction. This is "
+"covered in the participant chapter where the participant/back-end relation "
+"is explored further."
+msgstr ""
+"El elemento que falta aqui es el protocolo para guardar los cambios el cual "
+"finalmente permite que el trabajo back-end se vuelva durable o no al final "
+"de una transacción. Esto lo abordamos en el capítulo participante en donde "
+"exploramos mejor la relación participante/back-end. "

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,920 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactions_Overview.xml:6
+#, no-c-format
+msgid "Transactions Overview"
+msgstr "Sinopsis de transacciones"
+
+#. Tag: para
+#: Transactions_Overview.xml:7
+#, no-c-format
+msgid ""
+"Transactions have emerged as the dominant paradigm for coordinating "
+"interactions between parties in a distributed system, and in particular to "
+"manage applications that require concurrent access to shared data. Much of "
+"the JBossTS Web Service API is based on contemporary transaction APIs whose "
+"familiarity will enhance developer productivity and lessen the learning "
+"curve. While the following section provides the essential information that "
+"you should know before starting to use XTS for building transactional Web "
+"Services, it should not be treated as a definitive reference to all "
+"transactional technology."
+msgstr ""
+"Las transacciones han surgido como el paradigma dominante para coordinar las "
+"interacciones entre partes en un sistema distribuido y en particular para "
+"administrar aplicaciones que requieren acceso simultáneo a datos "
+"compartidos. Gran parte de la JBossTS Web Service API se basa en APIs de "
+"transacción contemporáneas cuya familiaridad mejorará la productividad del "
+"desarrollador y disminuirá la curva de aprendizaje. Aunque la siguiente "
+"sección proporciona la información esencial que usted debe conocer antes de "
+"empezar a utilizar XTS para construir servicios web transaccionales, no la "
+"debe considerar como una referencia definitiva para toda la tecnología "
+"transaccional. "
+
+#. Tag: para
+#: Transactions_Overview.xml:10
+#, no-c-format
+msgid ""
+"A classic transaction is a unit of work that either completely succeeds, or "
+"fails with all partially completed work being undone. When a transaction is "
+"committed, all changes made by the associated requests are made durable, "
+"normally by committing the results of the work to a database. If a "
+"transaction should fail and is rolled back, all changes made by the "
+"associated work are undone. Transactions in distributed systems typically "
+"require the use of a transaction manager that is responsible for "
+"coordinating all of the participants that are part of the transaction."
+msgstr ""
+"Una transacción clásica es una unidad de trabajo que tiene éxito por "
+"completo o que falla deshaciendo el trabajo completado solo de manera "
+"parcial. Cuando se guardan los cambios de una transacción (commit), todos "
+"los cambios realizados por las peticiones asociadas se hacen durables, "
+"usualmente guardando los resultados del trabajo en una base de datos. Si una "
+"transacción falla y se deshace, todos los cambios realizados por el trabajo "
+"asociado se deshacen. Las transacciones en sistemas distribuidos por lo "
+"general requieren el uso de un administrador de transacciones que es el "
+"responsable de coordinar todos los participantes que son parte de la "
+"transacción. "
+
+#. Tag: para
+#: Transactions_Overview.xml:13
+#, no-c-format
+msgid ""
+"The main components involved in using and defining transactional Web "
+"Services using XTS are illustrated in Figure 1."
+msgstr ""
+"Los componentes principales involucrados al definir y utilizar servicios web "
+"transaccionales utilizando XTS se ilustran en la figura 1. "
+
+#. Tag: para
+#: Transactions_Overview.xml:18
+#, no-c-format
+msgid ""
+"A Transaction Service: The Transaction Service captures the model of the "
+"underlying transaction protocol and coordinates parties affiliated with the "
+"transaction according to that model."
+msgstr ""
+"Un servicio transacción: el servicio transacción captura el modelo del "
+"protocolo de transacciones subyacentes y coordina las partes afiliadas con "
+"la transacción de acuerdo a ese modelo. "
+
+#. Tag: para
+#: Transactions_Overview.xml:23
+#, no-c-format
+msgid ""
+"A Transaction API: Provides an interface for transaction demarcation and the "
+"registration of participants."
+msgstr ""
+"Una API transacción: proporciona una interfaz para la demarcación de "
+"transacciones y el registro de los participantes. "
+
+#. Tag: para
+#: Transactions_Overview.xml:28
+#, no-c-format
+msgid ""
+"A Participant: The entity that cooperates with the transaction service on "
+"behalf of its associated business logic."
+msgstr ""
+"Un participante: la entidad que coopera con el servicio de transacción de "
+"parte de su lógica empresarial asociada. "
+
+#. Tag: para
+#: Transactions_Overview.xml:33
+#, no-c-format
+msgid ""
+"The Context: Captures the necessary details of the transaction such that "
+"participants can enlist within its scope."
+msgstr ""
+"El contexto: captura los detalles necesarios de la transacción tales como "
+"que los participantes puedan alistarse dentro de su ámbito. "
+
+#. Tag: caption
+#: Transactions_Overview.xml:42
+#, no-c-format
+msgid "Web Services and XTS"
+msgstr "Servicios web y XTS"
+
+#. Tag: title
+#: Transactions_Overview.xml:45
+#, no-c-format
+msgid "The Coordinator"
+msgstr "El coordinador"
+
+#. Tag: para
+#: Transactions_Overview.xml:46
+#, no-c-format
+msgid ""
+"Associated with every transaction is a coordinator, which is responsible for "
+"governing the outcome of the transaction. The coordinator may be implemented "
+"as a separate service or may be co-located with the user for improved "
+"performance. Each coordinator is created by the transaction manager service, "
+"which is in effect a factory for those coordinators."
+msgstr ""
+"Hay un coordinador asociado con toda transacción, el cual es el responsable "
+"de determinar el resultado de la transacción. El coordinador se puede "
+"implementar como un servicio separado o se puede ubicar con el usuario para "
+"mejorar el rendimiento. El servicio administrador de transacciones crea cada "
+"coordinador, el cual es en efecto una fábrica para esos coordinadores. "
+
+#. Tag: para
+#: Transactions_Overview.xml:50
+#, no-c-format
+msgid ""
+"A coordinator communicates with enrolled participants to inform them of the "
+"desired termination requirements, for instance, whether they should accept "
+"(for example, confirm) or reject (for example, cancel) the work done within "
+"the scope of the given transaction. For example, whether to purchase the "
+"(provisionally reserved) flight tickets for the user or to release them. An "
+"application/client may wish to terminate a transaction in a number of "
+"different ways (for example, confirm or cancel). However, although the "
+"coordinator will attempt to terminate in a manner consistent with that "
+"desired by the client, it is ultimately the interactions between the "
+"coordinator and the participants that will determine the actual final "
+"outcome."
+msgstr ""
+"Un coordinador se comunica con los participantes inscritos para informarles "
+"de los requerimientos de terminación deseados, por ejemplo, si deben aceptar "
+"(por ejemplo, confirmar) o rechazar (por ejemplo, cancelar) el trabajo "
+"realizado dentro del ámbito de la transacción dada. Por ejemplo, si comprar "
+"los tiquetes de vuelo (reservados provisionalmente) o si liberarlos. Una "
+"aplicación/cliente puede terminar una transacción de diferentes maneras (por "
+"ejemplo, confirmar o cancelar). Sin embargo, aunque el coordinador tratará "
+"de terminar de una manera consistente con la deseada por el cliente, es "
+"ultimadamente las interacciones entre el coordinador y los participantes las "
+"que determinarán el resultado final. "
+
+#. Tag: para
+#: Transactions_Overview.xml:53
+#, no-c-format
+msgid ""
+"A transaction manager is typically responsible for managing coordinators for "
+"many transactions. The initiator of the transaction (for example, the "
+"client) communicates with a transaction manager and asks it to start a new "
+"transaction and associate a coordinator with the transaction. Once created, "
+"the context can be propagated to Web services in order for them to associate "
+"their work with the transaction."
+msgstr ""
+"Usualmente un administrador de transacciones es el responsable de "
+"administrar coordinadores para muchas transacciones. El iniciador de la "
+"transacción (por ejemplo, el cliente) se comunica con un administrador de "
+"transacciones y le pide que inicie una nueva transacción y que asocie un "
+"coordinador con la transacción. Una vez creado, el contexto se puede "
+"propagar en los servicios web con el fin de asociar su trabajo con la "
+"transacción. "
+
+#. Tag: title
+#: Transactions_Overview.xml:57
+#, no-c-format
+msgid "The Transaction Context"
+msgstr "El contexto de transacción"
+
+#. Tag: para
+#: Transactions_Overview.xml:58
+#, no-c-format
+msgid ""
+"In order for a transaction to span a number of services, certain information "
+"has to be shared between those services in order to propagate information "
+"about the transaction. This information is known as the Context. Using XTS, "
+"the context is automatically propagated and processed by transaction-aware "
+"components of an application. Though XTS removes most of the work associated "
+"with propagating contexts, it is still instructive to understand what "
+"information is captured in a context:"
+msgstr ""
+"Con el fin de que una transacción abarque un número de servicios, cierta "
+"información se debe compartir entre esos servicios para poder propagar la "
+"información sobre la transacción. Esta información se conoce como el "
+"contexto. Usando XTS, el contexto es propagado automáticamente y procesado "
+"por componentes concientes de transacciones de una aplicación. Aunque XTS "
+"remueve la mayoría del trabajo asociado con la propagación de contextos "
+"todavía es instructivo para comprender la información que es capturada en un "
+"contexto: "
+
+#. Tag: para
+#: Transactions_Overview.xml:64
+#, no-c-format
+msgid ""
+"A transaction identifier which guarantees global uniqueness for an "
+"individual transaction;"
+msgstr ""
+"Un identificador transacción, el cual garantiza unicidad global para una "
+"transacción individual; "
+
+#. Tag: para
+#: Transactions_Overview.xml:69
+#, no-c-format
+msgid ""
+"The transaction coordinator location or endpoint address so participants can "
+"be enrolled."
+msgstr ""
+"La ubicación del coordinador de transacciones o la dirección del punto final "
+"para que los participantes se puedan inscribir. "
+
+#. Tag: caption
+#: Transactions_Overview.xml:78
+#, no-c-format
+msgid "Web Services and Context Flow"
+msgstr "Servicios web y flujo de contexto "
+
+#. Tag: para
+#: Transactions_Overview.xml:80
+#, no-c-format
+msgid ""
+"As shown in Figure 2, whenever an application message is sent, the XTS "
+"Client API automatically creates a context and embeds it into the message. "
+"Similarly, any transaction-aware services are able to extract that context "
+"using the XTS service-side infrastructure and use it to perform work within "
+"the context of a particular transaction – even though that transaction was "
+"initiated elsewhere on the Web! The value of this approach is that the "
+"business logic contained within the client application and services are not "
+"peppered with transaction-processing code."
+msgstr ""
+"Como se puede ver en la figura 2, cuando se envía un mensaje aplicación, la "
+"API cliente XTS crea de manera automática un contexto y lo incluye en el "
+"mensaje. De manera similar, cualquier servicio conciente de transacciones "
+"pueden extraer ese contexto utilizando la infraestructura del lado del "
+"servicio XTS y utilizarlo para realizar trabajos dentro del contexto de una "
+"transacción en particular - ¡aunque esa transacción fue inicada en otro "
+"lugar en la web! El valor de este enfoque es que la lógica empresarial "
+"contenida dentro de la aplicación del cliente y los servicios no están "
+"salpicados con el código de procesamiento de transacciones. "
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr "Transacciones ACID"
+
+#. Tag: para
+#: Transactions_Overview.xml:85
+#, no-c-format
+msgid ""
+"Traditionally, transaction processing systems support ACID properties. ACID "
+"is an acronym for Atomic, Consistent, Isolated, and Durable. A unit of work "
+"has traditionally been considered transactional only if the ACID properties "
+"are maintained:"
+msgstr ""
+"Usualmente los sistemas de procesamiento de transacciones soportan "
+"propiedades ACID. ACID es un acrónimo de Atómico, Consistente, aislado "
+"(Isolated en inglés) y Durable. Una unidad de trabajo usualmente ha sido "
+"considerada como transaccional solo si se mantienen las propiedades ACID: "
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr ""
+"Atomicidad: la transacción ejecuta completamente o no ejecuta absolutamente "
+"nada."
+
+#. Tag: para
+#: Transactions_Overview.xml:96
+#, no-c-format
+msgid ""
+"Consistency: The effects of the transaction preserve the internal "
+"consistency of an underlying data structure."
+msgstr ""
+"Consistencia: los efectos de la transacción preservan la consistencia "
+"interna de una estructura de datos subyacente. "
+
+#. Tag: para
+#: Transactions_Overview.xml:101
+#, no-c-format
+msgid ""
+"Isolated: The transaction runs as if it were running alone with no other "
+"transactions running and is not visible to other transactions."
+msgstr ""
+"Aislado: La transacción ejecuta como si estuviera corriendo sola sin otras "
+"transacciones ejecutando y no es visible para otras transacciones. "
+
+#. Tag: para
+#: Transactions_Overview.xml:106
+#, no-c-format
+msgid ""
+"Durable: the transaction’s results will not be lost in the event of a "
+"failure."
+msgstr ""
+"Durable: el resultado de la transacción no se perderá en el evento de una "
+"falla. "
+
+#. Tag: title
+#: Transactions_Overview.xml:112
+#, no-c-format
+msgid "Two-Phase Commit"
+msgstr "Guardar cambios en dos fases"
+
+#. Tag: para
+#: Transactions_Overview.xml:113
+#, no-c-format
+msgid ""
+"The classical two-phase commit approach is the bedrock of JBossTS (and more "
+"generally of Web Services transactions). Two-phase commit provides "
+"coordination of parties that are involved in a transaction. In general, the "
+"flow of a two-phase commit transaction is as follows:"
+msgstr ""
+"El enfoque clásico de guardar cambios en dos fases es el cimiento de JBossTS "
+"(y de una manera más general de las transacciones de servicios web). El "
+"guardar los cambios en dos fases proporciona la cordinación de las partes "
+"que están involucradas en una transacción. Por lo general, el siguiente es "
+"el flujo de una transacción para guardar los cambios en dos fases: "
+
+#. Tag: para
+#: Transactions_Overview.xml:119
+#, no-c-format
+msgid "A transaction is started, and some work is performed."
+msgstr "Se inicia una transacción y se realiza algo de trabajo. "
+
+#. Tag: para
+#: Transactions_Overview.xml:124
+#, no-c-format
+msgid "Once the work is finished, the two-phase commit begins."
+msgstr ""
+"Una vez se ha terminado el trabajo entonces comienzan a guardarse los "
+"cambios en dos fases. "
+
+#. Tag: para
+#: Transactions_Overview.xml:129
+#, no-c-format
+msgid ""
+"The coordinator (transaction manager) of the transaction asks each resource "
+"taking part in the transaction whether it is prepared to commit."
+msgstr ""
+"El coordinador (administrador de transacciones) de la transacción le "
+"pregunta a cada recurso que toma parte en la transacción si está preparado "
+"para guardar los cambios. "
+
+#. Tag: para
+#: Transactions_Overview.xml:134
+#, no-c-format
+msgid ""
+"If all resources respond positively, the coordinator instructs all work "
+"performed to be made durable (usually committed to a database)."
+msgstr ""
+"Si todos los recursos responden de manera positiva, el coordinador le ordena "
+"que todo el trabajo realizado se haga durable (usualmente se guarda en una "
+"base de datos). "
+
+#. Tag: para
+#: Transactions_Overview.xml:139
+#, no-c-format
+msgid ""
+"If not, all work performed is rolled back (undone) such that the underlying "
+"data structures are in their original states."
+msgstr ""
+"Si no, todo el trabajo realizado se deshace de tal manera que las "
+"estructuras de datos subyacentes se encuentren en sus estados originales. "
+
+#. Tag: caption
+#: Transactions_Overview.xml:148
+#, no-c-format
+msgid "The Two-Phase Commit Protocol"
+msgstr "El protocolo para guardar cambios en dos fases"
+
+#. Tag: para
+#: Transactions_Overview.xml:151
+#, no-c-format
+msgid ""
+"During two-phase commit transactions, coordinators and resources keep track "
+"of activity in non-volatile data stores so that they can recover in the case "
+"of a failure."
+msgstr ""
+"Durante las transacciones para guardar cambios en dos fases, los "
+"coordinadores y los recursos mantienen un registro de la actividad en "
+"almacenamientos de datos no volátiles para poder recuperar en caso de una "
+"falla. "
+
+#. Tag: title
+#: Transactions_Overview.xml:156
+#, no-c-format
+msgid "The synchronization protocol"
+msgstr "El protocolo de sincronización "
+
+#. Tag: para
+#: Transactions_Overview.xml:157
+#, no-c-format
+msgid ""
+"As well as the two-phase commit protocol, traditional transaction processing "
+"systems employ an additional protocol, often referred to as the "
+"synchronization protocol. If you recall the original ACID properties, then "
+"you’ll remember that Durability is important in the case where state changes "
+"have to be available despite failures. What this means is that applications "
+"interact with a persistence store of some kind (e.g., a database) and this "
+"can impose a significant overhead – disk access is orders of magnitude "
+"slower than access to main computer memory."
+msgstr ""
+"Así como el protocolo para guardar cambios en dos fases, los sistemas de "
+"procesamiento de transacciones tradicionales emplean un protocolo adicional, "
+"con frecuencia conocido como protocolo de sincronización. Si se acuerda de "
+"las propiedades ACID originales entonces recordará que la durabilidad es "
+"importante en el caso en que los cambios en el estado tengan que estar "
+"disponibles apesar de las fallas. Lo que esto significa es que las "
+"aplicaciones interactúan con un almacenamiento persistente de alguna clase "
+"(por ejemplo, una base de datos) y esto puede llegar a presentar un alto "
+"costo - el acceso al disco es mucho más lento que el acceso a la memoria "
+"principal del computador. "
+
+#. Tag: para
+#: Transactions_Overview.xml:161
+#, no-c-format
+msgid ""
+"One apparently obvious solution to this problem would be to cache the state "
+"in main memory and only operate on that for the duration of a transaction. "
+"Unfortunately you’d then need some way of being able to flush the state back "
+"to the persistent store before the transaction terminates, or risk losing "
+"the full ACID properties. This is what the synchronization protocol does, "
+"with Synchronization participants."
+msgstr ""
+"Una solución aparentemente obvia para este problema sería el poner en caché "
+"el estado en la memoria principal y solo operar en ese por la duración de "
+"una transacción. Desafortunadamente entonces necesitaría alguna forma de "
+"poder vaciar el estado de regreso en el almacenamiento persistente antes de "
+"que la transacción termine o sino se arriesga a perder todas las propiedades "
+"ACID. Esta es lo que hace el protocolo de sincronozación con participantes "
+"sincronización."
+
+#. Tag: para
+#: Transactions_Overview.xml:164
+#, no-c-format
+msgid ""
+"Synchronizations are informed that a transaction is about to commit, so they "
+"can, for example, flush cached state, which may be being used to improve "
+"performance of an application, to a durable representation prior to the "
+"transaction committing. They are then informed when the transaction has "
+"completed and in what state it completed."
+msgstr ""
+"Se les informa a las sincronizaciones que una transacción está a punto de "
+"guardar cambios para que puedan, por ejemplo, vaciar estado en caché, el "
+"cual se puede estar utilizando para mejorar el rendimiento de una aplicación "
+"para una representación durable antes de que la transacción guarde los "
+"cambios. Luego se les informa cuando la transacción se ha completado y el "
+"estado que completó. "
+
+#. Tag: para
+#: Transactions_Overview.xml:169
+#, no-c-format
+msgid ""
+"Synchronizations essentially turn the two-phase commit protocol into a four-"
+"phase protocol:"
+msgstr ""
+"Esencialmente las sincronizaciones convierten el protocolo para guardar los "
+"cambios en dos fases en un protocolo de cuatro fases: "
+
+#. Tag: para
+#: Transactions_Overview.xml:174
+#, no-c-format
+msgid ""
+"Before the transaction starts the two-phase commit, all registered "
+"Synchronizations are informed. Any failure at this point will cause the "
+"transaction to roll back."
+msgstr ""
+"Antes de que la transacción inicie a guardar los cambios en dos fases, se le "
+"informa a todas las sincronizaciones registradas. Cualquier falla en este "
+"punto hará que se deshaga la transacción. "
+
+#. Tag: para
+#: Transactions_Overview.xml:179
+#, no-c-format
+msgid "The coordinator then conducts the normal two-phase commit protocol."
+msgstr ""
+"Luego el coordinador conduce el protocolo normal para guardar los cambios en "
+"dos fases. "
+
+#. Tag: para
+#: Transactions_Overview.xml:184
+#, no-c-format
+msgid ""
+"Once the transaction has terminated, all registered Synchronizations are "
+"informed. However, this is a courtesy invocation because any failures at "
+"this stage are ignored: the transaction has terminated so there’s nothing to "
+"affect."
+msgstr ""
+"Una vez que la transacción ha terminado, se le informa a todas las "
+"sincronizaciones registradas. Sin embargo, esta es una invocación de "
+"cortesia ya que cualquier falla en esta etapa se ignora: la transacción ha "
+"terminado así que no hay nada afectado. "
+
+#. Tag: para
+#: Transactions_Overview.xml:189
+#, no-c-format
+msgid ""
+"Unlike the two-phase commit protocol, the synchronization protocol does not "
+"have the same failure requirements. For example, Synchronization "
+"participants don’t need to make sure they can recover in the event of "
+"failures; this is because any failure before the two-phase commit protocol "
+"completes means the transaction will roll back, and failures after it has "
+"completed can’t affect the data the Synchronization participants were "
+"managing."
+msgstr ""
+"De manera contraria que el protocolo para guardar los cambios en dos fases, "
+"el protocolo de sincronización no tiene los mismos requerimientos de falla. "
+"Por ejemplo, los participantes sincronización no necesitan asegurarse de que "
+"pueden recuperar en el caso de fallos; esto se debe a que cualquier fallo "
+"que se produzca antes de que el protocolo para guardar cambios en dos fases "
+"se haya completado significa que la transacción se deshará y las fallas "
+"después de que se ha completado no pueden afectar los datos que los "
+"participantes sincronización estaban administrando. "
+
+#. Tag: title
+#: Transactions_Overview.xml:193
+#, no-c-format
+msgid "Optimizations to the protocol"
+msgstr "Optimizaciones del protocolo"
+
+#. Tag: para
+#: Transactions_Overview.xml:194
+#, no-c-format
+msgid ""
+"There are several variants to the standard two-phase commit protocol that "
+"are worth knowing about because they can have an impact on performance and "
+"failure recovery. We shall briefly describe those that are the most common "
+"variants on the protocol:"
+msgstr ""
+"Hay varias variantes del protocolo estándar para guardar los cambios en dos "
+"fases que vale la pena conocer ya que pueden llegar a tener un impacto en el "
+"rendimiento y en la recuperación de fallas. Vamos a describir brevemente las "
+"variantes más comunes en el protocolo: "
+
+#. Tag: para
+#: Transactions_Overview.xml:200
+#, no-c-format
+msgid ""
+"Presumed abort: if a transaction is going to roll back then it may simply "
+"record this information locally and tell all enlisted participants. Failure "
+"to contact a participant has no affect on the transaction outcome; the "
+"transaction is effectively informing participants as a courtesy. Once all "
+"participants have been contacted the information about the transaction can "
+"be removed. If a subsequent request for the status of the transaction occurs "
+"there will be no information available and the requestor can assume that the "
+"transaction has aborted (rolled back). This optimization has the benefit "
+"that no information about participants need be made persistent until the "
+"transaction has decided to commit (i.e., progressed to the end of the "
+"prepare phase), since any failure prior to this point will be assumed to be "
+"an abort of the transaction."
+msgstr ""
+"Se supone aborto: si una transacción va a deshacer los cambios entonces "
+"puede que simplemente registre esta información de manera local y le diga a "
+"todos los participantes listados. Si no contacta un participante, esto no "
+"tiene efecto en el resultado de la transacción, la transacción sólo informa "
+"a los participantes como un gesto de cortesía. Una vez que todos los "
+"participantes hayan sido contactados entonces se puede borrar la información "
+"sobre la transacción. Si posteriormente tiene lugar una petición del estatus "
+"de la transacción, no habrá información disponible y el que realiza la "
+"petición puede asumir que la transacción ha abortado (se ha deschecho). Esta "
+"optimización tiene el beneficio que no es necesario hacer persistente la "
+"información sobre los participantes hasta que la transacción ha decidido "
+"guardar los cambios (por ejemplo, ha llegado hasta el final de la fase "
+"prepare) ya que se asumirá que cualquier falla previa a este punto es un "
+"aborto de la transacción. "
+
+#. Tag: para
+#: Transactions_Overview.xml:205
+#, no-c-format
+msgid ""
+"One-phase: if there is only a single participant involved in the "
+"transaction, the coordinator need not drive it through the prepare phase. "
+"Thus, the participant will simply be told to commit and the coordinator need "
+"not record information about the decision since the outcome of the "
+"transaction is solely down to the participant."
+msgstr ""
+"Una-fase: si solo hay un participante involucrado en la transacción, no es "
+"necesario que el coordinador lo dirija por la fase prepare. Por lo tanto, "
+"simplemente se le dirá al participante que guarde los cambios y no es "
+"necesario que el coordinador registre ninguna información sobre la decisión "
+"ya que el resultado de la transacción es solo para el participante. "
+
+#. Tag: para
+#: Transactions_Overview.xml:210
+#, no-c-format
+msgid ""
+"Read-only: when a participant is asked to prepare, it can indicate to the "
+"coordinator that no information or data that it controls has been modified "
+"during the transaction. Such a participant does not need to be informed "
+"about the outcome of the transaction since the fate of the participant has "
+"no affect on the transaction. As such, a read-only participant can be "
+"omitted from the second phase of the commit protocol."
+msgstr ""
+"Sólo-lectura: cuando se le pide a un participante que se prepare, puede "
+"indicarle al coordinador que ninguna de la información o datos que controla "
+"han sido modificados durante la transacción. No es necesario informar dicho "
+"participante sobre el resultado de la transacción ya que el destino del "
+"participante no tiene ningun efecto en la transacción. Como tal, se puede "
+"omitir un participante de sólo-lectura de la segunda fase del protocolo para "
+"guardar los cambios. "
+
+#. Tag: title
+#: Transactions_Overview.xml:216
+#, no-c-format
+msgid "Non-atomic transactions and heuristic outcomes"
+msgstr "Transacciones no-atómicas y resultados heurísticos"
+
+#. Tag: para
+#: Transactions_Overview.xml:217
+#, no-c-format
+msgid ""
+"In order to guarantee atomicity, the two-phase commit protocol is "
+"necessarily blocking. What this means is that as a result of failures, "
+"participants may remain blocked for an indefinite period of time even if "
+"failure recovery mechanisms exist. Some applications and participants simply "
+"cannot tolerate this blocking."
+msgstr ""
+"Con el fin de garantizar atomicidad, el protocolo de dos fases implementa el "
+"bloqueo. Es decir que en caso de fallos, puede que los participantes sean "
+"bloqueados durante un periodo indefinido de tiempo incluso si existen "
+"mecanismos de recuperación de fallos. Algunas aplicaciones y participantes "
+"simplemente no pueden tolerar este bloqueo. "
+
+#. Tag: para
+#: Transactions_Overview.xml:221
+#, no-c-format
+msgid ""
+"To break this blocking nature, participants that have got past the prepare "
+"phase are allowed to make autonomous decisions as to whether they commit or "
+"rollback: such a participant must record this decision in case it is "
+"eventually contacted to complete the original transaction. If the "
+"coordinator eventually informs the participant of the transaction outcome "
+"and it is the same as the choice the participant made, then there’s no "
+"problem. However, if it is contrary, then a non-atomic outcome has obviously "
+"happened: a heuristic outcome."
+msgstr ""
+"Para romper con esta naturaleza de bloqueo, los participantes que hayan "
+"pasado por la fase prepare pueden decidir autónomamente si deben guardar los "
+"cambios o deshacerlos: dicho participante debe registrar esta decisión en "
+"caso de que eventualmente se le contacte para completar la transacción "
+"original. Si el coordinador eventualmente le informa al participante sobre "
+"el resultado de la transacción y es el mismo que el particpante escogió "
+"entonces ha tenido lugar un resultado no-atómico: un resultado heurístico. "
+
+#. Tag: para
+#: Transactions_Overview.xml:224
+#, no-c-format
+msgid ""
+"How this heuristic outcome is reported to the application and resolved is "
+"usually the domain of complex, manually driven system administration tools, "
+"since in order to attempt an automatic resolution requires semantic "
+"information about the nature of participants involved in the transactions."
+msgstr ""
+"La manera en que este resultado heurístico es reportado a la aplicación y es "
+"resuelto, usualmente es el dominio de complejas herramientas de "
+"administración del sistema dirigidas manualmente ya que con el fin de "
+"intentar una resolución automática se requiere información semántica sobre "
+"la naturaleza de los participantes involucrados en las transacciones. "
+
+#. Tag: para
+#: Transactions_Overview.xml:227
+#, no-c-format
+msgid ""
+"Precisely when a participant makes a heuristic decision is obviously "
+"implementation dependant. Likewise, the choice the participant makes (to "
+"commit or to roll back) will depend upon the implementation and possibly the "
+"application/environment in which it finds itself. The possible heuristic "
+"outcomes are:"
+msgstr ""
+"Precisamente cuando un participante toma un decisión heurística obviamente "
+"es dependiente de la implementación. De la misma manera, la decisión que el "
+"participante toma (para guardar los cambios o para deshacerlos) dependerá de "
+"la implementación y posiblemente de la aplicación/entorno en el que se "
+"encuentre. Los resultados heurísticos posibles son:"
+
+#. Tag: para
+#: Transactions_Overview.xml:232
+#, no-c-format
+msgid ""
+"Heuristic rollback: the commit operation failed because some or all of the "
+"participants unilaterally rolled back the transaction."
+msgstr ""
+"Deshacer cambios heurísticamente: la operación para guardar los cambios "
+"falló porque algunos o todos los participantes deshicieron la transacción "
+"unilateralmente. "
+
+#. Tag: para
+#: Transactions_Overview.xml:237
+#, no-c-format
+msgid ""
+"Heuristic commit: an attempted rollback operation failed because all of the "
+"participants unilaterally committed. This may happen if, for example, the "
+"coordinator was able to successfully prepare the transaction but then "
+"decided to roll it back (for example, it could not update its log) but in "
+"the meanwhile the participants decided to commit."
+msgstr ""
+"Guardar los cambios heurísticamente: una operación para deshacer los cambios "
+"falló ya que todos los participantes guardaron los cambios de manera "
+"unilateral. Esto puede pasar, si por ejemplo, el coordinador pudo preparar "
+"exitosamente la transacción pero luego decidió deshacerla (por ejemplo, no "
+"pudo actualizar sus registros) pero mientras tanto los participantes "
+"decidieron guardar los cambios. "
+
+#. Tag: para
+#: Transactions_Overview.xml:242
+#, no-c-format
+msgid ""
+"Heuristic mixed: some updates (participants) were committed while others "
+"were rolled back."
+msgstr ""
+"Mezcla heurística: se guardaron los cambios para algunas actualizaciones "
+"(participantes) mientras que otras se deshicieron."
+
+#. Tag: para
+#: Transactions_Overview.xml:247
+#, no-c-format
+msgid ""
+"Heuristic hazard: the disposition of some of the updates is unknown. For "
+"those which are known, they have either all been committed or all rolled "
+"back."
+msgstr ""
+"Peligro heurístico: la disposición de algunas de las actualizaciones es "
+"conocida. Para aquellos que se conocen, se han guardado los cambios para "
+"todos o se deshicieron los cambios para todos. "
+
+#. Tag: para
+#: Transactions_Overview.xml:252
+#, no-c-format
+msgid ""
+"Heuristic decisions should be used with care and only in exceptional "
+"circumstances since there is the possibility that the decision will differ "
+"from that determined by the transaction service and will thus lead to a loss "
+"of integrity in the system. Having to perform resolution of heuristics is "
+"something you should try to avoid, either by working with services/"
+"participants that don’t cause heuristics, or by using a transaction service "
+"that provides assistance in the resolution process."
+msgstr ""
+"Las decisiones heurísticas se deben utilizar con cuidado y sólo en "
+"circumstancias excepcionales ya que existe la posibilidad de que la decisión "
+"sea diferente de la determinada por el servicio de transacciones y por lo "
+"tanto conllevará a una pérdida de integridad en el sistema. Debe evitar el "
+"tener que realizar una resolución heurística ya sea trabajando con servicios/"
+"participantes que no causen heurística o utilizando un servicio de "
+"transacciones que proporcione asistencia en el proceso de resolución. "
+
+#. Tag: title
+#: Transactions_Overview.xml:256
+#, no-c-format
+msgid "A New Transaction Protocol"
+msgstr "Un nuevo protocolo de transacciones"
+
+#. Tag: para
+#: Transactions_Overview.xml:257
+#, no-c-format
+msgid ""
+"Many component technologies offer mechanisms for coordinating ACID "
+"transactions based on two-phase commit semantics (i.e., CORBA/OTS, JTS/JTA, "
+"MTS/MSDTC). ACID transactions are not suitable for all Web services "
+"transactions since:"
+msgstr ""
+"Muchas tecnologías de componentes ofrecen mecanismos para coordinar "
+"transacciones ACID con base en la semántica para guardar los cambios en dos "
+"fases (por ejemplo, CORBA/OTS, JTS/JTA, MTS/MSDTC). Las transacciones ACID "
+"no son apropiadas para todas las transacciones de servicios web puesto que:"
+
+#. Tag: para
+#: Transactions_Overview.xml:263
+#, no-c-format
+msgid ""
+"Classic ACID transactions are predicated on the idea that an organization "
+"that develops and deploys applications does so using their own "
+"infrastructure, typically an Intranet. Ownership meant transactions operated "
+"in a trusted and predictable manner. To assure ACIDity, potentially long-"
+"lived locks could be kept on underlying data structures during two-phase "
+"commit. Resources could be used for any period of time and released when the "
+"transaction was complete. In the Web services arena, these assumptions are "
+"no longer valid. One obvious reason is that the owners of data exposed "
+"through a Web service will refuse to allow their data to be locked for "
+"extended periods since to allow such locks invites denial-of-service."
+msgstr ""
+"Las transacciones ACID clásicas son predicadas con base en la idea que una "
+"organización que desarrolla y despliega aplicaciones lo hace utilizando su "
+"propia infraestructura, usualmente una red interna. Ser el propietario "
+"implicaba que las transacciones operaban de una manera confiable y "
+"predecible. Para asegurar ACIDez, los bloqueos potencialmente largos podían "
+"permanecer en las estructuras de datos subyacentes cuando se guardan los "
+"cambios en dos estapas. Los recursos se pueden utilizar por cualquier "
+"periodo de tiempo y se liberan cuando la transacción se completa. En el "
+"campo de los servicios web, estos supuestos ya no son válidos. Una razón "
+"obvia es que los propietarios de datos expuestos por medio de un servicio "
+"web se negarán a permitir que sus datos sean bloqueados por periodos "
+"extendidos ya que el permitir dichos bloqueos invita a la negación del "
+"servicio. "
+
+#. Tag: para
+#: Transactions_Overview.xml:268
+#, no-c-format
+msgid ""
+"All application infrastructures are generally owned by a single party, "
+"systems using classical ACID transactions normally assume that participants "
+"in a transaction will obey the will of the transaction manager and only "
+"infrequently decide to make unilateral decisions which will hamper other "
+"participants in a transaction. On the contrary, Web services participating "
+"in a transaction can effectively decide to resign from the transaction at "
+"any time, and the consumer of the service generally has little in the way of "
+"quality of service guarantees to prevent this."
+msgstr ""
+"Todas las infraestructuras de aplicaciones son generalmente propiedad de una "
+"sola parte, los sistemas utilizando transacciones ACID clásicas normalmente "
+"asumen que los participantes en una transacción obedecerán al administrador "
+"de transacciones y solo muy rara vez decidirá tomar deciciones unilaterales, "
+"las cuales obstaculizarán a otros participantes en una transacción. Por el "
+"contrario, los servicios web participantes en una transacción pueden decidir "
+"de manera efectiva el renunciar de la transacción en cualquier momento y el "
+"consumidor del servicio generalmente tiene pocas garantías del servicio para "
+"prevenir esto. "
+
+#. Tag: title
+#: Transactions_Overview.xml:274
+#, no-c-format
+msgid "Adressing the Problems of Transactioning in Loosely Coupled Systems"
+msgstr ""
+"Tratar los problemas de transaccionamiento en sistemas acoplados débilmente"
+
+#. Tag: para
+#: Transactions_Overview.xml:275
+#, no-c-format
+msgid ""
+"Though extended transaction models which relax the ACID properties have been "
+"proposed over the years, to implement these concepts for the Web services "
+"architecture WS-T provides a new transaction protocol. XTS is designed to "
+"accommodate four underlying requirements inherent in any loosely coupled "
+"architecture like Web services:"
+msgstr ""
+"Aunque se ha propuesto por años los modelos de transacciones extendidas que "
+"relajan las propiedades ACID, el implementar estos conceptos para la "
+"arquitectura de servicios web, WS-T brinda un nuevo protocolo de "
+"transacción. XTS está diseñado para acomodar cuatro requerimientos "
+"subyacentes inherentes en cualquier arquitectura con acomplamiento débil "
+"como los servicios web: "
+
+#. Tag: para
+#: Transactions_Overview.xml:281
+#, no-c-format
+msgid ""
+"Ability to handle multiple successful outcomes to a transaction, with the "
+"ability to involve operations whose effects may not be isolated or durable;"
+msgstr ""
+"Habilidad para manejar múltiples resultados exitosos en una transacción, con "
+"la capacidad de involucrar operaciones cuyos efectos puede que no sean "
+"aislados o permanentes; "
+
+#. Tag: para
+#: Transactions_Overview.xml:286
+#, no-c-format
+msgid ""
+"Coordination of autonomous parties whose relationships are governed by "
+"contracts rather than the dictates of a central design authority;"
+msgstr ""
+"Coordinación de partes autónomas cuyas relaciones están governadas por "
+"contratos en vez de las órdenes de una autoridad de diseño central; "
+
+#. Tag: para
+#: Transactions_Overview.xml:291
+#, no-c-format
+msgid ""
+"Discontinuous service, where parties are anticipated to suffer outages "
+"during their lifetime, and coordinated work must be able to survive such "
+"outages;"
+msgstr ""
+"Servicio interrumpido, en donde se anticipa que las partes sufrirán apagones "
+"durante su periodo de vida y por lo tanto el trabajo coordinado debe poder "
+"sobrevivir tales apagones; "
+
+#. Tag: para
+#: Transactions_Overview.xml:296
+#, no-c-format
+msgid ""
+"Interoperation using XML over multiple communication protocols – XTS chooses "
+"to use SOAP encoding carried over HTTP for the first release and other SOAP-"
+"friendly transports for future releases."
+msgstr ""
+"Interoperación utilizando XML sobre múltiples protocolos de comunicación - "
+"XTS decide utilizar codificación SOAP sobre HTTP para el primer lanzamiento "
+"y otros transportes compatibles con SOAP para lanzamientos futuros. "

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/es-ES/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,1067 @@
+# translation of Stand-alone_Coordinator.po to
+# Language es-ES translations for  package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2009-01-09 16:31+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:6
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Overview"
+msgstr "Sinopsis de WS-C, WS-Atomic Transaction y WS-Business Activity "
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introducción"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:9
+#, no-c-format
+msgid ""
+"This section provides fundamental concepts associated with WS-C, WS-Atomic "
+"Transaction and WS-Business Activity. All of these concepts are defined in "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. WS-"
+"C, WS-Atomic Transaction and WS-Business Activity principles are discussed "
+"throughout this guide."
+msgstr ""
+"Esta sección proporciona los conceptos fundamentales asociados con WS-C, WS-"
+"Atomic Transaction y WS-Business Activity. Todos estos conceptos están "
+"definidos en las especificaciones WS-C, WS-Atomic Transaction y WS-Business "
+"Activity. En este manual discutiremos los principios de WS-C, WS-Atomic "
+"Transaction y WS-Business Activity. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:13
+#, no-c-format
+msgid ""
+"If you are well versed in the WS-C, WS-Atomic Transaction and WS-Business "
+"Activity specifications then you may want to just skim through this part of "
+"the manual."
+msgstr ""
+"Si conoce bien las especificaciones de WS-C, WS-Atomic Transaction y WS-"
+"Business Activity entonces probablemente solo quiera hojear esta parte del "
+"manual. "
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr "WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:21
+#, no-c-format
+msgid ""
+"In general terms, coordination is the act of one entity (known as the "
+"coordinator) disseminating information to a number of participants for some "
+"domain-specific reason. This reason could be in order to reach consensus on "
+"a decision like in a distributed transaction protocol, or simply to "
+"guarantee that all participants obtain a specific message, as occurs in a "
+"reliable multicast environment. When parties are being coordinated, "
+"information known as the coordination context is propagated to tie together "
+"operations which are logically part of the same coordinated work or "
+"activity. This context information may flow with normal application "
+"messages, or may be an explicit part of a message exchange and is specific "
+"to the type of coordination being performed."
+msgstr ""
+"En términos generales, la coordinación es el acto de una entidad (conocida "
+"como el coordinador) para repartir información a un número de participantes "
+"por alguna razón especifica del dominio. Esta razón podría ser para alcanzar "
+"un consenso en una decisión como en un protocolo de transacción distribuida "
+"o simplemente para garantizar que todos los participantes obtienen un "
+"mensaje especifico tal como sucede en un entorno multicast confiable. Cuando "
+"se están coordinando las partes, la información conocida como el contexto de "
+"coordinación se propaga para unir las operaciones que son lógicamente parte "
+"del mismo trabajo o actividad coordinados. Esta información de contexto "
+"puede fluir con mensajes de aplicación normales o puede ser una parte "
+"explícita del intercambio de mensajes y es especifico para el tipo de "
+"coordinación que se está realizando. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:24
+#, no-c-format
+msgid ""
+"The fundamental idea underpinning WS-Coordination is that there is a generic "
+"need for a coordination infrastructure in a Web services environment. The WS-"
+"Coordination specification defines a framework that allows different "
+"coordination protocols to be plugged-in to coordinate work between clients, "
+"services and participants, as shown in Figure 4."
+msgstr ""
+"La idea fundamental de WS-Coordination es que hay una necesidad genérica de "
+"una infraestructura de coordinación en un entorno de servicios web. La "
+"especificación WS-Coordination define un marco de trabajo que permite "
+"enchufar diferentes protocolos de coordinación para coordinar el trabajo "
+"entre clientes, servicios y participantes como se puede ver en la figura 4. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:27
+#, no-c-format
+msgid ""
+"At this level, an activity is minimally specified and is simply created, "
+"made to run, and then completed."
+msgstr ""
+"En este nivel, una actividad se especifica mínimamente y se crea de manera "
+"simple, se ejecuta y luego se completa. "
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:34
+#, no-c-format
+msgid "WS-C architecture"
+msgstr "Arquitectura WS-C"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:36
+#, no-c-format
+msgid ""
+"Whatever coordination protocol is used, and in whatever domain it is "
+"deployed, the same generic requirements are present:"
+msgstr ""
+"Los mismos requerimientos genéricos están presentesn en cualquier protocolo "
+"de coordinación que se utilice y en cualquier dominio en que se despliegue: "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:41
+#, no-c-format
+msgid ""
+"Instantiation (or activation) of a new coordinator for the specific "
+"coordination protocol, for a particular application instance;"
+msgstr ""
+"Instanciación (o activación) de un nuevo coordinador para el protocolo de "
+"coordinación específico, para una instancia de aplicación particular; "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:46
+#, no-c-format
+msgid ""
+"Registration of participants with the coordinator, such that they will "
+"receive that coordinator’s protocol messages during (some part of) the "
+"application’s lifetime;"
+msgstr ""
+"Registro de participantes con el coordinador de tal manera que recibirán los "
+"mensajes de protocolo del coordinador durante (alguna parte de) el tiempo de "
+"vida de la aplicación; "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:51
+#, no-c-format
+msgid ""
+"Propagation of contextual information between Web services that comprise the "
+"application;"
+msgstr ""
+"Propagación de información contextual entre servicios web que comprometen la "
+"aplicación; "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:56
+#, no-c-format
+msgid "An entity to drive the coordination protocol through to completion."
+msgstr "Una entidad para dirigir el protocolo de coordinación hasta el final."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:61
+#, no-c-format
+msgid ""
+"The first three of these points are directly the concern of WS-Coordination "
+"while the fourth is the responsibility of a third-party entity, usually the "
+"client application that controls the application as a whole. These four WS-"
+"Coordination roles and their interrelationships are shown in Figure 5."
+msgstr ""
+"El primeros tres puntos son directamente asuntos del WS-Coordination "
+"mientras que el cuarto punto es responsabilidad de una entidad de tercera "
+"parte, usualmente la aplicación de cliente que controla las aplicación como "
+"un todo. Estos cuatro roles WS-Coordination y sus inter-relaciones se pueden "
+"ver en la figura 5. "
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr "Infraestructura WS-C "
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:71
+#, no-c-format
+msgid "Activation"
+msgstr "Activación"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:72
+#, no-c-format
+msgid ""
+"The WS-Coordination framework exposes an Activation Service which supports "
+"the creation of coordinators for specific protocols and their associated "
+"contexts. The process of invoking an activation service is done "
+"asynchronously, and so the specification defines both the interface of the "
+"activation service itself, and that of the invoking service, so that the "
+"activation service can call back to deliver the results of the activation – "
+"namely a context that identifies the protocol type and coordinator location. "
+"These interfaces are presented in Figure 6, where the activation service has "
+"a one-way operation that expects to receive a "
+"<code>CreateCoordinationContext</code> message and correspondingly the "
+"service that sent the <code>CreateCoordinationContext</code> message expects "
+"to be called back with a <code>CreateCoordinationContextResponse</code> "
+"message, or informed of a problem via an <code>Error</code> message."
+msgstr ""
+"El marco de trabajo WS-Coordination expone un servicio de activación, el "
+"cual soporta la creación de coordinadores para protocolos específicos y sus "
+"contextos asociados. El proceso de invocar un servicio de activación se "
+"realiza de manera asincrónica y así la especificación define la interfaz del "
+"servicio de activación en sí y la del servicio de invocación de manera que "
+"el servicio de activación pueda devolver la llamada para entregar los "
+"resultados de la activación - a saber un contexto que identifica el tipo de "
+"protocolo y la ubicación del coordinador. Presentamos estas interfaces en la "
+"figura 6, en donde el servicio de activación tiene una operación de una sola "
+"vía que espera recibir un mensaje <code>CreateCoordinationContext</code> y "
+"de manera correspondiente el servicio que envió el mensaje "
+"<code>CreateCoordinationContext</code> espera que se le devuelva la llamada "
+"con un mensaje <code>CreateCoordinationContextResponse</code> o que se le "
+"informe de un problema a través de un mensaje <code>Error</code>."
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:76
+#, no-c-format
+msgid ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+msgstr ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:78
+#, no-c-format
+msgid "Registration"
+msgstr "Registro"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:79
+#, no-c-format
+msgid ""
+"Once a coordinator has been instantiated and a corresponding context created "
+"by the activation service, a Registration Service is created and exposed. "
+"This service allows participants to register to receive protocol messages "
+"associated with a particular coordinator. Like the activation service, the "
+"registration service assumes asynchronous communication and so specifies "
+"WSDL for both registration service and registration requester, as shown "
+"below."
+msgstr ""
+"Una vez un coordinador ha sido instanciado y el contexto correspondiente ha "
+"sido creado por el servicio de activación entonces se crea y se expone un "
+"servicio de registro. Este servicio le permite a los participantes "
+"registrarse para recibir mensajes de protocolo asociados con un coordinador "
+"en particular. Tal como el servicio de activación, el servicio de registro "
+"asume comunicación asincrónica y por lo tanto especifica WSDL para el "
+"servicio de registro y el para el que solicita el registro como se puede ver "
+"a continuación. "
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:83
+#, no-c-format
+msgid ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+msgstr ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:84
+#, no-c-format
+msgid ""
+"When a participant is registered with a coordinator through the registration "
+"service, it receives messages that the coordinator sends (for example, "
+"“prepare to complete” and “complete” messages if a two-phase protocol is "
+"used); where the coordinator’s protocol supports it, participants can also "
+"send messages back to the coordinator."
+msgstr ""
+"Cuando un participante es registrado con un coordinador por medio del "
+"servicio de registro, recibe mensajes que el coordinador envía (por ejemplo, "
+"mensajes como “prepare to complete” y “complete”si se utiliza un protocolo "
+"de dos fases); en donde el protocolo del coordinador lo soporta, los "
+"participantes también pueden enviar mensajes de regreso al coordinador. "
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:88
+#, no-c-format
+msgid "Completion"
+msgstr "Finalización"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:89
+#, no-c-format
+msgid ""
+"The role of terminator is generally played by the client application, which "
+"at an appropriate point will ask the coordinator to perform its particular "
+"coordination function with any registered participants – to drive the "
+"protocol through to its completion. On completion, the client application "
+"may be informed of an outcome for the activity which may vary from simple "
+"succeeded/failed notification through to complex structured data detailing "
+"the activity’s status."
+msgstr ""
+"Generalmente la aplicación cliente tiene el papel de terminator, el cual en "
+"el momento apropiado le pedirá al coordinador que realice su función de "
+"coordinación en particular con cualquiera de los participantes registrados - "
+"para dirigir el protocolo hasta el final. Al terminar, puede que se le "
+"informe a la aplicación cliente del resultado de la actividad la cual puede "
+"variar desde una notificación simple de éxito/fallo hasta datos "
+"estructurados de manera compleja detallando el estado de la actividad. "
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:96
+#, fuzzy, no-c-format
+msgid "WS-Transaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:97
+#, no-c-format
+msgid ""
+"In the past, making traditional transaction systems talk to one another was "
+"a holy grail that was rarely achieved. With the advent of Web services, "
+"there is an opportunity to leverage an unparalleled interoperability "
+"technology to splice together existing transaction processing systems that "
+"already form the backbone of enterprise level applications."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:101
+#, fuzzy, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr "WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:102
+#, no-c-format
+msgid ""
+"An important aspect of WS-Transaction that differentiates it from "
+"traditional transaction protocols is that a synchronous request/response "
+"model is not assumed. This model derives from the fact that WS-Transaction "
+"is, as shown in the figure below, layered upon the WS-Coordination protocol "
+"whose own communication patterns are asynchronous by default."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:110
+#, fuzzy, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr "Sinopsis de WS-C, WS-Atomic Transaction y WS-Business Activity "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:112
+#, no-c-format
+msgid ""
+"Web Services Coordination provides a generic framework for specific "
+"coordination protocols, like WS-Transaction, to be plugged in. Recall that "
+"WS-Coordination provides only context management – it allows contexts to be "
+"created and activities to be registered with those contexts. WS-Transaction "
+"leverages the context management framework provided by WS-Coordination in "
+"two ways. Firstly it extends the WS-Coordination context to create a "
+"transaction context. Secondly, it augments the activation and registration "
+"services with a number of additional services (Completion, "
+"CompletionWithAck, PhaseZero, 2PC, OutcomeNotification, BusinessAgreement, "
+"and BusinessAgreementWithComplete) and two protocol message sets (one for "
+"each of the transaction models supported in WS-Transaction) to build a fully-"
+"fledged transaction coordinator on top the WS-Coordination protocol "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:116
+#, fuzzy, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr "Arquitectura WS-C"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:117
+#, no-c-format
+msgid ""
+"WS-Transaction supports the notion of the service and participant as "
+"distinct roles, making the distinction between a transaction-aware service "
+"and the participants that act on behalf of the service during a transaction: "
+"transactional services deal with business-level protocols, while the "
+"participants handle the underlying WS-Transaction protocols, as shown above."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:125
+#, fuzzy, no-c-format
+msgid "WS-Transaction Global View"
+msgstr "Sinopsis de transacciones"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:127
+#, no-c-format
+msgid ""
+"A transaction-aware service encapsulates the business logic or work that is "
+"required to be conducted within the scope of a transaction. This work cannot "
+"be confirmed by the application unless the transaction also commits and so "
+"control is ultimately removed from the application and placed into the "
+"transaction’s domain."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:130
+#, no-c-format
+msgid ""
+"The participant is the entity that, under the dictates of the transaction "
+"coordinator, controls the outcome of the work performed by the transaction-"
+"aware Web service. In the figure above each service is shown with one "
+"associated participant that manages the transaction protocol messages on "
+"behalf of its service, while in the figure below, there is a close-up view "
+"of a single service, and a client application with their associated "
+"participants."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:137
+#, no-c-format
+msgid "Transactional Service and Participant"
+msgstr "Servicio transaccional y participante"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:139
+#, no-c-format
+msgid ""
+"The transaction-aware Web service and its participant both serve a shared "
+"transactional resource, and there is a control relationship between them "
+"through some API - which on the Java platform is JAXTX. In the example shown "
+"in the figure above, it is assumed that the database is accessed through a "
+"transactional JDBC database driver, where SQL statements are sent to the "
+"database for processing via that driver, but where those statements will be "
+"tentative and only commit if the transaction does. In order to do this, the "
+"driver/database will associate a participant with the transaction which will "
+"inform the database of the transaction outcome. Since all transactional "
+"invocations on the Web service carry a transaction context, the participant "
+"working with the database is able to identify the work that the "
+"transactional service did within the scope of a specific transaction and "
+"either commit or rollback the work."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:142
+#, no-c-format
+msgid ""
+"At the client end, things are less complex. Through its API, the client "
+"application registers a participant with the transaction through which it "
+"controls transaction termination."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:146
+#, fuzzy, no-c-format
+msgid "WS-Transaction Models"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:147
+#, no-c-format
+msgid ""
+"Given that traditional transaction models are not appropriate for Web "
+"services, the following question must be posed, “what type of model or "
+"protocol is appropriate?” The answer to that question is that that no one "
+"specific protocol is likely to be sufficient, given the wide range of "
+"situations that Web service transactions are likely to be deployed within. "
+"Hence the WS-Transaction specification proposes two distinct models, where "
+"each supports the semantics of a particular kind of B2B interaction. The "
+"following sections shall discuss these two WS-Transaction models."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:152
+#, no-c-format
+msgid ""
+"As with WS-Coordination, the two WS-Transaction models are extensible "
+"allowing implementations to tailor the protocols as they see fit (for "
+"example, to suit their deployment environments)."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:157
+#, no-c-format
+msgid "Atomic Transactions (AT)"
+msgstr "Transacciones atómicas "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:158
+#, no-c-format
+msgid ""
+"An atomic transaction or AT is similar to traditional ACID transactions and "
+"intended to support short-duration interactions where ACID semantics are "
+"appropriate. Within the scope of an AT, services typically enroll "
+"transaction-aware resources, such as databases and message queues, "
+"indirectly as participants under the control of the transaction. When the "
+"transaction terminates, the outcome decision of the AT is then propagated to "
+"each enlisted resource via the participant, and the appropriate commit or "
+"rollback actions are taken by each."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:162
+#, no-c-format
+msgid ""
+"This protocol is very similar to those employed by traditional transaction "
+"systems that already form the backbone of an enterprise. It is assumed that "
+"all services (and associated participants) provide ACID semantics and that "
+"any use of atomic transactions occurs in environments and situations where "
+"this is appropriate: in a trusted domain, over short durations."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:165
+#, no-c-format
+msgid ""
+"To begin an atomic transaction, the client application firstly locates a WS-"
+"Coordination coordinator Web service that supports WS-Transaction. Once "
+"located, the client sends a WS-Coordination CreateCoordinationContext "
+"message to the activation service specifying http://schemas.xmlsoap.org/"
+"ws/2004/10/wsat as its coordination type and will get back an appropriate WS-"
+"Transaction context from the activation service. The response to the "
+"CreateCoordinationContext message, the transaction context, has its "
+"CoordinationType element set to the WS-Atomic Transaction namespace, http://"
+"schemas.xmlsoap.org/ws/2004/10/wsat, and also contains a reference to the "
+"atomic transaction coordinator endpoint (the WS-Coordination registration "
+"service) where participants can be enlisted."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:168
+#, no-c-format
+msgid ""
+"After obtaining a transaction context from the coordinator, the client "
+"application then proceeds to interact with Web services to accomplish its "
+"business-level work. With each invocation on a business Web service, the "
+"client inserts the transaction context into a SOAP header block, such that "
+"each invocation is implicitly scoped by the transaction – the toolkits that "
+"support WS-Atomic Transaction-aware Web services provide facilities to "
+"correlate contexts found in SOAP header blocks with back-end operations."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:171
+#, no-c-format
+msgid ""
+"Once all the necessary application level work has been completed, the client "
+"can terminate the transaction, with the intent of making any changes to the "
+"service state permanent. To do this, the client application first registers "
+"its own participant for the Completion protocol. Once registered, the "
+"participant can instruct the coordinator either to try to commit or rollback "
+"the transaction. When the commit or rollback operation has completed, a "
+"status is returned to the participant to indicate the outcome of the "
+"transaction."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:174
+#, no-c-format
+msgid ""
+"While the completion protocol is straightforward, they hide the fact that in "
+"order to resolve to an outcome that several other protocols need to be "
+"executed."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:177
+#, no-c-format
+msgid ""
+"The first of these protocols is the optional Volatile2PC. The Volatile2PC "
+"protocol is the WS-Atomic Transaction equivalent of the synchronization "
+"protocol we discussed earlier. It is typically executed where a Web service "
+"needs to flush volatile (cached) state, which may be being used to improve "
+"performance of an application, to a database prior to the transaction "
+"committing. Once flushed, the data will then be controlled by a two-phase "
+"aware participant."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:180
+#, no-c-format
+msgid ""
+"All Volatile2PC participants are told that the transaction is about to "
+"complete (via the prepare message) and they can respond with either the "
+"prepared, aborted or readonly message; any failures at this stage will cause "
+"the transaction to rollback."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:183
+#, no-c-format
+msgid ""
+"After Volatile2PC prepare, the next protocol to execute in WS-Atomic "
+"Transaction is Durable2PC. The Durable2PC (an abbreviation of the term two-"
+"phase commit) protocol is at the very heart of WS-Atomic Transaction and is "
+"used to bring about the necessary consensus between participants in a "
+"transaction such that the transaction can safely be terminated."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:186
+#, no-c-format
+msgid ""
+"The two-phase commit protocol is used to ensure atomicity between "
+"participants, and is based on the classic two-phase commit with presumed "
+"abort technique. During the first phase, when the coordinator sends the "
+"prepare message, a participant must make durable any state changes that "
+"occurred during the scope of the transaction, such that these changes can "
+"either be rolled back or committed later. That is, any original state must "
+"not be lost at this point as the atomic transaction could still roll back. "
+"If the participant cannot prepare then it must inform the coordinator (via "
+"the aborted message) and the transaction will ultimately roll back. If the "
+"participant is responsible for a service that did not do any work during the "
+"course of the transaction, or at least did not do any work that modified any "
+"state, it can return the readonly message and it will be omitted from the "
+"second phase of the commit protocol. Otherwise, the prepared message is sent "
+"by the participant."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:189
+#, no-c-format
+msgid ""
+"Assuming no failures occurred during the first phase, in the second phase "
+"the coordinator sends the commit message to participants, who will make "
+"permanent the tentative work done by their associated services."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:192
+#, fuzzy, no-c-format
+msgid ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
+msgstr ""
+"Una-fase: si solo hay un participante involucrado en la transacción, no es "
+"necesario que el coordinador lo dirija por la fase prepare. Por lo tanto, "
+"simplemente se le dirá al participante que guarde los cambios y no es "
+"necesario que el coordinador registre ninguna información sobre la decisión "
+"ya que el resultado de la transacción es solo para el participante. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:195
+#, no-c-format
+msgid ""
+"The figure below<footnote> <para> Redrawn from the WS-Atomic Transaction "
+"specification. </para> </footnote> shows the state transitions of a WS-"
+"Atomic Transaction and the message exchanges between coordinator and "
+"participant; the coordinator generated messages are shown in the solid line, "
+"whereas the participant messages are shown by dashed lines."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:206
+#, fuzzy, no-c-format
+msgid "Two-Phase Commit State Transitions"
+msgstr "Guardar cambios en dos fases"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:208
+#, no-c-format
+msgid ""
+"Once the 2PC protocol has finished, the Completion protocol that originally "
+"began the termination of the transaction can complete, and inform the client "
+"application whether the transaction was committed or rolled back. "
+"Additionally, the Volatile2PC protocol may complete."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:211
+#, no-c-format
+msgid ""
+"Like the prepare phase of Volatile2PC, the final phase is optional and can "
+"be used to inform participants when the transaction has completed, typically "
+"so that they can release resources (for example, put a database connection "
+"back into the pool of connections)."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:214
+#, no-c-format
+msgid ""
+"Any registered Volatile2PC participants are invoked after the transaction "
+"has terminated and are told the state in which the transaction completed "
+"(the coordinator sends either the Committed or Aborted message). Since the "
+"transaction has terminated, any failures of participants at this stage are "
+"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
+"the transaction."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:217
+#, no-c-format
+msgid ""
+"Finally, after having gone through each of the stages in an AT, it is "
+"possible to see the intricate interweaving of individual protocols that goes "
+"to make up the AT as a whole in the following figure."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:224
+#, no-c-format
+msgid "The AT Model"
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:227
+#, fuzzy, no-c-format
+msgid "Business Activities (BA)"
+msgstr "Actividad empresarial"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:228
+#, no-c-format
+msgid ""
+"Most business-to-business applications require transactional support in "
+"order to guarantee consistent outcome and correct execution. These "
+"applications often involve long running computations, loosely coupled "
+"systems and components that do not share data, location, or administration "
+"and it is difficult to incorporate atomic transactions within such "
+"architectures. For example, an online bookshop may reserve books for an "
+"individual for a specific period of time, but if the individual does not "
+"purchase the books within that period they will be “put back onto the shelf” "
+"for others to buy. Furthermore, because it is not possible for anyone to "
+"have an infinite supply of stock, some online shops may appear to users to "
+"reserve items for them, but in fact may allow others to pre-empt that "
+"reservation (for instance, the same book may be “reserved” for multiple "
+"users concurrently); a user may subsequently find that the item is no longer "
+"available, or may have to be reordered specially for them."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:232
+#, no-c-format
+msgid ""
+"A business activity or BA is designed specifically for these kinds of long-"
+"duration interactions, where exclusively locking resources is impossible or "
+"impractical. In this model services are requested to do work, and where "
+"those services have the ability to undo any work, they inform the BA such "
+"that if the BA later decides the cancel the work (for instance if the "
+"business activity suffers a failure), it can instruct the service to execute "
+"its undo behavior. The key point for Business Activities is that how "
+"services do their work and provide compensation mechanisms is not the domain "
+"of the WS-Business Activity specification, but an implementation decision "
+"for the service provider."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:235
+#, no-c-format
+msgid ""
+"The WS- Business Activity simply defines a protocol for Web services-based "
+"applications to enable existing business processing and workflow systems to "
+"wrap their proprietary mechanisms and interoperate across implementations "
+"and business boundaries."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:238
+#, no-c-format
+msgid ""
+"A business activity may be partitioned into scopes, where a scope is a "
+"business task or unit of work using a collection of Web services. Such "
+"scopes can be nested to arbitrary degrees, forming parent and child "
+"relationships, where a parent scope has the ability to select which child "
+"tasks are to be included in the overall outcome protocol for a specific "
+"business activity, and so clearly non-atomic outcomes are possible. In a "
+"similar manner to traditional nested transactions, if a child task "
+"experiences an error, it can be caught by the parent who may be able to "
+"compensate and continue processing."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:241
+#, no-c-format
+msgid ""
+"When a child task completes it can either leave the business activity or "
+"signal to the parent that the work it has done can be compensated later. In "
+"the latter case, the compensation task may be called by the parent should it "
+"ultimately need to undo the work performed by the child."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:244
+#, no-c-format
+msgid ""
+"Unlike the WS-Atomic Transaction protocol model, where participants inform "
+"the coordinator of their state only when asked, a task within a business "
+"activity can specify its outcome to the parent directly without waiting for "
+"a request. This feature is useful when tasks fail such that the notification "
+"can be used by business activity exception handler to modify the goals and "
+"drive processing forward without having to meekly wait until the end of the "
+"transaction to admit to having failed – a well designed Business Activities "
+"should be proactive, if it is to perform well."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:247
+#, no-c-format
+msgid "Underpinning all of this are three fundamental assumptions:"
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:252
+#, no-c-format
+msgid ""
+"All state transitions are reliably recorded, including application state and "
+"coordination metadata (the record of sent and received messages);"
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:257
+#, no-c-format
+msgid ""
+"All request messages are acknowledged, so that problems are detected as "
+"early as possible. This avoids executing unnecessary tasks and can also "
+"detect a problem earlier when rectifying it is simpler and less expensive;"
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:262
+#, no-c-format
+msgid ""
+"As with atomic transactions, a response is defined as a separate operation "
+"and not as the output of the request. Message input-output implementations "
+"will typically have timeouts that are too short for some business activity "
+"responses. If the response is not received after a timeout, it is resent. "
+"This is repeated until a response is received. The request receiver discards "
+"all but one identical request received."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:267
+#, no-c-format
+msgid ""
+"As with atomic transactions, the business activity model has multiple "
+"protocols: <code>BusinessAgreementWithParticipantCompletion</code> and "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. However, unlike the "
+"AT protocol which is driven from the coordinator down to participants, this "
+"protocol is driven much more from the participants upwards."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
+#, no-c-format
+msgid ""
+"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
+"a child activity is initially created in the Active state; if it finishes "
+"the work it was created to do and no more participation is required within "
+"the scope of the BA (such as when the activity operates on immutable data), "
+"then the child can unilaterally send an exited message to the parent. "
+"However, if the child task finishes and wishes to continue in the BA then it "
+"must be able to compensate for the work it has performed. In this case it "
+"sends a completed message to the parent and waits to receive the final "
+"outcome of the BA from the parent. This outcome will either be a close "
+"message, meaning the BA has completed successfully or a compensate message "
+"indicating that the parent activity requires that the child task reverse its "
+"work."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
+#, no-c-format
+msgid ""
+"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
+"identical to the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol with the exception that the child cannot autonomously decide to end "
+"its participation in the business activity, even if it can be compensated. "
+"Rather the child task relies upon the parent to inform it when the child has "
+"received all requests for it to perform work which the parent does by "
+"sending the complete message to the child. The child then acts as it does in "
+"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:276
+#, no-c-format
+msgid ""
+"The crux of the BA model compared to the AT model is that is allows the "
+"participation of services that cannot or will not lock resources for "
+"extended periods."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:279
+#, no-c-format
+msgid ""
+"While the full ACID semantics are not maintained by a BA, consistency can "
+"still be maintained through compensation, though the task of writing correct "
+"compensating actions (and thus overall system consistency) is delegated to "
+"the developers of the services under control of the BA. Such compensations "
+"may use backward error recovery, but will typically employ forward recovery."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:283
+#, no-c-format
+msgid "Application Messages"
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:284
+#, no-c-format
+msgid ""
+"Application messages are the requests and responses that are sent between "
+"parties that constitute the work of a business process. Any such messages "
+"are considered opaque by XTS, and there is no mandatory message format, "
+"protocol binding, or encoding style so the developer is free to use any "
+"appropriate Web services protocol. In XTS, the transaction context is "
+"propagated within the headers of SOAP messages."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:289
+#, no-c-format
+msgid ""
+"XTS provides out-of-box support for service developers building WS-T-aware "
+"services on the JBoss, Weblogic and Glue platforms1. The provision of "
+"interceptors for automatic context handling at both client and service "
+"significantly simplifies the developer’s workload, allowing the developer to "
+"concentrate on writing the business logic without having to worry about the "
+"transactional infrastructure getting in the way. The interceptors simply add "
+"and remove context elements to application messages without altering the "
+"semantics of those messages. Any service which understands what to do with a "
+"WS-C context can use it, services which do not understand the context (those "
+"services that are not WS-C, WS-Atomic Transaction and WS-Business Activity-"
+"aware) may ignore the context; the important point here is that XTS manages "
+"contexts without user intervention."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:294
+#, fuzzy, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr "Sinopsis de WS-C, WS-Atomic Transaction y WS-Business Activity "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:295
+#, no-c-format
+msgid ""
+"Although the application or service developer rarely sees or is interested "
+"in the messages exchanged by the transactional infrastructure (the "
+"transaction manager and any participants), it is useful to understand what "
+"kinds of exchanges occur so that the underlying model can be fitted in to an "
+"overall architecture."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:299
+#, no-c-format
+msgid ""
+"In XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific "
+"messages are transported using SOAP messaging over HTTP. The types of "
+"messages that are propagated include instructions to perform standard "
+"transaction operations like begin, prepare."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:303
+#, no-c-format
+msgid ""
+"XTS messages do not interfere in any way, shape, or form, with the "
+"application messages, and nor is there any requirement for an application to "
+"use the same transport as the transaction-specific messages. For example, it "
+"is quite reasonable for a client application to deliver its application-"
+"specific messages using SOAP RPC over SMTP even though under the covers the "
+"XTS messages are delivered using a different mechanism."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:310
+#, no-c-format
+msgid "Summary"
+msgstr "Resumen"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:311
+#, no-c-format
+msgid ""
+"XTS provides a coordination infrastructure designed to allow transactions to "
+"run between enterprises across the Internet. That infrastructure is based on "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. It "
+"supports two kinds of transactions: atomic transactions and business "
+"activities, which can be combined in arbitrary ways to map elegantly onto "
+"the transactional requirements of the underlying problem. The use of the "
+"whole infrastructure is simple due to the fact that its functionality is "
+"exposed through a simple transactioning API. Furthermore XTS provides all of "
+"the necessary plumbing to keep application and transactional aspects of an "
+"application separate, and to ensure that the transactionality of a system "
+"does not interfere with the functional aspects of the system itself."
+msgstr ""

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Author_Group.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Author_Group.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Book_Info.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Book_Info.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,49 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide CP04"
+msgstr "Guide des programmeurs de transaction JBoss Services Web"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr ""
+"à utiliser avec la plate-forme JBoss Enterprise Application Platform 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr "Cet ouvrage concerne la programmation des transactions Services Web"
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Getting_Started.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Getting_Started.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Getting_Started.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,270 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Getting_Started.xml:6
+#, no-c-format
+msgid "Getting Started"
+msgstr "Comment démarrer"
+
+#. Tag: title
+#: Getting_Started.xml:8
+#, no-c-format
+msgid "Creating and deploying participants"
+msgstr "Créer et déployer des participants"
+
+#. Tag: para
+#: Getting_Started.xml:9
+#, no-c-format
+msgid ""
+"A participant is a software entity which is driven by the transaction "
+"manager on behalf of a Web service. The creation of participants is non-"
+"trivial since they ultimately reflect the state of a Web service’s back-end "
+"processing facilities which is a function of an enterprise’s own IT "
+"infrastructure. The most that can be said about the implementation of a "
+"participant without getting into detail about the back-end systems it "
+"represents, or the details of the underlying transaction protocol is that "
+"implementations must implement one of the following interfaces, depending "
+"upon the protocol it will participate within: <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code>, or, <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+msgstr ""
+"Un participant est une entité informatique qui est contrôlée par un "
+"gestionnaire de transactions pour le compte d'un service Web. La création de "
+"participants n'est pas triviale puisqu'au bout du compte, ils reflètent "
+"l'état des possibilités de traitement du back-end d'un service Web, qui est "
+"une fonction de l'infrastructure informatique particulière à une entreprise. "
+"Tout ce que l'on peut dire sur l'implémentation d'un participant sans entrer "
+"dans les détails à propos des systèmes back-end qu'il représente, ou les "
+"détails du protocole de transaction sous-jacent, c'est que les "
+"implémentations doivent mettre en oeuvre une des interfaces suivantes, "
+"suivant le protocole auquel il participera : <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code>, ou, <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+
+#. Tag: title
+#: Getting_Started.xml:15
+#, no-c-format
+msgid "Creating Client Applications"
+msgstr "Créer des applications client"
+
+#. Tag: para
+#: Getting_Started.xml:16
+#, no-c-format
+msgid ""
+"There are two aspects to a client application using XTS. The first is the "
+"transaction declaration aspects and the second is the business logic that "
+"the client application performs. The transaction declaration aspects are "
+"taken care of automatically with XTS’s client API. This API provides simple "
+"transaction directives like begin, commit, and rollback which the client "
+"application can use to initialize, manage, and terminate transactions. Under "
+"the covers, this API invokes (via SOAP) operations on the transaction "
+"manager."
+msgstr ""
+"Il y a deux aspects dans une application client qui utilise XTS. Le premier "
+"aspect concerne la déclaration de la transaction et le second la logique "
+"commerciale opérée par l'application client. Les aspects de déclaration de "
+"transaction sont traités automatiquement par l'API client de XTS. Cet API "
+"propose des directives de transactions simples, comme begin (commencer), "
+"commit (valider) et rollback (rejeter) que l'application du client peut "
+"utiliser pour initialiser, gérer, et terminer les transactions. Sous "
+"couvert, cet API invoque (via SOAP) les opération sur le gestionnaire de "
+"transactions."
+
+#. Tag: para
+#: Getting_Started.xml:19
+#, no-c-format
+msgid ""
+"When the client application performs invocations on business logic Web "
+"services, then XTS does not dictate an API for that purpose. However, there "
+"is a requirement that whatever API is chosen, the XTS context be inserted "
+"onto outgoing messages, and extracted and associated with the current thread "
+"for incoming messages. To make the user’s life easier, the XTS software "
+"comes complete with three sets of “filters” which can perform the task "
+"automatically. These filters are designed to work with JAX-RPC and "
+"webMethods client libraries."
+msgstr ""
+"Quand l'application client effectue des invocations sur des services Web de "
+"logique commerciale, alors XTS n'impose pas d'API dans ce but. Cependant, il "
+"est exigé que quel que soit l'API choisi, le contexte XTS devra être inséré "
+"dans les messages sortants, extraits et associés dans le thread courant pour "
+"les messages qui arrivent. Pour faciliter la vie de l'utilisateur, le "
+"logiciel XTS est proposé avec trois 'filtres' qui peuvent effectuer la tâche "
+"automatiquement. Ces filtres sont conçus pour travailler avec les "
+"bibliothèques des clients webMethods et JAX-RPC."
+
+#. Tag: para
+#: Getting_Started.xml:23
+#, no-c-format
+msgid ""
+"If the user chooses to use a different SOAP client infrastructure, then the "
+"onus to perform client-side header processing rests with them. XTS does not "
+"provide client-side infrastructure for anything other than JAX-RPC or "
+"webMethods for this release."
+msgstr ""
+"Si l'utilisateur choisit d'utiliser une infrastructure de client SOAP "
+"différente, alors il leur revient la charge d'effectuer des traitements d'en-"
+"têtes côté-client. XTS ne fournit pas d'infrastructure côté-client pour rien "
+"d'autre que JAX-RPC ou webMethods pour cette version."
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr "Gestionnaires de contexte JAX-RPC"
+
+#. Tag: para
+#: Getting_Started.xml:29
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC server-side context handler with the "
+"deployed web services, a handler chain must be included in the web services "
+"deployment descriptor. Please refer to the demo application <filename>jboss/"
+"webservices.xml</filename> deployment descriptor for an example of how this "
+"can be achieved."
+msgstr ""
+"Pour pouvoir enregistrer le gestionnaire de contexte côté-serveur dans les "
+"services web déployés, une chaîne de gestion devra être incluse dans le "
+"descripteur de déploiement des services web. Veuillez vous reporter au "
+"descripteur de déploiement <filename>jboss/webservices.xml</filename> de "
+"l'application de démonstration pour un exemple sur la façon de procéder."
+
+#. Tag: para
+#: Getting_Started.xml:33
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC client-side context handler used by the "
+"client applications, a handler chain must be included in the definition of "
+"the service-ref in the client web.xml deployment descriptor. Please refer to "
+"the demo application <filename>jboss/client-web-app.xml</filename> for an "
+"example of how this can be achieved."
+msgstr ""
+"Pour pouvoir enregistrer le gestionnaire de contexte côté-client JAX-RPC, "
+"une chaîne de gestion devra être incluse dans la définition de la ref-"
+"service dans le descripteur de déploiement du web.xml du client. Veillez "
+"vous référer à l'application de démonstration <filename>jboss/client-web-app."
+"xml</filename> pour un exemple sur la façon de procéder."
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr "Gestionnaires de contexte webMethods"
+
+#. Tag: para
+#: Getting_Started.xml:38
+#, no-c-format
+msgid ""
+"In order to register the webMethods server-side context handler with the "
+"deployed web services, the inbound and outbound interceptors must be "
+"configured in the web services deployment descriptor. An example of how this "
+"can be configured can be found in the demo application, for example, the "
+"<filename>RestaurantServiceAT.xml</filename>."
+msgstr ""
+"Pour pouvoir enregistrer le gestionnaire de contexte côté-serveur des "
+"webMethods dans les services web déployés, les intercepteurs d'entrée et de "
+"sortie doivent être configurés dans le descripteur de déploiement des "
+"services web. On peut trouver un exemple sur la façon dont cela peut être "
+"configuré dans l'application de démonstration, comme "
+"<filename>RestaurantServiceAT.xml</filename>."
+
+#. Tag: para
+#: Getting_Started.xml:42
+#, no-c-format
+msgid ""
+"In order to register the webMethods client-side context handler, the inbound "
+"and outbound interceptors must be configured in the <filename>glue-config."
+"xml</filename> deployment descriptor. Please refer to the soap interceptor "
+"section of the demo application glue-config.xml for an example of how this "
+"can be achieved."
+msgstr ""
+"Pour pouvoir enregistrer le gestionnaire de contexte côté-serveur des "
+"webMethods, les intercepteurs d'entrée et de sortie doivent être configurés "
+"dans le descripteur de déploiement <filename>glue-config.xml</filename>. On "
+"peut trouver un exemple sur la façon dont cela peut être réalisé dans la "
+"section sur l'intercepteur soap de l'application de démonstration glue-"
+"config.xml."
+
+#. Tag: title
+#: Getting_Started.xml:48
+#, no-c-format
+msgid "Hints and tips"
+msgstr "Astuces et conseils"
+
+#. Tag: para
+#: Getting_Started.xml:49
+#, no-c-format
+msgid ""
+"If you want to create multiple JBoss deploys on the same machine, then you "
+"may wish to look at <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/"
+"MultipleInstances.htm\"><emphasis>Setting up multiple instances</emphasis></"
+"ulink> for information on what is required."
+msgstr ""
+"Si vous souhaitez créer des déploiements multiples JBoss au sein de la même "
+"machine, alors vous souhaiterez sans doute consulter <ulink url=\"http://www."
+"yorku.ca/dkha/jboss/docs/MultipleInstances.htm\"><emphasis>Configurer des "
+"instance multpiples</emphasis></ulink> pour obtenir des informations sur ce "
+"qui est requis."
+
+#. Tag: title
+#: Getting_Started.xml:55
+#, no-c-format
+msgid "Summary"
+msgstr "Résumé"
+
+#. Tag: para
+#: Getting_Started.xml:56
+#, no-c-format
+msgid ""
+"This chapter has provided a high-level overview of how to use each of the "
+"major software pieces of the Web Services transactions component of JBossTS. "
+"The Web Services transaction manager provided by JBossTS is the hub of the "
+"architecture and is the only piece of software that users’ software does not "
+"bind to directly. XTS provides header processing infrastructure for dealing "
+"with Web Services transactions contexts for both users’ client applications "
+"and Web services. For developing transaction participants, XTS provides a "
+"simple interface plus the necessary document handling code."
+msgstr ""
+"Ce chapitre procure une présentation de haut niveau sur la façon d'utiliser "
+"chacune des pièces de programmation principales des composants de "
+"transactions de service Web de JBossTS. Le gestionnaire de transaction des "
+"services Web proposé par JBossTS se situe au centre de l'architecture et "
+"représente la seule pièce de programmation à laquelle les logiciels des "
+"utilisateurs ne sont pas liés directement. XTS propose une infrastructure de "
+"traitement de header (en-tête) pour s'occuper des contextes de transaction "
+"de service Web pour les services Web et pour les applications client des "
+"utilisateurs. Pour les participants aux transactions en cours, XTS fournit "
+"une interface simple, en plus du code de gestion de documents qu'il faut."
+
+#. Tag: para
+#: Getting_Started.xml:59
+#, no-c-format
+msgid ""
+"This chapter is meant as an overview only, and is unlikely to answer "
+"questions on more difficult and subtle aspects. For fuller explanations of "
+"the components, please refer to the appropriate chapter elsewhere in this "
+"document."
+msgstr ""
+"Ce chapitre est sensé ne représenter qu'un aperçu, et ne répondra sans doute "
+"pas à vos questions sur des aspects plus subtiles ou compliqués. Pour des "
+"explications plus complètes sur les composants, veuillez-vous référer au "
+"chapitre qui convient à un autre endroit dans ce document."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Introduction.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Introduction.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Introduction.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,412 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr "Introduction"
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr "Aperçu sur les transactions de Services Web JBossTS"
+
+#. Tag: para
+#: Introduction.xml:9
+#, no-c-format
+msgid ""
+"The XML transaction service component of JBossTS (shorthand referred to as "
+"XTS) supports the coordination of private and public Web services in a "
+"business transaction. Therefore, to understand XTS, you must be familiar "
+"with Web services, and also understand a little about transactions. This "
+"chapter introduces XTS and provides a brief overview of the technologies "
+"that form the Web services standard. Additionally, this chapter explores "
+"some of the fundamentals of transactioning technology and how it can be "
+"applied to Web services. Much of the content presented in this chapter is "
+"detailed throughout this guide; however, only overview information about Web "
+"services is provided. If you are new to creating Web services, please see "
+"consult your Web services platform documentation."
+msgstr ""
+"Le composant de service de transaction XML de JBossTS (XTS) prend en charge "
+"la coordination des services Web publics et privés dans une transaction "
+"commerciale. Ainsi, pour comprendre XTS, vous devez vous familiariser avec "
+"les services Web, et aussi comprendre un peu les transactions. Ce chapitre "
+"introduit XTS et fournit un bref aperçu sur les technologies qui forment les "
+"standards de service Web. De plus, ce chapitre explore certains fondamentaux "
+"de la technologie transactionnelle et comment elle peut être appliquée aux "
+"services Web. La plupart du contenu présenté dans ce chapitre est détaillé "
+"dans ce guide. Cependant, on ne propose qu'un aperçu sur les services Web. "
+"Si vous êtes nouveau dans la création de services Web, veuillez consulter "
+"votre documentaiton de plate-forme de services Web."
+
+#. Tag: para
+#: Introduction.xml:12
+#, no-c-format
+msgid ""
+"JBossTS provides as the XTS component a transaction solution for Web "
+"services. Using XTS, business partners can coordinate complex business "
+"transactions in a controlled and reliable manner. The JBossTS Web Services "
+"API supports a transactional coordination model based on the WS-C, WS-Atomic "
+"Transaction and WS-Business Activity specifications. WS-C is a generic "
+"coordination framework developed by IBM, Microsoft and BEA, WS-Atomic "
+"Transaction and WS-Business Activity are transaction protocols that utilize "
+"this framework."
+msgstr ""
+"JBossTS fournit en tant que composant XTS, une solution de transactions pour "
+"les services Web. En utilisant XTS, les partenaires commerciaux peuvent "
+"coordonner des transaction commerciales complexes d'une façon fiable et "
+"contrôlée. L'API de services Web JBossTS prend en charge un modèle de "
+"coordination transactionnelle basé sur les spécifications WS-C, WS-Atomic "
+"Transaction et WS-Business Activity. WS-C est une structure de coordination "
+"générique développée par IBM, Microsoft et BEA. WS-Atomic Transaction et WS-"
+"Business Activity sont des protocoles de transaction qui utilisent cette "
+"structure."
+
+#. Tag: para
+#: Introduction.xml:15
+#, no-c-format
+msgid ""
+"Web services are modular, reusable software components that are created by "
+"exposing business functionality through a Web service interface. Web "
+"services communicate directly with other Web services using standards-based "
+"technologies such as SOAP and HTTP. These standards-based communication "
+"technologies allow Web services to be accessed by customers, suppliers, and "
+"trading partners, independent of hardware operation system or programming "
+"environment. The result is a vastly improved collaboration environment as "
+"compared to today&#39;s EDI and business-to-business (B2B) solutions—an "
+"environment where businesses can expose their current and future business "
+"applications as Web services that can be easily discovered and accessed by "
+"external partners."
+msgstr ""
+"Les services Web sont des composants de logiciel réutilisables et modulables "
+"qui sont créés en exposant une fonctionnalité commerciale à travers une "
+"interface de services Web. Les services Web communiquent directement avec "
+"les autres services Web en utilisant des technologies basées-standard comme "
+"SOAP et HTTP. Ces technologies de communication basées-standard permettent "
+"que les services Web soient accessibles aux clients, aux fournisseurs, et "
+"aux partenaires commerciaux, indépendamment des systèmes d'exploitation du "
+"matériel ou des environnements de programmation. Il en résulte un "
+"environnement de collaboration largement amélioré par rapport aux solutions "
+"EDI ou B2B (business vers business)- et un environnement dans lequel les "
+"entreprises peuvent exposer leurs applications commerciales courantes et "
+"futures en tant que services Web, qui peuvent être découverts facilement, et "
+"auxquels les partenaires extérieurs peuvent facilement accéder."
+
+#. Tag: para
+#: Introduction.xml:18
+#, no-c-format
+msgid ""
+"Web services, by themselves, are not fault tolerant. In fact, some of the "
+"reasons that make it an attractive development solution are also the same "
+"reasons that service-based applications may have drawbacks:"
+msgstr ""
+"Les services Web, par eux-mêmes, ne tolèrent aucune erreur. En fait, les "
+"raisons qui font qu'elles représentent une solution de développement "
+"attractive, sont les mêmes raisons qui font que les applications basées-"
+"service peuvent présenter des inconvénients."
+
+#. Tag: para
+#: Introduction.xml:23
+#, no-c-format
+msgid ""
+"Application components that are exposed as Web services may be owned by "
+"third parties, which provides benefits in terms of cost of maintenance, but "
+"drawbacks in terms of having exclusive control over their behavior;"
+msgstr ""
+"Les composants de l'application qui sont exposés en tant que services Web, "
+"peuvent être possédés par des parties tierces, qui offrent des avantages en "
+"terme de coût de maintenance, mais des inconvénients au niveau du contrôle "
+"exclusif de leur comportement."
+
+#. Tag: para
+#: Introduction.xml:28
+#, no-c-format
+msgid ""
+"Web services are usually remotely located which increases risk of failure "
+"due to increased network travel for invocations."
+msgstr ""
+"Les services Web sont normalement situés assez loin, ce qui augmente le "
+"risque d'échec à cause des distances de réseau à parcourir qui augmentent "
+"pour les invocations."
+
+#. Tag: para
+#: Introduction.xml:33
+#, no-c-format
+msgid ""
+"Applications that have high dependability requirements, must find a method "
+"of minimizing the effects of errors that may occur when an application "
+"consumes Web services. One method of safeguarding against such failures is "
+"to interact with an application’s Web services within the context of a "
+"transaction. A transaction is simply a unit of work which is completed "
+"entirely, or in the case of failures is reversed to some agreed consistent "
+"state – normally to appear as if the work had never occurred in the first "
+"place. With XTS, transactions can span multiple Web services which mean that "
+"work performed across multiple enterprises can be managed with transactional "
+"support."
+msgstr ""
+"Les applications qui ont des prérequis de dépendance élevés, doivent trouver "
+"une méthode pour minimiser les effets des erreurs qui pourraient survenir "
+"quand une application consomme des services Web. Une méthode de sauvegarde "
+"en cas d'un tel échec, est de se connecter aux services Web d'une "
+"application dans le contexte d'une transaction. Une transaction est "
+"simplement une unité de travail qui est complètement terminée, ou qui en cas "
+"d'échec, est renvoyée à un état consistant sur lequel on peut se mettre "
+"d'accord - qui apparaîtrait normalement si le travail n'avait jamais eu lieu "
+"pour commencer. Avec XTS, les transactions peuvent s'étendre sur plusieurs "
+"services Web, ce qui signifie que le travail effectué à travers plusieurs "
+"entreprises peut être géré par un support transactionnel."
+
+#. Tag: title
+#: Introduction.xml:37
+#, no-c-format
+msgid "Managing Service-Based Processes"
+msgstr "Gérer les processus basés-service"
+
+#. Tag: para
+#: Introduction.xml:38
+#, no-c-format
+msgid ""
+"XTS allows you to create transactions that drive complex business processes "
+"spanning multiple Web services. Current Web services standards do not "
+"address the requirements for a high-level coordination of services since in "
+"today’s Web services applications, which use single request/receive "
+"interactions, coordination is typically not a problem. However, for "
+"applications that engage multiple services among multiple business partners, "
+"coordinating and controlling the resulting interactions is essential. This "
+"becomes even more apparent when you realize that you generally have little "
+"in the way of formal guarantees when interacting with third-party Web "
+"services."
+msgstr ""
+"XTS vous permet de créer des transactions qui sont à l'origine de processus "
+"commerciaux complexes à travers des services Web multiples. Les services Web "
+"standard actuels n'adressent pas les prérequis pour un haut niveau de "
+"coordination de services, puisque dans les applications de services Web "
+"actuels qui utilisent des interactions simples demande / réception, la "
+"coordination n'est pas normalement un problème. Cependant, pour des "
+"applications qui engagent des services multiples parmi des partenaires "
+"commerciaux divers, la coordination et le contrôle des interactions "
+"résultantes sont essentiels. Cela devient d'autant plus apparent quand vous "
+"réalisez que vous possédez très peu de garanties formelles en cas "
+"d'interaction avec des services Web tierces."
+
+#. Tag: para
+#: Introduction.xml:42
+#, no-c-format
+msgid ""
+"XTS provides the infrastructure for coordinating services during a business "
+"process. By organizing processes as transactions, business partners can "
+"collaborate on complex business interactions in a reliable manner, insuring "
+"the integrity of their data - usually represented by multiple changes to a "
+"database – but without the usual overheads and drawbacks of directly "
+"exposing traditional transaction-processing engines directly onto the web. "
+"The following example demonstrates how an application may manage service-"
+"based processes as transactions:"
+msgstr ""
+"XTS fournit une infrastructure de coordination des services pendant le "
+"processus commercial. En organisant les processus en transactions, les "
+"partenaires commerciaux peuvent collaborer sur dans des interactions "
+"commerciales complexes d'une manière fiable, en garantissant l'intégrité de "
+"leurs données - normalement représentées par les changements multiples dans "
+"une base de données - mais sans les surcharges ou inconvénients habituels "
+"d'exposer les moteurs de traitement de transactions traditionnels "
+"directement sur le réseau internet. L'exemple suivant montre comment une "
+"application peut gérer des processus basé-service en tant que transactions :"
+
+#. Tag: para
+#: Introduction.xml:45
+#, no-c-format
+msgid ""
+"The application in question allows a user to plan a social evening. This "
+"application is responsible for reserving a table at a restaurant, and "
+"reserving tickets to a show. Both activities are paid for using a credit "
+"card. In this example, each service represents exposed Web services provided "
+"by different service providers. XTS is used to envelop the interactions "
+"between the theater and restaurant services into a single (potentially) long-"
+"running business transaction. The business transaction must insure that "
+"seats are reserved both at the restaurant and the theater. If one event "
+"fails the user has the ability to decline both events, thus returning both "
+"services back to their original state. If both events are successful, the "
+"user’s credit card is charged and both seats are booked. As you may expect, "
+"the interaction between the services must be controlled in a reliable manner "
+"over a period of time. In addition, management must span several third-party "
+"services that are remotely deployed."
+msgstr ""
+"L'application en question permet aux utilisateurs d'organiser une soirée. "
+"Cette application est responsable de réserver une table dans un restaurant, "
+"et des tickets de spectacle. Ces deux activités sont payées par carte de "
+"crédit. Dans cet exemple, chaque service représente des services Web exposés "
+"proposés par des fournisseurs de service différents. XTS est utilisé pour "
+"englober des interactions entre les services de restauration et de théatre "
+"en une seule et (potentiellement) longue transaction commerciale. La "
+"transaction commerciale doit garantir que les places sont bien réservées au "
+"restaurant et au théatre à la fois. Si un événement venait à manquer, "
+"l'utilisateur aurait la possibilité de décliner les deux événements à la "
+"fois, retournant ainsi les deux services dans leur état d'origine. Si les "
+"deux événements aboutissent avec succès, la carte de crédit de l'utilisateur "
+"est débitée et les deux places sont réservées. Comme vous vous en doutez, "
+"l'interaction entre les services doit être contrôlée d'une manière fiable et "
+"sur une certaine durée. De plus, la gestion doit s'étendre sur plusieurs "
+"services de tierce partie qui sont déployés à distance."
+
+#. Tag: para
+#: Introduction.xml:49
+#, no-c-format
+msgid ""
+"Without the backing of a transaction, an undesirable outcome may occur. For "
+"example, the user credit card may be charged, even though one or both of the "
+"bookings may have failed."
+msgstr ""
+"Sans le soutien d'une transaction, on pourrait aboutir à un effet "
+"indésirable. Par exemple, la carte de crédit de l'utilisateur pourrait être "
+"débitée, même si une ou les deux réservations a pu échouer."
+
+#. Tag: para
+#: Introduction.xml:53
+#, no-c-format
+msgid ""
+"This simple example describes the situations where XTS excels at supporting "
+"business processes across multiple enterprises. This example is further "
+"refined throughout this guide, and appears as a standard demonstrator "
+"(including source code) with the XTS distribution."
+msgstr ""
+"Cet exemple simple décrit des situations pour lesquelles XTS excelle à "
+"supporter des processus commerciaux à travers des entreprises multiples. Cet "
+"exemple est raffiné en détails dans ce guide, et apparaît en tant que "
+"démonstrateur standard (y compris le code source) dans la distribution XTS."
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr "Programmes côté serveur"
+
+#. Tag: para
+#: Introduction.xml:58
+#, no-c-format
+msgid ""
+"The WS-C, WS-Atomic Transaction and WS-Business Activity protocols are based "
+"on one-way interactions of entities rather than traditional synchronous "
+"request/response RPC style interactions. Entities (for example, transaction "
+"participants) invoke operations on other entities (for example, the "
+"transaction coordinator) in order to return responses to requests. What this "
+"means is that the programming model is based on peer-to-peer relationships, "
+"with the result that all services, whether they are participants, "
+"coordinators or clients, must have an active component that allows them to "
+"receive unsolicited messages."
+msgstr ""
+"Les protocoles WS-C, WS-Atomic Transaction et WS-Business Activity sont "
+"basés sur des interactions unilatérales d'entités plutôt que sur des "
+"interactions traditionnelles synchronisées demande/réponse RPC. Les entités "
+"(par exemple, des participants à une transaction) invoquent des opérations "
+"sur d'autres entités (par exemple, le coordinateur de transactions) en vue "
+"de retourner des réponses aux demandes. Cela signifie que le modèle de "
+"programmation est basé sur une relation de paire à paire, ayant pour "
+"conséquence que tous les services, participants, coordinateurs ou clients, "
+"doivent avoir un composant actif qui leur permet de recevoir des messages "
+"non sollicités."
+
+#. Tag: para
+#: Introduction.xml:62
+#, no-c-format
+msgid ""
+"In the current implementation of XTS, the active component is achieved "
+"through the use of Java servlet technology. Each endpoint that can be "
+"communicated with via SOAP/XML is represented as a servlet (and published "
+"within JNDI). Fortunately for the developer, this use of servlets occurs "
+"transparently. The only drawback is that (currently) clients must reside "
+"within a domain capable of hosting servlets, i.e., an application server. It "
+"is our intention that future versions of XTS will provide configurable "
+"deployment options, allowing servlets where required, but not mandating them."
+msgstr ""
+"Dans l'implémentation courante de XTS, le composant actif est réalisé grâce "
+"à l'utilisation de la technologie du servlet Java. Chaque endpoint qui peut "
+"communiquer par SOAP/XML est représenté par un servlet (et publié dans "
+"JNDI). Heureusement pour le développeur, l'utilisation de servlets a lieu de "
+"façon transparente. Le seul problème est que les clients (actuels) doivent "
+"résider dans un domaine capable d'héberger les servlets, c'est à dire, un "
+"serveur d'applications. Nous avons l'intention d'équiper les versions "
+"futures de XTS d'options de déploiement configurables, autorisant les "
+"servlets en fonction des besoins, mais non obligatoires."
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr "SOAP"
+
+#. Tag: para
+#: Introduction.xml:67
+#, no-c-format
+msgid ""
+"SOAP has emerged as the de-facto message format for XML-based communication "
+"in the Web services arena. It is a lightweight protocol that allows the user "
+"to define the content of a message and to provide hints as to how recipients "
+"should process that message."
+msgstr ""
+"SOAP émerge comme le format de messages de-facto pour la communication basée-"
+"XML dans le domaine des services Web. Il s'agit d'un protocole léger qui "
+"permet aux utilisateurs de définir le contenu d'un message et de fournir des "
+"astuces sur la façon dont les destinataires devront traiter ce message."
+
+#. Tag: para
+#: Introduction.xml:71
+#, no-c-format
+msgid ""
+"SOAP messages can be divided into two main categories: Remote Procedure Call "
+"(RPC) and Document Exchange (DE). The primary difference between the two "
+"categories is that the SOAP specification defines encoding rules and "
+"conventions for RPC. The document exchange model allows the exchange of "
+"arbitrary XML documents - a key ingredient of B2B document exchange. XTS is "
+"based on the loosely coupled document-exchange style, yet it can support "
+"transactions spanning Web service that use either document-exchange or RPC."
+msgstr ""
+"Les messages SOAP peuvent être divisés en deux catégories principales : RPC "
+"(Remote Procedure Call / Appel de procédure à distance) et DE (Document "
+"Exchange / Echange de documents). La différence fondamentale entre les deux "
+"catégories est que la spécification SOAP détermine des règles de codage et "
+"des conventions pour RPC. Le modèle d'échange de documents permet l'échange "
+"de documents XML arbitraires - un ingrédient clé de l'échange de documents "
+"B2B. XTS est basé sur le style document DE couplé informellement, mais il "
+"peut prendre en charge des transactions de service Web qui utilisent les "
+"deux sortes de documents - DE ou RPC."
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr "Web Services Description Language (WSDL)"
+
+#. Tag: para
+#: Introduction.xml:76
+#, no-c-format
+msgid ""
+"WSDL is an XML-based language used to define Web service interfaces. An "
+"application that consumes a Web service parses the service’s WSDL document "
+"to discover the location of the service, the operations that the service "
+"supports, the protocol bindings the service supports (SOAP, HTTP, etc), and "
+"how to access them (for each operation, WSDL describes the format that the "
+"client must follow)."
+msgstr ""
+"WSDL est un langage basé-XML utilisé pour définir les interfaces de service "
+"Web. Une application qui consomme un service Web analyse le document WSDL du "
+"service pour découvrir la location du service, les opérations que le service "
+"prend en charge, les liaisons de protocole que le service prend en charge "
+"(SOAP,HTTP, etc) et comment y accéder (pour chaque opération, WSDL décrit le "
+"format que le client doit suivre)."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
===================================================================

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Participants.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Participants.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Participants.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,631 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Participants.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "Test"
+
+#. Tag: para
+#: Participants.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "Ceci est un paragraphe test"
+
+#. Tag: title
+#: Participants.xml:11
+#, no-c-format
+msgid "The Participant: an Overview"
+msgstr "Le participant : un aperçu général"
+
+#. Tag: para
+#: Participants.xml:12
+#, no-c-format
+msgid ""
+"The participant is the entity that performs the work pertaining to "
+"transaction management on behalf of the business services involved in an "
+"application. The Web service (for example, a theatre booking system) "
+"contains some business logic for reserving a seat, enquiring availability "
+"etc, but it will need to be supported by something that maintains "
+"information in a durable manner. Typically this will be a database, but it "
+"could be a file system, NVRAM, etc. Now, although the service may talk to "
+"the back-end database directly, it cannot commit or undo any changes it (the "
+"services) makes, since these are ultimately under the control of the "
+"transaction that scoped the work. In order for the transaction to be able to "
+"exercise this control, it must have some contact with the database. In XTS "
+"this is accomplished by the participant, and the role played by the "
+"participant between the transaction and back-end transaction processing "
+"infrastructure is shown in the following figure."
+msgstr ""
+"Le participant est une entité qui effectue le travail attenant à la gestion "
+"de transaction pour le compte des services commerciaux impliqués dans une "
+"application. Le service Web (par exemple, un système de réservation de "
+"théatre) contient une certaine logique commerciale pour réserver une place, "
+"vérifier la disponibilité, etc, mais il devra être supporté par quelque "
+"chose qui maintient l'information de façon durable. Normalement, il s'agira "
+"d'une base de données, mais il pourrait s'agir d'un système de fichiers, "
+"NVRAM, etc. Maintenant, malgré que le service puisse communiquer directement "
+"avec la base de données back-end, il ne peut pas valider ou supprimer de "
+"changements effectués par le service, puisqu'ils relèvent du contrôle de la "
+"transaction en question. Pour que la transaction puisse exercer ce genre de "
+"contrôle, elle doit être liée à une sorte de contrat avec la base de "
+"données. Dans XTS, c'est réalisé par le participant. Le rôle que joue le "
+"participant entre la transaction et l'infrastructure de traitement de "
+"transactions back-end est exposé dans le schéma suivant :"
+
+#. Tag: caption
+#: Participants.xml:19
+#, no-c-format
+msgid "Transactions, Participants, and Back-End Transaction Control"
+msgstr "Transactions, participants, et contrôle de transaction back-end"
+
+#. Tag: para
+#: Participants.xml:21
+#, no-c-format
+msgid ""
+"Each participant in XTS is related to either the Atomic Transaction or "
+"Business Activity protocols. In the following sections we’ll consider both "
+"protocols and their respective participants."
+msgstr ""
+"Chaque participant XTS est relié soit à un protocole AT (Atomic "
+"Transaction / transaction atomique), soit à un protocole BA (Business "
+"Acitivity / Activité commerciale). Dans les sections suivantes, nous allons "
+"considérer les deux protocoles et leurs participants respectifs."
+
+#. Tag: title
+#: Participants.xml:25
+#, no-c-format
+msgid "Atomic Transaction"
+msgstr "Transaction atomique"
+
+#. Tag: para
+#: Participants.xml:26
+#, no-c-format
+msgid ""
+"All Atomic Transaction participants are instances of one of the following "
+"interfaces."
+msgstr ""
+"Tous les participants de transactions atomiques sont des instances des "
+"interfaces suivantes. "
+
+#. Tag: title
+#: Participants.xml:31
+#, no-c-format
+msgid "Durable2PCParticipant"
+msgstr "Durable2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:32
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Durable2PC protocol with "
+"the following signatures, as per the <interfacename>com.arjuna.wst."
+"Durable2Participant</interfacename> interface:"
+msgstr ""
+"Ce participant prend en charge le protocole WS-Atomic Transaction Durable2PC "
+"avec les signatures suivantes, comme dans l'interface <interfacename>com."
+"arjuna.wst.Durable2Participant</interfacename> :"
+
+#. Tag: para
+#: Participants.xml:38
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the <code>com.arjuna.wst."
+"Vote</code>. Values are: <code>ReadOnly</code>, indicating the participant "
+"does not need to be informed of the transaction outcome as no state updates "
+"were made; Prepared, indicating the participant is prepared to commit or "
+"rollback depending on the final transaction outcome, and it has made "
+"sufficient state updates persistent to accomplish this; and Aborted, "
+"indicating the participant has aborted and the transaction should also "
+"attempt to do so."
+msgstr ""
+"<emphasis>prepare</emphasis>: le participant devrait effectuer le travail "
+"nécessaire qui puisse lui permettre de valider ou de rejeter le travail "
+"effectué par le service Web sous la coupe de la transaction. "
+"L'implémentation est libre de faire ce que bon lui semble pour remplir le "
+"contrat implicite avec le coordinateur. On s'attend à ce que le participant "
+"indique s'il peut ou non 'préparer' en retournant une instance de <code>com."
+"arjuna.wst.Vote</code>. Les valeurs sont : <code>ReadOnly</code>, indiquant "
+"par là même que le participant n'a pas besoin d'être informé du résultat de "
+"la transaction car il n'y a pas eu de mises à jour des états. 'Prepared' "
+"indique que le participant est prêt à valider ou à rejeter la transaction en "
+"fonction du résultat final de la transaction, et il a effectué suffisamment "
+"de mises à jour d'états persistants dans ce but. 'Aborted' (abandonné) "
+"indique que le participant a abandonné et que la transaction devrait essayer "
+"de faire la même chose."
+
+#. Tag: para
+#: Participants.xml:43 Participants.xml:81
+#, no-c-format
+msgid ""
+"<emphasis>commit</emphasis>: the participant should make permanent the work "
+"that it controls. What it does will depend upon its implementation, for "
+"example, commit the reservation of the theatre ticket. The participant will "
+"then return an indication of whether or not it succeeded."
+msgstr ""
+"<emphasis>commit</emphasis>: le participant devrait rendre permanent le "
+"travail qu'il contrôle. Ce qu'il fait dépendra de son implémentation, par "
+"exemple. valider la réservation de son billet de théatre. Le participant "
+"retournera alors une indication pour savoir si l'opération a réussi ou non."
+
+#. Tag: para
+#: Participants.xml:48 Participants.xml:86
+#, no-c-format
+msgid ""
+"<emphasis>rollback</emphasis>: the participant should undo the work that it "
+"controls. The participant will then return an indication of whether or not "
+"it succeeded."
+msgstr ""
+"<emphasis>rollback</emphasis>: le participant devrait démanteler le travail "
+"qu'il contrôle. Le participant retournera ou non une indication pour savoir "
+"si l'opération a réussi ou non."
+
+#. Tag: para
+#: Participants.xml:53 Participants.xml:91
+#, no-c-format
+msgid ""
+"<emphasis>commitOnePhase</emphasis>: if there is only a single "
+"TwoPCParticipant registered with the transaction, then the coordinator can "
+"optimize the protocol and simply tell the participant to commit: there is no "
+"need for a preparatory phase since consensus is implicit."
+msgstr ""
+"<emphasis>commitOnePhase</emphasis>: s'il y a un seul TwoPCParticipant "
+"enregistré dans la transaction, alors le coordinateur peut optimiser le "
+"protocole et indiquer au participant de valider l'opération : il n'y a pas "
+"besoin de phase préparatoire car le consensus est implicite."
+
+#. Tag: para
+#: Participants.xml:58 Participants.xml:96
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: during recovery the participant can inquire as "
+"to the status of the transaction it was registered with. If that transaction "
+"is no longer available (has rolled back) then this operation will be invoked "
+"by the coordination service."
+msgstr ""
+"<emphasis>unknown</emphasis>: pendant le recouvrement, le participant peut "
+"vérifier le statut de la transaction pour laquelle il est enregistré. Si "
+"cette transaction n'est plus disponible ( a été rejetée par exemple) alors, "
+"cette opération sera invoquée par le service de coordination."
+
+#. Tag: para
+#: Participants.xml:63 Participants.xml:101
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: during recovery the participant can enquire as "
+"to the status of the transaction it was registered with. If an error occurs "
+"(for example, the transaction service is unavailable) then this operation "
+"will be invoked."
+msgstr ""
+"<emphasis>error</emphasis>: pendant le recouvrement, le participant pourra "
+"vérifier le statut de la transaction pour laquelle il est enregistré. En cas "
+"d'erreur (par exemple, le service de transaction n'est pas disponible) "
+"alors, cette opération sera invoquée."
+
+#. Tag: title
+#: Participants.xml:69
+#, no-c-format
+msgid "Volatile2PCParticipant"
+msgstr "Volatile2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:70
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Volatile2PC protocol "
+"with the following signatures, as per the <interfacename>com.arjuna.wst."
+"Volatile2Participant</interfacename> interface:"
+msgstr ""
+"Ce participant prend en charge le protocole WS-Atomic Transaction "
+"Volatile2PC avec les signatures suivantes, comme dans l'interface "
+"<interfacename>com.arjuna.wst.Volatile2Participant</interfacename> :"
+
+#. Tag: para
+#: Participants.xml:76
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the com.arjuna.wst.Vote. "
+"Values are: ReadOnly, indicating the participant does not need to be "
+"informed of the transaction outcome as no state updates were made; Prepared, "
+"indicating the participant is prepared to commit or rollback depending on "
+"the final transaction outcome, and it has made sufficient state updates "
+"persistent to accomplish this; and Aborted, indicating the participant has "
+"aborted and the transaction should also attempt to do so."
+msgstr ""
+"<emphasis>prepare</emphasis>: le participant doit préparer n'importe quel "
+"travail nécessaire pour pouvoir valider ou rejeter le travail effectué par "
+"le service Web sous la coupe de la transaction. L'implémentation est libre "
+"de faire ce que bon lui semble pour remplir le contrat avec le coordinateur. "
+"On s'attend alors à ce que le participant indique s'il peut 'préparer' ou "
+"non en retournant une instance du com.arjuna.wst.Vote. Les valeurs sont : "
+"ReadOnly (lecture seule), indiquant que le participant n'a pas besoin d'être "
+"informé du résultat de la transaction car il n'y a pas eu de mise à jour des "
+"états. 'Prepared' indique que le participant est préparé à valider ou à "
+"rejeter en fonction du résultat final de la transaction, et il a effectué "
+"suffisamment de mises à jour d'états pour accomplir cette tâche. "
+"'Aborted' (abandonné) indique que le participant a abandonné et que la "
+"transaction devrait essayer de faire de même."
+
+#. Tag: title
+#: Participants.xml:107
+#, no-c-format
+msgid "Business Activity"
+msgstr "Activité commerciale"
+
+#. Tag: para
+#: Participants.xml:108
+#, no-c-format
+msgid ""
+"All Business Activity participants are instances of the following interfaces."
+msgstr ""
+"Tous les participants BA (Businees Activity / Activité commerciale) sont des "
+"instances des interfaces suivantes."
+
+#. Tag: title
+#: Participants.xml:113
+#, no-c-format
+msgid "BusinessAgreementWithParticipantCompletion"
+msgstr "BusinessAgreementWithParticipantCompletion"
+
+#. Tag: para
+#: Participants.xml:114
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"Ce participant prend en charge le protocole WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> avec les signatures "
+"suivantes, selon l'interface suivante <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename> :"
+
+#. Tag: para
+#: Participants.xml:120 Participants.xml:158
+#, no-c-format
+msgid ""
+"<emphasis>close</emphasis>: the transaction has completed successfully. The "
+"participant previously informed the coordinator that it was ready to "
+"complete."
+msgstr ""
+"<emphasis>close</emphasis>: la transaction a réussi. Le participant avait "
+"informé le coordinateur que la transaction était sur le point d'aboutir."
+
+#. Tag: para
+#: Participants.xml:125
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work. The participant cannot have informed the "
+"coordinator that it has completed."
+msgstr ""
+"<emphasis>cancel</emphasis>: la transaction est annulée, et le participant "
+"doit démanteler tout travail. Le participant n'a pu informer le coordinateur "
+"que la transaction a abouti."
+
+#. Tag: para
+#: Participants.xml:130 Participants.xml:168
+#, no-c-format
+msgid ""
+"<emphasis>compensate</emphasis>: the transaction has canceled. The "
+"participant previously informed the coordinator that it had finished work "
+"but could compensate later if required, so it is now requested to do so."
+msgstr ""
+"<emphasis>compensate</emphasis>: la transaction est annulée. Le participant "
+"avait informé le participant du fait qu'il avait terminé son travail, mais "
+"qu'il pourrait compenser plus tard si nécessaire. On lui demande maintenant "
+"de compenser."
+
+#. Tag: para
+#: Participants.xml:135 Participants.xml:178
+#, no-c-format
+msgid "<emphasis>status</emphasis>: return the status of the participant."
+msgstr "<emphasis>status</emphasis>: retourne le statut du participant."
+
+#. Tag: para
+#: Participants.xml:140 Participants.xml:183
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: if the participant inquires as to the status "
+"of the transaction it was registered with and that transaction is no longer "
+"available (has rolled back) then this operation will be invoked by the "
+"coordination service."
+msgstr ""
+"<emphasis>unknown</emphasis>: si le participant se renseigne sur le statut "
+"de la transaction dans laquelle il s'est enregistré, et que cette "
+"transaction n'est plus disponible (rejetée) alors cette opération sera "
+"invoquée par le service de coordination."
+
+#. Tag: para
+#: Participants.xml:145 Participants.xml:188
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: if the participant enquired as to the status of "
+"the transaction it was registered with and an error occurs (for example, the "
+"transaction service is unavailable) then this operation will be invoked."
+msgstr ""
+"<emphasis>error</emphasis>: si la participant se renseigne sur le statut de "
+"la transaction dans laquelle il s'est enregistré et qu'une erreur apparaisse "
+"(par exemple, le service de transaction n'est plus disponible) alors cette "
+"opération sera invoquée."
+
+#. Tag: title
+#: Participants.xml:151
+#, no-c-format
+msgid "BusinessAgreementWithCoordinatorCompletion"
+msgstr "BusinessAgreementWithCoordinatorCompletion"
+
+#. Tag: para
+#: Participants.xml:152
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"Le participant prend en charge le protocole "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> avec les signatures "
+"suivantes, suivant l'interface <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename> :"
+
+#. Tag: para
+#: Participants.xml:163
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work."
+msgstr ""
+"<emphasis>cancel</emphasis>: la transaction est annulée, et le participant "
+"devrait démanteler tout travail."
+
+#. Tag: para
+#: Participants.xml:173
+#, no-c-format
+msgid ""
+"<emphasis>complete</emphasis>: the coordinator is informing the participant "
+"that all work it needs to do within the scope of this business activity has "
+"been received."
+msgstr ""
+"<emphasis>complete</emphasis>: le coordinateur informe le participant que "
+"tout le travail à effectuer dans le cadre de cette activité commerciale a "
+"bien été reçu."
+
+#. Tag: title
+#: Participants.xml:194
+#, no-c-format
+msgid "BAParticipantManager"
+msgstr "BAParticipantManager"
+
+#. Tag: para
+#: Participants.xml:195
+#, no-c-format
+msgid ""
+"In order for the Business Activity protocol to work correctly, the "
+"participants must be able to autonomously signal the coordinator that they "
+"have left the activity (exited) or are ready to complete and (if necessary) "
+"compensate (completed). Unlike the Atomic Transaction protocol, where all "
+"interactions between the coordinator and participants are instigated by the "
+"coordinator when the transaction terminates, this interaction pattern "
+"requires the participant to be able to talk to the coordinator at any time "
+"during the lifetime of the business activity."
+msgstr ""
+"Pour que le protocole BA fonctionne correctement, les participants doivent "
+"être en mesure de signaler au coordinateur de façon autonome qu'ils ont "
+"abandonné l'activité (sortie) ou qu'ils sont sur le point de la conclure et "
+"(si nécessaire) compenser (terminé). A la différence du protocole AT, où "
+"toutes les transactions entre le coordinateur et les participants sont "
+"commises par le coordinateur en fin de transaction, ce modèle d'interaction "
+"exige que le participant soit en mesure de rentrer en contact avec le "
+"coordinateur à tout moment au cours de la durée de vie d'une activité "
+"commerciale."
+
+#. Tag: para
+#: Participants.xml:199
+#, no-c-format
+msgid ""
+"As such, whenever a participant is registered with a business activity, it "
+"receives a handle on the coordinator. This handle is an instance of the "
+"<interfacename>BAParticipantManager</interfacename> interface, located in "
+"<code>com.arjuna.wst.BAParticipantManager</code>, with the following methods:"
+msgstr ""
+"Ainsi, à chaque fois qu'un participant est enregistré dans une activité "
+"commerciale, il reçoit un descripteur sur le coordinateur. Ce descripteur "
+"est une instance de l'interface <interfacename>BAParticipantManager</"
+"interfacename> située dans <code>com.arjuna.wst.BAParticipantManager</code>, "
+"avec les méthodes suivantes :"
+
+#. Tag: para
+#: Participants.xml:204
+#, no-c-format
+msgid ""
+"<emphasis>exit</emphasis>: the participant has exited the business activity. "
+"The participant uses this to inform the coordinator that is has left the "
+"activity. It will not be informed when (and how) the business activity "
+"terminates."
+msgstr ""
+"<emphasis>exit</emphasis>: le participant a quitté une activité commercial "
+"(BA). Le participant l'utilise pour informer le coordinateur qu'il a quitté "
+"l'activité. Il ne sera pas notifié de quand (ni de comment) l'activité "
+"commerciale s'est terminée."
+
+#. Tag: para
+#: Participants.xml:209
+#, no-c-format
+msgid ""
+"<emphasis>completed</emphasis>: the participant has completed it works, but "
+"wishes to continue in the business activity, so that it will eventually be "
+"told when (and how) the activity terminates. The participant may later be "
+"asked to compensate for the work it has done."
+msgstr ""
+"<emphasis>completed</emphasis>: le participant a terminé son travail, mais "
+"souhaite continuer son activité commerciale, donc on lui indiquera quand (et "
+"comment) l'activité se termine. On demandera certainement au participant de "
+"compenser pour le travail accompli un peu plus tard."
+
+#. Tag: para
+#: Participants.xml:214
+#, no-c-format
+msgid ""
+"<emphasis>fault</emphasis>: the participant encountered an error during "
+"normal activation and has compensated. This places the business activity "
+"into a mandatory cancel-only mode."
+msgstr ""
+"<emphasis>fault</emphasis>: la participant se heurte à une erreur en cours "
+"d'activation normale et est compensé. Cela place l'activité commerciale dans "
+"un mode annulation-seulement de rigueur."
+
+#. Tag: title
+#: Participants.xml:222
+#, no-c-format
+msgid "Participant Creation and Deployment"
+msgstr "Création de participants et déploiement"
+
+#. Tag: para
+#: Participants.xml:223
+#, no-c-format
+msgid ""
+"As has been shown, the participant provides the plumbing that drives the "
+"transactional aspects of the service. This section discusses the specifics "
+"of Participant programming and usage."
+msgstr ""
+"Comme nous l'avons vu, le participant fournit la structure qui actionne les "
+"aspects transactionnels du service. Cette section aborde les spécificités de "
+"l'usage et de la programmation des participants."
+
+#. Tag: title
+#: Participants.xml:227
+#, no-c-format
+msgid "Implementing Participants"
+msgstr "Implémenter les participants"
+
+#. Tag: para
+#: Participants.xml:228
+#, no-c-format
+msgid ""
+"Implementing a participant is, in theory, a relatively straightforward task, "
+"though depending on the complexity of the transactional infrastructure that "
+"the participant is to manage, the actual size and complexity of a "
+"participant will vary. The participant interfaces can be found under "
+"<code>com.arjuna.wst</code>. Your implementation must implement one of these "
+"interfaces."
+msgstr ""
+"Implémenter un participant est, en théorie, une tâche simple, malgré le "
+"fait, qu'elle dépend de la complexité de l'infrastructure transactionnelle "
+"que le participant devra gérer. La taille et la complexité d'un participant "
+"varie. Les interfaces du participant peuvent être trouvées dans <code>com."
+"arjuna.wst</code>. Votre implémentation doit mettre en oeuvre une de ces "
+"interfaces."
+
+#. Tag: title
+#: Participants.xml:233
+#, no-c-format
+msgid "Deploying Participants"
+msgstr "Déployer les participants"
+
+#. Tag: para
+#: Participants.xml:234
+#, no-c-format
+msgid ""
+"In order to allow Participants to be located remote from the Transaction "
+"Manager, XTS includes transparent message routing functionality. The "
+"Participant classes are not exposed directly as web services, but rather "
+"registered with a web service which receives messages from the Transaction "
+"Manager and maps them to appropriate method invocations on the relevant "
+"Participant instance. Transactional web services will typically enroll a new "
+"Participant instance of the desired type for each new transaction. A unique "
+"identifier must be provided at enrollment time and will be used to map "
+"transaction protocol messages to the appropriate participant instance. Note "
+"that Participant method invocations do not occur in a specific transaction "
+"context. Therefore, if your Participant implementation requires knowledge of "
+"the transaction context (for example, to look up state information in a "
+"persistent store) then you should provide this to the Participant instance, "
+"typically as an argument to the constructor function. Sample Participant "
+"implementations and usage can be found in the demonstration application "
+"included with XTS."
+msgstr ""
+"Pour pouvoir autoriser les participants à être localisés à distance du "
+"gestionnaire de transaction, XTS inclut une fonctionnalité de routage de "
+"message transparente. Les classes de Participant ne sont pas exposées "
+"directement en tant que services web, mais elles sont enregistrées dans le "
+"service web qui reçoit les messages du gestionnaire de transactions et les "
+"mappe vers les invocations de méthode qui conviennent, sur l'instance de "
+"participant qui s'impose. Les services web transactionnels enrôleront "
+"normalement une nouvelle instance de Participant du type souhaité pour "
+"chaque nouvelle transaction. Un identifiant unique devra être fourni au "
+"moment de l'inscription et sera utilisé pour mapper les messages de "
+"protocole de transaction vers l'instance de participant qui convient. Notez "
+"bien que les invocations de méthodes de Participants n'ont pas lieu dans un "
+"contexte de transaction particulier. De ce fait, si l'implémentation de "
+"votre Participant requiert une connaissance du contexte de transaction (par "
+"exemple, pour chercher l'information sur les états dans un store permanent) "
+"alors vous devrez le fournir à l'instance du Participant, normalement sous "
+"la forme d'argument pour la fonction du constructeur. On peut trouver des "
+"exemples d'utilisation et d'implémentations de Participants dans "
+"l'application de démonstration incluse dans XTS."
+
+#. Tag: para
+#: Participants.xml:238
+#, no-c-format
+msgid ""
+"Any application code which creates and enrolls Participants must be deployed "
+"along with the parts of XTS necessary for receiving and processing incoming "
+"messages from the Transaction Manager. This typically means including the "
+"appropriate XTS .jar, .wsr and .war files in your application. If you are "
+"deploying your application only a server which does not already contain a "
+"Transaction Manger installation, you will also need to deploy the XTS "
+"configuration files."
+msgstr ""
+"Tout code d'application qui crée ou inscrit des Participants doit être "
+"déployé avec les parties XTS qu'il faut pour recevoir et traiter les "
+"messages en provenance du gestionnaire de transactions. Normalement, cela "
+"implique d'inclure les fichiers XTS .jar, .wsr et .war dans votre "
+"application. Si vous déployez votre application dans un serveur qui ne "
+"contient pas déjà une installation de gestionnaire de transaction, alors "
+"vous aurez également besoin de déployer les fichiers de configuration XTS."
+
+#. Tag: para
+#: Participants.xml:242
+#, no-c-format
+msgid ""
+"In early access releases of the XTS product, the Transaction Manager and "
+"participant management functions are not provided as separable components. "
+"Configuration and deployment of the participant infrastructure is therefore "
+"as in the Transaction Manger section above. More flexible deployment of the "
+"XTS components will be available in the final release."
+msgstr ""
+"Dans les versions d'accès des produits XTS, le gestionnaire de transactions "
+"et les fonctions de gestion des participants ne sont pas fournis en tant que "
+"composants séparés. La configuration et le déploiement de l'infrastructure "
+"du participant est la même que celle décrite dans la section gestionnaire de "
+"transaction ci-dessus. Un déploiement plus flexible des composants XTS sera "
+"disponible dans la version finale."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Preface.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Preface.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr "Préface"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Revision_History.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Revision_History.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,29 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "Historique de révision"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Stand-alone_Coordinator.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Stand-alone_Coordinator.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Stand-alone_Coordinator.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,39 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:6
+#, no-c-format
+msgid "Stand-alone Coordinator"
+msgstr "Coordinateur autonome"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introduction"
+
+#. Tag: para
+#: Stand-alone_Coordinator.xml:9
+#, no-c-format
+msgid ""
+"For configuring a stand-alone Web Services transaction coordinator, see the "
+"relevant chapter in the System Administrator’s Guide."
+msgstr ""
+"Pour configurer le coordinateur de transactions Web Services autonome, voir "
+"le chapitre concerné dans le Guide de l'administrateur de systémes."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/The_XTS_API.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/The_XTS_API.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/The_XTS_API.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,762 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr "L'API XTS"
+
+#. Tag: title
+#: The_XTS_API.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introduction"
+
+#. Tag: para
+#: The_XTS_API.xml:9
+#, no-c-format
+msgid ""
+"This chapter shows how to use the XTS API. This is of use both at the client-"
+"side where applications consume transactional Web services, and at the "
+"service/participant side where transactions need to be coordinated with back-"
+"end systems."
+msgstr ""
+"Ce chapitre montre comment utiliser l'API XTS. Il est utilisé à la fois côté-"
+"client quand les applications consomment des services Web transactionnelles, "
+"et du côté service/participant quand les transactions ont besoin d'être "
+"coordonnées par des systèmes back-end."
+
+#. Tag: title
+#: The_XTS_API.xml:15
+#, no-c-format
+msgid "API for the Atomic Transaction protocol"
+msgstr "API pour le protocole Atomic Transaction (AT)"
+
+#. Tag: para
+#: The_XTS_API.xml:16
+#, no-c-format
+msgid ""
+"The following classes and interfaces are located within the <package>com."
+"arjuna.wst or com.arjuna.mw.wst</package> packages and sub-packages."
+msgstr ""
+"Les classes et interfaces suivantes sont situées dans les paquets et sous-"
+"paquets <package>com.arjuna.wst or com.arjuna.mw.wst</package>."
+
+#. Tag: title
+#: The_XTS_API.xml:20
+#, no-c-format
+msgid "Vote"
+msgstr "Vote"
+
+#. Tag: para
+#: The_XTS_API.xml:21
+#, no-c-format
+msgid ""
+"During the two-phase commit protocol, a participant will be asked to vote on "
+"whether or not it can prepare to confirm the work that it controls. It must "
+"return one of the following subtypes of <code>com.arjuna.wst.Vote</code>:"
+msgstr ""
+"Pendant le protocole de validation en deux phases, on demandera à un "
+"participant de voter si il peut oui ou non se préparer à confirmer le "
+"travail qu'il contrôle. Il doit retourner l'un des sous-types de <code>com."
+"arjuna.wst.Vote</code> suivants :"
+
+#. Tag: para
+#: The_XTS_API.xml:27
+#, no-c-format
+msgid ""
+"<emphasis>Prepared</emphasis>: the participant indicates that it can prepare "
+"if asked to by the coordinator. It will not have committed at this stage "
+"however, since it does not know what the final outcome will be."
+msgstr ""
+"<emphasis>Prepared</emphasis>: le participant indique qu'il peut 'préparer' "
+"s'il y est invité par le coordinateur. Cependant, à ce niveau là, il n'aura "
+"pas validé car il ne sait pas ce que le résultat final sera."
+
+#. Tag: para
+#: The_XTS_API.xml:32
+#, no-c-format
+msgid ""
+"<emphasis>Aborted</emphasis>: the participant indicates that it cannot "
+"prepare and has in fact rolled back. The participant should not expect to "
+"get a second phase message."
+msgstr ""
+"<emphasis>Aborted</emphasis>: le participant indique qu'il ne peut pas "
+"'préparer' et qu'il a en fait été rejeté. Le participant ne devrait pas "
+"s'attendre à recevoir un second message."
+
+#. Tag: para
+#: The_XTS_API.xml:37
+#, no-c-format
+msgid ""
+"<emphasis>ReadOnly</emphasis>: the participant indicates that the work it "
+"controls has not made any changes to state that require it to be informed of "
+"the final outcome of the transaction. Essentially the participant is "
+"resigning from the transaction."
+msgstr ""
+"<emphasis>ReadOnly</emphasis>: le participant indique que le travail qu'il "
+"contrôle n'a pas effectué de changement d'états qui nécessitent qu'il soit "
+"informé du résultat final de la transaction. Essentiellement, la participant "
+"résigne de la transaction."
+
+#. Tag: para
+#: The_XTS_API.xml:42
+#, no-c-format
+msgid ""
+"Thus a possible implementation of a 2PC participant’s prepare method may "
+"resemble the following:"
+msgstr ""
+"Donc, une implémentation possible de la méthode 'prepare' du participant 2PC "
+"pourrait ressembler à ceci :"
+
+#. Tag: screen
+#: The_XTS_API.xml:45
+#, no-c-format
+msgid ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+msgstr ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+
+#. Tag: title
+#: The_XTS_API.xml:47
+#, no-c-format
+msgid "The transaction context"
+msgstr "Le contexte de transaction"
+
+#. Tag: para
+#: The_XTS_API.xml:48
+#, no-c-format
+msgid ""
+"A transaction is typically represented by some unique identifier and a "
+"reference to the coordinator which manages the transaction, for example, a "
+"URL. XTS allows transactions to be nested such that a transaction hierarchy "
+"(tree) may be formed. Thus, a transaction context may be a set of "
+"transactions, with the top-most transaction the root parent (superior)."
+msgstr ""
+"Une transaction est normalement représentée par certains identifiants "
+"uniques et une référence au coordinateur qui gère la transaction, comme par "
+"exemple, un URL. XTS permet que les transactions soient intégrées de façon à "
+"ce qu'une hiérarchie (arborescence) de transactions apparaisse. Ainsi, un "
+"contexte de transaction peut correspondre à un ensemble de transactions, "
+"avec la transaction la plus élevée comme parent racine (supérieur)."
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr "TxContext"
+
+#. Tag: para
+#: The_XTS_API.xml:54
+#, no-c-format
+msgid ""
+"<code>com.arjuna.mw.wst.TxContext</code> is an opaque representation of a "
+"transaction context."
+msgstr ""
+"<code>com.arjuna.mw.wst.TxContext</code> est une représentation opaque d'un "
+"contexte de transaction."
+
+#. Tag: para
+#: The_XTS_API.xml:60
+#, no-c-format
+msgid ""
+"<emphasis>valid</emphasis>: this indicates whether or not the contents are "
+"valid."
+msgstr ""
+"<emphasis>valid</emphasis>: indique si oui ou non les contenus sont valides."
+
+#. Tag: para
+#: The_XTS_API.xml:65
+#, no-c-format
+msgid "<emphasis>equals</emphasis>: can be used to compare two instances."
+msgstr ""
+"<emphasis>equals</emphasis>: peut être utilisé pour comparer deux instances."
+
+#. Tag: title
+#: The_XTS_API.xml:71
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: The_XTS_API.xml:72
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserTransaction</classname> is the class that "
+"most users (for example, clients and services) will see. This isolates them "
+"from the underlying protocol-specific aspects of the XTS implementation. "
+"Importantly, a UserTransaction does not represent a specific transaction, "
+"but rather is responsible for providing access to an implicit per-thread "
+"transaction context; it is similar to the UserTransaction in the JTA "
+"specification. Therefore, all of the UserTransaction methods implicitly act "
+"on the current thread of control."
+msgstr ""
+"La classe <classname>com.arjuna.wst.UserTransaction</classname> est la "
+"classe que la plupart des utilisateurs apercevront (par exemple, clients et "
+"services). Cela les isole des aspects particuliers au protocole sous-jacents "
+"de l'implémentation XTS. Surtout, une UserTransaction ne représente pas une "
+"transaction en particulier, mais est plutôt responsable de procurer un accès "
+"à un contexte de transaction par-thread implicite. C'est semblable à "
+"UserTransaction dans la spécification JTA. De ce fait, toutes les méthodes "
+"UderTransaction agissent implicitement sur le thread de contrôle courant."
+
+#. Tag: para
+#: The_XTS_API.xml:76
+#, no-c-format
+msgid ""
+"A new transaction is begun and associated with the invoking thread by using "
+"the begin method. If there is already a transaction associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created transaction with the "
+"current thread."
+msgstr ""
+"On commence une transaction et on l'associe à un thread invoquant par la "
+"méthode 'begin'. S'il existe déjà une transaction associée au thread, alors "
+"l'exception <code>WrongStateException</code> est lancée. Si cela fonctionne, "
+"cette opération associe la transaction nouvellement créée au thread actuel."
+
+#. Tag: para
+#: The_XTS_API.xml:79
+#, no-c-format
+msgid ""
+"The transaction is committed by the commit method. This will execute the "
+"Volatile2PC and Durable2PC protocols prior to returning. If there is no "
+"transaction associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. If the transaction "
+"ultimately rolls back then the <code>TransactionRolledBackException</code> "
+"is thrown. When complete, this operation disassociates the transaction from "
+"the current thread such that it becomes associated with no transaction."
+msgstr ""
+"La transaction est validée par la méthode de validation. Elle exécutera les "
+"protocoles Volatile2PC et Durable2PC avant d'être retournée. S'il n'y a pas "
+"de transaction associée au thread invoquant, alors "
+"<code>UnknownTransactionException</code> est lancé. Si la transaction finit "
+"par être rejetée, alors <code>TransactionRolledBackException</code> est "
+"lancé. Une fois terminée, cette opération dissocie la transaction du thread "
+"courant de façon à ce qu'il finisse par ne plus être associé à aucune "
+"transaction."
+
+#. Tag: para
+#: The_XTS_API.xml:82
+#, no-c-format
+msgid ""
+"The <code>rollback</code> operation will terminate the transaction and "
+"return normally if it succeeded, while throwing an appropriate exception if "
+"it didn’t. If there is no transaction associated with the invoking thread "
+"then <code>UnknownTransactionException</code> is thrown."
+msgstr ""
+"L'opération <code>rollback</code> terminera la transaction et retournera "
+"normalement en cas de succès, tout en lançant une exception qui convient en "
+"cas d'échec. S'il n'y a pas de transactions associées au thread invoquant, "
+"alors <code>UnknownTransactionException</code> est lancé."
+
+#. Tag: title
+#: The_XTS_API.xml:86
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr "UserTransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+"UserTransactions sont obtenues à partir de <code>UserTransactionFactory</"
+"code>."
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: The_XTS_API.xml:93
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface represents "
+"the service/container/participant’s (service-side users) typical way in "
+"which to interact with the underlying transaction service implementation. As "
+"with <interfacename>UserTransaction</interfacename> a "
+"<interfacename>TransactionManager</interfacename> does not represent a "
+"specific transaction, but rather is responsible for providing access to an "
+"implicit per-thread transaction context."
+msgstr ""
+"L'interface <interfacename>TransactionManager</interfacename> représente la "
+"façon typique dont le service/container/participant (utilisateurs côté-"
+"services) interacte avec l'implémentation de service de transaction sous-"
+"jacente. Comme pour <interfacename>UserTransaction</interfacename> un "
+"<interfacename>TransactionManager</interfacename> ne représente pas une "
+"transaction en particulier, mais est plutôt responsable d'offrir l'accès à "
+"un contexte de transaction implicite per-thread."
+
+#. Tag: para
+#: The_XTS_API.xml:97
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific transaction. In "
+"order to do this it is necessary to disassociate the thread from any "
+"transactions. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the transaction. The "
+"thread is then no longer associated with any transaction."
+msgstr ""
+"Un thread de contrôle peut exiger de passer par des périodes de non-"
+"transactionalité pour pouvoir effectuer du travail qui n'est pas associé à "
+"une transaction en particulier. Pour cela, il est nécessaire de dissocier le "
+"thread de toute transaction. La méthode 'suspend' le réalise, en retournant "
+"une instance <code>TxContext</code>, qui est un descripteur de la "
+"transaction. Le thread n'est plus alors associé à aucune transaction."
+
+#. Tag: para
+#: The_XTS_API.xml:100
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with a transaction(s) via its <code>TxContext</code>. Prior to "
+"association, the thread is disassociated with any transaction(s) with which "
+"it may be currently associated. If the <code>TxContext</code> is null, then "
+"the thread is associated with no transaction. The "
+"<code>UnknownTransactionException</code> exception is thrown if the "
+"transaction that the <code>TxContext</code> refers to is invalid in the "
+"scope of the invoking thread."
+msgstr ""
+"La méthode <methodname>resume</methodname> peut être utilisée pour (re-) "
+"associer un thread à une(des) transaction(s) via son <code>TxContext</code>. "
+"Avant cette association, le thread était disassocié de toute(s) transaction"
+"(s) avec la(les)quelle(s) il pourrait être actuellement associé. L'exception "
+"<code>UnknownTransactionException</code> est lancée si la transaction à "
+"laquelle <code>TxContext</code> se réfère n'est pas valide à portée du "
+"thread invoquant."
+
+#. Tag: para
+#: The_XTS_API.xml:103
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current transaction, or null if there is "
+"none. Unlike suspend, this method does not disassociate the current thread "
+"from the transaction(s). This can be used to enable multiple threads to "
+"execute within the scope of the same transaction."
+msgstr ""
+"La méthode <methodname>currentTransaction</methodname> retourne "
+"<code>TxContext</code> pour la transaction courante, ou nil s'il n'y en a "
+"pas. A la différence de 'suspend', cette méthode ne dissocie pas le thread "
+"courant de la (des) transactions. Cela peut être utilisé pour permettre à "
+"des threads multiples d'exécuter dans la limite de la même transaction."
+
+#. Tag: para
+#: The_XTS_API.xml:106
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a transaction, the "
+"container or participant must use:"
+msgstr ""
+"Pour pouvoir inscrire les participants ou les faire résigner d'une "
+"transaction, le container ou le participant doit utiliser :"
+
+#. Tag: para
+#: The_XTS_API.xml:111
+#, no-c-format
+msgid ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"Volatile2PC protocol; a unique identifier for the participant is also "
+"required. If there is no transaction associated with the invoking thread "
+"then the <code>UnknownTransactionException</code> exception is thrown. If "
+"the coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: engage le participant "
+"spécifié dans la transaction en cours de façon à ce qu'il puisse participer "
+"au protocole Volatile2PC. Le participant a besoin d'un identifiant unique. "
+"S'il n'existe pas de transaction associée au thread invoquant, alors "
+"l'exception <code>UnknownTransactionException</code> est lancée. Si le "
+"coordinateur a déjà un participant enrôlé sous le même identifiant, alors "
+"<code>AlreadyRegisteredException</code> sera lancé. Si la transaction n'est "
+"pas dans un état qui permettent aux participants de s'enrôler (par exemple, "
+"s'il est en cours de terminaison) alors <code>WrongStateException</code> "
+"sera lancé."
+
+#. Tag: para
+#: The_XTS_API.xml:116
+#, no-c-format
+msgid ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"2PC protocol; a unique identifier for the participant is also required. If "
+"there is no transaction associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: engage le participant "
+"spécifié dans la transaction en cours de façon à ce qu'il puisse participer "
+"au protocole 2PC. Le participant a besoin d'un identifiant unique. S'il "
+"n'existe pas de transaction associée au thread invoquant, alors l'exception "
+"<code>UnknownTransactionException</code> est lancée. Si le coordinateur a "
+"déjà un participant enrôlé sous le même identifiant, alors "
+"<code>AlreadyRegisteredException</code> sera lancé. Si la transaction n'est "
+"pas dans un état qui permette aux participants de s'enrôler (par exemple, "
+"s'il se termine) alors <code>WrongStateException</code> sera lancé."
+
+#. Tag: title
+#: The_XTS_API.xml:122
+#, no-c-format
+msgid "TransactionFactory"
+msgstr "TransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+"TransactionManagers sont obtenus à partir de <code>TransactionFactory</code>."
+
+#. Tag: title
+#: The_XTS_API.xml:130
+#, no-c-format
+msgid "API for the Business Activity protocol"
+msgstr "API pour le protocole BA (Business activité / activité commerciale)"
+
+#. Tag: title
+#: The_XTS_API.xml:132
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr "UserBusinessActivity"
+
+#. Tag: para
+#: The_XTS_API.xml:133
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserBusinessActivity</classname> is the class "
+"that most users (for example, clients and services) will see. This isolates "
+"them from the underlying protocol-specific aspects of the XTS "
+"implementation. Importantly, a <code>UserBusinessActivity</code> does not "
+"represent a specific business activity, but rather is responsible for "
+"providing access to an implicit per-thread activity. Therefore, all of the "
+"<code>UserBusinessActivity</code> methods implicitly act on the current "
+"thread of control."
+msgstr ""
+"La classe <classname>com.arjuna.wst.UserBusinessActivity</classname> est la "
+"classe que la plupart des utilisateurs (par exemple, les clients et les "
+"services) verront. Cela les isole des aspects spécifiques-protocole de "
+"l'implémentation XTS sous-jacente. Surtout, un <code>UserBusinessActivity</"
+"code> ne représente pas une activité commerciale en particulier, mais est "
+"plutôt responsable de fournir l'accès à une activité par-thread implicite. "
+"Ainsi, toutes les méthodes <code>UserBusinessActivity</code> agissent "
+"implicitement sur le thread de contrôle actuel. "
+
+#. Tag: para
+#: The_XTS_API.xml:137
+#, no-c-format
+msgid ""
+"A new business activity is begun and associated with the invoking thread by "
+"using the begin method. If there is already an activity associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created activity with the "
+"current thread."
+msgstr ""
+"On commence une transaction et on l'associe à un thread invoquant par la "
+"méthode 'begin'. S'il existe déjà une transaction associée au thread, alors "
+"l'exception <code>WrongStateException</code> est lancée. Si cela fonctionne, "
+"cette opération associe la transaction nouvellement créée au thread actuel."
+
+#. Tag: para
+#: The_XTS_API.xml:140
+#, no-c-format
+msgid ""
+"The business activity is completed successfully by the close method. This "
+"will execute the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol prior to returning. If there is no activity associated with the "
+"invoking thread then <code>UnknownTransactionException</code> is thrown. If "
+"the activity ultimately cancels then the "
+"<code>TransactionRolledBackException</code> is thrown. When complete, this "
+"operation disassociates the business activity from the current thread such "
+"that it becomes associated with no activity."
+msgstr ""
+"L'activité commerciale se termine avec succès en utilisant la méthode "
+"'close'. Cela permettra d'exécuter le protocole "
+"<code>BusinessAgreementWithParticipantCompletion</code> avant de retourner. "
+"S'il n'existe pas d'activité associée au thread invoquant, alors "
+"<code>UnknownTransactionException</code> est lancée. Si l'activité est "
+"finalement annulée, alors <code>TransactionRolledBackException</code> est "
+"annulé. Une fois terminée, cette opération dissocie l'activité commerciale "
+"du thread courant de façon à ce qu'il ne soit plus associé à aucune activité."
+
+#. Tag: para
+#: The_XTS_API.xml:143
+#, no-c-format
+msgid ""
+"The cancel operation will terminate the business activity and return "
+"normally if it succeeded, while throwing an appropriate exception if it "
+"didn’t. If there is no activity associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. Any participants that "
+"had previously completed will be informed to compensate for their work."
+msgstr ""
+"L'opération d'annulation terminera l'activité commerciale et retournera "
+"normalement en cas de succès, tout en lançant l'exception qui convient en "
+"cas d'échec. S'il n'y a aucune activité d'associée au thread invoquant, "
+"alors <code>UnknownTransactionException</code> sera lancé. Tout participant "
+"qui aurait déjà terminé, sera informé de compenser pour leur travail."
+
+#. Tag: para
+#: The_XTS_API.xml:146
+#, no-c-format
+msgid ""
+"Some participants may have registered for the "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol, which "
+"requires the coordinator or application to inform them when all work that "
+"they need to do within the scope of a business activity has been performed. "
+"The application should therefore use the complete method to inform these "
+"participants."
+msgstr ""
+"Certains participants ont pu s'enregistrer dans le protocole "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>, qui requiert que le "
+"coordinateur ou l'application les informent quand tout le travail nécessaire "
+"a été effectué dans la limite de l'activité commerciale. L'application "
+"devrait donc utiliser la méthode complète pour informer ces participants."
+
+#. Tag: title
+#: The_XTS_API.xml:150
+#, no-c-format
+msgid "UserBusinessActivityFactory"
+msgstr "UserBusinessActivityFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+"UserBusinessActivities sont obtenus à partir de "
+"<code>UserBusinessActivityFactory</code>."
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr "BusinessActivityManager"
+
+#. Tag: para
+#: The_XTS_API.xml:157
+#, no-c-format
+msgid ""
+"The <interfacename>BusinessActivityManager</interfacename> interface "
+"represents the service/container/participant’s (service-side users) typical "
+"way in which to interact with the underlying business activity service "
+"implementation. As with <interfacename>UserBusinessActivity</interfacename> "
+"a <interfacename>BusinessActivityManager</interfacename> does not represent "
+"a specific activity, but rather is responsible for providing access to an "
+"implicit per-thread activity."
+msgstr ""
+"L'interface <interfacename>BusinessActivityManager</interfacename> "
+"représente la façon typique dont le service/container/participant "
+"(utilisateurs côté-services) interacte avec l'implémentation de service de "
+"transaction sous-jacente. Comme pour <interfacename>UserBusinessActivity</"
+"interfacename> un <interfacename>BusinessActivityManager</interfacename> ne "
+"représente pas une transaction en particulier, mais plutôt, est responsable "
+"d'offrir l'accès à un contexte de transaction implicite per-thread."
+
+#. Tag: para
+#: The_XTS_API.xml:161
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific activity. In order "
+"to do this it is necessary to disassociate the thread from any business "
+"activities. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the activity. The "
+"thread is then no longer associated with any activity."
+msgstr ""
+"Un thread de contrôle peut exiger de passer par des périodes de non-"
+"transactionalité pour pouvoir effectuer du travail qui n'est pas associé à "
+"une activité en particulier. Pour cela, il est nécessaire de dissocier le "
+"thread de toute activité commerciale. La méthode 'suspend' le réalise, en "
+"retournant une instance <code>TxContext</code>, qui est un descripteur de "
+"l'activité. Le thread n'est plus alors associé à aucune activité."
+
+#. Tag: para
+#: The_XTS_API.xml:164
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with an activity (or activities) via its TxContext. Prior to "
+"association, the thread is disassociated with any activity with which it may "
+"be currently associated. If the <code>TxContext</code> is null, then the "
+"thread is associated with no activity. The "
+"<code>UnknownTransactionException</code> exception is thrown if the business "
+"activity that the TxContext refers to is invalid in the scope of the "
+"invoking thread."
+msgstr ""
+"La méthode <methodname>resume</methodname> peut être utilisée pour (re-)"
+"associer un thread à une activité (ou à des activités) via son TxContext. "
+"Avant toute association, le thread est dissocié de toute activité avec "
+"laquelle il pourrait être couramment associé. Si le  <code>TxContext</code> "
+"est nil, alors le thread n'est associé à aucune activité. L'exception "
+"<code>UnknownTransactionException</code> est lancée si l'activité "
+"commerciale à laquelle le TxContext se réfère est non valide dans la limite "
+"du thread invoqué."
+
+#. Tag: para
+#: The_XTS_API.xml:167
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current business activity, or null if there "
+"is none. Unlike suspend, this method does not disassociate the current "
+"thread from the activity. This can be used to enable multiple threads to "
+"execute within the scope of the same business activity."
+msgstr ""
+"La méthode <methodname>currentTransaction</methodname> retourne "
+"<code>TxContext</code> pour l'activité commerciale courante, ou nil s'il n'y "
+"en a pas. A la différence de 'suspend', cette méthode ne dissocie pas le "
+"thread courant de l'activité. Cela peut être utilisé pour permettre à des "
+"threads multiples d'exécuter dans la limite de la même activité commerciale."
+
+#. Tag: para
+#: The_XTS_API.xml:170
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a business activity, the "
+"container or participant must use:"
+msgstr ""
+"Pour pouvoir enrôler ou faire résigner des participants d'une activité "
+"commerciale, le container ou participant doit utiliser :"
+
+#. Tag: para
+#: The_XTS_API.xml:175
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"enlist the specified participant with current business activity such that it "
+"will participate in the <code>BusinessAgreementWithParticipantCompletion</"
+"code> protocol; a unique identifier for the participant is also required. If "
+"there is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"engage le participant spécifié dans l'activité commerciale en cours de façon "
+"à ce qu'il puisse participer au protocole "
+"<code>BusinessAgreementWithParticipantCompletion</code>. Le participant a "
+"besoin d'un identifiant unique. S'il n'existe pas d'activité commerciale "
+"associée au thread invoquant, alors l'exception "
+"<code>UnknownTransactionException</code> est lancée. Si le coordinateur a "
+"déjà un participant enrôlé sous le même identifiant, alors "
+"<code>AlreadyRegisteredException</code> sera lancé. Si la transaction n'est "
+"pas dans un état qui permette aux participants de s'enrôler (par exemple, "
+"s'il est en cours de terminaison) alors <code>WrongStateException</code> "
+"sera lancé."
+
+#. Tag: para
+#: The_XTS_API.xml:180
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"enlist the specified participant with current activity such that it will "
+"participate in the <code>BusinessAgreementWithCoordinatorCompletion</code> "
+"protocol; a unique identifier for the participant is also required. If there "
+"is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"engage le participant spécifié dans l'activité commerciale en cours de façon "
+"à ce qu'il puisse participer au protocole "
+"<code>BusinessAgreementWithParticipantCompletion</code>. Le participant a "
+"besoin d'un identifiant unique. S'il n'existe pas d'activité commerciale "
+"associée au thread invoquant, alors l'exception "
+"<code>UnknownTransactionException</code> est lancée. Si le coordinateur a "
+"déjà un participant enrôlé sous le même identifiant, alors "
+"<code>AlreadyRegisteredException</code> sera lancé. Si la transaction n'est "
+"pas dans un état qui permette aux participants de s'enrôler (par exemple, "
+"s'il est en cours de terminaison) alors <code>WrongStateException</code> "
+"sera lancé. "
+
+#. Tag: title
+#: The_XTS_API.xml:186
+#, no-c-format
+msgid "BusinessActivityManagerFactory"
+msgstr "BusinessActivityManagerFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
+"BusinessActivityManagers sont obtenus à partir de "
+"<code>BusinessActivityManagerFactory</code>."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactional_Web_Services.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactional_Web_Services.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactional_Web_Services.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,145 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr "Services Web transactionnels"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introduction"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:9
+#, no-c-format
+msgid ""
+"This chapter describes how to provide transactional support for new and "
+"existing Web services using the service-side facilities of XTS. It shows how "
+"new services can be made transactional with no additional programming, and "
+"how existing services can be made WS-T transaction-aware in a non-invasive "
+"fashion."
+msgstr ""
+"Ce chapitre décrit comment procurer un support transactionnel pour les "
+"services Web nouveaux ou existant, utilisant les possibilités de service "
+"XTS. Cela montre comment des nouveaux services peuvent être rendus "
+"transactionnels sans programmation supplémentaire, et comment des services "
+"existants peuvent être orientés-Transaction WS-T de manière non-invasive."
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr "Un service Web transactionnel"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:16
+#, no-c-format
+msgid ""
+"A Web service is a business-level entity. It encapsulates application logic "
+"needed to perform some domain-specific task, or is designed to delegate to a "
+"back-end system which executes that logic. Given it is part of application "
+"code, such non-functional requirements as transactionality should not "
+"impinge on its construction."
+msgstr ""
+"Un service Web est une entité niveau-business. Il représente une logique "
+"d'application nécessaire pour effectuer certaines tâches particulières-à-un-"
+"domaine, ou bien encore, est conçu pour être délégué à un système d'arrière-"
+"plan qui exécute cette logique. Comme il fait partie du code d'application, "
+"des exigences non-fonctionnelles, comme la transactionalité, ne devrait pas "
+"avoir d'effet négatif pour sa construction."
+
+#. Tag: para
+#: Transactional_Web_Services.xml:19
+#, no-c-format
+msgid ""
+"To support this notion, XTS provides a suite of components designed to work "
+"at the SOAP stack level, which deal with transactional matters on behalf of "
+"a Web service without requiring any changes to that service. In XTS two "
+"context handling components are registered with the SOAP server and deal "
+"with context management on behalf of the service without the service having "
+"to worry about context propagation issues itself. This is shown in the "
+"following figure."
+msgstr ""
+"Pour supporter cette notion, XTS fournit une suite de composants conçus pour "
+"travailler au niveau de la pile SOAP, qui s'occupe de problèmes "
+"transactionnels pour le compte d'un service Web, sans avoir besoin "
+"d'effectuer de changemente au niveau de ce service. Dans XTS, deux "
+"composants de gestion de contexte sont enregistrés dans le serveur SOAP et "
+"s'occupent de gestion de contexte pour le compte du service sans que le "
+"service ait à se préoccuper de propagation de contexte lui-même. Cela est "
+"expliqué dans le schéma suivant."
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr "Gestionnaires de contextes enregistrés dans le serveur SOAP"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:28
+#, no-c-format
+msgid ""
+"The detail of the context management that the context processor performs is "
+"unimportant to the Web service application logic, and is orthogonal to any "
+"work performed by any other protocol-specific context handlers too. However "
+"back-end systems which the Web service application logic uses (such as "
+"databases) are often interested in the front-end transaction context such "
+"that any operations invoked within its scope can be mapped onto a back-end "
+"transaction context. This is typically achieved at the back-end by wrapping "
+"a database driver in a veneer which implements both the interface of the "
+"original driver and hooks into the service-side API to access the "
+"transaction context details. The general architecture for this pattern is "
+"shown in the figure below."
+msgstr ""
+"Les détails du gestionnaire de contexte exécutés par le processeur de "
+"contexte ne sont pas très importants en termes de logique d'application du "
+"service Web, et sont orthogonaux à n'importe quel travail effectué par "
+"n'importe quel autre gestionnaire de contexte spécifique-protocole. "
+"Cependant, les systèmes d'arrière-plan utilisés par la logique de "
+"l'application service-Web (comme les bases de données), s'occupent le plus "
+"souvent des contextes de transactions frontales, de façon à ce que toute "
+"opération invoquée dans sa portée, peut être mappée dans un contexte de "
+"transaction en arrière-plan. C'est normalement réalisé en arrière-plan en "
+"enveloppant un pilote de base de donnée dans une sorte de placage qui "
+"implémente l'interface du pilote d'origine et qui s'attache l'API côté-"
+"service pour pouvoir accéder aux détails de contexte de transaction. "
+"L'architecture générale de ce modèle est exposé dans le schéma ci-dessous. "
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:35
+#, no-c-format
+msgid "General Pattern for Back-End Integration, Service Side"
+msgstr "Modèle général pour l'intégration Back-End, côté service"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:37
+#, no-c-format
+msgid ""
+"The missing element from this is the commit protocol which finally allows "
+"back-end work to be made durable or not at the end of a transaction. This is "
+"covered in the participant chapter where the participant/back-end relation "
+"is explored further."
+msgstr ""
+"L'élément manquant est le protocole de validation qui permet finalement que "
+"le travail d'arrière-plan soit durable ou pas en fin de transaction. C'est "
+"couvert dans le chapitre de participants qui explore un peu plus en détails "
+"la relation participant/back-end."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,917 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactions_Overview.xml:6
+#, no-c-format
+msgid "Transactions Overview"
+msgstr "Aperçu général des transactions"
+
+#. Tag: para
+#: Transactions_Overview.xml:7
+#, no-c-format
+msgid ""
+"Transactions have emerged as the dominant paradigm for coordinating "
+"interactions between parties in a distributed system, and in particular to "
+"manage applications that require concurrent access to shared data. Much of "
+"the JBossTS Web Service API is based on contemporary transaction APIs whose "
+"familiarity will enhance developer productivity and lessen the learning "
+"curve. While the following section provides the essential information that "
+"you should know before starting to use XTS for building transactional Web "
+"Services, it should not be treated as a definitive reference to all "
+"transactional technology."
+msgstr ""
+"Les transactions émergent en tant que paradigme dominant pour coordonner les "
+"interactions entre les parties dans un système distribué, et en particulier, "
+"pour gérer des applications qui ont besoin d'un accès concourant à des "
+"données partagées. Le service JBossTS Web Service API est basé sur des API "
+"de transactions contemporaines dont la familiarité permettra d'améliorer la "
+"productivité des développeurs et de réduire l'effort de formation. Tandis "
+"que la section suivante procure les informations principales que vous devez "
+"connaître avant de commencer d'utiliser XTS en vue de construire des "
+"Services Web transactionnels, vous ne devez pas pour autant considérer cette "
+"section comme une référence absolue sur la technologie transactionnelle."
+
+#. Tag: para
+#: Transactions_Overview.xml:10
+#, no-c-format
+msgid ""
+"A classic transaction is a unit of work that either completely succeeds, or "
+"fails with all partially completed work being undone. When a transaction is "
+"committed, all changes made by the associated requests are made durable, "
+"normally by committing the results of the work to a database. If a "
+"transaction should fail and is rolled back, all changes made by the "
+"associated work are undone. Transactions in distributed systems typically "
+"require the use of a transaction manager that is responsible for "
+"coordinating all of the participants that are part of the transaction."
+msgstr ""
+"Une transaction classique est une unité de travail qui, soit réussit "
+"complètement, soit échoue, avec une partie du travail réalisé qui se "
+"démantèle. Quand une transaction est validée, tous les changements effectués "
+"par les demandes associées, sont rendus durables, normalement grâce à la "
+"validation des résultats sur une base de données. Si une transaction échoue "
+"ou est rejetée, tous les changements effectués par le travail associé, sont "
+"démantelés. Les transactions en systèmes distribués requièrent normalement "
+"l'utilisation d'un gestionnaire de transactions, qui est responsable de "
+"coordonner tous les participants qui font partie d'une transaction."
+
+#. Tag: para
+#: Transactions_Overview.xml:13
+#, no-c-format
+msgid ""
+"The main components involved in using and defining transactional Web "
+"Services using XTS are illustrated in Figure 1."
+msgstr ""
+"Les principaux composants impliqués dans l'utilisation et la détermination "
+"des services transactionnels Web utilisant XTS, sont illustrés dans le "
+"Schéma 1."
+
+#. Tag: para
+#: Transactions_Overview.xml:18
+#, no-c-format
+msgid ""
+"A Transaction Service: The Transaction Service captures the model of the "
+"underlying transaction protocol and coordinates parties affiliated with the "
+"transaction according to that model."
+msgstr ""
+"Un service de transaction : le service de transaction enregistre le modèle "
+"du protocole de transaction sous-jacent et coordonne les parties affiliées à "
+"la transaction suivant ce modèle."
+
+#. Tag: para
+#: Transactions_Overview.xml:23
+#, no-c-format
+msgid ""
+"A Transaction API: Provides an interface for transaction demarcation and the "
+"registration of participants."
+msgstr ""
+"Un API de transaction : fournit une interface de démarcation de transaction "
+"et l'enregistrement des participants."
+
+#. Tag: para
+#: Transactions_Overview.xml:28
+#, no-c-format
+msgid ""
+"A Participant: The entity that cooperates with the transaction service on "
+"behalf of its associated business logic."
+msgstr ""
+"Un Participant : une entité qui coopère avec le service de transactions sur "
+"la base de sa logique commerciale associée."
+
+#. Tag: para
+#: Transactions_Overview.xml:33
+#, no-c-format
+msgid ""
+"The Context: Captures the necessary details of the transaction such that "
+"participants can enlist within its scope."
+msgstr ""
+"Le contexte : enregistre les détails utiles de la transaction de manière à "
+"ce que les participants puissent s'enlister dans sa portée."
+
+#. Tag: caption
+#: Transactions_Overview.xml:42
+#, no-c-format
+msgid "Web Services and XTS"
+msgstr "Services Web et XTS"
+
+#. Tag: title
+#: Transactions_Overview.xml:45
+#, no-c-format
+msgid "The Coordinator"
+msgstr "Le coordinateur"
+
+#. Tag: para
+#: Transactions_Overview.xml:46
+#, no-c-format
+msgid ""
+"Associated with every transaction is a coordinator, which is responsible for "
+"governing the outcome of the transaction. The coordinator may be implemented "
+"as a separate service or may be co-located with the user for improved "
+"performance. Each coordinator is created by the transaction manager service, "
+"which is in effect a factory for those coordinators."
+msgstr ""
+"Un coordinateur est associé à chaque transaction. Il est responsable de "
+"gérer le résultat de la transaction. Le coordinateur peut être implémenté en "
+"tant que service séparé ou peut être logé à côté de l'utilisateur pour une "
+"performance améliorée. Chaque coordinateur est créé par le service de "
+"gestion de transaction, qui est en fait, une usine pour ces coordinateurs."
+
+#. Tag: para
+#: Transactions_Overview.xml:50
+#, no-c-format
+msgid ""
+"A coordinator communicates with enrolled participants to inform them of the "
+"desired termination requirements, for instance, whether they should accept "
+"(for example, confirm) or reject (for example, cancel) the work done within "
+"the scope of the given transaction. For example, whether to purchase the "
+"(provisionally reserved) flight tickets for the user or to release them. An "
+"application/client may wish to terminate a transaction in a number of "
+"different ways (for example, confirm or cancel). However, although the "
+"coordinator will attempt to terminate in a manner consistent with that "
+"desired by the client, it is ultimately the interactions between the "
+"coordinator and the participants that will determine the actual final "
+"outcome."
+msgstr ""
+"Un coordinateur communique avec les participants enregistrés pour les "
+"informer des exigences de terminaison, par exemple, si ils doivent accepter "
+"(par exemple, confirmer) ou bien rejeter (par exemple, annuler) le travail "
+"entrepris dans la portée d'une transaction donnée. Par exemple, si on doit "
+"acheter le billet d'avion (réservé provisoirement pour le compte de "
+"l'utilisateur) ou si on doit le libérer. Une application/client souhaite "
+"peut-être faire aboutir une transaction d'un certain nombre de façons (comme "
+"confirmer ou annuler). Cependant, malgré que le coordinateur tentera de "
+"faire aboutir la transaction d'une manière consistante par rapport aux "
+"désirs du client, c'est finalement les interactions entre le coordinateur et "
+"les participants qui va déterminer le résultat final."
+
+#. Tag: para
+#: Transactions_Overview.xml:53
+#, no-c-format
+msgid ""
+"A transaction manager is typically responsible for managing coordinators for "
+"many transactions. The initiator of the transaction (for example, the "
+"client) communicates with a transaction manager and asks it to start a new "
+"transaction and associate a coordinator with the transaction. Once created, "
+"the context can be propagated to Web services in order for them to associate "
+"their work with the transaction."
+msgstr ""
+"Un gestionnaire de transactions est normalement responsable de gérer les "
+"coordinateurs pour plusieurs transactions. L'initiateur de la transaction "
+"(par exemple, le client) communique avec le gestionnaire de transactions et "
+"lui demande de démarrer une nouvelle transaction et de lui associer un "
+"coordinateur. Une fois créé, le contexte peut être propagé aux services Web "
+"pour qu'ils puissent associer leur travail à la transaction."
+
+#. Tag: title
+#: Transactions_Overview.xml:57
+#, no-c-format
+msgid "The Transaction Context"
+msgstr "Le contexte de transaction"
+
+#. Tag: para
+#: Transactions_Overview.xml:58
+#, no-c-format
+msgid ""
+"In order for a transaction to span a number of services, certain information "
+"has to be shared between those services in order to propagate information "
+"about the transaction. This information is known as the Context. Using XTS, "
+"the context is automatically propagated and processed by transaction-aware "
+"components of an application. Though XTS removes most of the work associated "
+"with propagating contexts, it is still instructive to understand what "
+"information is captured in a context:"
+msgstr ""
+"Pour qu'une transaction puisse s'étendre à un certain nombre de services, "
+"certaines informations doivent être partagées entre ces services pour "
+"pouvoir propager des informations sur la transaction. Cette information est "
+"connue en tant que Contexte. Utilisant XTS, le contexte est automatiquement "
+"propagé et traité par des composants orientés-transaction d'une application. "
+"Malgré que XTS retire la plupart du travail associé à la propagation des "
+"contextes, il est toujours instructif de comprendre quelle information est "
+"saisie dans un contexte donné."
+
+#. Tag: para
+#: Transactions_Overview.xml:64
+#, no-c-format
+msgid ""
+"A transaction identifier which guarantees global uniqueness for an "
+"individual transaction;"
+msgstr ""
+"Un identifiant de transaction qui garantit le caractère unique d'une "
+"transaction individuelle;"
+
+#. Tag: para
+#: Transactions_Overview.xml:69
+#, no-c-format
+msgid ""
+"The transaction coordinator location or endpoint address so participants can "
+"be enrolled."
+msgstr ""
+"La location du coordinateur de transactions ou l'adresse du point "
+"d'extrémité pour que les participants puissent s'enregistrer."
+
+#. Tag: caption
+#: Transactions_Overview.xml:78
+#, no-c-format
+msgid "Web Services and Context Flow"
+msgstr "Services Web et Flux contextuels"
+
+#. Tag: para
+#: Transactions_Overview.xml:80
+#, no-c-format
+msgid ""
+"As shown in Figure 2, whenever an application message is sent, the XTS "
+"Client API automatically creates a context and embeds it into the message. "
+"Similarly, any transaction-aware services are able to extract that context "
+"using the XTS service-side infrastructure and use it to perform work within "
+"the context of a particular transaction – even though that transaction was "
+"initiated elsewhere on the Web! The value of this approach is that the "
+"business logic contained within the client application and services are not "
+"peppered with transaction-processing code."
+msgstr ""
+"Comme le montre le schéma 2, quand un message d'application est envoyé, "
+"l'API client XTS crée automatiquement un contexte et l'intègre au message. "
+"De même, tout service orienté-transaction est capable d'extraire ce contexte "
+"en utilisant une infrastructure XTS côté-service et l'utiliser pour "
+"effectuer les tâches dans le contexte d'une transaction en particulier - "
+"même si cette transaction a été initiée à un autre endroit sur le Web! La "
+"valeur de cette approche est que les services et la logique commerciale "
+"contenue dans cette application ne soient pas parsemés de codes de "
+"traitement-de-transaction."
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr "Transactions ACID"
+
+#. Tag: para
+#: Transactions_Overview.xml:85
+#, no-c-format
+msgid ""
+"Traditionally, transaction processing systems support ACID properties. ACID "
+"is an acronym for Atomic, Consistent, Isolated, and Durable. A unit of work "
+"has traditionally been considered transactional only if the ACID properties "
+"are maintained:"
+msgstr ""
+"Traditionnellement, les systèmes de traitement de transaction prennent en "
+"charge les propriétés ACID. ACID est un acronyme pour Atomique, Consistant, "
+"Isolé et Durable. Une unité de travail est traditionnellement considérée "
+"transactionnelle si et seulement si les propriétés ACID sont conservées :"
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr "Atomicité : la transaction est exécutée complètement ou pas dutout."
+
+#. Tag: para
+#: Transactions_Overview.xml:96
+#, no-c-format
+msgid ""
+"Consistency: The effects of the transaction preserve the internal "
+"consistency of an underlying data structure."
+msgstr ""
+"Consistance : les effets de la transaction préservent l'homogénéité interne "
+"de la structure des données sous-jacentes."
+
+#. Tag: para
+#: Transactions_Overview.xml:101
+#, no-c-format
+msgid ""
+"Isolated: The transaction runs as if it were running alone with no other "
+"transactions running and is not visible to other transactions."
+msgstr ""
+"Isolée : la transaction est exécutée comme si elle était exécutée seule, "
+"sans aucune autre transaction en cours d'exécution et sans être visible par "
+"les autres transactions."
+
+#. Tag: para
+#: Transactions_Overview.xml:106
+#, no-c-format
+msgid ""
+"Durable: the transaction’s results will not be lost in the event of a "
+"failure."
+msgstr ""
+"Durable : les résultats de la transaction ne seront pas perdus en cas "
+"d'échec."
+
+#. Tag: title
+#: Transactions_Overview.xml:112
+#, no-c-format
+msgid "Two-Phase Commit"
+msgstr "Validation en deux-étapes"
+
+#. Tag: para
+#: Transactions_Overview.xml:113
+#, no-c-format
+msgid ""
+"The classical two-phase commit approach is the bedrock of JBossTS (and more "
+"generally of Web Services transactions). Two-phase commit provides "
+"coordination of parties that are involved in a transaction. In general, the "
+"flow of a two-phase commit transaction is as follows:"
+msgstr ""
+"L'approche de validation classique en deux phases est un aspect fondamental "
+"de JBossTS (et plus généralement des transaction Web Services). La "
+"validation en deux-phases fournit la coordination des parties qui sont "
+"impliquées dans la transaction. En général, le flux de la transation de "
+"validation en deux phases est comme suit :"
+
+#. Tag: para
+#: Transactions_Overview.xml:119
+#, no-c-format
+msgid "A transaction is started, and some work is performed."
+msgstr "Une transaction démarre et du travail est effectué."
+
+#. Tag: para
+#: Transactions_Overview.xml:124
+#, no-c-format
+msgid "Once the work is finished, the two-phase commit begins."
+msgstr ""
+"Une fois que le travail est achevé, le processus de validation en deux-"
+"phases débute."
+
+#. Tag: para
+#: Transactions_Overview.xml:129
+#, no-c-format
+msgid ""
+"The coordinator (transaction manager) of the transaction asks each resource "
+"taking part in the transaction whether it is prepared to commit."
+msgstr ""
+"Le coordinateur (gestionnaire de transactions) de la transaction demande à "
+"chaque ressource qui prend part à la transaction si elle est prêt à être "
+"validée."
+
+#. Tag: para
+#: Transactions_Overview.xml:134
+#, no-c-format
+msgid ""
+"If all resources respond positively, the coordinator instructs all work "
+"performed to be made durable (usually committed to a database)."
+msgstr ""
+"Si toutes les ressources répondent positivement, le coordinateur instruira "
+"que tout le travail achevé devra être durable (il sera normalement validé "
+"dans une base de données)."
+
+#. Tag: para
+#: Transactions_Overview.xml:139
+#, no-c-format
+msgid ""
+"If not, all work performed is rolled back (undone) such that the underlying "
+"data structures are in their original states."
+msgstr ""
+"Si non, tout le travail effectué sera rejeté (démantelé) de façon à ce que "
+"les structures de données sous-jacentes soient dans leurs états d'origine."
+
+#. Tag: caption
+#: Transactions_Overview.xml:148
+#, no-c-format
+msgid "The Two-Phase Commit Protocol"
+msgstr "Protocole de validation en deux-phases"
+
+#. Tag: para
+#: Transactions_Overview.xml:151
+#, no-c-format
+msgid ""
+"During two-phase commit transactions, coordinators and resources keep track "
+"of activity in non-volatile data stores so that they can recover in the case "
+"of a failure."
+msgstr ""
+"Pendant la procédure de validation en deux-temps, toutes les transactions, "
+"coordinateurs et ressources enregistrent un suivi des activités dans des "
+"mémoires non-volatiles de façon à ce qu'elles puissent être recouvrées en "
+"cas d'échec."
+
+#. Tag: title
+#: Transactions_Overview.xml:156
+#, no-c-format
+msgid "The synchronization protocol"
+msgstr "Le protocole de synchronisation"
+
+#. Tag: para
+#: Transactions_Overview.xml:157
+#, no-c-format
+msgid ""
+"As well as the two-phase commit protocol, traditional transaction processing "
+"systems employ an additional protocol, often referred to as the "
+"synchronization protocol. If you recall the original ACID properties, then "
+"you’ll remember that Durability is important in the case where state changes "
+"have to be available despite failures. What this means is that applications "
+"interact with a persistence store of some kind (e.g., a database) and this "
+"can impose a significant overhead – disk access is orders of magnitude "
+"slower than access to main computer memory."
+msgstr ""
+"Comme le protocole de validation en deux phases, les systèmes de traitement "
+"de transactions traditionnels utilisent un protocole supplémentaire, souvent "
+"connu sous le nom de protocole de synchronisation. Si vous vous souvenez des "
+"propriétés ACID d'origine, alors vous vous souviendrez que la Durabilité est "
+"importante dans le cas où les changements d'état sont rendus disponibles "
+"malgré les échecs. Cela signifie que les applications conversent avec un "
+"store persistant (comme une base de données) et que cela impose une "
+"surcharge importante - par ordre de magnitude, l'accès au disque est plus "
+"lent que l'accès à la mémoire de l'ordinateur principal."
+
+#. Tag: para
+#: Transactions_Overview.xml:161
+#, no-c-format
+msgid ""
+"One apparently obvious solution to this problem would be to cache the state "
+"in main memory and only operate on that for the duration of a transaction. "
+"Unfortunately you’d then need some way of being able to flush the state back "
+"to the persistent store before the transaction terminates, or risk losing "
+"the full ACID properties. This is what the synchronization protocol does, "
+"with Synchronization participants."
+msgstr ""
+"Une solution évidente apparemment à ce problème serait de cacher l'état dans "
+"la mémoire principale et n'opérer que la dessus pour la durée totale de la "
+"transaction. Malheureusement, vous aurez alors besoin de pouvoir évacuer "
+"l'état vers le store persistent avant la fin de la transaction, ou bien "
+"risquer de perdre toutes les propriétés ACID. C'est ce que le protocole de "
+"synchronisation peut faire, avec les participants à la synchronisation."
+
+#. Tag: para
+#: Transactions_Overview.xml:164
+#, no-c-format
+msgid ""
+"Synchronizations are informed that a transaction is about to commit, so they "
+"can, for example, flush cached state, which may be being used to improve "
+"performance of an application, to a durable representation prior to the "
+"transaction committing. They are then informed when the transaction has "
+"completed and in what state it completed."
+msgstr ""
+"Les synchronisations sont informées du fait qu'une transaction est sur le "
+"point d'être validée, donc elles peuvent, par exemple, évacuer l'état caché, "
+"qui pourrait être utilisé pour améliorer la performance d'une application, "
+"vers une représentation durable avant la validation de la transaction. Ils "
+"sont alors informés du fait que la transaction est terminée et dans quel "
+"état elle se termine."
+
+#. Tag: para
+#: Transactions_Overview.xml:169
+#, no-c-format
+msgid ""
+"Synchronizations essentially turn the two-phase commit protocol into a four-"
+"phase protocol:"
+msgstr ""
+"Les synchronisations transforment le protocole de validation en deux-phases "
+"en un protocole en quatre-phases :"
+
+#. Tag: para
+#: Transactions_Overview.xml:174
+#, no-c-format
+msgid ""
+"Before the transaction starts the two-phase commit, all registered "
+"Synchronizations are informed. Any failure at this point will cause the "
+"transaction to roll back."
+msgstr ""
+"Avant que la transaction ne commence le processus de validation en deux-"
+"phases, toutes les synchronisations enregistrées en sont informées. Tout "
+"échec à ce point entraînera le rejet de la transaction."
+
+#. Tag: para
+#: Transactions_Overview.xml:179
+#, no-c-format
+msgid "The coordinator then conducts the normal two-phase commit protocol."
+msgstr ""
+"Le coordinateur conduit alors le protocole de validation en deux phases."
+
+#. Tag: para
+#: Transactions_Overview.xml:184
+#, no-c-format
+msgid ""
+"Once the transaction has terminated, all registered Synchronizations are "
+"informed. However, this is a courtesy invocation because any failures at "
+"this stage are ignored: the transaction has terminated so there’s nothing to "
+"affect."
+msgstr ""
+"Une fois que la transaction est terminée, toutes les synchronisations "
+"enregistrées en sont informées. Cependant, il s'agit d'une invocation de "
+"courtoisie, car tout échec à ce niveau là sera ignoré : la transaction se "
+"termine donc il n'y a rien à affecter."
+
+#. Tag: para
+#: Transactions_Overview.xml:189
+#, no-c-format
+msgid ""
+"Unlike the two-phase commit protocol, the synchronization protocol does not "
+"have the same failure requirements. For example, Synchronization "
+"participants don’t need to make sure they can recover in the event of "
+"failures; this is because any failure before the two-phase commit protocol "
+"completes means the transaction will roll back, and failures after it has "
+"completed can’t affect the data the Synchronization participants were "
+"managing."
+msgstr ""
+"A la différence du protocole de validation en deux-étapes, le protocole de "
+"synchronisation ne possède pas les mêmes prérequis en cas d'échec. Ainsi, "
+"les participants à la synchronisation n'ont pas besoin de s'assurer qu'ils "
+"puissent recouvrir en cas d'échecs. En effet, tout échec qui survient avant "
+"que le protocole de validation en deux phases se termine entraîne le rejet "
+"de la transaction, et les échecs qui ont lieu après complétion, ne peuvent "
+"affecter les données que géraient les participants à la synchronisation."
+
+#. Tag: title
+#: Transactions_Overview.xml:193
+#, no-c-format
+msgid "Optimizations to the protocol"
+msgstr "Optimisations au protocole"
+
+#. Tag: para
+#: Transactions_Overview.xml:194
+#, no-c-format
+msgid ""
+"There are several variants to the standard two-phase commit protocol that "
+"are worth knowing about because they can have an impact on performance and "
+"failure recovery. We shall briefly describe those that are the most common "
+"variants on the protocol:"
+msgstr ""
+"Il existe plusieurs variantes au protocole de validation en deux phases qui "
+"sont utiles de connaître car elles peuvent avoir un impact sur la "
+"performance et le recouvremente en cas d'échec. Nous pouvons décrire "
+"rapidement celles qui sont les plus courantes sur le protocole :"
+
+#. Tag: para
+#: Transactions_Overview.xml:200
+#, no-c-format
+msgid ""
+"Presumed abort: if a transaction is going to roll back then it may simply "
+"record this information locally and tell all enlisted participants. Failure "
+"to contact a participant has no affect on the transaction outcome; the "
+"transaction is effectively informing participants as a courtesy. Once all "
+"participants have been contacted the information about the transaction can "
+"be removed. If a subsequent request for the status of the transaction occurs "
+"there will be no information available and the requestor can assume that the "
+"transaction has aborted (rolled back). This optimization has the benefit "
+"that no information about participants need be made persistent until the "
+"transaction has decided to commit (i.e., progressed to the end of the "
+"prepare phase), since any failure prior to this point will be assumed to be "
+"an abort of the transaction."
+msgstr ""
+"Annulation présumée : si une transaction doit être rejetée, alors "
+"l'information sera simplement enregistrée localement et tous les "
+"participants enregistrés seront informés. Tout manquement à appeler un "
+"participant n'a aucun effet sur le résultat de la transaction. Une fois que "
+"tous les participants auront été contactés, on peut supprimer l'information "
+"concernant la transaction. Si une demande suivante survient à propos du "
+"statut de la transaction, il n'y aura pas d'information disponible et le "
+"demandeur peut alors assumer que la transaction a été annulée (rejetée). "
+"Cette optimisation a pour avantage qu'aucune information à propos des "
+"participants n'a besoin d'être rendue persistante jusqu'à ce que la "
+"transaction ait décidé d'être validée (c'est à dire qu'elle ait progressé "
+"jusqu'au bout de la phase 'prepare'), puisque tout échec ayant lieu avant ce "
+"point précis sera considéré comme une annulation de la transaction."
+
+#. Tag: para
+#: Transactions_Overview.xml:205
+#, no-c-format
+msgid ""
+"One-phase: if there is only a single participant involved in the "
+"transaction, the coordinator need not drive it through the prepare phase. "
+"Thus, the participant will simply be told to commit and the coordinator need "
+"not record information about the decision since the outcome of the "
+"transaction is solely down to the participant."
+msgstr ""
+"Une-étape : s'il n'y a qu'un seul participant impliqué dans la transaction, "
+"le coordinateur aura besoin de la mener dans la phase 'prepare'. Ainsi, le "
+"participant devra simplement valider et le coordinateur n'aura pas besoin "
+"d'enregistrer l'information sur la décision puisque le résultat de la "
+"transaction est uniquement du ressort du participant."
+
+#. Tag: para
+#: Transactions_Overview.xml:210
+#, no-c-format
+msgid ""
+"Read-only: when a participant is asked to prepare, it can indicate to the "
+"coordinator that no information or data that it controls has been modified "
+"during the transaction. Such a participant does not need to be informed "
+"about the outcome of the transaction since the fate of the participant has "
+"no affect on the transaction. As such, a read-only participant can be "
+"omitted from the second phase of the commit protocol."
+msgstr ""
+"Lecture-seule : quand on demande à un participant de 'préparer', il peut "
+"indiquer au coordinateur qu'aucune information qu'il contrôle n'a été "
+"modifiée pendant la transaction. Un tel participant n'aura pas besoin d'être "
+"informé du résultat de la transaction puisque l'avenir d'un participant n'a "
+"pas d'effet sur la transaction. Ainsi, un participant lecture-seule peut "
+"être oublié en cours de la deuxième étape du protocole de validation."
+
+#. Tag: title
+#: Transactions_Overview.xml:216
+#, no-c-format
+msgid "Non-atomic transactions and heuristic outcomes"
+msgstr "Les transaction non-atomiques et les résultats heuristiques"
+
+#. Tag: para
+#: Transactions_Overview.xml:217
+#, no-c-format
+msgid ""
+"In order to guarantee atomicity, the two-phase commit protocol is "
+"necessarily blocking. What this means is that as a result of failures, "
+"participants may remain blocked for an indefinite period of time even if "
+"failure recovery mechanisms exist. Some applications and participants simply "
+"cannot tolerate this blocking."
+msgstr ""
+"Pour pouvoir garantir l'atomicité, le protocole de validation en deux phases "
+"bloque forcément. Ce que cela signifie, c'est que suite aux échecs, les "
+"participants peuvent rester bloqués pour une période de temps indéfinie même "
+"si les mécanisemes de recouvrement sont en place. Certaines applications et "
+"participants ne peuvent simplement pas tolérer ce blocage."
+
+#. Tag: para
+#: Transactions_Overview.xml:221
+#, no-c-format
+msgid ""
+"To break this blocking nature, participants that have got past the prepare "
+"phase are allowed to make autonomous decisions as to whether they commit or "
+"rollback: such a participant must record this decision in case it is "
+"eventually contacted to complete the original transaction. If the "
+"coordinator eventually informs the participant of the transaction outcome "
+"and it is the same as the choice the participant made, then there’s no "
+"problem. However, if it is contrary, then a non-atomic outcome has obviously "
+"happened: a heuristic outcome."
+msgstr ""
+"Pour passer outre ce problème de blocage, les participants qui ont dépassé "
+"l'étape 'prepare' sont autorisés à prendre des décisions autonomes à propos "
+"de la validation ou du rejet : un tel participant doit enregistrer cette "
+"décision au cas où serait contacté pour terminer la transaction d'origine. "
+"Si le coordinateur informe éventuellement le participant du résultat de la "
+"transaction et que c'est le même choix que celui du participant, alors il "
+"n'y a pas de problème. Mais, si c'est le contraire, alors on a un résultat "
+"non-atomique : un résultat heuristique."
+
+#. Tag: para
+#: Transactions_Overview.xml:224
+#, no-c-format
+msgid ""
+"How this heuristic outcome is reported to the application and resolved is "
+"usually the domain of complex, manually driven system administration tools, "
+"since in order to attempt an automatic resolution requires semantic "
+"information about the nature of participants involved in the transactions."
+msgstr ""
+"La façon dont un résultat heuristique est résolu et rapporté à l'application "
+"est normalement du ressort d'outils d'administration de systèmes complexes, "
+"opérés manuellement, puisque pour obtenir une résolution automatique, on "
+"aura besoin d'informations sémantiques sur la nature des participants "
+"impliqués dans les transactions."
+
+#. Tag: para
+#: Transactions_Overview.xml:227
+#, no-c-format
+msgid ""
+"Precisely when a participant makes a heuristic decision is obviously "
+"implementation dependant. Likewise, the choice the participant makes (to "
+"commit or to roll back) will depend upon the implementation and possibly the "
+"application/environment in which it finds itself. The possible heuristic "
+"outcomes are:"
+msgstr ""
+"Plus précisément, quand un participant prend une décision heuristique, il "
+"est évidemment dépendant de l'implémentation. De même, le choix d'un "
+"participant (validation ou rejet) dépend de l'implémentation et peut-être "
+"aussi de l'application ou de l'environnement dans laquelle/lequel il se "
+"trouve. Les résultats heuristiques possibles sont les suivants :"
+
+#. Tag: para
+#: Transactions_Overview.xml:232
+#, no-c-format
+msgid ""
+"Heuristic rollback: the commit operation failed because some or all of the "
+"participants unilaterally rolled back the transaction."
+msgstr ""
+"Rejet heuristique : l'opération de validation échoue car certains des "
+"participants ou tous les participants rejettent unilatéralement la "
+"transaction."
+
+#. Tag: para
+#: Transactions_Overview.xml:237
+#, no-c-format
+msgid ""
+"Heuristic commit: an attempted rollback operation failed because all of the "
+"participants unilaterally committed. This may happen if, for example, the "
+"coordinator was able to successfully prepare the transaction but then "
+"decided to roll it back (for example, it could not update its log) but in "
+"the meanwhile the participants decided to commit."
+msgstr ""
+"Validation heuristique : une tentative d'opération de rejet a échoué car "
+"tous les participants ont validé unilatéralement. Cela peut survenir, par "
+"exemple, si le coordinateur était en mesure de préparer la transaction mais "
+"décide de la rejeter (par exemple, il ne parvient pas à mettre à jour son "
+"log) mais que pendant ce temps là, les participants décident de valider."
+
+#. Tag: para
+#: Transactions_Overview.xml:242
+#, no-c-format
+msgid ""
+"Heuristic mixed: some updates (participants) were committed while others "
+"were rolled back."
+msgstr ""
+"Mélange d'heuristiques : certaines mises à jour (de participants) ont été "
+"validées alors que d'autres ont été rejetées."
+
+#. Tag: para
+#: Transactions_Overview.xml:247
+#, no-c-format
+msgid ""
+"Heuristic hazard: the disposition of some of the updates is unknown. For "
+"those which are known, they have either all been committed or all rolled "
+"back."
+msgstr ""
+"Danger heuristique : l'utilisation de certaines mises à jour n'est pas bien "
+"connue. Pour celles qui sont connues, elles ont été soit validées, soit "
+"rejetées."
+
+#. Tag: para
+#: Transactions_Overview.xml:252
+#, no-c-format
+msgid ""
+"Heuristic decisions should be used with care and only in exceptional "
+"circumstances since there is the possibility that the decision will differ "
+"from that determined by the transaction service and will thus lead to a loss "
+"of integrity in the system. Having to perform resolution of heuristics is "
+"something you should try to avoid, either by working with services/"
+"participants that don’t cause heuristics, or by using a transaction service "
+"that provides assistance in the resolution process."
+msgstr ""
+"Les décisions heuristiques devraient être utilisées avec attention et "
+"uniquement dans certaines circonstances puisqu'il y a possibilité que la "
+"décision soit différée de celle déterminée par le service de la transaction "
+"et mènerait à une perte d'intégrité dans le système. La résolution "
+"d'heuristiques est quelquechose que vous devriez essayer d'éviter, soit en "
+"évitant de travailler avec des services/participants qui ne causent pas "
+"d'heuristiques, soit en utilisant un service de transactions qui fournisse "
+"son assistance dans le processus de résolution."
+
+#. Tag: title
+#: Transactions_Overview.xml:256
+#, no-c-format
+msgid "A New Transaction Protocol"
+msgstr "Un nouveau protocole de transaction"
+
+#. Tag: para
+#: Transactions_Overview.xml:257
+#, no-c-format
+msgid ""
+"Many component technologies offer mechanisms for coordinating ACID "
+"transactions based on two-phase commit semantics (i.e., CORBA/OTS, JTS/JTA, "
+"MTS/MSDTC). ACID transactions are not suitable for all Web services "
+"transactions since:"
+msgstr ""
+"De nombreuses technologies de composants proposent des mécanismes pour "
+"coordonner les transactions ACID basées sur les sémantique de validation en "
+"deux-phases (c'est à dire, CORBA/OTS, JTS/JTA, MTS/MSDTC). Les transactions "
+"ACID ne sont pas adaptées à toutes les transactions de services Web car :"
+
+#. Tag: para
+#: Transactions_Overview.xml:263
+#, no-c-format
+msgid ""
+"Classic ACID transactions are predicated on the idea that an organization "
+"that develops and deploys applications does so using their own "
+"infrastructure, typically an Intranet. Ownership meant transactions operated "
+"in a trusted and predictable manner. To assure ACIDity, potentially long-"
+"lived locks could be kept on underlying data structures during two-phase "
+"commit. Resources could be used for any period of time and released when the "
+"transaction was complete. In the Web services arena, these assumptions are "
+"no longer valid. One obvious reason is that the owners of data exposed "
+"through a Web service will refuse to allow their data to be locked for "
+"extended periods since to allow such locks invites denial-of-service."
+msgstr ""
+"Les transactions ACID classiques découlent de l'idée qu'une organisation qui "
+"développe ou qui déploie des applications et le fait en utilisant ses "
+"propres infrastructures, normalement l'internet. Les sens de propriété "
+"venait du fait que les transactions étaient effectuées avec confiance et de "
+"façon prévisible. Pour garantir l'ACIDity, les verrous présumées de longue-"
+"vie pourraient être conservés sous les structures de données sous-jacentes "
+"au cours de la phase de validation en deux-étapes. Les ressources pouvaient "
+"être utilisées pour n'importe quelle durée et pouvaient être libérées quand "
+"la transaction était terminée. Dans la sphère des services Web, ces "
+"assomptions ne sont plus valides. Une raison principale est que les "
+"propriétaires de données exposées par un service Web, refuseront que leurs "
+"données soient verrouillées pour de longues durées puisqu'une telle "
+"permission entraîne le refus-de-service."
+
+#. Tag: para
+#: Transactions_Overview.xml:268
+#, no-c-format
+msgid ""
+"All application infrastructures are generally owned by a single party, "
+"systems using classical ACID transactions normally assume that participants "
+"in a transaction will obey the will of the transaction manager and only "
+"infrequently decide to make unilateral decisions which will hamper other "
+"participants in a transaction. On the contrary, Web services participating "
+"in a transaction can effectively decide to resign from the transaction at "
+"any time, and the consumer of the service generally has little in the way of "
+"quality of service guarantees to prevent this."
+msgstr ""
+"Toutes les infrastructures appartiennent généralement à une seule partie. "
+"Les systèmes utilisant des transactions ACID classiques assument normalement "
+"que les participants à une transaction suivront le bon vouloir du "
+"gestionnaire de transaction et ne décideront que rarement de prendre des "
+"décisions unilatérales qui retarderont les autres participants dans la "
+"transaction. Au contraire, les services Web participant à une transaction "
+"peuvent effectivement décider de quitter une transaction à tout moment, et "
+"le consommateur du service ne possède généralement guère les moyens, en "
+"terme de garanties de qualité de service, de l'en empêcher."
+
+#. Tag: title
+#: Transactions_Overview.xml:274
+#, no-c-format
+msgid "Adressing the Problems of Transactioning in Loosely Coupled Systems"
+msgstr ""
+"Adressant les problèmes de transaction dans les systèmes informellement "
+"couplés (Loosely Coupled Systems)."
+
+#. Tag: para
+#: Transactions_Overview.xml:275
+#, no-c-format
+msgid ""
+"Though extended transaction models which relax the ACID properties have been "
+"proposed over the years, to implement these concepts for the Web services "
+"architecture WS-T provides a new transaction protocol. XTS is designed to "
+"accommodate four underlying requirements inherent in any loosely coupled "
+"architecture like Web services:"
+msgstr ""
+"Malgré que les modèles de transactions prolongées qui relaxent les "
+"propriétés ACID aient été proposées depuis plusieurs années, pour "
+"implémenter ces concepts pour l'architecture de services Web, WS-T propose "
+"un nouveau protocole de transaction. XTS est conçu pour accommoder quatre "
+"prérequis sous-jacents inhérents à n'importe quel service Web d'architecture "
+"comparable informellement couplé :"
+
+#. Tag: para
+#: Transactions_Overview.xml:281
+#, no-c-format
+msgid ""
+"Ability to handle multiple successful outcomes to a transaction, with the "
+"ability to involve operations whose effects may not be isolated or durable;"
+msgstr ""
+"Capacité à gérer des résultats multiples pour une transaction, avec la "
+"capacité d'impliquer des opérations dont les effets ne sont peut-être pas "
+"isolés ou durables;"
+
+#. Tag: para
+#: Transactions_Overview.xml:286
+#, no-c-format
+msgid ""
+"Coordination of autonomous parties whose relationships are governed by "
+"contracts rather than the dictates of a central design authority;"
+msgstr ""
+"Coordination de parties autonomes dont les relations sont gouvernées par des "
+"contrats plutôt que par le dictât d'une autorité conceptuelle centrale;"
+
+#. Tag: para
+#: Transactions_Overview.xml:291
+#, no-c-format
+msgid ""
+"Discontinuous service, where parties are anticipated to suffer outages "
+"during their lifetime, and coordinated work must be able to survive such "
+"outages;"
+msgstr ""
+"Services discontinus, pour lesquelles les parties sont sensées souffrir "
+"d'interruptions au cours de leur durée de vie, le travail coordonné doit "
+"être en mesure de survivre à de telles interruptions;"
+
+#. Tag: para
+#: Transactions_Overview.xml:296
+#, no-c-format
+msgid ""
+"Interoperation using XML over multiple communication protocols – XTS chooses "
+"to use SOAP encoding carried over HTTP for the first release and other SOAP-"
+"friendly transports for future releases."
+msgstr ""
+"interopérations utilisant XML sur des protocoles multiples de communication "
+"- XTS choisit d'utiliser le codage SOAP transposé sur HTTP pour la première "
+"sortie de version et sur d'autres supports comptibles-SOAP pour les versions "
+"à venir."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/fr-FR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,1416 @@
+# translation of Stand-alone_Coordinator.po to French
+# Language fr-FR translations for  package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-12-16 09:18+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:6
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Overview"
+msgstr ""
+"Aperçu général des activités WS-C, Transactions WS-Atomic et WS-Business"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introduction"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:9
+#, no-c-format
+msgid ""
+"This section provides fundamental concepts associated with WS-C, WS-Atomic "
+"Transaction and WS-Business Activity. All of these concepts are defined in "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. WS-"
+"C, WS-Atomic Transaction and WS-Business Activity principles are discussed "
+"throughout this guide."
+msgstr ""
+"Cette section fournit des concepts fondamentaux associés aux activités WS-C, "
+"WS_Atomic Transaction, et WS-Business. Tous ces concepts sont définis dans "
+"les spécifications des activités WS-C, Transactions WS-Atomic et WS-"
+"Business. Les principes de WS-C, de WS-Atomic Transaction et de WS-Business "
+"sont expliqués dans ce guide."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:13
+#, no-c-format
+msgid ""
+"If you are well versed in the WS-C, WS-Atomic Transaction and WS-Business "
+"Activity specifications then you may want to just skim through this part of "
+"the manual."
+msgstr ""
+"Si vous êtes déjà bien familiers avec les spécifications de WS-C, de WS-"
+"Atomic Transaction et de WS-Business, vous pourrez sans doute passer cette "
+"partie du manuel."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr "WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:21
+#, no-c-format
+msgid ""
+"In general terms, coordination is the act of one entity (known as the "
+"coordinator) disseminating information to a number of participants for some "
+"domain-specific reason. This reason could be in order to reach consensus on "
+"a decision like in a distributed transaction protocol, or simply to "
+"guarantee that all participants obtain a specific message, as occurs in a "
+"reliable multicast environment. When parties are being coordinated, "
+"information known as the coordination context is propagated to tie together "
+"operations which are logically part of the same coordinated work or "
+"activity. This context information may flow with normal application "
+"messages, or may be an explicit part of a message exchange and is specific "
+"to the type of coordination being performed."
+msgstr ""
+"En général, la coordination est l'action d'une entité (connue en tant que "
+"coordinateur) qui distribue des informations à un certain nombre de "
+"participants pour une raison spécifique-domaine. Cette raison pourrait être "
+"en vue d'obtenir un consensus sur une décision telle qu'un protocole de "
+"transaction distribuée, ou simplement pour garantir que tous les "
+"participants obtiennent un message particulier, comme c'est le cas dans un "
+"environnement fiable en diffusion multiple. Quand les parties sont "
+"coordonnées, l'information connue sous le terme de contexte de coordination "
+"est propagée pour relier ensemble des opérations qui font logiquement partie "
+"du même ouvrage ou activité coordonnée. Cette information contextuelle peut "
+"faire partie des messages d'applications courants, ou pourrait faire partie "
+"explicite d'un échange de messages et être spécifique au type de "
+"coordination effectué."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:24
+#, no-c-format
+msgid ""
+"The fundamental idea underpinning WS-Coordination is that there is a generic "
+"need for a coordination infrastructure in a Web services environment. The WS-"
+"Coordination specification defines a framework that allows different "
+"coordination protocols to be plugged-in to coordinate work between clients, "
+"services and participants, as shown in Figure 4."
+msgstr ""
+"L'idée fondamentale sous la coordination-WS sous-jacente, c'est qu'il existe "
+"un besoin générique d'infrastructure de coordination pour un environnement "
+"de services Web. Les spécifications de WS-Coordination définissent une "
+"structure autorisant plusieurs protocoles de coordination à intégrer pour "
+"coordonner le travail entre les clients , les services et les participants, "
+"comme on peut l'observer sur le Schéma 4."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:27
+#, no-c-format
+msgid ""
+"At this level, an activity is minimally specified and is simply created, "
+"made to run, and then completed."
+msgstr ""
+"A ce niveau, une activité est spécifiée au minimum, et est simplement créée, "
+"conçue pour être opérationnelle, et aboutir."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:34
+#, no-c-format
+msgid "WS-C architecture"
+msgstr "WS-C architecture"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:36
+#, no-c-format
+msgid ""
+"Whatever coordination protocol is used, and in whatever domain it is "
+"deployed, the same generic requirements are present:"
+msgstr ""
+"Quel que soit le protocole de coordination utilisé, et quel que soit le "
+"domaine dans lequel a lieu son déploiement, les mêmes besoins génériques "
+"sont présents :"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:41
+#, no-c-format
+msgid ""
+"Instantiation (or activation) of a new coordinator for the specific "
+"coordination protocol, for a particular application instance;"
+msgstr ""
+"L'instanciation (ou l'activation) d'un nouveau coordinateur d'un protocole "
+"de coordination spécifique, pour une instance d'application particulière;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:46
+#, no-c-format
+msgid ""
+"Registration of participants with the coordinator, such that they will "
+"receive that coordinator’s protocol messages during (some part of) the "
+"application’s lifetime;"
+msgstr ""
+"Enregistrement des participants auprès du coordinateur, de telle façon qu'il "
+"recevront les messages du protocole du coordinateur pendant la durée de vie "
+"(ou une partie tout du moins) de l'application."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:51
+#, no-c-format
+msgid ""
+"Propagation of contextual information between Web services that comprise the "
+"application;"
+msgstr ""
+"Propogation d'information contextuelle entre les services Web qui font "
+"partie de l'application;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:56
+#, no-c-format
+msgid "An entity to drive the coordination protocol through to completion."
+msgstr ""
+"Une entité pour actionner le protocole de coordination à travers le "
+"processus."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:61
+#, no-c-format
+msgid ""
+"The first three of these points are directly the concern of WS-Coordination "
+"while the fourth is the responsibility of a third-party entity, usually the "
+"client application that controls the application as a whole. These four WS-"
+"Coordination roles and their interrelationships are shown in Figure 5."
+msgstr ""
+"Le premier point est directement lié à WS-Coordination alors que le "
+"quatrième est de la responsabilité d'une entité tierce, qui est d'habitude "
+"l'application du client qui contrôle l'application dans son ensemble. Ces "
+"quatre rôles WS Coordination et leurs interconnexions sont décrits dans le "
+"schéma 5."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr "Infrastructure WS-C"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:71
+#, no-c-format
+msgid "Activation"
+msgstr "Activation"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:72
+#, no-c-format
+msgid ""
+"The WS-Coordination framework exposes an Activation Service which supports "
+"the creation of coordinators for specific protocols and their associated "
+"contexts. The process of invoking an activation service is done "
+"asynchronously, and so the specification defines both the interface of the "
+"activation service itself, and that of the invoking service, so that the "
+"activation service can call back to deliver the results of the activation – "
+"namely a context that identifies the protocol type and coordinator location. "
+"These interfaces are presented in Figure 6, where the activation service has "
+"a one-way operation that expects to receive a "
+"<code>CreateCoordinationContext</code> message and correspondingly the "
+"service that sent the <code>CreateCoordinationContext</code> message expects "
+"to be called back with a <code>CreateCoordinationContextResponse</code> "
+"message, or informed of a problem via an <code>Error</code> message."
+msgstr ""
+"La structure WS-Coordination expose le service d'activation qui supporte la "
+"création de coordinateurs pour des protocoles particuliers et leurs "
+"contextes associés. Le processus d'invocation d'un service d'activation est "
+"effectué de façon asynchrone, et donc, la spécification définit l'interface "
+"du service d'activation lui-même sur celui du service invoquant, afin que le "
+"service d'activation puisse rappeler pour donner les résultats de "
+"l'activation - notamment un contexte qui identifie le type de protocole et "
+"la location de coordination. Ces interfaces sont présentées dans le schéma "
+"6, là où le service d'activation a une opération en sens unique qui attend "
+"un message <code>CreateCoordinationContext</code> et en parallèle, le "
+"service qui a envoyé le message <code>CreateCoordinationContext</code> "
+"s'attend à être rappelé par un message <code>CreateCoordinationContext</"
+"code>, ou à être informé d'un problème par l'intermédiaire d'un message "
+"<code>Error</code>."
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:76
+#, no-c-format
+msgid ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+msgstr ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:78
+#, no-c-format
+msgid "Registration"
+msgstr "Enregistrement"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:79
+#, no-c-format
+msgid ""
+"Once a coordinator has been instantiated and a corresponding context created "
+"by the activation service, a Registration Service is created and exposed. "
+"This service allows participants to register to receive protocol messages "
+"associated with a particular coordinator. Like the activation service, the "
+"registration service assumes asynchronous communication and so specifies "
+"WSDL for both registration service and registration requester, as shown "
+"below."
+msgstr ""
+"Une fois qu'un coordinateur a été instancié, et qu'un contexte correspondant "
+"a été créé par le service d'activation, un service d'enregistrement est créé "
+"et exposé. Ce service permet aux participants d'être enregistrés en vue de "
+"recevoir les messages de protocole associés à un coordinateur particulier. "
+"Comme le service d'activation, le service d'enregistrement assume une "
+"communication asynchrone et précise WSDL pour le service d'enregistrement et "
+"pour la demande d'enregistrement elle-même, comme démontré ci-dessous."
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:83
+#, no-c-format
+msgid ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+msgstr ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:84
+#, no-c-format
+msgid ""
+"When a participant is registered with a coordinator through the registration "
+"service, it receives messages that the coordinator sends (for example, "
+"“prepare to complete” and “complete” messages if a two-phase protocol is "
+"used); where the coordinator’s protocol supports it, participants can also "
+"send messages back to the coordinator."
+msgstr ""
+"Quand un participant est enregistré avec un coordinateur à travers le "
+"service d'enregistrement, il reçoit un message envoyé par le coordinateur "
+"(comme par exemple, \"prepare to complete\" (préparer à la réalisation) et "
+"\"complete\" (réaliser) dans le cas d'un protocole en deux phases). Quand le "
+"protocole du coordinateur le supporte, les participants peuvent également "
+"renvoyer des messsages au coordinateur."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:88
+#, no-c-format
+msgid "Completion"
+msgstr "Phase de réalisation "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:89
+#, no-c-format
+msgid ""
+"The role of terminator is generally played by the client application, which "
+"at an appropriate point will ask the coordinator to perform its particular "
+"coordination function with any registered participants – to drive the "
+"protocol through to its completion. On completion, the client application "
+"may be informed of an outcome for the activity which may vary from simple "
+"succeeded/failed notification through to complex structured data detailing "
+"the activity’s status."
+msgstr ""
+"Le rôle du terminateur est en général assumé par l'application du client, "
+"qui va demander au coordinateur, à un point précis, de procéder à sa "
+"fonction de coordination entre les participants enregistrés - pour acheminer "
+"le protocole vers sa complétion. Au moment de sa complétion, l'application "
+"du client pourra être informée d'un résultat qui peut varier entre une "
+"simple notification réussi/échoué et des données structurées complexes "
+"précisant le statut de l'activité."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:96
+#, no-c-format
+msgid "WS-Transaction"
+msgstr "WS-Transaction"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:97
+#, no-c-format
+msgid ""
+"In the past, making traditional transaction systems talk to one another was "
+"a holy grail that was rarely achieved. With the advent of Web services, "
+"there is an opportunity to leverage an unparalleled interoperability "
+"technology to splice together existing transaction processing systems that "
+"already form the backbone of enterprise level applications."
+msgstr ""
+"Dans le passé, faire parler des systèmes de transactions avec d'autres "
+"systèmes était une haute aspiration qui aboutissait rarement. Avec la venue "
+"des services Web, il existe une possibilité d'exploiter une technologie "
+"d'intéropérabilité sans parallèle pour raccorder ensemble des systèmes de "
+"traitement de transactions existantes qui forment déjà le support principal "
+"des applications au niveau entreprise."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:101
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr "Les fondations WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:102
+#, no-c-format
+msgid ""
+"An important aspect of WS-Transaction that differentiates it from "
+"traditional transaction protocols is that a synchronous request/response "
+"model is not assumed. This model derives from the fact that WS-Transaction "
+"is, as shown in the figure below, layered upon the WS-Coordination protocol "
+"whose own communication patterns are asynchronous by default."
+msgstr ""
+"Un aspect important de la transaction-WS qui la différencie des protocoles "
+"de transactions traditionnels est que le modèle synchronisé demande/réponse "
+"n'est pas assumé. Ce modèle dérive du fait que Transaction-WS est, comme "
+"montré dans le schéma ci-dessous, stratifié suivant le protocole WS-"
+"Coordinateur dont les modèles de communication sont asynchronisés par défaut."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:110
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr "WS-Coordination WS-Atomic Transaction et WS-Business Activity"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:112
+#, no-c-format
+msgid ""
+"Web Services Coordination provides a generic framework for specific "
+"coordination protocols, like WS-Transaction, to be plugged in. Recall that "
+"WS-Coordination provides only context management – it allows contexts to be "
+"created and activities to be registered with those contexts. WS-Transaction "
+"leverages the context management framework provided by WS-Coordination in "
+"two ways. Firstly it extends the WS-Coordination context to create a "
+"transaction context. Secondly, it augments the activation and registration "
+"services with a number of additional services (Completion, "
+"CompletionWithAck, PhaseZero, 2PC, OutcomeNotification, BusinessAgreement, "
+"and BusinessAgreementWithComplete) and two protocol message sets (one for "
+"each of the transaction models supported in WS-Transaction) to build a fully-"
+"fledged transaction coordinator on top the WS-Coordination protocol "
+"infrastructure."
+msgstr ""
+"Web Services Coordination fournit une structure générique pour des "
+"protocoles de coordination spécifiques, comme WS-Transaction, dans lesquels "
+"se connecter. Rappelez-vous bien que WS-Coordination ne fournit uniquement "
+"qu'un contexte de gestion - il permet aux contextes d'être créés et aux "
+"activités d'être enregistrées dans ces contextes. WS-Transaction exploite la "
+"structure de gestion de contexte fournie par WS-Coordination de deux façons. "
+"Tout d'abord, il propage le contexte de WS-Coordination en vue de créer un "
+"contexte de transaction. Deuxièmement, il augmente les services d'activation "
+"et d'enregistrement par un certain nombre de services supplémentaires "
+"(Completion, CompletionWithAck, PhaseZero, 2PC, OutcomeNotification, "
+"BusinessAgreement, and BusinessAgreementWithComplete) et de deux groupes de "
+"messages de protocole (un pour chacun des modèles de transaction pris en "
+"charge par WS-Transaction) pour construire un coordinateur de transaction au "
+"point par dessus l'infrastructure su protocole WS-Coordination."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:116
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr "Architecture WS-Transaction"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:117
+#, no-c-format
+msgid ""
+"WS-Transaction supports the notion of the service and participant as "
+"distinct roles, making the distinction between a transaction-aware service "
+"and the participants that act on behalf of the service during a transaction: "
+"transactional services deal with business-level protocols, while the "
+"participants handle the underlying WS-Transaction protocols, as shown above."
+msgstr ""
+"WS-Transaction supporte la notion de service et de participant comme des "
+"rôles séparés, faisant ainsi une claire distinction entre un service orienté-"
+"transaction et les participants qui agissent de la part du service en cours "
+"de transaction : les services transactionnels ont affaire à des protocoles "
+"niveau-business, alors que les participants ont affaire à des protocoles WS-"
+"Transaction sous-jacents, comme démontré ci-dessus."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:125
+#, no-c-format
+msgid "WS-Transaction Global View"
+msgstr "Vision d'ensemble de WS-Transaction"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:127
+#, no-c-format
+msgid ""
+"A transaction-aware service encapsulates the business logic or work that is "
+"required to be conducted within the scope of a transaction. This work cannot "
+"be confirmed by the application unless the transaction also commits and so "
+"control is ultimately removed from the application and placed into the "
+"transaction’s domain."
+msgstr ""
+"Un service orienté-transaction englobe la logique commerciale ou le travail "
+"nécessaire à effectuer dans le cadre d'une transaction. Ce travail ne peut "
+"pas être confirmé par une application à moins que la transaction ne soit "
+"validée également. Ainsi, on retire finalement le contrôle de l'application "
+"et il en ressort désormais du domaine de la transaction."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:130
+#, no-c-format
+msgid ""
+"The participant is the entity that, under the dictates of the transaction "
+"coordinator, controls the outcome of the work performed by the transaction-"
+"aware Web service. In the figure above each service is shown with one "
+"associated participant that manages the transaction protocol messages on "
+"behalf of its service, while in the figure below, there is a close-up view "
+"of a single service, and a client application with their associated "
+"participants."
+msgstr ""
+"Le participant est l'entité qui, sous les directives du coordinateur de la "
+"transaction, contrôle les aboutissants du travail effectué par le service "
+"Web orienté-transaction. Dans le schéma ci-dessus, chaque service est "
+"présenté avec un participant associé qui gère les messages de protocole de "
+"la transaction pour ses services, tandis que dans le schéma ci-dessous, on "
+"se concentre sur un seul service, et une application-client et ses "
+"participants associés."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:137
+#, no-c-format
+msgid "Transactional Service and Participant"
+msgstr "Service transactionnel et participant"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:139
+#, no-c-format
+msgid ""
+"The transaction-aware Web service and its participant both serve a shared "
+"transactional resource, and there is a control relationship between them "
+"through some API - which on the Java platform is JAXTX. In the example shown "
+"in the figure above, it is assumed that the database is accessed through a "
+"transactional JDBC database driver, where SQL statements are sent to the "
+"database for processing via that driver, but where those statements will be "
+"tentative and only commit if the transaction does. In order to do this, the "
+"driver/database will associate a participant with the transaction which will "
+"inform the database of the transaction outcome. Since all transactional "
+"invocations on the Web service carry a transaction context, the participant "
+"working with the database is able to identify the work that the "
+"transactional service did within the scope of a specific transaction and "
+"either commit or rollback the work."
+msgstr ""
+"Le service orienté-transaction et ses participants servent tous deux une "
+"ressource transactionnelle partagée, et il existe une relation de contrôle "
+"entre eux à travers l'API - qui est JAXTX sur la plateforme Java. Dans "
+"l'exemple du schéma ci-dessus, on assume que la base de données est "
+"accessible par le pilote de la base de données JDBC transactionnelle, où les "
+"énoncés SQL sont envoyés vers la base de données pour traitement par le "
+"pilote, mais où ces énoncés seront provisoires et ne seront validés que si "
+"la transaction fait de même. Pour cela, le pilote/base de données associera "
+"un participant à la transaction qui l'informera la base de données du "
+"résultat de la transaction. Comme toutes les invocations transactionnelles "
+"du service Web comportent un contexte de transaction, le participant qui "
+"travaille avec la base de données est capable d'identifier le travail "
+"effectué par le service transactionnel dans la limite d'une transaction "
+"particulière, puis, soit procède à la validation ou au rejet du travail."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:142
+#, no-c-format
+msgid ""
+"At the client end, things are less complex. Through its API, the client "
+"application registers a participant with the transaction through which it "
+"controls transaction termination."
+msgstr ""
+"Du côté client, les choses sont bien moins complexes. A travers les API, "
+"l'application client enregistre un participant dans la transaction à travers "
+"laquelle il contrôle la fin de la transaction."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:146
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr "Modèles de WS-Transaction"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:147
+#, no-c-format
+msgid ""
+"Given that traditional transaction models are not appropriate for Web "
+"services, the following question must be posed, “what type of model or "
+"protocol is appropriate?” The answer to that question is that that no one "
+"specific protocol is likely to be sufficient, given the wide range of "
+"situations that Web service transactions are likely to be deployed within. "
+"Hence the WS-Transaction specification proposes two distinct models, where "
+"each supports the semantics of a particular kind of B2B interaction. The "
+"following sections shall discuss these two WS-Transaction models."
+msgstr ""
+"Comme les modèles de transaction traditionnels ne sont pas appropriés pour "
+"les services Web, on doit se poser la question suivante, \"quel type de "
+"modèle ou de protocole est approprié ?\". La réponse à cette question est "
+"qu'aucun protocole en particulier n'est certainement suffisant, compte tenu "
+"du grand nombre de situations dans lesquelles les transactions de service "
+"Web sont susceptibles d'être déployées. Ainsi, la spécification WS-"
+"Transaction propose deux modèles distincts, qui supportent tous deux les "
+"sémantiques d'un genre d'interaction B2B particulière. Les sections "
+"suivantes discuteront ces deux modèles WS-Transaction."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:152
+#, no-c-format
+msgid ""
+"As with WS-Coordination, the two WS-Transaction models are extensible "
+"allowing implementations to tailor the protocols as they see fit (for "
+"example, to suit their deployment environments)."
+msgstr ""
+"Tout comme dans le cas de WS-Coordination, les deux modèles de WS-"
+"Transaction sont extensibles, permettant aux implémentations de mettre au "
+"point des protocoles qui leur conviennent (par exemple, personnalisés par "
+"rapport à leur environnement de déploiement)."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:157
+#, no-c-format
+msgid "Atomic Transactions (AT)"
+msgstr "Atomic Transactions (AT)"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:158
+#, no-c-format
+msgid ""
+"An atomic transaction or AT is similar to traditional ACID transactions and "
+"intended to support short-duration interactions where ACID semantics are "
+"appropriate. Within the scope of an AT, services typically enroll "
+"transaction-aware resources, such as databases and message queues, "
+"indirectly as participants under the control of the transaction. When the "
+"transaction terminates, the outcome decision of the AT is then propagated to "
+"each enlisted resource via the participant, and the appropriate commit or "
+"rollback actions are taken by each."
+msgstr ""
+"Une transaction atomique ou AT (de l'anglais Atomic Transaction) est "
+"semblable aux transactions ACID traditionnelles et est conçue pour prendre "
+"en charge des interactions de courte-durée pour lesquelles les sémantiques "
+"ACID sont appropriées. Dans la limite d'un AT, les services enregistrent "
+"normalement des ressources orientées-transaction, comme des bases de données "
+"et des files d'attente de messages, indirectement en tant que participants "
+"sous le contrôle de la transaction. Quand la transaction se termine, la "
+"décision émanant de l'AT est alors propagée vers chaque ressource listée par "
+"le participant, et les actions de validation ou de rejet qui conviennent "
+"sont prises par chacun."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:162
+#, no-c-format
+msgid ""
+"This protocol is very similar to those employed by traditional transaction "
+"systems that already form the backbone of an enterprise. It is assumed that "
+"all services (and associated participants) provide ACID semantics and that "
+"any use of atomic transactions occurs in environments and situations where "
+"this is appropriate: in a trusted domain, over short durations."
+msgstr ""
+"Ce protocole est très semblable à celui employé par les systèmes de "
+"transaction traditionnels qui constituent déjà la structure principale d'une "
+"entreprise. On assume que tous les services (et les participants qui y sont "
+"associés) fournissent des sémantiques ACID et que toute utilisation des "
+"transactions atomiques aient lieu dans des environnements et des situations "
+"qui s'y apprêtent : dans un domaine fiable, sur des périodes courtes."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:165
+#, no-c-format
+msgid ""
+"To begin an atomic transaction, the client application firstly locates a WS-"
+"Coordination coordinator Web service that supports WS-Transaction. Once "
+"located, the client sends a WS-Coordination CreateCoordinationContext "
+"message to the activation service specifying http://schemas.xmlsoap.org/"
+"ws/2004/10/wsat as its coordination type and will get back an appropriate WS-"
+"Transaction context from the activation service. The response to the "
+"CreateCoordinationContext message, the transaction context, has its "
+"CoordinationType element set to the WS-Atomic Transaction namespace, http://"
+"schemas.xmlsoap.org/ws/2004/10/wsat, and also contains a reference to the "
+"atomic transaction coordinator endpoint (the WS-Coordination registration "
+"service) where participants can be enlisted."
+msgstr ""
+"Pour démarrer une transaction atomique, l'application du client identifie "
+"tout d'abord un service Web de Coordination-WS qui prend en charge "
+"Transaction-WS. Suite à cette identification, le client envoie un message WS-"
+"Coordination CreateCoordinationContext vers le service d'activation en "
+"spécifiant comme type de coordination http://schemas.xmlsoap.org/ws/2004/10/"
+"wsat et obtiendra en retour un contexte WS-Transaction qui convient en "
+"provenance du service d'activation. La réponse au message "
+"CreateCoordinationContext, le contexte de transaction, a son élément "
+"CoordinationType dans l'espace-nom WS-Atomic Transaction, http://schemas."
+"xmlsoap.org/ws/2004/10/wsat, et contient aussi une référence à l'extrémité "
+"du coordinateur de transactions atomique (le service d'enregistrement WS-"
+"Coordination) qui répertorie des participants."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:168
+#, no-c-format
+msgid ""
+"After obtaining a transaction context from the coordinator, the client "
+"application then proceeds to interact with Web services to accomplish its "
+"business-level work. With each invocation on a business Web service, the "
+"client inserts the transaction context into a SOAP header block, such that "
+"each invocation is implicitly scoped by the transaction – the toolkits that "
+"support WS-Atomic Transaction-aware Web services provide facilities to "
+"correlate contexts found in SOAP header blocks with back-end operations."
+msgstr ""
+"Après avoir obtenu le contexte de transaction de la part du coordinateur, "
+"l'application client doit alors commencer à communiquer avec les services "
+"Web pour réaliser son travail niveau-business.  Après chaque invocation sur "
+"un service Web-business, le client insère le contexte de transaction dans un "
+"bloc SOAP, de façon à ce que chaque invocation soit implicitement mise à la "
+"portée de la transaction - le toolkit qui prend en charge les services Web "
+"WS-Atomic Transaction-aware, procure des fonctionnalités pour mettre en "
+"corrélation des contextes de blocs SOAP à opérations back-end."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:171
+#, no-c-format
+msgid ""
+"Once all the necessary application level work has been completed, the client "
+"can terminate the transaction, with the intent of making any changes to the "
+"service state permanent. To do this, the client application first registers "
+"its own participant for the Completion protocol. Once registered, the "
+"participant can instruct the coordinator either to try to commit or rollback "
+"the transaction. When the commit or rollback operation has completed, a "
+"status is returned to the participant to indicate the outcome of the "
+"transaction."
+msgstr ""
+"Une fois que tout le travail nécessaire au niveau application est terminé, "
+"le client pourra terminer la transaction, dans le but de rendre tout "
+"changement de l'état du service permanent. Pour cela, l'application client "
+"enregistre tout d'abord son propre participant pour le protocole Completion. "
+"Une fois enregistré, le participant peut alors instruire le coordinateur de "
+"soit essayer de valider, soit de rejeter la transaction. Une fois que "
+"l'opération de validation ou de rejet est terminée, un statut retourne vers "
+"le participant pour indiquer le résultat de la transaction."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:174
+#, no-c-format
+msgid ""
+"While the completion protocol is straightforward, they hide the fact that in "
+"order to resolve to an outcome that several other protocols need to be "
+"executed."
+msgstr ""
+"Malgré que le protocole de completion soit simple, il n'en demeure pas moins "
+"que pour obtenir un résultat, plusieurs protocoles doivent être exécutés."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:177
+#, no-c-format
+msgid ""
+"The first of these protocols is the optional Volatile2PC. The Volatile2PC "
+"protocol is the WS-Atomic Transaction equivalent of the synchronization "
+"protocol we discussed earlier. It is typically executed where a Web service "
+"needs to flush volatile (cached) state, which may be being used to improve "
+"performance of an application, to a database prior to the transaction "
+"committing. Once flushed, the data will then be controlled by a two-phase "
+"aware participant."
+msgstr ""
+"Le premier de ces protocoles est le protocole Volatile2PC optionnel. Le "
+"protocole Volatile2PC est la Transaction WS-Atomic équivalente au protocole "
+"de synchronisation dont nous avons discuté plus tôt. C'est normalement "
+"exécuté là où un service Web a besoin d'évacuer un état (caché) volatile, ce "
+"qui peut être utilisé en vue d'améliorer la performance d'une application, "
+"vers une base de données avant que la transaction ne soit validée. Une fois "
+"évacuées, les données seront contrôlées par le participant deux-étapes."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:180
+#, no-c-format
+msgid ""
+"All Volatile2PC participants are told that the transaction is about to "
+"complete (via the prepare message) and they can respond with either the "
+"prepared, aborted or readonly message; any failures at this stage will cause "
+"the transaction to rollback."
+msgstr ""
+"Tous les participants Volatile2PC sont instruits du fait que la transaction "
+"est sur le point de se terminer (via le message 'prepare') et ils peuvent "
+"répondre par les messages 'préparés' (prepared), 'abandonnés' (aborted) ou "
+"'lecture-uniquement'(readonly), tout échec à ce niveau entraînera l'échec de "
+"la transaction."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:183
+#, no-c-format
+msgid ""
+"After Volatile2PC prepare, the next protocol to execute in WS-Atomic "
+"Transaction is Durable2PC. The Durable2PC (an abbreviation of the term two-"
+"phase commit) protocol is at the very heart of WS-Atomic Transaction and is "
+"used to bring about the necessary consensus between participants in a "
+"transaction such that the transaction can safely be terminated."
+msgstr ""
+"Après que Volatile2PC se soit 'préparé', le prochain protocole à exécuter "
+"dans la Transaction WS-Atomique est Durable2PC. Le protocole Durable2PC (une "
+"abréviation du terme validation en deux-phases) est au coeur de la "
+"Transaction WS-Atomic et est utilisé pour créer le consensus utile entre les "
+"participants dans la transaction, de façon à ce que la transaction puisse se "
+"terminer en toute sécurité."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:186
+#, no-c-format
+msgid ""
+"The two-phase commit protocol is used to ensure atomicity between "
+"participants, and is based on the classic two-phase commit with presumed "
+"abort technique. During the first phase, when the coordinator sends the "
+"prepare message, a participant must make durable any state changes that "
+"occurred during the scope of the transaction, such that these changes can "
+"either be rolled back or committed later. That is, any original state must "
+"not be lost at this point as the atomic transaction could still roll back. "
+"If the participant cannot prepare then it must inform the coordinator (via "
+"the aborted message) and the transaction will ultimately roll back. If the "
+"participant is responsible for a service that did not do any work during the "
+"course of the transaction, or at least did not do any work that modified any "
+"state, it can return the readonly message and it will be omitted from the "
+"second phase of the commit protocol. Otherwise, the prepared message is sent "
+"by the participant."
+msgstr ""
+"Le protocole de validation en deux-phases est utilisé pour garantir "
+"l'atomicité entre les participants, et est basée sur la validation en deux-"
+"phases classique comprenant la supposée technique d'annulation. Au cours de "
+"la première phase, quand le coordinateur envoie le message 'prepare', un "
+"participant doit rendre durable tout changement d'état qui a pu avoir lieu "
+"pendant la transaction, de façon à ce que ces changements puissent être soit "
+"rejetés, soit validés plus tard. C'est à dire que tout état d'origine ne "
+"doit pas être perdu à ce niveau, car la transaction atomique pourrait "
+"toujours être rejetée. Si le participant ne peut pas se 'préparer', alors il "
+"devra en informer le coordinateur (par l'intermédiaire du message abandonné) "
+"et la transaction devra finalement être rejetée. Si le participant est "
+"responsable d'un service qui serait demeuré passif au cours de la "
+"transaction, ou tout du moins qui n'aurait effectué aucune tâche susceptible "
+"de modifier un état, il peut retourner le message 'lecture-"
+"uniquement' (readonly) et il sera omis dans la seconde phase du protocole de "
+"validation. Sinon, le message préparé sera envoyé par le participant."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:189
+#, no-c-format
+msgid ""
+"Assuming no failures occurred during the first phase, in the second phase "
+"the coordinator sends the commit message to participants, who will make "
+"permanent the tentative work done by their associated services."
+msgstr ""
+"Si aucun échec n'a lieu pendant la première phase, le coordinateur enverra "
+"le message de validation aux participants au cours de la seconde phase, ce "
+"qui rendra le travail provisoire effectué par ses services associés "
+"permanent."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:192
+#, no-c-format
+msgid ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
+msgstr ""
+"Si une transaction n'implique qu'un seul participant, la transaction WS-"
+"Atomic prendra en charge une optimisation de validation en une-phase. Comme "
+"il n'y a qu'un seul participant, ses décisions atteignent implicitement un "
+"consensus, et le coordinateur n'a pas besoin de conduire la transaction vers "
+"les deux étapes. Dans le meilleur cas, le participant sera tout simplement "
+"instruit de valider et le coordinateur de transactions n'aura pas besoin "
+"d'enregistrer d'informations sur la décision puisque le résultat est "
+"uniquement lié à ce seul participant."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:195
+#, no-c-format
+msgid ""
+"The figure below<footnote> <para> Redrawn from the WS-Atomic Transaction "
+"specification. </para> </footnote> shows the state transitions of a WS-"
+"Atomic Transaction and the message exchanges between coordinator and "
+"participant; the coordinator generated messages are shown in the solid line, "
+"whereas the participant messages are shown by dashed lines."
+msgstr ""
+"Le schéma ci-dessous <footnote> <para> Redrawn from the WS-Atomic "
+"Transaction specification. </para> </footnote> montre les transitions de "
+"l'état d'une Transaction WS-Atomique et le message est échangé entre le "
+"coordinateur et le participant; les messages générés par le coordinateur "
+"apparaissent sur une ligne solide, alors que les messages du participant "
+"sont indiqués par les lignes entrecoupées."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:206
+#, no-c-format
+msgid "Two-Phase Commit State Transitions"
+msgstr "Les transitions d'état de validation en deux-phases"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:208
+#, no-c-format
+msgid ""
+"Once the 2PC protocol has finished, the Completion protocol that originally "
+"began the termination of the transaction can complete, and inform the client "
+"application whether the transaction was committed or rolled back. "
+"Additionally, the Volatile2PC protocol may complete."
+msgstr ""
+"A la fin du protocole 2PC, le protocole de Completion, qui a déclenché le "
+"début du processus de fermeture de transaction, peut être complété, et "
+"informer l'application du client si la transaction était validée ou rejetée. "
+"De plus, le protocole Volatile2PC peut être mené à bonne fin."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:211
+#, no-c-format
+msgid ""
+"Like the prepare phase of Volatile2PC, the final phase is optional and can "
+"be used to inform participants when the transaction has completed, typically "
+"so that they can release resources (for example, put a database connection "
+"back into the pool of connections)."
+msgstr ""
+"Tout comme l'étape 'prepare' du protocole Volatile2PC, la phase finale est "
+"optionnelle et peut être utilisée pour informer les participants quand la "
+"transaction est terminée, normalement de façon à ce qu'ils puissent libérer "
+"des ressources (par exemple, en mettant un connexion de base de données au "
+"sein du pool de connexions)."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:214
+#, no-c-format
+msgid ""
+"Any registered Volatile2PC participants are invoked after the transaction "
+"has terminated and are told the state in which the transaction completed "
+"(the coordinator sends either the Committed or Aborted message). Since the "
+"transaction has terminated, any failures of participants at this stage are "
+"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
+"the transaction."
+msgstr ""
+"Tous les participants enregistrés sur le protocole Volatile2PC sont invoqués "
+"une fois que la transaction est terminée et sont informés de l'état dans "
+"lequel la transaction a été menée à bout (le coordinateur envoie un message "
+"de validation ou d'abandon). Depuis que la transaction est terminée, tout "
+"échec des participants à ce niveau sont ignorés - il s'agit purement d'un "
+"effort de courtoisie, donc n'a aucune influence sur le résultat de la "
+"transaction."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:217
+#, no-c-format
+msgid ""
+"Finally, after having gone through each of the stages in an AT, it is "
+"possible to see the intricate interweaving of individual protocols that goes "
+"to make up the AT as a whole in the following figure."
+msgstr ""
+"Finalement, après être passé par chacune des étapes d'un AT, il est possible "
+"d'observer la toile intriquée des protocoles individuels qui constituent "
+"l'AT dans son ensemble et suivant le schéma suivant."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:224
+#, no-c-format
+msgid "The AT Model"
+msgstr "Le modèle AT"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:227
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr "Business Activities (BA)"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:228
+#, no-c-format
+msgid ""
+"Most business-to-business applications require transactional support in "
+"order to guarantee consistent outcome and correct execution. These "
+"applications often involve long running computations, loosely coupled "
+"systems and components that do not share data, location, or administration "
+"and it is difficult to incorporate atomic transactions within such "
+"architectures. For example, an online bookshop may reserve books for an "
+"individual for a specific period of time, but if the individual does not "
+"purchase the books within that period they will be “put back onto the shelf” "
+"for others to buy. Furthermore, because it is not possible for anyone to "
+"have an infinite supply of stock, some online shops may appear to users to "
+"reserve items for them, but in fact may allow others to pre-empt that "
+"reservation (for instance, the same book may be “reserved” for multiple "
+"users concurrently); a user may subsequently find that the item is no longer "
+"available, or may have to be reordered specially for them."
+msgstr ""
+"La plupart des applications business-to-business ont besoin d'un soutien "
+"transactionnel pour pouvoir garantir un résultat consistant et une exécution "
+"correcte. Ces applications impliquent souvent des traitements de calcul "
+"longs, des systèmes couplés informellement, et des composants qui ne "
+"partagent ni de données, ni de location ou d'administration et il est "
+"difficile d'incorporer des transactions atomiques au sein de telles "
+"architectures. Ainsi, une librairie en ligne peut réserver des livres pour "
+"un individu pendant un certain temps, mais si l'individu n'achète pas les "
+"livres au cours de cette période, il seront 'remis sur les étagères' pour "
+"que d'autres individus puissent les acheter. De plus, comme il est "
+"impossible pour qui que ce soit de posséder des stocks illimités, certains "
+"magasins en peuvent donner l'impression aux utilisateurs qu'il se réservent "
+"des stocks pour eux-mêmes, quand en fait, ils sont sûrement en train de "
+"préempter cette réservation (par exemple, le même livre peut être réservé "
+"pour des utilisateurs multiples concouramment). Un utilisateur peut alors "
+"s'apercevoir qu'un article n'est plus disponible, ou qu'il doit être "
+"recommandé spécialement pour lui."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:232
+#, no-c-format
+msgid ""
+"A business activity or BA is designed specifically for these kinds of long-"
+"duration interactions, where exclusively locking resources is impossible or "
+"impractical. In this model services are requested to do work, and where "
+"those services have the ability to undo any work, they inform the BA such "
+"that if the BA later decides the cancel the work (for instance if the "
+"business activity suffers a failure), it can instruct the service to execute "
+"its undo behavior. The key point for Business Activities is that how "
+"services do their work and provide compensation mechanisms is not the domain "
+"of the WS-Business Activity specification, but an implementation decision "
+"for the service provider."
+msgstr ""
+"Un BA (de l'anglais Business Activity / activité commerciale) est conçu "
+"spécialement pour ces interactions de longue durée, pour lesquelles "
+"verrouiller exclusivement des ressources est impossible ou non pratique. "
+"Dans ce modèle, les services ont besoin d'effectuer un travail, et "
+"lorsqu'ils ont la possibilité de démanteler un travail, ils informent le BA, "
+"de façon à ce que si le BA décide plus tard d'annuler le travail (par "
+"exemple, si le BA échoue), il pourra instruire le service d'exécuter le "
+"démantèlement. Ce qui est important pour les BA, c'est que la façon dont les "
+"services font leur travail ou proposent des mécanismes de compensation, "
+"n'est pas du domaine de la spécification WS-Business Activity, mais une "
+"décision d'implémentation pour le fournisseur de services."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:235
+#, no-c-format
+msgid ""
+"The WS- Business Activity simply defines a protocol for Web services-based "
+"applications to enable existing business processing and workflow systems to "
+"wrap their proprietary mechanisms and interoperate across implementations "
+"and business boundaries."
+msgstr ""
+"Le WS-Business Activity définit simplement un protocole d'applications "
+"basées services-Web pour permettre le traitement des opérations en cours et "
+"et pour permettre aux systèmes de flux de travaux d'encapsuler leurs "
+"mécanismes propriétaires et d'opérer entre les limites des implémentations "
+"et des activités commerciales."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:238
+#, no-c-format
+msgid ""
+"A business activity may be partitioned into scopes, where a scope is a "
+"business task or unit of work using a collection of Web services. Such "
+"scopes can be nested to arbitrary degrees, forming parent and child "
+"relationships, where a parent scope has the ability to select which child "
+"tasks are to be included in the overall outcome protocol for a specific "
+"business activity, and so clearly non-atomic outcomes are possible. In a "
+"similar manner to traditional nested transactions, if a child task "
+"experiences an error, it can be caught by the parent who may be able to "
+"compensate and continue processing."
+msgstr ""
+"Une activité commerciale peut être partitionnée en portées, où chaque portée "
+"est une tâche commerciale ou une unité de travail qui utilise en ensemble de "
+"services Web. Ces portées peuvent être intégrées dans des degrés "
+"arbitraires, formant des relations parent-enfant, et pour lesquelles une "
+"portée parent est en mesure de sélectionner quelles tâches enfant peuvent "
+"être incluses dans le protocole de résultat général pour une activité "
+"commerciale spécifique, et donc, les résultats non-atomiques sont clairement "
+"possibles. A la manière des transactions intégrées traditionnelles, si une "
+"tâche enfant rencontre une erreur, elle peut être rattrapée par le parent "
+"qui peut certainement la compenser et continuer le processus."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:241
+#, no-c-format
+msgid ""
+"When a child task completes it can either leave the business activity or "
+"signal to the parent that the work it has done can be compensated later. In "
+"the latter case, the compensation task may be called by the parent should it "
+"ultimately need to undo the work performed by the child."
+msgstr ""
+"Quand une tâche enfant s'achève, elle peut soit quitter l'activité "
+"commerciale, soit signaler au parent que le travail qu'il a effectué pourra "
+"être compensé plus tard. Dans ce dernier cas, la tâche de compensation "
+"pourrait être appelée par le parent, s'il avait finalement besoin de "
+"démanteler le travail effectué par l'enfant."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:244
+#, no-c-format
+msgid ""
+"Unlike the WS-Atomic Transaction protocol model, where participants inform "
+"the coordinator of their state only when asked, a task within a business "
+"activity can specify its outcome to the parent directly without waiting for "
+"a request. This feature is useful when tasks fail such that the notification "
+"can be used by business activity exception handler to modify the goals and "
+"drive processing forward without having to meekly wait until the end of the "
+"transaction to admit to having failed – a well designed Business Activities "
+"should be proactive, if it is to perform well."
+msgstr ""
+"A la différence du modèle de protocole WS-Atomic Transaction, dans lequel "
+"les participants informent le coordinateur de leur état quand on le leur "
+"demande, une tâche qui prend place dans un BA peut informer le parent de son "
+"résultat directement, sans avoir à attendre une demande. Cette "
+"fonctionnalité est utile quand les tâches échouent de telle manière que la "
+"notification peut être utilisée par le gestionnaire d'exceptions de BA pour "
+"modifier les buts et continuer le processus sans avoir à attendre la fin de "
+"la transaction pour avoir la confirmation de l'échec - une BA bien conçue "
+"devrait être proactive, si elle doit être performante."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:247
+#, no-c-format
+msgid "Underpinning all of this are three fundamental assumptions:"
+msgstr "Il existe trois hypothèses fondamentales dans cette logique :"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:252
+#, no-c-format
+msgid ""
+"All state transitions are reliably recorded, including application state and "
+"coordination metadata (the record of sent and received messages);"
+msgstr ""
+"Toutes les transitions d'état sont enregistrées de façon fiable, y compris "
+"les états d'application, et les métadonnées de coordination "
+"(l'enregistrement des messages envoyés ou reçus);"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:257
+#, no-c-format
+msgid ""
+"All request messages are acknowledged, so that problems are detected as "
+"early as possible. This avoids executing unnecessary tasks and can also "
+"detect a problem earlier when rectifying it is simpler and less expensive;"
+msgstr ""
+"Toutes les demandes de messsages sont reconnues formellement, de façon à ce "
+"que les problèmes soient détectés le plus rapidement possible. Cela évite "
+"d'exécuter des tâches inutiles et permet également de détecter un problème "
+"tôt quand sa correction est plus simple et moins onéreuse."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:262
+#, no-c-format
+msgid ""
+"As with atomic transactions, a response is defined as a separate operation "
+"and not as the output of the request. Message input-output implementations "
+"will typically have timeouts that are too short for some business activity "
+"responses. If the response is not received after a timeout, it is resent. "
+"This is repeated until a response is received. The request receiver discards "
+"all but one identical request received."
+msgstr ""
+"Comme pour les transactions atomiques, une réponse est définie comme une "
+"opération séparée et non pas comme un résultat suite à une demande. Les "
+"implémentations d'entrée-sortie de messages auront normalement des délais "
+"qui sont trop courts pour certaines réponses de BA. Si la réponse n'est pas "
+"reçue après un certain temps, elle est renvoyée. Cette opération est "
+"renouvelée jusqu'à ce que l'on reçoive une réponse. Le réceptionniste des "
+"demandes ignorera toutes les réponses identiques reçues sauf une."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:267
+#, no-c-format
+msgid ""
+"As with atomic transactions, the business activity model has multiple "
+"protocols: <code>BusinessAgreementWithParticipantCompletion</code> and "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. However, unlike the "
+"AT protocol which is driven from the coordinator down to participants, this "
+"protocol is driven much more from the participants upwards."
+msgstr ""
+"Comme pour les transactions atomiques, le modèle d'activité commerciale "
+"comprend des protocoles multiples : "
+"<code>BusinessAgreementWithParticipantCompletion</code> et "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. Cependant, à la "
+"différence du protocole AT qui va du coordinateur vers les participants, ce "
+"protocole prend pour point de départ les participants."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
+#, no-c-format
+msgid ""
+"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
+"a child activity is initially created in the Active state; if it finishes "
+"the work it was created to do and no more participation is required within "
+"the scope of the BA (such as when the activity operates on immutable data), "
+"then the child can unilaterally send an exited message to the parent. "
+"However, if the child task finishes and wishes to continue in the BA then it "
+"must be able to compensate for the work it has performed. In this case it "
+"sends a completed message to the parent and waits to receive the final "
+"outcome of the BA from the parent. This outcome will either be a close "
+"message, meaning the BA has completed successfully or a compensate message "
+"indicating that the parent activity requires that the child task reverse its "
+"work."
+msgstr ""
+"Sous le protocole <code>BusinessAgreementWithParticipantCompletion</code>, "
+"une activité enfant est créée au départ dans l'état Active. S'il termine le "
+"travail pour lequel il a été conçu, et qu'il n'y ait plus besoin de "
+"participation dans la portée du BA (comme lorsque l'activité opère sur des "
+"données immuables), alors l'enfant peut envoyer unilatéralement un message "
+"'exited' aux parents. Mais, si l'enfant termine sa tâche et souhaite "
+"continuer dans le BA, alors il devra pouvoir compenser pour le travail qu'il "
+"a effectué. Dans ce cas, un message 'complete' est envoyé aux parents et on "
+"attend à recevoir le résultat final du BA des parents. Ce résultat sera soit "
+"un message 'close', indiquant que le BA a été réalisé avec succès, ou un "
+"message 'compensate', indiquant que l'activité parent exige que la tâche "
+"enfant inverse son travail."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
+#, no-c-format
+msgid ""
+"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
+"identical to the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol with the exception that the child cannot autonomously decide to end "
+"its participation in the business activity, even if it can be compensated. "
+"Rather the child task relies upon the parent to inform it when the child has "
+"received all requests for it to perform work which the parent does by "
+"sending the complete message to the child. The child then acts as it does in "
+"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
+msgstr ""
+"Le protocole <code>BusinessAgreementWithCoordinatorCompletion</code> est "
+"identique au protocole <code>BusinessAgreementWithParticipantCompletion</"
+"code> sauf que l'enfant ne peut pas automatiquement décider de mettre fin à "
+"sa participation à son activité commerciale (BA), même s'il peut être "
+"compensé. La tâche de l'enfant compte plutôt sur le parent pour l'informer "
+"quand l'enfant a reçu suffisamment de demandes pour qu'il puisse effectuer "
+"des tâches du domaine des parents en envoyant un message 'complete' à "
+"l'enfant. L'enfant agit alors comme il le fait dans le protocole "
+"<code>BusinessAgreementWithParticipantCompletion</code>."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:276
+#, no-c-format
+msgid ""
+"The crux of the BA model compared to the AT model is that is allows the "
+"participation of services that cannot or will not lock resources for "
+"extended periods."
+msgstr ""
+"Le fond du raisonnement du modèle BA par rapport au modèle AT, est qu'il "
+"permet la participation de services qui ne pourront ou ne voudront "
+"verrouiller des ressources pour des longues périodes."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:279
+#, no-c-format
+msgid ""
+"While the full ACID semantics are not maintained by a BA, consistency can "
+"still be maintained through compensation, though the task of writing correct "
+"compensating actions (and thus overall system consistency) is delegated to "
+"the developers of the services under control of the BA. Such compensations "
+"may use backward error recovery, but will typically employ forward recovery."
+msgstr ""
+"Tandis que les sémantiques ACID dans leur ensemble, ne sont pas maintenues "
+"par un BA, l'homogénéité peut toujours être maintenue par compensation, "
+"malgré que la tâche d'écrire des actions compensatoires correctes ( et donc "
+"l'homogénéité du système dans son ensemble) soit déléguée aux développeurs "
+"des services sous le contrôle du BA. De telles compensations peuvent "
+"utiliser le recouvrement rétroactif en cas d'erreur, mais emploiera, dans la "
+"plupart des cas, un recouvrement actif."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:283
+#, no-c-format
+msgid "Application Messages"
+msgstr "Messages d'application"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:284
+#, no-c-format
+msgid ""
+"Application messages are the requests and responses that are sent between "
+"parties that constitute the work of a business process. Any such messages "
+"are considered opaque by XTS, and there is no mandatory message format, "
+"protocol binding, or encoding style so the developer is free to use any "
+"appropriate Web services protocol. In XTS, the transaction context is "
+"propagated within the headers of SOAP messages."
+msgstr ""
+"Les messages d'application sont les demandes et les réponses qui sont "
+"envoyées entre les parties qui comprennent le travail d'un processus "
+"commercial. De tels messages sont considérés comme opaques par XTS, et il "
+"n'existe pas de format de message, de type de programmation de codage, de "
+"protocole obligatoire, donc le développeur est libre d'utiliser n'importe "
+"quel protocole de service Web qui convient. Dans XTS, le contexte de "
+"transaction est propagé dans les messages SOAP."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:289
+#, no-c-format
+msgid ""
+"XTS provides out-of-box support for service developers building WS-T-aware "
+"services on the JBoss, Weblogic and Glue platforms1. The provision of "
+"interceptors for automatic context handling at both client and service "
+"significantly simplifies the developer’s workload, allowing the developer to "
+"concentrate on writing the business logic without having to worry about the "
+"transactional infrastructure getting in the way. The interceptors simply add "
+"and remove context elements to application messages without altering the "
+"semantics of those messages. Any service which understands what to do with a "
+"WS-C context can use it, services which do not understand the context (those "
+"services that are not WS-C, WS-Atomic Transaction and WS-Business Activity-"
+"aware) may ignore the context; the important point here is that XTS manages "
+"contexts without user intervention."
+msgstr ""
+"XTS fournit un support out-of-box pour les développeurs de service "
+"construisant des services WS-T-aware sur JBoss, Weblogic et Glue platforms1. "
+"La provision d'intercepteurs pour la gestion de contexte automatique pour "
+"les clients et le service à la fois, simplifie énormément la tâche du "
+"développeur, lui permettant ainsi de se concentrer sur la rédaction de la "
+"logique commerciale sans avoir à se préoccuper de l'infrastructure "
+"transactionnelle. Les intercepteurs ajoutent ou retirent des éléments de "
+"contexte aux messages d'application tout simplement, sans altérer la "
+"sémantique de ces messages. Tout service qui comprend ce qu'il faut faire "
+"dans un contexte WS-C, peut l'utiliser. Les services qui ne comprennent pas "
+"bien le contexte (qui ne sont ni WS-C, WS-Atomic Transaction ou WS-Business "
+"Activity-aware) peuvent l'ignorer. Ce qui est important de comprendre ici, "
+"c'est que XTS gère les contextes sans besoin d'intervention de la part de "
+"l'utilisateur."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:294
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr "Messages WS-C, WS-Atomic Transaction et WS-Business Activity"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:295
+#, no-c-format
+msgid ""
+"Although the application or service developer rarely sees or is interested "
+"in the messages exchanged by the transactional infrastructure (the "
+"transaction manager and any participants), it is useful to understand what "
+"kinds of exchanges occur so that the underlying model can be fitted in to an "
+"overall architecture."
+msgstr ""
+"Malgré que le développeur de service ou d'application ne voie ou soit que "
+"rarement intéressé par les messages échangés par l'infrastructure "
+"transactionnelle (le gestionnaire de la transaction et n'importe quel "
+"participant), il est utile de comprendre les échanges qui peuvent prendre "
+"place de façon à ce que le modèle sous-jacent puisse être inscrit dans "
+"l'architecture dans son ensemble."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:299
+#, no-c-format
+msgid ""
+"In XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific "
+"messages are transported using SOAP messaging over HTTP. The types of "
+"messages that are propagated include instructions to perform standard "
+"transaction operations like begin, prepare."
+msgstr ""
+"Dans XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific, on "
+"transporte des messages en utilisant la messagerie SOAP sur HTTP. Les types "
+"de messages propagés comprennent des instructions pour réaliser des "
+"opérations de transactions standard comme 'begin' et 'prepare'."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:303
+#, no-c-format
+msgid ""
+"XTS messages do not interfere in any way, shape, or form, with the "
+"application messages, and nor is there any requirement for an application to "
+"use the same transport as the transaction-specific messages. For example, it "
+"is quite reasonable for a client application to deliver its application-"
+"specific messages using SOAP RPC over SMTP even though under the covers the "
+"XTS messages are delivered using a different mechanism."
+msgstr ""
+"Les messages XTS n'interfèrent en aucune façon ou forme, avec les message "
+"d'application, et il n'y a pas de prérequis pour qu'une application utilise "
+"le même moyen de transport que les messages spécifiques-transaction. Ainsi, "
+"il est assez raisonnable pour une application client d'envoyer ses messages "
+"spécifiques-application en utilisant SOAP RPC sur SMTP même si sous couvert "
+"les messages XTS sont envoyés par un mécanisme différent."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:310
+#, no-c-format
+msgid "Summary"
+msgstr "Résumé"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:311
+#, no-c-format
+msgid ""
+"XTS provides a coordination infrastructure designed to allow transactions to "
+"run between enterprises across the Internet. That infrastructure is based on "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. It "
+"supports two kinds of transactions: atomic transactions and business "
+"activities, which can be combined in arbitrary ways to map elegantly onto "
+"the transactional requirements of the underlying problem. The use of the "
+"whole infrastructure is simple due to the fact that its functionality is "
+"exposed through a simple transactioning API. Furthermore XTS provides all of "
+"the necessary plumbing to keep application and transactional aspects of an "
+"application separate, and to ensure that the transactionality of a system "
+"does not interfere with the functional aspects of the system itself."
+msgstr ""
+"XTS fournit une infrastructure conçue pour permettre aux transactions d'être "
+"exécutées par les entreprises à travers l'Internet. Cette infrastructure est "
+"basée sur les spécifications XTS, WS-C, WS-Atomic Transaction et WS-Business "
+"Activity. Elle prend en charge deux sortes de transactions: les transactions "
+"atomiques et les activités commerciales, qui peuvent être combinées de "
+"façons arbitraires pour mapper élégamment par rapport aux prérequis "
+"transactionnels du problème sous-jacent. L'utilisation de l'infrastructure "
+"dans son ensemble est simple du fait que sa fonctionnalité est exposée à "
+"travers un simple API transactionnel. De plus, XTS fournit toute la "
+"plomberie pour garder séparés l'application de ses aspects transactionnels, "
+"et pour veiller à ce que la transactionalité d'un système n'interfère pas "
+"avec les aspects fonctionnels du système lui-même."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Author_Group.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Author_Group.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Book_Info.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Book_Info.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,50 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide CP04"
+msgstr "JBoss トランザクション Web サービスプログラマガイド"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "JBoss Enterprise Application Platform 4.3 対応"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr ""
+"このマニュアルはトランザクション Web サービスの為のプログラミングを説明してい"
+"ます。"
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr "ロゴ"
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Getting_Started.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Getting_Started.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Getting_Started.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,262 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Getting_Started.xml:6
+#, no-c-format
+msgid "Getting Started"
+msgstr "さあ始めましょう"
+
+#. Tag: title
+#: Getting_Started.xml:8
+#, no-c-format
+msgid "Creating and deploying participants"
+msgstr "パーティシパントの作成とデプロイ"
+
+#. Tag: para
+#: Getting_Started.xml:9
+#, no-c-format
+msgid ""
+"A participant is a software entity which is driven by the transaction "
+"manager on behalf of a Web service. The creation of participants is non-"
+"trivial since they ultimately reflect the state of a Web service’s back-end "
+"processing facilities which is a function of an enterprise’s own IT "
+"infrastructure. The most that can be said about the implementation of a "
+"participant without getting into detail about the back-end systems it "
+"represents, or the details of the underlying transaction protocol is that "
+"implementations must implement one of the following interfaces, depending "
+"upon the protocol it will participate within: <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code>, or, <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+msgstr ""
+"パーティシパントとは、Web サービスの役目としてトランザクションマネージャに"
+"よって 駆動されるソフトウェアエンティティです。パーティシパントが最終的に 企"
+"業の IT インフラストラクチャの機能である Web サービスのバックエンドプロセッシ"
+"ング 設備の状態を反映するため、パーティシパントの作成は軽視することはできませ"
+"ん。それが表現する バックエンドシステムの詳細や、背後にあるトランザクションプ"
+"ロトコルの詳細を避けてパーティシパントの 実装について言えることは、その実装"
+"が、その参加するプロトコルに応じて以下のようなインターフェイスの１つを 実装し"
+"なければならないことです: <code>com.arjuna.wst.Durable2PCParticipant</"
+"code>、 <code>com.arjuna.wst.Volatile2PCParticipant</code>、\n"
+"  <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>、\n"
+" <code>com.arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</"
+"code>。"
+
+#. Tag: title
+#: Getting_Started.xml:15
+#, no-c-format
+msgid "Creating Client Applications"
+msgstr "クライアントアプリケーションの作成"
+
+#. Tag: para
+#: Getting_Started.xml:16
+#, no-c-format
+msgid ""
+"There are two aspects to a client application using XTS. The first is the "
+"transaction declaration aspects and the second is the business logic that "
+"the client application performs. The transaction declaration aspects are "
+"taken care of automatically with XTS’s client API. This API provides simple "
+"transaction directives like begin, commit, and rollback which the client "
+"application can use to initialize, manage, and terminate transactions. Under "
+"the covers, this API invokes (via SOAP) operations on the transaction "
+"manager."
+msgstr ""
+"XTS を使用するクライアントアプリケーションには２つの側面があります。１つめは "
+"トランザクション宣言の側面で、２つめはそのクライアントアプリケーションが実行"
+"する ビジネス論理の側面です。トランザクション宣言の側面は XTS のクライアント "
+"API に よって自動的に担当されています。この API が、begin、commit、rollback "
+"などの 簡単なトランザクションディレクティブを提供して、それをクライアントがト"
+"ランザクションの 始動、管理、終了のために使用できます。表面下では API が"
+"（SOAP 経由で）トランザクション マネージャ上のオペレーションを呼び出します。"
+
+#. Tag: para
+#: Getting_Started.xml:19
+#, no-c-format
+msgid ""
+"When the client application performs invocations on business logic Web "
+"services, then XTS does not dictate an API for that purpose. However, there "
+"is a requirement that whatever API is chosen, the XTS context be inserted "
+"onto outgoing messages, and extracted and associated with the current thread "
+"for incoming messages. To make the user’s life easier, the XTS software "
+"comes complete with three sets of “filters” which can perform the task "
+"automatically. These filters are designed to work with JAX-RPC and "
+"webMethods client libraries."
+msgstr ""
+"クライアントアプリケーションが、ビジネス論理 Web サービス上で呼び出しを 実行"
+"すると、XTS はその目的では API に指示しません。しかし、選択される API の種類"
+"に関係無く、XTS コンテキストが発信メッセージに挿入されて、 来信メッセージ用に"
+"取り出されて現在のスレッドと関連づけされる必要性が あります。これをユーザーの"
+"為に簡単にするために、XTS ソフトウェアは、この タスクを自動的に実行できるフィ"
+"ルターの３つのセットを付けて配布されています。 これらのフィルターは JAX-RPC "
+"と webMethods のクライアントライブラリを 使用して機能するように設計されていま"
+"す。"
+
+#. Tag: para
+#: Getting_Started.xml:23
+#, no-c-format
+msgid ""
+"If the user chooses to use a different SOAP client infrastructure, then the "
+"onus to perform client-side header processing rests with them. XTS does not "
+"provide client-side infrastructure for anything other than JAX-RPC or "
+"webMethods for this release."
+msgstr ""
+"ユーザーが異なる SOAP クライアントインフラストラクチャを選択する場合、 クライ"
+"アントサイドのヘッダプロセッシングの責任はそれらに所在します。 このリリースで"
+"は XTS は JAX-RPC 又は webMethods 以外のものにはクライアントサイドインフラス"
+"トラクチャを提供しません。"
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr "JAX-RPC コンテキストハンドラ"
+
+#. Tag: para
+#: Getting_Started.xml:29
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC server-side context handler with the "
+"deployed web services, a handler chain must be included in the web services "
+"deployment descriptor. Please refer to the demo application <filename>jboss/"
+"webservices.xml</filename> deployment descriptor for an example of how this "
+"can be achieved."
+msgstr ""
+"JAX-RPC サーバーサイドのコンテキストハンドラをデプロイした web サービスに 登"
+"録するには、ハンドラチェーンがその web サービスデプロイメント記述子に 含まれ"
+"ていなければなりません。これが達成される方法の例としてデモアプリケーションの "
+"<filename>jboss/webservices.xml</filename> デプロイメント記述子を参照して下さ"
+"い。"
+
+#. Tag: para
+#: Getting_Started.xml:33
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC client-side context handler used by the "
+"client applications, a handler chain must be included in the definition of "
+"the service-ref in the client web.xml deployment descriptor. Please refer to "
+"the demo application <filename>jboss/client-web-app.xml</filename> for an "
+"example of how this can be achieved."
+msgstr ""
+"クライアントアプリケーションで使用されている JAX-RPC クライアントサイドコンテ"
+"キスト ハンドラを登録するために、ハンドラチェーンが１つクライアント web.xml "
+"デプロイメント 記述子の service-ref  内の定義に含まれていなければなりません。"
+"これが達成される方法の 例としてデモアプリケーション <filename>jboss/client-"
+"web-app.xml</filename> を 参照して下さい。"
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr "webMethods コンテキストハンドラ"
+
+#. Tag: para
+#: Getting_Started.xml:38
+#, no-c-format
+msgid ""
+"In order to register the webMethods server-side context handler with the "
+"deployed web services, the inbound and outbound interceptors must be "
+"configured in the web services deployment descriptor. An example of how this "
+"can be configured can be found in the demo application, for example, the "
+"<filename>RestaurantServiceAT.xml</filename>."
+msgstr ""
+"webMethods サーバーサイドのハンドラをデプロイした web サービスに登録 するため"
+"には、インバウンドとアウトバウンドのインターセプタが、web サービスの デプロイ"
+"メント記述子内で設定されていなければなりません。この設定方法の例として デモア"
+"プリケーションである <filename>RestaurantServiceAT.xml</filename> を 参照して"
+"ください。"
+
+#. Tag: para
+#: Getting_Started.xml:42
+#, no-c-format
+msgid ""
+"In order to register the webMethods client-side context handler, the inbound "
+"and outbound interceptors must be configured in the <filename>glue-config."
+"xml</filename> deployment descriptor. Please refer to the soap interceptor "
+"section of the demo application glue-config.xml for an example of how this "
+"can be achieved."
+msgstr ""
+"webMethods クライアントサイドのコンテキストハンドラを登録するためには、 イン"
+"バウンドとアウトバウンドのインターセプタが <filename>glue-config.xml</"
+"filename> デプロイメント記述子内で設定されていなければなりません。 これが達成"
+"される方法の例としてデモアプリケーション glue-config.xml の soap インターセプ"
+"タを参照してください。"
+
+#. Tag: title
+#: Getting_Started.xml:48
+#, no-c-format
+msgid "Hints and tips"
+msgstr "ヒント"
+
+#. Tag: para
+#: Getting_Started.xml:49
+#, no-c-format
+msgid ""
+"If you want to create multiple JBoss deploys on the same machine, then you "
+"may wish to look at <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/"
+"MultipleInstances.htm\"><emphasis>Setting up multiple instances</emphasis></"
+"ulink> for information on what is required."
+msgstr ""
+"複数の JBoss デプロイを同じマシン上で作成したい場合は、必要となる情報を 得る"
+"ために <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/MultipleInstances.htm"
+"\"><emphasis>複数インスタンスのセッティング</emphasis></ulink> を参照して下さ"
+"い。"
+
+#. Tag: title
+#: Getting_Started.xml:55
+#, no-c-format
+msgid "Summary"
+msgstr "要約"
+
+#. Tag: para
+#: Getting_Started.xml:56
+#, no-c-format
+msgid ""
+"This chapter has provided a high-level overview of how to use each of the "
+"major software pieces of the Web Services transactions component of JBossTS. "
+"The Web Services transaction manager provided by JBossTS is the hub of the "
+"architecture and is the only piece of software that users’ software does not "
+"bind to directly. XTS provides header processing infrastructure for dealing "
+"with Web Services transactions contexts for both users’ client applications "
+"and Web services. For developing transaction participants, XTS provides a "
+"simple interface plus the necessary document handling code."
+msgstr ""
+"この章では、JBossTS の Web サービストランザクションコンポーネント内の 主なソ"
+"フトウェア部分のそれぞれを使用する方法について高度なレベルの概要を 提供してい"
+"ます。JBossTS により提供されている Web サービストランザクション マネージャは"
+"そのアーキテクチャの中心であり、ユーザーソフトウェアが直接 バインドしない唯一"
+"のソフトウェア部分です。XTS はユーザークライアントアプリケーションと Web サー"
+"ビスの両方の為に Web サービストランザクションコンテキストを扱う為の ヘッダプ"
+"ロセッシングインフラストラクチャを提供します。トランザクションパーティシパン"
+"トの 開発には、XTS が簡単なインターフェイスと必要なドキュメントハンドリング"
+"コードを提供します。"
+
+#. Tag: para
+#: Getting_Started.xml:59
+#, no-c-format
+msgid ""
+"This chapter is meant as an overview only, and is unlikely to answer "
+"questions on more difficult and subtle aspects. For fuller explanations of "
+"the components, please refer to the appropriate chapter elsewhere in this "
+"document."
+msgstr ""
+"この章は概要のみとして意図されています。そしてより難しい細かい領域での 質問に"
+"は対応していません。このコンポーネントのより完璧な説明には、この ドキュメント"
+"にある他のより適切な章を参照して下さい。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Introduction.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Introduction.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Introduction.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,392 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr "はじめに"
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr "JBossTS Web トランザクションの概要"
+
+#. Tag: para
+#: Introduction.xml:9
+#, no-c-format
+msgid ""
+"The XML transaction service component of JBossTS (shorthand referred to as "
+"XTS) supports the coordination of private and public Web services in a "
+"business transaction. Therefore, to understand XTS, you must be familiar "
+"with Web services, and also understand a little about transactions. This "
+"chapter introduces XTS and provides a brief overview of the technologies "
+"that form the Web services standard. Additionally, this chapter explores "
+"some of the fundamentals of transactioning technology and how it can be "
+"applied to Web services. Much of the content presented in this chapter is "
+"detailed throughout this guide; however, only overview information about Web "
+"services is provided. If you are new to creating Web services, please see "
+"consult your Web services platform documentation."
+msgstr ""
+"JBossTS の XML トランザクションサービスコンポーネント（短縮名：XTS）は ビジネ"
+"ストランザクション内で個人と公共の Web サービスのコーディネイトをサポートしま"
+"す。 そのため、XTS を理解するには、Web サービスに熟知していて、トランザクショ"
+"ンの 知識が少々必要となります。この章では、XTS を紹介して Web サービス標準を"
+"形成する 技術の簡単な概要を提供します。更にこの章ではトランザクション技術の土"
+"台の一部と それが Web サービスに応用される方法を探求していきます。この章で案"
+"内される内容の ほとんどは、このガイド内に渡って詳細に説明がありますが、Web "
+"サービスに関する 概要情報のみが提供されます。Web サービスの作成の経験がない方"
+"は Web サービス プラットフォームドキュメントを参考にして下さい。"
+
+#. Tag: para
+#: Introduction.xml:12
+#, no-c-format
+msgid ""
+"JBossTS provides as the XTS component a transaction solution for Web "
+"services. Using XTS, business partners can coordinate complex business "
+"transactions in a controlled and reliable manner. The JBossTS Web Services "
+"API supports a transactional coordination model based on the WS-C, WS-Atomic "
+"Transaction and WS-Business Activity specifications. WS-C is a generic "
+"coordination framework developed by IBM, Microsoft and BEA, WS-Atomic "
+"Transaction and WS-Business Activity are transaction protocols that utilize "
+"this framework."
+msgstr ""
+"XTS コンポーネントとして JBossTS は Web サービスのトランザクションソリュー"
+"ションを 提供します。XTS を使用すると、ビジネスパートナーは複雑なビジネストラ"
+"ンザクションを 制御された信頼できる方法でコーディネイトできます。JBossTS  "
+"Web サービス API は、WS-C、WS-Atomic Transaction、及び WS-Business Activity "
+"の使用をベースにしたトランザクショナルコーディネイトモデルを サポートします。"
+"WS-C は IBM、Microsoft そして BEA によって開発された汎用コーディネイトフレー"
+"ムワークであり、 WS-Atomic Transaction と WS-Business Activity はこのフレーム"
+"ワークを使用するトランザクションプロトコルです。"
+
+#. Tag: para
+#: Introduction.xml:15
+#, no-c-format
+msgid ""
+"Web services are modular, reusable software components that are created by "
+"exposing business functionality through a Web service interface. Web "
+"services communicate directly with other Web services using standards-based "
+"technologies such as SOAP and HTTP. These standards-based communication "
+"technologies allow Web services to be accessed by customers, suppliers, and "
+"trading partners, independent of hardware operation system or programming "
+"environment. The result is a vastly improved collaboration environment as "
+"compared to today&#39;s EDI and business-to-business (B2B) solutions—an "
+"environment where businesses can expose their current and future business "
+"applications as Web services that can be easily discovered and accessed by "
+"external partners."
+msgstr ""
+"Web サービスはモジュラーな再利用可能なソフトウェアコンポーネントであり、 Web "
+"サービスインターフェイスを介してビジネス機能を具現化することで作成 されます。"
+"Web サービスは、SOAP や HTTP などの標準ベースの技術を使用した 他の Web サービ"
+"スと直接通信します。これらの標準ベースの通信技術の使用によって Web サービスが"
+"顧客や、供給元、取引パートナー、独立したハードウェアオペレーション、 あるいは"
+"プログラミング環境からアクセスされるようになります。その結果は、今日の EDI と"
+"ビジネス対ビジネス(B2B) ソリューションに比較して多大なコラボレーション環境の"
+"向上を見せます。これは、ビジネスがそれらの現在と将来のビジネスアプリケーショ"
+"ンを、外部のパートナーに 簡単に発見できてアクセスできる Web サービスとして表"
+"面化できる環境となります。 "
+
+#. Tag: para
+#: Introduction.xml:18
+#, no-c-format
+msgid ""
+"Web services, by themselves, are not fault tolerant. In fact, some of the "
+"reasons that make it an attractive development solution are also the same "
+"reasons that service-based applications may have drawbacks:"
+msgstr ""
+"Web はそれ自身では、障害許容力はありません。実際、それが魅力的な開発ソリュー"
+"ションになる 理由のいくつかは、サービスベースのアプリケーションが欠点を持って"
+"いる理由にもなります:"
+
+#. Tag: para
+#: Introduction.xml:23
+#, no-c-format
+msgid ""
+"Application components that are exposed as Web services may be owned by "
+"third parties, which provides benefits in terms of cost of maintenance, but "
+"drawbacks in terms of having exclusive control over their behavior;"
+msgstr ""
+"Web サービスとして表面化しているアプリケーションコンポーネントはサードパー"
+"ティで 所有できます。このことは維持コスト面で利便性を提供しますが、同時にそれ"
+"らの動作に 独占的制御を持つ点で欠点ともなります。"
+
+#. Tag: para
+#: Introduction.xml:28
+#, no-c-format
+msgid ""
+"Web services are usually remotely located which increases risk of failure "
+"due to increased network travel for invocations."
+msgstr ""
+"Web サービスは通常リモートに配置されており、呼び出しの為に増大したネットワー"
+"ク 伝達により失敗するリスクを増加します。"
+
+#. Tag: para
+#: Introduction.xml:33
+#, no-c-format
+msgid ""
+"Applications that have high dependability requirements, must find a method "
+"of minimizing the effects of errors that may occur when an application "
+"consumes Web services. One method of safeguarding against such failures is "
+"to interact with an application’s Web services within the context of a "
+"transaction. A transaction is simply a unit of work which is completed "
+"entirely, or in the case of failures is reversed to some agreed consistent "
+"state – normally to appear as if the work had never occurred in the first "
+"place. With XTS, transactions can span multiple Web services which mean that "
+"work performed across multiple enterprises can be managed with transactional "
+"support."
+msgstr ""
+"高い依存性の要求を持つアプリケーションは、アプリケーションが Web サービスを "
+"消費する時に起こる可能性のあるエラーの効果を最低限にするメソッドを見つける必"
+"要が あります。そのような障害に対する安全対策としての１つのメソッドは、トラン"
+"ザクションの コンテキスト内でアプリケーションの Web サービスと通信することで"
+"す。トランザクションは 簡単に表現すると、全面的に完了するか又は障害時には同意"
+"済みの一定の状態に戻るような作業の単位です。 一定の状態に戻る場合は通常、作業"
+"が最初から発生していないかのように見えます。XTS の使用では、 トランザクション"
+"は複数の Web サービスに広がり、これは複数の企業に渡って実行された作業が トラ"
+"ンザクショナルサポート内で管理できることを意味します。"
+
+#. Tag: title
+#: Introduction.xml:37
+#, no-c-format
+msgid "Managing Service-Based Processes"
+msgstr "サービスベースプロセスの管理"
+
+#. Tag: para
+#: Introduction.xml:38
+#, no-c-format
+msgid ""
+"XTS allows you to create transactions that drive complex business processes "
+"spanning multiple Web services. Current Web services standards do not "
+"address the requirements for a high-level coordination of services since in "
+"today’s Web services applications, which use single request/receive "
+"interactions, coordination is typically not a problem. However, for "
+"applications that engage multiple services among multiple business partners, "
+"coordinating and controlling the resulting interactions is essential. This "
+"becomes even more apparent when you realize that you generally have little "
+"in the way of formal guarantees when interacting with third-party Web "
+"services."
+msgstr ""
+"XTS の使用により、複数の Web サービスに広がる複雑なビジネスプロセスを駆動す"
+"る トランザクションを作成できるようになります。現在の Web サービス標準はサー"
+"ビスの ハイレベルなコーディネイトの為の要求に対処していません。これは、通信の"
+"単独の要求/受信を使用する 今日の Web サービスアプリケーション内では、コーディ"
+"ネイトは一般的に問題がないからです。しかし、 複数のビジネスパートナー間で複数"
+"のサービスに従事するアプリケーションにとっては、結果と して出る通信のコーディ"
+"ネイトと制御は重要になります。このことはサードパーティの Web サービスと 通信"
+"している場合に正式な保証についてはあまり期待できないことに気がつく時により明"
+"確に なります。"
+
+#. Tag: para
+#: Introduction.xml:42
+#, no-c-format
+msgid ""
+"XTS provides the infrastructure for coordinating services during a business "
+"process. By organizing processes as transactions, business partners can "
+"collaborate on complex business interactions in a reliable manner, insuring "
+"the integrity of their data - usually represented by multiple changes to a "
+"database – but without the usual overheads and drawbacks of directly "
+"exposing traditional transaction-processing engines directly onto the web. "
+"The following example demonstrates how an application may manage service-"
+"based processes as transactions:"
+msgstr ""
+"XTS はビジネスプロセス中にサービスのコーディネイトの為のインフラストラクチャ"
+"を提供します。 プロセスをトランザクションとして構成することにより、ビジネス"
+"パートナーは信頼出来る 方法で複雑なビジネスインタラクションに於けるコラボレー"
+"ションが可能になり、使用するデータの整合性を 確保することができます。これは通"
+"常データベースへの複数の変更で現れます。 しかし、web に対して直接伝統的なトラ"
+"ンザクション/プロセッシングエンジンを表面化する通常の運営負担と欠点がなくなり"
+"ます。以下の例では、アプリケーションが サービスベースのプロセスをトランザク"
+"ションとして管理する方法をデモンストレーションで 示します。 "
+
+#. Tag: para
+#: Introduction.xml:45
+#, no-c-format
+msgid ""
+"The application in question allows a user to plan a social evening. This "
+"application is responsible for reserving a table at a restaurant, and "
+"reserving tickets to a show. Both activities are paid for using a credit "
+"card. In this example, each service represents exposed Web services provided "
+"by different service providers. XTS is used to envelop the interactions "
+"between the theater and restaurant services into a single (potentially) long-"
+"running business transaction. The business transaction must insure that "
+"seats are reserved both at the restaurant and the theater. If one event "
+"fails the user has the ability to decline both events, thus returning both "
+"services back to their original state. If both events are successful, the "
+"user’s credit card is charged and both seats are booked. As you may expect, "
+"the interaction between the services must be controlled in a reliable manner "
+"over a period of time. In addition, management must span several third-party "
+"services that are remotely deployed."
+msgstr ""
+"例として使用するアプリケーションはユーザーがソシアルイベントを企画できるよう"
+"にします。 このアプリケーションはレストランのテーブル予約と観劇のチケット予約"
+"の担当をします。 両方の活動はクレジットカードの使用で支払いがされます。この例"
+"では、各サービスは 異なるサービスプロバイダによって提供される具現化した Web "
+"サービスを表現します。 XTS は劇場とレストランのサービスの間のインタラクション"
+"を１つの長期実行(可能性のある）ビジネス トランザクションへと封入するために使"
+"用されます。このビジネストランザクションは レストランと劇場の両方での座席が予"
+"約されることを保証しなければなりません。１方の イベントが成立しなければユー"
+"ザーは両方のイベントを拒否する能力があります。そうして 両方のサービスを元の状"
+"態に戻します。両方のイベントが成立できると、ユーザーのクレジット カードは"
+"チャージされて両方の座席が予約されます。お判りのように、両サービス間のインタ"
+"ラクションは ある期間に渡って信頼できる方法で制御される必要があります。さらに"
+"は、その管理はリモートで デプロイされるいくつかのサードパーティのサービスに広"
+"がる必要があります。"
+
+#. Tag: para
+#: Introduction.xml:49
+#, no-c-format
+msgid ""
+"Without the backing of a transaction, an undesirable outcome may occur. For "
+"example, the user credit card may be charged, even though one or both of the "
+"bookings may have failed."
+msgstr ""
+"トランザクションの後押しがないと、良くない結果が出る可能性があります。例え"
+"ば、 １方、又は両方の予約が不成立した場合でもユーザーのクレジットカードが"
+"チャージされたり するかもしれません。"
+
+#. Tag: para
+#: Introduction.xml:53
+#, no-c-format
+msgid ""
+"This simple example describes the situations where XTS excels at supporting "
+"business processes across multiple enterprises. This example is further "
+"refined throughout this guide, and appears as a standard demonstrator "
+"(including source code) with the XTS distribution."
+msgstr ""
+"この簡単な例は、複数の企業に渡ってビジネスプロセスをサポートすることに XTS が"
+"卓越している状況を表しています。この例はこのガイド内でより洗練 されて行きま"
+"す。そして XTS ディストリビューションでの標準のデモンストレーション として"
+"（ソースコードを含む）出現してきます。"
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr "Servlets"
+
+#. Tag: para
+#: Introduction.xml:58
+#, no-c-format
+msgid ""
+"The WS-C, WS-Atomic Transaction and WS-Business Activity protocols are based "
+"on one-way interactions of entities rather than traditional synchronous "
+"request/response RPC style interactions. Entities (for example, transaction "
+"participants) invoke operations on other entities (for example, the "
+"transaction coordinator) in order to return responses to requests. What this "
+"means is that the programming model is based on peer-to-peer relationships, "
+"with the result that all services, whether they are participants, "
+"coordinators or clients, must have an active component that allows them to "
+"receive unsolicited messages."
+msgstr ""
+"WS-C、WS-Atomic Transaction、及び WS-Business Activity のプロトコルは 伝統的"
+"な同期型要求/応答 RPC スタイルの通信ではなく、エンティティの一方通行の 通信を"
+"ベースにしています。エンティティ（例えば、トランザクションパーティシパント）"
+"は 要求に応答を返す為に他のエンティティ（例えば、トランザクションコーディネー"
+"タ）上の オペレーションを呼び出します。このことはプログラミングモデルが ピア"
+"対ピアの関係をベースにしていると言う意味になります。そして全てのサービス"
+"（パーティシパント、 コーディネータ、又はクライアント）が要求されてないメッ"
+"セージを受信できるように するアクティブコンポーネントを持つ必要があると言う結"
+"果になります。"
+
+#. Tag: para
+#: Introduction.xml:62
+#, no-c-format
+msgid ""
+"In the current implementation of XTS, the active component is achieved "
+"through the use of Java servlet technology. Each endpoint that can be "
+"communicated with via SOAP/XML is represented as a servlet (and published "
+"within JNDI). Fortunately for the developer, this use of servlets occurs "
+"transparently. The only drawback is that (currently) clients must reside "
+"within a domain capable of hosting servlets, i.e., an application server. It "
+"is our intention that future versions of XTS will provide configurable "
+"deployment options, allowing servlets where required, but not mandating them."
+msgstr ""
+"現在の XTS の実装では、アクティブコンポーネントは Java servlet 技術を通じて "
+"達成されます。SOAP/XML を通じて通信できる各終点は、servlet として表現 されて"
+"います（そして JNDI 内で発行されています）。開発者にとって幸運なことは "
+"servlet のこの使用が透過的に発生することです。唯一の欠点は（現時点で）クライ"
+"アントが servlet をホストする能力を持つドメイン（アプリケーションサーバー）内"
+"に存在する必要が あることです。XTS の将来のバージョンが設定可能なデプロイメン"
+"トオプションを提供して servlet を強制しないで必要であれば servlet を許可する"
+"ようにすることが意図されています。"
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr "SOAP"
+
+#. Tag: para
+#: Introduction.xml:67
+#, no-c-format
+msgid ""
+"SOAP has emerged as the de-facto message format for XML-based communication "
+"in the Web services arena. It is a lightweight protocol that allows the user "
+"to define the content of a message and to provide hints as to how recipients "
+"should process that message."
+msgstr ""
+"SOAPは、Web サービスの舞台で XML ベース通信用の実質的メッセージ形式として 出"
+"現しました。ユーザーがメッセージの内容を定義して、受信者がそのメッセージを プ"
+"ロセスする方法についてのヒントを提供できるようにする軽量のプロトコルです。"
+
+#. Tag: para
+#: Introduction.xml:71
+#, no-c-format
+msgid ""
+"SOAP messages can be divided into two main categories: Remote Procedure Call "
+"(RPC) and Document Exchange (DE). The primary difference between the two "
+"categories is that the SOAP specification defines encoding rules and "
+"conventions for RPC. The document exchange model allows the exchange of "
+"arbitrary XML documents - a key ingredient of B2B document exchange. XTS is "
+"based on the loosely coupled document-exchange style, yet it can support "
+"transactions spanning Web service that use either document-exchange or RPC."
+msgstr ""
+"SOAP メッセージは２つの主要カテゴリに分けることができます。リモート プロシー"
+"ジャコール(RPC) と ドキュメントエクスチェンジ(DE) です。この ２つのカテゴリの"
+"主たる相違は SOAP 仕様が RPC 用にエンコーディングルールと 慣習を定義すること"
+"です。ドキュメントエクスチェンジモデルにより、随意の XML ドキュメントの交換が"
+"できるようになります。B2B ドキュメント交換の 基幹要素です。XTS は大まかに組み"
+"合わされたドキュメント交換スタイルをベースに していますが、ドキュメント交換、"
+"あるいは RPC を使用する Web サービス広範に 渡ってトランザクションをサポートで"
+"きます。"
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr "Web サービス記述言語 (WSDL)"
+
+#. Tag: para
+#: Introduction.xml:76
+#, no-c-format
+msgid ""
+"WSDL is an XML-based language used to define Web service interfaces. An "
+"application that consumes a Web service parses the service’s WSDL document "
+"to discover the location of the service, the operations that the service "
+"supports, the protocol bindings the service supports (SOAP, HTTP, etc), and "
+"how to access them (for each operation, WSDL describes the format that the "
+"client must follow)."
+msgstr ""
+"WSDL は、 Web サービスインターフェイスを定義するのに 使用される XML ベースの"
+"言語です。Web サービスを消費するアプリケーションは サービスの WSDL ドキュメン"
+"トを構文解析してサービスの場所、サービスが サポートするオペレーション、サービ"
+"スがサポートするプロトコル構築 (SOAP, HTTP, など)、 そして、それらにアクセス"
+"する方法を発見します（それぞれのオペレーションに、WSDL は クライアントが従う"
+"べき形式を表示します）。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
===================================================================

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Participants.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Participants.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Participants.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,618 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Participants.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "テスト"
+
+#. Tag: para
+#: Participants.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "これはテストの段落です"
+
+#. Tag: title
+#: Participants.xml:11
+#, no-c-format
+msgid "The Participant: an Overview"
+msgstr "パーティシパント: その概要"
+
+#. Tag: para
+#: Participants.xml:12
+#, no-c-format
+msgid ""
+"The participant is the entity that performs the work pertaining to "
+"transaction management on behalf of the business services involved in an "
+"application. The Web service (for example, a theatre booking system) "
+"contains some business logic for reserving a seat, enquiring availability "
+"etc, but it will need to be supported by something that maintains "
+"information in a durable manner. Typically this will be a database, but it "
+"could be a file system, NVRAM, etc. Now, although the service may talk to "
+"the back-end database directly, it cannot commit or undo any changes it (the "
+"services) makes, since these are ultimately under the control of the "
+"transaction that scoped the work. In order for the transaction to be able to "
+"exercise this control, it must have some contact with the database. In XTS "
+"this is accomplished by the participant, and the role played by the "
+"participant between the transaction and back-end transaction processing "
+"infrastructure is shown in the following figure."
+msgstr ""
+"パーティシパントとは、トランザクション管理に属する作業を実行するエンティティ"
+"であり、 これはアプリケーションに関与しているビジネスサービスを代表するもので"
+"す。Web サービス （例えば、劇場予約システム）には、座席の予約、問い合わせ機能"
+"などの為のいくつかの ビジネス論理が含まれていますが、それは恒久的な方法で情報"
+"を維持できるものでサポート されている必要があります。一般的にはそれはデータ"
+"ベースでしょう。しかしファイルシステム、 NVRAM、などでもあり得ます。そのサー"
+"ビスは直接バックエンドデータベースと通信するかも しれませんが、最終的にはその"
+"作業の範囲を受け持つトランザクションの制御下にあるため、 サービスはそれ自身が"
+"行う変更をコミットしたり取り戻したりすることは出来ません。 トランザクションが"
+"このような制御を実践できるようになるには、データベースとなんらかの接触を 持つ"
+"必要があります。 XTS では、これがパーティシパントによって実現されます。そし"
+"て そのトランザクションと、インフラストラクチャをプロセスしているバックエンド"
+"トランザクション との間で果たすパーティシパントの役目は以下の図に示してありま"
+"す。"
+
+#. Tag: caption
+#: Participants.xml:19
+#, no-c-format
+msgid "Transactions, Participants, and Back-End Transaction Control"
+msgstr ""
+"トランザクション、パーティシパント、そしてバックエンドトランザクション制御"
+
+#. Tag: para
+#: Participants.xml:21
+#, no-c-format
+msgid ""
+"Each participant in XTS is related to either the Atomic Transaction or "
+"Business Activity protocols. In the following sections we’ll consider both "
+"protocols and their respective participants."
+msgstr ""
+"XTS 内の各パーティシパントは Atomic Transaction か Business Activity の いず"
+"れかのプロトコルに関連しています。以下のセクションでは、これらの 両方のプロト"
+"コルとそれらのそれぞれのパーティシパントを考慮していきます。"
+
+#. Tag: title
+#: Participants.xml:25
+#, no-c-format
+msgid "Atomic Transaction"
+msgstr "アトミックトランザクション"
+
+#. Tag: para
+#: Participants.xml:26
+#, no-c-format
+msgid ""
+"All Atomic Transaction participants are instances of one of the following "
+"interfaces."
+msgstr ""
+"全ての Atomic Transaction パーティシパントは以下のインターフェイスの内の １つ"
+"のインスタンスです。"
+
+#. Tag: title
+#: Participants.xml:31
+#, no-c-format
+msgid "Durable2PCParticipant"
+msgstr "Durable2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:32
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Durable2PC protocol with "
+"the following signatures, as per the <interfacename>com.arjuna.wst."
+"Durable2Participant</interfacename> interface:"
+msgstr ""
+"このパーティシパントは、<interfacename>com.arjuna.wst.Durable2Participant</"
+"interfacename> インターフェイスと同様に 以下のシグニチャを使用して、WS-"
+"Atomic Transaction Durable2PC プロトコルを サポートします:"
+
+#. Tag: para
+#: Participants.xml:38
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the <code>com.arjuna.wst."
+"Vote</code>. Values are: <code>ReadOnly</code>, indicating the participant "
+"does not need to be informed of the transaction outcome as no state updates "
+"were made; Prepared, indicating the participant is prepared to commit or "
+"rollback depending on the final transaction outcome, and it has made "
+"sufficient state updates persistent to accomplish this; and Aborted, "
+"indicating the participant has aborted and the transaction should also "
+"attempt to do so."
+msgstr ""
+"<emphasis>prepare</emphasis>: パーティシパントはトランザクションの範囲内で "
+"Web サービスが実行する作業をコミット又はロールバックできるようするために要す"
+"る いずれかの作業を実行する必要があります。その実装はそれとコーディネータ間の"
+"暗黙の 契約を実現するために必要なことを自由に実行できます。パーティシパントは"
+"その準備が できるかどうかを提示するために  <code>com.arjuna.wst.Vote</code> "
+"のインスタンスを 返すことが期待されています。値 <code>ReadOnly</code> は状態"
+"の更新がない為に パーティシパントがトランザクションの結果連絡を受ける必要がな"
+"いことを示し、値 <code>Prepared</code> は トランザクションの最終結果によって"
+"はトランザクションがコミット又はロールバックをする準備があり、 これを達成する"
+"ために十分な状態更新を永続化したことを示します。値 <code>Aborted</code> は、 "
+"パーティシパントが中止しており、トランザクションもそうすべきであることを示し"
+"ます。"
+
+#. Tag: para
+#: Participants.xml:43 Participants.xml:81
+#, no-c-format
+msgid ""
+"<emphasis>commit</emphasis>: the participant should make permanent the work "
+"that it controls. What it does will depend upon its implementation, for "
+"example, commit the reservation of the theatre ticket. The participant will "
+"then return an indication of whether or not it succeeded."
+msgstr ""
+"<emphasis>commit</emphasis>: パーティシパントはそれが制御する作業を永久化 し"
+"なければなりません。それが行うことはその実装に左右されます。例えば、劇場用チ"
+"ケットの 予約をコミットするなど。パーティシパントはその後、そのコミットが成功"
+"したかどうかの 表示を返します。"
+
+#. Tag: para
+#: Participants.xml:48 Participants.xml:86
+#, no-c-format
+msgid ""
+"<emphasis>rollback</emphasis>: the participant should undo the work that it "
+"controls. The participant will then return an indication of whether or not "
+"it succeeded."
+msgstr ""
+"<emphasis>rollback</emphasis>: パーティシパントはそれが制御する作業を元に 戻"
+"します。パーティシパントはその後、それが成功したかどうかの表示を返します。"
+
+#. Tag: para
+#: Participants.xml:53 Participants.xml:91
+#, no-c-format
+msgid ""
+"<emphasis>commitOnePhase</emphasis>: if there is only a single "
+"TwoPCParticipant registered with the transaction, then the coordinator can "
+"optimize the protocol and simply tell the participant to commit: there is no "
+"need for a preparatory phase since consensus is implicit."
+msgstr ""
+"<emphasis>commitOnePhase</emphasis>: ただ１つの TwoPCParticipant が トランザ"
+"クションで登録されている場合、コーディネータはそのプロトコルを最適化 して、単"
+"にそのパーティシパントにコミットするように指示します。暗黙の同意があるため、"
+"準備の段階は必要ありません。"
+
+#. Tag: para
+#: Participants.xml:58 Participants.xml:96
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: during recovery the participant can inquire as "
+"to the status of the transaction it was registered with. If that transaction "
+"is no longer available (has rolled back) then this operation will be invoked "
+"by the coordination service."
+msgstr ""
+"<emphasis>unknown</emphasis>: リカバリの期間中に、パーティシパントはそれが 登"
+"録してあるトランザクションの状態を問い合わせることができます。トランザクショ"
+"ンが 使用不可になっている場合（ロールバックした場合）、このオペレーションは"
+"コーディネーション サービスによって呼び出されます。"
+
+#. Tag: para
+#: Participants.xml:63 Participants.xml:101
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: during recovery the participant can enquire as "
+"to the status of the transaction it was registered with. If an error occurs "
+"(for example, the transaction service is unavailable) then this operation "
+"will be invoked."
+msgstr ""
+"<emphasis>error</emphasis>: リカバリの期間中に、パーティシパントはそれが 登録"
+"してあるトランザクションの状態を問い合わせることができます。エラーが発生 （例"
+"えば、トランザクションサービスが利用不可）した場合、このオペレーションが 呼び"
+"出されます。 "
+
+#. Tag: title
+#: Participants.xml:69
+#, no-c-format
+msgid "Volatile2PCParticipant"
+msgstr "Volatile2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:70
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Volatile2PC protocol "
+"with the following signatures, as per the <interfacename>com.arjuna.wst."
+"Volatile2Participant</interfacename> interface:"
+msgstr ""
+"このパーティシパントは <interfacename>com.arjuna.wst.Volatile2Participant</"
+"interfacename> インターフェイスと同様に、 以下のシグニチャを使用して WS-"
+"Atomic Transaction Volatile2PC プロトコルを サポートします:"
+
+#. Tag: para
+#: Participants.xml:76
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the com.arjuna.wst.Vote. "
+"Values are: ReadOnly, indicating the participant does not need to be "
+"informed of the transaction outcome as no state updates were made; Prepared, "
+"indicating the participant is prepared to commit or rollback depending on "
+"the final transaction outcome, and it has made sufficient state updates "
+"persistent to accomplish this; and Aborted, indicating the participant has "
+"aborted and the transaction should also attempt to do so."
+msgstr ""
+"<emphasis>prepare</emphasis>: パーティシパントはトランザクションの範囲内で "
+"Web サービスが実行する作業をコミット又はロールバックできるようするために要す"
+"る いずれかの作業を実行する必要があります。その実装はそれとコーディネータ間の"
+"暗黙の 契約を実現するために必要なことを自由に実行できます。パーティシパントは"
+"その準備が できるかどうかを提示するために  <code>com.arjuna.wst.Vote</code> "
+"のインスタンスを 返すことが期待されています。値 <code>ReadOnly</code> は状態"
+"の更新がない為に パーティシパントがトランザクションの結果連絡を受ける必要がな"
+"いことを示し、値 <code>Prepared</code> は トランザクションの最終結果によって"
+"はトランザクションがコミット又はロールバックをする準備があり、 これを達成する"
+"ために十分な状態更新を永続化したことを示します。値 <code>Aborted</code> は、 "
+"パーティシパントが中止しており、トランザクションもそうすべきであることを示し"
+"ます。"
+
+#. Tag: title
+#: Participants.xml:107
+#, no-c-format
+msgid "Business Activity"
+msgstr "ビジネス活動"
+
+#. Tag: para
+#: Participants.xml:108
+#, no-c-format
+msgid ""
+"All Business Activity participants are instances of the following interfaces."
+msgstr ""
+"全てのビジネス活動のパーティシパントは、以下のインターフェイスのインスタンス"
+"です。"
+
+#. Tag: title
+#: Participants.xml:113
+#, no-c-format
+msgid "BusinessAgreementWithParticipantCompletion"
+msgstr "BusinessAgreementWithParticipantCompletion"
+
+#. Tag: para
+#: Participants.xml:114
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"このパーティシパントは <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename> イン"
+"ターフェイスに 準じて以下のシグニチャを使用して WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> プロトコルをサポート"
+"します。"
+
+#. Tag: para
+#: Participants.xml:120 Participants.xml:158
+#, no-c-format
+msgid ""
+"<emphasis>close</emphasis>: the transaction has completed successfully. The "
+"participant previously informed the coordinator that it was ready to "
+"complete."
+msgstr ""
+"<emphasis>close</emphasis>: トランザクションは正常に完了しました。パーティシ"
+"パントは 以前に完了準備が出来ていることをコーディネータに伝えています。"
+
+#. Tag: para
+#: Participants.xml:125
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work. The participant cannot have informed the "
+"coordinator that it has completed."
+msgstr ""
+"<emphasis>cancel</emphasis>: トランザクションはキャンセルされました。 そし"
+"て、パーティシパントはその作業を元に戻す必要があります。パーティシパントは 作"
+"業が完了したとコーディネータに通達できません。"
+
+#. Tag: para
+#: Participants.xml:130 Participants.xml:168
+#, no-c-format
+msgid ""
+"<emphasis>compensate</emphasis>: the transaction has canceled. The "
+"participant previously informed the coordinator that it had finished work "
+"but could compensate later if required, so it is now requested to do so."
+msgstr ""
+"<emphasis>compensate</emphasis>: トランザクションはキャンセルされました。 "
+"パーティシパントは以前にコーディネータに対してその作業が終了したことと 必要で"
+"あれば後でそれを補正出来ることを告げています。そこでパーティシパントは 今そう"
+"するように要求されています。"
+
+#. Tag: para
+#: Participants.xml:135 Participants.xml:178
+#, no-c-format
+msgid "<emphasis>status</emphasis>: return the status of the participant."
+msgstr "<emphasis>status</emphasis>: パーティシパントのステータスを返します"
+
+#. Tag: para
+#: Participants.xml:140 Participants.xml:183
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: if the participant inquires as to the status "
+"of the transaction it was registered with and that transaction is no longer "
+"available (has rolled back) then this operation will be invoked by the "
+"coordination service."
+msgstr ""
+"<emphasis>unknown</emphasis>: パーティシパントがそれが登録してある トランザク"
+"ションの状態を問い合わせして、そのトランザクションがもう利用 できない（ロール"
+"バックされている）場合、このオペレーションがコーディネーションサービスによっ"
+"て呼び出されます。"
+
+#. Tag: para
+#: Participants.xml:145 Participants.xml:188
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: if the participant enquired as to the status of "
+"the transaction it was registered with and an error occurs (for example, the "
+"transaction service is unavailable) then this operation will be invoked."
+msgstr ""
+"<emphasis>error</emphasis>: パーティシパントがそれが登録してある トランザク"
+"ションの状態を問い合わせして、エラーが発生した（例えば、 トランザクションサー"
+"ビスが利用不可になった）場合、このオペレーションが 呼び出されます。"
+
+#. Tag: title
+#: Participants.xml:151
+#, no-c-format
+msgid "BusinessAgreementWithCoordinatorCompletion"
+msgstr "BusinessAgreementWithCoordinatorCompletion"
+
+#. Tag: para
+#: Participants.xml:152
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"<interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename> と同様"
+"に パーティシパントは 以下のシグニチャを使用して WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> プロトコルを サポート"
+"します:"
+
+#. Tag: para
+#: Participants.xml:163
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work."
+msgstr ""
+"<emphasis>cancel</emphasis>: トランザクションはキャンセルされました。そして "
+"パーティシパントは全ての作業を元に戻す必要があります。"
+
+#. Tag: para
+#: Participants.xml:173
+#, no-c-format
+msgid ""
+"<emphasis>complete</emphasis>: the coordinator is informing the participant "
+"that all work it needs to do within the scope of this business activity has "
+"been received."
+msgstr ""
+"<emphasis>complete</emphasis>: コーディネータはパーティシパントに対して この"
+"ビジネス活動の有効範囲内で実行する必要のある全ての作業が受理されたことを 伝え"
+"ています。"
+
+#. Tag: title
+#: Participants.xml:194
+#, no-c-format
+msgid "BAParticipantManager"
+msgstr "BAParticipantManager"
+
+#. Tag: para
+#: Participants.xml:195
+#, no-c-format
+msgid ""
+"In order for the Business Activity protocol to work correctly, the "
+"participants must be able to autonomously signal the coordinator that they "
+"have left the activity (exited) or are ready to complete and (if necessary) "
+"compensate (completed). Unlike the Atomic Transaction protocol, where all "
+"interactions between the coordinator and participants are instigated by the "
+"coordinator when the transaction terminates, this interaction pattern "
+"requires the participant to be able to talk to the coordinator at any time "
+"during the lifetime of the business activity."
+msgstr ""
+"Business Activity プロトコルが正しく機能するためには、パーティシパントは 活動"
+"を停止した（退去した）こと、又は完了する準備があることそして（必要なら） 補正"
+"する（完了する）ことを自主的にコーディネータに信号送信する必要があります。 "
+"パーティシパントとコーディネータとの間の全ての通信が、トランザクションの終結"
+"時に コーディネータによって主導される Atomic Transaction プロトコルとは異な"
+"り、この 通信パターンでは、ビジネス活動の期間中にはいつでもパーティシパントが"
+"コーディネータに 話しかけることが出来るように要求されています。"
+
+#. Tag: para
+#: Participants.xml:199
+#, no-c-format
+msgid ""
+"As such, whenever a participant is registered with a business activity, it "
+"receives a handle on the coordinator. This handle is an instance of the "
+"<interfacename>BAParticipantManager</interfacename> interface, located in "
+"<code>com.arjuna.wst.BAParticipantManager</code>, with the following methods:"
+msgstr ""
+"このようにして、パーティシパントが１つのビジネス活動に登録してあるかにより、 "
+"それはコーディネータのハンドルを受理します。このハンドルは "
+"<interfacename>BAParticipantManager</interfacename> インターフェイスの インス"
+"タンスで、以下のメソッドを使用して <code>com.arjuna.wst."
+"BAParticipantManager</code> に 配置されています:"
+
+#. Tag: para
+#: Participants.xml:204
+#, no-c-format
+msgid ""
+"<emphasis>exit</emphasis>: the participant has exited the business activity. "
+"The participant uses this to inform the coordinator that is has left the "
+"activity. It will not be informed when (and how) the business activity "
+"terminates."
+msgstr ""
+"<emphasis>exit</emphasis>: パーティシパントはこのビジネス活動から 退去しまし"
+"た。パーティシパントはこれを使用して活動を退去したことを コーディネータに通達"
+"します。ビジネス活動が終了する時（及び方法）に 関しては通達されません。"
+
+#. Tag: para
+#: Participants.xml:209
+#, no-c-format
+msgid ""
+"<emphasis>completed</emphasis>: the participant has completed it works, but "
+"wishes to continue in the business activity, so that it will eventually be "
+"told when (and how) the activity terminates. The participant may later be "
+"asked to compensate for the work it has done."
+msgstr ""
+"<emphasis>completed</emphasis>: パーティシパントは作業を完了しましたが、 その"
+"ビジネス活動を継続する意志を持ちます。そこでパーティシパントは最終的に 活動を"
+"終結する時（及びその方法）を告げられます。パーティシパントは後で、 それが終了"
+"した完了の補正を依頼されるかもしれません。"
+
+#. Tag: para
+#: Participants.xml:214
+#, no-c-format
+msgid ""
+"<emphasis>fault</emphasis>: the participant encountered an error during "
+"normal activation and has compensated. This places the business activity "
+"into a mandatory cancel-only mode."
+msgstr ""
+"<emphasis>fault</emphasis>: パーティシパントは通常の活動中に エラーに遭遇して"
+"それを補正しました。これがビジネス活動を義務的な キャンセルオンリーモードに配"
+"置します。"
+
+#. Tag: title
+#: Participants.xml:222
+#, no-c-format
+msgid "Participant Creation and Deployment"
+msgstr "パーティシパントの作成とデプロイメント"
+
+#. Tag: para
+#: Participants.xml:223
+#, no-c-format
+msgid ""
+"As has been shown, the participant provides the plumbing that drives the "
+"transactional aspects of the service. This section discusses the specifics "
+"of Participant programming and usage."
+msgstr ""
+"以前に示してあるように、パーティシパントはサービスのトランザクション側面を 駆"
+"動する配管構成を提供します。このセクションはパーティシパントのプログラミング"
+"と その使用法の仕様について説明しています。"
+
+#. Tag: title
+#: Participants.xml:227
+#, no-c-format
+msgid "Implementing Participants"
+msgstr "パーティシパントの実装"
+
+#. Tag: para
+#: Participants.xml:228
+#, no-c-format
+msgid ""
+"Implementing a participant is, in theory, a relatively straightforward task, "
+"though depending on the complexity of the transactional infrastructure that "
+"the participant is to manage, the actual size and complexity of a "
+"participant will vary. The participant interfaces can be found under "
+"<code>com.arjuna.wst</code>. Your implementation must implement one of these "
+"interfaces."
+msgstr ""
+"パーティシパントの実装は、理論的には比較的に直線的で単純なタスクですが、 パー"
+"ティシパントが管理することになるトランザクションのインフラストラクチャの複雑"
+"さに よってはパーティシパントの実際のサイズと複雑さは変化します。パーティシパ"
+"ントインターフェイス群は <code>com.arjuna.wst</code> の下に配置されています。"
+"この実装はそれらのインターフェイスの１つを 実装しなければなりません。"
+
+#. Tag: title
+#: Participants.xml:233
+#, no-c-format
+msgid "Deploying Participants"
+msgstr "パーティシパントのデプロイ実行"
+
+#. Tag: para
+#: Participants.xml:234
+#, no-c-format
+msgid ""
+"In order to allow Participants to be located remote from the Transaction "
+"Manager, XTS includes transparent message routing functionality. The "
+"Participant classes are not exposed directly as web services, but rather "
+"registered with a web service which receives messages from the Transaction "
+"Manager and maps them to appropriate method invocations on the relevant "
+"Participant instance. Transactional web services will typically enroll a new "
+"Participant instance of the desired type for each new transaction. A unique "
+"identifier must be provided at enrollment time and will be used to map "
+"transaction protocol messages to the appropriate participant instance. Note "
+"that Participant method invocations do not occur in a specific transaction "
+"context. Therefore, if your Participant implementation requires knowledge of "
+"the transaction context (for example, to look up state information in a "
+"persistent store) then you should provide this to the Participant instance, "
+"typically as an argument to the constructor function. Sample Participant "
+"implementations and usage can be found in the demonstration application "
+"included with XTS."
+msgstr ""
+"トランザクションマネージャからリモートに配置されるようにパーティシパントを 許"
+"可するために、XTS には、透過的なメッセージ巡回機能が含まれています。 パーティ"
+"シパントクラスは直接 web サービスのように表面化していません。しかし、 トラン"
+"ザクションマネージャからメッセージを受信して、関連のあるパーティシパント イン"
+"スタンス上の適切なメソッド呼び出しにそれらをマップする web サービスに登録され"
+"て います。トランザクショナル web サービスは一般的に各新規のトランザクション"
+"用に 好ましいタイプのパーティシパントを採用します。特有の識別子がその採用時に"
+"用意されて トランザクションプロトコルメッセージを適切なパーティシパントインス"
+"タンスにマップする のに使用されなければなりません。パーティシパントメソッドの"
+"呼び出しは特定のトランザクション コンテキストでは発生しないことに注意して下さ"
+"い。そのため、使用中のパーティシパント実装が トランザクションコンテキストの知"
+"識を 必要とする場合（例えば、永続化ストア内の状態情報を見るためなど）、 それ"
+"を一般的にコンストラクタ関数への引数としてパーティシパントインスタンスに 提供"
+"しなければなりません。サンプルのパーティシパント実装とその使用法は XTS に収納"
+"されている デモンストレーションアプリケーションで見ることが出来ます。"
+
+#. Tag: para
+#: Participants.xml:238
+#, no-c-format
+msgid ""
+"Any application code which creates and enrolls Participants must be deployed "
+"along with the parts of XTS necessary for receiving and processing incoming "
+"messages from the Transaction Manager. This typically means including the "
+"appropriate XTS .jar, .wsr and .war files in your application. If you are "
+"deploying your application only a server which does not already contain a "
+"Transaction Manger installation, you will also need to deploy the XTS "
+"configuration files."
+msgstr ""
+"パーティシパントを作成して採用するいずれかのアプリケーションコードは、 トラン"
+"ザクションマネージャからの来信メッセージを受け取り、プロセスするために 必要"
+"な XTS のパーツと共にデプロイされなければなりません。このことは一般的に 適切"
+"な XTS .jar、.wsr  と .war のファイルを使用アプリケーションに含んでいること"
+"を 意味します。使用アプリケーションをトランザクションマネージャインストールの"
+"ない サーバーでデプロイする場合は、XTS 設定ファイルもデプロイする必要がありま"
+"す。"
+
+#. Tag: para
+#: Participants.xml:242
+#, no-c-format
+msgid ""
+"In early access releases of the XTS product, the Transaction Manager and "
+"participant management functions are not provided as separable components. "
+"Configuration and deployment of the participant infrastructure is therefore "
+"as in the Transaction Manger section above. More flexible deployment of the "
+"XTS components will be available in the final release."
+msgstr ""
+"XTS 製品の初期のアクセスリリースでは、トランザクションマネージャとパーティシ"
+"パント 管理機能は別々のコンポーネントとして提供されていました。パーティシパン"
+"トインフラストラクチャの 設定とデプロイメントはその為、上記のトランザクション"
+"マネージャセクション内にあるものと同様です。 XTS コンポーネントのより柔軟なデ"
+"プロイメントが最終リリースで利用可能になります。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Preface.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Preface.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr "序文"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Revision_History.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Revision_History.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,29 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "改訂履歴"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Stand-alone_Coordinator.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Stand-alone_Coordinator.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Stand-alone_Coordinator.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,39 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:6
+#, no-c-format
+msgid "Stand-alone Coordinator"
+msgstr "スタンドアローンコーディネータ"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "はじめに"
+
+#. Tag: para
+#: Stand-alone_Coordinator.xml:9
+#, no-c-format
+msgid ""
+"For configuring a stand-alone Web Services transaction coordinator, see the "
+"relevant chapter in the System Administrator’s Guide."
+msgstr ""
+"スタンドアローンの Web サービストランザクションコーディネータの設定には、 シ"
+"ステム管理ガイド内の関連した章をご覧下さい。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/The_XTS_API.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/The_XTS_API.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/The_XTS_API.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,745 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr "XTS API"
+
+#. Tag: title
+#: The_XTS_API.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "はじめに"
+
+#. Tag: para
+#: The_XTS_API.xml:9
+#, no-c-format
+msgid ""
+"This chapter shows how to use the XTS API. This is of use both at the client-"
+"side where applications consume transactional Web services, and at the "
+"service/participant side where transactions need to be coordinated with back-"
+"end systems."
+msgstr ""
+"この章では XTS API の使用法を案内しています。これはアプリケーションが トラン"
+"ザクショナル Web サービスを消費するクライアントサイドと、トランザクションが "
+"バックエンドシステムと同調している必要のあるサービス/クライアントサイドの両方"
+"での 使用についての案内です。"
+
+#. Tag: title
+#: The_XTS_API.xml:15
+#, no-c-format
+msgid "API for the Atomic Transaction protocol"
+msgstr "Atomic Transaction プロトコルのための API"
+
+#. Tag: para
+#: The_XTS_API.xml:16
+#, no-c-format
+msgid ""
+"The following classes and interfaces are located within the <package>com."
+"arjuna.wst or com.arjuna.mw.wst</package> packages and sub-packages."
+msgstr ""
+"以下のクラスとインターフェイスは <package>com.arjuna.wst or com.arjuna.mw."
+"wst</package> パッケージとサブパッケージ内に あります。"
+
+#. Tag: title
+#: The_XTS_API.xml:20
+#, no-c-format
+msgid "Vote"
+msgstr "投票"
+
+#. Tag: para
+#: The_XTS_API.xml:21
+#, no-c-format
+msgid ""
+"During the two-phase commit protocol, a participant will be asked to vote on "
+"whether or not it can prepare to confirm the work that it controls. It must "
+"return one of the following subtypes of <code>com.arjuna.wst.Vote</code>:"
+msgstr ""
+"２段階コミットプロトコルの間、パーティシパントはそれが制御する作業を確認でき"
+"る 準備があるかどうかについて投票するように依頼されます。以下のような "
+"<code>com.arjuna.wst.Vote</code> の サブタイプを返さなければなりません:"
+
+#. Tag: para
+#: The_XTS_API.xml:27
+#, no-c-format
+msgid ""
+"<emphasis>Prepared</emphasis>: the participant indicates that it can prepare "
+"if asked to by the coordinator. It will not have committed at this stage "
+"however, since it does not know what the final outcome will be."
+msgstr ""
+"<emphasis>Prepared</emphasis>: パーティシパントはそれがコーディネータに 依頼"
+"されれば準備ができていることを示します。この段階ではパーティシパントはまだ 最"
+"終的結果を知らないため、コミットしていません。"
+
+#. Tag: para
+#: The_XTS_API.xml:32
+#, no-c-format
+msgid ""
+"<emphasis>Aborted</emphasis>: the participant indicates that it cannot "
+"prepare and has in fact rolled back. The participant should not expect to "
+"get a second phase message."
+msgstr ""
+"<emphasis>Aborted</emphasis>: パーティシパントは準備できないこと、そして 実際"
+"にロールバックしたことを示します。パーティシパントは２段階目のメッセージを 受"
+"ける期待はできません。"
+
+#. Tag: para
+#: The_XTS_API.xml:37
+#, no-c-format
+msgid ""
+"<emphasis>ReadOnly</emphasis>: the participant indicates that the work it "
+"controls has not made any changes to state that require it to be informed of "
+"the final outcome of the transaction. Essentially the participant is "
+"resigning from the transaction."
+msgstr ""
+"<emphasis>ReadOnly</emphasis>: パーティシパントはそれが制御する作業が トラン"
+"ザクションの最終結果ついて情報を受ける必要のあるような状態の変化をしていない "
+"ことを示します。基本的にパーティシパントはトランザクションから退去していま"
+"す。"
+
+#. Tag: para
+#: The_XTS_API.xml:42
+#, no-c-format
+msgid ""
+"Thus a possible implementation of a 2PC participant’s prepare method may "
+"resemble the following:"
+msgstr ""
+"このようにして、2PC パーティシパントの prepare メソッドの可能な実装は以下に "
+"似たものになります:"
+
+#. Tag: screen
+#: The_XTS_API.xml:45
+#, no-c-format
+msgid ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+msgstr ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+
+#. Tag: title
+#: The_XTS_API.xml:47
+#, no-c-format
+msgid "The transaction context"
+msgstr "トランザクションコンテキスト"
+
+#. Tag: para
+#: The_XTS_API.xml:48
+#, no-c-format
+msgid ""
+"A transaction is typically represented by some unique identifier and a "
+"reference to the coordinator which manages the transaction, for example, a "
+"URL. XTS allows transactions to be nested such that a transaction hierarchy "
+"(tree) may be formed. Thus, a transaction context may be a set of "
+"transactions, with the top-most transaction the root parent (superior)."
+msgstr ""
+"トランザクションは標準的に特有の識別子と、トランザクションを管理する コーディ"
+"ネータへの参照（例えば、URL）とで表現されます。XTS はトランザクションが ネス"
+"ト化できるようにしてトランザクション階層（ツリー）が形成できるようにします。 "
+"そのため、トランザクションコンテキストは、ルートペアレントである最上部のトラ"
+"ンザクションを 持つトランザクション群であることができます。"
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr "TxContext"
+
+#. Tag: para
+#: The_XTS_API.xml:54
+#, no-c-format
+msgid ""
+"<code>com.arjuna.mw.wst.TxContext</code> is an opaque representation of a "
+"transaction context."
+msgstr ""
+"<code>com.arjuna.mw.wst.TxContext</code> はトランザクションコンテキストの 不"
+"明瞭な表現です。"
+
+#. Tag: para
+#: The_XTS_API.xml:60
+#, no-c-format
+msgid ""
+"<emphasis>valid</emphasis>: this indicates whether or not the contents are "
+"valid."
+msgstr ""
+"<emphasis>valid</emphasis>: これはコンテンツが有効であるかないかを示します。"
+
+#. Tag: para
+#: The_XTS_API.xml:65
+#, no-c-format
+msgid "<emphasis>equals</emphasis>: can be used to compare two instances."
+msgstr ""
+"<emphasis>equals</emphasis>: ２つのインスタンスを比較するのに使用されます。"
+
+#. Tag: title
+#: The_XTS_API.xml:71
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: The_XTS_API.xml:72
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserTransaction</classname> is the class that "
+"most users (for example, clients and services) will see. This isolates them "
+"from the underlying protocol-specific aspects of the XTS implementation. "
+"Importantly, a UserTransaction does not represent a specific transaction, "
+"but rather is responsible for providing access to an implicit per-thread "
+"transaction context; it is similar to the UserTransaction in the JTA "
+"specification. Therefore, all of the UserTransaction methods implicitly act "
+"on the current thread of control."
+msgstr ""
+"<classname>com.arjuna.wst.UserTransaction</classname> はほとんどのユーザー "
+"（例えば、クライアントとサービス）が見ることになるクラスです。これは XTS 実装"
+"の 背後にあるプロトコル特有の側面からそれらのユーザー達を隔離します。重要なこ"
+"とは、 UserTransaction が特定のトランザクションを表現するのではなく、むしろ暗"
+"黙了解の スレッド単位トランザクションコンテキストにアクセスを提供する役目を持"
+"ちます。 このことは、JTA 仕様の UserTransaction に似ています。そのため、全て"
+"の UserTransaction メソッドは必然的に制御の現在のスレッド上で行動します。"
+
+#. Tag: para
+#: The_XTS_API.xml:76
+#, no-c-format
+msgid ""
+"A new transaction is begun and associated with the invoking thread by using "
+"the begin method. If there is already a transaction associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created transaction with the "
+"current thread."
+msgstr ""
+"begin メソッドを使用して新規のトランザクションが開始されて呼び出すスレッドと "
+"関連づけされます。このスレッドに関連づけのあるトランザクションが既に存在する"
+"場合は、 <code>WrongStateException</code> 例外が送出されます。正しく開始され"
+"ると、 このオペレーションは新規に作成されたトランザクションを現在のスレッドに"
+"関連づけします"
+
+#. Tag: para
+#: The_XTS_API.xml:79
+#, no-c-format
+msgid ""
+"The transaction is committed by the commit method. This will execute the "
+"Volatile2PC and Durable2PC protocols prior to returning. If there is no "
+"transaction associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. If the transaction "
+"ultimately rolls back then the <code>TransactionRolledBackException</code> "
+"is thrown. When complete, this operation disassociates the transaction from "
+"the current thread such that it becomes associated with no transaction."
+msgstr ""
+"トランザクションは、commit メソッドによってコミットされます。これは "
+"Volatile2PC プロトコルと Durable2PC プロトコルを実行してから戻ります。 呼び出"
+"すスレッドに関連のあるトランザクションが存在しない場合は、 "
+"<code>UnknownTransactionException</code> が送出されます。トランザクションが "
+"最終的にロールバックすると、<code>TransactionRolledBackException</code> が 送"
+"出されます。完了すると、このオペレーションはそのトランザクションを現在のス"
+"レッドから 分離して、そのスレッドがどのトランザクションにも関連を持たないよう"
+"にします。"
+
+#. Tag: para
+#: The_XTS_API.xml:82
+#, no-c-format
+msgid ""
+"The <code>rollback</code> operation will terminate the transaction and "
+"return normally if it succeeded, while throwing an appropriate exception if "
+"it didn’t. If there is no transaction associated with the invoking thread "
+"then <code>UnknownTransactionException</code> is thrown."
+msgstr ""
+"<code>rollback</code> オペレーションはトランザクションを終結して、正しく 終結"
+"した場合は通常に戻ります。正しく終結しない場合は適切な例外を送出します。 呼び"
+"出すスレッドに関連したトランザクションが存在しない場合は、 "
+"<code>UnknownTransactionException</code> が送出されます。"
+
+#. Tag: title
+#: The_XTS_API.xml:86
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr "UserTransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+"UserTransactions は <code>UserTransactionFactory</code> から取得されます。"
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: The_XTS_API.xml:93
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface represents "
+"the service/container/participant’s (service-side users) typical way in "
+"which to interact with the underlying transaction service implementation. As "
+"with <interfacename>UserTransaction</interfacename> a "
+"<interfacename>TransactionManager</interfacename> does not represent a "
+"specific transaction, but rather is responsible for providing access to an "
+"implicit per-thread transaction context."
+msgstr ""
+"<interfacename>TransactionManager</interfacename> インターフェイスは背後にあ"
+"る トランザクションサービス実装とのインタラクションをするサービス/コンテナ/"
+"パーティシパント（サービス側のユーザー）の 標準的な方法を表現します。"
+"<interfacename>UserTransaction</interfacename> と同様に "
+"<interfacename>TransactionManager</interfacename> は特定のトランザクションを"
+"表現するものでは なく、むしろ暗黙了解のスレッド単位トランザクションコンテキス"
+"トへのアクセスを提供する役目を持ちます。"
+
+#. Tag: para
+#: The_XTS_API.xml:97
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific transaction. In "
+"order to do this it is necessary to disassociate the thread from any "
+"transactions. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the transaction. The "
+"thread is then no longer associated with any transaction."
+msgstr ""
+"制御のスレッドは、それが特定のトランザクションに関連のない作業を実施できるよ"
+"うに トランザクションでない期間を要求することができます。これを達成するため"
+"に、 スレッドをいずれのトランザクションからも分離する必要があります。これは "
+"suspend メソッドが達成します。そしてトランザクション上のハンドルである "
+"<code>TxContext</code> インスタンスを返します。スレッドはそれから いずれのト"
+"ランザクションとも関連を持たないようになります。"
+
+#. Tag: para
+#: The_XTS_API.xml:100
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with a transaction(s) via its <code>TxContext</code>. Prior to "
+"association, the thread is disassociated with any transaction(s) with which "
+"it may be currently associated. If the <code>TxContext</code> is null, then "
+"the thread is associated with no transaction. The "
+"<code>UnknownTransactionException</code> exception is thrown if the "
+"transaction that the <code>TxContext</code> refers to is invalid in the "
+"scope of the invoking thread."
+msgstr ""
+"<methodname>resume</methodname> メソッドはスレッドを <code>TxContext</code> "
+"経由で トランザクションに（再）関連づけするために使用することができます。新規"
+"関連づけの前にスレッドは 現在関連づけのある可能性を持つどのトランザクションと"
+"も分離されます。<code>TxContext</code> が null であれば スレッドはどのトラン"
+"ザクションにも関連づけがないことになります。<code>TxContext</code> で参照する"
+"トランザクションが 呼び出すスレッドの有効範囲内で無効である場合に "
+"<code>UnknownTransactionException</code> 例外が送出されます。"
+
+#. Tag: para
+#: The_XTS_API.xml:103
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current transaction, or null if there is "
+"none. Unlike suspend, this method does not disassociate the current thread "
+"from the transaction(s). This can be used to enable multiple threads to "
+"execute within the scope of the same transaction."
+msgstr ""
+"<methodname>currentTransaction</methodname> メソッドは現在のトランザクション"
+"の 為の <code>TxContext</code> を返します。それが存在しない場合は null を返し"
+"ます。 suspend とは異なり、このメソッドは現在のスレッドをトランザクションから"
+"分離しません。 これは同じトランザクションの有効範囲内で実行する複数のスレッド"
+"を有効にするのに使用 できます。"
+
+#. Tag: para
+#: The_XTS_API.xml:106
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a transaction, the "
+"container or participant must use:"
+msgstr ""
+"パーティシパントをトランザクションに登録と離籍するためには コンテナ、又はパー"
+"ティシパントは以下を使用する必要があります:"
+
+#. Tag: para
+#: The_XTS_API.xml:111
+#, no-c-format
+msgid ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"Volatile2PC protocol; a unique identifier for the participant is also "
+"required. If there is no transaction associated with the invoking thread "
+"then the <code>UnknownTransactionException</code> exception is thrown. If "
+"the coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: Volatile2PC プロトコルに参入"
+"するように 現在のトランザクションを持つ指定されたパーティシパントを募集しま"
+"す。パーティシパント用の特有な 識別子も必要になります。呼び出すスレッドに関連"
+"づけのあるトランザクションが存在しない場合は、 "
+"<code>UnknownTransactionException</code> 例外が送出されます。コーディネータが"
+"すでに 同じ識別子を持つパーティシパントを採用している場合は、"
+"<code>AlreadyRegisteredException</code> 例外が送出されます。トランザクション"
+"がパーティシパントの参加できる状態でない場合（例えば、終結している時）、 "
+"<code>WrongStateException</code> 例外が送出されます。"
+
+#. Tag: para
+#: The_XTS_API.xml:116
+#, no-c-format
+msgid ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"2PC protocol; a unique identifier for the participant is also required. If "
+"there is no transaction associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>:  2PC プロトコルに参入するよう"
+"に 現在のトランザクションを持つ指定されたパーティシパントを募集します。パー"
+"ティシパント用の特有な 識別子も必要になります。呼び出すスレッドに関連づけのあ"
+"るトランザクションが存在しない場合は、 <code>UnknownTransactionException</"
+"code> 例外が送出されます。コーディネータがすでに 同じ識別子を持つパーティシパ"
+"ントを採用している場合は、<code>AlreadyRegisteredException</code> 例外が送出"
+"されます。トランザクションがパーティシパントの参加できる状態でない場合（例え"
+"ば、終結している時）、 <code>WrongStateException</code> 例外が送出されます。"
+
+#. Tag: title
+#: The_XTS_API.xml:122
+#, no-c-format
+msgid "TransactionFactory"
+msgstr "TransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+"TransactionManagers は <code>TransactionFactory</code> から 取得できます。"
+
+#. Tag: title
+#: The_XTS_API.xml:130
+#, no-c-format
+msgid "API for the Business Activity protocol"
+msgstr "ビジネス活動プロトコルのための API"
+
+#. Tag: title
+#: The_XTS_API.xml:132
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr "UserBusinessActivity"
+
+#. Tag: para
+#: The_XTS_API.xml:133
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserBusinessActivity</classname> is the class "
+"that most users (for example, clients and services) will see. This isolates "
+"them from the underlying protocol-specific aspects of the XTS "
+"implementation. Importantly, a <code>UserBusinessActivity</code> does not "
+"represent a specific business activity, but rather is responsible for "
+"providing access to an implicit per-thread activity. Therefore, all of the "
+"<code>UserBusinessActivity</code> methods implicitly act on the current "
+"thread of control."
+msgstr ""
+"<classname>com.arjuna.wst.UserBusinessActivity</classname> はほとんどのユー"
+"ザー （例えば、クライアントとサービス）が見ることになるクラスです。これはそれ"
+"らのユーザーを XTS 実装の背後にあるプロトコル特有の側面から隔離します。重要な"
+"ことは、<code>UserBusinessActivity</code> が 特定のビジネス活動を表現するので"
+"はなく、暗黙了解のスレッド単位活動へのアクセスの提供する役目を持つことです。 "
+"そのため、<code>UserBusinessActivity</code> メソッドの全ては必然的に制御の現"
+"在のスレッド上で 行動します。"
+
+#. Tag: para
+#: The_XTS_API.xml:137
+#, no-c-format
+msgid ""
+"A new business activity is begun and associated with the invoking thread by "
+"using the begin method. If there is already an activity associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created activity with the "
+"current thread."
+msgstr ""
+"begin メソッドを使用することにより新規のビジネス活動が開始され、呼び出すス"
+"レッドとの 関連づけがなされます。このスレッドに既に関連を持つ活動がある場合"
+"は、<code>WrongStateException</code> 例外が送出されます。正しく開始されると、"
+"このオペレーションは新規に作成された活動を現在のスレッドに 関連づけします。"
+
+#. Tag: para
+#: The_XTS_API.xml:140
+#, no-c-format
+msgid ""
+"The business activity is completed successfully by the close method. This "
+"will execute the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol prior to returning. If there is no activity associated with the "
+"invoking thread then <code>UnknownTransactionException</code> is thrown. If "
+"the activity ultimately cancels then the "
+"<code>TransactionRolledBackException</code> is thrown. When complete, this "
+"operation disassociates the business activity from the current thread such "
+"that it becomes associated with no activity."
+msgstr ""
+"ビジネス活動は close メソッドによって完了されます。これが "
+"<code>BusinessAgreementWithParticipantCompletion</code> を 実行してから戻りま"
+"す。呼び出すスレッドに関連づけのある活動が存在しない場合は、"
+"<code>UnknownTransactionException</code> が 送出されます。活動が最終的に取消"
+"になる場合、<code>TransactionRolledBackException</code> が送出されます。 完了"
+"すると、このオペレーションは、ビジネス活動を現在のスレッドから分離して、それ"
+"がどの活動とも 関連を持たないようにします。"
+
+#. Tag: para
+#: The_XTS_API.xml:143
+#, no-c-format
+msgid ""
+"The cancel operation will terminate the business activity and return "
+"normally if it succeeded, while throwing an appropriate exception if it "
+"didn’t. If there is no activity associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. Any participants that "
+"had previously completed will be informed to compensate for their work."
+msgstr ""
+"cancel オペレーションは、ビジネス活動を終結して、それが正しく実施された場合"
+"は 元に戻ります。それが正常に実施されない場合は、適切な例外が送出されます。 "
+"呼び出すスレッドと関連づけのある活動が存在しない場合は、"
+"<code>UnknownTransactionException</code> が 送出されます。以前に完了している"
+"パーティシパントはそれらの作業を補正するように通達されます。"
+
+#. Tag: para
+#: The_XTS_API.xml:146
+#, no-c-format
+msgid ""
+"Some participants may have registered for the "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol, which "
+"requires the coordinator or application to inform them when all work that "
+"they need to do within the scope of a business activity has been performed. "
+"The application should therefore use the complete method to inform these "
+"participants."
+msgstr ""
+"一部のパーティシパントは <code>BusinessAgreementWithCoordinatorCompletion</"
+"code> プロトコルの為に登録されているかも知れません。このことはビジネス活動の"
+"範囲内で実施する必要のある 全ての作業が完了した時にコーディネータか、又はアプ"
+"リケーションがパーティシパント達に 通達することを要求します。アプリケーション"
+"はそこで complete メソッドを使用してこれらの パーティシパント達に通達します。"
+
+#. Tag: title
+#: The_XTS_API.xml:150
+#, no-c-format
+msgid "UserBusinessActivityFactory"
+msgstr "UserBusinessActivityFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+"UserBusinessActivities は <code>UserBusinessActivityFactory</code> から 取得"
+"できます。"
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr "BusinessActivityManager"
+
+#. Tag: para
+#: The_XTS_API.xml:157
+#, no-c-format
+msgid ""
+"The <interfacename>BusinessActivityManager</interfacename> interface "
+"represents the service/container/participant’s (service-side users) typical "
+"way in which to interact with the underlying business activity service "
+"implementation. As with <interfacename>UserBusinessActivity</interfacename> "
+"a <interfacename>BusinessActivityManager</interfacename> does not represent "
+"a specific activity, but rather is responsible for providing access to an "
+"implicit per-thread activity."
+msgstr ""
+"<interfacename>BusinessActivityManager</interfacename> インターフェイスは "
+"サービス/コンテナ/パーティシパント（サービス側のユーザー）が背後にあるビジネ"
+"ス活動 サービス実装と対応するための標準的な方法を表現します。"
+"<interfacename>UserBusinessActivity</interfacename> の場合と同様に、"
+"<interfacename>BusinessActivityManager</interfacename> は特定の活動は示さない"
+"で、むしろ 暗黙のスレッド単位の活動へのアクセスを提供する役目を果たします。"
+
+#. Tag: para
+#: The_XTS_API.xml:161
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific activity. In order "
+"to do this it is necessary to disassociate the thread from any business "
+"activities. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the activity. The "
+"thread is then no longer associated with any activity."
+msgstr ""
+"制御のスレッドは、特定の活動に関連していない作業を実行できるように トランザク"
+"ションでない期間を要求することができます。これを達成するには、 スレッドをいず"
+"れのビジネス活動からも分離する必要があります。suspend メソッドが これを達成で"
+"きて、それが活動上のハンドルである <code>TxContext</code> インスタンスを返し"
+"ます。 スレッドはそれからはもうどの活動にも関連づけを持ちません。"
+
+#. Tag: para
+#: The_XTS_API.xml:164
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with an activity (or activities) via its TxContext. Prior to "
+"association, the thread is disassociated with any activity with which it may "
+"be currently associated. If the <code>TxContext</code> is null, then the "
+"thread is associated with no activity. The "
+"<code>UnknownTransactionException</code> exception is thrown if the business "
+"activity that the TxContext refers to is invalid in the scope of the "
+"invoking thread."
+msgstr ""
+"<methodname>resume</methodname> メソッドはスレッドを TxContext 経由で 活動に"
+"（再）関連づけするために使用することができます。新規関連づけの前にスレッドは "
+"現在関連づけのある可能性を持つどの活動とも分離されます。<code>TxContext</"
+"code> が null であれば スレッドはどの活動にも関連づけがないことになります。"
+"TxContext で参照するビジネス活動が 呼び出すスレッドの有効範囲内で無効である場"
+"合に <code>UnknownTransactionException</code> 例外が送出されます。"
+
+#. Tag: para
+#: The_XTS_API.xml:167
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current business activity, or null if there "
+"is none. Unlike suspend, this method does not disassociate the current "
+"thread from the activity. This can be used to enable multiple threads to "
+"execute within the scope of the same business activity."
+msgstr ""
+"<methodname>currentTransaction</methodname> メソッドは現在のビジネス 活動の為"
+"の <code>TxContext</code> を返します。又はそれがない場合、null を 返します。"
+"suspend とは異なり、このメソッドは現在のスレッドを活動から分離しません。 これ"
+"は同じビジネス活動の範囲内で実行する為の複数スレッドを有効にするために使用で"
+"ます。"
+
+#. Tag: para
+#: The_XTS_API.xml:170
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a business activity, the "
+"container or participant must use:"
+msgstr ""
+"ビジネス活動に対してパーティシパントの登録と離籍をするために、 コンテナ、又は"
+"パーティシパントは以下を使用する必要があります:"
+
+#. Tag: para
+#: The_XTS_API.xml:175
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"enlist the specified participant with current business activity such that it "
+"will participate in the <code>BusinessAgreementWithParticipantCompletion</"
+"code> protocol; a unique identifier for the participant is also required. If "
+"there is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"<code>BusinessAgreementWithParticipantCompletion</code> プロトコルに参入する"
+"ように 現在のビジネス活動を持つ指定されたパーティシパントを募集します。パー"
+"ティシパント用の特有な 識別子も必要になります。呼び出すスレッドに関連づけのあ"
+"るビジネス活動が存在しない場合は、 <code>UnknownTransactionException</code> "
+"例外が送出されます。コーディネータがすでに 同じ識別子を持つパーティシパントを"
+"採用している場合は、<code>AlreadyRegisteredException</code> 例外が送出されま"
+"す。活動がパーティシパントの参加できる状態でない場合（例えば、終結している"
+"時）、 <code>WrongStateException</code> 例外が送出されます。"
+
+#. Tag: para
+#: The_XTS_API.xml:180
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"enlist the specified participant with current activity such that it will "
+"participate in the <code>BusinessAgreementWithCoordinatorCompletion</code> "
+"protocol; a unique identifier for the participant is also required. If there "
+"is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> プロトコルに参入する"
+"ように 現在のビジネス活動を持つ指定されたパーティシパントを募集します。パー"
+"ティシパント用の特有な 識別子も必要になります。呼び出すスレッドに関連づけのあ"
+"るビジネス活動が存在しない場合は、 <code>UnknownTransactionException</code> "
+"例外が送出されます。コーディネータがすでに 同じ識別子を持つパーティシパントを"
+"採用している場合は、<code>AlreadyRegisteredException</code> 例外が送出されま"
+"す。活動がパーティシパントの参加できる状態でない場合（例えば、終結している"
+"時）、 <code>WrongStateException</code> 例外が送出されます。 "
+
+#. Tag: title
+#: The_XTS_API.xml:186
+#, no-c-format
+msgid "BusinessActivityManagerFactory"
+msgstr "BusinessActivityManagerFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
+"BusinessActivityManagers は <code>BusinessActivityManagerFactory</code> から "
+"取得できます。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactional_Web_Services.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactional_Web_Services.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactional_Web_Services.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,139 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr "トランザクショナル Web サービス"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "はじめに"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:9
+#, no-c-format
+msgid ""
+"This chapter describes how to provide transactional support for new and "
+"existing Web services using the service-side facilities of XTS. It shows how "
+"new services can be made transactional with no additional programming, and "
+"how existing services can be made WS-T transaction-aware in a non-invasive "
+"fashion."
+msgstr ""
+"この章では、XTS のサービスサイドの機能を使用した新規の又は既存の Web サービス"
+"の 為のトランザクショナルサポートの提供方法を説明しています。ここでは、追加"
+"の プログラミングを使用しないで新規のサービスをトランザクション的にする方法"
+"と 侵略的でないスタイルで既存のサービスを WS-T トランザクション認識にする方法"
+"を 示しています。"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr "トランザクショナル Web サービス"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:16
+#, no-c-format
+msgid ""
+"A Web service is a business-level entity. It encapsulates application logic "
+"needed to perform some domain-specific task, or is designed to delegate to a "
+"back-end system which executes that logic. Given it is part of application "
+"code, such non-functional requirements as transactionality should not "
+"impinge on its construction."
+msgstr ""
+"Web サービスはビジネスレベルのエンティティです。これは一部のドメイン特有の タ"
+"スクを実践するために必要なアプリケーション論理をカプセル化し、そして その論理"
+"を実行するバックエンドシステムに仕事を委任するように設計されています。 アプリ"
+"ケーションコードの一部であることから、トランザクション性のような機能的でない "
+"要求はその構造に影響することはないはずです。"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:19
+#, no-c-format
+msgid ""
+"To support this notion, XTS provides a suite of components designed to work "
+"at the SOAP stack level, which deal with transactional matters on behalf of "
+"a Web service without requiring any changes to that service. In XTS two "
+"context handling components are registered with the SOAP server and deal "
+"with context management on behalf of the service without the service having "
+"to worry about context propagation issues itself. This is shown in the "
+"following figure."
+msgstr ""
+"この概念をサポートするために、XTS は SOAP スタックレベルで機能するように 設計"
+"されたコンポーネントのセットを提供し、これがそのサービスに如何なる変更も 必要"
+"とせずに Web サービスの役目としてトランザクショナル事項を取扱います。 XTS で"
+"は、２つのコンテキスト処理のコンポーネントが SOAP サーバーに登録 されており、"
+"コンテキストの伝播問題自身を懸念することなくサービスの役目として コンテキスト"
+"管理を取り扱います。以下にその様子を示しています。"
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr "SOAP サーバーを使用して登録されたコンテキストハンドラ"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:28
+#, no-c-format
+msgid ""
+"The detail of the context management that the context processor performs is "
+"unimportant to the Web service application logic, and is orthogonal to any "
+"work performed by any other protocol-specific context handlers too. However "
+"back-end systems which the Web service application logic uses (such as "
+"databases) are often interested in the front-end transaction context such "
+"that any operations invoked within its scope can be mapped onto a back-end "
+"transaction context. This is typically achieved at the back-end by wrapping "
+"a database driver in a veneer which implements both the interface of the "
+"original driver and hooks into the service-side API to access the "
+"transaction context details. The general architecture for this pattern is "
+"shown in the figure below."
+msgstr ""
+"コンテキストプロセッサが実行するコンテキスト管理の詳細は、Web サービス アプリ"
+"ケーション論理にとっては重要ではなく、他のプロトコル特有のコンテキスト ハンド"
+"ラによって実行される作業には直角交差しています。しかし、Web サービス アプリ"
+"ケーション論理が使用する（データベースなどの）バックエンドシステムは多くの 場"
+"合に、フロントエンドのトランザクションコンテキストに興味を持ち、その有効範囲"
+"で 呼び出されたオペレーションはいずれもバックエンドトランザクションコンテキス"
+"トに マップすることができます。これは一般的にデータベースドライバを、オリジナ"
+"ル ドライバのベニア内にラップすることにより、オリジナルドライバのインターフェ"
+"イスを 実装して、トランザクショナルコンテキストの詳細にアクセスするためにサー"
+"ビスサイドの API にフックするとバックエンドで達成できます。"
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:35
+#, no-c-format
+msgid "General Pattern for Back-End Integration, Service Side"
+msgstr "バックエンド統合の為の汎用パターン、サービスサイド"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:37
+#, no-c-format
+msgid ""
+"The missing element from this is the commit protocol which finally allows "
+"back-end work to be made durable or not at the end of a transaction. This is "
+"covered in the participant chapter where the participant/back-end relation "
+"is explored further."
+msgstr ""
+"ここで欠如している要素はコミットのプロトコルであり、これはバックエンドの作業"
+"が トランザクションの最後に恒久であるかどうかを決定できるようにします。このこ"
+"とは パーティシパントの章でカバーされていて、パーティシパント/バックエンドの"
+"関係がより詳しく検討されいます。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactions_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactions_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactions_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,872 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactions_Overview.xml:6
+#, no-c-format
+msgid "Transactions Overview"
+msgstr "トランザクションの概要"
+
+#. Tag: para
+#: Transactions_Overview.xml:7
+#, no-c-format
+msgid ""
+"Transactions have emerged as the dominant paradigm for coordinating "
+"interactions between parties in a distributed system, and in particular to "
+"manage applications that require concurrent access to shared data. Much of "
+"the JBossTS Web Service API is based on contemporary transaction APIs whose "
+"familiarity will enhance developer productivity and lessen the learning "
+"curve. While the following section provides the essential information that "
+"you should know before starting to use XTS for building transactional Web "
+"Services, it should not be treated as a definitive reference to all "
+"transactional technology."
+msgstr ""
+"トランザクションは分散型のシステム内でパーティ間のインタラクションをコーディ"
+"ネイトする為の 有力なパラダイムとして出現してきました。そして特に共有データへ"
+"の 並行アクセスを要求するアプリケーションの管理をします。JBossTS Web サービ"
+"ス API の多くが、熟知すると開発者の生産性を向上し急速な学習 ニーズを軽減する"
+"現代的なトランザクション API をベースにしています。 以下のセクションではトラ"
+"ンザクショナル Web サービスの構築の為の XTS 使用を開始する前に知っておくべき"
+"基本的な情報を提供していますが、これは すべてのトランザクショナル技術への決定"
+"的参照として判断すべきものでは ありません。"
+
+#. Tag: para
+#: Transactions_Overview.xml:10
+#, no-c-format
+msgid ""
+"A classic transaction is a unit of work that either completely succeeds, or "
+"fails with all partially completed work being undone. When a transaction is "
+"committed, all changes made by the associated requests are made durable, "
+"normally by committing the results of the work to a database. If a "
+"transaction should fail and is rolled back, all changes made by the "
+"associated work are undone. Transactions in distributed systems typically "
+"require the use of a transaction manager that is responsible for "
+"coordinating all of the participants that are part of the transaction."
+msgstr ""
+"古典的なトランザクションは完全に成功するか、失敗するか、そして部分的に 完了し"
+"たものは元に戻されると言う作業の単位です。トランザクションがコミット される"
+"と、関連した要求によりなされた全ての変更は、通常その結果をデータベースに 保存"
+"することにより恒久化されます。トランザクションが失敗してロールバックされた 場"
+"合は、関連した作業によりなされた変更はすべて元に戻されます。分散型システム内"
+"の トランザクションは標準的に、トランザクションの一部であるパーティシパントの"
+"全てを コーディネイトする役目を持つトランザクションマネージャの使用が必要とな"
+"ります。"
+
+#. Tag: para
+#: Transactions_Overview.xml:13
+#, no-c-format
+msgid ""
+"The main components involved in using and defining transactional Web "
+"Services using XTS are illustrated in Figure 1."
+msgstr ""
+"XTS を使用したトランザクショナル Web サービスの使用と定義に関与している主な "
+"コンポーネントは 図１に示してあります。"
+
+#. Tag: para
+#: Transactions_Overview.xml:18
+#, no-c-format
+msgid ""
+"A Transaction Service: The Transaction Service captures the model of the "
+"underlying transaction protocol and coordinates parties affiliated with the "
+"transaction according to that model."
+msgstr ""
+"トランザクションサービス: トランザクションサービスは背後にあるトランザクショ"
+"ンプロトコルの モデルを取り込んで、そのモデルに応じてトランザクションと提携さ"
+"れているパーティをコーディネイトします。"
+
+#. Tag: para
+#: Transactions_Overview.xml:23
+#, no-c-format
+msgid ""
+"A Transaction API: Provides an interface for transaction demarcation and the "
+"registration of participants."
+msgstr ""
+"トランザクション API: トランザクション区分とパーティシパントの登録用のイン"
+"ターフェイスを 提供します。"
+
+#. Tag: para
+#: Transactions_Overview.xml:28
+#, no-c-format
+msgid ""
+"A Participant: The entity that cooperates with the transaction service on "
+"behalf of its associated business logic."
+msgstr ""
+"パーティシパント: 関連づけのあるビジネス論理の代表としてトランザクション サー"
+"ビスとコラボレーションするエンティティです。"
+
+#. Tag: para
+#: Transactions_Overview.xml:33
+#, no-c-format
+msgid ""
+"The Context: Captures the necessary details of the transaction such that "
+"participants can enlist within its scope."
+msgstr ""
+"コンテキスト: トランザクションの必要な詳細を取り込んで、パーティシパントがそ"
+"の有効範囲内で 参加できるようにします。"
+
+#. Tag: caption
+#: Transactions_Overview.xml:42
+#, no-c-format
+msgid "Web Services and XTS"
+msgstr "Web サービスと XTS"
+
+#. Tag: title
+#: Transactions_Overview.xml:45
+#, no-c-format
+msgid "The Coordinator"
+msgstr "コーディネータ"
+
+#. Tag: para
+#: Transactions_Overview.xml:46
+#, no-c-format
+msgid ""
+"Associated with every transaction is a coordinator, which is responsible for "
+"governing the outcome of the transaction. The coordinator may be implemented "
+"as a separate service or may be co-located with the user for improved "
+"performance. Each coordinator is created by the transaction manager service, "
+"which is in effect a factory for those coordinators."
+msgstr ""
+"全てのトランザクションに関係しているのがコーディネータです。これは トランザク"
+"ションの結果を監督する責務を持ちます。コーディネータは 別のサービスとして実装"
+"されるか、あるいはパフォーマンス向上の為に ユーザーとの並列配置として使用でき"
+"ます。各コーディネータは結果的に コーディネータ達の生産向上となるトランザク"
+"ションマネージャサービスに よって作成されます。"
+
+#. Tag: para
+#: Transactions_Overview.xml:50
+#, no-c-format
+msgid ""
+"A coordinator communicates with enrolled participants to inform them of the "
+"desired termination requirements, for instance, whether they should accept "
+"(for example, confirm) or reject (for example, cancel) the work done within "
+"the scope of the given transaction. For example, whether to purchase the "
+"(provisionally reserved) flight tickets for the user or to release them. An "
+"application/client may wish to terminate a transaction in a number of "
+"different ways (for example, confirm or cancel). However, although the "
+"coordinator will attempt to terminate in a manner consistent with that "
+"desired by the client, it is ultimately the interactions between the "
+"coordinator and the participants that will determine the actual final "
+"outcome."
+msgstr ""
+"コーディネータは参入したパーティシパントと通信して目標とする 終結要求、例え"
+"ば、該当するトランザクションの有効範囲内でなされた作業を 受理する（例：確認）"
+"か又は拒否する（例：取消し）かどうかを通達します。 例として挙げると、ユーザー"
+"の為のフライトの予約（暫定予約済み）を購入するか 又はそれを取り消すかと言うこ"
+"とが考えられます。アプリケーション/クライアントは 色々な方法でトランザクショ"
+"ンを終結したい（例えば、確認か取消し）と意図するでしょう。 しかし、コーディ"
+"ネータがクライアントの意図する方法で終結を試みても、それは最終的には 実際の最"
+"終結果を決定するのはコーディネータとパーティシパントとの間の協議なのです。"
+
+#. Tag: para
+#: Transactions_Overview.xml:53
+#, no-c-format
+msgid ""
+"A transaction manager is typically responsible for managing coordinators for "
+"many transactions. The initiator of the transaction (for example, the "
+"client) communicates with a transaction manager and asks it to start a new "
+"transaction and associate a coordinator with the transaction. Once created, "
+"the context can be propagated to Web services in order for them to associate "
+"their work with the transaction."
+msgstr ""
+"トランザクションマネージャは標準的には、多くのトランザクションの為に コーディ"
+"ネータ達を管理する責務を持ちます。トランザクションのイニシエータ （例えば、ク"
+"ライアント）はトランザクションマネージャに通信して新規の トランザクションを開"
+"始し、コーディネータをそのトランザクションに関連づけする ことを依頼します。そ"
+"れが作成されると、そのコンテキストが Web サービスに伝播 されて Web サービスが"
+"トランザクションと作業の関連づけを持つようになります。"
+
+#. Tag: title
+#: Transactions_Overview.xml:57
+#, no-c-format
+msgid "The Transaction Context"
+msgstr "トランザクションコンテキスト"
+
+#. Tag: para
+#: Transactions_Overview.xml:58
+#, no-c-format
+msgid ""
+"In order for a transaction to span a number of services, certain information "
+"has to be shared between those services in order to propagate information "
+"about the transaction. This information is known as the Context. Using XTS, "
+"the context is automatically propagated and processed by transaction-aware "
+"components of an application. Though XTS removes most of the work associated "
+"with propagating contexts, it is still instructive to understand what "
+"information is captured in a context:"
+msgstr ""
+"トランザクションが数多くのサービスに広がるために、特定の情報がそれらの サービ"
+"ス間で共有されてトランザクションに関する情報が伝播する必要が あります。この情"
+"報はコンテキストとして知られています。XTS の使用では、 コンテキストは自動的に"
+"アプリケーションのトランザクション認識部分により 伝播されてプロセスされます。"
+"XTS はコンテキストの伝播に関与したほとんどの 作業を排除しますが、コンテキスト"
+"内にどのような情報が取り込まれているのかを 理解することは役に立ちます:"
+
+#. Tag: para
+#: Transactions_Overview.xml:64
+#, no-c-format
+msgid ""
+"A transaction identifier which guarantees global uniqueness for an "
+"individual transaction;"
+msgstr ""
+"個別のトランザクション用にグローバルな特殊性を保証するトランザクション識別子;"
+
+#. Tag: para
+#: Transactions_Overview.xml:69
+#, no-c-format
+msgid ""
+"The transaction coordinator location or endpoint address so participants can "
+"be enrolled."
+msgstr ""
+"パーティシパントが参加できるようにするトランザクションコーディネータの位置、"
+"又は 最終点アドレス。"
+
+#. Tag: caption
+#: Transactions_Overview.xml:78
+#, no-c-format
+msgid "Web Services and Context Flow"
+msgstr "Web サービスとコンテキストフロー"
+
+#. Tag: para
+#: Transactions_Overview.xml:80
+#, no-c-format
+msgid ""
+"As shown in Figure 2, whenever an application message is sent, the XTS "
+"Client API automatically creates a context and embeds it into the message. "
+"Similarly, any transaction-aware services are able to extract that context "
+"using the XTS service-side infrastructure and use it to perform work within "
+"the context of a particular transaction – even though that transaction was "
+"initiated elsewhere on the Web! The value of this approach is that the "
+"business logic contained within the client application and services are not "
+"peppered with transaction-processing code."
+msgstr ""
+"図２に示してあるように、アプリケーションメッセージが送信されると XTS Client "
+"API  は自動的にコンテキストを作成してそれをメッセージに埋め込みます。 同様"
+"に、トランザクション認識のサービスはいずれも XTS サービスサイドの インフラス"
+"トラクチャを使用してそのコンテキストを取り出すことができ、 トランザクション"
+"が Web の他の場所で開始されていても その特定の トランザクションのコンテキスト"
+"内で作業をするためにそれを使用します。 このアプローチの価値は、クライアントア"
+"プリケーションとサービス内に含まれる ビジネス論理はトランザクションプロセッシ"
+"ングコードにより懲らしめられる ことがないことです。"
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr "ACID トランザクション"
+
+#. Tag: para
+#: Transactions_Overview.xml:85
+#, no-c-format
+msgid ""
+"Traditionally, transaction processing systems support ACID properties. ACID "
+"is an acronym for Atomic, Consistent, Isolated, and Durable. A unit of work "
+"has traditionally been considered transactional only if the ACID properties "
+"are maintained:"
+msgstr ""
+"伝統的に、トランザクションプロセッシングは ACID プロパティをサポートします。 "
+"ACID は Atomic, Consistent, Isolated, Durable の頭文字です。伝統的に作業の １"
+"単位は、 ACID プロパティが維持できている場合のみにトランザクショナルと判定 さ"
+"れます:"
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr ""
+"Atomicity（原子性）:トランザクションは実行を完了するか、又は全くしません。"
+
+#. Tag: para
+#: Transactions_Overview.xml:96
+#, no-c-format
+msgid ""
+"Consistency: The effects of the transaction preserve the internal "
+"consistency of an underlying data structure."
+msgstr ""
+"Consistency（一貫性）:トランザクションの効果は、背後にあるデータ構造の内部的"
+"一貫性を 保存します。 "
+
+#. Tag: para
+#: Transactions_Overview.xml:101
+#, no-c-format
+msgid ""
+"Isolated: The transaction runs as if it were running alone with no other "
+"transactions running and is not visible to other transactions."
+msgstr ""
+"Isolated（隔離性）: トランザクションは、まるで他のトランザクションが実行して"
+"いなくて、 単独で実行しているかのように実行し、そして他のトランザクションには"
+"見えません。"
+
+#. Tag: para
+#: Transactions_Overview.xml:106
+#, no-c-format
+msgid ""
+"Durable: the transaction’s results will not be lost in the event of a "
+"failure."
+msgstr "Durable（恒久性）: トランザクションの結果は障害時でも消失しません。 "
+
+#. Tag: title
+#: Transactions_Overview.xml:112
+#, no-c-format
+msgid "Two-Phase Commit"
+msgstr "２段階コミット"
+
+#. Tag: para
+#: Transactions_Overview.xml:113
+#, no-c-format
+msgid ""
+"The classical two-phase commit approach is the bedrock of JBossTS (and more "
+"generally of Web Services transactions). Two-phase commit provides "
+"coordination of parties that are involved in a transaction. In general, the "
+"flow of a two-phase commit transaction is as follows:"
+msgstr ""
+"古典的な２段階コミットアプローチは、JBossTS（及び他の Web サービストランザク"
+"ション）の 岩床です。２段階コミットはトランザクションに関与しているパーティの"
+"同調を提供します。 一般的に２段階コミットトランザクションの流れは以下のように"
+"なります:"
+
+#. Tag: para
+#: Transactions_Overview.xml:119
+#, no-c-format
+msgid "A transaction is started, and some work is performed."
+msgstr "トランザクションが開始されます。そして一部の作業が実行されます。"
+
+#. Tag: para
+#: Transactions_Overview.xml:124
+#, no-c-format
+msgid "Once the work is finished, the two-phase commit begins."
+msgstr "作業が終了すると、２段階コミットが始まります。"
+
+#. Tag: para
+#: Transactions_Overview.xml:129
+#, no-c-format
+msgid ""
+"The coordinator (transaction manager) of the transaction asks each resource "
+"taking part in the transaction whether it is prepared to commit."
+msgstr ""
+"トランザクションのコーディネータ（トランザクションマネージャ）がトランザク"
+"ションに 参入している各リソースに対してコミットする準備があるかどうかを尋ねま"
+"す。"
+
+#. Tag: para
+#: Transactions_Overview.xml:134
+#, no-c-format
+msgid ""
+"If all resources respond positively, the coordinator instructs all work "
+"performed to be made durable (usually committed to a database)."
+msgstr ""
+"全てのリソースが肯定的に返事をした場合、コーディネータが 実行される全ての作業"
+"は恒久化すべきこと（通常、データベースへの保存）を 告げます。"
+
+#. Tag: para
+#: Transactions_Overview.xml:139
+#, no-c-format
+msgid ""
+"If not, all work performed is rolled back (undone) such that the underlying "
+"data structures are in their original states."
+msgstr ""
+"返事が肯定的でない場合は、実行された全ての作業はロールバック（元に戻す）して "
+"背後にあるデータベース構造が元の状態になるようにします。"
+
+#. Tag: caption
+#: Transactions_Overview.xml:148
+#, no-c-format
+msgid "The Two-Phase Commit Protocol"
+msgstr "２段階コミットプロトコル"
+
+#. Tag: para
+#: Transactions_Overview.xml:151
+#, no-c-format
+msgid ""
+"During two-phase commit transactions, coordinators and resources keep track "
+"of activity in non-volatile data stores so that they can recover in the case "
+"of a failure."
+msgstr ""
+"２段階コミットのトランザクションの間、コーディネータとリソースは揮発性でない "
+"データストア内の活動の記録をとり、障害の際に復元できるようにします。"
+
+#. Tag: title
+#: Transactions_Overview.xml:156
+#, no-c-format
+msgid "The synchronization protocol"
+msgstr "同期化プロトコル"
+
+#. Tag: para
+#: Transactions_Overview.xml:157
+#, no-c-format
+msgid ""
+"As well as the two-phase commit protocol, traditional transaction processing "
+"systems employ an additional protocol, often referred to as the "
+"synchronization protocol. If you recall the original ACID properties, then "
+"you’ll remember that Durability is important in the case where state changes "
+"have to be available despite failures. What this means is that applications "
+"interact with a persistence store of some kind (e.g., a database) and this "
+"can impose a significant overhead – disk access is orders of magnitude "
+"slower than access to main computer memory."
+msgstr ""
+"伝統的なトランザクションプロセッシングシステムは２段階コミットプロトコルの他"
+"にも、 追加のプロトコルを採用します。多くの場合これは同期化プロトコルと 呼ば"
+"れます。オリジナルの ACID プロパティを回想して頂くと、失敗にも係わらず 状態変"
+"化情報が必要となるケースでは Durability（恒久性）が重要になることを思い 出さ"
+"れるはずです。このことは、アプリケーションがある種の永続化ストア（データベー"
+"ス）と 通信して、これが重要な運営負担になると言う意味です（ディスクアクセスは"
+"メインコンピュータメモリへの アクセスよりも随分遅くなります）。 "
+
+#. Tag: para
+#: Transactions_Overview.xml:161
+#, no-c-format
+msgid ""
+"One apparently obvious solution to this problem would be to cache the state "
+"in main memory and only operate on that for the duration of a transaction. "
+"Unfortunately you’d then need some way of being able to flush the state back "
+"to the persistent store before the transaction terminates, or risk losing "
+"the full ACID properties. This is what the synchronization protocol does, "
+"with Synchronization participants."
+msgstr ""
+"この問題への明確なソリューションの１つはその状態をメインメモリーにキャッシュ"
+"して トランザクションの期間中にはそのキャッシュのみでオペレートすることです。"
+"残念ながら、 そうするとトランザクションが終結する前にその状態を永続化ストアに"
+"流すことが出来る ような手段が必要になります。さもなければ ACID プロパティの全"
+"体を失うリスクを負います。 これが同期化パーティシパントを使用した同期化プロト"
+"コルが実行する仕事になります。"
+
+#. Tag: para
+#: Transactions_Overview.xml:164
+#, no-c-format
+msgid ""
+"Synchronizations are informed that a transaction is about to commit, so they "
+"can, for example, flush cached state, which may be being used to improve "
+"performance of an application, to a durable representation prior to the "
+"transaction committing. They are then informed when the transaction has "
+"completed and in what state it completed."
+msgstr ""
+"同期化はトランザクションがコミットしそうだと言う通達を受けます。そうすると、 "
+"例えば、アプリケーションのパフォーマンスを向上するために使用されたキャッシュ"
+"化した 状態をトランザクションのコミット前に恒久化設備にフラッシュできます。そ"
+"れはその後、 何時トランザクションが終了したか、及びどの状態で終了したかの通達"
+"を受けます。"
+
+#. Tag: para
+#: Transactions_Overview.xml:169
+#, no-c-format
+msgid ""
+"Synchronizations essentially turn the two-phase commit protocol into a four-"
+"phase protocol:"
+msgstr ""
+"同期化は基本的に２段階コミットプロトコルを４段階プロトコルに転換します:"
+
+#. Tag: para
+#: Transactions_Overview.xml:174
+#, no-c-format
+msgid ""
+"Before the transaction starts the two-phase commit, all registered "
+"Synchronizations are informed. Any failure at this point will cause the "
+"transaction to roll back."
+msgstr ""
+"トランザクションが２段階コミットを開始する前に、全ての登録済み 同期化は通達を"
+"受けます。この時点での障害はいずれもトランザクションが ロールバックする原因に"
+"なります。"
+
+#. Tag: para
+#: Transactions_Overview.xml:179
+#, no-c-format
+msgid "The coordinator then conducts the normal two-phase commit protocol."
+msgstr "コーディネータは通常の２段階コミットプロトコルを実践します。"
+
+#. Tag: para
+#: Transactions_Overview.xml:184
+#, no-c-format
+msgid ""
+"Once the transaction has terminated, all registered Synchronizations are "
+"informed. However, this is a courtesy invocation because any failures at "
+"this stage are ignored: the transaction has terminated so there’s nothing to "
+"affect."
+msgstr ""
+"トランザクションが終結すると、全ての登録済み同期化は通達を受けます。 しかし、"
+"この段階での障害はどれも無視されるため、これは単に社交的な 呼び出しです。トラ"
+"ンザクションはもう終結しているため、何も影響は ありません。"
+
+#. Tag: para
+#: Transactions_Overview.xml:189
+#, no-c-format
+msgid ""
+"Unlike the two-phase commit protocol, the synchronization protocol does not "
+"have the same failure requirements. For example, Synchronization "
+"participants don’t need to make sure they can recover in the event of "
+"failures; this is because any failure before the two-phase commit protocol "
+"completes means the transaction will roll back, and failures after it has "
+"completed can’t affect the data the Synchronization participants were "
+"managing."
+msgstr ""
+"２段階コミットプロトコルとは異なり、同期化プロトコルは同じような 障害への必要"
+"事項を持ちません。例えば、同期化パーティシパントは 障害時にそれらが復元できる"
+"ことを確認する必要はありません。これは ２段階コミットプロトコルが完了する前の"
+"障害はどれもトランザクションの ロールバックになり、そして完了後の障害は同期化"
+"パーティシパントが 管理しているデータには影響がないからです。"
+
+#. Tag: title
+#: Transactions_Overview.xml:193
+#, no-c-format
+msgid "Optimizations to the protocol"
+msgstr "プロトコルへの最適化"
+
+#. Tag: para
+#: Transactions_Overview.xml:194
+#, no-c-format
+msgid ""
+"There are several variants to the standard two-phase commit protocol that "
+"are worth knowing about because they can have an impact on performance and "
+"failure recovery. We shall briefly describe those that are the most common "
+"variants on the protocol:"
+msgstr ""
+"標準の２段階コミットプロトコルには、パフォーマンスと障害復元にインパクトを 与"
+"える可能性の為に、知っておくべきいくつかの変種があります。このプロトコルの 最"
+"も一般的な変種についてここで簡単に説明しておきます:"
+
+#. Tag: para
+#: Transactions_Overview.xml:200
+#, no-c-format
+msgid ""
+"Presumed abort: if a transaction is going to roll back then it may simply "
+"record this information locally and tell all enlisted participants. Failure "
+"to contact a participant has no affect on the transaction outcome; the "
+"transaction is effectively informing participants as a courtesy. Once all "
+"participants have been contacted the information about the transaction can "
+"be removed. If a subsequent request for the status of the transaction occurs "
+"there will be no information available and the requestor can assume that the "
+"transaction has aborted (rolled back). This optimization has the benefit "
+"that no information about participants need be made persistent until the "
+"transaction has decided to commit (i.e., progressed to the end of the "
+"prepare phase), since any failure prior to this point will be assumed to be "
+"an abort of the transaction."
+msgstr ""
+"Presumed abort（推定放棄）: トランザクションがロールバックしそうな場合、 トラ"
+"ンザクションは単にこの情報をローカルで記録して、採用しているパーティシパント"
+"達に それを通達します。パーティシパントへの通達が達成されなくてもトランザク"
+"ションの結果には 影響がありません。トランザクションは社交的にパーティシパント"
+"に連絡しているだけです。 全てのパーティシパントが連絡を受けると、トランザク"
+"ションについての情報は破棄できます。 その後にトランザクションの状態についての"
+"要求が発生すると、情報は存在せずに要求側は トランザクションが放棄（ロールバッ"
+"ク）されたと推定します。この最適化の利便性として パーティシパントに関する情報"
+"はトランザクションがコミット（準備段階の最後にプロセス）を 決定するまで永続化"
+"する必要がないと言う点があります。この時点までの障害は全てトランザクションの"
+"放棄と 見なされるからです。"
+
+#. Tag: para
+#: Transactions_Overview.xml:205
+#, no-c-format
+msgid ""
+"One-phase: if there is only a single participant involved in the "
+"transaction, the coordinator need not drive it through the prepare phase. "
+"Thus, the participant will simply be told to commit and the coordinator need "
+"not record information about the decision since the outcome of the "
+"transaction is solely down to the participant."
+msgstr ""
+"One-phase（１段階）: トランザクションに関与しているのが単独のパーティシパント"
+"だけの 場合、コーディネータは準備段階全体に渡って通過する必要はありません。そ"
+"のため、 該当パーティシパントは単にコミットするように指示されて、トランザク"
+"ションの結果は そのパーティシパントだけの為であるためコーディネータはこの決定"
+"に関して情報を記録 する必要はありません。"
+
+#. Tag: para
+#: Transactions_Overview.xml:210
+#, no-c-format
+msgid ""
+"Read-only: when a participant is asked to prepare, it can indicate to the "
+"coordinator that no information or data that it controls has been modified "
+"during the transaction. Such a participant does not need to be informed "
+"about the outcome of the transaction since the fate of the participant has "
+"no affect on the transaction. As such, a read-only participant can be "
+"omitted from the second phase of the commit protocol."
+msgstr ""
+"Read-only（読み取りのみ）: パーティシパントは準備の要求を受けると、コーディ"
+"ネータに対してパーティシパントが制御している情報やデータがトランザクションの "
+"期間中に修正されていないことを示すことができます。そのようなパーティシパント"
+"は その動向がトランザクションに影響しない為、トランザクションの結果の通達を受"
+"ける 必要はありません。そのため、read-only のパーティシパントはコミットプロト"
+"コルの 第２段階から無視できます。"
+
+#. Tag: title
+#: Transactions_Overview.xml:216
+#, no-c-format
+msgid "Non-atomic transactions and heuristic outcomes"
+msgstr ""
+"原子性でない（Non-atomic）トランザクションと発見的方法（heuristic）の結果"
+
+#. Tag: para
+#: Transactions_Overview.xml:217
+#, no-c-format
+msgid ""
+"In order to guarantee atomicity, the two-phase commit protocol is "
+"necessarily blocking. What this means is that as a result of failures, "
+"participants may remain blocked for an indefinite period of time even if "
+"failure recovery mechanisms exist. Some applications and participants simply "
+"cannot tolerate this blocking."
+msgstr ""
+"原子性を保証する為に、２段階コミットプロトコルはブロッキングをしています。 こ"
+"れが意味することは、障害復元のメカニズムが存在する場合でも障害の結果として "
+"パーティシパントは無限にブロックされ続ける可能性があると言うことです。一部の "
+"アプリケーションとパーティシパントはこのブロッキングに対処できません。"
+
+#. Tag: para
+#: Transactions_Overview.xml:221
+#, no-c-format
+msgid ""
+"To break this blocking nature, participants that have got past the prepare "
+"phase are allowed to make autonomous decisions as to whether they commit or "
+"rollback: such a participant must record this decision in case it is "
+"eventually contacted to complete the original transaction. If the "
+"coordinator eventually informs the participant of the transaction outcome "
+"and it is the same as the choice the participant made, then there’s no "
+"problem. However, if it is contrary, then a non-atomic outcome has obviously "
+"happened: a heuristic outcome."
+msgstr ""
+"このブロッキングの性質を打破するために、準備段階を通過したパーティシパントは "
+"それらがコミットするかロールバックするかについて自主的な決定能力が与えられま"
+"す。 そのようなパーティシパントは、オリジナルトランザクションを最終的に完了す"
+"る為の 連絡を受ける場合に備えてこの決定を記録しなければなりません。コーディ"
+"ネータが パーティシパントに対してトランザクションの最終結果を通達して、それが"
+"パーティシパント自身の 決定と同じである場合、問題はありません。それが異なる場"
+"合、原子性でない結果が発生した ことが明確です。これが発見的方法"
+"（ heuristic ）の結果となります。"
+
+#. Tag: para
+#: Transactions_Overview.xml:224
+#, no-c-format
+msgid ""
+"How this heuristic outcome is reported to the application and resolved is "
+"usually the domain of complex, manually driven system administration tools, "
+"since in order to attempt an automatic resolution requires semantic "
+"information about the nature of participants involved in the transactions."
+msgstr ""
+"この発見的方法の結果がアプリケーションに報告される手段とその解決は通常、 原子"
+"性解決の試行はトランザクションに関与しているパーティシパントの性質に 関するセ"
+"マンティクな情報を必要とするために、複雑で手動主体のシステム管理ツールの 領域"
+"となります。"
+
+#. Tag: para
+#: Transactions_Overview.xml:227
+#, no-c-format
+msgid ""
+"Precisely when a participant makes a heuristic decision is obviously "
+"implementation dependant. Likewise, the choice the participant makes (to "
+"commit or to roll back) will depend upon the implementation and possibly the "
+"application/environment in which it finds itself. The possible heuristic "
+"outcomes are:"
+msgstr ""
+"正確にパーティシパントが発見的方法で決定をする時期は明らかに実装に 依存してい"
+"ます。同様に、パーティシパントがする決定（コミットかロールバックか）も 実装に"
+"依存して、多分、それ自身があるアプリケーション/環境にも依存します。 可能性の"
+"ある発見的方法は以下のようになります:"
+
+#. Tag: para
+#: Transactions_Overview.xml:232
+#, no-c-format
+msgid ""
+"Heuristic rollback: the commit operation failed because some or all of the "
+"participants unilaterally rolled back the transaction."
+msgstr ""
+"発見的方法のロールバック: 一部の、又は全てのパーティシパントが一方的にトラン"
+"ザクションを ロールバックしたため、commit オペレーションは失敗します。"
+
+#. Tag: para
+#: Transactions_Overview.xml:237
+#, no-c-format
+msgid ""
+"Heuristic commit: an attempted rollback operation failed because all of the "
+"participants unilaterally committed. This may happen if, for example, the "
+"coordinator was able to successfully prepare the transaction but then "
+"decided to roll it back (for example, it could not update its log) but in "
+"the meanwhile the participants decided to commit."
+msgstr ""
+"発見的方法のコミット: 全てのパーティシパントが一方的にコミットをしたため、 "
+"ロールバックの試みは失敗となります。これは、例えば、コーディネータが トランザ"
+"クションを正しく準備できてもそれをロールバックする決心しても （例えば、そのロ"
+"グを更新できなかった状態など）、その間にパーティシパントが コミットを決定した"
+"場合、発生します。"
+
+#. Tag: para
+#: Transactions_Overview.xml:242
+#, no-c-format
+msgid ""
+"Heuristic mixed: some updates (participants) were committed while others "
+"were rolled back."
+msgstr ""
+"発見的方法のミックス: 他のパーティシパントがロールバックしている状態で、 一部"
+"の更新（パーティシパント）がコミットされる状態。"
+
+#. Tag: para
+#: Transactions_Overview.xml:247
+#, no-c-format
+msgid ""
+"Heuristic hazard: the disposition of some of the updates is unknown. For "
+"those which are known, they have either all been committed or all rolled "
+"back."
+msgstr ""
+"発見的方法のハザード: 一部の更新の処置は不明です。知られているものについては "
+"それらは全てコミットされているか、又は全てロールバックされています。"
+
+#. Tag: para
+#: Transactions_Overview.xml:252
+#, no-c-format
+msgid ""
+"Heuristic decisions should be used with care and only in exceptional "
+"circumstances since there is the possibility that the decision will differ "
+"from that determined by the transaction service and will thus lead to a loss "
+"of integrity in the system. Having to perform resolution of heuristics is "
+"something you should try to avoid, either by working with services/"
+"participants that don’t cause heuristics, or by using a transaction service "
+"that provides assistance in the resolution process."
+msgstr ""
+"発見的方法の決定は注意して使用する必要があり、その決定がトランザクション サー"
+"ビスで決定したものと異なる状態では、システムの整合性の喪失に 継る可能性がある"
+"ため、例外的な状況のみの使用となります。発見的方法の原因にならないサービス/"
+"パーティシパントを使用するか、 解決プロセスの援助を提供するトランザクション"
+"サービスを使用することにより 発見的方法の解決を実行しなければならない状況は回"
+"避すべきです。"
+
+#. Tag: title
+#: Transactions_Overview.xml:256
+#, no-c-format
+msgid "A New Transaction Protocol"
+msgstr "新規のトランザクションプロトコル"
+
+#. Tag: para
+#: Transactions_Overview.xml:257
+#, no-c-format
+msgid ""
+"Many component technologies offer mechanisms for coordinating ACID "
+"transactions based on two-phase commit semantics (i.e., CORBA/OTS, JTS/JTA, "
+"MTS/MSDTC). ACID transactions are not suitable for all Web services "
+"transactions since:"
+msgstr ""
+"多くのコンポーネント技術が、２段階コミットセマンティクス（CORBA/OTS、 JTS/"
+"JTA、MTS/MSDTC）をベースにした ACID トランザクションのコーディネイトの為の メ"
+"カニズムを提供しています。ACID トランザクションは、以下のような理由で 全ての "
+"Web サービスには適切ではありません:"
+
+#. Tag: para
+#: Transactions_Overview.xml:263
+#, no-c-format
+msgid ""
+"Classic ACID transactions are predicated on the idea that an organization "
+"that develops and deploys applications does so using their own "
+"infrastructure, typically an Intranet. Ownership meant transactions operated "
+"in a trusted and predictable manner. To assure ACIDity, potentially long-"
+"lived locks could be kept on underlying data structures during two-phase "
+"commit. Resources could be used for any period of time and released when the "
+"transaction was complete. In the Web services arena, these assumptions are "
+"no longer valid. One obvious reason is that the owners of data exposed "
+"through a Web service will refuse to allow their data to be locked for "
+"extended periods since to allow such locks invites denial-of-service."
+msgstr ""
+"古典的な ACID トランザクションは、アプリケーションを開発しデプロイする組織"
+"は、 それ自身のインフラストラクチャ、特にイントラネットを使用してそれを実行す"
+"るとのアイデアに 基づいています。所有権とは、信頼できる予測可能な方法でオペ"
+"レートできるトランザクションを 意味します。ACID 性を保証するには、長期生存の"
+"可能性を持つロックが、２段階コミットの間に 背後にあるデータ構造上に保存できる"
+"ようにします。リソースは長い期間でも使用可能でトランザクションが 完了した時に"
+"開放できます。Web サービスの舞台では、これらの仮定はもう有効ではありません。 "
+"明確な理由の１つは、Web サービスを通じて表面化したデータの所有者は、ロックを"
+"することがサービス否定攻撃を招待することになり、長期間そのデータをロックする"
+"ことを拒否するからです。"
+
+#. Tag: para
+#: Transactions_Overview.xml:268
+#, no-c-format
+msgid ""
+"All application infrastructures are generally owned by a single party, "
+"systems using classical ACID transactions normally assume that participants "
+"in a transaction will obey the will of the transaction manager and only "
+"infrequently decide to make unilateral decisions which will hamper other "
+"participants in a transaction. On the contrary, Web services participating "
+"in a transaction can effectively decide to resign from the transaction at "
+"any time, and the consumer of the service generally has little in the way of "
+"quality of service guarantees to prevent this."
+msgstr ""
+"全てのアプリケーションインフラストラクチャは一般的に単独パーティによって所有"
+"されています。 そして古典的な ACID トランザクションを使用しているシステムは、"
+"通常トランザクション内の パーティシパントがトランザクションマネージャの意志に"
+"従い、稀に一方的な決定をしてそれが トランザクション内の他のパーティシパントを"
+"妨げると推測しています。それとは逆に、 トランザクション内に参加している Web "
+"サービスは実質的に何時でもトランザクションからの 辞任を決定することが可能であ"
+"り、サービスの消費者は一般的にこれを防ぐためのサービス品質保証の 方法はあまり"
+"持ちません。"
+
+#. Tag: title
+#: Transactions_Overview.xml:274
+#, no-c-format
+msgid "Adressing the Problems of Transactioning in Loosely Coupled Systems"
+msgstr "ゆるく結合しているシステム内のトランザクション問題への対処"
+
+#. Tag: para
+#: Transactions_Overview.xml:275
+#, no-c-format
+msgid ""
+"Though extended transaction models which relax the ACID properties have been "
+"proposed over the years, to implement these concepts for the Web services "
+"architecture WS-T provides a new transaction protocol. XTS is designed to "
+"accommodate four underlying requirements inherent in any loosely coupled "
+"architecture like Web services:"
+msgstr ""
+"ACID プロパティを柔軟にするトランザクションモデルの拡張は長い間提案されて い"
+"ましたが、Web サービスアーキテクチャ WS-T の為にこのような概念を実装すること"
+"は 新規のトランザクションプロトコルを提供することになります。XTS は Web サー"
+"ビスのような ゆるく結合されたアーキテクチャ内に継承される４つの底辺要求事項を"
+"受け付けるように設計 されています。"
+
+#. Tag: para
+#: Transactions_Overview.xml:281
+#, no-c-format
+msgid ""
+"Ability to handle multiple successful outcomes to a transaction, with the "
+"ability to involve operations whose effects may not be isolated or durable;"
+msgstr ""
+"その効果が隔離化や恒久化されない可能性のあるオペレーションを巻き込む能力と共"
+"に、 トランザクションへの複数の正しい結果を処理する能力;"
+
+#. Tag: para
+#: Transactions_Overview.xml:286
+#, no-c-format
+msgid ""
+"Coordination of autonomous parties whose relationships are governed by "
+"contracts rather than the dictates of a central design authority;"
+msgstr ""
+"その関係が中央の設計権限の指示ではなく、契約により監督されている自主的パー"
+"ティの コーディネイト;"
+
+#. Tag: para
+#: Transactions_Overview.xml:291
+#, no-c-format
+msgid ""
+"Discontinuous service, where parties are anticipated to suffer outages "
+"during their lifetime, and coordinated work must be able to survive such "
+"outages;"
+msgstr ""
+"パーティがその寿命の間に作動停止を被ることと、コーディネイト作業がそのような "
+"作動停止で生存しなければならないと予想されいるような断続的なサービス;"
+
+#. Tag: para
+#: Transactions_Overview.xml:296
+#, no-c-format
+msgid ""
+"Interoperation using XML over multiple communication protocols – XTS chooses "
+"to use SOAP encoding carried over HTTP for the first release and other SOAP-"
+"friendly transports for future releases."
+msgstr ""
+"複数の通信プロトコルでの XML を使用する混合オペレーション。XTS は最初のリリー"
+"スでは 継承された HTTP を使用し、将来のリリースでは他の SOAP フレンドリーなト"
+"ランスポートを 使用するように選択します。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/ja-JP/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,1348 @@
+# translation of Stand-alone_Coordinator.po to Japanese
+# Language ja-JP translations for Transactions_Web_Services_Programmers_Guide package.
+#
+# Automatically generated, 2008.
+# Kiyoto Hashida <khashida at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-09-05 08:44+1000\n"
+"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
+"Language-Team: Japanese <jp at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:6
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Overview"
+msgstr "WS-C、WS-Atomic Transaction、及び WS-Business Activity の概要"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "はじめに"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:9
+#, no-c-format
+msgid ""
+"This section provides fundamental concepts associated with WS-C, WS-Atomic "
+"Transaction and WS-Business Activity. All of these concepts are defined in "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. WS-"
+"C, WS-Atomic Transaction and WS-Business Activity principles are discussed "
+"throughout this guide."
+msgstr ""
+"このセクションでは、WS-C、WS-Atomic Transaction、及び WS-Business Activity "
+"に 関連した基本的な概念を提供します。これらの概念の全ては WS-C、WS-Atomic "
+"Transaction、 WS-Business Activity 仕様の中で定義されています。 WS-C、WS-"
+"Atomic Transaction、 WS-Business Activity の原則はこのガイドを通じて広範囲に"
+"説明してあります。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:13
+#, no-c-format
+msgid ""
+"If you are well versed in the WS-C, WS-Atomic Transaction and WS-Business "
+"Activity specifications then you may want to just skim through this part of "
+"the manual."
+msgstr ""
+"WS-C、 WS-Atomic Transaction、 WS-Business Activity 仕様に熟知されている場合"
+"は、 マニュアルのこの部分は軽く読み流しても良いでしょう。 "
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr "WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:21
+#, no-c-format
+msgid ""
+"In general terms, coordination is the act of one entity (known as the "
+"coordinator) disseminating information to a number of participants for some "
+"domain-specific reason. This reason could be in order to reach consensus on "
+"a decision like in a distributed transaction protocol, or simply to "
+"guarantee that all participants obtain a specific message, as occurs in a "
+"reliable multicast environment. When parties are being coordinated, "
+"information known as the coordination context is propagated to tie together "
+"operations which are logically part of the same coordinated work or "
+"activity. This context information may flow with normal application "
+"messages, or may be an explicit part of a message exchange and is specific "
+"to the type of coordination being performed."
+msgstr ""
+"一般的な表現では、コーディネイト（coordination）とは、エンティティの１つ"
+"（コーディネータ）が ドメイン特有の理由で多くのパーティシパントに情報を散布す"
+"る行為のことです。特有の理由とは 分散型トランザクションプロトコルなどの決定に"
+"ついて合意に到達する為とか、あるいは 信頼できるマルチキャスト環境内で発生する"
+"ような特定メッセージを全てのパーティシパントが 取得することを保証する為などで"
+"す。パーティがコーディネイトを受けている時には、コーディネイトコンテキストと"
+"して 知られる情報は同一のコーディネイト作業又は活動の論理的一部であるオペレー"
+"ションを一緒に 組織する為に伝搬されます。このコンテキスト情報は通常のアプリ"
+"ケーションメッセージと共に 移動するかも知れないし、又はメッセージ交換内の明示"
+"的な部分であって、そして実行されている コーディネイトの種類に特定のものかも知"
+"れません。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:24
+#, no-c-format
+msgid ""
+"The fundamental idea underpinning WS-Coordination is that there is a generic "
+"need for a coordination infrastructure in a Web services environment. The WS-"
+"Coordination specification defines a framework that allows different "
+"coordination protocols to be plugged-in to coordinate work between clients, "
+"services and participants, as shown in Figure 4."
+msgstr ""
+"WS-Coordination を支持している基本的な思考は、Web サービス環境内のコーディネ"
+"イトインフラストラクチャの為に 汎用のニーズがあると言うことです。WS-"
+"Coordination 仕様は、図４に示してあるように、異なる コーディネイトプロトコル"
+"がクライアント間、サービス間、パーティシパント間で作業をコーディネイトする為"
+"にプラグインされる ようにするフレームワークを定義します。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:27
+#, no-c-format
+msgid ""
+"At this level, an activity is minimally specified and is simply created, "
+"made to run, and then completed."
+msgstr ""
+"このレベルでは、活動は最小限に指定してあり簡単に作成されて、 実行されて、それ"
+"から完了します。"
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:34
+#, no-c-format
+msgid "WS-C architecture"
+msgstr "WS-C アーキテクチャ"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:36
+#, no-c-format
+msgid ""
+"Whatever coordination protocol is used, and in whatever domain it is "
+"deployed, the same generic requirements are present:"
+msgstr ""
+"使用されるコーディネイトプロトコルが何であっても、そしてどのドメインで それが"
+"使用されていても、同じ汎用の要求がそこに存在します:"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:41
+#, no-c-format
+msgid ""
+"Instantiation (or activation) of a new coordinator for the specific "
+"coordination protocol, for a particular application instance;"
+msgstr ""
+"特定のアプリケーションインスタンス用の特定のコーディネイトプロトコル用の新規"
+"の コーディネータの具体化（又はアクティベーション）;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:46
+#, no-c-format
+msgid ""
+"Registration of participants with the coordinator, such that they will "
+"receive that coordinator’s protocol messages during (some part of) the "
+"application’s lifetime;"
+msgstr ""
+"アプリケーションの寿命の間に（その一部分で）コーディネータのプロトコルメッ"
+"セージを 受信するようにコーディネータへのパーティシパントの登録;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:51
+#, no-c-format
+msgid ""
+"Propagation of contextual information between Web services that comprise the "
+"application;"
+msgstr "アプリケーションを形成する Web サービス群の間でコンテキスト情報の伝播;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:56
+#, no-c-format
+msgid "An entity to drive the coordination protocol through to completion."
+msgstr "完了までコーディネイトプロトコルをドライブするためのエンティティ。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:61
+#, no-c-format
+msgid ""
+"The first three of these points are directly the concern of WS-Coordination "
+"while the fourth is the responsibility of a third-party entity, usually the "
+"client application that controls the application as a whole. These four WS-"
+"Coordination roles and their interrelationships are shown in Figure 5."
+msgstr ""
+"これらのポイントの最初の３つは WS-Coordination に直接係わっています。 ４つめ"
+"は、サードパーティエンティティ、すなわち通常アプリケーションを全体として 制御"
+"するクライアントアプリケーションの責務です。これらの ４つの WS-Coordination "
+"の 役目とそれらのインタラクション関係は図５で示してあります。"
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr "WS-C インフラストラクチャ"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:71
+#, no-c-format
+msgid "Activation"
+msgstr "アクティベーション"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:72
+#, no-c-format
+msgid ""
+"The WS-Coordination framework exposes an Activation Service which supports "
+"the creation of coordinators for specific protocols and their associated "
+"contexts. The process of invoking an activation service is done "
+"asynchronously, and so the specification defines both the interface of the "
+"activation service itself, and that of the invoking service, so that the "
+"activation service can call back to deliver the results of the activation – "
+"namely a context that identifies the protocol type and coordinator location. "
+"These interfaces are presented in Figure 6, where the activation service has "
+"a one-way operation that expects to receive a "
+"<code>CreateCoordinationContext</code> message and correspondingly the "
+"service that sent the <code>CreateCoordinationContext</code> message expects "
+"to be called back with a <code>CreateCoordinationContextResponse</code> "
+"message, or informed of a problem via an <code>Error</code> message."
+msgstr ""
+"WS-Coordination フレームワークは、特定のプロトコルとそれらに関連したコンテキ"
+"ストの ためのコーディネータの作成をサポートするアクティベーションサービスを表"
+"面化します。 アクティベーションサービスの呼出プロセスは非同期的に実施されるた"
+"め、その仕様は アクティベーションサービス自身のインターフェイスと呼出サービス"
+"のインターフェイスの 両方を定義します。そのためアクティベーションサービスは"
+"コールバックして、プロトコルタイプと コーディネータの場所を識別するアクティ"
+"ベーションの結果（コンテキスト）を配達します。 図６にそのインターフェイスが示"
+"してありますが、そこではアクティベーションサービスは一方通行の オペレーション"
+"を持ち、<code>CreateCoordinationContext</code> メッセージを受信する ことを予"
+"期しています。それと同じように <code>CreateCoordinationContext</code> メッ"
+"セージを 送信したサービスは <code>CreateCoordinationContextResponse</code> "
+"メッセージで コールバックされるか、又は <code>Error</code> メッセージを通じて"
+"問題を通達されることを 予期しています。"
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:76
+#, no-c-format
+msgid ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+msgstr ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:78
+#, no-c-format
+msgid "Registration"
+msgstr "登録"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:79
+#, no-c-format
+msgid ""
+"Once a coordinator has been instantiated and a corresponding context created "
+"by the activation service, a Registration Service is created and exposed. "
+"This service allows participants to register to receive protocol messages "
+"associated with a particular coordinator. Like the activation service, the "
+"registration service assumes asynchronous communication and so specifies "
+"WSDL for both registration service and registration requester, as shown "
+"below."
+msgstr ""
+"コーディネータが具体化されて、その該当するコンテキストがアクティベーション "
+"サービスによって作成されると、登録サービスが作成されて表面化されます。 この"
+"サービスはパーティシパントが、特定のコーディネータに関連のあるプロトコル メッ"
+"セージを受信する為の登録をできるようにします。アクティベーションサービスと 同"
+"様に、登録サービスは非同期通信を想定しており、以下に示すような登録サービスと "
+"登録要求の両方の為の WSDL を指定します。"
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:83
+#, no-c-format
+msgid ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+msgstr ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:84
+#, no-c-format
+msgid ""
+"When a participant is registered with a coordinator through the registration "
+"service, it receives messages that the coordinator sends (for example, "
+"“prepare to complete” and “complete” messages if a two-phase protocol is "
+"used); where the coordinator’s protocol supports it, participants can also "
+"send messages back to the coordinator."
+msgstr ""
+"パーティシパントが、登録サービスを通じてコーディネータに登録されると、 コー"
+"ディネータが送信するメッセージ（例えば、“prepare to complete”、2段階プロトコ"
+"ルの場合は “complete”）を受信するようになります。コーディネータのプロトコルが"
+"サポートする場合は、 パーティシパントはコーディネータにメッセージを送り返すこ"
+"ともできます。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:88
+#, no-c-format
+msgid "Completion"
+msgstr "完了"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:89
+#, no-c-format
+msgid ""
+"The role of terminator is generally played by the client application, which "
+"at an appropriate point will ask the coordinator to perform its particular "
+"coordination function with any registered participants – to drive the "
+"protocol through to its completion. On completion, the client application "
+"may be informed of an outcome for the activity which may vary from simple "
+"succeeded/failed notification through to complex structured data detailing "
+"the activity’s status."
+msgstr ""
+"ターミネータ（terminator）の役目は通常クライアントアプリケーションが 演じま"
+"す。これは適切な時点でコーディネータに対して、登録してあるパーティシパント で"
+"使用している特定のコーディネイト機能を実行して、プロトコルをその完了まで駆動"
+"するように 依頼します。完了すると、クライアントアプリケーションはその活動の結"
+"果報告を 受けますが、これは単純な成功/失敗の通知から活動状態の詳細を持つデー"
+"タ構成までの 変化幅があります。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:96
+#, no-c-format
+msgid "WS-Transaction"
+msgstr "WS-Transaction"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:97
+#, no-c-format
+msgid ""
+"In the past, making traditional transaction systems talk to one another was "
+"a holy grail that was rarely achieved. With the advent of Web services, "
+"there is an opportunity to leverage an unparalleled interoperability "
+"technology to splice together existing transaction processing systems that "
+"already form the backbone of enterprise level applications."
+msgstr ""
+"過去には、伝統的なトランザクションシステム同士に会話をさせることは 稀にしか達"
+"成できない神聖なことでした。しかし Web サービスの出現により これまでにない相"
+"互オペレーションの技術を活用する機会が、エンタープライズレベルの アプリケー"
+"ションのバックボーンをすでに構成している既存のトランザクション プロセッシング"
+"システム群を結合できるようにしています。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:101
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr "WS-Coordination の基盤"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:102
+#, no-c-format
+msgid ""
+"An important aspect of WS-Transaction that differentiates it from "
+"traditional transaction protocols is that a synchronous request/response "
+"model is not assumed. This model derives from the fact that WS-Transaction "
+"is, as shown in the figure below, layered upon the WS-Coordination protocol "
+"whose own communication patterns are asynchronous by default."
+msgstr ""
+"WS-Transaction が伝統的なトランザクションプロトコルに差を付ける重要な 側面は"
+"同期の要求/応答モデルが想定されていないことです。このモデルは WS-Transaction "
+"が、下図に示してあるように、自身の通信パターンがデフォルトで 非同期である WS-"
+"Coordination プロトコルに階層化されている事実に由来しています。"
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:110
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr "WS-Coordination、 WS-Atomic Transaction、及び WS-Business Activity"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:112
+#, no-c-format
+msgid ""
+"Web Services Coordination provides a generic framework for specific "
+"coordination protocols, like WS-Transaction, to be plugged in. Recall that "
+"WS-Coordination provides only context management – it allows contexts to be "
+"created and activities to be registered with those contexts. WS-Transaction "
+"leverages the context management framework provided by WS-Coordination in "
+"two ways. Firstly it extends the WS-Coordination context to create a "
+"transaction context. Secondly, it augments the activation and registration "
+"services with a number of additional services (Completion, "
+"CompletionWithAck, PhaseZero, 2PC, OutcomeNotification, BusinessAgreement, "
+"and BusinessAgreementWithComplete) and two protocol message sets (one for "
+"each of the transaction models supported in WS-Transaction) to build a fully-"
+"fledged transaction coordinator on top the WS-Coordination protocol "
+"infrastructure."
+msgstr ""
+"Web サービスコーディネイトは WS-Transaction のようなプラグインされることにな"
+"る 特定の調整プロトコルの為の汎用フレームワークを提供します。 WS-"
+"Coordination がコンテキスト管理のみを提供することを思い出して 下さい。これは"
+"コンテキストを作成できるようにして、そのコンテキストを 使用して活動が登録でき"
+"るようにします。WS-Transaction は WS-Coordination で 提供されるコンテキスト管"
+"理フレームワークを２つの方法で増強します。１つめは WS-Coordination コンテキス"
+"トを拡張してトランザクションコンテキストを作成 することです。２つめはアクティ"
+"ベーションと登録に多数の追加サービス（Completion、 CompletionWithAck、"
+"PhaseZero、2PC、OutcomeNotification、BusinessAgreement 及び "
+"BusinessAgreementWithComplete）と２つのプロトコルメッセージセット（WS-"
+"Transaction 内で サポートされている各トランザクションモデル毎に１つ）の引数を"
+"付けて、WS-Coordination プロトコル インフラストラクチャの上に完全専従のトラン"
+"ザクションコーディネータを構築することです。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:116
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr "WS-Transaction アーキテクチャ"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:117
+#, no-c-format
+msgid ""
+"WS-Transaction supports the notion of the service and participant as "
+"distinct roles, making the distinction between a transaction-aware service "
+"and the participants that act on behalf of the service during a transaction: "
+"transactional services deal with business-level protocols, while the "
+"participants handle the underlying WS-Transaction protocols, as shown above."
+msgstr ""
+"WS-Transaction はサービスとパーティシパントの概念を区別した役目としてサポー"
+"ト して、トランザクション認識のサービスとトランザクションの期間中にそのサービ"
+"スの 代理として行動するパーティシパントとを分別します。トランザクションサービ"
+"スは ビジネスレベルのプロトコルを扱い、前述にあるようにパーティシパントは背後"
+"にある WS-Transaction プロトコルを扱います。"
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:125
+#, no-c-format
+msgid "WS-Transaction Global View"
+msgstr "WS-Transaction のグローバルビュー"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:127
+#, no-c-format
+msgid ""
+"A transaction-aware service encapsulates the business logic or work that is "
+"required to be conducted within the scope of a transaction. This work cannot "
+"be confirmed by the application unless the transaction also commits and so "
+"control is ultimately removed from the application and placed into the "
+"transaction’s domain."
+msgstr ""
+"トランザクション認識のサービスは、トランザクションの有効範囲内で実践される 必"
+"要のあるビジネス論理、あるいは作業をカプセル化します。この作業は、トランザク"
+"ションも コミットしない限りはアプリケーションによって確認されないため、制御は"
+"最終的に アプリケーションから削除されてトランザクションの領域に配置されます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:130
+#, no-c-format
+msgid ""
+"The participant is the entity that, under the dictates of the transaction "
+"coordinator, controls the outcome of the work performed by the transaction-"
+"aware Web service. In the figure above each service is shown with one "
+"associated participant that manages the transaction protocol messages on "
+"behalf of its service, while in the figure below, there is a close-up view "
+"of a single service, and a client application with their associated "
+"participants."
+msgstr ""
+"パーティシパントは、トランザクションコーディネータの権限下で、トランザクショ"
+"ン 認識の Web サービスにより実行される作業の結果を制御します。上記の図では、 "
+"サービスの代表としてトランザクションプロトコルメッセージを管理する 関連パー"
+"ティシパント１つを持つ各サービスが示されています。下記の図では、単独のサービ"
+"スと その関連パーティシパントを持つクライアントアプリケーションが１つクローズ"
+"アップで 示されています。"
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:137
+#, no-c-format
+msgid "Transactional Service and Participant"
+msgstr "トランザクショナルサービスとパーティシパント"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:139
+#, no-c-format
+msgid ""
+"The transaction-aware Web service and its participant both serve a shared "
+"transactional resource, and there is a control relationship between them "
+"through some API - which on the Java platform is JAXTX. In the example shown "
+"in the figure above, it is assumed that the database is accessed through a "
+"transactional JDBC database driver, where SQL statements are sent to the "
+"database for processing via that driver, but where those statements will be "
+"tentative and only commit if the transaction does. In order to do this, the "
+"driver/database will associate a participant with the transaction which will "
+"inform the database of the transaction outcome. Since all transactional "
+"invocations on the Web service carry a transaction context, the participant "
+"working with the database is able to identify the work that the "
+"transactional service did within the scope of a specific transaction and "
+"either commit or rollback the work."
+msgstr ""
+"トランザクション認識の Web サービスとそのパーティシパントは両方とも 共有のト"
+"ランザクショナルリソースにサービスし、いくつかの API を通じて その両者間に制"
+"御関係があります。これは Java プラットフォームでは JAXTX です。 上記の図に示"
+"されている例では、データベースがトランザクショナル JDBC データベース ドライ"
+"バーを通じてアクセスされると想定されており、ここでは SQL ステートメントは そ"
+"のドライバーを通じてプロセッシングの為にデータベースに送られることになりま"
+"す。 しかし、それらのステートメントが試験的であり、トランザクションがコミット"
+"した場合 にのみコミットします。これを行うには、ドライバー/データベースはパー"
+"ティシパントと、 トランザクション結果をデータベースに報告するトランザクション"
+"とを関連付けします。 Web サービス上の全てのトランザクショナル呼出はトランザク"
+"ションコンテキストを運び ますので、データベースを使って作業しているパーティシ"
+"パントは特定のトランザクションの 範囲内でトランザクションナルサービスが行った"
+"作業を識別することが出来て、その作業を コミットするか、又はロールバックしま"
+"す。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:142
+#, no-c-format
+msgid ""
+"At the client end, things are less complex. Through its API, the client "
+"application registers a participant with the transaction through which it "
+"controls transaction termination."
+msgstr ""
+"クライアントの側では、複雑度は少なくなります。その API を通して、クライアン"
+"ト アプリケーションはパーティシパントをトランザクションに登録します。この登録"
+"を 通じてトランザクションの終結を制御します。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:146
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr "WS-Transaction モデル"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:147
+#, no-c-format
+msgid ""
+"Given that traditional transaction models are not appropriate for Web "
+"services, the following question must be posed, “what type of model or "
+"protocol is appropriate?” The answer to that question is that that no one "
+"specific protocol is likely to be sufficient, given the wide range of "
+"situations that Web service transactions are likely to be deployed within. "
+"Hence the WS-Transaction specification proposes two distinct models, where "
+"each supports the semantics of a particular kind of B2B interaction. The "
+"following sections shall discuss these two WS-Transaction models."
+msgstr ""
+"伝統的なトランザクションモデルが Web サービスには適切でないと言う状況で、 次"
+"のような疑問が出てきます。「どのタイプのモデル、あるいはプロトコルが 適切"
+"か？」この疑問への答えは、Web サービストランザクションがその範囲内で デプロイ"
+"される状況が広範囲に及ぶためどの特定のプロトコルも単独では十分でないと 言うこ"
+"とです。そこで、WS-Transaction 仕様は、それぞれが特定の種類の B2B インタラク"
+"ションの セマンティクスをサポートする２つの独立したモデルを提案します。以下の"
+"セクションで これらの２つの WS-Transaction モデルを説明します。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:152
+#, no-c-format
+msgid ""
+"As with WS-Coordination, the two WS-Transaction models are extensible "
+"allowing implementations to tailor the protocols as they see fit (for "
+"example, to suit their deployment environments)."
+msgstr ""
+"WS-Coordination と同様に、２つの WS-Transaction モデルは拡張可能で、 必要に応"
+"じてプロトコルを注文仕立てするための実装ができるようになります。 （例えば、そ"
+"れらのデプロイメント環境に適合するように）"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:157
+#, no-c-format
+msgid "Atomic Transactions (AT)"
+msgstr "アトミックトランザクション (AT)"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:158
+#, no-c-format
+msgid ""
+"An atomic transaction or AT is similar to traditional ACID transactions and "
+"intended to support short-duration interactions where ACID semantics are "
+"appropriate. Within the scope of an AT, services typically enroll "
+"transaction-aware resources, such as databases and message queues, "
+"indirectly as participants under the control of the transaction. When the "
+"transaction terminates, the outcome decision of the AT is then propagated to "
+"each enlisted resource via the participant, and the appropriate commit or "
+"rollback actions are taken by each."
+msgstr ""
+"原子性トランザクション、いわゆるアトミックトランザクション (AT)、は伝統的な "
+"ACID トランザクションに似ており、ACID セマンティクスが適切となる短期間の イン"
+"タラクションをサポートするように意図されています。AT の有効範囲内では、サービ"
+"スは 一般的にデータベースやメッセージキューなどのトランザクション認識のリソー"
+"スを トランザクションの制御下で間接的にパーティシパントとして採り入れます。 "
+"トランザクションが終結すると、AT の結果決定はその後パーティシパントを通じて "
+"雇用されている各リソースに伝播されます。そしてそれぞれによって適切なコミッ"
+"ト、又は ロールバックのアクションが実施されます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:162
+#, no-c-format
+msgid ""
+"This protocol is very similar to those employed by traditional transaction "
+"systems that already form the backbone of an enterprise. It is assumed that "
+"all services (and associated participants) provide ACID semantics and that "
+"any use of atomic transactions occurs in environments and situations where "
+"this is appropriate: in a trusted domain, over short durations."
+msgstr ""
+"このプロトコルは、企業の骨組みをすでに形成している伝統的なトランザクション シ"
+"ステムで起用されているプロトコルに非常に似ています。このプロトコルは、 全ての"
+"サービス（及び関連したパーティシパント）が ACID セマンティクスを 提供するこ"
+"と、そして原子性のトランザクションの使用はいずれもこれが適切な 環境と状況（信"
+"頼できるドメイン内で短期間）で発生することを想定しています。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:165
+#, no-c-format
+msgid ""
+"To begin an atomic transaction, the client application firstly locates a WS-"
+"Coordination coordinator Web service that supports WS-Transaction. Once "
+"located, the client sends a WS-Coordination CreateCoordinationContext "
+"message to the activation service specifying http://schemas.xmlsoap.org/"
+"ws/2004/10/wsat as its coordination type and will get back an appropriate WS-"
+"Transaction context from the activation service. The response to the "
+"CreateCoordinationContext message, the transaction context, has its "
+"CoordinationType element set to the WS-Atomic Transaction namespace, http://"
+"schemas.xmlsoap.org/ws/2004/10/wsat, and also contains a reference to the "
+"atomic transaction coordinator endpoint (the WS-Coordination registration "
+"service) where participants can be enlisted."
+msgstr ""
+"原子性トランザクションを開始するために、クライアントアプリケーションは先ず、 "
+"WS-Transaction をサポートする WS-Coordination コーディネータ Web サービスを "
+"配置しなければなりません。それが配置されると、クライアントはアクティベーショ"
+"ン サービスに対して WS-Coordination CreateCoordinationContext メッセージを送"
+"信 して、http://schemas.xmlsoap.org/ws/2004/10/wsat をそのコーディネイトタイ"
+"プとして指定し、 アクティベーションサービスから適切な WS-Transaction コンテキ"
+"ストを取り戻します。 CreateCoordinationContext メッセージへの応答（トランザク"
+"ションコンテキスト）は その CoordinationType 要素を WS-Atomic Transaction "
+"ネームスペース http://schemas.xmlsoap.org/ws/2004/10/wsat にセットしてあり、"
+"パーティシパントが採用される 原子性トランザクションコーディネータの終点（WS-"
+"Coordination 登録サービス）への参照も含まれています。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:168
+#, no-c-format
+msgid ""
+"After obtaining a transaction context from the coordinator, the client "
+"application then proceeds to interact with Web services to accomplish its "
+"business-level work. With each invocation on a business Web service, the "
+"client inserts the transaction context into a SOAP header block, such that "
+"each invocation is implicitly scoped by the transaction – the toolkits that "
+"support WS-Atomic Transaction-aware Web services provide facilities to "
+"correlate contexts found in SOAP header blocks with back-end operations."
+msgstr ""
+"コーディネータからトランザクションコンテキストを取得した後、クライアント アプ"
+"リケーションは Web サービスとのインタラクションに進んでそのビジネスレベルの作"
+"業を 達成します。ビジネス Web サービスでのそれぞれの呼び出しで、クライアント"
+"は トランザクションコンテキストを SOAP ヘッダブロックに挿入します。そして 各"
+"呼び出しがトランザクションにより暗黙に機会を与えられるようにします。 WS-"
+"Atomic Transaction 認識の Web サービスをサポートするツールキットは SOAP ヘッ"
+"ダブロック内にあるコンテキストをバックエンドオペレーションに 相互関係づける機"
+"能を提供します。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:171
+#, no-c-format
+msgid ""
+"Once all the necessary application level work has been completed, the client "
+"can terminate the transaction, with the intent of making any changes to the "
+"service state permanent. To do this, the client application first registers "
+"its own participant for the Completion protocol. Once registered, the "
+"participant can instruct the coordinator either to try to commit or rollback "
+"the transaction. When the commit or rollback operation has completed, a "
+"status is returned to the participant to indicate the outcome of the "
+"transaction."
+msgstr ""
+"全ての必要なアプリケーションレベルの作業が完了すると、クライアントは サービス"
+"への変更はいずれも永久化の状態にする意図を持ってそのトランザクションを 終結す"
+"ることができます。これを実施するには、クライアントアプリケーションは先ず、 "
+"Completion プロトコルの為にそれ自身のパーティシパントを登録します。登録が 終"
+"了すると、パーティシパントはコーディネータに対してトランザクションのコミッ"
+"ト、 又はロールバックを試みるように指示します。コミットかロールバックのオペ"
+"レーションが 完了すると、状態はパーティシパントに戻されてそのトランザクション"
+"の結果を表示する ようになります。 "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:174
+#, no-c-format
+msgid ""
+"While the completion protocol is straightforward, they hide the fact that in "
+"order to resolve to an outcome that several other protocols need to be "
+"executed."
+msgstr ""
+"Completion プロトコルは簡単なものですが、そこには結果に対する決定をする為に "
+"他のいくつかのプロトコルを実行する必要があると言う事実が隠れています。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:177
+#, no-c-format
+msgid ""
+"The first of these protocols is the optional Volatile2PC. The Volatile2PC "
+"protocol is the WS-Atomic Transaction equivalent of the synchronization "
+"protocol we discussed earlier. It is typically executed where a Web service "
+"needs to flush volatile (cached) state, which may be being used to improve "
+"performance of an application, to a database prior to the transaction "
+"committing. Once flushed, the data will then be controlled by a two-phase "
+"aware participant."
+msgstr ""
+"これらのプロトコルの１つめは、オプションの Volatile2PC です。Volatile2PC プロ"
+"トコルは 以前に説明してある同期化プロトコルに対する WS-Atomic トランザクショ"
+"ンの 同等物です。これは標準的には、アプリケーションのパフォーマンスを向上する"
+"ために 使用されている揮発性の（キャッシュ化）状態をWeb サービスがフラッシュす"
+"る 必要のある部分でトランザクションがコミットする前にデータベースに対して実行"
+"されます。 フラッシュされると、データはそれから２段階認識のパーティシパントに"
+"よって制御されます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:180
+#, no-c-format
+msgid ""
+"All Volatile2PC participants are told that the transaction is about to "
+"complete (via the prepare message) and they can respond with either the "
+"prepared, aborted or readonly message; any failures at this stage will cause "
+"the transaction to rollback."
+msgstr ""
+"全ての Volatile2PC パーティシパントは、トランザクションが完了間近である こと"
+"を通達（prepare メッセージ経由）されて、それらのパーティシパントは prepared、"
+"aborted、又は readonly メッセージで応答することができます。 この段階での障害"
+"はいずれもトランザクションがロールバックする原因になります。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:183
+#, no-c-format
+msgid ""
+"After Volatile2PC prepare, the next protocol to execute in WS-Atomic "
+"Transaction is Durable2PC. The Durable2PC (an abbreviation of the term two-"
+"phase commit) protocol is at the very heart of WS-Atomic Transaction and is "
+"used to bring about the necessary consensus between participants in a "
+"transaction such that the transaction can safely be terminated."
+msgstr ""
+"Volatile2PC prepare の後、WS-Atomic Transaction 内で実行する次の プロトコル"
+"は Durable2PC です。Durable2PC （2PC は２段階コミットの略字） プロトコルは "
+"WS-Atomic Transaction の核心になるもので、トランザクション内の パーティシパン"
+"ト間に必要な同意をもたらして、トランザクションが安全に 終結するようにするもの"
+"です。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:186
+#, no-c-format
+msgid ""
+"The two-phase commit protocol is used to ensure atomicity between "
+"participants, and is based on the classic two-phase commit with presumed "
+"abort technique. During the first phase, when the coordinator sends the "
+"prepare message, a participant must make durable any state changes that "
+"occurred during the scope of the transaction, such that these changes can "
+"either be rolled back or committed later. That is, any original state must "
+"not be lost at this point as the atomic transaction could still roll back. "
+"If the participant cannot prepare then it must inform the coordinator (via "
+"the aborted message) and the transaction will ultimately roll back. If the "
+"participant is responsible for a service that did not do any work during the "
+"course of the transaction, or at least did not do any work that modified any "
+"state, it can return the readonly message and it will be omitted from the "
+"second phase of the commit protocol. Otherwise, the prepared message is sent "
+"by the participant."
+msgstr ""
+"２段階コミットプロトコルはパーティシパント間の原子性を確証する為に使用される"
+"もので、 推測される中止技術を使用する古典的な２段階コミットをベースにしていま"
+"す。第１段階では コーディネータが prepare メッセージを送った時にパーティシパ"
+"ントはトランザクションの 範囲内で発生した状態変化を恒久化して、それらの変更が"
+"後でロールバック、又はコミット できるようにしなければなりません。このことは、"
+"原子性トランザクションが まだロールバックできるため、オリジナルの状態はいずれ"
+"もこの時点では消失しないように する必要があると言うことです。パーティシパント"
+"が準備できない場合、コーディネータに（中止メッセージを介して） 通達しなければ"
+"ならず、そうするとトランザクションは最終的にロールバックされます。パーティシ"
+"パントが、 トランザクションの期間中にいずれの作業もしていない、あるいは状態を"
+"変更した作業をしていないサービスに ついて責務を持つ場合は readonly メッセージ"
+"を送ることができ、コミットプロトコルの第２段階から外され ます。それ以外の場合"
+"は準備のメッセージがパーティシパントにより送信されます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:189
+#, no-c-format
+msgid ""
+"Assuming no failures occurred during the first phase, in the second phase "
+"the coordinator sends the commit message to participants, who will make "
+"permanent the tentative work done by their associated services."
+msgstr ""
+"第１段階で障害が発生しなかったと想定して、第２段階でコーディネータはパーティ"
+"シパントに コミットメッセージを送信します。パーティシパントはそれらの関連した"
+"サービスに よってなされた試験的な作業を永久化します。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:192
+#, no-c-format
+msgid ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
+msgstr ""
+"トランザクションがただ１つのパーティシパントだけを巻き込んでいる場合は、 WS-"
+"Atomic Transaction は１段階コミットの最適化をサポートします。パーティシパント"
+"が １つだけですから、その決定は暗黙に同意に到達するそのため、コーディネータは"
+"２つの段階を 経てトランザクションを駆動する必要はありません。最適化してある"
+"ケースでは、パーティシパントは 単にコミットすることを指示され、トランザクショ"
+"ンの結果はその単独パーティシパントだけのものですから トランザクションコーディ"
+"ネータはその決定に関して情報を記録する必要はありません。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:195
+#, no-c-format
+msgid ""
+"The figure below<footnote> <para> Redrawn from the WS-Atomic Transaction "
+"specification. </para> </footnote> shows the state transitions of a WS-"
+"Atomic Transaction and the message exchanges between coordinator and "
+"participant; the coordinator generated messages are shown in the solid line, "
+"whereas the participant messages are shown by dashed lines."
+msgstr ""
+"以下の図：<footnote> <para>WS-Atomic Transaction 仕様から再描画したものです。"
+"</para> </footnote> は WS-Atomic Transaction のトランザクション 状態とコー"
+"ディネータとパーティシパント間のメッセージ交換を示しています。 コーディネータ"
+"生成のメッセージは実線で示してあり、パーティシパントのメッセージは 断線で示し"
+"てあります。"
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:206
+#, no-c-format
+msgid "Two-Phase Commit State Transitions"
+msgstr "２段階コミット状態転移"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:208
+#, no-c-format
+msgid ""
+"Once the 2PC protocol has finished, the Completion protocol that originally "
+"began the termination of the transaction can complete, and inform the client "
+"application whether the transaction was committed or rolled back. "
+"Additionally, the Volatile2PC protocol may complete."
+msgstr ""
+"2PC プロトコルが終了すると、最初にトランザクション終結を開始した Completion "
+"プロトコルは 完了できるようになり、クライアントアプリケーションに対してトラン"
+"ザクションがコミット されたか、又はロールバックされたかを通達することができま"
+"す。さらには、Volatile2PC プロトコルも完了できます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:211
+#, no-c-format
+msgid ""
+"Like the prepare phase of Volatile2PC, the final phase is optional and can "
+"be used to inform participants when the transaction has completed, typically "
+"so that they can release resources (for example, put a database connection "
+"back into the pool of connections)."
+msgstr ""
+"Volatile2PC の準備段階のように最終段階はオプションであり、トランザクションが "
+"完了した時にそれらがリソースを開放できるように（例えば、データベース接続を接"
+"続のプールに戻す）、 標準的にパーティシパントに通達するのに使用できます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:214
+#, no-c-format
+msgid ""
+"Any registered Volatile2PC participants are invoked after the transaction "
+"has terminated and are told the state in which the transaction completed "
+"(the coordinator sends either the Committed or Aborted message). Since the "
+"transaction has terminated, any failures of participants at this stage are "
+"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
+"the transaction."
+msgstr ""
+"登録済みの Volatile2PC パーティシパントはどれもトランザクションが 終結した後"
+"に呼び出されてトランザクションが完了した状態を通達されます。 （コーディネータ"
+"は完了済みか、中止済みのメッセージを送ります）トランザクションは 終結していま"
+"すから、この時点でのパーティシパントの障害は無視されます。これは 基本的に社交"
+"的な通信でありトランザクションの結果に何も影響ありません。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:217
+#, no-c-format
+msgid ""
+"Finally, after having gone through each of the stages in an AT, it is "
+"possible to see the intricate interweaving of individual protocols that goes "
+"to make up the AT as a whole in the following figure."
+msgstr ""
+"最後に AT 内の各ステージを通過した後には、以下の図にあるような  AT を 全体と"
+"して構成する個別のプロトコルの入り込んだ網羅を見ることができます。"
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:224
+#, no-c-format
+msgid "The AT Model"
+msgstr "AT モデル"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:227
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr "ビジネス活動  (BA)"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:228
+#, no-c-format
+msgid ""
+"Most business-to-business applications require transactional support in "
+"order to guarantee consistent outcome and correct execution. These "
+"applications often involve long running computations, loosely coupled "
+"systems and components that do not share data, location, or administration "
+"and it is difficult to incorporate atomic transactions within such "
+"architectures. For example, an online bookshop may reserve books for an "
+"individual for a specific period of time, but if the individual does not "
+"purchase the books within that period they will be “put back onto the shelf” "
+"for others to buy. Furthermore, because it is not possible for anyone to "
+"have an infinite supply of stock, some online shops may appear to users to "
+"reserve items for them, but in fact may allow others to pre-empt that "
+"reservation (for instance, the same book may be “reserved” for multiple "
+"users concurrently); a user may subsequently find that the item is no longer "
+"available, or may have to be reordered specially for them."
+msgstr ""
+"ほとんどのビジネス対ビジネスのアプリケーションは、均一的な結果と正しい実行を "
+"保証する為にトランザクショナルサポートを必要とします。これらのアプリケーショ"
+"ンは 長期間実行の演算、緩い結合のシステムとデータ共有をしないコンポーネント、"
+"場所、 又は管理などを巻き込んでおり、そのようなアーキテクチャ内で原子性のトラ"
+"ンザクションを 統合するのは難しい状態です。例えば、オンラインのブックショップ"
+"がある個人の為に 特定の期間だけ本を保留しておいたとします。しかし、その個人が"
+"その期間内に本を 購入しない場合は、他の客のために本を棚に戻します。さらには、"
+"誰も無限的にストックの 供給をできないため、一部のオンラインショップは客の為に"
+"本を保留しているように見えても、 実際には他の客にその保留物を先取りさせる（例"
+"えば、同じ本が同時に複数予約されている場合）かも しれません。その場合、最初の"
+"客は注文した本が無くなったことを知るか、あるいはそれを再度 予約する必要がある"
+"かも知れません。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:232
+#, no-c-format
+msgid ""
+"A business activity or BA is designed specifically for these kinds of long-"
+"duration interactions, where exclusively locking resources is impossible or "
+"impractical. In this model services are requested to do work, and where "
+"those services have the ability to undo any work, they inform the BA such "
+"that if the BA later decides the cancel the work (for instance if the "
+"business activity suffers a failure), it can instruct the service to execute "
+"its undo behavior. The key point for Business Activities is that how "
+"services do their work and provide compensation mechanisms is not the domain "
+"of the WS-Business Activity specification, but an implementation decision "
+"for the service provider."
+msgstr ""
+"ビジネス活動（BA）は特に長期間インタラクションの為に設計されたもので、そこで"
+"は、 専従的にリソースをロックすることはほとんど不可能で非現実的になります。 "
+"このモデルでは、サービスは作業をするように依頼されて、それらのサービスが いか"
+"なる作業をも元に戻すことができる部分では、 BA が後で作業を取り消す決断をした"
+"場合 （例えば、BA が障害を受けた時など）、 BA がサービスにその復元動作を実行"
+"するように 指示できることをサービスが BA に対してを伝えます。ビジネス活動の為"
+"のキーポイントは、 サービスがその作業を実施する手段とその補正の提供手段は WS-"
+"Business Activity 仕様の 領域ではなく、サービス提供者の実装決定であると言う点"
+"です。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:235
+#, no-c-format
+msgid ""
+"The WS- Business Activity simply defines a protocol for Web services-based "
+"applications to enable existing business processing and workflow systems to "
+"wrap their proprietary mechanisms and interoperate across implementations "
+"and business boundaries."
+msgstr ""
+"WS- Business Activity は単に Web サービスベースのアプリケーションの為にプロト"
+"コルを 定義して既存のビジネスプロセッシングとワークフローシステムを有効にする"
+"ことで、 それらのプロプライエタリメカニズムを包み込んで実装とビジネス境界全域"
+"に渡って 相互オペレーションを得るようにします。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:238
+#, no-c-format
+msgid ""
+"A business activity may be partitioned into scopes, where a scope is a "
+"business task or unit of work using a collection of Web services. Such "
+"scopes can be nested to arbitrary degrees, forming parent and child "
+"relationships, where a parent scope has the ability to select which child "
+"tasks are to be included in the overall outcome protocol for a specific "
+"business activity, and so clearly non-atomic outcomes are possible. In a "
+"similar manner to traditional nested transactions, if a child task "
+"experiences an error, it can be caught by the parent who may be able to "
+"compensate and continue processing."
+msgstr ""
+"ビジネス活動はいくつかの範囲（scope）に分けることができて、そこでは１つの範囲"
+"は Web サービスのコレクションを使用したビジネスタスク、又は作業の単位と なり"
+"ます。そのような範囲群は任意のレベルでネスト化が可能で、ペアレントと チャイル"
+"ドの関係を構成することができます。その中ではペアレント範囲はどの チャイルドタ"
+"スクが、特定のビジネス活動の為の全体的な結果プロトコル内に 含まれるべきかを選"
+"択する能力を持ちます。そして明確に原子性でない結果も 可能になります。伝統的な"
+"ネスト化のトランザクションに似た方法で、チャイルド タスクがエラーを経験してい"
+"る場合、そのプロセスを補正して継続できるペアレントに よって保護されることが出"
+"来ます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:241
+#, no-c-format
+msgid ""
+"When a child task completes it can either leave the business activity or "
+"signal to the parent that the work it has done can be compensated later. In "
+"the latter case, the compensation task may be called by the parent should it "
+"ultimately need to undo the work performed by the child."
+msgstr ""
+"チャイルドタスクが完了すると、それはビジネス活動を退去するか、あるいは 実行し"
+"た作業は後で補正できることの信号をペアレントに送信します。後者の ケースでは、"
+"チャイルドによって実行された作業が最終的にやり直しの必要を 持つ場合、補正タス"
+"クがペアレントによって呼び込まれます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:244
+#, no-c-format
+msgid ""
+"Unlike the WS-Atomic Transaction protocol model, where participants inform "
+"the coordinator of their state only when asked, a task within a business "
+"activity can specify its outcome to the parent directly without waiting for "
+"a request. This feature is useful when tasks fail such that the notification "
+"can be used by business activity exception handler to modify the goals and "
+"drive processing forward without having to meekly wait until the end of the "
+"transaction to admit to having failed – a well designed Business Activities "
+"should be proactive, if it is to perform well."
+msgstr ""
+"依頼された時にのみパーティシパントがコーディネータにその状態を通達すると言う "
+"WS-Atomic Transaction プロトコルモデルとは異なり、ビジネス活動内のタスクは 要"
+"求を待たずに直接ペアレントにその結果を指定することができます。この特徴は、 タ"
+"スクが失敗して、その通知がビジネス活動例外ハンドラーによって使用されて、 トラ"
+"ンザクションが失敗を認めることを黙って待つことなしに ゴールを修正してプロセス"
+"を前に駆動させる点で役に立ちます。良く機能するように 期待されている限りは、良"
+"く設計されたビジネス活動は前進的である必要があります。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:247
+#, no-c-format
+msgid "Underpinning all of this are three fundamental assumptions:"
+msgstr "この全てを支持しているのは、３つの基盤となる推測です:"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:252
+#, no-c-format
+msgid ""
+"All state transitions are reliably recorded, including application state and "
+"coordination metadata (the record of sent and received messages);"
+msgstr ""
+"全ての状態転移は、アプリケーションの状態と coordination メタデータ （送信済み"
+"と受信済みのメッセージ記録）を含んで信頼できる方法で記録されています;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:257
+#, no-c-format
+msgid ""
+"All request messages are acknowledged, so that problems are detected as "
+"early as possible. This avoids executing unnecessary tasks and can also "
+"detect a problem earlier when rectifying it is simpler and less expensive;"
+msgstr ""
+"全ての要求メッセージが承諾されて、問題は可能な限り早期に検出できる ようにしま"
+"す。これにより、不要なタスクの実行を避けて、訂正が簡単で 負担が少ない時に早期"
+"に問題を検出することもできます;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:262
+#, no-c-format
+msgid ""
+"As with atomic transactions, a response is defined as a separate operation "
+"and not as the output of the request. Message input-output implementations "
+"will typically have timeouts that are too short for some business activity "
+"responses. If the response is not received after a timeout, it is resent. "
+"This is repeated until a response is received. The request receiver discards "
+"all but one identical request received."
+msgstr ""
+"原子性トランザクションの使用と同様に、応答とは要求の出力としてでなく、別の オ"
+"ペレーションとして定義されています。メッセージ入力/出力の実装は標準的に 一部"
+"のビジネス活動応答には短すぎるタイムアウト設定を持っています。応答が タイムア"
+"ウトの後まで受信されない場合は、リセットされます。これは応答が 受信されるまで"
+"繰り返されます。要求レシーバーは受信した１つの同一要求以外は すべて破棄しま"
+"す。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:267
+#, no-c-format
+msgid ""
+"As with atomic transactions, the business activity model has multiple "
+"protocols: <code>BusinessAgreementWithParticipantCompletion</code> and "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. However, unlike the "
+"AT protocol which is driven from the coordinator down to participants, this "
+"protocol is driven much more from the participants upwards."
+msgstr ""
+"原子性トランザクションの使用と同様に、ビジネス活動モデルは複数のプロトコルを"
+"持ち ます: <code>BusinessAgreementWithParticipantCompletion</code> と "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> です。しかし、 コー"
+"ディネータからパーティシパントに下方に駆動する AT プロトコルとは異なり、 この"
+"プロトコルはもっと多くパーティシパントから上方に駆動されます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
+#, no-c-format
+msgid ""
+"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
+"a child activity is initially created in the Active state; if it finishes "
+"the work it was created to do and no more participation is required within "
+"the scope of the BA (such as when the activity operates on immutable data), "
+"then the child can unilaterally send an exited message to the parent. "
+"However, if the child task finishes and wishes to continue in the BA then it "
+"must be able to compensate for the work it has performed. In this case it "
+"sends a completed message to the parent and waits to receive the final "
+"outcome of the BA from the parent. This outcome will either be a close "
+"message, meaning the BA has completed successfully or a compensate message "
+"indicating that the parent activity requires that the child task reverse its "
+"work."
+msgstr ""
+"<code>BusinessAgreementWithParticipantCompletion</code> プロトコルの元で、 "
+"チャイルドの活動は最初は Active 状態で作成されます。それが実施するように与え"
+"られた 作業を終了して、ビジネス活動（BA）の範囲内（活動が不変データに於いてオ"
+"ペレートするなど）で 要求される参加がもう存在しない場合は、チャイルドはペアレ"
+"ントに exited メッセージを 一方的に送信することができます。しかし、チャイルド"
+"がタスクを終了して BA 内でまだ継続したい 場合は、それが実行した作業を補正する"
+"能力を持つ必要があります。このケースではチャイルドは completed メッセージをペ"
+"アレントに送信して、ペアレントから BA の最終結果を受け取ることを 待ちます。こ"
+"の結果とは BA が正しく完了したことを意味する close メッセージか、あるいはペア"
+"レント 活動がチャイルドタスク作業の反転を必要とすることを意味する compensate "
+"メッセージのどちらかに なります。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
+#, no-c-format
+msgid ""
+"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
+"identical to the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol with the exception that the child cannot autonomously decide to end "
+"its participation in the business activity, even if it can be compensated. "
+"Rather the child task relies upon the parent to inform it when the child has "
+"received all requests for it to perform work which the parent does by "
+"sending the complete message to the child. The child then acts as it does in "
+"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
+msgstr ""
+"<code>BusinessAgreementWithCoordinatorCompletion</code> プロトコルは、 補正で"
+"きる場合でもチャイルドが自動的にビジネス活動内への参加を停止することを 決定で"
+"きないこと以外では、<code>BusinessAgreementWithParticipantCompletion</code> "
+"プロトコルと同一です。チャイルドタスクは、チャイルドが作業を実行するための要"
+"求を全て 受けた時にその通達に於いてペアレントに依存してします。これはペアレン"
+"トがチャイルドに complete メッセージを送信することで実行されます。チャイルド"
+"はそれから、 <code>BusinessAgreementWithParticipantCompletion</code> プロトコ"
+"ル内で 実行するのと同じ行動をします。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:276
+#, no-c-format
+msgid ""
+"The crux of the BA model compared to the AT model is that is allows the "
+"participation of services that cannot or will not lock resources for "
+"extended periods."
+msgstr ""
+"AT  モデルに比較した BA モデルの利点は、長期間リソースをロックできない、又は "
+"しないサービスの参加を認可することです。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:279
+#, no-c-format
+msgid ""
+"While the full ACID semantics are not maintained by a BA, consistency can "
+"still be maintained through compensation, though the task of writing correct "
+"compensating actions (and thus overall system consistency) is delegated to "
+"the developers of the services under control of the BA. Such compensations "
+"may use backward error recovery, but will typically employ forward recovery."
+msgstr ""
+"完全な ACIDセマンティクスは BA によって維持されていませんが、それでも整合性は"
+"まだ 補正によって維持できます。但し、正確な補正のアクション（及び全体的システ"
+"ム整合性）を 書くタスクは BA の制御下にあるサービスの開発者に委任されます。そ"
+"のような補正は 下方互換のエラーリカバリを使用するかも知れませんが、標準的には"
+"上方互換リカバリを 採用します。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:283
+#, no-c-format
+msgid "Application Messages"
+msgstr "アプリケーションメッセージ"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:284
+#, no-c-format
+msgid ""
+"Application messages are the requests and responses that are sent between "
+"parties that constitute the work of a business process. Any such messages "
+"are considered opaque by XTS, and there is no mandatory message format, "
+"protocol binding, or encoding style so the developer is free to use any "
+"appropriate Web services protocol. In XTS, the transaction context is "
+"propagated within the headers of SOAP messages."
+msgstr ""
+"アプリケーションメッセージとは、ビジネスプロセスの作業を構成するパーティ間で "
+"送信される要求と応答のことです。そのようなメッセージはいずれも XTS では不明瞭"
+"だと 判断されて、そこには義務的なメッセージ形式やプロトコルバインディングやエ"
+"ンコーディング スタイルがないため、開発者は自由に適切な Web サービスプロトコ"
+"ルを使用することができます。 XTS では、トランザクションコンテキストは SOAP "
+"メッセージのヘッダー内で伝播されます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:289
+#, no-c-format
+msgid ""
+"XTS provides out-of-box support for service developers building WS-T-aware "
+"services on the JBoss, Weblogic and Glue platforms1. The provision of "
+"interceptors for automatic context handling at both client and service "
+"significantly simplifies the developer’s workload, allowing the developer to "
+"concentrate on writing the business logic without having to worry about the "
+"transactional infrastructure getting in the way. The interceptors simply add "
+"and remove context elements to application messages without altering the "
+"semantics of those messages. Any service which understands what to do with a "
+"WS-C context can use it, services which do not understand the context (those "
+"services that are not WS-C, WS-Atomic Transaction and WS-Business Activity-"
+"aware) may ignore the context; the important point here is that XTS manages "
+"contexts without user intervention."
+msgstr ""
+"XTS は製品出荷の状態でサービス開発者へのサポートを提供して、JBoss、"
+"Weblogic、 及び Glue platforms1 上で WS-T 認識のサービスを構築します。クライ"
+"アントとサービスの 両方で自動コンテキスト処理の為のインターセプタによるこの提"
+"供は、開発者の作業負担を 多大に簡素化して、開発者はトランザクションインフラス"
+"トラクチャが仕事の邪魔することを 心配しないでビジネス論理を書くことに集中でき"
+"るようになります。インターセプタは単に これらのメッセージのセマンティクスを変"
+"更しないでアプリケーションメッセージへのコンテキスト 要素を追加したり削除した"
+"りします。WS-C context を使って何をすべきか判っているサービスは いずれもこれ"
+"を使用できます。そのコンテキストを理解できないサービス（ WS-C、WS-Atomic "
+"Transaction、 及び WS-Business Activity 認識でないサービス）はこのコンテキス"
+"トを無視する可能性があります。 ここで重要なことは、XTS がユーザーの介入なしに"
+"コンテキストを管理できると言う点です。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:294
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr "WS-C, WS-Atomic Transaction 及び WS-Business Activity Messages"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:295
+#, no-c-format
+msgid ""
+"Although the application or service developer rarely sees or is interested "
+"in the messages exchanged by the transactional infrastructure (the "
+"transaction manager and any participants), it is useful to understand what "
+"kinds of exchanges occur so that the underlying model can be fitted in to an "
+"overall architecture."
+msgstr ""
+"アプリケーション又はサービスの開発者は稀にしか、トランザクショナルインフラス"
+"トラクチャ （トランザクションマネージャと全てのパーティシパント）によって交換"
+"されるメッセージを見たり あるいはそれに興味を示したりしませんが、どのような交"
+"換が発生しているのかを理解することは 役に立ちます。そうすると背後にあるモデル"
+"がアーキテクチャ全体に適合するようにできます。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:299
+#, no-c-format
+msgid ""
+"In XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific "
+"messages are transported using SOAP messaging over HTTP. The types of "
+"messages that are propagated include instructions to perform standard "
+"transaction operations like begin, prepare."
+msgstr ""
+"XTS の中では WS-C と WS-Atomic Transaction と WS-Business Activity の 独自の"
+"メッセージは HTTP 上で SOAP メッセージングを使用して配送されます。 伝播される"
+"メッセージのタイプには、begin や prepare のような標準のトランザクション オペ"
+"レーションを実行する指示が含まれています。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:303
+#, no-c-format
+msgid ""
+"XTS messages do not interfere in any way, shape, or form, with the "
+"application messages, and nor is there any requirement for an application to "
+"use the same transport as the transaction-specific messages. For example, it "
+"is quite reasonable for a client application to deliver its application-"
+"specific messages using SOAP RPC over SMTP even though under the covers the "
+"XTS messages are delivered using a different mechanism."
+msgstr ""
+"XTS メッセージはアプリケーションメッセージをどのような形、あるいは形式でも 妨"
+"害することはなく、またトランザクション特有のメッセージと同じトランスポートを "
+"使用するアプリケーションの為の要求もありません。例えば、影では XTS メッセージ"
+"は 異なるメカニズムを使用して配送されていますが、クライアントアプリケーション"
+"が そのアプリケーション特有のメッセージを SMTP 上で SOAP RPC を使用して配送す"
+"ることは 妥当なことです。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:310
+#, no-c-format
+msgid "Summary"
+msgstr "要約"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:311
+#, no-c-format
+msgid ""
+"XTS provides a coordination infrastructure designed to allow transactions to "
+"run between enterprises across the Internet. That infrastructure is based on "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. It "
+"supports two kinds of transactions: atomic transactions and business "
+"activities, which can be combined in arbitrary ways to map elegantly onto "
+"the transactional requirements of the underlying problem. The use of the "
+"whole infrastructure is simple due to the fact that its functionality is "
+"exposed through a simple transactioning API. Furthermore XTS provides all of "
+"the necessary plumbing to keep application and transactional aspects of an "
+"application separate, and to ensure that the transactionality of a system "
+"does not interfere with the functional aspects of the system itself."
+msgstr ""
+"XTS はインターネット全域に於いて企業間で実行されるトランザクションを許可する"
+"ように 設計されているコーディネイトインフラストラクチャを提供します。このイン"
+"フラストラクチャは WS-C、WS-Atomic Transaction、及び WS-Business Activity 仕"
+"様をベースにしています。 XTS は、２つの種類のトランザクションをサポートしま"
+"す。原子性トランザクションと ビジネス活動です。これらは随意な方法で組み合わせ"
+"ることが出来て、背後にある問題の トランザクション要求へエレガントにマップする"
+"ことができます。この全体のインフラストラクチャの 使用は、その機能が簡単なトラ"
+"ンザクショニング API を通じて表面化されていると言う事実により、 単純なもので"
+"す。さらには、XTS は全ての必要な配管処理を提供して、アプリケーションに関する "
+"アプリケーションとトランザクション側面を分離して、システムのトランザクション"
+"性がシステム自身の 機能側面を邪魔しないことを確実にします。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Author_Group.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Author_Group.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Book_Info.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Book_Info.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,49 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide CP04"
+msgstr "Guia dos Programadores dos Serviços da Web das Transações JBoss"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "para Uso com a Plataforma de Aplicativo do JBoss Enterprise 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr ""
+"Este livro fala a respeito da Programação dos Serviços da Web de Transação."
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Getting_Started.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Getting_Started.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Getting_Started.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,264 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Getting_Started.xml:6
+#, no-c-format
+msgid "Getting Started"
+msgstr "Inicializando"
+
+#. Tag: title
+#: Getting_Started.xml:8
+#, no-c-format
+msgid "Creating and deploying participants"
+msgstr "Criação e implementação de participantes"
+
+#. Tag: para
+#: Getting_Started.xml:9
+#, no-c-format
+msgid ""
+"A participant is a software entity which is driven by the transaction "
+"manager on behalf of a Web service. The creation of participants is non-"
+"trivial since they ultimately reflect the state of a Web service’s back-end "
+"processing facilities which is a function of an enterprise’s own IT "
+"infrastructure. The most that can be said about the implementation of a "
+"participant without getting into detail about the back-end systems it "
+"represents, or the details of the underlying transaction protocol is that "
+"implementations must implement one of the following interfaces, depending "
+"upon the protocol it will participate within: <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code>, or, <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+msgstr ""
+"O participante é uma entidade de software que é dirigida pelo gerenciador de "
+"transação representando um serviço da Web. A criação dos participantes não é "
+"trivial uma vez que eles refletem o estado das facilidades de processamento "
+"back-end de serviço da Web, que é uma função de uma infra-estrutura de TI "
+"própria empresarial. O máximo que pode ser dito sobre a implementação de um "
+"participante sem detalharmos sobre os sistemas back-end que isto representa, "
+"ou os detalhes de um protocolo de transação subjacente, é que as "
+"implementações devem aderir uma das seguintes interfaces, dependendo do "
+"protocolo que isto estará participando: <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code> ou <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+
+#. Tag: title
+#: Getting_Started.xml:15
+#, no-c-format
+msgid "Creating Client Applications"
+msgstr "Criação de Aplicativos de Cliente"
+
+#. Tag: para
+#: Getting_Started.xml:16
+#, no-c-format
+msgid ""
+"There are two aspects to a client application using XTS. The first is the "
+"transaction declaration aspects and the second is the business logic that "
+"the client application performs. The transaction declaration aspects are "
+"taken care of automatically with XTS’s client API. This API provides simple "
+"transaction directives like begin, commit, and rollback which the client "
+"application can use to initialize, manage, and terminate transactions. Under "
+"the covers, this API invokes (via SOAP) operations on the transaction "
+"manager."
+msgstr ""
+"Existem dois aspectos a um aplicativo de cliente usando o XTS. "
+"Primeiramente, é o aspecto de declaração de transação e o segundo é a lógica "
+"comercial que o aplicativo de cliente executa. Os aspectos da declaração de "
+"transação cuidam automaticamente com o API do cliente XTS. Este API fornece "
+"simples diretrizes de transação como inicializar, confirmar e reverter das "
+"quais o aplicativo do cliente pode usar para inicializar, gerenciar e "
+"finalizar transações. Sob coberturas, este API invoca operações (através do "
+"SOAP) no gerenciador de transação."
+
+#. Tag: para
+#: Getting_Started.xml:19
+#, no-c-format
+msgid ""
+"When the client application performs invocations on business logic Web "
+"services, then XTS does not dictate an API for that purpose. However, there "
+"is a requirement that whatever API is chosen, the XTS context be inserted "
+"onto outgoing messages, and extracted and associated with the current thread "
+"for incoming messages. To make the user’s life easier, the XTS software "
+"comes complete with three sets of “filters” which can perform the task "
+"automatically. These filters are designed to work with JAX-RPC and "
+"webMethods client libraries."
+msgstr ""
+"Quando um aplicativo de cliente executa nos serviços da Web de lógica "
+"comercial, o XTS não ordena um API para este propósito. No entanto, existe "
+"uma solicitação que independente do API escolhido, o contexto XTS será "
+"inserido em mensagens de saída, além de ser extraído e associado com a "
+"segmentação atual para mensagens de entrada. Para facilitar a vida do "
+"usuário, o software XTS vêem completo com estes três conjuntos de “filtros” "
+"que podem executar a tarefa automaticamente. Estes filtro são designados a "
+"trabalhar com JAX-RPC e bibliotecas do cliente webMethods."
+
+#. Tag: para
+#: Getting_Started.xml:23
+#, no-c-format
+msgid ""
+"If the user chooses to use a different SOAP client infrastructure, then the "
+"onus to perform client-side header processing rests with them. XTS does not "
+"provide client-side infrastructure for anything other than JAX-RPC or "
+"webMethods for this release."
+msgstr ""
+"Caso um usuário escolha usar uma infra-estrutura de cliente SOAP, então o "
+"ônus para executar o processamento do cabeçalho ao lado do cliente descansa "
+"com ele. O XTS fornece a infra-estrutura ao lado do cliente para JAX-RPC ou "
+"webMethods nesta versão."
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr "Manuseadores do Contexto JAX-RPC "
+
+#. Tag: para
+#: Getting_Started.xml:29
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC server-side context handler with the "
+"deployed web services, a handler chain must be included in the web services "
+"deployment descriptor. Please refer to the demo application <filename>jboss/"
+"webservices.xml</filename> deployment descriptor for an example of how this "
+"can be achieved."
+msgstr ""
+"Com o objetivo de registrar o manuseador do contexto ao lado do servidor JAX-"
+"RPC com os serviços da web implementados, uma corrente de manuseador deve "
+"ser incluída no descritor de implementação dos serviços da web. Por favor "
+"refira-se ao descritor de implementação <filename>jboss/webservices.xml</"
+"filename> do aplicativo demo para uma amostra de como isto pode ser atingido."
+
+#. Tag: para
+#: Getting_Started.xml:33
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC client-side context handler used by the "
+"client applications, a handler chain must be included in the definition of "
+"the service-ref in the client web.xml deployment descriptor. Please refer to "
+"the demo application <filename>jboss/client-web-app.xml</filename> for an "
+"example of how this can be achieved."
+msgstr ""
+"Com o objetivo de registrar um manuseador do contexto ao lado do cliente JAX-"
+"RPC usado pelos aplicativos do cliente, uma corrente de manuseador deve ser "
+"incluída na definição do service-ref no descritor de implementação web.xml "
+"do cliente. Por favor refira-se ao <filename>jboss/client-web-app.xml</"
+"filename> de aplicativo demo para uma amostra de como isto pode ser atingido."
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr "Manuseadores do Contexto webMethods"
+
+#. Tag: para
+#: Getting_Started.xml:38
+#, no-c-format
+msgid ""
+"In order to register the webMethods server-side context handler with the "
+"deployed web services, the inbound and outbound interceptors must be "
+"configured in the web services deployment descriptor. An example of how this "
+"can be configured can be found in the demo application, for example, the "
+"<filename>RestaurantServiceAT.xml</filename>."
+msgstr ""
+"Com o objetivo do manuseador de contexto ao lado do servidor webMethods com "
+"os serviços da web implementados, os interceptores de saída e de entrada "
+"devem ser configurados no descritor de implementação dos serviços da web. Um "
+"exemplo de como isto pode ser configurado encontra-se no aplicativo demo, "
+"por exemplo: <filename>RestaurantServiceAT.xml</filename>."
+
+#. Tag: para
+#: Getting_Started.xml:42
+#, no-c-format
+msgid ""
+"In order to register the webMethods client-side context handler, the inbound "
+"and outbound interceptors must be configured in the <filename>glue-config."
+"xml</filename> deployment descriptor. Please refer to the soap interceptor "
+"section of the demo application glue-config.xml for an example of how this "
+"can be achieved."
+msgstr ""
+"Com a finalidade de registrar o manuseador do contexto ao lado do cliente "
+"webMethods, os interceptores de saída e de entrada devem ser configurados no "
+"descritor de implementação <filename>glue-config.xml</filename>. Por favor "
+"refira-se à seção do interceptor soap do glue-config.xml de aplicativo demo "
+"para um exemplo de como isto pode ser atingido."
+
+#. Tag: title
+#: Getting_Started.xml:48
+#, no-c-format
+msgid "Hints and tips"
+msgstr "Dicas e Conselhos"
+
+#. Tag: para
+#: Getting_Started.xml:49
+#, no-c-format
+msgid ""
+"If you want to create multiple JBoss deploys on the same machine, then you "
+"may wish to look at <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/"
+"MultipleInstances.htm\"><emphasis>Setting up multiple instances</emphasis></"
+"ulink> for information on what is required."
+msgstr ""
+"Caso você deseje criar múltiplas implementações do JBoss na mesma máquina, "
+"então você poderá observar o <ulink url=\"http://www.yorku.ca/dkha/jboss/"
+"docs/MultipleInstances.htm\"><emphasis>Instalação de instâncias múltiplas</"
+"emphasis></ulink> para maiores informações sobre o que é requerido."
+
+#. Tag: title
+#: Getting_Started.xml:55
+#, no-c-format
+msgid "Summary"
+msgstr "Sumário"
+
+#. Tag: para
+#: Getting_Started.xml:56
+#, no-c-format
+msgid ""
+"This chapter has provided a high-level overview of how to use each of the "
+"major software pieces of the Web Services transactions component of JBossTS. "
+"The Web Services transaction manager provided by JBossTS is the hub of the "
+"architecture and is the only piece of software that users’ software does not "
+"bind to directly. XTS provides header processing infrastructure for dealing "
+"with Web Services transactions contexts for both users’ client applications "
+"and Web services. For developing transaction participants, XTS provides a "
+"simple interface plus the necessary document handling code."
+msgstr ""
+"Este capítulo fornece uma visão geral de alto nível de como usar cada um dos "
+"trechos do software principal do componente de transações dos Serviços da "
+"Web do JBoss. O gerenciador da transação dos Serviços da Web fornecido pelo "
+"JBossTS é o foco da arquitetura, e é o trecho único do software que não "
+"vincula diretamente no software dos usuários. O XTS fornece infra-estrutura "
+"do processamento do cabeçalho para manuseio com os contextos de ambos "
+"serviços da Web e aplicativos do cliente dos usuários. Para desenvolvimento "
+"dos participantes da transação, o XTS fornece uma interface simples mais o "
+"código de manuseio do documento necessário. "
+
+#. Tag: para
+#: Getting_Started.xml:59
+#, no-c-format
+msgid ""
+"This chapter is meant as an overview only, and is unlikely to answer "
+"questions on more difficult and subtle aspects. For fuller explanations of "
+"the components, please refer to the appropriate chapter elsewhere in this "
+"document."
+msgstr ""
+"Este capítulo é mencionado como uma visão geral apenas e dificilmente "
+"responderá perguntas mais difíceis e de aspectos súbitos. Para uma "
+"explicação completa dos componentes, por favor refira-se ao capítulo "
+"apropriado neste documento."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Introduction.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Introduction.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Introduction.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,405 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr "Introdução"
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr "Visão geral das transações dos Serviços da Web do JbossTS"
+
+#. Tag: para
+#: Introduction.xml:9
+#, no-c-format
+msgid ""
+"The XML transaction service component of JBossTS (shorthand referred to as "
+"XTS) supports the coordination of private and public Web services in a "
+"business transaction. Therefore, to understand XTS, you must be familiar "
+"with Web services, and also understand a little about transactions. This "
+"chapter introduces XTS and provides a brief overview of the technologies "
+"that form the Web services standard. Additionally, this chapter explores "
+"some of the fundamentals of transactioning technology and how it can be "
+"applied to Web services. Much of the content presented in this chapter is "
+"detailed throughout this guide; however, only overview information about Web "
+"services is provided. If you are new to creating Web services, please see "
+"consult your Web services platform documentation."
+msgstr ""
+"O componente de serviço da transação XML do JBossTS (estenografia referida "
+"como XTS) suporta a coordenação dos serviços da Web público e privado na "
+"transação comercial. Portanto, para o melhor entendimento do XTS, você deve "
+"estar familiar com os serviços da Web e entender também um pouco a respeito "
+"das transações. Este capítulo introduz o XTS e fornece uma visão rápida das "
+"tecnologias que formam o padrão de serviços da Web. Adicionado a isto, este "
+"capítulo explora alguns dos fundamentos da tecnologia de transação e como "
+"isto pode ser aplicado aos serviços da Web. A maioria do conteúdo "
+"apresentado neste capítulo está detalhado neste guia. No entanto, apenas a "
+"informação de visão geral sobre os serviços da Web é fornecida. Caso você "
+"seja novo na criação dos serviços da Web, por favor consulte a documentação "
+"da plataforma de serviços da Web. "
+
+#. Tag: para
+#: Introduction.xml:12
+#, no-c-format
+msgid ""
+"JBossTS provides as the XTS component a transaction solution for Web "
+"services. Using XTS, business partners can coordinate complex business "
+"transactions in a controlled and reliable manner. The JBossTS Web Services "
+"API supports a transactional coordination model based on the WS-C, WS-Atomic "
+"Transaction and WS-Business Activity specifications. WS-C is a generic "
+"coordination framework developed by IBM, Microsoft and BEA, WS-Atomic "
+"Transaction and WS-Business Activity are transaction protocols that utilize "
+"this framework."
+msgstr ""
+"O JBossTS fornece como componente XTS uma solução de transação para os "
+"serviços da Web. Os parceiros comerciais podem coordenar transações de "
+"comércio complexo numa maneira controlada e confiável com o uso do XTS. O "
+"API de Serviços da Web do JBossTS suporta o modelo de coordenação "
+"transacional baseado  no WS-C, na Transação WS-Atômica e nas especificações "
+"de Atividade WS-Comercial. O WS-C é um framework de coordenação genérica "
+"desenvolvido pela IBM, Microsoft e BEA. A Transação WS-Atômica e Atividade "
+"WS-Comercial são protocolos de transação que utilizam este framework."
+
+#. Tag: para
+#: Introduction.xml:15
+#, no-c-format
+msgid ""
+"Web services are modular, reusable software components that are created by "
+"exposing business functionality through a Web service interface. Web "
+"services communicate directly with other Web services using standards-based "
+"technologies such as SOAP and HTTP. These standards-based communication "
+"technologies allow Web services to be accessed by customers, suppliers, and "
+"trading partners, independent of hardware operation system or programming "
+"environment. The result is a vastly improved collaboration environment as "
+"compared to today&#39;s EDI and business-to-business (B2B) solutions—an "
+"environment where businesses can expose their current and future business "
+"applications as Web services that can be easily discovered and accessed by "
+"external partners."
+msgstr ""
+"Os serviços da Web são modulares, componentes de software reutilizáveis que "
+"são criados pela exposição da funcionalidade comercial através da interface "
+"do serviço da Web. Os serviços da Web comunicam-se diretamente com outros "
+"serviços da Web usando as tecnologias de padrão baseado tais como SOAP e "
+"FTTP. Estas tecnologias de comunicação de padrões-baseados permitem que os "
+"serviços da Web sejam acessados pelos clientes, fornecedores e parceiros "
+"comerciais, independente do sistema de operação de hardware ou ambiente de "
+"programação. O resultado é um ambiente de colaboração amplamente melhorado "
+"como comparado ao EDI de hoje e ambiente de soluções (B2B) de comércio a "
+"comércio onde os comércios podem expor os seus aplicativos atuais e futuros "
+"como os serviços da Web que podem ser facilmente descobertos e acessados por "
+"parceiros externos. "
+
+#. Tag: para
+#: Introduction.xml:18
+#, no-c-format
+msgid ""
+"Web services, by themselves, are not fault tolerant. In fact, some of the "
+"reasons that make it an attractive development solution are also the same "
+"reasons that service-based applications may have drawbacks:"
+msgstr ""
+"Os serviços da Web não toleram falha. Na realidade, algumas da razões que "
+"fazem isto uma solução de desenvolvimento atrativo são também as razões que "
+"os aplicativos de serviços baseados possam possuir defeitos:"
+
+#. Tag: para
+#: Introduction.xml:23
+#, no-c-format
+msgid ""
+"Application components that are exposed as Web services may be owned by "
+"third parties, which provides benefits in terms of cost of maintenance, but "
+"drawbacks in terms of having exclusive control over their behavior;"
+msgstr ""
+"Os componentes do aplicativo que estão expostos como serviços da Web podem "
+"pertencer a terceiros, que fornecem benefícios em termos do custo de "
+"manutenção, porém defeitos em termos de possuir controle exclusivo sobre o "
+"comportamento dos mesmos."
+
+#. Tag: para
+#: Introduction.xml:28
+#, no-c-format
+msgid ""
+"Web services are usually remotely located which increases risk of failure "
+"due to increased network travel for invocations."
+msgstr ""
+"Normalmente, os serviços da Web são remotamente localizados, o que aumenta o "
+"risco de falha devido ao aumento da viagem da rede para invocações."
+
+#. Tag: para
+#: Introduction.xml:33
+#, no-c-format
+msgid ""
+"Applications that have high dependability requirements, must find a method "
+"of minimizing the effects of errors that may occur when an application "
+"consumes Web services. One method of safeguarding against such failures is "
+"to interact with an application’s Web services within the context of a "
+"transaction. A transaction is simply a unit of work which is completed "
+"entirely, or in the case of failures is reversed to some agreed consistent "
+"state – normally to appear as if the work had never occurred in the first "
+"place. With XTS, transactions can span multiple Web services which mean that "
+"work performed across multiple enterprises can be managed with transactional "
+"support."
+msgstr ""
+"Os aplicativos que possuem solicitações de alta dependência, devem encontrar "
+"um método de minimização dos efeitos que podem ocorrer quando um aplicativo "
+"consome os serviços da Web. Um método de guarda segura em relação a tais "
+"falhas é a interação com os serviços da Web de um aplicativo com o contexto "
+"de uma transação. A transação é simplesmente uma unidade de trabalho que é "
+"completamente completada ou no caso de falhas é revertida para alguns "
+"estados de consistência entendidos (normalmente aparece como se o trabalho "
+"nunca houvesse ocorrido). As transações podem realizar scan nos serviços da "
+"Web múltiplos, dos quais significam que o trabalho executado através de "
+"empresas múltiplas podem ser gerenciadas com o suporte transacional."
+
+#. Tag: title
+#: Introduction.xml:37
+#, no-c-format
+msgid "Managing Service-Based Processes"
+msgstr "Gerenciamento dos Processos de Serviço Baseado"
+
+#. Tag: para
+#: Introduction.xml:38
+#, no-c-format
+msgid ""
+"XTS allows you to create transactions that drive complex business processes "
+"spanning multiple Web services. Current Web services standards do not "
+"address the requirements for a high-level coordination of services since in "
+"today’s Web services applications, which use single request/receive "
+"interactions, coordination is typically not a problem. However, for "
+"applications that engage multiple services among multiple business partners, "
+"coordinating and controlling the resulting interactions is essential. This "
+"becomes even more apparent when you realize that you generally have little "
+"in the way of formal guarantees when interacting with third-party Web "
+"services."
+msgstr ""
+"O XTS permite que você crie transações que dirigem os processos comerciais "
+"complexos realizando o span em serviços da Web múltiplos. Os serviços da Web "
+"atuais não endereçam as solicitações para uma coordenação de alto nível de "
+"serviço uma vez que a coordenação não é o problema para os aplicativos dos "
+"serviços da Web atuais, que utilizam interações únicas de solicitação/"
+"recebimento. No entanto, para aplicativos que empregam serviços múltiplos "
+"entre parceiros comerciais múltiplos, a coordenação e o controle de "
+"interações resultantes são essenciais. Isto começa a ser mais evidente "
+"quando você percebe que possui pouco na maneira de garantias formais, quando "
+"interagindo com os serviços da Web de terceiros."
+
+#. Tag: para
+#: Introduction.xml:42
+#, no-c-format
+msgid ""
+"XTS provides the infrastructure for coordinating services during a business "
+"process. By organizing processes as transactions, business partners can "
+"collaborate on complex business interactions in a reliable manner, insuring "
+"the integrity of their data - usually represented by multiple changes to a "
+"database – but without the usual overheads and drawbacks of directly "
+"exposing traditional transaction-processing engines directly onto the web. "
+"The following example demonstrates how an application may manage service-"
+"based processes as transactions:"
+msgstr ""
+"O XTS fornece a infra-estrutura para os serviços de coordenação durante o "
+"processo comercial. Quando organizando os processos como transações, os "
+"parceiros comerciais podem colaborar nas interações comerciais complexas "
+"numa maneira confiável, segurando a integridade dos dados dos mesmos, "
+"normalmente representado por múltiplas alterações no banco de dados, porém "
+"sem elevações e defeitos da exposição direta das máquinas de processamento "
+"de transação tradicional na web. O seguinte exemplo demonstra como um "
+"aplicativo pode gerenciar os processos de serviços baseados como transações."
+
+#. Tag: para
+#: Introduction.xml:45
+#, no-c-format
+msgid ""
+"The application in question allows a user to plan a social evening. This "
+"application is responsible for reserving a table at a restaurant, and "
+"reserving tickets to a show. Both activities are paid for using a credit "
+"card. In this example, each service represents exposed Web services provided "
+"by different service providers. XTS is used to envelop the interactions "
+"between the theater and restaurant services into a single (potentially) long-"
+"running business transaction. The business transaction must insure that "
+"seats are reserved both at the restaurant and the theater. If one event "
+"fails the user has the ability to decline both events, thus returning both "
+"services back to their original state. If both events are successful, the "
+"user’s credit card is charged and both seats are booked. As you may expect, "
+"the interaction between the services must be controlled in a reliable manner "
+"over a period of time. In addition, management must span several third-party "
+"services that are remotely deployed."
+msgstr ""
+"O aplicativo em questão permite um usuário a planejar uma noite social. Este "
+"aplicativo é responsável por reservar uma mesa no restaurante e reservar "
+"entradas para uma apresentação. Ambas atividades são pagas pelo uso de um "
+"cartão de crédito. Neste exemplo, cada serviço representa os serviços da Web "
+"expostos, fornecidos pelos diferentes fornecedores de serviço. O XTS é usado "
+"para embrulhar as interações entre os serviços do teatro e restaurante numa "
+"única (potencialmente) transação comercial de longa duração. A transação "
+"comercial deve garantir que os lugares são reservados tanto no restaurante "
+"como no teatro. Caso um dos eventos falhar, o usuário terá a habilidade de "
+"cancelar ambos os eventos, e portanto, retornando ambos serviços a seus "
+"estados originais. E, caso ambos os eventos sejam confirmados, o cartão de "
+"crédito do usuário será cobrado e ambos os lugares serão reservados. "
+"Conforme esperado, a interação entre os serviços deve ser controlada numa "
+"maneira confiável no decorrer de um certo período. Adicionado a isto, o "
+"gerenciamento deve realizar o span nos diversos serviços de terceiros que "
+"estão implementados remotamente."
+
+#. Tag: para
+#: Introduction.xml:49
+#, no-c-format
+msgid ""
+"Without the backing of a transaction, an undesirable outcome may occur. For "
+"example, the user credit card may be charged, even though one or both of the "
+"bookings may have failed."
+msgstr ""
+"Um resultado indesejado poderá ocorrer sem a recuperação da transação. Por "
+"exemplo, o usuário do cartão de crédito poderá ser cobrado, mesmo que uma "
+"das reservas não tenham sido confirmadas."
+
+#. Tag: para
+#: Introduction.xml:53
+#, no-c-format
+msgid ""
+"This simple example describes the situations where XTS excels at supporting "
+"business processes across multiple enterprises. This example is further "
+"refined throughout this guide, and appears as a standard demonstrator "
+"(including source code) with the XTS distribution."
+msgstr ""
+"Esta simples amostra descreve as situações onde o XTS excede no suporte de "
+"processos comercial através de empresas múltiplas. Este exemplo será visto "
+"futuramente neste guia e aparece como um demonstrador padrão (incluindo o "
+"código de fonte) com a distribuição XTS. "
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr "Servlets"
+
+#. Tag: para
+#: Introduction.xml:58
+#, no-c-format
+msgid ""
+"The WS-C, WS-Atomic Transaction and WS-Business Activity protocols are based "
+"on one-way interactions of entities rather than traditional synchronous "
+"request/response RPC style interactions. Entities (for example, transaction "
+"participants) invoke operations on other entities (for example, the "
+"transaction coordinator) in order to return responses to requests. What this "
+"means is that the programming model is based on peer-to-peer relationships, "
+"with the result that all services, whether they are participants, "
+"coordinators or clients, must have an active component that allows them to "
+"receive unsolicited messages."
+msgstr ""
+"Os protocolos de Atividade WS-Comercial, Transação WS-Atômica e WS-C são "
+"baseados nas interações de uma maneira de entidades ao invés da resposta/"
+"solicitação assíncrona tradicional de interações de estilo RPC. As entidades "
+"(por exemplo: participantes da transação) invocam operações em outras "
+"entidades, como o coordenador de transação) com o objetivo de retornar as "
+"respostas às solicitações. Isto significa que o modelo de programação é "
+"baseado nas relações igual à igual com o resultado que todos os serviços, se "
+"é que eles são participantes, coordenadores ou clientes, eles devem possuir "
+"um componente ativo que os permite receber mensagens não-solicitadas."
+
+#. Tag: para
+#: Introduction.xml:62
+#, no-c-format
+msgid ""
+"In the current implementation of XTS, the active component is achieved "
+"through the use of Java servlet technology. Each endpoint that can be "
+"communicated with via SOAP/XML is represented as a servlet (and published "
+"within JNDI). Fortunately for the developer, this use of servlets occurs "
+"transparently. The only drawback is that (currently) clients must reside "
+"within a domain capable of hosting servlets, i.e., an application server. It "
+"is our intention that future versions of XTS will provide configurable "
+"deployment options, allowing servlets where required, but not mandating them."
+msgstr ""
+"Na implementação atual do XTS, o componente ativo é ativado através do uso "
+"da tecnologia do Java servlet. Cada ponto final que pode ser comunicado "
+"através SOAP/XML é representado como um servlet (e publicado com o JNDI). "
+"Para a sorte do desenvolvedor, este uso dos servlets ocorre "
+"transparentemente. O único defeito é que, atualmente, os clientes devem "
+"residir com a capacidade de domínio dos servlets hospedeiros, por exemplo: "
+"um servidor do aplicativo. Nós possuimos por intenção que as versões futuras "
+"do XTS forneçam opções de implementação configuráveis, permitindo que "
+"servlets quando solicitado, mas não os fazendo mandatórios."
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr "SOAP"
+
+#. Tag: para
+#: Introduction.xml:67
+#, no-c-format
+msgid ""
+"SOAP has emerged as the de-facto message format for XML-based communication "
+"in the Web services arena. It is a lightweight protocol that allows the user "
+"to define the content of a message and to provide hints as to how recipients "
+"should process that message."
+msgstr ""
+"O SOAP emergiu como formato da mensagem de-facto para a comunicação baseada "
+"XML na arena de serviços da Web. Isto é um protocolo de carga leve que "
+"permite o usuário definir o conteúdo da mensagem e fornecer dicas de como os "
+"recipientes devem processar aquela mensagem. "
+
+#. Tag: para
+#: Introduction.xml:71
+#, no-c-format
+msgid ""
+"SOAP messages can be divided into two main categories: Remote Procedure Call "
+"(RPC) and Document Exchange (DE). The primary difference between the two "
+"categories is that the SOAP specification defines encoding rules and "
+"conventions for RPC. The document exchange model allows the exchange of "
+"arbitrary XML documents - a key ingredient of B2B document exchange. XTS is "
+"based on the loosely coupled document-exchange style, yet it can support "
+"transactions spanning Web service that use either document-exchange or RPC."
+msgstr ""
+"As mensagens SOAP podem ser divididas em duas categorias principais: Chamada "
+"de Processo Remoto - Remote Procedure Call (RPC) e Troca de Documento - "
+"Document Exchange (DE). A diferença primária entre as duas categorias é que "
+"a especificação SOAP define as regras de codificação e as convenções para o "
+"RPC. O modelo de alteração do documento permite a alteração dos documentos "
+"XML arbitrária - o ingrediente chave da alteração do documento B2B. O XTS é "
+"baseado no estilo de alteração de documento acoplado livre, ainda que isto "
+"possa suportar as transações do serviço da Web com span que usam tanto a "
+"alteração do documento ou o RPC."
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr "Linguagem de Descrição dos Serviços da Web (WSDL)"
+
+#. Tag: para
+#: Introduction.xml:76
+#, no-c-format
+msgid ""
+"WSDL is an XML-based language used to define Web service interfaces. An "
+"application that consumes a Web service parses the service’s WSDL document "
+"to discover the location of the service, the operations that the service "
+"supports, the protocol bindings the service supports (SOAP, HTTP, etc), and "
+"how to access them (for each operation, WSDL describes the format that the "
+"client must follow)."
+msgstr ""
+"O WSDL é uma linguagem baseada no XML usada para definir as interfaces de "
+"serviços da Web. Um aplicativo que consome as análises do serviço da Web do "
+"documento WSDL de serviço para descobrir a localização do serviço, as "
+"operações que o serviço suporta, os bindings do protocolo que o serviço "
+"suporta (SOAP, HTTP, etc) e como acessá-los (por cada operação, o WSDL "
+"descreve o formato que o cliente deve seguir)."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
===================================================================

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Participants.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Participants.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Participants.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,617 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Participants.xml:6
+#, no-c-format
+msgid "Test"
+msgstr "Texto"
+
+#. Tag: para
+#: Participants.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr "Este é um parágrafo de texto."
+
+#. Tag: title
+#: Participants.xml:11
+#, no-c-format
+msgid "The Participant: an Overview"
+msgstr "O Participante: uma Visão Geral"
+
+#. Tag: para
+#: Participants.xml:12
+#, no-c-format
+msgid ""
+"The participant is the entity that performs the work pertaining to "
+"transaction management on behalf of the business services involved in an "
+"application. The Web service (for example, a theatre booking system) "
+"contains some business logic for reserving a seat, enquiring availability "
+"etc, but it will need to be supported by something that maintains "
+"information in a durable manner. Typically this will be a database, but it "
+"could be a file system, NVRAM, etc. Now, although the service may talk to "
+"the back-end database directly, it cannot commit or undo any changes it (the "
+"services) makes, since these are ultimately under the control of the "
+"transaction that scoped the work. In order for the transaction to be able to "
+"exercise this control, it must have some contact with the database. In XTS "
+"this is accomplished by the participant, and the role played by the "
+"participant between the transaction and back-end transaction processing "
+"infrastructure is shown in the following figure."
+msgstr ""
+"O participante é a entidade que executa o trabalho pertencente ao "
+"gerenciamento da transação no papel do serviço comercial envolvido num "
+"aplicativo. O serviço da Web (por exemplo, o sistema de reserva de um "
+"teatro) contém algumas lógicas comerciais para reserva de uma entrada, "
+"solicitando disponibilidade, mas isto precisará ser suportado por alguma "
+"coisa que mantém a informação numa maneira durável. Normalmente, isto será "
+"um banco de dados, mas pode ser um sistema de arquivo, NVRAM, etc. Uma vez "
+"que o serviço pode comunicar-se com o banco de dados back-end diretamente, "
+"ele não poderá confirmar ou desfazer quaisquer alterações que estes serviços "
+"realizaram, uma vez que eles estão inteiramente sob o controle da transação "
+"que realizou o escopo no trabalho. Com o objetivo da transação estar apta a "
+"exercitar este controle, ela deve possuir algum contato com o banco de "
+"dados. No XTS, isto é completado pelo participante e executado pelo mesmo "
+"entre a transação e a infra-estrutura do processamento da transação back-end "
+"é apresentada na figura abaixo."
+
+#. Tag: caption
+#: Participants.xml:19
+#, no-c-format
+msgid "Transactions, Participants, and Back-End Transaction Control"
+msgstr "Transações, Participantes e Controle da Transação Back-End"
+
+#. Tag: para
+#: Participants.xml:21
+#, no-c-format
+msgid ""
+"Each participant in XTS is related to either the Atomic Transaction or "
+"Business Activity protocols. In the following sections we’ll consider both "
+"protocols and their respective participants."
+msgstr ""
+"Cada participante no XTS é relacionado tanto à Transação Atômica ou aos "
+"protocolos de Atividade Comercial. Nas seções seguintes, nós iremos "
+"considerar ambos os protocolos e seus participantes respectivamente."
+
+#. Tag: title
+#: Participants.xml:25
+#, no-c-format
+msgid "Atomic Transaction"
+msgstr "Transação Atômica"
+
+#. Tag: para
+#: Participants.xml:26
+#, no-c-format
+msgid ""
+"All Atomic Transaction participants are instances of one of the following "
+"interfaces."
+msgstr ""
+"Todos os participantes da Transação Atômica são instâncias de uma das "
+"seguintes interfaces."
+
+#. Tag: title
+#: Participants.xml:31
+#, no-c-format
+msgid "Durable2PCParticipant"
+msgstr "Durable2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:32
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Durable2PC protocol with "
+"the following signatures, as per the <interfacename>com.arjuna.wst."
+"Durable2Participant</interfacename> interface:"
+msgstr ""
+"Este participante fornece o protocolo Durable2PC de Transação WS-Atômica com "
+"as seguintes assinaturas, assim como na interface <interfacename>com.arjuna."
+"wst.Durable2Participant</interfacename>:"
+
+#. Tag: para
+#: Participants.xml:38
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the <code>com.arjuna.wst."
+"Vote</code>. Values are: <code>ReadOnly</code>, indicating the participant "
+"does not need to be informed of the transaction outcome as no state updates "
+"were made; Prepared, indicating the participant is prepared to commit or "
+"rollback depending on the final transaction outcome, and it has made "
+"sufficient state updates persistent to accomplish this; and Aborted, "
+"indicating the participant has aborted and the transaction should also "
+"attempt to do so."
+msgstr ""
+"<emphasis>preparo</emphasis>: o participante deve executar qualquer trabalho "
+"necessário para permitir que isto tanto confirme ou reverta o trabalho "
+"executado pelo serviço da Web sob o escopo da transação. A implementação "
+"está livre a realizar o que for necessário para representar o contrato "
+"implícito entre isto e o coordenador. Espera-se que o participante indique "
+"se é que ou não ele pode preparar o <code>com.arjuna.wst.Vote</code> pelo "
+"retorno de uma instância. Os valores são: <code>ReadOnly</code>, indicação "
+"de que o participante não precisa ser informado do resultado da transação "
+"uma vez que as atualizações de estado não foram feitas; Prepared, indicação "
+"de que o participante está preparado para realizar a confirmação ou "
+"reversão, dependendo do resultado da transação final e isto fez persistentes "
+"atualizações do estado suficiente para executar isto; e Aborted, indicação "
+"que o participante realizou o aborto e a transação deve tentar realizar isto "
+"também."
+
+#. Tag: para
+#: Participants.xml:43 Participants.xml:81
+#, no-c-format
+msgid ""
+"<emphasis>commit</emphasis>: the participant should make permanent the work "
+"that it controls. What it does will depend upon its implementation, for "
+"example, commit the reservation of the theatre ticket. The participant will "
+"then return an indication of whether or not it succeeded."
+msgstr ""
+"<emphasis>confirmação</emphasis>: o participante deve fazer permanente o "
+"trabalho que isto controla. O que isto realiza dependerá de sua própria "
+"implementação, por exemplo: confirmação da reserva do ingresso do teatro. O "
+"participante retornará uma indicação se que ou não este procedimento foi "
+"sucedido."
+
+#. Tag: para
+#: Participants.xml:48 Participants.xml:86
+#, no-c-format
+msgid ""
+"<emphasis>rollback</emphasis>: the participant should undo the work that it "
+"controls. The participant will then return an indication of whether or not "
+"it succeeded."
+msgstr ""
+"<emphasis>reversão</emphasis>: o participante deve desfazer o trabalho que "
+"ele controla. O mesmo retornará uma indicação se é que ou não isto foi "
+"sucedido."
+
+#. Tag: para
+#: Participants.xml:53 Participants.xml:91
+#, no-c-format
+msgid ""
+"<emphasis>commitOnePhase</emphasis>: if there is only a single "
+"TwoPCParticipant registered with the transaction, then the coordinator can "
+"optimize the protocol and simply tell the participant to commit: there is no "
+"need for a preparatory phase since consensus is implicit."
+msgstr ""
+"<emphasis>commitOnePhase</emphasis>: caso exista apenas um único "
+"TwoPCParticipant registrado com a transação, o coordenador pode otimizar o "
+"protocolo e simplesmente informar o participante a realizar a confirmação: "
+"não há necessidade para a fase preparatória desde que o consenso seja "
+"implícito."
+
+#. Tag: para
+#: Participants.xml:58 Participants.xml:96
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: during recovery the participant can inquire as "
+"to the status of the transaction it was registered with. If that transaction "
+"is no longer available (has rolled back) then this operation will be invoked "
+"by the coordination service."
+msgstr ""
+"<emphasis>desconhecido</emphasis>: durante a recuperação o participante pode "
+"solicitar ao status sobre a transação que isto foi registrado. Caso a "
+"transação não esteja mais disponível (efetuou a reversão), então esta "
+"operação será invocada pelo serviço de coordenação."
+
+#. Tag: para
+#: Participants.xml:63 Participants.xml:101
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: during recovery the participant can enquire as "
+"to the status of the transaction it was registered with. If an error occurs "
+"(for example, the transaction service is unavailable) then this operation "
+"will be invoked."
+msgstr ""
+"<emphasis>erro</emphasis>: durante a recuperação o participante pode "
+"solicitar ao status sobre a transação em que ele estava registrado. Caso um "
+"erro ocorra (por exemplo, o serviço de transação estiver indisponível) então "
+"esta operação será invocada."
+
+#. Tag: title
+#: Participants.xml:69
+#, no-c-format
+msgid "Volatile2PCParticipant"
+msgstr "Volatile2PCParticipant"
+
+#. Tag: para
+#: Participants.xml:70
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Volatile2PC protocol "
+"with the following signatures, as per the <interfacename>com.arjuna.wst."
+"Volatile2Participant</interfacename> interface:"
+msgstr ""
+"O participante suporta o protocolo Volatile2PC de Transação WS-Atômica com "
+"as seguintes assinaturas, conforme a interface <interfacename>com.arjuna.wst."
+"Volatile2Participant</interfacename>:"
+
+#. Tag: para
+#: Participants.xml:76
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the com.arjuna.wst.Vote. "
+"Values are: ReadOnly, indicating the participant does not need to be "
+"informed of the transaction outcome as no state updates were made; Prepared, "
+"indicating the participant is prepared to commit or rollback depending on "
+"the final transaction outcome, and it has made sufficient state updates "
+"persistent to accomplish this; and Aborted, indicating the participant has "
+"aborted and the transaction should also attempt to do so."
+msgstr ""
+"<emphasis>preparar</emphasis>: o participante deve executar qualquer "
+"trabalho necessário para permitir que isto seja confirmado "
+
+#. Tag: title
+#: Participants.xml:107
+#, no-c-format
+msgid "Business Activity"
+msgstr "Atividade Comercial"
+
+#. Tag: para
+#: Participants.xml:108
+#, no-c-format
+msgid ""
+"All Business Activity participants are instances of the following interfaces."
+msgstr ""
+"Todos os participantes da Atividade Comercial são instâncias das seguintes "
+"interfaces."
+
+#. Tag: title
+#: Participants.xml:113
+#, no-c-format
+msgid "BusinessAgreementWithParticipantCompletion"
+msgstr "BusinessAgreementWithParticipantCompletion"
+
+#. Tag: para
+#: Participants.xml:114
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"Este participante suporta o protocolo "
+"<code>BusinessAgreementWithParticipantCompletion</code> com as seguintes "
+"assinaturas, conforme a interface <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename>:"
+
+#. Tag: para
+#: Participants.xml:120 Participants.xml:158
+#, no-c-format
+msgid ""
+"<emphasis>close</emphasis>: the transaction has completed successfully. The "
+"participant previously informed the coordinator that it was ready to "
+"complete."
+msgstr ""
+"<emphasis>encerrar</emphasis>: a transação foi completada com êxito. O "
+"participante anterior informou o coordenador que ele estava pronto para ser "
+"completado."
+
+#. Tag: para
+#: Participants.xml:125
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work. The participant cannot have informed the "
+"coordinator that it has completed."
+msgstr ""
+"<emphasis>cancelar</emphasis>: a transação foi cancelada e o participante "
+"deve desfazer qualquer trabalho. O participante não pode informar o "
+"coordenador que isto foi completado."
+
+#. Tag: para
+#: Participants.xml:130 Participants.xml:168
+#, no-c-format
+msgid ""
+"<emphasis>compensate</emphasis>: the transaction has canceled. The "
+"participant previously informed the coordinator that it had finished work "
+"but could compensate later if required, so it is now requested to do so."
+msgstr ""
+"<emphasis>compensar</emphasis>: a transação foi cancelada. O participante "
+"anterior informou o coordenador que o trabalho foi encerrado, mas poderia "
+"compensar mais tarde caso fosse necessário, de forma que isto foi solicitado "
+"agora."
+
+#. Tag: para
+#: Participants.xml:135 Participants.xml:178
+#, no-c-format
+msgid "<emphasis>status</emphasis>: return the status of the participant."
+msgstr "<emphasis>status</emphasis>: retorna o status do participante."
+
+#. Tag: para
+#: Participants.xml:140 Participants.xml:183
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: if the participant inquires as to the status "
+"of the transaction it was registered with and that transaction is no longer "
+"available (has rolled back) then this operation will be invoked by the "
+"coordination service."
+msgstr ""
+"<emphasis>desconhecido</emphasis>: caso o participante questionar ao status "
+"da transação como ela foi registrada e que a transação não está mais "
+"disponível (foi revertida), esta operação será invocada pelo serviço de "
+"coordenação."
+
+#. Tag: para
+#: Participants.xml:145 Participants.xml:188
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: if the participant enquired as to the status of "
+"the transaction it was registered with and an error occurs (for example, the "
+"transaction service is unavailable) then this operation will be invoked."
+msgstr ""
+"<emphasis>erro</emphasis>: caso o participante questionar ao status da "
+"transação como ela foi registrada e que ocorreu um erro (por exemplo: o "
+"serviço da transação estava indisponível), a operação será invocada."
+
+#. Tag: title
+#: Participants.xml:151
+#, no-c-format
+msgid "BusinessAgreementWithCoordinatorCompletion"
+msgstr "BusinessAgreementWithCoordinatorCompletion"
+
+#. Tag: para
+#: Participants.xml:152
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+"Este participante suporta o protocolo "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> com as seguintes "
+"assinaturas, conforme a interface <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename>:"
+
+#. Tag: para
+#: Participants.xml:163
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work."
+msgstr ""
+"<emphasis>cancelar</emphasis>: a transação foi cancelada e o participante "
+"deve desfazer qualquer trabalho."
+
+#. Tag: para
+#: Participants.xml:173
+#, no-c-format
+msgid ""
+"<emphasis>complete</emphasis>: the coordinator is informing the participant "
+"that all work it needs to do within the scope of this business activity has "
+"been received."
+msgstr ""
+"<emphasis>completar</emphasis>: o coordenador está informando o participante "
+"que todo trabalho necessário para realizar com o escopo desta atividade "
+"comercial foi recebido."
+
+#. Tag: title
+#: Participants.xml:194
+#, no-c-format
+msgid "BAParticipantManager"
+msgstr "BAParticipantManager"
+
+#. Tag: para
+#: Participants.xml:195
+#, no-c-format
+msgid ""
+"In order for the Business Activity protocol to work correctly, the "
+"participants must be able to autonomously signal the coordinator that they "
+"have left the activity (exited) or are ready to complete and (if necessary) "
+"compensate (completed). Unlike the Atomic Transaction protocol, where all "
+"interactions between the coordinator and participants are instigated by the "
+"coordinator when the transaction terminates, this interaction pattern "
+"requires the participant to be able to talk to the coordinator at any time "
+"during the lifetime of the business activity."
+msgstr ""
+"Com o objetivo do protocolo da Atividade Comercial funcionar corretamente, "
+"os participantes devem estar aptos a indicar livremente o coordenador que "
+"eles deixaram a atividade (sairam) ou estão prontos para completar e, caso "
+"seja necessário, compensar (completar). Diferente do protocolo da Transação "
+"Atômica, onde todas as interações entre o coordenador e os participantes são "
+"estimuladas pelo coordenador quando a transação termina, o padrão da "
+"interação requer que o participante esteja apto a comunicar-se com o "
+"coordenador a qualquer momento durante o ciclo de vida da atividade "
+"comercial."
+
+#. Tag: para
+#: Participants.xml:199
+#, no-c-format
+msgid ""
+"As such, whenever a participant is registered with a business activity, it "
+"receives a handle on the coordinator. This handle is an instance of the "
+"<interfacename>BAParticipantManager</interfacename> interface, located in "
+"<code>com.arjuna.wst.BAParticipantManager</code>, with the following methods:"
+msgstr ""
+"A qualquer instante que um participante for registrado com uma atividade "
+"comercial, ele recebe uma ajuda do coordenador. Esta ajuda é uma instância "
+"da interface <interfacename>BAParticipantManager</interfacename>, localizada "
+"no <code>com.arjuna.wst.BAParticipantManager</code> com os seguintes métodos:"
+
+#. Tag: para
+#: Participants.xml:204
+#, no-c-format
+msgid ""
+"<emphasis>exit</emphasis>: the participant has exited the business activity. "
+"The participant uses this to inform the coordinator that is has left the "
+"activity. It will not be informed when (and how) the business activity "
+"terminates."
+msgstr ""
+"<emphasis>saída</emphasis>: o participante sai da atividade comercial. O "
+"participante usa isto para informar que o coordenador que ele deixou a "
+"atividade. Não haverá informação de quando (e como) a atividade comercial "
+"encerrará."
+
+#. Tag: para
+#: Participants.xml:209
+#, no-c-format
+msgid ""
+"<emphasis>completed</emphasis>: the participant has completed it works, but "
+"wishes to continue in the business activity, so that it will eventually be "
+"told when (and how) the activity terminates. The participant may later be "
+"asked to compensate for the work it has done."
+msgstr ""
+"<emphasis>completada</emphasis>: o participante completou o seu trabalho, "
+"mas deseja continuar a atividade comercial, de forma que isto será "
+"eventualmente informado quando (e como) a atividade encerra. O participante "
+"poderá ser questionado a compensar o trabalho realizado."
+
+#. Tag: para
+#: Participants.xml:214
+#, no-c-format
+msgid ""
+"<emphasis>fault</emphasis>: the participant encountered an error during "
+"normal activation and has compensated. This places the business activity "
+"into a mandatory cancel-only mode."
+msgstr ""
+"<emphasis>falha</emphasis>: o participante encontrou um erro durante a "
+"ativação normal e compensou isto. Isto coloca a atividade comercial num modo "
+"mandatório de cancelamento apenas."
+
+#. Tag: title
+#: Participants.xml:222
+#, no-c-format
+msgid "Participant Creation and Deployment"
+msgstr "Implementação e Criação do Participante"
+
+#. Tag: para
+#: Participants.xml:223
+#, no-c-format
+msgid ""
+"As has been shown, the participant provides the plumbing that drives the "
+"transactional aspects of the service. This section discusses the specifics "
+"of Participant programming and usage."
+msgstr ""
+"Conforme apresentado, o participante fornece a conexão que dirige os "
+"aspectos transacionas do serviço. Esta seção discute as especificações de "
+"programação e uso do Participante."
+
+#. Tag: title
+#: Participants.xml:227
+#, no-c-format
+msgid "Implementing Participants"
+msgstr "Ativação de Participantes"
+
+#. Tag: para
+#: Participants.xml:228
+#, no-c-format
+msgid ""
+"Implementing a participant is, in theory, a relatively straightforward task, "
+"though depending on the complexity of the transactional infrastructure that "
+"the participant is to manage, the actual size and complexity of a "
+"participant will vary. The participant interfaces can be found under "
+"<code>com.arjuna.wst</code>. Your implementation must implement one of these "
+"interfaces."
+msgstr ""
+"A ativação de participantes é, na teoria, uma tarefa relativamente direta, "
+"apesar de depender na complexidade da infraestrutura transacional que o "
+"participante está prestes a gerenciar, o tamanho atual e a complexidade do "
+"participante irá variar. As interfaces do participante pode ser encontrada "
+"sob <code>com.arjuna.wst</code>. A sua ativação deve ativar estas interfaces."
+
+#. Tag: title
+#: Participants.xml:233
+#, no-c-format
+msgid "Deploying Participants"
+msgstr "Implementação de Participantes"
+
+#. Tag: para
+#: Participants.xml:234
+#, no-c-format
+msgid ""
+"In order to allow Participants to be located remote from the Transaction "
+"Manager, XTS includes transparent message routing functionality. The "
+"Participant classes are not exposed directly as web services, but rather "
+"registered with a web service which receives messages from the Transaction "
+"Manager and maps them to appropriate method invocations on the relevant "
+"Participant instance. Transactional web services will typically enroll a new "
+"Participant instance of the desired type for each new transaction. A unique "
+"identifier must be provided at enrollment time and will be used to map "
+"transaction protocol messages to the appropriate participant instance. Note "
+"that Participant method invocations do not occur in a specific transaction "
+"context. Therefore, if your Participant implementation requires knowledge of "
+"the transaction context (for example, to look up state information in a "
+"persistent store) then you should provide this to the Participant instance, "
+"typically as an argument to the constructor function. Sample Participant "
+"implementations and usage can be found in the demonstration application "
+"included with XTS."
+msgstr ""
+"Com a finalidade de permitir que os Participantes sejam localizados "
+"remotamente do Gerenciador da Transação, o XTS inclui a funcionalidade de "
+"roteamento de mensagem clara. As classes do Participante não estão expostas "
+"diretamente como serviços da web, mas ao invés disto registradas com o "
+"serviço da web que recebe mensagens do Gerenciador de Transação e os mapeia "
+"às invocações de método apropriado na instância relevante do Participante.  "
+"Normalmente, os serviços da web Transacional adicionarão uma nova instância "
+"do Participante do tipo desejado para cada nova transação. Um identificador "
+"único deve ser fornecido no período de adicionamento e será usado para "
+"mapear as mensagens do protocolo de transação à instância do participante "
+"apropriado. Perceba que as invocações do método do Participante não ocorrem "
+"num contexto de transação específico. Portanto, caso a sua implementação do "
+"Participante solicite conhecimento do contexto de transação (por exemplo: "
+"observar a informação de estado num armazenamento persistente), você deverá "
+"fornecer esta instância do Participante, normalmente como um argumento à "
+"função do construtor. As implementações e uso do Participante de amostra "
+"podem ser encontradas no aplicativo de demonstração incluído com o XTS. "
+
+#. Tag: para
+#: Participants.xml:238
+#, no-c-format
+msgid ""
+"Any application code which creates and enrolls Participants must be deployed "
+"along with the parts of XTS necessary for receiving and processing incoming "
+"messages from the Transaction Manager. This typically means including the "
+"appropriate XTS .jar, .wsr and .war files in your application. If you are "
+"deploying your application only a server which does not already contain a "
+"Transaction Manger installation, you will also need to deploy the XTS "
+"configuration files."
+msgstr ""
+"Qualquer código de aplicativo que cria e adiciona Participantes deve ser "
+"implementado adiante com as partes do XTS necessárias para mensagens de "
+"chegada de processamento e recebimento a partir do Gerenciador da Transação. "
+"Isto significa a inclusão dos arquivos XTS .jar, .wsr and .war apropriados "
+"em seu aplicativo. Caso você esteja implementando seu aplicativo em apenas "
+"um servidor que não contém ainda a instalação do Gerenciador da Transação, "
+"você precisará implementar os arquivos de configuração XTS."
+
+#. Tag: para
+#: Participants.xml:242
+#, no-c-format
+msgid ""
+"In early access releases of the XTS product, the Transaction Manager and "
+"participant management functions are not provided as separable components. "
+"Configuration and deployment of the participant infrastructure is therefore "
+"as in the Transaction Manger section above. More flexible deployment of the "
+"XTS components will be available in the final release."
+msgstr ""
+"Nas versões de acessos anteriores do produto XTS, o Gerenciador de Transação "
+"e as funções de gerenciamento do participante não são fornecidas com "
+"componentes separados. A Configuração e a implementação da infraestrutura do "
+"participante está, portanto, como na seção de Gerenciador de Transação "
+"acima. A implementação de maior flexibilidade dos componentes XTS estarão "
+"disponíveis na versão final."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Preface.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Preface.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr "Prefácio"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Revision_History.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Revision_History.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,29 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "Histórico de Revisão"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Stand-alone_Coordinator.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Stand-alone_Coordinator.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Stand-alone_Coordinator.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,39 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:6
+#, no-c-format
+msgid "Stand-alone Coordinator"
+msgstr "Coordenador Autônomo"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introdução"
+
+#. Tag: para
+#: Stand-alone_Coordinator.xml:9
+#, no-c-format
+msgid ""
+"For configuring a stand-alone Web Services transaction coordinator, see the "
+"relevant chapter in the System Administrator’s Guide."
+msgstr ""
+"Para configuração de um coordenador de transação dos Serviços da Web "
+"autônomos, por favor consulte o capítulo no Guia do Administrador de Sistema."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/The_XTS_API.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/The_XTS_API.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/The_XTS_API.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,769 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr "O XTS API"
+
+#. Tag: title
+#: The_XTS_API.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introdução"
+
+#. Tag: para
+#: The_XTS_API.xml:9
+#, no-c-format
+msgid ""
+"This chapter shows how to use the XTS API. This is of use both at the client-"
+"side where applications consume transactional Web services, and at the "
+"service/participant side where transactions need to be coordinated with back-"
+"end systems."
+msgstr ""
+"Este capítulo apresenta como usar o XTS API. Isto é para ambos os usos no "
+"lado cliente onde os aplicativos consomem os serviços da Web transacional e "
+"no lado do serviço/participante onde as transações precisam ser coordenadas "
+"com os sistemas back-end. "
+
+#. Tag: title
+#: The_XTS_API.xml:15
+#, no-c-format
+msgid "API for the Atomic Transaction protocol"
+msgstr "O API para o protocolo da Transação Atômica"
+
+#. Tag: para
+#: The_XTS_API.xml:16
+#, no-c-format
+msgid ""
+"The following classes and interfaces are located within the <package>com."
+"arjuna.wst or com.arjuna.mw.wst</package> packages and sub-packages."
+msgstr ""
+"As seguintes classes e interfaces estão localizadas com os pacotes e sub-"
+"pacotes <package>com.arjuna.wst ou com.arjuna.mw.wst</package>."
+
+#. Tag: title
+#: The_XTS_API.xml:20
+#, no-c-format
+msgid "Vote"
+msgstr "Voto"
+
+#. Tag: para
+#: The_XTS_API.xml:21
+#, no-c-format
+msgid ""
+"During the two-phase commit protocol, a participant will be asked to vote on "
+"whether or not it can prepare to confirm the work that it controls. It must "
+"return one of the following subtypes of <code>com.arjuna.wst.Vote</code>:"
+msgstr ""
+"Durante a fase de confirmação de duas fases, o participante será questionado "
+"a votar se é que possível ou não confirmar o trabalho que isto controla. "
+"Isto deve retornar um dos seguintes sub-tipos de <code>com.arjuna.wst.Vote</"
+"code>:"
+
+#. Tag: para
+#: The_XTS_API.xml:27
+#, no-c-format
+msgid ""
+"<emphasis>Prepared</emphasis>: the participant indicates that it can prepare "
+"if asked to by the coordinator. It will not have committed at this stage "
+"however, since it does not know what the final outcome will be."
+msgstr ""
+"<emphasis>Preparado</emphasis>: o participante indica se ele pode preparar, "
+"caso isto seja solicitado pelo coordenador. Isto não será confirmado neste "
+"momento, uma vez que ele não saberá qual será o resultado final."
+
+#. Tag: para
+#: The_XTS_API.xml:32
+#, no-c-format
+msgid ""
+"<emphasis>Aborted</emphasis>: the participant indicates that it cannot "
+"prepare and has in fact rolled back. The participant should not expect to "
+"get a second phase message."
+msgstr ""
+"<emphasis>Abortado</emphasis>: o participante indica se ele pode ou não "
+"preparar e se isto afeta a reversão. O participante não deve esperar em "
+"receber uma mensagem de fase."
+
+#. Tag: para
+#: The_XTS_API.xml:37
+#, no-c-format
+msgid ""
+"<emphasis>ReadOnly</emphasis>: the participant indicates that the work it "
+"controls has not made any changes to state that require it to be informed of "
+"the final outcome of the transaction. Essentially the participant is "
+"resigning from the transaction."
+msgstr ""
+"<emphasis>ReadOnly</emphasis>: o participante indica se é que o trabalho que "
+"ele controla não efetuou alguma alteração ao estado que isto solicita ser "
+"informado no resultado final da transação. Basicamente, o participante é re-"
+"assinado a partir da transação."
+
+#. Tag: para
+#: The_XTS_API.xml:42
+#, no-c-format
+msgid ""
+"Thus a possible implementation of a 2PC participant’s prepare method may "
+"resemble the following:"
+msgstr ""
+"Desta maneira uma implementação possível do método de preparo do "
+"participante 2PC pode se parecer com o seguinte:"
+
+#. Tag: screen
+#: The_XTS_API.xml:45
+#, no-c-format
+msgid ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+msgstr ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+
+#. Tag: title
+#: The_XTS_API.xml:47
+#, no-c-format
+msgid "The transaction context"
+msgstr "O contexto de transação"
+
+#. Tag: para
+#: The_XTS_API.xml:48
+#, no-c-format
+msgid ""
+"A transaction is typically represented by some unique identifier and a "
+"reference to the coordinator which manages the transaction, for example, a "
+"URL. XTS allows transactions to be nested such that a transaction hierarchy "
+"(tree) may be formed. Thus, a transaction context may be a set of "
+"transactions, with the top-most transaction the root parent (superior)."
+msgstr ""
+"A transação é representada por um identificador único e uma referência ao "
+"coordenador que gerencia a transação, por exemplo: um URL. O XTS permite que "
+"as transações sejam aninhadas, tal como a hierarquia da transação (tree) "
+"possa ser formada. Desta maneira, o contexto de transação pode ser um "
+"conjunto de transação com a raiz parent da transação mais alta do topo "
+"(superior)."
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr "TxContext"
+
+#. Tag: para
+#: The_XTS_API.xml:54
+#, no-c-format
+msgid ""
+"<code>com.arjuna.mw.wst.TxContext</code> is an opaque representation of a "
+"transaction context."
+msgstr ""
+"<code>com.arjuna.mw.wst.TxContext</code> é uma representação opaca do "
+"contexto da transação."
+
+#. Tag: para
+#: The_XTS_API.xml:60
+#, no-c-format
+msgid ""
+"<emphasis>valid</emphasis>: this indicates whether or not the contents are "
+"valid."
+msgstr ""
+"<emphasis>válido</emphasis>: isto indica se é que ou não os conteúdos estão "
+"válidos."
+
+#. Tag: para
+#: The_XTS_API.xml:65
+#, no-c-format
+msgid "<emphasis>equals</emphasis>: can be used to compare two instances."
+msgstr ""
+"<emphasis>igual</emphasis>: pode ser usado para comparar duas instâncias."
+
+#. Tag: title
+#: The_XTS_API.xml:71
+#, no-c-format
+msgid "UserTransaction"
+msgstr "UserTransaction"
+
+#. Tag: para
+#: The_XTS_API.xml:72
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserTransaction</classname> is the class that "
+"most users (for example, clients and services) will see. This isolates them "
+"from the underlying protocol-specific aspects of the XTS implementation. "
+"Importantly, a UserTransaction does not represent a specific transaction, "
+"but rather is responsible for providing access to an implicit per-thread "
+"transaction context; it is similar to the UserTransaction in the JTA "
+"specification. Therefore, all of the UserTransaction methods implicitly act "
+"on the current thread of control."
+msgstr ""
+"A <classname>com.arjuna.wst.UserTransaction</classname> é a classe que a "
+"maioria dos usuários (por exemplo: clientes e servidores) verão. Isto os "
+"isola a partir dos aspectos do protocolo específico subjacente da "
+"implementação XTS. Uma UserTransaction não representa a transação "
+"específica, mas é responsável em fornecer acesso a um contexto de transação "
+"por segmentação implícita. Isto é similar à UserTransaction na especificação "
+"JTA. Portanto, todos os métodos da UserTransaction implícitos atuam na "
+"segmentação atual de controle."
+
+#. Tag: para
+#: The_XTS_API.xml:76
+#, no-c-format
+msgid ""
+"A new transaction is begun and associated with the invoking thread by using "
+"the begin method. If there is already a transaction associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created transaction with the "
+"current thread."
+msgstr ""
+"Uma nova transação é inicializada e associada com a segmentação invocada "
+"pelo uso do método de inicialização. Caso já exista uma transação associada "
+"com a segmentação, a exceção <code>WrongStateException</code> será lançada. "
+"Esta operação associa a nova transação criada com a segmentação atual, sob "
+"êxito de execução."
+
+#. Tag: para
+#: The_XTS_API.xml:79
+#, no-c-format
+msgid ""
+"The transaction is committed by the commit method. This will execute the "
+"Volatile2PC and Durable2PC protocols prior to returning. If there is no "
+"transaction associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. If the transaction "
+"ultimately rolls back then the <code>TransactionRolledBackException</code> "
+"is thrown. When complete, this operation disassociates the transaction from "
+"the current thread such that it becomes associated with no transaction."
+msgstr ""
+"A transação é confirmada pelo método de confirmação. Isto executará os "
+"protocolos Volatile2PC e Durable2PC antes do retorno. Caso não exista "
+"transação associada com a segmentação invocada, a "
+"<code>UnknownTransactionException</code> será lançada. Caso a transação seja "
+"revertida, a <code>TransactionRolledBackException</code> será lançada. Esta "
+"operação desassocia a transação a partir da segmentação atual, de forma que "
+"ela não se associa a nenhuma transação."
+
+#. Tag: para
+#: The_XTS_API.xml:82
+#, no-c-format
+msgid ""
+"The <code>rollback</code> operation will terminate the transaction and "
+"return normally if it succeeded, while throwing an appropriate exception if "
+"it didn’t. If there is no transaction associated with the invoking thread "
+"then <code>UnknownTransactionException</code> is thrown."
+msgstr ""
+"A operação <code>rollback</code> encerrará a transação e retornará ao normal "
+"caso ela seja sucedida, enquanto lançando uma exceção apropriada (caso ele "
+"já não o tenha feito). Caso não haja transação associada com a segmentação "
+"de invocação, a <code>UnknownTransactionException</code> será lançada."
+
+#. Tag: title
+#: The_XTS_API.xml:86
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr "UserTransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+"As UserTransactions são obtidas a partir da <code>UserTransactionFactory</"
+"code>."
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, no-c-format
+msgid "TransactionManager"
+msgstr "TransactionManager"
+
+#. Tag: para
+#: The_XTS_API.xml:93
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface represents "
+"the service/container/participant’s (service-side users) typical way in "
+"which to interact with the underlying transaction service implementation. As "
+"with <interfacename>UserTransaction</interfacename> a "
+"<interfacename>TransactionManager</interfacename> does not represent a "
+"specific transaction, but rather is responsible for providing access to an "
+"implicit per-thread transaction context."
+msgstr ""
+"A interface <interfacename>TransactionManager</interfacename> representa a "
+"maneira típica do participante/container/serviço (usuários ao lado do "
+"serviço), pela qual interage com a implementação do serviço de transação "
+"subjacente. Assim como a <interfacename>UserTransaction</interfacename>, a "
+"<interfacename>TransactionManager</interfacename> não representa uma "
+"transação específica, mas é responsável em fornecer acesso a um contexto de "
+"transação por segmentação implícita. "
+
+#. Tag: para
+#: The_XTS_API.xml:97
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific transaction. In "
+"order to do this it is necessary to disassociate the thread from any "
+"transactions. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the transaction. The "
+"thread is then no longer associated with any transaction."
+msgstr ""
+"A segmentação de controle pode solicitar períodos de não-transacionalidade, "
+"de forma que ela executará trabalho que não é associado com uma transação "
+"específica. Com o objetivo de realizar isto, é necessário desassociar a "
+"segmentação a partir das transações. O método suspenso completa isto, "
+"retornando uma instância de <code>TxContext</code>, da qual é uma ajuda na "
+"transação. A segmentação não é mais associada com qualquer transação."
+
+#. Tag: para
+#: The_XTS_API.xml:100
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with a transaction(s) via its <code>TxContext</code>. Prior to "
+"association, the thread is disassociated with any transaction(s) with which "
+"it may be currently associated. If the <code>TxContext</code> is null, then "
+"the thread is associated with no transaction. The "
+"<code>UnknownTransactionException</code> exception is thrown if the "
+"transaction that the <code>TxContext</code> refers to is invalid in the "
+"scope of the invoking thread."
+msgstr ""
+"O método <methodname>resume</methodname> pode ser usado para (re-)associar "
+"uma segmentação com a(s) transação(ões) através do próprio <code>TxContext</"
+"code>. Precedente a esta associação, a segmentação é desassociada com "
+"qualquer Transação(ões) pelas quais elas possam ser associadas. Caso o "
+"<code>TxContext</code> seja nulo, a segmentação não é associada a nenhuma "
+"transação. A excepção é lançada caso a transação que o <code>TxContext</"
+"code> se refere é inválido ao escopo da segmentação de invocação."
+
+#. Tag: para
+#: The_XTS_API.xml:103
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current transaction, or null if there is "
+"none. Unlike suspend, this method does not disassociate the current thread "
+"from the transaction(s). This can be used to enable multiple threads to "
+"execute within the scope of the same transaction."
+msgstr ""
+"O método <methodname>currentTransaction</methodname> retorna o "
+"<code>TxContext</code> para a transação atual ou nulo caso não haja nada. "
+"Diferente de suspenso, este método não desassocia a segmentação atual a "
+"partir da(s) transação(ões). Isto pode ser usado para ativar as segmentações "
+"múltiplas para execução com o escopo da mesma transação."
+
+#. Tag: para
+#: The_XTS_API.xml:106
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a transaction, the "
+"container or participant must use:"
+msgstr ""
+"Com o objetivo de registrar e re-assinar os participantes com a transação, o "
+"container ou participante devem usar:"
+
+#. Tag: para
+#: The_XTS_API.xml:111
+#, no-c-format
+msgid ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"Volatile2PC protocol; a unique identifier for the participant is also "
+"required. If there is no transaction associated with the invoking thread "
+"then the <code>UnknownTransactionException</code> exception is thrown. If "
+"the coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: lista o participante "
+"especificado com a transação atual que isto participará no protocolo "
+"Volatile2PC. O identificador único para o participante é também solicitado. "
+"Caso não haja transação associada com a segmentação de invocação, a exceção "
+"<code>UnknownTransactionException</code> será lançada. Caso o coordenador já "
+"tenha participado do adicionamento com o mesmo identificador, a "
+"<code>AlreadyRegisteredException</code> será lançada. Caso a transação não "
+"esteja num estado onde os participantes podem ser adicionados (por exemplo: "
+"isto está sendo encerrado), a <code>WrongStateException</code> será lançada."
+
+#. Tag: para
+#: The_XTS_API.xml:116
+#, no-c-format
+msgid ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"2PC protocol; a unique identifier for the participant is also required. If "
+"there is no transaction associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: lista o participante "
+"especificado com a transação atual, tal como isto participará no protocolo "
+"2PC (um identificador único para o participante é também solicitado). Caso "
+"não haja transação associada com a segmentação de invocação, a exceção "
+"<code>UnknownTransactionException</code> será lançada. Caso o coordenador já "
+"possua um participante adicionado com o mesmo identificador, a "
+"<code>AlreadyRegisteredException</code> será lançada. Caso a transação não "
+"estiver num estado onde participantes podem ser adicionados (por exemplo: "
+"isto está sendo finalizado) a <code>WrongStateException</code> será lançada."
+
+#. Tag: title
+#: The_XTS_API.xml:122
+#, no-c-format
+msgid "TransactionFactory"
+msgstr "TransactionFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+"Os TransactionManagers são obtidos a partir da <code>TransactionFactory</"
+"code>."
+
+#. Tag: title
+#: The_XTS_API.xml:130
+#, no-c-format
+msgid "API for the Business Activity protocol"
+msgstr "O API para o protocolo da Atividade Comercial"
+
+#. Tag: title
+#: The_XTS_API.xml:132
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr "UserBusinessActivity"
+
+#. Tag: para
+#: The_XTS_API.xml:133
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserBusinessActivity</classname> is the class "
+"that most users (for example, clients and services) will see. This isolates "
+"them from the underlying protocol-specific aspects of the XTS "
+"implementation. Importantly, a <code>UserBusinessActivity</code> does not "
+"represent a specific business activity, but rather is responsible for "
+"providing access to an implicit per-thread activity. Therefore, all of the "
+"<code>UserBusinessActivity</code> methods implicitly act on the current "
+"thread of control."
+msgstr ""
+"A <classname>com.arjuna.wst.UserBusinessActivity</classname> é a classe que "
+"a maioria dos usuários (por exemplo: clientes e serviços) verão. Isto os "
+"isola dos aspectos de protocolo específico subjacente da implementação XTS. "
+"A <code>UserBusinessActivity</code> não representa uma atividade comercial "
+"específica, mas é responsável em fornecer acesso a uma atividade por "
+"segmentação implícita. Portanto, todos os métodos de "
+"<code>UserBusinessActivity</code> implícitos atuam na segmentação atual de "
+"controle."
+
+#. Tag: para
+#: The_XTS_API.xml:137
+#, no-c-format
+msgid ""
+"A new business activity is begun and associated with the invoking thread by "
+"using the begin method. If there is already an activity associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created activity with the "
+"current thread."
+msgstr ""
+"Uma nova atividade comercial é inicializada e associada com a segmentação de "
+"invocação pelo uso do método inicializado. Caso já exista uma atividade "
+"associada com a segmentação, a exceção <code>WrongStateException</code> será "
+"lançada. Esta operação associa a nova atividade criada com a segmentação "
+"atual, em caso da operação ser bem sucedida."
+
+#. Tag: para
+#: The_XTS_API.xml:140
+#, no-c-format
+msgid ""
+"The business activity is completed successfully by the close method. This "
+"will execute the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol prior to returning. If there is no activity associated with the "
+"invoking thread then <code>UnknownTransactionException</code> is thrown. If "
+"the activity ultimately cancels then the "
+"<code>TransactionRolledBackException</code> is thrown. When complete, this "
+"operation disassociates the business activity from the current thread such "
+"that it becomes associated with no activity."
+msgstr ""
+"A atividade comercial é completada com sucesso pelo método encerrar. Isto "
+"executará o protocolo de <code>BusinessAgreementWithParticipantCompletion</"
+"code> antes do retorno. Caso não haja atividade associada com a segmentação "
+"de invocação, a <code>UnknownTransactionException</code> será lançada. Caso "
+"a atividade seja cancelada, a <code>TransactionRolledBackException</code> "
+"será lançada. Uma vez completada, esta operação desassocia a atividade "
+"comercial a partir da segmentação atual, de forma que isto não se associa a "
+"nenhuma atividade."
+
+#. Tag: para
+#: The_XTS_API.xml:143
+#, no-c-format
+msgid ""
+"The cancel operation will terminate the business activity and return "
+"normally if it succeeded, while throwing an appropriate exception if it "
+"didn’t. If there is no activity associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. Any participants that "
+"had previously completed will be informed to compensate for their work."
+msgstr ""
+"A operação cancelar encerrará a atividade comercial e, normalmente, "
+"retornará caso isto seja bem sucedida, enquanto lançando uma exceção "
+"apropriada (caso isto não tenha sido realizado). Caso não haja atividade "
+"associada com a segmentação da invocação, a "
+"<code>UnknownTransactionException</code> será lançada. Quaisquer "
+"participantes que tenham completado anteriormente serão informados a "
+"compensar os seus trabalhos."
+
+#. Tag: para
+#: The_XTS_API.xml:146
+#, no-c-format
+msgid ""
+"Some participants may have registered for the "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol, which "
+"requires the coordinator or application to inform them when all work that "
+"they need to do within the scope of a business activity has been performed. "
+"The application should therefore use the complete method to inform these "
+"participants."
+msgstr ""
+"Alguns participantes podem ser registrados para o protocolo de "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>, que requer que o "
+"coordenador ou aplicativo os informe quando todo trabalho que eles precisam "
+"para realizar com o escopo de uma atividade comercial sendo desempenhada. O "
+"aplicativo deve, portanto, usar o método completar para informar estes "
+"participantes."
+
+#. Tag: title
+#: The_XTS_API.xml:150
+#, no-c-format
+msgid "UserBusinessActivityFactory"
+msgstr "UserBusinessActivityFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+"As UserBusinessActivities são obtidas a partir de uma "
+"<code>UserBusinessActivityFactory</code>."
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr "BusinessActivityManager"
+
+#. Tag: para
+#: The_XTS_API.xml:157
+#, no-c-format
+msgid ""
+"The <interfacename>BusinessActivityManager</interfacename> interface "
+"represents the service/container/participant’s (service-side users) typical "
+"way in which to interact with the underlying business activity service "
+"implementation. As with <interfacename>UserBusinessActivity</interfacename> "
+"a <interfacename>BusinessActivityManager</interfacename> does not represent "
+"a specific activity, but rather is responsible for providing access to an "
+"implicit per-thread activity."
+msgstr ""
+"A interface <interfacename>BusinessActivityManager</interfacename> "
+"representa a maneira típica de participante/container/serviço (usuários ao "
+"lado do serviço) pelo qual interage com a implementação de serviço de "
+"atividade comercial subjacente. Assim como a "
+"<interfacename>UserBusinessActivity</interfacename>, o "
+"<interfacename>BusinessActivityManager</interfacename> não representa uma "
+"atividade específica, mas é responsável em fornecer acesso à atividade por "
+"segmentação implícita."
+
+#. Tag: para
+#: The_XTS_API.xml:161
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific activity. In order "
+"to do this it is necessary to disassociate the thread from any business "
+"activities. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the activity. The "
+"thread is then no longer associated with any activity."
+msgstr ""
+"O controle de segmentação pode solicitar períodos de não-transacionalidade, "
+"de forma que ele pode executar o trabalho que não está associado com uma "
+"atividade específica. Com o objetivo de realizar isto, é necessário "
+"desassociar a segmentação a partir de quaisquer atividades comerciais. O "
+"método suspender executa isto, retornando a instância <code>TxContext</"
+"code>, que é uma ajuda na atividade. A segmentação não é mais associada com "
+"qualquer atividade."
+
+#. Tag: para
+#: The_XTS_API.xml:164
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with an activity (or activities) via its TxContext. Prior to "
+"association, the thread is disassociated with any activity with which it may "
+"be currently associated. If the <code>TxContext</code> is null, then the "
+"thread is associated with no activity. The "
+"<code>UnknownTransactionException</code> exception is thrown if the business "
+"activity that the TxContext refers to is invalid in the scope of the "
+"invoking thread."
+msgstr ""
+"O método <methodname>resumir</methodname> pode ser usado para (re-)associar "
+"uma segmentação com uma atividade (ou atividades) através do próprio "
+"TxContext. Precedente a esta associação, a segmentação é desassociada com "
+"qualquer atividade que isto possa estar associada no momento. Caso o "
+"<code>TxContext</code> seja nulo, então a segmentação não é associada com "
+"nenhuma atividade. A exceção <code>UnknownTransactionException</code> é "
+"lançada caso a atividade comercial que o TxContext refere-se é inválida no "
+"contexto da segmentação de invocação."
+
+#. Tag: para
+#: The_XTS_API.xml:167
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current business activity, or null if there "
+"is none. Unlike suspend, this method does not disassociate the current "
+"thread from the activity. This can be used to enable multiple threads to "
+"execute within the scope of the same business activity."
+msgstr ""
+"O método <methodname>currentTransaction</methodname> retorna o "
+"<code>TxContext</code> para a atividade comercial atual ou é nulo (caso não "
+"haja algum). Diferente do método suspender, este método não desassocia a "
+"segmentação atual a partir da atividade. Isto pode ser usado para ativar "
+"segmentações múltiplas para executar com o escopo a mesma atividade "
+"comercial."
+
+#. Tag: para
+#: The_XTS_API.xml:170
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a business activity, the "
+"container or participant must use:"
+msgstr ""
+"Com o objetivo de registra e re-assinar participantes com a atividade "
+"comercial, o container ou participante deve usar:"
+
+#. Tag: para
+#: The_XTS_API.xml:175
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"enlist the specified participant with current business activity such that it "
+"will participate in the <code>BusinessAgreementWithParticipantCompletion</"
+"code> protocol; a unique identifier for the participant is also required. If "
+"there is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"lista o participante especificado com a atividade comercial atual, de forma "
+"que isto participará do protocolo "
+"<code>BusinessAgreementWithParticipantCompletion</code> (um identificador "
+"único para o participante será também solicitado. Caso não haja atividade "
+"comercial associada com a segmentação de invocação, a exceção "
+"<code>UnknownTransactionException</code> será lançada. Caso o coordenador "
+"possua um participante adicionado com o mesmo identificador, a "
+"<code>AlreadyRegisteredException</code> será lançada. Caso a atividade não "
+"estiver num estado onde os participantes possam ser associados (por exemplo: "
+"isto estiver sendo encerrado), a <code>WrongStateException</code> será "
+"lançada."
+
+#. Tag: para
+#: The_XTS_API.xml:180
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"enlist the specified participant with current activity such that it will "
+"participate in the <code>BusinessAgreementWithCoordinatorCompletion</code> "
+"protocol; a unique identifier for the participant is also required. If there "
+"is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"lista o participante especificado com a atividade atual, de forma que isto "
+"participará do protocolo <code>BusinessAgreementWithCoordinatorCompletion</"
+"code> (um identificador único para o participante será também solicitado). "
+"Caso não haja atividade comercial associada com a segmentação da invocação, "
+"a exceção <code>UnknownTransactionException</code> será lançada. Caso o "
+"coordenador já tenha um participante adicionado com o mesmo identificador, a "
+"<code>AlreadyRegisteredException</code> será lançada. Caso a atividade não "
+"estiver na situação onde participantes possam ser adicionados (por exemplo: "
+"isto estiver sendo encerrado), a <code>WrongStateException</code> será "
+"lançada."
+
+#. Tag: title
+#: The_XTS_API.xml:186
+#, no-c-format
+msgid "BusinessActivityManagerFactory"
+msgstr "BusinessActivityManagerFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
+"Os BusinessActivityManagers são obtidos a partir de uma "
+"<code>BusinessActivityManagerFactory</code>."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactional_Web_Services.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactional_Web_Services.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactional_Web_Services.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,142 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr "Serviços da Web Transacional "
+
+#. Tag: title
+#: Transactional_Web_Services.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introdução"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:9
+#, no-c-format
+msgid ""
+"This chapter describes how to provide transactional support for new and "
+"existing Web services using the service-side facilities of XTS. It shows how "
+"new services can be made transactional with no additional programming, and "
+"how existing services can be made WS-T transaction-aware in a non-invasive "
+"fashion."
+msgstr ""
+"Este capítulo descreve como fornecer o suporte transacional para serviços "
+"novos e existentes da Web usando as facilidades ao lado do serviço do XTS. "
+"Isto demonstra como os novos serviços podem ser feitos transacionais sem uma "
+"programação adicional e como serviços existentes podem ser feitos cientes da "
+"transação WS-T numa moda não-invasiva."
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr "O Serviço da Web Transacional"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:16
+#, no-c-format
+msgid ""
+"A Web service is a business-level entity. It encapsulates application logic "
+"needed to perform some domain-specific task, or is designed to delegate to a "
+"back-end system which executes that logic. Given it is part of application "
+"code, such non-functional requirements as transactionality should not "
+"impinge on its construction."
+msgstr ""
+"O serviço da Web numa entidade de serviço comercial. Ele encapsula a lógica "
+"do aplicativo necessária para executar alguma tarefa de domínio específico "
+"ou é designado a delegar um sistema back-end que executa aquela lógica. Uma "
+"vez que isto é parte do código do aplicativo, tais solicitações não-"
+"funcionais como a transacionalidade colidem com suas construções."
+
+#. Tag: para
+#: Transactional_Web_Services.xml:19
+#, no-c-format
+msgid ""
+"To support this notion, XTS provides a suite of components designed to work "
+"at the SOAP stack level, which deal with transactional matters on behalf of "
+"a Web service without requiring any changes to that service. In XTS two "
+"context handling components are registered with the SOAP server and deal "
+"with context management on behalf of the service without the service having "
+"to worry about context propagation issues itself. This is shown in the "
+"following figure."
+msgstr ""
+"Para suportar esta noção, o XTS fornece uma suíte de componentes designada a "
+"trabalhar no nível de empilhamento SOAP, que cuida dos assuntos "
+"transacionais em nome do serviço da Web sem solicitar qualquer alterações "
+"aquele serviço. No XTS dois componentes de manuseio do contexto são "
+"registrados com o servidor SOAP e cuidam do gerenciador do contexto em nome "
+"do serviço sem que o mesmo tenha que se preocupar com os problemas de "
+"propagação do contexto. Isto é apresentado na figura abaixo:"
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr "Manuseadores do Contexto Registrado com o Servidor SOAP"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:28
+#, no-c-format
+msgid ""
+"The detail of the context management that the context processor performs is "
+"unimportant to the Web service application logic, and is orthogonal to any "
+"work performed by any other protocol-specific context handlers too. However "
+"back-end systems which the Web service application logic uses (such as "
+"databases) are often interested in the front-end transaction context such "
+"that any operations invoked within its scope can be mapped onto a back-end "
+"transaction context. This is typically achieved at the back-end by wrapping "
+"a database driver in a veneer which implements both the interface of the "
+"original driver and hooks into the service-side API to access the "
+"transaction context details. The general architecture for this pattern is "
+"shown in the figure below."
+msgstr ""
+"O detalhe do gerenciador do contexto em que o processador do contexto "
+"executa não possui importância à lógica de aplicativo do servidor da Web e é "
+"ortogonal a qualquer trabalho executado por quaisquer manuseadores do "
+"contexto de protocolo especificado. No entanto, os sistemas back-end que a "
+"lógica de serviço da Web usa (tais como banco de dados) são freqüentemente "
+"interessantes no contexto de transação de frente tais como quaisquer "
+"operações invocadas com o próprio escopo podendo ser mapeado num contexto de "
+"transação back-end. Isto é tipicamente atingido no back-end pelo "
+"empacotamento do driver de banco de dados no adicionamento que implementa "
+"ambas as interfaces do driver original e junta-se ao API ao lado do servidor "
+"para acessar os detalhes do contexto de transação. A arquitetura geral para "
+"este padrão é apresentada na figura abaixo."
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:35
+#, no-c-format
+msgid "General Pattern for Back-End Integration, Service Side"
+msgstr "Padrão Geral para a Integração Back-End, ao lado do Servidor"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:37
+#, no-c-format
+msgid ""
+"The missing element from this is the commit protocol which finally allows "
+"back-end work to be made durable or not at the end of a transaction. This is "
+"covered in the participant chapter where the participant/back-end relation "
+"is explored further."
+msgstr ""
+"O elemento que faltante é o protocolo que finalmente permite que o trabalho "
+"back-end possa ser feito durável ou não no final da transação. Isto é "
+"coberto num capítulo participante onde a relação participante/back-end é "
+"explorada à frente."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,900 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactions_Overview.xml:6
+#, no-c-format
+msgid "Transactions Overview"
+msgstr "Visão Geral das Transações"
+
+#. Tag: para
+#: Transactions_Overview.xml:7
+#, no-c-format
+msgid ""
+"Transactions have emerged as the dominant paradigm for coordinating "
+"interactions between parties in a distributed system, and in particular to "
+"manage applications that require concurrent access to shared data. Much of "
+"the JBossTS Web Service API is based on contemporary transaction APIs whose "
+"familiarity will enhance developer productivity and lessen the learning "
+"curve. While the following section provides the essential information that "
+"you should know before starting to use XTS for building transactional Web "
+"Services, it should not be treated as a definitive reference to all "
+"transactional technology."
+msgstr ""
+"As transações emergiram como um paradigma dominante para as interações de "
+"coordenação entre as partes num sistema distribuído, e particularmente para "
+"gerenciar aplicativos que solicitam acesso atual aos dados compartilhados. A "
+"maioria dos APIs de Serviço da Web do JBossTS são baseados numa transação "
+"contemporânea de APIs familiarizáveis que aumentarão a produtividade do "
+"desenvolvedor e reduzirão a curva de aprendizado. Enquanto a seção seguinte "
+"fornece a informação essencial que você deve conhecer antes de inicializar o "
+"uso do XTS para construção dos Serviços da Web transacional, ela não deve "
+"ser tratada como uma referência definitiva a todas as tecnologias "
+"transacionais. "
+
+#. Tag: para
+#: Transactions_Overview.xml:10
+#, no-c-format
+msgid ""
+"A classic transaction is a unit of work that either completely succeeds, or "
+"fails with all partially completed work being undone. When a transaction is "
+"committed, all changes made by the associated requests are made durable, "
+"normally by committing the results of the work to a database. If a "
+"transaction should fail and is rolled back, all changes made by the "
+"associated work are undone. Transactions in distributed systems typically "
+"require the use of a transaction manager that is responsible for "
+"coordinating all of the participants that are part of the transaction."
+msgstr ""
+"A transação clássica é uma unidade de trabalho que tanto sucede "
+"completamente ou falha com todo trabalho parcialmente completado sendo "
+"desfeito. Enquanto a transação é confirmada, todas as alterações feitas "
+"pelas solicitações associadas são feitas duráveis, normalmente pela "
+"confirmação dos resultados de trabalho a um banco de dados. Caso a transação "
+"falhar e for revertida, todas as alterações realizadas pelo trabalho "
+"associado serão desfeitas. Normalmente, as transações nos sistemas "
+"distribuídos solicitam o uso do gerenciador da transação que é responsável "
+"pela coordenação de todos os participantes que fazem parte da transação."
+
+#. Tag: para
+#: Transactions_Overview.xml:13
+#, no-c-format
+msgid ""
+"The main components involved in using and defining transactional Web "
+"Services using XTS are illustrated in Figure 1."
+msgstr ""
+"Os componentes principais envolvidos no uso e definição dos Serviços da Web "
+"transacional usando o XTS estão ilustrados na Figura 1."
+
+#. Tag: para
+#: Transactions_Overview.xml:18
+#, no-c-format
+msgid ""
+"A Transaction Service: The Transaction Service captures the model of the "
+"underlying transaction protocol and coordinates parties affiliated with the "
+"transaction according to that model."
+msgstr ""
+"O Serviço Transacional: O Serviço Transacional captura o modelo do protocolo "
+"de transação subjacente e coordena as partes afiliadas com a transação de "
+"acordo com aquele modelo."
+
+#. Tag: para
+#: Transactions_Overview.xml:23
+#, no-c-format
+msgid ""
+"A Transaction API: Provides an interface for transaction demarcation and the "
+"registration of participants."
+msgstr ""
+"O API de Transação: Fornece uma interface para a demarcação da transação e "
+"registro dos participantes."
+
+#. Tag: para
+#: Transactions_Overview.xml:28
+#, no-c-format
+msgid ""
+"A Participant: The entity that cooperates with the transaction service on "
+"behalf of its associated business logic."
+msgstr ""
+"O Participante: A entidade que coopera com o serviço da transação em nome da "
+"própria lógica comercial associada."
+
+#. Tag: para
+#: Transactions_Overview.xml:33
+#, no-c-format
+msgid ""
+"The Context: Captures the necessary details of the transaction such that "
+"participants can enlist within its scope."
+msgstr ""
+"O Contexto: Captura os detalhes necessários da transação de forma que os "
+"participantes podem listar com o próprio escopo."
+
+#. Tag: caption
+#: Transactions_Overview.xml:42
+#, no-c-format
+msgid "Web Services and XTS"
+msgstr "Serviços da Web e XTS"
+
+#. Tag: title
+#: Transactions_Overview.xml:45
+#, no-c-format
+msgid "The Coordinator"
+msgstr "O Coordenador"
+
+#. Tag: para
+#: Transactions_Overview.xml:46
+#, no-c-format
+msgid ""
+"Associated with every transaction is a coordinator, which is responsible for "
+"governing the outcome of the transaction. The coordinator may be implemented "
+"as a separate service or may be co-located with the user for improved "
+"performance. Each coordinator is created by the transaction manager service, "
+"which is in effect a factory for those coordinators."
+msgstr ""
+"O coordenador está associado com cada transação, que é responsável por "
+"governar o resultado da transação. O coordenador pode ser implementado como "
+"um serviço separado ou ser colocado com um usuário para melhoramento do "
+"desempenho. Cada coordenador é criado pelo serviço gerenciador da transação, "
+"que é o efeito da criação para estes coordenadores."
+
+#. Tag: para
+#: Transactions_Overview.xml:50
+#, no-c-format
+msgid ""
+"A coordinator communicates with enrolled participants to inform them of the "
+"desired termination requirements, for instance, whether they should accept "
+"(for example, confirm) or reject (for example, cancel) the work done within "
+"the scope of the given transaction. For example, whether to purchase the "
+"(provisionally reserved) flight tickets for the user or to release them. An "
+"application/client may wish to terminate a transaction in a number of "
+"different ways (for example, confirm or cancel). However, although the "
+"coordinator will attempt to terminate in a manner consistent with that "
+"desired by the client, it is ultimately the interactions between the "
+"coordinator and the participants that will determine the actual final "
+"outcome."
+msgstr ""
+"O coordenador comunica-se com os participantes conectados para informá-los "
+"das solicitações de término desejadas, por exemplo: quando eles devem "
+"aceitar (confirmar) ou rejeitar (cancelar) o trabalho realizado com o escopo "
+"da transação gerada. Por exemplo: comprar ou não os bilhetes de avião "
+"(temporariamente reservados) para o usuário ou liberá-los."
+
+#. Tag: para
+#: Transactions_Overview.xml:53
+#, no-c-format
+msgid ""
+"A transaction manager is typically responsible for managing coordinators for "
+"many transactions. The initiator of the transaction (for example, the "
+"client) communicates with a transaction manager and asks it to start a new "
+"transaction and associate a coordinator with the transaction. Once created, "
+"the context can be propagated to Web services in order for them to associate "
+"their work with the transaction."
+msgstr ""
+"O gerenciador da transação é normalmente responsável por gerenciar os "
+"coordenadores por muitas transações. O iniciador da transação (por exemplo: "
+"o cliente comunica-se com o gerenciador da transação e pede para inicializar "
+"uma nova transação e associar um coordenador com a transação. Uma vez "
+"criado, o contexto pode ser propagado aos serviços da Web, com o objetivo de "
+"associá-los ao próprio trabalho com a associação."
+
+#. Tag: title
+#: Transactions_Overview.xml:57
+#, no-c-format
+msgid "The Transaction Context"
+msgstr "O Contexto da Transação"
+
+#. Tag: para
+#: Transactions_Overview.xml:58
+#, no-c-format
+msgid ""
+"In order for a transaction to span a number of services, certain information "
+"has to be shared between those services in order to propagate information "
+"about the transaction. This information is known as the Context. Using XTS, "
+"the context is automatically propagated and processed by transaction-aware "
+"components of an application. Though XTS removes most of the work associated "
+"with propagating contexts, it is still instructive to understand what "
+"information is captured in a context:"
+msgstr ""
+"Com o objetivo da transação realizar o span num número de serviços, certas "
+"informações precisam ser compartilhadas entre estes serviços, com o objetivo "
+"de propagar a informação a respeito da transação. Esta informação é "
+"conhecida como Contexto. O contexto é automaticamente propagado e processado "
+"pelos componentes cientes da transação de um aplicativo, pelo uso do XTS. "
+"Visto que o XTS remove a maioria do trabalho associado com os contextos de "
+"propagação, isto continua sendo instrutivo o entendimento de qual informação "
+"é capturada num contexto:"
+
+#. Tag: para
+#: Transactions_Overview.xml:64
+#, no-c-format
+msgid ""
+"A transaction identifier which guarantees global uniqueness for an "
+"individual transaction;"
+msgstr ""
+"O identificador da transação que garante a exclusividade global para uma "
+"transação individual;"
+
+#. Tag: para
+#: Transactions_Overview.xml:69
+#, no-c-format
+msgid ""
+"The transaction coordinator location or endpoint address so participants can "
+"be enrolled."
+msgstr ""
+"A localização do coordenador de transação ou o endereço de ponto final, de "
+"forma que os participantes podem ser registrados."
+
+#. Tag: caption
+#: Transactions_Overview.xml:78
+#, no-c-format
+msgid "Web Services and Context Flow"
+msgstr "Os Serviços da Web e o Fluxo do Contexto"
+
+#. Tag: para
+#: Transactions_Overview.xml:80
+#, no-c-format
+msgid ""
+"As shown in Figure 2, whenever an application message is sent, the XTS "
+"Client API automatically creates a context and embeds it into the message. "
+"Similarly, any transaction-aware services are able to extract that context "
+"using the XTS service-side infrastructure and use it to perform work within "
+"the context of a particular transaction – even though that transaction was "
+"initiated elsewhere on the Web! The value of this approach is that the "
+"business logic contained within the client application and services are not "
+"peppered with transaction-processing code."
+msgstr ""
+"Conforme apresentado na Figura 2, toda a vez que uma mensagem é enviada, o "
+"API do Cliente XTS automaticamente cria um contexto e adiciona isto à "
+"mensagem. Parecido com isto, os serviços cientes de transação estão aptos a "
+"extrair aquele contexto usando a infra-estrutura ao lado do serviço XTS e o "
+"utilizam para executar o trabalho com o contexto de uma transação "
+"particular, mesmo que a transação tenha sido inicializada em algum outro "
+"lugar da Web. O valor desta abordagem é aquele contido na lógica comercial "
+"com o aplicativo do cliente e os serviços não estão temperados com o código "
+"de processamento da transação."
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr "Transações ACID"
+
+#. Tag: para
+#: Transactions_Overview.xml:85
+#, no-c-format
+msgid ""
+"Traditionally, transaction processing systems support ACID properties. ACID "
+"is an acronym for Atomic, Consistent, Isolated, and Durable. A unit of work "
+"has traditionally been considered transactional only if the ACID properties "
+"are maintained:"
+msgstr ""
+"Tradicionalmente, os sistemas de processamento da transação suportam as "
+"propriedades ACID. O AID é um acrônimo para Atômica, Consistente, Isolada e "
+"Durável. A unidade de trabalho é tradicionalmente considerada transacional, "
+"apenas se as propriedades ACID estiverem sendo mantidas:"
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr "Atomicidade: A transação executa tudo por completo ou nada."
+
+#. Tag: para
+#: Transactions_Overview.xml:96
+#, no-c-format
+msgid ""
+"Consistency: The effects of the transaction preserve the internal "
+"consistency of an underlying data structure."
+msgstr ""
+"Consistência: Os efeitos da transação preservam a consistência interna de "
+"uma estrutura da dados subjacentes."
+
+#. Tag: para
+#: Transactions_Overview.xml:101
+#, no-c-format
+msgid ""
+"Isolated: The transaction runs as if it were running alone with no other "
+"transactions running and is not visible to other transactions."
+msgstr ""
+"Isolada: A transação roda como se ela estivesse rodando sozinha com nenhuma "
+"outra transação rodando e isto não é visível às outras transações."
+
+#. Tag: para
+#: Transactions_Overview.xml:106
+#, no-c-format
+msgid ""
+"Durable: the transaction’s results will not be lost in the event of a "
+"failure."
+msgstr ""
+"Durável: Os resultados da transação não serão perdidos num evento de falha."
+
+#. Tag: title
+#: Transactions_Overview.xml:112
+#, no-c-format
+msgid "Two-Phase Commit"
+msgstr "Confirmação de Duas Fases"
+
+#. Tag: para
+#: Transactions_Overview.xml:113
+#, no-c-format
+msgid ""
+"The classical two-phase commit approach is the bedrock of JBossTS (and more "
+"generally of Web Services transactions). Two-phase commit provides "
+"coordination of parties that are involved in a transaction. In general, the "
+"flow of a two-phase commit transaction is as follows:"
+msgstr ""
+"A clássica abordagem de confirmação de duas fases é o fundamento do JBossTS "
+"(e geralmente das transações dos Serviços da Web). A confirmação de duas "
+"fases fornece a coordenação das partes que estão envolvidas numa transação. "
+"Em geral, o fluxo da transação de duas fases é a seguinte:"
+
+#. Tag: para
+#: Transactions_Overview.xml:119
+#, no-c-format
+msgid "A transaction is started, and some work is performed."
+msgstr "A transação é inicializada e alguns trabalhos são executados."
+
+#. Tag: para
+#: Transactions_Overview.xml:124
+#, no-c-format
+msgid "Once the work is finished, the two-phase commit begins."
+msgstr ""
+"Uma vez que o trabalho é concluído, a confirmação de duas fases inicializa."
+
+#. Tag: para
+#: Transactions_Overview.xml:129
+#, no-c-format
+msgid ""
+"The coordinator (transaction manager) of the transaction asks each resource "
+"taking part in the transaction whether it is prepared to commit."
+msgstr ""
+"O coordenador (gerenciador da transação) da transação pergunta a cada "
+"recurso fazendo parte da transação se é que isto está preparado para a "
+"confirmação ou não."
+
+#. Tag: para
+#: Transactions_Overview.xml:134
+#, no-c-format
+msgid ""
+"If all resources respond positively, the coordinator instructs all work "
+"performed to be made durable (usually committed to a database)."
+msgstr ""
+"Caso todos os recursos respondam positivamente, o coordenador instrui todo "
+"trabalho executado a ser durável (normalmente confirmado ao banco de dados)."
+
+#. Tag: para
+#: Transactions_Overview.xml:139
+#, no-c-format
+msgid ""
+"If not, all work performed is rolled back (undone) such that the underlying "
+"data structures are in their original states."
+msgstr ""
+"Do contrário, todo o trabalho executado é revertido (desfeito), de tal "
+"maneira que as estruturas de dados estão em seus estados originais. "
+
+#. Tag: caption
+#: Transactions_Overview.xml:148
+#, no-c-format
+msgid "The Two-Phase Commit Protocol"
+msgstr "O Protocolo de Conformação de Duas Fases"
+
+#. Tag: para
+#: Transactions_Overview.xml:151
+#, no-c-format
+msgid ""
+"During two-phase commit transactions, coordinators and resources keep track "
+"of activity in non-volatile data stores so that they can recover in the case "
+"of a failure."
+msgstr ""
+"Durante as transações de confirmação de duas fases, os coordenadores e "
+"recursos checam a atividade em armazenamentos de dados não-voláteis, de "
+"forma que eles podem realizar a recuperação no caso de uma falha."
+
+#. Tag: title
+#: Transactions_Overview.xml:156
+#, no-c-format
+msgid "The synchronization protocol"
+msgstr "O protocolo de sincronização"
+
+#. Tag: para
+#: Transactions_Overview.xml:157
+#, no-c-format
+msgid ""
+"As well as the two-phase commit protocol, traditional transaction processing "
+"systems employ an additional protocol, often referred to as the "
+"synchronization protocol. If you recall the original ACID properties, then "
+"you’ll remember that Durability is important in the case where state changes "
+"have to be available despite failures. What this means is that applications "
+"interact with a persistence store of some kind (e.g., a database) and this "
+"can impose a significant overhead – disk access is orders of magnitude "
+"slower than access to main computer memory."
+msgstr ""
+"Assim como o protocolo de confirmação de duas fases, os sistemas de "
+"processamento de transação tradicional empregam um protocolo adicional, "
+"normalmente referidos ao protocolo de sincronização. Caso você chame "
+"novamente as propriedades ACID original, então você lembrará que a "
+"durabilidade é importante em casos onde as alterações de estado precisam "
+"estar disponíveis independente das falhas. Isto quer dizer que os "
+"aplicativos interagem com o armazenamento de persistência de alguma forma "
+"(por exemplo: um banco de dados) e isto pode impor uma elevação "
+"significativa - o acesso ao disco é um pedido de lenta magnitude do que o "
+"acesso à memória do computador principal. "
+
+#. Tag: para
+#: Transactions_Overview.xml:161
+#, no-c-format
+msgid ""
+"One apparently obvious solution to this problem would be to cache the state "
+"in main memory and only operate on that for the duration of a transaction. "
+"Unfortunately you’d then need some way of being able to flush the state back "
+"to the persistent store before the transaction terminates, or risk losing "
+"the full ACID properties. This is what the synchronization protocol does, "
+"with Synchronization participants."
+msgstr ""
+"Uma solução aparentemente óbvia a este problema pode ser a realização do "
+"cache ao estado em memória, e apenas operar nisto para a duração da "
+"transação. Infelizmente, você precisará de alguma forma estar apto a "
+"esvaziar o estado de retorno ao armazenamento persistente, antes da "
+"transação finalizar ou haverá risco de perda de todas as propriedades ACID. "
+"Isto é o que o protocolo de sincronização realiza com os participantes de "
+"Sincronização."
+
+#. Tag: para
+#: Transactions_Overview.xml:164
+#, no-c-format
+msgid ""
+"Synchronizations are informed that a transaction is about to commit, so they "
+"can, for example, flush cached state, which may be being used to improve "
+"performance of an application, to a durable representation prior to the "
+"transaction committing. They are then informed when the transaction has "
+"completed and in what state it completed."
+msgstr ""
+"As sincronizações são informadas que a transação está prestes a ser "
+"confirmada, de forma que elas podem, por exemplo, esvaziar o estado com "
+"cache que poderá ser utilizado para melhorar o desempenho de um aplicativo a "
+"uma representação durável antecedente à confirmação da transação. Elas serão "
+"notificadas quando a transação for completada e em que estado ela foi "
+"completada."
+
+#. Tag: para
+#: Transactions_Overview.xml:169
+#, no-c-format
+msgid ""
+"Synchronizations essentially turn the two-phase commit protocol into a four-"
+"phase protocol:"
+msgstr ""
+"As sincronizações modificam o protocolo de confirmação de duas fases num "
+"protocolo de quatro fases:"
+
+#. Tag: para
+#: Transactions_Overview.xml:174
+#, no-c-format
+msgid ""
+"Before the transaction starts the two-phase commit, all registered "
+"Synchronizations are informed. Any failure at this point will cause the "
+"transaction to roll back."
+msgstr ""
+"Antes das transações inicializarem a confirmação de duas fases, todas as "
+"Sincronizações registradas serão informadas. Qualquer falha neste ponto "
+"causará a reversão da transação."
+
+#. Tag: para
+#: Transactions_Overview.xml:179
+#, no-c-format
+msgid "The coordinator then conducts the normal two-phase commit protocol."
+msgstr ""
+"O coordenador então conduz o protocolo normal de confirmação de duas fases."
+
+#. Tag: para
+#: Transactions_Overview.xml:184
+#, no-c-format
+msgid ""
+"Once the transaction has terminated, all registered Synchronizations are "
+"informed. However, this is a courtesy invocation because any failures at "
+"this stage are ignored: the transaction has terminated so there’s nothing to "
+"affect."
+msgstr ""
+"Uma vez que a transação for finalizada, todas as Sincronizações registradas "
+"serão informadas. No entanto, esta é a invocação de cortesia uma vez que "
+"quaisquer falhas neste estágio serão ignoradas: a transação foi finalizada, "
+"portanto não há nada a ser afetado."
+
+#. Tag: para
+#: Transactions_Overview.xml:189
+#, no-c-format
+msgid ""
+"Unlike the two-phase commit protocol, the synchronization protocol does not "
+"have the same failure requirements. For example, Synchronization "
+"participants don’t need to make sure they can recover in the event of "
+"failures; this is because any failure before the two-phase commit protocol "
+"completes means the transaction will roll back, and failures after it has "
+"completed can’t affect the data the Synchronization participants were "
+"managing."
+msgstr ""
+"Diferente do protocolo de duas fases, o protocolo de sincronização não "
+"possui as mesmas solicitações de falha. Por exemplo: os participantes da "
+"Sincronização não precisam certificar-se de que eles podem realizar a "
+"recuperação num evento de falha. Isto é devido a qualquer falha antes do "
+"protocolo de confirmação de duas fases ser completado, significando que a "
+"transação reverterá e falhará após ser completada, além de não poder afetar "
+"os dados dos participantes de Sincronização sendo gerenciados."
+
+#. Tag: title
+#: Transactions_Overview.xml:193
+#, no-c-format
+msgid "Optimizations to the protocol"
+msgstr "Optimizações ao protocolo"
+
+#. Tag: para
+#: Transactions_Overview.xml:194
+#, no-c-format
+msgid ""
+"There are several variants to the standard two-phase commit protocol that "
+"are worth knowing about because they can have an impact on performance and "
+"failure recovery. We shall briefly describe those that are the most common "
+"variants on the protocol:"
+msgstr ""
+"Existem diversas variações do protocolo de confirmação de duas fases padrão "
+"que valem a pena serem conhecidos, uma vez que eles podem ter um impacto no "
+"desempenho e falha da recuperação. Iremos descrever brevemente as variações "
+"mais comuns no protocolo:"
+
+#. Tag: para
+#: Transactions_Overview.xml:200
+#, no-c-format
+msgid ""
+"Presumed abort: if a transaction is going to roll back then it may simply "
+"record this information locally and tell all enlisted participants. Failure "
+"to contact a participant has no affect on the transaction outcome; the "
+"transaction is effectively informing participants as a courtesy. Once all "
+"participants have been contacted the information about the transaction can "
+"be removed. If a subsequent request for the status of the transaction occurs "
+"there will be no information available and the requestor can assume that the "
+"transaction has aborted (rolled back). This optimization has the benefit "
+"that no information about participants need be made persistent until the "
+"transaction has decided to commit (i.e., progressed to the end of the "
+"prepare phase), since any failure prior to this point will be assumed to be "
+"an abort of the transaction."
+msgstr ""
+"Aborto presumido: caso a transação seja revertida, ela gravará esta "
+"informação localmente e informará a todos os participantes listados. A falha "
+"em contactar um participante não possui efeito no resultado da transação. A "
+"transação está informando os participantes como uma cortesia. Uma vez que "
+"todos os participantes tenham sido contactados, a informação sobre a "
+"transação poderá ser removida. Caso uma solicitação subseqüente para o "
+"status da transação ocorrer, não haverá informação disponível e o "
+"solicitador poderá assumir que a transação foi abortada (revertida). Esta "
+"otimização possui o benefício de não possuir informação sobre participantes "
+"que precisam ser persistentes até que a transação tenha decidido ser "
+"confirmada (por exemplo: progressão ao final da fase de preparo), uma vez "
+"que qualquer falha antecedente a este ponto será assumida como um aborto "
+"desta transação."
+
+#. Tag: para
+#: Transactions_Overview.xml:205
+#, no-c-format
+msgid ""
+"One-phase: if there is only a single participant involved in the "
+"transaction, the coordinator need not drive it through the prepare phase. "
+"Thus, the participant will simply be told to commit and the coordinator need "
+"not record information about the decision since the outcome of the "
+"transaction is solely down to the participant."
+msgstr ""
+"Uma fase: caso exista apenas um único participante envolvido na transação, o "
+"coordenador não precisa dirigir isto através da fase de preparo. Desta "
+"forma, o participante irá simplesmente dizer para confirmar e o coordenador "
+"não precisa gravar informação sobre a decisão, desde que o resultado da "
+"transação seja pouco apenas ao participante."
+
+#. Tag: para
+#: Transactions_Overview.xml:210
+#, no-c-format
+msgid ""
+"Read-only: when a participant is asked to prepare, it can indicate to the "
+"coordinator that no information or data that it controls has been modified "
+"during the transaction. Such a participant does not need to be informed "
+"about the outcome of the transaction since the fate of the participant has "
+"no affect on the transaction. As such, a read-only participant can be "
+"omitted from the second phase of the commit protocol."
+msgstr ""
+"Apenas leitura: quando um participante é informado a preparar-se, isto pode "
+"indicar ao coordenador que nenhuma informação ou dados que isto controla foi "
+"modificado durante a transação. Tal participante não precisa ser informado "
+"sobre o resultado da transação, uma vez que o destino do participante não "
+"possui efeito na transação. Desta forma, o participante de apenas leitura "
+"pode ser omitido da segunda fase do protocolo de confirmação."
+
+#. Tag: title
+#: Transactions_Overview.xml:216
+#, no-c-format
+msgid "Non-atomic transactions and heuristic outcomes"
+msgstr "Transações não-atômicas e resultados heurísticos"
+
+#. Tag: para
+#: Transactions_Overview.xml:217
+#, no-c-format
+msgid ""
+"In order to guarantee atomicity, the two-phase commit protocol is "
+"necessarily blocking. What this means is that as a result of failures, "
+"participants may remain blocked for an indefinite period of time even if "
+"failure recovery mechanisms exist. Some applications and participants simply "
+"cannot tolerate this blocking."
+msgstr ""
+"Com o objetivo de garantir atomicidade, o protocolo de confirmação de duas "
+"fases é necessariamente bloqueado. Isto significa que como resultado de "
+"falhas, os participantes podem continuar bloqueados por um período "
+"indefinido, mesmo se os mecanismos de recuperação de falha existirem. Alguns "
+"aplicativos e participantes não podem tolerar este bloqueamento."
+
+#. Tag: para
+#: Transactions_Overview.xml:221
+#, no-c-format
+msgid ""
+"To break this blocking nature, participants that have got past the prepare "
+"phase are allowed to make autonomous decisions as to whether they commit or "
+"rollback: such a participant must record this decision in case it is "
+"eventually contacted to complete the original transaction. If the "
+"coordinator eventually informs the participant of the transaction outcome "
+"and it is the same as the choice the participant made, then there’s no "
+"problem. However, if it is contrary, then a non-atomic outcome has obviously "
+"happened: a heuristic outcome."
+msgstr ""
+"Para quebrar esta natureza de bloqueamento, os participantes que passaram da "
+"fase de preparo são liberados para realizar decisões autônomas como "
+"confirmar ou reverter ou não. De forma, o participante deve gravar esta "
+"decisão no caso dela ser eventualmente contactada para completar a transação "
+"original. Caso o coordenador eventualmente informar o participante do "
+"resultado da transação e isto for o mesmo da escolha feita pelo "
+"participante, então não haverá problema. No entanto, caso isto seja "
+"contrário, um resultado não-atômico aconteceu com certeza: um resultado "
+"heurístico. "
+
+#. Tag: para
+#: Transactions_Overview.xml:224
+#, no-c-format
+msgid ""
+"How this heuristic outcome is reported to the application and resolved is "
+"usually the domain of complex, manually driven system administration tools, "
+"since in order to attempt an automatic resolution requires semantic "
+"information about the nature of participants involved in the transactions."
+msgstr ""
+"Como este resultado heurístico é relatado ao aplicativo e resolvido é "
+"normalmente o domínio de complexidade, manualmente dirigindo as ferramentas "
+"de administração de sistema, desde que solicite informação semântica sobre a "
+"natureza dos participantes envolvidos na transação, com o objetivo de "
+"empreender uma resolução automática."
+
+#. Tag: para
+#: Transactions_Overview.xml:227
+#, no-c-format
+msgid ""
+"Precisely when a participant makes a heuristic decision is obviously "
+"implementation dependant. Likewise, the choice the participant makes (to "
+"commit or to roll back) will depend upon the implementation and possibly the "
+"application/environment in which it finds itself. The possible heuristic "
+"outcomes are:"
+msgstr ""
+"Certamente, quando um participante realiza uma decisão heurística é "
+"claramente uma dependência de implementação. Da mesma forma, a escolha em "
+"que o participante realiza (de confirmação ou de reversão) dependerá da "
+"implementação e possivelmente do aplicativo/ambiente em que isto se "
+"encontra. Os possíveis resultados heurísticos são:"
+
+#. Tag: para
+#: Transactions_Overview.xml:232
+#, no-c-format
+msgid ""
+"Heuristic rollback: the commit operation failed because some or all of the "
+"participants unilaterally rolled back the transaction."
+msgstr ""
+"Reversão Heurística: a operação de confirmação falhou uma vez que alguns ou "
+"todos os participantes unilateralmente reverteram a transação."
+
+#. Tag: para
+#: Transactions_Overview.xml:237
+#, no-c-format
+msgid ""
+"Heuristic commit: an attempted rollback operation failed because all of the "
+"participants unilaterally committed. This may happen if, for example, the "
+"coordinator was able to successfully prepare the transaction but then "
+"decided to roll it back (for example, it could not update its log) but in "
+"the meanwhile the participants decided to commit."
+msgstr ""
+"Confirmação Heurística: uma tentativa da operação recuperação falhou, pois "
+"todos os participantes confirmaram unilateralmente. Isto pode acontecer se, "
+"por exemplo, o coordenador estava apto a preparar com êxito a transação, mas "
+"depois resolveu reverter isto (por exemplo: isto não pode atualizar o "
+"próprio log), mas os participantes decidiram confirmá-la."
+
+#. Tag: para
+#: Transactions_Overview.xml:242
+#, no-c-format
+msgid ""
+"Heuristic mixed: some updates (participants) were committed while others "
+"were rolled back."
+msgstr ""
+"Mistura Heurística: algumas atualizações (participantes) foram confirmadas "
+"enquanto outras foram revertidas."
+
+#. Tag: para
+#: Transactions_Overview.xml:247
+#, no-c-format
+msgid ""
+"Heuristic hazard: the disposition of some of the updates is unknown. For "
+"those which are known, they have either all been committed or all rolled "
+"back."
+msgstr ""
+"Perigo Heurístico: a disposição de algumas atualizações são desconhecidas. "
+"Para aquelas que são conhecidas, elas podem tanto ter sido confirmadas ou "
+"revertidas."
+
+#. Tag: para
+#: Transactions_Overview.xml:252
+#, no-c-format
+msgid ""
+"Heuristic decisions should be used with care and only in exceptional "
+"circumstances since there is the possibility that the decision will differ "
+"from that determined by the transaction service and will thus lead to a loss "
+"of integrity in the system. Having to perform resolution of heuristics is "
+"something you should try to avoid, either by working with services/"
+"participants that don’t cause heuristics, or by using a transaction service "
+"that provides assistance in the resolution process."
+msgstr ""
+"As decisões heurísticas devem ser usadas com cuidado e apenas em "
+"circunstâncias excepcionais, desde que exista a possibilidade que a decisão "
+"diferencie-se daquela determinada pelo serviço de transação e, portanto, "
+"levará a perda da integridade no sistema. Você deve evitar executar a "
+"resolução das heurísticas, tanto pelo trabalho com serviços/participantes "
+"que não causam heurísticas ou pelo uso do serviço da transação que fornece "
+"assistência no processo da resolução."
+
+#. Tag: title
+#: Transactions_Overview.xml:256
+#, no-c-format
+msgid "A New Transaction Protocol"
+msgstr "O Novo Protocolo da Transação"
+
+#. Tag: para
+#: Transactions_Overview.xml:257
+#, no-c-format
+msgid ""
+"Many component technologies offer mechanisms for coordinating ACID "
+"transactions based on two-phase commit semantics (i.e., CORBA/OTS, JTS/JTA, "
+"MTS/MSDTC). ACID transactions are not suitable for all Web services "
+"transactions since:"
+msgstr ""
+"Muitas tecnologias de componentes oferecem mecanismos para coordenação das "
+"transações ACID baseadas nas semânticas de duas faces. (por exemplo: CORBA/"
+"OTS, JTS/JTA, MTS/MSDTC). As transações ACID não são adequadas para todas as "
+"transações de serviços da Web, desde que:"
+
+#. Tag: para
+#: Transactions_Overview.xml:263
+#, no-c-format
+msgid ""
+"Classic ACID transactions are predicated on the idea that an organization "
+"that develops and deploys applications does so using their own "
+"infrastructure, typically an Intranet. Ownership meant transactions operated "
+"in a trusted and predictable manner. To assure ACIDity, potentially long-"
+"lived locks could be kept on underlying data structures during two-phase "
+"commit. Resources could be used for any period of time and released when the "
+"transaction was complete. In the Web services arena, these assumptions are "
+"no longer valid. One obvious reason is that the owners of data exposed "
+"through a Web service will refuse to allow their data to be locked for "
+"extended periods since to allow such locks invites denial-of-service."
+msgstr ""
+"As transações ACID clássicas são determinadas na idéia que uma organização "
+"desenvolve e implementa aplicativos usando a própria infra-estrutura dos "
+"mesmos, tipicamente a Internet. A posse significa que as transações são "
+"operadas numa maneira confiável e previsível. Para garantir a ACIDity, os "
+"bloqueios de vida longa podem ser mantidos nas estruturas de dados "
+"subjacentes durante a confirmação de duas fases. O recursos podem ser usados "
+"para qualquer período de tempo e liberados quando a transação for completada "
+"na arena de serviços da Web, essas hipóteses não são mais válidas. Uma razão "
+"óbvia é que os proprietários de dados expostos através do serviço da Web "
+"serão recusados para permitir que seus dados sejam bloqueados por períodos "
+"extensos, desde que permita que tais bloqueios convidem a negação de serviço."
+
+#. Tag: para
+#: Transactions_Overview.xml:268
+#, no-c-format
+msgid ""
+"All application infrastructures are generally owned by a single party, "
+"systems using classical ACID transactions normally assume that participants "
+"in a transaction will obey the will of the transaction manager and only "
+"infrequently decide to make unilateral decisions which will hamper other "
+"participants in a transaction. On the contrary, Web services participating "
+"in a transaction can effectively decide to resign from the transaction at "
+"any time, and the consumer of the service generally has little in the way of "
+"quality of service guarantees to prevent this."
+msgstr ""
+"Todas as infra-estruturas do aplicativo são geralmente propriedade de uma "
+"parte única, os sistemas usando as transações ACID clássicas normalmente "
+"assumem que os participantes na transação obedecerão a vontade do "
+"gerenciador da transação, e às vezes decidem realizar decisões unilaterais "
+"que atrasará outros participantes na transação. Do contrário, os Serviços da "
+"Web participantes na transação podem efetivamente decidir desconectar-se da "
+"transação a qualquer instante e o consumidor do serviço geralmente possui "
+"muito pouco, de forma que a qualidade de serviço previne isto. "
+
+#. Tag: title
+#: Transactions_Overview.xml:274
+#, no-c-format
+msgid "Adressing the Problems of Transactioning in Loosely Coupled Systems"
+msgstr ""
+"Endereçando os Problemas de Transacionamento nos Sistemas Loosely Coupled"
+
+#. Tag: para
+#: Transactions_Overview.xml:275
+#, no-c-format
+msgid ""
+"Though extended transaction models which relax the ACID properties have been "
+"proposed over the years, to implement these concepts for the Web services "
+"architecture WS-T provides a new transaction protocol. XTS is designed to "
+"accommodate four underlying requirements inherent in any loosely coupled "
+"architecture like Web services:"
+msgstr ""
+"Uma vez que os modelos de transação estendidas que relaxam as propriedades "
+"ACID têm sido sugeridos pelos últimos anos, para implementar estes conceitos "
+"pelos serviços da Web a arquitetura WS-T fornece um novo protocolo de "
+"transação. O XTS é designado a acomodar quatro inerentes solicitações "
+"subjacentes em qualquer arquitetura loosely coupled como os serviços da Web:"
+
+#. Tag: para
+#: Transactions_Overview.xml:281
+#, no-c-format
+msgid ""
+"Ability to handle multiple successful outcomes to a transaction, with the "
+"ability to involve operations whose effects may not be isolated or durable;"
+msgstr ""
+"Habilidade para manusear resultados com êxito múltiplos para uma transação, "
+"com a habilidade de envolver as operações que pertencem aos efeitos podem "
+"não ser isoladas ou duráveis;"
+
+#. Tag: para
+#: Transactions_Overview.xml:286
+#, no-c-format
+msgid ""
+"Coordination of autonomous parties whose relationships are governed by "
+"contracts rather than the dictates of a central design authority;"
+msgstr ""
+"A coordenação de partes autônomas que pertencem a relações que estão "
+"governadas pelos contratos ao invés de ordenar de uma autoridade de design "
+"central;"
+
+#. Tag: para
+#: Transactions_Overview.xml:291
+#, no-c-format
+msgid ""
+"Discontinuous service, where parties are anticipated to suffer outages "
+"during their lifetime, and coordinated work must be able to survive such "
+"outages;"
+msgstr ""
+"Serviço descontínuo, onde as partes estão antecipadas para sofrerem "
+"interrupções durante o tempo de vida das mesmas e o trabalho coordenado "
+"estar apto a sobreviver tais interrupções; "
+
+#. Tag: para
+#: Transactions_Overview.xml:296
+#, no-c-format
+msgid ""
+"Interoperation using XML over multiple communication protocols – XTS chooses "
+"to use SOAP encoding carried over HTTP for the first release and other SOAP-"
+"friendly transports for future releases."
+msgstr ""
+"Inter-operação usando o XML sobre os protocolos de comunicações múltiplas - "
+"o XTS escolhe o uso da codificação SOAP transmitida ao HTTP para a primeira "
+"liberação e outros transportes amigáveis para versões futuras."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/pt-BR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,1389 @@
+# translation of Stand-alone_Coordinator.po to Brazilian Portuguese
+# Language pt-BR translations for  package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-20 11:17+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:6
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Overview"
+msgstr "Visão Geral da Atividade Comercial-WS, Transação Atômica-WS e WS-C"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "Introdução"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:9
+#, no-c-format
+msgid ""
+"This section provides fundamental concepts associated with WS-C, WS-Atomic "
+"Transaction and WS-Business Activity. All of these concepts are defined in "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. WS-"
+"C, WS-Atomic Transaction and WS-Business Activity principles are discussed "
+"throughout this guide."
+msgstr ""
+"Esta seção fornece os conceitos fundamentais associados com a Atividade "
+"Comercial-WS e Transação Atômica- WS e WS-C. Todos estes conceitos estão "
+"definidos nas especificações da Atividade Comercial-WS e Transação Atômica- "
+"WS e WS-C. Os princípios da Atividade Comercial-WS e Transação Atômica- WS e "
+"WS-C serão discutidos neste guia."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:13
+#, no-c-format
+msgid ""
+"If you are well versed in the WS-C, WS-Atomic Transaction and WS-Business "
+"Activity specifications then you may want to just skim through this part of "
+"the manual."
+msgstr ""
+"Se você estiver bem experiente nas especificações de Atividade Comercial-WS "
+"e Transação Atômica- WS e WS-C, você precisará realizar apenas uma leitura "
+"rápida nesta parte do manual."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr "Coordenação WS"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:21
+#, no-c-format
+msgid ""
+"In general terms, coordination is the act of one entity (known as the "
+"coordinator) disseminating information to a number of participants for some "
+"domain-specific reason. This reason could be in order to reach consensus on "
+"a decision like in a distributed transaction protocol, or simply to "
+"guarantee that all participants obtain a specific message, as occurs in a "
+"reliable multicast environment. When parties are being coordinated, "
+"information known as the coordination context is propagated to tie together "
+"operations which are logically part of the same coordinated work or "
+"activity. This context information may flow with normal application "
+"messages, or may be an explicit part of a message exchange and is specific "
+"to the type of coordination being performed."
+msgstr ""
+"Em geral, a coordenação é o ato de uma entidade (conhecida como coordenador) "
+"de disseminar informação a um número de participantes para alguma razão "
+"específica de domínio. Esta razão pode estar em ordem para alcançar consenso "
+"na decisão como o protocolo de transação distribuída, ou simplesmente para "
+"garantir que todos os participantes obtenham uma mensagem específica, "
+"conforme ocorre num ambiente de transmissão múltipla confiável. Quando "
+"partes estiverem sendo coordenadas, a informação conhecida como o contexto "
+"de coordenação é propagado para amarrar as operações que são, logicamente, "
+"parte do mesmo trabalho ou atividade. Esta informação de contexto pode vazar "
+"com as mensagens de aplicativo normal ou ser uma parte explícita da troca de "
+"mensagem e é específica ao tipo de coordenação sendo executada."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:24
+#, no-c-format
+msgid ""
+"The fundamental idea underpinning WS-Coordination is that there is a generic "
+"need for a coordination infrastructure in a Web services environment. The WS-"
+"Coordination specification defines a framework that allows different "
+"coordination protocols to be plugged-in to coordinate work between clients, "
+"services and participants, as shown in Figure 4."
+msgstr ""
+"A idéia fundamental apoiando a Coordenação-WS é que existe uma necessidade "
+"genérica para a infra-estrutura da coordenação num ambiente de serviços da "
+"Web. A especificação da Coordenação-WS define um framework que permite "
+"diferentes protocolos de coordenação a serem conectados para coordenar "
+"trabalho entre clientes, serviços e participantes, conforme na Figura 4."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:27
+#, no-c-format
+msgid ""
+"At this level, an activity is minimally specified and is simply created, "
+"made to run, and then completed."
+msgstr ""
+"Nestas alturas, uma atividade é especifica de forma mínima e é simples "
+"criada, feita para rodar e então completada."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:34
+#, no-c-format
+msgid "WS-C architecture"
+msgstr "Arquitetura WS-C "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:36
+#, no-c-format
+msgid ""
+"Whatever coordination protocol is used, and in whatever domain it is "
+"deployed, the same generic requirements are present:"
+msgstr ""
+"Qualquer que seja o protocolo de coordenação utilizado e qualquer que seja o "
+"domínio que isto implementa, as mesmas solicitações genéricas estão "
+"presentes:"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:41
+#, no-c-format
+msgid ""
+"Instantiation (or activation) of a new coordinator for the specific "
+"coordination protocol, for a particular application instance;"
+msgstr ""
+"Instanciação (ou ativação) de um novo coordenador para o protocolo de "
+"coordenação específico, para uma instância de aplicativo particular;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:46
+#, no-c-format
+msgid ""
+"Registration of participants with the coordinator, such that they will "
+"receive that coordinator’s protocol messages during (some part of) the "
+"application’s lifetime;"
+msgstr ""
+"Registro de participantes com o coordenador, de forma que eles receberão as "
+"mensagens de protocolo do coordenador durante (alguma parte) do ciclo de "
+"vida do aplicativo;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:51
+#, no-c-format
+msgid ""
+"Propagation of contextual information between Web services that comprise the "
+"application;"
+msgstr ""
+"Informação contextual de propagação entre serviços da Web que englobam o "
+"aplicativo;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:56
+#, no-c-format
+msgid "An entity to drive the coordination protocol through to completion."
+msgstr ""
+"Uma entidade para dirigir o protocolo de coordenação através da finalização. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:61
+#, no-c-format
+msgid ""
+"The first three of these points are directly the concern of WS-Coordination "
+"while the fourth is the responsibility of a third-party entity, usually the "
+"client application that controls the application as a whole. These four WS-"
+"Coordination roles and their interrelationships are shown in Figure 5."
+msgstr ""
+"Os três primeiros pontos são diretamente a preocupação do Coordenador-Ws, "
+"enquanto que o quarto é a responsabilidade da entidade de terceira parte. "
+"Normalmente, o aplicativo do cliente que controla o aplicativo como um todo. "
+"Estas quatro funções de Coordenação- WS e suas inter-relações são "
+"apresentadas na Figura 5."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr "Infra-estrutura WS-C"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:71
+#, no-c-format
+msgid "Activation"
+msgstr "Ativação"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:72
+#, no-c-format
+msgid ""
+"The WS-Coordination framework exposes an Activation Service which supports "
+"the creation of coordinators for specific protocols and their associated "
+"contexts. The process of invoking an activation service is done "
+"asynchronously, and so the specification defines both the interface of the "
+"activation service itself, and that of the invoking service, so that the "
+"activation service can call back to deliver the results of the activation – "
+"namely a context that identifies the protocol type and coordinator location. "
+"These interfaces are presented in Figure 6, where the activation service has "
+"a one-way operation that expects to receive a "
+"<code>CreateCoordinationContext</code> message and correspondingly the "
+"service that sent the <code>CreateCoordinationContext</code> message expects "
+"to be called back with a <code>CreateCoordinationContextResponse</code> "
+"message, or informed of a problem via an <code>Error</code> message."
+msgstr ""
+"O framework de Coordenação WS expõem um Serviço de ativação que suporta a "
+"criação dos coordenadores para protocolos específicos e seus contextos "
+"associados. O processo de invocação de um serviço de ativação é feito "
+"assincronamente e então a especificação define ambas as interfaces do "
+"serviço de ativação por si próprio e do serviço de invocação, de forma que o "
+"serviço de ativação pode chamar novamente para entrega dos resultados de "
+"ativação - nomeadamente um contexto que identifica o tipo de protocolo e "
+"localidade do coordenador. Estas interfaces estão presentes na Figura 6, "
+"onde o serviço de ativação possui a operação da maneira que espera receber "
+"uma mensagem <code>CreateCoordinationContext</code> e corresponder o serviço "
+"que enviou a mensagem <code>CreateCoordinationContext</code>, espera ser "
+"chamada de volta com uma mensagem <code>CreateCoordinationContextResponse</"
+"code> ou informar a respeito do problema através da mensagem <code>Error</"
+"code>."
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:76
+#, no-c-format
+msgid ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+msgstr ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:78
+#, no-c-format
+msgid "Registration"
+msgstr "Registro"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:79
+#, no-c-format
+msgid ""
+"Once a coordinator has been instantiated and a corresponding context created "
+"by the activation service, a Registration Service is created and exposed. "
+"This service allows participants to register to receive protocol messages "
+"associated with a particular coordinator. Like the activation service, the "
+"registration service assumes asynchronous communication and so specifies "
+"WSDL for both registration service and registration requester, as shown "
+"below."
+msgstr ""
+"Uma vez que o coordenador tenha sido re-inicializado e o contexto "
+"correspondente criado pelo serviço de ativação, o Serviço de Registro é "
+"criado e exposto. Este serviço permite que os participantes registrem-se "
+"para receber mensagens de protocolo associado com um coordenador particular. "
+"Assim como o serviço de ativação, o serviço de registro assume a comunicação "
+"assíncrona e então especifica o WSDL para ambos serviço de registro e "
+"solicitador de registro, conforme apresentado abaixo."
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:83
+#, no-c-format
+msgid ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+msgstr ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:84
+#, no-c-format
+msgid ""
+"When a participant is registered with a coordinator through the registration "
+"service, it receives messages that the coordinator sends (for example, "
+"“prepare to complete” and “complete” messages if a two-phase protocol is "
+"used); where the coordinator’s protocol supports it, participants can also "
+"send messages back to the coordinator."
+msgstr ""
+"Quando um participante é registrado com um coordenador através do serviço de "
+"registro, ele recebe a mensagem que o coordenador envia (por exemplo: as "
+"mensagens “preparar para completar” e “completar”, caso o protocolo de suas "
+"fases seja utilizado). O protocolo do coordenador suporta isto e os "
+"participantes podem enviar mensagens de volta ao coordenador."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:88
+#, no-c-format
+msgid "Completion"
+msgstr "Finalização"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:89
+#, no-c-format
+msgid ""
+"The role of terminator is generally played by the client application, which "
+"at an appropriate point will ask the coordinator to perform its particular "
+"coordination function with any registered participants – to drive the "
+"protocol through to its completion. On completion, the client application "
+"may be informed of an outcome for the activity which may vary from simple "
+"succeeded/failed notification through to complex structured data detailing "
+"the activity’s status."
+msgstr ""
+"A função do finalizador é normalmente rodada pelo aplicativo do cliente, que "
+"em um determinado momento perguntará ao coordenador para executar a própria "
+"função de coordenação particular com quaisquer participantes registrados - "
+"para dirigir o protocolo através de sua finalização. Na finalização, o "
+"aplicativo do cliente poderá ser informado de um resultado para a atividade "
+"que pode variar de uma simples notificação de êxito/falha através dos dados "
+"estruturados complexos, detalhando o status da atividade."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:96
+#, no-c-format
+msgid "WS-Transaction"
+msgstr "Transação WS"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:97
+#, no-c-format
+msgid ""
+"In the past, making traditional transaction systems talk to one another was "
+"a holy grail that was rarely achieved. With the advent of Web services, "
+"there is an opportunity to leverage an unparalleled interoperability "
+"technology to splice together existing transaction processing systems that "
+"already form the backbone of enterprise level applications."
+msgstr ""
+"Anteriormente, fazer com que sistemas de transação tradicional comuniquem-se "
+"entre si era um tanto complicado que raramente era possível. Com a vinda dos "
+"serviços da Web, existe uma oportunidade para levantar uma tecnologia de "
+"interoperabilidade não-paralela para dividir junto sistemas de processamento "
+"de transações existentes que já fazem parte da infra-estrutura principal dos "
+"aplicativos de nível empresarial."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:101
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr "Fundamentos de Coordenação WS"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:102
+#, no-c-format
+msgid ""
+"An important aspect of WS-Transaction that differentiates it from "
+"traditional transaction protocols is that a synchronous request/response "
+"model is not assumed. This model derives from the fact that WS-Transaction "
+"is, as shown in the figure below, layered upon the WS-Coordination protocol "
+"whose own communication patterns are asynchronous by default."
+msgstr ""
+"Um aspecto importante da Transação que a diferencia dos protocolos de "
+"transação tradicional é que o modelo de solicitação/resposta assíncrona não "
+"é assumido. Este modelo deriva do fato em que a Transação WS é, conforme "
+"apresentado na figura abaixo, segmentada até o protocolo do Coordenador-WS "
+"que pertence aos padrões de comunicação que são assíncronos pelo padrão."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:110
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr "Atividade Comercial-WS e Transação Atômica-WS de Coordenação-WS"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:112
+#, no-c-format
+msgid ""
+"Web Services Coordination provides a generic framework for specific "
+"coordination protocols, like WS-Transaction, to be plugged in. Recall that "
+"WS-Coordination provides only context management – it allows contexts to be "
+"created and activities to be registered with those contexts. WS-Transaction "
+"leverages the context management framework provided by WS-Coordination in "
+"two ways. Firstly it extends the WS-Coordination context to create a "
+"transaction context. Secondly, it augments the activation and registration "
+"services with a number of additional services (Completion, "
+"CompletionWithAck, PhaseZero, 2PC, OutcomeNotification, BusinessAgreement, "
+"and BusinessAgreementWithComplete) and two protocol message sets (one for "
+"each of the transaction models supported in WS-Transaction) to build a fully-"
+"fledged transaction coordinator on top the WS-Coordination protocol "
+"infrastructure."
+msgstr ""
+"A Coordenação de Serviços da Web fornecem um framework genérico para "
+"protocolos de coordenação específico, como a Transação WS, a ser conectada. "
+"Lembre-se que a Coordenação fornece apenas um gerenciamento de contexto - "
+"isto permite que contextos sejam criados e atividades sejam registradas com "
+"estes contextos. A Transação WS eleva o framework de gerenciamento de "
+"contexto fornecido pela Coordenação-WS em duas maneiras. Primeiramente isto "
+"estende o contexto de Coordenação-WS para criar um contexto de transação. "
+"Depois, isto aumenta os serviços de ativação e registro com um número "
+"adicional de serviços (Completion, CompletionWithAck, PhaseZero, 2PC, "
+"OutcomeNotification, BusinessAgreement e BusinessAgreementWithComplete) e "
+"dois conjuntos de mensagem de protocolo (um para cada modelo de transação "
+"suportado na Transação-WS) para construir o coordenador de transação "
+"completa no topo da infra-estrutura de protocolo de Coordenação-WS."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:116
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr "Arquitetura de Transação-WS"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:117
+#, no-c-format
+msgid ""
+"WS-Transaction supports the notion of the service and participant as "
+"distinct roles, making the distinction between a transaction-aware service "
+"and the participants that act on behalf of the service during a transaction: "
+"transactional services deal with business-level protocols, while the "
+"participants handle the underlying WS-Transaction protocols, as shown above."
+msgstr ""
+"A Transação-WS suporta a noção do serviço e participante como funções "
+"distintas, realizando a distinção entre o serviço ciente de transação e os "
+"participantes que atuam no lugar do serviço durante a transação. Os serviços "
+"transacionais lidam com os protocolos de nível comercial, enquanto que os "
+"participantes manuseiam os protocolos de Transação-WS subjacente, conforme "
+"apresentado acima."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:125
+#, no-c-format
+msgid "WS-Transaction Global View"
+msgstr "Visão Global da Transação-WS"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:127
+#, no-c-format
+msgid ""
+"A transaction-aware service encapsulates the business logic or work that is "
+"required to be conducted within the scope of a transaction. This work cannot "
+"be confirmed by the application unless the transaction also commits and so "
+"control is ultimately removed from the application and placed into the "
+"transaction’s domain."
+msgstr ""
+"O serviço ciente da transação encapsula a lógica comercial ou trabalho que é "
+"solicitado a ser conduzido com o escopo de uma transação. Este trabalho não "
+"pode ser confirmado pelo aplicativo a não ser que a transação também "
+"confirme, e desta forma, o controle será completamente removido do "
+"aplicativo e colocado no domínio da transação."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:130
+#, no-c-format
+msgid ""
+"The participant is the entity that, under the dictates of the transaction "
+"coordinator, controls the outcome of the work performed by the transaction-"
+"aware Web service. In the figure above each service is shown with one "
+"associated participant that manages the transaction protocol messages on "
+"behalf of its service, while in the figure below, there is a close-up view "
+"of a single service, and a client application with their associated "
+"participants."
+msgstr ""
+"O participante é a entidade disto, sob a definição do coordenador da "
+"transação, controlando o resultado do trabalho executado pelo serviço da Web "
+"ciente da transação. Na figura acima, cada serviço é apresentado com um "
+"participante associado que gerencia as mensagens de protocolo de transação "
+"no lugar do próprio serviço, enquanto que a figura abaixo possui uma "
+"visualização de perto de um serviço único, além do aplicativo do cliente com "
+"seus participantes associados."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:137
+#, no-c-format
+msgid "Transactional Service and Participant"
+msgstr "Participante e Serviço Transacional"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:139
+#, no-c-format
+msgid ""
+"The transaction-aware Web service and its participant both serve a shared "
+"transactional resource, and there is a control relationship between them "
+"through some API - which on the Java platform is JAXTX. In the example shown "
+"in the figure above, it is assumed that the database is accessed through a "
+"transactional JDBC database driver, where SQL statements are sent to the "
+"database for processing via that driver, but where those statements will be "
+"tentative and only commit if the transaction does. In order to do this, the "
+"driver/database will associate a participant with the transaction which will "
+"inform the database of the transaction outcome. Since all transactional "
+"invocations on the Web service carry a transaction context, the participant "
+"working with the database is able to identify the work that the "
+"transactional service did within the scope of a specific transaction and "
+"either commit or rollback the work."
+msgstr ""
+"Ambos serviço da Web ciente da transação e seus participantes servem um "
+"recurso transacional compartilhado e existe uma relação de controle entre "
+"eles através de algum API, pelo qual a plataforma Java é JAXTX. No exemplo "
+"apresentado na figura acima, assume-se que o banco de dados é acessado "
+"através de um driver de banco de dados JDBC transacional, onde as expressões "
+"SQL são configuradas ao banco de dados pelo processamento através daquele "
+"driver, mas onde aquelas expressões serão temporárias e apenas confirmadas, "
+"caso a transação realize isto. Com o objetivo de realizar isto, o driver/"
+"banco de dados irá associar um participante com a transação que informará o "
+"banco de dados do resultado da transação. Uma vez que todas as invocações no "
+"serviço da Web carregam um contexto de transação, o participante trabalhando "
+"com o banco de dados está apto a identificar o trabalho que o serviço "
+"transacional realizou com o escopo de uma transação específica e tanto "
+"completar ou reverter o trabalho."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:142
+#, no-c-format
+msgid ""
+"At the client end, things are less complex. Through its API, the client "
+"application registers a participant with the transaction through which it "
+"controls transaction termination."
+msgstr ""
+"Já pelo lado do cliente, as coisas são menos complexas. O aplicativo do "
+"cliente registra um participante com a transação através do qual isto "
+"controla o término da transação."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:146
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr "Modelos de Transação-WS"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:147
+#, no-c-format
+msgid ""
+"Given that traditional transaction models are not appropriate for Web "
+"services, the following question must be posed, “what type of model or "
+"protocol is appropriate?” The answer to that question is that that no one "
+"specific protocol is likely to be sufficient, given the wide range of "
+"situations that Web service transactions are likely to be deployed within. "
+"Hence the WS-Transaction specification proposes two distinct models, where "
+"each supports the semantics of a particular kind of B2B interaction. The "
+"following sections shall discuss these two WS-Transaction models."
+msgstr ""
+"Uma vez que os modelos de transação tradicional não são apropriados para os "
+"Serviços da Web, a questão seguinte colocada em posição: “Qual o tipo de "
+"modelo ou protocolo é apropriado?” A resposta a esta questão é que nenhum "
+"protocolo específico é aparentemente suficiente, dada a larga abrangência "
+"das situações que as transações do serviço da Web são possivelmente "
+"implementadas. Então, a especificação da Transação-WS propõe dois modelos "
+"distintos, onde cada suporta a semântica de um tipo particular de interação "
+"B2B. As seções seguintes discutirão estes dois modelos de Transação-WS."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:152
+#, no-c-format
+msgid ""
+"As with WS-Coordination, the two WS-Transaction models are extensible "
+"allowing implementations to tailor the protocols as they see fit (for "
+"example, to suit their deployment environments)."
+msgstr ""
+"Assim como a Coordenação-WS, os dois modelos de Transação-WS estão "
+"permitindo extensivamente as implementações para juntar os protocolos de "
+"forma que eles vejam compatibilidade (por exemplo: para adaptar os ambientes "
+"de implementação dos mesmos)."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:157
+#, no-c-format
+msgid "Atomic Transactions (AT)"
+msgstr "Transações Atômicas (AT)"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:158
+#, no-c-format
+msgid ""
+"An atomic transaction or AT is similar to traditional ACID transactions and "
+"intended to support short-duration interactions where ACID semantics are "
+"appropriate. Within the scope of an AT, services typically enroll "
+"transaction-aware resources, such as databases and message queues, "
+"indirectly as participants under the control of the transaction. When the "
+"transaction terminates, the outcome decision of the AT is then propagated to "
+"each enlisted resource via the participant, and the appropriate commit or "
+"rollback actions are taken by each."
+msgstr ""
+"Uma Transação Atômica ou AT é similar às transações ACID tradicionais e "
+"tendem a suportar as interações de curta duração onde as semânticas ACID são "
+"apropriadas. Com o escopo de um AT, os serviços normalmente registram os "
+"recursos cientes da transação, tais como banco de dados e filas de mensagem, "
+"indiretamente como participantes sob o controle da transação. Quando uma "
+"transação é finalizada, a decisão de resultado do AT é então propagada para "
+"cada recurso listado através do participante e confirmação apropriada ou "
+"ações de reversão são tomadas por cada um."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:162
+#, no-c-format
+msgid ""
+"This protocol is very similar to those employed by traditional transaction "
+"systems that already form the backbone of an enterprise. It is assumed that "
+"all services (and associated participants) provide ACID semantics and that "
+"any use of atomic transactions occurs in environments and situations where "
+"this is appropriate: in a trusted domain, over short durations."
+msgstr ""
+"Este protocolo é bastante parecido a estes empregados pelos sistemas de "
+"transação tradicional que já formam a parte da infra-estrutura principal de "
+"uma empresa. Assume-se que todos os serviços (e participantes associados) "
+"forneçam semânticas e que qualquer uso de transações atômicas ocorra em "
+"ambientes e situações onde isto é apropriado: num domínio confiável, além de "
+"curtas durações."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:165
+#, no-c-format
+msgid ""
+"To begin an atomic transaction, the client application firstly locates a WS-"
+"Coordination coordinator Web service that supports WS-Transaction. Once "
+"located, the client sends a WS-Coordination CreateCoordinationContext "
+"message to the activation service specifying http://schemas.xmlsoap.org/"
+"ws/2004/10/wsat as its coordination type and will get back an appropriate WS-"
+"Transaction context from the activation service. The response to the "
+"CreateCoordinationContext message, the transaction context, has its "
+"CoordinationType element set to the WS-Atomic Transaction namespace, http://"
+"schemas.xmlsoap.org/ws/2004/10/wsat, and also contains a reference to the "
+"atomic transaction coordinator endpoint (the WS-Coordination registration "
+"service) where participants can be enlisted."
+msgstr ""
+"Para inicializar uma transação atômica, o aplicativo do cliente "
+"primeiramente localiza um serviço da Web do coordenador de Coordenação-WS "
+"que suporta a Transação-WS. Uma vez localizado, o cliente envia a mensagem "
+"do CreateCoordinationContext de Coordenação-WS para o serviço de ativação "
+"especificando o http://schemas.xmlsoap.org/ws/2004/10/wsat como o próprio "
+"tipo de coordenação e retornará um contexto de Transação-WS apropriado, a "
+"partir do serviço de ativação. A resposta a esta mensagem do "
+"CreateCoordinationContext, o contexto de transação, possui o próprio "
+"elemento de CoordinationType configurado para o espaço do nome de Transação "
+"Atômica-WS, http://schemas.xmlsoap.org/ws/2004/10/wsat. Além disso, contém "
+"uma referência ao ponto final do coordenador de transação atômica (o serviço "
+"de registro da Coordenação-WS) onde participantes podem ser listados. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:168
+#, no-c-format
+msgid ""
+"After obtaining a transaction context from the coordinator, the client "
+"application then proceeds to interact with Web services to accomplish its "
+"business-level work. With each invocation on a business Web service, the "
+"client inserts the transaction context into a SOAP header block, such that "
+"each invocation is implicitly scoped by the transaction – the toolkits that "
+"support WS-Atomic Transaction-aware Web services provide facilities to "
+"correlate contexts found in SOAP header blocks with back-end operations."
+msgstr ""
+"Após obter um contexto de transação do coordenador, o aplicativo do cliente "
+"então procede com o objetivo de interagir com os serviços da Web para "
+"completar o próprio trabalho de nível comercial. Com cada invocação num "
+"serviço da web comercial, o cliente insere o contexto de transação num "
+"bloqueio de cabeçalho SOAP, tal que cada invocação sofre a realização do "
+"escopo implicitamente pela transação. Os toolkits que suportam os serviços "
+"da Web cientes da Transação Atômica-WS fornecem facilidades aos contextos co-"
+"relacionados encontrados nos bloqueios do cabeçalho SOAP com as operações "
+"back-end."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:171
+#, no-c-format
+msgid ""
+"Once all the necessary application level work has been completed, the client "
+"can terminate the transaction, with the intent of making any changes to the "
+"service state permanent. To do this, the client application first registers "
+"its own participant for the Completion protocol. Once registered, the "
+"participant can instruct the coordinator either to try to commit or rollback "
+"the transaction. When the commit or rollback operation has completed, a "
+"status is returned to the participant to indicate the outcome of the "
+"transaction."
+msgstr ""
+"Uma vez que o trabalho do nível do aplicativo necessário tenha sido "
+"completado, o cliente pode terminar a transação com a intenção de realizar "
+"qualquer alteração ao estado de serviço permanente. Para isto, o aplicativo "
+"do cliente primeiro registra o próprio participante para o protocolo de "
+"finalização. Uma vez registrado, o participante pode instruir o coordenador "
+"tanto para tentar confirmar ou reverter a transação. Quando a operação de "
+"confirmação ou reversão for completada, o status é retornado ao participante "
+"para indicar o resultado da transação."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:174
+#, no-c-format
+msgid ""
+"While the completion protocol is straightforward, they hide the fact that in "
+"order to resolve to an outcome that several other protocols need to be "
+"executed."
+msgstr ""
+"Enquanto protocolo de finalização é direto, ele omite o fato que com o "
+"objetivo de resolver um resultado, outros demais protocolos precisam ser "
+"executados."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:177
+#, no-c-format
+msgid ""
+"The first of these protocols is the optional Volatile2PC. The Volatile2PC "
+"protocol is the WS-Atomic Transaction equivalent of the synchronization "
+"protocol we discussed earlier. It is typically executed where a Web service "
+"needs to flush volatile (cached) state, which may be being used to improve "
+"performance of an application, to a database prior to the transaction "
+"committing. Once flushed, the data will then be controlled by a two-phase "
+"aware participant."
+msgstr ""
+"O primeiro destes protocolos é o Volatile2PC opcional. O protocolo "
+"Volatile2PC é a Transação Atômica equivalente do protocolo de sincronização "
+"que discutimos antes. Ele é tipicamente executado onde o serviço da Web "
+"precisa esvaziar o estado (com cache) volátil, que pode ser utilizado para "
+"melhoramento do desempenho de um aplicativo, para um banco de dados prévio "
+"ao da confirmação da transação. Uma vez esvaziado, os dados serão então "
+"controlados pelo participante ciente de duas fases."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:180
+#, no-c-format
+msgid ""
+"All Volatile2PC participants are told that the transaction is about to "
+"complete (via the prepare message) and they can respond with either the "
+"prepared, aborted or readonly message; any failures at this stage will cause "
+"the transaction to rollback."
+msgstr ""
+"Todos os participantes Volatile2PC são informados que a transação está "
+"prestes a ser completada (através da mensagem de preparo) e eles podem "
+"responder tanto com a mensagem preparada, abortada ou de leitura apenas. "
+"Quaisquer falhas neste estágio farão com que a transação sofra a reversão."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:183
+#, no-c-format
+msgid ""
+"After Volatile2PC prepare, the next protocol to execute in WS-Atomic "
+"Transaction is Durable2PC. The Durable2PC (an abbreviation of the term two-"
+"phase commit) protocol is at the very heart of WS-Atomic Transaction and is "
+"used to bring about the necessary consensus between participants in a "
+"transaction such that the transaction can safely be terminated."
+msgstr ""
+"Após o preparo Volatile2PC, o próximo protocolo a executar a Transação "
+"Atômica-WS é o Durable2PC. O protocolo Durable2PC (uma abreviação do termo "
+"de confirmação de duas fases) está no coração da Transação Atômica-WS e é "
+"usado para trazer o consenso necessário entre os participantes numa "
+"transação, de forma que a mesma pode seguramente ser finalizada."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:186
+#, no-c-format
+msgid ""
+"The two-phase commit protocol is used to ensure atomicity between "
+"participants, and is based on the classic two-phase commit with presumed "
+"abort technique. During the first phase, when the coordinator sends the "
+"prepare message, a participant must make durable any state changes that "
+"occurred during the scope of the transaction, such that these changes can "
+"either be rolled back or committed later. That is, any original state must "
+"not be lost at this point as the atomic transaction could still roll back. "
+"If the participant cannot prepare then it must inform the coordinator (via "
+"the aborted message) and the transaction will ultimately roll back. If the "
+"participant is responsible for a service that did not do any work during the "
+"course of the transaction, or at least did not do any work that modified any "
+"state, it can return the readonly message and it will be omitted from the "
+"second phase of the commit protocol. Otherwise, the prepared message is sent "
+"by the participant."
+msgstr ""
+"O protocolo de confirmação de duas fases é usado para garantir a atomicidade "
+"entre participantes e é baseada na confirmação de duas fases clássica com a "
+"técnica de aborto presumida. Durante a primeira fase, quando o coordenador "
+"envia a mensagem de preparo, o participante deve fazer durável quaisquer "
+"alterações que ocorrem durante o escopo da transação, de forma que estas "
+"alterações podem tanto ser revertidas ou confirmadas mais tarde. Isto é, "
+"qualquer estado original não pode ser perdido nestas alturas uma vez que a "
+"transação atômica poderá continuar com a reversão. Caso o participante não "
+"possa preparar, então ele deverá informar ao coordenador (através da "
+"mensagem abortada) e a transação será revertida por completo. Caso o "
+"participante seja responsável pelo serviço que não realizou nenhum trabalho "
+"durante o curso da transação, ou pelo menos não realizou nenhum trabalho que "
+"modificou qualquer estado, ele poderá retornar a mensagem apenas pronta e "
+"isto será omitido a partir da segunda fase do protocolo de confirmação. Do "
+"contrário, a mensagem preparada é enviada pelo participante."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:189
+#, no-c-format
+msgid ""
+"Assuming no failures occurred during the first phase, in the second phase "
+"the coordinator sends the commit message to participants, who will make "
+"permanent the tentative work done by their associated services."
+msgstr ""
+"Assumindo que nenhuma falha ocorreu durante a primeira fase, na segunda fase "
+"o coordenador envia a mensagem de confirmação aos participantes, que farão "
+"permanente a tentativa de trabalho feita por seus serviços associados."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:192
+#, no-c-format
+msgid ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
+msgstr ""
+"Caso a transação envolva apenas um único participante, a Transação Atômica-"
+"WS suporta a otimização de confirmação de uma fase. Uma vez que há apenas um "
+"participante, suas decisões implícitas alcançam o consenso e, desta forma, o "
+"coordenador não precisa dirigir a transação através de ambas as fases. No "
+"caso de otimização, será dito ao participante para realizar a confirmação e "
+"o coordenador da transação não precisará gravar a informação sobre a "
+"decisão, uma vez que o resultado da transação é baixo para um participante "
+"único."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:195
+#, no-c-format
+msgid ""
+"The figure below<footnote> <para> Redrawn from the WS-Atomic Transaction "
+"specification. </para> </footnote> shows the state transitions of a WS-"
+"Atomic Transaction and the message exchanges between coordinator and "
+"participant; the coordinator generated messages are shown in the solid line, "
+"whereas the participant messages are shown by dashed lines."
+msgstr ""
+"A figura abaixo <footnote> <para> Retirada a partir da especificação da "
+"Transação Atômica </para> </footnote> apresenta o estado de transições da "
+"Transação Atômica WS e as alterações de mensagem entre o coordenador e o "
+"participante. O coordenador gera as mensagens que são apresentadas numa "
+"linha sólida, enquanto que as mensagens do participante são apresentadas por "
+"linhas tracejadas."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:206
+#, no-c-format
+msgid "Two-Phase Commit State Transitions"
+msgstr "Transações de Estado de Confirmação de Duas Fases"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:208
+#, no-c-format
+msgid ""
+"Once the 2PC protocol has finished, the Completion protocol that originally "
+"began the termination of the transaction can complete, and inform the client "
+"application whether the transaction was committed or rolled back. "
+"Additionally, the Volatile2PC protocol may complete."
+msgstr ""
+"Uma vez que o protocolo 2PC tenha finalizado, o protocolo de Finalização que "
+"originalmente inicializou o término da transação pode completar e informar "
+"ao aplicativo do cliente se é que ou não a transação foi confirmada ou "
+"revertida. Adicionalmente, o protocolo Volatile2PC poderá ser completado."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:211
+#, no-c-format
+msgid ""
+"Like the prepare phase of Volatile2PC, the final phase is optional and can "
+"be used to inform participants when the transaction has completed, typically "
+"so that they can release resources (for example, put a database connection "
+"back into the pool of connections)."
+msgstr ""
+"Assim como a fase de preparo do Volatile2PC, a fase final é opcional e pode "
+"ser usada para informar participantes quando a transação será completada, de "
+"maneira que eles podem liberar recursos (por exemplo: adicione a conexão de "
+"banco de dados de volta ao pool de conexões)."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:214
+#, no-c-format
+msgid ""
+"Any registered Volatile2PC participants are invoked after the transaction "
+"has terminated and are told the state in which the transaction completed "
+"(the coordinator sends either the Committed or Aborted message). Since the "
+"transaction has terminated, any failures of participants at this stage are "
+"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
+"the transaction."
+msgstr ""
+"Quaisquer participantes Volatile2PC registrados são invocados após a "
+"transação ter sido terminada e são informados que o estado em que a "
+"transação é completada (o coordenador envia tanto a Confirmação ou mensagem "
+"abortada). Uma vez que a transação tenha finalizado, quaisquer falhas dos "
+"participantes neste estado são ignoradas - isto é essencialmente uma "
+"cortesia e não possui influência no resultado da transação."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:217
+#, no-c-format
+msgid ""
+"Finally, after having gone through each of the stages in an AT, it is "
+"possible to see the intricate interweaving of individual protocols that goes "
+"to make up the AT as a whole in the following figure."
+msgstr ""
+"Finalmente, após ter passado por cada um dos estágios no AT, é possível ver "
+"a mistura intricante de protocolos individuais que completam o AT como um "
+"todo, na figura seguinte."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:224
+#, no-c-format
+msgid "The AT Model"
+msgstr "O Modelo AT"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:227
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr "Atividades Comerciais (BA)"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:228
+#, no-c-format
+msgid ""
+"Most business-to-business applications require transactional support in "
+"order to guarantee consistent outcome and correct execution. These "
+"applications often involve long running computations, loosely coupled "
+"systems and components that do not share data, location, or administration "
+"and it is difficult to incorporate atomic transactions within such "
+"architectures. For example, an online bookshop may reserve books for an "
+"individual for a specific period of time, but if the individual does not "
+"purchase the books within that period they will be “put back onto the shelf” "
+"for others to buy. Furthermore, because it is not possible for anyone to "
+"have an infinite supply of stock, some online shops may appear to users to "
+"reserve items for them, but in fact may allow others to pre-empt that "
+"reservation (for instance, the same book may be “reserved” for multiple "
+"users concurrently); a user may subsequently find that the item is no longer "
+"available, or may have to be reordered specially for them."
+msgstr ""
+"A maioria dos aplicativos comercial-para-comercial solicitam suporte "
+"transacional de maneira para garantir o resultado de consistência e execução "
+"correta. Estes aplicativos envolvem computação de longa rodagem na maioria "
+"das vezes, sistemas loosely coupled e componentes que não compartilham "
+"dados, localidade ou administração, além de ser difícil encorporar "
+"transações atômicas com tais arquiteturas. Por exemplo, uma livraria online "
+"pode reservar livros para um indivíduo por um período de tempo específico, "
+"mas se o indivíduo não comprar os livros num período determinado, eles serão "
+"“colocados na prateleira” para outras pessoas os comprarem. Além disto, uma "
+"vez que não é possível para qualquer um possuir um suprimento infinito de "
+"estoque, algumas lojas online podem aparecer para os usuários para reservar "
+"itens para os mesmos, mas na realidade podem permitir que outros pré-"
+"esvaziem aquela reserva (por exemplo: o mesmo livro pode ser “reservado” por "
+"atuais usuários múltiplos). Um usuário pode subseqüentemente encontrar que o "
+"item não está mais disponível ou especialmente ser reordenado para o mesmo. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:232
+#, no-c-format
+msgid ""
+"A business activity or BA is designed specifically for these kinds of long-"
+"duration interactions, where exclusively locking resources is impossible or "
+"impractical. In this model services are requested to do work, and where "
+"those services have the ability to undo any work, they inform the BA such "
+"that if the BA later decides the cancel the work (for instance if the "
+"business activity suffers a failure), it can instruct the service to execute "
+"its undo behavior. The key point for Business Activities is that how "
+"services do their work and provide compensation mechanisms is not the domain "
+"of the WS-Business Activity specification, but an implementation decision "
+"for the service provider."
+msgstr ""
+"Uma atividade comercial ou BA é designada especialmente para estes tipos de "
+"interações de longa duração, onde os recursos de bloqueamento exclusivos são "
+"impossíveis ou impraticável. Neste modelo, os serviços são solicitados para "
+"realizar trabalho e onde aqueles serviços possuem a habilidade para desfazer "
+"qualquer trabalho, eles informam ao BA de forma que se o BA decidir mais "
+"tarde cancelar o trabalho (por exemplo se a atividade comercial sofrer a "
+"falha), ele poderá instruir o serviço para executar o próprio comportamento "
+"de desfeito. A chave principal para as Atividades Comerciais é como os "
+"serviços realizam o próprio trabalho e fornecem mecanismos de compensação e "
+"não o domínio da especificação de Atividade Comercial, mas a decisão de "
+"implementação para o provedor do serviço."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:235
+#, no-c-format
+msgid ""
+"The WS- Business Activity simply defines a protocol for Web services-based "
+"applications to enable existing business processing and workflow systems to "
+"wrap their proprietary mechanisms and interoperate across implementations "
+"and business boundaries."
+msgstr ""
+"A Atividade Comercial-WS simplesmente define um protocolo para os "
+"aplicativos de serviços da Web baseados para ativar o processamento "
+"comercial existente e os sistemas de fluxo de trabalho a empacotar os "
+"mecanismos proprietários e interoperar através de implementações e limites "
+"comerciais."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:238
+#, no-c-format
+msgid ""
+"A business activity may be partitioned into scopes, where a scope is a "
+"business task or unit of work using a collection of Web services. Such "
+"scopes can be nested to arbitrary degrees, forming parent and child "
+"relationships, where a parent scope has the ability to select which child "
+"tasks are to be included in the overall outcome protocol for a specific "
+"business activity, and so clearly non-atomic outcomes are possible. In a "
+"similar manner to traditional nested transactions, if a child task "
+"experiences an error, it can be caught by the parent who may be able to "
+"compensate and continue processing."
+msgstr ""
+"A atividade comercial pode ser partida em escopos, onde um escopo é uma "
+"tarefa comercial ou unidade de trabalho usando uma coleção de serviços da "
+"Web. Tais escopos podem ser aninhados a graus arbitrários, formando relações "
+"parent e child, onde o escopo parent possui a habilidade para selecionar "
+"quais tarefas child serão incluídas no protocolo de resultado geral para uma "
+"atividade comercial específica, e resultados não-atômicos são possíveis. "
+"Numa maneira similar às transações aninhadas tradicionais, caso uma tarefa "
+"child experienciar um erro, isto pode ser capturado por um parent que está "
+"apto a compensar e continuar o processamento. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:241
+#, no-c-format
+msgid ""
+"When a child task completes it can either leave the business activity or "
+"signal to the parent that the work it has done can be compensated later. In "
+"the latter case, the compensation task may be called by the parent should it "
+"ultimately need to undo the work performed by the child."
+msgstr ""
+"Quando uma tarefa child é completada, ela pode tanto deixar a atividade "
+"comercial ou acenar ao parent em que o trabalho foi realizado possa ser "
+"compensado mais tarde. Em último caso, o trabalho de compensação pode ser "
+"chamado pelo parent caso este precise desfazer o trabalho executado pelo "
+"child."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:244
+#, no-c-format
+msgid ""
+"Unlike the WS-Atomic Transaction protocol model, where participants inform "
+"the coordinator of their state only when asked, a task within a business "
+"activity can specify its outcome to the parent directly without waiting for "
+"a request. This feature is useful when tasks fail such that the notification "
+"can be used by business activity exception handler to modify the goals and "
+"drive processing forward without having to meekly wait until the end of the "
+"transaction to admit to having failed – a well designed Business Activities "
+"should be proactive, if it is to perform well."
+msgstr ""
+"Diferente do modelo de protocolo da Transação Atômica-WS, onde participantes "
+"informam o coordenador do estado em que os mesmos apenas quando solicitado, "
+"uma tarefa com uma atividade comercial pode especificar seu resultado ao "
+"parent diretamente sem esperar pela solicitação. Este recurso é útil quando "
+"as tarefas falham de forma que a notificação pode ser usada pelo manuseador "
+"da exceção de atividade comercial para modificar os objetivos e drive "
+"processamento o envio sem ter que esperar obedientemente até o final da "
+"transação para admitir ter falhado. As Atividades Comerciais bem desenhadas "
+"devem ser pró-ativas, caso isto necessite de uma boa execução."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:247
+#, no-c-format
+msgid "Underpinning all of this are three fundamental assumptions:"
+msgstr "Existem três concepções fundamentais apoiando tudo isto:"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:252
+#, no-c-format
+msgid ""
+"All state transitions are reliably recorded, including application state and "
+"coordination metadata (the record of sent and received messages);"
+msgstr ""
+"Todas as transmissões de estado são gravadas de forma confiante, incluindo o "
+"estado do aplicativo e os meta-dados de coordenação ( a gravação de "
+"mensagens de envio e recebimento);"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:257
+#, no-c-format
+msgid ""
+"All request messages are acknowledged, so that problems are detected as "
+"early as possible. This avoids executing unnecessary tasks and can also "
+"detect a problem earlier when rectifying it is simpler and less expensive;"
+msgstr ""
+"Todas as mensagens de solicitação são reconhecidas, de forma que os "
+"problemas são detectados o mais cedo possível. Isto evita tarefas "
+"desnecessárias de execução e pode também detectar um problema mais rápido "
+"quando retificando que isto é mais simples e mais barato;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:262
+#, no-c-format
+msgid ""
+"As with atomic transactions, a response is defined as a separate operation "
+"and not as the output of the request. Message input-output implementations "
+"will typically have timeouts that are too short for some business activity "
+"responses. If the response is not received after a timeout, it is resent. "
+"This is repeated until a response is received. The request receiver discards "
+"all but one identical request received."
+msgstr ""
+"Assim como as transações atômicas, a resposta é definida como uma operação "
+"separada e não como um emissor de solicitação. As implementações de receptor-"
+"emissor de mensagem possuiram intervalos que são também pequenos para as "
+"respostas da atividade comercial. Caso a resposta não seja recebida após um "
+"intervalo, ela será re-enviada. Isto é repetido até que uma resposta seja "
+"recebida. O recipiente da solicitação descarta todas, mas uma solicitação "
+"idêntica é recebida. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:267
+#, no-c-format
+msgid ""
+"As with atomic transactions, the business activity model has multiple "
+"protocols: <code>BusinessAgreementWithParticipantCompletion</code> and "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. However, unlike the "
+"AT protocol which is driven from the coordinator down to participants, this "
+"protocol is driven much more from the participants upwards."
+msgstr ""
+"Assim como as transações atômicas, o modelo de atividade comercial possui "
+"múltiplos protocolos: <code>BusinessAgreementWithParticipantCompletion</"
+"code> e <code>BusinessAgreementWithCoordinatorCompletion</code>. No entanto, "
+"diferente do protocolo AT que é dirigido a partir de um coordenador abaixo "
+"para participantes, este protocolo é dirigido muito mais pelos participantes "
+"acima."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
+#, no-c-format
+msgid ""
+"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
+"a child activity is initially created in the Active state; if it finishes "
+"the work it was created to do and no more participation is required within "
+"the scope of the BA (such as when the activity operates on immutable data), "
+"then the child can unilaterally send an exited message to the parent. "
+"However, if the child task finishes and wishes to continue in the BA then it "
+"must be able to compensate for the work it has performed. In this case it "
+"sends a completed message to the parent and waits to receive the final "
+"outcome of the BA from the parent. This outcome will either be a close "
+"message, meaning the BA has completed successfully or a compensate message "
+"indicating that the parent activity requires that the child task reverse its "
+"work."
+msgstr ""
+"Sob o protocolo <code>BusinessAgreementWithParticipantCompletion</code>, a "
+"atividade child é inicialmente criada no estado Ativo. Caso isto finalize o "
+"trabalho que foi criado para realizar e nenhum outro solicitante é requerido "
+"no escopo do BA (tal como quando a atividade opera em dados imutáveis), o "
+"child poderá então enviar unilateralmente uma mensagem ao parent."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
+#, no-c-format
+msgid ""
+"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
+"identical to the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol with the exception that the child cannot autonomously decide to end "
+"its participation in the business activity, even if it can be compensated. "
+"Rather the child task relies upon the parent to inform it when the child has "
+"received all requests for it to perform work which the parent does by "
+"sending the complete message to the child. The child then acts as it does in "
+"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
+msgstr ""
+"O protocolo <code>BusinessAgreementWithCoordinatorCompletion</code> é "
+"idêntico ao protocolo <code>BusinessAgreementWithParticipantCompletion</"
+"code> com a exceção que o child não pode decidir idenpedentemente encerrar "
+"sua participação na atividade comercial, mesmo que isto possa ser "
+"compensado. Ao invés da tarefa child basear-se no parente para informá-lo "
+"quando o parente o child recebeu todas as solicitações para que isto execute "
+"o trabalho em que o parent realiza pelo enviou da mensagem completa ao "
+"child. O Child então atua como ele faz no protocolo "
+"<code>BusinessAgreementWithParticipantCompletion</code>."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:276
+#, no-c-format
+msgid ""
+"The crux of the BA model compared to the AT model is that is allows the "
+"participation of services that cannot or will not lock resources for "
+"extended periods."
+msgstr ""
+"A principal preocupação do modelo BA comparado ao modelo AT é que isto "
+"permite a participação de serviços, da qual não pode ou não bloqueará os "
+"recursos por períodos longos."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:279
+#, no-c-format
+msgid ""
+"While the full ACID semantics are not maintained by a BA, consistency can "
+"still be maintained through compensation, though the task of writing correct "
+"compensating actions (and thus overall system consistency) is delegated to "
+"the developers of the services under control of the BA. Such compensations "
+"may use backward error recovery, but will typically employ forward recovery."
+msgstr ""
+"Enquanto as semânticas ACID completas não são mantidas pelo BA, a "
+"consistência pode continuar sendo mantida através da compensação, uma vez "
+"que a tarefa de correta gravação de ações de compensação (e desta forma a "
+"consistência do sistema em geral) é delegada aos desenvolvedores de serviços "
+"sob controle do BA. Tais compensações podem usar a recuperação de erro "
+"anterior, mas irão empregar a recuperação à frente."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:283
+#, no-c-format
+msgid "Application Messages"
+msgstr "Mensagens de Aplicativo"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:284
+#, no-c-format
+msgid ""
+"Application messages are the requests and responses that are sent between "
+"parties that constitute the work of a business process. Any such messages "
+"are considered opaque by XTS, and there is no mandatory message format, "
+"protocol binding, or encoding style so the developer is free to use any "
+"appropriate Web services protocol. In XTS, the transaction context is "
+"propagated within the headers of SOAP messages."
+msgstr ""
+"As mensagens de aplicativos são solicitações e respostas que são enviadas "
+"entre as partes que constituem o trabalho de um processo comercial. "
+"Quaisquer mensagens são consideradas opacas pelo XTS e não há formato de "
+"mensagem mandatório, protocolo binding ou estilo de codificação de forma que "
+"o desenvolvedor está livre para a usar qualquer protocolo de serviços da Web "
+"apropriados. No XTS, o contexto de transação é propagado com os cabeçalhos "
+"das mensagens SOAP. "
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:289
+#, no-c-format
+msgid ""
+"XTS provides out-of-box support for service developers building WS-T-aware "
+"services on the JBoss, Weblogic and Glue platforms1. The provision of "
+"interceptors for automatic context handling at both client and service "
+"significantly simplifies the developer’s workload, allowing the developer to "
+"concentrate on writing the business logic without having to worry about the "
+"transactional infrastructure getting in the way. The interceptors simply add "
+"and remove context elements to application messages without altering the "
+"semantics of those messages. Any service which understands what to do with a "
+"WS-C context can use it, services which do not understand the context (those "
+"services that are not WS-C, WS-Atomic Transaction and WS-Business Activity-"
+"aware) may ignore the context; the important point here is that XTS manages "
+"contexts without user intervention."
+msgstr ""
+"O XTS fornece suporte fora da caixa para construção de desenvolvedores de "
+"serviço no JBoss, Weblogic e Glue plataforms1. O fornecimento de "
+"interceptores para o manuseamento do contexto automático em ambos cliente e "
+"serviço simplifica a carga de trabalho do desenvolvedor, permitindo o "
+"desenvolvedor concentrar-se na escrita da lógica comercial sem ter que "
+"preocupar-se com a infra-estrutura transacional no caminho. Os interceptores "
+"apenas adicionam e removem os elementos do contexto para as mensagens do "
+"aplicativo sem alterar as semânticas destas mensagens. Qualquer serviço que "
+"entende o que realizar com o contexto WS-C, pode utilizar isto. Os serviços "
+"que não entendem o contexto (aqueles serviços que não estão cientes da "
+"Atividade Comercial WS) podem ignorá-lo. Um ponto a ser destacado é que o "
+"XTS gerencia os contextos sem a intervenção do usuário. "
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:294
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr "Mensagens de Atividade Comercial-WS, Transação Atômica-WS e WS-C"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:295
+#, no-c-format
+msgid ""
+"Although the application or service developer rarely sees or is interested "
+"in the messages exchanged by the transactional infrastructure (the "
+"transaction manager and any participants), it is useful to understand what "
+"kinds of exchanges occur so that the underlying model can be fitted in to an "
+"overall architecture."
+msgstr ""
+"Mesmo que o desenvolvedor do serviço e aplicativo raramente vejam ou estejam "
+"interessados nas mensagens alteradas pela infra-estrutura (o gerenciador da "
+"transação e quaisquer participantes), é interessante entender os tipos de "
+"alterações que ocorrem, de forma que o modelo subjacente pode ser moldado "
+"numa arquitetura mais abrangente."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:299
+#, no-c-format
+msgid ""
+"In XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific "
+"messages are transported using SOAP messaging over HTTP. The types of "
+"messages that are propagated include instructions to perform standard "
+"transaction operations like begin, prepare."
+msgstr ""
+"Na Transação Atômica WS, WS-C e XTS e específica Atividade Comercial-WS, as "
+"mensagens são transportadas usando o mensageiro SOAP sobre o HTTP. Os tipos "
+"de mensagens que são propagados inclui instruções para executar as operações "
+"de transação padrão como inicializar e preparar."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:303
+#, no-c-format
+msgid ""
+"XTS messages do not interfere in any way, shape, or form, with the "
+"application messages, and nor is there any requirement for an application to "
+"use the same transport as the transaction-specific messages. For example, it "
+"is quite reasonable for a client application to deliver its application-"
+"specific messages using SOAP RPC over SMTP even though under the covers the "
+"XTS messages are delivered using a different mechanism."
+msgstr ""
+"As mensagens XTS não interferem em nenhuma maneira, figura ou forma com as "
+"mensagens do aplicativo e não há qualquer solicitação para um aplicativo "
+"usar o mesmo transporte como o das mensagens especificadas na transação. Por "
+"exemplo: é bastante razoável para um aplicativo do cliente entregar as "
+"próprias mensagens específicas do aplicativo usando o SOAP RPC sobre o SMTP, "
+"mesmo sob as coberturas de mensagens XTS são entregues usando um mecanismo "
+"diferente."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:310
+#, no-c-format
+msgid "Summary"
+msgstr "Sumário"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:311
+#, no-c-format
+msgid ""
+"XTS provides a coordination infrastructure designed to allow transactions to "
+"run between enterprises across the Internet. That infrastructure is based on "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. It "
+"supports two kinds of transactions: atomic transactions and business "
+"activities, which can be combined in arbitrary ways to map elegantly onto "
+"the transactional requirements of the underlying problem. The use of the "
+"whole infrastructure is simple due to the fact that its functionality is "
+"exposed through a simple transactioning API. Furthermore XTS provides all of "
+"the necessary plumbing to keep application and transactional aspects of an "
+"application separate, and to ensure that the transactionality of a system "
+"does not interfere with the functional aspects of the system itself."
+msgstr ""
+"O XTS fornece uma infra-estrutura designada a permitir que transações rodem "
+"entre empresas através da Internet. Estas infra-estruturas são baseadas nas "
+"especificações da Transação Atômica-WS, WS-C e Atividade Comercial-WS. Isto "
+"suporta dois tipos de transações: atividades comerciais e transações "
+"atômicas, que podem ser combinadas em maneiras arbitrárias para mapear "
+"elegantemente nas solicitações transacionais do problema subjacente. O uso "
+"da infra-estrutura por completo é simples, devido ao fato que sua "
+"funcionalidade é exposta através de um API transacional simples. Além disso, "
+"o XTS fornece toda profundidade necessária para manter o aplicativo e os "
+"aspectos transacionais de um aplicativo separado e garantir que a "
+"transacionalidade de um sistema não interfera com os aspectos funcionais do "
+"sistema por si só."

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Author_Group.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Author_Group.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Author_Group.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Book_Info.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Book_Info.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Book_Info.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,48 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide CP04"
+msgstr "JBoss Transactions Web 服务程序员指南"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "用于 JBoss 企业级应用程序平台 4.3"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr "本书介绍了 Transaction Web 服务的编程"
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr "Logo"
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Getting_Started.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Getting_Started.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Getting_Started.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,233 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Getting_Started.xml:6
+#, no-c-format
+msgid "Getting Started"
+msgstr "起步"
+
+#. Tag: title
+#: Getting_Started.xml:8
+#, no-c-format
+msgid "Creating and deploying participants"
+msgstr "创建和部署参与者"
+
+#. Tag: para
+#: Getting_Started.xml:9
+#, no-c-format
+msgid ""
+"A participant is a software entity which is driven by the transaction "
+"manager on behalf of a Web service. The creation of participants is non-"
+"trivial since they ultimately reflect the state of a Web service’s back-end "
+"processing facilities which is a function of an enterprise’s own IT "
+"infrastructure. The most that can be said about the implementation of a "
+"participant without getting into detail about the back-end systems it "
+"represents, or the details of the underlying transaction protocol is that "
+"implementations must implement one of the following interfaces, depending "
+"upon the protocol it will participate within: <code>com.arjuna.wst."
+"Durable2PCParticipant</code>, <code>com.arjuna.wst.Volatile2PCParticipant</"
+"code>, or, <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>, <code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>."
+msgstr ""
+"参与者（participant）是一个事务管理者替 Web 服务驱动的软件实体。参与者的创建"
+"很重要，因为它们最终反映了作为企业自身的 IT 基础结构功能的 Web 服务的后台处理"
+"机制的状态。参与者的实现无需了解参与者代表的后台系统或底层事务协议的细节，它"
+"最重要的是根据它参与的协议实现下面的接口之一：<code>com.arjuna.wst."
+"Durable2PCParticipant</code>、<code>com.arjuna.wst.Volatile2PCParticipant</"
+"code> 或 <code>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</code>、<code>com."
+"arjuna.wst.BusinessAgreementWithCoordinatorCompletionParticipant</code>。"
+
+#. Tag: title
+#: Getting_Started.xml:15
+#, no-c-format
+msgid "Creating Client Applications"
+msgstr "创建客户端程序"
+
+#. Tag: para
+#: Getting_Started.xml:16
+#, no-c-format
+msgid ""
+"There are two aspects to a client application using XTS. The first is the "
+"transaction declaration aspects and the second is the business logic that "
+"the client application performs. The transaction declaration aspects are "
+"taken care of automatically with XTS’s client API. This API provides simple "
+"transaction directives like begin, commit, and rollback which the client "
+"application can use to initialize, manage, and terminate transactions. Under "
+"the covers, this API invokes (via SOAP) operations on the transaction "
+"manager."
+msgstr ""
+"使用 XTS 的客户端程序有两个方面。第一个是事务声明，第二个是客户端执行的商业逻"
+"辑。XTS 的客户端 API 将自动处理事务声明方面。这个 API 提供客户端可用于初始"
+"化、管理和终止事务的简单事务指令如 begin、commit 和 rollback。从底层来讲，"
+"API 调用了（通过 SOAP）事务管理者上的操作。"
+
+#. Tag: para
+#: Getting_Started.xml:19
+#, no-c-format
+msgid ""
+"When the client application performs invocations on business logic Web "
+"services, then XTS does not dictate an API for that purpose. However, there "
+"is a requirement that whatever API is chosen, the XTS context be inserted "
+"onto outgoing messages, and extracted and associated with the current thread "
+"for incoming messages. To make the user’s life easier, the XTS software "
+"comes complete with three sets of “filters” which can perform the task "
+"automatically. These filters are designed to work with JAX-RPC and "
+"webMethods client libraries."
+msgstr ""
+"当客户端程序对商业逻辑执行调用时，XTS 不会为此指定 API。然而，每当 API 被选择"
+"时，XTS 上下文都被要求插入到转出的消息里，抽取并和转入消息的当前线程相关联。"
+"为了方便用户，XTS 软件带有三套完整的“过滤器”来自动执行任务。这些过滤器是为了"
+"和 JAX-RPC 以及 webMethods 客户端库一起使用的。"
+
+#. Tag: para
+#: Getting_Started.xml:23
+#, no-c-format
+msgid ""
+"If the user chooses to use a different SOAP client infrastructure, then the "
+"onus to perform client-side header processing rests with them. XTS does not "
+"provide client-side infrastructure for anything other than JAX-RPC or "
+"webMethods for this release."
+msgstr ""
+"如果用户选择不同的 SOAP 客户端架构，那它得负担执行客户端头部信息处理的负荷。"
+"本版本的 XTS 不提供除了 JAX-RPC 或 webMethods 之外的任何客户端架构。"
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr "JAX-RPC 上下文处理程序"
+
+#. Tag: para
+#: Getting_Started.xml:29
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC server-side context handler with the "
+"deployed web services, a handler chain must be included in the web services "
+"deployment descriptor. Please refer to the demo application <filename>jboss/"
+"webservices.xml</filename> deployment descriptor for an example of how this "
+"can be achieved."
+msgstr ""
+"为了向 Web 服务注册 JAX-RPC 上下文处理程序，Web 服务的部署描述符必须包含处理"
+"程序链。请参考示例程序的 <filename>jboss/webservices.xml</filename>。"
+
+#. Tag: para
+#: Getting_Started.xml:33
+#, no-c-format
+msgid ""
+"In order to register the JAX-RPC client-side context handler used by the "
+"client applications, a handler chain must be included in the definition of "
+"the service-ref in the client web.xml deployment descriptor. Please refer to "
+"the demo application <filename>jboss/client-web-app.xml</filename> for an "
+"example of how this can be achieved."
+msgstr ""
+"为了注册客户端程序使用的 JAX-RPC 客户端上下文处理程序，客户端的 web.xml 描述"
+"符里的 service-ref 必须包含一个处理程序链。请参考示例程序的 <filename>jboss/"
+"client-web-app.xml</filename>。"
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr "webMethods 上下文处理程序"
+
+#. Tag: para
+#: Getting_Started.xml:38
+#, no-c-format
+msgid ""
+"In order to register the webMethods server-side context handler with the "
+"deployed web services, the inbound and outbound interceptors must be "
+"configured in the web services deployment descriptor. An example of how this "
+"can be configured can be found in the demo application, for example, the "
+"<filename>RestaurantServiceAT.xml</filename>."
+msgstr ""
+"为了在已部署的 Web 服务里注册 webMethods 服务器端上下文处理程序，你必须在部署"
+"描述符里配置 inbound 和 outbound 拦截器。在演示程序里你可以找到一个配置的例"
+"子，如 <filename>RestaurantServiceAT.xml</filename>。"
+
+#. Tag: para
+#: Getting_Started.xml:42
+#, no-c-format
+msgid ""
+"In order to register the webMethods client-side context handler, the inbound "
+"and outbound interceptors must be configured in the <filename>glue-config."
+"xml</filename> deployment descriptor. Please refer to the soap interceptor "
+"section of the demo application glue-config.xml for an example of how this "
+"can be achieved."
+msgstr ""
+"为了在已部署的 Web 服务里注册 webMethods 客户端上下文处理程序，你必须在 "
+"<filename>glue-config.xml</filename> 部署描述符里配置 inbound 和 outbound 拦"
+"截器。关于如何实现这些，请参考演示程序的 glue-config.xml 里的 SOAP 拦截器部"
+"分。"
+
+#. Tag: title
+#: Getting_Started.xml:48
+#, no-c-format
+msgid "Hints and tips"
+msgstr "提示"
+
+#. Tag: para
+#: Getting_Started.xml:49
+#, no-c-format
+msgid ""
+"If you want to create multiple JBoss deploys on the same machine, then you "
+"may wish to look at <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/"
+"MultipleInstances.htm\"><emphasis>Setting up multiple instances</emphasis></"
+"ulink> for information on what is required."
+msgstr ""
+"如果你想在相同的机器上创建多个 JBoss 部署，你可能需要看看 <ulink url="
+"\"http://www.yorku.ca/dkha/jboss/docs/MultipleInstances.htm\"><emphasis>设立"
+"多个实例</emphasis></ulink> 上的相关要求。"
+
+#. Tag: title
+#: Getting_Started.xml:55
+#, no-c-format
+msgid "Summary"
+msgstr "总结"
+
+#. Tag: para
+#: Getting_Started.xml:56
+#, no-c-format
+msgid ""
+"This chapter has provided a high-level overview of how to use each of the "
+"major software pieces of the Web Services transactions component of JBossTS. "
+"The Web Services transaction manager provided by JBossTS is the hub of the "
+"architecture and is the only piece of software that users’ software does not "
+"bind to directly. XTS provides header processing infrastructure for dealing "
+"with Web Services transactions contexts for both users’ client applications "
+"and Web services. For developing transaction participants, XTS provides a "
+"simple interface plus the necessary document handling code."
+msgstr ""
+"本章高度概括了如何使用 JBossTS 的 Web 服务事务组件的每个主要软件。JBossTS 提"
+"供的 Web 服务事务管理者是其基础机构的核心，也是用户软件唯一无需直接绑定的软"
+"件。XTS 提供处理用于用户程序和 web 服务的事务上下文的头部信息处理基础结构。为"
+"了开发事务参与者，XTS 提供了一个简单的接口以及必需的文档处理代码。"
+
+#. Tag: para
+#: Getting_Started.xml:59
+#, no-c-format
+msgid ""
+"This chapter is meant as an overview only, and is unlikely to answer "
+"questions on more difficult and subtle aspects. For fuller explanations of "
+"the components, please refer to the appropriate chapter elsewhere in this "
+"document."
+msgstr ""
+"本章只是作为一个概述，它不可能回答更加复杂和详细的问题。关于组件的更为完整的"
+"解释，请参考本文档的相关章节。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Introduction.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Introduction.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Introduction.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,343 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr "介绍"
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr "JBossTS Web 服务的事务概述"
+
+#. Tag: para
+#: Introduction.xml:9
+#, no-c-format
+msgid ""
+"The XML transaction service component of JBossTS (shorthand referred to as "
+"XTS) supports the coordination of private and public Web services in a "
+"business transaction. Therefore, to understand XTS, you must be familiar "
+"with Web services, and also understand a little about transactions. This "
+"chapter introduces XTS and provides a brief overview of the technologies "
+"that form the Web services standard. Additionally, this chapter explores "
+"some of the fundamentals of transactioning technology and how it can be "
+"applied to Web services. Much of the content presented in this chapter is "
+"detailed throughout this guide; however, only overview information about Web "
+"services is provided. If you are new to creating Web services, please see "
+"consult your Web services platform documentation."
+msgstr ""
+"JBossTS 的 XML 事务服务组件（简称为 XTS）支持在商业事务里协调 private 和 "
+"public 的 Web 服务。因此，为了理解 XTS，你必须熟悉 Web 服务、也必须了解事务方"
+"面的一些知识。本章介绍了 XTS 并提供组成 Web 服务标准的技术概述。此外，本章探"
+"讨了事务技术的一些基本知识以及如何把它应用到 Web 服务中去。本章里出现的许多内"
+"容都将在本指南里详细讨论；然而，关于 Web 服务则只进行了概述。如果你是创建 "
+"Web 服务的新手，请参考相关 Web 服务平台的文档。"
+
+#. Tag: para
+#: Introduction.xml:12
+#, no-c-format
+msgid ""
+"JBossTS provides as the XTS component a transaction solution for Web "
+"services. Using XTS, business partners can coordinate complex business "
+"transactions in a controlled and reliable manner. The JBossTS Web Services "
+"API supports a transactional coordination model based on the WS-C, WS-Atomic "
+"Transaction and WS-Business Activity specifications. WS-C is a generic "
+"coordination framework developed by IBM, Microsoft and BEA, WS-Atomic "
+"Transaction and WS-Business Activity are transaction protocols that utilize "
+"this framework."
+msgstr ""
+"JBossTS 以 XTS 组件的形式为 Web 服务提供了事务解决方案。商业伙伴可以用 XTS 以"
+"可控和可靠的方式协调复杂的商业事务。JBossTS 的 Web 服务 API 支持基于 WS-C、"
+"WS-Atomic Transaction 和 WS-Business Activity 事务性的协调模型。WS-C 是 IBM、"
+"Microsoft 和 BEA 开发的一个通用协调框架，WS-Atomic Transaction 和 WS-"
+"Business Activity 则是利用该框架的事务协议。"
+
+#. Tag: para
+#: Introduction.xml:15
+#, no-c-format
+msgid ""
+"Web services are modular, reusable software components that are created by "
+"exposing business functionality through a Web service interface. Web "
+"services communicate directly with other Web services using standards-based "
+"technologies such as SOAP and HTTP. These standards-based communication "
+"technologies allow Web services to be accessed by customers, suppliers, and "
+"trading partners, independent of hardware operation system or programming "
+"environment. The result is a vastly improved collaboration environment as "
+"compared to today&#39;s EDI and business-to-business (B2B) solutions—an "
+"environment where businesses can expose their current and future business "
+"applications as Web services that can be easily discovered and accessed by "
+"external partners."
+msgstr ""
+"Web 服务是通过使用 Web 服务接口开放商业功能而创建的模块化的、可重用的软件组"
+"件。Web 服务用标准化的技术如 SOAP 和 HTTP 直接和其他 Web 服务通信。这些标准化"
+"的通信技术允许客户、供应商、交易伙伴独立于硬件操作系统或程序环境访问 Web 服"
+"务。其结果是一个和目前的 EDI 和 business-to-business (B2B) 解决方案相比，大大"
+"提高的合作环境 - 企业可以以 Web 服务的形式开放当前和将来的商业程序，而外部的"
+"伙伴可以轻易地发现和进行访问。"
+
+#. Tag: para
+#: Introduction.xml:18
+#, no-c-format
+msgid ""
+"Web services, by themselves, are not fault tolerant. In fact, some of the "
+"reasons that make it an attractive development solution are also the same "
+"reasons that service-based applications may have drawbacks:"
+msgstr ""
+"Web 服务本身是不能容错的。事实上，它成为一个吸引人的开发解决方案的原因，也导"
+"致它可能具有基于服务的应用程序的缺点："
+
+#. Tag: para
+#: Introduction.xml:23
+#, no-c-format
+msgid ""
+"Application components that are exposed as Web services may be owned by "
+"third parties, which provides benefits in terms of cost of maintenance, but "
+"drawbacks in terms of having exclusive control over their behavior;"
+msgstr ""
+"作为 Web 服务开放的应用程序组件可能由第三方所有，它对于维护成本来说是有益处"
+"的，但也有对其行为不能进行独占控制的缺点："
+
+#. Tag: para
+#: Introduction.xml:28
+#, no-c-format
+msgid ""
+"Web services are usually remotely located which increases risk of failure "
+"due to increased network travel for invocations."
+msgstr "Web 通常位于远程主机，由于网络通信的增加，导致了发生故障的风险增大。"
+
+#. Tag: para
+#: Introduction.xml:33
+#, no-c-format
+msgid ""
+"Applications that have high dependability requirements, must find a method "
+"of minimizing the effects of errors that may occur when an application "
+"consumes Web services. One method of safeguarding against such failures is "
+"to interact with an application’s Web services within the context of a "
+"transaction. A transaction is simply a unit of work which is completed "
+"entirely, or in the case of failures is reversed to some agreed consistent "
+"state – normally to appear as if the work had never occurred in the first "
+"place. With XTS, transactions can span multiple Web services which mean that "
+"work performed across multiple enterprises can be managed with transactional "
+"support."
+msgstr ""
+"具有高可靠性要求的应用程序必须找到一个可最小化在消费 Web 服务时发生错误的方"
+"法。应付这种故障发生的一个办法是在事务的上下文里和应用程序的 Web 服务进行交"
+"互。事务是完全完成的一组动作或在发生故障时返回到某个协议好的一致的状态 - 就好"
+"像这些工作起初就没发生过一样。使用 XTS，事务可以跨越多个 Web 服务，这意味着可"
+"以用事务来管理在多个企业里执行的工作。"
+
+#. Tag: title
+#: Introduction.xml:37
+#, no-c-format
+msgid "Managing Service-Based Processes"
+msgstr "管理基于服务的进程"
+
+#. Tag: para
+#: Introduction.xml:38
+#, no-c-format
+msgid ""
+"XTS allows you to create transactions that drive complex business processes "
+"spanning multiple Web services. Current Web services standards do not "
+"address the requirements for a high-level coordination of services since in "
+"today’s Web services applications, which use single request/receive "
+"interactions, coordination is typically not a problem. However, for "
+"applications that engage multiple services among multiple business partners, "
+"coordinating and controlling the resulting interactions is essential. This "
+"becomes even more apparent when you realize that you generally have little "
+"in the way of formal guarantees when interacting with third-party Web "
+"services."
+msgstr ""
+"XTS 允许你创建驱动跨多个 Web 服务的复杂商业过程的事务。目前的 Web 服务标准没"
+"有解决对高层次协调服务的要求，因为现在的 Web 服务程序里都使用单一的请求/接收"
+"交互，协调通常还不是一个问题。然而，对于涉及多个商业伙伴的多个服务的应用程"
+"序，协调和控制交互结果是基本的。当和第三方 Web 服务交互而更难于进行控制时，这"
+"个问题就更明显了。"
+
+#. Tag: para
+#: Introduction.xml:42
+#, no-c-format
+msgid ""
+"XTS provides the infrastructure for coordinating services during a business "
+"process. By organizing processes as transactions, business partners can "
+"collaborate on complex business interactions in a reliable manner, insuring "
+"the integrity of their data - usually represented by multiple changes to a "
+"database – but without the usual overheads and drawbacks of directly "
+"exposing traditional transaction-processing engines directly onto the web. "
+"The following example demonstrates how an application may manage service-"
+"based processes as transactions:"
+msgstr ""
+"XTS 提供在商业过程中协调服务的基础结构。通过把过程组织成事务，商业伙伴可以可"
+"靠的方式在复杂的商业交互时进行合作，确保数据的集成性 - 通常在对数据库进行多路"
+"修改时体现 - 但不会有直接对 web 开放传统的事务处理引擎通常所具有的开销和缺"
+"点。下面的例子演示了应用程序是如何以事务的方式管理基于服务的过程的："
+
+#. Tag: para
+#: Introduction.xml:45
+#, no-c-format
+msgid ""
+"The application in question allows a user to plan a social evening. This "
+"application is responsible for reserving a table at a restaurant, and "
+"reserving tickets to a show. Both activities are paid for using a credit "
+"card. In this example, each service represents exposed Web services provided "
+"by different service providers. XTS is used to envelop the interactions "
+"between the theater and restaurant services into a single (potentially) long-"
+"running business transaction. The business transaction must insure that "
+"seats are reserved both at the restaurant and the theater. If one event "
+"fails the user has the ability to decline both events, thus returning both "
+"services back to their original state. If both events are successful, the "
+"user’s credit card is charged and both seats are booked. As you may expect, "
+"the interaction between the services must be controlled in a reliable manner "
+"over a period of time. In addition, management must span several third-party "
+"services that are remotely deployed."
+msgstr ""
+"该应用程序允许用户计划一个社交晚会。它负责在饭店里预订座位以及观赏演出的票。"
+"这两个活动都通过信用卡进行付款。在这个例子里，每个服务都代表不同服务提供者所"
+"提供的 Web 服务。XTS 被用来把戏院和饭店服务之间的交互封装到单个（可能的话）的"
+"长期运行的商业事务里。这个商业事务必须确保预订好戏院和饭店的座位。如果其中一"
+"个事件失败的话，用户应能将两者都取消，并把这两个服务都返回至初始状态。如果两"
+"个事件都成功了，用户的信用卡将被划款且预订好了两个座位。如你所希望的，在一段"
+"时间内，这些服务间的交互必须以可靠的方式进行控制。此外，该应用程序应该能够管"
+"理在远程部署的多个第三方服务。"
+
+#. Tag: para
+#: Introduction.xml:49
+#, no-c-format
+msgid ""
+"Without the backing of a transaction, an undesirable outcome may occur. For "
+"example, the user credit card may be charged, even though one or both of the "
+"bookings may have failed."
+msgstr ""
+"没有事务的支持，意外的结果就可能发生。例如，即使其中一个预订失败了，用户的信"
+"用卡也可能被划款。"
+
+#. Tag: para
+#: Introduction.xml:53
+#, no-c-format
+msgid ""
+"This simple example describes the situations where XTS excels at supporting "
+"business processes across multiple enterprises. This example is further "
+"refined throughout this guide, and appears as a standard demonstrator "
+"(including source code) with the XTS distribution."
+msgstr ""
+"这个简单的例子描述了 XTS 善于支持跨多个企业的商业过程的情景。本指南将进一步精"
+"炼这个例子，它可以作为一个带有 XTS 的标准演示程序（包括源码）。"
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr "Servlets"
+
+#. Tag: para
+#: Introduction.xml:58
+#, no-c-format
+msgid ""
+"The WS-C, WS-Atomic Transaction and WS-Business Activity protocols are based "
+"on one-way interactions of entities rather than traditional synchronous "
+"request/response RPC style interactions. Entities (for example, transaction "
+"participants) invoke operations on other entities (for example, the "
+"transaction coordinator) in order to return responses to requests. What this "
+"means is that the programming model is based on peer-to-peer relationships, "
+"with the result that all services, whether they are participants, "
+"coordinators or clients, must have an active component that allows them to "
+"receive unsolicited messages."
+msgstr ""
+"WS-C、WS-Atomic Transaction 和 WS-Business Activity 协议基于单向的实体交互而"
+"不是传统的同步请求/响应 RPC 风格的交互。实体（如事务参与者）调用其他实体的操"
+"作（例如事务协调者）来向请求返回响应。这意味着编程模式基于点对点的关系，所有"
+"的服务，不管是参与者、协调者还是客户，都必须有一个活动的组件来接收任意的消"
+"息。"
+
+#. Tag: para
+#: Introduction.xml:62
+#, no-c-format
+msgid ""
+"In the current implementation of XTS, the active component is achieved "
+"through the use of Java servlet technology. Each endpoint that can be "
+"communicated with via SOAP/XML is represented as a servlet (and published "
+"within JNDI). Fortunately for the developer, this use of servlets occurs "
+"transparently. The only drawback is that (currently) clients must reside "
+"within a domain capable of hosting servlets, i.e., an application server. It "
+"is our intention that future versions of XTS will provide configurable "
+"deployment options, allowing servlets where required, but not mandating them."
+msgstr ""
+"在当前的 XTS 实现里，这个活动组件是通过 Java servlet 技术实现的。每个通过 "
+"SOAP/XML 通信的终端都由一个 servlet 代表（并用 JNDI 发布）。幸运的是，对于开"
+"发人员来说，这种 servlet 的用法是透明的。唯一的缺点是客户端必须驻留在可以容"
+"纳 servlet 的域里，例如应用服务器。XTS 的将来版本将提供可配置的部署选项，在需"
+"要时可允许 servlet 但不作要求。"
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr "SOAP"
+
+#. Tag: para
+#: Introduction.xml:67
+#, no-c-format
+msgid ""
+"SOAP has emerged as the de-facto message format for XML-based communication "
+"in the Web services arena. It is a lightweight protocol that allows the user "
+"to define the content of a message and to provide hints as to how recipients "
+"should process that message."
+msgstr ""
+"SOAP 已经成为在 Web 服务领域里的基于 XML 的通信的事实上的消息格式。它是一个轻"
+"量级的协议，允许用户定义消息的内容并提供关于接收者如何处理该消息的提示。"
+
+#. Tag: para
+#: Introduction.xml:71
+#, no-c-format
+msgid ""
+"SOAP messages can be divided into two main categories: Remote Procedure Call "
+"(RPC) and Document Exchange (DE). The primary difference between the two "
+"categories is that the SOAP specification defines encoding rules and "
+"conventions for RPC. The document exchange model allows the exchange of "
+"arbitrary XML documents - a key ingredient of B2B document exchange. XTS is "
+"based on the loosely coupled document-exchange style, yet it can support "
+"transactions spanning Web service that use either document-exchange or RPC."
+msgstr ""
+"SOAP 消息可以分成两个主要类别：远程过程调用（Remote Procedure Call，RPC）和文"
+"档交换（Document Exchange，DE）。这两个类别的主要区别是 SOAP 规格定义了 RPC "
+"的编码规则和约定。文档交换模型允许任意 XML 文档的交换 - B2B 文档交换的关键因"
+"素。XTS 基于松耦合的文档交换风格，然而它也支持使用文档交换或 RPC 的跨 Web 服"
+"务的事务。"
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr "Web Services Description Language (WSDL)"
+
+#. Tag: para
+#: Introduction.xml:76
+#, no-c-format
+msgid ""
+"WSDL is an XML-based language used to define Web service interfaces. An "
+"application that consumes a Web service parses the service’s WSDL document "
+"to discover the location of the service, the operations that the service "
+"supports, the protocol bindings the service supports (SOAP, HTTP, etc), and "
+"how to access them (for each operation, WSDL describes the format that the "
+"client must follow)."
+msgstr ""
+"WSDL 是用于定义 Web 服务接口的基于 XML 的语言。使用 Web 服务的程序解析服务的 "
+"WSDL 文档来发现服务的位置、服务所支持的操作、服务所支持的协议绑定（SOAP、"
+"HTTP 等）以及如何进行访问（对于每个操作，WSDL 描述了客户端必须遵循的格式）。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/JBoss_Transactions_Web_Services_Programmers_Guide_CP04.po
===================================================================

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Participants.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Participants.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Participants.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,460 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Participants.xml:6
+#, no-c-format
+msgid "Test"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:7
+#, no-c-format
+msgid "This is a test paragraph"
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:11
+#, no-c-format
+msgid "The Participant: an Overview"
+msgstr "参与者：概述"
+
+#. Tag: para
+#: Participants.xml:12
+#, no-c-format
+msgid ""
+"The participant is the entity that performs the work pertaining to "
+"transaction management on behalf of the business services involved in an "
+"application. The Web service (for example, a theatre booking system) "
+"contains some business logic for reserving a seat, enquiring availability "
+"etc, but it will need to be supported by something that maintains "
+"information in a durable manner. Typically this will be a database, but it "
+"could be a file system, NVRAM, etc. Now, although the service may talk to "
+"the back-end database directly, it cannot commit or undo any changes it (the "
+"services) makes, since these are ultimately under the control of the "
+"transaction that scoped the work. In order for the transaction to be able to "
+"exercise this control, it must have some contact with the database. In XTS "
+"this is accomplished by the participant, and the role played by the "
+"participant between the transaction and back-end transaction processing "
+"infrastructure is shown in the following figure."
+msgstr ""
+
+#. Tag: caption
+#: Participants.xml:19
+#, no-c-format
+msgid "Transactions, Participants, and Back-End Transaction Control"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:21
+#, no-c-format
+msgid ""
+"Each participant in XTS is related to either the Atomic Transaction or "
+"Business Activity protocols. In the following sections we’ll consider both "
+"protocols and their respective participants."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:25
+#, fuzzy, no-c-format
+msgid "Atomic Transaction"
+msgstr "ACID 事务"
+
+#. Tag: para
+#: Participants.xml:26
+#, no-c-format
+msgid ""
+"All Atomic Transaction participants are instances of one of the following "
+"interfaces."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:31
+#, no-c-format
+msgid "Durable2PCParticipant"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:32
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Durable2PC protocol with "
+"the following signatures, as per the <interfacename>com.arjuna.wst."
+"Durable2Participant</interfacename> interface:"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:38
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the <code>com.arjuna.wst."
+"Vote</code>. Values are: <code>ReadOnly</code>, indicating the participant "
+"does not need to be informed of the transaction outcome as no state updates "
+"were made; Prepared, indicating the participant is prepared to commit or "
+"rollback depending on the final transaction outcome, and it has made "
+"sufficient state updates persistent to accomplish this; and Aborted, "
+"indicating the participant has aborted and the transaction should also "
+"attempt to do so."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:43 Participants.xml:81
+#, no-c-format
+msgid ""
+"<emphasis>commit</emphasis>: the participant should make permanent the work "
+"that it controls. What it does will depend upon its implementation, for "
+"example, commit the reservation of the theatre ticket. The participant will "
+"then return an indication of whether or not it succeeded."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:48 Participants.xml:86
+#, no-c-format
+msgid ""
+"<emphasis>rollback</emphasis>: the participant should undo the work that it "
+"controls. The participant will then return an indication of whether or not "
+"it succeeded."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:53 Participants.xml:91
+#, no-c-format
+msgid ""
+"<emphasis>commitOnePhase</emphasis>: if there is only a single "
+"TwoPCParticipant registered with the transaction, then the coordinator can "
+"optimize the protocol and simply tell the participant to commit: there is no "
+"need for a preparatory phase since consensus is implicit."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:58 Participants.xml:96
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: during recovery the participant can inquire as "
+"to the status of the transaction it was registered with. If that transaction "
+"is no longer available (has rolled back) then this operation will be invoked "
+"by the coordination service."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:63 Participants.xml:101
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: during recovery the participant can enquire as "
+"to the status of the transaction it was registered with. If an error occurs "
+"(for example, the transaction service is unavailable) then this operation "
+"will be invoked."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:69
+#, no-c-format
+msgid "Volatile2PCParticipant"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:70
+#, no-c-format
+msgid ""
+"This participant supports the WS-Atomic Transaction Volatile2PC protocol "
+"with the following signatures, as per the <interfacename>com.arjuna.wst."
+"Volatile2Participant</interfacename> interface:"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:76
+#, no-c-format
+msgid ""
+"<emphasis>prepare</emphasis>: the participant should perform any work "
+"necessary to allow it to either commit or rollback the work performed by the "
+"Web service under the scope of the transaction. The implementation is free "
+"to do whatever it needs to in order to fulfill the implicit contract between "
+"it and the coordinator. The participant is expected to indicate whether it "
+"can prepare or not by returning an instance of the com.arjuna.wst.Vote. "
+"Values are: ReadOnly, indicating the participant does not need to be "
+"informed of the transaction outcome as no state updates were made; Prepared, "
+"indicating the participant is prepared to commit or rollback depending on "
+"the final transaction outcome, and it has made sufficient state updates "
+"persistent to accomplish this; and Aborted, indicating the participant has "
+"aborted and the transaction should also attempt to do so."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:107
+#, fuzzy, no-c-format
+msgid "Business Activity"
+msgstr "BusinessActivityManager"
+
+#. Tag: para
+#: Participants.xml:108
+#, no-c-format
+msgid ""
+"All Business Activity participants are instances of the following interfaces."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:113
+#, no-c-format
+msgid "BusinessAgreementWithParticipantCompletion"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:114
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithParticipantCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithParticipantCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:120 Participants.xml:158
+#, no-c-format
+msgid ""
+"<emphasis>close</emphasis>: the transaction has completed successfully. The "
+"participant previously informed the coordinator that it was ready to "
+"complete."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:125
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work. The participant cannot have informed the "
+"coordinator that it has completed."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:130 Participants.xml:168
+#, no-c-format
+msgid ""
+"<emphasis>compensate</emphasis>: the transaction has canceled. The "
+"participant previously informed the coordinator that it had finished work "
+"but could compensate later if required, so it is now requested to do so."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:135 Participants.xml:178
+#, no-c-format
+msgid "<emphasis>status</emphasis>: return the status of the participant."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:140 Participants.xml:183
+#, no-c-format
+msgid ""
+"<emphasis>unknown</emphasis>: if the participant inquires as to the status "
+"of the transaction it was registered with and that transaction is no longer "
+"available (has rolled back) then this operation will be invoked by the "
+"coordination service."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:145 Participants.xml:188
+#, no-c-format
+msgid ""
+"<emphasis>error</emphasis>: if the participant enquired as to the status of "
+"the transaction it was registered with and an error occurs (for example, the "
+"transaction service is unavailable) then this operation will be invoked."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:151
+#, no-c-format
+msgid "BusinessAgreementWithCoordinatorCompletion"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:152
+#, no-c-format
+msgid ""
+"This participant supports the WS-T "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol with the "
+"following signatures, as per the <interfacename>com.arjuna.wst."
+"BusinessAgreementWithCoordinatorCompletionParticipant</interfacename> "
+"interface:"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:163
+#, no-c-format
+msgid ""
+"<emphasis>cancel</emphasis>: the transaction has canceled, and the "
+"participant should undo any work."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:173
+#, no-c-format
+msgid ""
+"<emphasis>complete</emphasis>: the coordinator is informing the participant "
+"that all work it needs to do within the scope of this business activity has "
+"been received."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:194
+#, fuzzy, no-c-format
+msgid "BAParticipantManager"
+msgstr "参与者：概述"
+
+#. Tag: para
+#: Participants.xml:195
+#, no-c-format
+msgid ""
+"In order for the Business Activity protocol to work correctly, the "
+"participants must be able to autonomously signal the coordinator that they "
+"have left the activity (exited) or are ready to complete and (if necessary) "
+"compensate (completed). Unlike the Atomic Transaction protocol, where all "
+"interactions between the coordinator and participants are instigated by the "
+"coordinator when the transaction terminates, this interaction pattern "
+"requires the participant to be able to talk to the coordinator at any time "
+"during the lifetime of the business activity."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:199
+#, no-c-format
+msgid ""
+"As such, whenever a participant is registered with a business activity, it "
+"receives a handle on the coordinator. This handle is an instance of the "
+"<interfacename>BAParticipantManager</interfacename> interface, located in "
+"<code>com.arjuna.wst.BAParticipantManager</code>, with the following methods:"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:204
+#, no-c-format
+msgid ""
+"<emphasis>exit</emphasis>: the participant has exited the business activity. "
+"The participant uses this to inform the coordinator that is has left the "
+"activity. It will not be informed when (and how) the business activity "
+"terminates."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:209
+#, no-c-format
+msgid ""
+"<emphasis>completed</emphasis>: the participant has completed it works, but "
+"wishes to continue in the business activity, so that it will eventually be "
+"told when (and how) the activity terminates. The participant may later be "
+"asked to compensate for the work it has done."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:214
+#, no-c-format
+msgid ""
+"<emphasis>fault</emphasis>: the participant encountered an error during "
+"normal activation and has compensated. This places the business activity "
+"into a mandatory cancel-only mode."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:222
+#, no-c-format
+msgid "Participant Creation and Deployment"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:223
+#, no-c-format
+msgid ""
+"As has been shown, the participant provides the plumbing that drives the "
+"transactional aspects of the service. This section discusses the specifics "
+"of Participant programming and usage."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:227
+#, no-c-format
+msgid "Implementing Participants"
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:228
+#, no-c-format
+msgid ""
+"Implementing a participant is, in theory, a relatively straightforward task, "
+"though depending on the complexity of the transactional infrastructure that "
+"the participant is to manage, the actual size and complexity of a "
+"participant will vary. The participant interfaces can be found under "
+"<code>com.arjuna.wst</code>. Your implementation must implement one of these "
+"interfaces."
+msgstr ""
+
+#. Tag: title
+#: Participants.xml:233
+#, fuzzy, no-c-format
+msgid "Deploying Participants"
+msgstr "创建和部署参与者"
+
+#. Tag: para
+#: Participants.xml:234
+#, no-c-format
+msgid ""
+"In order to allow Participants to be located remote from the Transaction "
+"Manager, XTS includes transparent message routing functionality. The "
+"Participant classes are not exposed directly as web services, but rather "
+"registered with a web service which receives messages from the Transaction "
+"Manager and maps them to appropriate method invocations on the relevant "
+"Participant instance. Transactional web services will typically enroll a new "
+"Participant instance of the desired type for each new transaction. A unique "
+"identifier must be provided at enrollment time and will be used to map "
+"transaction protocol messages to the appropriate participant instance. Note "
+"that Participant method invocations do not occur in a specific transaction "
+"context. Therefore, if your Participant implementation requires knowledge of "
+"the transaction context (for example, to look up state information in a "
+"persistent store) then you should provide this to the Participant instance, "
+"typically as an argument to the constructor function. Sample Participant "
+"implementations and usage can be found in the demonstration application "
+"included with XTS."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:238
+#, no-c-format
+msgid ""
+"Any application code which creates and enrolls Participants must be deployed "
+"along with the parts of XTS necessary for receiving and processing incoming "
+"messages from the Transaction Manager. This typically means including the "
+"appropriate XTS .jar, .wsr and .war files in your application. If you are "
+"deploying your application only a server which does not already contain a "
+"Transaction Manger installation, you will also need to deploy the XTS "
+"configuration files."
+msgstr ""
+
+#. Tag: para
+#: Participants.xml:242
+#, no-c-format
+msgid ""
+"In early access releases of the XTS product, the Transaction Manager and "
+"participant management functions are not provided as separable components. "
+"Configuration and deployment of the participant infrastructure is therefore "
+"as in the Transaction Manger section above. More flexible deployment of the "
+"XTS components will be available in the final release."
+msgstr ""

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Preface.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Preface.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Preface.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,23 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr "序言"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Revision_History.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Revision_History.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Revision_History.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,29 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr "修订历史记录"
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Stand-alone_Coordinator.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Stand-alone_Coordinator.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Stand-alone_Coordinator.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,38 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:6
+#, no-c-format
+msgid "Stand-alone Coordinator"
+msgstr "独立协调者"
+
+#. Tag: title
+#: Stand-alone_Coordinator.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "介绍"
+
+#. Tag: para
+#: Stand-alone_Coordinator.xml:9
+#, no-c-format
+msgid ""
+"For configuring a stand-alone Web Services transaction coordinator, see the "
+"relevant chapter in the System Administrator’s Guide."
+msgstr ""
+"关于配置独立的 Web 服务的事务协调者，请参考《系统管理员指南》的相关章节。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/The_XTS_API.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/The_XTS_API.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/The_XTS_API.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,577 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr "XTS API"
+
+#. Tag: title
+#: The_XTS_API.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "介绍"
+
+#. Tag: para
+#: The_XTS_API.xml:9
+#, no-c-format
+msgid ""
+"This chapter shows how to use the XTS API. This is of use both at the client-"
+"side where applications consume transactional Web services, and at the "
+"service/participant side where transactions need to be coordinated with back-"
+"end systems."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:15
+#, fuzzy, no-c-format
+msgid "API for the Atomic Transaction protocol"
+msgstr "新的事务协议"
+
+#. Tag: para
+#: The_XTS_API.xml:16
+#, no-c-format
+msgid ""
+"The following classes and interfaces are located within the <package>com."
+"arjuna.wst or com.arjuna.mw.wst</package> packages and sub-packages."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:20
+#, no-c-format
+msgid "Vote"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:21
+#, no-c-format
+msgid ""
+"During the two-phase commit protocol, a participant will be asked to vote on "
+"whether or not it can prepare to confirm the work that it controls. It must "
+"return one of the following subtypes of <code>com.arjuna.wst.Vote</code>:"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:27
+#, no-c-format
+msgid ""
+"<emphasis>Prepared</emphasis>: the participant indicates that it can prepare "
+"if asked to by the coordinator. It will not have committed at this stage "
+"however, since it does not know what the final outcome will be."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:32
+#, no-c-format
+msgid ""
+"<emphasis>Aborted</emphasis>: the participant indicates that it cannot "
+"prepare and has in fact rolled back. The participant should not expect to "
+"get a second phase message."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:37
+#, no-c-format
+msgid ""
+"<emphasis>ReadOnly</emphasis>: the participant indicates that the work it "
+"controls has not made any changes to state that require it to be informed of "
+"the final outcome of the transaction. Essentially the participant is "
+"resigning from the transaction."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:42
+#, no-c-format
+msgid ""
+"Thus a possible implementation of a 2PC participant’s prepare method may "
+"resemble the following:"
+msgstr ""
+
+#. Tag: screen
+#: The_XTS_API.xml:45
+#, no-c-format
+msgid ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+msgstr ""
+"public Vote prepare () throws WrongStateException, SystemException\n"
+"{\n"
+"        // Some participant logic here\n"
+"        \n"
+"        if(/* some condition based on the outcome of the business logic */)\n"
+"        {\n"
+"                // Vote to confirm\n"
+"                return new com.arjuna.wst.Prepared();\n"
+"        }\n"
+"        else if(/*some other condition based on the outcome of the business "
+"logic*/)\n"
+"        {\n"
+"                // Resign\n"
+"                return new com.arjuna.wst.ReadOnly();\n"
+"        }\n"
+"        else\n"
+"        {\n"
+"                // Vote to cancel\n"
+"                return new com.arjuna.wst.Aborted();\n"
+"        }\n"
+"}"
+
+#. Tag: title
+#: The_XTS_API.xml:47
+#, fuzzy, no-c-format
+msgid "The transaction context"
+msgstr "新的事务协议"
+
+#. Tag: para
+#: The_XTS_API.xml:48
+#, no-c-format
+msgid ""
+"A transaction is typically represented by some unique identifier and a "
+"reference to the coordinator which manages the transaction, for example, a "
+"URL. XTS allows transactions to be nested such that a transaction hierarchy "
+"(tree) may be formed. Thus, a transaction context may be a set of "
+"transactions, with the top-most transaction the root parent (superior)."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr "TxContext"
+
+#. Tag: para
+#: The_XTS_API.xml:54
+#, no-c-format
+msgid ""
+"<code>com.arjuna.mw.wst.TxContext</code> is an opaque representation of a "
+"transaction context."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:60
+#, no-c-format
+msgid ""
+"<emphasis>valid</emphasis>: this indicates whether or not the contents are "
+"valid."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:65
+#, no-c-format
+msgid "<emphasis>equals</emphasis>: can be used to compare two instances."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:71
+#, fuzzy, no-c-format
+msgid "UserTransaction"
+msgstr "ACID 事务"
+
+#. Tag: para
+#: The_XTS_API.xml:72
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserTransaction</classname> is the class that "
+"most users (for example, clients and services) will see. This isolates them "
+"from the underlying protocol-specific aspects of the XTS implementation. "
+"Importantly, a UserTransaction does not represent a specific transaction, "
+"but rather is responsible for providing access to an implicit per-thread "
+"transaction context; it is similar to the UserTransaction in the JTA "
+"specification. Therefore, all of the UserTransaction methods implicitly act "
+"on the current thread of control."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:76
+#, no-c-format
+msgid ""
+"A new transaction is begun and associated with the invoking thread by using "
+"the begin method. If there is already a transaction associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created transaction with the "
+"current thread."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:79
+#, no-c-format
+msgid ""
+"The transaction is committed by the commit method. This will execute the "
+"Volatile2PC and Durable2PC protocols prior to returning. If there is no "
+"transaction associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. If the transaction "
+"ultimately rolls back then the <code>TransactionRolledBackException</code> "
+"is thrown. When complete, this operation disassociates the transaction from "
+"the current thread such that it becomes associated with no transaction."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:82
+#, no-c-format
+msgid ""
+"The <code>rollback</code> operation will terminate the transaction and "
+"return normally if it succeeded, while throwing an appropriate exception if "
+"it didn’t. If there is no transaction associated with the invoking thread "
+"then <code>UnknownTransactionException</code> is thrown."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:86
+#, fuzzy, no-c-format
+msgid "UserTransactionFactory"
+msgstr "UserBusinessActivityFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, fuzzy, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+"UserBusinessActivities 从 <code>UserBusinessActivityFactory</code> 中获得。"
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, fuzzy, no-c-format
+msgid "TransactionManager"
+msgstr "事务概述"
+
+#. Tag: para
+#: The_XTS_API.xml:93
+#, no-c-format
+msgid ""
+"The <interfacename>TransactionManager</interfacename> interface represents "
+"the service/container/participant’s (service-side users) typical way in "
+"which to interact with the underlying transaction service implementation. As "
+"with <interfacename>UserTransaction</interfacename> a "
+"<interfacename>TransactionManager</interfacename> does not represent a "
+"specific transaction, but rather is responsible for providing access to an "
+"implicit per-thread transaction context."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:97
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific transaction. In "
+"order to do this it is necessary to disassociate the thread from any "
+"transactions. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the transaction. The "
+"thread is then no longer associated with any transaction."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:100
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with a transaction(s) via its <code>TxContext</code>. Prior to "
+"association, the thread is disassociated with any transaction(s) with which "
+"it may be currently associated. If the <code>TxContext</code> is null, then "
+"the thread is associated with no transaction. The "
+"<code>UnknownTransactionException</code> exception is thrown if the "
+"transaction that the <code>TxContext</code> refers to is invalid in the "
+"scope of the invoking thread."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:103
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current transaction, or null if there is "
+"none. Unlike suspend, this method does not disassociate the current thread "
+"from the transaction(s). This can be used to enable multiple threads to "
+"execute within the scope of the same transaction."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:106
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a transaction, the "
+"container or participant must use:"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:111
+#, no-c-format
+msgid ""
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"Volatile2PC protocol; a unique identifier for the participant is also "
+"required. If there is no transaction associated with the invoking thread "
+"then the <code>UnknownTransactionException</code> exception is thrown. If "
+"the coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:116
+#, no-c-format
+msgid ""
+"<emphasis>enlistForDurableTwoPhase</emphasis>: enlist the specified "
+"participant with current transaction such that it will participate in the "
+"2PC protocol; a unique identifier for the participant is also required. If "
+"there is no transaction associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the "
+"transaction is not in a state where participants can be enrolled (for "
+"example, it is terminating) then <code>WrongStateException</code> will be "
+"thrown."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:122
+#, fuzzy, no-c-format
+msgid "TransactionFactory"
+msgstr "ACID 事务"
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, fuzzy, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+"BusinessActivityManagers 通过 <code>BusinessActivityManagerFactory</code> 获"
+"得。"
+
+#. Tag: title
+#: The_XTS_API.xml:130
+#, no-c-format
+msgid "API for the Business Activity protocol"
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:132
+#, fuzzy, no-c-format
+msgid "UserBusinessActivity"
+msgstr "UserBusinessActivityFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:133
+#, no-c-format
+msgid ""
+"The <classname>com.arjuna.wst.UserBusinessActivity</classname> is the class "
+"that most users (for example, clients and services) will see. This isolates "
+"them from the underlying protocol-specific aspects of the XTS "
+"implementation. Importantly, a <code>UserBusinessActivity</code> does not "
+"represent a specific business activity, but rather is responsible for "
+"providing access to an implicit per-thread activity. Therefore, all of the "
+"<code>UserBusinessActivity</code> methods implicitly act on the current "
+"thread of control."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:137
+#, no-c-format
+msgid ""
+"A new business activity is begun and associated with the invoking thread by "
+"using the begin method. If there is already an activity associated with the "
+"thread then the <code>WrongStateException</code> exception is thrown. Upon "
+"success, this operation associates the newly created activity with the "
+"current thread."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:140
+#, no-c-format
+msgid ""
+"The business activity is completed successfully by the close method. This "
+"will execute the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol prior to returning. If there is no activity associated with the "
+"invoking thread then <code>UnknownTransactionException</code> is thrown. If "
+"the activity ultimately cancels then the "
+"<code>TransactionRolledBackException</code> is thrown. When complete, this "
+"operation disassociates the business activity from the current thread such "
+"that it becomes associated with no activity."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:143
+#, no-c-format
+msgid ""
+"The cancel operation will terminate the business activity and return "
+"normally if it succeeded, while throwing an appropriate exception if it "
+"didn’t. If there is no activity associated with the invoking thread then "
+"<code>UnknownTransactionException</code> is thrown. Any participants that "
+"had previously completed will be informed to compensate for their work."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:146
+#, no-c-format
+msgid ""
+"Some participants may have registered for the "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> protocol, which "
+"requires the coordinator or application to inform them when all work that "
+"they need to do within the scope of a business activity has been performed. "
+"The application should therefore use the complete method to inform these "
+"participants."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:150
+#, no-c-format
+msgid "UserBusinessActivityFactory"
+msgstr "UserBusinessActivityFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+"UserBusinessActivities 从 <code>UserBusinessActivityFactory</code> 中获得。"
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr "BusinessActivityManager"
+
+#. Tag: para
+#: The_XTS_API.xml:157
+#, no-c-format
+msgid ""
+"The <interfacename>BusinessActivityManager</interfacename> interface "
+"represents the service/container/participant’s (service-side users) typical "
+"way in which to interact with the underlying business activity service "
+"implementation. As with <interfacename>UserBusinessActivity</interfacename> "
+"a <interfacename>BusinessActivityManager</interfacename> does not represent "
+"a specific activity, but rather is responsible for providing access to an "
+"implicit per-thread activity."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:161
+#, no-c-format
+msgid ""
+"A thread of control may require periods of non-transactionality so that it "
+"may perform work that is not associated with a specific activity. In order "
+"to do this it is necessary to disassociate the thread from any business "
+"activities. The suspend method accomplishes this, returning a "
+"<code>TxContext</code> instance, which is a handle on the activity. The "
+"thread is then no longer associated with any activity."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:164
+#, no-c-format
+msgid ""
+"The <methodname>resume</methodname> method can be used to (re-)associate a "
+"thread with an activity (or activities) via its TxContext. Prior to "
+"association, the thread is disassociated with any activity with which it may "
+"be currently associated. If the <code>TxContext</code> is null, then the "
+"thread is associated with no activity. The "
+"<code>UnknownTransactionException</code> exception is thrown if the business "
+"activity that the TxContext refers to is invalid in the scope of the "
+"invoking thread."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:167
+#, no-c-format
+msgid ""
+"The <methodname>currentTransaction</methodname> method returns the "
+"<code>TxContext</code> for the current business activity, or null if there "
+"is none. Unlike suspend, this method does not disassociate the current "
+"thread from the activity. This can be used to enable multiple threads to "
+"execute within the scope of the same business activity."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:170
+#, no-c-format
+msgid ""
+"In order to register and resign participants with a business activity, the "
+"container or participant must use:"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:175
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
+"enlist the specified participant with current business activity such that it "
+"will participate in the <code>BusinessAgreementWithParticipantCompletion</"
+"code> protocol; a unique identifier for the participant is also required. If "
+"there is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:180
+#, no-c-format
+msgid ""
+"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
+"enlist the specified participant with current activity such that it will "
+"participate in the <code>BusinessAgreementWithCoordinatorCompletion</code> "
+"protocol; a unique identifier for the participant is also required. If there "
+"is no business activity associated with the invoking thread then the "
+"<code>UnknownTransactionException</code> exception is thrown. If the "
+"coordinator already has a participant enrolled with the same identifier, "
+"then <code>AlreadyRegisteredException</code> will be thrown. If the activity "
+"is not in a state where participants can be enrolled (for example, it is "
+"terminating) then <code>WrongStateException</code> will be thrown."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:186
+#, no-c-format
+msgid "BusinessActivityManagerFactory"
+msgstr "BusinessActivityManagerFactory"
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
+"BusinessActivityManagers 通过 <code>BusinessActivityManagerFactory</code> 获"
+"得。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactional_Web_Services.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactional_Web_Services.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactional_Web_Services.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,120 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr "事务性 Web 服务"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "介绍"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:9
+#, no-c-format
+msgid ""
+"This chapter describes how to provide transactional support for new and "
+"existing Web services using the service-side facilities of XTS. It shows how "
+"new services can be made transactional with no additional programming, and "
+"how existing services can be made WS-T transaction-aware in a non-invasive "
+"fashion."
+msgstr ""
+"本章描述了如何用 XTS 的服务端功能为新的和现有的 Web 服务提供事务性支持。它演"
+"示了新的服务如何不需额外编程就可以成为事务性的，以及现有的服务如何以非侵入方"
+"式成为 WS-T 事务性的。"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr "事务性 Web 服务"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:16
+#, no-c-format
+msgid ""
+"A Web service is a business-level entity. It encapsulates application logic "
+"needed to perform some domain-specific task, or is designed to delegate to a "
+"back-end system which executes that logic. Given it is part of application "
+"code, such non-functional requirements as transactionality should not "
+"impinge on its construction."
+msgstr ""
+"Web 服务是一个商业级的实体。它封装了执行某些域专有的任务的程序逻辑，并把这些"
+"任务委托给执行该逻辑的后台系统。非功能性的要求如事务性不应该影响程序代码的构"
+"建。"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:19
+#, no-c-format
+msgid ""
+"To support this notion, XTS provides a suite of components designed to work "
+"at the SOAP stack level, which deal with transactional matters on behalf of "
+"a Web service without requiring any changes to that service. In XTS two "
+"context handling components are registered with the SOAP server and deal "
+"with context management on behalf of the service without the service having "
+"to worry about context propagation issues itself. This is shown in the "
+"following figure."
+msgstr ""
+"为了支持这种主张，XTS 提供了一套 SOAP 栈级别的组件，它替 Web 服务处理事务性问"
+"题而无需修改该服务。在 XTS 里，有两个上下文处理组件在 SOAP 服务器上注册并替服"
+"务管理上下文，服务自身不需要担心上下文传递的问题。下图显示了这一点。"
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr "在 SOAP 服务器上注册的上下文处理程序"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:28
+#, no-c-format
+msgid ""
+"The detail of the context management that the context processor performs is "
+"unimportant to the Web service application logic, and is orthogonal to any "
+"work performed by any other protocol-specific context handlers too. However "
+"back-end systems which the Web service application logic uses (such as "
+"databases) are often interested in the front-end transaction context such "
+"that any operations invoked within its scope can be mapped onto a back-end "
+"transaction context. This is typically achieved at the back-end by wrapping "
+"a database driver in a veneer which implements both the interface of the "
+"original driver and hooks into the service-side API to access the "
+"transaction context details. The general architecture for this pattern is "
+"shown in the figure below."
+msgstr ""
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:35
+#, no-c-format
+msgid "General Pattern for Back-End Integration, Service Side"
+msgstr "后台集成的通用模型，服务器端"
+
+#. Tag: para
+#: Transactional_Web_Services.xml:37
+#, no-c-format
+msgid ""
+"The missing element from this is the commit protocol which finally allows "
+"back-end work to be made durable or not at the end of a transaction. This is "
+"covered in the participant chapter where the participant/back-end relation "
+"is explored further."
+msgstr ""
+"这里未提及的元素是最后在事务结束时允许后台工作持久化与否的提交协议。参与者章"
+"节将涵盖这些内容并进一步探讨参与者/后台之间的关系。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,703 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Transactions_Overview.xml:6
+#, no-c-format
+msgid "Transactions Overview"
+msgstr "事务概述"
+
+#. Tag: para
+#: Transactions_Overview.xml:7
+#, no-c-format
+msgid ""
+"Transactions have emerged as the dominant paradigm for coordinating "
+"interactions between parties in a distributed system, and in particular to "
+"manage applications that require concurrent access to shared data. Much of "
+"the JBossTS Web Service API is based on contemporary transaction APIs whose "
+"familiarity will enhance developer productivity and lessen the learning "
+"curve. While the following section provides the essential information that "
+"you should know before starting to use XTS for building transactional Web "
+"Services, it should not be treated as a definitive reference to all "
+"transactional technology."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:10
+#, no-c-format
+msgid ""
+"A classic transaction is a unit of work that either completely succeeds, or "
+"fails with all partially completed work being undone. When a transaction is "
+"committed, all changes made by the associated requests are made durable, "
+"normally by committing the results of the work to a database. If a "
+"transaction should fail and is rolled back, all changes made by the "
+"associated work are undone. Transactions in distributed systems typically "
+"require the use of a transaction manager that is responsible for "
+"coordinating all of the participants that are part of the transaction."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:13
+#, no-c-format
+msgid ""
+"The main components involved in using and defining transactional Web "
+"Services using XTS are illustrated in Figure 1."
+msgstr "图例 1 解释了使用和定义采用 XTS 的事务性 web 服务的主要组件。"
+
+#. Tag: para
+#: Transactions_Overview.xml:18
+#, no-c-format
+msgid ""
+"A Transaction Service: The Transaction Service captures the model of the "
+"underlying transaction protocol and coordinates parties affiliated with the "
+"transaction according to that model."
+msgstr ""
+"事务服务（Transaction Service）：事务服务捕获底层事务协议的模型并协调按照该模"
+"型和事务相关联的各方。"
+
+#. Tag: para
+#: Transactions_Overview.xml:23
+#, no-c-format
+msgid ""
+"A Transaction API: Provides an interface for transaction demarcation and the "
+"registration of participants."
+msgstr "Transaction API：为事务限界和参与者注册提供接口。"
+
+#. Tag: para
+#: Transactions_Overview.xml:28
+#, no-c-format
+msgid ""
+"A Participant: The entity that cooperates with the transaction service on "
+"behalf of its associated business logic."
+msgstr "参与者（Participant）：替相关联的商业逻辑和事务服务合作的实体。"
+
+#. Tag: para
+#: Transactions_Overview.xml:33
+#, no-c-format
+msgid ""
+"The Context: Captures the necessary details of the transaction such that "
+"participants can enlist within its scope."
+msgstr ""
+"上下文（Context）：捕获事务的必要细节，让参与者可以在其作用域里进行登记。"
+
+#. Tag: caption
+#: Transactions_Overview.xml:42
+#, no-c-format
+msgid "Web Services and XTS"
+msgstr "Web 服务和 XTS"
+
+#. Tag: title
+#: Transactions_Overview.xml:45
+#, no-c-format
+msgid "The Coordinator"
+msgstr "协调者（Coordinator）"
+
+#. Tag: para
+#: Transactions_Overview.xml:46
+#, no-c-format
+msgid ""
+"Associated with every transaction is a coordinator, which is responsible for "
+"governing the outcome of the transaction. The coordinator may be implemented "
+"as a separate service or may be co-located with the user for improved "
+"performance. Each coordinator is created by the transaction manager service, "
+"which is in effect a factory for those coordinators."
+msgstr ""
+"协调者和每个事务相关联，它负责管理的事务的结果。协调者可以独立的服务实施或与"
+"用户集成来提高性能。事务管理者服务创建每个协调者，它实际上是一个协调者工厂。"
+
+#. Tag: para
+#: Transactions_Overview.xml:50
+#, no-c-format
+msgid ""
+"A coordinator communicates with enrolled participants to inform them of the "
+"desired termination requirements, for instance, whether they should accept "
+"(for example, confirm) or reject (for example, cancel) the work done within "
+"the scope of the given transaction. For example, whether to purchase the "
+"(provisionally reserved) flight tickets for the user or to release them. An "
+"application/client may wish to terminate a transaction in a number of "
+"different ways (for example, confirm or cancel). However, although the "
+"coordinator will attempt to terminate in a manner consistent with that "
+"desired by the client, it is ultimately the interactions between the "
+"coordinator and the participants that will determine the actual final "
+"outcome."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:53
+#, no-c-format
+msgid ""
+"A transaction manager is typically responsible for managing coordinators for "
+"many transactions. The initiator of the transaction (for example, the "
+"client) communicates with a transaction manager and asks it to start a new "
+"transaction and associate a coordinator with the transaction. Once created, "
+"the context can be propagated to Web services in order for them to associate "
+"their work with the transaction."
+msgstr ""
+
+#. Tag: title
+#: Transactions_Overview.xml:57
+#, fuzzy, no-c-format
+msgid "The Transaction Context"
+msgstr "新的事务协议"
+
+#. Tag: para
+#: Transactions_Overview.xml:58
+#, no-c-format
+msgid ""
+"In order for a transaction to span a number of services, certain information "
+"has to be shared between those services in order to propagate information "
+"about the transaction. This information is known as the Context. Using XTS, "
+"the context is automatically propagated and processed by transaction-aware "
+"components of an application. Though XTS removes most of the work associated "
+"with propagating contexts, it is still instructive to understand what "
+"information is captured in a context:"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:64
+#, no-c-format
+msgid ""
+"A transaction identifier which guarantees global uniqueness for an "
+"individual transaction;"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:69
+#, no-c-format
+msgid ""
+"The transaction coordinator location or endpoint address so participants can "
+"be enrolled."
+msgstr ""
+
+#. Tag: caption
+#: Transactions_Overview.xml:78
+#, no-c-format
+msgid "Web Services and Context Flow"
+msgstr "Web 服务和上下文流程"
+
+#. Tag: para
+#: Transactions_Overview.xml:80
+#, no-c-format
+msgid ""
+"As shown in Figure 2, whenever an application message is sent, the XTS "
+"Client API automatically creates a context and embeds it into the message. "
+"Similarly, any transaction-aware services are able to extract that context "
+"using the XTS service-side infrastructure and use it to perform work within "
+"the context of a particular transaction – even though that transaction was "
+"initiated elsewhere on the Web! The value of this approach is that the "
+"business logic contained within the client application and services are not "
+"peppered with transaction-processing code."
+msgstr ""
+"如图 2 所示，每当发送一条应用程序消息，XTS 客户度 API 都自动地创建一个上下文"
+"并嵌入到该消息里。类似地，任何启用事务的服务都能够用 XTS 服务器端基础结构来抽"
+"取上下文并用其在特定事务的上下文里执行相关应用 － 即使该事务是在 Web 上的其他"
+"地方启动的！这个方法的好处是客户端程序和服务里的商业逻辑不会和事务处理代码混"
+"在一起。"
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr "ACID 事务"
+
+#. Tag: para
+#: Transactions_Overview.xml:85
+#, no-c-format
+msgid ""
+"Traditionally, transaction processing systems support ACID properties. ACID "
+"is an acronym for Atomic, Consistent, Isolated, and Durable. A unit of work "
+"has traditionally been considered transactional only if the ACID properties "
+"are maintained:"
+msgstr ""
+"传统上，事务处理系统支持 ACID 属性。ACID 是 Atomic、Consistent、solated 和 "
+"Durable 的缩写。只要维持了 ACID 属性，某个工作单元通常被认为是事务性的："
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr "原子性（Atomicity）：事务完全执行或根本不执行。"
+
+#. Tag: para
+#: Transactions_Overview.xml:96
+#, no-c-format
+msgid ""
+"Consistency: The effects of the transaction preserve the internal "
+"consistency of an underlying data structure."
+msgstr "一致性（Consistency）：事务的结果和底层数据结构保持内部一致性。"
+
+#. Tag: para
+#: Transactions_Overview.xml:101
+#, no-c-format
+msgid ""
+"Isolated: The transaction runs as if it were running alone with no other "
+"transactions running and is not visible to other transactions."
+msgstr ""
+"独立性（Isolated）：事务单独地运行，和其他事务的运行无关，且不为其他事务所"
+"见。"
+
+#. Tag: para
+#: Transactions_Overview.xml:106
+#, no-c-format
+msgid ""
+"Durable: the transaction’s results will not be lost in the event of a "
+"failure."
+msgstr "持久性（Durable）：出现故障时，事务的结果不会丢失。"
+
+#. Tag: title
+#: Transactions_Overview.xml:112
+#, no-c-format
+msgid "Two-Phase Commit"
+msgstr "两阶段提交"
+
+#. Tag: para
+#: Transactions_Overview.xml:113
+#, no-c-format
+msgid ""
+"The classical two-phase commit approach is the bedrock of JBossTS (and more "
+"generally of Web Services transactions). Two-phase commit provides "
+"coordination of parties that are involved in a transaction. In general, the "
+"flow of a two-phase commit transaction is as follows:"
+msgstr ""
+"经典的两阶段提交（Two-phase commit）方法是 JBossTS（或者可说是 Web 服务的事"
+"务）的基石。两阶段提交提供了事务涉及的各方的协作。通常来说，两阶段提交事务的"
+"流程为："
+
+#. Tag: para
+#: Transactions_Overview.xml:119
+#, no-c-format
+msgid "A transaction is started, and some work is performed."
+msgstr "事务启动并执行某些工作。"
+
+#. Tag: para
+#: Transactions_Overview.xml:124
+#, no-c-format
+msgid "Once the work is finished, the two-phase commit begins."
+msgstr "一旦完成了这些工作，两阶段提交开始。"
+
+#. Tag: para
+#: Transactions_Overview.xml:129
+#, no-c-format
+msgid ""
+"The coordinator (transaction manager) of the transaction asks each resource "
+"taking part in the transaction whether it is prepared to commit."
+msgstr "事务的协调者（事务管理者）询问参与事务的每个资源是否准备好提交了。"
+
+#. Tag: para
+#: Transactions_Overview.xml:134
+#, no-c-format
+msgid ""
+"If all resources respond positively, the coordinator instructs all work "
+"performed to be made durable (usually committed to a database)."
+msgstr ""
+"如果所有资源都响应是，协调者指示把所有执行的工作持久化（通常是提交到数据"
+"库）。"
+
+#. Tag: para
+#: Transactions_Overview.xml:139
+#, no-c-format
+msgid ""
+"If not, all work performed is rolled back (undone) such that the underlying "
+"data structures are in their original states."
+msgstr ""
+"如果否，所有执行的工作将被回滚（取消），使得底层的数据结构回到原始的状态。"
+
+#. Tag: caption
+#: Transactions_Overview.xml:148
+#, no-c-format
+msgid "The Two-Phase Commit Protocol"
+msgstr "两阶段提交协议"
+
+#. Tag: para
+#: Transactions_Overview.xml:151
+#, no-c-format
+msgid ""
+"During two-phase commit transactions, coordinators and resources keep track "
+"of activity in non-volatile data stores so that they can recover in the case "
+"of a failure."
+msgstr ""
+"在两阶段提交的过程中，协调者和资源都在非易变的数据库里记录活动，以便在发生故"
+"障时能够进行恢复。"
+
+#. Tag: title
+#: Transactions_Overview.xml:156
+#, fuzzy, no-c-format
+msgid "The synchronization protocol"
+msgstr "新的事务协议"
+
+#. Tag: para
+#: Transactions_Overview.xml:157
+#, no-c-format
+msgid ""
+"As well as the two-phase commit protocol, traditional transaction processing "
+"systems employ an additional protocol, often referred to as the "
+"synchronization protocol. If you recall the original ACID properties, then "
+"you’ll remember that Durability is important in the case where state changes "
+"have to be available despite failures. What this means is that applications "
+"interact with a persistence store of some kind (e.g., a database) and this "
+"can impose a significant overhead – disk access is orders of magnitude "
+"slower than access to main computer memory."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:161
+#, no-c-format
+msgid ""
+"One apparently obvious solution to this problem would be to cache the state "
+"in main memory and only operate on that for the duration of a transaction. "
+"Unfortunately you’d then need some way of being able to flush the state back "
+"to the persistent store before the transaction terminates, or risk losing "
+"the full ACID properties. This is what the synchronization protocol does, "
+"with Synchronization participants."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:164
+#, no-c-format
+msgid ""
+"Synchronizations are informed that a transaction is about to commit, so they "
+"can, for example, flush cached state, which may be being used to improve "
+"performance of an application, to a durable representation prior to the "
+"transaction committing. They are then informed when the transaction has "
+"completed and in what state it completed."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:169
+#, no-c-format
+msgid ""
+"Synchronizations essentially turn the two-phase commit protocol into a four-"
+"phase protocol:"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:174
+#, no-c-format
+msgid ""
+"Before the transaction starts the two-phase commit, all registered "
+"Synchronizations are informed. Any failure at this point will cause the "
+"transaction to roll back."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:179
+#, no-c-format
+msgid "The coordinator then conducts the normal two-phase commit protocol."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:184
+#, no-c-format
+msgid ""
+"Once the transaction has terminated, all registered Synchronizations are "
+"informed. However, this is a courtesy invocation because any failures at "
+"this stage are ignored: the transaction has terminated so there’s nothing to "
+"affect."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:189
+#, no-c-format
+msgid ""
+"Unlike the two-phase commit protocol, the synchronization protocol does not "
+"have the same failure requirements. For example, Synchronization "
+"participants don’t need to make sure they can recover in the event of "
+"failures; this is because any failure before the two-phase commit protocol "
+"completes means the transaction will roll back, and failures after it has "
+"completed can’t affect the data the Synchronization participants were "
+"managing."
+msgstr ""
+
+#. Tag: title
+#: Transactions_Overview.xml:193
+#, no-c-format
+msgid "Optimizations to the protocol"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:194
+#, no-c-format
+msgid ""
+"There are several variants to the standard two-phase commit protocol that "
+"are worth knowing about because they can have an impact on performance and "
+"failure recovery. We shall briefly describe those that are the most common "
+"variants on the protocol:"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:200
+#, no-c-format
+msgid ""
+"Presumed abort: if a transaction is going to roll back then it may simply "
+"record this information locally and tell all enlisted participants. Failure "
+"to contact a participant has no affect on the transaction outcome; the "
+"transaction is effectively informing participants as a courtesy. Once all "
+"participants have been contacted the information about the transaction can "
+"be removed. If a subsequent request for the status of the transaction occurs "
+"there will be no information available and the requestor can assume that the "
+"transaction has aborted (rolled back). This optimization has the benefit "
+"that no information about participants need be made persistent until the "
+"transaction has decided to commit (i.e., progressed to the end of the "
+"prepare phase), since any failure prior to this point will be assumed to be "
+"an abort of the transaction."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:205
+#, fuzzy, no-c-format
+msgid ""
+"One-phase: if there is only a single participant involved in the "
+"transaction, the coordinator need not drive it through the prepare phase. "
+"Thus, the participant will simply be told to commit and the coordinator need "
+"not record information about the decision since the outcome of the "
+"transaction is solely down to the participant."
+msgstr ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
+
+#. Tag: para
+#: Transactions_Overview.xml:210
+#, no-c-format
+msgid ""
+"Read-only: when a participant is asked to prepare, it can indicate to the "
+"coordinator that no information or data that it controls has been modified "
+"during the transaction. Such a participant does not need to be informed "
+"about the outcome of the transaction since the fate of the participant has "
+"no affect on the transaction. As such, a read-only participant can be "
+"omitted from the second phase of the commit protocol."
+msgstr ""
+
+#. Tag: title
+#: Transactions_Overview.xml:216
+#, no-c-format
+msgid "Non-atomic transactions and heuristic outcomes"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:217
+#, no-c-format
+msgid ""
+"In order to guarantee atomicity, the two-phase commit protocol is "
+"necessarily blocking. What this means is that as a result of failures, "
+"participants may remain blocked for an indefinite period of time even if "
+"failure recovery mechanisms exist. Some applications and participants simply "
+"cannot tolerate this blocking."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:221
+#, no-c-format
+msgid ""
+"To break this blocking nature, participants that have got past the prepare "
+"phase are allowed to make autonomous decisions as to whether they commit or "
+"rollback: such a participant must record this decision in case it is "
+"eventually contacted to complete the original transaction. If the "
+"coordinator eventually informs the participant of the transaction outcome "
+"and it is the same as the choice the participant made, then there’s no "
+"problem. However, if it is contrary, then a non-atomic outcome has obviously "
+"happened: a heuristic outcome."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:224
+#, no-c-format
+msgid ""
+"How this heuristic outcome is reported to the application and resolved is "
+"usually the domain of complex, manually driven system administration tools, "
+"since in order to attempt an automatic resolution requires semantic "
+"information about the nature of participants involved in the transactions."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:227
+#, no-c-format
+msgid ""
+"Precisely when a participant makes a heuristic decision is obviously "
+"implementation dependant. Likewise, the choice the participant makes (to "
+"commit or to roll back) will depend upon the implementation and possibly the "
+"application/environment in which it finds itself. The possible heuristic "
+"outcomes are:"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:232
+#, no-c-format
+msgid ""
+"Heuristic rollback: the commit operation failed because some or all of the "
+"participants unilaterally rolled back the transaction."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:237
+#, no-c-format
+msgid ""
+"Heuristic commit: an attempted rollback operation failed because all of the "
+"participants unilaterally committed. This may happen if, for example, the "
+"coordinator was able to successfully prepare the transaction but then "
+"decided to roll it back (for example, it could not update its log) but in "
+"the meanwhile the participants decided to commit."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:242
+#, no-c-format
+msgid ""
+"Heuristic mixed: some updates (participants) were committed while others "
+"were rolled back."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:247
+#, no-c-format
+msgid ""
+"Heuristic hazard: the disposition of some of the updates is unknown. For "
+"those which are known, they have either all been committed or all rolled "
+"back."
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:252
+#, no-c-format
+msgid ""
+"Heuristic decisions should be used with care and only in exceptional "
+"circumstances since there is the possibility that the decision will differ "
+"from that determined by the transaction service and will thus lead to a loss "
+"of integrity in the system. Having to perform resolution of heuristics is "
+"something you should try to avoid, either by working with services/"
+"participants that don’t cause heuristics, or by using a transaction service "
+"that provides assistance in the resolution process."
+msgstr ""
+
+#. Tag: title
+#: Transactions_Overview.xml:256
+#, no-c-format
+msgid "A New Transaction Protocol"
+msgstr "新的事务协议"
+
+#. Tag: para
+#: Transactions_Overview.xml:257
+#, no-c-format
+msgid ""
+"Many component technologies offer mechanisms for coordinating ACID "
+"transactions based on two-phase commit semantics (i.e., CORBA/OTS, JTS/JTA, "
+"MTS/MSDTC). ACID transactions are not suitable for all Web services "
+"transactions since:"
+msgstr ""
+"许多组件技术都提供协调基于两阶段提交模式（如 CORBA/OTS、JTS/JTA、MTS/MSDTC）"
+"的 ACID 事务的机制。ACID 事务不适合于所有的 Web 服务，因为："
+
+#. Tag: para
+#: Transactions_Overview.xml:263
+#, no-c-format
+msgid ""
+"Classic ACID transactions are predicated on the idea that an organization "
+"that develops and deploys applications does so using their own "
+"infrastructure, typically an Intranet. Ownership meant transactions operated "
+"in a trusted and predictable manner. To assure ACIDity, potentially long-"
+"lived locks could be kept on underlying data structures during two-phase "
+"commit. Resources could be used for any period of time and released when the "
+"transaction was complete. In the Web services arena, these assumptions are "
+"no longer valid. One obvious reason is that the owners of data exposed "
+"through a Web service will refuse to allow their data to be locked for "
+"extended periods since to allow such locks invites denial-of-service."
+msgstr ""
+"经典的 ACID 事务根据某个机构用自己的基础结构（如企业网）来开发和部署应用程序"
+"来判定。所有权表示事务以可信任和可预测的方式来操作。要确保 ACID 属性，潜在的"
+"长期锁可以在两阶段提交过程中保持在底层数据结构里。资源可以在任何时期被使用并"
+"在当事务完成时释放。在 Web 服务领域里，这些假设都不再有效。显然的一个原因是，"
+"通过 Web 服务开放的数据的所有者将拒绝将其数据锁定更长的时间，因为允许这样的锁"
+"可能招致 denial-of-service 攻击。"
+
+#. Tag: para
+#: Transactions_Overview.xml:268
+#, no-c-format
+msgid ""
+"All application infrastructures are generally owned by a single party, "
+"systems using classical ACID transactions normally assume that participants "
+"in a transaction will obey the will of the transaction manager and only "
+"infrequently decide to make unilateral decisions which will hamper other "
+"participants in a transaction. On the contrary, Web services participating "
+"in a transaction can effectively decide to resign from the transaction at "
+"any time, and the consumer of the service generally has little in the way of "
+"quality of service guarantees to prevent this."
+msgstr ""
+"通常所有的应用程序基础结构都由单方所有，使用经典 ACID 事务的协调通常假设事务"
+"的参与者将遵从事务管理者，且只会偶尔执行阻碍事务里其他参与者的单方面决定。相"
+"反，参与事务的 Web 服务可以有效地决定在任何时候从事务退出，事务的消费者通常几"
+"乎没办法阻止这种情况的发生。"
+
+#. Tag: title
+#: Transactions_Overview.xml:274
+#, no-c-format
+msgid "Adressing the Problems of Transactioning in Loosely Coupled Systems"
+msgstr "解决松耦合系统里的事务问题"
+
+#. Tag: para
+#: Transactions_Overview.xml:275
+#, no-c-format
+msgid ""
+"Though extended transaction models which relax the ACID properties have been "
+"proposed over the years, to implement these concepts for the Web services "
+"architecture WS-T provides a new transaction protocol. XTS is designed to "
+"accommodate four underlying requirements inherent in any loosely coupled "
+"architecture like Web services:"
+msgstr ""
+"放松 ACID 属性的扩展事务模型已经计划了多年，为了实现用于 Web 服务架构的这些概"
+"念，WS-T 提供了一种的新的事务协议。XTS 的目的是满足任何松耦合架构如 Web 服务"
+"固有的 4 个底层要求："
+
+#. Tag: para
+#: Transactions_Overview.xml:281
+#, no-c-format
+msgid ""
+"Ability to handle multiple successful outcomes to a transaction, with the "
+"ability to involve operations whose effects may not be isolated or durable;"
+msgstr "处理事务的多个成功结果的能力，以及调用影响可能不是隔离的或持久的操作。"
+
+#. Tag: para
+#: Transactions_Overview.xml:286
+#, no-c-format
+msgid ""
+"Coordination of autonomous parties whose relationships are governed by "
+"contracts rather than the dictates of a central design authority;"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:291
+#, no-c-format
+msgid ""
+"Discontinuous service, where parties are anticipated to suffer outages "
+"during their lifetime, and coordinated work must be able to survive such "
+"outages;"
+msgstr ""
+
+#. Tag: para
+#: Transactions_Overview.xml:296
+#, no-c-format
+msgid ""
+"Interoperation using XML over multiple communication protocols – XTS chooses "
+"to use SOAP encoding carried over HTTP for the first release and other SOAP-"
+"friendly transports for future releases."
+msgstr ""
+"使用 XML 且基于多个通信协议的内部操作 - 在第一个版本里 XTS 选择基于 HTTP 的 "
+"SOAP 编码，在以后的版本里会使用方便 SOAP 的其他传输协议。"

Added: labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	                        (rev 0)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_4/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po	2009-03-17 02:41:09 UTC (rev 25676)
@@ -0,0 +1,1154 @@
+# translation of Stand-alone_Coordinator.po to
+# Language zh-CN translations for  package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Stand-alone_Coordinator\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-17 01:17+0000\n"
+"PO-Revision-Date: 2008-11-25 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:6
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Overview"
+msgstr "WS-C、WS-Atomic Transaction 和 WS-Business Activity 概述"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr "介绍"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:9
+#, no-c-format
+msgid ""
+"This section provides fundamental concepts associated with WS-C, WS-Atomic "
+"Transaction and WS-Business Activity. All of these concepts are defined in "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. WS-"
+"C, WS-Atomic Transaction and WS-Business Activity principles are discussed "
+"throughout this guide."
+msgstr ""
+"本节提供了和 WS-C、WS-Atomic Transaction 和 WS-Business Activity 相关的基本概"
+"念。所有这些概念都定义在 WS-C、WS-Atomic Transaction 和 WS-Business Activity "
+"的规格里。整本指南都将讨论 WS-C、WS-Atomic Transaction 和 WS-Business "
+"Activity 的原则。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:13
+#, no-c-format
+msgid ""
+"If you are well versed in the WS-C, WS-Atomic Transaction and WS-Business "
+"Activity specifications then you may want to just skim through this part of "
+"the manual."
+msgstr ""
+"如果你很熟悉 WS-C、WS-Atomic Transaction 和 WS-Business Activity 规格，那么你"
+"可以跳过这一部分。"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr "WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:21
+#, no-c-format
+msgid ""
+"In general terms, coordination is the act of one entity (known as the "
+"coordinator) disseminating information to a number of participants for some "
+"domain-specific reason. This reason could be in order to reach consensus on "
+"a decision like in a distributed transaction protocol, or simply to "
+"guarantee that all participants obtain a specific message, as occurs in a "
+"reliable multicast environment. When parties are being coordinated, "
+"information known as the coordination context is propagated to tie together "
+"operations which are logically part of the same coordinated work or "
+"activity. This context information may flow with normal application "
+"messages, or may be an explicit part of a message exchange and is specific "
+"to the type of coordination being performed."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:24
+#, no-c-format
+msgid ""
+"The fundamental idea underpinning WS-Coordination is that there is a generic "
+"need for a coordination infrastructure in a Web services environment. The WS-"
+"Coordination specification defines a framework that allows different "
+"coordination protocols to be plugged-in to coordinate work between clients, "
+"services and participants, as shown in Figure 4."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:27
+#, no-c-format
+msgid ""
+"At this level, an activity is minimally specified and is simply created, "
+"made to run, and then completed."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:34
+#, no-c-format
+msgid "WS-C architecture"
+msgstr "WS-C 的架构"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:36
+#, no-c-format
+msgid ""
+"Whatever coordination protocol is used, and in whatever domain it is "
+"deployed, the same generic requirements are present:"
+msgstr "不管使用什么协调协议，也不管部署在哪个域，都有着相同的要求："
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:41
+#, no-c-format
+msgid ""
+"Instantiation (or activation) of a new coordinator for the specific "
+"coordination protocol, for a particular application instance;"
+msgstr "为特定应用程序实例或为特殊的协调协议实例化（激活）新的协调者；"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:46
+#, no-c-format
+msgid ""
+"Registration of participants with the coordinator, such that they will "
+"receive that coordinator’s protocol messages during (some part of) the "
+"application’s lifetime;"
+msgstr ""
+"向协议者（coordinator）注册参与者，因此在应用程序的生存期间（某段期间）它们将"
+"接收协议者的协议消息。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:51
+#, no-c-format
+msgid ""
+"Propagation of contextual information between Web services that comprise the "
+"application;"
+msgstr "在组成应用程序的 Web 服务间传递上下文信息；"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:56
+#, no-c-format
+msgid "An entity to drive the coordination protocol through to completion."
+msgstr "驱动协调协议以至完成的实体。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:61
+#, no-c-format
+msgid ""
+"The first three of these points are directly the concern of WS-Coordination "
+"while the fourth is the responsibility of a third-party entity, usually the "
+"client application that controls the application as a whole. These four WS-"
+"Coordination roles and their interrelationships are shown in Figure 5."
+msgstr ""
+"这些要点里的头三点都和 WS-Coordination 直接相关，而第四点则负责第三方实体，通"
+"常是总体上控制应用程序的客户端应用程序。Figure 5 显示了这四个 WS-"
+"Coordination 作用及其相互关系。"
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr "WS-C 的基础结构"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:71
+#, no-c-format
+msgid "Activation"
+msgstr "激活"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:72
+#, no-c-format
+msgid ""
+"The WS-Coordination framework exposes an Activation Service which supports "
+"the creation of coordinators for specific protocols and their associated "
+"contexts. The process of invoking an activation service is done "
+"asynchronously, and so the specification defines both the interface of the "
+"activation service itself, and that of the invoking service, so that the "
+"activation service can call back to deliver the results of the activation – "
+"namely a context that identifies the protocol type and coordinator location. "
+"These interfaces are presented in Figure 6, where the activation service has "
+"a one-way operation that expects to receive a "
+"<code>CreateCoordinationContext</code> message and correspondingly the "
+"service that sent the <code>CreateCoordinationContext</code> message expects "
+"to be called back with a <code>CreateCoordinationContextResponse</code> "
+"message, or informed of a problem via an <code>Error</code> message."
+msgstr ""
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:76
+#, no-c-format
+msgid ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+msgstr ""
+"&lt;!-- Activation Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"CreateCoordinationContext\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContext\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Activation Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"ActivationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation \n"
+"                name=\"CreateCoordinationContextResponse\"&gt;\n"
+"                &lt;wsdl:input \n"
+"                message=\"wscoor:CreateCoordinationContextResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\\"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:78
+#, no-c-format
+msgid "Registration"
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:79
+#, no-c-format
+msgid ""
+"Once a coordinator has been instantiated and a corresponding context created "
+"by the activation service, a Registration Service is created and exposed. "
+"This service allows participants to register to receive protocol messages "
+"associated with a particular coordinator. Like the activation service, the "
+"registration service assumes asynchronous communication and so specifies "
+"WSDL for both registration service and registration requester, as shown "
+"below."
+msgstr ""
+
+#. Tag: screen
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:83
+#, no-c-format
+msgid ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+msgstr ""
+"&lt;!-- Registration Service portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationCoordinatorPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"Register\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Register\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;\n"
+"        \n"
+"&lt;!-- Registration Requester portType Declaration --&gt;\n"
+"&lt;wsdl:portType name=\"RegistrationRequesterPortType\"&gt;\n"
+"        &lt;wsdl:operation name=\"RegisterResponse\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:RegisterResponse\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"        &lt;wsdl:operation name=\"Error\"&gt;\n"
+"                &lt;wsdl:input message=\"wscoor:Error\"/&gt;\n"
+"        &lt;/wsdl:operation&gt;\n"
+"&lt;/wsdl:portType&gt;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:84
+#, no-c-format
+msgid ""
+"When a participant is registered with a coordinator through the registration "
+"service, it receives messages that the coordinator sends (for example, "
+"“prepare to complete” and “complete” messages if a two-phase protocol is "
+"used); where the coordinator’s protocol supports it, participants can also "
+"send messages back to the coordinator."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:88
+#, no-c-format
+msgid "Completion"
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:89
+#, no-c-format
+msgid ""
+"The role of terminator is generally played by the client application, which "
+"at an appropriate point will ask the coordinator to perform its particular "
+"coordination function with any registered participants – to drive the "
+"protocol through to its completion. On completion, the client application "
+"may be informed of an outcome for the activity which may vary from simple "
+"succeeded/failed notification through to complex structured data detailing "
+"the activity’s status."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:96
+#, fuzzy, no-c-format
+msgid "WS-Transaction"
+msgstr "ACID 事务"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:97
+#, no-c-format
+msgid ""
+"In the past, making traditional transaction systems talk to one another was "
+"a holy grail that was rarely achieved. With the advent of Web services, "
+"there is an opportunity to leverage an unparalleled interoperability "
+"technology to splice together existing transaction processing systems that "
+"already form the backbone of enterprise level applications."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:101
+#, fuzzy, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr "WS-Coordination"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:102
+#, no-c-format
+msgid ""
+"An important aspect of WS-Transaction that differentiates it from "
+"traditional transaction protocols is that a synchronous request/response "
+"model is not assumed. This model derives from the fact that WS-Transaction "
+"is, as shown in the figure below, layered upon the WS-Coordination protocol "
+"whose own communication patterns are asynchronous by default."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:110
+#, fuzzy, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr "WS-C、WS-Atomic Transaction 和 WS-Business Activity 概述"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:112
+#, no-c-format
+msgid ""
+"Web Services Coordination provides a generic framework for specific "
+"coordination protocols, like WS-Transaction, to be plugged in. Recall that "
+"WS-Coordination provides only context management – it allows contexts to be "
+"created and activities to be registered with those contexts. WS-Transaction "
+"leverages the context management framework provided by WS-Coordination in "
+"two ways. Firstly it extends the WS-Coordination context to create a "
+"transaction context. Secondly, it augments the activation and registration "
+"services with a number of additional services (Completion, "
+"CompletionWithAck, PhaseZero, 2PC, OutcomeNotification, BusinessAgreement, "
+"and BusinessAgreementWithComplete) and two protocol message sets (one for "
+"each of the transaction models supported in WS-Transaction) to build a fully-"
+"fledged transaction coordinator on top the WS-Coordination protocol "
+"infrastructure."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:116
+#, fuzzy, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr "WS-C 的架构"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:117
+#, no-c-format
+msgid ""
+"WS-Transaction supports the notion of the service and participant as "
+"distinct roles, making the distinction between a transaction-aware service "
+"and the participants that act on behalf of the service during a transaction: "
+"transactional services deal with business-level protocols, while the "
+"participants handle the underlying WS-Transaction protocols, as shown above."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:125
+#, fuzzy, no-c-format
+msgid "WS-Transaction Global View"
+msgstr "事务概述"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:127
+#, no-c-format
+msgid ""
+"A transaction-aware service encapsulates the business logic or work that is "
+"required to be conducted within the scope of a transaction. This work cannot "
+"be confirmed by the application unless the transaction also commits and so "
+"control is ultimately removed from the application and placed into the "
+"transaction’s domain."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:130
+#, no-c-format
+msgid ""
+"The participant is the entity that, under the dictates of the transaction "
+"coordinator, controls the outcome of the work performed by the transaction-"
+"aware Web service. In the figure above each service is shown with one "
+"associated participant that manages the transaction protocol messages on "
+"behalf of its service, while in the figure below, there is a close-up view "
+"of a single service, and a client application with their associated "
+"participants."
+msgstr ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:137
+#, fuzzy, no-c-format
+msgid "Transactional Service and Participant"
+msgstr "事务性 Web 服务"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:139
+#, no-c-format
+msgid ""
+"The transaction-aware Web service and its participant both serve a shared "
+"transactional resource, and there is a control relationship between them "
+"through some API - which on the Java platform is JAXTX. In the example shown "
+"in the figure above, it is assumed that the database is accessed through a "
+"transactional JDBC database driver, where SQL statements are sent to the "
+"database for processing via that driver, but where those statements will be "
+"tentative and only commit if the transaction does. In order to do this, the "
+"driver/database will associate a participant with the transaction which will "
+"inform the database of the transaction outcome. Since all transactional "
+"invocations on the Web service carry a transaction context, the participant "
+"working with the database is able to identify the work that the "
+"transactional service did within the scope of a specific transaction and "
+"either commit or rollback the work."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:142
+#, no-c-format
+msgid ""
+"At the client end, things are less complex. Through its API, the client "
+"application registers a participant with the transaction through which it "
+"controls transaction termination."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:146
+#, fuzzy, no-c-format
+msgid "WS-Transaction Models"
+msgstr "ACID 事务"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:147
+#, no-c-format
+msgid ""
+"Given that traditional transaction models are not appropriate for Web "
+"services, the following question must be posed, “what type of model or "
+"protocol is appropriate?” The answer to that question is that that no one "
+"specific protocol is likely to be sufficient, given the wide range of "
+"situations that Web service transactions are likely to be deployed within. "
+"Hence the WS-Transaction specification proposes two distinct models, where "
+"each supports the semantics of a particular kind of B2B interaction. The "
+"following sections shall discuss these two WS-Transaction models."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:152
+#, no-c-format
+msgid ""
+"As with WS-Coordination, the two WS-Transaction models are extensible "
+"allowing implementations to tailor the protocols as they see fit (for "
+"example, to suit their deployment environments)."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:157
+#, fuzzy, no-c-format
+msgid "Atomic Transactions (AT)"
+msgstr "ACID 事务"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:158
+#, no-c-format
+msgid ""
+"An atomic transaction or AT is similar to traditional ACID transactions and "
+"intended to support short-duration interactions where ACID semantics are "
+"appropriate. Within the scope of an AT, services typically enroll "
+"transaction-aware resources, such as databases and message queues, "
+"indirectly as participants under the control of the transaction. When the "
+"transaction terminates, the outcome decision of the AT is then propagated to "
+"each enlisted resource via the participant, and the appropriate commit or "
+"rollback actions are taken by each."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:162
+#, no-c-format
+msgid ""
+"This protocol is very similar to those employed by traditional transaction "
+"systems that already form the backbone of an enterprise. It is assumed that "
+"all services (and associated participants) provide ACID semantics and that "
+"any use of atomic transactions occurs in environments and situations where "
+"this is appropriate: in a trusted domain, over short durations."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:165
+#, no-c-format
+msgid ""
+"To begin an atomic transaction, the client application firstly locates a WS-"
+"Coordination coordinator Web service that supports WS-Transaction. Once "
+"located, the client sends a WS-Coordination CreateCoordinationContext "
+"message to the activation service specifying http://schemas.xmlsoap.org/"
+"ws/2004/10/wsat as its coordination type and will get back an appropriate WS-"
+"Transaction context from the activation service. The response to the "
+"CreateCoordinationContext message, the transaction context, has its "
+"CoordinationType element set to the WS-Atomic Transaction namespace, http://"
+"schemas.xmlsoap.org/ws/2004/10/wsat, and also contains a reference to the "
+"atomic transaction coordinator endpoint (the WS-Coordination registration "
+"service) where participants can be enlisted."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:168
+#, no-c-format
+msgid ""
+"After obtaining a transaction context from the coordinator, the client "
+"application then proceeds to interact with Web services to accomplish its "
+"business-level work. With each invocation on a business Web service, the "
+"client inserts the transaction context into a SOAP header block, such that "
+"each invocation is implicitly scoped by the transaction – the toolkits that "
+"support WS-Atomic Transaction-aware Web services provide facilities to "
+"correlate contexts found in SOAP header blocks with back-end operations."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:171
+#, no-c-format
+msgid ""
+"Once all the necessary application level work has been completed, the client "
+"can terminate the transaction, with the intent of making any changes to the "
+"service state permanent. To do this, the client application first registers "
+"its own participant for the Completion protocol. Once registered, the "
+"participant can instruct the coordinator either to try to commit or rollback "
+"the transaction. When the commit or rollback operation has completed, a "
+"status is returned to the participant to indicate the outcome of the "
+"transaction."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:174
+#, no-c-format
+msgid ""
+"While the completion protocol is straightforward, they hide the fact that in "
+"order to resolve to an outcome that several other protocols need to be "
+"executed."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:177
+#, no-c-format
+msgid ""
+"The first of these protocols is the optional Volatile2PC. The Volatile2PC "
+"protocol is the WS-Atomic Transaction equivalent of the synchronization "
+"protocol we discussed earlier. It is typically executed where a Web service "
+"needs to flush volatile (cached) state, which may be being used to improve "
+"performance of an application, to a database prior to the transaction "
+"committing. Once flushed, the data will then be controlled by a two-phase "
+"aware participant."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:180
+#, no-c-format
+msgid ""
+"All Volatile2PC participants are told that the transaction is about to "
+"complete (via the prepare message) and they can respond with either the "
+"prepared, aborted or readonly message; any failures at this stage will cause "
+"the transaction to rollback."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:183
+#, no-c-format
+msgid ""
+"After Volatile2PC prepare, the next protocol to execute in WS-Atomic "
+"Transaction is Durable2PC. The Durable2PC (an abbreviation of the term two-"
+"phase commit) protocol is at the very heart of WS-Atomic Transaction and is "
+"used to bring about the necessary consensus between participants in a "
+"transaction such that the transaction can safely be terminated."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:186
+#, no-c-format
+msgid ""
+"The two-phase commit protocol is used to ensure atomicity between "
+"participants, and is based on the classic two-phase commit with presumed "
+"abort technique. During the first phase, when the coordinator sends the "
+"prepare message, a participant must make durable any state changes that "
+"occurred during the scope of the transaction, such that these changes can "
+"either be rolled back or committed later. That is, any original state must "
+"not be lost at this point as the atomic transaction could still roll back. "
+"If the participant cannot prepare then it must inform the coordinator (via "
+"the aborted message) and the transaction will ultimately roll back. If the "
+"participant is responsible for a service that did not do any work during the "
+"course of the transaction, or at least did not do any work that modified any "
+"state, it can return the readonly message and it will be omitted from the "
+"second phase of the commit protocol. Otherwise, the prepared message is sent "
+"by the participant."
+msgstr ""
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:189
+#, no-c-format
+msgid ""
+"Assuming no failures occurred during the first phase, in the second phase "
+"the coordinator sends the commit message to participants, who will make "
+"permanent the tentative work done by their associated services."
+msgstr ""
+"Assuming no failures occurred during the first phase, in the second phase "
+"the coordinator sends the commit message to participants, who will make "
+"permanent the tentative work done by their associated services."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:192
+#, no-c-format
+msgid ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
+msgstr ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:195
+#, no-c-format
+msgid ""
+"The figure below<footnote> <para> Redrawn from the WS-Atomic Transaction "
+"specification. </para> </footnote> shows the state transitions of a WS-"
+"Atomic Transaction and the message exchanges between coordinator and "
+"participant; the coordinator generated messages are shown in the solid line, "
+"whereas the participant messages are shown by dashed lines."
+msgstr ""
+"The figure below<footnote> <para> Redrawn from the WS-Atomic Transaction "
+"specification. </para> </footnote> shows the state transitions of a WS-"
+"Atomic Transaction and the message exchanges between coordinator and "
+"participant; the coordinator generated messages are shown in the solid line, "
+"whereas the participant messages are shown by dashed lines."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:206
+#, fuzzy, no-c-format
+msgid "Two-Phase Commit State Transitions"
+msgstr "两阶段提交"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:208
+#, no-c-format
+msgid ""
+"Once the 2PC protocol has finished, the Completion protocol that originally "
+"began the termination of the transaction can complete, and inform the client "
+"application whether the transaction was committed or rolled back. "
+"Additionally, the Volatile2PC protocol may complete."
+msgstr ""
+"Once the 2PC protocol has finished, the Completion protocol that originally "
+"began the termination of the transaction can complete, and inform the client "
+"application whether the transaction was committed or rolled back. "
+"Additionally, the Volatile2PC protocol may complete."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:211
+#, no-c-format
+msgid ""
+"Like the prepare phase of Volatile2PC, the final phase is optional and can "
+"be used to inform participants when the transaction has completed, typically "
+"so that they can release resources (for example, put a database connection "
+"back into the pool of connections)."
+msgstr ""
+"Like the prepare phase of Volatile2PC, the final phase is optional and can "
+"be used to inform participants when the transaction has completed, typically "
+"so that they can release resources (for example, put a database connection "
+"back into the pool of connections)."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:214
+#, no-c-format
+msgid ""
+"Any registered Volatile2PC participants are invoked after the transaction "
+"has terminated and are told the state in which the transaction completed "
+"(the coordinator sends either the Committed or Aborted message). Since the "
+"transaction has terminated, any failures of participants at this stage are "
+"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
+"the transaction."
+msgstr ""
+"Any registered Volatile2PC participants are invoked after the transaction "
+"has terminated and are told the state in which the transaction completed "
+"(the coordinator sends either the Committed or Aborted message). Since the "
+"transaction has terminated, any failures of participants at this stage are "
+"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
+"the transaction."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:217
+#, no-c-format
+msgid ""
+"Finally, after having gone through each of the stages in an AT, it is "
+"possible to see the intricate interweaving of individual protocols that goes "
+"to make up the AT as a whole in the following figure."
+msgstr ""
+"Finally, after having gone through each of the stages in an AT, it is "
+"possible to see the intricate interweaving of individual protocols that goes "
+"to make up the AT as a whole in the following figure."
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:224
+#, no-c-format
+msgid "The AT Model"
+msgstr "AT 模型"
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:227
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr "商业活动（Business Activities，BA）"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:228
+#, no-c-format
+msgid ""
+"Most business-to-business applications require transactional support in "
+"order to guarantee consistent outcome and correct execution. These "
+"applications often involve long running computations, loosely coupled "
+"systems and components that do not share data, location, or administration "
+"and it is difficult to incorporate atomic transactions within such "
+"architectures. For example, an online bookshop may reserve books for an "
+"individual for a specific period of time, but if the individual does not "
+"purchase the books within that period they will be “put back onto the shelf” "
+"for others to buy. Furthermore, because it is not possible for anyone to "
+"have an infinite supply of stock, some online shops may appear to users to "
+"reserve items for them, but in fact may allow others to pre-empt that "
+"reservation (for instance, the same book may be “reserved” for multiple "
+"users concurrently); a user may subsequently find that the item is no longer "
+"available, or may have to be reordered specially for them."
+msgstr ""
+"Most business-to-business applications require transactional support in "
+"order to guarantee consistent outcome and correct execution. These "
+"applications often involve long running computations, loosely coupled "
+"systems and components that do not share data, location, or administration "
+"and it is difficult to incorporate atomic transactions within such "
+"architectures. For example, an online bookshop may reserve books for an "
+"individual for a specific period of time, but if the individual does not "
+"purchase the books within that period they will be “put back onto the shelf” "
+"for others to buy. Furthermore, because it is not possible for anyone to "
+"have an infinite supply of stock, some online shops may appear to users to "
+"reserve items for them, but in fact may allow others to pre-empt that "
+"reservation (for instance, the same book may be “reserved” for multiple "
+"users concurrently); a user may subsequently find that the item is no longer "
+"available, or may have to be reordered specially for them."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:232
+#, no-c-format
+msgid ""
+"A business activity or BA is designed specifically for these kinds of long-"
+"duration interactions, where exclusively locking resources is impossible or "
+"impractical. In this model services are requested to do work, and where "
+"those services have the ability to undo any work, they inform the BA such "
+"that if the BA later decides the cancel the work (for instance if the "
+"business activity suffers a failure), it can instruct the service to execute "
+"its undo behavior. The key point for Business Activities is that how "
+"services do their work and provide compensation mechanisms is not the domain "
+"of the WS-Business Activity specification, but an implementation decision "
+"for the service provider."
+msgstr ""
+"A business activity or BA is designed specifically for these kinds of long-"
+"duration interactions, where exclusively locking resources is impossible or "
+"impractical. In this model services are requested to do work, and where "
+"those services have the ability to undo any work, they inform the BA such "
+"that if the BA later decides the cancel the work (for instance if the "
+"business activity suffers a failure), it can instruct the service to execute "
+"its undo behavior. The key point for Business Activities is that how "
+"services do their work and provide compensation mechanisms is not the domain "
+"of the WS-Business Activity specification, but an implementation decision "
+"for the service provider."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:235
+#, no-c-format
+msgid ""
+"The WS- Business Activity simply defines a protocol for Web services-based "
+"applications to enable existing business processing and workflow systems to "
+"wrap their proprietary mechanisms and interoperate across implementations "
+"and business boundaries."
+msgstr ""
+"The WS- Business Activity simply defines a protocol for Web services-based "
+"applications to enable existing business processing and workflow systems to "
+"wrap their proprietary mechanisms and interoperate across implementations "
+"and business boundaries."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:238
+#, no-c-format
+msgid ""
+"A business activity may be partitioned into scopes, where a scope is a "
+"business task or unit of work using a collection of Web services. Such "
+"scopes can be nested to arbitrary degrees, forming parent and child "
+"relationships, where a parent scope has the ability to select which child "
+"tasks are to be included in the overall outcome protocol for a specific "
+"business activity, and so clearly non-atomic outcomes are possible. In a "
+"similar manner to traditional nested transactions, if a child task "
+"experiences an error, it can be caught by the parent who may be able to "
+"compensate and continue processing."
+msgstr ""
+"A business activity may be partitioned into scopes, where a scope is a "
+"business task or unit of work using a collection of Web services. Such "
+"scopes can be nested to arbitrary degrees, forming parent and child "
+"relationships, where a parent scope has the ability to select which child "
+"tasks are to be included in the overall outcome protocol for a specific "
+"business activity, and so clearly non-atomic outcomes are possible. In a "
+"similar manner to traditional nested transactions, if a child task "
+"experiences an error, it can be caught by the parent who may be able to "
+"compensate and continue processing."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:241
+#, no-c-format
+msgid ""
+"When a child task completes it can either leave the business activity or "
+"signal to the parent that the work it has done can be compensated later. In "
+"the latter case, the compensation task may be called by the parent should it "
+"ultimately need to undo the work performed by the child."
+msgstr ""
+"When a child task completes it can either leave the business activity or "
+"signal to the parent that the work it has done can be compensated later. In "
+"the latter case, the compensation task may be called by the parent should it "
+"ultimately need to undo the work performed by the child."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:244
+#, no-c-format
+msgid ""
+"Unlike the WS-Atomic Transaction protocol model, where participants inform "
+"the coordinator of their state only when asked, a task within a business "
+"activity can specify its outcome to the parent directly without waiting for "
+"a request. This feature is useful when tasks fail such that the notification "
+"can be used by business activity exception handler to modify the goals and "
+"drive processing forward without having to meekly wait until the end of the "
+"transaction to admit to having failed – a well designed Business Activities "
+"should be proactive, if it is to perform well."
+msgstr ""
+"Unlike the WS-Atomic Transaction protocol model, where participants inform "
+"the coordinator of their state only when asked, a task within a business "
+"activity can specify its outcome to the parent directly without waiting for "
+"a request. This feature is useful when tasks fail such that the notification "
+"can be used by business activity exception handler to modify the goals and "
+"drive processing forward without having to meekly wait until the end of the "
+"transaction to admit to having failed – a well designed Business Activities "
+"should be proactive, if it is to perform well."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:247
+#, no-c-format
+msgid "Underpinning all of this are three fundamental assumptions:"
+msgstr "Underpinning all of this are three fundamental assumptions:"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:252
+#, no-c-format
+msgid ""
+"All state transitions are reliably recorded, including application state and "
+"coordination metadata (the record of sent and received messages);"
+msgstr ""
+"All state transitions are reliably recorded, including application state and "
+"coordination metadata (the record of sent and received messages);"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:257
+#, no-c-format
+msgid ""
+"All request messages are acknowledged, so that problems are detected as "
+"early as possible. This avoids executing unnecessary tasks and can also "
+"detect a problem earlier when rectifying it is simpler and less expensive;"
+msgstr ""
+"All request messages are acknowledged, so that problems are detected as "
+"early as possible. This avoids executing unnecessary tasks and can also "
+"detect a problem earlier when rectifying it is simpler and less expensive;"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:262
+#, no-c-format
+msgid ""
+"As with atomic transactions, a response is defined as a separate operation "
+"and not as the output of the request. Message input-output implementations "
+"will typically have timeouts that are too short for some business activity "
+"responses. If the response is not received after a timeout, it is resent. "
+"This is repeated until a response is received. The request receiver discards "
+"all but one identical request received."
+msgstr ""
+"As with atomic transactions, a response is defined as a separate operation "
+"and not as the output of the request. Message input-output implementations "
+"will typically have timeouts that are too short for some business activity "
+"responses. If the response is not received after a timeout, it is resent. "
+"This is repeated until a response is received. The request receiver discards "
+"all but one identical request received."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:267
+#, no-c-format
+msgid ""
+"As with atomic transactions, the business activity model has multiple "
+"protocols: <code>BusinessAgreementWithParticipantCompletion</code> and "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. However, unlike the "
+"AT protocol which is driven from the coordinator down to participants, this "
+"protocol is driven much more from the participants upwards."
+msgstr ""
+"As with atomic transactions, the business activity model has multiple "
+"protocols: <code>BusinessAgreementWithParticipantCompletion</code> and "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. However, unlike the "
+"AT protocol which is driven from the coordinator down to participants, this "
+"protocol is driven much more from the participants upwards."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
+#, no-c-format
+msgid ""
+"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
+"a child activity is initially created in the Active state; if it finishes "
+"the work it was created to do and no more participation is required within "
+"the scope of the BA (such as when the activity operates on immutable data), "
+"then the child can unilaterally send an exited message to the parent. "
+"However, if the child task finishes and wishes to continue in the BA then it "
+"must be able to compensate for the work it has performed. In this case it "
+"sends a completed message to the parent and waits to receive the final "
+"outcome of the BA from the parent. This outcome will either be a close "
+"message, meaning the BA has completed successfully or a compensate message "
+"indicating that the parent activity requires that the child task reverse its "
+"work."
+msgstr ""
+"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
+"a child activity is initially created in the Active state; if it finishes "
+"the work it was created to do and no more participation is required within "
+"the scope of the BA (such as when the activity operates on immutable data), "
+"then the child can unilaterally send an exited message to the parent. "
+"However, if the child task finishes and wishes to continue in the BA then it "
+"must be able to compensate for the work it has performed. In this case it "
+"sends a completed message to the parent and waits to receive the final "
+"outcome of the BA from the parent. This outcome will either be a close "
+"message, meaning the BA has completed successfully or a compensate message "
+"indicating that the parent activity requires that the child task reverse its "
+"work."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
+#, no-c-format
+msgid ""
+"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
+"identical to the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol with the exception that the child cannot autonomously decide to end "
+"its participation in the business activity, even if it can be compensated. "
+"Rather the child task relies upon the parent to inform it when the child has "
+"received all requests for it to perform work which the parent does by "
+"sending the complete message to the child. The child then acts as it does in "
+"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
+msgstr ""
+"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
+"identical to the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol with the exception that the child cannot autonomously decide to end "
+"its participation in the business activity, even if it can be compensated. "
+"Rather the child task relies upon the parent to inform it when the child has "
+"received all requests for it to perform work which the parent does by "
+"sending the complete message to the child. The child then acts as it does in "
+"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:276
+#, no-c-format
+msgid ""
+"The crux of the BA model compared to the AT model is that is allows the "
+"participation of services that cannot or will not lock resources for "
+"extended periods."
+msgstr ""
+"The crux of the BA model compared to the AT model is that is allows the "
+"participation of services that cannot or will not lock resources for "
+"extended periods."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:279
+#, no-c-format
+msgid ""
+"While the full ACID semantics are not maintained by a BA, consistency can "
+"still be maintained through compensation, though the task of writing correct "
+"compensating actions (and thus overall system consistency) is delegated to "
+"the developers of the services under control of the BA. Such compensations "
+"may use backward error recovery, but will typically employ forward recovery."
+msgstr ""
+"While the full ACID semantics are not maintained by a BA, consistency can "
+"still be maintained through compensation, though the task of writing correct "
+"compensating actions (and thus overall system consistency) is delegated to "
+"the developers of the services under control of the BA. Such compensations "
+"may use backward error recovery, but will typically employ forward recovery."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:283
+#, no-c-format
+msgid "Application Messages"
+msgstr "应用程序消息"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:284
+#, no-c-format
+msgid ""
+"Application messages are the requests and responses that are sent between "
+"parties that constitute the work of a business process. Any such messages "
+"are considered opaque by XTS, and there is no mandatory message format, "
+"protocol binding, or encoding style so the developer is free to use any "
+"appropriate Web services protocol. In XTS, the transaction context is "
+"propagated within the headers of SOAP messages."
+msgstr ""
+"应用程序消息是在组成商业过程的行为各方间传递的请求和响应。XTS 把任何这样的消"
+"息都认为是不透明的，不存在强制的消息格式、协议绑定或编码风格，所以开发人员可"
+"以自由地使用任何合适的 Web 服务协议。在 XTS 里，事务上下文是在 SOAP 消息的头"
+"部进行传递的。"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:289
+#, no-c-format
+msgid ""
+"XTS provides out-of-box support for service developers building WS-T-aware "
+"services on the JBoss, Weblogic and Glue platforms1. The provision of "
+"interceptors for automatic context handling at both client and service "
+"significantly simplifies the developer’s workload, allowing the developer to "
+"concentrate on writing the business logic without having to worry about the "
+"transactional infrastructure getting in the way. The interceptors simply add "
+"and remove context elements to application messages without altering the "
+"semantics of those messages. Any service which understands what to do with a "
+"WS-C context can use it, services which do not understand the context (those "
+"services that are not WS-C, WS-Atomic Transaction and WS-Business Activity-"
+"aware) may ignore the context; the important point here is that XTS manages "
+"contexts without user intervention."
+msgstr ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:294
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:295
+#, no-c-format
+msgid ""
+"Although the application or service developer rarely sees or is interested "
+"in the messages exchanged by the transactional infrastructure (the "
+"transaction manager and any participants), it is useful to understand what "
+"kinds of exchanges occur so that the underlying model can be fitted in to an "
+"overall architecture."
+msgstr ""
+"Although the application or service developer rarely sees or is interested "
+"in the messages exchanged by the transactional infrastructure (the "
+"transaction manager and any participants), it is useful to understand what "
+"kinds of exchanges occur so that the underlying model can be fitted in to an "
+"overall architecture."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:299
+#, no-c-format
+msgid ""
+"In XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific "
+"messages are transported using SOAP messaging over HTTP. The types of "
+"messages that are propagated include instructions to perform standard "
+"transaction operations like begin, prepare."
+msgstr ""
+"In XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific "
+"messages are transported using SOAP messaging over HTTP. The types of "
+"messages that are propagated include instructions to perform standard "
+"transaction operations like begin, prepare."
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:303
+#, no-c-format
+msgid ""
+"XTS messages do not interfere in any way, shape, or form, with the "
+"application messages, and nor is there any requirement for an application to "
+"use the same transport as the transaction-specific messages. For example, it "
+"is quite reasonable for a client application to deliver its application-"
+"specific messages using SOAP RPC over SMTP even though under the covers the "
+"XTS messages are delivered using a different mechanism."
+msgstr ""
+"XTS messages do not interfere in any way, shape, or form, with the "
+"application messages, and nor is there any requirement for an application to "
+"use the same transport as the transaction-specific messages. For example, it "
+"is quite reasonable for a client application to deliver its application-"
+"specific messages using SOAP RPC over SMTP even though under the covers the "
+"XTS messages are delivered using a different mechanism."
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:310
+#, no-c-format
+msgid "Summary"
+msgstr "总结"
+
+#. Tag: para
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:311
+#, no-c-format
+msgid ""
+"XTS provides a coordination infrastructure designed to allow transactions to "
+"run between enterprises across the Internet. That infrastructure is based on "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. It "
+"supports two kinds of transactions: atomic transactions and business "
+"activities, which can be combined in arbitrary ways to map elegantly onto "
+"the transactional requirements of the underlying problem. The use of the "
+"whole infrastructure is simple due to the fact that its functionality is "
+"exposed through a simple transactioning API. Furthermore XTS provides all of "
+"the necessary plumbing to keep application and transactional aspects of an "
+"application separate, and to ensure that the transactionality of a system "
+"does not interfere with the functional aspects of the system itself."
+msgstr ""
+"XTS provides a coordination infrastructure designed to allow transactions to "
+"run between enterprises across the Internet. That infrastructure is based on "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. It "
+"supports two kinds of transactions: atomic transactions and business "
+"activities, which can be combined in arbitrary ways to map elegantly onto "
+"the transactional requirements of the underlying problem. The use of the "
+"whole infrastructure is simple due to the fact that its functionality is "
+"exposed through a simple transactioning API. Furthermore XTS provides all of "
+"the necessary plumbing to keep application and transactional aspects of an "
+"application separate, and to ensure that the transactionality of a system "
+"does not interfere with the functional aspects of the system itself."