[jboss-svn-commits] JBL Code SVN: r24086 - labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Web_Services_Programmers_Guide/zh-CN.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Tue Nov 25 00:23:58 EST 2008
Author: xhuang at jboss.com
Date: 2008-11-25 00:23:58 -0500 (Tue, 25 Nov 2008)
New Revision: 24086
Modified:
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
Log:
update
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-11-25 05:15:57 UTC (rev 24085)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Web_Services_Programmers_Guide/zh-CN/WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.po 2008-11-25 05:23:58 UTC (rev 24086)
@@ -8,7 +8,7 @@
"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-23 06:34+0000\n"
-"PO-Revision-Date: 2008-11-25 14:15+1000\n"
+"PO-Revision-Date: 2008-11-25 15:23+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -622,6 +622,9 @@
"the coordinator sends the commit message to participants, who will make "
"permanent the tentative work done by their associated services."
msgstr ""
+"Assuming no failures occurred during the first phase, in the second phase "
+"the coordinator sends the commit message to participants, who will make "
+"permanent the tentative work done by their associated services."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:192
@@ -635,6 +638,13 @@
"transaction coordinator need not record information about the decision since "
"the outcome of the transaction is solely down to that single participant."
msgstr ""
+"If a transaction involves only a single participant, WS-Atomic Transaction "
+"supports a one-phase commit optimization. Since there is only one "
+"participant, its decisions implicitly reach consensus, and so the "
+"coordinator need not drive the transaction through both phases. In the "
+"optimized case, the participant will simply be told to commit and the "
+"transaction coordinator need not record information about the decision since "
+"the outcome of the transaction is solely down to that single participant."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:195
@@ -646,6 +656,11 @@
"participant; the coordinator generated messages are shown in the solid line, "
"whereas the participant messages are shown by dashed lines."
msgstr ""
+"The figure below<footnote> <para> Redrawn from the WS-Atomic Transaction "
+"specification. </para> </footnote> shows the state transitions of a WS-"
+"Atomic Transaction and the message exchanges between coordinator and "
+"participant; the coordinator generated messages are shown in the solid line, "
+"whereas the participant messages are shown by dashed lines."
#. Tag: caption
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:206
@@ -662,6 +677,10 @@
"application whether the transaction was committed or rolled back. "
"Additionally, the Volatile2PC protocol may complete."
msgstr ""
+"Once the 2PC protocol has finished, the Completion protocol that originally "
+"began the termination of the transaction can complete, and inform the client "
+"application whether the transaction was committed or rolled back. "
+"Additionally, the Volatile2PC protocol may complete."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:211
@@ -672,6 +691,10 @@
"so that they can release resources (for example, put a database connection "
"back into the pool of connections)."
msgstr ""
+"Like the prepare phase of Volatile2PC, the final phase is optional and can "
+"be used to inform participants when the transaction has completed, typically "
+"so that they can release resources (for example, put a database connection "
+"back into the pool of connections)."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:214
@@ -684,6 +707,12 @@
"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
"the transaction."
msgstr ""
+"Any registered Volatile2PC participants are invoked after the transaction "
+"has terminated and are told the state in which the transaction completed "
+"(the coordinator sends either the Committed or Aborted message). Since the "
+"transaction has terminated, any failures of participants at this stage are "
+"ignored –it is essentially a courtesy, and has no bearing on the outcome of "
+"the transaction."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:217
@@ -693,18 +722,21 @@
"possible to see the intricate interweaving of individual protocols that goes "
"to make up the AT as a whole in the following figure."
msgstr ""
+"Finally, after having gone through each of the stages in an AT, it is "
+"possible to see the intricate interweaving of individual protocols that goes "
+"to make up the AT as a whole in the following figure."
#. Tag: caption
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:224
#, no-c-format
msgid "The AT Model"
-msgstr ""
+msgstr "AT 模型"
#. Tag: title
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:227
#, no-c-format
msgid "Business Activities (BA)"
-msgstr ""
+msgstr "商业活动（Business Activities，BA）"
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:228
@@ -725,6 +757,20 @@
"users concurrently); a user may subsequently find that the item is no longer "
"available, or may have to be reordered specially for them."
msgstr ""
+"Most business-to-business applications require transactional support in "
+"order to guarantee consistent outcome and correct execution. These "
+"applications often involve long running computations, loosely coupled "
+"systems and components that do not share data, location, or administration "
+"and it is difficult to incorporate atomic transactions within such "
+"architectures. For example, an online bookshop may reserve books for an "
+"individual for a specific period of time, but if the individual does not "
+"purchase the books within that period they will be “put back onto the shelf” "
+"for others to buy. Furthermore, because it is not possible for anyone to "
+"have an infinite supply of stock, some online shops may appear to users to "
+"reserve items for them, but in fact may allow others to pre-empt that "
+"reservation (for instance, the same book may be “reserved” for multiple "
+"users concurrently); a user may subsequently find that the item is no longer "
+"available, or may have to be reordered specially for them."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:232
@@ -741,6 +787,16 @@
"of the WS-Business Activity specification, but an implementation decision "
"for the service provider."
msgstr ""
+"A business activity or BA is designed specifically for these kinds of long-"
+"duration interactions, where exclusively locking resources is impossible or "
+"impractical. In this model services are requested to do work, and where "
+"those services have the ability to undo any work, they inform the BA such "
+"that if the BA later decides the cancel the work (for instance if the "
+"business activity suffers a failure), it can instruct the service to execute "
+"its undo behavior. The key point for Business Activities is that how "
+"services do their work and provide compensation mechanisms is not the domain "
+"of the WS-Business Activity specification, but an implementation decision "
+"for the service provider."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:235
@@ -751,6 +807,10 @@
"wrap their proprietary mechanisms and interoperate across implementations "
"and business boundaries."
msgstr ""
+"The WS- Business Activity simply defines a protocol for Web services-based "
+"applications to enable existing business processing and workflow systems to "
+"wrap their proprietary mechanisms and interoperate across implementations "
+"and business boundaries."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:238
@@ -766,6 +826,15 @@
"experiences an error, it can be caught by the parent who may be able to "
"compensate and continue processing."
msgstr ""
+"A business activity may be partitioned into scopes, where a scope is a "
+"business task or unit of work using a collection of Web services. Such "
+"scopes can be nested to arbitrary degrees, forming parent and child "
+"relationships, where a parent scope has the ability to select which child "
+"tasks are to be included in the overall outcome protocol for a specific "
+"business activity, and so clearly non-atomic outcomes are possible. In a "
+"similar manner to traditional nested transactions, if a child task "
+"experiences an error, it can be caught by the parent who may be able to "
+"compensate and continue processing."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:241
@@ -776,6 +845,10 @@
"the latter case, the compensation task may be called by the parent should it "
"ultimately need to undo the work performed by the child."
msgstr ""
+"When a child task completes it can either leave the business activity or "
+"signal to the parent that the work it has done can be compensated later. In "
+"the latter case, the compensation task may be called by the parent should it "
+"ultimately need to undo the work performed by the child."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:244
@@ -790,12 +863,20 @@
"transaction to admit to having failed – a well designed Business Activities "
"should be proactive, if it is to perform well."
msgstr ""
+"Unlike the WS-Atomic Transaction protocol model, where participants inform "
+"the coordinator of their state only when asked, a task within a business "
+"activity can specify its outcome to the parent directly without waiting for "
+"a request. This feature is useful when tasks fail such that the notification "
+"can be used by business activity exception handler to modify the goals and "
+"drive processing forward without having to meekly wait until the end of the "
+"transaction to admit to having failed – a well designed Business Activities "
+"should be proactive, if it is to perform well."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:247
#, no-c-format
msgid "Underpinning all of this are three fundamental assumptions:"
-msgstr ""
+msgstr "Underpinning all of this are three fundamental assumptions:"
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:252
@@ -804,6 +885,8 @@
"All state transitions are reliably recorded, including application state and "
"coordination metadata (the record of sent and received messages);"
msgstr ""
+"All state transitions are reliably recorded, including application state and "
+"coordination metadata (the record of sent and received messages);"
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:257
@@ -813,6 +896,9 @@
"early as possible. This avoids executing unnecessary tasks and can also "
"detect a problem earlier when rectifying it is simpler and less expensive;"
msgstr ""
+"All request messages are acknowledged, so that problems are detected as "
+"early as possible. This avoids executing unnecessary tasks and can also "
+"detect a problem earlier when rectifying it is simpler and less expensive;"
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:262
@@ -825,6 +911,12 @@
"This is repeated until a response is received. The request receiver discards "
"all but one identical request received."
msgstr ""
+"As with atomic transactions, a response is defined as a separate operation "
+"and not as the output of the request. Message input-output implementations "
+"will typically have timeouts that are too short for some business activity "
+"responses. If the response is not received after a timeout, it is resent. "
+"This is repeated until a response is received. The request receiver discards "
+"all but one identical request received."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:267
@@ -836,6 +928,11 @@
"AT protocol which is driven from the coordinator down to participants, this "
"protocol is driven much more from the participants upwards."
msgstr ""
+"As with atomic transactions, the business activity model has multiple "
+"protocols: <code>BusinessAgreementWithParticipantCompletion</code> and "
+"<code>BusinessAgreementWithCoordinatorCompletion</code>. However, unlike the "
+"AT protocol which is driven from the coordinator down to participants, this "
+"protocol is driven much more from the participants upwards."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:270
@@ -854,6 +951,18 @@
"indicating that the parent activity requires that the child task reverse its "
"work."
msgstr ""
+"Under the <code>BusinessAgreementWithParticipantCompletion</code> protocol, "
+"a child activity is initially created in the Active state; if it finishes "
+"the work it was created to do and no more participation is required within "
+"the scope of the BA (such as when the activity operates on immutable data), "
+"then the child can unilaterally send an exited message to the parent. "
+"However, if the child task finishes and wishes to continue in the BA then it "
+"must be able to compensate for the work it has performed. In this case it "
+"sends a completed message to the parent and waits to receive the final "
+"outcome of the BA from the parent. This outcome will either be a close "
+"message, meaning the BA has completed successfully or a compensate message "
+"indicating that the parent activity requires that the child task reverse its "
+"work."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:273
@@ -868,6 +977,14 @@
"sending the complete message to the child. The child then acts as it does in "
"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
msgstr ""
+"The <code>BusinessAgreementWithCoordinatorCompletion</code> protocol is "
+"identical to the <code>BusinessAgreementWithParticipantCompletion</code> "
+"protocol with the exception that the child cannot autonomously decide to end "
+"its participation in the business activity, even if it can be compensated. "
+"Rather the child task relies upon the parent to inform it when the child has "
+"received all requests for it to perform work which the parent does by "
+"sending the complete message to the child. The child then acts as it does in "
+"the <code>BusinessAgreementWithParticipantCompletion</code> protocol."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:276
@@ -877,6 +994,9 @@
"participation of services that cannot or will not lock resources for "
"extended periods."
msgstr ""
+"The crux of the BA model compared to the AT model is that is allows the "
+"participation of services that cannot or will not lock resources for "
+"extended periods."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:279
@@ -888,12 +1008,17 @@
"the developers of the services under control of the BA. Such compensations "
"may use backward error recovery, but will typically employ forward recovery."
msgstr ""
+"While the full ACID semantics are not maintained by a BA, consistency can "
+"still be maintained through compensation, though the task of writing correct "
+"compensating actions (and thus overall system consistency) is delegated to "
+"the developers of the services under control of the BA. Such compensations "
+"may use backward error recovery, but will typically employ forward recovery."
#. Tag: title
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:283
#, no-c-format
msgid "Application Messages"
-msgstr ""
+msgstr "应用程序消息"
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:284
@@ -906,6 +1031,12 @@
"appropriate Web services protocol. In XTS, the transaction context is "
"propagated within the headers of SOAP messages."
msgstr ""
+"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."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:289
@@ -924,12 +1055,24 @@
"aware) may ignore the context; the important point here is that XTS manages "
"contexts without user intervention."
msgstr ""
+"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."
#. 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 ""
+msgstr "WS-C, WS-Atomic Transaction and WS-Business Activity Messages"
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:295
@@ -941,6 +1084,11 @@
"kinds of exchanges occur so that the underlying model can be fitted in to an "
"overall architecture."
msgstr ""
+"Although the application or service developer rarely sees or is interested "
+"in the messages exchanged by the transactional infrastructure (the "
+"transaction manager and any participants), it is useful to understand what "
+"kinds of exchanges occur so that the underlying model can be fitted in to an "
+"overall architecture."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:299
@@ -951,6 +1099,10 @@
"messages that are propagated include instructions to perform standard "
"transaction operations like begin, prepare."
msgstr ""
+"In XTS, WS-C, WS-Atomic Transaction and WS-Business Activity-specific "
+"messages are transported using SOAP messaging over HTTP. The types of "
+"messages that are propagated include instructions to perform standard "
+"transaction operations like begin, prepare."
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:303
@@ -963,12 +1115,18 @@
"specific messages using SOAP RPC over SMTP even though under the covers the "
"XTS messages are delivered using a different mechanism."
msgstr ""
+"XTS messages do not interfere in any way, shape, or form, with the "
+"application messages, and nor is there any requirement for an application to "
+"use the same transport as the transaction-specific messages. For example, it "
+"is quite reasonable for a client application to deliver its application-"
+"specific messages using SOAP RPC over SMTP even though under the covers the "
+"XTS messages are delivered using a different mechanism."
#. Tag: title
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:310
#, no-c-format
msgid "Summary"
-msgstr ""
+msgstr "总结"
#. Tag: para
#: WS-C_WS-Atomic_Transaction_and_WS-Business_Activity_Overview.xml:311
@@ -986,4 +1144,15 @@
"application separate, and to ensure that the transactionality of a system "
"does not interfere with the functional aspects of the system itself."
msgstr ""
+"XTS provides a coordination infrastructure designed to allow transactions to "
+"run between enterprises across the Internet. That infrastructure is based on "
+"the WS-C, WS-Atomic Transaction and WS-Business Activity specifications. It "
+"supports two kinds of transactions: atomic transactions and business "
+"activities, which can be combined in arbitrary ways to map elegantly onto "
+"the transactional requirements of the underlying problem. The use of the "
+"whole infrastructure is simple due to the fact that its functionality is "
+"exposed through a simple transactioning API. Furthermore XTS provides all of "
+"the necessary plumbing to keep application and transactional aspects of an "
+"application separate, and to ensure that the transactionality of a system "
+"does not interfere with the functional aspects of the system itself."
More information about the jboss-svn-commits
mailing list