[jbosscache-commits] JBoss Cache SVN: r7459 - enterprise-docs/tags/JBoss_EAP_4_3/Cache_Tutorial/fr-FR.
jbosscache-commits at lists.jboss.org
jbosscache-commits at lists.jboss.org
Tue Jan 13 19:48:40 EST 2009
Author: xhuang at jboss.com
Date: 2009-01-13 19:48:40 -0500 (Tue, 13 Jan 2009)
New Revision: 7459
Removed:
enterprise-docs/tags/JBoss_EAP_4_3/Cache_Tutorial/fr-FR/Tutorial.po
Log:
update
Deleted: enterprise-docs/tags/JBoss_EAP_4_3/Cache_Tutorial/fr-FR/Tutorial.po
===================================================================
--- enterprise-docs/tags/JBoss_EAP_4_3/Cache_Tutorial/fr-FR/Tutorial.po 2009-01-14 00:47:14 UTC (rev 7458)
+++ enterprise-docs/tags/JBoss_EAP_4_3/Cache_Tutorial/fr-FR/Tutorial.po 2009-01-14 00:48:40 UTC (rev 7459)
@@ -1,971 +0,0 @@
-# Language fr-FR translations for JBoss_EAP package.
-# Copyright (C) 2009 Free Software Foundation, Inc.
-# Automatically generated, 2009.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: JBoss_EAP 4_3\n"
-"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: Tutorial.xml:10
-#, no-c-format
-msgid "JBossCache Tutorial"
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:13
-#, no-c-format
-msgid "Introduction"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:14
-#, no-c-format
-msgid ""
-"JBossCache is an in-memory replicated (synchronous or asynchronous), "
-"transactional, and fine-grained cache. It consists of two subsystems: "
-"TreeCache (plaing cache) and PojoCache (object-oriented POJO cache). In this "
-"tutorial, we will demonstrate the usage of both cache features. For details "
-"of the usage and APIs, please refer to the user manuals for <ulink url="
-"\"http://labs.jboss.org/portal/jbosscache/docs/index.html\">TreeCache</"
-"ulink> and <ulink url=\"http://labs.jboss.org/portal/jbosscache/docs/index."
-"html\">PojoCache</ulink>."
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:18
-#, no-c-format
-msgid "Scope"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:21
-#, no-c-format
-msgid "Cache creation and modification"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:26
-#, no-c-format
-msgid "Replication"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:31
-#, no-c-format
-msgid "<para>PojoCache</para>"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:36
-#, no-c-format
-msgid "Transaction"
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:45
-#, no-c-format
-msgid "Configuration"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:46
-#, no-c-format
-msgid ""
-"First download the standalone TreeCache code from <ulink url=\"http://labs."
-"jboss.org/portal/jbosscache/download/index.html\">here</ulink>. Unzip it, "
-"and you will get a root directory (jboss-cache in our example)."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:49
-#, no-c-format
-msgid ""
-"The configuration files are located under the etc directory. You can modify "
-"the behavior of TreeCache through editing the various configuration files."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:54
-#, no-c-format
-msgid ""
-"<literal>log4j.xml</literal>. Logging output. You can turn on logging level "
-"or change log file directory (default is <literal>/tmp/jbosscache.log</"
-"literal>)."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:59
-#, no-c-format
-msgid ""
-"<literal>replSync-service.xml</literal>. Tree cache configuration file (file "
-"name is not fixed. You specify the file to be read in "
-"<literal>PropertyConfigurator</literal>). The settings are for a replicated, "
-"synchronous, and transactional cache. The default DummyTransactionManager is "
-"used with a transaction isolation level of REPEATABLE_READ. For details of "
-"the configuration parameters, please refer to the <ulink url=\"http://www."
-"jboss.org/products/jbosscache/docs\">Treecache</ulink>. Note that this file "
-"is used in the BSH ( <ulink url=\"http://www.beanshell.org/\">BeanShell</"
-"ulink>, a lightweight Java compatible scripting language) script to "
-"configure the cache."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:64
-#, no-c-format
-msgid ""
-"<literal>jboss-aop.xml</literal>. AOP pointcut and advice definition for the "
-"example POJO classes, Person and Address, respectively. For details of how "
-"to put your own class under AOP, please refer to the <ulink url=\"http://www."
-"jboss.org/products/jbosscache/docs\">PojoCache</ulink>. This file is read in "
-"when the process is started."
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:71
-#, no-c-format
-msgid "Script"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:72
-#, no-c-format
-msgid ""
-"The script files that are needed (located under install directory) in this "
-"tutorial are:"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:77
-#, no-c-format
-msgid ""
-"<literal>build.sh</literal> (or <literal>build.bat</literal> for DOS/"
-"Windows). Simple build script that wraps around ant. Users can simply type "
-"<literal>sh build.sh</literal> for help. Note from now on, we will only "
-"refer to the Unix version with the understanding that there is a "
-"corresponding DOS counterpart. The same goes for runDemoShell explained next."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:82
-#, no-c-format
-msgid ""
-"<literal>runDemoShell.sh</literal>. Simple run script that wraps around "
-"BeanShell. This is used to operate the replicated cache through interactive "
-"command line."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:87
-#, no-c-format
-msgid ""
-"<literal>plain.bsh</literal>. Java code that instantiate and configure the "
-"cache. It also creates an example cache entry."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:92
-#, no-c-format
-msgid ""
-"<literal>aop.bsh</literal>. Java codes that instantiate and configure the "
-"aop cache. In addition, it also sets up the example POJO (plaing old Java "
-"object) classes (e.g., Person and Address)."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:97
-#, no-c-format
-msgid ""
-"<literal>aopWithTx.bsh</literal>. Same with aop.bsh except it also "
-"instantiates a transaction context."
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:104
-#, no-c-format
-msgid "Example POJO"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:105
-#, no-c-format
-msgid ""
-"The example POJO classes used for PojoCache demo are: <literal>Person</"
-"literal> and <literal>Address</literal>. They are located under "
-"<literal>tests/org/jboss/cache/aop</literal> directory. <literal>Person</"
-"literal> has attributes of <literal>String age, Address addr, List languages "
-"</literal> , etc. We will demonstrate that once you put the POJO instance in "
-"the cache, plain get/set POJO methods will be intercepted by the cache."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:108
-#, no-c-format
-msgid ""
-"Here is the snippet of the class definition for <literal>Person</literal> "
-"and <literal>Address</literal> ."
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:111
-#, no-c-format
-msgid ""
-"public class Person {\n"
-" String name=null;\n"
-" int age=0;\n"
-" Map hobbies=null;\n"
-" Address address=null;\n"
-" Set skills;\n"
-" List languages;\n"
-"\n"
-" public String getName() { return name; }\n"
-" public void setName(String name) { this.name=name; }\n"
-" ...\n"
-" }"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:112
-#, no-c-format
-msgid ""
-"public class Address {\n"
-" String street=null;\n"
-" String city=null;\n"
-" int zip=0;\n"
-"\n"
-" public String getStreet() { return street; }\n"
-" public void setStreet(String street) { this.street=street; }\n"
-" ...\n"
-" }"
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:115
-#, no-c-format
-msgid "Demo"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:116
-#, no-c-format
-msgid ""
-"To run the demo, you will need at least two windows: one to peruse the cache "
-"contents (plus non-aop operations) and the other to operate the cache "
-"directly. Of course, you can also open more than one GUI window to see the "
-"cache replication at work to multiple members. You will also need to run the "
-"scripts under jboss-cache installation directory after you unzip the release "
-"package (jboss-cache-dist.zip). Due to the limitation of the GUI, please "
-"note that:"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:121
-#, no-c-format
-msgid ""
-"For each demo example, it'd be best if you re-start the whole setup."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:126
-#, no-c-format
-msgid ""
-"While you can modify the cache content on the GUI window and it will show up "
-"on the BSH cache content (e.g., through <literal>cache.printDetails()</"
-"literal> ), this won't work on PojoCache demo. That is, you can only "
-"modify the cache content on the BSH window."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:131
-#, no-c-format
-msgid "The two demo programs to run are:"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:136
-#, no-c-format
-msgid ""
-"On the first window for the GUI, type <literal>sh build.sh </literal> to see "
-"the available commands. To run the GUI, type <literal>sh build.sh run.demo</"
-"literal> . It will startup a PojoCache GUI. Later on, you can click on a "
-"node to view the the contents. Note that you can also add/modify the node "
-"contents for non-AOP cache entries. Since the GUI entry only accepts String "
-"for now, operation on aop cache from the GUI will not always work (unless it "
-"is a String type)."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:141
-#, no-c-format
-msgid ""
-"On the second window for the interactive Java commands, type sh runShellDemo."
-"sh to fire off the BeanShell interactive command shell (you can use either "
-"^D or ^Z in Windows and Unix to exit afterward). You can then read in the "
-"Java code scripts to showcase the cache capabilities (e.g., plain.bsh, aop."
-"bsh, and aopWithTx.bsh). See the following for details."
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:148
-#, no-c-format
-msgid "Plain cache"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:149
-#, no-c-format
-msgid ""
-"Once you are in the shell, you can either execute the script to populate the "
-"cache, or type it in manually by command line. To run the script, type "
-"<literal>sourceRelative(\"plain.bsh\");</literal> under the interactive BSH "
-"shell. For this to work, you'll need to have your working directory set "
-"to the directory in which plain.bsh resides (otherwise give the full "
-"pathname of plain.bsh). Basically, the script will create cache entries that "
-"will be replicated onto the GUI. (You may have to type show() into the "
-"resulting beanshell window yourself) Here are the snippets for the script:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:152
-#, no-c-format
-msgid ""
-"import org.jboss.cache.*;\n"
-" show(); // verbose mode for bean shell\n"
-" TreeCache tree = new TreeCache();\n"
-" PropertyConfigurator config = new PropertyConfigurator(); \n"
-" // configure tree cache. Needs to be in the classpath\n"
-" config.configure(tree, \"META-INF/replSync-service.xml\");\n"
-" tree.startService(); \n"
-" // kick start tree cache\n"
-" tree.put(\"/a/b/c\", \"ben\", \"me\"); \n"
-" // create a cache entry.\n"
-" // Node \"/a/b/c\" will be created if it does not yet exist."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:153
-#, no-c-format
-msgid ""
-"You should see in the GUI that a new entry of <literal>/a/b/c</literal> has "
-"been created. Click on the node c to see the content. You can modify the "
-"contents from the GUI as well. To create another node, for example, you can "
-"type in the shell:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:156
-#, no-c-format
-msgid ""
-"tree.put(\"/a/b/c/d\", \"JBoss\", \"Open Source\");\n"
-" tree.get(\"/a/b/c/d\", \"JBoss\");"
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:159
-#, no-c-format
-msgid "<title>PojoCache</title>"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:160
-#, no-c-format
-msgid ""
-"Once you are in the shell, type <literal>sourceRelative(\"aop.bsh\");</"
-"literal> to execute the shell script. Basically, aop.bsh illustrates the "
-"steps to instantiate a cache, configure it, and then create entries under "
-"it. Here are the snippets:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:163
-#, no-c-format
-msgid ""
-"import org.jboss.cache.PropertyConfigurator;\n"
-" import org.jboss.cache.aop.PojoCache;\n"
-" import org.jboss.cache.aop.test.Person;\n"
-" import org.jboss.cache.aop.test.Address;\n"
-" show(); // verbose mode for bean shell\n"
-" PojoCache tree = new PojoCache();\n"
-" PropertyConfigurator config = new PropertyConfigurator(); // "
-"configure tree cache.\n"
-" config.configure(tree, \"META-INF/replSync-service.xml\");\n"
-" Person joe = new Person(); // instantiate a Person object named "
-"joe\n"
-" joe.setName(\"Joe Black\");\n"
-" joe.setAge(31);\n"
-" Address addr = new Address(); // instantiate a Address object named "
-"addr\n"
-" addr.setCity(\"Sunnyvale\");\n"
-" addr.setStreet(\"123 Albert Ave\");\n"
-" addr.setZip(94086); joe.setAddress(addr); // set the address "
-"reference\n"
-" tree.startService(); // kick start tree cache\n"
-" tree.putObject(\"/aop/joe\", joe); \n"
-" // add aop sanctioned object (and sub-objects) into cache.\n"
-" // since it is aop-sanctioned, use of plain get/set methods will "
-"take care\n"
-" // of cache contents automatically.\n"
-" joe.setAge(41);"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:164
-#, no-c-format
-msgid ""
-"Note the API needed to put the object (and its dependent ones) into cache is "
-"putObject. Once the second window finishes execution, you should see the "
-"first GUI window has been populated with entries of /aop/joe/address. Click "
-"on each tree node will display different values associated with that node."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:167
-#, no-c-format
-msgid ""
-"Next step to see AOP in action, you can do plain get/set methods without "
-"ever worrying about put it in the cache. For example, you can do in the "
-"shell window joe.setAge(20); and see that GUI gets updated with the age "
-"field automatically (if not, click away and back will refresh the GUI "
-"content). Also to demonstrate the object graph replication, you can modify "
-"Joe's address and see the cache will update it automatically. For "
-"example, type addr.setCity(\"San Jose\"); in the interactive shell, you "
-"should see in the GUI that the address got modified."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:170
-#, no-c-format
-msgid ""
-"Finally, PojoCache also supports get/set with parameter type of Collection "
-"classes (i.e., List, Map, and Set). For example, type the following in the "
-"shell command line:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:173
-#, no-c-format
-msgid ""
-"ArrayList lang = new ArrayList();\n"
-" lang.add(\"Ensligh\");\n"
-" lang.add(\"Mandarin\");\n"
-" joe.setLanguages(lang);"
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:176
-#, no-c-format
-msgid "PojoCache with Transaction"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:177
-#, no-c-format
-msgid ""
-"To see TreeCache transaction at work, you start with the same setup with "
-"last section except you load the bsh of aopWithTx.bsh instead of aop.bsh. "
-"The additional snippets are:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:180
-#, no-c-format
-msgid ""
-"import org.jboss.cache.PropertyConfigurator;\n"
-" import org.jboss.cache.aop.PojoCache;\n"
-" import org.jboss.cache.aop.test.Person;\n"
-" import org.jboss.cache.aop.test.Address;// Tx imports\n"
-" import javax.transaction.UserTransaction; import javax.naming.*;\n"
-" import org.jboss.cache.transaction.DummyTransactionManager;\n"
-" show(); // verbose mode for bean shell\n"
-" // Set up transaction manager\n"
-" DummyTransactionManager.getInstance();\n"
-" Properties prop = new Properties();\n"
-" prop.put(Context.INITIAL_CONTEXT_FACTORY,\n"
-" \"org.jboss.cache.transaction.DummyContextFactory\");\n"
-" UserTransaction tx = (UserTransaction)new\n"
-" InitialContext(prop).lookup(\"UserTransaction\");\n"
-" PojoCache tree = new PojoCache();\n"
-" PropertyConfigurator config = new PropertyConfigurator(); \n"
-" // configure tree cache.\n"
-" config.configure(tree, \"META-INF/replSync-service.xml\");\n"
-" joe = new Person();\n"
-" joe.setName(\"Joe Black\");\n"
-" joe.setAge(31);\n"
-"\n"
-" Address addr = new Address();\n"
-" addr.setCity(\"Sunnyvale\");\n"
-" addr.setStreet(\"123 Albert Ave\");\n"
-" addr.setZip(94086);\n"
-" joe.setAddress(addr);\n"
-"\n"
-" tree.startService(); // kick start tree cache\n"
-" tree.putObject(\"/aop/joe\", joe); // add aop sanctioned object\n"
-" // since it is aop-sanctioned, use of plain get/set methods will "
-"take care\n"
-" of cache contents automatically.\n"
-" // Also it is transacted\n"
-" tx.begin();\n"
-" joe.setAge(41);\n"
-" joe.getAddress().setZip(95124);\n"
-" tx.commit();"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:181
-#, no-c-format
-msgid "In this example, a default dummy transaction manager is used."
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:184
-#, no-c-format
-msgid ""
-"tx.begin();\n"
-" addr.setZip(95131);\n"
-" tx.rollback();"
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:187
-#, no-c-format
-msgid "CacheLoader examples"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:188
-#, no-c-format
-msgid ""
-"All the examples below are based on the JBossCache standalone distribution. "
-"We assume the ZIP file has been unzipped into a directory <literal>jboss-"
-"cache</literal> ."
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:192
-#, no-c-format
-msgid "Local cache with CacheLoader"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:193
-#, no-c-format
-msgid ""
-"This demo shows a local PojoCache with a CacheLoader. We will insert a POJO "
-"into the cache, and see that the POJO is transparently saved using the "
-"CacheLoader."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:196
-#, no-c-format
-msgid ""
-"To run this, you have to modify <literal>jboss-cache/output/etc/META-INF/"
-"oodb-service.xml</literal> : change <literal>CacheLoaderConfig</literal> to "
-"point to a valid directory (create it if it doesn't yet exist):"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:199
-#, no-c-format
-msgid ""
-"<attribute name=\"CacheLoaderConfig\">\n"
-" location=c:\\\\tmp\\\\oodb\n"
-" </attribute>"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:200
-#, no-c-format
-msgid ""
-"Then start the beanshell and source <literal>oodb.bsh</literal> into it. "
-"Note that <literal>oodb.bsh</literal> already contains code to create and "
-"retrieve POJO from the cache. So remember to comment them out if you decide "
-"to create the Person instance yourself."
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:203
-#, no-c-format
-msgid ""
-"bela at laptop /cygdrive/c/jboss-cache\n"
-" $ ./runShellDemo.sh\n"
-" BeanShell 1.3.0 - by Pat Niemeyer (pat at pat.net)\n"
-" bsh % sourceRelative(\"oodb.bsh\");\n"
-" interceptor chain is:\n"
-" class org.jboss.cache.interceptors.CallInterceptor\n"
-" class org.jboss.cache.interceptors.CacheLoaderInterceptor\n"
-" class org.jboss.cache.interceptors.TransactionInterceptor\n"
-" <null>\n"
-" bsh %"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:204
-#, no-c-format
-msgid ""
-"Next, create an instance of Person, and set its address and other fields:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:207
-#, no-c-format
-msgid ""
-"bsh % p=new Person();\n"
-" <name=null, age=0, hobbies=, address=null, skills=null, "
-"languages=null>\n"
-" bsh % p.age=3;\n"
-" <3>\n"
-" bsh % p.name=\"Michelle\";\n"
-" <Michelle>\n"
-" bsh % addr=new Address();\n"
-" <street=null, city=null, zip=0>\n"
-" bsh % addr.city=\"San Jose\";\n"
-" <San Jose>\n"
-" bsh % addr.zip=95124;\n"
-" <95124>\n"
-" bsh % addr.street=\"1704 Almond Blossom Lane\";\n"
-" <1704 Almond Blossom Lane>\n"
-" bsh % p.setAddress(addr);\n"
-" bsh % tree.putObject(\"/person/me\", p);\n"
-" bsh % p;\n"
-" <name=Michelle, age=3, hobbies=, address=street=1704 Almond "
-"Blossom Lane, \n"
-" city=San Jose, zip=95124, skills=null, languages=null>\n"
-" bsh %"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:208
-#, no-c-format
-msgid ""
-"The <literal>Person</literal> object with all of its fields and subobjects "
-"is now saved. Let's kill beanshell and restart it. At this point, "
-"because the instance of <literal>Person</literal> we created was given the "
-"name \"p\", we can retrieve it again:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:211
-#, no-c-format
-msgid ""
-"bela at laptop /cygdrive/c/jboss-cache\n"
-" $ ./runShellDemo.sh\n"
-" BeanShell 1.3.0 - by Pat Niemeyer (pat at pat.net)\n"
-" bsh % sourceRelative(\"oodb.bsh\");\n"
-" interceptor chain is:\n"
-" class org.jboss.cache.interceptors.CallInterceptor\n"
-" class org.jboss.cache.interceptors.CacheLoaderInterceptor\n"
-" class org.jboss.cache.interceptors.TransactionInterceptor\n"
-" <null>\n"
-" bsh % tree;\n"
-" </>\n"
-" bsh % p=tree.getObject(\"/person/me\");\n"
-" <name=Michelle, age=3, hobbies=, address=street=1704 Almond "
-"Blossom Lane, \n"
-" city=San Jose, zip=95124, skills=null, languages=null>\n"
-" bsh % tree;\n"
-" </p\n"
-" /address\n"
-" >\n"
-" bsh %"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:212
-#, no-c-format
-msgid ""
-"The interesting thing here is that the cache was initially empty (\"/\"). "
-"Only when we loaded \"p\", did it get populated (lazy loading). You can see "
-"that the values of \"p\" are loaded from the datastore where they were "
-"previously saved."
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:221
-#, no-c-format
-msgid "Replicated cache with shared datastore"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:222
-#, no-c-format
-msgid ""
-"The scenario that we'll run in this example is described in the "
-"documentation for JBossCache. It consists of 2 separate nodes that replicate "
-"their contents between each other. In addition, they both point to the "
-"<emphasis>same</emphasis> datastore. The configuration is in file "
-"<literal>jboss-cache/output/etc/META-INF/replAsyncSharedCacheLoader-service."
-"xml</literal> :"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:225
-#, no-c-format
-msgid ""
-"<!-- Whether or not to fetch state on joining a cluster -->\n"
-" <attribute name=\"FetchStateOnStartup\">false</"
-"attribute>\n"
-" <attribute name=\"CacheLoaderClass\">org.jboss.cache."
-"loader.FileCacheLoader</attribute>\n"
-" <attribute name=\"CacheLoaderConfig\">\n"
-" location=c:\\\\tmp\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>"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:226
-#, no-c-format
-msgid ""
-"The <literal>FetchStateOnStartup</literal> attribute set to <literal>false</"
-"literal> means that a newly started cache will <emphasis>not</emphasis> "
-"attempt to fetch the state (neither transient nor persistent). Therefore, "
-"attributes <literal>CacheLoaderFetchTransientState</literal> and "
-"<literal>CacheLoaderFetchPersistentState</literal> will be ignored. "
-"<literal>CacheLoaderShared</literal> set to <literal>true</literal> means "
-"that both nodes will share the same datastore, which resides in <literal>c:"
-"\\tmp</literal> in the example (this assumes that both nodes have access to "
-"the same file system). Please make sure that <literal>c:\\tmp</literal> "
-"exists, or point the config string to a different existing directory."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:229
-#, no-c-format
-msgid ""
-"This configuration would essentially provide for two <literal>cold</literal> "
-"nodes, in the sense that all contents of a new cache is in the datastore, "
-"and is lazy-loaded via the CacheLoader when accessed. However, this is not "
-"true, as <literal>CacheLoaderPreload</literal> points to \"/\", which is the "
-"root of the entire tree. Therefore, all of the contents of the cache are "
-"recursively pre-loaded. This is probably a bad configuration when you have a "
-"lot of data in the cache, because <emphasis>all</emphasis> of your data will "
-"be loaded into the cache."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:232
-#, no-c-format
-msgid ""
-"Note that with a shared datastore, the node that makes a modification is the "
-"one who writes it to the store using the CacheLoader. This prevents both "
-"nodes from writing the same data twice."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:235
-#, no-c-format
-msgid ""
-"We can now start 2 instances by opening two shells and executing the "
-"following ANT target:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:238
-#, no-c-format
-msgid ""
-"bela at laptop /cygdrive/c/jboss-cache\n"
-" $ ./build.sh run.demo.async.shared.cacheloader\n"
-" Buildfile: build.xml\n"
-"\n"
-" init:\n"
-"\n"
-" compile:\n"
-"\n"
-" run.demo.async.shared.cacheloader:\n"
-" [java] ** node loaded: /a\n"
-" [java] ** node loaded: /a/b\n"
-" [java] ** node loaded: /a/b/c\n"
-" [java] ** node loaded: /uno\n"
-" [java] ** node loaded: /uno/due\n"
-"\n"
-" [java] -------------------------------------------------------\n"
-" [java] GMS: address is 192.168.1.184:1357\n"
-" [java] -------------------------------------------------------\n"
-" [java] interceptor chain is:\n"
-" [java] class org.jboss.cache.interceptors.CallInterceptor\n"
-" [java] class org.jboss.cache.interceptors."
-"ReplicationInterceptor\n"
-" [java] class org.jboss.cache.interceptors."
-"CacheLoaderInterceptor\n"
-" [java] class org.jboss.cache.interceptors."
-"TransactionInterceptor\n"
-" [java] ** view change: [192.168.1.184:1355|1] "
-"[192.168.1.184:1355,\n"
-" 192.168.1.184:1357]\n"
-" [java] ** node modified: /"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:239
-#, no-c-format
-msgid ""
-"2 GUI instances will appear, showing the tree structure of the cache "
-"graphically. Nodes can be added, modified or removed by right-clicking or "
-"using the menu. Any modification is replicated between the two nodes. If "
-"both nodes are killed, and subsequently one or both nodes are restarted, the "
-"state is the same as before shutdown as it was persisted to the shared store "
-"via the CacheLoader."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:242
-#, no-c-format
-msgid ""
-"Note that the example above shows the 2 nodes running on the same machine "
-"(192.168.1.184) on ports 1355 and 1357."
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:247
-#, no-c-format
-msgid "Replicated cache with unshared (local) datastore"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:248
-#, no-c-format
-msgid ""
-"In this example, we'll run 2 nodes again, but this time, instead of "
-"sharing the same datastore, each node has its own datastore. The "
-"configuration is in file <literal>jboss-cache/output/etc/META-INF/node{1,2}."
-"xml</literal> . We'll look at node1.xml:"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:251
-#, no-c-format
-msgid ""
-"<attribute name=\"CacheLoaderClass\">org.jboss.cache.loader.bdbje."
-"BdbjeCacheLoader</attribute>\n"
-" <attribute name=\"CacheLoaderConfig\">\n"
-" location=c:\\\\tmp\\\\node1\n"
-" </attribute>\n"
-" <attribute name=\"CacheLoaderShared\">false</"
-"attribute>\n"
-" <attribute name=\"CacheLoaderPreload\">/</"
-"attribute>\n"
-" <attribute name=\"CacheLoaderFetchTransientState\">"
-"false</attribute>\n"
-" <attribute name=\"CacheLoaderFetchPersistentState\">"
-"true</attribute>"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:252
-#, no-c-format
-msgid ""
-"Again, we use the Sleepycat CacheLoader implementation in "
-"<literal>CacheLoaderClass</literal> . The <literal>CacheLoaderConfig</"
-"literal> points to <literal>c:\\tmp\\node1</literal> . This is the directory "
-"in which the Sleepycat DB for node1 will reside. File node2.xml has a "
-"configuration that points to <literal>c:\\tmp\\node2</literal> , so we have "
-"2 different unshared datastores. Note that, of course, we still have the "
-"same filesystem in our case, because we run the 2 nodes on the same machine. "
-"In practice those two directories would reside on two different machines, "
-"and each machine would run one JBossCache process. Note that the 2 "
-"directories have to exis"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:255
-#, no-c-format
-msgid ""
-"To create an unshared datastore, we set the <literal>CacheLoaderShared</"
-"literal> attribute to <literal>false</literal> ."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:258
-#, no-c-format
-msgid ""
-"The example can be run by again opening 2 shells, and running 2 ANT targets "
-"(here we show the target for node1):"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:261
-#, no-c-format
-msgid ""
-"bela at laptop /cygdrive/c/jboss-cache\n"
-" $ ./build.sh run.demo.unshared.node2\n"
-" Buildfile: build.xml\n"
-"\n"
-" init:\n"
-"\n"
-" compile:\n"
-"\n"
-" run.demo.unshared.node2:\n"
-" [java] ** node loaded: /a\n"
-" [java] ** node loaded: /a/a2\n"
-" ..."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:262
-#, no-c-format
-msgid ""
-"The <literal>run.demo.unshared.node2</literal> target runs node2, which will "
-"have its own store located at <literal>c:\\tmp\\node2</literal> (shown "
-"above). Whenever a change is made on either of the 2 nodes, it is replicated "
-"to the other node, and persisted in both local datastores. You can kill and "
-"restart a node, or even both nodes, and the data will still be available due "
-"to the persistent backend store(s)."
-msgstr ""
-
-#. Tag: title
-#: Tutorial.xml:267
-#, no-c-format
-msgid "Troubleshooting"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:268
-#, no-c-format
-msgid ""
-"Here are some tips for troubleshooting, if you encounter problems during "
-"this demo."
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:273
-#, no-c-format
-msgid ""
-"Most of the time, the problem will come from cache replication layer, i.e., "
-"JGroups package. On the output window, you can see the JGroups membership "
-"view. See if it is updated when you run the BSH commands. It should show a "
-"view with at least two members. For example, on my window, I see"
-msgstr ""
-
-#. Tag: programlisting
-#: Tutorial.xml:276
-#, no-c-format
-msgid ""
-"[java] ** view change: [BWANG-HOME:4381|1] [BWANG-HOME:4381, BWANG-HOME:4383]"
-msgstr ""
-
-#. Tag: para
-#: Tutorial.xml:277
-#, no-c-format
-msgid ""
-"with 2 members: 4381 and 4383. On the other hand, if you don't close the "
-"previous running cache instance, the membership view will also include the "
-"previous existing ones. This can corrupt the states. So you will have to "
-"make sure there is no running TreeCache processes before each demo. If you "
-"have problem with this, please consult the <ulink url=\"http://www.jgroups."
-"org/javagroupsnew/docs/index.html\">JGroups website </ulink>"
-msgstr ""
More information about the jbosscache-commits
mailing list