[jboss-cvs] JBossAS SVN: r79436 - projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/pt-BR.

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

Author: ldelima at redhat.com
Date: 2008-10-13 22:18:45 -0400 (Mon, 13 Oct 2008)
New Revision: 79436

Modified:
   projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/pt-BR/Introduction.po
Log:
translation ongoing

Modified: projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/pt-BR/Introduction.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/pt-BR/Introduction.po	2008-10-14 02:18:11 UTC (rev 79435)
+++ projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/pt-BR/Introduction.po	2008-10-14 02:18:45 UTC (rev 79436)
@@ -223,6 +223,16 @@
 "transaction context. So you can start another transaction on pojo2 and it "
 "will succeed."
 msgstr ""
+"Transaction. The POJO operation can be transacted once a TransactionManager "
+"is specified properly. Upon user rollback, it will rollback all POJO "
+"operations as well. Note that the transaction context only applies to the "
+"node level though. That is, in a complex object graph where you have "
+"multiple sub-nodes, only the nodes (or fields) accessed by a user are under "
+"transaction context. To give an example, if I have a POJO that has field "
+"references to another two POJOs (say, pojo1 and pojo2). When pojo1 is "
+"modified and under transaction context, pojo2 is not under the same "
+"transaction context. So you can start another transaction on pojo2 and it "
+"will succeed."
 
 #. Tag: para
 #: Introduction.xml:77