[jboss-cvs] JBossAS SVN: r76624 - projects/docs/enterprise/4.3/Cache/Cache_Tutorial/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Aug 4 19:07:21 EDT 2008
Author: ldelima at redhat.com
Date: 2008-08-04 19:07:21 -0400 (Mon, 04 Aug 2008)
New Revision: 76624
Modified:
projects/docs/enterprise/4.3/Cache/Cache_Tutorial/pt-BR/Cache_Tutorial.po
Log:
translation ongoing
Modified: projects/docs/enterprise/4.3/Cache/Cache_Tutorial/pt-BR/Cache_Tutorial.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Tutorial/pt-BR/Cache_Tutorial.po 2008-08-04 23:02:18 UTC (rev 76623)
+++ projects/docs/enterprise/4.3/Cache/Cache_Tutorial/pt-BR/Cache_Tutorial.po 2008-08-04 23:07:21 UTC (rev 76624)
@@ -8,7 +8,7 @@
"Project-Id-Version: Cache_Tutorial\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-07-24 03:55+0000\n"
-"PO-Revision-Date: 2008-08-04 12:46+1000\n"
+"PO-Revision-Date: 2008-08-05 09:06+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"
@@ -141,6 +141,11 @@
"jboss.org/products/jbosscache/docs\">PojoCache</ulink>. This file is read in "
"when the process is started."
msgstr ""
+"<literal>jboss-aop.xml</literal>. AOP pointcut and advice definition for the "
+"example POJO classes, Person and Address, respectively. For details of how "
+"to put your own class under AOP, please refer to the <ulink url=\"http://www."
+"jboss.org/products/jbosscache/docs\">PojoCache</ulink>. This file is read in "
+"when the process is started."
#. Tag: title
#: Cache_Tutorial.xml:71
@@ -529,6 +534,14 @@
"example, type addr.setCity(\"San Jose\"); in the interactive shell, you "
"should see in the GUI that the address got modified."
msgstr ""
+"Next step to see AOP in action, you can do plain get/set methods without "
+"ever worrying about put it in the cache. For example, you can do in the "
+"shell window joe.setAge(20); and see that GUI gets updated with the age "
+"field automatically (if not, click away and back will refresh the GUI "
+"content). Also to demonstrate the object graph replication, you can modify "
+"Joe's address and see the cache will update it automatically. For "
+"example, type addr.setCity(\"San Jose\"); in the interactive shell, you "
+"should see in the GUI that the address got modified."
#. Tag: para
#: Cache_Tutorial.xml:170
@@ -538,6 +551,9 @@
"classes (i.e., List, Map, and Set). For example, type the following in the "
"shell command line:"
msgstr ""
+"Finally, PojoCache also supports get/set with parameter type of Collection "
+"classes (i.e., List, Map, and Set). For example, type the following in the "
+"shell command line:"
#. Tag: programlisting
#: Cache_Tutorial.xml:173
@@ -557,7 +573,7 @@
#: Cache_Tutorial.xml:176
#, no-c-format
msgid "PojoCache with Transaction"
-msgstr ""
+msgstr "PojoCache with Transaction"
#. Tag: para
#: Cache_Tutorial.xml:177
@@ -567,6 +583,9 @@
"last section except you load the bsh of aopWithTx.bsh instead of aop.bsh. "
"The additional snippets are:"
msgstr ""
+"To see TreeCache transaction at work, you start with the same setup with "
+"last section except you load the bsh of aopWithTx.bsh instead of aop.bsh. "
+"The additional snippets are:"
#. Tag: programlisting
#: Cache_Tutorial.xml:180
@@ -654,7 +673,7 @@
#: Cache_Tutorial.xml:181
#, no-c-format
msgid "In this example, a default dummy transaction manager is used."
-msgstr ""
+msgstr "In this example, a default dummy transaction manager is used."
#. Tag: programlisting
#: Cache_Tutorial.xml:184
@@ -672,7 +691,7 @@
#: Cache_Tutorial.xml:187
#, no-c-format
msgid "CacheLoader examples"
-msgstr ""
+msgstr "CacheLoader examples"
#. Tag: para
#: Cache_Tutorial.xml:188
@@ -682,12 +701,15 @@
"We assume the ZIP file has been unzipped into a directory <literal>jboss-"
"cache</literal> ."
msgstr ""
+"All the examples below are based on the JBossCache standalone distribution. "
+"We assume the ZIP file has been unzipped into a directory <literal>jboss-"
+"cache</literal> ."
#. Tag: title
#: Cache_Tutorial.xml:192
#, no-c-format
msgid "Local cache with CacheLoader"
-msgstr ""
+msgstr "Local cache with CacheLoader"
#. Tag: para
#: Cache_Tutorial.xml:193
@@ -697,6 +719,9 @@
"into the cache, and see that the POJO is transparently saved using the "
"CacheLoader."
msgstr ""
+"This demo shows a local PojoCache with a CacheLoader. We will insert a POJO "
+"into the cache, and see that the POJO is transparently saved using the "
+"CacheLoader."
#. Tag: para
#: Cache_Tutorial.xml:196
@@ -706,6 +731,9 @@
"oodb-service.xml</literal> : change <literal>CacheLoaderConfig</literal> to "
"point to a valid directory (create it if it doesn't yet exist):"
msgstr ""
+"To run this, you have to modify <literal>jboss-cache/output/etc/META-INF/"
+"oodb-service.xml</literal> : change <literal>CacheLoaderConfig</literal> to "
+"point to a valid directory (create it if it doesn't yet exist):"
#. Tag: programlisting
#: Cache_Tutorial.xml:199
@@ -728,6 +756,10 @@
"retrieve POJO from the cache. So remember to comment them out if you decide "
"to create the Person instance yourself."
msgstr ""
+"Then start the beanshell and source <literal>oodb.bsh</literal> into it. "
+"Note that <literal>oodb.bsh</literal> already contains code to create and "
+"retrieve POJO from the cache. So remember to comment them out if you decide "
+"to create the Person instance yourself."
#. Tag: programlisting
#: Cache_Tutorial.xml:203
@@ -759,7 +791,7 @@
#: Cache_Tutorial.xml:204
#, no-c-format
msgid "Next, create an instance of Person, and set its address and other fields:"
-msgstr ""
+msgstr "Next, create an instance of Person, and set its address and other fields:"
#. Tag: programlisting
#: Cache_Tutorial.xml:207
@@ -820,6 +852,10 @@
"because the instance of <literal>Person</literal> we created was given the "
"name \"p\", we can retrieve it again:"
msgstr ""
+"The <literal>Person</literal> object with all of its fields and subobjects "
+"is now saved. Let's kill beanshell and restart it. At this point, "
+"because the instance of <literal>Person</literal> we created was given the "
+"name \"p\", we can retrieve it again:"
#. Tag: programlisting
#: Cache_Tutorial.xml:211
@@ -876,12 +912,16 @@
"that the values of \"p\" are loaded from the datastore where they were "
"previously saved."
msgstr ""
+"The interesting thing here is that the cache was initially empty (\"/\"). "
+"Only when we loaded \"p\", did it get populated (lazy loading). You can see "
+"that the values of \"p\" are loaded from the datastore where they were "
+"previously saved."
#. Tag: title
#: Cache_Tutorial.xml:221
#, no-c-format
msgid "Replicated cache with shared datastore"
-msgstr ""
+msgstr "Replicated cache with shared datastore"
#. Tag: para
#: Cache_Tutorial.xml:222
@@ -894,6 +934,12 @@
"<literal>jboss-cache/output/etc/META-INF/replAsyncSharedCacheLoader-service."
"xml</literal> :"
msgstr ""
+"The scenario that we'll run in this example is described in the "
+"documentation for JBossCache. It consists of 2 separate nodes that replicate "
+"their contents between each other. In addition, they both point to the "
+"<emphasis>same</emphasis> datastore. The configuration is in file "
+"<literal>jboss-cache/output/etc/META-INF/replAsyncSharedCacheLoader-service."
+"xml</literal> :"
#. Tag: programlisting
#: Cache_Tutorial.xml:225
@@ -948,6 +994,16 @@
"the same file system). Please make sure that <literal>c:\\tmp</literal> "
"exists, or point the config string to a different existing directory."
msgstr ""
+"The <literal>FetchStateOnStartup</literal> attribute set to <literal>false</"
+"literal> means that a newly started cache will <emphasis>not</emphasis> "
+"attempt to fetch the state (neither transient nor persistent). Therefore, "
+"attributes <literal>CacheLoaderFetchTransientState</literal> and "
+"<literal>CacheLoaderFetchPersistentState</literal> will be ignored. "
+"<literal>CacheLoaderShared</literal> set to <literal>true</literal> means "
+"that both nodes will share the same datastore, which resides in <literal>c:"
+"\\tmp</literal> in the example (this assumes that both nodes have access to "
+"the same file system). Please make sure that <literal>c:\\tmp</literal> "
+"exists, or point the config string to a different existing directory."
#. Tag: para
#: Cache_Tutorial.xml:229
@@ -962,6 +1018,14 @@
"lot of data in the cache, because <emphasis>all</emphasis> of your data will "
"be loaded into the cache."
msgstr ""
+"This configuration would essentially provide for two <literal>cold</literal> "
+"nodes, in the sense that all contents of a new cache is in the datastore, "
+"and is lazy-loaded via the CacheLoader when accessed. However, this is not "
+"true, as <literal>CacheLoaderPreload</literal> points to \"/\", which is the "
+"root of the entire tree. Therefore, all of the contents of the cache are "
+"recursively pre-loaded. This is probably a bad configuration when you have a "
+"lot of data in the cache, because <emphasis>all</emphasis> of your data will "
+"be loaded into the cache."
#. Tag: para
#: Cache_Tutorial.xml:232
@@ -971,6 +1035,9 @@
"one who writes it to the store using the CacheLoader. This prevents both "
"nodes from writing the same data twice."
msgstr ""
+"Note that with a shared datastore, the node that makes a modification is the "
+"one who writes it to the store using the CacheLoader. This prevents both "
+"nodes from writing the same data twice."
#. Tag: para
#: Cache_Tutorial.xml:235
@@ -979,6 +1046,8 @@
"We can now start 2 instances by opening two shells and executing the "
"following ANT target:"
msgstr ""
+"We can now start 2 instances by opening two shells and executing the "
+"following ANT target:"
#. Tag: programlisting
#: Cache_Tutorial.xml:238
@@ -1057,6 +1126,12 @@
"state is the same as before shutdown as it was persisted to the shared store "
"via the CacheLoader."
msgstr ""
+"2 GUI instances will appear, showing the tree structure of the cache "
+"graphically. Nodes can be added, modified or removed by right-clicking or "
+"using the menu. Any modification is replicated between the two nodes. If "
+"both nodes are killed, and subsequently one or both nodes are restarted, the "
+"state is the same as before shutdown as it was persisted to the shared store "
+"via the CacheLoader."
#. Tag: para
#: Cache_Tutorial.xml:242
@@ -1065,12 +1140,14 @@
"Note that the example above shows the 2 nodes running on the same machine "
"(192.168.1.184) on ports 1355 and 1357."
msgstr ""
+"Note that the example above shows the 2 nodes running on the same machine "
+"(192.168.1.184) on ports 1355 and 1357."
#. Tag: title
#: Cache_Tutorial.xml:247
#, no-c-format
msgid "Replicated cache with unshared (local) datastore"
-msgstr ""
+msgstr "Replicated cache with unshared (local) datastore"
#. Tag: para
#: Cache_Tutorial.xml:248
@@ -1081,6 +1158,10 @@
"configuration is in file <literal>jboss-cache/output/etc/META-INF/node{1,2}."
"xml</literal> . We'll look at node1.xml:"
msgstr ""
+"In this example, we'll run 2 nodes again, but this time, instead of "
+"sharing the same datastore, each node has its own datastore. The "
+"configuration is in file <literal>jboss-cache/output/etc/META-INF/node{1,2}."
+"xml</literal> . We'll look at node1.xml:"
#. Tag: programlisting
#: Cache_Tutorial.xml:251
@@ -1129,6 +1210,11 @@
"and each machine would run one JBossCache process. Note that the 2 "
"directories have to exis"
msgstr ""
+"Again, we use the Sleepycat CacheLoader implementation in "
+"<literal>CacheLoaderClass</literal> . The <literal>CacheLoaderConfig</"
+"literal> points to <literal>c:\\tmp\\node1</literal> . This is the directory "
+"in which the Sleepycat DB for node1 will reside. File node2.xml has a "
+"configuration that points to <literal>c"
#. Tag: para
#: Cache_Tutorial.xml:255
@@ -1137,6 +1223,8 @@
"To create an unshared datastore, we set the <literal>CacheLoaderShared</"
"literal> attribute to <literal>false</literal> ."
msgstr ""
+"To create an unshared datastore, we set the <literal>CacheLoaderShared</"
+"literal> attribute to <literal>false</literal> ."
#. Tag: para
#: Cache_Tutorial.xml:258
@@ -1145,6 +1233,8 @@
"The example can be run by again opening 2 shells, and running 2 ANT targets "
"(here we show the target for node1):"
msgstr ""
+"The example can be run by again opening 2 shells, and running 2 ANT targets "
+"(here we show the target for node1):"
#. Tag: programlisting
#: Cache_Tutorial.xml:261
@@ -1187,12 +1277,18 @@
"restart a node, or even both nodes, and the data will still be available due "
"to the persistent backend store(s)."
msgstr ""
+"The <literal>run.demo.unshared.node2</literal> target runs node2, which will "
+"have its own store located at <literal>c:\\tmp\\node2</literal> (shown "
+"above). Whenever a change is made on either of the 2 nodes, it is replicated "
+"to the other node, and persisted in both local datastores. You can kill and "
+"restart a node, or even both nodes, and the data will still be available due "
+"to the persistent backend store(s)."
#. Tag: title
#: Cache_Tutorial.xml:267
#, no-c-format
msgid "Troubleshooting"
-msgstr ""
+msgstr "Troubleshooting"
#. Tag: para
#: Cache_Tutorial.xml:268
@@ -1201,6 +1297,8 @@
"Here are some tips for troubleshooting, if you encounter problems during "
"this demo."
msgstr ""
+"Here are some tips for troubleshooting, if you encounter problems during "
+"this demo."
#. Tag: para
#: Cache_Tutorial.xml:273
@@ -1211,6 +1309,10 @@
"view. See if it is updated when you run the BSH commands. It should show a "
"view with at least two members. For example, on my window, I see"
msgstr ""
+"Most of the time, the problem will come from cache replication layer, i.e., "
+"JGroups package. On the output window, you can see the JGroups membership "
+"view. See if it is updated when you run the BSH commands. It should show a "
+"view with at least two members. For example, on my window, I see"
#. Tag: programlisting
#: Cache_Tutorial.xml:276
@@ -1229,4 +1331,10 @@
"have problem with this, please consult the <ulink url=\"http://www.jgroups."
"org/javagroupsnew/docs/index.html\">JGroups website </ulink>"
msgstr ""
+"with 2 members: 4381 and 4383. On the other hand, if you don't close the "
+"previous running cache instance, the membership view will also include the "
+"previous existing ones. This can corrupt the states. So you will have to "
+"make sure there is no running TreeCache processes before each demo. If you "
+"have problem with this, please consult the <ulink url=\"http://www.jgroups."
+"org/javagroupsnew/docs/index.html\">JGroups website </ulink>"
More information about the jboss-cvs-commits
mailing list