[jboss-cvs] JBossAS SVN: r77342 - projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Aug 22 03:29:40 EDT 2008
Author: ldelima at redhat.com
Date: 2008-08-22 03:29:40 -0400 (Fri, 22 Aug 2008)
New Revision: 77342
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-22 07:22:59 UTC (rev 77341)
+++ projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po 2008-08-22 07:29:40 UTC (rev 77342)
@@ -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-21 14:41+1000\n"
+"PO-Revision-Date: 2008-08-22 17:26+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"
@@ -1098,7 +1098,7 @@
"approach is quite severe so in general another local in-vm version will need "
"to be used as a \"near-line\" cache. Note also that each time the serialized "
"bytes are deserialized, a new instance of the object is created."
-msgstr "Para solucionar o segundo problema, a única solução (que nós sabemos) "
+msgstr "Para solucionar o segundo problema, a única solução (que nós sabemos) é \"serializar\" o cache de código byte e apenas desserializá-lo durante cada obtenção de objeto (e isto será caro!). Isto é, durante uma operação de adição, a instância de objeto será serializada e, portanto, pode ser desserializada com segurança pelo carregador de classe \"estrangeiro\". No entanto, a penalidade de desempenho desta abordagem é bastante severa, de forma que em geral outro local em versão vm será necessário ser usado como um cache \"perto da fila\". Perceba que a cada instante em que os bytes serializados estiverem desserializados, uma nova instância do objeto é criada."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:952
@@ -1305,7 +1305,7 @@
"that it can operate as long as the cache is up and running."
msgstr ""
"Para implementação deste recurso, por favor siga as instruções indicadas no exemplo encontrado na seção TreeCacheMarshaller do guia do usuário. É importante perceber que ao invés de um <literal>ServletContextListener</literal>, você poderá adicionar um código ao <literal>MBean</literal>, que contém os métodos de ciclo de vida, como por exemplo: <literal>start()</literal> e <literal>stop()</"
-"literal>. A chave principal para este MBean dependerá no cache de destinação, de forma que ele pode operar contanto que o cache esteja funcionando e rodando. "
+"literal>. A tecla para este MBean dependerá no cache de destinação, de forma que ele pode operar contanto que o cache esteja funcionando e rodando. "
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:1049
@@ -1397,18 +1397,7 @@
"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."
-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."
+msgstr "Pense no PojoCache como um TreeCache em esteróides. :-) Falando sério agora, ambos são armazenamentos de cache: um é um cache genérico e o outro é um POJO Cache. No entanto, enquanto o TreeCache apenas fornece o armazenamento de referência do objeto puro (por exemplo; <literal>put(FQN fqn, Object key, Object value) </literal>) o PojoCache vai além disso e executa o mapeamento do objeto de replicação do nível de campo fine-grained, além do gerenciamento de relacionamento para o usuário nos bastidores. Como resultado, caso você tenha sistemas de objeto complexo, pelo qual você gostaria realizar o cache, você poderá ter o PojoCache gerenciando isto para você. Você simplesmente tratará de seus sistemas de objeto uma vez que eles residem na memória, por exemplo: use os seus métodos POJO regulares sem se preocupar com o gerenciamento do cache. Além disso, isto é verdadeiro para o modo de replicação também. "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1140
@@ -1489,14 +1478,13 @@
" 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 "
+"Sim. Isto é muito parecido com o TreeCache MBean. A única diferença é o nome do objeto e o nome da classe. Por exemplo: ao invés de <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."
+"programlisting> no arquivo de configuração xml."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1212
@@ -1504,9 +1492,7 @@
msgid ""
"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?"
+msgstr "Posso pré-compilar as classes aop tais como aquelas que não são necessárias usar o carregador de classe do sistema e o xml de configuração jboss-aop?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1218
@@ -1518,13 +1504,7 @@
"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."
-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."
+msgstr "Sim. As últimas versões do JBossCache possuem uma opção pré-compilar chamada <literal>aopc</literal>. Você pode usar esta opção para pré-compilar seu POJO \"posicionado\". Uma vez as classes tenham sido gerado o código byte, elas poderão ser tratadas como arquivos de classes regulares, por exemplo; você não precisará incluir qualquer <literal>jboss-aop.xml</literal> que especifica o POJO oportuno e para especificação do carregador da classe de sistema JBossAop."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1230
@@ -1537,18 +1517,14 @@
"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."
+"Para um exemplo em como se utilizar o <literal>aopc</literal>, por favor consulte 1) diretório de <literal>tools</literal> para o PojoCacheTasks14.xml e "
+"PojoCacheTasks50.xml. Ambos contém as tarefas Ant que você pode importar a seu projeto regular para <literal>annoc</literal> e <literal>aopc</literal>. Adicionado a isto, por favor cvheck-out o diretório de <literal>examples</literal> para exemplos concretos."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1250
#, no-c-format
msgid "How do I use aopc on multiple module directories?"
-msgstr "How do I use aopc on multiple module directories?"
+msgstr "Como eu uso o aopc em diretórios de módulo múltiplos?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1254
@@ -1556,15 +1532,13 @@
msgid ""
"In aopc, you specify the src path for a specific directory. To pre-compile "
"multiple ones, you will need to invoke aopc multiple times."
-msgstr ""
-"In aopc, you specify the src path for a specific directory. To pre-compile "
-"multiple ones, you will need to invoke aopc multiple times."
+msgstr "No aopc, você especifica o src path para um diretório específico. Para pré-compilação dos dos diretórios múltiplos, você precisará invocar os períodos múltiplos aopc. "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1263
#, no-c-format
msgid "What's in the <literal>jboss-aop.xml</literal> configuration?"
-msgstr "What's in the <literal>jboss-aop.xml</literal> configuration?"
+msgstr "O que há na configuração <literal>jboss-aop.xml</literal>?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1270
@@ -1579,14 +1553,9 @@
"CacheInterceptor</literal> to this POJO to perform object mapping and "
"relationship management."
msgstr ""
-"<literal>jboss-aop.xml</literal> is needed for POJO instrumentation. In "
-"<literal>jboss-aop.xml</literal> , you can declare your POJO (e.g., "
-"<literal>Person</literal> ) to be \"prepared\", a JBossAop term to denote "
-"that the object will be \"aspectized\" by the system. After this "
-"declaration, JBossAop will invoke any interceptor that associates with this "
-"POJO. PojoCache will dynamically add an <literal>org.jboss.cache.aop."
-"CacheInterceptor</literal> to this POJO to perform object mapping and "
-"relationship management."
+"O <literal>jboss-aop.xml</literal> é necessário para a instrumentação do POJO. No <literal>jboss-aop.xml</literal>, você pode declarar seu POJO (por exemplo: "
+"<literal>Person</literal>) a ser \"preparado\" e o termo JBossAop a estipular que o objeto será \"posicionado\" pelo sistema. Após esta declaração, O JBossAop irá invocar qualquer interceptor que é associado com este POJO. O PojoCache adicionará dinamicamente um <literal>org.jboss.cache.aop."
+"CacheInterceptor</literal> a este POJO para executar o mapeamento do objeto e gerenciamento de relacionamento."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1288
@@ -1594,15 +1563,13 @@
msgid ""
"Note that to add your POJO, you should declare all the fields to be "
"\"prepared\" as in the example."
-msgstr ""
-"Note that to add your POJO, you should declare all the fields to be "
-"\"prepared\" as in the example."
+msgstr "Perceba que para adicionar seu POJO, você deverá declarar todos os campos a serem \"preparados\" como no exemplo."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1296
#, no-c-format
msgid "Can I use annotation instead of the xml declaration?"
-msgstr "Can I use annotation instead of the xml declaration?"
+msgstr "Posso usar a anotação ao invés da declaração xml?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1300
@@ -1610,15 +1577,13 @@
msgid ""
"Yes, starting with JBossCache 1.3, you can use annotation to instrument your "
"POJO for both JDK1.4 and 1.5. Check the documentation for details."
-msgstr ""
-"Yes, starting with JBossCache 1.3, you can use annotation to instrument your "
-"POJO for both JDK1.4 and 1.5. Check the documentation for details."
+msgstr "Sim, inicializando pelo JBossCache 1.3, vocêr pode usar a anotação para instrumentar ser POJO para ambos JDK1.4 e 1.5. Cheque a documentação para maiores informações a respeito."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1308
#, no-c-format
msgid "What are the pro and con of xml vs. annotation?"
-msgstr "What are the pro and con of xml vs. annotation?"
+msgstr "Quais são os prós e contras do xml vs. a anotação?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1312
@@ -1629,12 +1594,7 @@
"annotation is well suited for PojoCache. This is because once you specify "
"the annotation, you'd probably change it rarely since there is no parameters "
"to tune, for example."
-msgstr ""
-"It really depends on your organization environment, I'd say, since this can "
-"be turned into a hot debate. Having said that, I feel strongly that POJO "
-"annotation is well suited for PojoCache. This is because once you specify "
-"the annotation, you'd probably change it rarely since there is no parameters "
-"to tune, for example."
+msgstr "Isto na realidade depende no seu ambiente de organização. Podemos dizer que desde que isto possa tornar-se num debate "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1324
@@ -1644,9 +1604,8 @@
"and <literal>@org.jboss.cache.aop.annotation.Serializable</literal> field "
"level annotations?"
msgstr ""
-"What are the <literal>@org.jboss.cache.aop.annotation.Transient</literal> "
-"and <literal>@org.jboss.cache.aop.annotation.Serializable</literal> field "
-"level annotations?"
+"Quais são as anotações de nível de campo <literal>@org.jboss.cache.aop.annotation.Transient</literal> "
+"e <literal>@org.jboss.cache.aop.annotation.Serializable</literal>?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1333
@@ -1656,11 +1615,7 @@
"first one, <literal>@Transient</literal> , when applied has the same effect "
"as declaring a field <literal>transient</literal> . PojoCache won't put this "
"field under management."
-msgstr ""
-"Starting in 1.4, we also offer two additional field-level annotations. The "
-"first one, <literal>@Transient</literal> , when applied has the same effect "
-"as declaring a field <literal>transient</literal> . PojoCache won't put this "
-"field under management."
+msgstr "Inicializando em 1.4., nós oferecemos também duas anotações de nível de campo adicionais. a primeira, <literal>@Transient</literal>, quando aplicada possui o mesmo efeito como se estivesse declarando um campo <literal>transient</literal>. O PojoCache não colocaria este campo sob gerenciamento."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1341
@@ -1669,16 +1624,13 @@
"The second one, <literal>@Serializable</literal> when applied, will cause "
"PojoCache to treat the field as a Serializable object even when it is "
"<literal>@PojoCacheable</literal> ."
-msgstr ""
-"The second one, <literal>@Serializable</literal> when applied, will cause "
-"PojoCache to treat the field as a Serializable object even when it is "
-"<literal>@PojoCacheable</literal> ."
+msgstr "A segunda, <literal>@Serializable</literal>, quando aplicada causará o PojoCache "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1353
#, no-c-format
msgid "What about compile-time vs. load-time instrumentation then?"
-msgstr "What about compile-time vs. load-time instrumentation then?"
+msgstr "E a respeito do compilador de período vs. a instrumentação de período de carregamento então?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1357
@@ -1688,11 +1640,7 @@
"via aopc. I prefer this approach because it is easier to debug (at least at "
"the development stage). In addition, once I generate the new class, there is "
"no more steps needed."
-msgstr ""
-"Again it depends. But my preference is to do compile-time instrumentation "
-"via aopc. I prefer this approach because it is easier to debug (at least at "
-"the development stage). In addition, once I generate the new class, there is "
-"no more steps needed."
+msgstr "Mais uma vez, isto depende. Porém, minha preferência é realizar a instrumentação de período compilado através do aopc. Eu prefiro esta abordagem, pois através dela é mais fácil de se realizar o debug (pelo menos no estágio de desenvolvimento). Adicionado a isto, uma vez que eu gere a nova classe, não haverá mais nenhum passo necessário."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1368
@@ -1700,9 +1648,7 @@
msgid ""
"Is it possible to store the same object multiple times but with different "
"Fqn paths? Like /foo/byName and /foo/byId ?"
-msgstr ""
-"Is it possible to store the same object multiple times but with different "
-"Fqn paths? Like /foo/byName and /foo/byId ?"
+msgstr "É possível armazenar o mesmo objeto múltiplas vezes, mas em diferentes Fqn paths? Assim como no /foo/byName e /foo/byId?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1374
@@ -1711,10 +1657,7 @@
"Yes, you can use PojoCache to do that. It supports the notion of object "
"reference. PojoCache manages the unique object through association of the "
"dynamic cache interceptor."
-msgstr ""
-"Yes, you can use PojoCache to do that. It supports the notion of object "
-"reference. PojoCache manages the unique object through association of the "
-"dynamic cache interceptor."
+msgstr "Sim, você pode usar o PojoCache para realizar isto. Ele suporta a noção da referência do objeto. O PojoCache gerencia o objeto único através da associação do interceptor do cache dinâmico."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1383
@@ -1723,8 +1666,8 @@
"Do I need to declare all my objects \"prepared\" in <literal>jboss-aop.xml</"
"literal> ?"
msgstr ""
-"Do I need to declare all my objects \"prepared\" in <literal>jboss-aop.xml</"
-"literal> ?"
+"Eu preciso declarar todos os meus objetos \"preparados\" no <literal>jboss-aop.xml</"
+"literal>?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1390
@@ -1734,17 +1677,13 @@
"manage for you, you can leave it out of the declaration. The cache will "
"treat this object as a \"primitive\" type. However, the object will need to "
"implement <literal>Serializable</literal> interface for replication."
-msgstr ""
-"Not necessarily. If there is an object that you don't need the cache to "
-"manage for you, you can leave it out of the declaration. The cache will "
-"treat this object as a \"primitive\" type. However, the object will need to "
-"implement <literal>Serializable</literal> interface for replication."
+msgstr "Não necessariamente. Caso exista um objeto que você não precise do cache para gerenciá-lo para você, você poderá deixá-lo fora da declaração. O cache tratará deste objeto como um tipo \"primitivo\". No entanto, o objeto precisará implementar a interface <literal>Serializable</literal> para a replicação."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1402
#, no-c-format
msgid "Can the cache aop intercept update via reflection?"
-msgstr "Can the cache aop intercept update via reflection?"
+msgstr "O cache aop pode interceptar a atualização através da reflexão?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1406
@@ -1753,10 +1692,7 @@
"No. The update via reflection will not be intercepted in JBossAop and "
"therefore PojoCache will not be able to perform the necessary "
"synchronization."
-msgstr ""
-"No. The update via reflection will not be intercepted in JBossAop and "
-"therefore PojoCache will not be able to perform the necessary "
-"synchronization."
+msgstr "Não. A atualização a partir da reflexão não será interceptada no JBossAop e, portanto, o PojoCache não estará apto a executar a sincronização necessária."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1415
@@ -1764,9 +1700,7 @@
msgid ""
"When I declare my POJO to be \"aspectized\", what happens to the fields with "
"transient, static, and final modifiers?"
-msgstr ""
-"When I declare my POJO to be \"aspectized\", what happens to the fields with "
-"transient, static, and final modifiers?"
+msgstr "Quando eu declarar meu POJO a ser \"posicionado\", o que acontecerá aos campos transitórios, estáticos e modificadores finais?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1421
@@ -1774,9 +1708,7 @@
msgid ""
"PojoCache currently will ignore the fields with these modifiers. That is, it "
"won't put these fields into the cache (and thus no replication either)."
-msgstr ""
-"PojoCache currently will ignore the fields with these modifiers. That is, it "
-"won't put these fields into the cache (and thus no replication either)."
+msgstr "O PojoCache irá ignorar os campos com estes modificadores no momento. Isto é, ele não colocará estes campos no cache (e, portanto, nem a replicação)."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1430
@@ -1785,8 +1717,8 @@
"What are those keys such as <literal>JBoss:internal:class</literal> and "
"<literal>AOPInstance</literal> ?"
msgstr ""
-"What are those keys such as <literal>JBoss:internal:class</literal> and "
-"<literal>AOPInstance</literal> ?"
+"Quais são estes teclas, tais como <literal>JBoss:internal:class</literal> e "
+"<literal>AOPInstance</literal>?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1439
@@ -1794,15 +1726,13 @@
msgid ""
"They are for internal use only. Users should ignore these keys and values in "
"the node hashmap."
-msgstr ""
-"They are for internal use only. Users should ignore these keys and values in "
-"the node hashmap."
+msgstr "Eles são para uso interno apenas. Os usuários deverão ignorar estes teclas e valores no nó hashmap."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1447
#, no-c-format
msgid "What about Collection classes? Do I need to declare them \"prepared\"?"
-msgstr "What about Collection classes? Do I need to declare them \"prepared\"?"
+msgstr "E a respeito das classes de Coleção? Eu precisarei declará-las \"preparadas\"? "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1453
@@ -1815,14 +1745,7 @@
"delegate the operations to a cache interceptor that implements the actual "
"Collection classes APIs. That is, the system classes won't be invoked when "
"used in PojoCache."
-msgstr ""
-"No. Since the Collection classes such as <literal>ArrayList</literal> are "
-"java util classes, aop by default won't instrument these classes. Instead, "
-"PojoCache will generate a dynamic class proxy for the Collection classes "
-"(upon the <literal>putObject</literal> call is invoked). The proxy will "
-"delegate the operations to a cache interceptor that implements the actual "
-"Collection classes APIs. That is, the system classes won't be invoked when "
-"used in PojoCache."
+msgstr "Não. Uma vez que as classes de Coleção , tais como <literal>ArrayList</literal>, são classes java util, o aop não instrumentará estas classes. Ao invés disto, o PojoCache gerará um proxy de classe dinâmica para as classes de Coleção (até que a chamada <literal>putObject</literal> seja invocada). O proxy delegará as operações ao interceptor do cache que implementa os APIs de classe de Coleção atual. Isto é, as classes do sistema não serão invocadas quando utilizadas no PojoCache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1465
@@ -1833,12 +1756,7 @@
"implications in performance for certain APIs. For example, both "
"<literal>ArrayList</literal> and <literal>LinkedList</literal> will have the "
"same implementation. Plan is currently underway to optimize these APIs."
-msgstr ""
-"Internally, the cache interceptor implements the APIs by direct interaction "
-"with respect to the underlying cache store. Note that this can have "
-"implications in performance for certain APIs. For example, both "
-"<literal>ArrayList</literal> and <literal>LinkedList</literal> will have the "
-"same implementation. Plan is currently underway to optimize these APIs."
+msgstr "Internamente, o interceptor do cache implementa os APIs pela interação direta, respeitando o armazenamento do cache base. Perceba que isto poderá ter implicações no desempenho para certos APIs. Por exemplo, ambos <literal>ArrayList</literal> e <literal>LinkedList</literal> terão a mesma implementação. O Plan está no momento a caminho para a otimização destes APIs."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1480
@@ -1847,8 +1765,8 @@
"How do I use <literal>List</literal> , <literal>Set</literal> , and "
"<literal>Map</literal> dynamic proxy?"
msgstr ""
-"How do I use <literal>List</literal> , <literal>Set</literal> , and "
-"<literal>Map</literal> dynamic proxy?"
+"Como eu usarei o proxy de dinâmica <literal>List</literal> , <literal>Set</literal> e "
+"<literal>Map</literal>?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1492
@@ -1859,10 +1777,8 @@
"them \"aspectized\". It is done via a dynamic proxy. Here is a code snippet "
"to use an <literal>ArrayList</literal> proxy class."
msgstr ""
-"PojoCache supports classes extending from <literal>List</literal> , "
-"<literal>Set</literal> , and <literal>Map</literal> without users to declare "
-"them \"aspectized\". It is done via a dynamic proxy. Here is a code snippet "
-"to use an <literal>ArrayList</literal> proxy class."
+"O PojoCache suporta as classes estendidas a partir da <literal>List</literal> , "
+"<literal>Set</literal> e <literal>Map</literal>, sem que os usuários tenham que declará-las. Isto é feito através do proxy dinâmico. Segue abaixo um trecho do código para uso em uma classe de proxy <literal>ArrayList</literal>."
#. Tag: programlisting
#: Cache_Frequently_Asked_Questions.xml:1504
@@ -1906,9 +1822,7 @@
msgid ""
"What is the proper way of assigning two different keys with Collection class "
"object?"
-msgstr ""
-"What is the proper way of assigning two different keys with Collection class "
-"object?"
+msgstr "Qual é a maneira apropriada de determinar duas teclas com o objeto de classe de Coleção?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1516
@@ -1917,10 +1831,7 @@
"Let's say you want to assign a <literal>List</literal> object under two "
"different names, you will need to use the class proxy to insert the second "
"time to ensure both are managed by the cache. Here is the code snippet."
-msgstr ""
-"Let's say you want to assign a <literal>List</literal> object under two "
-"different names, you will need to use the class proxy to insert the second "
-"time to ensure both are managed by the cache. Here is the code snippet."
+msgstr "Vamos dizer que você deseja determinar o objeto de <literal>List</literal>, sob dois diferentes nomes. Você precisará usar o proxy de classe para inserir pela segunda vez e garantir que ambos estão sendo gerenciados pelo cache. A seguir, o trecho do código:"
#. Tag: programlisting
#: Cache_Frequently_Asked_Questions.xml:1524
@@ -1964,11 +1875,7 @@
"classes once they are managed by the cache. But what happens to Pojos that "
"share the Collection objects, e.g., a <literal>List</literal> instance that "
"is shared by 2 Pojos?"
-msgstr ""
-"OK, so I know I am supposed to use proxy when manipulating the Collection "
-"classes once they are managed by the cache. But what happens to Pojos that "
-"share the Collection objects, e.g., a <literal>List</literal> instance that "
-"is shared by 2 Pojos?"
+msgstr "OK, sabemos que deveríamos usar o proxy quando manipulando as classes de Coleção, uma vez que elas são gerenciadas pelo cache. No entanto, o que acontence com os Pojos que compartilham os objetos de Coleção? Por exemplo: uma instância de <literal>List</literal> que está compartilhada por \" Pojos?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1539
@@ -1978,11 +1885,7 @@
"automatically. That is, when you ask the Cache to manage it, the Cache will "
"dynamically swap out the regular Collection references with the dynamic "
"proxy ones. As a result, it is transparent to the users."
-msgstr ""
-"Pojos that share Collection instance references will be handled by the cache "
-"automatically. That is, when you ask the Cache to manage it, the Cache will "
-"dynamically swap out the regular Collection references with the dynamic "
-"proxy ones. As a result, it is transparent to the users."
+msgstr "Os Pojos que compartilham as referências de instância de Coleção serão manuseadas pelo cache automaticamente. Isto é, quando você chamar o Cache para manusear isto, o Cache irá limpar as referências de Coleção regular com os proxy dinâmicos. Como resultado, isto fica bem claro aos usuários."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1550
@@ -1990,9 +1893,7 @@
msgid ""
"What happens when my \"aspectized\" POJO has field members that are of "
"Collection class ?"
-msgstr ""
-"What happens when my \"aspectized\" POJO has field members that are of "
-"Collection class ?"
+msgstr "O que acontece quando meu POJO \"aspectized\" possui membros de campos que são das classes de Coleção?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1556
@@ -2004,11 +1905,8 @@
"Map), PojoCache will first map the collection into cache. Then, it will swap "
"out dynamically the field reference with an corresponding proxy reference."
msgstr ""
-"When a user puts a POJO into the cache through the call <literal>putObject</"
-"literal> , it will recursively map the field members into the cache store as "
-"well. When the field member is of a Collection class (e.g., List, Set, or "
-"Map), PojoCache will first map the collection into cache. Then, it will swap "
-"out dynamically the field reference with an corresponding proxy reference."
+"Quando um usuário adiciona um Pojo ao um cache através da chamada <literal>putObject</"
+"literal>, ele irá mapear de maneira repetitiva os membros dos campos dentro do armazenamento do cache também. Quando o membro do campo for de uma classe de Coleção (por exemplo: Listar, Configurar ou Mapear, o PojoCache irá primeiramente mapear a coleção ao cache. E então, ele irá limpar dinamicamente a referência do campo com uma referência de proxy correspondente."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1565
@@ -2016,15 +1914,13 @@
msgid ""
"This is necessary so that an internal update on the field member will be "
"intercepted by the cache."
-msgstr ""
-"This is necessary so that an internal update on the field member will be "
-"intercepted by the cache."
+msgstr "Isto é necessário para que uma atualização interna no campo do usuário seja interceptada pelo cahe."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1574
#, no-c-format
msgid "What are the limitation of Collection classes in PojoCache?"
-msgstr "What are the limitation of Collection classes in PojoCache?"
+msgstr "Qual é a limitação das classes de Coleção no PojoCache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1578
@@ -2033,10 +1929,7 @@
"Use of Collection class in PojoCache helps you to track fine-grained changes "
"in your collection fields automatically. However, current implementation has "
"the follow limitation that we plan to address soon."
-msgstr ""
-"Use of Collection class in PojoCache helps you to track fine-grained changes "
-"in your collection fields automatically. However, current implementation has "
-"the follow limitation that we plan to address soon."
+msgstr "O uso da classe de Coleção no PojoCache o auxília a encontrar mudanças finer-grained em seus campos de coleção, automaticamente. No entanto, a implementação atual possui a seguinte limitação, da qual planejamos em endereçá-la em seguida."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1582
@@ -2050,18 +1943,7 @@
"java.util.HashSet implementation. The List interface maps to java.util."
"ArrayList implementation. The Map interface maps to java.util.HashMap "
"implementation."
-msgstr ""
-"Currently, we only support a limited implementation of Collection classes. "
-"That is, we support APIs in List, Set, and Map. However, since the APIs do "
-"not stipulate of constraints like NULL key or value, it makes mapping of "
-"user instance to our proHTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes.xy tricky. For example, ArrayList would allow NULL "
-"value and some other implementation would not. The Set interface maps to "
-"java.util.HashSet implementation. The List interface maps to java.util."
-"ArrayList implementation. The Map interface maps to java.util.HashMap "
-"implementation."
+msgstr "Atualmente, apenas suportamos uma implementação limitada das classes de Coleção. Isto é, suportamos APIs em Listar, Configurar e Mapear. No entanto, uma vez que os APIs não estipulam os obstáculos como a tecla NULL ou valor, eles fazem com que o mapeamento da instância do usuário seja complicada para nosso proxy. Por exemplo, o ArrayList permitiria um valor NULL enquanto algumas outras implementação não permitiriam. A interface Configurar não mapeia para a implementação java.util.HashSet. A interface Listar mapeia para a implementação java.util.HashMap."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1590
@@ -2072,35 +1954,19 @@
"slow. Performance between Set, Map and List collections also vary. Adding "
"items to a Set is slower than a List or Map, since Set does not allow "
"duplicate entries."
-msgstr ""
-"Another related issue is the expected performance. For example, the current "
-"implementation is ordered, so that makes insert/delete from the Collection "
-"slow. Performance between Set, Map and List collections also vary. Adding "
-"items to a Set is slower than a List or Map, since Set does not allow "
-"duplicate entries."
+msgstr "Outro problema relativo é o desempenho esperado. Por exemplo: a implementação atual é ordenada, de forma que isto faz a inserção/deletação lenta, a partir da Coleção. O adicionamento de ítens ao Configurar é mais lenta quando compararmos com Listar ou mapear, uma vez que Configurar não permite entradas duplicadas. "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1604
#, no-c-format
msgid "What are the pros and cons of PojoCache?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <empHTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes.hasis>one</emphasis> of the nodes."
+msgstr "Quais são os prós e contras do PojoCache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1608
#, no-c-format
msgid "As mentioned in the reference doc, PojoCache has the following advantages:"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Conforme mencionado na referência doc, o PojoCache possui as seguintes vantagens:"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1611
@@ -2110,11 +1976,7 @@
"PojoCache and once your POJO is put in the cache store, there is no need to "
"use another API to trigger your changes. Furthermore, the replication are "
"fine-grained field level. Note this also applies to persistency."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Replicação fine-grained e/ou persistência. Caso você utilize um PojoCache distribuído e uma vez que seu Pojo seja colocado no armazenamento do cache, não há necessidade para usar outro API para realizar o trigger em suas alterações. Além disso, as replicações estão em um nível de campo fine-grained. Perceba que isto também aplica-se à persistência."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1618
@@ -2122,11 +1984,7 @@
msgid ""
"Fine-grained replication can have potential performance gain if your POJO is "
"big and the changes are fine-grained, e.g., only to some selected fields."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "A replicação fine-grained pode possuir o potencial de ganhar desempenho, caso o POJO seja grande e as alterações sejam fine-grained. Por exemplo: apenas para alguns campos selecionados."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1623
@@ -2134,24 +1992,13 @@
msgid ""
"POJO can posses object relationship, e.g., multiple referenced. Distributed "
"PojoCache will handle this transparently for you."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <empHTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes.hasis>one</emphasis> of the nodes."
+msgstr "O POJO pode possuir relacionamento de objeto, por exemplo: múltiplo referenciado. O PojoCache Distribuído manuseará isto claramente a você."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1628
#, no-c-format
msgid "And here are some cases that you may not want to use PojoCache:"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Segue abaixo alguns casos em que você não desejará usar o PojoCache:"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1631
@@ -2160,11 +2007,7 @@
"You use only cache. That is you don't need replication or persistency. Then "
"since everything is operated on the in-memory POJO reference, there is no "
"need for PojoCache."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O uso apenas do cache. Quer dizer, você não precisará de replicação ou persistência. Então, uma vez que tudo é operado na referência do POJO em memória, não há necessidade alguma para o PojoCache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1636
@@ -2173,11 +2016,7 @@
"You have simple and small POJOs. Your POJO is small in size and also there "
"is no object relationship, then PojoCache possess not clear advantage to "
"plain cache."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Você possua POJOs simples e pequenos. O seu POJO é pequeno em tamanho e também não há relacionamento de objeto, então a posse do PojoCache não clareia a vantagem do cache plano. "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1641
@@ -2187,11 +2026,7 @@
"twice as much of memory (the original POJO in-memory space and also the "
"additional cache store for the primitive fields), you may not want to use "
"PojoCache."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O seu aplicativo seja vinculado por uso de memória. Uma vez que o PojoCache precisa quase o dobro de memória (o espaço em memória do POJO original e também o armazenamento do cache original para os campos primitivos), você provavelmente não desejará utilizar o PojoCache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1647
@@ -2200,31 +2035,19 @@
"Your POJO lifetime is short. That is, you need to create and destroy your "
"POJO often. Then you need to do \"pubObject\" and \"removeObject\" often, it "
"will be slow in performance."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O tempo de vida de seu POJO seja curto. Isto é, você precisa criar e destruir seu POJO com freqüência. Desta maneira, você precisa realizar o \"pubObject\" e \"removeObject\" com freqüência, sendo que isto fará com que o desempenho se torne bastante demorado."
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:1657
#, no-c-format
msgid "Eviction Policies"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Políticas de Remoção"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1664
#, no-c-format
msgid "Does JBoss Cache support eviction policies?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O JBoss Cache suporta as políticas de remoção?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1668
@@ -2237,11 +2060,7 @@
"for details. Currently there is user-contributed policy called "
"<literal>FIFOPolicy</literal> that evicts the node based on FIFO principle "
"only."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Sim. O JBoss Cache implementa atualmente uma política de remoção LRU para ambos TreeCache (<literal>org.jboss.cache.eviction.LRUPolicy</literal>) e PojoCache (<literal>org.jboss.cache.aop.eviction.AopLRUPolicy</literal>). Os usuários podem também liga-se às próprias políticas de remoção. Consulte o manual do usuário para maiores detalhes. Atualmente, existe uma política do usuário contribuinte chamada <literal>FIFOPolicy</literal>, pela qual remove o nó baseado no princípio FIFO apenas."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1689
@@ -2249,11 +2068,7 @@
msgid ""
"Why can't I use <literal>org.jboss.cache.eviction.LRUPolicy</literal> for "
"PojoCache as well?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "E por quê eu ão posso usar o <literal>org.jboss.cache.eviction.LRUPolicy</literal> para o PojoCache também?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1697
@@ -2263,10 +2078,8 @@
"AopLRUPolicy</literal> ) because AOP has its eviction algorithm, although is "
"LRU but has totally different notion of an \"object\", for example."
msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+"Para o PojoCache, você precisará usar o <literal>org.jboss.cache.aop.eviction."
+"AopLRUPolicy</literal>, pois o AOP possui o próprio algoritmo de remoção, mesmo sendo LRU, ele possui uma noção totalmente diferente de um \"object\", por exemplo."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1708
@@ -2274,21 +2087,13 @@
msgid ""
"Does JBoss Cache's implemented LRU eviction policy operates in replication "
"mode?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O JBoss Cache de política de remoção LRU implementada opera no modo de replicação?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1714
#, no-c-format
msgid "Yes and no. :-)"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Sim e não. :-)"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1716
@@ -2301,11 +2106,7 @@
"returns null), it should get it from the other data source and re-populate "
"the data in the cache. During this moment, the node content will be "
"propagated and the cache content will be in sync."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "A política LRU apenas opera no modo local. Isto é, os nós são apenas removidos localmente. O resultado disto poderá ser que os conteúdos do cache não sejam sincronizados temporariamente. Mas, quando um usuário tentar obter os conteúdos do cache de um nó removido e descobrir que que ele é nulo (por exemplo: <literal>get</literal> retornar nulo), isto deverá obter isto a partir de outra fonte de recurso e re-abastecer os dados no cache. Neste momento, o conteúdo do nó será propagado e o conteúdo do cache estará em sync."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1727
@@ -2316,11 +2117,7 @@
"your use case, you can set multiple cache instances to have their own "
"eviction policy (which are applied locally) or just have selected instances "
"with eviction policies activated."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "No entanto, você pode continuar rodando as políticas de remoção com a configuração de modo do cache, para tanto o <literal>REPL_SYNC</literal> ou <literal>REPL_ASYNC</literal>. Dependo do seu caso de uso, você poderá configurar instâncias de cache múltiplas para ter a própria política de remoção (da qual é aplicada localmente) ou apenas possui instâncias selecionadas com as políticas de remoção ativadas."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1738
@@ -2329,21 +2126,13 @@
"Also note that, with cache loader option, a locally evicted node can also be "
"persisted to the backend store and a user can retrieve it from the store "
"later on."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Perceba também, com a opção do carregador do cache, um nó removido localmente pode também ser persistido ao ao armazenamento backend e um usuário pode restaurar isto, a partir do armazenamento mais tarde."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1747
#, no-c-format
msgid "Does JBoss Cache support <literal>Region</literal> ?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O JBoss Cache suporta <literal>Region</literal>?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1754
@@ -2353,10 +2142,8 @@
"eviction policy parameters (e.g., <literal>maxNodes</literal> or "
"<literal>timeToIdleSeconds</literal> )"
msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+"Sim. O JBoss Cache possui a noção de região, onde um usuário pode configurar os parâmetros da política de remoção (por exemplo: <literal>maxNodes</literal> ou "
+"<literal>timeToIdleSeconds</literal>)."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1762
@@ -2368,11 +2155,7 @@
"separate regions. But note that you can configure the region "
"programmatically now, i.e., everything has to be configured through the xml "
"file."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Uma região no JBoss Cache marca uma porção da hierarquia tree, por exemplo: um nome inteiramente qualificado (<literal>FQN</literal>). Por exemplo: um usuário pode definir<literal>/org/jboss</literal> e <literal>/org/foocom</literal> como duas regiões separadas. No entanto, perceba que você pode configurar a região de maneira programática agora, por exemplo: tudo deve ser configurado através do arquivo xml."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1779
@@ -2380,41 +2163,25 @@
msgid ""
"What are the <literal>EvictionPolicyConfig</literal> tag parameters for "
"<literal>org.jboss.cache.eviction.LRUPolicy</literal> ?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Quais são os parâmetros de caracter <literal>EvictionPolicyConfig</literal> para a <literal>org.jboss.cache.eviction.LRUPolicy</literal>?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1789
#, no-c-format
msgid "They are:"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Eles são:"
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:1793
#, no-c-format
msgid "Parameters"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Parâmetros"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1798
#, no-c-format
msgid "wakeUpIntervalInSeconds"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "wakeUpIntervalInSeconds"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1800
@@ -2422,21 +2189,13 @@
msgid ""
"Interval where the clean up thread wakes to process the sitting queue and "
"sweep away the old data."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Intervalo onde o segmento de limpeza acorda para processar o a fila de espera e limpa os dados antigos. "
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1806
#, no-c-format
msgid "region"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "região"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1808
@@ -2444,51 +2203,31 @@
msgid ""
"A area where each eviction policy parameters are specified. Note that it "
"needs a minimum of <literal>/_default</literal> region."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Uma área onde os parâmetros de cada política de remoção estão especificados. Perceba que isto precisa de um número mínimo de regiões <literal>/_default</literal>."
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1816
#, no-c-format
msgid "maxNodes"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "maxNodes"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1818
#, no-c-format
msgid "Max number of nodes allowed in the eviction queue. 0 means no limit."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Número max de nós permitidos na fila de remoção. 0 significa que não há limite."
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1824
#, no-c-format
msgid "timeToLiveInSeconds"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "timeToLiveInSeconds"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1826
#, no-c-format
msgid "Age (in seconds) for the node to be evicted in the queue. 0 denotes no limit."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Idade (em segundos) para o nó ser removido da fila. 0 marca estipula não-limite."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1838
@@ -2496,11 +2235,7 @@
msgid ""
"I have turned on the eviction policy, why do I still get \"out of memory"
"\" (OOM) exception?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Eu acionei a política de remoção, por quê eu continuo obtendo a exceção (OOM) \"fora da memória\"?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1844
@@ -2515,10 +2250,8 @@
"the VM heap size, you can also reduce the <literal>wakeUpIntervaleInSeconds</"
"literal> so the timer thread processes the queue more frequently."
msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+"OOM pode ocorrer quando a velocidade de acesso do cache excede a velocidade do controlador de tempo de manuseio da política de remoção. O manuseador da política de remoção estimulará cada segundo do <literal>wakeUpIntervalInSeconds</literal> para processar a fila do evento de remoção. Além disso, o tamanho da fila é fixado em 2000, agora. Desta maneira, quando o tamanho da fila estiver cheio, ele criará um backlog, fazendo com que o OOM aconteça, a não ser que o controlador de tempo da remoção o alcance. Para endereçar este problema, adicionado ao aumento do tamanho de empilhamento VM, você pode também reduzir o <literal>wakeUpIntervaleInSeconds</"
+"literal>, de forma que o segmento do controlador de tempo a fila mais freqüente. "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1858
@@ -2526,31 +2259,19 @@
msgid ""
"We will also externalize the queue size so it will be configurable in the "
"next release."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Nós também externalizaremos o tamanho da fila, para que isto seja configurável na próxima versão."
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:1866
#, no-c-format
msgid "Cache Loaders"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Cache Loaders"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1873
#, no-c-format
msgid "What is a CacheLoader?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O que é o CacheLoader?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1877
@@ -2561,11 +2282,7 @@
"data is not in the cache, and when modifications are made to data in the "
"cache the CacheLoader is called to store those modifications back to the "
"store."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O CacheLoader é a conexão do JBossCache a um armazenamento de dados (persistentes). O CacheLoader é chamado pelo JBossCache para prtoduzir dados a partir de um armazenamento, quando aqueles dados não estiverem no cache, e quando as modificações efetuadas para os dados do CacheLoader forem chamadas para armazenar aquelas modificações de volta ao armazenamento."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1884
@@ -2577,11 +2294,7 @@
"data is evicted, in order to provide fast access to frequently accessed "
"data. This is all configured through XML, and the programmer doesn't have to "
"take care of loading and eviction."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Em conjunção com as políticas de remoção, o JBossCache com o CacheLoader permitem que o usuário mantenha um cache vinculado para um grande armazenamento de dados backend. Os dados usados são freqüentemente produzidos a partir de um armazenamento de dados dentro do cache, e os dados menos utilizados são removidos. Tudo isto, com o objetivo de fornecer o acesso rápido aos dados acessados com mais freqüência. Isto é todo configurado através do XML e o programador não precisa preocupar-se com o carregamento e a remoção. "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1893
@@ -2589,11 +2302,7 @@
msgid ""
"JBossCache currently ships with several CacheLoader implementations, "
"including:"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O JBossCache atualmente lança diversas implementações do CacheLoader, incluindo:"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1900
@@ -2604,10 +2313,8 @@
"subdirectories etc. Attributes of a node are mapped to a file <literal>data</"
"literal> inside the directory."
msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+"FileCacheLoader: isto implementa o uso do sistema do arquivo para o armazenamento e restauração de dados. Os nós do JBossCache estão mapeados para diretórios e sub-nós para sub-diretórios, etc. Os atributos de um nó estão mapeados para um arquivo de <literal>data</"
+"literal>, dentro do diretório."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1911
@@ -2620,10 +2327,10 @@
"url=\"http://www.sleepycat.com/jeforjbosscache\">commercial license from "
"Sleepycat </ulink> ."
msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+"BdbjeCacheLoader: esta implementação baseia-se no banco de dados de Edição Java Sleepycat, um banco de dados transacional rápido e eficiente. Isto utiliza um arquivo único para o armazenamento completo. Perceba que se você usar o Sleepycat do CacheLoader com o JBoss Cache e desejar lançar seu produto, Você terá que adquirir uma <ulink "
+"url=\"http://www.sleepycat.com/jeforjbosscache\">commercial license from "
+"Sleepycat </ulink> . <ulink "
+"url=\"http://www.sleepycat.com/jeforjbosscache\"> licença comercial a partir do Sleepycat</ulink>."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1923
@@ -2631,11 +2338,7 @@
msgid ""
"JDBCCacheLoader: this implementation uses the relational database as the "
"persistent storage."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "JDBCCacheLoader: esta implementação usa o banco de dados relacional como um armazenamento persistente."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1929
@@ -2643,31 +2346,19 @@
msgid ""
"ClusteredCacheLoader: this implementation queries the rest of the cluster, "
"treating other servers' in-memory state as a data store."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "ClusteredCacheLoader: esta implementação questiona o resto do cluster, manejando os outros servidores de estado em memória como um armazenamento de dados."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1935
#, no-c-format
msgid "And more. See the documentation for more details."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Por favor, consulte a documentação para maiores detalhes e informações."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1944
#, no-c-format
msgid "Can writing to CacheLoaders be asynchronous?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Eu posso rodar o CacheLoaders como assíncrono?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1948
@@ -2676,21 +2367,13 @@
"As of JBossCache 1.2.4, yes. Set the CacheLoaderAsynchronous property to "
"true. See the JBossCache documentation for a more detailed discussion. By "
"default though, all cache loader writes are synchronous and will block."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Como parte do JBossCache 1.2.4, sim. Confogure a propriedade do CacheLoaderAsynchronous para verdadeiro. Consulte a documentação do JBossCache para informações mais detalhadas. Pelo padrão, todos os carregadores de cache são assíncronos e irão bloquear. "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1958
#, no-c-format
msgid "Can I write my own CacheLoader ?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Eu posso gravar meu próprio CacheLoader?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1962
@@ -2700,20 +2383,14 @@
"CacheLoader</literal> . It is configured via the XML file (see JBossCache "
"and Tutorial documentation)."
msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+"Sim. O CacheLoader é uma classe implementando o <literal>org.jboss.cache.loader."
+"CacheLoader</literal>. Ele é configurado através do arquivo XML (consulte o JBossCache e a documentação tutorial)."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1973
#, no-c-format
msgid "Does a CacheLoader have to use a persistent store ?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O CacheLoader precisa utilizar um armazenamento persistente?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1977
@@ -2724,31 +2401,19 @@
"fetches contents from the web. Note that an implementation of CacheLoader "
"may not implement the 'store' functionality in this case, but just the "
"'load' functionality."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "No, um CacheLoader poderia, por exemplo, produzir (e possivelmente armazenar) os próprios dados a partir de um webdav-capable webserver. Outro exemplo, é o servidor caching proxy, pelo qual produz os conteúdos a partir da web. Perceba que uma implementação do CacheLoader não poderá implementar a funcionalidade de 'armazenamento' neste caso, mas apenas a funcionalidade de 'carregamento'."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1989
#, no-c-format
msgid "What can I use a CacheLoader for?"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "O que eu posso usar o CacheLoader para?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1993
#, no-c-format
msgid "Some applications:"
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "Alguns aplicativos:"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1998
@@ -2758,11 +2423,7 @@
"CacheLoader can be configured to be shared, or unshared, meaning that every "
"node in a cluster has its own local store. It is also possible to attach a "
"CacheLoader to just <emphasis>one</emphasis> of the nodes."
-msgstr ""
-"HTTP sessions can be persisted (besides being replicated by JBossCache). The "
-"CacheLoader can be configured to be shared, or unshared, meaning that every "
-"node in a cluster has its own local store. It is also possible to attach a "
-"CacheLoader to just <emphasis>one</emphasis> of the nodes."
+msgstr "As sessões HTTP podem ser persistentes (fora o fato de serem replicadas pelo JBossCache). O CacheLoader pode ser "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2010
More information about the jboss-cvs-commits
mailing list