[jboss-cvs] JBossAS SVN: r77261 - projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Aug 21 00:41:54 EDT 2008
Author: ldelima at redhat.com
Date: 2008-08-21 00:41:54 -0400 (Thu, 21 Aug 2008)
New Revision: 77261
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-21 02:35:53 UTC (rev 77260)
+++ projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po 2008-08-21 04:41:54 UTC (rev 77261)
@@ -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:17+1000\n"
+"PO-Revision-Date: 2008-08-21 14:41+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,15 +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 ""
-"To solve the second kind of issue, the only solution (that we know of) is to "
-"cache \"serialized\" byte code and only de-serialize it during every object "
-"get (and this will be expensive!). That is, during a put operation, the "
-"object instance will be serialized and therefore can be deserialized safely "
-"by a \"foreign\" classloader. However, the performance penalty of this "
-"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) "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:952
@@ -1116,11 +1108,7 @@
"<literal>MarshalledValue</literal> that wraps around the serialized object. "
"Here is a code snippet that illustrates how you can create a wrapper around "
"JBossCache to handle the classloader issue:"
-msgstr ""
-"To help with this kind of handling, JBoss has a utility class called "
-"<literal>MarshalledValue</literal> that wraps around the serialized object. "
-"Here is a code snippet that illustrates how you can create a wrapper around "
-"JBossCache to handle the classloader issue:"
+msgstr "Para auxílio neste tipo de manuseio, o JBoss possui a classe de utilidade chamada <literal>MarshalledValue</literal>, que se dispõe ao redor do objeto serializado. Segue abaixo, o trecho do código que ilustra como você pode criar uma disposição em volta do JBossCache, para o manuseio do problema do carregador de classe:"
#. Tag: programlisting
#: Cache_Frequently_Asked_Questions.xml:961
@@ -1182,7 +1170,7 @@
#: Cache_Frequently_Asked_Questions.xml:967
#, no-c-format
msgid "Does JBoss Cache currently support pre-event and post-event notification?"
-msgstr "Does JBoss Cache currently support pre-event and post-event notification?"
+msgstr "O JBoss Cache suporta atualmente a notificação de pré e pós-evento?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:973
@@ -1193,12 +1181,7 @@
"notification. See documentation for more details. Note that "
"TreeCacheListener and ExtendedTreeCacheListener will be merged into "
"TreeCacheListener in release 1.3."
-msgstr ""
-"Yes. Starting with release 1.2.4, JBoss Cache has introduced "
-"ExtendedTreeCacheListener which takes in consideration pre and post event "
-"notification. See documentation for more details. Note that "
-"TreeCacheListener and ExtendedTreeCacheListener will be merged into "
-"TreeCacheListener in release 1.3."
+msgstr "Sim. Inicializando com a versão 1.2.4, o JBoss Cache introduziu o ExtendedTreeCacheListener, do qual leva em consideração a notificação de pré e pós-evento. Consulte a documentação para informações mais detalhadas. Perceba que o TreeCacheListener e ExtendedTreeCacheListener irão mergir para o TreeCacheListener na versão 1.3."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:984
@@ -1207,8 +1190,8 @@
"How do I implement a custom listener to listen to <literal>TreeCache</"
"literal> events?"
msgstr ""
-"How do I implement a custom listener to listen to <literal>TreeCache</"
-"literal> events?"
+"Como eu implemento um ouvinte personalizado para escutar os eventos do <literal>TreeCache</"
+"literal>?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:991
@@ -1220,10 +1203,7 @@
"listen to the events as they occur by calling TreeCache.addTreeCacheListener"
"(myListener)."
msgstr ""
-"You create a class (myListener) that extends AbstractTreeCacheListener and "
-"provide concrete implementation for the node events that you are interested "
-"in. Then you add this listener to the TreeCache instance on startup to "
-"listen to the events as they occur by calling TreeCache.addTreeCacheListener"
+"Você cria a classe (myListener) que extende o AbstractTreeCacheListener e fornece implementação concreta para os eventos de nó, dos quais você possui interesse. E, então, você adicionará este ouvinte à instância TreeCache na inicialização, com a finalidade de escutar os eventos uma vez que eles ocorrem pela chamada do TreeCache.addTreeCacheListener"
"(myListener)."
#. Tag: programlisting
@@ -1269,10 +1249,7 @@
"Can I use <literal>useRegionBasedMarshalling</literal> attribute in JBoss "
"Cache in order to get around ClassCastExceptions happening when accessing "
"data in the cache that has just been redeployed?"
-msgstr ""
-"Can I use <literal>useRegionBasedMarshalling</literal> attribute in JBoss "
-"Cache in order to get around ClassCastExceptions happening when accessing "
-"data in the cache that has just been redeployed?"
+msgstr "Posso usar o atributo <literal>useRegionBasedMarshalling</literal> no JBoss Cache com a finalidade das ClassCastExceptions ocorrerem, quando acessando os dados em cada cache, do qual acabou de ser re-implementado?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1011
@@ -1282,11 +1259,7 @@
"designed as a workaround for those replicated caches that upon state "
"transfer did not have access to the classloaders defining the objects in the "
"cache."
-msgstr ""
-"Yes, you can. Originally, <literal>TreeCache</literal> Marshalling was "
-"designed as a workaround for those replicated caches that upon state "
-"transfer did not have access to the classloaders defining the objects in the "
-"cache."
+msgstr "Sim, você pode. Originalmente o <literal>TreeCache</literal> Marshalling foi criado como um trabalho para aqueles caches replicados que até o estado de transferência, não possui pacesso aos carregadores de classe definindo os objetos no cache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1016
@@ -1302,17 +1275,7 @@
"would result on a ClassCastException. This is because even though the class "
"names are the same, the class definitions are not. The current classloader "
"is different to the one when the classes were originally put."
-msgstr ""
-"On each deployment, JBoss creates a new classloader per the top level "
-"deployment artifact, for example an EAR. You also have to bear in mind that "
-"a class in an application server is defined not only by the class name but "
-"also its classloader. So, assuming that the cache is not deployed as part of "
-"your deployment, you could deploy an application and put instances of "
-"classes belonging to this deployment inside the cache. If you did a "
-"redeployment and try to do a get operation of the data previously put, this "
-"would result on a ClassCastException. This is because even though the class "
-"names are the same, the class definitions are not. The current classloader "
-"is different to the one when the classes were originally put."
+msgstr "Em cada implementação, o JBoss cria um novo carregador de classe por artefato de implementação de nível top, por exemplo um EAR. Você terá que ter em mente que a classe no servidor do aplicativo é definido não apenas pelo nome da classe, mas também por seu carregador de classe. Desta forma, assumimos que o cache não é implementado como parte de sua implementação. Você poderá implementar um aplicativo e colocar instâncias de classes pertencentes a esta implementação dentro do cache. Caso você tenha feito a re-implementação e tentar realizar a obtenção da operação dos dados adicionados anteriormente, isto poderá resultar numa ClassCastException. Isto deve-se ao fato de que mesmo que os nomes das classes serem os mesmos, as definições de classes não são as mesmas. O carregador de classe atual é diferente ao daquele em que as classes foram originalmente aderidas."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1026
@@ -1327,16 +1290,7 @@
"some kind of persistence backing where the data survives, for example using "
"CacheLoaders, or when JBossCache is used as a second level cache in a "
"persistence framework."
-msgstr ""
-"By enabling marshalling, you can control the lifecycle of the data in the "
-"cache and if on undeployment, you inactivate the region and unregister the "
-"classloader that you'd have registered on deployment, you'd evict the data "
-"in the cache locally. That means that in the next deployment, the data won't "
-"be in the cache, therefore avoiding the problem. Obviously, using "
-"marshalling to get around this problem is only recommended when you have "
-"some kind of persistence backing where the data survives, for example using "
-"CacheLoaders, or when JBossCache is used as a second level cache in a "
-"persistence framework."
+msgstr "Pela ativação do controle, você poderá controlar o ciclo de vida dos dados no cache e caso de uma desimplementação, você desativará a região e desiregistrará o carregador de classe que você registrou na implementação. Você removeria os dados localmente no cache. Isto significa que na próxima implementação, os dados não estarão no cache, portanto evitando o problema. É claro que o uso do controle para buscar este problema, é apenas recomendado quando você possuir algum tipo de persistência retornando para onde os dados sobrevivem, por exemplo o uso dos carregadores de Cache, ou quando o JbossCache for usado como cache de segundo nível num framework de persistência."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1035
@@ -1350,13 +1304,8 @@
"literal>. The key would be for this MBean to depend on the target cache, so "
"that it can operate as long as the cache is up and running."
msgstr ""
-"To implement this feature, please follow the instructions indicated in the "
-"example located in the TreeCacheMarshaller section of the user's guide. It's "
-"worth noting that instead of a <literal>ServletContextListener</literal>, "
-"you could add this code into an <literal>MBean</literal> that contained "
-"lifecycle methods, such as <literal>start()</literal> and <literal>stop()</"
-"literal>. The key would be for this MBean to depend on the target cache, so "
-"that it can operate as long as the cache is up and running."
+"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. "
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:1049
@@ -1384,17 +1333,7 @@
"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."
-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."
+msgstr "O PojoCache (atualmente implementado PojoCache como uma sub-classe do TreeCache) é um cache POJO (objeto Java antigo e plano) transacional e campo replicado a nível fine-grained. Pelo POJO, nós queremos dizer que o cache: 1) gerencia automaticamente o mapeamento do objeto e relação de um cliente sob ambos modos de cache replicado e local; 2) fornece suporte ao relacionamento de herança entre POJOs \"posicionados\". Se utilizarmos a dinâmica AOP no JBossAop, ele estará apto a mapear o objeto complexo no armazenamento do cache, preservando e gerenciando o relacionamento do objeto, nos bastidores. Durante o módulo de replicação, ele executa a atualização fine-granularity (por exemplo; baseando-se nos campos), e desta forma, ele possui o potencial de auxílio ao desempenho do cache, além do potencial de minimizar o tráfego da rede."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1073
@@ -1406,19 +1345,13 @@
"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."
-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."
+msgstr "Uma vez que seu POJO seja gerenciado pelo cache, todas as operações de cache serão transparentes, a partir de uma perspectiva do usuário. Portanto, todas as usuais semânticas de método no VM POJO continuam preservadas, fornecendo facilidades de uso. Por exemplo, caso o POJO tenha sido adicionado a um PojoCache (pela chamada putObjeto, por exemplo), então qualquer método obter/configurar será interceptado pelo PojoCache para o fornecimento de dados a partir do cache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1086
#, no-c-format
msgid "What's the relationship between PojoCache and TreeCacheAop classes?"
-msgstr "What's the relationship between PojoCache and TreeCacheAop classes?"
+msgstr "Qual é o relacionamento entre o PojoCache e as classes TreeCacheAop?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1090
@@ -1427,16 +1360,13 @@
"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."
-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."
+msgstr "Desde a versão 1.4, nós temos criado a nova classe chamada PojoCache (para melhor reflexo da natureza do cache). A antiga implementação TreeCacheAop não está mais em uso."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1098
#, no-c-format
msgid "Does PojoCache have all the functional capabilities of TreeCache?"
-msgstr "Does PojoCache have all the functional capabilities of TreeCache?"
+msgstr "O PojoCache possui todas as capacidades funcionais do TreeCache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1104
@@ -1444,15 +1374,13 @@
msgid ""
"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."
+msgstr "Sim. O PojoCache estende o TreeCache, de maneira com que ele possua os mesmos recursos do TreeCache, como o modo do cache, o nível de isolação de transação e a política de remoção."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1113
#, no-c-format
msgid "What is the difference between TreeCache and PojoCache?"
-msgstr "What is the difference between TreeCache and PojoCache?"
+msgstr "Qual é a diferença entre o TreeCache e o PojoCache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1119
@@ -1486,7 +1414,7 @@
#: Cache_Frequently_Asked_Questions.xml:1140
#, no-c-format
msgid "What are the steps to use the PojoCache feature?"
-msgstr "What are the steps to use the PojoCache feature?"
+msgstr "Quais são os passos para o uso do recurso do PojoCache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1144
@@ -1494,9 +1422,7 @@
msgid ""
"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:"
+msgstr "Inicializando pela versão 1.3, depende do JDK que você utilizará, uma vez que ele possui passos ligeiramente diferentes. Mas, em geral, veja a seguir o que é necessário para o uso do PojoCache:"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1151
@@ -1506,11 +1432,7 @@
"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."
-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."
+msgstr "preparação do POJO. Você pode tanto realizá-lo através da declaração ou anotação xml. No caso da anotação, você poderá usar tanto o estilo JDK1.4 ou JDK50 (do qual faz parte do JVM spec). Caso você utilize o JDK14, você precisará de uma anotação pré-compiladora (annoc) para pré-processá-lo."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1159
@@ -1521,12 +1443,7 @@
"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."
-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."
+msgstr "instrumentação. Você precisará instrumentar o seu POJO tanto no período de compilação quanto no período de carregamento. Caso você realize isto no período de compilação, você usará o chamado pré-compilador aop (aopc) para realizar a manipulação bytecode. Caso você realize isto através do período de carregamento, você precisará de um carregador de classe de sistema especial ou, no JDK50, você poderá usar a opção javaagent."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1168
@@ -1536,17 +1453,13 @@
"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."
-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."
+msgstr "Desta maneira, caso você use o JDK50, por exemplo, com a anotação e instrumentação de período de carregamento, então você não precisará de qualquer passo de pré-processamento para o uso dp PojoCache. Para um exemplo completo, por favor refira-se ao diretório de exemplos de distro. Existem diversos exemplos de PojoCache que usam diferentes opções."
#. 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 "Can I run PojoCache in JBoss AS 3.2.x application server?"
+msgstr "Posso rodar o PojoCache num servidor do aplicativo JBoss AS 3.2.x?1"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1185
@@ -1555,16 +1468,13 @@
"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."
-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."
+msgstr "Sim e não. Sim, desde que o JBossAop possa ser suporte também para o 3.2.x (consulte o JBossAop wiki para maiores informações a respeito). No entanto, isto será um imenso trabalho. Portanto, a versão do JBoss recomendada para rodar o PojoCache é 4.x."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1195
#, no-c-format
msgid "Can PojoCache run as a MBean as well?"
-msgstr "Can PojoCache run as a MBean as well?"
+msgstr "Posso rodar o PojoCache como um MBean também?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1199
@@ -2144,7 +2054,10 @@
"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 proxy tricky. For example, ArrayList would allow NULL "
+"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 "
@@ -2171,12 +2084,23 @@
#, 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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1611
@@ -2187,6 +2111,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1618
@@ -2195,6 +2123,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1623
@@ -2203,12 +2135,23 @@
"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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1631
@@ -2218,6 +2161,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1636
@@ -2227,6 +2174,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1641
@@ -2237,6 +2188,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1647
@@ -2246,18 +2201,30 @@
"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."
#. 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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1668
@@ -2271,6 +2238,10 @@
"<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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1689
@@ -2279,6 +2250,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1697
@@ -2288,6 +2263,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1708
@@ -2296,12 +2275,20 @@
"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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1716
@@ -2315,6 +2302,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1727
@@ -2326,6 +2317,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1738
@@ -2335,12 +2330,20 @@
"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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1754
@@ -2350,6 +2353,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1762
@@ -2362,6 +2369,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1779
@@ -2370,24 +2381,40 @@
"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."
#. 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."
#. 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."
#. 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."
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1800
@@ -2396,12 +2423,20 @@
"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."
#. 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."
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1808
@@ -2410,30 +2445,50 @@
"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."
#. 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."
#. 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."
#. 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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1838
@@ -2442,6 +2497,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1844
@@ -2456,6 +2515,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1858
@@ -2464,18 +2527,30 @@
"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."
#. 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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1877
@@ -2487,6 +2562,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1884
@@ -2499,6 +2578,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1893
@@ -2507,6 +2590,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1900
@@ -2517,6 +2604,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1911
@@ -2529,6 +2620,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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1923
@@ -2537,6 +2632,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1929
@@ -2545,18 +2644,30 @@
"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."
#. 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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1948
@@ -2566,12 +2677,20 @@
"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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1962
@@ -2581,12 +2700,20 @@
"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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1977
@@ -2598,18 +2725,30 @@
"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."
#. 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."
#. 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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1998
@@ -2620,6 +2759,10 @@
"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."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2010
@@ -2628,6 +2771,8 @@
"Simple persistence for POJOs. Use of JBossCache aop and a local CacheLoader "
"persist POJOs transparently into the store provided by the CacheLoader."
msgstr ""
+"Simple persistence for POJOs. Use of JBossCache aop and a local CacheLoader "
+"persist POJOs transparently into the store provided by the CacheLoader."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2017
@@ -2638,6 +2783,10 @@
"when the first node is started again, the data previously saved will still "
"be available (e.g. a shopping cart)."
msgstr ""
+"Highly available replicated and persisted data store. The service is up as "
+"long as at least 1 node is running, but even if all nodes are taken offline, "
+"when the first node is started again, the data previously saved will still "
+"be available (e.g. a shopping cart)."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2026
@@ -2648,12 +2797,16 @@
"fetches it from the web. This could actually be a replicated and "
"transactional version of Squid."
msgstr ""
+"A caching web proxy (a la Squid): all data are contents of URLs, users "
+"access the proxy, and if the URL is not in the cache, the CacheLoader "
+"fetches it from the web. This could actually be a replicated and "
+"transactional version of Squid."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2040
#, no-c-format
msgid "How do I configure JBossCache with a CacheLoader?"
-msgstr ""
+msgstr "How do I configure JBossCache with a CacheLoader?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2044
@@ -2663,12 +2816,15 @@
"configuration string have to be given. JBossCache will then instantiate a "
"CacheLoader. See JBossCache documentation for details."
msgstr ""
+"Through XML: both the fully-qualified classname of the CacheLoader and its "
+"configuration string have to be given. JBossCache will then instantiate a "
+"CacheLoader. See JBossCache documentation for details."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2054
#, no-c-format
msgid "Do I have to pay to use Sleepycat's CacheLoader?"
-msgstr ""
+msgstr "Do I have to pay to use Sleepycat's CacheLoader?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2058
@@ -2679,12 +2835,16 @@
"from Sleepycat. See details at <ulink url=\"http://www.sleepycat.com/"
"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ."
msgstr ""
+"Not if you use it only for personal use. As soon as you distribute your "
+"product with BdbjeCacheLoader, you have to purchase a commercial license "
+"from Sleepycat. See details at <ulink url=\"http://www.sleepycat.com/"
+"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2071
#, no-c-format
msgid "Can I use more than one cache loader?"
-msgstr ""
+msgstr "Can I use more than one cache loader?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2075
@@ -2698,6 +2858,13 @@
"written to (except if the ignoreModifications element has been set to true "
"for a specific cache loader."
msgstr ""
+"As of JBossCache 1.3.0, yes. With the new CacheLoaderConfiguration XML "
+"element (see user manual section on cache loaders) you can now describe "
+"several cache loaders. The impact is that the cache will look at all of the "
+"cache loaders in the order they've been configured, until it finds a valid, "
+"non-null element of data. When performing writes, all cache loaders are "
+"written to (except if the ignoreModifications element has been set to true "
+"for a specific cache loader."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2089
@@ -2707,6 +2874,9 @@
"pessimistic locking, and I attempt to read a node after removing it from "
"within the same transaction scope?"
msgstr ""
+"Why do cache loaders go into an inconsistent state when I use transactions, "
+"pessimistic locking, and I attempt to read a node after removing it from "
+"within the same transaction scope?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2096
@@ -2718,6 +2888,11 @@
"JBoss Cache 1.4.0. A very simple workaround if you're using JBoss Cache 1.3."
"x is to use optimistic locking."
msgstr ""
+"This is a known bug (see <ulink url=\"http://jira.jboss.com/jira/browse/"
+"JBCACHE-477\">JBCACHE-477</ulink> and <ulink url=\"http://jira.jboss.com/"
+"jira/browse/JBCACHE-352\">JBCACHE-352</ulink> ), which have been fixed in "
+"JBoss Cache 1.4.0. A very simple workaround if you're using JBoss Cache 1.3."
+"x is to use optimistic locking."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2104
@@ -2729,12 +2904,17 @@
"pessimistic locking and a cache loader), you may see IllegalStateExceptions "
"thrown."
msgstr ""
+"One of the consequences of this bug is that, for example, if you use "
+"PojoCache with pojos that have private references to a List and you update "
+"and remove someelements of that List within a transaction (when using "
+"pessimistic locking and a cache loader), you may see IllegalStateExceptions "
+"thrown."
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:2116
#, no-c-format
msgid "Troubleshooting"
-msgstr ""
+msgstr "Troubleshooting"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2121
@@ -2743,6 +2923,8 @@
"I am having problems getting JBoss Cache to work, where can I get "
"information on troubleshooting?"
msgstr ""
+"I am having problems getting JBoss Cache to work, where can I get "
+"information on troubleshooting?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2125
@@ -2752,4 +2934,7 @@
"wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheTroubleshooting\">wiki link</"
"ulink> ."
msgstr ""
+"Troubleshooting section can be found in the following <ulink url=\"http://"
+"wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheTroubleshooting\">wiki link</"
+"ulink> ."
More information about the jboss-cvs-commits
mailing list