[jboss-cvs] JBossAS SVN: r68119 - projects/docs/trunk/Server_Configuration_Guide/es-ES.

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

Author: xhuang at jboss.com
Date: 2007-12-10 17:27:30 -0500 (Mon, 10 Dec 2007)
New Revision: 68119

Removed:
   projects/docs/trunk/Server_Configuration_Guide/es-ES/J2EE_Transactions_On_JBOSS.po
Log:
Merge with latest en-US

Deleted: projects/docs/trunk/Server_Configuration_Guide/es-ES/J2EE_Transactions_On_JBOSS.po
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/es-ES/J2EE_Transactions_On_JBOSS.po	2007-12-10 22:26:23 UTC (rev 68118)
+++ projects/docs/trunk/Server_Configuration_Guide/es-ES/J2EE_Transactions_On_JBOSS.po	2007-12-10 22:27:30 UTC (rev 68119)
@@ -1,760 +0,0 @@
-# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
-# Automatically generated, 2007.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: JBEAP 420\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2007-11-06 22:32+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\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
-#: J2EE_Transactions_On_JBOSS.xml:6
-#, fuzzy, no-c-format
-msgid "Transactions on JBoss"
-msgstr "Transacciones y Concurrencia"
-
-#. Tag: subtitle
-#: J2EE_Transactions_On_JBOSS.xml:7
-#, fuzzy, no-c-format
-msgid "The JTA Transaction Service"
-msgstr "TransactionManagers de JTA"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:8
-#, no-c-format
-msgid ""
-"This chapter discusses transaction management in JBoss and the JBossTX "
-"architecture. The JBossTX architecture allows for any Java Transaction API "
-"(JTA) transaction manager implementation to be used. JBossTX includes a fast "
-"in-VM implementation of a JTA compatible transaction manager that is used as "
-"the default transaction manager. We will first provide an overview of the "
-"key transaction concepts and notions in the JTA to provide sufficient "
-"background for the JBossTX architecture discussion. We will then discuss the "
-"interfaces that make up the JBossTX architecture and conclude with a "
-"discussion of the MBeans available for integration of alternate transaction "
-"managers."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:12
-#, fuzzy, no-c-format
-msgid "Transaction/JTA Overview"
-msgstr "Tiempo de espera de la transacción"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:13
-#, no-c-format
-msgid ""
-"For the purpose of this discussion, we can define a transaction as a unit of "
-"work containing one or more operations involving one or more shared "
-"resources having ACID properties. ACID is an acronym for atomicity, "
-"consistency, isolation and durability, the four important properties of "
-"transactions. The meanings of these terms is:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:18
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Atomicity</emphasis>: A transaction must be atomic. "
-"This means that either all the work done in the transaction must be "
-"performed, or none of it must be performed. Doing part of a transaction is "
-"not allowed."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:23
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Consistency</emphasis>: When a transaction is "
-"completed, the system must be in a stable and consistent condition."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:28
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Isolation</emphasis>: Different transactions must be "
-"isolated from each other. This means that the partial work done in one "
-"transaction is not visible to other transactions until the transaction is "
-"committed, and that each process in a multi-user system can be programmed as "
-"if it was the only process accessing the system."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:33
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Durability</emphasis>: The changes made during a "
-"transaction are made persistent when it is committed. When a transaction is "
-"committed, its changes will not be lost, even if the server crashes "
-"afterwards."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:38
-#, no-c-format
-msgid ""
-"To illustrate these concepts, consider a simple banking account application. "
-"The banking application has a database with a number of accounts. The sum of "
-"the amounts of all accounts must always be 0. An amount of money M is moved "
-"from account A to account B by subtracting M from account A and adding M to "
-"account B. This operation must be done in a transaction, and all four ACID "
-"properties are important."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:41
-#, no-c-format
-msgid ""
-"The atomicity property means that both the withdrawal and deposit is "
-"performed as an indivisible unit. If, for some reason, both cannot be done "
-"nothing will be done."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:44
-#, no-c-format
-msgid ""
-"The consistency property means that after the transaction, the sum of the "
-"amounts of all accounts must still be 0."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:47
-#, no-c-format
-msgid ""
-"The isolation property is important when more than one bank clerk uses the "
-"system at the same time. A withdrawal or deposit could be implemented as a "
-"three-step process: First the amount of the account is read from the "
-"database; then something is subtracted from or added to the amount read from "
-"the database; and at last the new amount is written to the database. Without "
-"transaction isolation several bad things could happen. For example, if two "
-"processes read the amount of account A at the same time, and each "
-"independently added or subtracted something before writing the new amount to "
-"the database, the first change would be incorrectly overwritten by the last."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:50
-#, no-c-format
-msgid ""
-"The durability property is also important. If a money transfer transaction "
-"is committed, the bank must trust that some subsequent failure cannot undo "
-"the money transfer."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:54
-#, fuzzy, no-c-format
-msgid "Pessimistic and optimistic locking"
-msgstr "Bloqueo pesimista"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:55
-#, no-c-format
-msgid ""
-"Transactional isolation is usually implemented by locking whatever is "
-"accessed in a transaction. There are two different approaches to "
-"transactional locking: Pessimistic locking and optimistic locking."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:58
-#, no-c-format
-msgid ""
-"The disadvantage of pessimistic locking is that a resource is locked from "
-"the time it is first accessed in a transaction until the transaction is "
-"finished, making it inaccessible to other transactions during that time. If "
-"most transactions simply look at the resource and never change it, an "
-"exclusive lock may be overkill as it may cause lock contention, and "
-"optimistic locking may be a better approach. With pessimistic locking, locks "
-"are applied in a fail-safe way. In the banking application example, an "
-"account is locked as soon as it is accessed in a transaction. Attempts to "
-"use the account in other transactions while it is locked will either result "
-"in the other process being delayed until the account lock is released, or "
-"that the process transaction will be rolled back. The lock exists until the "
-"transaction has either been committed or rolled back."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:61
-#, no-c-format
-msgid ""
-"With optimistic locking, a resource is not actually locked when it is first "
-"is accessed by a transaction. Instead, the state of the resource at the time "
-"when it would have been locked with the pessimistic locking approach is "
-"saved. Other transactions are able to concurrently access to the resource "
-"and the possibility of conflicting changes is possible. At commit time, when "
-"the resource is about to be updated in persistent storage, the state of the "
-"resource is read from storage again and compared to the state that was saved "
-"when the resource was first accessed in the transaction. If the two states "
-"differ, a conflicting update was made, and the transaction will be rolled "
-"back."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:64
-#, no-c-format
-msgid ""
-"In the banking application example, the amount of an account is saved when "
-"the account is first accessed in a transaction. If the transaction changes "
-"the account amount, the amount is read from the store again just before the "
-"amount is about to be updated. If the amount has changed since the "
-"transaction began, the transaction will fail itself, otherwise the new "
-"amount is written to persistent storage."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:70
-#, no-c-format
-msgid "The components of a distributed transaction"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:71
-#, no-c-format
-msgid ""
-"There are a number of participants in a distributed transaction. These "
-"include:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:76
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transaction Manager</emphasis>: This component is "
-"distributed across the transactional system. It manages and coordinates the "
-"work involved in the transaction. The transaction manager is exposed by the "
-"<literal>javax.transaction.TransactionManager</literal> interface in JTA."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:81
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transaction Context</emphasis>: A transaction "
-"context identifies a particular transaction. In JTA the corresponding "
-"interface is <literal>javax.transaction.Transaction</literal>."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:86
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transactional Client</emphasis>: A transactional "
-"client can invoke operations on one or more transactional objects in a "
-"single transaction. The transactional client that started the transaction is "
-"called the transaction originator. A transaction client is either an "
-"explicit or implicit user of JTA interfaces and has no interface "
-"representation in the JTA."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:91
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transactional Object</emphasis>: A transactional "
-"object is an object whose behavior is affected by operations performed on it "
-"within a transactional context. A transactional object can also be a "
-"transactional client. Most Enterprise Java Beans are transactional objects."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:96
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Recoverable Resource</emphasis>: A recoverable "
-"resource is a transactional object whose state is saved to stable storage if "
-"the transaction is committed, and whose state can be reset to what it was at "
-"the beginning of the transaction if the transaction is rolled back. At "
-"commit time, the transaction manager uses the two-phase XA protocol when "
-"communicating with the recoverable resource to ensure transactional "
-"integrity when more than one recoverable resource is involved in the "
-"transaction being committed. Transactional databases and message brokers "
-"like JBossMQ are examples of recoverable resources. A recoverable resource "
-"is represented using the <literal>javax.transaction.xa.XAResource</literal> "
-"interface in JTA."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:104
-#, no-c-format
-msgid "The two-phase XA protocol"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:105
-#, no-c-format
-msgid ""
-"When a transaction is about to be committed, it is the responsibility of the "
-"transaction manager to ensure that either all of it is committed, or that "
-"all of is rolled back. If only a single recoverable resource is involved in "
-"the transaction, the task of the transaction manager is simple: It just has "
-"to tell the resource to commit the changes to stable storage."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:108
-#, no-c-format
-msgid ""
-"When more than one recoverable resource is involved in the transaction, "
-"management of the commit gets more complicated. Simply asking each of the "
-"recoverable resources to commit changes to stable storage is not enough to "
-"maintain the atomic property of the transaction. The reason for this is that "
-"if one recoverable resource has committed and another fails to commit, part "
-"of the transaction would be committed and the other part rolled back."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:111
-#, no-c-format
-msgid ""
-"To get around this problem, the two-phase XA protocol is used. The XA "
-"protocol involves an extra prepare phase before the actual commit phase. "
-"Before asking any of the recoverable resources to commit the changes, the "
-"transaction manager asks all the recoverable resources to prepare to commit. "
-"When a recoverable resource indicates it is prepared to commit the "
-"transaction, it has ensured that it can commit the transaction. The resource "
-"is still able to rollback the transaction if necessary as well."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:114
-#, no-c-format
-msgid ""
-"So the first phase consists of the transaction manager asking all the "
-"recoverable resources to prepare to commit. If any of the recoverable "
-"resources fails to prepare, the transaction will be rolled back. But if all "
-"recoverable resources indicate they were able to prepare to commit, the "
-"second phase of the XA protocol begins. This consists of the transaction "
-"manager asking all the recoverable resources to commit the transaction. "
-"Because all the recoverable resources have indicated they are prepared, this "
-"step cannot fail."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:120
-#, fuzzy, no-c-format
-msgid "Heuristic exceptions"
-msgstr "manejar excepciones"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:121
-#, no-c-format
-msgid ""
-"In a distributed environment communications failures can happen. If "
-"communication between the transaction manager and a recoverable resource is "
-"not possible for an extended period of time, the recoverable resource may "
-"decide to unilaterally commit or rollback changes done in the context of a "
-"transaction. Such a decision is called a heuristic decision. It is one of "
-"the worst errors that may happen in a transaction system, as it can lead to "
-"parts of the transaction being committed while other parts are rolled back, "
-"thus violating the atomicity property of transaction and possibly leading to "
-"data integrity corruption."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:124
-#, no-c-format
-msgid ""
-"Because of the dangers of heuristic exceptions, a recoverable resource that "
-"makes a heuristic decision is required to maintain all information about the "
-"decision in stable storage until the transaction manager tells it to forget "
-"about the heuristic decision. The actual data about the heuristic decision "
-"that is saved in stable storage depends on the type of recoverable resource "
-"and is not standardized. The idea is that a system manager can look at the "
-"data, and possibly edit the resource to correct any data integrity problems."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:127
-#, no-c-format
-msgid ""
-"There are several different kinds of heuristic exceptions defined by the "
-"JTA. The <literal>javax.transaction.HeuristicCommitException</literal> is "
-"thrown when a recoverable resource is asked to rollback to report that a "
-"heuristic decision was made and that all relevant updates have been "
-"committed. On the opposite end is the <literal>javax.transaction."
-"HeuristicRollbackException</literal>, which is thrown by a recoverable "
-"resource when it is asked to commit to indicate that a heuristic decision "
-"was made and that all relevant updates have been rolled back."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:130
-#, no-c-format
-msgid ""
-"The <literal>javax.transaction.HeuristicMixedException</literal> is the "
-"worst heuristic exception. It is thrown to indicate that parts of the "
-"transaction were committed, while other parts were rolled back. The "
-"transaction manager throws this exception when some recoverable resources "
-"did a heuristic commit, while other recoverable resources did a heuristic "
-"rollback."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:136
-#, fuzzy, no-c-format
-msgid "Transaction IDs and branches"
-msgstr "Transacciones y Concurrencia"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:137
-#, no-c-format
-msgid ""
-"In JTA, the identity of transactions is encapsulated in objects implementing "
-"the <literal>javax.transaction.xa.Xid</literal> interface. The transaction "
-"ID is an aggregate of three parts:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:142
-#, no-c-format
-msgid ""
-"The format identifier indicates the transaction family and tells how the "
-"other two parts should be interpreted."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:147
-#, no-c-format
-msgid ""
-"The global transaction id identified the global transaction within the "
-"transaction family."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:152
-#, no-c-format
-msgid ""
-"The branch qualifier denotes a particular branch of the global transaction."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:157
-#, no-c-format
-msgid ""
-"Transaction branches are used to identify different parts of the same global "
-"transaction. Whenever the transaction manager involves a new recoverable "
-"resource in a transaction it creates a new transaction branch."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:165
-#, fuzzy, no-c-format
-msgid "JBoss Transaction Internals"
-msgstr "TransactionManagers de JTA"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:166
-#, no-c-format
-msgid ""
-"The JBoss application server is written to be independent of the actual "
-"transaction manager used. JBoss uses the JTA <literal>javax.transaction."
-"TransactionManager</literal> interface as its view of the server transaction "
-"manager. Thus, JBoss may use any transaction manager which implements the "
-"JTA <literal>TransactionManager</literal> interface. Whenever a transaction "
-"manager is used it is obtained from the well-known JNDI location, "
-"<literal>java:/TransactionManager</literal>. This is the globally available "
-"access point for the server transaction manager."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:169
-#, no-c-format
-msgid ""
-"If transaction contexts are to be propagated with RMI/JRMP calls, the "
-"transaction manager must also implement two simple interfaces for the import "
-"and export of transaction propagation contexts (TPCs). The interfaces are "
-"<literal>TransactionPropagationContextImporter</literal>, and "
-"<literal>TransactionPropagationContextFactory</literal>, both in the "
-"<literal>org.jboss.tm</literal> package."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:172
-#, no-c-format
-msgid ""
-"Being independent of the actual transaction manager used also means that "
-"JBoss does not specify the format of type of the transaction propagation "
-"contexts used. In JBoss, a TPC is of type <literal>Object</literal>, and the "
-"only requirement is that the TPC must implementation the <literal>java.io."
-"Serializable</literal> interface."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:175
-#, no-c-format
-msgid ""
-"When using the RMI/JRMP protocol for remote calls, the TPC is carried as a "
-"field in the <literal>org.jboss.ejb.plugins.jrmp.client."
-"RemoteMethodInvocation</literal> class that is used to forward remote method "
-"invocation requests."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:179
-#, fuzzy, no-c-format
-msgid "Adapting a Transaction Manager to JBoss"
-msgstr "TransactionManagers de JTA"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:180
-#, no-c-format
-msgid ""
-"A transaction manager has to implement the Java Transaction API to be easily "
-"integrated with JBoss. As almost everything in JBoss, the transaction "
-"manager is managed as an MBean. Like all JBoss services, it should implement "
-"<literal>org.jboss.system.ServiceMBean</literal> to ensure proper life-cycle "
-"management."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:183
-#, no-c-format
-msgid ""
-"The primary requirement of the transaction manager service on startup is "
-"that it binds its implementation of the three required interfaces into JNDI. "
-"These interfaces and their JNDI locations are:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:188
-#, no-c-format
-msgid ""
-"The <literal>javax.transaction.TransactionManager</literal> interface is "
-"used by the application server to manage transactions on behalf of the "
-"transactional objects that use container managed transactions. It must be "
-"bound under the JNDI name <literal>java:/TransactionManager</literal>."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:193
-#, no-c-format
-msgid ""
-"The <literal>TransactionPropagationContextFactory</literal> interface is "
-"called by JBoss whenever a transaction propagation context is needed for "
-"transporting a transaction with a remote method call. It must be bound under "
-"the JNDI name <literal>java:/TransactionPropagationContextImporter</literal>."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:198
-#, no-c-format
-msgid ""
-"The <literal>TransactionPropagationContextImporter</literal> interface is "
-"called by JBoss whenever a transaction propagation context from an incoming "
-"remote method invocation has to be converted to a transaction that can be "
-"used within the receiving JBoss server VM."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:203
-#, no-c-format
-msgid ""
-"Establishing these JNDI bindings is all the transaction manager service "
-"needs to do to install its implementation as the JBoss server transaction "
-"manager."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:209
-#, fuzzy, no-c-format
-msgid "The Default Transaction Manager"
-msgstr "TransactionManagers de JTA"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:210
-#, no-c-format
-msgid ""
-"JBoss is by default configured to use the fast in-VM transaction manager. "
-"This transaction manager is very fast, but does have two limitations."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:215
-#, no-c-format
-msgid ""
-"It does not do transactional logging, and is thus incapable of automated "
-"recovery after a server crash."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:220
-#, no-c-format
-msgid ""
-"While it does support propagating transaction contexts with remote calls, it "
-"does not support propagating transaction contexts to other virtual machines, "
-"so all transactional work must be done in the same virtual machine as the "
-"JBoss server."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:225
-#, no-c-format
-msgid ""
-"The corresponding default transaction manager MBean service is the "
-"<literal>org.jboss.tm.TransactionManagerService</literal> MBean. It has two "
-"configurable attributes:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:230
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">TransactionTimeout</emphasis>: The default "
-"transaction timeout in seconds. The default value is 300 seconds (5 minutes)."
-msgstr ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> establece el "
-"número máximo de milisegundos a esperar por una adquisisión de bloqueo. El "
-"valor por defecto es 15000."
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:235
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">InterruptThreads</emphasis>: Indicates whether or "
-"not the transaction manager should interrupt threads when the transaction "
-"times out. The default value is false."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:240
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">GlobalIdsEnabled</emphasis>: Indicates whether or "
-"not the transaction manager should use global transaction ids. This should "
-"be set to true for transaction demarcation over IIOP. The default value is "
-"true."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:245
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">XidFactory</emphasis>: The JMX <literal>ObjectName</"
-"literal> of the MBean service that provides the <literal>org.jboss.tm."
-"XidFactoryMBean</literal> implementation. The <literal>XidFactoryMBean</"
-"literal> interface is used to create <literal>javax.transaction.xa.Xid</"
-"literal> instances. This is a workaround for XA JDBC drivers that only work "
-"with their own Xid implementation. Examples of such drivers are the older "
-"Oracle XA drivers. The default factory is <literal>jboss:service=XidFactory</"
-"literal>."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:251
-#, no-c-format
-msgid "org.jboss.tm.XidFactory"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:252
-#, no-c-format
-msgid ""
-"The <literal>XidFactory</literal> MBean is a factory for <literal>javax."
-"transaction.xa.Xid</literal> instances in the form of <literal>org.jboss.tm."
-"XidImpl</literal>. The <literal>XidFactory</literal> allows for "
-"customization of the <literal>XidImpl</literal> that it constructs through "
-"the following attributes:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:257
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">BaseGlobalId</emphasis>: This is used for building "
-"globally unique transaction identifiers. This must be set individually if "
-"multiple JBoss instances are running on the same machine. The default value "
-"is the host name of the JBoss server, followed by a slash."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:262
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">GlobalIdNumber</emphasis>: A long value used as "
-"initial transaction id. The default is 0."
-msgstr ""
-"<emphasis role=\"bold\">cookies</emphasis>: Esta es una bandera que indica "
-"si se seguirá el rastro de las sesiones utilizando cookies. Por defecto, es "
-"verdadero."
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:267
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Pad</emphasis>: The pad value determines whether the "
-"byte[] returned by the Xid <literal>getGlobalTransactionId</literal> and "
-"<literal>getBranchQualifier</literal> methods should be equal to maximum 64 "
-"byte length or a variable value &lt;= 64. Some resource managers (Oracle, "
-"for example) require ids that are max length in size."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:277
-#, fuzzy, no-c-format
-msgid "UserTransaction Support"
-msgstr "jta.UserTransaction"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:278
-#, no-c-format
-msgid ""
-"The JTA <literal>javax.transaction.UserTransaction</literal> interface "
-"allows applications to explicitly control transactions. For enterprise "
-"session beans that manage transaction themselves (BMT), a "
-"<literal>UserTransaction</literal> can be obtained by calling the "
-"<literal>getUserTransaction</literal> method on the bean context object, "
-"<literal>javax.ejb.SessionContext</literal>."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:281
-#, no-c-format
-msgid ""
-"The <literal>ClientUserTransactionService</literal> MBean publishes a "
-"<literal>UserTransaction</literal> implementation under the JNDI name "
-"<literal>UserTransaction</literal>. When the <literal>UserTransaction</"
-"literal> is obtained with a JNDI lookup from a external client, a very "
-"simple <literal>UserTransaction</literal> suitable for thin clients is "
-"returned. This <literal>UserTransaction</literal> implementation only "
-"controls the transactions on the server the <literal>UserTransaction</"
-"literal> object was obtained from. Local transactional work done in the "
-"client is not done within the transactions started by this "
-"<literal>UserTransaction</literal> object."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:284
-#, no-c-format
-msgid ""
-"When a <literal>UserTransaction</literal> object is obtained by looking up "
-"JNDI name <literal>UserTransaction</literal> in the same virtual machine as "
-"JBoss, a simple interface to the JTA <literal>TransactionManager</literal> "
-"is returned. This is suitable for web components running in web containers "
-"embedded in JBoss. When components are deployed in an embedded web server, "
-"the deployer will make a JNDI link from the standard <literal>java:comp/"
-"UserTransaction</literal> ENC name to the global <literal>UserTransaction</"
-"literal> binding so that the web components can lookup the "
-"<literal>UserTransaction</literal> instance under JNDI name as specified by "
-"the J2EE."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:287
-#, no-c-format
-msgid ""
-"Note: For BMT beans, do not obtain the <literal>UserTransaction</literal> "
-"interface using a JNDI lookup. Doing this violates the EJB specification, "
-"and the returned <literal>UserTransaction</literal> object does not have the "
-"hooks the EJB container needs to make important checks."
-msgstr ""