[jbosscache-commits] JBoss Cache SVN: r7395 - in enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide: pot and 1 other directory.
jbosscache-commits at lists.jboss.org
jbosscache-commits at lists.jboss.org
Thu Jan 8 00:17:29 EST 2009
Author: irooskov at redhat.com
Date: 2009-01-08 00:17:29 -0500 (Thu, 08 Jan 2009)
New Revision: 7395
Modified:
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/en-US/Introduction.xml
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Architecture.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Basic_api.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Book_Info.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Cache_loaders.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Colophon.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Compatibility.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Configuration.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Eviction_policies.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Introduction.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Jboss_integration.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Mgmt_information.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Replication.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/State_transfer.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Transactions.pot
enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Treecache_marshaller.pot
Log:
updated Introduction with JIRA JBPAPP-1434 fix and updated pot files
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/en-US/Introduction.xml
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/en-US/Introduction.xml 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/en-US/Introduction.xml 2009-01-08 05:17:29 UTC (rev 7395)
@@ -6,7 +6,7 @@
<section id="Introduction-What_is_a_TreeCache">
<title>What is a TreeCache?</title>
<para>
- A <literal>TreeCache</literal> is a tree-structured, replicated, transactional cache from JBoss Cache. <literal>TreeCache</literal> is the backbone for many fundamental JBoss Application Server clustering services, including - in certain versions - clustering JNDI, HTTP and EJB sessions, and clustering JMS.
+ A <literal>TreeCache</literal> is a tree-structured, replicated, transactional cache from JBoss Cache. <literal>TreeCache</literal> is the backbone for many fundamental JBoss Application Server clustering services, including - in certain versions - HTTP and EJB sessions.
</para>
<para>
In addition to this, <literal>TreeCache</literal> can be used as a standalone transactional and replicated cache or even an object oriented data store, may be embedded in other J2EE compliant application servers such as BEA WebLogic or IBM WebSphere, servlet containers such as Tomcat, or even in Java applications that do not run from within an application server.
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Architecture.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Architecture.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Architecture.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,42 +1,51 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:25-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Architecture.xml:15(None)
-msgid "@@image: 'images/TreeCacheArchitecture.png'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-
-#: ./Architecture.xml:10(title)
+#. Tag: title
+#: Architecture.xml:5
+#, no-c-format
msgid "Architecture"
msgstr ""
-#: ./Architecture.xml:12(title)
+#. Tag: title
+#: Architecture.xml:7
+#, no-c-format
msgid "Schematic TreeCache architecture"
msgstr ""
-#: ./Architecture.xml:19(para)
-msgid "The architecture is shown above. The example shows 2 Java VMs, each has created an instance of <literal>TreeCache</literal>. These VMs can be located on the same machine, or on 2 different machines. The setup of the underlying group communication subsystem is done using <ulink url=\"http://www.jgroups.org\">JGroups</ulink>."
+#. Tag: para
+#: Architecture.xml:14
+#, no-c-format
+msgid ""
+"The architecture is shown above. The example shows 2 Java VMs, each has "
+"created an instance of <literal>TreeCache</literal>. These VMs can be "
+"located on the same machine, or on 2 different machines. The setup of the "
+"underlying group communication subsystem is done using <ulink url=\"http://"
+"www.jgroups.org\">JGroups</ulink>."
msgstr ""
-#: ./Architecture.xml:23(para)
-msgid "Note that you can have more than 2 caches in a cluster."
+#. Tag: para
+#: Architecture.xml:17
+#, no-c-format
+msgid ""
+"Any modification (see API below) in one cache will be replicated to the "
+"other cache<footnote><para> Note that you can have more than 2 caches in a "
+"cluster. </para> </footnote> and vice versa. Depending on the transactional "
+"settings, this replication will occur either after each modification or at "
+"the end of a transaction (at commit time). When a new cache is created, it "
+"can optionally acquire the contents from one of the existing caches on "
+"startup."
msgstr ""
-
-#: ./Architecture.xml:22(para)
-msgid "Any modification (see API below) in one cache will be replicated to the other cache<placeholder-1/> and vice versa. Depending on the transactional settings, this replication will occur either after each modification or at the end of a transaction (at commit time). When a new cache is created, it can optionally acquire the contents from one of the existing caches on startup."
-msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Architecture.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Basic_api.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Basic_api.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Basic_api.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,124 +1,239 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:26-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Basic_api.xml:46(None)
-msgid "@@image: 'images/TreeNodeExample.png'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-
-#: ./Basic_api.xml:10(title)
+#. Tag: title
+#: Basic_api.xml:5
+#, no-c-format
msgid "Basic API"
msgstr ""
-#: ./Basic_api.xml:11(para)
+#. Tag: para
+#: Basic_api.xml:6
+#, no-c-format
msgid "Here's some sample code before we dive into the API itself:"
msgstr ""
-#: ./Basic_api.xml:14(programlisting)
-#, no-wrap
-msgid "TreeCache tree = new TreeCache();\ntree.setClusterName(\"demo-cluster\");\ntree.setClusterProperties(\"default.xml\"); // uses defaults if not provided\ntree.setCacheMode(TreeCache.REPL_SYNC);\ntree.createService(); // not necessary, but is same as MBean lifecycle\ntree.startService(); // kick start tree cache\ntree.put(\"/a/b/c\", \"name\", \"Ben\");\ntree.put(\"/a/b/c/d\", \"uid\", new Integer(322649));\nInteger tmp = (Integer) tree.get(\"/a/b/c/d\", \"uid\");\ntree.remove(\"/a/b\");\ntree.stopService();\ntree.destroyService(); // not necessary, but is same as MBean lifecycle\n"
+#. Tag: programlisting
+#: Basic_api.xml:9
+#, no-c-format
+msgid ""
+"TreeCache tree = new TreeCache();\n"
+"tree.setClusterName(\"demo-cluster\");\n"
+"tree.setClusterProperties(\"default.xml\"); // uses defaults if not "
+"provided\n"
+"tree.setCacheMode(TreeCache.REPL_SYNC);\n"
+"tree.createService(); // not necessary, but is same as MBean lifecycle\n"
+"tree.startService(); // kick start tree cache\n"
+"tree.put(\"/a/b/c\", \"name\", \"Ben\");\n"
+"tree.put(\"/a/b/c/d\", \"uid\", new Integer(322649));\n"
+"Integer tmp = (Integer) tree.get(\"/a/b/c/d\", \"uid\");\n"
+"tree.remove(\"/a/b\");\n"
+"tree.stopService();\n"
+"tree.destroyService(); // not necessary, but is same as MBean lifecycle"
msgstr ""
-#: ./Basic_api.xml:27(para)
-msgid "The sample code first creates a <literal>TreeCache</literal> instance and then configures it. There is another constructor which accepts a number of configuration options. However, the <literal>TreeCache</literal> can be configured entirely from an XML file (shown later) and we don't recommend manual configuration as shown in the sample."
+#. Tag: para
+#: Basic_api.xml:10
+#, no-c-format
+msgid ""
+"The sample code first creates a <literal>TreeCache</literal> instance and "
+"then configures it. There is another constructor which accepts a number of "
+"configuration options. However, the <literal>TreeCache</literal> can be "
+"configured entirely from an XML file (shown later) and we don't recommend "
+"manual configuration as shown in the sample."
msgstr ""
-#: ./Basic_api.xml:30(para)
-msgid "The cluster name, properties of the underlying JGroups stack, and cache mode (synchronous replication) are configured first (a list of configuration options is shown later). Then we start the <literal>TreeCache</literal>. If replication is enabled, this will make the <literal>TreeCache</literal> join the cluster, and acquire initial state from an existing node."
+#. Tag: para
+#: Basic_api.xml:13
+#, no-c-format
+msgid ""
+"The cluster name, properties of the underlying JGroups stack, and cache mode "
+"(synchronous replication) are configured first (a list of configuration "
+"options is shown later). Then we start the <literal>TreeCache</literal>. If "
+"replication is enabled, this will make the <literal>TreeCache</literal> join "
+"the cluster, and acquire initial state from an existing node."
msgstr ""
-#: ./Basic_api.xml:33(para)
-msgid "Then we add 2 items into the cache: the first element creates a node \"a\" with a child node \"b\" that has a child node \"c\". (<literal>TreeCache</literal> by default creates intermediary nodes that don't exist). The key \"name\" is then inserted into the \"/a/b/c\" node, with a value of \"Ben\"."
+#. Tag: para
+#: Basic_api.xml:16
+#, no-c-format
+msgid ""
+"Then we add 2 items into the cache: the first element creates a node \"a\" "
+"with a child node \"b\" that has a child node \"c\". (<literal>TreeCache</"
+"literal> by default creates intermediary nodes that don't exist). The key "
+"\"name\" is then inserted into the \"/a/b/c\" node, with a value of \"Ben\"."
msgstr ""
-#: ./Basic_api.xml:36(para)
-msgid "The other element will create just the subnode \"d\" of \"c\" because \"/a/b/c\" already exists. It binds the integer 322649 under key \"uid\"."
+#. Tag: para
+#: Basic_api.xml:19
+#, no-c-format
+msgid ""
+"The other element will create just the subnode \"d\" of \"c\" because \"/a/b/"
+"c\" already exists. It binds the integer 322649 under key \"uid\"."
msgstr ""
-#: ./Basic_api.xml:39(para)
+#. Tag: para
+#: Basic_api.xml:22
+#, no-c-format
msgid "The resulting tree looks like this:"
msgstr ""
-#: ./Basic_api.xml:43(title)
+#. Tag: title
+#: Basic_api.xml:26
+#, no-c-format
msgid "Sample Tree Nodes"
msgstr ""
-#: ./Basic_api.xml:50(para)
-msgid "The <literal>TreeCache</literal> has 4 nodes \"a\", \"b\", \"c\" and \"d\". Nodes \"/a/b/c\" has values \"name\" associated with \"Ben\" in its map, and node \"/a/b/c/d\" has values \"uid\" and 322649."
+#. Tag: para
+#: Basic_api.xml:33
+#, no-c-format
+msgid ""
+"The <literal>TreeCache</literal> has 4 nodes \"a\", \"b\", \"c\" and \"d\". "
+"Nodes \"/a/b/c\" has values \"name\" associated with \"Ben\" in its map, and "
+"node \"/a/b/c/d\" has values \"uid\" and 322649."
msgstr ""
-#: ./Basic_api.xml:53(para)
-msgid "Each node can be retrieved by its absolute name (e.g. \"/a/b/c\") or by navigating from parent to children (e.g. navigate from \"a\" to \"b\", then from \"b\" to \"c\")."
+#. Tag: para
+#: Basic_api.xml:36
+#, no-c-format
+msgid ""
+"Each node can be retrieved by its absolute name (e.g. \"/a/b/c\") or by "
+"navigating from parent to children (e.g. navigate from \"a\" to \"b\", then "
+"from \"b\" to \"c\")."
msgstr ""
-#: ./Basic_api.xml:56(para)
-msgid "The next method in the example gets the value associated with key=\"uid\" in node \"/a/b/c/d\", which is the integer 322649."
+#. Tag: para
+#: Basic_api.xml:39
+#, no-c-format
+msgid ""
+"The next method in the example gets the value associated with key=\"uid\" in "
+"node \"/a/b/c/d\", which is the integer 322649."
msgstr ""
-#: ./Basic_api.xml:59(para)
-msgid "The remove() method then removes node \"/a/b\" and all subnodes recursively from the cache. In this case, nodes \"/a/b/c/d\", \"/a/b/c\" and \"/a/b\" will be removed, leaving only \"/a\"."
+#. Tag: para
+#: Basic_api.xml:42
+#, no-c-format
+msgid ""
+"The remove() method then removes node \"/a/b\" and all subnodes recursively "
+"from the cache. In this case, nodes \"/a/b/c/d\", \"/a/b/c\" and \"/a/b\" "
+"will be removed, leaving only \"/a\"."
msgstr ""
-#: ./Basic_api.xml:62(para)
-msgid "Finally, the <literal>TreeCache</literal> is stopped. This will cause it to leave the cluster, and every node in the cluster will be notified. Note that <literal>TreeCache</literal> can be stopped and started again. When it is stopped, all contents will be deleted. And when it is restarted, if it joins a cache group, the state will be replicated initially. So potentially you can recreate the contents."
+#. Tag: para
+#: Basic_api.xml:45
+#, no-c-format
+msgid ""
+"Finally, the <literal>TreeCache</literal> is stopped. This will cause it to "
+"leave the cluster, and every node in the cluster will be notified. Note that "
+"<literal>TreeCache</literal> can be stopped and started again. When it is "
+"stopped, all contents will be deleted. And when it is restarted, if it joins "
+"a cache group, the state will be replicated initially. So potentially you "
+"can recreate the contents."
msgstr ""
-#: ./Basic_api.xml:65(para)
-msgid "In the sample, replication was enabled, which caused the 2 put() and the 1 remove() methods to replicated their changes to all nodes in the cluster. The get() method was executed on the local cache only."
+#. Tag: para
+#: Basic_api.xml:48
+#, no-c-format
+msgid ""
+"In the sample, replication was enabled, which caused the 2 put() and the 1 "
+"remove() methods to replicated their changes to all nodes in the cluster. "
+"The get() method was executed on the local cache only."
msgstr ""
-#: ./Basic_api.xml:68(para)
-msgid "Keys into the cache can be either strings separated by slashes ('/'), e.g. \"/a/b/c\", or they can be fully qualified names Fqns . An Fqn is essentially a list of Objects that need to implement hashCode() and equals(). All strings are actually transformed into Fqns internally. Fqns are more efficient than strings, for example:"
+#. Tag: para
+#: Basic_api.xml:51
+#, no-c-format
+msgid ""
+"Keys into the cache can be either strings separated by slashes ('/'), e.g. "
+"\"/a/b/c\", or they can be fully qualified names Fqns . An Fqn is "
+"essentially a list of Objects that need to implement hashCode() and equals"
+"(). All strings are actually transformed into Fqns internally. Fqns are more "
+"efficient than strings, for example:"
msgstr ""
-#: ./Basic_api.xml:71(programlisting)
-#, no-wrap
-msgid "String n1 = \"/300/322649\";\nFqn n2 = new Fqn(new Object{new Integer(300), new Integer(322649)});\n"
+#. Tag: programlisting
+#: Basic_api.xml:54
+#, no-c-format
+msgid ""
+"String n1 = \"/300/322649\";\n"
+"Fqn n2 = new Fqn(new Object{new Integer(300), new Integer(322649)});"
msgstr ""
-#: ./Basic_api.xml:74(para)
-msgid "In this example, we want to access a node that has information for employee with id=322649 in department with id=300. The string version needs two map lookups on Strings, whereas the Fqn version needs two map lookups on Integers. In a large hashtable, the hashCode() method for String may have collisions, leading to actual string comparisons. Also, clients of the cache may already have identifiers for their objects in Object form, and don't want to transform between Object and Strings, preventing unnecessary copying."
+#. Tag: para
+#: Basic_api.xml:55
+#, no-c-format
+msgid ""
+"In this example, we want to access a node that has information for employee "
+"with id=322649 in department with id=300. The string version needs two map "
+"lookups on Strings, whereas the Fqn version needs two map lookups on "
+"Integers. In a large hashtable, the hashCode() method for String may have "
+"collisions, leading to actual string comparisons. Also, clients of the cache "
+"may already have identifiers for their objects in Object form, and don't "
+"want to transform between Object and Strings, preventing unnecessary copying."
msgstr ""
-#: ./Basic_api.xml:77(para)
-msgid "Note that the modification methods are put() and remove(). The only get method is get()."
+#. Tag: para
+#: Basic_api.xml:58
+#, no-c-format
+msgid ""
+"Note that the modification methods are put() and remove(). The only get "
+"method is get()."
msgstr ""
-#: ./Basic_api.xml:81(para)
-msgid "Plus their equivalent helper methods taking a String as node name."
+#. Tag: para
+#: Basic_api.xml:61
+#, no-c-format
+msgid ""
+"There are 2 put() methods<footnote><para> Plus their equivalent helper "
+"methods taking a String as node name. </para> </footnote> : <literal>put(Fqn "
+"node, Object key, Object key)</literal> and <literal>put(Fqn node, Map "
+"values)</literal>. The former takes the node name, creates it if it doesn't "
+"yet exist, and put the key and value into the node's map, returning the "
+"previous value. The latter takes a map of keys and values and adds them to "
+"the node's map, overwriting existing keys and values. Content that is not in "
+"the new map remains in the node's map."
msgstr ""
-#: ./Basic_api.xml:80(para)
-msgid "There are 2 put() methods<placeholder-1/> : <literal>put(Fqn node, Object key, Object key)</literal> and <literal>put(Fqn node, Map values)</literal>. The former takes the node name, creates it if it doesn't yet exist, and put the key and value into the node's map, returning the previous value. The latter takes a map of keys and values and adds them to the node's map, overwriting existing keys and values. Content that is not in the new map remains in the node's map."
+#. Tag: para
+#: Basic_api.xml:67
+#, no-c-format
+msgid ""
+"There are 3 remove() methods: <literal>remove(Fqn node, Object key)</"
+"literal>, <literal>remove(Fqn node)</literal> and <literal>removeData(Fqn "
+"node)</literal>. The first removes the given key from the node. The second "
+"removes the entire node and all subnodes, and the third removes all elements "
+"from the given node's map."
msgstr ""
-#: ./Basic_api.xml:86(para)
-msgid "There are 3 remove() methods: <literal>remove(Fqn node, Object key)</literal>, <literal>remove(Fqn node)</literal> and <literal>removeData(Fqn node)</literal>. The first removes the given key from the node. The second removes the entire node and all subnodes, and the third removes all elements from the given node's map."
+#. Tag: para
+#: Basic_api.xml:70
+#, no-c-format
+msgid ""
+"The get methods are: <literal>get(Fqn node)</literal> and <literal>get(Fqn "
+"node, Object key)</literal>. The former returns a Node<footnote><para> This "
+"is mainly used internally, and we may decide to remove public access to the "
+"Node in a future release. </para> </footnote> object, allowing for direct "
+"navigation, the latter returns the value for the given key for a node."
msgstr ""
-#: ./Basic_api.xml:90(para)
-msgid "This is mainly used internally, and we may decide to remove public access to the Node in a future release."
+#. Tag: para
+#: Basic_api.xml:76
+#, no-c-format
+msgid ""
+"Also, the <literal>TreeCache</literal> has a number of getters and setters. "
+"Since the API may change at any time, we recommend the Javadoc for up-to-"
+"date information."
msgstr ""
-
-#: ./Basic_api.xml:89(para)
-msgid "The get methods are: <literal>get(Fqn node)</literal> and <literal>get(Fqn node, Object key)</literal>. The former returns a Node<placeholder-1/> object, allowing for direct navigation, the latter returns the value for the given key for a node."
-msgstr ""
-
-#: ./Basic_api.xml:95(para)
-msgid "Also, the <literal>TreeCache</literal> has a number of getters and setters. Since the API may change at any time, we recommend the Javadoc for up-to-date information."
-msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Basic_api.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Book_Info.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Book_Info.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Book_Info.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,52 +1,40 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:26-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Book_Info.xml:22(None)
-msgid "@@image: 'Common_Content/images/rhlogo-chapter-title.png'; md5=THIS FILE DOESN'T EXIST"
+#. Tag: title
+#: Book_Info.xml:5
+#, no-c-format
+msgid "JBoss Cache Tree Cache Guide CP06"
msgstr ""
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Book_Info.xml:29(None)
-msgid "@@image: 'Common_Content/images/rhlogo-title.png'; md5=THIS FILE DOESN'T EXIST"
+#. Tag: subtitle
+#: Book_Info.xml:6
+#, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 6"
msgstr ""
-#: ./Book_Info.xml:10(title)
-msgid "JBoss Cache Tree Cache"
-msgstr ""
-
-#: ./Book_Info.xml:11(subtitle)
-msgid "A Structured, Replicated, Transactional Cache"
-msgstr ""
-
-#: ./Book_Info.xml:12(issuenum)
-msgid "1.4.1 \"Cayenne\""
-msgstr ""
-
-#: ./Book_Info.xml:13(productnumber)
-msgid "0"
-msgstr ""
-
-#: ./Book_Info.xml:15(para)
+#. Tag: para
+#: Book_Info.xml:12
+#, no-c-format
msgid "This book is about the JBoss Cache Tree Cache."
msgstr ""
-#: ./Book_Info.xml:19(isbn)
-msgid "N/A"
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Book_Info.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Cache_loaders.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Cache_loaders.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Cache_loaders.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,599 +1,1772 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:26-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Cache_loaders.xml:457(None)
-msgid "@@image: 'images/SharedCacheLoader.png'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Cache_loaders.xml:480(None)
-msgid "@@image: 'images/OnlyOneCacheLoader.png'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Cache_loaders.xml:495(None)
-msgid "@@image: 'images/LocalCacheLoader.png'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-
-#: ./Cache_loaders.xml:10(title)
+#. Tag: title
+#: Cache_loaders.xml:5
+#, no-c-format
msgid "Cache Loaders"
msgstr ""
-#: ./Cache_loaders.xml:14(para)
-msgid "Whenever a cache element is accessed, and that element is not in the cache (e.g. due to eviction or due to server restart), then the cache loader transparently loads the element into the cache if found in the backend store."
+#. Tag: para
+#: Cache_loaders.xml:6
+#, no-c-format
+msgid ""
+"JBoss Cache can use a <emphasis>cache loader</emphasis> to back up the in-"
+"memory cache to a backend datastore. If JBoss Cache is configured with a "
+"cache loader, then the following features are provided:"
msgstr ""
-#: ./Cache_loaders.xml:17(para)
-msgid "Whenever an element is modified, added or removed, then that modification is persisted in the backend store via the cache loader. If transactions are used, all modifications created within a transaction are persisted. To this end, the cache loader takes part in the two phase commit protocol run by the transaction manager."
+#. Tag: para
+#: Cache_loaders.xml:9
+#, no-c-format
+msgid ""
+"Whenever a cache element is accessed, and that element is not in the cache "
+"(e.g. due to eviction or due to server restart), then the cache loader "
+"transparently loads the element into the cache if found in the backend store."
msgstr ""
-#: ./Cache_loaders.xml:11(para)
-msgid "JBoss Cache can use a <emphasis>cache loader</emphasis> to back up the in-memory cache to a backend datastore. If JBoss Cache is configured with a cache loader, then the following features are provided: <placeholder-1/>"
+#. Tag: para
+#: Cache_loaders.xml:12
+#, no-c-format
+msgid ""
+"Whenever an element is modified, added or removed, then that modification is "
+"persisted in the backend store via the cache loader. If transactions are "
+"used, all modifications created within a transaction are persisted. To this "
+"end, the cache loader takes part in the two phase commit protocol run by the "
+"transaction manager."
msgstr ""
-#: ./Cache_loaders.xml:21(para)
-msgid "Currently, the cache loader API looks similar to the TreeCache API. In the future, they will both implement the <emphasis>same</emphasis> interface. The goal is to be able to form hierarchical cache topologies, where one cache can delegate to another, which in turn may delegate to yet another cache."
+#. Tag: para
+#: Cache_loaders.xml:16
+#, no-c-format
+msgid ""
+"Currently, the cache loader API looks similar to the TreeCache API. In the "
+"future, they will both implement the <emphasis>same</emphasis> interface. "
+"The goal is to be able to form hierarchical cache topologies, where one "
+"cache can delegate to another, which in turn may delegate to yet another "
+"cache."
msgstr ""
-#: ./Cache_loaders.xml:24(para)
-msgid "As of JBossCache 1.3.0, you can now define several cache loaders, in a chain. 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. See the configuration section below for details."
+#. Tag: para
+#: Cache_loaders.xml:19
+#, no-c-format
+msgid ""
+"As of JBossCache 1.3.0, you can now define several cache loaders, in a "
+"chain. 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. See the configuration section below for details."
msgstr ""
-#: ./Cache_loaders.xml:27(para)
-msgid "The cache loader interface is defined in org.jboss.cache.loader.CacheLoader as follows (edited for brevity):"
+#. Tag: para
+#: Cache_loaders.xml:22
+#, no-c-format
+msgid ""
+"The cache loader interface is defined in org.jboss.cache.loader.CacheLoader "
+"as follows (edited for brevity):"
msgstr ""
-#: ./Cache_loaders.xml:30(programlisting)
-#, no-wrap
-msgid "public interface CacheLoader extends Service {\n\n /**\n * Sets the configuration. Will be called before {@link #create()} and {@link #start()}\n * @param props A set of properties specific to a given CacheLoader\n */\n void setConfig(Properties props);\n\n void setCache(TreeCache c);\n\n\n /**\n * Returns a list of children names, all names are <em>relative</em>. Returns null if \n * the parent node is not found.\n * The returned set must not be modified, e.g. use Collections.unmodifiableSet(s) to \n * return the result\n * @param fqn The FQN of the parent\n * @return Set<String>. A list of children. Returns null if no children nodes are present,\n * or the parent is not present\n */\n Set getChildrenNames(Fqn fqn) throws Exception;\n\n\n /**\n * Returns the value for a given key. Returns null if the node doesn't exist, or the value \n * is not bound\n */\n Object get(Fqn name, Object key) thr!
ows Exception;\n\n\n /**\n * Returns all keys and values from the persistent store, given a fully qualified name.\n * \n * NOTE that the expected return value of this method has changed from JBossCache 1.2.x \n * and before! This will affect cache loaders written prior to JBossCache 1.3.0 and such \n * implementations should be checked for compliance with the behaviour expected.\n * \n * @param name\n * @return Map<Object,Object> of keys and values for the given node. Returns null if the \n * node is not found. If the node is found but has no attributes, this method returns \n * an empty Map.\n * @throws Exception\n */\n Map get(Fqn name) throws Exception;\n\n\n\n /**\n * Checks whether the CacheLoader has a node with Fqn\n * @return True if node exists, false otherwise\n */\n boolean exists(Fqn name) throws Exception;\n\n\n /**\n * Inserts key and value into the attributes hashmap of the given node. If the !
node does \n * not exist, all parent nodes from the root down are c
reated automatically\n */\n void put(Fqn name, Object key, Object value) throws Exception;\n\n /**\n * Inserts all elements of attributes into the attributes hashmap of the given node, \n * overwriting existing attributes, but not clearing the existing hashmap before\n * insertion (making it a union of existing and new attributes)\n * If the node does not exist, all parent nodes from the root down are created \n * automatically\n * @param name The fully qualified name of the node\n * @param attributes A Map of attributes. Can be null\n */\n void put(Fqn name, Map attributes) throws Exception;\n\n /**\n * Inserts all modifications to the backend store. Overwrite whatever is already in\n * the datastore.\n * @param modifications A List<Modification> of modifications\n * @throws Exception\n */\n void put(List modifications) throws Exception;\n\n /** Removes the given key and value from the attributes of the given node.!
\n * No-op if node doesn't exist */\n void remove(Fqn name, Object key) throws Exception;\n\n /**\n * Removes the given node. If the node is the root of a subtree, this will recursively \n * remove all subnodes, depth-first\n */\n void remove(Fqn name) throws Exception;\n\n /** Removes all attributes from a given node, but doesn't delete the node itself */\n void removeData(Fqn name) throws Exception;\n\n\n /**\n * Prepare the modifications. For example, for a DB-based CacheLoader:\n * \n * Create a local (JDBC) transaction\n * Associate the local transaction with tx (tx is the key)\n * Execute the coresponding SQL statements against the DB (statements derived from \n *modifications)\n * \n * For non-transactional CacheLoader (e.g. file-based), this could be a null operation\n * @param tx The transaction, just used as a hashmap key\n * @param modifications List<Modification>, a list of all modifications !
within the given \n * transaction\n * @param one_phase Persi
st immediately and (for example) commit the local JDBC \n * transaction as well. When true, we won't get a {@link #commit(Object)} or \n * {@link #rollback(Object)} method call later\n */\n void prepare(Object tx, List modifications, boolean one_phase) throws Exception;\n\n /**\n * Commit the transaction. A DB-based CacheLoader would look up the local JDBC transaction \n * associated with tx and commit that transaction\n * Non-transactional CacheLoaders could simply write the data that was previously saved \n * transiently under the given tx key, to (for example) a file system (note this only holds if \n * the previous prepare() did not define one_phase=true\n */\n void commit(Object tx) throws Exception;\n\n /**\n * Roll the transaction back. A DB-based CacheLoader would look up the local JDBC \n * transaction associated with tx and roll back that transaction\n */\n void rollback(Object tx);\n\n /**\n * Fetch the entire sta!
te for this cache from secondary storage (disk, DB) and return\n * it as a byte buffer. This is for initialization of a new cache from a remote cache. \n * The new cache would then call storeEntireState()\n * todo: define binary format for exchanging state\n */\n byte[] loadEntireState() throws Exception;\n\n /** Store the given state in secondary storage. Overwrite whatever is currently in storage */\n void storeEntireState(byte[] state) throws Exception;\n}\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:25
+#, no-c-format
+msgid ""
+"public interface CacheLoader extends Service {\n"
+"\n"
+" /**\n"
+" * Sets the configuration. Will be called before {@link #create()} and "
+"{@link #start()}\n"
+" * @param props A set of properties specific to a given CacheLoader\n"
+" */\n"
+" void setConfig(Properties props);\n"
+"\n"
+" void setCache(TreeCache c);\n"
+"\n"
+"\n"
+" /**\n"
+" * Returns a list of children names, all names are <em>relative</"
+"em>. Returns null if \n"
+" * the parent node is not found.\n"
+" * The returned set must not be modified, e.g. use Collections."
+"unmodifiableSet(s) to \n"
+" * return the result\n"
+" * @param fqn The FQN of the parent\n"
+" * @return Set<String>. A list of children. Returns null if no "
+"children nodes are present,\n"
+" * or the parent is not present\n"
+" */\n"
+" Set getChildrenNames(Fqn fqn) throws Exception;\n"
+"\n"
+"\n"
+" /**\n"
+" * Returns the value for a given key. Returns null if the node doesn't "
+"exist, or the value \n"
+" * is not bound\n"
+" */\n"
+" Object get(Fqn name, Object key) throws Exception;\n"
+"\n"
+"\n"
+" /**\n"
+" * Returns all keys and values from the persistent store, given a fully "
+"qualified name.\n"
+" * \n"
+" * NOTE that the expected return value of this method has changed from "
+"JBossCache 1.2.x \n"
+" * and before! This will affect cache loaders written prior to "
+"JBossCache 1.3.0 and such \n"
+" * implementations should be checked for compliance with the behaviour "
+"expected.\n"
+" * \n"
+" * @param name\n"
+" * @return Map<Object,Object> of keys and values for the given "
+"node. Returns null if the \n"
+" * node is not found. If the node is found but has no attributes, this "
+"method returns \n"
+" * an empty Map.\n"
+" * @throws Exception\n"
+" */\n"
+" Map get(Fqn name) throws Exception;\n"
+"\n"
+"\n"
+"\n"
+" /**\n"
+" * Checks whether the CacheLoader has a node with Fqn\n"
+" * @return True if node exists, false otherwise\n"
+" */\n"
+" boolean exists(Fqn name) throws Exception;\n"
+"\n"
+"\n"
+" /**\n"
+" * Inserts key and value into the attributes hashmap of the given node. "
+"If the node does \n"
+" * not exist, all parent nodes from the root down are created "
+"automatically\n"
+" */\n"
+" void put(Fqn name, Object key, Object value) throws Exception;\n"
+"\n"
+" /**\n"
+" * Inserts all elements of attributes into the attributes hashmap of the "
+"given node, \n"
+" * overwriting existing attributes, but not clearing the existing hashmap "
+"before\n"
+" * insertion (making it a union of existing and new attributes)\n"
+" * If the node does not exist, all parent nodes from the root down are "
+"created \n"
+" * automatically\n"
+" * @param name The fully qualified name of the node\n"
+" * @param attributes A Map of attributes. Can be null\n"
+" */\n"
+" void put(Fqn name, Map attributes) throws Exception;\n"
+"\n"
+" /**\n"
+" * Inserts all modifications to the backend store. Overwrite whatever is "
+"already in\n"
+" * the datastore.\n"
+" * @param modifications A List<Modification> of modifications\n"
+" * @throws Exception\n"
+" */\n"
+" void put(List modifications) throws Exception;\n"
+"\n"
+" /** Removes the given key and value from the attributes of the given "
+"node. \n"
+" * No-op if node doesn't exist */\n"
+" void remove(Fqn name, Object key) throws Exception;\n"
+"\n"
+" /**\n"
+" * Removes the given node. If the node is the root of a subtree, this "
+"will recursively \n"
+" * remove all subnodes, depth-first\n"
+" */\n"
+" void remove(Fqn name) throws Exception;\n"
+"\n"
+" /** Removes all attributes from a given node, but doesn't delete the node "
+"itself */\n"
+" void removeData(Fqn name) throws Exception;\n"
+"\n"
+"\n"
+" /**\n"
+" * Prepare the modifications. For example, for a DB-based CacheLoader:\n"
+" * \n"
+" * Create a local (JDBC) transaction\n"
+" * Associate the local transaction with tx (tx is the key)\n"
+" * Execute the coresponding SQL statements against the DB (statements "
+"derived from \n"
+" *modifications)\n"
+" * \n"
+" * For non-transactional CacheLoader (e.g. file-based), this could be a "
+"null operation\n"
+" * @param tx The transaction, just used as a hashmap key\n"
+" * @param modifications List<Modification>, a list of all "
+"modifications within the given \n"
+" * transaction\n"
+" * @param one_phase Persist immediately and (for example) commit the "
+"local JDBC \n"
+" * transaction as well. When true, we won't get a {@link #commit(Object)} "
+"or \n"
+" * {@link #rollback(Object)} method call later\n"
+" */\n"
+" void prepare(Object tx, List modifications, boolean one_phase) throws "
+"Exception;\n"
+"\n"
+" /**\n"
+" * Commit the transaction. A DB-based CacheLoader would look up the local "
+"JDBC transaction \n"
+" * associated with tx and commit that transaction\n"
+" * Non-transactional CacheLoaders could simply write the data that was "
+"previously saved \n"
+" * transiently under the given tx key, to (for example) a file system "
+"(note this only holds if \n"
+" * the previous prepare() did not define one_phase=true\n"
+" */\n"
+" void commit(Object tx) throws Exception;\n"
+"\n"
+" /**\n"
+" * Roll the transaction back. A DB-based CacheLoader would look up the "
+"local JDBC \n"
+" * transaction associated with tx and roll back that transaction\n"
+" */\n"
+" void rollback(Object tx);\n"
+"\n"
+" /**\n"
+" * Fetch the entire state for this cache from secondary storage (disk, "
+"DB) and return\n"
+" * it as a byte buffer. This is for initialization of a new cache from a "
+"remote cache. \n"
+" * The new cache would then call storeEntireState()\n"
+" * todo: define binary format for exchanging state\n"
+" */\n"
+" byte[] loadEntireState() throws Exception;\n"
+"\n"
+" /** Store the given state in secondary storage. Overwrite whatever is "
+"currently in storage */\n"
+" void storeEntireState(byte[] state) throws Exception;\n"
+"}"
msgstr ""
-#: ./Cache_loaders.xml:168(para)
-msgid "<emphasis role=\"bold\">NOTE:</emphasis> the contract defined by the CacheLoader interface has changed from JBoss Cache 1.3.0 onwards, specifically with the <literal>get(Fqn fqn)</literal> method. Special care must be taken with custom CacheLoader implementations to ensure this new contract is still adhered to. See the javadoc above on this method for details, or visit <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheCacheLoaders\">this wiki page</ulink> for more discussion on this."
+#. Tag: para
+#: Cache_loaders.xml:26
+#, no-c-format
+msgid ""
+"<emphasis role=\"bold\">NOTE:</emphasis> the contract defined by the "
+"CacheLoader interface has changed from JBoss Cache 1.3.0 onwards, "
+"specifically with the <literal>get(Fqn fqn)</literal> method. Special care "
+"must be taken with custom CacheLoader implementations to ensure this new "
+"contract is still adhered to. See the javadoc above on this method for "
+"details, or visit <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?"
+"page=JBossCacheCacheLoaders\">this wiki page</ulink> for more discussion on "
+"this."
msgstr ""
-#: ./Cache_loaders.xml:171(para)
-msgid "CacheLoader implementations that need to support partial state transfer should also implement the subinterface org.jboss.cache.loader.ExtendedCacheLoader:"
+#. Tag: para
+#: Cache_loaders.xml:29
+#, no-c-format
+msgid ""
+"CacheLoader implementations that need to support partial state transfer "
+"should also implement the subinterface org.jboss.cache.loader."
+"ExtendedCacheLoader:"
msgstr ""
-#: ./Cache_loaders.xml:174(programlisting)
-#, no-wrap
-msgid "public interface ExtendedCacheLoader extends CacheLoader\n{\n /**\n * Fetch a portion of the state for this cache from secondary storage \n * (disk, DB) and return it as a byte buffer.\n * This is for activation of a portion of new cache from a remote cache. \n * The new cache would then call {@link #storeState(byte[], Fqn)}.\n * \n * @param subtree Fqn naming the root (i.e. highest level parent) node of\n * the subtree for which state is requested.\n * \n * @see org.jboss.cache.TreeCache#activateRegion(String)\n */\n byte[] loadState(Fqn subtree) throws Exception;\n \n /**\n * Store the given portion of the cache tree's state in secondary storage. \n * Overwrite whatever is currently in secondary storage. If the transferred \n * state has Fqns equal to or children of parameter <code>subtree</code>, \n * then no special behavior is required. Otherwise, ensure that\n * the state is in!
tegrated under the given 'subtree'. Typically\n * in the latter case 'subtree' would be the Fqn of the buddy \n * backup region for a buddy group; e.g.\n * \n * If the the transferred state had Fqns starting with \"/a\" and\n * 'subtree' was \"/_BUDDY_BACKUP_/192.168.1.2:5555\" then the\n * state should be stored in the local persistent store under\n * \"/_BUDDY_BACKUP_/192.168.1.2:5555/a\"\n * \n * @param state the state to store\n * @param subtree Fqn naming the root (i.e. highest level parent) node of\n * the subtree included in 'state'. If the Fqns \n * of the data included in 'state' are not \n * already children of 'subtree', then their\n * Fqns should be altered to make them children of \n * 'subtree' before they are persisted.\n */ \n void storeState(byte[] state, Fqn subtree) throws Exception;\n \n /**\n * Sets the {@link RegionM!
anager} this object should use to manage \n * marshalling/unmarshal
ling of different regions using different\n * classloaders.\n *\n * NOTE: This method is only intended to be used by the TreeCache instance \n * this cache loader is associated with.\n * \n * @param manager the region manager to use, or <code>null</code>.\n */\n void setRegionManager(RegionManager manager);\n\n}\n \n"
+#. Tag: programlisting
+#: Cache_loaders.xml:32
+#, no-c-format
+msgid ""
+"public interface ExtendedCacheLoader extends CacheLoader\n"
+"{\n"
+" /**\n"
+" * Fetch a portion of the state for this cache from secondary storage \n"
+" * (disk, DB) and return it as a byte buffer.\n"
+" * This is for activation of a portion of new cache from a remote "
+"cache. \n"
+" * The new cache would then call {@link #storeState(byte[], Fqn)}.\n"
+" * \n"
+" * @param subtree Fqn naming the root (i.e. highest level parent) node "
+"of\n"
+" * the subtree for which state is requested.\n"
+" * \n"
+" * @see org.jboss.cache.TreeCache#activateRegion(String)\n"
+" */\n"
+" byte[] loadState(Fqn subtree) throws Exception;\n"
+" \n"
+" /**\n"
+" * Store the given portion of the cache tree's state in secondary "
+"storage. \n"
+" * Overwrite whatever is currently in secondary storage. If the "
+"transferred \n"
+" * state has Fqns equal to or children of parameter <code>subtree</"
+"code>, \n"
+" * then no special behavior is required. Otherwise, ensure that\n"
+" * the state is integrated under the given 'subtree'. Typically\n"
+" * in the latter case 'subtree' would be the Fqn of the buddy \n"
+" * backup region for a buddy group; e.g.\n"
+" * \n"
+" * If the the transferred state had Fqns starting with \"/a\" and\n"
+" * 'subtree' was \"/_BUDDY_BACKUP_/192.168.1.2:5555\" then the\n"
+" * state should be stored in the local persistent store under\n"
+" * \"/_BUDDY_BACKUP_/192.168.1.2:5555/a\"\n"
+" * \n"
+" * @param state the state to store\n"
+" * @param subtree Fqn naming the root (i.e. highest level parent) node "
+"of\n"
+" * the subtree included in 'state'. If the Fqns \n"
+" * of the data included in 'state' are not \n"
+" * already children of 'subtree', then their\n"
+" * Fqns should be altered to make them children of \n"
+" * 'subtree' before they are persisted.\n"
+" */ \n"
+" void storeState(byte[] state, Fqn subtree) throws Exception;\n"
+" \n"
+" /**\n"
+" * Sets the {@link RegionManager} this object should use to manage \n"
+" * marshalling/unmarshalling of different regions using different\n"
+" * classloaders.\n"
+" *\n"
+" * NOTE: This method is only intended to be used by the TreeCache "
+"instance \n"
+" * this cache loader is associated with.\n"
+" * \n"
+" * @param manager the region manager to use, or <code>null</code>.\n"
+" */\n"
+" void setRegionManager(RegionManager manager);\n"
+"\n"
+"}"
msgstr ""
-#: ./Cache_loaders.xml:228(para)
-msgid "<emphasis role=\"bold\">NOTE:</emphasis> If a cache loader is used along with buddy replication, the cache loader must implement <literal>ExtendedCacheLoader</literal> unless its <literal>FetchPersistentState</literal> property is set to false."
+#. Tag: para
+#: Cache_loaders.xml:33
+#, no-c-format
+msgid ""
+"<emphasis role=\"bold\">NOTE:</emphasis> If a cache loader is used along "
+"with buddy replication, the cache loader must implement "
+"<literal>ExtendedCacheLoader</literal> unless its "
+"<literal>FetchPersistentState</literal> property is set to false."
msgstr ""
-#: ./Cache_loaders.xml:231(para)
-msgid "<emphasis role=\"bold\">NOTE:</emphasis> the contract defined by the <literal>ExtendedCacheLoader</literal> interface has changed from JBoss Cache 1.4.0 onwards, specifically with the requirement that data passed to <literal>storeState</literal> method be integrated under the given subtree, even if that data didn't originate in that subtree. This behavior is necessary to properly support buddy replication. Special care must be taken with custom ExtendedCacheLoader implementations to ensure this new contract is still adhered to."
+#. Tag: para
+#: Cache_loaders.xml:36
+#, no-c-format
+msgid ""
+"<emphasis role=\"bold\">NOTE:</emphasis> the contract defined by the "
+"<literal>ExtendedCacheLoader</literal> interface has changed from JBoss "
+"Cache 1.4.0 onwards, specifically with the requirement that data passed to "
+"<literal>storeState</literal> method be integrated under the given subtree, "
+"even if that data didn't originate in that subtree. This behavior is "
+"necessary to properly support buddy replication. Special care must be taken "
+"with custom ExtendedCacheLoader implementations to ensure this new contract "
+"is still adhered to."
msgstr ""
-#: ./Cache_loaders.xml:235(title)
+#. Tag: title
+#: Cache_loaders.xml:40
+#, no-c-format
msgid "The CacheLoader Interface"
msgstr ""
-#: ./Cache_loaders.xml:236(para)
-msgid "The interaction between JBoss Cache and a CacheLoader implementation is as follows. When <literal>CacheLoaderConfiguration</literal> (see below) is non-null, an instance of each configured <literal>cacheloader</literal> is created when the cache is created. Since <literal>CacheLoader</literal> extends <literal>Service</literal>,"
+#. Tag: para
+#: Cache_loaders.xml:41
+#, no-c-format
+msgid ""
+"The interaction between JBoss Cache and a CacheLoader implementation is as "
+"follows. When <literal>CacheLoaderConfiguration</literal> (see below) is non-"
+"null, an instance of each configured <literal>cacheloader</literal> is "
+"created when the cache is created. Since <literal>CacheLoader</literal> "
+"extends <literal>Service</literal>,"
msgstr ""
-#: ./Cache_loaders.xml:239(programlisting)
-#, no-wrap
-msgid "public interface Service {\n void create() throws Exception;\n\n void start() throws Exception;\n\n void stop();\n\n void destroy();\n}\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:44
+#, no-c-format
+msgid ""
+"public interface Service {\n"
+" void create() throws Exception;\n"
+"\n"
+" void start() throws Exception;\n"
+"\n"
+" void stop();\n"
+"\n"
+" void destroy();\n"
+"}"
msgstr ""
-#: ./Cache_loaders.xml:249(para)
-msgid "<literal>CacheLoader.create()</literal> and <literal>CacheLoader.start()</literal> are called when the cache is started. Correspondingly, <literal>stop()</literal> and <literal>destroy()</literal> are called when the cache is stopped."
+#. Tag: para
+#: Cache_loaders.xml:45
+#, no-c-format
+msgid ""
+"<literal>CacheLoader.create()</literal> and <literal>CacheLoader.start()</"
+"literal> are called when the cache is started. Correspondingly, <literal>stop"
+"()</literal> and <literal>destroy()</literal> are called when the cache is "
+"stopped."
msgstr ""
-#: ./Cache_loaders.xml:252(para)
-msgid "Next, <literal>setConfig()</literal> and <literal>setCache()</literal> are called. The latter can be used to store a reference to the cache, the former is used to configure this instance of the CacheLoader. For example, here a database CacheLoader could establish a connection to the database."
+#. Tag: para
+#: Cache_loaders.xml:48
+#, no-c-format
+msgid ""
+"Next, <literal>setConfig()</literal> and <literal>setCache()</literal> are "
+"called. The latter can be used to store a reference to the cache, the former "
+"is used to configure this instance of the CacheLoader. For example, here a "
+"database CacheLoader could establish a connection to the database."
msgstr ""
-#: ./Cache_loaders.xml:255(para)
-msgid "The CacheLoader interface has a set of methods that are called when no transactions are used: <literal>get()</literal>, <literal>put()</literal>, <literal>remove()</literal> and <literal>removeData()</literal>: they get/set/remove the value immediately. These methods are described as javadoc comments in the above interface."
+#. Tag: para
+#: Cache_loaders.xml:51
+#, no-c-format
+msgid ""
+"The CacheLoader interface has a set of methods that are called when no "
+"transactions are used: <literal>get()</literal>, <literal>put()</literal>, "
+"<literal>remove()</literal> and <literal>removeData()</literal>: they get/"
+"set/remove the value immediately. These methods are described as javadoc "
+"comments in the above interface."
msgstr ""
-#: ./Cache_loaders.xml:258(para)
-msgid "Then there are three methods that are used with transactions: <literal>prepare()</literal>, <literal>commit()</literal> and <literal>rollback()</literal>. The <literal>prepare()</literal> method is called when a transaction is to be committed. It has a transaction object and a list of modfications as argument. The transaction object can be used as a key into a hashmap of transactions, where the values are the lists of modifications. Each modification list has a number of <literal>Modification</literal> elements, which represent the changes made to a cache for a given transaction. When <literal>prepare()</literal> returns successfully, then the CacheLoader <emphasis>must</emphasis> be able to commit (or rollback) the transaction successfully."
+#. Tag: para
+#: Cache_loaders.xml:54
+#, no-c-format
+msgid ""
+"Then there are three methods that are used with transactions: "
+"<literal>prepare()</literal>, <literal>commit()</literal> and "
+"<literal>rollback()</literal>. The <literal>prepare()</literal> method is "
+"called when a transaction is to be committed. It has a transaction object "
+"and a list of modfications as argument. The transaction object can be used "
+"as a key into a hashmap of transactions, where the values are the lists of "
+"modifications. Each modification list has a number of <literal>Modification</"
+"literal> elements, which represent the changes made to a cache for a given "
+"transaction. When <literal>prepare()</literal> returns successfully, then "
+"the CacheLoader <emphasis>must</emphasis> be able to commit (or rollback) "
+"the transaction successfully."
msgstr ""
-#: ./Cache_loaders.xml:261(para)
-msgid "Currently, the TreeCache takes care of calling prepare(), commit() and rollback() on the CacheLoaders at the right time. We intend to make both the TreeCache and the CacheLoaders XA resources, so that instead of calling those methods on a loader, the cache will only enlist the loader with the TransactionManager on the same transaction."
+#. Tag: para
+#: Cache_loaders.xml:57
+#, no-c-format
+msgid ""
+"Currently, the TreeCache takes care of calling prepare(), commit() and "
+"rollback() on the CacheLoaders at the right time. We intend to make both the "
+"TreeCache and the CacheLoaders XA resources, so that instead of calling "
+"those methods on a loader, the cache will only enlist the loader with the "
+"TransactionManager on the same transaction."
msgstr ""
-#: ./Cache_loaders.xml:264(para)
-msgid "The <literal>commit()</literal> method tells the CacheLoader to commit the transaction, and the <literal>rollback()</literal> method tells the CacheLoader to discard the changes associated with that transaction."
+#. Tag: para
+#: Cache_loaders.xml:60
+#, no-c-format
+msgid ""
+"The <literal>commit()</literal> method tells the CacheLoader to commit the "
+"transaction, and the <literal>rollback()</literal> method tells the "
+"CacheLoader to discard the changes associated with that transaction."
msgstr ""
-#: ./Cache_loaders.xml:267(para)
-msgid "The last two methods are <literal>loadEntireState()</literal> and <literal>storeEntireState()</literal>. The first method asks the CacheLoader to get the entire state the backend store manages and return it as a byte buffer, and the second tells a CacheLoader to replace its entire state with the byte buffer argument. These methods are used for scenarios where each JBossCache node in a cluster has its own local data store, e.g. a local DB, and - when a new node starts - we have to initialize its backend store with the contents of the backend store of an existing member. See below for deails."
+#. Tag: para
+#: Cache_loaders.xml:63
+#, no-c-format
+msgid ""
+"The last two methods are <literal>loadEntireState()</literal> and "
+"<literal>storeEntireState()</literal>. The first method asks the CacheLoader "
+"to get the entire state the backend store manages and return it as a byte "
+"buffer, and the second tells a CacheLoader to replace its entire state with "
+"the byte buffer argument. These methods are used for scenarios where each "
+"JBossCache node in a cluster has its own local data store, e.g. a local DB, "
+"and - when a new node starts - we have to initialize its backend store with "
+"the contents of the backend store of an existing member. See below for "
+"deails."
msgstr ""
-#: ./Cache_loaders.xml:270(para)
-msgid "The <literal>ExtendedCacheLoader</literal> methods are also related to state transfer. The <literal>loadState(Fqn)</literal> method is called when the cache is preparing a partial state transfer -- that is, the transfer of just the portion of the cache loader's state that is rooted in the given Fqn. The <literal>storeState(byte[], Fqn)</literal> method is then invoked on the cache loader of the node that is receiving the state transfer. Partial state transfers occur when the cache's <literal>activateRegion()</literal> API is used and during the formation of buddy groups if buddy replication is used."
+#. Tag: para
+#: Cache_loaders.xml:66
+#, no-c-format
+msgid ""
+"The <literal>ExtendedCacheLoader</literal> methods are also related to state "
+"transfer. The <literal>loadState(Fqn)</literal> method is called when the "
+"cache is preparing a partial state transfer -- that is, the transfer of just "
+"the portion of the cache loader's state that is rooted in the given Fqn. The "
+"<literal>storeState(byte[], Fqn)</literal> method is then invoked on the "
+"cache loader of the node that is receiving the state transfer. Partial state "
+"transfers occur when the cache's <literal>activateRegion()</literal> API is "
+"used and during the formation of buddy groups if buddy replication is used."
msgstr ""
-#: ./Cache_loaders.xml:276(title)
+#. Tag: title
+#: Cache_loaders.xml:72
+#, no-c-format
msgid "Configuration via XML"
msgstr ""
-#: ./Cache_loaders.xml:277(para)
+#. Tag: para
+#: Cache_loaders.xml:73
+#, no-c-format
msgid "The CacheLoader is configured as follows in the JBossCache XML file:"
msgstr ""
-#: ./Cache_loaders.xml:280(programlisting)
-#, no-wrap
-msgid " <!-- ==================================================================== -->\n <!-- Defines TreeCache configuration -->\n <!-- ==================================================================== -->\n\n <mbean code=\"org.jboss.cache.TreeCache\" name=\"jboss.cache:service=TreeCache\">\n\n <!-- New 1.3.x cache loader config block -->\n <attribute name=\"CacheLoaderConfiguration\">\n <config>\n <!-- if passivation is true, only the first cache loader is used; \n\t\tthe rest are ignored -->\n <passivation>false</passivation>\n <!-- comma delimited FQNs to preload -->\n <preload>/</preload>\n <!-- are the cache loaders shared in a cluster? -->\n <shared>false</shared>\n\n <!-- we can now have mul!
tiple cache loaders, which get chained -->\n <!-- the 'cacheloader' element may be repeated -->\n <cacheloader>\n <class>org.jboss.cache.loader.JDBCCacheLoader</class>\n <!-- same as the old CacheLoaderConfig attribute -->\n <properties>\n cache.jdbc.driver=com.mysql.jdbc.Driver\n cache.jdbc.url=jdbc:mysql://localhost:3306/jbossdb\n cache.jdbc.user=root\n cache.jdbc.password=\n </properties>\n <!-- whether the cache loader writes are asynchronous -->\n <async>false</async>\n <!-- only one cache loader in the chain may set fetchPersistentState \n\t\t to true.\n An exception is thrown if more than one cache loader sets this \n\t\t\tto !
true. -->\n <fetchPersistentState>true<
/fetchPersistentState>\n <!-- determines whether this cache loader ignores writes - defaults \n\t\t to false. -->\n <ignoreModifications>false</ignoreModifications>\n <!-- if set to true, purges the contents of this cache loader when \n\t\t the cache starts up.\n Defaults to false. -->\n <purgeOnStartup>false</purgeOnStartup>\n </cacheloader>\n\n </config>\n </attribute>\n\n </mbean>\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:76
+#, no-c-format
+msgid ""
+"<!-- ==================================================================== "
+"-->\n"
+" <!-- Defines TreeCache "
+"configuration -->\n"
+" <!-- "
+"==================================================================== -->\n"
+"\n"
+" <mbean code=\"org.jboss.cache.TreeCache\" name=\"jboss.cache:"
+"service=TreeCache\">\n"
+"\n"
+" <!-- New 1.3.x cache loader config block -->\n"
+" <attribute name=\"CacheLoaderConfiguration\">\n"
+" <config>\n"
+" <!-- if passivation is true, only the first cache loader "
+"is used; \n"
+" the rest are ignored -->\n"
+" <passivation>false</passivation>\n"
+" <!-- comma delimited FQNs to preload -->\n"
+" <preload>/</preload>\n"
+" <!-- are the cache loaders shared in a cluster? -->\n"
+" <shared>false</shared>\n"
+"\n"
+" <!-- we can now have multiple cache loaders, which get "
+"chained -->\n"
+" <!-- the 'cacheloader' element may be repeated -->\n"
+" <cacheloader>\n"
+" <class>org.jboss.cache.loader.JDBCCacheLoader</"
+"class>\n"
+" <!-- same as the old CacheLoaderConfig attribute --"
+">\n"
+" <properties>\n"
+" cache.jdbc.driver=com.mysql.jdbc.Driver\n"
+" cache.jdbc.url=jdbc:mysql://localhost:3306/jbossdb\n"
+" cache.jdbc.user=root\n"
+" cache.jdbc.password=\n"
+" </properties>\n"
+" <!-- whether the cache loader writes are asynchronous "
+"-->\n"
+" <async>false</async>\n"
+" <!-- only one cache loader in the chain may set "
+"fetchPersistentState \n"
+" to true.\n"
+" An exception is thrown if more than one cache loader "
+"sets this \n"
+" to true. -->\n"
+" <fetchPersistentState>true</"
+"fetchPersistentState>\n"
+" <!-- determines whether this cache loader ignores "
+"writes - defaults \n"
+" to false. -->\n"
+" <ignoreModifications>false</"
+"ignoreModifications>\n"
+" <!-- if set to true, purges the contents of this "
+"cache loader when \n"
+" the cache starts up.\n"
+" Defaults to false. -->\n"
+" <purgeOnStartup>false</purgeOnStartup>\n"
+" </cacheloader>\n"
+"\n"
+" </config>\n"
+" </attribute>\n"
+"\n"
+" </mbean>"
msgstr ""
-#: ./Cache_loaders.xml:329(para)
-msgid "<emphasis role=\"bold\">Note:</emphasis> In JBossCache releases prior to 1.3.0, the cache loader configuration block used to look like this. Note that this form is <emphasis role=\"deprecated\">DEPRECATED</emphasis> and you will have to replace your cache loader configuration with a block similar to the one above."
+#. Tag: para
+#: Cache_loaders.xml:77
+#, no-c-format
+msgid ""
+"<emphasis role=\"bold\">Note:</emphasis> In JBossCache releases prior to "
+"1.3.0, the cache loader configuration block used to look like this. Note "
+"that this form is <emphasis role=\"deprecated\">DEPRECATED</emphasis> and "
+"you will have to replace your cache loader configuration with a block "
+"similar to the one above."
msgstr ""
-#: ./Cache_loaders.xml:333(programlisting)
-#, no-wrap
-msgid " <!-- ==================================================================== -->\n <!-- Defines TreeCache configuration -->\n <!-- ==================================================================== -->\n\n <mbean code=\"org.jboss.cache.TreeCache\" name=\"jboss.cache:service=TreeCache\">\n <attribute name=\"CacheLoaderClass\">org.jboss.cache.loader.bdbje.BdbjeCacheLoader\n </attribute>\n <!-- attribute name=\"CacheLoaderClass\">org.jboss.cache.loader.FileCacheLoader\n </attribute -->\n <attribute name=\"CacheLoaderConfig\" replace=\"false\">\n location=c:\\\\tmp\\\\bdbje\n </attribute>\n <attribute name=\"CacheLoaderShared\">true</attribute>\n <attribute name=\"CacheLoaderPreload\">/</attribute>\n <attribute name=\"CacheLoaderFetchTransientState\">false</attribute>!
\n <attribute name=\"CacheLoaderFetchPersistentState\">true</attribute>\n <attribute name=\"CacheLoaderAsynchronous\">true</attribute>\n </mbean>\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:81
+#, no-c-format
+msgid ""
+"<!-- ==================================================================== "
+"-->\n"
+" <!-- Defines TreeCache "
+"configuration -->\n"
+" <!-- "
+"==================================================================== -->\n"
+"\n"
+" <mbean code=\"org.jboss.cache.TreeCache\" name=\"jboss.cache:"
+"service=TreeCache\">\n"
+" <attribute name=\"CacheLoaderClass\">org.jboss.cache.loader."
+"bdbje.BdbjeCacheLoader\n"
+" </attribute>\n"
+" <!-- attribute name=\"CacheLoaderClass\">org.jboss.cache.loader."
+"FileCacheLoader\n"
+" </attribute -->\n"
+" <attribute name=\"CacheLoaderConfig\" replace=\"false\">\n"
+" location=c:\\tmp\\bdbje\n"
+" </attribute>\n"
+" <attribute name=\"CacheLoaderShared\">true</attribute>\n"
+" <attribute name=\"CacheLoaderPreload\">/</attribute>\n"
+" <attribute name=\"CacheLoaderFetchTransientState\">false</"
+"attribute>\n"
+" <attribute name=\"CacheLoaderFetchPersistentState\">true</"
+"attribute>\n"
+" <attribute name=\"CacheLoaderAsynchronous\">true</"
+"attribute>\n"
+" </mbean>"
msgstr ""
-#: ./Cache_loaders.xml:353(para)
-msgid "The <literal>CacheLoaderClass</literal> attribute defines the class of the CacheLoader implementation. (Note that, because of a bug in the properties editor in JBoss, backslashes in variables for Windows filenames might not get expanded correctly, so replace=\"false\" may be necessary)."
+#. Tag: para
+#: Cache_loaders.xml:83
+#, no-c-format
+msgid ""
+"The <literal>CacheLoaderClass</literal> attribute defines the class of the "
+"CacheLoader implementation. (Note that, because of a bug in the properties "
+"editor in JBoss, backslashes in variables for Windows filenames might not "
+"get expanded correctly, so replace=\"false\" may be necessary)."
msgstr ""
-#: ./Cache_loaders.xml:356(para)
+#. Tag: para
+#: Cache_loaders.xml:86
+#, no-c-format
msgid "The currently available implementations shipped with JBossCache are:"
msgstr ""
-#: ./Cache_loaders.xml:361(para)
-msgid "<literal>FileCacheLoader</literal>, which is a simple filesystem-based implementation. The <literal><cacheloader><properties></literal> element needs to contain a \"location\" property, which maps to a directory where the file is located (e.g., \"location=c:\\\\tmp\")."
+#. Tag: para
+#: Cache_loaders.xml:91
+#, no-c-format
+msgid ""
+"<literal>FileCacheLoader</literal>, which is a simple filesystem-based "
+"implementation. The <literal><cacheloader><properties></literal> "
+"element needs to contain a \"location\" property, which maps to a directory "
+"where the file is located (e.g., \"location=c:\\tmp\")."
msgstr ""
-#: ./Cache_loaders.xml:366(para)
-msgid "<literal>BdbjeCacheLoader</literal>, which is a CacheLoader implementation based on the Sleepycat DB Java Edition. The <literal><cacheloader><properties></literal> element needs to contain a \"location\" property, which maps to a directory,where the database file for Sleepycat resides (e.g., \"location=c:\\\\tmp\")."
+#. Tag: para
+#: Cache_loaders.xml:96
+#, no-c-format
+msgid ""
+"<literal>BdbjeCacheLoader</literal>, which is a CacheLoader implementation "
+"based on the Sleepycat DB Java Edition. The <literal><cacheloader><"
+"properties></literal> element needs to contain a \"location\" property, "
+"which maps to a directory,where the database file for Sleepycat resides (e."
+"g., \"location=c:\\tmp\")."
msgstr ""
-#: ./Cache_loaders.xml:371(para)
-msgid "<literal>JDBCCacheLoader</literal>, which is a CacheLoader implementation using JDBC to access any relational database. The <literal><cacheloader><properties></literal> element contains a number of properties needed to connect to the database such as username, password, and connection URL. See the section on JDBCCacheLoader for more details."
+#. Tag: para
+#: Cache_loaders.xml:101
+#, no-c-format
+msgid ""
+"<literal>JDBCCacheLoader</literal>, which is a CacheLoader implementation "
+"using JDBC to access any relational database. The <literal><"
+"cacheloader><properties></literal> element contains a number of "
+"properties needed to connect to the database such as username, password, and "
+"connection URL. See the section on JDBCCacheLoader for more details."
msgstr ""
-#: ./Cache_loaders.xml:376(para)
-msgid "<literal>LocalDelegatingCacheLoader</literal>, which enables loading from and storing to another local (same VM) TreeCache."
+#. Tag: para
+#: Cache_loaders.xml:106
+#, no-c-format
+msgid ""
+"<literal>LocalDelegatingCacheLoader</literal>, which enables loading from "
+"and storing to another local (same VM) TreeCache."
msgstr ""
-#: ./Cache_loaders.xml:381(para)
-msgid "<literal>TcpDelegatingCacheLoader</literal>, which enables loading from and storing to a remote (different VM) TreeCache using TCP as the transport mechanism. This CacheLoader is available in JBossCache version 1.3.0 and above."
+#. Tag: para
+#: Cache_loaders.xml:111
+#, no-c-format
+msgid ""
+"<literal>TcpDelegatingCacheLoader</literal>, which enables loading from and "
+"storing to a remote (different VM) TreeCache using TCP as the transport "
+"mechanism. This CacheLoader is available in JBossCache version 1.3.0 and "
+"above."
msgstr ""
-#: ./Cache_loaders.xml:386(para)
-msgid "<literal>ClusteredCacheLoader</literal>, which allows querying of other caches in the same cluster for in-memory data via the same clustering protocols used to replicate data. Writes are <emphasis role=\"bold\">not</emphasis> 'stored' though, as replication would take care of any updates needed. You need to specify a property called \"<literal>timeout</literal>\", a long value telling the cache loader how many milliseconds to wait for responses from the cluster before assuming a null value. For example, \"<literal>timeout = 3000</literal>\" would use a timeout value of 3 seconds. This CacheLoader is available in JBossCache version 1.3.0 and above."
+#. Tag: para
+#: Cache_loaders.xml:116
+#, no-c-format
+msgid ""
+"<literal>ClusteredCacheLoader</literal>, which allows querying of other "
+"caches in the same cluster for in-memory data via the same clustering "
+"protocols used to replicate data. Writes are <emphasis role=\"bold\">not</"
+"emphasis> 'stored' though, as replication would take care of any updates "
+"needed. You need to specify a property called \"<literal>timeout</literal>"
+"\", a long value telling the cache loader how many milliseconds to wait for "
+"responses from the cluster before assuming a null value. For example, "
+"\"<literal>timeout = 3000</literal>\" would use a timeout value of 3 "
+"seconds. This CacheLoader is available in JBossCache version 1.3.0 and above."
msgstr ""
-#: ./Cache_loaders.xml:391(para)
-msgid "Note that the Sleepycat implementation is much more efficient than the filesystem-based implementation, and provides transactional guarantees, but requires a commercial license if distributed with an application (see http://www.sleepycat.com/jeforjbosscache for details)."
+#. Tag: para
+#: Cache_loaders.xml:121
+#, no-c-format
+msgid ""
+"Note that the Sleepycat implementation is much more efficient than the "
+"filesystem-based implementation, and provides transactional guarantees, but "
+"requires a commercial license if distributed with an application (see http://"
+"www.sleepycat.com/jeforjbosscache for details)."
msgstr ""
-#: ./Cache_loaders.xml:394(para)
-msgid "An implementation of CacheLoader has to have an empty constructor due to the way it is instantiated."
+#. Tag: para
+#: Cache_loaders.xml:124
+#, no-c-format
+msgid ""
+"An implementation of CacheLoader has to have an empty constructor due to the "
+"way it is instantiated."
msgstr ""
-#: ./Cache_loaders.xml:397(para)
-msgid "The <literal>properties</literal> element defines a configuration specific to the given implementation. The filesystem-based implementation for example defines the root directory to be used, whereas a database implementation might define the database URL, name and password to establish a database connection. This configuration is passed to the CacheLoader implementation via <literal>CacheLoader.setConfig(Properties)</literal>. Note that backspaces may have to be escaped. <emphasis>Analogous to the <literal>CacheLoaderConfig</literal> attribute in pre-1.3.0 configurations.</emphasis>"
+#. Tag: para
+#: Cache_loaders.xml:127
+#, no-c-format
+msgid ""
+"The <literal>properties</literal> element defines a configuration specific "
+"to the given implementation. The filesystem-based implementation for example "
+"defines the root directory to be used, whereas a database implementation "
+"might define the database URL, name and password to establish a database "
+"connection. This configuration is passed to the CacheLoader implementation "
+"via <literal>CacheLoader.setConfig(Properties)</literal>. Note that "
+"backspaces may have to be escaped. <emphasis>Analogous to the "
+"<literal>CacheLoaderConfig</literal> attribute in pre-1.3.0 configurations.</"
+"emphasis>"
msgstr ""
-#: ./Cache_loaders.xml:400(para)
-msgid "<literal>preload</literal> allows us to define a list of nodes, or even entire subtrees, that are visited by the cache on startup, in order to preload the data associated with those nodes. The default (\"/\") loads the entire data available in the backend store into the cache, which is probably not a good idea given that the data in the backend store might be large. As an example, <literal>/a, /product/catalogue</literal> loads the subtrees <literal>/a</literal> and <literal>/product/catalogue</literal> into the cache, but nothing else. Anything else is loaded lazily when accessed. Preloading makes sense when one anticipates using elements under a given subtree frequently. <emphasis>Note that preloading loads all nodes and associated attributes from the given node, recursively up to the root node</emphasis>. <emphasis>Analogous to the <literal>CacheLoaderPreload</literal> attribute in pre-1.3.0 configurations.</emphasis>"
+#. Tag: para
+#: Cache_loaders.xml:130
+#, no-c-format
+msgid ""
+"<literal>preload</literal> allows us to define a list of nodes, or even "
+"entire subtrees, that are visited by the cache on startup, in order to "
+"preload the data associated with those nodes. The default (\"/\") loads the "
+"entire data available in the backend store into the cache, which is probably "
+"not a good idea given that the data in the backend store might be large. As "
+"an example, <literal>/a, /product/catalogue</literal> loads the subtrees "
+"<literal>/a</literal> and <literal>/product/catalogue</literal> into the "
+"cache, but nothing else. Anything else is loaded lazily when accessed. "
+"Preloading makes sense when one anticipates using elements under a given "
+"subtree frequently. <emphasis>Note that preloading loads all nodes and "
+"associated attributes from the given node, recursively up to the root node</"
+"emphasis>. <emphasis>Analogous to the <literal>CacheLoaderPreload</literal> "
+"attribute in pre-1.3.0 configurations.</emphasis>"
msgstr ""
-#: ./Cache_loaders.xml:403(para)
-msgid "<literal>fetchPersistentState</literal> determines whether or not to fetch the persistent state of a cache when joining a cluster. Only one configured cache loader may set this property to true; if more than one cache loader does so, a configuration exception will be thrown when starting your cache service. <emphasis>Analogous to the <literal>CacheLoaderFetchPersistentState</literal> attribute in pre-1.3.0 configurations.</emphasis>"
+#. Tag: para
+#: Cache_loaders.xml:133
+#, no-c-format
+msgid ""
+"<literal>fetchPersistentState</literal> determines whether or not to fetch "
+"the persistent state of a cache when joining a cluster. Only one configured "
+"cache loader may set this property to true; if more than one cache loader "
+"does so, a configuration exception will be thrown when starting your cache "
+"service. <emphasis>Analogous to the "
+"<literal>CacheLoaderFetchPersistentState</literal> attribute in pre-1.3.0 "
+"configurations.</emphasis>"
msgstr ""
-#: ./Cache_loaders.xml:406(para)
-msgid "<literal>async</literal> determines whether writes to the cache loader block until completed, or are run on a separate thread so writes return immediately. If this is set to true, an instance of <literal>org.jboss.cache.loader.AsyncCacheLoader</literal> is constructed with an instance of the actual cache loader to be used. The <literal>AsyncCacheLoader</literal> then delegates all requests to the underlying cache loader, using a separate thread if necessary. See the Javadocs on <literal>org.jboss.cache.loader.AsyncCacheLoader</literal> for more details. If unspecified, the <literal>async</literal> element defaults to <emphasis>false</emphasis>. <emphasis>Analogous to the <literal>CacheLoaderAsynchronous</literal> attribute in pre-1.3.0 configurations.</emphasis>"
+#. Tag: para
+#: Cache_loaders.xml:136
+#, no-c-format
+msgid ""
+"<literal>async</literal> determines whether writes to the cache loader block "
+"until completed, or are run on a separate thread so writes return "
+"immediately. If this is set to true, an instance of <literal>org.jboss.cache."
+"loader.AsyncCacheLoader</literal> is constructed with an instance of the "
+"actual cache loader to be used. The <literal>AsyncCacheLoader</literal> then "
+"delegates all requests to the underlying cache loader, using a separate "
+"thread if necessary. See the Javadocs on <literal>org.jboss.cache.loader."
+"AsyncCacheLoader</literal> for more details. If unspecified, the "
+"<literal>async</literal> element defaults to <emphasis>false</emphasis>. "
+"<emphasis>Analogous to the <literal>CacheLoaderAsynchronous</literal> "
+"attribute in pre-1.3.0 configurations.</emphasis>"
msgstr ""
-#: ./Cache_loaders.xml:409(para)
-msgid "<emphasis role=\"bold\">Note on using the <literal>async</literal> element:</emphasis> there is always the possibility of dirty reads since all writes are performed asynchronously, and it is thus impossible to guarantee when (and even if) a write succeeds. This needs to be kept in mind when setting the <literal>async</literal> element to true."
+#. Tag: para
+#: Cache_loaders.xml:139
+#, no-c-format
+msgid ""
+"<emphasis role=\"bold\">Note on using the <literal>async</literal> element:</"
+"emphasis> there is always the possibility of dirty reads since all writes "
+"are performed asynchronously, and it is thus impossible to guarantee when "
+"(and even if) a write succeeds. This needs to be kept in mind when setting "
+"the <literal>async</literal> element to true."
msgstr ""
-#: ./Cache_loaders.xml:412(para)
-msgid "<literal>ignoreModifications</literal> determines whether write methods are pushed down to the specific cache loader. Situations may arise where transient application data should only reside in a file based cache loader on the same server as the in-memory cache, for example, with a further shared JDBC cache loader used by all servers in the network. This feature allows you to write to the 'local' file cache loader but not the shared JDBC cache loader. This property defaults to <literal>false</literal>, so writes are propagated to all cache loaders configured."
+#. Tag: para
+#: Cache_loaders.xml:142
+#, no-c-format
+msgid ""
+"<literal>ignoreModifications</literal> determines whether write methods are "
+"pushed down to the specific cache loader. Situations may arise where "
+"transient application data should only reside in a file based cache loader "
+"on the same server as the in-memory cache, for example, with a further "
+"shared JDBC cache loader used by all servers in the network. This feature "
+"allows you to write to the 'local' file cache loader but not the shared JDBC "
+"cache loader. This property defaults to <literal>false</literal>, so writes "
+"are propagated to all cache loaders configured."
msgstr ""
-#: ./Cache_loaders.xml:415(para)
-msgid "<literal>purgeOnStatup</literal> empties the specified cache loader (if <literal>ignoreModifications</literal> is <literal>false</literal>) when the cache loader starts up."
+#. Tag: para
+#: Cache_loaders.xml:145
+#, no-c-format
+msgid ""
+"<literal>purgeOnStatup</literal> empties the specified cache loader (if "
+"<literal>ignoreModifications</literal> is <literal>false</literal>) when the "
+"cache loader starts up."
msgstr ""
-#: ./Cache_loaders.xml:421(title)
+#. Tag: title
+#: Cache_loaders.xml:151
+#, no-c-format
msgid "Cache passivation"
msgstr ""
-#: ./Cache_loaders.xml:422(para)
-msgid "A CacheLoader can be used to enforce node passivation and activation on eviction in a TreeCache."
+#. Tag: para
+#: Cache_loaders.xml:152
+#, no-c-format
+msgid ""
+"A CacheLoader can be used to enforce node passivation and activation on "
+"eviction in a TreeCache."
msgstr ""
-#: ./Cache_loaders.xml:425(para)
-msgid "<emphasis>Cache Passivation</emphasis> is the process of removing an object from in-memory cache and writing it to a secondary data store (e.g., file system, database) on eviction. <emphasis>Cache Activation</emphasis> is the process of restoring an object from the data store into the in-memory cache when it's needed to be used. In both cases, the configured CacheLoader will be used to read from the data store and write to the data store."
+#. Tag: para
+#: Cache_loaders.xml:155
+#, no-c-format
+msgid ""
+"<emphasis>Cache Passivation</emphasis> is the process of removing an object "
+"from in-memory cache and writing it to a secondary data store (e.g., file "
+"system, database) on eviction. <emphasis>Cache Activation</emphasis> is the "
+"process of restoring an object from the data store into the in-memory cache "
+"when it's needed to be used. In both cases, the configured CacheLoader will "
+"be used to read from the data store and write to the data store."
msgstr ""
-#: ./Cache_loaders.xml:428(para)
-msgid "When the eviction policy in effect calls evict() to evict a node from the cache, if passivation is enabled, a notification that the node is being passivated will be emitted to the tree cache listeners and the node and its children will be stored in the cache loader store. When a user calls get() on a node that was evicted earlier, the node is loaded (lazy loaded) from the cache loader store into the in-memory cache. When the node and its children have been loaded, they're removed from the cache loader and a notification is emitted to the tree cache listeners that the node has been activated."
+#. Tag: para
+#: Cache_loaders.xml:158
+#, no-c-format
+msgid ""
+"When the eviction policy in effect calls evict() to evict a node from the "
+"cache, if passivation is enabled, a notification that the node is being "
+"passivated will be emitted to the tree cache listeners and the node and its "
+"children will be stored in the cache loader store. When a user calls get() "
+"on a node that was evicted earlier, the node is loaded (lazy loaded) from "
+"the cache loader store into the in-memory cache. When the node and its "
+"children have been loaded, they're removed from the cache loader and a "
+"notification is emitted to the tree cache listeners that the node has been "
+"activated."
msgstr ""
-#: ./Cache_loaders.xml:431(para)
-msgid "To enable cache passivation/activation, you can set <literal>passivation</literal> to true. The default is false. You set it via the XML cache configuration file. The XML above shows the <literal>passivation</literal> element when configuring a cache loader. When passivation is used, only the first cache loader configured is used. All others are ignored."
+#. Tag: para
+#: Cache_loaders.xml:161
+#, no-c-format
+msgid ""
+"To enable cache passivation/activation, you can set <literal>passivation</"
+"literal> to true. The default is false. You set it via the XML cache "
+"configuration file. The XML above shows the <literal>passivation</literal> "
+"element when configuring a cache loader. When passivation is used, only the "
+"first cache loader configured is used. All others are ignored."
msgstr ""
-#: ./Cache_loaders.xml:437(title)
+#. Tag: title
+#: Cache_loaders.xml:167
+#, no-c-format
msgid "CacheLoader use cases"
msgstr ""
-#: ./Cache_loaders.xml:439(title)
+#. Tag: title
+#: Cache_loaders.xml:169
+#, no-c-format
msgid "Local cache with store"
msgstr ""
-#: ./Cache_loaders.xml:440(para)
-msgid "This is the simplest case. We have a JBossCache instance, whose mode is <literal>LOCAL</literal>, therefore no replication is going on. The CacheLoader simply loads non-existing elements from the store and stores modifications back to the store. When the cache is started, depending on the <literal>preload</literal> element, certain data can be preloaded, so that the cache is partly warmed up."
+#. Tag: para
+#: Cache_loaders.xml:170
+#, no-c-format
+msgid ""
+"This is the simplest case. We have a JBossCache instance, whose mode is "
+"<literal>LOCAL</literal>, therefore no replication is going on. The "
+"CacheLoader simply loads non-existing elements from the store and stores "
+"modifications back to the store. When the cache is started, depending on the "
+"<literal>preload</literal> element, certain data can be preloaded, so that "
+"the cache is partly warmed up."
msgstr ""
-#: ./Cache_loaders.xml:443(para)
-msgid "When using PojoCache, this means that entire POJOs can be stored to a database or a filesystem, and when accessing fields of a POJO, they will be lazily loaded using the CacheLoader to access a backend store. This feature effectively provides simple persistency for any POJO."
+#. Tag: para
+#: Cache_loaders.xml:173
+#, no-c-format
+msgid ""
+"When using PojoCache, this means that entire POJOs can be stored to a "
+"database or a filesystem, and when accessing fields of a POJO, they will be "
+"lazily loaded using the CacheLoader to access a backend store. This feature "
+"effectively provides simple persistency for any POJO."
msgstr ""
-#: ./Cache_loaders.xml:449(title)
+#. Tag: title
+#: Cache_loaders.xml:179
+#, no-c-format
msgid "Replicated caches with all nodes sharing the same store"
msgstr ""
-#: ./Cache_loaders.xml:450(para)
-msgid "The following figure shows 2 JBossCache nodes sharing the same backend store:"
+#. Tag: para
+#: Cache_loaders.xml:180
+#, no-c-format
+msgid ""
+"The following figure shows 2 JBossCache nodes sharing the same backend store:"
msgstr ""
-#: ./Cache_loaders.xml:454(title)
+#. Tag: title
+#: Cache_loaders.xml:184
+#, no-c-format
msgid "2 nodes sharing a backend store"
msgstr ""
-#: ./Cache_loaders.xml:462(para)
-msgid "Of course they can enable state transfer, if they want to have a warm or hot cache after startup."
+#. Tag: para
+#: Cache_loaders.xml:191
+#, no-c-format
+msgid ""
+"Both nodes have a CacheLoader that accesses a common shared backend store. "
+"This could for example be a shared filesystem (using the FileCacheLoader), "
+"or a shared database. Because both nodes access the same store, they don't "
+"necessarily need state transfer on startup.<footnote><para> Of course they "
+"can enable state transfer, if they want to have a warm or hot cache after "
+"startup. </para> </footnote>Rather, the<literal>FetchInMemoryState</literal> "
+"attribute could be set to false, resulting in a 'cold' cache, that gradually "
+"warms up as elements are accessed and loaded for the first time. This would "
+"mean that individual caches in a cluster might have different in-memory "
+"state at any given time (largely depending on their preloading and eviction "
+"strategies)."
msgstr ""
-#: ./Cache_loaders.xml:461(para)
-msgid "Both nodes have a CacheLoader that accesses a common shared backend store. This could for example be a shared filesystem (using the FileCacheLoader), or a shared database. Because both nodes access the same store, they don't necessarily need state transfer on startup.<placeholder-1/>Rather, the<literal>FetchInMemoryState</literal> attribute could be set to false, resulting in a 'cold' cache, that gradually warms up as elements are accessed and loaded for the first time. This would mean that individual caches in a cluster might have different in-memory state at any given time (largely depending on their preloading and eviction strategies)."
+#. Tag: para
+#: Cache_loaders.xml:197
+#, no-c-format
+msgid ""
+"When storing a value, the writer takes care of storing the change in the "
+"backend store. For example, if node1 made change C1 and node2 C2, then node1 "
+"would tell its CacheLoader to store C1, and node2 would tell its CacheLoader "
+"to store C2."
msgstr ""
-#: ./Cache_loaders.xml:467(para)
-msgid "When storing a value, the writer takes care of storing the change in the backend store. For example, if node1 made change C1 and node2 C2, then node1 would tell its CacheLoader to store C1, and node2 would tell its CacheLoader to store C2."
-msgstr ""
-
-#: ./Cache_loaders.xml:473(title)
+#. Tag: title
+#: Cache_loaders.xml:203
+#, no-c-format
msgid "Replicated caches with only one node having a store"
msgstr ""
-#: ./Cache_loaders.xml:477(title)
+#. Tag: title
+#: Cache_loaders.xml:205
+#, no-c-format
msgid "2 nodes but only one accesses the backend store"
msgstr ""
-#: ./Cache_loaders.xml:484(para)
-msgid "This is a similar case as the previous one, but here only one node in the cluster interacts with a backend store via its CacheLoader. All other nodes perform in-memory replication. A use case for this is HTTP session replication, where all nodes replicate sessions in-memory, and - in addition - one node saves the sessions to a persistent backend store. Note that here it may make sense for the CacheLoader to store changes asynchronously, that is <emphasis>not</emphasis> on the caller's thread, in order not to slow down the cluster by accessing (for example) a database. This is a non-issue when using asynchronous replication."
+#. Tag: para
+#: Cache_loaders.xml:212
+#, no-c-format
+msgid ""
+"This is a similar case as the previous one, but here only one node in the "
+"cluster interacts with a backend store via its CacheLoader. All other nodes "
+"perform in-memory replication. A use case for this is HTTP session "
+"replication, where all nodes replicate sessions in-memory, and - in addition "
+"- one node saves the sessions to a persistent backend store. Note that here "
+"it may make sense for the CacheLoader to store changes asynchronously, that "
+"is <emphasis>not</emphasis> on the caller's thread, in order not to slow "
+"down the cluster by accessing (for example) a database. This is a non-issue "
+"when using asynchronous replication."
msgstr ""
-#: ./Cache_loaders.xml:490(title)
+#. Tag: title
+#: Cache_loaders.xml:218
+#, no-c-format
msgid "Replicated caches with each node having its own store"
msgstr ""
-#: ./Cache_loaders.xml:492(title)
+#. Tag: title
+#: Cache_loaders.xml:220
+#, no-c-format
msgid "2 nodes each having its own backend store"
msgstr ""
-#: ./Cache_loaders.xml:499(para)
-msgid "Here, each node has its own datastore. Modifications to the cache are (a) replicated across the cluster and (b) persisted using the CacheLoader. This means that all datastores have exactly the same state. When replicating changes synchronously and in a transaction, the two phase commit protocol takes care that all modifications are replicated and persisted in each datastore, or none is replicated and persisted (atomic updates)."
+#. Tag: para
+#: Cache_loaders.xml:227
+#, no-c-format
+msgid ""
+"Here, each node has its own datastore. Modifications to the cache are (a) "
+"replicated across the cluster and (b) persisted using the CacheLoader. This "
+"means that all datastores have exactly the same state. When replicating "
+"changes synchronously and in a transaction, the two phase commit protocol "
+"takes care that all modifications are replicated and persisted in each "
+"datastore, or none is replicated and persisted (atomic updates)."
msgstr ""
-#: ./Cache_loaders.xml:502(para)
-msgid "Note that currently JBossCache is <emphasis>not</emphasis> an XAResource, that means it doesn't implement recovery. When used with a TransactionManager that supports recovery, this functionality is not available."
+#. Tag: para
+#: Cache_loaders.xml:230
+#, no-c-format
+msgid ""
+"Note that currently JBossCache is <emphasis>not</emphasis> an XAResource, "
+"that means it doesn't implement recovery. When used with a "
+"TransactionManager that supports recovery, this functionality is not "
+"available."
msgstr ""
-#: ./Cache_loaders.xml:505(para)
-msgid "The challenge here is state transfer: when a new node starts it needs to do the following:"
+#. Tag: para
+#: Cache_loaders.xml:233
+#, no-c-format
+msgid ""
+"The challenge here is state transfer: when a new node starts it needs to do "
+"the following:"
msgstr ""
-#: ./Cache_loaders.xml:510(para)
+#. Tag: para
+#: Cache_loaders.xml:238
+#, no-c-format
msgid "Tell the coordinator (oldest node in a cluster) to send it the state"
msgstr ""
-#: ./Cache_loaders.xml:515(para)
-msgid "The coordinator then needs to wait until all in-flight transactions have completed. During this time, it will not allow for new transactions to be started."
+#. Tag: para
+#: Cache_loaders.xml:243
+#, no-c-format
+msgid ""
+"The coordinator then needs to wait until all in-flight transactions have "
+"completed. During this time, it will not allow for new transactions to be "
+"started."
msgstr ""
-#: ./Cache_loaders.xml:520(para)
-msgid "Then the coordinator asks its CacheLoader for the entire state using <literal>loadEntireState()</literal>. It then sends back that state to the new node."
+#. Tag: para
+#: Cache_loaders.xml:248
+#, no-c-format
+msgid ""
+"Then the coordinator asks its CacheLoader for the entire state using "
+"<literal>loadEntireState()</literal>. It then sends back that state to the "
+"new node."
msgstr ""
-#: ./Cache_loaders.xml:525(para)
-msgid "The new node then tells its CacheLoader to store that state in its store, overwriting the old state. This is the <literal>CacheLoader.storeEntireState()</literal> method"
+#. Tag: para
+#: Cache_loaders.xml:253
+#, no-c-format
+msgid ""
+"The new node then tells its CacheLoader to store that state in its store, "
+"overwriting the old state. This is the <literal>CacheLoader.storeEntireState"
+"()</literal> method"
msgstr ""
-#: ./Cache_loaders.xml:530(para)
-msgid "As an option, the transient (in-memory) state can be transferred as well during the state transfer."
+#. Tag: para
+#: Cache_loaders.xml:258
+#, no-c-format
+msgid ""
+"As an option, the transient (in-memory) state can be transferred as well "
+"during the state transfer."
msgstr ""
-#: ./Cache_loaders.xml:535(para)
-msgid "The new node now has the same state in its backend store as everyone else in the cluster, and modifications received from other nodes will now be persisted using the local CacheLoader."
+#. Tag: para
+#: Cache_loaders.xml:263
+#, no-c-format
+msgid ""
+"The new node now has the same state in its backend store as everyone else in "
+"the cluster, and modifications received from other nodes will now be "
+"persisted using the local CacheLoader."
msgstr ""
-#: ./Cache_loaders.xml:545(title)
+#. Tag: title
+#: Cache_loaders.xml:271
+#, no-c-format
msgid "Hierarchical caches"
msgstr ""
-#: ./Cache_loaders.xml:546(para)
-msgid "If you need to set up a hierarchy within a single VM, you can use the <literal>LocalDelegatingCacheLoader</literal>. This type of hierarchy can currently only be set up programmatically. The code below shows how a first-level cache delegates to a local second-level cache:"
+#. Tag: para
+#: Cache_loaders.xml:272
+#, no-c-format
+msgid ""
+"If you need to set up a hierarchy within a single VM, you can use the "
+"<literal>LocalDelegatingCacheLoader</literal>. This type of hierarchy can "
+"currently only be set up programmatically. The code below shows how a first-"
+"level cache delegates to a local second-level cache:"
msgstr ""
-#: ./Cache_loaders.xml:549(programlisting)
-#, no-wrap
-msgid "TreeCache firstLevel, secondLevel;\nLocalDelegatingCacheLoader cache_loader;\n\n// create and configure firstLevel\nfirstLevel=new TreeCache();\n\n// create and configure secondLevel\nsecondLevel=new TreeCache();\n\n// create DelegatingCacheLoader\ncache_loader=new LocalDelegatingCacheLoader(secondLevel);\n\n// set CacheLoader in firstLevel\nfirstLevel.setCacheLoader(cache_loader);\n\n// start secondLevel\nsecondLevel.startService();\n\n// start firstLevel\nfirstLevel.startService();\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:275
+#, no-c-format
+msgid ""
+"TreeCache firstLevel, secondLevel;\n"
+"LocalDelegatingCacheLoader cache_loader;\n"
+"\n"
+"// create and configure firstLevel\n"
+"firstLevel=new TreeCache();\n"
+"\n"
+"// create and configure secondLevel\n"
+"secondLevel=new TreeCache();\n"
+"\n"
+"// create DelegatingCacheLoader\n"
+"cache_loader=new LocalDelegatingCacheLoader(secondLevel);\n"
+"\n"
+"// set CacheLoader in firstLevel\n"
+"firstLevel.setCacheLoader(cache_loader);\n"
+"\n"
+"// start secondLevel\n"
+"secondLevel.startService();\n"
+"\n"
+"// start firstLevel\n"
+"firstLevel.startService();"
msgstr ""
-#: ./Cache_loaders.xml:570(para)
-msgid "If you need to set up a hierarchy across VMs but within a cluster, you can use the <literal>RpcDelegatingCacheLoader</literal>, which delegates all cache loading requests from non-coordinator caches to the cluster's coordinator cache. The coordinator cache is the first cache in the cluster to come online. Note that if the coordinator cache leaves the cluster for any reason, the second cache in the cluster to come online becomes the coordinator and so on. The XML below shows how to configure a cluster using <literal>RpcDelegatingCacheLoader</literal>:"
+#. Tag: para
+#: Cache_loaders.xml:276
+#, no-c-format
+msgid ""
+"If you need to set up a hierarchy across VMs but within a cluster, you can "
+"use the <literal>RpcDelegatingCacheLoader</literal>, which delegates all "
+"cache loading requests from non-coordinator caches to the cluster's "
+"coordinator cache. The coordinator cache is the first cache in the cluster "
+"to come online. Note that if the coordinator cache leaves the cluster for "
+"any reason, the second cache in the cluster to come online becomes the "
+"coordinator and so on. The XML below shows how to configure a cluster using "
+"<literal>RpcDelegatingCacheLoader</literal>:"
msgstr ""
-#: ./Cache_loaders.xml:573(programlisting)
-#, no-wrap
-msgid "<!-- ==================================================================== -->\n<!-- Defines TreeCache configuration -->\n<!-- ==================================================================== -->\n\n<mbean code=\"org.jboss.cache.TreeCache\" name=\"jboss.cache:service=TreeCache\">\n...\n<attribute name=\"CacheLoaderConfiguration\">\n <config>\n <passivation>false</passivation>\n <preload>/some/stuff</preload>\n <cacheloader>\n <class>org.jboss.cache.loader.RpcDelegatingCacheLoader</class>\n <!-- whether the cache loader writes are asynchronous -->\n <async>false</async>\n <!-- only one cache loader in the chain may set fetchPersistentState to true.\n An exception is thrown if more than one cache loader sets this to true. \n\t -->\n !
<fetchPersistentState>false</fetchPersistentState>\n <!-- determines whether this cache loader ignores writes - defaults to false. \n\t -->\n <ignoreModifications>false</ignoreModifications>\n <!-- if set to true, purges the contents of this cache loader when \n\t the cache starts up.\n Defaults to false. -->\n <purgeOnStartup>false</purgeOnStartup>\n </cacheloader>\n </config>\n</attribute>\n...\n</mbean>\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:279
+#, no-c-format
+msgid ""
+"<!-- ==================================================================== "
+"-->\n"
+"<!-- Defines TreeCache configuration "
+"-->\n"
+"<!-- ==================================================================== "
+"-->\n"
+"\n"
+"<mbean code=\"org.jboss.cache.TreeCache\" name=\"jboss.cache:"
+"service=TreeCache\">\n"
+"...\n"
+"<attribute name=\"CacheLoaderConfiguration\">\n"
+" <config>\n"
+" <passivation>false</passivation>\n"
+" <preload>/some/stuff</preload>\n"
+" <cacheloader>\n"
+" <class>org.jboss.cache.loader.RpcDelegatingCacheLoader</"
+"class>\n"
+" <!-- whether the cache loader writes are asynchronous -->\n"
+" <async>false</async>\n"
+" <!-- only one cache loader in the chain may set "
+"fetchPersistentState to true.\n"
+" An exception is thrown if more than one cache loader sets "
+"this to true. \n"
+" -->\n"
+" <fetchPersistentState>false</fetchPersistentState>\n"
+" <!-- determines whether this cache loader ignores writes - "
+"defaults to false. \n"
+" -->\n"
+" <ignoreModifications>false</ignoreModifications>\n"
+" <!-- if set to true, purges the contents of this cache loader "
+"when \n"
+" the cache starts up.\n"
+" Defaults to false. -->\n"
+" <purgeOnStartup>false</purgeOnStartup>\n"
+" </cacheloader>\n"
+" </config>\n"
+"</attribute>\n"
+"...\n"
+"</mbean>"
msgstr ""
-#: ./Cache_loaders.xml:604(para)
-msgid "Note that currently (JBossCache 1.3.0) this cache loader is not well supported, and has not been tested. We suggest to use TcpDelegatingCacheLoader instead (see next)."
+#. Tag: para
+#: Cache_loaders.xml:280
+#, no-c-format
+msgid ""
+"Note that currently (JBossCache 1.3.0) this cache loader is not well "
+"supported, and has not been tested. We suggest to use "
+"TcpDelegatingCacheLoader instead (see next)."
msgstr ""
-#: ./Cache_loaders.xml:612(title)
+#. Tag: title
+#: Cache_loaders.xml:286
+#, no-c-format
msgid "TcpDelegatingCacheLoader"
msgstr ""
-#: ./Cache_loaders.xml:613(para)
-msgid "This cache loader allows to delegate loads and stores to another instance of JBossCache, which could reside (a)in the same address space, (b) in a different process on the same host, or (c) in a different process on a different host. Option (a) is mostly used for unit testing, and the envisaged use is (b) and (c)."
+#. Tag: para
+#: Cache_loaders.xml:287
+#, no-c-format
+msgid ""
+"This cache loader allows to delegate loads and stores to another instance of "
+"JBossCache, which could reside (a)in the same address space, (b) in a "
+"different process on the same host, or (c) in a different process on a "
+"different host. Option (a) is mostly used for unit testing, and the "
+"envisaged use is (b) and (c)."
msgstr ""
-#: ./Cache_loaders.xml:616(para)
-msgid "A TcpDelegatingCacheLoader talks to a remote TcpCacheServer, which can be a standalone process, or embedded as an MBean inside JBoss. The TcpCacheServer has a reference to another JBossCache, which it can create itself, or which is given to it (e.g. by JBoss, using dependency injection)."
+#. Tag: para
+#: Cache_loaders.xml:290
+#, no-c-format
+msgid ""
+"A TcpDelegatingCacheLoader talks to a remote TcpCacheServer, which can be a "
+"standalone process, or embedded as an MBean inside JBoss. The TcpCacheServer "
+"has a reference to another JBossCache, which it can create itself, or which "
+"is given to it (e.g. by JBoss, using dependency injection)."
msgstr ""
-#: ./Cache_loaders.xml:619(para)
-msgid "The TcpDelegatingCacheLoader is configured with the host and port of the remote TcpCacheServer, and uses this to communicate to it."
+#. Tag: para
+#: Cache_loaders.xml:293
+#, no-c-format
+msgid ""
+"The TcpDelegatingCacheLoader is configured with the host and port of the "
+"remote TcpCacheServer, and uses this to communicate to it."
msgstr ""
-#: ./Cache_loaders.xml:624(para)
-msgid "An example set of a TcpCacheServer running inside of JBoss is shown below:"
+#. Tag: para
+#: Cache_loaders.xml:296
+#, no-c-format
+msgid ""
+"An example set of a TcpCacheServer running inside of JBoss is shown below:"
msgstr ""
-#: ./Cache_loaders.xml:627(programlisting)
-#, no-wrap
-msgid "<server>\n\n <classpath codebase=\"./lib\" archives=\"jboss-cache.jar\"/>\n\n <mbean code=\"org.jboss.cache.loader.tcp.TcpCacheServer\" \n name=\"jboss.cache:service=TcpCacheServer\">\n <depends optional-attribute-name=\"Cache\"\n proxy-type=\"attribute\">jboss.cache:service=TreeCache</depends>\n <attribute name=\"BindAddress\">${jboss.bind.address:localhost}</attribute>\n <attribute name=\"Port\">7500</attribute>\n <attribute name=\"MBeanServerName\"></attribute>\n <!--<attribute name=\"CacheName\">jboss.cache:service=TreeCache</attribute>-->\n </mbean>\n\n</server> \n"
+#. Tag: programlisting
+#: Cache_loaders.xml:299
+#, no-c-format
+msgid ""
+"<server>\n"
+"\n"
+" <classpath codebase=\"./lib\" archives=\"jboss-cache.jar\"/>\n"
+"\n"
+" <mbean code=\"org.jboss.cache.loader.tcp.TcpCacheServer\" \n"
+" name=\"jboss.cache:service=TcpCacheServer\">\n"
+" <depends optional-attribute-name=\"Cache\"\n"
+" proxy-type=\"attribute\">jboss.cache:service=TreeCache</"
+"depends>\n"
+" <attribute name=\"BindAddress\">${jboss.bind.address:"
+"localhost}</attribute>\n"
+" <attribute name=\"Port\">7500</attribute>\n"
+" <attribute name=\"MBeanServerName\"></attribute>\n"
+" <!--<attribute name=\"CacheName\">jboss.cache:"
+"service=TreeCache</attribute>-->\n"
+" </mbean>\n"
+"\n"
+"</server>"
msgstr ""
-#: ./Cache_loaders.xml:643(para)
-msgid "The BindAddress and Port define where its server socket is listening on, and an existing JBossCache MBean is injected into it (assigned to 'Cache'). This means that all requests from the TcpDelegatingCacheLoader will be received by this instance and forwarded to the JBossCache MBean."
+#. Tag: para
+#: Cache_loaders.xml:300
+#, no-c-format
+msgid ""
+"The BindAddress and Port define where its server socket is listening on, and "
+"an existing JBossCache MBean is injected into it (assigned to 'Cache'). This "
+"means that all requests from the TcpDelegatingCacheLoader will be received "
+"by this instance and forwarded to the JBossCache MBean."
msgstr ""
-#: ./Cache_loaders.xml:646(para)
-msgid "Note that there is also a 'Config' attribute which points to a config XML file for JBossCache. If it is set, then the TcpCacheServer will create its own instance of JBossCache and configure it according to the Config attribute."
+#. Tag: para
+#: Cache_loaders.xml:303
+#, no-c-format
+msgid ""
+"Note that there is also a 'Config' attribute which points to a config XML "
+"file for JBossCache. If it is set, then the TcpCacheServer will create its "
+"own instance of JBossCache and configure it according to the Config "
+"attribute."
msgstr ""
-#: ./Cache_loaders.xml:649(para) ./Cache_loaders.xml:717(para)
+#. Tag: para
+#: Cache_loaders.xml:306 Cache_loaders.xml:342
+#, no-c-format
msgid "The client side looks as follow:"
msgstr ""
-#: ./Cache_loaders.xml:652(programlisting)
-#, no-wrap
-msgid "<attribute name=\"CacheLoaderConfiguration\">\n <config>\n <cacheloader>\n <class>org.jboss.cache.loader.tcp.TcpDelegatingCacheLoader</class>\n <properties>\n host=localhost\n port=7500\n </properties>\n </cacheloader>\n </config>\n</attribute>\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:309
+#, no-c-format
+msgid ""
+"<attribute name=\"CacheLoaderConfiguration\">\n"
+" <config>\n"
+" <cacheloader>\n"
+" <class>org.jboss.cache.loader.tcp."
+"TcpDelegatingCacheLoader</class>\n"
+" <properties>\n"
+" host=localhost\n"
+" port=7500\n"
+" </properties>\n"
+" </cacheloader>\n"
+" </config>\n"
+"</attribute>"
msgstr ""
-#: ./Cache_loaders.xml:664(para)
-msgid "This means this instance of JBossCache will delegate all load and store requests to the remote TcpCacheServer running at localhost:7500."
+#. Tag: para
+#: Cache_loaders.xml:310
+#, no-c-format
+msgid ""
+"This means this instance of JBossCache will delegate all load and store "
+"requests to the remote TcpCacheServer running at localhost:7500."
msgstr ""
-#: ./Cache_loaders.xml:667(para)
-msgid "A typical use case could be multiple replicated instance of JBossCache in the same cluster, all delegating to the same TcpCacheServer instance. The TcpCacheServer might itself delegate to a database via JDBCCacheLoader, but the point here is that - if we have 5 nodes all accessing the same dataset - they will load the data from the TcpCacheServer, which has do execute one SQL statement per unloaded data set. If the nodes went directly to the database, then we'd have the same SQL executed multiple times. So TcpCacheServer serves as a natural cache in front of the DB (assuming that a network round trip is faster than a DB access (which usually also include a network round trip))."
+#. Tag: para
+#: Cache_loaders.xml:313
+#, no-c-format
+msgid ""
+"A typical use case could be multiple replicated instance of JBossCache in "
+"the same cluster, all delegating to the same TcpCacheServer instance. The "
+"TcpCacheServer might itself delegate to a database via JDBCCacheLoader, but "
+"the point here is that - if we have 5 nodes all accessing the same dataset - "
+"they will load the data from the TcpCacheServer, which has do execute one "
+"SQL statement per unloaded data set. If the nodes went directly to the "
+"database, then we'd have the same SQL executed multiple times. So "
+"TcpCacheServer serves as a natural cache in front of the DB (assuming that a "
+"network round trip is faster than a DB access (which usually also include a "
+"network round trip))."
msgstr ""
-#: ./Cache_loaders.xml:670(para)
-msgid "To alleviate single point of failure, we could combine this with a ChainingCacheLoader, where the first CacheLoader is a ClusteredCacheLoader, the second a TcpDelegatingCacheLoader, and the last a JDBCacheLoader, effectively defining our cost of access to a cache in increasing order of cost."
+#. Tag: para
+#: Cache_loaders.xml:316
+#, no-c-format
+msgid ""
+"To alleviate single point of failure, we could combine this with a "
+"ChainingCacheLoader, where the first CacheLoader is a ClusteredCacheLoader, "
+"the second a TcpDelegatingCacheLoader, and the last a JDBCacheLoader, "
+"effectively defining our cost of access to a cache in increasing order of "
+"cost."
msgstr ""
-#: ./Cache_loaders.xml:678(title)
+#. Tag: title
+#: Cache_loaders.xml:322
+#, no-c-format
msgid "RmiDelegatingCacheLoader"
msgstr ""
-#: ./Cache_loaders.xml:679(para)
-msgid "Similar to the TcpDelegatingCacheLoader, the RmiDelegatingCacheLoader uses RMI as a method of communicating with a remote cache."
+#. Tag: para
+#: Cache_loaders.xml:323
+#, no-c-format
+msgid ""
+"Similar to the TcpDelegatingCacheLoader, the RmiDelegatingCacheLoader uses "
+"RMI as a method of communicating with a remote cache."
msgstr ""
-#: ./Cache_loaders.xml:682(para)
-msgid "An RmiDelegatingCacheLoader talks to a remote RmiCacheServer, which is a standalone process. The RmiCacheServer has a reference to another JBossCache, which it can create itself, or which is given to it (e.g. by JBoss, using dependency injection)."
+#. Tag: para
+#: Cache_loaders.xml:326
+#, no-c-format
+msgid ""
+"An RmiDelegatingCacheLoader talks to a remote RmiCacheServer, which is a "
+"standalone process. The RmiCacheServer has a reference to another "
+"JBossCache, which it can create itself, or which is given to it (e.g. by "
+"JBoss, using dependency injection)."
msgstr ""
-#: ./Cache_loaders.xml:685(para)
-msgid "The RmiDelegatingCacheLoader is configured with the host, port of the remote RMI server and the bind name of the RmiCacheServer, and uses this to communicate."
+#. Tag: para
+#: Cache_loaders.xml:329
+#, no-c-format
+msgid ""
+"The RmiDelegatingCacheLoader is configured with the host, port of the remote "
+"RMI server and the bind name of the RmiCacheServer, and uses this to "
+"communicate."
msgstr ""
-#: ./Cache_loaders.xml:690(para)
-msgid "An example set of an RmiCacheServer running inside of JBoss is shown below:"
+#. Tag: para
+#: Cache_loaders.xml:332
+#, no-c-format
+msgid ""
+"An example set of an RmiCacheServer running inside of JBoss is shown below:"
msgstr ""
-#: ./Cache_loaders.xml:693(programlisting)
-#, no-wrap
-msgid "<server>\n\n <classpath codebase=\"./lib\" archives=\"jboss-cache.jar\"/>\n\n <mbean code=\"org.jboss.cache.loader.rmi.RmiCacheServer\" \n name=\"jboss.cache:service=RmiCacheServer\">\n <depends optional-attribute-name=\"Cache\"\n proxy-type=\"attribute\">jboss.cache:service=TreeCache</depends>\n <!-- the address and port of the RMI server. -->\n <attribute name=\"BindAddress\">${jboss.bind.address:localhost}</attribute>\n <attribute name=\"Port\">1098</attribute>\n <attribute name=\"BindName\">MyRmiCacheServer</attribute>\n <attribute name=\"MBeanServerName\"></attribute>\n <!--<attribute name=\"CacheName\">jboss.cache:service=TreeCache</attribute>-->\n </mbean>\n\n</server> \n"
+#. Tag: programlisting
+#: Cache_loaders.xml:335
+#, no-c-format
+msgid ""
+"<server>\n"
+"\n"
+" <classpath codebase=\"./lib\" archives=\"jboss-cache.jar\"/>\n"
+"\n"
+" <mbean code=\"org.jboss.cache.loader.rmi.RmiCacheServer\" \n"
+" name=\"jboss.cache:service=RmiCacheServer\">\n"
+" <depends optional-attribute-name=\"Cache\"\n"
+" proxy-type=\"attribute\">jboss.cache:service=TreeCache</"
+"depends>\n"
+" <!-- the address and port of the RMI server. -->\n"
+" <attribute name=\"BindAddress\">${jboss.bind.address:"
+"localhost}</attribute>\n"
+" <attribute name=\"Port\">1098</attribute>\n"
+" <attribute name=\"BindName\">MyRmiCacheServer</"
+"attribute>\n"
+" <attribute name=\"MBeanServerName\"></attribute>\n"
+" <!--<attribute name=\"CacheName\">jboss.cache:"
+"service=TreeCache</attribute>-->\n"
+" </mbean>\n"
+"\n"
+"</server>"
msgstr ""
-#: ./Cache_loaders.xml:711(para)
-msgid "The BindAddress and Port should point to an already-running RMI server and the BindName is the name the object is bound to in the RMI server. An existing JBossCache MBean is injected into it (assigned to 'Cache'). This means that all requests from the TcpDelegatingCacheLoader will be received by this instance and forwarded to the JBossCache MBean."
+#. Tag: para
+#: Cache_loaders.xml:336
+#, no-c-format
+msgid ""
+"The BindAddress and Port should point to an already-running RMI server and "
+"the BindName is the name the object is bound to in the RMI server. An "
+"existing JBossCache MBean is injected into it (assigned to 'Cache'). This "
+"means that all requests from the TcpDelegatingCacheLoader will be received "
+"by this instance and forwarded to the JBossCache MBean."
msgstr ""
-#: ./Cache_loaders.xml:714(para)
-msgid "Note that there is also a 'Config' attribute which points to a config XML file for JBossCache. If it is set, then the RmiCacheServer will create its own instance of JBossCache and configure it according to the Config attribute."
+#. Tag: para
+#: Cache_loaders.xml:339
+#, no-c-format
+msgid ""
+"Note that there is also a 'Config' attribute which points to a config XML "
+"file for JBossCache. If it is set, then the RmiCacheServer will create its "
+"own instance of JBossCache and configure it according to the Config "
+"attribute."
msgstr ""
-#: ./Cache_loaders.xml:720(programlisting)
-#, no-wrap
-msgid "<attribute name=\"CacheLoaderConfiguration\">\n <config>\n <cacheloader>\n <class>org.jboss.cache.loader.RmiDelegatingCacheLoader</class>\n <properties>\n host=localhost\n port=1098\n \t\t name=MyRmiCacheServer\n </properties>\n </cacheloader>\n </config>\n</attribute>\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:345
+#, no-c-format
+msgid ""
+"<attribute name=\"CacheLoaderConfiguration\">\n"
+" <config>\n"
+" <cacheloader>\n"
+" <class>org.jboss.cache.loader.RmiDelegatingCacheLoader</"
+"class>\n"
+" <properties>\n"
+" host=localhost\n"
+" port=1098\n"
+" name=MyRmiCacheServer\n"
+" </properties>\n"
+" </cacheloader>\n"
+" </config>\n"
+"</attribute>"
msgstr ""
-#: ./Cache_loaders.xml:733(para)
-msgid "This means this instance of JBossCache will delegate all load and store requests to the remote RmiCacheServer running as MyRmiCacheServer on an RMI server running on localhost:1098."
+#. Tag: para
+#: Cache_loaders.xml:346
+#, no-c-format
+msgid ""
+"This means this instance of JBossCache will delegate all load and store "
+"requests to the remote RmiCacheServer running as MyRmiCacheServer on an RMI "
+"server running on localhost:1098."
msgstr ""
-#: ./Cache_loaders.xml:736(para)
-msgid "Very similar use case scenarios that apply to TcpDelegatingCacheLoaders above apply to RmiDelegatingCacheLoaders as well."
+#. Tag: para
+#: Cache_loaders.xml:349
+#, no-c-format
+msgid ""
+"Very similar use case scenarios that apply to TcpDelegatingCacheLoaders "
+"above apply to RmiDelegatingCacheLoaders as well."
msgstr ""
-#: ./Cache_loaders.xml:746(title)
+#. Tag: title
+#: Cache_loaders.xml:357
+#, no-c-format
msgid "JDBC-based CacheLoader"
msgstr ""
-#: ./Cache_loaders.xml:747(para)
-msgid "JBossCache is distributed with a JDBC-based CacheLoader implementation that stores/loads nodes' state into a relational database. The implementing class is <literal>org.jboss.cache.loader.JDBCCacheLoader</literal>."
+#. Tag: para
+#: Cache_loaders.xml:358
+#, no-c-format
+msgid ""
+"JBossCache is distributed with a JDBC-based CacheLoader implementation that "
+"stores/loads nodes' state into a relational database. The implementing class "
+"is <literal>org.jboss.cache.loader.JDBCCacheLoader</literal>."
msgstr ""
-#: ./Cache_loaders.xml:753(para)
+#. Tag: para
+#: Cache_loaders.xml:361
+#, no-c-format
+msgid ""
+"The current implementation uses just one table. Each row in the table "
+"represents one node and contains three columns:"
+msgstr ""
+
+#. Tag: para
+#: Cache_loaders.xml:364
+#, no-c-format
msgid "column for FQN (which is also a primary key column)"
msgstr ""
-#: ./Cache_loaders.xml:756(para)
+#. Tag: para
+#: Cache_loaders.xml:367
+#, no-c-format
msgid "column for node contents (attribute/value pairs)"
msgstr ""
-#: ./Cache_loaders.xml:759(para)
+#. Tag: para
+#: Cache_loaders.xml:370
+#, no-c-format
msgid "column for parent FQN"
msgstr ""
-#: ./Cache_loaders.xml:750(para)
-msgid "The current implementation uses just one table. Each row in the table represents one node and contains three columns: <placeholder-1/>"
+#. Tag: para
+#: Cache_loaders.xml:374
+#, no-c-format
+msgid ""
+"FQN's are stored as strings. Node content is stored as a BLOB. "
+"<emphasis>WARNING:</emphasis> TreeCache does not impose any limitations on "
+"the types of objects used in FQN but this implementation of CacheLoader "
+"requires FQN to contain only objects of type <literal>java.lang.String</"
+"literal>. Another limitation for FQN is its length. Since FQN is a primary "
+"key, its default column type is <literal>VARCHAR</literal> which can store "
+"text values up to some maximum length determined by the database. FQN is "
+"also subject to any maximum primary key length restriction imposed by the "
+"database."
msgstr ""
-#: ./Cache_loaders.xml:763(para)
-msgid "FQN's are stored as strings. Node content is stored as a BLOB. <emphasis>WARNING:</emphasis> TreeCache does not impose any limitations on the types of objects used in FQN but this implementation of CacheLoader requires FQN to contain only objects of type <literal>java.lang.String</literal>. Another limitation for FQN is its length. Since FQN is a primary key, its default column type is <literal>VARCHAR</literal> which can store text values up to some maximum length determined by the database. FQN is also subject to any maximum primary key length restriction imposed by the database."
+#. Tag: para
+#: Cache_loaders.xml:377
+#, no-c-format
+msgid ""
+"See <ulink url=\"???\">http://wiki.jboss.org/wiki/Wiki.jsp?"
+"page=JDBCCacheLoader</ulink> for configuration tips with specific database "
+"systems."
msgstr ""
-#: ./Cache_loaders.xml:766(para)
-msgid "See <ulink url=\"???\">http://wiki.jboss.org/wiki/Wiki.jsp?page=JDBCCacheLoader</ulink> for configuration tips with specific database systems."
-msgstr ""
-
-#: ./Cache_loaders.xml:770(title)
+#. Tag: title
+#: Cache_loaders.xml:381
+#, no-c-format
msgid "JDBCCacheLoader configuration"
msgstr ""
-#: ./Cache_loaders.xml:772(title)
+#. Tag: title
+#: Cache_loaders.xml:383
+#, no-c-format
msgid "Table configuration"
msgstr ""
-#: ./Cache_loaders.xml:776(para)
-msgid "<emphasis>cache.jdbc.table.name</emphasis> - the name of the table. The default value is 'jbosscache'."
+#. Tag: para
+#: Cache_loaders.xml:384
+#, no-c-format
+msgid ""
+"Table and column names as well as column types are configurable with the "
+"following properties."
msgstr ""
-#: ./Cache_loaders.xml:779(para)
-msgid "<emphasis>cache.jdbc.table.primarykey</emphasis> - the name of the primary key for the table. The default value is 'jbosscache_pk'."
+#. Tag: para
+#: Cache_loaders.xml:387
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.table.name</emphasis> - the name of the table. The "
+"default value is 'jbosscache'."
msgstr ""
-#: ./Cache_loaders.xml:782(para)
-msgid "<emphasis>cache.jdbc.table.create</emphasis> - can be true or false. Indicates whether to create the table during startup. If true, the table is created if it doesn't already exist. The default value is true."
+#. Tag: para
+#: Cache_loaders.xml:390
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.table.primarykey</emphasis> - the name of the primary "
+"key for the table. The default value is 'jbosscache_pk'."
msgstr ""
-#: ./Cache_loaders.xml:785(para)
-msgid "<emphasis>cache.jdbc.table.drop</emphasis> - can be true or false. Indicates whether to drop the table during shutdown. The default value is true."
+#. Tag: para
+#: Cache_loaders.xml:393
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.table.create</emphasis> - can be true or false. "
+"Indicates whether to create the table during startup. If true, the table is "
+"created if it doesn't already exist. The default value is true."
msgstr ""
-#: ./Cache_loaders.xml:788(para)
-msgid "<emphasis>cache.jdbc.fqn.column</emphasis> - FQN column name. The default value is 'fqn'."
+#. Tag: para
+#: Cache_loaders.xml:396
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.table.drop</emphasis> - can be true or false. Indicates "
+"whether to drop the table during shutdown. The default value is true."
msgstr ""
-#: ./Cache_loaders.xml:791(para)
-msgid "<emphasis>cache.jdbc.fqn.type</emphasis> - FQN column type. The default value is 'varchar(255)'."
+#. Tag: para
+#: Cache_loaders.xml:399
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.fqn.column</emphasis> - FQN column name. The default "
+"value is 'fqn'."
msgstr ""
-#: ./Cache_loaders.xml:794(para)
-msgid "<emphasis>cache.jdbc.node.column</emphasis> - node contents column name. The default value is 'node'."
+#. Tag: para
+#: Cache_loaders.xml:402
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.fqn.type</emphasis> - FQN column type. The default "
+"value is 'varchar(255)'."
msgstr ""
-#: ./Cache_loaders.xml:797(para)
-msgid "<emphasis>cache.jdbc.node.type</emphasis> - node contents column type. The default value is 'blob'. This type must specify a valid binary data type for the database being used."
+#. Tag: para
+#: Cache_loaders.xml:405
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.node.column</emphasis> - node contents column name. The "
+"default value is 'node'."
msgstr ""
-#: ./Cache_loaders.xml:773(para)
-msgid "Table and column names as well as column types are configurable with the following properties. <placeholder-1/>"
+#. Tag: para
+#: Cache_loaders.xml:408
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.node.type</emphasis> - node contents column type. The "
+"default value is 'blob'. This type must specify a valid binary data type for "
+"the database being used."
msgstr ""
-#: ./Cache_loaders.xml:804(title)
+#. Tag: title
+#: Cache_loaders.xml:415
+#, no-c-format
msgid "DataSource"
msgstr ""
-#: ./Cache_loaders.xml:808(para)
-msgid "<emphasis>cache.jdbc.datasource</emphasis> - JNDI name of the DataSource. The default value is 'java:/DefaultDS'."
+#. Tag: para
+#: Cache_loaders.xml:416
+#, no-c-format
+msgid ""
+"If you are using JBossCache in a managed environment (e.g., an application "
+"server) you can specify the JNDI name of the DataSource you want to use."
msgstr ""
-#: ./Cache_loaders.xml:805(para)
-msgid "If you are using JBossCache in a managed environment (e.g., an application server) you can specify the JNDI name of the DataSource you want to use. <placeholder-1/>"
+#. Tag: para
+#: Cache_loaders.xml:419
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.datasource</emphasis> - JNDI name of the DataSource. "
+"The default value is 'java:/DefaultDS'."
msgstr ""
-#: ./Cache_loaders.xml:815(title)
+#. Tag: title
+#: Cache_loaders.xml:426
+#, no-c-format
msgid "JDBC driver"
msgstr ""
-#: ./Cache_loaders.xml:819(para)
-msgid "<emphasis>cache.jdbc.driver</emphasis> - fully qualified JDBC driver name."
+#. Tag: para
+#: Cache_loaders.xml:427
+#, no-c-format
+msgid ""
+"If you are <emphasis>not</emphasis> using DataSource you have the following "
+"properties to configure database access using a JDBC driver."
msgstr ""
-#: ./Cache_loaders.xml:822(para)
-msgid "<emphasis>cache.jdbc.url</emphasis> - URL to connect to the database."
+#. Tag: para
+#: Cache_loaders.xml:430
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.driver</emphasis> - fully qualified JDBC driver name."
msgstr ""
-#: ./Cache_loaders.xml:825(para)
-msgid "<emphasis>cache.jdbc.user</emphasis> - user name to connect to the database."
+#. Tag: para
+#: Cache_loaders.xml:433
+#, no-c-format
+msgid "<emphasis>cache.jdbc.url</emphasis> - URL to connect to the database."
msgstr ""
-#: ./Cache_loaders.xml:828(para)
-msgid "<emphasis>cache.jdbc.password</emphasis> - password to connect to the database."
+#. Tag: para
+#: Cache_loaders.xml:436
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.user</emphasis> - user name to connect to the database."
msgstr ""
-#: ./Cache_loaders.xml:816(para)
-msgid "If you are <emphasis>not</emphasis> using DataSource you have the following properties to configure database access using a JDBC driver. <placeholder-1/>"
+#. Tag: para
+#: Cache_loaders.xml:439
+#, no-c-format
+msgid ""
+"<emphasis>cache.jdbc.password</emphasis> - password to connect to the "
+"database."
msgstr ""
-#: ./Cache_loaders.xml:835(title)
+#. Tag: title
+#: Cache_loaders.xml:446
+#, no-c-format
msgid "Configuration example"
msgstr ""
-#: ./Cache_loaders.xml:836(para)
-msgid "Below is an example of a JDBC CacheLoader using Oracle as database. The CacheLoaderConfiguration XML element contains an arbitrary set of properties which define the database-related configuration."
+#. Tag: para
+#: Cache_loaders.xml:447
+#, no-c-format
+msgid ""
+"Below is an example of a JDBC CacheLoader using Oracle as database. The "
+"CacheLoaderConfiguration XML element contains an arbitrary set of properties "
+"which define the database-related configuration."
msgstr ""
-#: ./Cache_loaders.xml:840(programlisting)
-#, no-wrap
-msgid "<attribute name=\"CacheLoaderConfiguration\">\n <config>\n <passivation>false</passivation>\n <preload>/some/stuff</preload>\n <cacheloader>\n <class>org.jboss.cache.loader.JDBCCacheLoader</class>\n <!-- same as the old CacheLoaderConfig attribute -->\n <properties>\n cache.jdbc.table.name=jbosscache\n cache.jdbc.table.create=true\n cache.jdbc.table.drop=true\n cache.jdbc.table.primarykey=jbosscache_pk\n cache.jdbc.fqn.column=fqn\n cache.jdbc.fqn.type=varchar(255)\n cache.jdbc.node.column=node\n cache.jdbc.node.type=blob\n cache.jdbc.parent.column=parent\n cache.jdbc.driver=oracle.jdbc.OracleDriver\n cache.jdbc.url=jdbc:oracle:thin:@localhost:1521:JBOSSDB\n cache.jdbc.u!
ser=SCOTT\n cache.jdbc.password=TIGER\n </properties>\n <!-- whether the cache loader writes are asynchronous -->\n <async>false</async>\n <!-- only one cache loader in the chain may set fetchPersistentState to true.\n An exception is thrown if more than one cache loader sets this to true. \n\t\t -->\n <fetchPersistentState>true</fetchPersistentState>\n <!-- determines whether this cache loader ignores writes - defaults to false. \n\t -->\n <ignoreModifications>false</ignoreModifications>\n <!-- if set to true, purges the contents of this cache loader when the cache \n\t starts up. Defaults to false. -->\n <purgeOnStartup>false</purgeOnStartup>\n </cacheloader>\n </config>\n</attribute>\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:451
+#, no-c-format
+msgid ""
+"<attribute name=\"CacheLoaderConfiguration\">\n"
+" <config>\n"
+" <passivation>false</passivation>\n"
+" <preload>/some/stuff</preload>\n"
+" <cacheloader>\n"
+" <class>org.jboss.cache.loader.JDBCCacheLoader</"
+"class>\n"
+" <!-- same as the old CacheLoaderConfig attribute -->\n"
+" <properties>\n"
+" cache.jdbc.table.name=jbosscache\n"
+" cache.jdbc.table.create=true\n"
+" cache.jdbc.table.drop=true\n"
+" cache.jdbc.table.primarykey=jbosscache_pk\n"
+" cache.jdbc.fqn.column=fqn\n"
+" cache.jdbc.fqn.type=varchar(255)\n"
+" cache.jdbc.node.column=node\n"
+" cache.jdbc.node.type=blob\n"
+" cache.jdbc.parent.column=parent\n"
+" cache.jdbc.driver=oracle.jdbc.OracleDriver\n"
+" cache.jdbc.url=jdbc:oracle:thin:@localhost:1521:JBOSSDB\n"
+" cache.jdbc.user=SCOTT\n"
+" cache.jdbc.password=TIGER\n"
+" </properties>\n"
+" <!-- whether the cache loader writes are asynchronous -->\n"
+" <async>false</async>\n"
+" <!-- only one cache loader in the chain may set "
+"fetchPersistentState to true.\n"
+" An exception is thrown if more than one cache loader sets "
+"this to true. \n"
+" -->\n"
+" <fetchPersistentState>true</fetchPersistentState>\n"
+" <!-- determines whether this cache loader ignores writes - "
+"defaults to false. \n"
+" -->\n"
+" <ignoreModifications>false</ignoreModifications>\n"
+" <!-- if set to true, purges the contents of this cache loader "
+"when the cache \n"
+" starts up. Defaults to false. -->\n"
+" <purgeOnStartup>false</purgeOnStartup>\n"
+" </cacheloader>\n"
+" </config>\n"
+"</attribute>"
msgstr ""
-#: ./Cache_loaders.xml:879(para)
-msgid "As an alternative to configuring the entire JDBC connection, the name of an existing data source can be given:"
+#. Tag: para
+#: Cache_loaders.xml:453
+#, no-c-format
+msgid ""
+"As an alternative to configuring the entire JDBC connection, the name of an "
+"existing data source can be given:"
msgstr ""
-#: ./Cache_loaders.xml:882(programlisting)
-#, no-wrap
-msgid "<attribute name=\"CacheLoaderConfiguration\">\n <config>\n <passivation>false</passivation>\n <preload>/some/stuff</preload>\n <cacheloader>\n <class>org.jboss.cache.loader.JDBCCacheLoader</class>\n <!-- same as the old CacheLoaderConfig attribute -->\n <properties>\n cache.jdbc.datasource=java:/DefaultDS\n </properties>\n <!-- whether the cache loader writes are asynchronous -->\n <async>false</async>\n <!-- only one cache loader in the chain may set fetchPersistentState to true.\n An exception is thrown if more than one cache loader sets this to true. \n\t\t -->\n <fetchPersistentState>true</fetchPersistentState>\n <!-- determines whether this cache loader ignores writes - defaults to false. \n\t -->!
;\n <ignoreModifications>false</ignoreModifications>\n <!-- if set to true, purges the contents of this cache loader when the cache \n\t starts up. Defaults to false. -->\n <purgeOnStartup>false</purgeOnStartup>\n </cacheloader>\n </config>\n</attribute>\n"
+#. Tag: programlisting
+#: Cache_loaders.xml:456
+#, no-c-format
+msgid ""
+"<attribute name=\"CacheLoaderConfiguration\">\n"
+" <config>\n"
+" <passivation>false</passivation>\n"
+" <preload>/some/stuff</preload>\n"
+" <cacheloader>\n"
+" <class>org.jboss.cache.loader.JDBCCacheLoader</"
+"class>\n"
+" <!-- same as the old CacheLoaderConfig attribute -->\n"
+" <properties>\n"
+" cache.jdbc.datasource=java:/DefaultDS\n"
+" </properties>\n"
+" <!-- whether the cache loader writes are asynchronous -->\n"
+" <async>false</async>\n"
+" <!-- only one cache loader in the chain may set "
+"fetchPersistentState to true.\n"
+" An exception is thrown if more than one cache loader sets "
+"this to true. \n"
+" -->\n"
+" <fetchPersistentState>true</fetchPersistentState>\n"
+" <!-- determines whether this cache loader ignores writes - "
+"defaults to false. \n"
+" -->\n"
+" <ignoreModifications>false</ignoreModifications>\n"
+" <!-- if set to true, purges the contents of this cache loader "
+"when the cache \n"
+" starts up. Defaults to false. -->\n"
+" <purgeOnStartup>false</purgeOnStartup>\n"
+" </cacheloader>\n"
+" </config>\n"
+"</attribute>"
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Cache_loaders.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Colophon.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Colophon.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Colophon.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,68 +1,62 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:25-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ./Colophon.xml:9(title)
+#. Tag: title
+#: Colophon.xml:4
+#, no-c-format
msgid "Bibliography"
msgstr ""
-#: ./Colophon.xml:10(title)
+#. Tag: title
+#: Colophon.xml:5
+#, no-c-format
msgid "Authors"
msgstr ""
-#: ./Colophon.xml:12(honorific)
-msgid "Mr"
+#. Tag: author
+#: Colophon.xml:6
+#, no-c-format
+msgid ""
+"<honorific>Mr</honorific><firstname>Norman</firstname> <surname>Walsh</"
+"surname>"
msgstr ""
-#: ./Colophon.xml:12(firstname)
-msgid "Norman"
+#. Tag: affiliation
+#: Colophon.xml:9
+#, no-c-format
+msgid ""
+"<shortaffil>ATI</shortaffil><jobtitle>Senior Application Analyst</"
+"jobtitle><orgname>ArborText, Inc.</orgname><orgdiv>Application Developement</"
+"orgdiv>"
msgstr ""
-#: ./Colophon.xml:13(surname)
-msgid "Walsh"
-msgstr ""
-
-#: ./Colophon.xml:14(shortaffil)
-msgid "ATI"
-msgstr ""
-
-#: ./Colophon.xml:14(jobtitle)
-msgid "Senior Application Analyst"
-msgstr ""
-
-#: ./Colophon.xml:14(orgname)
-msgid "ArborText, Inc."
-msgstr ""
-
-#: ./Colophon.xml:14(orgdiv)
-msgid "Application Developement"
-msgstr ""
-
-#: ./Colophon.xml:16(title)
+#. Tag: title
+#: Colophon.xml:11
+#, no-c-format
msgid "Translator"
msgstr ""
-#: ./Colophon.xml:17(firstname)
-msgid "John"
+#. Tag: othercredit
+#: Colophon.xml:12
+#, no-c-format
+msgid "<firstname>John</firstname> <surname>Doe</surname>"
msgstr ""
-#: ./Colophon.xml:18(surname)
-msgid "Doe"
-msgstr ""
-
-#: ./Colophon.xml:19(contrib)
+#. Tag: contrib
+#: Colophon.xml:14
+#, no-c-format
msgid "Extensive review and rough drafts of Section 1.3, 1.4, and 1.5"
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Colophon.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Compatibility.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Compatibility.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Compatibility.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,36 +1,80 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:26-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ./Compatibility.xml:10(title)
+#. Tag: title
+#: Compatibility.xml:5
+#, no-c-format
msgid "Version Compatibility and Interoperability"
msgstr ""
-#: ./Compatibility.xml:11(para)
-msgid "While this is not absolutely guaranteed, generally speaking within a major version, releases of JBoss Cache are meant to be compatible and interoperable. Compatible in the sense that it should be possible to upgrade an application from one version to another by simply replacing the jars. Interoperable in the sense that if two different versions of JBoss Cache are used in the same cluster, they should be able to exchange replication and state transfer messages. Note however that interoperability requires use of the same JGroups version in all nodes in the cluster. In most cases, the version of JGroups used by a version of JBoss Cache can be upgraded."
+#. Tag: para
+#: Compatibility.xml:6
+#, no-c-format
+msgid ""
+"While this is not absolutely guaranteed, generally speaking within a major "
+"version, releases of JBoss Cache are meant to be compatible and "
+"interoperable. Compatible in the sense that it should be possible to upgrade "
+"an application from one version to another by simply replacing the jars. "
+"Interoperable in the sense that if two different versions of JBoss Cache are "
+"used in the same cluster, they should be able to exchange replication and "
+"state transfer messages. Note however that interoperability requires use of "
+"the same JGroups version in all nodes in the cluster. In most cases, the "
+"version of JGroups used by a version of JBoss Cache can be upgraded."
msgstr ""
-#: ./Compatibility.xml:14(para)
-msgid "In the 1.2.4 and 1.2.4.SP1 releases, API compatibility and interoperability with previous releases was broken. The primary purpose of the 1.2.4.SP2 release was to restore API compatibility and interoperability. Note, however, that restoring API compatibility with earlier releases meant that 1.2.4.SP2 is not completely API compatible with the other two 1.2.4 releases. If you have built applications on top of 1.2.4 or 1.2.4.SP1, please recompile before upgrading to 1.2.4.SP2 in order to be sure you have no issues."
+#. Tag: para
+#: Compatibility.xml:9
+#, no-c-format
+msgid ""
+"In the 1.2.4 and 1.2.4.SP1 releases, API compatibility and interoperability "
+"with previous releases was broken. The primary purpose of the 1.2.4.SP2 "
+"release was to restore API compatibility and interoperability. Note, "
+"however, that restoring API compatibility with earlier releases meant that "
+"1.2.4.SP2 is not completely API compatible with the other two 1.2.4 "
+"releases. If you have built applications on top of 1.2.4 or 1.2.4.SP1, "
+"please recompile before upgrading to 1.2.4.SP2 in order to be sure you have "
+"no issues."
msgstr ""
-#: ./Compatibility.xml:17(para)
-msgid "Beginning in 1.2.4.SP2, a new configuration attribute <literal>ReplicationVersion</literal> has been added. This attribute needs to be set in order to allow interoperability with previous releases. The value should be set to the release name of the version with which interoperability is desired, e.g. \"1.2.3\". If this attribute is set, the wire format of replication and state transfer messages will conform to that understood by the indicated release. This mechanism allows us to improve JBoss Cache by using more efficient wire formats while still providing a means to preserve interoperability."
+#. Tag: para
+#: Compatibility.xml:12
+#, no-c-format
+msgid ""
+"Beginning in 1.2.4.SP2, a new configuration attribute "
+"<literal>ReplicationVersion</literal> has been added. This attribute needs "
+"to be set in order to allow interoperability with previous releases. The "
+"value should be set to the release name of the version with which "
+"interoperability is desired, e.g. \"1.2.3\". If this attribute is set, the "
+"wire format of replication and state transfer messages will conform to that "
+"understood by the indicated release. This mechanism allows us to improve "
+"JBoss Cache by using more efficient wire formats while still providing a "
+"means to preserve interoperability."
msgstr ""
-#: ./Compatibility.xml:20(para)
-msgid "In a rare usage scenario, multiple different JBoss Cache instances may be operating on each node in a cluster, but not all need to interoperate with a version 1.2.3 cache, and thus some caches will not be configured with <literal>ReplicationVersion</literal> set to 1.2.3. This can cause problems with serialization of Fqn objects. If you are using this kind of configuration, are having problems and are unwilling to set <literal>ReplicationVersion</literal> to <literal>1.2.3</literal> on all caches, a workaround is to set system property <literal>jboss.cache.fqn.123compatible</literal> to <literal>true</literal>."
+#. Tag: para
+#: Compatibility.xml:15
+#, no-c-format
+msgid ""
+"In a rare usage scenario, multiple different JBoss Cache instances may be "
+"operating on each node in a cluster, but not all need to interoperate with a "
+"version 1.2.3 cache, and thus some caches will not be configured with "
+"<literal>ReplicationVersion</literal> set to 1.2.3. This can cause problems "
+"with serialization of Fqn objects. If you are using this kind of "
+"configuration, are having problems and are unwilling to set "
+"<literal>ReplicationVersion</literal> to <literal>1.2.3</literal> on all "
+"caches, a workaround is to set system property <literal>jboss.cache."
+"fqn.123compatible</literal> to <literal>true</literal>."
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Compatibility.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Configuration.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Configuration.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Configuration.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,277 +1,769 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:26-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ./Configuration.xml:10(title)
+#. Tag: title
+#: Configuration.xml:5
+#, no-c-format
msgid "Configuration"
msgstr ""
-#: ./Configuration.xml:11(para)
-msgid "All properties of the cache are configured via setters and can be retrieved via getters. This can be done either manually, or via the <literal>PropertyConfigurator</literal> and an XML file."
+#. Tag: para
+#: Configuration.xml:6
+#, no-c-format
+msgid ""
+"All properties of the cache are configured via setters and can be retrieved "
+"via getters. This can be done either manually, or via the "
+"<literal>PropertyConfigurator</literal> and an XML file."
msgstr ""
-#: ./Configuration.xml:15(title)
+#. Tag: title
+#: Configuration.xml:10
+#, no-c-format
msgid "Sample XML-Based Configuration"
msgstr ""
-#: ./Configuration.xml:16(para)
+#. Tag: para
+#: Configuration.xml:11
+#, no-c-format
msgid "A sample XML configuration file is shown below:"
msgstr ""
-#: ./Configuration.xml:19(programlisting)
-#, no-wrap
-msgid "<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n<server>\n <classpath codebase=\"./lib\" archives=\"jboss-cache.jar, jgroups.jar\" />\n\n <!-- ==================================================================== -->\n <!-- Defines TreeCache configuration -->\n <!-- ==================================================================== -->\n <mbean code=\"org.jboss.cache.TreeCache\" name=\"jboss.cache:service=TreeCache\">\n <depends>jboss:service=Naming</depends>\n <depends>jboss:service=TransactionManager</depends>\n\n\n <!-- Configure the TransactionManager -->\n <attribute name=\"TransactionManagerLookupClass\">\n org.jboss.cache.DummyTransactionManagerLookup\n </attribute>\n\n<!-- \nNode locking scheme : \nPESSIMISTIC (default)\nOPTIMISTIC \n-->\n<attribute name=\"NodeLockingScheme\">PESSIMISTIC</attrib!
ute>\n\n <!--\n Node locking isolation level : \n SERIALIZABLE\n REPEATABLE_READ (default)\n READ_COMMITTED\n READ_UNCOMMITTED\n NONE\n\n(ignored if NodeLockingScheme is OPTIMISTIC)\n -->\n <attribute name=\"IsolationLevel\">REPEATABLE_READ</attribute>\n\n <!-- Lock parent before doing node additions/removes -->\n <attribute name=\"LockParentForChildInsertRemove\">true</attribute>\n\n <!-- Valid modes are LOCAL\n REPL_ASYNC\n REPL_SYNC\n INVALIDATION_ASYNC\n INVALIDATION_SYNC\n -->\n <attribute name=\"CacheMode\">LOCAL</attribute>\n \n <!-- Whether each interceptor should have an mbean\n registered to capture and display its st!
atistics. -->\n <attribute name=\"UseInterceptorMbeans\">
true</attribute>\n\n <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a\n cluster, in order to find each other -->\n <attribute name=\"ClusterName\">JBoss-Cache-Cluster</attribute>\n\n <!-- Uncomment next three statements to enable JGroups multiplexer.\n This configuration is dependent on the JGroups multiplexer being\n registered in an MBean server such as JBossAS. -->\n <!--\n <depends>jgroups.mux:name=Multiplexer</depends>\n <attribute name=\"MultiplexerService\">jgroups.mux:name=Multiplexer</attribute>\n <attribute name=\"MultiplexerStack\">udp</attribute>\n -->\n\n <!-- JGroups protocol stack properties. ClusterConfig isn't used if the\n multiplexer is enabled and successfully initialized. -->\n <attribute name=\"ClusterConfig\">\n <config>\n <!-- UDP: if you have a multihomed machine,\n !
set the bind_addr attribute to the appropriate NIC IP address\n -->\n <!-- UDP: On Windows machines, because of the media sense feature\n being broken with multicast (even after disabling media sense)\n set the loopback attribute to true\n -->\n <UDP mcast_addr=\"228.1.2.3\" mcast_port=\"45566\" ip_ttl=\"64\" ip_mcast=\"true\"\n mcast_send_buf_size=\"150000\" mcast_recv_buf_size=\"80000\" \n\t ucast_send_buf_size=\"150000\" ucast_recv_buf_size=\"80000\"\n\t loopback=\"false\" />\n <PING timeout=\"2000\" num_initial_members=\"3\" up_thread=\"false\" \n\t down_thread=\"false\" />\n <MERGE2 min_interval=\"10000\" max_interval=\"20000\" />\n <FD shun=\"true\" up_thread=\"true\" down_thread=\"true\" />\n <VERIFY_SUSPECT timeout=\"1500\" up_thread=\"false\" down_thread=\"false\" />\n <pbcast.NAKACK gc_lag=\"50\" max_xmi!
t_size=\"8192\" \n\t retransmit_timeout=\"600,1200,2400,4800\" up_th
read=\"false\"\n down_thread=\"false\" />\n <UNICAST timeout=\"600,1200,2400\" window_size=\"100\" min_threshold=\"10\" \n\t down_thread=\"false\" />\n <pbcast.STABLE desired_avg_gossip=\"20000\" up_thread=\"false\" down_thread=\"false\" />\n <FRAG frag_size=\"8192\" down_thread=\"false\" up_thread=\"false\" />\n <pbcast.GMS join_timeout=\"5000\" join_retry_timeout=\"2000\" shun=\"true\" \n\t print_local_addr=\"true\" />\n <pbcast.STATE_TRANSFER up_thread=\"false\" down_thread=\"false\" />\n </config>\n </attribute>\n\n <!-- The max amount of time (in milliseconds) we wait until the\n initial state (ie. the contents of the cache) are retrieved from\n existing members in a clustered environment\n -->\n <attribute name=\"InitialStateRetrievalTimeout\">5000</attribute>\n\n <!-- Number of milliseconds to wait until a!
ll responses for a\n synchronous call have been received.\n -->\n <attribute name=\"SyncReplTimeout\">10000</attribute>\n\n <!-- Max number of milliseconds to wait for a lock acquisition -->\n <attribute name=\"LockAcquisitionTimeout\">15000</attribute>\n\n <!-- Name of the eviction policy class. -->\n <attribute name=\"EvictionPolicyClass\">org.jboss.cache.eviction.LRUPolicy</attribute>\n\n <!-- Specific eviction policy configurations. This is LRU -->\n <attribute name=\"EvictionPolicyConfig\">\n <config>\n <attribute name=\"wakeUpIntervalSeconds\">5</attribute>\n <!-- Cache wide default -->\n <region name=\"/_default_\">\n <attribute name=\"maxNodes\">5000</attribute>\n <attribute name=\"timeToLiveSeconds\">1000</attribute>\n <!-- Maximum time an object is kept in ca!
che regardless of idle time -->\n <attribute name=\"maxA
geSeconds\">120</attribute>\n </region>\n\n <region name=\"/org/jboss/data\">\n <attribute name=\"maxNodes\">5000</attribute>\n <attribute name=\"timeToLiveSeconds\">1000</attribute>\n </region>\n\n <region name=\"/org/jboss/test/data\">\n <attribute name=\"maxNodes\">5</attribute>\n <attribute name=\"timeToLiveSeconds\">4</attribute>\n </region>\n </config>\n </attribute>\n\n <!-- New 1.3.x cache loader config block -->\n <attribute name=\"CacheLoaderConfiguration\">\n <config>\n <!-- if passivation is true, only the first cache loader is used; \n\t\t the rest are ignored -->\n <passivation>false</passivation>\n <preload>/a/b, /allTempObjects, /some/specific/fqn</preload>\n !
<shared>false</shared>\n\n <!-- we can now have multiple cache loaders, which get chained -->\n <cacheloader>\n <class>org.jboss.cache.loader.FileCacheLoader</class>\n <!-- same as the old CacheLoaderConfig attribute -->\n <properties>\n location=/tmp/myFileStore\n </properties>\n <!-- whether the cache loader writes are asynchronous -->\n <async>false</async>\n <!-- only one cache loader in the chain may set \n\t\t fetchPersistentState \n\t\t\tto true.\n An exception is thrown if more than one cache loader \n\t\t\tsets this to \n\t\t\ttrue. -->\n <fetchPersistentState>true</fetchPersistentState>\n <!-- determines whether this cache !
loader ignores writes - \n\t\t defaults to \n\t\t\tfalse. -->
;\n <ignoreModifications>false</ignoreModifications>\n <!-- if set to true, purges the contents of this cache loader \n\t\t when the cache starts up. Defaults to false. -->\n <purgeOnStartup>false</purgeOnStartup>\n </cacheloader>\n\n <cacheloader>\n <class>org.jboss.cache.loader.JDBCCacheLoader</class>\n <!-- same as the old CacheLoaderConfig attribute -->\n <properties>\n cache.jdbc.driver=com.mysql.jdbc.Driver\n cache.jdbc.url=jdbc:mysql://localhost:3306/jbossdb\n cache.jdbc.user=root\n cache.jdbc.password=\n </properties>\n <!-- whether the cache loader writes are asynchronous -->\n <async>t!
rue</async>\n <!-- only one cache loader in the chain may set fetchPersistentState\n\t\t to true. An exception is thrown if more than one cache loader \n\t\t\tsets this to true. -->\n <fetchPersistentState>false</fetchPersistentState>\n <!-- determines whether this cache loader ignores writes - defaults \n\t\t to false. -->\n <ignoreModifications>true</ignoreModifications>\n <!-- if set to true, purges the contents of this cache loader when the \n\t\t cache starts up. Defaults to false. -->\n <purgeOnStartup>false</purgeOnStartup>\n </cacheloader>\n\n </config>\n </attribute>\n\n\n </mbean>\n</server> \n"
+#. Tag: programlisting
+#: Configuration.xml:14
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n"
+"<server>\n"
+" <classpath codebase=\"./lib\" archives=\"jboss-cache.jar, jgroups.jar"
+"\" />\n"
+"\n"
+" <!-- "
+"==================================================================== --"
+">\n"
+" <!-- Defines TreeCache "
+"configuration -->\n"
+" <!-- "
+"==================================================================== --"
+">\n"
+" <mbean code=\"org.jboss.cache.TreeCache\" name=\"jboss.cache:"
+"service=TreeCache\">\n"
+" <depends>jboss:service=Naming</depends>\n"
+" <depends>jboss:service=TransactionManager</depends>\n"
+"\n"
+"\n"
+" <!-- Configure the TransactionManager -->\n"
+" <attribute name=\"TransactionManagerLookupClass\">\n"
+" org.jboss.cache.DummyTransactionManagerLookup\n"
+" </attribute>\n"
+"\n"
+"<!-- \n"
+"Node locking scheme : \n"
+"PESSIMISTIC (default)\n"
+"OPTIMISTIC \n"
+"-->\n"
+"<attribute name=\"NodeLockingScheme\">PESSIMISTIC</attribute>\n"
+"\n"
+" <!--\n"
+" Node locking isolation level : \n"
+" SERIALIZABLE\n"
+" REPEATABLE_READ (default)\n"
+" READ_COMMITTED\n"
+" READ_UNCOMMITTED\n"
+" NONE\n"
+"\n"
+"(ignored if NodeLockingScheme is OPTIMISTIC)\n"
+" -->\n"
+" <attribute name=\"IsolationLevel\">REPEATABLE_READ</"
+"attribute>\n"
+"\n"
+" <!-- Lock parent before doing node additions/removes -->\n"
+" <attribute name=\"LockParentForChildInsertRemove\">true</"
+"attribute>\n"
+"\n"
+" <!-- Valid modes are LOCAL\n"
+" REPL_ASYNC\n"
+" REPL_SYNC\n"
+" INVALIDATION_ASYNC\n"
+" INVALIDATION_SYNC\n"
+" -->\n"
+" <attribute name=\"CacheMode\">LOCAL</attribute>\n"
+" \n"
+" <!-- Whether each interceptor should have an mbean\n"
+" registered to capture and display its statistics. -->\n"
+" <attribute name=\"UseInterceptorMbeans\">true</attribute>\n"
+"\n"
+" <!-- Name of cluster. Needs to be the same for all TreeCache nodes in "
+"a\n"
+" cluster, in order to find each other -->\n"
+" <attribute name=\"ClusterName\">JBoss-Cache-Cluster</"
+"attribute>\n"
+"\n"
+" <!-- Uncomment next three statements to enable JGroups multiplexer.\n"
+" This configuration is dependent on the JGroups multiplexer being\n"
+" registered in an MBean server such as JBossAS. -->\n"
+" <!--\n"
+" <depends>jgroups.mux:name=Multiplexer</depends>\n"
+" <attribute name=\"MultiplexerService\">jgroups.mux:"
+"name=Multiplexer</attribute>\n"
+" <attribute name=\"MultiplexerStack\">udp</attribute>\n"
+" -->\n"
+"\n"
+" <!-- JGroups protocol stack properties. ClusterConfig isn't used if "
+"the\n"
+" multiplexer is enabled and successfully initialized. -->\n"
+" <attribute name=\"ClusterConfig\">\n"
+" <config>\n"
+" <!-- UDP: if you have a multihomed machine,\n"
+" set the bind_addr attribute to the appropriate NIC IP "
+"address\n"
+" -->\n"
+" <!-- UDP: On Windows machines, because of the media sense "
+"feature\n"
+" being broken with multicast (even after disabling media "
+"sense)\n"
+" set the loopback attribute to true\n"
+" -->\n"
+" <UDP mcast_addr=\"228.1.2.3\" mcast_port=\"45566\" ip_ttl=\"64\" "
+"ip_mcast=\"true\"\n"
+" mcast_send_buf_size=\"150000\" mcast_recv_buf_size=\"80000\" \n"
+" ucast_send_buf_size=\"150000\" ucast_recv_buf_size=\"80000\"\n"
+" loopback=\"false\" />\n"
+" <PING timeout=\"2000\" num_initial_members=\"3\" up_thread=\"false"
+"\" \n"
+" down_thread=\"false\" />\n"
+" <MERGE2 min_interval=\"10000\" max_interval=\"20000\" />\n"
+" <FD shun=\"true\" up_thread=\"true\" down_thread=\"true\" />\n"
+" <VERIFY_SUSPECT timeout=\"1500\" up_thread=\"false\" down_thread="
+"\"false\" />\n"
+" <pbcast.NAKACK gc_lag=\"50\" max_xmit_size=\"8192\" \n"
+" retransmit_timeout=\"600,1200,2400,4800\" up_thread=\"false\"\n"
+" down_thread=\"false\" />\n"
+" <UNICAST timeout=\"600,1200,2400\" window_size=\"100\" "
+"min_threshold=\"10\" \n"
+" down_thread=\"false\" />\n"
+" <pbcast.STABLE desired_avg_gossip=\"20000\" up_thread=\"false\" "
+"down_thread=\"false\" />\n"
+" <FRAG frag_size=\"8192\" down_thread=\"false\" up_thread=\"false"
+"\" />\n"
+" <pbcast.GMS join_timeout=\"5000\" join_retry_timeout=\"2000\" "
+"shun=\"true\" \n"
+" print_local_addr=\"true\" />\n"
+" <pbcast.STATE_TRANSFER up_thread=\"false\" down_thread=\"false\" /"
+">\n"
+" </config>\n"
+" </attribute>\n"
+"\n"
+" <!-- The max amount of time (in milliseconds) we wait until the\n"
+" initial state (ie. the contents of the cache) are retrieved "
+"from\n"
+" existing members in a clustered environment\n"
+" -->\n"
+" <attribute name=\"InitialStateRetrievalTimeout\">5000</"
+"attribute>\n"
+"\n"
+" <!-- Number of milliseconds to wait until all responses for a\n"
+" synchronous call have been received.\n"
+" -->\n"
+" <attribute name=\"SyncReplTimeout\">10000</attribute>\n"
+"\n"
+" <!-- Max number of milliseconds to wait for a lock acquisition --"
+">\n"
+" <attribute name=\"LockAcquisitionTimeout\">15000</"
+"attribute>\n"
+"\n"
+" <!-- Name of the eviction policy class. -->\n"
+" <attribute name=\"EvictionPolicyClass\">org.jboss.cache.eviction."
+"LRUPolicy</attribute>\n"
+"\n"
+" <!-- Specific eviction policy configurations. This is LRU -->\n"
+" <attribute name=\"EvictionPolicyConfig\">\n"
+" <config>\n"
+" <attribute name=\"wakeUpIntervalSeconds\">5</attribute>\n"
+" <!-- Cache wide default -->\n"
+" <region name=\"/_default_\">\n"
+" <attribute name=\"maxNodes\">5000</attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">1000</attribute>\n"
+" <!-- Maximum time an object is kept in cache regardless of idle "
+"time -->\n"
+" <attribute name=\"maxAgeSeconds\">120</attribute>\n"
+" </region>\n"
+"\n"
+" <region name=\"/org/jboss/data\">\n"
+" <attribute name=\"maxNodes\">5000</attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">1000</attribute>\n"
+" </region>\n"
+"\n"
+" <region name=\"/org/jboss/test/data\">\n"
+" <attribute name=\"maxNodes\">5</attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">4</attribute>\n"
+" </region>\n"
+" </config>\n"
+" </attribute>\n"
+"\n"
+" <!-- New 1.3.x cache loader config block -->\n"
+" <attribute name=\"CacheLoaderConfiguration\">\n"
+" <config>\n"
+" <!-- if passivation is true, only the first cache loader "
+"is used; \n"
+" the rest are ignored -->\n"
+" <passivation>false</passivation>\n"
+" <preload>/a/b, /allTempObjects, /some/specific/fqn</"
+"preload>\n"
+" <shared>false</shared>\n"
+"\n"
+" <!-- we can now have multiple cache loaders, which get "
+"chained -->\n"
+" <cacheloader>\n"
+" <class>org.jboss.cache.loader.FileCacheLoader</"
+"class>\n"
+" <!-- same as the old CacheLoaderConfig attribute --"
+">\n"
+" <properties>\n"
+" location=/tmp/myFileStore\n"
+" </properties>\n"
+" <!-- whether the cache loader writes are asynchronous "
+"-->\n"
+" <async>false</async>\n"
+" <!-- only one cache loader in the chain may set \n"
+" fetchPersistentState \n"
+" to true.\n"
+" An exception is thrown if more than one cache "
+"loader \n"
+" sets this to \n"
+" true. -->\n"
+" <fetchPersistentState>true</"
+"fetchPersistentState>\n"
+" <!-- determines whether this cache loader ignores "
+"writes - \n"
+" defaults to \n"
+" false. -->\n"
+" <ignoreModifications>false</"
+"ignoreModifications>\n"
+" <!-- if set to true, purges the contents of this "
+"cache loader \n"
+" when the cache starts up. Defaults to false. --"
+">\n"
+" <purgeOnStartup>false</purgeOnStartup>\n"
+" </cacheloader>\n"
+"\n"
+" <cacheloader>\n"
+" <class>org.jboss.cache.loader.JDBCCacheLoader</"
+"class>\n"
+" <!-- same as the old CacheLoaderConfig attribute --"
+">\n"
+" <properties>\n"
+" cache.jdbc.driver=com.mysql.jdbc.Driver\n"
+" cache.jdbc.url=jdbc:mysql://localhost:3306/jbossdb\n"
+" cache.jdbc.user=root\n"
+" cache.jdbc.password=\n"
+" </properties>\n"
+" <!-- whether the cache loader writes are asynchronous "
+"-->\n"
+" <async>true</async>\n"
+" <!-- only one cache loader in the chain may set "
+"fetchPersistentState\n"
+" to true. An exception is thrown if more than one "
+"cache loader \n"
+" sets this to true. -->\n"
+" <fetchPersistentState>false</"
+"fetchPersistentState>\n"
+" <!-- determines whether this cache loader ignores "
+"writes - defaults \n"
+" to false. -->\n"
+" <ignoreModifications>true</"
+"ignoreModifications>\n"
+" <!-- if set to true, purges the contents of this "
+"cache loader when the \n"
+" cache starts up. Defaults to false. -->\n"
+" <purgeOnStartup>false</purgeOnStartup>\n"
+" </cacheloader>\n"
+"\n"
+" </config>\n"
+" </attribute>\n"
+"\n"
+"\n"
+" </mbean>\n"
+"</server>"
msgstr ""
-#: ./Configuration.xml:222(para)
-msgid "We will switch to using an XMBean in a future release."
+#. Tag: para
+#: Configuration.xml:15
+#, no-c-format
+msgid ""
+"The PropertyConfigurator.configure() method needs to have as argument a "
+"filename which is located on the classpath; it will use be used to configure "
+"JBoss Cache from the properties defined in it. Note that this configuration "
+"file is used to configure JBoss Cache both as a standalone cache, and as an "
+"MBean if run inside the JBoss container."
msgstr ""
-#: ./Configuration.xml:221(para)
-msgid "The PropertyConfigurator.configure() method needs to have as argument a filename which is located on the classpath; it will use be used to configure JBoss Cache from the properties defined in it. Note that this configuration file is used to configure JBoss Cache both as a standalone cache, and as an MBean if run inside the JBoss container.<placeholder-1/>"
+#. Tag: para
+#: Configuration.xml:16
+#, no-c-format
+msgid "We will switch to using an XMBean in a future release."
msgstr ""
-#: ./Configuration.xml:230(title)
+#. Tag: title
+#: Configuration.xml:24
+#, no-c-format
msgid "Definition of XML attributes"
msgstr ""
-#: ./Configuration.xml:231(para)
+#. Tag: para
+#: Configuration.xml:25
+#, no-c-format
msgid "A list of definitions of each of the XML attributes used above:"
msgstr ""
-#: ./Configuration.xml:238(para)
+#. Tag: para
+#: Configuration.xml:32
+#, no-c-format
msgid "Name"
msgstr ""
-#: ./Configuration.xml:243(para)
+#. Tag: para
+#: Configuration.xml:37
+#, no-c-format
msgid "Description"
msgstr ""
-#: ./Configuration.xml:250(para)
+#. Tag: para
+#: Configuration.xml:44
+#, no-c-format
msgid "BuddyReplicationConfig"
msgstr ""
-#: ./Configuration.xml:255(para)
-msgid "An XML element that contains detailed buddy replication configuration. See section above on Buddy Replication."
+#. Tag: para
+#: Configuration.xml:49
+#, no-c-format
+msgid ""
+"An XML element that contains detailed buddy replication configuration. See "
+"section above on Buddy Replication."
msgstr ""
-#: ./Configuration.xml:262(para)
+#. Tag: para
+#: Configuration.xml:56
+#, no-c-format
msgid "CacheLoaderConfiguration"
msgstr ""
-#: ./Configuration.xml:267(para)
-msgid "An XML element that contains detailed cache loader configuration. See section above on Cache Loaders."
+#. Tag: para
+#: Configuration.xml:61
+#, no-c-format
+msgid ""
+"An XML element that contains detailed cache loader configuration. See "
+"section above on Cache Loaders."
msgstr ""
-#: ./Configuration.xml:274(para)
+#. Tag: para
+#: Configuration.xml:68
+#, no-c-format
msgid "CacheMode"
msgstr ""
-#: ./Configuration.xml:279(para)
+#. Tag: para
+#: Configuration.xml:73
+#, no-c-format
msgid "LOCAL, REPL_SYNC, REPL_ASYNC, INVALIDATION_SYNC or INVALIDATION_ASYNC"
msgstr ""
-#: ./Configuration.xml:286(para)
+#. Tag: para
+#: Configuration.xml:80
+#, no-c-format
msgid "ClusterConfig"
msgstr ""
-#: ./Configuration.xml:291(para)
-msgid "The configuration of the underlying JGroups stack. Ignored if <literal>MultiplexerService</literal> and <literal>MultiplexerStack</literal> are used. See the various *-service.xml files in the source distribution <literal>etc/META-INF</literal> folder for examples. See the <ulink url=\"http://www.jgroups.org\">JGroups documentation</ulink> or the <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups\">JGroups wiki page</ulink> for more information."
+#. Tag: para
+#: Configuration.xml:85
+#, no-c-format
+msgid ""
+"The configuration of the underlying JGroups stack. Ignored if "
+"<literal>MultiplexerService</literal> and <literal>MultiplexerStack</"
+"literal> are used. See the various *-service.xml files in the source "
+"distribution <literal>etc/META-INF</literal> folder for examples. See the "
+"<ulink url=\"http://www.jgroups.org\">JGroups documentation</ulink> or the "
+"<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups\">JGroups wiki "
+"page</ulink> for more information."
msgstr ""
-#: ./Configuration.xml:298(para)
+#. Tag: para
+#: Configuration.xml:92
+#, no-c-format
msgid "ClusterName"
msgstr ""
-#: ./Configuration.xml:303(para)
-msgid "Name of cluster. Needs to be the same for all nodes in a cluster in order for them to communicate with each other."
+#. Tag: para
+#: Configuration.xml:97
+#, no-c-format
+msgid ""
+"Name of cluster. Needs to be the same for all nodes in a cluster in order "
+"for them to communicate with each other."
msgstr ""
-#: ./Configuration.xml:310(para)
+#. Tag: para
+#: Configuration.xml:104
+#, no-c-format
msgid "EvictionPolicyClass"
msgstr ""
-#: ./Configuration.xml:315(para)
-msgid "The name of a class implementing EvictionPolicy. Deprecated; it is preferable to configure the eviction policy class as part of the <literal>EvictionPolicyConfig</literal>."
+#. Tag: para
+#: Configuration.xml:109
+#, no-c-format
+msgid ""
+"The name of a class implementing EvictionPolicy. Deprecated; it is "
+"preferable to configure the eviction policy class as part of the "
+"<literal>EvictionPolicyConfig</literal>."
msgstr ""
-#: ./Configuration.xml:322(para)
+#. Tag: para
+#: Configuration.xml:116
+#, no-c-format
msgid "EvictionPolicyConfig"
msgstr ""
-#: ./Configuration.xml:327(para)
-msgid "Configuration parameter for the specified eviction policy. Note that the content is provider specific."
+#. Tag: para
+#: Configuration.xml:121
+#, no-c-format
+msgid ""
+"Configuration parameter for the specified eviction policy. Note that the "
+"content is provider specific."
msgstr ""
-#: ./Configuration.xml:334(para)
+#. Tag: para
+#: Configuration.xml:128
+#, no-c-format
msgid "FetchInMemoryState (renamed from FetchStateOnStartup)"
msgstr ""
-#: ./Configuration.xml:339(para)
-msgid "Whether or not to acquire the initial in-memory state from existing members. Allows for hot/cold caches (true/false). Also see the fetchPersistentState element in CacheLoaderConfiguration."
+#. Tag: para
+#: Configuration.xml:133
+#, no-c-format
+msgid ""
+"Whether or not to acquire the initial in-memory state from existing members. "
+"Allows for hot/cold caches (true/false). Also see the fetchPersistentState "
+"element in CacheLoaderConfiguration."
msgstr ""
-#: ./Configuration.xml:346(para)
+#. Tag: para
+#: Configuration.xml:140
+#, no-c-format
msgid "InactiveOnStartup"
msgstr ""
-#: ./Configuration.xml:351(para)
-msgid "Whether or not the entire tree is inactive upon startup, only responding to replication messages after <literal>activateRegion()</literal> is called to activate one or more parts of the tree. If true, property <literal>FetchInMemoryState</literal> is ignored. This property should only be set to true if <literal>UseRegionBasedMarshalling</literal> is also <literal>true</literal>."
+#. Tag: para
+#: Configuration.xml:145
+#, no-c-format
+msgid ""
+"Whether or not the entire tree is inactive upon startup, only responding to "
+"replication messages after <literal>activateRegion()</literal> is called to "
+"activate one or more parts of the tree. If true, property "
+"<literal>FetchInMemoryState</literal> is ignored. This property should only "
+"be set to true if <literal>UseRegionBasedMarshalling</literal> is also "
+"<literal>true</literal>."
msgstr ""
-#: ./Configuration.xml:358(para)
+#. Tag: para
+#: Configuration.xml:152
+#, no-c-format
msgid "InitialStateRetrievalTimeout"
msgstr ""
-#: ./Configuration.xml:363(para)
-msgid "Time in milliseconds to wait for initial state retrieval. This should be longer than <literal>LockAcquisitionTimeout</literal> as the node providing state may need to wait that long to acquire necessary read locks on the cache."
+#. Tag: para
+#: Configuration.xml:157
+#, no-c-format
+msgid ""
+"Time in milliseconds to wait for initial state retrieval. This should be "
+"longer than <literal>LockAcquisitionTimeout</literal> as the node providing "
+"state may need to wait that long to acquire necessary read locks on the "
+"cache."
msgstr ""
-#: ./Configuration.xml:370(para)
+#. Tag: para
+#: Configuration.xml:164
+#, no-c-format
msgid "IsolationLevel"
msgstr ""
-#: ./Configuration.xml:375(para)
-msgid "Node locking isolation level : SERIALIZABLE, REPEATABLE_READ (default), READ_COMMITTED, READ_UNCOMMITTED, and NONE. Note that this is ignored if NodeLockingScheme is OPTIMISTIC. Case doesn't matter. See documentation on Transactions and Concurrency for more details."
+#. Tag: para
+#: Configuration.xml:169
+#, no-c-format
+msgid ""
+"Node locking isolation level : SERIALIZABLE, REPEATABLE_READ (default), "
+"READ_COMMITTED, READ_UNCOMMITTED, and NONE. Note that this is ignored if "
+"NodeLockingScheme is OPTIMISTIC. Case doesn't matter. See documentation on "
+"Transactions and Concurrency for more details."
msgstr ""
-#: ./Configuration.xml:382(para)
+#. Tag: para
+#: Configuration.xml:176
+#, no-c-format
msgid "LockAcquisitionTimeout"
msgstr ""
-#: ./Configuration.xml:387(para)
-msgid "Time in milliseconds to wait for a lock to be acquired. If a lock cannot be acquired an exception will be thrown."
+#. Tag: para
+#: Configuration.xml:181
+#, no-c-format
+msgid ""
+"Time in milliseconds to wait for a lock to be acquired. If a lock cannot be "
+"acquired an exception will be thrown."
msgstr ""
-#: ./Configuration.xml:394(para)
+#. Tag: para
+#: Configuration.xml:188
+#, no-c-format
msgid "MultiplexerService"
msgstr ""
-#: ./Configuration.xml:399(para)
-msgid "The JMX object name of the service that defines the JGroups multiplexer. In JBoss AS 5 this service is normally defined in the jgroups-multiplexer.sar. If this attribute is defined, the cache will look up the multiplexer service in JMX and will use it to obtain a multiplexed JGroups channel. The configuration of the channel will be that associated with <literal>MultiplexerStack</literal>. The <literal>ClusterConfig</literal> attribute will be ignored."
+#. Tag: para
+#: Configuration.xml:193
+#, no-c-format
+msgid ""
+"The JMX object name of the service that defines the JGroups multiplexer. In "
+"JBoss AS 5 this service is normally defined in the jgroups-multiplexer.sar. "
+"If this attribute is defined, the cache will look up the multiplexer service "
+"in JMX and will use it to obtain a multiplexed JGroups channel. The "
+"configuration of the channel will be that associated with "
+"<literal>MultiplexerStack</literal>. The <literal>ClusterConfig</literal> "
+"attribute will be ignored."
msgstr ""
-#: ./Configuration.xml:406(para)
+#. Tag: para
+#: Configuration.xml:200
+#, no-c-format
msgid "MultiplexerStack"
msgstr ""
-#: ./Configuration.xml:411(para)
-msgid "The name of the JGroups stack to be used with the TreeCache cluster. Stacks are defined in the configuration of the external <literal>MultiplexerService</literal> discussed above. In JBoss AS 5 this is normally done in the jgroups-multiplexer.sar\\META-INF\\multiplexer-stacks.xml file. The default stack is <literal>udp</literal>. This attribute is used in conjunction with <literal>MultiplexerService</literal>."
+#. Tag: para
+#: Configuration.xml:205
+#, no-c-format
+msgid ""
+"The name of the JGroups stack to be used with the TreeCache cluster. Stacks "
+"are defined in the configuration of the external "
+"<literal>MultiplexerService</literal> discussed above. In JBoss AS 5 this is "
+"normally done in the jgroups-multiplexer.sar\META-INF\multiplexer-"
+"stacks.xml file. The default stack is <literal>udp</literal>. This attribute "
+"is used in conjunction with <literal>MultiplexerService</literal>."
msgstr ""
-#: ./Configuration.xml:418(para)
+#. Tag: para
+#: Configuration.xml:212
+#, no-c-format
msgid "NodeLockingScheme"
msgstr ""
-#: ./Configuration.xml:423(para)
-msgid "May be PESSIMISTIC (default) or OPTIMISTIC. See documentation on Transactions and Concurrency for more details."
+#. Tag: para
+#: Configuration.xml:217
+#, no-c-format
+msgid ""
+"May be PESSIMISTIC (default) or OPTIMISTIC. See documentation on "
+"Transactions and Concurrency for more details."
msgstr ""
-#: ./Configuration.xml:430(para)
+#. Tag: para
+#: Configuration.xml:224
+#, no-c-format
msgid "ReplicationVersion"
msgstr ""
-#: ./Configuration.xml:435(para)
-msgid "Tells the cache to serialize cluster traffic in a format consistent with that used by the given release of JBoss Cache. Different JBoss Cache versions use different wire formats; setting this attribute tells a cache from a later release to serialize data using the format from an earlier release. This allows caches from different releases to interoperate. For example, a 1.2.4.SP2 cache could have this value set to \"1.2.3\", allowing it to interoperate with a 1.2.3 cache. Valid values are a dot-separated release number, with any SP qualifer also separated by a dot, e.g. \"1.2.3\" or \"1.2.4.SP2\"."
+#. Tag: para
+#: Configuration.xml:229
+#, no-c-format
+msgid ""
+"Tells the cache to serialize cluster traffic in a format consistent with "
+"that used by the given release of JBoss Cache. Different JBoss Cache "
+"versions use different wire formats; setting this attribute tells a cache "
+"from a later release to serialize data using the format from an earlier "
+"release. This allows caches from different releases to interoperate. For "
+"example, a 1.2.4.SP2 cache could have this value set to \"1.2.3\", allowing "
+"it to interoperate with a 1.2.3 cache. Valid values are a dot-separated "
+"release number, with any SP qualifer also separated by a dot, e.g. \"1.2.3\" "
+"or \"1.2.4.SP2\"."
msgstr ""
-#: ./Configuration.xml:442(para)
+#. Tag: para
+#: Configuration.xml:236
+#, no-c-format
msgid "ReplQueueInterval"
msgstr ""
-#: ./Configuration.xml:447(para)
-msgid "Time in milliseconds for elements from the replication queue to be replicated."
+#. Tag: para
+#: Configuration.xml:241
+#, no-c-format
+msgid ""
+"Time in milliseconds for elements from the replication queue to be "
+"replicated."
msgstr ""
-#: ./Configuration.xml:454(para)
+#. Tag: para
+#: Configuration.xml:248
+#, no-c-format
msgid "ReplQueueMaxElements"
msgstr ""
-#: ./Configuration.xml:459(para)
-msgid "Max number of elements in the replication queue until replication kicks in."
+#. Tag: para
+#: Configuration.xml:253
+#, no-c-format
+msgid ""
+"Max number of elements in the replication queue until replication kicks in."
msgstr ""
-#: ./Configuration.xml:466(para)
+#. Tag: para
+#: Configuration.xml:260
+#, no-c-format
msgid "SyncCommitPhase"
msgstr ""
-#: ./Configuration.xml:471(para)
-msgid "This option is used to control the behaviour of the commit part of a 2-phase commit protocol, when using REPL_SYNC (does not apply to other cache modes). By default this is set to <literal>false</literal>. There is a performance penalty to enabling this, especially when running in a large cluster, but the upsides are greater cluster-wide data integrity. See the chapter on Clustered Caches for more information on this."
+#. Tag: para
+#: Configuration.xml:265
+#, no-c-format
+msgid ""
+"This option is used to control the behaviour of the commit part of a 2-phase "
+"commit protocol, when using REPL_SYNC (does not apply to other cache modes). "
+"By default this is set to <literal>false</literal>. There is a performance "
+"penalty to enabling this, especially when running in a large cluster, but "
+"the upsides are greater cluster-wide data integrity. See the chapter on "
+"Clustered Caches for more information on this."
msgstr ""
-#: ./Configuration.xml:478(para)
+#. Tag: para
+#: Configuration.xml:272
+#, no-c-format
msgid "SyncReplTimeout"
msgstr ""
-#: ./Configuration.xml:483(para)
-msgid "For synchronous replication: time in milliseconds to wait until replication acks have been received from all nodes in the cluster."
+#. Tag: para
+#: Configuration.xml:277
+#, no-c-format
+msgid ""
+"For synchronous replication: time in milliseconds to wait until replication "
+"acks have been received from all nodes in the cluster."
msgstr ""
-#: ./Configuration.xml:490(para)
+#. Tag: para
+#: Configuration.xml:284
+#, no-c-format
msgid "SyncRollbackPhase"
msgstr ""
-#: ./Configuration.xml:495(para)
-msgid "This option is used to control the behaviour of the rollback part of a 2-phase commit protocol, when using REPL_SYNC (does not apply to other cache modes). By default this is set to <literal>false</literal>. There is a performance penalty to enabling this, especially when running in a large cluster, but the upsides are greater cluster-wide data integrity. See the chapter on Clustered Caches for more information on this."
+#. Tag: para
+#: Configuration.xml:289
+#, no-c-format
+msgid ""
+"This option is used to control the behaviour of the rollback part of a 2-"
+"phase commit protocol, when using REPL_SYNC (does not apply to other cache "
+"modes). By default this is set to <literal>false</literal>. There is a "
+"performance penalty to enabling this, especially when running in a large "
+"cluster, but the upsides are greater cluster-wide data integrity. See the "
+"chapter on Clustered Caches for more information on this."
msgstr ""
-#: ./Configuration.xml:502(para)
+#. Tag: para
+#: Configuration.xml:296
+#, no-c-format
msgid "TransactionManagerLookupClass"
msgstr ""
-#: ./Configuration.xml:507(para)
-msgid "The fully qualified name of a class implementing TransactionManagerLookup. Default is JBossTransactionManagerLookup. There is also an option of DummyTransactionManagerLookup for example."
+#. Tag: para
+#: Configuration.xml:301
+#, no-c-format
+msgid ""
+"The fully qualified name of a class implementing TransactionManagerLookup. "
+"Default is JBossTransactionManagerLookup. There is also an option of "
+"DummyTransactionManagerLookup for example."
msgstr ""
-#: ./Configuration.xml:514(para)
+#. Tag: para
+#: Configuration.xml:308
+#, no-c-format
msgid "UseInterceptorMbeans"
msgstr ""
-#: ./Configuration.xml:519(para)
-msgid "Specifies whether each interceptor should have an associated mbean registered. Interceptor mbeans are used to capture statistics and display them in JMX. This setting enables or disables all such interceptor mbeans. Default value is <emphasis>true</emphasis>."
+#. Tag: para
+#: Configuration.xml:313
+#, no-c-format
+msgid ""
+"Specifies whether each interceptor should have an associated mbean "
+"registered. Interceptor mbeans are used to capture statistics and display "
+"them in JMX. This setting enables or disables all such interceptor mbeans. "
+"Default value is <emphasis>true</emphasis>."
msgstr ""
-#: ./Configuration.xml:526(para)
+#. Tag: para
+#: Configuration.xml:320
+#, no-c-format
msgid "UseRegionBasedMarshalling"
msgstr ""
-#: ./Configuration.xml:531(para)
-msgid "When unmarshalling replicated data, this option specifies whether or not to use different classloaders (for different cache regions). This defaults to <literal>false</literal> if unspecified."
+#. Tag: para
+#: Configuration.xml:325
+#, no-c-format
+msgid ""
+"When unmarshalling replicated data, this option specifies whether or not to "
+"use different classloaders (for different cache regions). This defaults to "
+"<literal>false</literal> if unspecified."
msgstr ""
-#: ./Configuration.xml:538(para)
+#. Tag: para
+#: Configuration.xml:332
+#, no-c-format
msgid "UseReplQueue"
msgstr ""
-#: ./Configuration.xml:543(para)
-msgid "For asynchronous replication: whether or not to use a replication queue (true/false)."
+#. Tag: para
+#: Configuration.xml:337
+#, no-c-format
+msgid ""
+"For asynchronous replication: whether or not to use a replication queue "
+"(true/false)."
msgstr ""
-#: ./Configuration.xml:550(para)
+#. Tag: para
+#: Configuration.xml:344
+#, no-c-format
msgid "LockParentForChildInsertRemove"
msgstr ""
-#: ./Configuration.xml:555(para)
-msgid "When used with pessimistic locking and <literal>IsolationLevel</literal> of <literal>REPEATABLE_READ</literal>, this parameter specifies whether parent nodes need to be locked for writing when adding or removing child nodes. This prevents phantom reads, providing \"stronger-than-repeatable-read\" data integrity. This defaults to <literal>false</literal> and is ignored if used with optimistic locking or other isolation levels."
+#. Tag: para
+#: Configuration.xml:349
+#, no-c-format
+msgid ""
+"When used with pessimistic locking and <literal>IsolationLevel</literal> of "
+"<literal>REPEATABLE_READ</literal>, this parameter specifies whether parent "
+"nodes need to be locked for writing when adding or removing child nodes. "
+"This prevents phantom reads, providing \"stronger-than-repeatable-read\" "
+"data integrity. This defaults to <literal>false</literal> and is ignored if "
+"used with optimistic locking or other isolation levels."
msgstr ""
-#: ./Configuration.xml:566(title)
+#. Tag: title
+#: Configuration.xml:360
+#, no-c-format
msgid "Overriding options"
msgstr ""
-#: ./Configuration.xml:567(para)
-msgid "As of JBoss Cache 1.3.0, a new API has been introduced, to allow you to override certain behaviour of the cache on a per invocation basis. This involves creating an instance of <literal>org.jboss.cache.config.Option</literal>, setting the options you wish to override on the <literal>Option</literal> object and passing it in as a parameter to overloaded versions of <literal>get()</literal>, <literal>put()</literal> and <literal>remove()</literal>. See the javadocs on the <literal>Option</literal> class for details on these options."
+#. Tag: para
+#: Configuration.xml:361
+#, no-c-format
+msgid ""
+"As of JBoss Cache 1.3.0, a new API has been introduced, to allow you to "
+"override certain behaviour of the cache on a per invocation basis. This "
+"involves creating an instance of <literal>org.jboss.cache.config.Option</"
+"literal>, setting the options you wish to override on the <literal>Option</"
+"literal> object and passing it in as a parameter to overloaded versions of "
+"<literal>get()</literal>, <literal>put()</literal> and <literal>remove()</"
+"literal>. See the javadocs on the <literal>Option</literal> class for "
+"details on these options."
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Configuration.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Eviction_policies.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Eviction_policies.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Eviction_policies.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,234 +1,1283 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:25-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Eviction_policies.xml:29(None)
-msgid "@@image: 'images/EvictionUML.png'; md5=bd586afcaf2dad0d49833aff2578f602"
-msgstr ""
-
-#: ./Eviction_policies.xml:10(title)
+#. Tag: title
+#: Eviction_policies.xml:5
+#, no-c-format
msgid "Eviction Policies"
msgstr ""
-#: ./Eviction_policies.xml:11(para)
-msgid "Eviction policies specify the behavior of a node residing inside the cache, e.g., life time and maximum numbers allowed. Memory constraints on servers mean caches cannot grow indefinitely, so policies need to be in place to restrict the size of the cache in memory."
+#. Tag: para
+#: Eviction_policies.xml:6
+#, no-c-format
+msgid ""
+"Eviction policies specify the behavior of a node residing inside the cache, "
+"e.g., life time and maximum numbers allowed. Memory constraints on servers "
+"mean caches cannot grow indefinitely, so policies need to be in place to "
+"restrict the size of the cache in memory."
msgstr ""
-#: ./Eviction_policies.xml:15(title)
+#. Tag: title
+#: Eviction_policies.xml:10
+#, no-c-format
msgid "Eviction Policy Plugin"
msgstr ""
-#: ./Eviction_policies.xml:16(para)
-msgid "The design of the JBoss Cache eviction policy framework is based on the loosely coupled observable pattern (albeit still synchronous) where the eviction region manager will register a <literal>TreeCacheListener</literal> to handle cache events and relay them back to the eviction policies. Whenever a cached node is added, removed, evicted, or visited, the eviction registered <literal>TreeCacheListener</literal> will maintain state statistics and information will be relayed to each individual Eviction Region. Each Region can define a different <literal>EvictionPolicy</literal> implementation that will know how to correlate cache add, remove, and visit events back to a defined eviction behavior. It's the policy provider's responsibility to decide when to call back the cache \"evict\" operation."
+#. Tag: para
+#: Eviction_policies.xml:11
+#, no-c-format
+msgid ""
+"The design of the JBoss Cache eviction policy framework is based on the "
+"loosely coupled observable pattern (albeit still synchronous) where the "
+"eviction region manager will register a <literal>TreeCacheListener</literal> "
+"to handle cache events and relay them back to the eviction policies. "
+"Whenever a cached node is added, removed, evicted, or visited, the eviction "
+"registered <literal>TreeCacheListener</literal> will maintain state "
+"statistics and information will be relayed to each individual Eviction "
+"Region. Each Region can define a different <literal>EvictionPolicy</literal> "
+"implementation that will know how to correlate cache add, remove, and visit "
+"events back to a defined eviction behavior. It's the policy provider's "
+"responsibility to decide when to call back the cache \"evict\" operation."
msgstr ""
-#: ./Eviction_policies.xml:19(para)
-msgid "There is a single eviction thread (timer) that will run at a configured interval. This thread will make calls into each of the policy providers and inform it of any <literal>TreeCacheListener</literal> aggregated adds, removes and visits (gets) to the cache during the configured interval. The eviction thread is responsible for kicking off the eviction policy processing (a single pass) for each configured eviction cache region."
+#. Tag: para
+#: Eviction_policies.xml:14
+#, no-c-format
+msgid ""
+"There is a single eviction thread (timer) that will run at a configured "
+"interval. This thread will make calls into each of the policy providers and "
+"inform it of any <literal>TreeCacheListener</literal> aggregated adds, "
+"removes and visits (gets) to the cache during the configured interval. The "
+"eviction thread is responsible for kicking off the eviction policy "
+"processing (a single pass) for each configured eviction cache region."
msgstr ""
-#: ./Eviction_policies.xml:22(para)
-msgid "In order to implement an eviction policy, the following interfaces must be implemented: org.jboss.cache.eviction.EvictionPolicy, org.jboss.cache.eviction.EvictionAlgorithm, org.jboss.cache.eviction.EvictionQueue and org.jboss.cache.eviction.EvictionConfiguration. When compounded together, each of these interface implementations define all the underlying mechanics necessary for a complete eviction policy implementation."
+#. Tag: para
+#: Eviction_policies.xml:17
+#, no-c-format
+msgid ""
+"In order to implement an eviction policy, the following interfaces must be "
+"implemented: org.jboss.cache.eviction.EvictionPolicy, org.jboss.cache."
+"eviction.EvictionAlgorithm, org.jboss.cache.eviction.EvictionQueue and org."
+"jboss.cache.eviction.EvictionConfiguration. When compounded together, each "
+"of these interface implementations define all the underlying mechanics "
+"necessary for a complete eviction policy implementation."
msgstr ""
-#: ./Eviction_policies.xml:26(title)
+#. Tag: title
+#: Eviction_policies.xml:21
+#, no-c-format
msgid "TreeCache eviction UML Diagram"
msgstr ""
-#: ./Eviction_policies.xml:33(programlisting)
-#, no-wrap
-msgid "public interface EvictionPolicy\n{\n /**\n * Evict a node form the underlying cache.\n *\n * @param fqn DataNode corresponds to this fqn.\n * @throws Exception\n */\n void evict(Fqn fqn) throws Exception;\n\n /**\n * Return children names as Objects\n *\n * @param fqn\n * @return Child names under given fqn\n */\n Set getChildrenNames(Fqn fqn);\n\n /**\n * Is this a leaf node?\n *\n * @param fqn\n * @return true/false if leaf node.\n */\n boolean hasChild(Fqn fqn);\n\n Object getCacheData(Fqn fqn, Object key);\n\n /**\n * Method called to configure this implementation.\n */\n void configure(TreeCache cache);\n\n /**\n * Get the associated EvictionAlgorithm used by the EvictionPolicy.\n * <p/>\n * This relationship should be 1-1.\n *\n * @return An EvictionAlgorithm implementation.\n */\n EvictionAlgorithm getEvictionAlgorithm();\n\n /**\n * The EvictionConfiguration !
implementation class used by this EvictionPolicy.\n *\n * @return EvictionConfiguration implementation class.\n */\n Class getEvictionConfigurationClass();\n\n}\n"
+#. Tag: programlisting
+#: Eviction_policies.xml:28
+#, no-c-format
+msgid ""
+"public interface EvictionPolicy\n"
+"{\n"
+" /**\n"
+" * Evict a node form the underlying cache.\n"
+" *\n"
+" * @param fqn DataNode corresponds to this fqn.\n"
+" * @throws Exception\n"
+" */\n"
+" void evict(Fqn fqn) throws Exception;\n"
+"\n"
+" /**\n"
+" * Return children names as Objects\n"
+" *\n"
+" * @param fqn\n"
+" * @return Child names under given fqn\n"
+" */\n"
+" Set getChildrenNames(Fqn fqn);\n"
+"\n"
+" /**\n"
+" * Is this a leaf node?\n"
+" *\n"
+" * @param fqn\n"
+" * @return true/false if leaf node.\n"
+" */\n"
+" boolean hasChild(Fqn fqn);\n"
+"\n"
+" Object getCacheData(Fqn fqn, Object key);\n"
+"\n"
+" /**\n"
+" * Method called to configure this implementation.\n"
+" */\n"
+" void configure(TreeCache cache);\n"
+"\n"
+" /**\n"
+" * Get the associated EvictionAlgorithm used by the EvictionPolicy.\n"
+" * <p/>\n"
+" * This relationship should be 1-1.\n"
+" *\n"
+" * @return An EvictionAlgorithm implementation.\n"
+" */\n"
+" EvictionAlgorithm getEvictionAlgorithm();\n"
+"\n"
+" /**\n"
+" * The EvictionConfiguration implementation class used by this "
+"EvictionPolicy.\n"
+" *\n"
+" * @return EvictionConfiguration implementation class.\n"
+" */\n"
+" Class getEvictionConfigurationClass();\n"
+"\n"
+"}"
msgstr ""
-#: ./Eviction_policies.xml:84(programlisting)
-#, no-wrap
-msgid "public interface EvictionAlgorithm\n{\n /**\n * Entry point for evictin algorithm. This is an api called by the EvictionTimerTask\n * to process the node events in waiting and actual pruning, if necessary.\n *\n * @param region Region that this algorithm will operate on.\n */\n void process(Region region) throws EvictionException;\n\n /**\n * Reset the whole eviction queue. Queue may needs to be reset due to corrupted state, \n * for example.\n *\n * @param region Region that this algorithm will operate on.\n */\n void resetEvictionQueue(Region region);\n\n /**\n * Get the EvictionQueue implementation used by this algorithm.\n *\n * @return the EvictionQueue implementation.\n */\n EvictionQueue getEvictionQueue();\n\n}\n \n"
+#. Tag: programlisting
+#: Eviction_policies.xml:29
+#, no-c-format
+msgid ""
+"public interface EvictionAlgorithm\n"
+"{\n"
+" /**\n"
+" * Entry point for evictin algorithm. This is an api called by the "
+"EvictionTimerTask\n"
+" * to process the node events in waiting and actual pruning, if "
+"necessary.\n"
+" *\n"
+" * @param region Region that this algorithm will operate on.\n"
+" */\n"
+" void process(Region region) throws EvictionException;\n"
+"\n"
+" /**\n"
+" * Reset the whole eviction queue. Queue may needs to be reset due to "
+"corrupted state, \n"
+" * for example.\n"
+" *\n"
+" * @param region Region that this algorithm will operate on.\n"
+" */\n"
+" void resetEvictionQueue(Region region);\n"
+"\n"
+" /**\n"
+" * Get the EvictionQueue implementation used by this algorithm.\n"
+" *\n"
+" * @return the EvictionQueue implementation.\n"
+" */\n"
+" EvictionQueue getEvictionQueue();\n"
+"\n"
+"}"
msgstr ""
-#: ./Eviction_policies.xml:112(programlisting)
-#, no-wrap
-msgid "public interface EvictionQueue\n{\n /**\n * Get the first entry in the queue.\n * <p/>\n * If there are no entries in queue, this method will return null.\n * <p/>\n * The first node returned is expected to be the first node to evict.\n *\n * @return first NodeEntry in queue.\n */\n public NodeEntry getFirstNodeEntry();\n\n /**\n * Retrieve a node entry by Fqn.\n * <p/>\n * This will return null if the entry is not found.\n *\n * @param fqn Fqn of the node entry to retrieve.\n * @return Node Entry object associated with given Fqn param.\n */\n public NodeEntry getNodeEntry(Fqn fqn);\n\n public NodeEntry getNodeEntry(String fqn);\n\n /**\n * Check if queue contains the given NodeEntry.\n *\n * @param entry NodeEntry to check for existence in queue.\n * @return true/false if NodeEntry exists in queue.\n */\n public boolean containsNodeEntry(NodeEntry entry);\n\n /**\n * Rem!
ove a NodeEntry from queue.\n * <p/>\n * If the NodeEntry does not exist in the queue, this method will return normally.\n *\n * @param entry The NodeEntry to remove from queue.\n */\n public void removeNodeEntry(NodeEntry entry);\n\n /**\n * Add a NodeEntry to the queue.\n *\n * @param entry The NodeEntry to add to queue.\n */\n public void addNodeEntry(NodeEntry entry);\n\n /**\n * Get the size of the queue.\n *\n * @return The number of items in the queue.\n */\n public int size();\n\n /**\n * Clear the queue.\n */\n public void clear();\n\n}\n \n"
+#. Tag: programlisting
+#: Eviction_policies.xml:30
+#, no-c-format
+msgid ""
+"public interface EvictionQueue\n"
+"{\n"
+" /**\n"
+" * Get the first entry in the queue.\n"
+" * <p/>\n"
+" * If there are no entries in queue, this method will return null.\n"
+" * <p/>\n"
+" * The first node returned is expected to be the first node to evict.\n"
+" *\n"
+" * @return first NodeEntry in queue.\n"
+" */\n"
+" public NodeEntry getFirstNodeEntry();\n"
+"\n"
+" /**\n"
+" * Retrieve a node entry by Fqn.\n"
+" * <p/>\n"
+" * This will return null if the entry is not found.\n"
+" *\n"
+" * @param fqn Fqn of the node entry to retrieve.\n"
+" * @return Node Entry object associated with given Fqn param.\n"
+" */\n"
+" public NodeEntry getNodeEntry(Fqn fqn);\n"
+"\n"
+" public NodeEntry getNodeEntry(String fqn);\n"
+"\n"
+" /**\n"
+" * Check if queue contains the given NodeEntry.\n"
+" *\n"
+" * @param entry NodeEntry to check for existence in queue.\n"
+" * @return true/false if NodeEntry exists in queue.\n"
+" */\n"
+" public boolean containsNodeEntry(NodeEntry entry);\n"
+"\n"
+" /**\n"
+" * Remove a NodeEntry from queue.\n"
+" * <p/>\n"
+" * If the NodeEntry does not exist in the queue, this method will return "
+"normally.\n"
+" *\n"
+" * @param entry The NodeEntry to remove from queue.\n"
+" */\n"
+" public void removeNodeEntry(NodeEntry entry);\n"
+"\n"
+" /**\n"
+" * Add a NodeEntry to the queue.\n"
+" *\n"
+" * @param entry The NodeEntry to add to queue.\n"
+" */\n"
+" public void addNodeEntry(NodeEntry entry);\n"
+"\n"
+" /**\n"
+" * Get the size of the queue.\n"
+" *\n"
+" * @return The number of items in the queue.\n"
+" */\n"
+" public int size();\n"
+"\n"
+" /**\n"
+" * Clear the queue.\n"
+" */\n"
+" public void clear();\n"
+"\n"
+"}"
msgstr ""
-#: ./Eviction_policies.xml:176(programlisting)
-#, no-wrap
-msgid "public interface EvictionConfiguration\n{\n public static final int WAKEUP_DEFAULT = 5;\n\n public static final String ATTR = \"attribute\";\n public static final String NAME = \"name\";\n\n public static final String REGION = \"region\";\n public static final String WAKEUP_INTERVAL_SECONDS = \"wakeUpIntervalSeconds\";\n public static final String MAX_NODES = \"maxNodes\";\n public static final String TIME_TO_IDLE_SECONDS = \"timeToIdleSeconds\";\n public static final String TIME_TO_LIVE_SECONDS = \"timeToLiveSeconds\";\n public static final String MAX_AGE_SECONDS = \"maxAgeSeconds\";\n public static final String MIN_NODES = \"minNodes\";\n public static final String REGION_POLICY_CLASS = \"policyClass\";\n\n /**\n * Parse the XML configuration for the given specific eviction region.\n * <p/>\n * The element parameter should contain the entire region block. An example\n * of an entire Element of the region would be:\n * &l!
t;p/>\n * <region name=\"abc\">\n * <attribute name=\"maxNodes\">10</attribute>\n * </region>\n *\n * @param element DOM element for the region. <region name=\"abc\"></region>\n * @throws ConfigureException\n */\n public void parseXMLConfig(Element element) throws ConfigureException;\n}\n"
+#. Tag: programlisting
+#: Eviction_policies.xml:31
+#, no-c-format
+msgid ""
+"public interface EvictionConfiguration\n"
+"{\n"
+" public static final int WAKEUP_DEFAULT = 5;\n"
+"\n"
+" public static final String ATTR = \"attribute\";\n"
+" public static final String NAME = \"name\";\n"
+"\n"
+" public static final String REGION = \"region\";\n"
+" public static final String WAKEUP_INTERVAL_SECONDS = "
+"\"wakeUpIntervalSeconds\";\n"
+" public static final String MAX_NODES = \"maxNodes\";\n"
+" public static final String TIME_TO_IDLE_SECONDS = \"timeToIdleSeconds\";\n"
+" public static final String TIME_TO_LIVE_SECONDS = \"timeToLiveSeconds\";\n"
+" public static final String MAX_AGE_SECONDS = \"maxAgeSeconds\";\n"
+" public static final String MIN_NODES = \"minNodes\";\n"
+" public static final String REGION_POLICY_CLASS = \"policyClass\";\n"
+"\n"
+" /**\n"
+" * Parse the XML configuration for the given specific eviction region.\n"
+" * <p/>\n"
+" * The element parameter should contain the entire region block. An "
+"example\n"
+" * of an entire Element of the region would be:\n"
+" * <p/>\n"
+" * <region name=\"abc\">\n"
+" * <attribute name=\"maxNodes\">10</attribute>\n"
+" * </region>\n"
+" *\n"
+" * @param element DOM element for the region. <region name=\"abc\">"
+"</region>\n"
+" * @throws ConfigureException\n"
+" */\n"
+" public void parseXMLConfig(Element element) throws ConfigureException;\n"
+"}"
msgstr ""
-#: ./Eviction_policies.xml:209(emphasis) ./Eviction_policies.xml:648(emphasis) ./Eviction_policies.xml:740(emphasis) ./Eviction_policies.xml:758(emphasis)
+#. Tag: emphasis
+#: Eviction_policies.xml:33 Eviction_policies.xml:55 Eviction_policies.xml:66
+#: Eviction_policies.xml:77
+#, no-c-format
msgid "Note that:"
msgstr ""
-#: ./Eviction_policies.xml:213(para)
-msgid "The EvictionConfiguration class 'parseXMLConfig(Element)' method expects only the DOM element pertaining to the region the policy is being configured for."
+#. Tag: para
+#: Eviction_policies.xml:37
+#, no-c-format
+msgid ""
+"The EvictionConfiguration class 'parseXMLConfig(Element)' method expects "
+"only the DOM element pertaining to the region the policy is being configured "
+"for."
msgstr ""
-#: ./Eviction_policies.xml:220(para)
-msgid "The EvictionConfiguration implementation should maintain getter and setter methods for configured properties pertaining to the policy used on a given cache region. (e.g. for LRUConfiguration there is a int getMaxNodes() and a setMaxNodes(int))"
+#. Tag: para
+#: Eviction_policies.xml:44
+#, no-c-format
+msgid ""
+"The EvictionConfiguration implementation should maintain getter and setter "
+"methods for configured properties pertaining to the policy used on a given "
+"cache region. (e.g. for LRUConfiguration there is a int getMaxNodes() and a "
+"setMaxNodes(int))"
msgstr ""
-#: ./Eviction_policies.xml:225(para)
-msgid "Alternatively, the implementation of a new eviction policy provider can be further simplified by extending BaseEvictionPolicy and BaseEvictionAlgorithm. Or for properly sorted EvictionAlgorithms (sorted in eviction order - see LFUAlgorithm) extending BaseSortedEvictionAlgorithm and implementing SortedEvictionQueue takes care of most of the common functionality available in a set of eviction policy provider classes"
+#. Tag: para
+#: Eviction_policies.xml:49
+#, no-c-format
+msgid ""
+"Alternatively, the implementation of a new eviction policy provider can be "
+"further simplified by extending BaseEvictionPolicy and "
+"BaseEvictionAlgorithm. Or for properly sorted EvictionAlgorithms (sorted in "
+"eviction order - see LFUAlgorithm) extending BaseSortedEvictionAlgorithm and "
+"implementing SortedEvictionQueue takes care of most of the common "
+"functionality available in a set of eviction policy provider classes"
msgstr ""
-#: ./Eviction_policies.xml:228(programlisting)
-#, no-wrap
-msgid "public abstract class BaseEvictionPolicy implements EvictionPolicy\n{\n protected static final Fqn ROOT = new Fqn(\"/\");\n\n protected TreeCache cache_;\n\n public BaseEvictionPolicy()\n {\n }\n\n /** EvictionPolicy interface implementation */\n\n /**\n * Evict the node under given Fqn from cache.\n *\n * @param fqn The fqn of a node in cache.\n * @throws Exception\n */\n public void evict(Fqn fqn) throws Exception\n {\n cache_.evict(fqn);\n }\n\n /**\n * Return a set of child names under a given Fqn.\n *\n * @param fqn Get child names for given Fqn in cache.\n * @return Set of children name as Objects\n */\n public Set getChildrenNames(Fqn fqn)\n {\n try\n {\n return cache_.getChildrenNames(fqn);\n }\n catch (CacheException e)\n {\n e.printStackTrace();\n }\n return null;\n }\n\n public boolean hasChild(Fqn fqn)\n {\n return cache_.hasChild(fqn!
);\n }\n\n public Object getCacheData(Fqn fqn, Object key)\n {\n try\n {\n return cache_.get(fqn, key);\n }\n catch (CacheException e)\n {\n e.printStackTrace();\n }\n return null;\n }\n\n public void configure(TreeCache cache)\n {\n this.cache_ = cache;\n }\n\n}\n"
+#. Tag: programlisting
+#: Eviction_policies.xml:52
+#, no-c-format
+msgid ""
+"public abstract class BaseEvictionPolicy implements EvictionPolicy\n"
+"{\n"
+" protected static final Fqn ROOT = new Fqn(\"/\");\n"
+"\n"
+" protected TreeCache cache_;\n"
+"\n"
+" public BaseEvictionPolicy()\n"
+" {\n"
+" }\n"
+"\n"
+" /** EvictionPolicy interface implementation */\n"
+"\n"
+" /**\n"
+" * Evict the node under given Fqn from cache.\n"
+" *\n"
+" * @param fqn The fqn of a node in cache.\n"
+" * @throws Exception\n"
+" */\n"
+" public void evict(Fqn fqn) throws Exception\n"
+" {\n"
+" cache_.evict(fqn);\n"
+" }\n"
+"\n"
+" /**\n"
+" * Return a set of child names under a given Fqn.\n"
+" *\n"
+" * @param fqn Get child names for given Fqn in cache.\n"
+" * @return Set of children name as Objects\n"
+" */\n"
+" public Set getChildrenNames(Fqn fqn)\n"
+" {\n"
+" try\n"
+" {\n"
+" return cache_.getChildrenNames(fqn);\n"
+" }\n"
+" catch (CacheException e)\n"
+" {\n"
+" e.printStackTrace();\n"
+" }\n"
+" return null;\n"
+" }\n"
+"\n"
+" public boolean hasChild(Fqn fqn)\n"
+" {\n"
+" return cache_.hasChild(fqn);\n"
+" }\n"
+"\n"
+" public Object getCacheData(Fqn fqn, Object key)\n"
+" {\n"
+" try\n"
+" {\n"
+" return cache_.get(fqn, key);\n"
+" }\n"
+" catch (CacheException e)\n"
+" {\n"
+" e.printStackTrace();\n"
+" }\n"
+" return null;\n"
+" }\n"
+"\n"
+" public void configure(TreeCache cache)\n"
+" {\n"
+" this.cache_ = cache;\n"
+" }\n"
+"\n"
+"}"
msgstr ""
-#: ./Eviction_policies.xml:295(programlisting)
-#, no-wrap
-msgid "public abstract class BaseEvictionAlgorithm implements EvictionAlgorithm\n{\n private static final Log log = LogFactory.getLog(BaseEvictionAlgorithm.class);\n\n protected Region region;\n protected BoundedBuffer recycleQueue;\n protected EvictionQueue evictionQueue;\n\n /**\n * This method will create an EvictionQueue implementation and prepare it for use.\n *\n * @param region Region to setup an eviction queue for.\n * @return The created EvictionQueue to be used as the eviction queue for this algorithm.\n * @throws EvictionException\n * @see EvictionQueue\n */\n protected abstract EvictionQueue setupEvictionQueue(Region region) throws EvictionException;\n\n /**\n * This method will check whether the given node should be evicted or not.\n *\n * @param ne NodeEntry to test eviction for.\n * @return True if the given node should be evicted. False if the given node should not \n * be evicted.\n */\n protected abstr!
act boolean shouldEvictNode(NodeEntry ne);\n\n protected BaseEvictionAlgorithm()\n {\n recycleQueue = new BoundedBuffer();\n }\n\n protected void initialize(Region region) throws EvictionException\n {\n this.region = region;\n evictionQueue = setupEvictionQueue(region);\n }\n\n /**\n * Process the given region.\n * <p/>\n * Eviction Processing encompasses the following:\n * <p/>\n * - Add/Remove/Visit Nodes\n * - Prune according to Eviction Algorithm\n * - Empty/Retry the recycle queue of previously evicted but locked (during actual \n * cache eviction) \n *nodes.\n *\n * @param region Cache region to process for eviction.\n * @throws EvictionException\n */\n public void process(Region region) throws EvictionException\n {\n if (this.region == null)\n {\n this.initialize(region);\n }\n\n this.processQueues(region);\n this.emptyRecycleQueue();\n this.prune!
();\n }\n\n public void resetEvictionQueue(Region region)\n {\n
}\n\n /**\n * Get the underlying EvictionQueue implementation.\n *\n * @return the EvictionQueue used by this algorithm\n * @see EvictionQueue\n */\n public EvictionQueue getEvictionQueue()\n {\n return this.evictionQueue;\n }\n\n /**\n * Event processing for Evict/Add/Visiting of nodes.\n * <p/>\n * - On AddEvents a new element is added into the eviction queue\n * - On RemoveEvents, the removed element is removed from the eviction queue.\n * - On VisitEvents, the visited node has its eviction statistics updated (idleTime, \n * numberOfNodeVisists, etc..)\n *\n * @param region Cache region to process for eviction.\n * @throws EvictionException\n */\n protected void processQueues(Region region) throws EvictionException\n {\n EvictedEventNode node;\n int count = 0;\n while ((node = region.takeLastEventNode()) != null)\n {\n int eventType = node.getEvent();\n Fqn fqn = no!
de.getFqn();\n\n count++;\n switch (eventType)\n {\n case EvictedEventNode.ADD_EVENT:\n this.processAddedNodes(fqn);\n break;\n case EvictedEventNode.REMOVE_EVENT:\n this.processRemovedNodes(fqn);\n break;\n case EvictedEventNode.VISIT_EVENT:\n this.processVisitedNodes(fqn);\n break;\n default:\n throw new RuntimeException(\"Illegal Eviction Event type \" + eventType);\n }\n }\n\n if (log.isTraceEnabled())\n {\n log.trace(\"processed \" + count + \" node events\");\n }\n\n }\n\n protected void evict(NodeEntry ne)\n {\n// NodeEntry ne = evictionQueue.getNodeEntry(fqn);\n if (ne != null)\n {\n evictionQueue.removeNodeEntry(ne);\n if (!this.evictCacheNode(ne.getFqn()))\n {\n try\n {\n recycleQueue.p!
ut(ne);\n }\n catch (InterruptedException e)\n
{\n e.printStackTrace();\n }\n }\n }\n }\n\n /**\n * Evict a node from cache.\n *\n * @param fqn node corresponds to this fqn\n * @return True if successful\n */\n protected boolean evictCacheNode(Fqn fqn)\n {\n if (log.isTraceEnabled())\n {\n log.trace(\"Attempting to evict cache node with fqn of \" + fqn);\n }\n EvictionPolicy policy = region.getEvictionPolicy();\n // Do an eviction of this node\n\n try\n {\n policy.evict(fqn);\n }\n catch (Exception e)\n {\n if (e instanceof TimeoutException)\n {\n log.warn(\"eviction of \" + fqn + \" timed out. Will retry later.\");\n return false;\n }\n e.printStackTrace();\n return false;\n }\n\n if (log.isTraceEnabled())\n {\n log.trace(\"Eviction of cache node with fqn of \" + fqn + \" successful\");\n }\n\n !
return true;\n }\n\n /**\n * Process an Added cache node.\n *\n * @param fqn FQN of the added node.\n * @throws EvictionException\n */\n protected void processAddedNodes(Fqn fqn) throws EvictionException\n {\n if (log.isTraceEnabled())\n {\n log.trace(\"Adding node \" + fqn + \" to eviction queue\");\n }\n\n long stamp = System.currentTimeMillis();\n NodeEntry ne = new NodeEntry(fqn);\n ne.setModifiedTimeStamp(stamp);\n ne.setNumberOfNodeVisits(1);\n // add it to the node map and eviction queue\n if (evictionQueue.containsNodeEntry(ne))\n {\n if (log.isTraceEnabled())\n {\n log.trace(\"Queue already contains \" + ne.getFqn() + \" processing it as visited\");\n }\n this.processVisitedNodes(ne.getFqn());\n return;\n }\n\n evictionQueue.addNodeEntry(ne);\n\n if (log.isTraceEnabled())\n {\n log.trace(ne.getFqn() + \" !
added successfully to eviction queue\");\n }\n }\n\n /**\n
* Remove a node from cache.\n * \n * This method will remove the node from the eviction queue as well as\n * evict the node from cache.\n * \n * If a node cannot be removed from cache, this method will remove it from the\n * eviction queue and place the element into the recycleQueue. Each node in the recycle \n * queue will get retried until proper cache eviction has taken place.\n * \n * Because EvictionQueues are collections, when iterating them from an iterator, use \n * iterator.remove() to avoid ConcurrentModificationExceptions. Use the boolean \n * parameter to indicate the calling context.\n *\n * @param fqn FQN of the removed node\n * @throws EvictionException\n */\n protected void processRemovedNodes(Fqn fqn) throws EvictionException\n {\n if (log.isTraceEnabled())\n {\n log.trace(\"Removing node \" + fqn + \" from eviction queue and attempting eviction\");\n }\n\n NodeEntry ne = evictionQ!
ueue.getNodeEntry(fqn);\n if (ne != null)\n {\n evictionQueue.removeNodeEntry(ne);\n }\n\n if (log.isTraceEnabled())\n {\n log.trace(fqn + \" removed from eviction queue\");\n }\n }\n\n /**\n * Visit a node in cache.\n * <p/>\n * This method will update the numVisits and modifiedTimestamp properties of the Node.\n * These properties are used as statistics to determine eviction (LRU, LFU, MRU, etc..)\n * <p/>\n * *Note* that this method updates Node Entries by reference and does not put them back\n * into the queue. For some sorted collections, a remove, and a re-add is required to\n * maintain the sorted order of the elements.\n *\n * @param fqn FQN of the visited node.\n * @throws EvictionException\n */\n protected void processVisitedNodes(Fqn fqn) throws EvictionException\n {\n NodeEntry ne = evictionQueue.getNodeEntry(fqn);\n if (ne == null)\n {\n !
this.processAddedNodes(fqn);\n return;\n }\n // note
this method will visit and modify the node statistics by reference!\n // if a collection is only guaranteed sort order by adding to the collection,\n // this implementation will not guarantee sort order.\n ne.setNumberOfNodeVisits(ne.getNumberOfNodeVisits() + 1);\n ne.setModifiedTimeStamp(System.currentTimeMillis());\n }\n\n /**\n * Empty the Recycle Queue.\n * <p/>\n * This method will go through the recycle queue and retry to evict the nodes from cache.\n *\n * @throws EvictionException\n */\n protected void emptyRecycleQueue() throws EvictionException\n {\n while (true)\n {\n Fqn fqn;\n\n try\n {\n fqn = (Fqn) recycleQueue.poll(0);\n }\n catch (InterruptedException e)\n {\n e.printStackTrace();\n break;\n }\n\n if (fqn == null)\n {\n if (log.isTraceEnabled())\n {\n log.tr!
ace(\"Recycle queue is empty\");\n }\n break;\n }\n\n if (log.isTraceEnabled())\n {\n log.trace(\"emptying recycle bin. Evict node \" + fqn);\n }\n\n // Still doesn't work\n if (!evictCacheNode(fqn))\n {\n try\n {\n recycleQueue.put(fqn);\n }\n catch (InterruptedException e)\n {\n e.printStackTrace();\n }\n break;\n }\n }\n }\n\n protected void prune() throws EvictionException\n {\n NodeEntry entry;\n while ((entry = evictionQueue.getFirstNodeEntry()) != null)\n {\n if (this.shouldEvictNode(entry))\n {\n this.evict(entry);\n }\n else\n {\n break;\n }\n }\n }\n\n}\n"
+#. Tag: programlisting
+#: Eviction_policies.xml:53
+#, no-c-format
+msgid ""
+"public abstract class BaseEvictionAlgorithm implements EvictionAlgorithm\n"
+"{\n"
+" private static final Log log = LogFactory.getLog(BaseEvictionAlgorithm."
+"class);\n"
+"\n"
+" protected Region region;\n"
+" protected BoundedBuffer recycleQueue;\n"
+" protected EvictionQueue evictionQueue;\n"
+"\n"
+" /**\n"
+" * This method will create an EvictionQueue implementation and prepare it "
+"for use.\n"
+" *\n"
+" * @param region Region to setup an eviction queue for.\n"
+" * @return The created EvictionQueue to be used as the eviction queue for "
+"this algorithm.\n"
+" * @throws EvictionException\n"
+" * @see EvictionQueue\n"
+" */\n"
+" protected abstract EvictionQueue setupEvictionQueue(Region region) throws "
+"EvictionException;\n"
+"\n"
+" /**\n"
+" * This method will check whether the given node should be evicted or "
+"not.\n"
+" *\n"
+" * @param ne NodeEntry to test eviction for.\n"
+" * @return True if the given node should be evicted. False if the given "
+"node should not \n"
+" * be evicted.\n"
+" */\n"
+" protected abstract boolean shouldEvictNode(NodeEntry ne);\n"
+"\n"
+" protected BaseEvictionAlgorithm()\n"
+" {\n"
+" recycleQueue = new BoundedBuffer();\n"
+" }\n"
+"\n"
+" protected void initialize(Region region) throws EvictionException\n"
+" {\n"
+" this.region = region;\n"
+" evictionQueue = setupEvictionQueue(region);\n"
+" }\n"
+"\n"
+" /**\n"
+" * Process the given region.\n"
+" * <p/>\n"
+" * Eviction Processing encompasses the following:\n"
+" * <p/>\n"
+" * - Add/Remove/Visit Nodes\n"
+" * - Prune according to Eviction Algorithm\n"
+" * - Empty/Retry the recycle queue of previously evicted but locked "
+"(during actual \n"
+" * cache eviction) \n"
+" *nodes.\n"
+" *\n"
+" * @param region Cache region to process for eviction.\n"
+" * @throws EvictionException\n"
+" */\n"
+" public void process(Region region) throws EvictionException\n"
+" {\n"
+" if (this.region == null)\n"
+" {\n"
+" this.initialize(region);\n"
+" }\n"
+"\n"
+" this.processQueues(region);\n"
+" this.emptyRecycleQueue();\n"
+" this.prune();\n"
+" }\n"
+"\n"
+" public void resetEvictionQueue(Region region)\n"
+" {\n"
+" }\n"
+"\n"
+" /**\n"
+" * Get the underlying EvictionQueue implementation.\n"
+" *\n"
+" * @return the EvictionQueue used by this algorithm\n"
+" * @see EvictionQueue\n"
+" */\n"
+" public EvictionQueue getEvictionQueue()\n"
+" {\n"
+" return this.evictionQueue;\n"
+" }\n"
+"\n"
+" /**\n"
+" * Event processing for Evict/Add/Visiting of nodes.\n"
+" * <p/>\n"
+" * - On AddEvents a new element is added into the eviction queue\n"
+" * - On RemoveEvents, the removed element is removed from the eviction "
+"queue.\n"
+" * - On VisitEvents, the visited node has its eviction statistics updated "
+"(idleTime, \n"
+" * numberOfNodeVisists, etc..)\n"
+" *\n"
+" * @param region Cache region to process for eviction.\n"
+" * @throws EvictionException\n"
+" */\n"
+" protected void processQueues(Region region) throws EvictionException\n"
+" {\n"
+" EvictedEventNode node;\n"
+" int count = 0;\n"
+" while ((node = region.takeLastEventNode()) != null)\n"
+" {\n"
+" int eventType = node.getEvent();\n"
+" Fqn fqn = node.getFqn();\n"
+"\n"
+" count++;\n"
+" switch (eventType)\n"
+" {\n"
+" case EvictedEventNode.ADD_EVENT:\n"
+" this.processAddedNodes(fqn);\n"
+" break;\n"
+" case EvictedEventNode.REMOVE_EVENT:\n"
+" this.processRemovedNodes(fqn);\n"
+" break;\n"
+" case EvictedEventNode.VISIT_EVENT:\n"
+" this.processVisitedNodes(fqn);\n"
+" break;\n"
+" default:\n"
+" throw new RuntimeException(\"Illegal Eviction Event type \" + "
+"eventType);\n"
+" }\n"
+" }\n"
+"\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"processed \" + count + \" node events\");\n"
+" }\n"
+"\n"
+" }\n"
+"\n"
+" protected void evict(NodeEntry ne)\n"
+" {\n"
+"// NodeEntry ne = evictionQueue.getNodeEntry(fqn);\n"
+" if (ne != null)\n"
+" {\n"
+" evictionQueue.removeNodeEntry(ne);\n"
+" if (!this.evictCacheNode(ne.getFqn()))\n"
+" {\n"
+" try\n"
+" {\n"
+" recycleQueue.put(ne);\n"
+" }\n"
+" catch (InterruptedException e)\n"
+" {\n"
+" e.printStackTrace();\n"
+" }\n"
+" }\n"
+" }\n"
+" }\n"
+"\n"
+" /**\n"
+" * Evict a node from cache.\n"
+" *\n"
+" * @param fqn node corresponds to this fqn\n"
+" * @return True if successful\n"
+" */\n"
+" protected boolean evictCacheNode(Fqn fqn)\n"
+" {\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"Attempting to evict cache node with fqn of \" + fqn);\n"
+" }\n"
+" EvictionPolicy policy = region.getEvictionPolicy();\n"
+" // Do an eviction of this node\n"
+"\n"
+" try\n"
+" {\n"
+" policy.evict(fqn);\n"
+" }\n"
+" catch (Exception e)\n"
+" {\n"
+" if (e instanceof TimeoutException)\n"
+" {\n"
+" log.warn(\"eviction of \" + fqn + \" timed out. Will retry later."
+"\");\n"
+" return false;\n"
+" }\n"
+" e.printStackTrace();\n"
+" return false;\n"
+" }\n"
+"\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"Eviction of cache node with fqn of \" + fqn + \" "
+"successful\");\n"
+" }\n"
+"\n"
+" return true;\n"
+" }\n"
+"\n"
+" /**\n"
+" * Process an Added cache node.\n"
+" *\n"
+" * @param fqn FQN of the added node.\n"
+" * @throws EvictionException\n"
+" */\n"
+" protected void processAddedNodes(Fqn fqn) throws EvictionException\n"
+" {\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"Adding node \" + fqn + \" to eviction queue\");\n"
+" }\n"
+"\n"
+" long stamp = System.currentTimeMillis();\n"
+" NodeEntry ne = new NodeEntry(fqn);\n"
+" ne.setModifiedTimeStamp(stamp);\n"
+" ne.setNumberOfNodeVisits(1);\n"
+" // add it to the node map and eviction queue\n"
+" if (evictionQueue.containsNodeEntry(ne))\n"
+" {\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"Queue already contains \" + ne.getFqn() + \" "
+"processing it as visited\");\n"
+" }\n"
+" this.processVisitedNodes(ne.getFqn());\n"
+" return;\n"
+" }\n"
+"\n"
+" evictionQueue.addNodeEntry(ne);\n"
+"\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(ne.getFqn() + \" added successfully to eviction queue"
+"\");\n"
+" }\n"
+" }\n"
+"\n"
+" /**\n"
+" * Remove a node from cache.\n"
+" * \n"
+" * This method will remove the node from the eviction queue as well as\n"
+" * evict the node from cache.\n"
+" * \n"
+" * If a node cannot be removed from cache, this method will remove it "
+"from the\n"
+" * eviction queue and place the element into the recycleQueue. Each node "
+"in the recycle \n"
+" * queue will get retried until proper cache eviction has taken place.\n"
+" * \n"
+" * Because EvictionQueues are collections, when iterating them from an "
+"iterator, use \n"
+" * iterator.remove() to avoid ConcurrentModificationExceptions. Use the "
+"boolean \n"
+" * parameter to indicate the calling context.\n"
+" *\n"
+" * @param fqn FQN of the removed node\n"
+" * @throws EvictionException\n"
+" */\n"
+" protected void processRemovedNodes(Fqn fqn) throws EvictionException\n"
+" {\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"Removing node \" + fqn + \" from eviction queue and "
+"attempting eviction\");\n"
+" }\n"
+"\n"
+" NodeEntry ne = evictionQueue.getNodeEntry(fqn);\n"
+" if (ne != null)\n"
+" {\n"
+" evictionQueue.removeNodeEntry(ne);\n"
+" }\n"
+"\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(fqn + \" removed from eviction queue\");\n"
+" }\n"
+" }\n"
+"\n"
+" /**\n"
+" * Visit a node in cache.\n"
+" * <p/>\n"
+" * This method will update the numVisits and modifiedTimestamp properties "
+"of the Node.\n"
+" * These properties are used as statistics to determine eviction (LRU, "
+"LFU, MRU, etc..)\n"
+" * <p/>\n"
+" * *Note* that this method updates Node Entries by reference and does not "
+"put them back\n"
+" * into the queue. For some sorted collections, a remove, and a re-add is "
+"required to\n"
+" * maintain the sorted order of the elements.\n"
+" *\n"
+" * @param fqn FQN of the visited node.\n"
+" * @throws EvictionException\n"
+" */\n"
+" protected void processVisitedNodes(Fqn fqn) throws EvictionException\n"
+" {\n"
+" NodeEntry ne = evictionQueue.getNodeEntry(fqn);\n"
+" if (ne == null)\n"
+" {\n"
+" this.processAddedNodes(fqn);\n"
+" return;\n"
+" }\n"
+" // note this method will visit and modify the node statistics by "
+"reference!\n"
+" // if a collection is only guaranteed sort order by adding to the "
+"collection,\n"
+" // this implementation will not guarantee sort order.\n"
+" ne.setNumberOfNodeVisits(ne.getNumberOfNodeVisits() + 1);\n"
+" ne.setModifiedTimeStamp(System.currentTimeMillis());\n"
+" }\n"
+"\n"
+" /**\n"
+" * Empty the Recycle Queue.\n"
+" * <p/>\n"
+" * This method will go through the recycle queue and retry to evict the "
+"nodes from cache.\n"
+" *\n"
+" * @throws EvictionException\n"
+" */\n"
+" protected void emptyRecycleQueue() throws EvictionException\n"
+" {\n"
+" while (true)\n"
+" {\n"
+" Fqn fqn;\n"
+"\n"
+" try\n"
+" {\n"
+" fqn = (Fqn) recycleQueue.poll(0);\n"
+" }\n"
+" catch (InterruptedException e)\n"
+" {\n"
+" e.printStackTrace();\n"
+" break;\n"
+" }\n"
+"\n"
+" if (fqn == null)\n"
+" {\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"Recycle queue is empty\");\n"
+" }\n"
+" break;\n"
+" }\n"
+"\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"emptying recycle bin. Evict node \" + fqn);\n"
+" }\n"
+"\n"
+" // Still doesn't work\n"
+" if (!evictCacheNode(fqn))\n"
+" {\n"
+" try\n"
+" {\n"
+" recycleQueue.put(fqn);\n"
+" }\n"
+" catch (InterruptedException e)\n"
+" {\n"
+" e.printStackTrace();\n"
+" }\n"
+" break;\n"
+" }\n"
+" }\n"
+" }\n"
+"\n"
+" protected void prune() throws EvictionException\n"
+" {\n"
+" NodeEntry entry;\n"
+" while ((entry = evictionQueue.getFirstNodeEntry()) != null)\n"
+" {\n"
+" if (this.shouldEvictNode(entry))\n"
+" {\n"
+" this.evict(entry);\n"
+" }\n"
+" else\n"
+" {\n"
+" break;\n"
+" }\n"
+" }\n"
+" }\n"
+"\n"
+"}"
msgstr ""
-#: ./Eviction_policies.xml:652(para)
-msgid "The BaseEvictionAlgorithm class maintains a processing structure. It will process the ADD, REMOVE, and VISIT events queued by the Region (events are originated from the EvictionTreeCacheListener) first. It also maintains an collection of items that were not properly evicted during the last go around because of held locks. That list is pruned. Finally, the EvictionQueue itself is pruned for entries that should be evicted based upon the configured eviction rules for the region."
+#. Tag: para
+#: Eviction_policies.xml:59
+#, no-c-format
+msgid ""
+"The BaseEvictionAlgorithm class maintains a processing structure. It will "
+"process the ADD, REMOVE, and VISIT events queued by the Region (events are "
+"originated from the EvictionTreeCacheListener) first. It also maintains an "
+"collection of items that were not properly evicted during the last go around "
+"because of held locks. That list is pruned. Finally, the EvictionQueue "
+"itself is pruned for entries that should be evicted based upon the "
+"configured eviction rules for the region."
msgstr ""
-#: ./Eviction_policies.xml:657(programlisting)
-#, no-wrap
-msgid "\n public abstract class BaseSortedEvictionAlgorithm extends BaseEvictionAlgorithm \n implements EvictionAlgorithm\n {\n private static final Log log = LogFactory.getLog(BaseSortedEvictionAlgorithm.class);\n\n public void process(Region region) throws EvictionException\n {\n super.process(region);\n }\n\n protected void processQueues(Region region) throws EvictionException\n {\n boolean evictionNodesModified = false;\n\n EvictedEventNode node;\n int count = 0;\n while ((node = region.takeLastEventNode()) != null)\n {\n int eventType = node.getEvent();\n Fqn fqn = node.getFqn();\n\n count++;\n switch (eventType)\n {\n case EvictedEventNode.ADD_EVENT:\n this.processAddedNodes(fqn);\n evictionNodesModified = true;\n break;\n case EvictedEventNode.REMOVE_EV!
ENT:\n this.processRemovedNodes(fqn);\n break;\n case EvictedEventNode.VISIT_EVENT:\n this.processVisitedNodes(fqn);\n evictionNodesModified = true;\n break;\n default:\n throw new RuntimeException(\"Illegal Eviction Event type \" + eventType);\n }\n }\n\n if (log.isTraceEnabled())\n {\n log.trace(\"Eviction nodes visited or added requires resort of queue \" +\n\t evictionNodesModified);\n }\n\n this.resortEvictionQueue(evictionNodesModified);\n\n\n if (log.isTraceEnabled())\n {\n log.trace(\"processed \" + count + \" node events\");\n }\n\n }\n\n /**\n * This method is called to resort the queue after add or visit events have occurred.\n * \n * If the parameter is true, the queue needs to be resorted. If it is false, th!
e queue \n * does not need resorting.\n *\n * @param
evictionQueueModified True if the queue was added to or visisted during event \n * processing.\n */\n protected void resortEvictionQueue(boolean evictionQueueModified)\n {\n long begin = System.currentTimeMillis();\n ((SortedEvictionQueue) evictionQueue).resortEvictionQueue();\n long end = System.currentTimeMillis();\n\n if (log.isTraceEnabled())\n {\n long diff = end - begin;\n log.trace(\"Took \" + diff + \"ms to sort queue with \" + getEvictionQueue().size()\n\t + \" elements\");\n }\n }\n\n }\n"
+#. Tag: programlisting
+#: Eviction_policies.xml:64
+#, no-c-format
+msgid ""
+"public abstract class BaseSortedEvictionAlgorithm extends "
+"BaseEvictionAlgorithm \n"
+" implements EvictionAlgorithm\n"
+" {\n"
+" private static final Log log = LogFactory.getLog"
+"(BaseSortedEvictionAlgorithm.class);\n"
+"\n"
+" public void process(Region region) throws EvictionException\n"
+" {\n"
+" super.process(region);\n"
+" }\n"
+"\n"
+" protected void processQueues(Region region) throws EvictionException\n"
+" {\n"
+" boolean evictionNodesModified = false;\n"
+"\n"
+" EvictedEventNode node;\n"
+" int count = 0;\n"
+" while ((node = region.takeLastEventNode()) != null)\n"
+" {\n"
+" int eventType = node.getEvent();\n"
+" Fqn fqn = node.getFqn();\n"
+"\n"
+" count++;\n"
+" switch (eventType)\n"
+" {\n"
+" case EvictedEventNode.ADD_EVENT:\n"
+" this.processAddedNodes(fqn);\n"
+" evictionNodesModified = true;\n"
+" break;\n"
+" case EvictedEventNode.REMOVE_EVENT:\n"
+" this.processRemovedNodes(fqn);\n"
+" break;\n"
+" case EvictedEventNode.VISIT_EVENT:\n"
+" this.processVisitedNodes(fqn);\n"
+" evictionNodesModified = true;\n"
+" break;\n"
+" default:\n"
+" throw new RuntimeException(\"Illegal Eviction Event type "
+"\" + eventType);\n"
+" }\n"
+" }\n"
+"\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"Eviction nodes visited or added requires resort of "
+"queue \" +\n"
+" evictionNodesModified);\n"
+" }\n"
+"\n"
+" this.resortEvictionQueue(evictionNodesModified);\n"
+"\n"
+"\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" log.trace(\"processed \" + count + \" node events\");\n"
+" }\n"
+"\n"
+" }\n"
+"\n"
+" /**\n"
+" * This method is called to resort the queue after add or visit events "
+"have occurred.\n"
+" * \n"
+" * If the parameter is true, the queue needs to be resorted. If it is "
+"false, the queue \n"
+" * does not need resorting.\n"
+" *\n"
+" * @param evictionQueueModified True if the queue was added to or "
+"visisted during event \n"
+" * processing.\n"
+" */\n"
+" protected void resortEvictionQueue(boolean evictionQueueModified)\n"
+" {\n"
+" long begin = System.currentTimeMillis();\n"
+" ((SortedEvictionQueue) evictionQueue).resortEvictionQueue();\n"
+" long end = System.currentTimeMillis();\n"
+"\n"
+" if (log.isTraceEnabled())\n"
+" {\n"
+" long diff = end - begin;\n"
+" log.trace(\"Took \" + diff + \"ms to sort queue with \" + "
+"getEvictionQueue().size()\n"
+" + \" elements\");\n"
+" }\n"
+" }\n"
+"\n"
+" }"
msgstr ""
-#: ./Eviction_policies.xml:744(para)
-msgid "The BaseSortedEvictionAlgorithm class will maintain a boolean through the algorithm processing that will determine if any new nodes were added or visited. This allows the Algorithm to determine whether to resort the eviction queue items (in first to evict order) or to skip the potentially expensive sorting if there have been no changes to the cache in this region."
+#. Tag: para
+#: Eviction_policies.xml:70
+#, no-c-format
+msgid ""
+"The BaseSortedEvictionAlgorithm class will maintain a boolean through the "
+"algorithm processing that will determine if any new nodes were added or "
+"visited. This allows the Algorithm to determine whether to resort the "
+"eviction queue items (in first to evict order) or to skip the potentially "
+"expensive sorting if there have been no changes to the cache in this region."
msgstr ""
-#: ./Eviction_policies.xml:749(programlisting)
-#, no-wrap
-msgid "public interface SortedEvictionQueue extends EvictionQueue\n{\n /**\n * Provide contract to resort a sorted queue.\n */\n public void resortEvictionQueue();\n}\n"
+#. Tag: programlisting
+#: Eviction_policies.xml:75
+#, no-c-format
+msgid ""
+"public interface SortedEvictionQueue extends EvictionQueue\n"
+"{\n"
+" /**\n"
+" * Provide contract to resort a sorted queue.\n"
+" */\n"
+" public void resortEvictionQueue();\n"
+"}"
msgstr ""
-#: ./Eviction_policies.xml:762(para)
-msgid "The SortedEvictionQueue interface defines the contract used by the BaseSortedEvictionAlgorithm abstract class that is used to resort the underlying queue. Again, the queue sorting should be sorted in first to evict order. The first entry in the list should evict before the last entry in the queue. The last entry in the queue should be the last entry that will require eviction."
+#. Tag: para
+#: Eviction_policies.xml:81
+#, no-c-format
+msgid ""
+"The SortedEvictionQueue interface defines the contract used by the "
+"BaseSortedEvictionAlgorithm abstract class that is used to resort the "
+"underlying queue. Again, the queue sorting should be sorted in first to "
+"evict order. The first entry in the list should evict before the last entry "
+"in the queue. The last entry in the queue should be the last entry that will "
+"require eviction."
msgstr ""
-#: ./Eviction_policies.xml:770(title)
+#. Tag: title
+#: Eviction_policies.xml:89
+#, no-c-format
msgid "TreeCache Eviction Policy Configuration"
msgstr ""
-#: ./Eviction_policies.xml:771(para)
-msgid "TreeCache 1.2.X allows a single eviction policy provider class to be configured for use by all regions. As of TreeCache 1.3.x each cache region can define its own eviction policy provider or it can use the eviction policy provider class defined at the cache level (1.2.x backwards compatibility)"
+#. Tag: para
+#: Eviction_policies.xml:90
+#, no-c-format
+msgid ""
+"TreeCache 1.2.X allows a single eviction policy provider class to be "
+"configured for use by all regions. As of TreeCache 1.3.x each cache region "
+"can define its own eviction policy provider or it can use the eviction "
+"policy provider class defined at the cache level (1.2.x backwards "
+"compatibility)"
msgstr ""
-#: ./Eviction_policies.xml:774(para)
-msgid "Here is an example of a legacy 1.2.x EvictionPolicyConfig element to configure TreeCache for use with a single eviction policy provider"
+#. Tag: para
+#: Eviction_policies.xml:93
+#, no-c-format
+msgid ""
+"Here is an example of a legacy 1.2.x EvictionPolicyConfig element to "
+"configure TreeCache for use with a single eviction policy provider"
msgstr ""
-#: ./Eviction_policies.xml:777(programlisting)
-#, no-wrap
-msgid "\n <attribute name=\"EvictionPolicyClass\">org.jboss.cache.eviction.LRUPolicy</attribute>\n <!-- Specific eviction policy configurations. This is LRU -->\n <attribute name=\"EvictionPolicyConfig\">\n <config>\n <attribute name=\"wakeUpIntervalSeconds\">5</attribute>\n <!-- Cache wide default -->\n <region name=\"/_default_\">\n <attribute name=\"maxNodes\">5000</attribute>\n <attribute name=\"timeToLiveSeconds\">1000</attribute>\n </region>\n <region name=\"/org/jboss/data\">\n <attribute name=\"maxNodes\">5000</attribute>\n <attribute name=\"timeToLiveSeconds\">1000</attribute>\n </region>\n <region name=\"/org/jboss/test/data\"&!
gt;\n <attribute name=\"maxNodes\">5</attribute>\n <attribute name=\"timeToLiveSeconds\">4</attribute>\n </region>\n <region name=\"/test/\">\n <attribute name=\"maxNodes\">10000</attribute>\n <attribute name=\"timeToLiveSeconds\">5</attribute>\n </region>\n <region name=\"/maxAgeTest/\">\n <attribute name=\"maxNodes\">10000</attribute>\n <attribute name=\"timeToLiveSeconds\">8</attribute>\n <attribute name=\"maxAgeSeconds\">10</attribute>\n </region>\n </config>\n </attribute>\n \n"
+#. Tag: programlisting
+#: Eviction_policies.xml:96
+#, no-c-format
+msgid ""
+"<attribute name=\"EvictionPolicyClass\">org.jboss.cache.eviction."
+"LRUPolicy</attribute>\n"
+" <!-- Specific eviction policy configurations. This is LRU --"
+">\n"
+" <attribute name=\"EvictionPolicyConfig\">\n"
+" <config>\n"
+" <attribute name=\"wakeUpIntervalSeconds\">5</"
+"attribute>\n"
+" <!-- Cache wide default -->\n"
+" <region name=\"/_default_\">\n"
+" <attribute name=\"maxNodes\">5000</"
+"attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">1000</"
+"attribute>\n"
+" </region>\n"
+" <region name=\"/org/jboss/data\">\n"
+" <attribute name=\"maxNodes\">5000</"
+"attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">1000</"
+"attribute>\n"
+" </region>\n"
+" <region name=\"/org/jboss/test/data\">\n"
+" <attribute name=\"maxNodes\">5</attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">4</"
+"attribute>\n"
+" </region>\n"
+" <region name=\"/test/\">\n"
+" <attribute name=\"maxNodes\">10000</"
+"attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">5</"
+"attribute>\n"
+" </region>\n"
+" <region name=\"/maxAgeTest/\">\n"
+" <attribute name=\"maxNodes\">10000</"
+"attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">8</"
+"attribute>\n"
+" <attribute name=\"maxAgeSeconds\">10</"
+"attribute>\n"
+" </region>\n"
+" </config>\n"
+" </attribute>"
msgstr ""
-#: ./Eviction_policies.xml:809(para)
-msgid "Here is an example of configuring a different eviction provider per region"
+#. Tag: para
+#: Eviction_policies.xml:97
+#, no-c-format
+msgid ""
+"Here is an example of configuring a different eviction provider per region"
msgstr ""
-#: ./Eviction_policies.xml:812(programlisting)
-#, no-wrap
-msgid "\n <attribute name=\"EvictionPolicyConfig\">\n <config>\n <attribute name=\"wakeUpIntervalSeconds\">5</attribute>\n <!-- Cache wide default -->\n <region name=\"/_default_\" policyClass=\"org.jboss.cache.eviction.LRUPolicy\">\n <attribute name=\"maxNodes\">5000</attribute>\n <attribute name=\"timeToLiveSeconds\">1000</attribute>\n </region>\n <region name=\"/org/jboss/data\" policyClass=\"org.jboss.cache.eviction.LFUPolicy\">\n <attribute name=\"maxNodes\">5000</attribute>\n <attribute name=\"minNodes\">1000</attribute>\n </region>\n <region name=\"/org/jboss/test/data\"\n\t policyClass=\"org.jboss.cache.eviction.FIFOPolicy\">\n <attribute name=\"maxNodes\">5</attribute>\n &!
lt;/region>\n <region name=\"/test/\" policyClass=\"org.jboss.cache.eviction.MRUPolicy\">\n <attribute name=\"maxNodes\">10000</attribute>\n </region>\n <region name=\"/maxAgeTest/\" policyClass=\"org.jboss.cache.eviction.LRUPolicy\">\n <attribute name=\"maxNodes\">10000</attribute>\n <attribute name=\"timeToLiveSeconds\">8</attribute>\n <attribute name=\"maxAgeSeconds\">10</attribute>\n </region>\n </config>\n </attribute>\n \n"
+#. Tag: programlisting
+#: Eviction_policies.xml:100
+#, no-c-format
+msgid ""
+"<attribute name=\"EvictionPolicyConfig\">\n"
+" <config>\n"
+" <attribute name=\"wakeUpIntervalSeconds\">5</"
+"attribute>\n"
+" <!-- Cache wide default -->\n"
+" <region name=\"/_default_\" policyClass=\"org.jboss.cache."
+"eviction.LRUPolicy\">\n"
+" <attribute name=\"maxNodes\">5000</attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">1000</"
+"attribute>\n"
+" </region>\n"
+" <region name=\"/org/jboss/data\" policyClass=\"org.jboss."
+"cache.eviction.LFUPolicy\">\n"
+" <attribute name=\"maxNodes\">5000</attribute>\n"
+" <attribute name=\"minNodes\">1000</attribute>\n"
+" </region>\n"
+" <region name=\"/org/jboss/test/data\"\n"
+" policyClass=\"org.jboss.cache.eviction.FIFOPolicy\">\n"
+" <attribute name=\"maxNodes\">5</attribute>\n"
+" </region>\n"
+" <region name=\"/test/\" policyClass=\"org.jboss.cache."
+"eviction.MRUPolicy\">\n"
+" <attribute name=\"maxNodes\">10000</attribute>\n"
+" </region>\n"
+" <region name=\"/maxAgeTest/\" policyClass=\"org.jboss.cache."
+"eviction.LRUPolicy\">\n"
+" <attribute name=\"maxNodes\">10000</attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">8</"
+"attribute>\n"
+" <attribute name=\"maxAgeSeconds\">10</attribute>\n"
+" </region>\n"
+" </config>\n"
+" </attribute>"
msgstr ""
-#: ./Eviction_policies.xml:841(para)
-msgid "Lastly, an example of mixed mode. In this scenario the regions that have a specific policy defined will use that policy. Those that do not will default to the policy defined on the entire cache instance."
+#. Tag: para
+#: Eviction_policies.xml:101
+#, no-c-format
+msgid ""
+"Lastly, an example of mixed mode. In this scenario the regions that have a "
+"specific policy defined will use that policy. Those that do not will default "
+"to the policy defined on the entire cache instance."
msgstr ""
-#: ./Eviction_policies.xml:844(programlisting)
-#, no-wrap
-msgid "\n <attribute name=\"EvictionPolicyClass\">org.jboss.cache.eviction.LRUPolicy</attribute>\n <!-- Specific eviction policy configurations. This is LRU -->\n <attribute name=\"EvictionPolicyConfig\">\n <config>\n <attribute name=\"wakeUpIntervalSeconds\">5</attribute>\n <!-- Cache wide default -->\n <region name=\"/_default_\">\n <attribute name=\"maxNodes\">5000</attribute>\n <attribute name=\"timeToLiveSeconds\">1000</attribute>\n </region>\n <region name=\"/org/jboss/data\" policyClass=\"org.jboss.cache.eviction.FIFOPolicy\">\n <attribute name=\"maxNodes\">5000</attribute>\n </region>\n <region name=\"/test/\" policyClass=\"org.jboss.cache.eviction.MRUPolicy\">\n <attribute name=\"maxNodes\">100!
00</attribute>\n </region>\n <region name=\"/maxAgeTest/\">\n <attribute name=\"maxNodes\">10000</attribute>\n <attribute name=\"timeToLiveSeconds\">8</attribute>\n <attribute name=\"maxAgeSeconds\">10</attribute>\n </region>\n </config>\n </attribute>\n \n"
+#. Tag: programlisting
+#: Eviction_policies.xml:104
+#, no-c-format
+msgid ""
+"<attribute name=\"EvictionPolicyClass\">org.jboss.cache.eviction."
+"LRUPolicy</attribute>\n"
+" <!-- Specific eviction policy configurations. This is LRU -->\n"
+" <attribute name=\"EvictionPolicyConfig\">\n"
+" <config>\n"
+" <attribute name=\"wakeUpIntervalSeconds\">5</"
+"attribute>\n"
+" <!-- Cache wide default -->\n"
+" <region name=\"/_default_\">\n"
+" <attribute name=\"maxNodes\">5000</attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">1000</"
+"attribute>\n"
+" </region>\n"
+" <region name=\"/org/jboss/data\" policyClass=\"org.jboss."
+"cache.eviction.FIFOPolicy\">\n"
+" <attribute name=\"maxNodes\">5000</attribute>\n"
+" </region>\n"
+" <region name=\"/test/\" policyClass=\"org.jboss.cache."
+"eviction.MRUPolicy\">\n"
+" <attribute name=\"maxNodes\">10000</attribute>\n"
+" </region>\n"
+" <region name=\"/maxAgeTest/\">\n"
+" <attribute name=\"maxNodes\">10000</attribute>\n"
+" <attribute name=\"timeToLiveSeconds\">8</"
+"attribute>\n"
+" <attribute name=\"maxAgeSeconds\">10</attribute>\n"
+" </region>\n"
+" </config>\n"
+" </attribute>"
msgstr ""
-#: ./Eviction_policies.xml:870(para)
-msgid "TreeCache now allows reconfiguration of eviction policy providers programatically at runtime. An example of how to reconfigure at runtime and how to set an LRU region to have maxNodes to 12345 timeToLiveSeconds to 500 and maxAgeSeconds to 1000 programatically."
+#. Tag: para
+#: Eviction_policies.xml:105
+#, no-c-format
+msgid ""
+"TreeCache now allows reconfiguration of eviction policy providers "
+"programatically at runtime. An example of how to reconfigure at runtime and "
+"how to set an LRU region to have maxNodes to 12345 timeToLiveSeconds to 500 "
+"and maxAgeSeconds to 1000 programatically."
msgstr ""
-#: ./Eviction_policies.xml:873(programlisting)
-#, no-wrap
-msgid "\n // note this is just to show that a running TreeCache instance must be\n // retrieved somehow. How it is implemented is up to the implementor.\n TreeCache cache = getRunningTreeCacheInstance();\n\n org.jboss.cache.eviction.RegionManager regionManager = cache.getEvictionRegionManager();\n org.jboss.cache.eviction.Region region = regionManager.getRegion(\"/myRegionName\");\n EvictionConfiguation config = region.getEvictionConfiguration();\n ((LRUConfiguration)config).setMaxNodes(12345);\n ((LRUConfiguration)config).setTimeToLiveSeconds(500);\n ((LRUConfiguration)config).setMaxAgeSeconds(1000);\n \n"
+#. Tag: programlisting
+#: Eviction_policies.xml:108
+#, no-c-format
+msgid ""
+"// note this is just to show that a running TreeCache instance must be\n"
+" // retrieved somehow. How it is implemented is up to the "
+"implementor.\n"
+" TreeCache cache = getRunningTreeCacheInstance();\n"
+"\n"
+" org.jboss.cache.eviction.RegionManager regionManager = cache."
+"getEvictionRegionManager();\n"
+" org.jboss.cache.eviction.Region region = regionManager.getRegion(\"/"
+"myRegionName\");\n"
+" EvictionConfiguation config = region.getEvictionConfiguration();\n"
+" ((LRUConfiguration)config).setMaxNodes(12345);\n"
+" ((LRUConfiguration)config).setTimeToLiveSeconds(500);\n"
+" ((LRUConfiguration)config).setMaxAgeSeconds(1000);"
msgstr ""
-#: ./Eviction_policies.xml:889(title)
+#. Tag: title
+#: Eviction_policies.xml:112
+#, no-c-format
msgid "TreeCache LRU eviction policy implementation"
msgstr ""
-#: ./Eviction_policies.xml:890(para)
-msgid "TreeCache has implemented a LRU eviction policy, <literal>org.jboss.cache.eviction.LRUPolicy</literal>, that controls both the node lifetime and age. This policy guarantees O(n) = 1 for adds, removals and lookups (visits). It has the following configuration parameters:"
+#. Tag: para
+#: Eviction_policies.xml:113
+#, no-c-format
+msgid ""
+"TreeCache has implemented a LRU eviction policy, <literal>org.jboss.cache."
+"eviction.LRUPolicy</literal>, that controls both the node lifetime and age. "
+"This policy guarantees O(n) = 1 for adds, removals and lookups (visits). It "
+"has the following configuration parameters:"
msgstr ""
-#: ./Eviction_policies.xml:895(para) ./Eviction_policies.xml:933(para) ./Eviction_policies.xml:961(para) ./Eviction_policies.xml:989(para)
-msgid "<literal>wakeUpIntervalSeconds</literal>. This is the interval (in seconds) to process the node events and also to perform sweeping for the size limit and age-out nodes."
+#. Tag: para
+#: Eviction_policies.xml:118 Eviction_policies.xml:156
+#: Eviction_policies.xml:184 Eviction_policies.xml:212
+#, no-c-format
+msgid ""
+"<literal>wakeUpIntervalSeconds</literal>. This is the interval (in seconds) "
+"to process the node events and also to perform sweeping for the size limit "
+"and age-out nodes."
msgstr ""
-#: ./Eviction_policies.xml:903(para)
-msgid "<literal>maxNodes</literal>. This is the maximum number of nodes allowed in this region. 0 denotes no limit."
+#. Tag: para
+#: Eviction_policies.xml:123 Eviction_policies.xml:161
+#: Eviction_policies.xml:189 Eviction_policies.xml:217
+#, no-c-format
+msgid ""
+"<literal>Region</literal>. Region is a group of nodes that possess the same "
+"eviction policy, e.g., same expired time. In TreeCache, region is denoted by "
+"a fqn, e.g., <literal>/company/personnel</literal>, and it is recursive. In "
+"specifying the region, the order is important. For example, if <literal>/org/"
+"jboss/test</literal> is specified before <literal>/org/jboss/test/data</"
+"literal>, then any node under <literal>/org/jboss/test/data</literal> "
+"belongs to the first region rather than the second. Note also that whenever "
+"eviction policy is activated, there should always be a <literal>/_default_</"
+"literal> region which covers all the eviction policies not specified by the "
+"user. In addition, the region configuration is not programmable, i.e., all "
+"the policies have to be specified via XML configuration."
msgstr ""
-#: ./Eviction_policies.xml:908(para)
-msgid "<literal>timeToLiveSeconds</literal>. Time to idle (in seconds) before the node is swept away. 0 denotes no limit."
+#. Tag: para
+#: Eviction_policies.xml:126
+#, no-c-format
+msgid ""
+"<literal>maxNodes</literal>. This is the maximum number of nodes allowed in "
+"this region. 0 denotes no limit."
msgstr ""
-#: ./Eviction_policies.xml:913(para)
-msgid "<literal>maxAgeSeconds</literal>. Time an object should exist in TreeCache (in seconds) regardless of idle time before the node is swept away. 0 denotes no limit."
+#. Tag: para
+#: Eviction_policies.xml:131
+#, no-c-format
+msgid ""
+"<literal>timeToLiveSeconds</literal>. Time to idle (in seconds) before the "
+"node is swept away. 0 denotes no limit."
msgstr ""
-#: ./Eviction_policies.xml:900(para) ./Eviction_policies.xml:938(para) ./Eviction_policies.xml:966(para) ./Eviction_policies.xml:994(para)
-msgid "<literal>Region</literal>. Region is a group of nodes that possess the same eviction policy, e.g., same expired time. In TreeCache, region is denoted by a fqn, e.g., <literal>/company/personnel</literal>, and it is recursive. In specifying the region, the order is important. For example, if <literal>/org/jboss/test</literal> is specified before <literal>/org/jboss/test/data</literal>, then any node under <literal>/org/jboss/test/data</literal> belongs to the first region rather than the second. Note also that whenever eviction policy is activated, there should always be a <literal>/_default_</literal> region which covers all the eviction policies not specified by the user. In addition, the region configuration is not programmable, i.e., all the policies have to be specified via XML configuration.<placeholder-1/>"
+#. Tag: para
+#: Eviction_policies.xml:136
+#, no-c-format
+msgid ""
+"<literal>maxAgeSeconds</literal>. Time an object should exist in TreeCache "
+"(in seconds) regardless of idle time before the node is swept away. 0 "
+"denotes no limit."
msgstr ""
-#: ./Eviction_policies.xml:921(para)
+#. Tag: para
+#: Eviction_policies.xml:144
+#, no-c-format
msgid "Please see the above section for an example."
msgstr ""
-#: ./Eviction_policies.xml:927(title)
+#. Tag: title
+#: Eviction_policies.xml:150
+#, no-c-format
msgid "TreeCache FIFO eviction policy implementation"
msgstr ""
-#: ./Eviction_policies.xml:928(para)
-msgid "TreeCache has implemented a FIFO eviction policy, <literal>org.jboss.cache.eviction.FIFOPolicy</literal>, that will control the eviction in a proper first in first out order. This policy guarantees O(n) = 1 for adds, removals and lookups (visits). It has the following configuration parameters:"
+#. Tag: para
+#: Eviction_policies.xml:151
+#, no-c-format
+msgid ""
+"TreeCache has implemented a FIFO eviction policy, <literal>org.jboss.cache."
+"eviction.FIFOPolicy</literal>, that will control the eviction in a proper "
+"first in first out order. This policy guarantees O(n) = 1 for adds, removals "
+"and lookups (visits). It has the following configuration parameters:"
msgstr ""
-#: ./Eviction_policies.xml:941(para) ./Eviction_policies.xml:969(para)
-msgid "<literal>maxNodes</literal>. This is the maximum number of nodes allowed in this region. Any integer less than or equal to 0 will throw an exception when the policy provider is being configured for use."
+#. Tag: para
+#: Eviction_policies.xml:164 Eviction_policies.xml:192
+#, no-c-format
+msgid ""
+"<literal>maxNodes</literal>. This is the maximum number of nodes allowed in "
+"this region. Any integer less than or equal to 0 will throw an exception "
+"when the policy provider is being configured for use."
msgstr ""
-#: ./Eviction_policies.xml:949(para) ./Eviction_policies.xml:977(para) ./Eviction_policies.xml:1010(para)
+#. Tag: para
+#: Eviction_policies.xml:172 Eviction_policies.xml:200
+#: Eviction_policies.xml:233
+#, no-c-format
msgid "Please read the above section for an example."
msgstr ""
-#: ./Eviction_policies.xml:955(title)
+#. Tag: title
+#: Eviction_policies.xml:178
+#, no-c-format
msgid "TreeCache MRU eviction policy implementation"
msgstr ""
-#: ./Eviction_policies.xml:956(para)
-msgid "TreeCache has implemented a MRU eviction policy, <literal>org.jboss.cache.eviction.MRUPolicy</literal>, that will control the eviction in based on most recently used algorithm. The most recently used nodes will be the first to evict with this policy. This policy guarantees O(n) = 1 for adds, removals and lookups (visits). It has the following configuration parameters:"
+#. Tag: para
+#: Eviction_policies.xml:179
+#, no-c-format
+msgid ""
+"TreeCache has implemented a MRU eviction policy, <literal>org.jboss.cache."
+"eviction.MRUPolicy</literal>, that will control the eviction in based on "
+"most recently used algorithm. The most recently used nodes will be the first "
+"to evict with this policy. This policy guarantees O(n) = 1 for adds, "
+"removals and lookups (visits). It has the following configuration parameters:"
msgstr ""
-#: ./Eviction_policies.xml:983(title)
+#. Tag: title
+#: Eviction_policies.xml:206
+#, no-c-format
msgid "TreeCache LFU eviction policy implementation"
msgstr ""
-#: ./Eviction_policies.xml:984(para)
-msgid "TreeCache has implemented a LFU eviction policy, <literal>org.jboss.cache.eviction.LFUPolicy</literal>, that will control the eviction in based on least frequently used algorithm. The least frequently used nodes will be the first to evict with this policy. Node usage starts at 1 when a node is first added. Each time it is visted, the node usage counter increments by 1. This number is used to determine which nodes are least frequently used. LFU is also a sorted eviction algorithm. The underlying EvictionQueue implementation and algorithm is sorted in ascending order of the node visits counter. This class guarantees O(n) = 1 for adds, removal and searches. However, when any number of nodes are added/visited to the queue for a given processing pass, a single O(n) = n*log(n) operation is used to resort the queue in proper LFU order. Similarly if any nodes are removed or evicted, a single O(n) = n pruning operation is necessary to clean up the EvictionQueue. LFU has the f!
ollowing configuration parameters:"
+#. Tag: para
+#: Eviction_policies.xml:207
+#, no-c-format
+msgid ""
+"TreeCache has implemented a LFU eviction policy, <literal>org.jboss.cache."
+"eviction.LFUPolicy</literal>, that will control the eviction in based on "
+"least frequently used algorithm. The least frequently used nodes will be the "
+"first to evict with this policy. Node usage starts at 1 when a node is first "
+"added. Each time it is visted, the node usage counter increments by 1. This "
+"number is used to determine which nodes are least frequently used. LFU is "
+"also a sorted eviction algorithm. The underlying EvictionQueue "
+"implementation and algorithm is sorted in ascending order of the node visits "
+"counter. This class guarantees O(n) = 1 for adds, removal and searches. "
+"However, when any number of nodes are added/visited to the queue for a given "
+"processing pass, a single O(n) = n*log(n) operation is used to resort the "
+"queue in proper LFU order. Similarly if any nodes are removed or evicted, a "
+"single O(n) = n pruning operation is necessary to clean up the "
+"EvictionQueue. LFU has the following configuration parameters:"
msgstr ""
-#: ./Eviction_policies.xml:997(para)
-msgid "<literal>maxNodes</literal>. This is the maximum number of nodes allowed in this region. A value of 0 for maxNodes means that there is no upper bound for the configured cache region."
+#. Tag: para
+#: Eviction_policies.xml:220
+#, no-c-format
+msgid ""
+"<literal>maxNodes</literal>. This is the maximum number of nodes allowed in "
+"this region. A value of 0 for maxNodes means that there is no upper bound "
+"for the configured cache region."
msgstr ""
-#: ./Eviction_policies.xml:1002(para)
-msgid "<literal>minNodes</literal>. This is the minimum number of nodes allowed in this region. This value determines what the eviction queue should prune down to per pass. e.g. If minNodes is 10 and the cache grows to 100 nodes, the cache is pruned down to the 10 most frequently used nodes when the eviction timer makes a pass through the eviction algorithm."
+#. Tag: para
+#: Eviction_policies.xml:225
+#, no-c-format
+msgid ""
+"<literal>minNodes</literal>. This is the minimum number of nodes allowed in "
+"this region. This value determines what the eviction queue should prune down "
+"to per pass. e.g. If minNodes is 10 and the cache grows to 100 nodes, the "
+"cache is pruned down to the 10 most frequently used nodes when the eviction "
+"timer makes a pass through the eviction algorithm."
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Eviction_policies.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Introduction.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Introduction.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Introduction.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,72 +1,178 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:25-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ./Introduction.xml:10(title)
+#. Tag: title
+#: Introduction.xml:5
+#, no-c-format
msgid "Introduction"
msgstr ""
-#: ./Introduction.xml:12(title)
+#. Tag: title
+#: Introduction.xml:7
+#, no-c-format
msgid "What is a TreeCache?"
msgstr ""
-#: ./Introduction.xml:13(para)
-msgid "A <literal>TreeCache</literal> is a tree-structured, replicated, transactional cache from JBoss Cache. <literal>TreeCache</literal> is the backbone for many fundamental JBoss Application Server clustering services, including - in certain versions - clustering JNDI, HTTP and EJB sessions, and clustering JMS."
+#. Tag: para
+#: Introduction.xml:8
+#, no-c-format
+msgid ""
+"A <literal>TreeCache</literal> is a tree-structured, replicated, "
+"transactional cache from JBoss Cache. <literal>TreeCache</literal> is the "
+"backbone for many fundamental JBoss Application Server clustering services, "
+"including - in certain versions - HTTP and EJB sessions."
msgstr ""
-#: ./Introduction.xml:16(para)
-msgid "In addition to this, <literal>TreeCache</literal> can be used as a standalone transactional and replicated cache or even an object oriented data store, may be embedded in other J2EE compliant application servers such as BEA WebLogic or IBM WebSphere, servlet containers such as Tomcat, or even in Java applications that do not run from within an application server."
+#. Tag: para
+#: Introduction.xml:11
+#, no-c-format
+msgid ""
+"In addition to this, <literal>TreeCache</literal> can be used as a "
+"standalone transactional and replicated cache or even an object oriented "
+"data store, may be embedded in other J2EE compliant application servers such "
+"as BEA WebLogic or IBM WebSphere, servlet containers such as Tomcat, or even "
+"in Java applications that do not run from within an application server."
msgstr ""
-#: ./Introduction.xml:22(title)
+#. Tag: title
+#: Introduction.xml:17
+#, no-c-format
msgid "TreeCache Basics"
msgstr ""
-#: ./Introduction.xml:23(para)
-msgid "The structure of a <literal>TreeCache</literal> is a tree with nodes. Each node has a name and zero or more children. A node can only have 1 parent; there is currently no support for graphs. A node can be reached by navigating from the root recursively through children, until the requested node is found. It can also be accessed by giving a fully qualified name (FQN), which consists of the concatenation of all node names from the root to the node in question."
+#. Tag: para
+#: Introduction.xml:18
+#, no-c-format
+msgid ""
+"The structure of a <literal>TreeCache</literal> is a tree with nodes. Each "
+"node has a name and zero or more children. A node can only have 1 parent; "
+"there is currently no support for graphs. A node can be reached by "
+"navigating from the root recursively through children, until the requested "
+"node is found. It can also be accessed by giving a fully qualified name "
+"(FQN), which consists of the concatenation of all node names from the root "
+"to the node in question."
msgstr ""
-#: ./Introduction.xml:26(para)
-msgid "A <literal>TreeCache</literal> can have multiple roots, allowing for a number of different trees to be present in a single cache instance. Note that a one level tree is essentially a <literal>HashMap</literal>. Each node in the tree has a map of keys and values. For a replicated cache, all keys and values have to be <literal>Serializable</literal>. Serializability is not a requirement for <literal>PojoCache</literal>, where reflection and aspect-oriented programming is used to replicate any type."
+#. Tag: para
+#: Introduction.xml:21
+#, no-c-format
+msgid ""
+"A <literal>TreeCache</literal> can have multiple roots, allowing for a "
+"number of different trees to be present in a single cache instance. Note "
+"that a one level tree is essentially a <literal>HashMap</literal>. Each node "
+"in the tree has a map of keys and values. For a replicated cache, all keys "
+"and values have to be <literal>Serializable</literal>. Serializability is "
+"not a requirement for <literal>PojoCache</literal>, where reflection and "
+"aspect-oriented programming is used to replicate any type."
msgstr ""
-#: ./Introduction.xml:29(para)
-msgid "A <literal>TreeCache</literal> can be either local or replicated. Local trees exist only inside the Java VM in which they are created, whereas replicated trees propagate any changes to all other replicated trees in the same cluster. A cluster may span different hosts on a network or just different JVMs on a single host."
+#. Tag: para
+#: Introduction.xml:24
+#, no-c-format
+msgid ""
+"A <literal>TreeCache</literal> can be either local or replicated. Local "
+"trees exist only inside the Java VM in which they are created, whereas "
+"replicated trees propagate any changes to all other replicated trees in the "
+"same cluster. A cluster may span different hosts on a network or just "
+"different JVMs on a single host."
msgstr ""
-#: ./Introduction.xml:32(para)
-msgid "The first version of <literal>TreeCache</literal> was essentially a single <literal>HashMap</literal> that replicated. However, the decision was taken to go with a tree structured cache because (a) it is more flexible and efficient and (b) a tree can always be reduced to a map, thereby offering both possibilities. The efficiency argument was driven by concerns over replication overhead, and was that a value itself can be a rather sophisticated object, with aggregation pointing to other objects, or an object containing many fields. A small change in the object would therefore trigger the entire object (possibly the transitive closure over the object graph) to be serialized and propagated to the other nodes in the cluster. With a tree, only the modified nodes in the tree need to be serialized and propagated. This is not necessarily a concern for <literal>TreeCache</literal>, but is a vital requirement for <literal>PojoCache</literal> (as we will see in the separate <li!
teral>PojoCache</literal> documentation)."
+#. Tag: para
+#: Introduction.xml:27
+#, no-c-format
+msgid ""
+"The first version of <literal>TreeCache</literal> was essentially a single "
+"<literal>HashMap</literal> that replicated. However, the decision was taken "
+"to go with a tree structured cache because (a) it is more flexible and "
+"efficient and (b) a tree can always be reduced to a map, thereby offering "
+"both possibilities. The efficiency argument was driven by concerns over "
+"replication overhead, and was that a value itself can be a rather "
+"sophisticated object, with aggregation pointing to other objects, or an "
+"object containing many fields. A small change in the object would therefore "
+"trigger the entire object (possibly the transitive closure over the object "
+"graph) to be serialized and propagated to the other nodes in the cluster. "
+"With a tree, only the modified nodes in the tree need to be serialized and "
+"propagated. This is not necessarily a concern for <literal>TreeCache</"
+"literal>, but is a vital requirement for <literal>PojoCache</literal> (as we "
+"will see in the separate <literal>PojoCache</literal> documentation)."
msgstr ""
-#: ./Introduction.xml:35(para)
-msgid "When a change is made to the <literal>TreeCache</literal>, and that change is done in the context of a transaction, then we defer the replication of changes until the transaction commits successfully. All modifications are kept in a list associated with the transaction for the caller. When the transaction commits, we replicate the changes. Otherwise, (on a rollback) we simply undo the changes locally and release any locks, resulting in zero replication traffic and overhead. For example, if a caller makes 100 modifications and then rolls back the transaction, we will not replicate anything, resulting in no network traffic."
+#. Tag: para
+#: Introduction.xml:30
+#, no-c-format
+msgid ""
+"When a change is made to the <literal>TreeCache</literal>, and that change "
+"is done in the context of a transaction, then we defer the replication of "
+"changes until the transaction commits successfully. All modifications are "
+"kept in a list associated with the transaction for the caller. When the "
+"transaction commits, we replicate the changes. Otherwise, (on a rollback) we "
+"simply undo the changes locally and release any locks, resulting in zero "
+"replication traffic and overhead. For example, if a caller makes 100 "
+"modifications and then rolls back the transaction, we will not replicate "
+"anything, resulting in no network traffic."
msgstr ""
-#: ./Introduction.xml:38(para)
-msgid "If a caller has no transaction associated with it (and isolation level is not NONE - more about this later), we will replicate right after each modification, e.g. in the above case we would send 100 messages, plus an additional message for the rollback. In this sense, running without a transaction can be thought of as analogous as running with auto-commit switched on in JDBC terminology, where each operation is committed automatically."
+#. Tag: para
+#: Introduction.xml:33
+#, no-c-format
+msgid ""
+"If a caller has no transaction associated with it (and isolation level is "
+"not NONE - more about this later), we will replicate right after each "
+"modification, e.g. in the above case we would send 100 messages, plus an "
+"additional message for the rollback. In this sense, running without a "
+"transaction can be thought of as analogous as running with auto-commit "
+"switched on in JDBC terminology, where each operation is committed "
+"automatically."
msgstr ""
-#: ./Introduction.xml:41(para)
-msgid "There is an API for plugging in different transaction managers: all it requires is to get the transaction associated with the caller's thread. Several <literal>TransactionManagerLookup</literal> implementations are provided for popular transaction managers, including a <literal>DummyTransactionManager</literal> for testing."
+#. Tag: para
+#: Introduction.xml:36
+#, no-c-format
+msgid ""
+"There is an API for plugging in different transaction managers: all it "
+"requires is to get the transaction associated with the caller's thread. "
+"Several <literal>TransactionManagerLookup</literal> implementations are "
+"provided for popular transaction managers, including a "
+"<literal>DummyTransactionManager</literal> for testing."
msgstr ""
-#: ./Introduction.xml:44(para)
-msgid "Finally, we use pessimistic locking of the cache by default, with optimistic locking as a configurable option. With pessimistic locking, we can configure the local locking policy corresponding to database-style transaction isolation levels, i.e., SERIALIZABLE, REPEATABLE, READ_COMMITTED, READ_UNCOMMITTED and NONE. More on transaction isolation levels will be discussed later. Note that the cluster-wide isolation level is READ-UNCOMMITTED by default as we don’t acquire a cluster-wide lock on touching an object for which we don’t yet have a lock (this would result in too high an overhead for messaging)."
+#. Tag: para
+#: Introduction.xml:39
+#, no-c-format
+msgid ""
+"Finally, we use pessimistic locking of the cache by default, with optimistic "
+"locking as a configurable option. With pessimistic locking, we can configure "
+"the local locking policy corresponding to database-style transaction "
+"isolation levels, i.e., SERIALIZABLE, REPEATABLE, READ_COMMITTED, "
+"READ_UNCOMMITTED and NONE. More on transaction isolation levels will be "
+"discussed later. Note that the cluster-wide isolation level is READ-"
+"UNCOMMITTED by default as we do not acquire a cluster-wide lock on touching "
+"an object for which we do not yet have a lock (this would result in too high "
+"an overhead for messaging)."
msgstr ""
-#: ./Introduction.xml:47(para)
-msgid "With optimistic locking, isolation levels are ignored as each transaction effectively maintains a copy of the data with which it works on and then attempts to merge back into the tree structure upon transaction completion. This results in a near-serializable degree of data integrity, applied cluster-wide, for the minor performance penalty incurred when validating workspace data at commit time, and the occasional transaction commit failure due to validation failures at commit time."
+#. Tag: para
+#: Introduction.xml:42
+#, no-c-format
+msgid ""
+"With optimistic locking, isolation levels are ignored as each transaction "
+"effectively maintains a copy of the data with which it works on and then "
+"attempts to merge back into the tree structure upon transaction completion. "
+"This results in a near-serializable degree of data integrity, applied "
+"cluster-wide, for the minor performance penalty incurred when validating "
+"workspace data at commit time, and the occasional transaction commit failure "
+"due to validation failures at commit time."
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Introduction.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Jboss_integration.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Jboss_integration.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Jboss_integration.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,58 +1,130 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:26-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:15+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ./Jboss_integration.xml:10(title)
+#. Tag: title
+#: Jboss_integration.xml:5
+#, no-c-format
msgid "Running JBoss Cache within JBoss Application Server"
msgstr ""
-#: ./Jboss_integration.xml:11(para)
-msgid "If JBoss Cache is run in JBoss AS then JBoss Cache can be deployed as an MBean. The steps below illustrate how to do this. We do not deploy JBoss Cache as a Service Archive (SAR), but as a JAR (<literal>jboss-cache.jar</literal> in the lib directory) and an XML file defining the MBean. Of course, JBoss Cache can also be deployed as a SAR, or even as part of a WAR, EJB or EAR."
+#. Tag: para
+#: Jboss_integration.xml:6
+#, no-c-format
+msgid ""
+"If JBoss Cache is run in JBoss AS then JBoss Cache can be deployed as an "
+"MBean. The steps below illustrate how to do this. We do not deploy JBoss "
+"Cache as a Service Archive (SAR), but as a JAR (<literal>jboss-cache.jar</"
+"literal> in the lib directory) and an XML file defining the MBean. Of "
+"course, JBoss Cache can also be deployed as a SAR, or even as part of a WAR, "
+"EJB or EAR."
msgstr ""
-#: ./Jboss_integration.xml:14(para)
-msgid "First, the <literal>jboss-cache.jar</literal> file has to be copied to the /lib directory and JBoss AS has to be restarted. Then a regular JBoss Cache configuration file in XML format has to be copied to the /deploy directory. The XML file format is the same as discussed in the Configuration chapter."
+#. Tag: para
+#: Jboss_integration.xml:9
+#, no-c-format
+msgid ""
+"First, the <literal>jboss-cache.jar</literal> file has to be copied to the /"
+"lib directory and JBoss AS has to be restarted. Then a regular JBoss Cache "
+"configuration file in XML format has to be copied to the /deploy directory. "
+"The XML file format is the same as discussed in the Configuration chapter."
msgstr ""
-#: ./Jboss_integration.xml:17(para)
-msgid "In order to be used from a client such as a servlet in the Tomcat web container inside the same JBoss container, JMX can be used:"
+#. Tag: para
+#: Jboss_integration.xml:12
+#, no-c-format
+msgid ""
+"In order to be used from a client such as a servlet in the Tomcat web "
+"container inside the same JBoss container, JMX can be used:"
msgstr ""
-#: ./Jboss_integration.xml:20(programlisting)
-#, no-wrap
-msgid "MBeanServer server=MBeanServerLocator.locateJBoss();\nTreeCacheMBean cache;\ncache=(TreeCacheMBean)MBeanProxyExt.create(TreeCacheMBean.class,\n\"jboss.cache:service=TreeCache\", server);\ncache.put(\"/a/b/c\", null);\n"
+#. Tag: programlisting
+#: Jboss_integration.xml:15
+#, no-c-format
+msgid ""
+"MBeanServer server=MBeanServerLocator.locateJBoss();\n"
+"TreeCacheMBean cache;\n"
+"cache=(TreeCacheMBean)MBeanProxyExt.create(TreeCacheMBean.class,\n"
+"\"jboss.cache:service=TreeCache\", server);\n"
+"cache.put(\"/a/b/c\", null);"
msgstr ""
-#: ./Jboss_integration.xml:26(para)
-msgid "The MBeanServerLocator class is a helper to find the (only) JBoss MBean server inside the current VM. The static create() method creates a dynamic proxy to the given interface and uses JMX to dynamically dispatch methods invoked against the generated interface. The name used to look up the MBean is the same as defined in the configuration file."
+#. Tag: para
+#: Jboss_integration.xml:16
+#, no-c-format
+msgid ""
+"The MBeanServerLocator class is a helper to find the (only) JBoss MBean "
+"server inside the current VM. The static create() method creates a dynamic "
+"proxy to the given interface and uses JMX to dynamically dispatch methods "
+"invoked against the generated interface. The name used to look up the MBean "
+"is the same as defined in the configuration file."
msgstr ""
-#: ./Jboss_integration.xml:30(title)
+#. Tag: title
+#: Jboss_integration.xml:20
+#, no-c-format
msgid "Running as an MBean"
msgstr ""
-#: ./Jboss_integration.xml:32(programlisting)
-#, no-wrap
-msgid " <mbean\n code=\"org.jboss.invocation.jrmp.server.JRMPProxyFactory\"\n name=\"mydomain:service=proxyFactory,type=jrmp,target=factory\">\n <attribute\n name=\"InvokerName\">jboss:service=invoker,type=jrmp</attribute>\n <attribute\n name=\"TargetName\">jboss.cache:service=TreeCache</attribute>\n <attribute name=\"JndiName\">MyCache</attribute> <attribute\n name=\"InvokeTargetMethod\">true</attribute> <attribute\n name=\"ExportedInterface\">org.jboss.cache.TreeCacheMBean</attribute>\n <attribute name=\"ClientInterceptors\"> <iterceptors>\n <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>\n <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>\n <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>\n </iterceptors> </attribute>\n <!
depends>jboss:service=invoker,type=jrmp</depends>\n <depends>jboss.cache:service=TreeCache</depends>\n </mbean> \n"
+#. Tag: para
+#: Jboss_integration.xml:21
+#, no-c-format
+msgid ""
+"If JBoss Cache is run inside of JBoss AS (as an MBean), we can bind it into "
+"JNDI using JrmpProxyFactory, just like any other MBean. Below is an example "
+"of how to do this:"
msgstr ""
-#: ./Jboss_integration.xml:31(para)
-msgid "If JBoss Cache is run inside of JBoss AS (as an MBean), we can bind it into JNDI using JrmpProxyFactory, just like any other MBean. Below is an example of how to do this: <placeholder-1/>"
+#. Tag: programlisting
+#: Jboss_integration.xml:22
+#, no-c-format
+msgid ""
+"<mbean\n"
+" code=\"org.jboss.invocation.jrmp.server.JRMPProxyFactory\"\n"
+" name=\"mydomain:service=proxyFactory,type=jrmp,target=factory\">\n"
+" <attribute\n"
+" name=\"InvokerName\">jboss:service=invoker,type=jrmp</"
+"attribute>\n"
+" <attribute\n"
+" name=\"TargetName\">jboss.cache:service=TreeCache</"
+"attribute>\n"
+" <attribute name=\"JndiName\">MyCache</attribute> <"
+"attribute\n"
+" name=\"InvokeTargetMethod\">true</attribute> <attribute\n"
+" name=\"ExportedInterface\">org.jboss.cache.TreeCacheMBean</"
+"attribute>\n"
+" <attribute name=\"ClientInterceptors\"> <iterceptors>\n"
+" <interceptor>org.jboss.proxy.ClientMethodInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.proxy.SecurityInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.invocation.InvokerInterceptor</"
+"interceptor>\n"
+" </iterceptors> </attribute>\n"
+" <depends>jboss:service=invoker,type=jrmp</depends>\n"
+" <depends>jboss.cache:service=TreeCache</depends>\n"
+" </mbean>"
msgstr ""
-#: ./Jboss_integration.xml:52(para)
-msgid "The <literal>InvokerName</literal> attribute needs to point to a valid JBoss invoker MBean. <literal>TargetName</literal> is the JMX name of the MBean that needs to be bound into JNDI. <literal>JndiName</literal> is the name under which the MBean will be bound, and <literal>ExportedInterface</literal> is the interface name of the MBean."
+#. Tag: para
+#: Jboss_integration.xml:24
+#, no-c-format
+msgid ""
+"The <literal>InvokerName</literal> attribute needs to point to a valid JBoss "
+"invoker MBean. <literal>TargetName</literal> is the JMX name of the MBean "
+"that needs to be bound into JNDI. <literal>JndiName</literal> is the name "
+"under which the MBean will be bound, and <literal>ExportedInterface</"
+"literal> is the interface name of the MBean."
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Jboss_integration.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Mgmt_information.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Mgmt_information.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Mgmt_information.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,524 +1,915 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:26-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:16+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Mgmt_information.xml:705(None)
-msgid "@@image: 'images/CacheMgmtInterceptor.png'; md5=d22eef17d6db9c24bcd6c85a82134569"
-msgstr ""
-
-#: ./Mgmt_information.xml:10(title)
+#. Tag: title
+#: Mgmt_information.xml:5
+#, no-c-format
msgid "Management Information"
msgstr ""
-#: ./Mgmt_information.xml:11(para)
-msgid "JBoss Cache includes JMX MBeans to expose cache functionality and provide statistics that can be used to analyze cache operations. JBoss Cache can also broadcast cache events as MBean notifications for handling via JMX monitoring tools."
+#. Tag: para
+#: Mgmt_information.xml:6
+#, no-c-format
+msgid ""
+"JBoss Cache includes JMX MBeans to expose cache functionality and provide "
+"statistics that can be used to analyze cache operations. JBoss Cache can "
+"also broadcast cache events as MBean notifications for handling via JMX "
+"monitoring tools."
msgstr ""
-#: ./Mgmt_information.xml:15(title)
+#. Tag: title
+#: Mgmt_information.xml:10
+#, no-c-format
msgid "JBoss Cache MBeans"
msgstr ""
-#: ./Mgmt_information.xml:16(para)
-msgid "JBoss Cache provides an MBean that allows JMX access to a cache instance. This MBean is accessible from an MBean server through the service name specified in the cache instance's configuration. For example, the Tomcat clustering cache instance is accessible through the service named \"jboss.cache:service=TomcatClusteringCache.\" This MBean can be used to perform most cache operations via JMX."
+#. Tag: para
+#: Mgmt_information.xml:11
+#, no-c-format
+msgid ""
+"JBoss Cache provides an MBean that allows JMX access to a cache instance. "
+"This MBean is accessible from an MBean server through the service name "
+"specified in the cache instance's configuration. For example, the Tomcat "
+"clustering cache instance is accessible through the service named \"jboss."
+"cache:service=TomcatClusteringCache.\" This MBean can be used to perform "
+"most cache operations via JMX."
msgstr ""
-#: ./Mgmt_information.xml:19(para)
-msgid "JBoss Cache also provides MBeans for each interceptor configured in the cache's interceptor stack. These MBeans are used to capture and expose statistics related to cache operations. They are hierarchically associated with the cache's primary MBean and have service names that reflect this relationship. For example, a replication interceptor MBean for the TomcatClusteringCache instance will be accessible through the service named \"jboss.cache:service=TomcatClusteringCache,treecache-interceptor=ReplicationInterceptor.\""
+#. Tag: para
+#: Mgmt_information.xml:14
+#, no-c-format
+msgid ""
+"JBoss Cache also provides MBeans for each interceptor configured in the "
+"cache's interceptor stack. These MBeans are used to capture and expose "
+"statistics related to cache operations. They are hierarchically associated "
+"with the cache's primary MBean and have service names that reflect this "
+"relationship. For example, a replication interceptor MBean for the "
+"TomcatClusteringCache instance will be accessible through the service named "
+"\"jboss.cache:service=TomcatClusteringCache,treecache-"
+"interceptor=ReplicationInterceptor.\""
msgstr ""
-#: ./Mgmt_information.xml:25(title)
+#. Tag: title
+#: Mgmt_information.xml:20
+#, no-c-format
msgid "JBoss Cache Statistics"
msgstr ""
-#: ./Mgmt_information.xml:26(para)
-msgid "JBoss Cache captures statistics in its interceptors and exposes the statistics through interceptor MBeans. Cache interceptor MBeans are enabled by default; these MBeans can be disabled for a specific cache instance through the <emphasis>UseInterceptorMbeans</emphasis> attribute. See the Configuration chapter for further details on configuration of this attribute."
+#. Tag: para
+#: Mgmt_information.xml:21
+#, no-c-format
+msgid ""
+"JBoss Cache captures statistics in its interceptors and exposes the "
+"statistics through interceptor MBeans. Cache interceptor MBeans are enabled "
+"by default; these MBeans can be disabled for a specific cache instance "
+"through the <emphasis>UseInterceptorMbeans</emphasis> attribute. See the "
+"Configuration chapter for further details on configuration of this attribute."
msgstr ""
-#: ./Mgmt_information.xml:29(para)
-msgid "Each interceptor's MBean provides an attribute that can be used to disable maintenance of statistics for that interceptor. Note that the majority of the statistics are provided by the CacheMgmtInterceptor MBean so this interceptor is the most significant in this regard. If you want to disable all statistics for performance reasons, you should utilize the <emphasis>UseInterceptorMbeans</emphasis> configuration setting as this will prevent the CacheMgmtInterceptor from being included in the cache's interceptor stack when the cache is started."
+#. Tag: para
+#: Mgmt_information.xml:24
+#, no-c-format
+msgid ""
+"Each interceptor's MBean provides an attribute that can be used to disable "
+"maintenance of statistics for that interceptor. Note that the majority of "
+"the statistics are provided by the CacheMgmtInterceptor MBean so this "
+"interceptor is the most significant in this regard. If you want to disable "
+"all statistics for performance reasons, you should utilize the "
+"<emphasis>UseInterceptorMbeans</emphasis> configuration setting as this will "
+"prevent the CacheMgmtInterceptor from being included in the cache's "
+"interceptor stack when the cache is started."
msgstr ""
-#: ./Mgmt_information.xml:32(para)
-msgid "Each interceptor provides the following common operations and attributes."
+#. Tag: para
+#: Mgmt_information.xml:27
+#, no-c-format
+msgid ""
+"Each interceptor provides the following common operations and attributes."
msgstr ""
-#: ./Mgmt_information.xml:37(para)
-msgid "dumpStatistics - returns a Map containing the interceptor's attributes and values."
+#. Tag: para
+#: Mgmt_information.xml:32
+#, no-c-format
+msgid ""
+"dumpStatistics - returns a Map containing the interceptor's attributes and "
+"values."
msgstr ""
-#: ./Mgmt_information.xml:40(para)
+#. Tag: para
+#: Mgmt_information.xml:35
+#, no-c-format
msgid "resetStatistics - resets all statistics maintained by the interceptor."
msgstr ""
-#: ./Mgmt_information.xml:43(para)
-msgid "setStatisticsEnabled(boolean) - allows statistics to be disabled for a specific interceptor."
+#. Tag: para
+#: Mgmt_information.xml:38
+#, no-c-format
+msgid ""
+"setStatisticsEnabled(boolean) - allows statistics to be disabled for a "
+"specific interceptor."
msgstr ""
-#: ./Mgmt_information.xml:46(para)
-msgid "The following table describes the statistics currently available for JBoss Cache."
+#. Tag: para
+#: Mgmt_information.xml:41
+#, no-c-format
+msgid ""
+"The following table describes the statistics currently available for JBoss "
+"Cache."
msgstr ""
-#: ./Mgmt_information.xml:50(title)
+#. Tag: title
+#: Mgmt_information.xml:45
+#, no-c-format
msgid "JBoss Cache Management Statistics"
msgstr ""
-#: ./Mgmt_information.xml:58(entry)
+#. Tag: entry
+#: Mgmt_information.xml:53
+#, no-c-format
msgid "MBean Name"
msgstr ""
-#: ./Mgmt_information.xml:61(entry)
+#. Tag: entry
+#: Mgmt_information.xml:56
+#, no-c-format
msgid "Attribute"
msgstr ""
-#: ./Mgmt_information.xml:64(entry)
+#. Tag: entry
+#: Mgmt_information.xml:59
+#, no-c-format
msgid "Type"
msgstr ""
-#: ./Mgmt_information.xml:67(entry)
+#. Tag: entry
+#: Mgmt_information.xml:62
+#, no-c-format
msgid "Description"
msgstr ""
-#: ./Mgmt_information.xml:74(entry)
+#. Tag: entry
+#: Mgmt_information.xml:69
+#, no-c-format
msgid "ActivationInterceptor"
msgstr ""
-#: ./Mgmt_information.xml:77(entry)
+#. Tag: entry
+#: Mgmt_information.xml:72
+#, no-c-format
msgid "Activations"
msgstr ""
-#: ./Mgmt_information.xml:80(entry) ./Mgmt_information.xml:94(entry) ./Mgmt_information.xml:108(entry) ./Mgmt_information.xml:122(entry) ./Mgmt_information.xml:136(entry) ./Mgmt_information.xml:150(entry) ./Mgmt_information.xml:164(entry) ./Mgmt_information.xml:206(entry) ./Mgmt_information.xml:220(entry) ./Mgmt_information.xml:234(entry) ./Mgmt_information.xml:248(entry) ./Mgmt_information.xml:290(entry) ./Mgmt_information.xml:304(entry) ./Mgmt_information.xml:318(entry) ./Mgmt_information.xml:332(entry) ./Mgmt_information.xml:346(entry) ./Mgmt_information.xml:360(entry)
+#. Tag: entry
+#: Mgmt_information.xml:75 Mgmt_information.xml:89 Mgmt_information.xml:103
+#: Mgmt_information.xml:117 Mgmt_information.xml:131 Mgmt_information.xml:145
+#: Mgmt_information.xml:159 Mgmt_information.xml:201 Mgmt_information.xml:215
+#: Mgmt_information.xml:229 Mgmt_information.xml:243 Mgmt_information.xml:285
+#: Mgmt_information.xml:299 Mgmt_information.xml:313 Mgmt_information.xml:327
+#: Mgmt_information.xml:341 Mgmt_information.xml:355
+#, no-c-format
msgid "long"
msgstr ""
-#: ./Mgmt_information.xml:83(entry)
+#. Tag: entry
+#: Mgmt_information.xml:78
+#, no-c-format
msgid "Number of passivated nodes that have been activated."
msgstr ""
-#: ./Mgmt_information.xml:88(entry) ./Mgmt_information.xml:102(entry)
+#. Tag: entry
+#: Mgmt_information.xml:83 Mgmt_information.xml:97
+#, no-c-format
msgid "CacheLoaderInterceptor"
msgstr ""
-#: ./Mgmt_information.xml:91(entry)
+#. Tag: entry
+#: Mgmt_information.xml:86
+#, no-c-format
msgid "CacheLoaderLoads"
msgstr ""
-#: ./Mgmt_information.xml:97(entry)
+#. Tag: entry
+#: Mgmt_information.xml:92
+#, no-c-format
msgid "Number of nodes loaded through a cache loader."
msgstr ""
-#: ./Mgmt_information.xml:105(entry)
+#. Tag: entry
+#: Mgmt_information.xml:100
+#, no-c-format
msgid "CacheLoaderMisses"
msgstr ""
-#: ./Mgmt_information.xml:111(entry)
+#. Tag: entry
+#: Mgmt_information.xml:106
+#, no-c-format
msgid "Number of unsuccessful attempts to load a node through a cache loader."
msgstr ""
-#: ./Mgmt_information.xml:116(entry) ./Mgmt_information.xml:130(entry) ./Mgmt_information.xml:144(entry) ./Mgmt_information.xml:158(entry) ./Mgmt_information.xml:172(entry) ./Mgmt_information.xml:186(entry) ./Mgmt_information.xml:200(entry) ./Mgmt_information.xml:214(entry) ./Mgmt_information.xml:228(entry) ./Mgmt_information.xml:242(entry) ./Mgmt_information.xml:256(entry) ./Mgmt_information.xml:270(entry)
+#. Tag: entry
+#: Mgmt_information.xml:111 Mgmt_information.xml:125 Mgmt_information.xml:139
+#: Mgmt_information.xml:153 Mgmt_information.xml:167 Mgmt_information.xml:181
+#: Mgmt_information.xml:195 Mgmt_information.xml:209 Mgmt_information.xml:223
+#: Mgmt_information.xml:237 Mgmt_information.xml:251 Mgmt_information.xml:265
+#, no-c-format
msgid "CacheMgmtInterceptor"
msgstr ""
-#: ./Mgmt_information.xml:119(entry)
+#. Tag: entry
+#: Mgmt_information.xml:114
+#, no-c-format
msgid "Hits"
msgstr ""
-#: ./Mgmt_information.xml:125(entry)
+#. Tag: entry
+#: Mgmt_information.xml:120
+#, no-c-format
msgid "Number of successful attribute retrievals."
msgstr ""
-#: ./Mgmt_information.xml:133(entry)
+#. Tag: entry
+#: Mgmt_information.xml:128
+#, no-c-format
msgid "Misses"
msgstr ""
-#: ./Mgmt_information.xml:139(entry)
+#. Tag: entry
+#: Mgmt_information.xml:134
+#, no-c-format
msgid "Number of unsuccessful attribute retrievals."
msgstr ""
-#: ./Mgmt_information.xml:147(entry)
+#. Tag: entry
+#: Mgmt_information.xml:142
+#, no-c-format
msgid "Stores"
msgstr ""
-#: ./Mgmt_information.xml:153(entry)
+#. Tag: entry
+#: Mgmt_information.xml:148
+#, no-c-format
msgid "Number of attribute store operations."
msgstr ""
-#: ./Mgmt_information.xml:161(entry)
+#. Tag: entry
+#: Mgmt_information.xml:156
+#, no-c-format
msgid "Evictions"
msgstr ""
-#: ./Mgmt_information.xml:167(entry)
+#. Tag: entry
+#: Mgmt_information.xml:162
+#, no-c-format
msgid "Number of node evictions."
msgstr ""
-#: ./Mgmt_information.xml:175(entry)
+#. Tag: entry
+#: Mgmt_information.xml:170
+#, no-c-format
msgid "NumberOfAttributes"
msgstr ""
-#: ./Mgmt_information.xml:178(entry) ./Mgmt_information.xml:192(entry)
-msgid "int"
+#. Tag: entry
+#: Mgmt_information.xml:173 Mgmt_information.xml:187
+#, no-c-format
+msgid "<entry>int</entry>"
msgstr ""
-#: ./Mgmt_information.xml:181(entry)
+#. Tag: entry
+#: Mgmt_information.xml:176
+#, no-c-format
msgid "Number of attributes currently cached."
msgstr ""
-#: ./Mgmt_information.xml:189(entry)
+#. Tag: entry
+#: Mgmt_information.xml:184
+#, no-c-format
msgid "NumberOfNodes"
msgstr ""
-#: ./Mgmt_information.xml:195(entry)
+#. Tag: entry
+#: Mgmt_information.xml:190
+#, no-c-format
msgid "Number of nodes currently cached."
msgstr ""
-#: ./Mgmt_information.xml:203(entry)
+#. Tag: entry
+#: Mgmt_information.xml:198
+#, no-c-format
msgid "ElapsedTime"
msgstr ""
-#: ./Mgmt_information.xml:209(entry)
+#. Tag: entry
+#: Mgmt_information.xml:204
+#, no-c-format
msgid "Number of seconds that the cache has been running."
msgstr ""
-#: ./Mgmt_information.xml:217(entry)
+#. Tag: entry
+#: Mgmt_information.xml:212
+#, no-c-format
msgid "TimeSinceReset"
msgstr ""
-#: ./Mgmt_information.xml:223(entry)
+#. Tag: entry
+#: Mgmt_information.xml:218
+#, no-c-format
msgid "Number of seconds since the cache statistics have been reset."
msgstr ""
-#: ./Mgmt_information.xml:231(entry)
+#. Tag: entry
+#: Mgmt_information.xml:226
+#, no-c-format
msgid "AverageReadTime"
msgstr ""
-#: ./Mgmt_information.xml:237(entry)
-msgid "Average time in milliseconds to retrieve a cache attribute, including unsuccessful attribute retrievals."
+#. Tag: entry
+#: Mgmt_information.xml:232
+#, no-c-format
+msgid ""
+"Average time in milliseconds to retrieve a cache attribute, including "
+"unsuccessful attribute retrievals."
msgstr ""
-#: ./Mgmt_information.xml:245(entry)
+#. Tag: entry
+#: Mgmt_information.xml:240
+#, no-c-format
msgid "AverageWriteTime"
msgstr ""
-#: ./Mgmt_information.xml:251(entry)
+#. Tag: entry
+#: Mgmt_information.xml:246
+#, no-c-format
msgid "Average time in milliseconds to write a cache attribute."
msgstr ""
-#: ./Mgmt_information.xml:259(entry)
+#. Tag: entry
+#: Mgmt_information.xml:254
+#, no-c-format
msgid "HitMissRatio"
msgstr ""
-#: ./Mgmt_information.xml:262(entry) ./Mgmt_information.xml:276(entry)
+#. Tag: entry
+#: Mgmt_information.xml:257 Mgmt_information.xml:271
+#, no-c-format
msgid "double"
msgstr ""
-#: ./Mgmt_information.xml:265(entry)
-msgid "Ratio of hits to hits and misses. A hit is a get attribute operation that results in an object being returned to the client. The retrieval may be from a cache loader if the entry isn't in the local cache."
+#. Tag: entry
+#: Mgmt_information.xml:260
+#, no-c-format
+msgid ""
+"Ratio of hits to hits and misses. A hit is a get attribute operation that "
+"results in an object being returned to the client. The retrieval may be from "
+"a cache loader if the entry isn't in the local cache."
msgstr ""
-#: ./Mgmt_information.xml:273(entry)
+#. Tag: entry
+#: Mgmt_information.xml:268
+#, no-c-format
msgid "ReadWriteRatio"
msgstr ""
-#: ./Mgmt_information.xml:279(entry)
-msgid "Ratio of read operations to write operations. This is the ratio of cache hits and misses to cache stores."
+#. Tag: entry
+#: Mgmt_information.xml:274
+#, no-c-format
+msgid ""
+"Ratio of read operations to write operations. This is the ratio of cache "
+"hits and misses to cache stores."
msgstr ""
-#: ./Mgmt_information.xml:284(entry)
+#. Tag: entry
+#: Mgmt_information.xml:279
+#, no-c-format
msgid "CacheStoreInterceptor"
msgstr ""
-#: ./Mgmt_information.xml:287(entry)
+#. Tag: entry
+#: Mgmt_information.xml:282
+#, no-c-format
msgid "CacheLoaderStores"
msgstr ""
-#: ./Mgmt_information.xml:293(entry)
+#. Tag: entry
+#: Mgmt_information.xml:288
+#, no-c-format
msgid "Number of nodes written to the cache loader."
msgstr ""
-#: ./Mgmt_information.xml:298(entry)
+#. Tag: entry
+#: Mgmt_information.xml:293
+#, no-c-format
msgid "InvalidationInterceptor"
msgstr ""
-#: ./Mgmt_information.xml:301(entry)
+#. Tag: entry
+#: Mgmt_information.xml:296
+#, no-c-format
msgid "Invalidations"
msgstr ""
-#: ./Mgmt_information.xml:307(entry)
+#. Tag: entry
+#: Mgmt_information.xml:302
+#, no-c-format
msgid "Number of cached nodes that have been invalidated."
msgstr ""
-#: ./Mgmt_information.xml:312(entry)
+#. Tag: entry
+#: Mgmt_information.xml:307
+#, no-c-format
msgid "PassivationInterceptor"
msgstr ""
-#: ./Mgmt_information.xml:315(entry)
+#. Tag: entry
+#: Mgmt_information.xml:310
+#, no-c-format
msgid "Passivations"
msgstr ""
-#: ./Mgmt_information.xml:321(entry)
+#. Tag: entry
+#: Mgmt_information.xml:316
+#, no-c-format
msgid "Number of cached nodes that have been passivated."
msgstr ""
-#: ./Mgmt_information.xml:326(entry) ./Mgmt_information.xml:340(entry) ./Mgmt_information.xml:354(entry)
+#. Tag: entry
+#: Mgmt_information.xml:321 Mgmt_information.xml:335 Mgmt_information.xml:349
+#, no-c-format
msgid "TxInterceptor"
msgstr ""
-#: ./Mgmt_information.xml:329(entry)
+#. Tag: entry
+#: Mgmt_information.xml:324
+#, no-c-format
msgid "Prepares"
msgstr ""
-#: ./Mgmt_information.xml:335(entry)
+#. Tag: entry
+#: Mgmt_information.xml:330
+#, no-c-format
msgid "Number of transaction prepare operations performed by this interceptor."
msgstr ""
-#: ./Mgmt_information.xml:343(entry)
+#. Tag: entry
+#: Mgmt_information.xml:338
+#, no-c-format
msgid "Commits"
msgstr ""
-#: ./Mgmt_information.xml:349(entry)
+#. Tag: entry
+#: Mgmt_information.xml:344
+#, no-c-format
msgid "Number of transaction commit operations performed by this interceptor."
msgstr ""
-#: ./Mgmt_information.xml:357(entry)
+#. Tag: entry
+#: Mgmt_information.xml:352
+#, no-c-format
msgid "Rollbacks"
msgstr ""
-#: ./Mgmt_information.xml:363(entry)
-msgid "Number of transaction rollbacks operations performed by this interceptor."
+#. Tag: entry
+#: Mgmt_information.xml:358
+#, no-c-format
+msgid ""
+"Number of transaction rollbacks operations performed by this interceptor."
msgstr ""
-#: ./Mgmt_information.xml:373(title)
+#. Tag: title
+#: Mgmt_information.xml:368
+#, no-c-format
msgid "Receiving Cache Notifications"
msgstr ""
-#: ./Mgmt_information.xml:374(para)
-msgid "JBoss Cache users can register a listener to receive cache events as described in the Eviction Policies chapter. Users can alternatively utilize the cache's management information infrastructure to receive these events via JMX notifications. Cache events are accessible as notifications by registering a NotificationListener for the CacheMgmtInterceptor MBean. This functionality is only available if cache statistics are enabled as described in the previous section."
+#. Tag: para
+#: Mgmt_information.xml:369
+#, no-c-format
+msgid ""
+"JBoss Cache users can register a listener to receive cache events as "
+"described in the Eviction Policies chapter. Users can alternatively utilize "
+"the cache's management information infrastructure to receive these events "
+"via JMX notifications. Cache events are accessible as notifications by "
+"registering a NotificationListener for the CacheMgmtInterceptor MBean. This "
+"functionality is only available if cache statistics are enabled as described "
+"in the previous section."
msgstr ""
-#: ./Mgmt_information.xml:377(para)
-msgid "The following table depicts the JMX notifications available for JBoss Cache as well as the cache events to which they correspond. These are the notifications that can be received through the CacheMgmtInterceptor MBean. Each notification represents a single event published by JBoss Cache and provides user data corresponding to the parameters of the event."
+#. Tag: para
+#: Mgmt_information.xml:372
+#, no-c-format
+msgid ""
+"The following table depicts the JMX notifications available for JBoss Cache "
+"as well as the cache events to which they correspond. These are the "
+"notifications that can be received through the CacheMgmtInterceptor MBean. "
+"Each notification represents a single event published by JBoss Cache and "
+"provides user data corresponding to the parameters of the event."
msgstr ""
-#: ./Mgmt_information.xml:381(title)
+#. Tag: title
+#: Mgmt_information.xml:376
+#, no-c-format
msgid "JBoss Cache MBean Notifications"
msgstr ""
-#: ./Mgmt_information.xml:385(entry)
+#. Tag: entry
+#: Mgmt_information.xml:380
+#, no-c-format
msgid "Notification Type"
msgstr ""
-#: ./Mgmt_information.xml:388(entry)
+#. Tag: entry
+#: Mgmt_information.xml:383
+#, no-c-format
msgid "Notification Data"
msgstr ""
-#: ./Mgmt_information.xml:391(entry)
+#. Tag: entry
+#: Mgmt_information.xml:386
+#, no-c-format
msgid "TreeCacheListener Event"
msgstr ""
-#: ./Mgmt_information.xml:398(entry)
+#. Tag: entry
+#: Mgmt_information.xml:393
+#, no-c-format
msgid "org.jboss.cache.CacheStarted"
msgstr ""
-#: ./Mgmt_information.xml:401(entry) ./Mgmt_information.xml:412(entry)
+#. Tag: entry
+#: Mgmt_information.xml:396 Mgmt_information.xml:407
+#, no-c-format
msgid "String : cache service name"
msgstr ""
-#: ./Mgmt_information.xml:404(entry)
+#. Tag: entry
+#: Mgmt_information.xml:399
+#, no-c-format
msgid "cacheStarted"
msgstr ""
-#: ./Mgmt_information.xml:409(entry)
+#. Tag: entry
+#: Mgmt_information.xml:404
+#, no-c-format
msgid "org.jboss.cache.CacheStopped"
msgstr ""
-#: ./Mgmt_information.xml:415(entry)
+#. Tag: entry
+#: Mgmt_information.xml:410
+#, no-c-format
msgid "cacheStopped"
msgstr ""
-#: ./Mgmt_information.xml:420(entry)
+#. Tag: entry
+#: Mgmt_information.xml:415
+#, no-c-format
msgid "org.jboss.cache.NodeCreated"
msgstr ""
-#: ./Mgmt_information.xml:423(entry) ./Mgmt_information.xml:434(entry) ./Mgmt_information.xml:445(entry) ./Mgmt_information.xml:456(entry) ./Mgmt_information.xml:467(entry) ./Mgmt_information.xml:478(entry)
+#. Tag: entry
+#: Mgmt_information.xml:418 Mgmt_information.xml:429 Mgmt_information.xml:440
+#: Mgmt_information.xml:451 Mgmt_information.xml:462 Mgmt_information.xml:473
+#, no-c-format
msgid "String : fqn"
msgstr ""
-#: ./Mgmt_information.xml:426(entry)
+#. Tag: entry
+#: Mgmt_information.xml:421
+#, no-c-format
msgid "NodeCreated"
msgstr ""
-#: ./Mgmt_information.xml:431(entry)
+#. Tag: entry
+#: Mgmt_information.xml:426
+#, no-c-format
msgid "org.jboss.cache.NodeEvicted"
msgstr ""
-#: ./Mgmt_information.xml:437(entry)
+#. Tag: entry
+#: Mgmt_information.xml:432
+#, no-c-format
msgid "NodeEvicted"
msgstr ""
-#: ./Mgmt_information.xml:442(entry)
+#. Tag: entry
+#: Mgmt_information.xml:437
+#, no-c-format
msgid "org.jboss.cache.NodeLoaded"
msgstr ""
-#: ./Mgmt_information.xml:448(entry)
+#. Tag: entry
+#: Mgmt_information.xml:443
+#, no-c-format
msgid "NodeLoaded"
msgstr ""
-#: ./Mgmt_information.xml:453(entry)
+#. Tag: entry
+#: Mgmt_information.xml:448
+#, no-c-format
msgid "org.jboss.cache.NodeModifed"
msgstr ""
-#: ./Mgmt_information.xml:459(entry)
+#. Tag: entry
+#: Mgmt_information.xml:454
+#, no-c-format
msgid "NodeModifed"
msgstr ""
-#: ./Mgmt_information.xml:464(entry)
+#. Tag: entry
+#: Mgmt_information.xml:459
+#, no-c-format
msgid "org.jboss.cache.NodeRemoved"
msgstr ""
-#: ./Mgmt_information.xml:470(entry)
+#. Tag: entry
+#: Mgmt_information.xml:465
+#, no-c-format
msgid "NodeRemoved"
msgstr ""
-#: ./Mgmt_information.xml:475(entry)
+#. Tag: entry
+#: Mgmt_information.xml:470
+#, no-c-format
msgid "org.jboss.cache.NodeVisited"
msgstr ""
-#: ./Mgmt_information.xml:481(entry)
+#. Tag: entry
+#: Mgmt_information.xml:476
+#, no-c-format
msgid "NodeVisited"
msgstr ""
-#: ./Mgmt_information.xml:486(entry)
+#. Tag: entry
+#: Mgmt_information.xml:481
+#, no-c-format
msgid "org.jboss.cache.ViewChange"
msgstr ""
-#: ./Mgmt_information.xml:489(entry)
+#. Tag: entry
+#: Mgmt_information.xml:484
+#, no-c-format
msgid "String : view"
msgstr ""
-#: ./Mgmt_information.xml:492(entry)
+#. Tag: entry
+#: Mgmt_information.xml:487
+#, no-c-format
msgid "ViewChange"
msgstr ""
-#: ./Mgmt_information.xml:497(entry)
-msgid "org.jboss.cache.NodeActivate"
+#. Tag: entry
+#: Mgmt_information.xml:492
+#, no-c-format
+msgid "org.jboss.cache.NodeActivate:"
msgstr ""
-#: ./Mgmt_information.xml:502(entry) ./Mgmt_information.xml:522(entry) ./Mgmt_information.xml:542(entry) ./Mgmt_information.xml:567(entry) ./Mgmt_information.xml:587(entry)
+#. Tag: para
+#: Mgmt_information.xml:496 Mgmt_information.xml:517 Mgmt_information.xml:538
+#: Mgmt_information.xml:564 Mgmt_information.xml:585
+#, no-c-format
msgid "Object[0]=String: fqn"
msgstr ""
-#: ./Mgmt_information.xml:507(entry) ./Mgmt_information.xml:527(entry) ./Mgmt_information.xml:547(entry) ./Mgmt_information.xml:572(entry) ./Mgmt_information.xml:592(entry)
+#. Tag: para
+#: Mgmt_information.xml:501 Mgmt_information.xml:522 Mgmt_information.xml:543
+#: Mgmt_information.xml:569 Mgmt_information.xml:590
+#, no-c-format
msgid "Object[1]=Boolean: pre"
msgstr ""
-#: ./Mgmt_information.xml:512(entry)
+#. Tag: entry
+#: Mgmt_information.xml:508
+#, no-c-format
msgid "NodeActivate"
msgstr ""
-#: ./Mgmt_information.xml:517(entry)
+#. Tag: entry
+#: Mgmt_information.xml:513
+#, no-c-format
msgid "org.jboss.cache.NodeEvict"
msgstr ""
-#: ./Mgmt_information.xml:532(entry)
+#. Tag: entry
+#: Mgmt_information.xml:528
+#, no-c-format
msgid "NodeEvict"
msgstr ""
-#: ./Mgmt_information.xml:537(entry)
+#. Tag: entry
+#: Mgmt_information.xml:533
+#, no-c-format
msgid "org.jboss.cache.NodeModify"
msgstr ""
-#: ./Mgmt_information.xml:552(entry) ./Mgmt_information.xml:597(entry)
+#. Tag: para
+#: Mgmt_information.xml:548 Mgmt_information.xml:595
+#, no-c-format
msgid "Object[2]=Boolean: isLocal"
msgstr ""
-#: ./Mgmt_information.xml:557(entry)
+#. Tag: entry
+#: Mgmt_information.xml:554
+#, no-c-format
msgid "NodeModify"
msgstr ""
-#: ./Mgmt_information.xml:562(entry)
+#. Tag: entry
+#: Mgmt_information.xml:559
+#, no-c-format
msgid "org.jboss.cache.NodePassivate"
msgstr ""
-#: ./Mgmt_information.xml:577(entry)
+#. Tag: entry
+#: Mgmt_information.xml:575
+#, no-c-format
msgid "NodePassivate"
msgstr ""
-#: ./Mgmt_information.xml:582(entry)
+#. Tag: entry
+#: Mgmt_information.xml:580
+#, no-c-format
msgid "org.jboss.cache.NodeRemove"
msgstr ""
-#: ./Mgmt_information.xml:602(entry)
+#. Tag: entry
+#: Mgmt_information.xml:601
+#, no-c-format
msgid "NodeRemove"
msgstr ""
-#: ./Mgmt_information.xml:609(para)
-msgid "The following is an example of how to programmatically receive cache notifications when running in a JBoss application server environment. In this example, the client uses a filter to specify which events are of interest."
+#. Tag: para
+#: Mgmt_information.xml:608
+#, no-c-format
+msgid ""
+"The following is an example of how to programmatically receive cache "
+"notifications when running in a JBoss application server environment. In "
+"this example, the client uses a filter to specify which events are of "
+"interest."
msgstr ""
-#: ./Mgmt_information.xml:612(programlisting)
-#, no-wrap
-msgid "\nMyListener listener = new MyListener();\nNotificationFilterSupport filter = null;\n \n// get reference to MBean server\nContext ic = new InitialContext();\nMBeanServerConnection server = (MBeanServerConnection)ic.lookup(\"jmx/invoker/RMIAdaptor\");\n \n// get reference to CacheMgmtInterceptor MBean\nString cache_service = \"jboss.cache:service=TomcatClusteringCache\";\nString mgmt_service = cache_service + \",treecache-interceptor=CacheMgmtInterceptor\";\nObjectName mgmt_name = new ObjectName(mgmt_service);\n \n// configure a filter to only receive node created and removed events\nfilter = new NotificationFilterSupport();\nfilter.disableAllTypes();\nfilter.enableType(CacheMgmtInterceptor.NOTIF_NODE_CREATED);\nfilter.enableType(CacheMgmtInterceptor.NOTIF_NODE_REMOVED);\n \n// register the listener with a filter\n// leave the filter null to receive all cache events\nserver.addNotificationListener(mgmt_name, listener, filter, null);\n \n// ...\n \n// on completion of !
processing, unregister the listener\nserver.removeNotificationListener(mgmt_name, listener, filter, null);\n \n"
+#. Tag: programlisting
+#: Mgmt_information.xml:611
+#, no-c-format
+msgid ""
+"MyListener listener = new MyListener();\n"
+"NotificationFilterSupport filter = null;\n"
+" \n"
+"// get reference to MBean server\n"
+"Context ic = new InitialContext();\n"
+"MBeanServerConnection server = (MBeanServerConnection)ic.lookup(\"jmx/"
+"invoker/RMIAdaptor\");\n"
+" \n"
+"// get reference to CacheMgmtInterceptor MBean\n"
+"String cache_service = \"jboss.cache:service=TomcatClusteringCache\";\n"
+"String mgmt_service = cache_service + \",treecache-"
+"interceptor=CacheMgmtInterceptor\";\n"
+"ObjectName mgmt_name = new ObjectName(mgmt_service);\n"
+" \n"
+"// configure a filter to only receive node created and removed events\n"
+"filter = new NotificationFilterSupport();\n"
+"filter.disableAllTypes();\n"
+"filter.enableType(CacheMgmtInterceptor.NOTIF_NODE_CREATED);\n"
+"filter.enableType(CacheMgmtInterceptor.NOTIF_NODE_REMOVED);\n"
+" \n"
+"// register the listener with a filter\n"
+"// leave the filter null to receive all cache events\n"
+"server.addNotificationListener(mgmt_name, listener, filter, null);\n"
+" \n"
+"// ...\n"
+" \n"
+"// on completion of processing, unregister the listener\n"
+"server.removeNotificationListener(mgmt_name, listener, filter, null);"
msgstr ""
-#: ./Mgmt_information.xml:641(para)
-msgid "The following is the simple notification listener implementation used in the previous example."
+#. Tag: para
+#: Mgmt_information.xml:612
+#, no-c-format
+msgid ""
+"The following is the simple notification listener implementation used in the "
+"previous example."
msgstr ""
-#: ./Mgmt_information.xml:644(programlisting)
-#, no-wrap
-msgid "\nprivate class MyListener implements NotificationListener, Serializable {\n public void handleNotification(Notification notification, Object handback) {\n String message = notification.getMessage();\n String type = notification.getType();\n Object userData = notification.getUserData();\n System.out.println(type + \": \"+message);\n if (userData == null) {\n System.out.println(\"notification data is null\");\n }\n else if (userData instanceof String) {\n System.out.println(\"notification data: \"+(String)userData);\n }\n else if (userData instanceof Object[]) {\n Object[] ud = (Object[])userData;\n for (int i = 0; i > ud.length; i++) {\n System.out.println(\"notification data: \"+ud[i].toString());\n }\n }\n else {\n System.out.println(\"notification data class: \" + userData.getClass().getName());\n }\n }\n} \n"
+#. Tag: programlisting
+#: Mgmt_information.xml:615
+#, no-c-format
+msgid ""
+"private class MyListener implements NotificationListener, Serializable {\n"
+" public void handleNotification(Notification notification, Object "
+"handback) {\n"
+" String message = notification.getMessage();\n"
+" String type = notification.getType();\n"
+" Object userData = notification.getUserData();\n"
+" System.out.println(type + \": \"+message);\n"
+" if (userData == null) {\n"
+" System.out.println(\"notification data is null\");\n"
+" }\n"
+" else if (userData instanceof String) {\n"
+" System.out.println(\"notification data: \"+(String)userData);\n"
+" }\n"
+" else if (userData instanceof Object[]) {\n"
+" Object[] ud = (Object[])userData;\n"
+" for (int i = 0; i > ud.length; i++) {\n"
+" System.out.println(\"notification data: \"+ud[i].toString());\n"
+" }\n"
+" }\n"
+" else {\n"
+" System.out.println(\"notification data class: \" + userData.getClass"
+"().getName());\n"
+" }\n"
+" }\n"
+"}"
msgstr ""
-#: ./Mgmt_information.xml:669(para)
-msgid "Note: the JBoss Cache management implementation only listens to cache events after a client registers to receive MBean notifications. As soon as no clients are registered for notifications, the MBean will remove itself as a cache listener."
+#. Tag: para
+#: Mgmt_information.xml:616
+#, no-c-format
+msgid ""
+"Note: the JBoss Cache management implementation only listens to cache events "
+"after a client registers to receive MBean notifications. As soon as no "
+"clients are registered for notifications, the MBean will remove itself as a "
+"cache listener."
msgstr ""
-#: ./Mgmt_information.xml:675(title)
+#. Tag: title
+#: Mgmt_information.xml:622
+#, no-c-format
msgid "Accessing Cache MBeans in a Standalone Environment"
msgstr ""
-#: ./Mgmt_information.xml:676(para)
-msgid "JBoss Cache MBeans are readily accessed when running cache instances in an application server that provides an MBean server interface such as JBoss JMX Console. Refer to server documentation for instructions on how to access MBeans running in a server's MBean container."
+#. Tag: para
+#: Mgmt_information.xml:623
+#, no-c-format
+msgid ""
+"JBoss Cache MBeans are readily accessed when running cache instances in an "
+"application server that provides an MBean server interface such as JBoss JMX "
+"Console. Refer to server documentation for instructions on how to access "
+"MBeans running in a server's MBean container."
msgstr ""
-#: ./Mgmt_information.xml:679(para)
-msgid "JBoss Cache MBeans are also accessible when running in a non-server environment if the JVM is JDK 5.0 or later. When running a standalone cache in a JDK 5 environment, you can access the cache's MBeans as follows."
+#. Tag: para
+#: Mgmt_information.xml:626
+#, no-c-format
+msgid ""
+"JBoss Cache MBeans are also accessible when running in a non-server "
+"environment if the JVM is JDK 5.0 or later. When running a standalone cache "
+"in a JDK 5 environment, you can access the cache's MBeans as follows."
msgstr ""
-#: ./Mgmt_information.xml:685(para)
-msgid "Set the system property <emphasis>-Dcom.sun.management.jmxremote</emphasis> when starting the JVM where the cache will run."
+#. Tag: para
+#: Mgmt_information.xml:632
+#, no-c-format
+msgid ""
+"Set the system property <emphasis>-Dcom.sun.management.jmxremote</emphasis> "
+"when starting the JVM where the cache will run."
msgstr ""
-#: ./Mgmt_information.xml:688(para)
-msgid "Once the JVM is running, start the JDK 5 <emphasis>jconsole</emphasis> utility, located in the JDK's /bin directory."
+#. Tag: para
+#: Mgmt_information.xml:635
+#, no-c-format
+msgid ""
+"Once the JVM is running, start the JDK 5 <emphasis>jconsole</emphasis> "
+"utility, located in the JDK's /bin directory."
msgstr ""
-#: ./Mgmt_information.xml:691(para)
-msgid "When the utility loads, you will be able to select your JVM and connect to it. The JBoss Cache MBeans will be available on the MBeans panel."
+#. Tag: para
+#: Mgmt_information.xml:638
+#, no-c-format
+msgid ""
+"When the utility loads, you will be able to select your JVM and connect to "
+"it. The JBoss Cache MBeans will be available on the MBeans panel."
msgstr ""
-#: ./Mgmt_information.xml:695(para)
-msgid "Note: The <emphasis>jconsole</emphasis> utility will automatically register as a listener for cache notifications when connected to a JVM running JBoss Cache instances."
+#. Tag: para
+#: Mgmt_information.xml:642
+#, no-c-format
+msgid ""
+"Note: The <emphasis>jconsole</emphasis> utility will automatically register "
+"as a listener for cache notifications when connected to a JVM running JBoss "
+"Cache instances."
msgstr ""
-#: ./Mgmt_information.xml:698(para)
-msgid "The following figure shows cache interceptor MBeans in <emphasis>jconsole</emphasis>. Cache statistics are displayed for the CacheMgmt interceptor:"
+#. Tag: para
+#: Mgmt_information.xml:645
+#, no-c-format
+msgid ""
+"The following figure shows cache interceptor MBeans in <emphasis>jconsole</"
+"emphasis>. Cache statistics are displayed for the CacheMgmt interceptor:"
msgstr ""
-#: ./Mgmt_information.xml:702(title)
+#. Tag: title
+#: Mgmt_information.xml:649
+#, no-c-format
msgid "CacheMgmtInterceptor MBean"
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Mgmt_information.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Replication.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Replication.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Replication.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,195 +1,491 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:25-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:16+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./Replication.xml:127(None)
-msgid "@@image: 'images/PackageOverview-BuddyReplication.png'; md5=cc12e01d13713d372f6231d8d4c4c48e"
-msgstr ""
-
-#: ./Replication.xml:10(title)
+#. Tag: title
+#: Replication.xml:5
+#, no-c-format
msgid "Clustered Caches"
msgstr ""
-#: ./Replication.xml:11(para)
-msgid "The <literal>TreeCache</literal> can be configured to be either local (standalone) or clustered. If in a cluster, the cache can be configured to replicate changes, or to invalidate changes. A detailed discussion on this follows."
+#. Tag: para
+#: Replication.xml:6
+#, no-c-format
+msgid ""
+"The <literal>TreeCache</literal> can be configured to be either local "
+"(standalone) or clustered. If in a cluster, the cache can be configured to "
+"replicate changes, or to invalidate changes. A detailed discussion on this "
+"follows."
msgstr ""
-#: ./Replication.xml:15(title)
+#. Tag: title
+#: Replication.xml:10
+#, no-c-format
msgid "Local Cache"
msgstr ""
-#: ./Replication.xml:16(para)
-msgid "Local caches don't join a cluster and don't communicate with other nodes in a cluster. Therefore their elements don't need to be serializable - however, we recommend making them serializable, enabling a user to change the cache mode at any time."
+#. Tag: para
+#: Replication.xml:11
+#, no-c-format
+msgid ""
+"Local caches don't join a cluster and don't communicate with other nodes in "
+"a cluster. Therefore their elements don't need to be serializable - however, "
+"we recommend making them serializable, enabling a user to change the cache "
+"mode at any time."
msgstr ""
-#: ./Replication.xml:22(title)
+#. Tag: title
+#: Replication.xml:17
+#, no-c-format
msgid "Clustered Cache - Using Replication"
msgstr ""
-#: ./Replication.xml:23(para)
-msgid "Replicated caches replicate all changes to the other <literal>TreeCache</literal> instances in the cluster. Replication can either happen after each modification (no transactions), or at the end of a transaction (commit time)."
+#. Tag: para
+#: Replication.xml:18
+#, no-c-format
+msgid ""
+"Replicated caches replicate all changes to the other <literal>TreeCache</"
+"literal> instances in the cluster. Replication can either happen after each "
+"modification (no transactions), or at the end of a transaction (commit time)."
msgstr ""
-#: ./Replication.xml:26(para)
-msgid "Replication can be synchronous or asynchronous . Use of either one of the options is application dependent. Synchronous replication blocks the caller (e.g. on a put()) until the modifications have been replicated successfully to all nodes in a cluster. Asynchronous replication performs replication in the background (the put() returns immediately). <literal>TreeCache</literal> also offers a replication queue, where modifications are replicated periodically (i.e. interval-based), or when the queue size exceeds a number of elements, or a combination thereof."
+#. Tag: para
+#: Replication.xml:21
+#, no-c-format
+msgid ""
+"Replication can be synchronous or asynchronous . Use of either one of the "
+"options is application dependent. Synchronous replication blocks the caller "
+"(e.g. on a put()) until the modifications have been replicated successfully "
+"to all nodes in a cluster. Asynchronous replication performs replication in "
+"the background (the put() returns immediately). <literal>TreeCache</literal> "
+"also offers a replication queue, where modifications are replicated "
+"periodically (i.e. interval-based), or when the queue size exceeds a number "
+"of elements, or a combination thereof."
msgstr ""
-#: ./Replication.xml:29(para)
-msgid "Asynchronous replication is faster (no caller blocking), because synchronous replication requires acknowledgments from all nodes in a cluster that they received and applied the modification successfully (round-trip time). However, when a synchronous replication returns successfully, the caller knows for sure that all modifications have been applied at all nodes, whereas this may or may not be the case with asynchronous replication. With asynchronous replication, errors are simply written to a log. Even when using transactions, a transaction may succeed but replication may not succeed on all <literal>TreeCache</literal> instances."
+#. Tag: para
+#: Replication.xml:24
+#, no-c-format
+msgid ""
+"Asynchronous replication is faster (no caller blocking), because synchronous "
+"replication requires acknowledgments from all nodes in a cluster that they "
+"received and applied the modification successfully (round-trip time). "
+"However, when a synchronous replication returns successfully, the caller "
+"knows for sure that all modifications have been applied at all nodes, "
+"whereas this may or may not be the case with asynchronous replication. With "
+"asynchronous replication, errors are simply written to a log. Even when "
+"using transactions, a transaction may succeed but replication may not "
+"succeed on all <literal>TreeCache</literal> instances."
msgstr ""
-#: ./Replication.xml:33(title)
+#. Tag: title
+#: Replication.xml:28
+#, no-c-format
msgid "Replicated Caches and Transactions"
msgstr ""
-#: ./Replication.xml:34(para)
-msgid "When using transactions, replication only occurs at the transaction boundary - i.e., when a transaction commits. This results in minimising replication traffic since a single modification os broadcast rather than a series of individual modifications, and can be a lot more efficient than not using transactions. Another effect of this is that if a transaction were to roll back, nothing is broadcast across a cluster."
+#. Tag: para
+#: Replication.xml:29
+#, no-c-format
+msgid ""
+"When using transactions, replication only occurs at the transaction boundary "
+"- i.e., when a transaction commits. This results in minimising replication "
+"traffic since a single modification os broadcast rather than a series of "
+"individual modifications, and can be a lot more efficient than not using "
+"transactions. Another effect of this is that if a transaction were to roll "
+"back, nothing is broadcast across a cluster."
msgstr ""
-#: ./Replication.xml:37(para)
-msgid "Depending on whether you are running your cluster in asynchronous or synchronous mode, JBoss Cache will use either a single phase or <ulink url=\"http://en.wikipedia.org/wiki/Two-phase_commit_protocol\">two phase commit</ulink> protocol, respectively."
+#. Tag: para
+#: Replication.xml:32
+#, no-c-format
+msgid ""
+"Depending on whether you are running your cluster in asynchronous or "
+"synchronous mode, JBoss Cache will use either a single phase or <ulink url="
+"\"http://en.wikipedia.org/wiki/Two-phase_commit_protocol\">two phase commit</"
+"ulink> protocol, respectively."
msgstr ""
-#: ./Replication.xml:41(title)
+#. Tag: title
+#: Replication.xml:36
+#, no-c-format
msgid "One Phase Commits"
msgstr ""
-#: ./Replication.xml:42(para)
-msgid "Used when your cache mode is REPL_ASYNC. All modifications are replicated in a single call, which instructs remote caches to apply the changes to their local in-memory state and commit locally. Remote errors/rollbacks are never fed back to the originator of the transaction since the communication is asynchronous."
+#. Tag: para
+#: Replication.xml:37
+#, no-c-format
+msgid ""
+"Used when your cache mode is REPL_ASYNC. All modifications are replicated in "
+"a single call, which instructs remote caches to apply the changes to their "
+"local in-memory state and commit locally. Remote errors/rollbacks are never "
+"fed back to the originator of the transaction since the communication is "
+"asynchronous."
msgstr ""
-#: ./Replication.xml:48(title)
+#. Tag: title
+#: Replication.xml:43
+#, no-c-format
msgid "Two Phase Commits"
msgstr ""
-#: ./Replication.xml:49(para)
-msgid "Used when your cache mode is REPL_SYNC. Upon committing your transaction, JBoss Cache broadcasts a prepare call, which carries all modifications relevant to the transaction. Remote caches then acquire local locks on their im-memory state and apply the modifications. Once all remote caches respond to the prepare call, the originator of the transaction broadcasts a commit. This instructs all remote caches to commit their data. If any of the caches fail to respond to the prepare phase, the originator broadcasts a rollback."
+#. Tag: para
+#: Replication.xml:44
+#, no-c-format
+msgid ""
+"Used when your cache mode is REPL_SYNC. Upon committing your transaction, "
+"JBoss Cache broadcasts a prepare call, which carries all modifications "
+"relevant to the transaction. Remote caches then acquire local locks on their "
+"im-memory state and apply the modifications. Once all remote caches respond "
+"to the prepare call, the originator of the transaction broadcasts a commit. "
+"This instructs all remote caches to commit their data. If any of the caches "
+"fail to respond to the prepare phase, the originator broadcasts a rollback."
msgstr ""
-#: ./Replication.xml:52(para)
-msgid "Note that although the prepare phase is synchronous, the commit and rollback phases are asynchronous. This is because <ulink url=\"http://java.sun.com/products/jta/\">Sun's JTA specification</ulink> does not specify how transactional resources should deal with failures at this stage of a transaction; and other resources participating in the transaction may have indeterminate state anyway. As such, we do away with the overhead of synchronous communication for this phase of the transaction. That said, they can be forced to be synchronous using the <literal>SyncCommitPhase</literal> and <literal>SyncRollbackPhase</literal> configuration options."
+#. Tag: para
+#: Replication.xml:47
+#, no-c-format
+msgid ""
+"Note that although the prepare phase is synchronous, the commit and rollback "
+"phases are asynchronous. This is because <ulink url=\"http://java.sun.com/"
+"products/jta/\">Sun's JTA specification</ulink> does not specify how "
+"transactional resources should deal with failures at this stage of a "
+"transaction; and other resources participating in the transaction may have "
+"indeterminate state anyway. As such, we do away with the overhead of "
+"synchronous communication for this phase of the transaction. That said, they "
+"can be forced to be synchronous using the <literal>SyncCommitPhase</literal> "
+"and <literal>SyncRollbackPhase</literal> configuration options."
msgstr ""
-#: ./Replication.xml:60(title)
+#. Tag: title
+#: Replication.xml:55
+#, no-c-format
msgid "Buddy Replication"
msgstr ""
-#: ./Replication.xml:61(para)
-msgid "Buddy Replication allows you to suppress replicating your data to all instances in a cluster. Instead, each instance picks one or more 'buddies' in the cluster, and only replicates to these specific buddies. This greatly helps scalability as there is no longer a memory and network traffic impact every time another instance is added to a cluster."
+#. Tag: para
+#: Replication.xml:56
+#, no-c-format
+msgid ""
+"Buddy Replication allows you to suppress replicating your data to all "
+"instances in a cluster. Instead, each instance picks one or more 'buddies' "
+"in the cluster, and only replicates to these specific buddies. This greatly "
+"helps scalability as there is no longer a memory and network traffic impact "
+"every time another instance is added to a cluster."
msgstr ""
-#: ./Replication.xml:64(para)
-msgid "One of the most common use cases of Buddy Replication is when a replicated cache is used by a servlet container to store HTTP session data. One of the pre-requisites to buddy replication working well and being a real benefit is the use of <emphasis>session affinity</emphasis>, also known as <emphasis>sticky sessions</emphasis> in HTTP session replication speak. What this means is that if certain data is frequently accessed, it is desirable that this is always accessed on one instance rather than in a round-robin fashion as this helps the cache cluster optimise how it chooses buddies, where it stores data, and minimises replication traffic."
+#. Tag: para
+#: Replication.xml:59
+#, no-c-format
+msgid ""
+"One of the most common use cases of Buddy Replication is when a replicated "
+"cache is used by a servlet container to store HTTP session data. One of the "
+"pre-requisites to buddy replication working well and being a real benefit is "
+"the use of <emphasis>session affinity</emphasis>, also known as "
+"<emphasis>sticky sessions</emphasis> in HTTP session replication speak. What "
+"this means is that if certain data is frequently accessed, it is desirable "
+"that this is always accessed on one instance rather than in a round-robin "
+"fashion as this helps the cache cluster optimise how it chooses buddies, "
+"where it stores data, and minimises replication traffic."
msgstr ""
-#: ./Replication.xml:67(para)
-msgid "If this is not possible, Buddy Replication may prove to be more of an overhead than a benefit."
+#. Tag: para
+#: Replication.xml:62
+#, no-c-format
+msgid ""
+"If this is not possible, Buddy Replication may prove to be more of an "
+"overhead than a benefit."
msgstr ""
-#: ./Replication.xml:71(title)
+#. Tag: title
+#: Replication.xml:66
+#, no-c-format
msgid "Selecting Buddies"
msgstr ""
-#: ./Replication.xml:72(para)
-msgid "Buddy Replication uses an instance of a <literal>org.jboss.cache.buddyreplication.BuddyLocator</literal> which contains the logic used to select buddies in a network. JBoss Cache currently ships with a single implementation, <literal>org.jboss.cache.buddyreplication.NextMemberBuddyLocator</literal>, which is used as a default if no implementation is provided. The <literal>NextMemberBuddyLocator</literal> selects the next member in the cluster, as the name suggests, and guarantees an even spread of buddies for each instance."
+#. Tag: para
+#: Replication.xml:67
+#, no-c-format
+msgid ""
+"Buddy Replication uses an instance of a <literal>org.jboss.cache."
+"buddyreplication.BuddyLocator</literal> which contains the logic used to "
+"select buddies in a network. JBoss Cache currently ships with a single "
+"implementation, <literal>org.jboss.cache.buddyreplication."
+"NextMemberBuddyLocator</literal>, which is used as a default if no "
+"implementation is provided. The <literal>NextMemberBuddyLocator</literal> "
+"selects the next member in the cluster, as the name suggests, and guarantees "
+"an even spread of buddies for each instance."
msgstr ""
-#: ./Replication.xml:78(para)
-msgid "<literal>numBuddies</literal> - specifies how many buddies each instance should pick to back its data onto. This defaults to 1."
+#. Tag: para
+#: Replication.xml:70
+#, no-c-format
+msgid ""
+"The <literal>NextMemberBuddyLocator</literal> takes in 2 parameters, both "
+"optional."
msgstr ""
-#: ./Replication.xml:81(para)
-msgid "<literal>ignoreColocatedBuddies</literal> - means that each instance will <emphasis>try</emphasis> to select a buddy on a different physical host. If not able to do so though, it will fall back to colocated instances. This defaults to <literal>true</literal>."
+#. Tag: para
+#: Replication.xml:73
+#, no-c-format
+msgid ""
+"<literal>numBuddies</literal> - specifies how many buddies each instance "
+"should pick to back its data onto. This defaults to 1."
msgstr ""
-#: ./Replication.xml:75(para)
-msgid "The <literal>NextMemberBuddyLocator</literal> takes in 2 parameters, both optional. <placeholder-1/>"
+#. Tag: para
+#: Replication.xml:76
+#, no-c-format
+msgid ""
+"<literal>ignoreColocatedBuddies</literal> - means that each instance will "
+"<emphasis>try</emphasis> to select a buddy on a different physical host. If "
+"not able to do so though, it will fall back to colocated instances. This "
+"defaults to <literal>true</literal>."
msgstr ""
-#: ./Replication.xml:88(title)
+#. Tag: title
+#: Replication.xml:83
+#, no-c-format
msgid "BuddyPools"
msgstr ""
-#: ./Replication.xml:89(para)
-msgid "Also known as replication groups, a buddy pool is an optional construct where each instance in a cluster may be configured with a buddy pool name. Think of this as an 'exclusive club membership' where when selecting buddies, <literal>BuddyLocator</literal>s would try and select buddies sharing the same buddy pool name. This allows system administrators a degree of flexibility and control over how buddies are selected. For example, a sysadmin may put two instances on two separate physical servers that may be on two separate physical racks in the same buddy pool. So rather than picking an instance on a different host on the same rack, <literal>BuddyLocator</literal>s would rather pick the instance in the same buddy pool, on a separate rack which may add a degree of redundancy."
+#. Tag: para
+#: Replication.xml:84
+#, no-c-format
+msgid ""
+"Also known as replication groups, a buddy pool is an optional construct "
+"where each instance in a cluster may be configured with a buddy pool name. "
+"Think of this as an 'exclusive club membership' where when selecting "
+"buddies, <literal>BuddyLocator</literal>s would try and select buddies "
+"sharing the same buddy pool name. This allows system administrators a degree "
+"of flexibility and control over how buddies are selected. For example, a "
+"sysadmin may put two instances on two separate physical servers that may be "
+"on two separate physical racks in the same buddy pool. So rather than "
+"picking an instance on a different host on the same rack, "
+"<literal>BuddyLocator</literal>s would rather pick the instance in the same "
+"buddy pool, on a separate rack which may add a degree of redundancy."
msgstr ""
-#: ./Replication.xml:95(title)
+#. Tag: title
+#: Replication.xml:90
+#, no-c-format
msgid "Failover"
msgstr ""
-#: ./Replication.xml:96(para)
-msgid "In the unfortunate event of an instance crashing, it is assumed that the client connecting to the cache (directly or indirectly, via some other service such as HTTP session replication) is able to redirect the request to any other random cache instance in the cluster. This is where a concept of Data Gravitation comes in."
+#. Tag: para
+#: Replication.xml:91
+#, no-c-format
+msgid ""
+"In the unfortunate event of an instance crashing, it is assumed that the "
+"client connecting to the cache (directly or indirectly, via some other "
+"service such as HTTP session replication) is able to redirect the request to "
+"any other random cache instance in the cluster. This is where a concept of "
+"Data Gravitation comes in."
msgstr ""
-#: ./Replication.xml:99(para)
-msgid "Data Gravitation is a concept where if a request is made on a cache in the cluster and the cache does not contain this information, it then asks other instances in the cluster for the data. If even this fails, it would (optionally) ask other instances to check in the backup data they store for other caches. This means that even if a cache containing your session dies, other instances will still be able to access this data by asking the cluster to search through their backups for this data."
+#. Tag: para
+#: Replication.xml:94
+#, no-c-format
+msgid ""
+"Data Gravitation is a concept where if a request is made on a cache in the "
+"cluster and the cache does not contain this information, it then asks other "
+"instances in the cluster for the data. If even this fails, it would "
+"(optionally) ask other instances to check in the backup data they store for "
+"other caches. This means that even if a cache containing your session dies, "
+"other instances will still be able to access this data by asking the cluster "
+"to search through their backups for this data."
msgstr ""
-#: ./Replication.xml:102(para)
-msgid "Once located, this data is then transferred to the instance which requested it and is added to this instance's data tree. It is then (optionally) removed from all other instances (and backups) so that if session affinity is used, the affinity should now be to this new cache instance which has just <emphasis>taken ownership</emphasis> of this data."
+#. Tag: para
+#: Replication.xml:97
+#, no-c-format
+msgid ""
+"Once located, this data is then transferred to the instance which requested "
+"it and is added to this instance's data tree. It is then (optionally) "
+"removed from all other instances (and backups) so that if session affinity "
+"is used, the affinity should now be to this new cache instance which has "
+"just <emphasis>taken ownership</emphasis> of this data."
msgstr ""
-#: ./Replication.xml:108(para)
-msgid "<literal>dataGravitationRemoveOnFind</literal> - forces all remote caches that own the data or hold backups for the data to remove that data, thereby making the requesting cache the new data owner. If set to <literal>false</literal> an evict is broadcast instead of a remove, so any state persisted in cache loaders will remain. This is useful if you have a shared cache loader configured. Defaults to <literal>true</literal>."
+#. Tag: para
+#: Replication.xml:100
+#, no-c-format
+msgid ""
+"Data Gravitation is implemented as an interceptor. The following (all "
+"optional) configuration properties pertain to data gravitation."
msgstr ""
-#: ./Replication.xml:111(para)
-msgid "<literal>dataGravitationSearchBackupTrees</literal> - Asks remote instances to search through their backups as well as main data trees. Defaults to <literal>true</literal>. The resulting effect is that if this is <literal>true</literal> then backup nodes can respond to data gravitation requests in addition to data owners."
+#. Tag: para
+#: Replication.xml:103
+#, no-c-format
+msgid ""
+"<literal>dataGravitationRemoveOnFind</literal> - forces all remote caches "
+"that own the data or hold backups for the data to remove that data, thereby "
+"making the requesting cache the new data owner. If set to <literal>false</"
+"literal> an evict is broadcast instead of a remove, so any state persisted "
+"in cache loaders will remain. This is useful if you have a shared cache "
+"loader configured. Defaults to <literal>true</literal>."
msgstr ""
-#: ./Replication.xml:114(para)
-msgid "<literal>autoDataGravitation</literal> - Whether data gravitation occurs for every cache miss. My default this is set to <literal>false</literal> to prevent unnecessary network calls. Most use cases will know when it may need to gravitate data and will pass in an <literal>Option</literal> to enable data gravitation on a per-invocation basis. If <literal>autoDataGravitation</literal> is <literal>true</literal> this <literal>Option</literal> is unnecessary."
+#. Tag: para
+#: Replication.xml:106
+#, no-c-format
+msgid ""
+"<literal>dataGravitationSearchBackupTrees</literal> - Asks remote instances "
+"to search through their backups as well as main data trees. Defaults to "
+"<literal>true</literal>. The resulting effect is that if this is "
+"<literal>true</literal> then backup nodes can respond to data gravitation "
+"requests in addition to data owners."
msgstr ""
-#: ./Replication.xml:105(para)
-msgid "Data Gravitation is implemented as an interceptor. The following (all optional) configuration properties pertain to data gravitation. <placeholder-1/>"
+#. Tag: para
+#: Replication.xml:109
+#, no-c-format
+msgid ""
+"<literal>autoDataGravitation</literal> - Whether data gravitation occurs for "
+"every cache miss. My default this is set to <literal>false</literal> to "
+"prevent unnecessary network calls. Most use cases will know when it may need "
+"to gravitate data and will pass in an <literal>Option</literal> to enable "
+"data gravitation on a per-invocation basis. If <literal>autoDataGravitation</"
+"literal> is <literal>true</literal> this <literal>Option</literal> is "
+"unnecessary."
msgstr ""
-#: ./Replication.xml:121(title)
+#. Tag: title
+#: Replication.xml:116
+#, no-c-format
msgid "Implementation"
msgstr ""
-#: ./Replication.xml:124(title)
-msgid "Class diagram of the classes involved in buddy replication and how they are related to each other"
+#. Tag: title
+#: Replication.xml:119
+#, no-c-format
+msgid ""
+"Class diagram of the classes involved in buddy replication and how they are "
+"related to each other"
msgstr ""
-#: ./Replication.xml:135(title)
+#. Tag: title
+#: Replication.xml:130
+#, no-c-format
msgid "Configuration"
msgstr ""
-#: ./Replication.xml:137(programlisting)
-#, no-wrap
-msgid "\n<!-- Buddy Replication config -->\n<attribute name=\"BuddyReplicationConfig\">\n<config>\n \n<!-- Enables buddy replication. This is the ONLY mandatory configuration element here. -->\n<buddyReplicationEnabled>true</buddyReplicationEnabled>\n \n<!-- These are the default values anyway -->\n<buddyLocatorClass>\n org.jboss.cache.buddyreplication.NextMemberBuddyLocator\n</buddyLocatorClass>\n \n<!-- numBuddies is the number of backup nodes each node maintains. \nignoreColocatedBuddies means that each node will *try* to select a buddy on a different \nphysical host. If not able to do so though, it will fall back to colocated nodes. -->\n<buddyLocatorProperties>\n numBuddies = 1\n ignoreColocatedBuddies = true\n</buddyLocatorProperties>\n \n<!-- A way to specify a preferred replica!
tion group. If specified, we try to pick a \nbuddy who shares the same pool name (falling back to other buddies if not available).\nThis allows the sysdmin to hint at backup buddies are picked, so for example, nodes may be \nhinted to pick buddies on a different physical rack or power supply for added fault tolerance. \n-->\n<buddyPoolName>myBuddyPoolReplicationGroup</buddyPoolName>\n \n<!-- Communication timeout for inter-buddy group organisation messages (such as assigning \nto and removing from groups, defaults to 1000. -->\n<buddyCommunicationTimeout>2000</buddyCommunicationTimeout>\n\n<!-- Whether data is removed from old owners when gravitated to a new owner. \nDefaults to true. -->\n<dataGravitationRemoveOnFind>true</dataGravitationRemoveOnFind>\n\n<!-- Whether backup nodes can respond to data gravitation requests, or only the data owner \nis supposed to respond. Defaults to true. --!
>\n<dataGravitationSearchBackupTrees>true</dataGravitation
SearchBackupTrees>\n\n<!-- Whether all cache misses result in a data gravitation request. Defaults to false, \nrequiring callers to enable data gravitation on a per-invocation basis using the Options API. \n-->\n<autoDataGravitation>false</autoDataGravitation>\n\n</config>\n</attribute>\n \n \n"
+#. Tag: programlisting
+#: Replication.xml:132
+#, no-c-format
+msgid ""
+"<!-- Buddy Replication config -->\n"
+"<attribute name=\"BuddyReplicationConfig\">\n"
+"<config>\n"
+" \n"
+"<!-- Enables buddy replication. This is the ONLY mandatory configuration "
+"element here. -->\n"
+"<buddyReplicationEnabled>true</buddyReplicationEnabled>\n"
+" \n"
+"<!-- These are the default values anyway -->\n"
+"<buddyLocatorClass>\n"
+" org.jboss.cache.buddyreplication.NextMemberBuddyLocator\n"
+"</buddyLocatorClass>\n"
+" \n"
+"<!-- numBuddies is the number of backup nodes each node maintains. \n"
+"ignoreColocatedBuddies means that each node will *try* to select a buddy on "
+"a different \n"
+"physical host. If not able to do so though, it will fall back to colocated "
+"nodes. -->\n"
+"<buddyLocatorProperties>\n"
+" numBuddies = 1\n"
+" ignoreColocatedBuddies = true\n"
+"</buddyLocatorProperties>\n"
+" \n"
+"<!-- A way to specify a preferred replication group. If specified, we "
+"try to pick a \n"
+"buddy who shares the same pool name (falling back to other buddies if not "
+"available).\n"
+"This allows the sysdmin to hint at backup buddies are picked, so for "
+"example, nodes may be \n"
+"hinted to pick buddies on a different physical rack or power supply for "
+"added fault tolerance. \n"
+"-->\n"
+"<buddyPoolName>myBuddyPoolReplicationGroup</buddyPoolName>\n"
+" \n"
+"<!-- Communication timeout for inter-buddy group organisation messages "
+"(such as assigning \n"
+"to and removing from groups, defaults to 1000. -->\n"
+"<buddyCommunicationTimeout>2000</buddyCommunicationTimeout>\n"
+"\n"
+"<!-- Whether data is removed from old owners when gravitated to a new "
+"owner. \n"
+"Defaults to true. -->\n"
+"<dataGravitationRemoveOnFind>true</dataGravitationRemoveOnFind>\n"
+"\n"
+"<!-- Whether backup nodes can respond to data gravitation requests, or "
+"only the data owner \n"
+"is supposed to respond. Defaults to true. -->\n"
+"<dataGravitationSearchBackupTrees>true</"
+"dataGravitationSearchBackupTrees>\n"
+"\n"
+"<!-- Whether all cache misses result in a data gravitation request. "
+"Defaults to false, \n"
+"requiring callers to enable data gravitation on a per-invocation basis using "
+"the Options API. \n"
+"-->\n"
+"<autoDataGravitation>false</autoDataGravitation>\n"
+"\n"
+"</config>\n"
+"</attribute>"
msgstr ""
-#: ./Replication.xml:195(title)
+#. Tag: title
+#: Replication.xml:141
+#, no-c-format
msgid "Clustered Cache - Using Invalidation"
msgstr ""
-#: ./Replication.xml:196(para)
-msgid "If a cache is configured for invalidation rather than replication, every time data is changed in a cache other caches in the cluster receive a message informing them that their data is now stale and should be evicted from memory. Invalidation, when used with a shared cache loader (see chapter on Cache Loaders) would cause remote caches to refer to the shared cache loader to retrieve modified data. The benefit of this is twofold: network traffic is minimised as invalidation messages are very small compared to replicating updated data, and also that other caches in the cluster look up modified data in a lazy manner, only when needed."
+#. Tag: para
+#: Replication.xml:142
+#, no-c-format
+msgid ""
+"If a cache is configured for invalidation rather than replication, every "
+"time data is changed in a cache other caches in the cluster receive a "
+"message informing them that their data is now stale and should be evicted "
+"from memory. Invalidation, when used with a shared cache loader (see chapter "
+"on Cache Loaders) would cause remote caches to refer to the shared cache "
+"loader to retrieve modified data. The benefit of this is twofold: network "
+"traffic is minimised as invalidation messages are very small compared to "
+"replicating updated data, and also that other caches in the cluster look up "
+"modified data in a lazy manner, only when needed."
msgstr ""
-#: ./Replication.xml:199(para)
-msgid "Invalidation messages are sent after each modification (no transactions), or at the end of a transaction, upon successful commit. This is usually more efficient as invalidation messages can be optimised for the transaction as a whole rather than on a per-modification basis."
+#. Tag: para
+#: Replication.xml:145
+#, no-c-format
+msgid ""
+"Invalidation messages are sent after each modification (no transactions), or "
+"at the end of a transaction, upon successful commit. This is usually more "
+"efficient as invalidation messages can be optimised for the transaction as a "
+"whole rather than on a per-modification basis."
msgstr ""
-#: ./Replication.xml:202(para)
-msgid "Invalidation too can be synchronous or asynchronous, and just as in the case of replication, synchronous invalidation blocks until all caches in the cluster receive invalidation messages and have evicted stale data while asynchronous invalidation works in a 'fire-and-forget' mode, where invalidation messages are broadcast but doesn't block and wait for responses."
+#. Tag: para
+#: Replication.xml:148
+#, no-c-format
+msgid ""
+"Invalidation too can be synchronous or asynchronous, and just as in the case "
+"of replication, synchronous invalidation blocks until all caches in the "
+"cluster receive invalidation messages and have evicted stale data while "
+"asynchronous invalidation works in a 'fire-and-forget' mode, where "
+"invalidation messages are broadcast but doesn't block and wait for responses."
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Replication.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/State_transfer.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/State_transfer.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/State_transfer.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,116 +1,266 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:25-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:16+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ./State_transfer.xml:10(title)
+#. Tag: title
+#: State_transfer.xml:5
+#, no-c-format
msgid "State Transfer"
msgstr ""
-#: ./State_transfer.xml:11(para)
-msgid "\"State Transfer\" refers to the process by which a JBoss Cache instance prepares itself to begin providing a service by acquiring the current state from another cache instance and integrating that state into its own state."
+#. Tag: para
+#: State_transfer.xml:6
+#, no-c-format
+msgid ""
+"\"State Transfer\" refers to the process by which a JBoss Cache instance "
+"prepares itself to begin providing a service by acquiring the current state "
+"from another cache instance and integrating that state into its own state."
msgstr ""
-#: ./State_transfer.xml:15(title)
+#. Tag: title
+#: State_transfer.xml:10
+#, no-c-format
msgid "Types of State Transfer"
msgstr ""
-#: ./State_transfer.xml:16(para)
-msgid "The state that is acquired and integrated can consist of two basic types:"
+#. Tag: para
+#: State_transfer.xml:11
+#, no-c-format
+msgid ""
+"The state that is acquired and integrated can consist of two basic types:"
msgstr ""
-#: ./State_transfer.xml:21(para)
-msgid "\"Transient\" or \"in-memory\" state. This consists of the actual in-memory state of another cache instance -- the contents of the various in-memory nodes in the cache that is providing state are serialized and transferred; the recipient deserializes the data, creates corresponding nodes in its own in-memory tree, and populates them with the transferred data."
+#. Tag: para
+#: State_transfer.xml:16
+#, no-c-format
+msgid ""
+"\"Transient\" or \"in-memory\" state. This consists of the actual in-memory "
+"state of another cache instance -- the contents of the various in-memory "
+"nodes in the cache that is providing state are serialized and transferred; "
+"the recipient deserializes the data, creates corresponding nodes in its own "
+"in-memory tree, and populates them with the transferred data."
msgstr ""
-#: ./State_transfer.xml:24(para)
-msgid "\"In-memory\" state transfer is enabled by setting the cache's <literal>FetchInMemoryState</literal> property to <literal>true</literal>."
+#. Tag: para
+#: State_transfer.xml:19
+#, no-c-format
+msgid ""
+"\"In-memory\" state transfer is enabled by setting the cache's "
+"<literal>FetchInMemoryState</literal> property to <literal>true</literal>."
msgstr ""
-#: ./State_transfer.xml:29(para)
-msgid "\"Persistent\" state. Only applicable if a non-shared cache loader is used. The state stored in the state-provider cache's persistent store is deserialized and transferred; the recipient passes the data to its own cache loader, which persists it to the recipient's persistent store."
+#. Tag: para
+#: State_transfer.xml:24
+#, no-c-format
+msgid ""
+"\"Persistent\" state. Only applicable if a non-shared cache loader is used. "
+"The state stored in the state-provider cache's persistent store is "
+"deserialized and transferred; the recipient passes the data to its own cache "
+"loader, which persists it to the recipient's persistent store."
msgstr ""
-#: ./State_transfer.xml:32(para)
-msgid "\"Persistent\" state transfer is enabled by setting a cache loader's <literal>CacheLoaderFetchPersistentState</literal> property to <literal>true</literal>. If multiple cache loaders are configured in a chain, only one can have this property set to true; otherwise you will get an exception at startup."
+#. Tag: para
+#: State_transfer.xml:27
+#, no-c-format
+msgid ""
+"\"Persistent\" state transfer is enabled by setting a cache loader's "
+"<literal>CacheLoaderFetchPersistentState</literal> property to "
+"<literal>true</literal>. If multiple cache loaders are configured in a "
+"chain, only one can have this property set to true; otherwise you will get "
+"an exception at startup."
msgstr ""
-#: ./State_transfer.xml:35(para)
-msgid "Persistent state transfer with a shared cache loader does not make sense, as the same persistent store that provides the data will just end up receiving it. Therefore, if a shared cache loader is used, the cache will not allow a persistent state transfer even if a cache loader has <literal>CacheLoaderFetchPersistentState</literal> set to <literal>true</literal>."
+#. Tag: para
+#: State_transfer.xml:30
+#, no-c-format
+msgid ""
+"Persistent state transfer with a shared cache loader does not make sense, as "
+"the same persistent store that provides the data will just end up receiving "
+"it. Therefore, if a shared cache loader is used, the cache will not allow a "
+"persistent state transfer even if a cache loader has "
+"<literal>CacheLoaderFetchPersistentState</literal> set to <literal>true</"
+"literal>."
msgstr ""
-#: ./State_transfer.xml:40(para)
-msgid "Which of these types of state transfer is appropriate depends on the usage of the cache."
+#. Tag: para
+#: State_transfer.xml:35
+#, no-c-format
+msgid ""
+"Which of these types of state transfer is appropriate depends on the usage "
+"of the cache."
msgstr ""
-#: ./State_transfer.xml:45(para)
-msgid "If a write-through cache loader is used, the current cache state is fully represented by the persistent state. Data may have been evicted from the in-memory state, but it will still be in the persistent store. In this case, if the cache loader is not shared, persistent state transfer is used to ensure the new cache has the correct state. In-memory state can be transferred as well if the desire is to have a \"hot\" cache -- one that has all relevant data in memory when the cache begins providing service. (Note that the \"CacheLoaderPreload\" configuration parameter can be used as well to provide a \"warm\" or \"hot\" cache without requiring an in-memory state transfer. This approach somewhat reduces the burden on the cache instance providing state, but increases the load on the persistent store on the recipient side.)"
+#. Tag: para
+#: State_transfer.xml:40
+#, no-c-format
+msgid ""
+"If a write-through cache loader is used, the current cache state is fully "
+"represented by the persistent state. Data may have been evicted from the in-"
+"memory state, but it will still be in the persistent store. In this case, if "
+"the cache loader is not shared, persistent state transfer is used to ensure "
+"the new cache has the correct state. In-memory state can be transferred as "
+"well if the desire is to have a \"hot\" cache -- one that has all relevant "
+"data in memory when the cache begins providing service. (Note that the "
+"\"CacheLoaderPreload\" configuration parameter can be used as well to "
+"provide a \"warm\" or \"hot\" cache without requiring an in-memory state "
+"transfer. This approach somewhat reduces the burden on the cache instance "
+"providing state, but increases the load on the persistent store on the "
+"recipient side.)"
msgstr ""
-#: ./State_transfer.xml:50(para)
-msgid "If a cache loader is used with passivation, the full representation of the state can only be obtained by combining the in-memory (i.e. non-passivated) and persistent (i.e. passivated) states. Therefore an in-memory state transfer is necesssary. A persistent state transfer is necessary if the cache loader is not shared."
+#. Tag: para
+#: State_transfer.xml:45
+#, no-c-format
+msgid ""
+"If a cache loader is used with passivation, the full representation of the "
+"state can only be obtained by combining the in-memory (i.e. non-passivated) "
+"and persistent (i.e. passivated) states. Therefore an in-memory state "
+"transfer is necesssary. A persistent state transfer is necessary if the "
+"cache loader is not shared."
msgstr ""
-#: ./State_transfer.xml:55(para)
-msgid "If no cache loader is used and the cache is solely a write-aside cache (i.e. one that is used to cache data that can also be found in a persistent store, e.g. a database), whether or not in-memory state should be transferred depends on whether or not a \"hot\" cache is desired."
+#. Tag: para
+#: State_transfer.xml:50
+#, no-c-format
+msgid ""
+"If no cache loader is used and the cache is solely a write-aside cache (i.e. "
+"one that is used to cache data that can also be found in a persistent store, "
+"e.g. a database), whether or not in-memory state should be transferred "
+"depends on whether or not a \"hot\" cache is desired."
msgstr ""
-#: ./State_transfer.xml:63(title)
+#. Tag: title
+#: State_transfer.xml:58
+#, no-c-format
msgid "When State Transfer Occurs"
msgstr ""
-#: ./State_transfer.xml:64(para)
-msgid "If either in-memory or persistent state transfer is enabled, a full or partial state transfer will be done at various times, depending on how the cache is used. \"Full\" state transfer refers to the transfer of the state related to the entire tree -- i.e. the root node and all nodes below it. A \"partial\" state transfer is one where just a portion of the tree is transferred -- i.e. a node at a given Fqn and all nodes below it."
+#. Tag: para
+#: State_transfer.xml:59
+#, no-c-format
+msgid ""
+"If either in-memory or persistent state transfer is enabled, a full or "
+"partial state transfer will be done at various times, depending on how the "
+"cache is used. \"Full\" state transfer refers to the transfer of the state "
+"related to the entire tree -- i.e. the root node and all nodes below it. A "
+"\"partial\" state transfer is one where just a portion of the tree is "
+"transferred -- i.e. a node at a given Fqn and all nodes below it."
msgstr ""
-#: ./State_transfer.xml:67(para)
-msgid "If either in-memory or persistent state transfer is enabled, state transfer will occur at the following times:"
+#. Tag: para
+#: State_transfer.xml:62
+#, no-c-format
+msgid ""
+"If either in-memory or persistent state transfer is enabled, state transfer "
+"will occur at the following times:"
msgstr ""
-#: ./State_transfer.xml:72(para)
-msgid "Initial state transfer. This occurs when the cache is first started (as part of the processing of the <literal>start()</literal> method). This is a full state transfer. The state is retrieved from the cache instance that has been operational the longest. If there is any problem receiving or integrating the state, the cache will not start."
+#. Tag: para
+#: State_transfer.xml:67
+#, no-c-format
+msgid ""
+"Initial state transfer. This occurs when the cache is first started (as part "
+"of the processing of the <literal>start()</literal> method). This is a full "
+"state transfer. The state is retrieved from the cache instance that has been "
+"operational the longest. If there is any problem receiving or integrating "
+"the state, the cache will not start."
msgstr ""
-#: ./State_transfer.xml:75(para)
+#. Tag: para
+#: State_transfer.xml:70
+#, no-c-format
msgid "Initial state transfer will occur unless:"
msgstr ""
-#: ./State_transfer.xml:80(para)
-msgid "The cache's <literal>InactiveOnStartup</literal> property is <literal>true</literal>. This property is used in conjunction with region-based marshalling; see below for more on this."
+#. Tag: para
+#: State_transfer.xml:75
+#, no-c-format
+msgid ""
+"The cache's <literal>InactiveOnStartup</literal> property is <literal>true</"
+"literal>. This property is used in conjunction with region-based "
+"marshalling; see below for more on this."
msgstr ""
-#: ./State_transfer.xml:85(para)
-msgid "Buddy replication is used. See below for more on state transfer with buddy replication."
+#. Tag: para
+#: State_transfer.xml:80
+#, no-c-format
+msgid ""
+"Buddy replication is used. See below for more on state transfer with buddy "
+"replication."
msgstr ""
-#: ./State_transfer.xml:92(para)
-msgid "Partial state transfer following region activation. Only relevant when region-based marshalling is used. Here a special classloader is needed to unmarshal the state for a portion of the tree. State transfer cannot succeed until the application registers this classloader with the cache. Once the application registers its classloader, it calls <literal>activateRegion(String fqn)</literal>. As part of the region activation process, a partial state transfer of the relevant subtree's state is performed. The state is requested from the oldest cache instance in the cluster; if that instance responds with no state, state is requested from each instance one by one until one provides state or all instances have been queried."
+#. Tag: para
+#: State_transfer.xml:87
+#, no-c-format
+msgid ""
+"Partial state transfer following region activation. Only relevant when "
+"region-based marshalling is used. Here a special classloader is needed to "
+"unmarshal the state for a portion of the tree. State transfer cannot succeed "
+"until the application registers this classloader with the cache. Once the "
+"application registers its classloader, it calls <literal>activateRegion"
+"(String fqn)</literal>. As part of the region activation process, a partial "
+"state transfer of the relevant subtree's state is performed. The state is "
+"requested from the oldest cache instance in the cluster; if that instance "
+"responds with no state, state is requested from each instance one by one "
+"until one provides state or all instances have been queried."
msgstr ""
-#: ./State_transfer.xml:95(para)
-msgid "Typically when region-based marshalling is used, the cache's <literal>InactiveOnStartup</literal> property is set to <literal>true</literal>. This suppresses initial state transfer, which would fail due to the inability to deserialize the transferred state."
+#. Tag: para
+#: State_transfer.xml:90
+#, no-c-format
+msgid ""
+"Typically when region-based marshalling is used, the cache's "
+"<literal>InactiveOnStartup</literal> property is set to <literal>true</"
+"literal>. This suppresses initial state transfer, which would fail due to "
+"the inability to deserialize the transferred state."
msgstr ""
-#: ./State_transfer.xml:100(para)
-msgid "Buddy replication. When buddy replication is used, initial state transfer is disabled. Instead, when a cache instance joins the cluster, it becomes the buddy of one or more other instances, and one or more other instances become its buddy. Each time an instance determines it has a new buddy providing backup for it, it pushes it's current state to the new buddy. This \"pushing\" of state to the new buddy is slightly different from other forms of state transfer, which are based on a \"pull\" approach (i.e. recipient asks for and receives state). However, the process of preparing and integrating the state is the same."
+#. Tag: para
+#: State_transfer.xml:95
+#, no-c-format
+msgid ""
+"Buddy replication. When buddy replication is used, initial state transfer is "
+"disabled. Instead, when a cache instance joins the cluster, it becomes the "
+"buddy of one or more other instances, and one or more other instances become "
+"its buddy. Each time an instance determines it has a new buddy providing "
+"backup for it, it pushes it's current state to the new buddy. This \"pushing"
+"\" of state to the new buddy is slightly different from other forms of state "
+"transfer, which are based on a \"pull\" approach (i.e. recipient asks for "
+"and receives state). However, the process of preparing and integrating the "
+"state is the same."
msgstr ""
-#: ./State_transfer.xml:103(para)
-msgid "This \"push\" of state upon buddy group formation only occurs if the <literal>InactiveOnStartup</literal> property is set to <literal>false</literal>. If it is <literal>true</literal>, state transfer amongst the buddies only occurs when the application calls <literal>activateRegion(String fqn)</literal> on the various members of the group."
+#. Tag: para
+#: State_transfer.xml:98
+#, no-c-format
+msgid ""
+"This \"push\" of state upon buddy group formation only occurs if the "
+"<literal>InactiveOnStartup</literal> property is set to <literal>false</"
+"literal>. If it is <literal>true</literal>, state transfer amongst the "
+"buddies only occurs when the application calls <literal>activateRegion"
+"(String fqn)</literal> on the various members of the group."
msgstr ""
-#: ./State_transfer.xml:106(para)
-msgid "Partial state transfer following an <literal>activateRegion()</literal> call is slightly different in the buddy replication case as well. Instead of requesting the partial state from one cache instance, and trying all instances until one responds, with buddy replication the instance that is activating a region will request partial state from each instance for which it is serving as a backup."
+#. Tag: para
+#: State_transfer.xml:101
+#, no-c-format
+msgid ""
+"Partial state transfer following an <literal>activateRegion()</literal> call "
+"is slightly different in the buddy replication case as well. Instead of "
+"requesting the partial state from one cache instance, and trying all "
+"instances until one responds, with buddy replication the instance that is "
+"activating a region will request partial state from each instance for which "
+"it is serving as a backup."
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./State_transfer.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Transactions.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Transactions.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Transactions.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,258 +1,579 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:26-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:16+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ./Transactions.xml:10(title)
+#. Tag: title
+#: Transactions.xml:5
+#, no-c-format
msgid "Transactions and Concurrency"
msgstr ""
-#: ./Transactions.xml:12(title)
+#. Tag: title
+#: Transactions.xml:7
+#, no-c-format
msgid "Concurrent Access"
msgstr ""
-#: ./Transactions.xml:13(para)
-msgid "JBoss Cache uses a pessimistic locking scheme by default to prevent concurrent access to the same data. Optimistic locking may alternatively be used, and is discussed later."
+#. Tag: para
+#: Transactions.xml:8
+#, no-c-format
+msgid ""
+"JBoss Cache uses a pessimistic locking scheme by default to prevent "
+"concurrent access to the same data. Optimistic locking may alternatively be "
+"used, and is discussed later."
msgstr ""
-#: ./Transactions.xml:17(title)
+#. Tag: title
+#: Transactions.xml:12
+#, no-c-format
msgid "Locks"
msgstr ""
-#: ./Transactions.xml:18(para)
-msgid "Locking is done internally, on a node-level. For example when we want to access \"/a/b/c\", a lock will be acquired for nodes \"a\", \"b\" and \"c\". When the same transaction wants to access \"/a/b/c/d\", since we already hold locks for \"a\", \"b\" and \"c\", we only need to acquire a lock for \"d\"."
+#. Tag: para
+#: Transactions.xml:13
+#, no-c-format
+msgid ""
+"Locking is done internally, on a node-level. For example when we want to "
+"access \"/a/b/c\", a lock will be acquired for nodes \"a\", \"b\" and \"c\". "
+"When the same transaction wants to access \"/a/b/c/d\", since we already "
+"hold locks for \"a\", \"b\" and \"c\", we only need to acquire a lock for \"d"
+"\"."
msgstr ""
-#: ./Transactions.xml:21(para)
-msgid "Lock owners are either transactions (call is made within the scope of an existing transaction) or threads (no transaction associated with the call). Regardless, a transaction or a thread is internally transformed into an instance of <literal>GlobalTransaction</literal>, which is used as a globally unique ID for modifications across a cluster. E.g. when we run a two-phase commit protocol (see below) across the cluster, the <literal>GlobalTransaction</literal> uniquely identifies the unit of work across a cluster."
+#. Tag: para
+#: Transactions.xml:16
+#, no-c-format
+msgid ""
+"Lock owners are either transactions (call is made within the scope of an "
+"existing transaction) or threads (no transaction associated with the call). "
+"Regardless, a transaction or a thread is internally transformed into an "
+"instance of <literal>GlobalTransaction</literal>, which is used as a "
+"globally unique ID for modifications across a cluster. E.g. when we run a "
+"two-phase commit protocol (see below) across the cluster, the "
+"<literal>GlobalTransaction</literal> uniquely identifies the unit of work "
+"across a cluster."
msgstr ""
-#: ./Transactions.xml:24(para)
-msgid "Locks can be read or write locks. Write locks serialize read and write access, whereas read-only locks only serialize read access. When a write lock is held, no other write or read locks can be acquired. When a read lock is held, others can acquire read locks. However, to acquire write locks, one has to wait until all read locks have been released. When scheduled concurrently, write locks always have precedence over read locks. Note that (if enabled) read locks can be upgraded to write locks."
+#. Tag: para
+#: Transactions.xml:19
+#, no-c-format
+msgid ""
+"Locks can be read or write locks. Write locks serialize read and write "
+"access, whereas read-only locks only serialize read access. When a write "
+"lock is held, no other write or read locks can be acquired. When a read lock "
+"is held, others can acquire read locks. However, to acquire write locks, one "
+"has to wait until all read locks have been released. When scheduled "
+"concurrently, write locks always have precedence over read locks. Note that "
+"(if enabled) read locks can be upgraded to write locks."
msgstr ""
-#: ./Transactions.xml:27(para)
-msgid "Using read-write locks helps in the following scenario: consider a tree with entries \"/a/b/n1\" and \"/a/b/n2\". With write-locks, when Tx1 accesses \"/a/b/n1\", Tx2 cannot access \"/a/b/n2\" until Tx1 has completed and released its locks. However, with read-write locks this is possible, because Tx1 acquires read-locks for \"/a/b\" and a read-write lock for \"/a/b/n1\". Tx2 is then able to acquire read-locks for \"/a/b\" as well, plus a read-write lock for \"/a/b/n2\". This allows for more concurrency in accessing the cache."
+#. Tag: para
+#: Transactions.xml:22
+#, no-c-format
+msgid ""
+"Using read-write locks helps in the following scenario: consider a tree with "
+"entries \"/a/b/n1\" and \"/a/b/n2\". With write-locks, when Tx1 accesses \"/"
+"a/b/n1\", Tx2 cannot access \"/a/b/n2\" until Tx1 has completed and released "
+"its locks. However, with read-write locks this is possible, because Tx1 "
+"acquires read-locks for \"/a/b\" and a read-write lock for \"/a/b/n1\". Tx2 "
+"is then able to acquire read-locks for \"/a/b\" as well, plus a read-write "
+"lock for \"/a/b/n2\". This allows for more concurrency in accessing the "
+"cache."
msgstr ""
-#: ./Transactions.xml:33(title)
+#. Tag: title
+#: Transactions.xml:28
+#, no-c-format
msgid "Pessimistic locking"
msgstr ""
-#: ./Transactions.xml:34(para)
-msgid "By default, JBoss Cache uses pessimistic locking. Locking is not exposed directly to user. Instead, a transaction isolation level which provides different locking behaviour is configurable."
+#. Tag: para
+#: Transactions.xml:29
+#, no-c-format
+msgid ""
+"By default, JBoss Cache uses pessimistic locking. Locking is not exposed "
+"directly to user. Instead, a transaction isolation level which provides "
+"different locking behaviour is configurable."
msgstr ""
-#: ./Transactions.xml:38(title)
+#. Tag: title
+#: Transactions.xml:33
+#, no-c-format
msgid "Isolation levels"
msgstr ""
-#: ./Transactions.xml:39(para)
-msgid "JBoss Cache supports the following transaction isolation levels, analogous to database ACID isolation levels. A user can configure an instance-wide isolation level of NONE, READ_UNCOMMITTED, READ_COMMITTED, REPEATABLE_READ, or SERIALIZABLE. REPEATABLE_READ is the default isolation level used."
+#. Tag: para
+#: Transactions.xml:34
+#, no-c-format
+msgid ""
+"JBoss Cache supports the following transaction isolation levels, analogous "
+"to database ACID isolation levels. A user can configure an instance-wide "
+"isolation level of NONE, READ_UNCOMMITTED, READ_COMMITTED, REPEATABLE_READ, "
+"or SERIALIZABLE. REPEATABLE_READ is the default isolation level used."
msgstr ""
-#: ./Transactions.xml:44(para)
-msgid "NONE. No transaction support is needed. There is no locking at this level, e.g., users will have to manage the data integrity. Implementations use no locks."
+#. Tag: para
+#: Transactions.xml:39
+#, no-c-format
+msgid ""
+"NONE. No transaction support is needed. There is no locking at this level, e."
+"g., users will have to manage the data integrity. Implementations use no "
+"locks."
msgstr ""
-#: ./Transactions.xml:50(programlisting)
-#, no-wrap
-msgid "\n Tx1 Tx2\n W\n R\n"
+#. Tag: para
+#: Transactions.xml:44
+#, no-c-format
+msgid ""
+"READ_UNCOMMITTED. Data can be read anytime while write operations are "
+"exclusive. Note that this level doesn't prevent the so-called \"dirty read\" "
+"where data modified in Tx1 can be read in Tx2 before Tx1 commits. In other "
+"words, if you have the following sequence, <programlisting>\n"
+" Tx1 Tx2\n"
+" W\n"
+" R\n"
+"</programlisting> using this isolation level will not Tx2 read operation. "
+"Implementations typically use an exclusive lock for writes while reads don't "
+"need to acquire a lock."
msgstr ""
-#: ./Transactions.xml:49(para)
-msgid "READ_UNCOMMITTED. Data can be read anytime while write operations are exclusive. Note that this level doesn't prevent the so-called \"dirty read\" where data modified in Tx1 can be read in Tx2 before Tx1 commits. In other words, if you have the following sequence, <placeholder-1/> using this isolation level will not Tx2 read operation. Implementations typically use an exclusive lock for writes while reads don't need to acquire a lock."
+#. Tag: para
+#: Transactions.xml:50
+#, no-c-format
+msgid ""
+"READ_COMMITTED. Data can be read any time as long as there is no write. This "
+"level prevents the dirty read. But it doesn’t prevent the so-called "
+"‘non-repeatable read’ where one thread reads the data twice can "
+"produce different results. For example, if you have the following sequence,"
msgstr ""
-#: ./Transactions.xml:60(programlisting)
-#, no-wrap
-msgid "\nTx1 Tx2\n R\n W\n R\n"
+#. Tag: programlisting
+#: Transactions.xml:51
+#, no-c-format
+msgid ""
+"Tx1 Tx2\n"
+" R\n"
+" W\n"
+" R"
msgstr ""
-#: ./Transactions.xml:59(para)
-msgid "READ_COMMITTED. Data can be read any time as long as there is no write. This level prevents the dirty read. But it doesn’t prevent the so-called ‘non-repeatable read’ where one thread reads the data twice can produce different results. For example, if you have the following sequence, <placeholder-1/>"
-msgstr ""
-
-#: ./Transactions.xml:67(para)
+#. Tag: para
+#: Transactions.xml:53
+#, no-c-format
msgid "where the second read in Tx1 thread will produce different result."
msgstr ""
-#: ./Transactions.xml:70(para)
-msgid "Implementations usually use a read-write lock; reads succeed acquiring the lock when there are only reads, writes have to wait until there are no more readers holding the lock, and readers are blocked acquiring the lock until there are no more writers holding the lock. Reads typically release the read-lock when done, so that a subsequent read to the same data has to re-acquire a read-lock; this leads to nonrepeatable reads, where 2 reads of the same data might return different values. Note that, the write only applies regardless of transaction state (whether it has been committed or not)."
+#. Tag: para
+#: Transactions.xml:56
+#, no-c-format
+msgid ""
+"Implementations usually use a read-write lock; reads succeed acquiring the "
+"lock when there are only reads, writes have to wait until there are no more "
+"readers holding the lock, and readers are blocked acquiring the lock until "
+"there are no more writers holding the lock. Reads typically release the read-"
+"lock when done, so that a subsequent read to the same data has to re-acquire "
+"a read-lock; this leads to nonrepeatable reads, where 2 reads of the same "
+"data might return different values. Note that, the write only applies "
+"regardless of transaction state (whether it has been committed or not)."
msgstr ""
-#: ./Transactions.xml:75(para)
-msgid "REPEATABLE_READ. Data can be read while there is no write and vice versa. This level prevents \"non-repeatable read\" but it does not prevent the so-called \"phantom read\" where new data can be inserted into the tree from the other transaction. Implementations typically use a read-write lock. This is the default isolation level used."
+#. Tag: para
+#: Transactions.xml:61
+#, no-c-format
+msgid ""
+"REPEATABLE_READ. Data can be read while there is no write and vice versa. "
+"This level prevents \"non-repeatable read\" but it does not prevent the so-"
+"called \"phantom read\" where new data can be inserted into the tree from "
+"the other transaction. Implementations typically use a read-write lock. This "
+"is the default isolation level used."
msgstr ""
-#: ./Transactions.xml:80(para)
-msgid "SERIALIZABLE. Data access is synchronized with exclusive locks. Only 1 writer or reader can have the lock at any given time. Locks are released at the end of the transaction. Regarded as very poor for performance and thread/transaction concurrency."
+#. Tag: para
+#: Transactions.xml:66
+#, no-c-format
+msgid ""
+"SERIALIZABLE. Data access is synchronized with exclusive locks. Only 1 "
+"writer or reader can have the lock at any given time. Locks are released at "
+"the end of the transaction. Regarded as very poor for performance and thread/"
+"transaction concurrency."
msgstr ""
-#: ./Transactions.xml:88(title)
+#. Tag: title
+#: Transactions.xml:74
+#, no-c-format
msgid "Insertion and Removal of Nodes"
msgstr ""
-#: ./Transactions.xml:89(para)
-msgid "By default, before inserting a new node into the tree or removing an existing node from the tree, JBoss Cache will attempt to acquire a write lock on the new node's parent node. This approach treats child nodes as an integral part of a parent node's state. This approach provide greater correctness, but at a cost of lesser concurrency if nodes are frequently added or removed. For use cases where this greater correctness is not meaningful, JBoss Cache provides a configuration option <literal>LockParentForChildInsertRemove</literal>. If this is set to <literal>false</literal>, insertions and removals of child nodes only require the acquisition of a <emphasis>read lock</emphasis> on the parent node."
+#. Tag: para
+#: Transactions.xml:75
+#, no-c-format
+msgid ""
+"By default, before inserting a new node into the tree or removing an "
+"existing node from the tree, JBoss Cache will attempt to acquire a write "
+"lock on the new node's parent node. This approach treats child nodes as an "
+"integral part of a parent node's state. This approach provide greater "
+"correctness, but at a cost of lesser concurrency if nodes are frequently "
+"added or removed. For use cases where this greater correctness is not "
+"meaningful, JBoss Cache provides a configuration option "
+"<literal>LockParentForChildInsertRemove</literal>. If this is set to "
+"<literal>false</literal>, insertions and removals of child nodes only "
+"require the acquisition of a <emphasis>read lock</emphasis> on the parent "
+"node."
msgstr ""
-#: ./Transactions.xml:97(title)
+#. Tag: title
+#: Transactions.xml:83
+#, no-c-format
msgid "Optimistic locking"
msgstr ""
-#: ./Transactions.xml:98(para)
-msgid "The motivation for optimistic locking is to improve concurrency. When a lot of threads have a lot of contention for access to the data tree, it can be inefficient to lock portions of the tree - for reading or writing - for the entire duration of a transaction as we do in pessimistic locking. Optimistic locking allows for greater concurrency of threads and transactions by using a technique called data versioning, explained here. Note that isolation levels (if configured) are ignored if optimistic locking is enabled."
+#. Tag: para
+#: Transactions.xml:84
+#, no-c-format
+msgid ""
+"The motivation for optimistic locking is to improve concurrency. When a lot "
+"of threads have a lot of contention for access to the data tree, it can be "
+"inefficient to lock portions of the tree - for reading or writing - for the "
+"entire duration of a transaction as we do in pessimistic locking. Optimistic "
+"locking allows for greater concurrency of threads and transactions by using "
+"a technique called data versioning, explained here. Note that isolation "
+"levels (if configured) are ignored if optimistic locking is enabled."
msgstr ""
-#: ./Transactions.xml:102(title)
+#. Tag: title
+#: Transactions.xml:88
+#, no-c-format
msgid "Architecture"
msgstr ""
-#: ./Transactions.xml:104(para)
-msgid "Because of this requirement, you must always have a transaction manager configured when using optimistic locking."
+#. Tag: para
+#: Transactions.xml:89
+#, no-c-format
+msgid ""
+"Optimistic locking treats all method calls as transactional<footnote><para> "
+"Because of this requirement, you must always have a transaction manager "
+"configured when using optimistic locking. </para> </footnote>. Even if you "
+"do not invoke a call within the scope of an ongoing transaction, JBoss Cache "
+"creates an implicit transaction and commits this transaction when the "
+"invocation completes. Each transaction maintains a transaction workspace, "
+"which contains a copy of the data used within the transaction."
msgstr ""
-#: ./Transactions.xml:103(para)
-msgid "Optimistic locking treats all method calls as transactional<placeholder-1/>. Even if you do not invoke a call within the scope of an ongoing transaction, JBoss Cache creates an implicit transaction and commits this transaction when the invocation completes. Each transaction maintains a transaction workspace, which contains a copy of the data used within the transaction."
+#. Tag: para
+#: Transactions.xml:95
+#, no-c-format
+msgid ""
+"For example, if a transaction calls get(\"/a/b/c\"), nodes a, b and c are "
+"copied from the main data tree and into the workspace. The data is versioned "
+"and all calls in the transaction work on the copy of the data rather than "
+"the actual data. When the transaction commits, it's workspace is merged back "
+"into the underlying tree by matching versions. If there is a version "
+"mismatch - such as when the actual data tree has a higher version than the "
+"workspace, perhaps if another transaction were to access the same data, "
+"change it and commit before the first transaction can finish - the "
+"transaction throws a <literal>RollbackException</literal> when committing "
+"and the commit fails."
msgstr ""
-#: ./Transactions.xml:109(para)
-msgid "For example, if a transaction calls get(\"/a/b/c\"), nodes a, b and c are copied from the main data tree and into the workspace. The data is versioned and all calls in the transaction work on the copy of the data rather than the actual data. When the transaction commits, it's workspace is merged back into the underlying tree by matching versions. If there is a version mismatch - such as when the actual data tree has a higher version than the workspace, perhaps if another transaction were to access the same data, change it and commit before the first transaction can finish - the transaction throws a <literal>RollbackException</literal> when committing and the commit fails."
+#. Tag: para
+#: Transactions.xml:98
+#, no-c-format
+msgid ""
+"Optimistic locking uses the same locks we speak of above, but the locks are "
+"only held for a very short duration - at the start of a transaction to build "
+"a workspace, and when the transaction commits and has to merge data back "
+"into the tree."
msgstr ""
-#: ./Transactions.xml:112(para)
-msgid "Optimistic locking uses the same locks we speak of above, but the locks are only held for a very short duration - at the start of a transaction to build a workspace, and when the transaction commits and has to merge data back into the tree."
+#. Tag: para
+#: Transactions.xml:101
+#, no-c-format
+msgid ""
+"So while optimistic locking may occasionally fail if version validations "
+"fail or may run slightly slower than pessimistic locking due to the "
+"inevitable overhead and extra processing of maintaining workspaces, "
+"versioned data and validating on commit, it does buy you a near-SERIALIZABLE "
+"degree of data integrity while maintaining a very high level of concurrency."
msgstr ""
-#: ./Transactions.xml:115(para)
-msgid "So while optimistic locking may occasionally fail if version validations fail or may run slightly slower than pessimistic locking due to the inevitable overhead and extra processing of maintaining workspaces, versioned data and validating on commit, it does buy you a near-SERIALIZABLE degree of data integrity while maintaining a very high level of concurrency."
-msgstr ""
-
-#: ./Transactions.xml:121(title)
+#. Tag: title
+#: Transactions.xml:107
+#, no-c-format
msgid "Configuration"
msgstr ""
-#: ./Transactions.xml:122(programlisting)
-#, no-wrap
-msgid "\n...\n<!--\nNode locking scheme:\n OPTIMISTIC\n PESSIMISTIC (default)\n-->\n<attribute name=\"NodeLockingScheme\">OPTIMISTIC</attribute>\n...\n"
+#. Tag: para
+#: Transactions.xml:108
+#, no-c-format
+msgid ""
+"Optimistic locking is enabled by using the NodeLockingScheme XML attribute, "
+"and setting it to \"OPTIMISTIC\":"
msgstr ""
-#: ./Transactions.xml:122(para)
-msgid "Optimistic locking is enabled by using the NodeLockingScheme XML attribute, and setting it to \"OPTIMISTIC\": <placeholder-1/>"
+#. Tag: programlisting
+#: Transactions.xml:108
+#, no-c-format
+msgid ""
+"...\n"
+"<!--\n"
+"Node locking scheme:\n"
+" OPTIMISTIC\n"
+" PESSIMISTIC (default)\n"
+"-->\n"
+"<attribute name=\"NodeLockingScheme\">OPTIMISTIC</attribute>\n"
+"..."
msgstr ""
-#: ./Transactions.xml:139(title)
+#. Tag: title
+#: Transactions.xml:116
+#, no-c-format
msgid "Transactional Support"
msgstr ""
-#: ./Transactions.xml:141(para)
-msgid "Depending on whether interval-based asynchronous replication is used"
+#. Tag: para
+#: Transactions.xml:117
+#, no-c-format
+msgid ""
+"JBoss Cache can be configured to use transactions to bundle units of work, "
+"which can then be replicated as one unit. Alternatively, if transaction "
+"support is disabled, it is equivalent to setting AutoCommit to on where "
+"modifications are potentially<footnote><para> Depending on whether interval-"
+"based asynchronous replication is used </para> </footnote> replicated after "
+"every change (if replication is enabled)."
msgstr ""
-#: ./Transactions.xml:140(para)
-msgid "JBoss Cache can be configured to use transactions to bundle units of work, which can then be replicated as one unit. Alternatively, if transaction support is disabled, it is equivalent to setting AutoCommit to on where modifications are potentially<placeholder-1/> replicated after every change (if replication is enabled)."
-msgstr ""
-
-#: ./Transactions.xml:146(para)
+#. Tag: para
+#: Transactions.xml:123
+#, no-c-format
msgid "What JBoss Cache does on every incoming call (e.g. put()) is:"
msgstr ""
-#: ./Transactions.xml:151(para)
+#. Tag: para
+#: Transactions.xml:128
+#, no-c-format
msgid "get the transaction associated with the thread"
msgstr ""
-#: ./Transactions.xml:156(para)
-msgid "register (if not already done) with the transaction manager to be notified when a transaction commits or is rolled back."
+#. Tag: para
+#: Transactions.xml:133
+#, no-c-format
+msgid ""
+"register (if not already done) with the transaction manager to be notified "
+"when a transaction commits or is rolled back."
msgstr ""
-#: ./Transactions.xml:161(para)
-msgid "In order to do this, the cache has to be configured with an instance of a <literal>TransactionManagerLookup</literal> which returns a <literal>javax.transaction.TransactionManager</literal>."
+#. Tag: para
+#: Transactions.xml:138
+#, no-c-format
+msgid ""
+"In order to do this, the cache has to be configured with an instance of a "
+"<literal>TransactionManagerLookup</literal> which returns a <literal>javax."
+"transaction.TransactionManager</literal>."
msgstr ""
-#: ./Transactions.xml:164(para)
-msgid "JBoss Cache ships with <literal>JBossTransactionManagerLookup</literal> and <literal>GenericTransactionManagerLookup</literal>. The <literal>JBossTransactionManagerLookup</literal> is able to bind to a running JBoss Application Server and retrieve a <literal>TransactionManager</literal> while the <literal>GenericTransactionManagerLookup</literal> is able to bind to most popular Java EE application servers and provide the same functionality. A dummy implementation - <literal>DummyTransactionManagerLookup</literal> - is also provided, which may be used for standalone JBoss Cache applications and unit tests running outside a Java EE Application Server. Being a dummy, however, this is just for demo and testing purposes and is not recommended for production use."
+#. Tag: para
+#: Transactions.xml:141
+#, no-c-format
+msgid ""
+"JBoss Cache ships with <literal>JBossTransactionManagerLookup</literal> and "
+"<literal>GenericTransactionManagerLookup</literal>. The "
+"<literal>JBossTransactionManagerLookup</literal> is able to bind to a "
+"running JBoss Application Server and retrieve a <literal>TransactionManager</"
+"literal> while the <literal>GenericTransactionManagerLookup</literal> is "
+"able to bind to most popular Java EE application servers and provide the "
+"same functionality. A dummy implementation - "
+"<literal>DummyTransactionManagerLookup</literal> - is also provided, which "
+"may be used for standalone JBoss Cache applications and unit tests running "
+"outside a Java EE Application Server. Being a dummy, however, this is just "
+"for demo and testing purposes and is not recommended for production use."
msgstr ""
-#: ./Transactions.xml:167(para)
-msgid "The implementation of the <literal>JBossTransactionManagerLookup</literal> is as follows:"
+#. Tag: para
+#: Transactions.xml:144
+#, no-c-format
+msgid ""
+"The implementation of the <literal>JBossTransactionManagerLookup</literal> "
+"is as follows:"
msgstr ""
-#: ./Transactions.xml:170(programlisting)
-#, no-wrap
-msgid "public class JBossTransactionManagerLookup implements TransactionManagerLookup {\n\n public JBossTransactionManagerLookup() {}\n\n public TransactionManager getTransactionManager() throws Exception {\n Object tmp=new InitialContext().lookup(\"java:/TransactionManager\");\n return (TransactionManager)tmp;\n }\n}\n"
+#. Tag: programlisting
+#: Transactions.xml:147
+#, no-c-format
+msgid ""
+"public class JBossTransactionManagerLookup implements "
+"TransactionManagerLookup {\n"
+"\n"
+" public JBossTransactionManagerLookup() {}\n"
+"\n"
+" public TransactionManager getTransactionManager() throws Exception {\n"
+" Object tmp=new InitialContext().lookup(\"java:/TransactionManager"
+"\");\n"
+" return (TransactionManager)tmp;\n"
+" }\n"
+"}"
msgstr ""
-#: ./Transactions.xml:180(para)
-msgid "The implementation looks up the JBoss Transaction Manager from JNDI and returns it."
+#. Tag: para
+#: Transactions.xml:148
+#, no-c-format
+msgid ""
+"The implementation looks up the JBoss Transaction Manager from JNDI and "
+"returns it."
msgstr ""
-#: ./Transactions.xml:183(para)
-msgid "When a call comes in, the <literal>TreeCache</literal> gets the current transaction and records the modification under the transaction as key. (If there is no transaction, the modification is applied immediately and possibly replicated). So over the lifetime of the transaction all modifications will be recorded and associated with the transaction. Also, the <literal>TreeCache</literal> registers with the transaction to be notified of transaction committed or aborted when it first encounters the transaction."
+#. Tag: para
+#: Transactions.xml:151
+#, no-c-format
+msgid ""
+"When a call comes in, the <literal>TreeCache</literal> gets the current "
+"transaction and records the modification under the transaction as key. (If "
+"there is no transaction, the modification is applied immediately and "
+"possibly replicated). So over the lifetime of the transaction all "
+"modifications will be recorded and associated with the transaction. Also, "
+"the <literal>TreeCache</literal> registers with the transaction to be "
+"notified of transaction committed or aborted when it first encounters the "
+"transaction."
msgstr ""
-#: ./Transactions.xml:186(para)
-msgid "When a transaction rolls back, we undo the changes in the cache and release all locks."
+#. Tag: para
+#: Transactions.xml:154
+#, no-c-format
+msgid ""
+"When a transaction rolls back, we undo the changes in the cache and release "
+"all locks."
msgstr ""
-#: ./Transactions.xml:190(para)
-msgid "Only with synchronous replication or invalidation."
+#. Tag: para
+#: Transactions.xml:157
+#, no-c-format
+msgid ""
+"When the transaction commits, we initiate a two-phase commit "
+"protocol<footnote><para> Only with synchronous replication or invalidation. "
+"</para> </footnote> : in the first phase, a PREPARE containing all "
+"modifications for the current transaction is sent to all nodes in the "
+"cluster. Each node acquires all necessary locks and applies the changes, and "
+"then sends back a success message. If a node in a cluster cannot acquire all "
+"locks, or fails otherwise, it sends back a failure message."
msgstr ""
-#: ./Transactions.xml:189(para)
-msgid "When the transaction commits, we initiate a two-phase commit protocol<placeholder-1/> : in the first phase, a PREPARE containing all modifications for the current transaction is sent to all nodes in the cluster. Each node acquires all necessary locks and applies the changes, and then sends back a success message. If a node in a cluster cannot acquire all locks, or fails otherwise, it sends back a failure message."
+#. Tag: para
+#: Transactions.xml:163
+#, no-c-format
+msgid ""
+"The coordinator of the two-phase commit protocol waits for all responses (or "
+"a timeout, whichever occurs first). If one of the nodes in the cluster "
+"responds with FAIL (or we hit the timeout), then a rollback phase is "
+"initiated: a ROLLBACK message is sent to all nodes in the cluster. On "
+"reception of the ROLLBACK message, every node undoes the changes for the "
+"given transaction, and releases all locks held for the transaction."
msgstr ""
-#: ./Transactions.xml:195(para)
-msgid "The coordinator of the two-phase commit protocol waits for all responses (or a timeout, whichever occurs first). If one of the nodes in the cluster responds with FAIL (or we hit the timeout), then a rollback phase is initiated: a ROLLBACK message is sent to all nodes in the cluster. On reception of the ROLLBACK message, every node undoes the changes for the given transaction, and releases all locks held for the transaction."
+#. Tag: para
+#: Transactions.xml:166
+#, no-c-format
+msgid ""
+"If all responses are OK, a COMMIT message is sent to all nodes in the "
+"cluster. On reception of a COMMIT message, each node applies the changes for "
+"the given transaction and releases all locks associated with the transaction."
msgstr ""
-#: ./Transactions.xml:198(para)
-msgid "If all responses are OK, a COMMIT message is sent to all nodes in the cluster. On reception of a COMMIT message, each node applies the changes for the given transaction and releases all locks associated with the transaction."
+#. Tag: para
+#: Transactions.xml:169
+#, no-c-format
+msgid ""
+"When we referred to 'transaction', we actually mean a global representation "
+"of a local transaction, which uniquely identifies a transaction across a "
+"cluster."
msgstr ""
-#: ./Transactions.xml:201(para)
-msgid "When we referred to 'transaction', we actually mean a global representation of a local transaction, which uniquely identifies a transaction across a cluster."
-msgstr ""
-
-#: ./Transactions.xml:205(title)
+#. Tag: title
+#: Transactions.xml:173
+#, no-c-format
msgid "Example"
msgstr ""
-#: ./Transactions.xml:206(para)
-msgid "Let's look at an example of how to use JBoss Cache in a standalone (i.e. outside an application server) fashion with dummy transactions:"
+#. Tag: para
+#: Transactions.xml:174
+#, no-c-format
+msgid ""
+"Let's look at an example of how to use JBoss Cache in a standalone (i.e. "
+"outside an application server) fashion with dummy transactions:"
msgstr ""
-#: ./Transactions.xml:209(programlisting)
-#, no-wrap
-msgid "Properties prop = new Properties();\nprop.put(Context.INITIAL_CONTEXT_FACTORY, \"org.jboss.cache.transaction.DummyContextFactory\");\nUser Transaction tx=(UserTransaction)new InitialContext(prop).lookup(\"UserTransaction\");\nTreeCache tree = new TreeCache();\nPropertyConfigurator config = new PropertyConfigurator();\nconfig.configure(tree, \"META-INF/replSync-service.xml\");\ntree.createService(); // not necessary\ntree.startService(); // kick start tree cache\n\ntry {\n tx.begin();\n tree.put(\"/classes/cs-101\", \"description\", \"the basics\");\n tree.put(\"/classes/cs-101\", \"teacher\", \"Ben\");\n tx.commit();\n}\ncatch(Throwable ex) {\n try { tx.rollback(); } catch(Throwable t) {}\n}\n"
+#. Tag: programlisting
+#: Transactions.xml:177
+#, no-c-format
+msgid ""
+"Properties prop = new Properties();\n"
+"prop.put(Context.INITIAL_CONTEXT_FACTORY, \"org.jboss.cache.transaction."
+"DummyContextFactory\");\n"
+"User Transaction tx=(UserTransaction)new InitialContext(prop).lookup"
+"(\"UserTransaction\");\n"
+"TreeCache tree = new TreeCache();\n"
+"PropertyConfigurator config = new PropertyConfigurator();\n"
+"config.configure(tree, \"META-INF/replSync-service.xml\");\n"
+"tree.createService(); // not necessary\n"
+"tree.startService(); // kick start tree cache\n"
+"\n"
+"try {\n"
+" tx.begin();\n"
+" tree.put(\"/classes/cs-101\", \"description\", \"the basics\");\n"
+" tree.put(\"/classes/cs-101\", \"teacher\", \"Ben\");\n"
+" tx.commit();\n"
+"}\n"
+"catch(Throwable ex) {\n"
+" try { tx.rollback(); } catch(Throwable t) {}\n"
+"}"
msgstr ""
-#: ./Transactions.xml:228(para)
-msgid "The first lines obtain a user transaction using the 'JEE way' via JNDI. Note that we could also say"
+#. Tag: para
+#: Transactions.xml:178
+#, no-c-format
+msgid ""
+"The first lines obtain a user transaction using the 'JEE way' via JNDI. Note "
+"that we could also say"
msgstr ""
-#: ./Transactions.xml:232(programlisting)
-#, no-wrap
-msgid "UserTransaction tx = new DummyUserTransaction(DummyTransactionManager.getInstance());"
+#. Tag: programlisting
+#: Transactions.xml:182
+#, no-c-format
+msgid ""
+"UserTransaction tx = new DummyUserTransaction(DummyTransactionManager."
+"getInstance());"
msgstr ""
-#: ./Transactions.xml:234(para)
-msgid "Then we create a new TreeCache and configure it using a PropertyConfigurator class and a configuration XML file (see below for a list of all configuration options)."
+#. Tag: para
+#: Transactions.xml:184
+#, no-c-format
+msgid ""
+"Then we create a new TreeCache and configure it using a PropertyConfigurator "
+"class and a configuration XML file (see below for a list of all "
+"configuration options)."
msgstr ""
-#: ./Transactions.xml:237(para)
-msgid "Next we start the cache. Then, we start a transaction (and associate it with the current thread internally). Any methods invoked on the cache will now be collected and only applied when the transaction is committed. In the above case, we create a node \"/classes/cs-101\" and add 2 elements to its map. Assuming that the cache is configured to use synchronous replication, on transaction commit the modifications are replicated. If there is an exception in the methods (e.g. lock acquisition failed), or in the two-phase commit protocol applying the modifications to all nodes in the cluster, the transaction is rolled back."
+#. Tag: para
+#: Transactions.xml:187
+#, no-c-format
+msgid ""
+"Next we start the cache. Then, we start a transaction (and associate it with "
+"the current thread internally). Any methods invoked on the cache will now be "
+"collected and only applied when the transaction is committed. In the above "
+"case, we create a node \"/classes/cs-101\" and add 2 elements to its map. "
+"Assuming that the cache is configured to use synchronous replication, on "
+"transaction commit the modifications are replicated. If there is an "
+"exception in the methods (e.g. lock acquisition failed), or in the two-phase "
+"commit protocol applying the modifications to all nodes in the cluster, the "
+"transaction is rolled back."
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Transactions.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
Modified: enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Treecache_marshaller.pot
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Treecache_marshaller.pot 2009-01-07 19:00:28 UTC (rev 7394)
+++ enterprise-docs/tags/JBoss_EAP_4_2_6/Cache_Tree_Cache_Guide/pot/Treecache_marshaller.pot 2009-01-08 05:17:29 UTC (rev 7395)
@@ -1,228 +1,708 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-04-17 00:25-0500\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-01-08 05:16+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ./Treecache_marshaller.xml:10(title)
+#. Tag: title
+#: Treecache_marshaller.xml:5
+#, no-c-format
msgid "TreeCacheMarshaller"
msgstr ""
-#: ./Treecache_marshaller.xml:11(para)
-msgid "Rather than using standard Java serialization to serialize <literal>java.lang.reflect.Method</literal> objects and their parameters when remote caches talk to each other to replicate data, JBoss Cache uses its own mechanism to marshall and unmarshall data called the <literal>TreeCacheMarshaller</literal>."
+#. Tag: para
+#: Treecache_marshaller.xml:6
+#, no-c-format
+msgid ""
+"Rather than using standard Java serialization to serialize <literal>java."
+"lang.reflect.Method</literal> objects and their parameters when remote "
+"caches talk to each other to replicate data, JBoss Cache uses its own "
+"mechanism to marshall and unmarshall data called the "
+"<literal>TreeCacheMarshaller</literal>."
msgstr ""
-#: ./Treecache_marshaller.xml:14(para)
-msgid "In addition to providing the performance and efficiency enhancements over standard Java serialization, The <literal>TreeCacheMarshaller</literal> also performs one other function. In order to deserialize an object replicated to it from a remote cache, a cache instance needs to have access to the classloader that defines the object's class. This is simple if the cache's own classloader can access the required classes, but for situations where JBoss Cache is used as a service supporting clients that use different classloaders, the <literal>TreeCacheMarshaller</literal> can be configured to use different classloaders on a per-region basis by allowing application code to register a classloader that should be used to handle replication for a portion of the tree."
+#. Tag: para
+#: Treecache_marshaller.xml:9
+#, no-c-format
+msgid ""
+"In addition to providing the performance and efficiency enhancements over "
+"standard Java serialization, The <literal>TreeCacheMarshaller</literal> also "
+"performs one other function. In order to deserialize an object replicated to "
+"it from a remote cache, a cache instance needs to have access to the "
+"classloader that defines the object's class. This is simple if the cache's "
+"own classloader can access the required classes, but for situations where "
+"JBoss Cache is used as a service supporting clients that use different "
+"classloaders, the <literal>TreeCacheMarshaller</literal> can be configured "
+"to use different classloaders on a per-region basis by allowing application "
+"code to register a classloader that should be used to handle replication for "
+"a portion of the tree."
msgstr ""
-#: ./Treecache_marshaller.xml:18(title)
+#. Tag: title
+#: Treecache_marshaller.xml:13
+#, no-c-format
msgid "Basic Usage"
msgstr ""
-#: ./Treecache_marshaller.xml:19(para)
-msgid "<literal>TreeCache</literal> exposes the following basic API for controlling the behavior of <literal>TreeCacheMarshaller</literal>:"
+#. Tag: para
+#: Treecache_marshaller.xml:14
+#, no-c-format
+msgid ""
+"<literal>TreeCache</literal> exposes the following basic API for controlling "
+"the behavior of <literal>TreeCacheMarshaller</literal>:"
msgstr ""
-#: ./Treecache_marshaller.xml:22(programlisting)
-#, no-wrap
-msgid "\n/**\n * Sets whether marshalling uses scoped class loaders on a per region basis.\n *\n * This property must be set to true before any call to\n * {@link #registerClassLoader(String, ClassLoader)} or\n * {@link #activateRegion(String)}\n *\n * @param isTrue\n */\nvoid setUseRegionBasedMarshalling(boolean isTrue);\n\n/**\n * Gets whether marshalling uses scoped class loaders on a per region basis.\n */\nboolean getUseRegionBasedMarshalling();\n\n/**\n * Registers the given classloader with <code>TreeCacheMarshaller</code> for\n * use in unmarshalling replicated objects for the specified region.\n *\n * @param fqn The fqn region. This fqn and its children will use this classloader for \n * (un)marshalling.\n * @param cl The class loader to use\n *\n * @throws RegionNameConflictException if <code>fqn</code> is a descendant of\n * an FQN that already has a classloader registered.\n * @throws IllegalStateException if <code>useMarshalling</code> is <code>false</code>\n *!
/\nvoid registerClassLoader(String fqn, ClassLoader cl) throws RegionNameConflictException;\n\n/**\n * Instructs the <code>TreeCacheMarshaller</code> to no longer use a special\n * classloader to unmarshal replicated objects for the specified region.\n *\n * @param fqn The fqn of the root node of region.\n *\n * @throws RegionNotFoundException if no classloader has been registered for\n * <code>fqn</code>.\n * @throws IllegalStateException if <code>useMarshalling</code> is <code>false</code>\n */\nvoid unregisterClassLoader(String fqn) throws RegionNotFoundException;\n \n"
+#. Tag: programlisting
+#: Treecache_marshaller.xml:17
+#, no-c-format
+msgid ""
+"/**\n"
+" * Sets whether marshalling uses scoped class loaders on a per region "
+"basis.\n"
+" *\n"
+" * This property must be set to true before any call to\n"
+" * {@link #registerClassLoader(String, ClassLoader)} or\n"
+" * {@link #activateRegion(String)}\n"
+" *\n"
+" * @param isTrue\n"
+" */\n"
+"void setUseRegionBasedMarshalling(boolean isTrue);\n"
+"\n"
+"/**\n"
+" * Gets whether marshalling uses scoped class loaders on a per region "
+"basis.\n"
+" */\n"
+"boolean getUseRegionBasedMarshalling();\n"
+"\n"
+"/**\n"
+" * Registers the given classloader with <code>TreeCacheMarshaller</code> "
+"for\n"
+" * use in unmarshalling replicated objects for the specified region.\n"
+" *\n"
+" * @param fqn The fqn region. This fqn and its children will use this "
+"classloader for \n"
+" * (un)marshalling.\n"
+" * @param cl The class loader to use\n"
+" *\n"
+" * @throws RegionNameConflictException if <code>fqn</code> is a descendant "
+"of\n"
+" * an FQN that already has a classloader registered.\n"
+" * @throws IllegalStateException if <code>useMarshalling</code> is "
+"<code>false</code>\n"
+" */\n"
+"void registerClassLoader(String fqn, ClassLoader cl) throws "
+"RegionNameConflictException;\n"
+"\n"
+"/**\n"
+" * Instructs the <code>TreeCacheMarshaller</code> to no longer use a "
+"special\n"
+" * classloader to unmarshal replicated objects for the specified region.\n"
+" *\n"
+" * @param fqn The fqn of the root node of region.\n"
+" *\n"
+" * @throws RegionNotFoundException if no classloader has been registered "
+"for\n"
+" * <code>fqn</code>.\n"
+" * @throws IllegalStateException if <code>useMarshalling</code> is "
+"<code>false</code>\n"
+" */\n"
+"void unregisterClassLoader(String fqn) throws RegionNotFoundException;"
msgstr ""
-#: ./Treecache_marshaller.xml:66(para)
-msgid "Property <literal>UseRegionBasedMarshalling</literal> controls whether classloader-based marshalling should be used. This property should be set as part of normal cache configuration, typically in the cache's XML configuration file:"
+#. Tag: para
+#: Treecache_marshaller.xml:18
+#, no-c-format
+msgid ""
+"Property <literal>UseRegionBasedMarshalling</literal> controls whether "
+"classloader-based marshalling should be used. This property should be set as "
+"part of normal cache configuration, typically in the cache's XML "
+"configuration file:"
msgstr ""
-#: ./Treecache_marshaller.xml:69(programlisting)
-#, no-wrap
-msgid "<attribute name=\"UseRegionBasedMarshalling\">true</attribute>"
+#. Tag: programlisting
+#: Treecache_marshaller.xml:21
+#, no-c-format
+msgid ""
+"<attribute name=\"UseRegionBasedMarshalling\">true</attribute>"
msgstr ""
-#: ./Treecache_marshaller.xml:70(para)
-msgid "Anytime after <literal>UseRegionBasedMarshalling</literal> is set to <literal>true</literal>, the application code can call <literal>registerClassLoader</literal> to associate a classloader with the portion of the cache rooted in a particular FQN. Once registered, the classloader will be used to unmarshal any replication traffic related to the node identified by the FQN or to any of its descendants."
+#. Tag: para
+#: Treecache_marshaller.xml:22
+#, no-c-format
+msgid ""
+"Anytime after <literal>UseRegionBasedMarshalling</literal> is set to "
+"<literal>true</literal>, the application code can call "
+"<literal>registerClassLoader</literal> to associate a classloader with the "
+"portion of the cache rooted in a particular FQN. Once registered, the "
+"classloader will be used to unmarshal any replication traffic related to the "
+"node identified by the FQN or to any of its descendants."
msgstr ""
-#: ./Treecache_marshaller.xml:73(para)
-msgid "At this time, <literal>registerClassLoader</literal> only supports String-based FQNs."
+#. Tag: para
+#: Treecache_marshaller.xml:25
+#, no-c-format
+msgid ""
+"At this time, <literal>registerClassLoader</literal> only supports String-"
+"based FQNs."
msgstr ""
-#: ./Treecache_marshaller.xml:76(para)
-msgid "Note that it is illegal to register a classloader for an FQN that is a descendant of an FQN for which a classloader has already been registered. For example, if classloader <literal>X</literal> is registered for FQN <literal>/a</literal>, a <literal>RegionNameConflictException</literal> will be thrown if an attempt is made to register classloader <literal>Y</literal> for FQN <literal>/a/b</literal>."
+#. Tag: para
+#: Treecache_marshaller.xml:28
+#, no-c-format
+msgid ""
+"Note that it is illegal to register a classloader for an FQN that is a "
+"descendant of an FQN for which a classloader has already been registered. "
+"For example, if classloader <literal>X</literal> is registered for FQN "
+"<literal>/a</literal>, a <literal>RegionNameConflictException</literal> will "
+"be thrown if an attempt is made to register classloader <literal>Y</literal> "
+"for FQN <literal>/a/b</literal>."
msgstr ""
-#: ./Treecache_marshaller.xml:79(para)
-msgid "Method <literal>unregisterClassLoader</literal> is used to remove the association between a classloader and a particular cache region. Be sure to call this method when you are done using the cache with a particular classloader, or a reference to the classloader will be held, causing a memory leak!"
+#. Tag: para
+#: Treecache_marshaller.xml:31
+#, no-c-format
+msgid ""
+"Method <literal>unregisterClassLoader</literal> is used to remove the "
+"association between a classloader and a particular cache region. Be sure to "
+"call this method when you are done using the cache with a particular "
+"classloader, or a reference to the classloader will be held, causing a "
+"memory leak!"
msgstr ""
-#: ./Treecache_marshaller.xml:85(title)
+#. Tag: title
+#: Treecache_marshaller.xml:37
+#, no-c-format
msgid "Region Activation/Inactivation"
msgstr ""
-#: ./Treecache_marshaller.xml:86(para)
-msgid "The basic API discussed above is helpful, but in situations where applications with different classloaders are sharing a cache, the lifecycle of those applications will typically be different from that of the cache. The result of this is that it is difficult or impossible to register all required classloaders before a cache is started. For example, consider the following scenario:"
+#. Tag: para
+#: Treecache_marshaller.xml:38
+#, no-c-format
+msgid ""
+"The basic API discussed above is helpful, but in situations where "
+"applications with different classloaders are sharing a cache, the lifecycle "
+"of those applications will typically be different from that of the cache. "
+"The result of this is that it is difficult or impossible to register all "
+"required classloaders before a cache is started. For example, consider the "
+"following scenario:"
msgstr ""
-#: ./Treecache_marshaller.xml:91(para)
+#. Tag: para
+#: Treecache_marshaller.xml:43
+#, no-c-format
msgid "TreeCache on machine A starts."
msgstr ""
-#: ./Treecache_marshaller.xml:94(para)
+#. Tag: para
+#: Treecache_marshaller.xml:46
+#, no-c-format
msgid "On A a classloader is registered under FQN /x."
msgstr ""
-#: ./Treecache_marshaller.xml:97(para)
+#. Tag: para
+#: Treecache_marshaller.xml:49
+#, no-c-format
msgid "Machine B starts, so TreeCache on B starts."
msgstr ""
-#: ./Treecache_marshaller.xml:100(para)
+#. Tag: para
+#: Treecache_marshaller.xml:52
+#, no-c-format
msgid "An object is put in the machine A cache under FQN /x/1."
msgstr ""
-#: ./Treecache_marshaller.xml:103(para)
-msgid "Replication to B fails, as the required classloader is not yet registered."
+#. Tag: para
+#: Treecache_marshaller.xml:55
+#, no-c-format
+msgid ""
+"Replication to B fails, as the required classloader is not yet registered."
msgstr ""
-#: ./Treecache_marshaller.xml:106(para)
-msgid "On B a classloader is registered under FQN /x, but too late to prevent the replication error."
+#. Tag: para
+#: Treecache_marshaller.xml:58
+#, no-c-format
+msgid ""
+"On B a classloader is registered under FQN /x, but too late to prevent the "
+"replication error."
msgstr ""
-#: ./Treecache_marshaller.xml:109(para)
-msgid "Furthermore, if any objects had been added to server A before server B was started, the initial transfer of state from A to B would have failed as well, as B would not be able to unmarshal the transferred objects."
+#. Tag: para
+#: Treecache_marshaller.xml:61
+#, no-c-format
+msgid ""
+"Furthermore, if any objects had been added to server A before server B was "
+"started, the initial transfer of state from A to B would have failed as "
+"well, as B would not be able to unmarshal the transferred objects."
msgstr ""
-#: ./Treecache_marshaller.xml:112(para)
-msgid "To resolve this problem, if region-based marshalling is used a cache instance can be configured to ignore replication events for a portion of the tree. That portion of the tree is considered \"inactive\". After the needed classloader has been registered, the portion of the tree can be \"activated\". Activation causes the following events to occur:"
+#. Tag: para
+#: Treecache_marshaller.xml:64
+#, no-c-format
+msgid ""
+"To resolve this problem, if region-based marshalling is used a cache "
+"instance can be configured to ignore replication events for a portion of the "
+"tree. That portion of the tree is considered \"inactive\". After the needed "
+"classloader has been registered, the portion of the tree can be \"activated"
+"\". Activation causes the following events to occur:"
msgstr ""
-#: ./Treecache_marshaller.xml:117(para)
-msgid "Any existing state for that portion of the tree is transferred from another node in the cluster and integrated into the local tree."
+#. Tag: para
+#: Treecache_marshaller.xml:69
+#, no-c-format
+msgid ""
+"Any existing state for that portion of the tree is transferred from another "
+"node in the cluster and integrated into the local tree."
msgstr ""
-#: ./Treecache_marshaller.xml:120(para)
-msgid "TreeCacheMarshaller begins normal handling of replication traffic related to the portion of the tree."
+#. Tag: para
+#: Treecache_marshaller.xml:72
+#, no-c-format
+msgid ""
+"TreeCacheMarshaller begins normal handling of replication traffic related to "
+"the portion of the tree."
msgstr ""
-#: ./Treecache_marshaller.xml:123(para)
-msgid "In addition to the basic marshalling related API discussed above, TreeCache exposes the following API related to activating and inactivating portions of the cache:"
+#. Tag: para
+#: Treecache_marshaller.xml:75
+#, no-c-format
+msgid ""
+"In addition to the basic marshalling related API discussed above, TreeCache "
+"exposes the following API related to activating and inactivating portions of "
+"the cache:"
msgstr ""
-#: ./Treecache_marshaller.xml:126(programlisting)
-#, no-wrap
-msgid "\n/**\n * Sets whether the entire tree is inactive upon startup, only responding\n * to replication messages after {@link #activateRegion(String)} is\n * called to activate one or more parts of the tree.\n * <p>\n * This property is only relevant if {@link #getUseRegionBasedMarshalling()} is\n * <code>true</code>.\n *\n */\npublic void setInactiveOnStartup(boolean inactiveOnStartup);\n\n/**\n * Gets whether the entire tree is inactive upon startup, only responding\n * to replication messages after {@link #activateRegion(String)} is\n * called to activate one or more parts of the tree.\n * <p>\n * This property is only relevant if {@link #getUseRegionBasedMarshalling()} is\n * <code>true</code>.\n */\npublic boolean isInactiveOnStartup();\n\n/**\n * Causes the cache to transfer state for the subtree rooted at\n * <code>subtreeFqn</code> and to begin accepting replication messages\n * for that subtree.\n * \n * NOTE: This method will cause the creation of a!
node\n * in the local tree at <code>subtreeFqn</code> whether or not that\n * node exists anywhere else in the cluster. If the node does not exist\n * elsewhere, the local node will be empty. The creation of this node will\n * not be replicated.\n *\n * @param subtreeFqn Fqn string indicating the uppermost node in the\n * portion of the tree that should be activated.\n *\n * @throws RegionNotEmptyException if the node <code>subtreeFqn</code>\n * exists and has either data or children\n *\n * @throws IllegalStateException if useRegionBasedMarshalling is <code>false</code>\n */\npublic void activateRegion(String subtreeFqn)\n throws RegionNotEmptyException, RegionNameConflictException, CacheException;\n\n/**\n * Causes the cache to stop accepting replication events for the subtree\n * rooted at <code>subtreeFqn</code> and evict all nodes in that subtree.\n *\n * @param subtreeFqn Fqn string indicating the uppermost node in the\n * portion of the tree that should be acti!
vated.\n * @throws RegionNameConflictException if <code>subtreeFqn</co
de> indicates\n * a node that is part of another subtree that is being specially\n * managed (either by activate/inactiveRegion()\n * or by registerClassLoader())\n * @throws CacheException if there is a problem evicting nodes\n *\n * @throws IllegalStateException if useRegionBasedMarshalling is <code>false</code>\n */\npublic void inactivateRegion(String subtreeFqn) throws RegionNameConflictException,\nCacheException;\n \n"
+#. Tag: programlisting
+#: Treecache_marshaller.xml:78
+#, no-c-format
+msgid ""
+"/**\n"
+" * Sets whether the entire tree is inactive upon startup, only responding\n"
+" * to replication messages after {@link #activateRegion(String)} is\n"
+" * called to activate one or more parts of the tree.\n"
+" * <p>\n"
+" * This property is only relevant if {@link #getUseRegionBasedMarshalling()} "
+"is\n"
+" * <code>true</code>.\n"
+" *\n"
+" */\n"
+"public void setInactiveOnStartup(boolean inactiveOnStartup);\n"
+"\n"
+"/**\n"
+" * Gets whether the entire tree is inactive upon startup, only responding\n"
+" * to replication messages after {@link #activateRegion(String)} is\n"
+" * called to activate one or more parts of the tree.\n"
+" * <p>\n"
+" * This property is only relevant if {@link #getUseRegionBasedMarshalling()} "
+"is\n"
+" * <code>true</code>.\n"
+" */\n"
+"public boolean isInactiveOnStartup();\n"
+"\n"
+"/**\n"
+" * Causes the cache to transfer state for the subtree rooted at\n"
+" * <code>subtreeFqn</code> and to begin accepting replication messages\n"
+" * for that subtree.\n"
+" * \n"
+" * NOTE: This method will cause the creation of a node\n"
+" * in the local tree at <code>subtreeFqn</code> whether or not that\n"
+" * node exists anywhere else in the cluster. If the node does not exist\n"
+" * elsewhere, the local node will be empty. The creation of this node will\n"
+" * not be replicated.\n"
+" *\n"
+" * @param subtreeFqn Fqn string indicating the uppermost node in the\n"
+" * portion of the tree that should be activated.\n"
+" *\n"
+" * @throws RegionNotEmptyException if the node <code>subtreeFqn</code>\n"
+" * exists and has either data or children\n"
+" *\n"
+" * @throws IllegalStateException if useRegionBasedMarshalling is "
+"<code>false</code>\n"
+" */\n"
+"public void activateRegion(String subtreeFqn)\n"
+" throws RegionNotEmptyException, RegionNameConflictException, "
+"CacheException;\n"
+"\n"
+"/**\n"
+" * Causes the cache to stop accepting replication events for the subtree\n"
+" * rooted at <code>subtreeFqn</code> and evict all nodes in that subtree.\n"
+" *\n"
+" * @param subtreeFqn Fqn string indicating the uppermost node in the\n"
+" * portion of the tree that should be activated.\n"
+" * @throws RegionNameConflictException if <code>subtreeFqn</code> indicates\n"
+" * a node that is part of another subtree that is being specially\n"
+" * managed (either by activate/inactiveRegion()\n"
+" * or by registerClassLoader())\n"
+" * @throws CacheException if there is a problem evicting nodes\n"
+" *\n"
+" * @throws IllegalStateException if useRegionBasedMarshalling is "
+"<code>false</code>\n"
+" */\n"
+"public void inactivateRegion(String subtreeFqn) throws "
+"RegionNameConflictException,\n"
+"CacheException;"
msgstr ""
-#: ./Treecache_marshaller.xml:188(para)
-msgid "Property <literal>InactiveOnStartup</literal> controls whether the entire cache should be considered inactive when the cache starts. In most use cases where region activation is needed, this property would be set to true. This property should be set as part of normal cache configuration, typically in the cache's XML configuration file:"
+#. Tag: para
+#: Treecache_marshaller.xml:79
+#, no-c-format
+msgid ""
+"Property <literal>InactiveOnStartup</literal> controls whether the entire "
+"cache should be considered inactive when the cache starts. In most use cases "
+"where region activation is needed, this property would be set to true. This "
+"property should be set as part of normal cache configuration, typically in "
+"the cache's XML configuration file:"
msgstr ""
-#: ./Treecache_marshaller.xml:191(programlisting)
-#, no-wrap
+#. Tag: programlisting
+#: Treecache_marshaller.xml:82
+#, no-c-format
msgid "<attribute name=\"InactiveOnStartup\">true</attribute>"
msgstr ""
-#: ./Treecache_marshaller.xml:192(para)
-msgid "When <literal>InactiveOnStartup</literal> is set to true, no state transfer will be performed on startup, even if property <literal>FetchInMemoryState</literal> is true."
+#. Tag: para
+#: Treecache_marshaller.xml:83
+#, no-c-format
+msgid ""
+"When <literal>InactiveOnStartup</literal> is set to true, no state transfer "
+"will be performed on startup, even if property <literal>FetchInMemoryState</"
+"literal> is true."
msgstr ""
-#: ./Treecache_marshaller.xml:195(para)
-msgid "When <literal>activateRegion()</literal> is invoked, each node in the cluster will be queried to see if it has active state for that portion of the tree. If one does, it will return the current state, which will then be integrated into the tree. Once state is transferred from one node, no other nodes will be asked for state. This process is somewhat different from the initial state transfer process that occurs at startup when property <literal>FetchInMemoryState</literal> is set to true. During initial state transfer, only the oldest member of the cluster is queried for state. This approach is inadequate for region activation, as it is possible that the oldest member of the cluster also has the region inactivated, and thus cannot provide state. So, each node in the cluster is queried until one provides state."
+#. Tag: para
+#: Treecache_marshaller.xml:86
+#, no-c-format
+msgid ""
+"When <literal>activateRegion()</literal> is invoked, each node in the "
+"cluster will be queried to see if it has active state for that portion of "
+"the tree. If one does, it will return the current state, which will then be "
+"integrated into the tree. Once state is transferred from one node, no other "
+"nodes will be asked for state. This process is somewhat different from the "
+"initial state transfer process that occurs at startup when property "
+"<literal>FetchInMemoryState</literal> is set to true. During initial state "
+"transfer, only the oldest member of the cluster is queried for state. This "
+"approach is inadequate for region activation, as it is possible that the "
+"oldest member of the cluster also has the region inactivated, and thus "
+"cannot provide state. So, each node in the cluster is queried until one "
+"provides state."
msgstr ""
-#: ./Treecache_marshaller.xml:198(para)
-msgid "Before requesting state from other nodes, <literal>activateRegion()</literal> will confirm that there is no existing data in the portion of the tree being activated. If there is any, a <literal>RegionNotEmptyException</literal> will be thrown."
+#. Tag: para
+#: Treecache_marshaller.xml:89
+#, no-c-format
+msgid ""
+"Before requesting state from other nodes, <literal>activateRegion()</"
+"literal> will confirm that there is no existing data in the portion of the "
+"tree being activated. If there is any, a <literal>RegionNotEmptyException</"
+"literal> will be thrown."
msgstr ""
-#: ./Treecache_marshaller.xml:201(para)
-msgid "It is important to understand that when a region of the tree is marked as inactive, this only means replication traffic from other cluster nodes related to that portion of the tree will be ignored. It is still technically possible for objects to be placed in the inactive portion of the tree locally (via a <literal>put</literal> call), and any such local activity will be replicated to other nodes. TreeCache will not prevent this kind of local activity on an inactive region, but, as discussed above <literal>activateRegion()</literal> will throw an exception if it discovers data in a region that is being activated."
+#. Tag: para
+#: Treecache_marshaller.xml:92
+#, no-c-format
+msgid ""
+"It is important to understand that when a region of the tree is marked as "
+"inactive, this only means replication traffic from other cluster nodes "
+"related to that portion of the tree will be ignored. It is still technically "
+"possible for objects to be placed in the inactive portion of the tree "
+"locally (via a <literal>put</literal> call), and any such local activity "
+"will be replicated to other nodes. TreeCache will not prevent this kind of "
+"local activity on an inactive region, but, as discussed above "
+"<literal>activateRegion()</literal> will throw an exception if it discovers "
+"data in a region that is being activated."
msgstr ""
-#: ./Treecache_marshaller.xml:205(title)
+#. Tag: title
+#: Treecache_marshaller.xml:96
+#, no-c-format
msgid "Example usage of Region Activation/Inactivation"
msgstr ""
-#: ./Treecache_marshaller.xml:206(para)
-msgid "As an example of the usage of region activation and inactivation, let's imagine a scenario where a TreeCache instance is deployed as a shared MBean service by deploying a <literal>-service.xml</literal> in the JBoss <literal>/deploy</literal> directory. One of the users of this cache could be a web application, which when started will register its classloader with the TreeCache and activate its own region of the cache."
+#. Tag: para
+#: Treecache_marshaller.xml:97
+#, no-c-format
+msgid ""
+"As an example of the usage of region activation and inactivation, let's "
+"imagine a scenario where a TreeCache instance is deployed as a shared MBean "
+"service by deploying a <literal>-service.xml</literal> in the JBoss "
+"<literal>/deploy</literal> directory. One of the users of this cache could "
+"be a web application, which when started will register its classloader with "
+"the TreeCache and activate its own region of the cache."
msgstr ""
-#: ./Treecache_marshaller.xml:209(para)
-msgid "First, the XML configuration file for the shared cache service would be configured as follows (only relevant portions are shown):"
+#. Tag: para
+#: Treecache_marshaller.xml:100
+#, no-c-format
+msgid ""
+"First, the XML configuration file for the shared cache service would be "
+"configured as follows (only relevant portions are shown):"
msgstr ""
-#: ./Treecache_marshaller.xml:212(programlisting)
-#, no-wrap
-msgid "\n<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n<server>\n <classpath codebase=\"./lib\" archives=\"jboss-cache.jar, jgroups.jar\" />\n\n <!-- ==================================================================== -->\n <!-- Defines TreeCache configuration -->\n <!-- ==================================================================== -->\n <mbean code=\"org.jboss.cache.TreeCache\" name=\"com.xyz.cache:service=SharedCache\">\n\n .......\n\n <!-- Configure Marshalling -->\n <attribute name=\"getUseRegionBasedMarshalling\">true</attribute>\n <attribute name=\"InactiveOnStartup\">true</attribute>\n\n ........\n\n </mbean>\n</server>\n"
+#. Tag: programlisting
+#: Treecache_marshaller.xml:103
+#, no-c-format
+msgid ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n"
+"<server>\n"
+" <classpath codebase=\"./lib\" archives=\"jboss-cache.jar, jgroups.jar"
+"\" />\n"
+"\n"
+" <!-- "
+"==================================================================== --"
+">\n"
+" <!-- Defines TreeCache "
+"configuration -->\n"
+" <!-- "
+"==================================================================== --"
+">\n"
+" <mbean code=\"org.jboss.cache.TreeCache\" name=\"com.xyz.cache:"
+"service=SharedCache\">\n"
+"\n"
+" .......\n"
+"\n"
+" <!-- Configure Marshalling -->\n"
+" <attribute name=\"getUseRegionBasedMarshalling\">true</"
+"attribute>\n"
+" <attribute name=\"InactiveOnStartup\">true</attribute>\n"
+"\n"
+" ........\n"
+"\n"
+" </mbean>\n"
+"</server>"
msgstr ""
-#: ./Treecache_marshaller.xml:233(para)
-msgid "For the webapp, registering/unregistering the classloader and activating/inactivating the app's region in the cache are tasks that should be done as part of initialization and destruction of the app. So, using a <literal>ServletContextListener</literal> to manage these tasks seems logical. Following is an example listener:"
+#. Tag: para
+#: Treecache_marshaller.xml:104
+#, no-c-format
+msgid ""
+"For the webapp, registering/unregistering the classloader and activating/"
+"inactivating the app's region in the cache are tasks that should be done as "
+"part of initialization and destruction of the app. So, using a "
+"<literal>ServletContextListener</literal> to manage these tasks seems "
+"logical. Following is an example listener:"
msgstr ""
-#: ./Treecache_marshaller.xml:236(programlisting)
-#, no-wrap
-msgid "\npackage example;\n\nimport javax.management.MalformedObjectNameException;\nimport javax.management.ObjectName;\nimport javax.servlet.ServletContextEvent;\nimport javax.servlet.ServletContextListener;\n\nimport org.jboss.cache.TreeCacheMBean;\nimport org.jboss.mx.util.MBeanProxyExt;\n\npublic class ActiveInactiveRegionExample implements ServletContextListener\n{\n private TreeCacheMBean cache;\n\n public void contextInitialized(ServletContextEvent arg0) {\n try {\n findCache();\n\n cache.registerClassLoader(\"/example\", Thread.currentThread().getContextClassLoader());\n cache.activeRegion(\"/example\");\n }\n catch (Exception e) {\n // ... handle exception\n }\n\n }\n\n public void contextDestroyed(ServletContextEvent arg0) {\n cache.inactivateRegion(\"/example\");\n cache.unregisterClassLoader(\"/example\");\n }\n\n private void findCache() throws MalformedObjectNameException {\n // Fin!
d the shared cache service in JMX and create a proxy to it\n ObjectName cacheServiceName_ = new ObjectName(\"com.xyz.cache:service=SharedCache\");\n // Create Proxy-Object for this service\n cache = (TreeCacheMBean) MBeanProxyExt.create(TreeCacheMBean.class, cacheServiceName_);\n }\n}\n"
+#. Tag: programlisting
+#: Treecache_marshaller.xml:107
+#, no-c-format
+msgid ""
+"package example;\n"
+"\n"
+"import javax.management.MalformedObjectNameException;\n"
+"import javax.management.ObjectName;\n"
+"import javax.servlet.ServletContextEvent;\n"
+"import javax.servlet.ServletContextListener;\n"
+"\n"
+"import org.jboss.cache.TreeCacheMBean;\n"
+"import org.jboss.mx.util.MBeanProxyExt;\n"
+"\n"
+"public class ActiveInactiveRegionExample implements ServletContextListener\n"
+"{\n"
+" private TreeCacheMBean cache;\n"
+"\n"
+" public void contextInitialized(ServletContextEvent arg0) {\n"
+" try {\n"
+" findCache();\n"
+"\n"
+" cache.registerClassLoader(\"/example\", Thread.currentThread()."
+"getContextClassLoader());\n"
+" cache.activeRegion(\"/example\");\n"
+" }\n"
+" catch (Exception e) {\n"
+" // ... handle exception\n"
+" }\n"
+"\n"
+" }\n"
+"\n"
+" public void contextDestroyed(ServletContextEvent arg0) {\n"
+" cache.inactivateRegion(\"/example\");\n"
+" cache.unregisterClassLoader(\"/example\");\n"
+" }\n"
+"\n"
+" private void findCache() throws MalformedObjectNameException {\n"
+" // Find the shared cache service in JMX and create a proxy to it\n"
+" ObjectName cacheServiceName_ = new ObjectName(\"com.xyz.cache:"
+"service=SharedCache\");\n"
+" // Create Proxy-Object for this service\n"
+" cache = (TreeCacheMBean) MBeanProxyExt.create(TreeCacheMBean.class, "
+"cacheServiceName_);\n"
+" }\n"
+"}"
msgstr ""
-#: ./Treecache_marshaller.xml:277(para)
-msgid "The listener makes use of the JBoss utility class <literal>MBeanProxyExt</literal> to find the TreeCache in JMX and create a proxy to it. (See the \"Running and using TreeCache inside JBoss\" section below for more on accessing a TreeCache). It then registers its classloader with the cache and activates its region. When the webapp is being destroyed, it inactivates its region and unregisters its classloader (thus ensuring that the classloader isn't leaked via a reference to it held by TreeCacheMarshaller)."
+#. Tag: para
+#: Treecache_marshaller.xml:108
+#, no-c-format
+msgid ""
+"The listener makes use of the JBoss utility class <literal>MBeanProxyExt</"
+"literal> to find the TreeCache in JMX and create a proxy to it. (See the "
+"\"Running and using TreeCache inside JBoss\" section below for more on "
+"accessing a TreeCache). It then registers its classloader with the cache and "
+"activates its region. When the webapp is being destroyed, it inactivates its "
+"region and unregisters its classloader (thus ensuring that the classloader "
+"isn't leaked via a reference to it held by TreeCacheMarshaller)."
msgstr ""
-#: ./Treecache_marshaller.xml:280(para)
-msgid "Note the order of the method calls in the example class -- register a classloader before activating a region, and inactivate the region before unregistering the classloader."
+#. Tag: para
+#: Treecache_marshaller.xml:111
+#, no-c-format
+msgid ""
+"Note the order of the method calls in the example class -- register a "
+"classloader before activating a region, and inactivate the region before "
+"unregistering the classloader."
msgstr ""
-#: ./Treecache_marshaller.xml:288(title)
+#. Tag: title
+#: Treecache_marshaller.xml:119
+#, no-c-format
msgid "Region Activation/Inactivation with a CacheLoader"
msgstr ""
-#: ./Treecache_marshaller.xml:289(para)
-msgid "The activateRegion()/inactivateRegion() API can be used in conjunction with a CacheLoader as well, but only if the cache loader implementation implements interface <literal>org.jboss.cache.loader.ExtendedCacheLoader</literal>. This is a subinterface of the normal <literal>CacheLoader</literal> interface. It additionally specifies the following methods needed to support the partial state transfer that occurs when a region is activated:"
+#. Tag: para
+#: Treecache_marshaller.xml:120
+#, no-c-format
+msgid ""
+"The activateRegion()/inactivateRegion() API can be used in conjunction with "
+"a CacheLoader as well, but only if the cache loader implementation "
+"implements interface <literal>org.jboss.cache.loader.ExtendedCacheLoader</"
+"literal>. This is a subinterface of the normal <literal>CacheLoader</"
+"literal> interface. It additionally specifies the following methods needed "
+"to support the partial state transfer that occurs when a region is activated:"
msgstr ""
-#: ./Treecache_marshaller.xml:292(programlisting)
-#, no-wrap
-msgid "\n /**\n * Fetch a portion of the state for this cache from secondary storage\n * (disk, DB) and return it as a byte buffer.\n * This is for activation of a portion of new cache from a remote cache.\n * The new cache would then call {@link #storeState(byte[], Fqn)}.\n *\n * @param subtree Fqn naming the root (i.e. highest level parent) node of\n * the subtree for which state is requested.\n *\n * @see org.jboss.cache.TreeCache#activateRegion(String)\n */\n byte[] loadState(Fqn subtree) throws Exception;\n\n /**\n * Store the given portion of the cache tree's state in secondary storage.\n * Overwrite whatever is currently in secondary storage.\n *\n * @param state the state to store\n * @param subtree Fqn naming the root (i.e. highest level parent) node of\n * the subtree included in <code>state</code>.\n */\n void storeState(byte[] state, Fqn subtree) throws Exception;\n\n /*!
*\n * Sets the RegionManager this object should use to manage\n * marshalling/unmarshalling of different regions using different\n * classloaders.\n * \n * NOTE: This method is only intended to be used\n * by the <code>TreeCache</code> instance this cache loader is\n * associated with.\n * \n *\n * @param manager the region manager to use, or <code>null</code>.\n */\n void setRegionManager(RegionManager manager);\n \n"
+#. Tag: programlisting
+#: Treecache_marshaller.xml:123
+#, no-c-format
+msgid ""
+"/**\n"
+" * Fetch a portion of the state for this cache from secondary storage\n"
+" * (disk, DB) and return it as a byte buffer.\n"
+" * This is for activation of a portion of new cache from a remote cache.\n"
+" * The new cache would then call {@link #storeState(byte[], Fqn)}.\n"
+" *\n"
+" * @param subtree Fqn naming the root (i.e. highest level parent) node "
+"of\n"
+" * the subtree for which state is requested.\n"
+" *\n"
+" * @see org.jboss.cache.TreeCache#activateRegion(String)\n"
+" */\n"
+" byte[] loadState(Fqn subtree) throws Exception;\n"
+"\n"
+" /**\n"
+" * Store the given portion of the cache tree's state in secondary "
+"storage.\n"
+" * Overwrite whatever is currently in secondary storage.\n"
+" *\n"
+" * @param state the state to store\n"
+" * @param subtree Fqn naming the root (i.e. highest level parent) node "
+"of\n"
+" * the subtree included in <code>state</code>.\n"
+" */\n"
+" void storeState(byte[] state, Fqn subtree) throws Exception;\n"
+"\n"
+" /**\n"
+" * Sets the RegionManager this object should use to manage\n"
+" * marshalling/unmarshalling of different regions using different\n"
+" * classloaders.\n"
+" * \n"
+" * NOTE: This method is only intended to be used\n"
+" * by the <code>TreeCache</code> instance this cache loader is\n"
+" * associated with.\n"
+" * \n"
+" *\n"
+" * @param manager the region manager to use, or <code>null</code>.\n"
+" */\n"
+" void setRegionManager(RegionManager manager);"
msgstr ""
-#: ./Treecache_marshaller.xml:331(para)
-msgid "JBossCache currently comes with two implementations of ExtendedCacheLoader, <literal>FileExtendedCacheLoader</literal> and <literal>JDBCExtendedCacheLoader</literal>. These classes extend FileCacheLoader and JDBCCacheLoader, respectively, implementing the extra methods in the extended interface."
+#. Tag: para
+#: Treecache_marshaller.xml:124
+#, no-c-format
+msgid ""
+"JBossCache currently comes with two implementations of ExtendedCacheLoader, "
+"<literal>FileExtendedCacheLoader</literal> and "
+"<literal>JDBCExtendedCacheLoader</literal>. These classes extend "
+"FileCacheLoader and JDBCCacheLoader, respectively, implementing the extra "
+"methods in the extended interface."
msgstr ""
-#: ./Treecache_marshaller.xml:337(title)
+#. Tag: title
+#: Treecache_marshaller.xml:130
+#, no-c-format
msgid "Performance over Java serialization"
msgstr ""
-#: ./Treecache_marshaller.xml:338(para)
-msgid "To achieve the performance and efficiency gains, the <literal>TreeCacheMarshaller</literal> uses a number of techniques including method ids for known methods and magic numbers for known internal class types which drastically reduces the size of calls to remote caches, greatly improving throughput and reducing the overhead of Java serialization."
+#. Tag: para
+#: Treecache_marshaller.xml:131
+#, no-c-format
+msgid ""
+"To achieve the performance and efficiency gains, the "
+"<literal>TreeCacheMarshaller</literal> uses a number of techniques including "
+"method ids for known methods and magic numbers for known internal class "
+"types which drastically reduces the size of calls to remote caches, greatly "
+"improving throughput and reducing the overhead of Java serialization."
msgstr ""
-#: ./Treecache_marshaller.xml:341(para)
-msgid "To make things even faster, the <literal>TreeCacheMarshaller</literal> uses <ulink url=\"http://labs.jboss.org/portal/index.html?ctrl:id=page.default.info&project=serialization\">JBoss Serialization</ulink>, a highly efficient drop-in replacement for Java serialization for user-defined classes. JBoss Serialization is enabled and always used by default, although this can be disabled, causing the marshalling of user-defined classes to revert to Java serialization. JBoss Serialization is disabled by passing in the <literal>-Dserialization.jboss=false</literal> environment variable into your JVM."
+#. Tag: para
+#: Treecache_marshaller.xml:134
+#, no-c-format
+msgid ""
+"To make things even faster, the <literal>TreeCacheMarshaller</literal> uses "
+"<ulink url=\"http://labs.jboss.org/portal/index.html?ctrl:id=page.default."
+"info&project=serialization\">JBoss Serialization</ulink>, a highly "
+"efficient drop-in replacement for Java serialization for user-defined "
+"classes. JBoss Serialization is enabled and always used by default, although "
+"this can be disabled, causing the marshalling of user-defined classes to "
+"revert to Java serialization. JBoss Serialization is disabled by passing in "
+"the <literal>-Dserialization.jboss=false</literal> environment variable into "
+"your JVM."
msgstr ""
-#: ./Treecache_marshaller.xml:347(title)
+#. Tag: title
+#: Treecache_marshaller.xml:140
+#, no-c-format
msgid "Backward compatibility"
msgstr ""
-#: ./Treecache_marshaller.xml:348(para)
-msgid "Marshalling in JBoss Cache is now versioned. All communications between caches contain a version <literal>short</literal> which allows JBoss Cache instances of different versions to communicate with each other. Up until JBoss Cache 1.4.0, all versions were able to communicate with each other anyway since they all used simple serialization of <literal>org.jgroups.MethodCall</literal> objects, provided they all used the same version of JGroups. This requirement (more a requirement of the JGroups messaging layer than JBoss Cache) still exists, even though with JBoss Cache 1.4.0, we've moved to a much more efficient and sophisticated marshalling mechanism."
+#. Tag: para
+#: Treecache_marshaller.xml:141
+#, no-c-format
+msgid ""
+"Marshalling in JBoss Cache is now versioned. All communications between "
+"caches contain a version <literal>short</literal> which allows JBoss Cache "
+"instances of different versions to communicate with each other. Up until "
+"JBoss Cache 1.4.0, all versions were able to communicate with each other "
+"anyway since they all used simple serialization of <literal>org.jgroups."
+"MethodCall</literal> objects, provided they all used the same version of "
+"JGroups. This requirement (more a requirement of the JGroups messaging layer "
+"than JBoss Cache) still exists, even though with JBoss Cache 1.4.0, we've "
+"moved to a much more efficient and sophisticated marshalling mechanism."
msgstr ""
-#: ./Treecache_marshaller.xml:352(programlisting)
-#, no-wrap
-msgid " \n<!-- takes values such as 1.2.3, 1.2.4 and 1.3.0 -->\n<attribute name=\"ReplicationVersion\">1.2.4</attribute>\n"
+#. Tag: para
+#: Treecache_marshaller.xml:144
+#, no-c-format
+msgid ""
+"JBoss Cache 1.4.0 and future releases of JBoss Cache will always be able to "
+"unmarshall data from previous versions of JBoss Cache. For JBoss Cache 1.4.0 "
+"and future releases to marshall data in a format that is compatible with "
+"older versions, however, you would have to start JBoss Cache with the "
+"following configuration attribute:"
msgstr ""
-#: ./Treecache_marshaller.xml:351(para)
-msgid "JBoss Cache 1.4.0 and future releases of JBoss Cache will always be able to unmarshall data from previous versions of JBoss Cache. For JBoss Cache 1.4.0 and future releases to marshall data in a format that is compatible with older versions, however, you would have to start JBoss Cache with the following configuration attribute: <placeholder-1/>"
+#. Tag: programlisting
+#: Treecache_marshaller.xml:145
+#, no-c-format
+msgid ""
+"<!-- takes values such as 1.2.3, 1.2.4 and 1.3.0 -->\n"
+"<attribute name=\"ReplicationVersion\">1.2.4</attribute>"
msgstr ""
-
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: ./Treecache_marshaller.xml:0(None)
-msgid "translator-credits"
-msgstr ""
-
More information about the jbosscache-commits
mailing list