[jboss-cvs] JBossAS SVN: r77225 - projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Aug 20 02:14:25 EDT 2008
Author: ldelima at redhat.com
Date: 2008-08-20 02:14:25 -0400 (Wed, 20 Aug 2008)
New Revision: 77225
Modified:
projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po
Log:
translation ongoing
Modified: projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po 2008-08-20 06:14:07 UTC (rev 77224)
+++ projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po 2008-08-20 06:14:25 UTC (rev 77225)
@@ -5,7 +5,7 @@
"Project-Id-Version: Cache_Frequently_Asked_Questions\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-05-30 03:54+0000\n"
-"PO-Revision-Date: 2008-08-20 16:03+1000\n"
+"PO-Revision-Date: 2008-08-20 16:14+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -1084,12 +1084,7 @@
"application code to register a classloader with a portion of the cache tree "
"for use in handling objects replicated to that portion. See the "
"TreeCacheMarshaller section of the user guide for more details."
-msgstr ""
-"To solve the first kind of issue, in JBoss Cache 1.2.4 we introduced the "
-"concept of a <literal>TreeCacheMarshaller</literal> . Basically, this allows "
-"application code to register a classloader with a portion of the cache tree "
-"for use in handling objects replicated to that portion. See the "
-"TreeCacheMarshaller section of the user guide for more details."
+msgstr "Para resolver o primeiro tipo de problema, nós introduzimos, no JBoss Cache 1.2.4, o conceito de um <literal>TreeCacheMarshaller</literal>. Basicamente, isto permite o código do aplicativo registrar o carregador da classe com a porção do cache tree, para uso de manuseio dos objetos replicados daquela porção. Consulte a seção TreeCacheMarshallerdo guia do usuário, para maiores informações."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:941
@@ -1367,13 +1362,13 @@
#: Cache_Frequently_Asked_Questions.xml:1049
#, no-c-format
msgid "JBoss Cache - Pojo Cache"
-msgstr ""
+msgstr "JBoss Cache - Pojo Cache"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1055
#, no-c-format
msgid "What is PojoCache?"
-msgstr ""
+msgstr "O que é o PojoCache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1059
@@ -1390,6 +1385,16 @@
"granularity (i.e., on a per-field basis) update, and thus has the potential "
"to boost cache performance and minimize network traffic."
msgstr ""
+"PojoCache (currently implemented PojoCache as a sub-class of TreeCache) is a "
+"fine-grained field-level replicated and transactional POJO (plain old Java "
+"object) cache. By POJO, we mean that the cache: 1) automatically manages "
+"object mapping and relationship for a client under both local and replicated "
+"cache mode, 2) provides support for inheritance relationship between "
+"\"aspectized\" POJOs. By leveraging the dynamic AOP in JBossAop, it is able "
+"to map a complex object into the cache store, preserve and manage the object "
+"relationship behind the scene. During replication mode, it performs fine-"
+"granularity (i.e., on a per-field basis) update, and thus has the potential "
+"to boost cache performance and minimize network traffic."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1073
@@ -1402,12 +1407,18 @@
"set method will be intercepted by PojoCache to provide the data from the "
"cache."
msgstr ""
+"From a user perspective, once your POJO is managed by the cache, all cache "
+"operations are transparent. Therefore, all the usual in-VM POJO method "
+"semantics are still preserved, providing ease of use. For example, if a POJO "
+"has been put in PojoCache (by calling putObject, for example), then any get/"
+"set method will be intercepted by PojoCache to provide the data from the "
+"cache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1086
#, no-c-format
msgid "What's the relationship between PojoCache and TreeCacheAop classes?"
-msgstr ""
+msgstr "What's the relationship between PojoCache and TreeCacheAop classes?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1090
@@ -1417,12 +1428,15 @@
"reflect the cache nature). The old implementation TreeCacheAop has been "
"deprecated."
msgstr ""
+"Since release 1.4, we have created a new class called PojoCache (to better "
+"reflect the cache nature). The old implementation TreeCacheAop has been "
+"deprecated."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1098
#, no-c-format
msgid "Does PojoCache have all the functional capabilities of TreeCache?"
-msgstr ""
+msgstr "Does PojoCache have all the functional capabilities of TreeCache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1104
@@ -1431,12 +1445,14 @@
"Yes. PojoCache extends TreeCache so it has all the same features TreeCache "
"such as cache mode, transaction isolation level, and eviction policy."
msgstr ""
+"Yes. PojoCache extends TreeCache so it has all the same features TreeCache "
+"such as cache mode, transaction isolation level, and eviction policy."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1113
#, no-c-format
msgid "What is the difference between TreeCache and PojoCache?"
-msgstr ""
+msgstr "What is the difference between TreeCache and PojoCache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1119
@@ -1454,12 +1470,23 @@
"about cache management. Furthermore, this is true in replication mode as "
"well."
msgstr ""
+"Think of PojoCache as a TreeCache on steroids. :-) Seriously, both are cache "
+"stores-- one is a generic cache and the other other one POJO Cache. However, "
+"while TreeCache only provides pure object reference storage (e.g., "
+"<literal>put(FQN fqn, Object key, Object value) </literal> ), PojoCache goes "
+"beyond that and performs fine-grained field level replication object mapping "
+"and relationship management for a user behind the scenes. As a result, if "
+"you have complex object systems that you would like to cache, you can have "
+"PojoCache manage it for you. You simply treat your object systems as they "
+"are residing in-memory, e.g., use your regular POJO methods without worrying "
+"about cache management. Furthermore, this is true in replication mode as "
+"well."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1140
#, no-c-format
msgid "What are the steps to use the PojoCache feature?"
-msgstr ""
+msgstr "What are the steps to use the PojoCache feature?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1144
@@ -1468,6 +1495,8 @@
"Starting from release 1.3, depends on the JDK you use, it has slightly "
"different steps. But in general, in order to use PojoCache, you will need to:"
msgstr ""
+"Starting from release 1.3, depends on the JDK you use, it has slightly "
+"different steps. But in general, in order to use PojoCache, you will need to:"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1151
@@ -1478,6 +1507,10 @@
"part of JVM spec). If you use JDK14, you will also need a annotation pre-"
"compiler (annoc) to pre-process it."
msgstr ""
+"prepare POJO. You can do either via xml declaration or annotation. For "
+"annotation, you can use either the JDK1.4 style or JDK50 one (of which is "
+"part of JVM spec). If you use JDK14, you will also need a annotation pre-"
+"compiler (annoc) to pre-process it."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1159
@@ -1489,6 +1522,11 @@
"however, you need either a special system class loader or, in JDK50, you can "
"use the javaagent option."
msgstr ""
+"instrumentation. You will need to instrument your POJO either at compile-"
+"time or load-time. If you do it during compile-time, you use so-called aop "
+"pre-compiler (aopc) to do bytecode manipulation. If you do it via load-time, "
+"however, you need either a special system class loader or, in JDK50, you can "
+"use the javaagent option."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1168
@@ -1499,12 +1537,16 @@
"PojoCache. For a full example, please refer to the distro examples "
"directory. There are numerous PojoCache examples that uses different options."
msgstr ""
+"So if you use JDK50, for example, with annotation and load-time "
+"instrumentation, then you won't need any pre-processing step to use "
+"PojoCache. For a full example, please refer to the distro examples "
+"directory. There are numerous PojoCache examples that uses different options."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1179
#, no-c-format
msgid "Can I run PojoCache in JBoss AS 3.2.x application server?"
-msgstr ""
+msgstr "Can I run PojoCache in JBoss AS 3.2.x application server?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1185
@@ -1514,12 +1556,15 @@
"JBossAop wiki for details). However, it will take some effort. Therefore, "
"the recommended JBoss version is 4.x to run PojoCache."
msgstr ""
+"Yes and no. Yes, since JBossAop can also be back-ported to 3.2.x (see "
+"JBossAop wiki for details). However, it will take some effort. Therefore, "
+"the recommended JBoss version is 4.x to run PojoCache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1195
#, no-c-format
msgid "Can PojoCache run as a MBean as well?"
-msgstr ""
+msgstr "Can PojoCache run as a MBean as well?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1199
@@ -1534,6 +1579,14 @@
" name=\"jboss.cache:service=PojoCache\"></"
"programlisting> in the xml configuration file."
msgstr ""
+"Yes. It is almost the same as TreeCache MBean. The only difference is the "
+"object name and the class name. E.g., instead of <programlisting><mbean "
+"code=\"org.jboss.cache.TreeCache\"\n"
+" name=\"jboss.cache:service=TreeCache\"></"
+"programlisting> you will have: <programlisting><mbean code=\"org.jboss."
+"cache.aop.PojoCache\"\n"
+" name=\"jboss.cache:service=PojoCache\"></"
+"programlisting> in the xml configuration file."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1212
@@ -1542,6 +1595,8 @@
"Can I pre-compile the aop classes such that I don't need to use the system "
"classloader and jboss-aop configuration xml?"
msgstr ""
+"Can I pre-compile the aop classes such that I don't need to use the system "
+"classloader and jboss-aop configuration xml?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1218
@@ -1554,6 +1609,12 @@
"any <literal>jboss-aop.xml</literal> that specifies the advisable POJO and "
"to specify the JBossAop system class loader."
msgstr ""
+"Yes. The latest versions of JBossCache have a pre-compiler option called "
+"<literal>aopc</literal> . You can use this option to pre-compile your "
+"\"aspectized\" POJO. Once the classes have been byte code generated, they "
+"can be treated as regular class files, i.e., you will not need to include "
+"any <literal>jboss-aop.xml</literal> that specifies the advisable POJO and "
+"to specify the JBossAop system class loader."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1230
@@ -1566,12 +1627,18 @@
"In addition, please also check out the <literal>examples</literal> directory "
"for concrete examples."
msgstr ""
+"For an example of how to use <literal>aopc</literal> , please see 1) "
+"<literal>tools</literal> directory for PojoCacheTasks14.xml and "
+"PojoCacheTasks50.xml. Both contain Ant tasks that you can import to your "
+"regular project for <literal>annoc</literal> and <literal>aopc</literal> . "
+"In addition, please also check out the <literal>examples</literal> directory "
+"for concrete examples."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1250
#, no-c-format
msgid "How do I use aopc on multiple module directories?"
-msgstr ""
+msgstr "How do I use aopc on multiple module directories?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1254
More information about the jboss-cvs-commits
mailing list