[jboss-cvs] JBossAS SVN: r78771 - in projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide: de-DE and 6 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Sep 23 02:35:15 EDT 2008
Author: xhuang at jboss.com
Date: 2008-09-23 02:35:15 -0400 (Tue, 23 Sep 2008)
New Revision: 78771
Added:
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Getting_Started.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Introduction.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/JBoss_Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Participants.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Stand-alone_Coordinator.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/The_XTS_API.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactional_Web_Services.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Getting_Started.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Introduction.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/JBoss_Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Participants.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Stand-alone_Coordinator.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/The_XTS_API.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactional_Web_Services.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Getting_Started.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Introduction.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/JBoss_Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Participants.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Stand-alone_Coordinator.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/The_XTS_API.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactional_Web_Services.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Getting_Started.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Introduction.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/JBoss_Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Participants.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Stand-alone_Coordinator.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/The_XTS_API.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactional_Web_Services.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Appendix.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Getting_Started.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Introduction.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/JBoss_Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Participants.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Stand-alone_Coordinator.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/The_XTS_API.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactional_Web_Services.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Web_Services_Programmers_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
Modified:
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/Makefile
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Getting_Started.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Introduction.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Stand-alone_Coordinator.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/The_XTS_API.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactional_Web_Services.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Author_Group.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Book_Info.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Getting_Started.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Introduction.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Participants.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Preface.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Revision_History.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Stand-alone_Coordinator.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/The_XTS_API.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Transactional_Web_Services.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Transactions_Overview.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.pot
projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/messages.mo
Log:
merge
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/Makefile
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/Makefile 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/Makefile 2008-09-23 06:35:15 UTC (rev 78771)
@@ -5,7 +5,7 @@
BRAND = JBoss
#OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW
-OTHER_LANGS = ja-JP
+OTHER_LANGS = de-DE es-ES fr-FR ja-JP pt-BR zh-CN
COMMON_CONFIG = /usr/share/publican
include $(COMMON_CONFIG)/make/Makefile.common
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Appendix.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"PO-Revision-Date: 2008-09-01 01:36+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Author_Group.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Book_Info.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,44 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Getting_Started.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Getting_Started.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,191 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Introduction.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Introduction.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Introduction.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,273 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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'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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/JBoss_Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Participants.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Participants.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Participants.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,457 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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
+#, 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Preface.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Revision_History.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,26 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Stand-alone_Coordinator.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Stand-alone_Coordinator.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Stand-alone_Coordinator.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,34 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/The_XTS_API.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/The_XTS_API.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/The_XTS_API.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,547 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, 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
+#, no-c-format
+msgid "TransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactional_Web_Services.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactional_Web_Services.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactional_Web_Services.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,106 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,654 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions_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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/de-DE/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,950 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr ""
+
+#. 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 ""
+"<!-- Activation Service portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"CreateCoordinationContext\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContext\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Activation Requester portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationRequesterPortType\">\n"
+" <wsdl:operation \n"
+" name=\"CreateCoordinationContextResponse\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContextResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\\"
+msgstr ""
+
+#. 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 ""
+"<!-- Registration Service portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"Register\">\n"
+" <wsdl:input message=\"wscoor:Register\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Registration Requester portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationRequesterPortType\">\n"
+" <wsdl:operation name=\"RegisterResponse\">\n"
+" <wsdl:input message=\"wscoor:RegisterResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr ""
+
+#. 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
+#, 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Appendix.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"PO-Revision-Date: 2008-09-01 01:36+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Author_Group.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Book_Info.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,44 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Getting_Started.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Getting_Started.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,191 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Introduction.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Introduction.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Introduction.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,273 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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'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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/JBoss_Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Participants.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Participants.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Participants.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,457 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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
+#, 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Preface.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Revision_History.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,26 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Stand-alone_Coordinator.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Stand-alone_Coordinator.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Stand-alone_Coordinator.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,34 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/The_XTS_API.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/The_XTS_API.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/The_XTS_API.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,547 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, 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
+#, no-c-format
+msgid "TransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactional_Web_Services.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactional_Web_Services.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactional_Web_Services.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,106 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,654 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions_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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/es-ES/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,950 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr ""
+
+#. 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 ""
+"<!-- Activation Service portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"CreateCoordinationContext\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContext\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Activation Requester portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationRequesterPortType\">\n"
+" <wsdl:operation \n"
+" name=\"CreateCoordinationContextResponse\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContextResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\\"
+msgstr ""
+
+#. 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 ""
+"<!-- Registration Service portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"Register\">\n"
+" <wsdl:input message=\"wscoor:Register\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Registration Requester portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationRequesterPortType\">\n"
+" <wsdl:operation name=\"RegisterResponse\">\n"
+" <wsdl:input message=\"wscoor:RegisterResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr ""
+
+#. 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
+#, 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Appendix.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"PO-Revision-Date: 2008-09-01 01:36+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Author_Group.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Book_Info.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,44 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Getting_Started.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Getting_Started.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,191 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Introduction.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Introduction.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Introduction.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,273 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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'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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/JBoss_Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Participants.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Participants.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Participants.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,457 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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
+#, 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Preface.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Revision_History.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,26 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Stand-alone_Coordinator.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Stand-alone_Coordinator.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Stand-alone_Coordinator.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,34 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/The_XTS_API.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/The_XTS_API.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/The_XTS_API.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,547 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, 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
+#, no-c-format
+msgid "TransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactional_Web_Services.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactional_Web_Services.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactional_Web_Services.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,106 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,654 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions_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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/fr-FR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,950 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr ""
+
+#. 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 ""
+"<!-- Activation Service portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"CreateCoordinationContext\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContext\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Activation Requester portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationRequesterPortType\">\n"
+" <wsdl:operation \n"
+" name=\"CreateCoordinationContextResponse\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContextResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\\"
+msgstr ""
+
+#. 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 ""
+"<!-- Registration Service portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"Register\">\n"
+" <wsdl:input message=\"wscoor:Register\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Registration Requester portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationRequesterPortType\">\n"
+" <wsdl:operation name=\"RegisterResponse\">\n"
+" <wsdl:input message=\"wscoor:RegisterResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr ""
+
+#. 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
+#, 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Book_Info.po 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Book_Info.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Book_Info\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: 2008-09-05 08:47+1000\n"
"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
"Language-Team: Japanese <jp at li.org>\n"
@@ -18,31 +18,32 @@
#. Tag: title
#: Book_Info.xml:6
-#, no-c-format
-msgid "Transactions Web Services Programmers Guide"
+#, fuzzy, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide"
msgstr "トランザクション Web サービスプログラマガイド"
#. Tag: subtitle
#: Book_Info.xml:7
-#, no-c-format
-msgid "JBoss Enterprise Application Platform"
+#, fuzzy, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
msgstr "JBoss Enterprise Application Platform"
#. Tag: para
-#: Book_Info.xml:11
+#: Book_Info.xml:13
#, no-c-format
msgid "This book is about Programming for Transaction Web Services"
-msgstr "このマニュアルはトランザクション Web サービスの為のプログラミングを説明しています。"
+msgstr ""
+"このマニュアルはトランザクション Web サービスの為のプログラミングを説明してい"
+"ます。"
#. Tag: phrase
-#: Book_Info.xml:18
+#: Book_Info.xml:20
#, no-c-format
msgid "Logo"
msgstr "ロゴ"
#. Tag: holder
-#: Book_Info.xml:24
+#: Book_Info.xml:26
#, no-c-format
msgid "&HOLDER;"
msgstr "&HOLDER;"
-
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Getting_Started.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Getting_Started.po 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Getting_Started.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Getting_Started\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: 2008-09-17 17:14+1000\n"
"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
"Language-Team: Japanese <jp at li.org>\n"
@@ -23,13 +23,13 @@
msgstr "さあ始めましょう"
#. Tag: title
-#: Getting_Started.xml:10
+#: Getting_Started.xml:8
#, no-c-format
msgid "Creating and deploying participants"
msgstr "パーティシパントの作成とデプロイ"
#. Tag: para
-#: Getting_Started.xml:11
+#: Getting_Started.xml:9
#, no-c-format
msgid ""
"A participant is a software entity which is driven by the transaction "
@@ -46,25 +46,28 @@
"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>。"
+"パーティシパントとは、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:17
+#: Getting_Started.xml:15
#, no-c-format
msgid "Creating Client Applications"
msgstr "クライアントアプリケーションの作成"
#. Tag: para
-#: Getting_Started.xml:18
+#: Getting_Started.xml:16
#, no-c-format
msgid ""
"There are two aspects to a client application using XTS. The first is the "
@@ -77,15 +80,15 @@
"manager."
msgstr ""
"XTS を使用するクライアントアプリケーションには２つの側面があります。１つめは "
-"トランザクション宣言の側面で、２つめはそのクライアントアプリケーションが実行する "
-"ビジネス論理の側面です。トランザクション宣言の側面は XTS のクライアント API に "
-"よって自動的に担当されています。この API が、begin、commit、rollback などの "
-"簡単なトランザクションディレクティブを提供して、それをクライアントがトランザクションの "
-"始動、管理、終了のために使用できます。表面下では API が（SOAP 経由で）トランザクション "
-"マネージャ上のオペレーションを呼び出します。"
+"トランザクション宣言の側面で、２つめはそのクライアントアプリケーションが実行"
+"する ビジネス論理の側面です。トランザクション宣言の側面は XTS のクライアント "
+"API に よって自動的に担当されています。この API が、begin、commit、rollback "
+"などの 簡単なトランザクションディレクティブを提供して、それをクライアントがト"
+"ランザクションの 始動、管理、終了のために使用できます。表面下では API が"
+"（SOAP 経由で）トランザクション マネージャ上のオペレーションを呼び出します。"
#. Tag: para
-#: Getting_Started.xml:21
+#: Getting_Started.xml:19
#, no-c-format
msgid ""
"When the client application performs invocations on business logic Web "
@@ -97,17 +100,17 @@
"automatically. These filters are designed to work with JAX-RPC and "
"webMethods client libraries."
msgstr ""
-"クライアントアプリケーションが、ビジネス論理 Web サービス上で呼び出しを "
-"実行すると、XTS はその目的では API に指示しません。しかし、選択される "
-"API の種類に関係無く、XTS コンテキストが発信メッセージに挿入されて、 "
-"来信メッセージ用に取り出されて現在のスレッドと関連づけされる必要性が "
-"あります。これをユーザーの為に簡単にするために、XTS ソフトウェアは、この "
-"タスクを自動的に実行できるフィルターの３つのセットを付けて配布されています。 "
-"これらのフィルターは JAX-RPC と webMethods のクライアントライブラリを "
-"使用して機能するように設計されています。"
+"クライアントアプリケーションが、ビジネス論理 Web サービス上で呼び出しを 実行"
+"すると、XTS はその目的では API に指示しません。しかし、選択される API の種類"
+"に関係無く、XTS コンテキストが発信メッセージに挿入されて、 来信メッセージ用に"
+"取り出されて現在のスレッドと関連づけされる必要性が あります。これをユーザーの"
+"為に簡単にするために、XTS ソフトウェアは、この タスクを自動的に実行できるフィ"
+"ルターの３つのセットを付けて配布されています。 これらのフィルターは JAX-RPC "
+"と webMethods のクライアントライブラリを 使用して機能するように設計されていま"
+"す。"
#. Tag: para
-#: Getting_Started.xml:25
+#: Getting_Started.xml:23
#, no-c-format
msgid ""
"If the user chooses to use a different SOAP client infrastructure, then the "
@@ -115,19 +118,19 @@
"provide client-side infrastructure for anything other than JAX-RPC or "
"webMethods for this release."
msgstr ""
-"ユーザーが異なる SOAP クライアントインフラストラクチャを選択する場合、 "
-"クライアントサイドのヘッダプロセッシングの責任はそれらに所在します。 "
-"このリリースでは XTS は JAX-RPC 又は webMethods 以外のものには"
-"クライアントサイドインフラストラクチャを提供しません。"
+"ユーザーが異なる SOAP クライアントインフラストラクチャを選択する場合、 クライ"
+"アントサイドのヘッダプロセッシングの責任はそれらに所在します。 このリリースで"
+"は XTS は JAX-RPC 又は webMethods 以外のものにはクライアントサイドインフラス"
+"トラクチャを提供しません。"
#. Tag: title
-#: Getting_Started.xml:30
+#: Getting_Started.xml:28
#, no-c-format
msgid "JAX-RPC Context Handlers"
msgstr "JAX-RPC コンテキストハンドラ"
#. Tag: para
-#: Getting_Started.xml:31
+#: Getting_Started.xml:29
#, no-c-format
msgid ""
"In order to register the JAX-RPC server-side context handler with the "
@@ -136,13 +139,14 @@
"webservices.xml</filename> deployment descriptor for an example of how this "
"can be achieved."
msgstr ""
-"JAX-RPC サーバーサイドのコンテキストハンドラをデプロイした web サービスに "
-"登録するには、ハンドラチェーンがその web サービスデプロイメント記述子に "
-"含まれていなければなりません。これが達成される方法の例としてデモアプリケーションの "
-"<filename>jboss/webservices.xml</filename> デプロイメント記述子を参照して下さい。"
+"JAX-RPC サーバーサイドのコンテキストハンドラをデプロイした web サービスに 登"
+"録するには、ハンドラチェーンがその web サービスデプロイメント記述子に 含まれ"
+"ていなければなりません。これが達成される方法の例としてデモアプリケーションの "
+"<filename>jboss/webservices.xml</filename> デプロイメント記述子を参照して下さ"
+"い。"
#. Tag: para
-#: Getting_Started.xml:35
+#: Getting_Started.xml:33
#, no-c-format
msgid ""
"In order to register the JAX-RPC client-side context handler used by the "
@@ -151,20 +155,20 @@
"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> を "
-"参照して下さい。"
+"クライアントアプリケーションで使用されている JAX-RPC クライアントサイドコンテ"
+"キスト ハンドラを登録するために、ハンドラチェーンが１つクライアント web.xml "
+"デプロイメント 記述子の service-ref 内の定義に含まれていなければなりません。"
+"これが達成される方法の 例としてデモアプリケーション <filename>jboss/client-"
+"web-app.xml</filename> を 参照して下さい。"
#. Tag: title
-#: Getting_Started.xml:39
+#: Getting_Started.xml:37
#, no-c-format
msgid "webMethods Context Handlers"
msgstr "webMethods コンテキストハンドラ"
#. Tag: para
-#: Getting_Started.xml:40
+#: Getting_Started.xml:38
#, no-c-format
msgid ""
"In order to register the webMethods server-side context handler with the "
@@ -173,14 +177,14 @@
"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> を "
-"参照してください。"
+"webMethods サーバーサイドのハンドラをデプロイした web サービスに登録 するため"
+"には、インバウンドとアウトバウンドのインターセプタが、web サービスの デプロイ"
+"メント記述子内で設定されていなければなりません。この設定方法の例として デモア"
+"プリケーションである <filename>RestaurantServiceAT.xml</filename> を 参照して"
+"ください。"
#. Tag: para
-#: Getting_Started.xml:44
+#: Getting_Started.xml:42
#, no-c-format
msgid ""
"In order to register the webMethods client-side context handler, the inbound "
@@ -189,20 +193,20 @@
"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 インターセプタを参照してください。"
+"webMethods クライアントサイドのコンテキストハンドラを登録するためには、 イン"
+"バウンドとアウトバウンドのインターセプタが <filename>glue-config.xml</"
+"filename> デプロイメント記述子内で設定されていなければなりません。 これが達成"
+"される方法の例としてデモアプリケーション glue-config.xml の soap インターセプ"
+"タを参照してください。"
#. Tag: title
-#: Getting_Started.xml:50
+#: Getting_Started.xml:48
#, no-c-format
msgid "Hints and tips"
msgstr "ヒント"
#. Tag: para
-#: Getting_Started.xml:51
+#: Getting_Started.xml:49
#, no-c-format
msgid ""
"If you want to create multiple JBoss deploys on the same machine, then you "
@@ -210,19 +214,19 @@
"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> を参照して下さい。"
+"複数の JBoss デプロイを同じマシン上で作成したい場合は、必要となる情報を 得る"
+"ために <ulink url=\"http://www.yorku.ca/dkha/jboss/docs/MultipleInstances.htm"
+"\"><emphasis>複数インスタンスのセッティング</emphasis></ulink> を参照して下さ"
+"い。"
#. Tag: title
-#: Getting_Started.xml:57
+#: Getting_Started.xml:55
#, no-c-format
msgid "Summary"
msgstr "要約"
#. Tag: para
-#: Getting_Started.xml:58
+#: Getting_Started.xml:56
#, no-c-format
msgid ""
"This chapter has provided a high-level overview of how to use each of the "
@@ -234,17 +238,18 @@
"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 が簡単なインターフェイスと必要なドキュメントハンドリングコードを提供します。"
+"この章では、JBossTS の Web サービストランザクションコンポーネント内の 主なソ"
+"フトウェア部分のそれぞれを使用する方法について高度なレベルの概要を 提供してい"
+"ます。JBossTS により提供されている Web サービストランザクション マネージャは"
+"そのアーキテクチャの中心であり、ユーザーソフトウェアが直接 バインドしない唯一"
+"のソフトウェア部分です。XTS はユーザークライアントアプリケーションと Web サー"
+"ビスの両方の為に Web サービストランザクションコンテキストを扱う為の ヘッダプ"
+"ロセッシングインフラストラクチャを提供します。トランザクションパーティシパン"
+"トの 開発には、XTS が簡単なインターフェイスと必要なドキュメントハンドリング"
+"コードを提供します。"
#. Tag: para
-#: Getting_Started.xml:61
+#: Getting_Started.xml:59
#, no-c-format
msgid ""
"This chapter is meant as an overview only, and is unlikely to answer "
@@ -252,7 +257,6 @@
"the components, please refer to the appropriate chapter elsewhere in this "
"document."
msgstr ""
-"この章は概要のみとして意図されています。そしてより難しい細かい領域での "
-"質問には対応していません。このコンポーネントのより完璧な説明には、この "
-"ドキュメントにある他のより適切な章を参照して下さい。"
-
+"この章は概要のみとして意図されています。そしてより難しい細かい領域での 質問に"
+"は対応していません。このコンポーネントのより完璧な説明には、この ドキュメント"
+"にある他のより適切な章を参照して下さい。"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Introduction.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Introduction.po 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Introduction.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Introduction\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: 2008-09-17 11:06+1000\n"
"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
"Language-Team: Japanese <jp at li.org>\n"
@@ -23,13 +23,13 @@
msgstr "はじめに"
#. Tag: title
-#: Introduction.xml:10
+#: Introduction.xml:8
#, no-c-format
msgid "JBossTS Web Services transactions overview"
msgstr "JBossTS Web トランザクションの概要"
#. Tag: para
-#: Introduction.xml:11
+#: Introduction.xml:9
#, no-c-format
msgid ""
"The XML transaction service component of JBossTS (shorthand referred to as "
@@ -44,18 +44,18 @@
"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 サービス "
-"プラットフォームドキュメントを参考にして下さい。"
+"JBossTS の XML トランザクションサービスコンポーネント（短縮名：XTS）は ビジネ"
+"ストランザクション内で個人と公共の Web サービスの調整をサポートします。 その"
+"ため、XTS を理解するには、Web サービスに熟知していて、トランザクションの 知識"
+"が少々必要となります。この章では、XTS を紹介して Web サービス標準を形成する "
+"技術の簡単な概要を提供します。更にこの章ではトランザクション技術の土台の一部"
+"と それが Web サービスに応用される方法を探求していきます。この章で案内される"
+"内容の ほとんどは、このガイド内に渡って詳細に説明がありますが、Web サービスに"
+"関する 概要情報のみが提供されます。Web サービスの作成の経験がない方は Web "
+"サービス プラットフォームドキュメントを参考にして下さい。"
#. Tag: para
-#: Introduction.xml:14
+#: Introduction.xml:12
#, no-c-format
msgid ""
"JBossTS provides as the XTS component a transaction solution for Web "
@@ -67,15 +67,17 @@
"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 はこのフレームワークを使用するトランザクションプロトコルです。"
+"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:17
+#: Introduction.xml:15
#, no-c-format
msgid ""
"Web services are modular, reusable software components that are created by "
@@ -90,51 +92,53 @@
"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 サービスとして表面化できる環境となります。 "
+"Web サービスはモジュラーな再利用可能なソフトウェアコンポーネントであり、 Web "
+"サービスインターフェイスを介してビジネス機能を具現化することで作成 されます。"
+"Web サービスは、SOAP や HTTP などの標準ベースの技術を使用した 他の Web サービ"
+"スと直接通信します。これらの標準ベースの通信技術の使用によって Web サービスが"
+"顧客や、供給元、取引パートナー、独立したハードウェアオペレーション、 あるいは"
+"プログラミング環境からアクセスされるようになります。その結果は、今日の EDI と"
+"ビジネス対ビジネス(B2B) ソリューションに比較して多大な協調環境の向上を見せま"
+"す。これは、ビジネスがそれらの現在と将来のビジネスアプリケーションを、外部の"
+"パートナーに 簡単に発見できてアクセスできる Web サービスとして表面化できる環"
+"境となります。 "
#. Tag: para
-#: Introduction.xml:20
+#: 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 はそれ自身では、障害許容力はありません。実際、それが魅力的な開発ソリューションになる "
-"理由のいくつかは、サービスベースのアプリケーションが欠点を持っている理由にもなります:"
+"Web はそれ自身では、障害許容力はありません。実際、それが魅力的な開発ソリュー"
+"ションになる 理由のいくつかは、サービスベースのアプリケーションが欠点を持って"
+"いる理由にもなります:"
#. Tag: para
-#: Introduction.xml:25
+#: 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 サービスとして表面化しているアプリケーションコンポーネントはサードパーティで "
-"所有できます。このことは維持コスト面で利便性を提供しますが、同時にそれらの動作に "
-"独占的制御を持つ点で欠点ともなります。"
+"Web サービスとして表面化しているアプリケーションコンポーネントはサードパー"
+"ティで 所有できます。このことは維持コスト面で利便性を提供しますが、同時にそれ"
+"らの動作に 独占的制御を持つ点で欠点ともなります。"
#. Tag: para
-#: Introduction.xml:30
+#: 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 サービスは通常リモートに配置されており、呼び出しの為に増大したネットワーク "
-"伝達により失敗するリスクを増加します。"
+"Web サービスは通常リモートに配置されており、呼び出しの為に増大したネットワー"
+"ク 伝達により失敗するリスクを増加します。"
#. Tag: para
-#: Introduction.xml:35
+#: Introduction.xml:33
#, no-c-format
msgid ""
"Applications that have high dependability requirements, must find a method "
@@ -149,22 +153,23 @@
"support."
msgstr ""
"高い依存性の要求を持つアプリケーションは、アプリケーションが Web サービスを "
-"消費する時に起こる可能性のあるエラーの効果を最低限にするメソッドを見つける必要が "
-"あります。そのような障害に対する安全対策としての１つのメソッドは、トランザクションの "
-"コンテキスト内でアプリケーションの Web サービスと通信することです。トランザクションは "
-"簡単に表現すると、全面的に完了するか又は障害時には同意済みの一定の状態に戻るような作業の単位です。 "
-"一定の状態に戻る場合は通常、作業が最初から発生していないかのように見えます。XTS の使用では、 "
-"トランザクションは複数の Web サービスに広がり、これは複数の企業に渡って実行された作業が "
-"トランザクショナルサポート内で管理できることを意味します。"
+"消費する時に起こる可能性のあるエラーの効果を最低限にするメソッドを見つける必"
+"要が あります。そのような障害に対する安全対策としての１つのメソッドは、トラン"
+"ザクションの コンテキスト内でアプリケーションの Web サービスと通信することで"
+"す。トランザクションは 簡単に表現すると、全面的に完了するか又は障害時には同意"
+"済みの一定の状態に戻るような作業の単位です。 一定の状態に戻る場合は通常、作業"
+"が最初から発生していないかのように見えます。XTS の使用では、 トランザクション"
+"は複数の Web サービスに広がり、これは複数の企業に渡って実行された作業が トラ"
+"ンザクショナルサポート内で管理できることを意味します。"
#. Tag: title
-#: Introduction.xml:39
+#: Introduction.xml:37
#, no-c-format
msgid "Managing Service-Based Processes"
msgstr "サービスベースプロセスの管理"
#. Tag: para
-#: Introduction.xml:40
+#: Introduction.xml:38
#, no-c-format
msgid ""
"XTS allows you to create transactions that drive complex business processes "
@@ -178,17 +183,17 @@
"in the way of formal guarantees when interacting with third-party Web "
"services."
msgstr ""
-"XTS の使用により、複数の Web サービスに広がる複雑なビジネスプロセスを駆動する "
-"トランザクションを作成できるようになります。現在の Web サービス標準はサービスの "
-"ハイレベルな調整の為の要求に対処していません。これは、通信の単独の要求/受信を使用する "
-"今日の Web サービスアプリケーション内では、調整は一般的に問題がないからです。しかし、 "
-"複数のビジネスパートナー間で複数のサービスに従事するアプリケーションにとっては、結果と "
-"して出る通信の調整と制御は重要になります。このことはサードパーティの Web サービスと "
-"通信している場合に正式な保証についてはあまり期待できないことに気がつく時により明確に "
-"なります。"
+"XTS の使用により、複数の Web サービスに広がる複雑なビジネスプロセスを駆動す"
+"る トランザクションを作成できるようになります。現在の Web サービス標準はサー"
+"ビスの ハイレベルな調整の為の要求に対処していません。これは、通信の単独の要"
+"求/受信を使用する 今日の Web サービスアプリケーション内では、調整は一般的に問"
+"題がないからです。しかし、 複数のビジネスパートナー間で複数のサービスに従事す"
+"るアプリケーションにとっては、結果と して出る通信の調整と制御は重要になりま"
+"す。このことはサードパーティの Web サービスと 通信している場合に正式な保証に"
+"ついてはあまり期待できないことに気がつく時により明確に なります。"
#. Tag: para
-#: Introduction.xml:44
+#: Introduction.xml:42
#, no-c-format
msgid ""
"XTS provides the infrastructure for coordinating services during a business "
@@ -200,17 +205,17 @@
"The following example demonstrates how an application may manage service-"
"based processes as transactions:"
msgstr ""
-"XTS はビジネスプロセス中にサービスの調整の為のインフラストラクチャを提供します。 "
-"プロセスをトランザクションとして構成することにより、ビジネスパートナーは信頼出来る "
-"方法で複雑なビジネス交流に於ける協調が可能になり、使用するデータの整合性を "
-"確保することができます。これは通常データベースへの複数の変更で現れます。 "
-"しかし、web に対して直接伝統的なトランザクション/プロセッシングエンジンを表面化する"
-"通常の運営負担と欠点がなくなります。以下の例では、アプリケーションが "
-"サービスベースのプロセスをトランザクションとして管理する方法をデモンストレーションで "
-"示します。 "
+"XTS はビジネスプロセス中にサービスの調整の為のインフラストラクチャを提供しま"
+"す。 プロセスをトランザクションとして構成することにより、ビジネスパートナーは"
+"信頼出来る 方法で複雑なビジネス交流に於ける協調が可能になり、使用するデータの"
+"整合性を 確保することができます。これは通常データベースへの複数の変更で現れま"
+"す。 しかし、web に対して直接伝統的なトランザクション/プロセッシングエンジン"
+"を表面化する通常の運営負担と欠点がなくなります。以下の例では、アプリケーショ"
+"ンが サービスベースのプロセスをトランザクションとして管理する方法をデモンスト"
+"レーションで 示します。 "
#. Tag: para
-#: Introduction.xml:47
+#: Introduction.xml:45
#, no-c-format
msgid ""
"The application in question allows a user to plan a social evening. This "
@@ -228,33 +233,34 @@
"over a period of time. In addition, management must span several third-party "
"services that are remotely deployed."
msgstr ""
-"例として使用するアプリケーションはユーザーがソシアルイベントを企画できるようにします。 "
-"このアプリケーションはレストランのテーブル予約と観劇のチケット予約の担当をします。 "
-"両方の活動はクレジットカードの使用で支払いがされます。この例では、各サービスは "
-"異なるサービスプロバイダによって提供される具現化した Web サービスを表現します。 "
-"XTS は劇場とレストランのサービスの間の交流を１つの長期実行(可能性のある）ビジネス "
-"トランザクションへと封入するために使用されます。このビジネストランザクションは "
-"レストランと劇場の両方での座席が予約されることを保証しなければなりません。１方の "
-"イベントが成立しなければユーザーは両方のイベントを拒否する能力があります。そうして "
-"両方のサービスを元の状態に戻します。両方のイベントが成立できると、ユーザーのクレジット "
-"カードはチャージされて両方の座席が予約されます。お判りのように、両サービス間の交流は "
-"ある期間に渡って信頼できる方法で制御される必要があります。さらには、その管理はリモートで "
-"デプロイされるいくつかのサードパーティのサービスに広がる必要があります。"
+"例として使用するアプリケーションはユーザーがソシアルイベントを企画できるよう"
+"にします。 このアプリケーションはレストランのテーブル予約と観劇のチケット予約"
+"の担当をします。 両方の活動はクレジットカードの使用で支払いがされます。この例"
+"では、各サービスは 異なるサービスプロバイダによって提供される具現化した Web "
+"サービスを表現します。 XTS は劇場とレストランのサービスの間の交流を１つの長期"
+"実行(可能性のある）ビジネス トランザクションへと封入するために使用されます。"
+"このビジネストランザクションは レストランと劇場の両方での座席が予約されること"
+"を保証しなければなりません。１方の イベントが成立しなければユーザーは両方のイ"
+"ベントを拒否する能力があります。そうして 両方のサービスを元の状態に戻します。"
+"両方のイベントが成立できると、ユーザーのクレジット カードはチャージされて両方"
+"の座席が予約されます。お判りのように、両サービス間の交流は ある期間に渡って信"
+"頼できる方法で制御される必要があります。さらには、その管理はリモートで デプロ"
+"イされるいくつかのサードパーティのサービスに広がる必要があります。"
#. Tag: para
-#: Introduction.xml:51
+#: 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:55
+#: Introduction.xml:53
#, no-c-format
msgid ""
"This simple example describes the situations where XTS excels at supporting "
@@ -262,19 +268,19 @@
"refined throughout this guide, and appears as a standard demonstrator "
"(including source code) with the XTS distribution."
msgstr ""
-"この簡単な例は、複数の企業に渡ってビジネスプロセスをサポートすることに "
-"XTS が卓越している状況を表しています。この例はこのガイド内でより洗練 "
-"されて行きます。そして XTS ディストリビューションでの標準のデモンストレーション "
-"として（ソースコードを含む）出現してきます。"
+"この簡単な例は、複数の企業に渡ってビジネスプロセスをサポートすることに XTS が"
+"卓越している状況を表しています。この例はこのガイド内でより洗練 されて行きま"
+"す。そして XTS ディストリビューションでの標準のデモンストレーション として"
+"（ソースコードを含む）出現してきます。"
#. Tag: title
-#: Introduction.xml:59
+#: Introduction.xml:57
#, no-c-format
msgid "Servlets"
msgstr "Servlets"
#. Tag: para
-#: Introduction.xml:60
+#: Introduction.xml:58
#, no-c-format
msgid ""
"The WS-C, WS-Atomic Transaction and WS-Business Activity protocols are based "
@@ -287,17 +293,18 @@
"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 スタイルの通信ではなく、エンティティの一方通行の "
-"通信をベースにしています。エンティティ（例えば、トランザクションパーティシパント）は "
-"要求に応答を返す為に他のエンティティ（例えば、トランザクションコーディネータ）上の "
-"オペレーションを呼び出します。このことはプログラミングモデルが "
-"ピア対ピアの関係をベースにしていると言う意味になります。そして全てのサービス（パーティシパント、 "
-"コーディネータ、又はクライアント）が要求されてないメッセージを受信できるように "
-"するアクティブコンポーネントを持つ必要があると言う結果になります。"
+"WS-C、WS-Atomic Transaction、及び WS-Business Activity のプロトコルは 伝統的"
+"な同期型要求/応答 RPC スタイルの通信ではなく、エンティティの一方通行の 通信を"
+"ベースにしています。エンティティ（例えば、トランザクションパーティシパント）"
+"は 要求に応答を返す為に他のエンティティ（例えば、トランザクションコーディネー"
+"タ）上の オペレーションを呼び出します。このことはプログラミングモデルが ピア"
+"対ピアの関係をベースにしていると言う意味になります。そして全てのサービス"
+"（パーティシパント、 コーディネータ、又はクライアント）が要求されてないメッ"
+"セージを受信できるように するアクティブコンポーネントを持つ必要があると言う結"
+"果になります。"
#. Tag: para
-#: Introduction.xml:64
+#: Introduction.xml:62
#, no-c-format
msgid ""
"In the current implementation of XTS, the active component is achieved "
@@ -310,21 +317,22 @@
"deployment options, allowing servlets where required, but not mandating them."
msgstr ""
"現在の XTS の実装では、アクティブコンポーネントは Java servlet 技術を通じて "
-"達成されます。SOAP/XML を通じて通信できる各終点は、servlet として表現 "
-"されています（そして JNDI 内で発行されています）。開発者にとって幸運なことは "
-"servlet のこの使用が透過的に発生することです。唯一の欠点は（現時点で）クライアントが "
-"servlet をホストする能力を持つドメイン（アプリケーションサーバー）内に存在する必要が "
-"あることです。XTS の将来のバージョンが設定可能なデプロイメントオプションを提供して "
-"servlet を強制しないで必要であれば servlet を許可するようにすることが意図されています。"
+"達成されます。SOAP/XML を通じて通信できる各終点は、servlet として表現 されて"
+"います（そして JNDI 内で発行されています）。開発者にとって幸運なことは "
+"servlet のこの使用が透過的に発生することです。唯一の欠点は（現時点で）クライ"
+"アントが servlet をホストする能力を持つドメイン（アプリケーションサーバー）内"
+"に存在する必要が あることです。XTS の将来のバージョンが設定可能なデプロイメン"
+"トオプションを提供して servlet を強制しないで必要であれば servlet を許可する"
+"ようにすることが意図されています。"
#. Tag: title
-#: Introduction.xml:68
+#: Introduction.xml:66
#, no-c-format
msgid "SOAP"
msgstr "SOAP"
#. Tag: para
-#: Introduction.xml:69
+#: Introduction.xml:67
#, no-c-format
msgid ""
"SOAP has emerged as the de-facto message format for XML-based communication "
@@ -332,12 +340,12 @@
"to define the content of a message and to provide hints as to how recipients "
"should process that message."
msgstr ""
-"SOAPは、Web サービスの舞台で XML ベース通信用の実質的メッセージ形式として "
-"出現しました。ユーザーがメッセージの内容を定義して、受信者がそのメッセージを "
-"プロセスする方法についてのヒントを提供できるようにする軽量のプロトコルです。"
+"SOAPは、Web サービスの舞台で XML ベース通信用の実質的メッセージ形式として 出"
+"現しました。ユーザーがメッセージの内容を定義して、受信者がそのメッセージを プ"
+"ロセスする方法についてのヒントを提供できるようにする軽量のプロトコルです。"
#. Tag: para
-#: Introduction.xml:73
+#: Introduction.xml:71
#, no-c-format
msgid ""
"SOAP messages can be divided into two main categories: Remote Procedure Call "
@@ -348,23 +356,23 @@
"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 サービス広範に "
-"渡ってトランザクションをサポートできます。"
+"SOAP メッセージは２つの主要カテゴリに分けることができます。リモート プロシー"
+"ジャコール(RPC) と ドキュメントエクスチェンジ(DE) です。この ２つのカテゴリの"
+"主たる相違は SOAP 仕様が RPC 用にエンコーディングルールと 慣習を定義すること"
+"です。ドキュメントエクスチェンジモデルにより、随意の XML ドキュメントの交換が"
+"できるようになります。B2B ドキュメント交換の 基幹要素です。XTS は大まかに組み"
+"合わされたドキュメント交換スタイルをベースに していますが、ドキュメント交換、"
+"あるいは RPC を使用する Web サービス広範に 渡ってトランザクションをサポートで"
+"きます。"
#. Tag: title
-#: Introduction.xml:77
+#: Introduction.xml:75
#, no-c-format
msgid "Web Services Description Language (WSDL)"
msgstr "Web サービス記述言語 (WSDL)"
#. Tag: para
-#: Introduction.xml:78
+#: Introduction.xml:76
#, no-c-format
msgid ""
"WSDL is an XML-based language used to define Web service interfaces. An "
@@ -374,10 +382,9 @@
"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 は "
-"クライアントが従うべき形式を表示します）。"
-
+"WSDL は、 Web サービスインターフェイスを定義するのに 使用される XML ベースの"
+"言語です。Web サービスを消費するアプリケーションは サービスの WSDL ドキュメン"
+"トを構文解析してサービスの場所、サービスが サポートするオペレーション、サービ"
+"スがサポートするプロトコル構築 (SOAP, HTTP, など)、 そして、それらにアクセス"
+"する方法を発見します（それぞれのオペレーションに、WSDL は クライアントが従う"
+"べき形式を表示します）。"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Revision_History.po 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Revision_History.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Revision_History\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: 2008-09-05 08:40+1000\n"
"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
"Language-Team: Japanese <jp at li.org>\n"
@@ -16,9 +16,14 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
msgstr "<firstname></firstname> <surname></surname> <email></email>"
-
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Stand-alone_Coordinator.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Stand-alone_Coordinator.po 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Stand-alone_Coordinator.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Stand-alone_Coordinator\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+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"
@@ -23,18 +23,17 @@
msgstr "スタンドアローンコーディネータ"
#. Tag: title
-#: Stand-alone_Coordinator.xml:10
+#: Stand-alone_Coordinator.xml:8
#, no-c-format
msgid "Introduction"
msgstr "はじめに"
#. Tag: para
-#: Stand-alone_Coordinator.xml:11
+#: 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 サービストランザクションコーディネータの設定には、 "
-"システム管理ガイド内の関連した章をご覧下さい。"
-
+"スタンドアローンの Web サービストランザクションコーディネータの設定には、 シ"
+"ステム管理ガイド内の関連した章をご覧下さい。"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/The_XTS_API.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/The_XTS_API.po 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/The_XTS_API.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: The_XTS_API\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: 2008-09-17 19:09+1000\n"
"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
"Language-Team: Japanese <jp at li.org>\n"
@@ -23,13 +23,13 @@
msgstr "XTS API"
#. Tag: title
-#: The_XTS_API.xml:10
+#: The_XTS_API.xml:8
#, no-c-format
msgid "Introduction"
msgstr "はじめに"
#. Tag: para
-#: The_XTS_API.xml:11
+#: 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-"
@@ -37,72 +37,71 @@
"service/participant side where transactions need to be coordinated with back-"
"end systems."
msgstr ""
-"この章では XTS API の使用法を案内しています。これはアプリケーションが "
-"トランザクショナル Web サービスを消費するクライアントサイドと、トランザクションが "
-"バックエンドシステムと同調している必要のあるサービス/クライアントサイドの両方での "
-"使用についての案内です。"
+"この章では XTS API の使用法を案内しています。これはアプリケーションが トラン"
+"ザクショナル Web サービスを消費するクライアントサイドと、トランザクションが "
+"バックエンドシステムと同調している必要のあるサービス/クライアントサイドの両方"
+"での 使用についての案内です。"
#. Tag: title
-#: The_XTS_API.xml:17
+#: 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:18
+#: 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> パッケージとサブパッケージ内に "
-"あります。"
+"以下のクラスとインターフェイスは <package>com.arjuna.wst or com.arjuna.mw."
+"wst</package> パッケージとサブパッケージ内に あります。"
#. Tag: title
-#: The_XTS_API.xml:22
+#: The_XTS_API.xml:20
#, no-c-format
msgid "Vote"
msgstr "投票"
#. Tag: para
-#: The_XTS_API.xml:23
+#: 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> の "
-"サブタイプを返さなければなりません:"
+"２段階コミットプロトコルの間、パーティシパントはそれが制御する作業を確認でき"
+"る 準備があるかどうかについて投票するように依頼されます。以下のような "
+"<code>com.arjuna.wst.Vote</code> の サブタイプを返さなければなりません:"
#. Tag: para
-#: The_XTS_API.xml:29
+#: 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>: パーティシパントはそれがコーディネータに "
-"依頼されれば準備ができていることを示します。この段階ではパーティシパントはまだ "
-"最終的結果を知らないため、コミットしていません。"
+"<emphasis>Prepared</emphasis>: パーティシパントはそれがコーディネータに 依頼"
+"されれば準備ができていることを示します。この段階ではパーティシパントはまだ 最"
+"終的結果を知らないため、コミットしていません。"
#. Tag: para
-#: The_XTS_API.xml:34
+#: 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>: パーティシパントは準備できないこと、そして "
-"実際にロールバックしたことを示します。パーティシパントは２段階目のメッセージを "
-"受ける期待はできません。"
+"<emphasis>Aborted</emphasis>: パーティシパントは準備できないこと、そして 実際"
+"にロールバックしたことを示します。パーティシパントは２段階目のメッセージを 受"
+"ける期待はできません。"
#. Tag: para
-#: The_XTS_API.xml:39
+#: The_XTS_API.xml:37
#, no-c-format
msgid ""
"<emphasis>ReadOnly</emphasis>: the participant indicates that the work it "
@@ -110,12 +109,13 @@
"the final outcome of the transaction. Essentially the participant is "
"resigning from the transaction."
msgstr ""
-"<emphasis>ReadOnly</emphasis>: パーティシパントはそれが制御する作業が "
-"トランザクションの最終結果ついて情報を受ける必要のあるような状態の変化をしていない "
-"ことを示します。基本的にパーティシパントはトランザクションから退去しています。"
+"<emphasis>ReadOnly</emphasis>: パーティシパントはそれが制御する作業が トラン"
+"ザクションの最終結果ついて情報を受ける必要のあるような状態の変化をしていない "
+"ことを示します。基本的にパーティシパントはトランザクションから退去していま"
+"す。"
#. Tag: para
-#: The_XTS_API.xml:44
+#: The_XTS_API.xml:42
#, no-c-format
msgid ""
"Thus a possible implementation of a 2PC participant’s prepare method may "
@@ -125,7 +125,7 @@
"似たものになります:"
#. Tag: screen
-#: The_XTS_API.xml:47
+#: The_XTS_API.xml:45
#, no-c-format
msgid ""
"public Vote prepare () throws WrongStateException, SystemException\n"
@@ -173,13 +173,13 @@
"}"
#. Tag: title
-#: The_XTS_API.xml:49
+#: The_XTS_API.xml:47
#, no-c-format
msgid "The transaction context"
msgstr "トランザクションコンテキスト"
#. Tag: para
-#: The_XTS_API.xml:50
+#: The_XTS_API.xml:48
#, no-c-format
msgid ""
"A transaction is typically represented by some unique identifier and a "
@@ -188,50 +188,52 @@
"(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 はトランザクションが "
-"ネスト化できるようにしてトランザクション階層（ツリー）が形成できるようにします。 "
-"そのため、トランザクションコンテキストは、ルートペアレントである最上部のトランザクションを "
-"持つトランザクション群であることができます。"
+"トランザクションは標準的に特有の識別子と、トランザクションを管理する コーディ"
+"ネータへの参照（例えば、URL）とで表現されます。XTS はトランザクションが ネス"
+"ト化できるようにしてトランザクション階層（ツリー）が形成できるようにします。 "
+"そのため、トランザクションコンテキストは、ルートペアレントである最上部のトラ"
+"ンザクションを 持つトランザクション群であることができます。"
#. Tag: title
-#: The_XTS_API.xml:55
+#: The_XTS_API.xml:53
#, no-c-format
msgid "TxContext"
msgstr "TxContext"
#. Tag: para
-#: The_XTS_API.xml:56
+#: 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> はトランザクションコンテキストの "
-"不明瞭な表現です。"
+"<code>com.arjuna.mw.wst.TxContext</code> はトランザクションコンテキストの 不"
+"明瞭な表現です。"
#. Tag: para
-#: The_XTS_API.xml:62
+#: 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>: これはコンテンツが有効であるかないかを示します。"
+msgstr ""
+"<emphasis>valid</emphasis>: これはコンテンツが有効であるかないかを示します。"
#. Tag: para
-#: The_XTS_API.xml:67
+#: The_XTS_API.xml:65
#, no-c-format
msgid "<emphasis>equals</emphasis>: can be used to compare two instances."
-msgstr "<emphasis>equals</emphasis>: ２つのインスタンスを比較するのに使用されます。"
+msgstr ""
+"<emphasis>equals</emphasis>: ２つのインスタンスを比較するのに使用されます。"
#. Tag: title
-#: The_XTS_API.xml:73
+#: The_XTS_API.xml:71
#, no-c-format
msgid "UserTransaction"
msgstr "UserTransaction"
#. Tag: para
-#: The_XTS_API.xml:74
+#: The_XTS_API.xml:72
#, no-c-format
msgid ""
"The <classname>com.arjuna.wst.UserTransaction</classname> is the class that "
@@ -244,15 +246,15 @@
"on the current thread of control."
msgstr ""
"<classname>com.arjuna.wst.UserTransaction</classname> はほとんどのユーザー "
-"（例えば、クライアントとサービス）が見ることになるクラスです。これは XTS 実装の "
-"背後にあるプロトコル特有の側面からそれらのユーザー達を隔離します。重要なことは、 "
-"UserTransaction が特定のトランザクションを表現するのではなく、むしろ暗黙了解の "
-"スレッド単位トランザクションコンテキストにアクセスを提供する役目を持ちます。 "
-"このことは、JTA 仕様の UserTransaction に似ています。そのため、全ての "
-"UserTransaction メソッドは必然的に制御の現在のスレッド上で行動します。"
+"（例えば、クライアントとサービス）が見ることになるクラスです。これは XTS 実装"
+"の 背後にあるプロトコル特有の側面からそれらのユーザー達を隔離します。重要なこ"
+"とは、 UserTransaction が特定のトランザクションを表現するのではなく、むしろ暗"
+"黙了解の スレッド単位トランザクションコンテキストにアクセスを提供する役目を持"
+"ちます。 このことは、JTA 仕様の UserTransaction に似ています。そのため、全て"
+"の UserTransaction メソッドは必然的に制御の現在のスレッド上で行動します。"
#. Tag: para
-#: The_XTS_API.xml:78
+#: The_XTS_API.xml:76
#, no-c-format
msgid ""
"A new transaction is begun and associated with the invoking thread by using "
@@ -262,12 +264,13 @@
"current thread."
msgstr ""
"begin メソッドを使用して新規のトランザクションが開始されて呼び出すスレッドと "
-"関連づけされます。このスレッドに関連づけのあるトランザクションが既に存在する場合は、 "
-"<code>WrongStateException</code> 例外が送出されます。正しく開始されると、 "
-"このオペレーションは新規に作成されたトランザクションを現在のスレッドに関連づけします"
+"関連づけされます。このスレッドに関連づけのあるトランザクションが既に存在する"
+"場合は、 <code>WrongStateException</code> 例外が送出されます。正しく開始され"
+"ると、 このオペレーションは新規に作成されたトランザクションを現在のスレッドに"
+"関連づけします"
#. Tag: para
-#: The_XTS_API.xml:81
+#: The_XTS_API.xml:79
#, no-c-format
msgid ""
"The transaction is committed by the commit method. This will execute the "
@@ -279,15 +282,16 @@
"the current thread such that it becomes associated with no transaction."
msgstr ""
"トランザクションは、commit メソッドによってコミットされます。これは "
-"Volatile2PC プロトコルと Durable2PC プロトコルを実行してから戻ります。 "
-"呼び出すスレッドに関連のあるトランザクションが存在しない場合は、 "
+"Volatile2PC プロトコルと Durable2PC プロトコルを実行してから戻ります。 呼び出"
+"すスレッドに関連のあるトランザクションが存在しない場合は、 "
"<code>UnknownTransactionException</code> が送出されます。トランザクションが "
-"最終的にロールバックすると、<code>TransactionRolledBackException</code> が "
-"送出されます。完了すると、このオペレーションはそのトランザクションを現在のスレッドから "
-"分離して、そのスレッドがどのトランザクションにも関連を持たないようにします。"
+"最終的にロールバックすると、<code>TransactionRolledBackException</code> が 送"
+"出されます。完了すると、このオペレーションはそのトランザクションを現在のス"
+"レッドから 分離して、そのスレッドがどのトランザクションにも関連を持たないよう"
+"にします。"
#. Tag: para
-#: The_XTS_API.xml:84
+#: The_XTS_API.xml:82
#, no-c-format
msgid ""
"The <code>rollback</code> operation will terminate the transaction and "
@@ -295,31 +299,33 @@
"it didn’t. If there is no transaction associated with the invoking thread "
"then <code>UnknownTransactionException</code> is thrown."
msgstr ""
-"<code>rollback</code> オペレーションはトランザクションを終結して、正しく "
-"終結した場合は通常に戻ります。正しく終結しない場合は適切な例外を送出します。 "
-"呼び出すスレッドに関連したトランザクションが存在しない場合は、 "
+"<code>rollback</code> オペレーションはトランザクションを終結して、正しく 終結"
+"した場合は通常に戻ります。正しく終結しない場合は適切な例外を送出します。 呼び"
+"出すスレッドに関連したトランザクションが存在しない場合は、 "
"<code>UnknownTransactionException</code> が送出されます。"
#. Tag: title
-#: The_XTS_API.xml:88
+#: The_XTS_API.xml:86
#, no-c-format
msgid "UserTransactionFactory"
msgstr "UserTransactionFactory"
#. Tag: para
-#: The_XTS_API.xml:89
+#: The_XTS_API.xml:87
#, no-c-format
-msgid "UserTransactions are obtained from a <code>UserTransactionFactory</code>."
-msgstr "UserTransactions は <code>UserTransactionFactory</code> から取得されます。"
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+"UserTransactions は <code>UserTransactionFactory</code> から取得されます。"
#. Tag: title
-#: The_XTS_API.xml:94
+#: The_XTS_API.xml:92
#, no-c-format
msgid "TransactionManager"
msgstr "TransactionManager"
#. Tag: para
-#: The_XTS_API.xml:95
+#: The_XTS_API.xml:93
#, no-c-format
msgid ""
"The <interfacename>TransactionManager</interfacename> interface represents "
@@ -330,14 +336,16 @@
"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> は特定のトランザクションを表現するものでは "
-"なく、むしろ暗黙了解のスレッド単位トランザクションコンテキストへのアクセスを提供する役目を持ちます。"
+"<interfacename>TransactionManager</interfacename> インターフェイスは背後にあ"
+"る トランザクションサービス実装との交流をするサービス/コンテナ/パーティシパン"
+"ト（サービス側のユーザー）の 標準的な方法を表現します。"
+"<interfacename>UserTransaction</interfacename> と同様に "
+"<interfacename>TransactionManager</interfacename> は特定のトランザクションを"
+"表現するものでは なく、むしろ暗黙了解のスレッド単位トランザクションコンテキス"
+"トへのアクセスを提供する役目を持ちます。"
#. Tag: para
-#: The_XTS_API.xml:99
+#: The_XTS_API.xml:97
#, no-c-format
msgid ""
"A thread of control may require periods of non-transactionality so that it "
@@ -347,15 +355,15 @@
"<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> インスタンスを返します。スレッドはそれから "
-"いずれのトランザクションとも関連を持たないようになります。"
+"<code>TxContext</code> インスタンスを返します。スレッドはそれから いずれのト"
+"ランザクションとも関連を持たないようになります。"
#. Tag: para
-#: The_XTS_API.xml:102
+#: The_XTS_API.xml:100
#, no-c-format
msgid ""
"The <methodname>resume</methodname> method can be used to (re-)associate a "
@@ -367,15 +375,16 @@
"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> "
-"例外が送出されます。"
+"<methodname>resume</methodname> メソッドはスレッドを <code>TxContext</code> "
+"経由で トランザクションに（再）関連づけするために使用することができます。新規"
+"関連づけの前にスレッドは 現在関連づけのある可能性を持つどのトランザクションと"
+"も分離されます。<code>TxContext</code> が null であれば スレッドはどのトラン"
+"ザクションにも関連づけがないことになります。<code>TxContext</code> で参照する"
+"トランザクションが 呼び出すスレッドの有効範囲内で無効である場合に "
+"<code>UnknownTransactionException</code> 例外が送出されます。"
#. Tag: para
-#: The_XTS_API.xml:105
+#: The_XTS_API.xml:103
#, no-c-format
msgid ""
"The <methodname>currentTransaction</methodname> method returns the "
@@ -384,24 +393,24 @@
"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 とは異なり、このメソッドは現在のスレッドをトランザクションから分離しません。 "
-"これは同じトランザクションの有効範囲内で実行する複数のスレッドを有効にするのに使用 "
-"できます。"
+"<methodname>currentTransaction</methodname> メソッドは現在のトランザクション"
+"の 為の <code>TxContext</code> を返します。それが存在しない場合は null を返し"
+"ます。 suspend とは異なり、このメソッドは現在のスレッドをトランザクションから"
+"分離しません。 これは同じトランザクションの有効範囲内で実行する複数のスレッド"
+"を有効にするのに使用 できます。"
#. Tag: para
-#: The_XTS_API.xml:108
+#: 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:113
+#: The_XTS_API.xml:111
#, no-c-format
msgid ""
"<emphasis>enlistForVolatileTwoPhase</emphasis>: enlist the specified "
@@ -415,16 +424,18 @@
"example, it is terminating) then <code>WrongStateException</code> will be "
"thrown."
msgstr ""
-"<emphasis>enlistForVolatileTwoPhase</emphasis>: Volatile2PC プロトコルに参入するように "
-"現在のトランザクションを持つ指定されたパーティシパントを募集します。パーティシパント用の特有な "
-"識別子も必要になります。呼び出すスレッドに関連づけのあるトランザクションが存在しない場合は、 "
-"<code>UnknownTransactionException</code> 例外が送出されます。コーディネータがすでに "
-"同じ識別子を持つパーティシパントを採用している場合は、<code>AlreadyRegisteredException</code> "
-"例外が送出されます。トランザクションがパーティシパントの参加できる状態でない場合（例えば、終結している時）、 "
+"<emphasis>enlistForVolatileTwoPhase</emphasis>: Volatile2PC プロトコルに参入"
+"するように 現在のトランザクションを持つ指定されたパーティシパントを募集しま"
+"す。パーティシパント用の特有な 識別子も必要になります。呼び出すスレッドに関連"
+"づけのあるトランザクションが存在しない場合は、 "
+"<code>UnknownTransactionException</code> 例外が送出されます。コーディネータが"
+"すでに 同じ識別子を持つパーティシパントを採用している場合は、"
+"<code>AlreadyRegisteredException</code> 例外が送出されます。トランザクション"
+"がパーティシパントの参加できる状態でない場合（例えば、終結している時）、 "
"<code>WrongStateException</code> 例外が送出されます。"
#. Tag: para
-#: The_XTS_API.xml:118
+#: The_XTS_API.xml:116
#, no-c-format
msgid ""
"<emphasis>enlistForDurableTwoPhase</emphasis>: enlist the specified "
@@ -438,42 +449,43 @@
"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> 例外が送出されます。"
+"<emphasis>enlistForDurableTwoPhase</emphasis>: 2PC プロトコルに参入するよう"
+"に 現在のトランザクションを持つ指定されたパーティシパントを募集します。パー"
+"ティシパント用の特有な 識別子も必要になります。呼び出すスレッドに関連づけのあ"
+"るトランザクションが存在しない場合は、 <code>UnknownTransactionException</"
+"code> 例外が送出されます。コーディネータがすでに 同じ識別子を持つパーティシパ"
+"ントを採用している場合は、<code>AlreadyRegisteredException</code> 例外が送出"
+"されます。トランザクションがパーティシパントの参加できる状態でない場合（例え"
+"ば、終結している時）、 <code>WrongStateException</code> 例外が送出されます。"
#. Tag: title
-#: The_XTS_API.xml:124
+#: The_XTS_API.xml:122
#, no-c-format
msgid "TransactionFactory"
msgstr "TransactionFactory"
#. Tag: para
-#: The_XTS_API.xml:125
+#: The_XTS_API.xml:123
#, no-c-format
-msgid "TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
msgstr ""
-"TransactionManagers は <code>TransactionFactory</code> から "
-"取得できます。"
+"TransactionManagers は <code>TransactionFactory</code> から 取得できます。"
#. Tag: title
-#: The_XTS_API.xml:132
+#: The_XTS_API.xml:130
#, no-c-format
msgid "API for the Business Activity protocol"
msgstr "ビジネス活動プロトコルのための API"
#. Tag: title
-#: The_XTS_API.xml:136
+#: The_XTS_API.xml:132
#, no-c-format
msgid "UserBusinessActivity"
msgstr "UserBusinessActivity"
#. Tag: para
-#: The_XTS_API.xml:137
+#: The_XTS_API.xml:133
#, no-c-format
msgid ""
"The <classname>com.arjuna.wst.UserBusinessActivity</classname> is the class "
@@ -485,15 +497,16 @@
"<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> メソッドの全ては必然的に制御の現在のスレッド上で "
-"行動します。"
+"<classname>com.arjuna.wst.UserBusinessActivity</classname> はほとんどのユー"
+"ザー （例えば、クライアントとサービス）が見ることになるクラスです。これはそれ"
+"らのユーザーを XTS 実装の背後にあるプロトコル特有の側面から隔離します。重要な"
+"ことは、<code>UserBusinessActivity</code> が 特定のビジネス活動を表現するので"
+"はなく、暗黙了解のスレッド単位活動へのアクセスの提供する役目を持つことです。 "
+"そのため、<code>UserBusinessActivity</code> メソッドの全ては必然的に制御の現"
+"在のスレッド上で 行動します。"
#. Tag: para
-#: The_XTS_API.xml:141
+#: The_XTS_API.xml:137
#, no-c-format
msgid ""
"A new business activity is begun and associated with the invoking thread by "
@@ -502,13 +515,13 @@
"success, this operation associates the newly created activity with the "
"current thread."
msgstr ""
-"begin メソッドを使用することにより新規のビジネス活動が開始され、呼び出すスレッドとの "
-"関連づけがなされます。このスレッドに既に関連を持つ活動がある場合は、<code>WrongStateException</code> "
-"例外が送出されます。正しく開始されると、このオペレーションは新規に作成された活動を現在のスレッドに "
-"関連づけします。"
+"begin メソッドを使用することにより新規のビジネス活動が開始され、呼び出すス"
+"レッドとの 関連づけがなされます。このスレッドに既に関連を持つ活動がある場合"
+"は、<code>WrongStateException</code> 例外が送出されます。正しく開始されると、"
+"このオペレーションは新規に作成された活動を現在のスレッドに 関連づけします。"
#. Tag: para
-#: The_XTS_API.xml:144
+#: The_XTS_API.xml:140
#, no-c-format
msgid ""
"The business activity is completed successfully by the close method. This "
@@ -520,14 +533,16 @@
"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> が送出されます。 "
-"完了すると、このオペレーションは、ビジネス活動を現在のスレッドから分離して、それがどの活動とも "
-"関連を持たないようにします。"
+"ビジネス活動は close メソッドによって完了されます。これが "
+"<code>BusinessAgreementWithParticipantCompletion</code> を 実行してから戻りま"
+"す。呼び出すスレッドに関連づけのある活動が存在しない場合は、"
+"<code>UnknownTransactionException</code> が 送出されます。活動が最終的に取消"
+"になる場合、<code>TransactionRolledBackException</code> が送出されます。 完了"
+"すると、このオペレーションは、ビジネス活動を現在のスレッドから分離して、それ"
+"がどの活動とも 関連を持たないようにします。"
#. Tag: para
-#: The_XTS_API.xml:147
+#: The_XTS_API.xml:143
#, no-c-format
msgid ""
"The cancel operation will terminate the business activity and return "
@@ -536,13 +551,14 @@
"<code>UnknownTransactionException</code> is thrown. Any participants that "
"had previously completed will be informed to compensate for their work."
msgstr ""
-"cancel オペレーションは、ビジネス活動を終結して、それが正しく実施された場合は "
-"元に戻ります。それが正常に実施されない場合は、適切な例外が送出されます。 "
-"呼び出すスレッドと関連づけのある活動が存在しない場合は、<code>UnknownTransactionException</code> が "
-"送出されます。以前に完了しているパーティシパントはそれらの作業を補正するように通達されます。"
+"cancel オペレーションは、ビジネス活動を終結して、それが正しく実施された場合"
+"は 元に戻ります。それが正常に実施されない場合は、適切な例外が送出されます。 "
+"呼び出すスレッドと関連づけのある活動が存在しない場合は、"
+"<code>UnknownTransactionException</code> が 送出されます。以前に完了している"
+"パーティシパントはそれらの作業を補正するように通達されます。"
#. Tag: para
-#: The_XTS_API.xml:150
+#: The_XTS_API.xml:146
#, no-c-format
msgid ""
"Some participants may have registered for the "
@@ -552,36 +568,36 @@
"The application should therefore use the complete method to inform these "
"participants."
msgstr ""
-"一部のパーティシパントは <code>BusinessAgreementWithCoordinatorCompletion</code> "
-"プロトコルの為に登録されているかも知れません。このことはビジネス活動の範囲内で実施する必要のある "
-"全ての作業が完了した時にコーディネータか、又はアプリケーションがパーティシパント達に "
-"通達することを要求します。アプリケーションはそこで complete メソッドを使用してこれらの "
-"パーティシパント達に通達します。"
+"一部のパーティシパントは <code>BusinessAgreementWithCoordinatorCompletion</"
+"code> プロトコルの為に登録されているかも知れません。このことはビジネス活動の"
+"範囲内で実施する必要のある 全ての作業が完了した時にコーディネータか、又はアプ"
+"リケーションがパーティシパント達に 通達することを要求します。アプリケーション"
+"はそこで complete メソッドを使用してこれらの パーティシパント達に通達します。"
#. Tag: title
-#: The_XTS_API.xml:154
+#: The_XTS_API.xml:150
#, no-c-format
msgid "UserBusinessActivityFactory"
msgstr "UserBusinessActivityFactory"
#. Tag: para
-#: The_XTS_API.xml:155
+#: The_XTS_API.xml:151
#, no-c-format
msgid ""
"UserBusinessActivities are obtained from a "
"<code>UserBusinessActivityFactory</code>."
msgstr ""
-"UserBusinessActivities は <code>UserBusinessActivityFactory</code> から "
-"取得できます。"
+"UserBusinessActivities は <code>UserBusinessActivityFactory</code> から 取得"
+"できます。"
#. Tag: title
-#: The_XTS_API.xml:160
+#: The_XTS_API.xml:156
#, no-c-format
msgid "BusinessActivityManager"
msgstr "BusinessActivityManager"
#. Tag: para
-#: The_XTS_API.xml:161
+#: The_XTS_API.xml:157
#, no-c-format
msgid ""
"The <interfacename>BusinessActivityManager</interfacename> interface "
@@ -593,13 +609,14 @@
"implicit per-thread activity."
msgstr ""
"<interfacename>BusinessActivityManager</interfacename> インターフェイスは "
-"サービス/コンテナ/パーティシパント（サービス側のユーザー）が背後にあるビジネス活動 "
-"サービス実装と対応するための標準的な方法を表現します。<interfacename>UserBusinessActivity</interfacename> "
-"の場合と同様に、<interfacename>BusinessActivityManager</interfacename> は特定の活動は示さないで、むしろ "
-"暗黙のスレッド単位の活動へのアクセスを提供する役目を果たします。"
+"サービス/コンテナ/パーティシパント（サービス側のユーザー）が背後にあるビジネ"
+"ス活動 サービス実装と対応するための標準的な方法を表現します。"
+"<interfacename>UserBusinessActivity</interfacename> の場合と同様に、"
+"<interfacename>BusinessActivityManager</interfacename> は特定の活動は示さない"
+"で、むしろ 暗黙のスレッド単位の活動へのアクセスを提供する役目を果たします。"
#. Tag: para
-#: The_XTS_API.xml:165
+#: The_XTS_API.xml:161
#, no-c-format
msgid ""
"A thread of control may require periods of non-transactionality so that it "
@@ -609,14 +626,14 @@
"<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> インスタンスを返します。 "
-"スレッドはそれからはもうどの活動にも関連づけを持ちません。"
+"制御のスレッドは、特定の活動に関連していない作業を実行できるように トランザク"
+"ションでない期間を要求することができます。これを達成するには、 スレッドをいず"
+"れのビジネス活動からも分離する必要があります。suspend メソッドが これを達成で"
+"きて、それが活動上のハンドルである <code>TxContext</code> インスタンスを返し"
+"ます。 スレッドはそれからはもうどの活動にも関連づけを持ちません。"
#. Tag: para
-#: The_XTS_API.xml:168
+#: The_XTS_API.xml:164
#, no-c-format
msgid ""
"The <methodname>resume</methodname> method can be used to (re-)associate a "
@@ -628,15 +645,15 @@
"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> "
-"例外が送出されます。"
+"<methodname>resume</methodname> メソッドはスレッドを TxContext 経由で 活動に"
+"（再）関連づけするために使用することができます。新規関連づけの前にスレッドは "
+"現在関連づけのある可能性を持つどの活動とも分離されます。<code>TxContext</"
+"code> が null であれば スレッドはどの活動にも関連づけがないことになります。"
+"TxContext で参照するビジネス活動が 呼び出すスレッドの有効範囲内で無効である場"
+"合に <code>UnknownTransactionException</code> 例外が送出されます。"
#. Tag: para
-#: The_XTS_API.xml:171
+#: The_XTS_API.xml:167
#, no-c-format
msgid ""
"The <methodname>currentTransaction</methodname> method returns the "
@@ -645,23 +662,24 @@
"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 とは異なり、このメソッドは現在のスレッドを活動から分離しません。 "
-"これは同じビジネス活動の範囲内で実行する為の複数スレッドを有効にするために使用でます。"
+"<methodname>currentTransaction</methodname> メソッドは現在のビジネス 活動の為"
+"の <code>TxContext</code> を返します。又はそれがない場合、null を 返します。"
+"suspend とは異なり、このメソッドは現在のスレッドを活動から分離しません。 これ"
+"は同じビジネス活動の範囲内で実行する為の複数スレッドを有効にするために使用で"
+"ます。"
#. Tag: para
-#: The_XTS_API.xml:174
+#: 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:179
+#: The_XTS_API.xml:175
#, no-c-format
msgid ""
"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
@@ -676,16 +694,17 @@
"terminating) then <code>WrongStateException</code> will be thrown."
msgstr ""
"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
-"<code>BusinessAgreementWithParticipantCompletion</code> プロトコルに参入するように "
-"現在のビジネス活動を持つ指定されたパーティシパントを募集します。パーティシパント用の特有な "
-"識別子も必要になります。呼び出すスレッドに関連づけのあるビジネス活動が存在しない場合は、 "
-"<code>UnknownTransactionException</code> 例外が送出されます。コーディネータがすでに "
-"同じ識別子を持つパーティシパントを採用している場合は、<code>AlreadyRegisteredException</code> "
-"例外が送出されます。活動がパーティシパントの参加できる状態でない場合（例えば、終結している時）、 "
-"<code>WrongStateException</code> 例外が送出されます。"
+"<code>BusinessAgreementWithParticipantCompletion</code> プロトコルに参入する"
+"ように 現在のビジネス活動を持つ指定されたパーティシパントを募集します。パー"
+"ティシパント用の特有な 識別子も必要になります。呼び出すスレッドに関連づけのあ"
+"るビジネス活動が存在しない場合は、 <code>UnknownTransactionException</code> "
+"例外が送出されます。コーディネータがすでに 同じ識別子を持つパーティシパントを"
+"採用している場合は、<code>AlreadyRegisteredException</code> 例外が送出されま"
+"す。活動がパーティシパントの参加できる状態でない場合（例えば、終結している"
+"時）、 <code>WrongStateException</code> 例外が送出されます。"
#. Tag: para
-#: The_XTS_API.xml:184
+#: The_XTS_API.xml:180
#, no-c-format
msgid ""
"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
@@ -700,22 +719,23 @@
"terminating) then <code>WrongStateException</code> will be thrown."
msgstr ""
"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
-"<code>BusinessAgreementWithCoordinatorCompletion</code> プロトコルに参入するように "
-"現在のビジネス活動を持つ指定されたパーティシパントを募集します。パーティシパント用の特有な "
-"識別子も必要になります。呼び出すスレッドに関連づけのあるビジネス活動が存在しない場合は、 "
-"<code>UnknownTransactionException</code> 例外が送出されます。コーディネータがすでに "
-"同じ識別子を持つパーティシパントを採用している場合は、<code>AlreadyRegisteredException</code> "
-"例外が送出されます。活動がパーティシパントの参加できる状態でない場合（例えば、終結している時）、 "
-"<code>WrongStateException</code> 例外が送出されます。 "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> プロトコルに参入する"
+"ように 現在のビジネス活動を持つ指定されたパーティシパントを募集します。パー"
+"ティシパント用の特有な 識別子も必要になります。呼び出すスレッドに関連づけのあ"
+"るビジネス活動が存在しない場合は、 <code>UnknownTransactionException</code> "
+"例外が送出されます。コーディネータがすでに 同じ識別子を持つパーティシパントを"
+"採用している場合は、<code>AlreadyRegisteredException</code> 例外が送出されま"
+"す。活動がパーティシパントの参加できる状態でない場合（例えば、終結している"
+"時）、 <code>WrongStateException</code> 例外が送出されます。 "
#. Tag: title
-#: The_XTS_API.xml:190
+#: The_XTS_API.xml:186
#, no-c-format
msgid "BusinessActivityManagerFactory"
msgstr "BusinessActivityManagerFactory"
#. Tag: para
-#: The_XTS_API.xml:191
+#: The_XTS_API.xml:187
#, no-c-format
msgid ""
"BusinessActivityManagers are obtained from a "
@@ -723,4 +743,3 @@
msgstr ""
"BusinessActivityManagers は <code>BusinessActivityManagerFactory</code> から "
"取得できます。"
-
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactional_Web_Services.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactional_Web_Services.po 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/Transactional_Web_Services.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Transactional_Web_Services\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: 2008-09-05 14:16+1000\n"
"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
"Language-Team: Japanese <jp at li.org>\n"
@@ -23,13 +23,13 @@
msgstr "トランザクショナル Web サービス"
#. Tag: title
-#: Transactional_Web_Services.xml:10
+#: Transactional_Web_Services.xml:8
#, no-c-format
msgid "Introduction"
msgstr "はじめに"
#. Tag: para
-#: Transactional_Web_Services.xml:11
+#: Transactional_Web_Services.xml:9
#, no-c-format
msgid ""
"This chapter describes how to provide transactional support for new and "
@@ -38,20 +38,20 @@
"how existing services can be made WS-T transaction-aware in a non-invasive "
"fashion."
msgstr ""
-"この章では、XTS のサービスサイドの機能を使用した新規の又は既存の Web サービスの "
-"為のトランザクショナルサポートの提供方法を説明しています。ここでは、追加の "
-"プログラミングを使用しないで新規のサービスをトランザクション的にする方法と "
-"侵略的でないスタイルで既存のサービスを WS-T トランザクション認識にする方法を "
-"示しています。"
+"この章では、XTS のサービスサイドの機能を使用した新規の又は既存の Web サービス"
+"の 為のトランザクショナルサポートの提供方法を説明しています。ここでは、追加"
+"の プログラミングを使用しないで新規のサービスをトランザクション的にする方法"
+"と 侵略的でないスタイルで既存のサービスを WS-T トランザクション認識にする方法"
+"を 示しています。"
#. Tag: title
-#: Transactional_Web_Services.xml:17
+#: Transactional_Web_Services.xml:15
#, no-c-format
msgid "A Transactional Web Service"
msgstr "トランザクショナル Web サービス"
#. Tag: para
-#: Transactional_Web_Services.xml:18
+#: Transactional_Web_Services.xml:16
#, no-c-format
msgid ""
"A Web service is a business-level entity. It encapsulates application logic "
@@ -60,14 +60,14 @@
"code, such non-functional requirements as transactionality should not "
"impinge on its construction."
msgstr ""
-"Web サービスはビジネスレベルのエンティティです。これは一部のドメイン特有の "
-"タスクを実践するために必要なアプリケーション論理をカプセル化し、そして "
-"その論理を実行するバックエンドシステムに仕事を委任するように設計されています。 "
-"アプリケーションコードの一部であることから、トランザクション性のような機能的でない "
+"Web サービスはビジネスレベルのエンティティです。これは一部のドメイン特有の タ"
+"スクを実践するために必要なアプリケーション論理をカプセル化し、そして その論理"
+"を実行するバックエンドシステムに仕事を委任するように設計されています。 アプリ"
+"ケーションコードの一部であることから、トランザクション性のような機能的でない "
"要求はその構造に影響することはないはずです。"
#. Tag: para
-#: Transactional_Web_Services.xml:21
+#: Transactional_Web_Services.xml:19
#, no-c-format
msgid ""
"To support this notion, XTS provides a suite of components designed to work "
@@ -78,21 +78,21 @@
"to worry about context propagation issues itself. This is shown in the "
"following figure."
msgstr ""
-"この概念をサポートするために、XTS は SOAP スタックレベルで機能するように "
-"設計されたコンポーネントのセットを提供し、これがそのサービスに如何なる変更も "
-"必要とせずに Web サービスの役目としてトランザクショナル事項を取扱います。 "
-"XTS では、２つのコンテキスト処理のコンポーネントが SOAP サーバーに登録 "
-"されており、コンテキストの伝播問題自身を懸念することなくサービスの役目として "
-"コンテキスト管理を取り扱います。以下にその様子を示しています。"
+"この概念をサポートするために、XTS は SOAP スタックレベルで機能するように 設計"
+"されたコンポーネントのセットを提供し、これがそのサービスに如何なる変更も 必要"
+"とせずに Web サービスの役目としてトランザクショナル事項を取扱います。 XTS で"
+"は、２つのコンテキスト処理のコンポーネントが SOAP サーバーに登録 されており、"
+"コンテキストの伝播問題自身を懸念することなくサービスの役目として コンテキスト"
+"管理を取り扱います。以下にその様子を示しています。"
#. Tag: caption
-#: Transactional_Web_Services.xml:28
+#: Transactional_Web_Services.xml:26
#, no-c-format
msgid "Context Handlers Registered with the SOAP Server"
msgstr "SOAP サーバーを使用して登録されたコンテキストハンドラ"
#. Tag: para
-#: Transactional_Web_Services.xml:30
+#: Transactional_Web_Services.xml:28
#, no-c-format
msgid ""
"The detail of the context management that the context processor performs is "
@@ -107,25 +107,25 @@
"transaction context details. The general architecture for this pattern is "
"shown in the figure below."
msgstr ""
-"コンテキストプロセッサが実行するコンテキスト管理の詳細は、Web サービス "
-"アプリケーション論理にとっては重要ではなく、他のプロトコル特有のコンテキスト "
-"ハンドラによって実行される作業には直角交差しています。しかし、Web サービス "
-"アプリケーション論理が使用する（データベースなどの）バックエンドシステムは多くの "
-"場合に、フロントエンドのトランザクションコンテキストに興味を持ち、その有効範囲で "
-"呼び出されたオペレーションはいずれもバックエンドトランザクションコンテキストに "
-"マップすることができます。これは一般的にデータベースドライバを、オリジナル "
-"ドライバのベニア内にラップすることにより、オリジナルドライバのインターフェイスを "
-"実装して、トランザクショナルコンテキストの詳細にアクセスするためにサービスサイドの "
-"API にフックするとバックエンドで達成できます。"
+"コンテキストプロセッサが実行するコンテキスト管理の詳細は、Web サービス アプリ"
+"ケーション論理にとっては重要ではなく、他のプロトコル特有のコンテキスト ハンド"
+"ラによって実行される作業には直角交差しています。しかし、Web サービス アプリ"
+"ケーション論理が使用する（データベースなどの）バックエンドシステムは多くの 場"
+"合に、フロントエンドのトランザクションコンテキストに興味を持ち、その有効範囲"
+"で 呼び出されたオペレーションはいずれもバックエンドトランザクションコンテキス"
+"トに マップすることができます。これは一般的にデータベースドライバを、オリジナ"
+"ル ドライバのベニア内にラップすることにより、オリジナルドライバのインターフェ"
+"イスを 実装して、トランザクショナルコンテキストの詳細にアクセスするためにサー"
+"ビスサイドの API にフックするとバックエンドで達成できます。"
#. Tag: caption
-#: Transactional_Web_Services.xml:37
+#: Transactional_Web_Services.xml:35
#, no-c-format
msgid "General Pattern for Back-End Integration, Service Side"
msgstr "バックエンド統合の為の汎用パターン、サービスサイド"
#. Tag: para
-#: Transactional_Web_Services.xml:39
+#: Transactional_Web_Services.xml:37
#, no-c-format
msgid ""
"The missing element from this is the commit protocol which finally allows "
@@ -133,7 +133,7 @@
"covered in the participant chapter where the participant/back-end relation "
"is explored further."
msgstr ""
-"ここで欠如している要素はコミットのプロトコルであり、これはバックエンドの作業が "
-"トランザクションの最後に恒久であるかどうかを決定できるようにします。このことは "
-"パーティシパントの章でカバーされていて、パーティシパント/バックエンドの関係がより詳しく検討されいます。"
-
+"ここで欠如している要素はコミットのプロトコルであり、これはバックエンドの作業"
+"が トランザクションの最後に恒久であるかどうかを決定できるようにします。このこ"
+"とは パーティシパントの章でカバーされていて、パーティシパント/バックエンドの"
+"関係がより詳しく検討されいます。"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/ja-JP/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -5,9 +5,10 @@
# Kiyoto Hashida <khashida at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview\n"
+"Project-Id-Version: WS-C_WS-Atomic_Transaction_and_WS-"
+"Business_Activity_Overview\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: 2008-09-17 17:05+1000\n"
"Last-Translator: Kiyoto Hashida <khashida at redhat.com>\n"
"Language-Team: Japanese <jp at li.org>\n"
@@ -23,13 +24,13 @@
msgstr "WS-C、WS-Atomic Transaction、及び WS-Business Activity の概要"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:10
+#: 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:11
+#: 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 "
@@ -38,30 +39,31 @@
"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 の原則はこのガイドを通じて広範囲に説明してあります。"
+"このセクションでは、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:15
+#: 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 仕様に熟知されている場合は、 "
-"マニュアルのこの部分は軽く読み流しても良いでしょう。 "
+"WS-C、 WS-Atomic Transaction、 WS-Business Activity 仕様に熟知されている場合"
+"は、 マニュアルのこの部分は軽く読み流しても良いでしょう。 "
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:22
+#: 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:23
+#: 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 "
@@ -76,18 +78,19 @@
"messages, or may be an explicit part of a message exchange and is specific "
"to the type of coordination being performed."
msgstr ""
-"一般的な表現では、調整（coordination）とは、エンティティの１つ（コーディネータ）が "
-"ドメイン特有の理由で多くのパーティシパントに情報を散布する行為のことです。特有の理由とは "
-"分散型トランザクションプロトコルなどの決定について合意に到達する為とか、あるいは "
-"信頼できるマルチキャスト環境内で発生するような特定メッセージを全てのパーティシパントが "
-"取得することを保証する為などです。パーティが調整を受けている時には、調整コンテキストとして "
-"知られる情報は同一の調整作業又は活動の論理的一部であるオペレーションを一緒に "
-"組織する為に伝搬されます。このコンテキスト情報は通常のアプリケーションメッセージと共に "
-"移動するかも知れないし、又はメッセージ交換内の明示的な部分であって、そして実行されている "
-"調整の種類に特定のものかも知れません。"
+"一般的な表現では、調整（coordination）とは、エンティティの１つ（コーディネー"
+"タ）が ドメイン特有の理由で多くのパーティシパントに情報を散布する行為のことで"
+"す。特有の理由とは 分散型トランザクションプロトコルなどの決定について合意に到"
+"達する為とか、あるいは 信頼できるマルチキャスト環境内で発生するような特定メッ"
+"セージを全てのパーティシパントが 取得することを保証する為などです。パーティが"
+"調整を受けている時には、調整コンテキストとして 知られる情報は同一の調整作業又"
+"は活動の論理的一部であるオペレーションを一緒に 組織する為に伝搬されます。この"
+"コンテキスト情報は通常のアプリケーションメッセージと共に 移動するかも知れない"
+"し、又はメッセージ交換内の明示的な部分であって、そして実行されている 調整の種"
+"類に特定のものかも知れません。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:26
+#: 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 "
@@ -96,60 +99,61 @@
"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 仕様は、図４に示してあるように、異なる "
-"調整プロトコルがクライアント間、サービス間、パーティシパント間で作業を調整する為にプラグインされる "
-"ようにするフレームワークを定義します。"
+"WS-Coordination を支持している基本的な思考は、Web サービス環境内の調整インフ"
+"ラストラクチャの為に 汎用のニーズがあると言うことです。WS-Coordination 仕様"
+"は、図４に示してあるように、異なる 調整プロトコルがクライアント間、サービス"
+"間、パーティシパント間で作業を調整する為にプラグインされる ようにするフレーム"
+"ワークを定義します。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:29
+#: 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:36
+#: 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:38
+#: 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:43
+#: 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:48
+#: 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:53
+#: 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 "
@@ -157,13 +161,13 @@
msgstr "アプリケーションを形成する Web サービス群の間でコンテキスト情報の伝播;"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:58
+#: 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:63
+#: 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 "
@@ -171,25 +175,25 @@
"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 の "
-"役目とそれらの交流関係は図５で示してあります。"
+"これらのポイントの最初の３つは WS-Coordination に直接係わっています。 ４つめ"
+"は、サードパーティエンティティ、すなわち通常アプリケーションを全体として 制御"
+"するクライアントアプリケーションの責務です。これらの ４つの WS-Coordination "
+"の 役目とそれらの交流関係は図５で示してあります。"
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:70
+#: 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:73
+#: 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:74
+#: 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 "
@@ -206,21 +210,22 @@
"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> メッセージを通じて問題を通達されることを "
-"予期しています。"
+"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:78
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:76
#, no-c-format
msgid ""
"<!-- Activation Service portType Declaration -->\n"
@@ -264,13 +269,13 @@
"</wsdl:portType>\\"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:80
+#: 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:81
+#: 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 "
@@ -282,14 +287,14 @@
"below."
msgstr ""
"コーディネータが具体化されて、その該当するコンテキストがアクティベーション "
-"サービスによって作成されると、登録サービスが作成されて表面化されます。 "
-"このサービスはパーティシパントが、特定のコーディネータに関連のあるプロトコル "
-"メッセージを受信する為の登録をできるようにします。アクティベーションサービスと "
-"同様に、登録サービスは非同期通信を想定しており、以下に示すような登録サービスと "
+"サービスによって作成されると、登録サービスが作成されて表面化されます。 この"
+"サービスはパーティシパントが、特定のコーディネータに関連のあるプロトコル メッ"
+"セージを受信する為の登録をできるようにします。アクティベーションサービスと 同"
+"様に、登録サービスは非同期通信を想定しており、以下に示すような登録サービスと "
"登録要求の両方の為の WSDL を指定します。"
#. Tag: screen
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:85
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:83
#, no-c-format
msgid ""
"<!-- Registration Service portType Declaration -->\n"
@@ -327,7 +332,7 @@
"</wsdl:portType>"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:86
+#: 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 "
@@ -336,19 +341,20 @@
"used); where the coordinator’s protocol supports it, participants can also "
"send messages back to the coordinator."
msgstr ""
-"パーティシパントが、登録サービスを通じてコーディネータに登録されると、 "
-"コーディネータが送信するメッセージ（例えば、“prepare to complete”、2段階プロトコルの場合は "
-"“complete”）を受信するようになります。コーディネータのプロトコルがサポートする場合は、 "
-"パーティシパントはコーディネータにメッセージを送り返すこともできます。"
+"パーティシパントが、登録サービスを通じてコーディネータに登録されると、 コー"
+"ディネータが送信するメッセージ（例えば、“prepare to complete”、2段階プロトコ"
+"ルの場合は “complete”）を受信するようになります。コーディネータのプロトコルが"
+"サポートする場合は、 パーティシパントはコーディネータにメッセージを送り返すこ"
+"ともできます。"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:90
+#: 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:91
+#: 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 "
@@ -359,21 +365,21 @@
"succeeded/failed notification through to complex structured data detailing "
"the activity’s status."
msgstr ""
-"ターミネータ（terminator）の役目は通常クライアントアプリケーションが "
-"演じます。これは適切な時点でコーディネータに対して、登録してあるパーティシパント "
-"で使用している特定の調整機能を実行して、プロトコルをその完了まで駆動するように "
-"依頼します。完了すると、クライアントアプリケーションはその活動の結果報告を "
-"受けますが、これは単純な成功/失敗の通知から活動状態の詳細を持つデータ構成までの "
-"変化幅があります。"
+"ターミネータ（terminator）の役目は通常クライアントアプリケーションが 演じま"
+"す。これは適切な時点でコーディネータに対して、登録してあるパーティシパント で"
+"使用している特定の調整機能を実行して、プロトコルをその完了まで駆動するように "
+"依頼します。完了すると、クライアントアプリケーションはその活動の結果報告を 受"
+"けますが、これは単純な成功/失敗の通知から活動状態の詳細を持つデータ構成まで"
+"の 変化幅があります。"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:98
+#: 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:99
+#: 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 "
@@ -382,20 +388,20 @@
"technology to splice together existing transaction processing systems that "
"already form the backbone of enterprise level applications."
msgstr ""
-"過去には、伝統的なトランザクションシステム同士に会話をさせることは "
-"稀にしか達成できない神聖なことでした。しかし Web サービスの出現により "
-"これまでにない相互オペレーションの技術を活用する機会が、エンタープライズレベルの "
-"アプリケーションのバックボーンをすでに構成している既存のトランザクション "
-"プロセッシングシステム群を結合できるようにしています。"
+"過去には、伝統的なトランザクションシステム同士に会話をさせることは 稀にしか達"
+"成できない神聖なことでした。しかし Web サービスの出現により これまでにない相"
+"互オペレーションの技術を活用する機会が、エンタープライズレベルの アプリケー"
+"ションのバックボーンをすでに構成している既存のトランザクション プロセッシング"
+"システム群を結合できるようにしています。"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:103
+#: 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:104
+#: 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 "
@@ -404,20 +410,19 @@
"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 プロトコルに階層化されている事実に"
-"由来しています。"
+"WS-Transaction が伝統的なトランザクションプロトコルに差を付ける重要な 側面は"
+"同期の要求/応答モデルが想定されていないことです。このモデルは WS-Transaction "
+"が、下図に示してあるように、自身の通信パターンがデフォルトで 非同期である WS-"
+"Coordination プロトコルに階層化されている事実に由来しています。"
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:112
+#: 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:114
+#: 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 "
@@ -434,27 +439,28 @@
"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 プロトコル "
-"インフラストラクチャの上に完全専従のトランザクションコーディネータを構築することです。"
+"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:118
+#: 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:119
+#: 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 "
@@ -463,20 +469,20 @@
"transactional services deal with business-level protocols, while the "
"participants handle the underlying WS-Transaction protocols, as shown above."
msgstr ""
-"WS-Transaction はサービスとパーティシパントの概念を区別した役目としてサポート "
-"して、トランザクション認識のサービスとトランザクションの期間中にそのサービスの "
-"代理として行動するパーティシパントとを分別します。トランザクションサービスは "
-"ビジネスレベルのプロトコルを扱い、前述にあるようにパーティシパントは背後にある "
-"WS-Transaction プロトコルを扱います。"
+"WS-Transaction はサービスとパーティシパントの概念を区別した役目としてサポー"
+"ト して、トランザクション認識のサービスとトランザクションの期間中にそのサービ"
+"スの 代理として行動するパーティシパントとを分別します。トランザクションサービ"
+"スは ビジネスレベルのプロトコルを扱い、前述にあるようにパーティシパントは背後"
+"にある WS-Transaction プロトコルを扱います。"
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:127
+#: 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:129
+#: 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 "
@@ -485,13 +491,13 @@
"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:132
+#: 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 "
@@ -502,21 +508,21 @@
"of a single service, and a client application with their associated "
"participants."
msgstr ""
-"パーティシパントは、トランザクションコーディネータの権限下で、トランザクション "
-"認識の Web サービスにより実行される作業の結果を制御します。上記の図では、 "
-"サービスの代表としてトランザクションプロトコルメッセージを管理する "
-"関連パーティシパント１つを持つ各サービスが示されています。下記の図では、単独のサービスと "
-"その関連パーティシパントを持つクライアントアプリケーションが１つクローズアップで "
-"示されています。"
+"パーティシパントは、トランザクションコーディネータの権限下で、トランザクショ"
+"ン 認識の Web サービスにより実行される作業の結果を制御します。上記の図では、 "
+"サービスの代表としてトランザクションプロトコルメッセージを管理する 関連パー"
+"ティシパント１つを持つ各サービスが示されています。下記の図では、単独のサービ"
+"スと その関連パーティシパントを持つクライアントアプリケーションが１つクローズ"
+"アップで 示されています。"
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:139
+#: 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:141
+#: 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 "
@@ -533,40 +539,41 @@
"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 サービス上の全てのトランザクショナル呼出はトランザクションコンテキストを運び "
-"ますので、データベースを使って作業しているパーティシパントは特定のトランザクションの "
-"範囲内でトランザクションナルサービスが行った作業を識別することが出来て、その作業を "
-"コミットするか、又はロールバックします。"
+"トランザクション認識の Web サービスとそのパーティシパントは両方とも 共有のト"
+"ランザクショナルリソースにサービスし、いくつかの API を通じて その両者間に制"
+"御関係があります。これは Java プラットフォームでは JAXTX です。 上記の図に示"
+"されている例では、データベースがトランザクショナル JDBC データベース ドライ"
+"バーを通じてアクセスされると想定されており、ここでは SQL ステートメントは そ"
+"のドライバーを通じてプロセッシングの為にデータベースに送られることになりま"
+"す。 しかし、それらのステートメントが試験的であり、トランザクションがコミット"
+"した場合 にのみコミットします。これを行うには、ドライバー/データベースはパー"
+"ティシパントと、 トランザクション結果をデータベースに報告するトランザクション"
+"とを関連付けします。 Web サービス上の全てのトランザクショナル呼出はトランザク"
+"ションコンテキストを運び ますので、データベースを使って作業しているパーティシ"
+"パントは特定のトランザクションの 範囲内でトランザクションナルサービスが行った"
+"作業を識別することが出来て、その作業を コミットするか、又はロールバックしま"
+"す。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:144
+#: 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 を通して、クライアント "
-"アプリケーションはパーティシパントをトランザクションに登録します。この登録を "
-"通じてトランザクションの終結を制御します。"
+"クライアントの側では、複雑度は少なくなります。その API を通して、クライアン"
+"ト アプリケーションはパーティシパントをトランザクションに登録します。この登録"
+"を 通じてトランザクションの終結を制御します。"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:148
+#: 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:149
+#: 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 "
@@ -578,34 +585,34 @@
"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 交流の "
-"セマンティクスをサポートする２つの独立したモデルを提案します。以下のセクションで "
+"伝統的なトランザクションモデルが Web サービスには適切でないと言う状況で、 次"
+"のような疑問が出てきます。「どのタイプのモデル、あるいはプロトコルが 適切"
+"か？」この疑問への答えは、Web サービストランザクションがその範囲内で デプロイ"
+"される状況が広範囲に及ぶためどの特定のプロトコルも単独では十分でないと 言うこ"
+"とです。そこで、WS-Transaction 仕様は、それぞれが特定の種類の B2B 交流の セマ"
+"ンティクスをサポートする２つの独立したモデルを提案します。以下のセクションで "
"これらの２つの WS-Transaction モデルを説明します。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:154
+#: 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 モデルは拡張可能で、 "
-"必要に応じてプロトコルを注文仕立てするための実装ができるようになります。 "
-"（例えば、それらのデプロイメント環境に適合するように）"
+"WS-Coordination と同様に、２つの WS-Transaction モデルは拡張可能で、 必要に応"
+"じてプロトコルを注文仕立てするための実装ができるようになります。 （例えば、そ"
+"れらのデプロイメント環境に適合するように）"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:159
+#: 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:160
+#: 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 "
@@ -618,16 +625,16 @@
"rollback actions are taken by each."
msgstr ""
"原子性トランザクション、いわゆるアトミックトランザクション (AT)、は伝統的な "
-"ACID トランザクションに似ており、ACID セマンティクスが適切となる短期間の "
-"交流をサポートするように意図されています。AT の有効範囲内では、サービスは "
-"一般的にデータベースやメッセージキューなどのトランザクション認識のリソースを "
-"トランザクションの制御下で間接的にパーティシパントとして採り入れます。 "
-"トランザクションが終結すると、AT の結果決定はその後パーティシパントを通じて "
-"雇用されている各リソースに伝播されます。そしてそれぞれによって適切なコミット、又は "
-"ロールバックのアクションが実施されます。"
+"ACID トランザクションに似ており、ACID セマンティクスが適切となる短期間の 交流"
+"をサポートするように意図されています。AT の有効範囲内では、サービスは 一般的"
+"にデータベースやメッセージキューなどのトランザクション認識のリソースを トラン"
+"ザクションの制御下で間接的にパーティシパントとして採り入れます。 トランザク"
+"ションが終結すると、AT の結果決定はその後パーティシパントを通じて 雇用されて"
+"いる各リソースに伝播されます。そしてそれぞれによって適切なコミット、又は ロー"
+"ルバックのアクションが実施されます。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:164
+#: 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 "
@@ -636,14 +643,14 @@
"any use of atomic transactions occurs in environments and situations where "
"this is appropriate: in a trusted domain, over short durations."
msgstr ""
-"このプロトコルは、企業の骨組みをすでに形成している伝統的なトランザクション "
-"システムで起用されているプロトコルに非常に似ています。このプロトコルは、 "
-"全てのサービス（及び関連したパーティシパント）が ACID セマンティクスを "
-"提供すること、そして原子性のトランザクションの使用はいずれもこれが適切な "
-"環境と状況（信頼できるドメイン内で短期間）で発生することを想定しています。"
+"このプロトコルは、企業の骨組みをすでに形成している伝統的なトランザクション シ"
+"ステムで起用されているプロトコルに非常に似ています。このプロトコルは、 全ての"
+"サービス（及び関連したパーティシパント）が ACID セマンティクスを 提供するこ"
+"と、そして原子性のトランザクションの使用はいずれもこれが適切な 環境と状況（信"
+"頼できるドメイン内で短期間）で発生することを想定しています。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:167
+#: 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-"
@@ -660,18 +667,18 @@
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 登録サービス）への参照も"
-"含まれています。"
+"配置しなければなりません。それが配置されると、クライアントはアクティベーショ"
+"ン サービスに対して 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:170
+#: 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 "
@@ -682,17 +689,17 @@
"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 ヘッダブロック内にあるコンテキストをバックエンドオペレーションに "
-"相互関係づける機能を提供します。"
+"コーディネータからトランザクションコンテキストを取得した後、クライアント アプ"
+"リケーションは Web サービスとの交流に進んでそのビジネスレベルの作業を 達成し"
+"ます。ビジネス Web サービスでのそれぞれの呼び出しで、クライアントは トランザ"
+"クションコンテキストを SOAP ヘッダブロックに挿入します。そして 各呼び出しがト"
+"ランザクションにより暗黙に機会を与えられるようにします。 WS-Atomic "
+"Transaction 認識の Web サービスをサポートするツールキットは SOAP ヘッダブロッ"
+"ク内にあるコンテキストをバックエンドオペレーションに 相互関係づける機能を提供"
+"します。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:173
+#: 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 "
@@ -704,17 +711,17 @@
"status is returned to the participant to indicate the outcome of the "
"transaction."
msgstr ""
-"全ての必要なアプリケーションレベルの作業が完了すると、クライアントは "
-"サービスへの変更はいずれも永久化の状態にする意図を持ってそのトランザクションを "
-"終結することができます。これを実施するには、クライアントアプリケーションは先ず、 "
-"Completion プロトコルの為にそれ自身のパーティシパントを登録します。登録が "
-"終了すると、パーティシパントはコーディネータに対してトランザクションのコミット、 "
-"又はロールバックを試みるように指示します。コミットかロールバックのオペレーションが "
-"完了すると、状態はパーティシパントに戻されてそのトランザクションの結果を表示する "
-"ようになります。 "
+"全ての必要なアプリケーションレベルの作業が完了すると、クライアントは サービス"
+"への変更はいずれも永久化の状態にする意図を持ってそのトランザクションを 終結す"
+"ることができます。これを実施するには、クライアントアプリケーションは先ず、 "
+"Completion プロトコルの為にそれ自身のパーティシパントを登録します。登録が 終"
+"了すると、パーティシパントはコーディネータに対してトランザクションのコミッ"
+"ト、 又はロールバックを試みるように指示します。コミットかロールバックのオペ"
+"レーションが 完了すると、状態はパーティシパントに戻されてそのトランザクション"
+"の結果を表示する ようになります。 "
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:176
+#: 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 "
@@ -725,7 +732,7 @@
"他のいくつかのプロトコルを実行する必要があると言う事実が隠れています。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:179
+#: 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 "
@@ -736,15 +743,16 @@
"committing. Once flushed, the data will then be controlled by a two-phase "
"aware participant."
msgstr ""
-"これらのプロトコルの１つめは、オプションの Volatile2PC です。Volatile2PC "
-"プロトコルは 以前に説明してある同期化プロトコルに対する WS-Atomic トランザクションの "
-"同等物です。これは標準的には、アプリケーションのパフォーマンスを向上するために "
-"使用されている揮発性の（キャッシュ化）状態をWeb サービスがフラッシュする "
-"必要のある部分でトランザクションがコミットする前にデータベースに対して実行されます。 "
-"フラッシュされると、データはそれから２段階認識のパーティシパントによって制御されます。"
+"これらのプロトコルの１つめは、オプションの Volatile2PC です。Volatile2PC プロ"
+"トコルは 以前に説明してある同期化プロトコルに対する WS-Atomic トランザクショ"
+"ンの 同等物です。これは標準的には、アプリケーションのパフォーマンスを向上する"
+"ために 使用されている揮発性の（キャッシュ化）状態をWeb サービスがフラッシュす"
+"る 必要のある部分でトランザクションがコミットする前にデータベースに対して実行"
+"されます。 フラッシュされると、データはそれから２段階認識のパーティシパントに"
+"よって制御されます。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:182
+#: 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 "
@@ -752,13 +760,13 @@
"prepared, aborted or readonly message; any failures at this stage will cause "
"the transaction to rollback."
msgstr ""
-"全ての Volatile2PC パーティシパントは、トランザクションが完了間近である "
-"ことを通達（prepare メッセージ経由）されて、それらのパーティシパントは "
-"prepared、aborted、又は readonly メッセージで応答することができます。 "
-"この段階での障害はいずれもトランザクションがロールバックする原因になります。"
+"全ての Volatile2PC パーティシパントは、トランザクションが完了間近である こと"
+"を通達（prepare メッセージ経由）されて、それらのパーティシパントは prepared、"
+"aborted、又は readonly メッセージで応答することができます。 この段階での障害"
+"はいずれもトランザクションがロールバックする原因になります。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:185
+#: 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 "
@@ -767,14 +775,14 @@
"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 の核心になるもので、トランザクション内の "
-"パーティシパント間に必要な同意をもたらして、トランザクションが安全に "
-"終結するようにするものです。"
+"Volatile2PC prepare の後、WS-Atomic Transaction 内で実行する次の プロトコル"
+"は Durable2PC です。Durable2PC （2PC は２段階コミットの略字） プロトコルは "
+"WS-Atomic Transaction の核心になるもので、トランザクション内の パーティシパン"
+"ト間に必要な同意をもたらして、トランザクションが安全に 終結するようにするもの"
+"です。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:188
+#: 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 "
@@ -792,32 +800,34 @@
"second phase of the commit protocol. Otherwise, the prepared message is sent "
"by the participant."
msgstr ""
-"２段階コミットプロトコルはパーティシパント間の原子性を確証する為に使用されるもので、 "
-"推測される中止技術を使用する古典的な２段階コミットをベースにしています。第１段階では "
-"コーディネータが prepare メッセージを送った時にパーティシパントはトランザクションの "
-"範囲内で発生した状態変化を恒久化して、それらの変更が後でロールバック、又はコミット "
-"できるようにしなければなりません。このことは、原子性トランザクションが "
-"まだロールバックできるため、オリジナルの状態はいずれもこの時点では消失しないように "
-"する必要があると言うことです。パーティシパントが準備できない場合、コーディネータに（中止メッセージを介して） "
-"通達しなければならず、そうするとトランザクションは最終的にロールバックされます。パーティシパントが、 "
-"トランザクションの期間中にいずれの作業もしていない、あるいは状態を変更した作業をしていないサービスに "
-"ついて責務を持つ場合は readonly メッセージを送ることができ、コミットプロトコルの第２段階から外され "
-"ます。それ以外の場合は準備のメッセージがパーティシパントにより送信されます。"
+"２段階コミットプロトコルはパーティシパント間の原子性を確証する為に使用される"
+"もので、 推測される中止技術を使用する古典的な２段階コミットをベースにしていま"
+"す。第１段階では コーディネータが prepare メッセージを送った時にパーティシパ"
+"ントはトランザクションの 範囲内で発生した状態変化を恒久化して、それらの変更が"
+"後でロールバック、又はコミット できるようにしなければなりません。このことは、"
+"原子性トランザクションが まだロールバックできるため、オリジナルの状態はいずれ"
+"もこの時点では消失しないように する必要があると言うことです。パーティシパント"
+"が準備できない場合、コーディネータに（中止メッセージを介して） 通達しなければ"
+"ならず、そうするとトランザクションは最終的にロールバックされます。パーティシ"
+"パントが、 トランザクションの期間中にいずれの作業もしていない、あるいは状態を"
+"変更した作業をしていないサービスに ついて責務を持つ場合は readonly メッセージ"
+"を送ることができ、コミットプロトコルの第２段階から外され ます。それ以外の場合"
+"は準備のメッセージがパーティシパントにより送信されます。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:191
+#: 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:194
+#: 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 "
@@ -828,15 +838,16 @@
"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 は１段階コミットの最適化をサポートします。パーティシパントが "
-"１つだけですから、その決定は暗黙に同意に到達するそのため、コーディネータは２つの段階を "
-"経てトランザクションを駆動する必要はありません。最適化してあるケースでは、パーティシパントは "
-"単にコミットすることを指示され、トランザクションの結果はその単独パーティシパントだけのものですから "
-"トランザクションコーディネータはその決定に関して情報を記録する必要はありません。"
+"トランザクションがただ１つのパーティシパントだけを巻き込んでいる場合は、 WS-"
+"Atomic Transaction は１段階コミットの最適化をサポートします。パーティシパント"
+"が １つだけですから、その決定は暗黙に同意に到達するそのため、コーディネータは"
+"２つの段階を 経てトランザクションを駆動する必要はありません。最適化してある"
+"ケースでは、パーティシパントは 単にコミットすることを指示され、トランザクショ"
+"ンの結果はその単独パーティシパントだけのものですから トランザクションコーディ"
+"ネータはその決定に関して情報を記録する必要はありません。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:197
+#: 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 "
@@ -846,19 +857,19 @@
"whereas the participant messages are shown by dashed lines."
msgstr ""
"以下の図：<footnote> <para>WS-Atomic Transaction 仕様から再描画したものです。"
-"</para> </footnote> は WS-Atomic Transaction のトランザクション "
-"状態とコーディネータとパーティシパント間のメッセージ交換を示しています。 "
-"コーディネータ生成のメッセージは実線で示してあり、パーティシパントのメッセージは "
-"断線で示してあります。"
+"</para> </footnote> は WS-Atomic Transaction のトランザクション 状態とコー"
+"ディネータとパーティシパント間のメッセージ交換を示しています。 コーディネータ"
+"生成のメッセージは実線で示してあり、パーティシパントのメッセージは 断線で示し"
+"てあります。"
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:208
+#: 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:210
+#: 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 "
@@ -866,13 +877,13 @@
"application whether the transaction was committed or rolled back. "
"Additionally, the Volatile2PC protocol may complete."
msgstr ""
-"2PC プロトコルが終了すると、最初にトランザクション終結を開始した Completion プロトコルは "
-"完了できるようになり、クライアントアプリケーションに対してトランザクションがコミット "
-"されたか、又はロールバックされたかを通達することができます。さらには、Volatile2PC "
-"プロトコルも完了できます。"
+"2PC プロトコルが終了すると、最初にトランザクション終結を開始した Completion "
+"プロトコルは 完了できるようになり、クライアントアプリケーションに対してトラン"
+"ザクションがコミット されたか、又はロールバックされたかを通達することができま"
+"す。さらには、Volatile2PC プロトコルも完了できます。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:213
+#: 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 "
@@ -881,11 +892,11 @@
"back into the pool of connections)."
msgstr ""
"Volatile2PC の準備段階のように最終段階はオプションであり、トランザクションが "
-"完了した時にそれらがリソースを開放できるように（例えば、データベース接続を接続のプールに戻す）、 "
-"標準的にパーティシパントに通達するのに使用できます。"
+"完了した時にそれらがリソースを開放できるように（例えば、データベース接続を接"
+"続のプールに戻す）、 標準的にパーティシパントに通達するのに使用できます。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:216
+#: 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 "
@@ -895,37 +906,37 @@
"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
"the transaction."
msgstr ""
-"登録済みの Volatile2PC パーティシパントはどれもトランザクションが "
-"終結した後に呼び出されてトランザクションが完了した状態を通達されます。 "
-"（コーディネータは完了済みか、中止済みのメッセージを送ります）トランザクションは "
-"終結していますから、この時点でのパーティシパントの障害は無視されます。これは "
-"基本的に社交的な通信でありトランザクションの結果に何も影響ありません。"
+"登録済みの Volatile2PC パーティシパントはどれもトランザクションが 終結した後"
+"に呼び出されてトランザクションが完了した状態を通達されます。 （コーディネータ"
+"は完了済みか、中止済みのメッセージを送ります）トランザクションは 終結していま"
+"すから、この時点でのパーティシパントの障害は無視されます。これは 基本的に社交"
+"的な通信でありトランザクションの結果に何も影響ありません。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:219
+#: 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 を "
-"全体として構成する個別のプロトコルの入り込んだ網羅を見ることができます。"
+"最後に AT 内の各ステージを通過した後には、以下の図にあるような AT を 全体と"
+"して構成する個別のプロトコルの入り込んだ網羅を見ることができます。"
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:226
+#: 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:229
+#: 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:230
+#: 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 "
@@ -944,19 +955,20 @@
"available, or may have to be reordered specially for them."
msgstr ""
"ほとんどのビジネス対ビジネスのアプリケーションは、均一的な結果と正しい実行を "
-"保証する為にトランザクショナルサポートを必要とします。これらのアプリケーションは "
-"長期間実行の演算、緩い結合のシステムとデータ共有をしないコンポーネント、場所、 "
-"又は管理などを巻き込んでおり、そのようなアーキテクチャ内で原子性のトランザクションを "
-"統合するのは難しい状態です。例えば、オンラインのブックショップがある個人の為に "
-"特定の期間だけ本を保留しておいたとします。しかし、その個人がその期間内に本を "
-"購入しない場合は、他の客のために本を棚に戻します。さらには、誰も無限的にストックの "
-"供給をできないため、一部のオンラインショップは客の為に本を保留しているように見えても、 "
-"実際には他の客にその保留物を先取りさせる（例えば、同じ本が同時に複数予約されている場合）かも "
-"しれません。その場合、最初の客は注文した本が無くなったことを知るか、あるいはそれを再度 "
-"予約する必要があるかも知れません。"
+"保証する為にトランザクショナルサポートを必要とします。これらのアプリケーショ"
+"ンは 長期間実行の演算、緩い結合のシステムとデータ共有をしないコンポーネント、"
+"場所、 又は管理などを巻き込んでおり、そのようなアーキテクチャ内で原子性のトラ"
+"ンザクションを 統合するのは難しい状態です。例えば、オンラインのブックショップ"
+"がある個人の為に 特定の期間だけ本を保留しておいたとします。しかし、その個人が"
+"その期間内に本を 購入しない場合は、他の客のために本を棚に戻します。さらには、"
+"誰も無限的にストックの 供給をできないため、一部のオンラインショップは客の為に"
+"本を保留しているように見えても、 実際には他の客にその保留物を先取りさせる（例"
+"えば、同じ本が同時に複数予約されている場合）かも しれません。その場合、最初の"
+"客は注文した本が無くなったことを知るか、あるいはそれを再度 予約する必要がある"
+"かも知れません。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:234
+#: 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-"
@@ -970,17 +982,17 @@
"of the WS-Business Activity specification, but an implementation decision "
"for the service provider."
msgstr ""
-"ビジネス活動（BA）は特に長期間交流の為に設計されたもので、そこでは、 "
-"専従的にリソースをロックすることはほとんど不可能で非現実的になります。 "
-"このモデルでは、サービスは作業をするように依頼されて、それらのサービスが "
-"いかなる作業をも元に戻すことができる部分では、 BA が後で作業を取り消す決断をした場合 "
-"（例えば、BA が障害を受けた時など）、 BA がサービスにその復元動作を実行するように "
-"指示できることをサービスが BA に対してを伝えます。ビジネス活動の為のキーポイントは、 "
-"サービスがその作業を実施する手段とその補正の提供手段は WS-Business Activity 仕様の "
-"領域ではなく、サービス提供者の実装決定であると言う点です。"
+"ビジネス活動（BA）は特に長期間交流の為に設計されたもので、そこでは、 専従的に"
+"リソースをロックすることはほとんど不可能で非現実的になります。 このモデルで"
+"は、サービスは作業をするように依頼されて、それらのサービスが いかなる作業をも"
+"元に戻すことができる部分では、 BA が後で作業を取り消す決断をした場合 （例え"
+"ば、BA が障害を受けた時など）、 BA がサービスにその復元動作を実行するように "
+"指示できることをサービスが BA に対してを伝えます。ビジネス活動の為のキーポイ"
+"ントは、 サービスがその作業を実施する手段とその補正の提供手段は WS-Business "
+"Activity 仕様の 領域ではなく、サービス提供者の実装決定であると言う点です。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:237
+#: 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 "
@@ -988,13 +1000,13 @@
"wrap their proprietary mechanisms and interoperate across implementations "
"and business boundaries."
msgstr ""
-"WS- Business Activity は単に Web サービスベースのアプリケーションの為にプロトコルを "
-"定義して既存のビジネスプロセッシングとワークフローシステムを有効にすることで、 "
-"それらのプロプライエタリメカニズムを包み込んで実装とビジネス境界全域に渡って "
-"相互オペレーションを得るようにします。"
+"WS- Business Activity は単に Web サービスベースのアプリケーションの為にプロト"
+"コルを 定義して既存のビジネスプロセッシングとワークフローシステムを有効にする"
+"ことで、 それらのプロプライエタリメカニズムを包み込んで実装とビジネス境界全域"
+"に渡って 相互オペレーションを得るようにします。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:240
+#: 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 "
@@ -1007,18 +1019,18 @@
"experiences an error, it can be caught by the parent who may be able to "
"compensate and continue processing."
msgstr ""
-"ビジネス活動はいくつかの範囲（scope）に分けることができて、そこでは１つの範囲は "
-"Web サービスのコレクションを使用したビジネスタスク、又は作業の単位と "
-"なります。そのような範囲群は任意のレベルでネスト化が可能で、ペアレントと "
-"チャイルドの関係を構成することができます。その中ではペアレント範囲はどの "
-"チャイルドタスクが、特定のビジネス活動の為の全体的な結果プロトコル内に "
-"含まれるべきかを選択する能力を持ちます。そして明確に原子性でない結果も "
-"可能になります。伝統的なネスト化のトランザクションに似た方法で、チャイルド "
-"タスクがエラーを経験している場合、そのプロセスを補正して継続できるペアレントに "
-"よって保護されることが出来ます。"
+"ビジネス活動はいくつかの範囲（scope）に分けることができて、そこでは１つの範囲"
+"は Web サービスのコレクションを使用したビジネスタスク、又は作業の単位と なり"
+"ます。そのような範囲群は任意のレベルでネスト化が可能で、ペアレントと チャイル"
+"ドの関係を構成することができます。その中ではペアレント範囲はどの チャイルドタ"
+"スクが、特定のビジネス活動の為の全体的な結果プロトコル内に 含まれるべきかを選"
+"択する能力を持ちます。そして明確に原子性でない結果も 可能になります。伝統的な"
+"ネスト化のトランザクションに似た方法で、チャイルド タスクがエラーを経験してい"
+"る場合、そのプロセスを補正して継続できるペアレントに よって保護されることが出"
+"来ます。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:243
+#: 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 "
@@ -1026,13 +1038,13 @@
"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:246
+#: 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 "
@@ -1045,43 +1057,43 @@
"should be proactive, if it is to perform well."
msgstr ""
"依頼された時にのみパーティシパントがコーディネータにその状態を通達すると言う "
-"WS-Atomic Transaction プロトコルモデルとは異なり、ビジネス活動内のタスクは "
-"要求を待たずに直接ペアレントにその結果を指定することができます。この特徴は、 "
-"タスクが失敗して、その通知がビジネス活動例外ハンドラーによって使用されて、 "
-"トランザクションが失敗を認めることを黙って待つことなしに "
-"ゴールを修正してプロセスを前に駆動させる点で役に立ちます。良く機能するように "
-"期待されている限りは、良く設計されたビジネス活動は前進的である必要があります。"
+"WS-Atomic Transaction プロトコルモデルとは異なり、ビジネス活動内のタスクは 要"
+"求を待たずに直接ペアレントにその結果を指定することができます。この特徴は、 タ"
+"スクが失敗して、その通知がビジネス活動例外ハンドラーによって使用されて、 トラ"
+"ンザクションが失敗を認めることを黙って待つことなしに ゴールを修正してプロセス"
+"を前に駆動させる点で役に立ちます。良く機能するように 期待されている限りは、良"
+"く設計されたビジネス活動は前進的である必要があります。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:249
+#: 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:254
+#: 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 メタデータ "
-"（送信済みと受信済みのメッセージ記録）を含んで信頼できる方法で記録されています;"
+"全ての状態転移は、アプリケーションの状態と coordination メタデータ （送信済み"
+"と受信済みのメッセージ記録）を含んで信頼できる方法で記録されています;"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:259
+#: 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:264
+#: 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 "
@@ -1091,15 +1103,15 @@
"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:269
+#: 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 "
@@ -1108,14 +1120,14 @@
"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 プロトコルとは異なり、 "
-"このプロトコルはもっと多くパーティシパントから上方に駆動されます。"
+"原子性トランザクションの使用と同様に、ビジネス活動モデルは複数のプロトコルを"
+"持ち ます: <code>BusinessAgreementWithParticipantCompletion</code> と "
+"<code>BusinessAgreementWithCoordinatorCompletion</code> です。しかし、 コー"
+"ディネータからパーティシパントに下方に駆動する AT プロトコルとは異なり、 この"
+"プロトコルはもっと多くパーティシパントから上方に駆動されます。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:272
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
#, no-c-format
msgid ""
"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
@@ -1132,18 +1144,19 @@
"work."
msgstr ""
"<code>BusinessAgreementWithParticipantCompletion</code> プロトコルの元で、 "
-"チャイルドの活動は最初は Active 状態で作成されます。それが実施するように与えられた "
-"作業を終了して、ビジネス活動（BA）の範囲内（活動が不変データに於いてオペレートするなど）で "
-"要求される参加がもう存在しない場合は、チャイルドはペアレントに exited メッセージを "
-"一方的に送信することができます。しかし、チャイルドがタスクを終了して BA 内でまだ継続したい "
-"場合は、それが実行した作業を補正する能力を持つ必要があります。このケースではチャイルドは "
-"completed メッセージをペアレントに送信して、ペアレントから BA の最終結果を受け取ることを "
-"待ちます。この結果とは BA が正しく完了したことを意味する close メッセージか、あるいはペアレント "
-"活動がチャイルドタスク作業の反転を必要とすることを意味する compensate メッセージのどちらかに "
-"なります。"
+"チャイルドの活動は最初は Active 状態で作成されます。それが実施するように与え"
+"られた 作業を終了して、ビジネス活動（BA）の範囲内（活動が不変データに於いてオ"
+"ペレートするなど）で 要求される参加がもう存在しない場合は、チャイルドはペアレ"
+"ントに exited メッセージを 一方的に送信することができます。しかし、チャイルド"
+"がタスクを終了して BA 内でまだ継続したい 場合は、それが実行した作業を補正する"
+"能力を持つ必要があります。このケースではチャイルドは completed メッセージをペ"
+"アレントに送信して、ペアレントから BA の最終結果を受け取ることを 待ちます。こ"
+"の結果とは BA が正しく完了したことを意味する close メッセージか、あるいはペア"
+"レント 活動がチャイルドタスク作業の反転を必要とすることを意味する compensate "
+"メッセージのどちらかに なります。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:275
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
#, no-c-format
msgid ""
"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
@@ -1155,17 +1168,17 @@
"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> プロトコル内で "
-"実行するのと同じ行動をします。"
+"<code>BusinessAgreementWithCoordinatorCompletion</code> プロトコルは、 補正で"
+"きる場合でもチャイルドが自動的にビジネス活動内への参加を停止することを 決定で"
+"きないこと以外では、<code>BusinessAgreementWithParticipantCompletion</code> "
+"プロトコルと同一です。チャイルドタスクは、チャイルドが作業を実行するための要"
+"求を全て 受けた時にその通達に於いてペアレントに依存してします。これはペアレン"
+"トがチャイルドに complete メッセージを送信することで実行されます。チャイルド"
+"はそれから、 <code>BusinessAgreementWithParticipantCompletion</code> プロトコ"
+"ル内で 実行するのと同じ行動をします。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:278
+#: 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 "
@@ -1176,7 +1189,7 @@
"しないサービスの参加を認可することです。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:281
+#: 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 "
@@ -1185,20 +1198,20 @@
"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 の制御下にあるサービスの開発者に委任されます。そのような補正は "
-"下方互換のエラーリカバリを使用するかも知れませんが、標準的には上方互換リカバリを "
-"採用します。"
+"完全な ACIDセマンティクスは BA によって維持されていませんが、それでも整合性は"
+"まだ 補正によって維持できます。但し、正確な補正のアクション（及び全体的システ"
+"ム整合性）を 書くタスクは BA の制御下にあるサービスの開発者に委任されます。そ"
+"のような補正は 下方互換のエラーリカバリを使用するかも知れませんが、標準的には"
+"上方互換リカバリを 採用します。"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:285
+#: 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:286
+#: 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 "
@@ -1209,13 +1222,14 @@
"propagated within the headers of SOAP messages."
msgstr ""
"アプリケーションメッセージとは、ビジネスプロセスの作業を構成するパーティ間で "
-"送信される要求と応答のことです。そのようなメッセージはいずれも XTS では不明瞭だと "
-"判断されて、そこには義務的なメッセージ形式やプロトコルバインディングやエンコーディング "
-"スタイルがないため、開発者は自由に適切な Web サービスプロトコルを使用することができます。 "
-"XTS では、トランザクションコンテキストは SOAP メッセージのヘッダー内で伝播されます。"
+"送信される要求と応答のことです。そのようなメッセージはいずれも XTS では不明瞭"
+"だと 判断されて、そこには義務的なメッセージ形式やプロトコルバインディングやエ"
+"ンコーディング スタイルがないため、開発者は自由に適切な Web サービスプロトコ"
+"ルを使用することができます。 XTS では、トランザクションコンテキストは SOAP "
+"メッセージのヘッダー内で伝播されます。"
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:291
+#: 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 "
@@ -1231,25 +1245,27 @@
"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 がユーザーの介入なしにコンテキストを管理できると言う点です。"
+"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:296
+#: 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:297
+#: 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 "
@@ -1258,13 +1274,14 @@
"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:301
+#: 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 "
@@ -1272,13 +1289,13 @@
"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 のような標準のトランザクション "
-"オペレーションを実行する指示が含まれています。"
+"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:305
+#: 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 "
@@ -1288,21 +1305,21 @@
"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 を使用して配送することは "
-"妥当なことです。"
+"XTS メッセージはアプリケーションメッセージをどのような形、あるいは形式でも 妨"
+"害することはなく、またトランザクション特有のメッセージと同じトランスポートを "
+"使用するアプリケーションの為の要求もありません。例えば、影では XTS メッセージ"
+"は 異なるメカニズムを使用して配送されていますが、クライアントアプリケーション"
+"が そのアプリケーション特有のメッセージを SMTP 上で SOAP RPC を使用して配送す"
+"ることは 妥当なことです。"
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:312
+#: 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:313
+#: 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 "
@@ -1317,14 +1334,14 @@
"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 は全ての必要な配管処理を提供して、アプリケーションに関する "
-"アプリケーションとトランザクション側面を分離して、システムのトランザクション性がシステム自身の "
-"機能側面を邪魔しないことを確実にします。"
-
+"XTS はインターネット全域に於いて企業間で実行されるトランザクションを許可する"
+"ように 設計されている調整インフラストラクチャを提供します。このインフラストラ"
+"クチャは WS-C、WS-Atomic Transaction、及び WS-Business Activity 仕様をベース"
+"にしています。 XTS は、２つの種類のトランザクションをサポートします。原子性ト"
+"ランザクションと ビジネス活動です。これらは随意な方法で組み合わせることが出来"
+"て、背後にある問題の トランザクション要求へエレガントにマップすることができま"
+"す。この全体のインフラストラクチャの 使用は、その機能が簡単なトランザクショニ"
+"ング API を通じて表面化されていると言う事実により、 単純なものです。さらに"
+"は、XTS は全ての必要な配管処理を提供して、アプリケーションに関する アプリケー"
+"ションとトランザクション側面を分離して、システムのトランザクション性がシステ"
+"ム自身の 機能側面を邪魔しないことを確実にします。"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Author_Group.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Author_Group.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Author_Group.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Book_Info.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Book_Info.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Book_Info.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -17,29 +17,29 @@
#. Tag: title
#: Book_Info.xml:6
#, no-c-format
-msgid "Transactions Web Services Programmers Guide"
+msgid "JBoss Transactions Web Services Programmers Guide"
msgstr ""
#. Tag: subtitle
#: Book_Info.xml:7
#, no-c-format
-msgid "JBoss Enterprise Application Platform"
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
msgstr ""
#. Tag: para
-#: Book_Info.xml:11
+#: Book_Info.xml:13
#, no-c-format
msgid "This book is about Programming for Transaction Web Services"
msgstr ""
#. Tag: phrase
-#: Book_Info.xml:18
+#: Book_Info.xml:20
#, no-c-format
msgid "Logo"
msgstr ""
#. Tag: holder
-#: Book_Info.xml:24
+#: Book_Info.xml:26
#, no-c-format
msgid "&HOLDER;"
msgstr ""
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Getting_Started.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Getting_Started.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Getting_Started.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: Getting_Started.xml:10
+#: Getting_Started.xml:8
#, no-c-format
msgid "Creating and deploying participants"
msgstr ""
#. Tag: para
-#: Getting_Started.xml:11
+#: Getting_Started.xml:9
#, no-c-format
msgid ""
"A participant is a software entity which is driven by the transaction "
@@ -46,13 +46,13 @@
msgstr ""
#. Tag: title
-#: Getting_Started.xml:17
+#: Getting_Started.xml:15
#, no-c-format
msgid "Creating Client Applications"
msgstr ""
#. Tag: para
-#: Getting_Started.xml:18
+#: Getting_Started.xml:16
#, no-c-format
msgid ""
"There are two aspects to a client application using XTS. The first is the "
@@ -66,7 +66,7 @@
msgstr ""
#. Tag: para
-#: Getting_Started.xml:21
+#: Getting_Started.xml:19
#, no-c-format
msgid ""
"When the client application performs invocations on business logic Web "
@@ -80,7 +80,7 @@
msgstr ""
#. Tag: para
-#: Getting_Started.xml:25
+#: Getting_Started.xml:23
#, no-c-format
msgid ""
"If the user chooses to use a different SOAP client infrastructure, then the "
@@ -90,13 +90,13 @@
msgstr ""
#. Tag: title
-#: Getting_Started.xml:30
+#: Getting_Started.xml:28
#, no-c-format
msgid "JAX-RPC Context Handlers"
msgstr ""
#. Tag: para
-#: Getting_Started.xml:31
+#: Getting_Started.xml:29
#, no-c-format
msgid ""
"In order to register the JAX-RPC server-side context handler with the "
@@ -107,7 +107,7 @@
msgstr ""
#. Tag: para
-#: Getting_Started.xml:35
+#: Getting_Started.xml:33
#, no-c-format
msgid ""
"In order to register the JAX-RPC client-side context handler used by the "
@@ -118,13 +118,13 @@
msgstr ""
#. Tag: title
-#: Getting_Started.xml:39
+#: Getting_Started.xml:37
#, no-c-format
msgid "webMethods Context Handlers"
msgstr ""
#. Tag: para
-#: Getting_Started.xml:40
+#: Getting_Started.xml:38
#, no-c-format
msgid ""
"In order to register the webMethods server-side context handler with the "
@@ -135,7 +135,7 @@
msgstr ""
#. Tag: para
-#: Getting_Started.xml:44
+#: Getting_Started.xml:42
#, no-c-format
msgid ""
"In order to register the webMethods client-side context handler, the inbound "
@@ -146,13 +146,13 @@
msgstr ""
#. Tag: title
-#: Getting_Started.xml:50
+#: Getting_Started.xml:48
#, no-c-format
msgid "Hints and tips"
msgstr ""
#. Tag: para
-#: Getting_Started.xml:51
+#: Getting_Started.xml:49
#, no-c-format
msgid ""
"If you want to create multiple JBoss deploys on the same machine, then you "
@@ -162,13 +162,13 @@
msgstr ""
#. Tag: title
-#: Getting_Started.xml:57
+#: Getting_Started.xml:55
#, no-c-format
msgid "Summary"
msgstr ""
#. Tag: para
-#: Getting_Started.xml:58
+#: Getting_Started.xml:56
#, no-c-format
msgid ""
"This chapter has provided a high-level overview of how to use each of the "
@@ -182,7 +182,7 @@
msgstr ""
#. Tag: para
-#: Getting_Started.xml:61
+#: Getting_Started.xml:59
#, no-c-format
msgid ""
"This chapter is meant as an overview only, and is unlikely to answer "
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Introduction.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Introduction.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Introduction.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: Introduction.xml:10
+#: Introduction.xml:8
#, no-c-format
msgid "JBossTS Web Services transactions overview"
msgstr ""
#. Tag: para
-#: Introduction.xml:11
+#: Introduction.xml:9
#, no-c-format
msgid ""
"The XML transaction service component of JBossTS (shorthand referred to as "
@@ -44,7 +44,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:14
+#: Introduction.xml:12
#, no-c-format
msgid ""
"JBossTS provides as the XTS component a transaction solution for Web "
@@ -58,7 +58,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:17
+#: Introduction.xml:15
#, no-c-format
msgid ""
"Web services are modular, reusable software components that are created by "
@@ -75,7 +75,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:20
+#: Introduction.xml:18
#, no-c-format
msgid ""
"Web services, by themselves, are not fault tolerant. In fact, some of the "
@@ -84,7 +84,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:25
+#: Introduction.xml:23
#, no-c-format
msgid ""
"Application components that are exposed as Web services may be owned by "
@@ -93,7 +93,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:30
+#: Introduction.xml:28
#, no-c-format
msgid ""
"Web services are usually remotely located which increases risk of failure "
@@ -101,7 +101,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:35
+#: Introduction.xml:33
#, no-c-format
msgid ""
"Applications that have high dependability requirements, must find a method "
@@ -117,13 +117,13 @@
msgstr ""
#. Tag: title
-#: Introduction.xml:39
+#: Introduction.xml:37
#, no-c-format
msgid "Managing Service-Based Processes"
msgstr ""
#. Tag: para
-#: Introduction.xml:40
+#: Introduction.xml:38
#, no-c-format
msgid ""
"XTS allows you to create transactions that drive complex business processes "
@@ -139,7 +139,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:44
+#: Introduction.xml:42
#, no-c-format
msgid ""
"XTS provides the infrastructure for coordinating services during a business "
@@ -153,7 +153,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:47
+#: Introduction.xml:45
#, no-c-format
msgid ""
"The application in question allows a user to plan a social evening. This "
@@ -173,7 +173,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:51
+#: Introduction.xml:49
#, no-c-format
msgid ""
"Without the backing of a transaction, an undesirable outcome may occur. For "
@@ -182,7 +182,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:55
+#: Introduction.xml:53
#, no-c-format
msgid ""
"This simple example describes the situations where XTS excels at supporting "
@@ -192,13 +192,13 @@
msgstr ""
#. Tag: title
-#: Introduction.xml:59
+#: Introduction.xml:57
#, no-c-format
msgid "Servlets"
msgstr ""
#. Tag: para
-#: Introduction.xml:60
+#: Introduction.xml:58
#, no-c-format
msgid ""
"The WS-C, WS-Atomic Transaction and WS-Business Activity protocols are based "
@@ -213,7 +213,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:64
+#: Introduction.xml:62
#, no-c-format
msgid ""
"In the current implementation of XTS, the active component is achieved "
@@ -227,13 +227,13 @@
msgstr ""
#. Tag: title
-#: Introduction.xml:68
+#: Introduction.xml:66
#, no-c-format
msgid "SOAP"
msgstr ""
#. Tag: para
-#: Introduction.xml:69
+#: Introduction.xml:67
#, no-c-format
msgid ""
"SOAP has emerged as the de-facto message format for XML-based communication "
@@ -243,7 +243,7 @@
msgstr ""
#. Tag: para
-#: Introduction.xml:73
+#: Introduction.xml:71
#, no-c-format
msgid ""
"SOAP messages can be divided into two main categories: Remote Procedure Call "
@@ -256,13 +256,13 @@
msgstr ""
#. Tag: title
-#: Introduction.xml:77
+#: Introduction.xml:75
#, no-c-format
msgid "Web Services Description Language (WSDL)"
msgstr ""
#. Tag: para
-#: Introduction.xml:78
+#: Introduction.xml:76
#, no-c-format
msgid ""
"WSDL is an XML-based language used to define Web service interfaces. An "
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Participants.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Participants.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Participants.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Preface.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Preface.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Preface.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Revision_History.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Revision_History.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Revision_History.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -14,8 +14,14 @@
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
#. Tag: author
-#: Revision_History.xml:9
+#: Revision_History.xml:12
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
msgstr ""
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Stand-alone_Coordinator.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Stand-alone_Coordinator.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Stand-alone_Coordinator.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: Stand-alone_Coordinator.xml:10
+#: Stand-alone_Coordinator.xml:8
#, no-c-format
msgid "Introduction"
msgstr ""
#. Tag: para
-#: Stand-alone_Coordinator.xml:11
+#: Stand-alone_Coordinator.xml:9
#, no-c-format
msgid ""
"For configuring a stand-alone Web Services transaction coordinator, see the "
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/The_XTS_API.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/The_XTS_API.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/The_XTS_API.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:10
+#: The_XTS_API.xml:8
#, no-c-format
msgid "Introduction"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:11
+#: 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-"
@@ -37,13 +37,13 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:17
+#: The_XTS_API.xml:15
#, no-c-format
msgid "API for the Atomic Transaction protocol"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:18
+#: The_XTS_API.xml:16
#, no-c-format
msgid ""
"The following classes and interfaces are located within the <package>com."
@@ -51,13 +51,13 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:22
+#: The_XTS_API.xml:20
#, no-c-format
msgid "Vote"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:23
+#: The_XTS_API.xml:21
#, no-c-format
msgid ""
"During the two-phase commit protocol, a participant will be asked to vote on "
@@ -66,7 +66,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:29
+#: The_XTS_API.xml:27
#, no-c-format
msgid ""
"<emphasis>Prepared</emphasis>: the participant indicates that it can prepare "
@@ -75,7 +75,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:34
+#: The_XTS_API.xml:32
#, no-c-format
msgid ""
"<emphasis>Aborted</emphasis>: the participant indicates that it cannot "
@@ -84,7 +84,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:39
+#: The_XTS_API.xml:37
#, no-c-format
msgid ""
"<emphasis>ReadOnly</emphasis>: the participant indicates that the work it "
@@ -94,7 +94,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:44
+#: The_XTS_API.xml:42
#, no-c-format
msgid ""
"Thus a possible implementation of a 2PC participant’s prepare method may "
@@ -102,7 +102,7 @@
msgstr ""
#. Tag: screen
-#: The_XTS_API.xml:47
+#: The_XTS_API.xml:45
#, no-c-format
msgid ""
"public Vote prepare () throws WrongStateException, SystemException\n"
@@ -129,13 +129,13 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:49
+#: The_XTS_API.xml:47
#, no-c-format
msgid "The transaction context"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:50
+#: The_XTS_API.xml:48
#, no-c-format
msgid ""
"A transaction is typically represented by some unique identifier and a "
@@ -146,13 +146,13 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:55
+#: The_XTS_API.xml:53
#, no-c-format
msgid "TxContext"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:56
+#: The_XTS_API.xml:54
#, no-c-format
msgid ""
"<code>com.arjuna.mw.wst.TxContext</code> is an opaque representation of a "
@@ -160,7 +160,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:62
+#: The_XTS_API.xml:60
#, no-c-format
msgid ""
"<emphasis>valid</emphasis>: this indicates whether or not the contents are "
@@ -168,19 +168,19 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:67
+#: 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:73
+#: The_XTS_API.xml:71
#, no-c-format
msgid "UserTransaction"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:74
+#: The_XTS_API.xml:72
#, no-c-format
msgid ""
"The <classname>com.arjuna.wst.UserTransaction</classname> is the class that "
@@ -194,7 +194,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:78
+#: The_XTS_API.xml:76
#, no-c-format
msgid ""
"A new transaction is begun and associated with the invoking thread by using "
@@ -205,7 +205,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:81
+#: The_XTS_API.xml:79
#, no-c-format
msgid ""
"The transaction is committed by the commit method. This will execute the "
@@ -218,7 +218,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:84
+#: The_XTS_API.xml:82
#, no-c-format
msgid ""
"The <code>rollback</code> operation will terminate the transaction and "
@@ -228,26 +228,26 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:88
+#: The_XTS_API.xml:86
#, no-c-format
msgid "UserTransactionFactory"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:89
+#: The_XTS_API.xml:87
#, no-c-format
msgid ""
"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:94
+#: The_XTS_API.xml:92
#, no-c-format
msgid "TransactionManager"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:95
+#: The_XTS_API.xml:93
#, no-c-format
msgid ""
"The <interfacename>TransactionManager</interfacename> interface represents "
@@ -260,7 +260,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:99
+#: The_XTS_API.xml:97
#, no-c-format
msgid ""
"A thread of control may require periods of non-transactionality so that it "
@@ -272,7 +272,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:102
+#: The_XTS_API.xml:100
#, no-c-format
msgid ""
"The <methodname>resume</methodname> method can be used to (re-)associate a "
@@ -286,7 +286,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:105
+#: The_XTS_API.xml:103
#, no-c-format
msgid ""
"The <methodname>currentTransaction</methodname> method returns the "
@@ -297,7 +297,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:108
+#: The_XTS_API.xml:106
#, no-c-format
msgid ""
"In order to register and resign participants with a transaction, the "
@@ -305,7 +305,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:113
+#: The_XTS_API.xml:111
#, no-c-format
msgid ""
"<emphasis>enlistForVolatileTwoPhase</emphasis>: enlist the specified "
@@ -321,7 +321,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:118
+#: The_XTS_API.xml:116
#, no-c-format
msgid ""
"<emphasis>enlistForDurableTwoPhase</emphasis>: enlist the specified "
@@ -337,32 +337,32 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:124
+#: The_XTS_API.xml:122
#, no-c-format
msgid "TransactionFactory"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:125
+#: The_XTS_API.xml:123
#, no-c-format
msgid ""
"TransactionManagers are obtained from a <code>TransactionFactory</code>."
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:132
+#: The_XTS_API.xml:130
#, no-c-format
msgid "API for the Business Activity protocol"
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:136
+#: The_XTS_API.xml:132
#, no-c-format
msgid "UserBusinessActivity"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:137
+#: The_XTS_API.xml:133
#, no-c-format
msgid ""
"The <classname>com.arjuna.wst.UserBusinessActivity</classname> is the class "
@@ -376,7 +376,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:141
+#: The_XTS_API.xml:137
#, no-c-format
msgid ""
"A new business activity is begun and associated with the invoking thread by "
@@ -387,7 +387,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:144
+#: The_XTS_API.xml:140
#, no-c-format
msgid ""
"The business activity is completed successfully by the close method. This "
@@ -401,7 +401,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:147
+#: The_XTS_API.xml:143
#, no-c-format
msgid ""
"The cancel operation will terminate the business activity and return "
@@ -412,7 +412,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:150
+#: The_XTS_API.xml:146
#, no-c-format
msgid ""
"Some participants may have registered for the "
@@ -424,13 +424,13 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:154
+#: The_XTS_API.xml:150
#, no-c-format
msgid "UserBusinessActivityFactory"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:155
+#: The_XTS_API.xml:151
#, no-c-format
msgid ""
"UserBusinessActivities are obtained from a "
@@ -438,13 +438,13 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:160
+#: The_XTS_API.xml:156
#, no-c-format
msgid "BusinessActivityManager"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:161
+#: The_XTS_API.xml:157
#, no-c-format
msgid ""
"The <interfacename>BusinessActivityManager</interfacename> interface "
@@ -457,7 +457,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:165
+#: The_XTS_API.xml:161
#, no-c-format
msgid ""
"A thread of control may require periods of non-transactionality so that it "
@@ -469,7 +469,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:168
+#: The_XTS_API.xml:164
#, no-c-format
msgid ""
"The <methodname>resume</methodname> method can be used to (re-)associate a "
@@ -483,7 +483,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:171
+#: The_XTS_API.xml:167
#, no-c-format
msgid ""
"The <methodname>currentTransaction</methodname> method returns the "
@@ -494,7 +494,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:174
+#: The_XTS_API.xml:170
#, no-c-format
msgid ""
"In order to register and resign participants with a business activity, the "
@@ -502,7 +502,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:179
+#: The_XTS_API.xml:175
#, no-c-format
msgid ""
"<emphasis>enlistForBusinessAgreementWithParticipantCompletion</emphasis>: "
@@ -518,7 +518,7 @@
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:184
+#: The_XTS_API.xml:180
#, no-c-format
msgid ""
"<emphasis>enlistForBusinessAgreementWithCoordinatorCompletion</emphasis>: "
@@ -534,13 +534,13 @@
msgstr ""
#. Tag: title
-#: The_XTS_API.xml:190
+#: The_XTS_API.xml:186
#, no-c-format
msgid "BusinessActivityManagerFactory"
msgstr ""
#. Tag: para
-#: The_XTS_API.xml:191
+#: The_XTS_API.xml:187
#, no-c-format
msgid ""
"BusinessActivityManagers are obtained from a "
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Transactional_Web_Services.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Transactional_Web_Services.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Transactional_Web_Services.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: Transactional_Web_Services.xml:10
+#: Transactional_Web_Services.xml:8
#, no-c-format
msgid "Introduction"
msgstr ""
#. Tag: para
-#: Transactional_Web_Services.xml:11
+#: Transactional_Web_Services.xml:9
#, no-c-format
msgid ""
"This chapter describes how to provide transactional support for new and "
@@ -38,13 +38,13 @@
msgstr ""
#. Tag: title
-#: Transactional_Web_Services.xml:17
+#: Transactional_Web_Services.xml:15
#, no-c-format
msgid "A Transactional Web Service"
msgstr ""
#. Tag: para
-#: Transactional_Web_Services.xml:18
+#: Transactional_Web_Services.xml:16
#, no-c-format
msgid ""
"A Web service is a business-level entity. It encapsulates application logic "
@@ -55,7 +55,7 @@
msgstr ""
#. Tag: para
-#: Transactional_Web_Services.xml:21
+#: Transactional_Web_Services.xml:19
#, no-c-format
msgid ""
"To support this notion, XTS provides a suite of components designed to work "
@@ -68,13 +68,13 @@
msgstr ""
#. Tag: caption
-#: Transactional_Web_Services.xml:28
+#: Transactional_Web_Services.xml:26
#, no-c-format
msgid "Context Handlers Registered with the SOAP Server"
msgstr ""
#. Tag: para
-#: Transactional_Web_Services.xml:30
+#: Transactional_Web_Services.xml:28
#, no-c-format
msgid ""
"The detail of the context management that the context processor performs is "
@@ -91,13 +91,13 @@
msgstr ""
#. Tag: caption
-#: Transactional_Web_Services.xml:37
+#: Transactional_Web_Services.xml:35
#, no-c-format
msgid "General Pattern for Back-End Integration, Service Side"
msgstr ""
#. Tag: para
-#: Transactional_Web_Services.xml:39
+#: Transactional_Web_Services.xml:37
#, no-c-format
msgid ""
"The missing element from this is the commit protocol which finally allows "
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Transactions_Overview.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Transactions_Overview.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/Transactions_Overview.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.pot
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.pot 2008-09-23 06:31:08 UTC (rev 78770)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.pot 2008-09-23 06:35:15 UTC (rev 78771)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,13 +21,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:10
+#: 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:11
+#: 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 "
@@ -38,7 +38,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:15
+#: 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 "
@@ -47,13 +47,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:22
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
#, no-c-format
msgid "WS-Coordination"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:23
+#: 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 "
@@ -70,7 +70,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:26
+#: 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 "
@@ -81,7 +81,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:29
+#: 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, "
@@ -89,13 +89,13 @@
msgstr ""
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:36
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:34
#, no-c-format
msgid "WS-C architecture"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:38
+#: 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 "
@@ -103,7 +103,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:43
+#: 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 "
@@ -111,7 +111,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:48
+#: 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 "
@@ -120,7 +120,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:53
+#: 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 "
@@ -128,13 +128,13 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:58
+#: 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:63
+#: 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 "
@@ -144,19 +144,19 @@
msgstr ""
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:70
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
#, no-c-format
msgid "WS-C infrastructure"
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:73
+#: 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:74
+#: 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 "
@@ -175,7 +175,7 @@
msgstr ""
#. Tag: screen
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:78
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:76
#, no-c-format
msgid ""
"<!-- Activation Service portType Declaration -->\n"
@@ -200,13 +200,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:80
+#: 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:81
+#: 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 "
@@ -219,7 +219,7 @@
msgstr ""
#. Tag: screen
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:85
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:83
#, no-c-format
msgid ""
"<!-- Registration Service portType Declaration -->\n"
@@ -241,7 +241,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:86
+#: 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 "
@@ -252,13 +252,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:90
+#: 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:91
+#: 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 "
@@ -271,13 +271,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:98
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:96
#, no-c-format
msgid "WS-Transaction"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:99
+#: 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 "
@@ -288,13 +288,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:103
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:101
#, no-c-format
msgid "WS-Coordination Foundations"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:104
+#: 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 "
@@ -305,13 +305,13 @@
msgstr ""
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:112
+#: 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 ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:114
+#: 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 "
@@ -330,13 +330,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:118
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:116
#, no-c-format
msgid "WS-Transaction Architecture"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:119
+#: 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 "
@@ -347,13 +347,13 @@
msgstr ""
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:127
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:125
#, no-c-format
msgid "WS-Transaction Global View"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:129
+#: 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 "
@@ -364,7 +364,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:132
+#: 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 "
@@ -377,13 +377,13 @@
msgstr ""
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:139
+#: 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:141
+#: 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 "
@@ -402,7 +402,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:144
+#: 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 "
@@ -411,13 +411,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:148
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:146
#, no-c-format
msgid "WS-Transaction Models"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:149
+#: 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 "
@@ -431,7 +431,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:154
+#: 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 "
@@ -440,13 +440,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:159
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:157
#, no-c-format
msgid "Atomic Transactions (AT)"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:160
+#: 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 "
@@ -460,7 +460,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:164
+#: 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 "
@@ -471,7 +471,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:167
+#: 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-"
@@ -488,7 +488,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:170
+#: 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 "
@@ -501,7 +501,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:173
+#: 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 "
@@ -515,7 +515,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:176
+#: 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 "
@@ -524,7 +524,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:179
+#: 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 "
@@ -537,7 +537,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:182
+#: 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 "
@@ -547,7 +547,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:185
+#: 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 "
@@ -558,7 +558,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:188
+#: 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 "
@@ -578,7 +578,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:191
+#: 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 "
@@ -587,7 +587,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:194
+#: 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 "
@@ -600,7 +600,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:197
+#: 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 "
@@ -611,13 +611,13 @@
msgstr ""
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:208
+#: 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:210
+#: 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 "
@@ -627,7 +627,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:213
+#: 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 "
@@ -637,7 +637,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:216
+#: 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 "
@@ -649,7 +649,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:219
+#: 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 "
@@ -658,19 +658,19 @@
msgstr ""
#. Tag: caption
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:226
+#: 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:229
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:227
#, no-c-format
msgid "Business Activities (BA)"
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:230
+#: 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 "
@@ -690,7 +690,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:234
+#: 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-"
@@ -706,7 +706,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:237
+#: 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 "
@@ -716,7 +716,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:240
+#: 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 "
@@ -731,7 +731,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:243
+#: 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 "
@@ -741,7 +741,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:246
+#: 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 "
@@ -755,13 +755,13 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:249
+#: 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:254
+#: 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 "
@@ -769,7 +769,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:259
+#: 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 "
@@ -778,7 +778,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:264
+#: 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 "
@@ -790,7 +790,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:269
+#: 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 "
@@ -801,7 +801,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:272
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
#, no-c-format
msgid ""
"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
@@ -819,7 +819,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:275
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
#, no-c-format
msgid ""
"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
@@ -833,7 +833,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:278
+#: 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 "
@@ -842,7 +842,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:281
+#: 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 "
@@ -853,13 +853,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:285
+#: 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:286
+#: 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 "
@@ -871,7 +871,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:291
+#: 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 "
@@ -889,13 +889,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:296
+#: 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 ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:297
+#: 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 "
@@ -906,7 +906,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:301
+#: 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 "
@@ -916,7 +916,7 @@
msgstr ""
#. Tag: para
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:305
+#: 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 "
@@ -928,13 +928,13 @@
msgstr ""
#. Tag: title
-#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:312
+#: 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:313
+#: 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 "
Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pot/messages.mo
===================================================================
(Binary files differ)
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Appendix.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"PO-Revision-Date: 2008-09-01 01:36+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Author_Group.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Book_Info.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,44 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Getting_Started.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Getting_Started.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,191 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Introduction.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Introduction.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Introduction.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,273 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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'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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/JBoss_Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Participants.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Participants.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Participants.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,457 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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
+#, 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Preface.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Revision_History.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,26 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Stand-alone_Coordinator.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Stand-alone_Coordinator.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Stand-alone_Coordinator.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,34 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/The_XTS_API.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/The_XTS_API.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/The_XTS_API.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,547 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, 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
+#, no-c-format
+msgid "TransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactional_Web_Services.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactional_Web_Services.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactional_Web_Services.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,106 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,654 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions_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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/pt-BR/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,950 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr ""
+
+#. 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 ""
+"<!-- Activation Service portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"CreateCoordinationContext\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContext\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Activation Requester portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationRequesterPortType\">\n"
+" <wsdl:operation \n"
+" name=\"CreateCoordinationContextResponse\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContextResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\\"
+msgstr ""
+
+#. 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 ""
+"<!-- Registration Service portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"Register\">\n"
+" <wsdl:input message=\"wscoor:Register\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Registration Requester portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationRequesterPortType\">\n"
+" <wsdl:operation name=\"RegisterResponse\">\n"
+" <wsdl:input message=\"wscoor:RegisterResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr ""
+
+#. 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
+#, 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Appendix.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Appendix.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-01 01:36+0000\n"
+"PO-Revision-Date: 2008-09-01 01:36+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Appendix.xml:9
+#, no-c-format
+msgid "Revision History"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Author_Group.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Book_Info.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,44 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions Web Services Programmers Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about Programming for Transaction Web Services"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Getting_Started.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Getting_Started.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,191 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:28
+#, no-c-format
+msgid "JAX-RPC Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Getting_Started.xml:37
+#, no-c-format
+msgid "webMethods Context Handlers"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Introduction.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Introduction.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Introduction.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,273 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Introduction.xml:6
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:8
+#, no-c-format
+msgid "JBossTS Web Services transactions overview"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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'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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:57
+#, no-c-format
+msgid "Servlets"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:66
+#, no-c-format
+msgid "SOAP"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Introduction.xml:75
+#, no-c-format
+msgid "Web Services Description Language (WSDL)"
+msgstr ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/JBoss_Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Participants.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Participants.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Participants.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,457 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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
+#, 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Preface.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Revision_History.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,26 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Stand-alone_Coordinator.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Stand-alone_Coordinator.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Stand-alone_Coordinator.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,34 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/The_XTS_API.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/The_XTS_API.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/The_XTS_API.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,547 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: The_XTS_API.xml:6
+#, no-c-format
+msgid "The XTS API"
+msgstr ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: The_XTS_API.xml:53
+#, no-c-format
+msgid "TxContext"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserTransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:87
+#, no-c-format
+msgid ""
+"UserTransactions are obtained from a <code>UserTransactionFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:92
+#, 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
+#, no-c-format
+msgid "TransactionFactory"
+msgstr ""
+
+#. Tag: para
+#: The_XTS_API.xml:123
+#, no-c-format
+msgid ""
+"TransactionManagers are obtained from a <code>TransactionFactory</code>."
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "UserBusinessActivity"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:151
+#, no-c-format
+msgid ""
+"UserBusinessActivities are obtained from a "
+"<code>UserBusinessActivityFactory</code>."
+msgstr ""
+
+#. Tag: title
+#: The_XTS_API.xml:156
+#, no-c-format
+msgid "BusinessActivityManager"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: The_XTS_API.xml:187
+#, no-c-format
+msgid ""
+"BusinessActivityManagers are obtained from a "
+"<code>BusinessActivityManagerFactory</code>."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactional_Web_Services.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactional_Web_Services.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactional_Web_Services.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,106 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactional_Web_Services.xml:6
+#, no-c-format
+msgid "Transactional Web Services"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactional_Web_Services.xml:15
+#, no-c-format
+msgid "A Transactional Web Service"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: Transactional_Web_Services.xml:26
+#, no-c-format
+msgid "Context Handlers Registered with the SOAP Server"
+msgstr ""
+
+#. 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: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,654 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Transactions_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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: Transactions_Overview.xml:84
+#, no-c-format
+msgid "ACID Transactions"
+msgstr ""
+
+#. 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 ""
+
+#. Tag: para
+#: Transactions_Overview.xml:91
+#, no-c-format
+msgid "Atomicity: The transaction executes completely or not at all."
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/Transactions_Web_Services_Programmers_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-09-23 06:35:15 UTC (rev 78771)
@@ -0,0 +1,950 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:34+0000\n"
+"PO-Revision-Date: 2008-09-23 06:34+0000\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: title
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:20
+#, no-c-format
+msgid "WS-Coordination"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. 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 ""
+
+#. Tag: caption
+#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:68
+#, no-c-format
+msgid "WS-C infrastructure"
+msgstr ""
+
+#. 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 ""
+"<!-- Activation Service portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"CreateCoordinationContext\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContext\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Activation Requester portType Declaration -->\n"
+"<wsdl:portType name=\"ActivationRequesterPortType\">\n"
+" <wsdl:operation \n"
+" name=\"CreateCoordinationContextResponse\">\n"
+" <wsdl:input \n"
+" message=\"wscoor:CreateCoordinationContextResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\\"
+msgstr ""
+
+#. 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 ""
+"<!-- Registration Service portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationCoordinatorPortType\">\n"
+" <wsdl:operation name=\"Register\">\n"
+" <wsdl:input message=\"wscoor:Register\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>\n"
+" \n"
+"<!-- Registration Requester portType Declaration -->\n"
+"<wsdl:portType name=\"RegistrationRequesterPortType\">\n"
+" <wsdl:operation name=\"RegisterResponse\">\n"
+" <wsdl:input message=\"wscoor:RegisterResponse\"/>\n"
+" </wsdl:operation>\n"
+" <wsdl:operation name=\"Error\">\n"
+" <wsdl:input message=\"wscoor:Error\"/>\n"
+" </wsdl:operation>\n"
+"</wsdl:portType>"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination Foundations"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Coordination WS-Atomic Transaction and WS-Business Activity"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Architecture"
+msgstr ""
+
+#. 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
+#, 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "WS-Transaction Models"
+msgstr ""
+
+#. 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, 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 ""
+
+#. 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
+#, no-c-format
+msgid "Business Activities (BA)"
+msgstr ""
+
+#. 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
+#, no-c-format
+msgid "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
+msgstr ""
+
+#. 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 ""
+
+#. 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 ""
More information about the jboss-cvs-commits
mailing list