[jbosscache-commits] JBoss Cache SVN: r8224 - in enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ: de-DE and 5 other directories.

Author: xhuang(a)jboss.com Date: 2009-09-14 19:41:10 -0400 (Mon, 14 Sep 2009) New Revision: 8224 Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Author_Group.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Book_Info.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/CacheLoader_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Eviction_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/General_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/JBoss_Cache_Frequently_Asked_Questions.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Revision_History.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/TreeCache_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Troubleshooting.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Author_Group.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Book_Info.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/CacheLoader_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Eviction_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/General_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/JBoss_Cache_Frequently_Asked_Questions.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Revision_History.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/TreeCache_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Troubleshooting.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Author_Group.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Book_Info.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/CacheLoader_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Eviction_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/General_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/JBoss_Cache_Frequently_Asked_Questions.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Revision_History.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/TreeCache_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Troubleshooting.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Author_Group.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Book_Info.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/CacheLoader_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Eviction_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/General_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/JBoss_Cache_Frequently_Asked_Questions.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Revision_History.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/TreeCache_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Troubleshooting.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Author_Group.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Book_Info.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/CacheLoader_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Eviction_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/General_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/JBoss_Cache_Frequently_Asked_Questions.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Revision_History.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/TreeCache_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Troubleshooting.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Author_Group.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Book_Info.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/CacheLoader_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Eviction_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/General_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/JBoss_Cache_Frequently_Asked_Questions.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Revision_History.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/TreeCache_FAQ.po enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Troubleshooting.po Log: Generate PO based on v4.3 Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Author_Group.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Author_Group.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Author_Group.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,19 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-09-20 16:08+1000\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: firstname +#: Author_Group.xml:7 +#, no-c-format +msgid "Ben Wang, Bela Ban, Manik Surtani, Scott Marlow, Galder Zamarreño" +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Book_Info.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Book_Info.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Book_Info.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,38 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-09-20 16:08+1000\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Book_Info.xml:5 +#, fuzzy, no-c-format +msgid "JBoss Cache Frequently Asked Questions" +msgstr "Häufig gestellte Fragen (FAQs)" + +#. Tag: subtitle +#: Book_Info.xml:6 +#, no-c-format +msgid "for Use with JBoss Enterprise Application Platform 5.0" +msgstr "" + +#. Tag: para +#: Book_Info.xml:12 +#, no-c-format +msgid "" +"This book is a compilation of frequently asked questions about JBoss Cache" +msgstr "Dieses Buch ist eine Sammlung häufig gestellter Fragen zu JBoss Cache" + +#. Tag: holder +#: Book_Info.xml:24 +#, no-c-format +msgid "&HOLDER;" +msgstr "&HOLDER;" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/CacheLoader_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/CacheLoader_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/CacheLoader_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,369 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-09-20 16:08+1000\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: CacheLoader_FAQ.xml:6 +#, no-c-format +msgid "Cache Loaders" +msgstr "Cache Loader" + +#. Tag: para +#: CacheLoader_FAQ.xml:12 +#, fuzzy, no-c-format +msgid "What is a cache loader?" +msgstr "Was ist ein CacheLoader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:16 +#, fuzzy, no-c-format +msgid "" +"A cache loader is the connection of JBoss Cache to a (persistent) data " +"store. The cache loader is called by JBoss Cache to fetch data from a store " +"when that data is not in the cache, and when modifications are made to data " +"in the cache the Cache Loader is called to store those modifications back to " +"the store." +msgstr "" +"Ein CacheLoader ist die Verbindung von JBossCache mit einem (persistenten) " +"Datenspeicher. Der CacheLoader wird von JBossCache aufgerufen, um Daten von " +"einem Speicher abzurufen, wenn sich diese nicht im Cache befinden und wenn " +"Änderungen an den Daten im Cache vorgenommen werden, so wird der CacheLoader " +"aufgerufen, um diese Änderungen wieder im Speicher zu speichern." + +#. Tag: para +#: CacheLoader_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "" +"In conjunction with eviction policies, JBoss Cache with a cache loader " +"allows a user to maintain a bounded cache for a large backend datastore. " +"Frequently used data is fetched from the datastore into the cache, and the " +"least used data is evicted, in order to provide fast access to frequently " +"accessed data. This is all configured through XML, and the programmer " +"doesn't have to take care of loading and eviction." +msgstr "" +"In Verbindung mit den \"Eviction\"-Richtlinien gestattet JBossCache mit " +"einem CacheLoader es einem Benutzer ein Cache für einen großen Backend-" +"Datenspeicher zu warten. Häufig verwendete Daten werden vom Datenspeicher in " +"das Cache abgerufen und die am wenigsten verwendeten Daten ausgewiesen, um " +"schnellen Zugriff auf häufig verwendete Daten zu gewährleisten. Das alles " +"wird durch XML konfiguriert und der Programmierer muss sich nicht um das " +"Laden und Eviction zu kümmern." + +#. Tag: para +#: CacheLoader_FAQ.xml:32 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache currently ships with several cache loader implementations, " +"including:" +msgstr "" +"JBossCache wird derzeit mit mehreren CacheLoader-Implementierungen " +"geliefert, darunter:" + +#. Tag: para +#: CacheLoader_FAQ.xml:37 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.FileCacheLoader</literal> : this " +"implementation uses the file system to store and retrieve data. JBoss Cache " +"nodes are mapped to directories, subnodes to subdirectories etc. Attributes " +"of a node are mapped to a data file inside the directory." +msgstr "" +"FileCacheLoader: Diese Implementierung verwendet das Dateisystem zum " +"Spechern und Abrufen von Daten. JBossCache Nodes sind zu Verzeichnissen, Sub-" +"Nodes zu Unterverzeichnissen usw. gemappt. Attribute eines Node sind zu " +"einer Datei <literal>data</literal> innerhalb eines Verzeichnisses gemappt." + +#. Tag: para +#: CacheLoader_FAQ.xml:49 +#, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.jdbm.JdbmCacheLoader</literal> : this " +"implementation is based on<ulink url=\"http://jdbm.sourceforge.net/\"> JDBM</" +"ulink>, an open source file-based transactional persistence engine." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:58 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.bdbje.BdbjeCacheLoader</literal> : this " +"implementation is based on the Oracle's Berkeley DB Java Edition database, a " +"fast and efficient transactional database. It uses a single file for the " +"entire store. Note that if you use the Berkeley DB cache loader with JBoss " +"Cache and wish to ship your product, you will have to acquire a <ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">commercial license from Oracle</" +"ulink>." +msgstr "" +"BdbjeCacheLoader: Diese Implementierung basiert auf der Sleepycat Java " +"Edition Datenbank, einer schnellen und effizienten transaktionalen " +"Datenbank. Sie verwendet eine einzelne Datei für den gesamten Speicher." +"Beachten Sie, dass falls Sie Sleepycat's CacheLoader mit JBoss Cache " +"verwenden und Sie Ihr Produkt vertreiben möchten, Sie eine <ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">kommerzielle Lizenz von " +"Sleepycat </ulink> werden erwerben müssen." + +#. Tag: para +#: CacheLoader_FAQ.xml:71 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.JDBCCacheLoader</literal> : this " +"implementation uses the relational database as the persistent storage." +msgstr "" +"JDBCCacheLoader: Diese Implementierung verwendet die relationale Datenbank " +"als persistenten Speicher." + +#. Tag: para +#: CacheLoader_FAQ.xml:79 +#, fuzzy, no-c-format +msgid "" +"And more. See the chapter on cache loaders in the Users' Guide for more " +"details." +msgstr "Und mehr. Weitere Informationen entnehmen Sie btte der Dokumentation." + +#. Tag: para +#: CacheLoader_FAQ.xml:88 +#, no-c-format +msgid "Is the FileCacheLoader recommended for production use?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:92 +#, no-c-format +msgid "" +"No, it is not. The FileCacheLoader has some severe limitations which " +"restrict its use in a production environment, or if used in such an " +"environment, it should be used with due care and sufficient understanding of " +"these limitations." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:99 +#, no-c-format +msgid "" +"Due to the way the FileCacheLoader represents a tree structure on disk " +"(directories and files) traversal is inefficient for deep trees." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:103 +#, no-c-format +msgid "" +"Usage on shared filesystems like NFS, Windows shares, etc. should be avoided " +"as these do not implement proper file locking and can cause data corruption." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:107 +#, no-c-format +msgid "" +"Usage with an isolation level of NONE can cause corrupt writes as multiple " +"threads attempt to write to the same file." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:111 +#, no-c-format +msgid "" +"File systems are inherently not transactional, so when attempting to use " +"your cache in a transactional context, failures when writing to the file " +"(which happens during the commit phase) cannot be recovered." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:120 +#, no-c-format +msgid "" +"As a rule of thumb, it is recommended that the FileCacheLoader not be used " +"in a highly concurrent, transactional or stressful environment, and its use " +"is restricted to testing." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:130 +#, fuzzy, no-c-format +msgid "Can writing to cache loaders be asynchronous?" +msgstr "Kann der Schreibvorgang in CacheLoaders asynchron sein?" + +#. Tag: para +#: CacheLoader_FAQ.xml:134 +#, fuzzy, no-c-format +msgid "" +"Yes. Set the <literal>async</literal> attrobute to true. See the JBoss Cache " +"Users' Guide for a more detailed discussion. By default though, all cache " +"loader writes are synchronous and will block." +msgstr "" +"Seit JBossCache 1.2.4, ja. Setzen Sie die CacheLoaderAsynchronous-Property " +"auf \"true\". Eine ausführliche Erläuterung finden Sie in der JBossCache-" +"Dokumentation. Standardmäßig finden alle Schreibvorgänge im Cache-Lader " +"synchron statt und blocken." + +#. Tag: para +#: CacheLoader_FAQ.xml:145 +#, fuzzy, no-c-format +msgid "Can I write my own cache loader ?" +msgstr "Kann ich meinen eigenen CacheLoader schreiben?" + +#. Tag: para +#: CacheLoader_FAQ.xml:149 +#, fuzzy, no-c-format +msgid "" +"Yes. A cache loader is a class implementing <literal>org.jboss.cache.loader." +"CacheLoader</literal> or extending <literal>org.jboss.cache.loader." +"AbstractCacheLoader</literal> . It is configured via the XML file (see JBoss " +"Cache Users' Guide)." +msgstr "" +"Ja. Bei einem CacheLoader handelt es sich um eine <literal>org.jboss.cache." +"loader.CacheLoader</literal> implementierende Klasse. Sie wird via der XML-" +"Datei implementiert (siehe JBossCache und Tutorial Dokumentation)." + +#. Tag: para +#: CacheLoader_FAQ.xml:161 +#, fuzzy, no-c-format +msgid "Does a cache loader have to use a persistent store ?" +msgstr "Muss ein CacheLoader einen persistenten Speicher verwenden?" + +#. Tag: para +#: CacheLoader_FAQ.xml:165 +#, fuzzy, no-c-format +msgid "" +"No, a cache loader could for example fetch (and possibly store) its data " +"from a webdav-capable webserver. Another example is a caching proxy server, " +"which fetches contents from the web. Note that an implementation of " +"CacheLoader may not implement the 'store' functionality in this case, but " +"just the 'load' functionality." +msgstr "" +"Nein. Ein CacheLoader könnte zum Beispiel seine Daten (und möglicherweise " +"Speicher) von einem webdav-fähigen Webserver abrufen. Ein weiteres Beispiel " +"ist ein Caching Proxy Server, der Inhalte aus dem Web abruft. Beachten Sie, " +"dass eine Implementierung von CacheLoader in diesem Falle möglicherweise " +"nicht die 'Speicher'-Funktionalität implementiert, sondern lediglich die " +"'Lade'-Funktionalität." + +#. Tag: para +#: CacheLoader_FAQ.xml:177 +#, fuzzy, no-c-format +msgid "Do I have to pay to use Oracle's Berkeley DB CacheLoader?" +msgstr "Muss ich Sleepycats CacheLoader benutzen?" + +#. Tag: para +#: CacheLoader_FAQ.xml:181 +#, fuzzy, no-c-format +msgid "" +"Not if you use it only for personal use. As soon as you distribute your " +"product with BdbjeCacheLoader, you have to purchase a commercial license " +"from Oracle. See details at <ulink url=\"http://www.sleepycat.com/" +"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ." +msgstr "" +"Nicht, wenn Sie dies nur für Ihren persönlichen Gebrauch nutzen. Sobald Sie " +"Ihr Produkt aber mit BdbjeCacheLoader distribuieren, müssen Sie eine " +"kommerzielle Lizenz von Sleepycat erwerben. Einzelheiten finden Sie unter " +"<ulink url=\"http://www.sleepycat.com/jeforjbosscache\">http://www.... +"com/jeforjbosscache </ulink> ." + +#. Tag: para +#: CacheLoader_FAQ.xml:194 +#, no-c-format +msgid "Are there any tools available to monitor the Berkeley DB instance?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:198 +#, no-c-format +msgid "" +"Yes. Oracle ships a JMX-based monitoring tool, called <ulink url=\"http://" +"www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/" +"jmx/JEMonitor.html\"> JEMonitor </ulink> which can be downloaded from the " +"Oracle website." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:211 +#, no-c-format +msgid "" +"When tuning my Berkeley DB instance, where should I put my je.properties " +"file?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:215 +#, no-c-format +msgid "" +"<literal>je.properties</literal> should reside in your Berkeley DB home " +"directory. This is the directory you pass in to the BDBJECacheLoader's " +"<literal>location</literal> configuration property." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:227 +#, no-c-format +msgid "Can I use more than one cache loader?" +msgstr "Kann ich mehr als einen Cache-Lader verwenden?" + +#. Tag: para +#: CacheLoader_FAQ.xml:231 +#, fuzzy, no-c-format +msgid "" +"Yes. Within the CacheLoaderConfiguration XML element (see Users' Guide " +"chapter on cache loaders) you can describe several cache loaders. The impact " +"is that the cache will look at all of the cache loaders in the order they've " +"been configured, until it finds a valid, non-null element of data. When " +"performing writes, all cache loaders are written to (except if the " +"ignoreModifications element has been set to true for a specific cache loader." +msgstr "" +"Seit JBossCache 1.3.0, ja. Mit dem neuen CacheLoaderConfiguration XML-" +"Element (siehe Benutzerhandbuch-Abschnitt zu Cache-Ladern) können Sie jetzt " +"mehrere Cache-Lader beschreiben. Die Folge ist, dass das Cache sämtliche " +"Cache-Lader in der Reihenfolge, in der diese konfiguriert wurden, " +"berücksichtigt, bis es ein gültiges, nicht-Null Datenelement findet. Bei der " +"Durchführung von Schreibvorgängen wird in alle Cache-Lader geschrieben " +"(außer wenn das ignoreModifications-Element für einen bestimmten Cache-Lader " +"auf \"true\" gesetzt wurde)." + +#. Tag: para +#: CacheLoader_FAQ.xml:245 +#, no-c-format +msgid "" +"Can I migrate a JDBCacheLoader or FileCacheLoader based cache store " +"containing data formatted with JBoss Cache 1.x.x to JBoss Cache 2.0 format?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:250 +#, no-c-format +msgid "" +"Yes. See \"Transforming Cache Loaders\" section within the \"Cache Loaders\" " +"section located in the JBoss Cache Users' Guide." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:257 +#, no-c-format +msgid "Is the TCPDelegatingCacheLoader resilient to TCPCacheServer restarts?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:263 +#, no-c-format +msgid "" +"As of JBoss Cache 2.1.0, the answer is yes. See the Users' Guide for details " +"on how to configure and tune your retries and wait period for reestablishing " +"the TCP connection." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:269 +#, no-c-format +msgid "" +"Prior to that, restarting the TCPCacheServer would also mean restarting your " +"application that uses the cache." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Eviction_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Eviction_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Eviction_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,171 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-09-20 16:08+1000\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Eviction_FAQ.xml:6 +#, no-c-format +msgid "Eviction Policies" +msgstr "\"Eviction\"-Richtlinien" + +#. Tag: para +#: Eviction_FAQ.xml:10 +#, no-c-format +msgid "Does JBoss Cache support eviction policies?" +msgstr "Unterstützt JBoss Cache \"Eviction\"-Richtlinien?" + +#. Tag: para +#: Eviction_FAQ.xml:14 +#, no-c-format +msgid "" +"Yes. JBoss Cache currently supports multiple eviction policies such as LRU, " +"MRU, and FIFO. Users can also plug in their own eviction policy algorithms. " +"See user guide for details." +msgstr "" + +#. Tag: para +#: Eviction_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "Does JBoss Cache's eviction policy operates in replication mode?" +msgstr "" +"Operiert JBoss Caches implementierte LRU “Eviction”-Richtlinie im " +"Replikationsmodus?" + +#. Tag: para +#: Eviction_FAQ.xml:29 +#, no-c-format +msgid "Yes and no. :-)" +msgstr "Ja und nein. :-)" + +#. Tag: para +#: Eviction_FAQ.xml:31 +#, fuzzy, no-c-format +msgid "" +"The eviction policy only operates in local mode. That is, nodes are only " +"evicted locally. This may cause the cache contents not to be synchronized " +"temporarily. But when a user tries to obtain the cached contents of an " +"evicted node and finds out that is null (e.g., <literal>get</literal> " +"returns null), it should get it from the other data source and re-populate " +"the data in the cache. During this moment, the node content will be " +"propagated and the cache content will be in sync." +msgstr "" +"Die LRU-Richtlinie läuft nur in lokalem Modus. Das heißt, eine Eviction der " +"Nodes findet nur lokal statt. Dies kann dazu führen, dass Cache-Inhalte " +"temporär nicht synchronisiert werden. Versucht ein Benutzer aber, die " +"gecachten Inhalte eines Nodes abzurufen, bei dem eine Eviction durchgeführt " +"wurde und findet dieser heraus, dass dies Null ist (z.B. liefert " +"<literal>get</literal> Null), sollten diese von der anderen Datenquelle " +"abgerufen und das Cache erneut mit den Daten aufgefüllt werden. In diesem " +"Moment werden die Node-Inhalte weitergegeben und die Cache-Inhalte sind in " +"sync." + +#. Tag: para +#: Eviction_FAQ.xml:42 +#, no-c-format +msgid "" +"However, you still can run eviction policies with cache mode set to either " +"<literal>REPL_SYNC</literal> or <literal>REPL_ASYNC</literal> . Depending on " +"your use case, you can set multiple cache instances to have their own " +"eviction policy (which are applied locally) or just have selected instances " +"with eviction policies activated." +msgstr "" +"Sie können jedoch \"Eviction\"-Richtlinien nach wie vor mit auf " +"<literal>REPL_SYNC</literal> oder <literal>REPL_ASYNC</literal> " +"eingestelltem Cache-Modus ausführen. Je nach Ihrem Anwendungsfall können Sie " +"mehrere Cache-Instanzen mit jeweils eigener \"Eviction\"-Richtlinie (die " +"lokal angewendet werden) oder nur ausgewählte Instanzen mit aktivierten " +"\"Eviction\"-Richtlinien besitzen." + +#. Tag: para +#: Eviction_FAQ.xml:53 +#, no-c-format +msgid "" +"Also note that, with cache loader option, a locally evicted node can also be " +"persisted to the backend store and a user can retrieve it from the store " +"later on." +msgstr "" +"Beachten Sie auch, dass mit der Cache-Loader-Option ein lokal ausgewiesener " +"Node (d.h. Bei dem eine Eviction stattgefunden hat) auch zum Backend-" +"Speicher hin persistiert werden kann und dass ein Benutzer diesen später aus " +"dem Speicher abrufen kann." + +#. Tag: para +#: Eviction_FAQ.xml:62 +#, no-c-format +msgid "Does JBoss Cache support <literal>Region</literal> ?" +msgstr "Unterstützt JBoss Cache <literal>Region</literal> ?" + +#. Tag: para +#: Eviction_FAQ.xml:69 +#, no-c-format +msgid "" +"Yes. JBoss Cache has the notion of region where a user can configure the " +"eviction policy parameters (e.g., <literal>maxNodes</literal> or " +"<literal>timeToIdleSeconds</literal> )" +msgstr "" +"Ja. JBoss Cache kennt den Begriff der \"Region\" wo ein Benutzer die " +"Parameter der Eviction-Richtlinien konfigurieren kann (z.B. " +"<literal>maxNodes</literal> oder <literal>timeToIdleSeconds</literal> )" + +#. Tag: para +#: Eviction_FAQ.xml:77 +#, fuzzy, no-c-format +msgid "" +"A region in JBoss Cache denotes a portion of tree hierarchy, e.g., a fully " +"qualified name ( <literal>org.jboss.cache.Fqn</literal> ). For example, a " +"user can define <literal>/org/jboss</literal> and <literal>/org/foocom</" +"literal> as two separate regions. But note that you can configure the region " +"programmatically now, i.e., everything has to be configured through the xml " +"file." +msgstr "" +"Eine Region bei JBoss Cache denotiert einen Teil der Baumhierarchie z.B. " +"einen vollständig angegebenen Namen ( <literal>FQN</literal> ). Fzum " +"Beispiel kann ein Benutzer <literal>/org/jboss</literal> und <literal>/org/" +"foocom</literal> als zwei separate Regionen definieren. Beachten Sie aber, " +"dass Sie die Region jetzt programmatisch definieren können, d.h. Alles muss " +"über die xml-Datei konfiguriert werden." + +#. Tag: para +#: Eviction_FAQ.xml:94 +#, no-c-format +msgid "" +"I have turned on the eviction policy, why do I still get \"out of memory" +"\" (OOM) exception?" +msgstr "" +"Ich habe die \"Eviction\"-Richtlinie eingeschaltet, warum erhalte ich nach " +"wie vor eine \"out of memory\" (OOM) Ausnahme?" + +#. Tag: para +#: Eviction_FAQ.xml:100 +#, fuzzy, no-c-format +msgid "" +"OOM can happen when the speed of cache access exceeds the speed of eviction " +"policy handling timer. Eviction policy handler will wake up every " +"<literal>wakeUpInterval</literal> milliseconds (or " +"<literal>wakeUpIntervalSeconds</literal> seconds, prior to 3.x) to process " +"the eviction event queue. So when the queue size is full, it will create a " +"backlog and cause out-of-memory exceptions to happen unless the eviction " +"timer catches up. To address this problem, in addition to increase the VM " +"heap size, you can also reduce the <literal>wakeUpInterval</literal> so the " +"timer thread processes the queue more frequently." +msgstr "" +"OOM kann vorkommen, wenn die Geschwindigkeit des Cache-Zugriffs die " +"Geschwindigkeit des Timers, der die Eviction-Richtlinien handhabt, " +"überschreitet. Der Handhaber der Eviction-Richtlinien erwacht alle " +"<literal>wakeUpIntervalInSeconds</literal> Sekunden, um die “Eviction”-" +"Ereigniswarteschlange zu bearbeiten. Und die Größe der Warteschlange ist " +"jetzt bei 20000 festgelegt. Wenn also die Größe der Warteschlange voll ist, " +"wird ein Backlog erstellt und OOM findet statt, falls der Eviction-Timer " +"nicht aufholt. Um dieses Problem anzugehen können Sie – neben Erhöhung des " +"VM-Heap-Size – auch den <literal>wakeUpIntervaleInSeconds</literal> " +"reduzieren, damit der Timer-Thread die Warteschlange häufiger bearbeitet." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/General_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/General_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/General_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,167 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-09-20 16:08+1000\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: General_FAQ.xml:6 +#, no-c-format +msgid "General Information" +msgstr "Allgemeines Informationen" + +#. Tag: para +#: General_FAQ.xml:10 +#, no-c-format +msgid "What is JBoss Cache?" +msgstr "Was ist JBoss Cache?" + +#. Tag: para +#: General_FAQ.xml:14 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache is a replicated and transactional cache. It is replicated since " +"multiple JBoss Cache instances can be distributed (either within the same " +"JVM or across several JVMs whether they reside on the same machine or on " +"different machines on a network) and data is replicated across the whole " +"group. It is transactional because a user can configure a <ulink url=" +"\"http://java.sun.com/products/jta/\">JTA</ulink> compliant transaction " +"manager and make any cache interaction transactional, and caches would " +"participate in ongoing JTA transactions. Note that the cache can also be run " +"without any replication; this is the local mode." +msgstr "" +"Bei JBoss Cache handelt es sich um ein repliziertes und transaktionales " +"Cache. Es ist repliziert, da mehrere JBoss Cache Instanzen repliziert werden " +"können (entweder innerhalb derselben JVM oder über mehrere JVMs hinweg, ob " +"sich diese nun auf derselben Maschine oder aber verschiedenen Maschinen in " +"einem Netzwerk befinden) und Daten werden über die gesamte Gruppe hinweg " +"repliziert. Es ist transaktional, weil ein Benutzer einen JTA-fähigen " +"Transaktions-Manager konfigurieren und die Cache Operation somit " +"transaktional machen kann. Beachten Sie, dass das Cache auch ohne jegliche " +"Replikation laufen kann; dies ist dann der lokale Modus." + +#. Tag: para +#: General_FAQ.xml:28 +#, no-c-format +msgid "" +"JBoss Cache comes in two flavours: Core and POJO versions. The core library " +"(using the <literal>org.jboss.cache.Cache</literal> interface) is the " +"underlying library that organises data in a tree-like structure and handles " +"all locking, passivation, eviction and replication characteristics of data " +"in the cache. The POJO library (using the <literal>org.jboss.cache.pojo." +"PojoCache</literal> interface) is built atop the core library and allows " +"introspection of objects in the cache providing transparent coherence by " +"using JBoss AOP. Note that the POJO edition of JBoss Cache (often referred " +"to as POJO Cache) comes with a separate set of documentation (Users' Guide, " +"FAQ, etc.) available on the JBoss Cache <ulink url=\"http://www.jboss.org/" +"jbosscache/\">documentation website</ulink>." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:66 +#, no-c-format +msgid "Who are the JBoss Cache developers?" +msgstr "Wer sind die Entwickler von JBoss Cache?" + +#. Tag: para +#: General_FAQ.xml:70 +#, no-c-format +msgid "" +"JBoss Cache has an active community of developers and contributors. The " +"project was founded by Bela Ban and is currently led by Manik Surtani. Jason " +"Greene is the lead for the POJO Cache subsystem, and other contributors both " +"past and present include Ben Wang, Harald Gliebe, Brian Stansberry, Vladimir " +"Blagojevic, Mircea Markus, Jimmy Wilson, Galder Zamarreño and Elias Ross." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:139 +#, no-c-format +msgid "How do I know the version of JBoss Cache that I am using?" +msgstr "Woher weiß ich, welche Version von JBoss Cache ich benutze?" + +#. Tag: para +#: General_FAQ.xml:143 +#, no-c-format +msgid "" +"<literal>java -jar jbosscache-core.jar</literal> will spit out version " +"details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:152 +#, fuzzy, no-c-format +msgid "" +"Can I run JBoss Cache outside of the JBoss Enterprise Application Platform?" +msgstr "" +"Kann ich JBoss Cache außerhalb des JBoss Application Server laufen lassen?" + +#. Tag: para +#: General_FAQ.xml:157 +#, no-c-format +msgid "" +"Absolutely! Even though JBoss Cache comes integrated with the JBoss " +"Enterprise Application Platform, it can also be used in any other Java EE " +"server such as BEA WebLogic, IBM Websphere or Tomcat. It can also run in a " +"standalone Java process, completely outside of an application server. See " +"the Users' Guide for more details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:170 +#, no-c-format +msgid "" +"How can I migrate my application and configuration from using JBoss Cache 1." +"x to 2.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:173 +#, no-c-format +msgid "" +"Look at <ulink url=\"http://www.jboss.org/community/docs/DOC-10246\">this " +"wiki page</ulink> for help." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:182 +#, no-c-format +msgid "What about from 2.x to 3.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:185 +#, no-c-format +msgid "" +"JBoss Cache 3.x is API compatible with 2.x, although as far as possible you " +"should refactor your code not to use deprecated methods as these may " +"disappear in future releases of JBoss Cache." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:190 +#, no-c-format +msgid "" +"JBoss Cache 3.x comes with an all new configuration format. Old 2.x " +"configuration files will still work, although you will get a warning in the " +"logs about this. Again, as far as possible, we recommend migrating your " +"configuration file to the new format. Scripts are provided with the JBoss " +"Cache 3.x distribution to migrate configuration files (see " +"<literal>config2to3.sh</literal> and<literal>config2to3.bat</literal>)." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:201 +#, no-c-format +msgid "" +"Note that to take advantage of some of the new features in JBoss Cache 3.x, " +"you need to be using the new configuration format." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/JBoss_Cache_Frequently_Asked_Questions.po =================================================================== Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Revision_History.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Revision_History.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Revision_History.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,25 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-09-20 16:08+1000\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Revision_History.xml:6 +#, no-c-format +msgid "Revision History" +msgstr "" + +#. Tag: author +#: Revision_History.xml:12 +#, fuzzy, no-c-format +msgid "<firstname></firstname> <surname></surname> <email></email>" +msgstr "<firstname>Jasna</firstname> <surname>Dimanoski</surname>" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/TreeCache_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/TreeCache_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/TreeCache_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,1086 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-09-20 16:08+1000\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: TreeCache_FAQ.xml:6 +#, fuzzy, no-c-format +msgid "JBoss Cache: Core" +msgstr "JBoss Cache 1.4.1" + +#. Tag: para +#: TreeCache_FAQ.xml:26 +#, no-c-format +msgid "Can I run multiple JBoss Cache instances on the same VM?" +msgstr "Kann ich mehrere JBoss Cache Instanzen auf derselben VM laufen lassen?" + +#. Tag: para +#: TreeCache_FAQ.xml:30 +#, no-c-format +msgid "" +"Yes. There are some scenarios where you may want to run multiple instances " +"of JBoss Cache. For example, you want to run multiple local cache instances " +"with each instance having its own configuration (e.g., different cache " +"policy). In this case, you will need multiple xml configuration files." +msgstr "" +"Ja. Es gibt einige Szenarien, bei denen Sie vielleicht mehrere Instanzen von " +"JBoss Cache ausführen möchten. Wenn Sie zum Beispiel mehrere lokal Cache " +"Instanzen ausführen möchten, und jede Instanz ihre eigene Konfiguration " +"besitzen soll (z.B. verschiedene Cache Richtlinien). In diesem Fall werden " +"Sie mehrere xml-Konfigurationsdateien benötigen." + +#. Tag: para +#: TreeCache_FAQ.xml:41 +#, fuzzy, no-c-format +msgid "Can JBoss Cache run as a second level cache inside Hibernate?" +msgstr "" +"Kann TreeCache als Cache der zweiten Ebene innerhalb von Hibernate laufen?" + +#. Tag: para +#: TreeCache_FAQ.xml:47 +#, fuzzy, no-c-format +msgid "" +"Yes. Since Hibernate 3.0 release, you can configure it to use JBoss Cache as " +"a second level cache. For details, see Hibernate documentation, and also see " +"<ulink url=\"http://www.jboss.org/community/docs/DOC-10265\">this wiki page</" +"ulink>." +msgstr "" +"Ja. Seit der Release von Hibernate 3.0 können Sie es zur Verwendung von " +"JBoss Cache (genauer TreeCache) als Cache der zweiten Ebene konfigurieren. " +"Einzelheiten finden Sie in der Hibernate Dokumentation sowie <ulink url=" +"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate\"> http://" +"wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate </ulink>" + +#. Tag: para +#: TreeCache_FAQ.xml:52 +#, no-c-format +msgid "" +"JBoss Cache 3.x with MVCC in particular works very well as a Hibernate " +"second level cache." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:60 +#, fuzzy, no-c-format +msgid "What about using POJO Cache as a Hibernate cache?" +msgstr "Kann PojoCache als ein Hibernate Cache verwendet werden?" + +#. Tag: para +#: TreeCache_FAQ.xml:64 +#, fuzzy, no-c-format +msgid "" +"It is not necessary to use POJO Cache for second level cache inside " +"Hibernate because Hibernate manages fine-grained fields in Java objects. " +"Using POJO Cache won't provide any advantage, and will be an unnecessary " +"performance drawback." +msgstr "" +"Es ist nicht nötig PojoCache für das Cache der zweiten ebene innerhalb " +"Hibernate zu verwenden, da Hibernate feinkörnige Felder in Java Objekten " +"managt. Die Verwendung von PojoCache bietet keinerlei Vorteile." + +#. Tag: para +#: TreeCache_FAQ.xml:74 +#, no-c-format +msgid "How can I configure JBoss Cache?" +msgstr "Wie kann ich JBoss Cache konfigurieren?" + +#. Tag: para +#: TreeCache_FAQ.xml:78 +#, no-c-format +msgid "" +"You can configure the JBoss Cache through a configuration xml file or " +"programmatically using a <literal>org.jboss.cache.config.Configuration</" +"literal> object, passed in to the <literal>org.jboss.cache.CacheFactory</" +"literal> instance." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:90 +#, no-c-format +msgid "" +"Can I use a schema or DTD to validate my JBoss Cache configuration file?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:95 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, yes. An XSD schema is provided in your jbosscache-" +"core.jar file, and is also available online, on<ulink url=\"http://www.jboss." +"org/jbosscache/jbosscache-config-3.0.xsd\"> http://www.jboss.org/jbosscache/" +"jbosscache-config-3.0.xsd</ulink>. You can configure your IDE, text editor " +"or XML authoring tool to use this schema to validate your file." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:108 +#, no-c-format +msgid "What is the difference between the different cache modes?" +msgstr "Was ist der Unterschied zwischen den verschiedenen Cache-Modi?" + +#. Tag: para +#: TreeCache_FAQ.xml:113 +#, no-c-format +msgid "" +"JBossCache has five different cache modes, i.e., <literal>LOCAL</literal> , " +"<literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> and <literal>INVALIDATION_ASYNC</" +"literal> . If you want to run JBoss Cache as a single instance, then you " +"should set the cache mode to <literal>LOCAL</literal> so that it won't " +"attempt to replicate anything. If you want to have synchronous replication " +"among different JBoss Cache instances, you set it to <literal>REPL_SYNC</" +"literal> . For asynchronous replication, use <literal>AYSNC_REPL</literal> . " +"If you do not wish to replicate cached data but simply inform other caches " +"in a cluster that data under specific addresses are now stale and should be " +"evicted from memory, use <literal>INVALIDATION_SYNC</literal> or " +"<literal>INVALIDTAION_ASYNC</literal> . Synchronous and asynchronous " +"behavior applies to invalidation as well as replication." +msgstr "" +"JBossCache besitzt fünf verschiedene Cache-Modi, d.h. <literal>LOCAL</" +"literal> , <literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> und <literal>INVALIDATION_ASYNC</" +"literal> . Falls Sie JBoss Cache als eine einzelne Instanz ausführen " +"möchten, so sollten Sie den Cache-Modus auf <literal>LOCAL</literal> setzen, " +"damit nicht der Versuch unternommen wird, etwas zu replizieren. Falls Sie " +"synchrone Replikation zwischen JBoss Cache Instanzen wünschen, setzen Sie es " +"auf <literal>REPL_SYNC</literal>. Für asynchrone Replikation verwenden Sie " +"<literal>AYSNC_REPL</literal>. Falls Sie gecachte Daten nicht replizieren " +"wollen, sondern lediglich andere Caches innerhalb eines Clusters darüber " +"informieren wollen, dass Daten unter bestimmten Adressen jetzt veraltet sind " +"und aus dem Speicher entfernt werden sollten, verwenden Sie " +"<literal>INVALIDATION_SYNC</literal> oder <literal>INVALIDTAION_ASYNC</" +"literal>. Synchrones und asynchrones Verhalten gilt für Invalidierung ebenso " +"wie für Replikation." + +#. Tag: para +#: TreeCache_FAQ.xml:143 +#, no-c-format +msgid "" +"Note that <literal>ASYNC_REPL</literal> and <literal>INVALIDATION_ASYNC</" +"literal> are non-blocking. This can be useful when you want to have another " +"JBoss Cache serving as a mirror or backup and you don't want to wait for " +"confirmation that this mirror has received your messages." +msgstr "" +"Beachten Sie, dass <literal>ASYNC_REPL</literal> und " +"<literal>INVALIDATION_ASYNC</literal> nicht blockend sind. Dies kann von " +"Nutzen sein, wenn ein anderes JBoss Cache als Mirror oder Backup dienen soll " +"und Sie nicht Sie nicht auf Bestätigung warten wollen, dass dieser Mirror " +"Ihre Nachrichten erhalten hat." + +#. Tag: para +#: TreeCache_FAQ.xml:157 +#, no-c-format +msgid "How does JBoss Cache's replication mechanism work?" +msgstr "Wie funktioniert der Replikationsmechanismus von JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:161 +#, no-c-format +msgid "" +"JBoss Cache leverages <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"for network communications. A JGroups configuration section is present in " +"your JBoss Cache configuration." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:166 +#, fuzzy, no-c-format +msgid "" +"A user can configure the cluster of JBoss Cache instances by sharing the " +"same cluster name ( <literal>cluster name</literal> ). There is also an " +"option of whether to populate the cache data upon starting a new instance in " +"the <literal>ClusterConfig</literal> attribute." +msgstr "" +"JBoss Cache nutzt <ulink url=\"http://www.jgroups.org\">JGroups</ulink> als " +"eine Replikationsebene ein. Ein Benutzer kann den Cluster von JBoss Cache " +"Instanzen durch Freigabe desselben Cluster-Namens konfigurieren " +"( <literal>cluster name</literal> ). Es gibt außerdem die Option des " +"Auffüllens von Cache Daten beim Starten einer neuen Instanz im " +"<literal>ClusterConfig</literal>-Attribut." + +#. Tag: para +#: TreeCache_FAQ.xml:178 +#, fuzzy, no-c-format +msgid "" +"Note that once all instances join the same replication group, every " +"replication change is propagated to all participating members. There is no " +"mechanism for sub-partitioning where some replication can be done within " +"only a subset of members, unless you use the Buddy Replication features. See " +"the Users' Guide for more details on this." +msgstr "" +"Beachten Sie, dass - nachdem sich alle Instanzen derselben " +"Replikationsgruppe angeschlossen haben - jede Replikationsänderung an alle " +"teilnehmenden Mitglieder fortgepflanzt werden muss. Es existiert kein " +"Mechanismus zur Unterpartitionierung, wo einiges an Replikation innerhalb " +"lediglich eines Untersatzes an Mitgliedern vorgenommen werden kann. Wir " +"arbeiten jedoch daran." + +#. Tag: para +#: TreeCache_FAQ.xml:190 +#, no-c-format +msgid "" +"I run a 2 node cluster. If the network dies, do the caches continue to run?" +msgstr "" +"Ich betreibe ein 2-Node Cluster. Wenn das Netzwerk den Betrieb einstellt, " +"laufen die Caches dennoch weiter?" + +#. Tag: para +#: TreeCache_FAQ.xml:194 +#, no-c-format +msgid "" +"Yes, both will continue to run, but depending on your replication mode, all " +"transactions or operations may not complete. If <literal>REPL_SYNC</literal> " +"is used, operations will fail while if <literal>REPL_ASYNC</literal> is used " +"they will succeed. Even if they succeed though, caches will be out of sync." +msgstr "" +"Ja, beide laufen weiter, aer je nach Ihrem Replikationsmodus sind " +"möglicherweise nicht alle Transaktionen oder Operationen vollständig. Wird " +"<literal>REPL_SYNC</literal> verwendet, schlagen Operationen fehl, während " +"sie bei der Verwendung von <literal>REPL_ASYNC</literal> erfolgreich " +"verlaufen. Selbst wenn diese erfolgreich verlaufen, so sind die Caches nicht " +"in sync." + +#. Tag: para +#: TreeCache_FAQ.xml:207 +#, no-c-format +msgid "" +"Can I plug in library X instead of JGroups to handle remote calls and group " +"communications?" +msgstr "" +"Kann ich Bibliothek X statt JGroups einbnden, um Remote Aufrufe und " +"Gruppenkommunikation zu handhaben?" + +#. Tag: para +#: TreeCache_FAQ.xml:212 +#, fuzzy, no-c-format +msgid "" +"At this stage the answer is no. We do have an abstraction layer between the " +"communication suite and JBoss Cache in the pipelines, and this may appear as " +"a feature at some stage in the future." +msgstr "" +"Zum momentanen Zeitpunkt (JBoss Cache 1.x) lautet die Antwort Nein. Wir " +"haben aber eine Abstraktionsebene zwischen der Kommunikations-Suite und " +"JBoss Cache in der Pipeline, und es ist möglich, dass des zu einem späteren " +"Zetpunkt noch als Feature erscheint." + +#. Tag: para +#: TreeCache_FAQ.xml:223 +#, no-c-format +msgid "" +"Does the cache need to replicate to every other instance in the cluster? " +"Isn't this slow if the cluster is large?" +msgstr "" +"Muss das Cache zu jeder anderen Instanz im Cluster replizieren? Ist das " +"nicht langsam, wenn das Cluster groß ist?" + +#. Tag: para +#: TreeCache_FAQ.xml:230 +#, fuzzy, no-c-format +msgid "" +"Replication need not occur to every node in the cluster. This feature - " +"called Buddy Replication - allows each node to pick one or more 'buddies' in " +"the cluster and only replicate to its buddies. This allows a cluster to " +"scale very easily with no extra impact on memory or network traffic with " +"each node added." +msgstr "" +"Seit JBoss Cache 1.4.0 muss Replikation nicht an jedem Node im Cluster " +"stattfinden. Dieses Feature - genannt \"Buddy Replication\" - gestattet es " +"jedem Node, einen oder mehrere 'Buddies' im Cluster auszuwählen und nur zu " +"diesen hin zu replizieren. Dies gestattet es einem Cluster ganz einfach zu " +"skalieren ohne, dass der Speicher oder Netzwerkverkehr mit jedem " +"hinzugefügten Node beeinflusst würden." + +#. Tag: para +#: TreeCache_FAQ.xml:237 +#, fuzzy, no-c-format +msgid "" +"See the Users' Guide for more information on Buddy Replication, and how it " +"can be used to achieve very high scalability." +msgstr "" +"Im Benutzerhandbuch finden Sie weitere Informationen zu Buddy Replikation " +"und wie es zur Erreichung hoher Skalierbarkeit eingesetzt werden kann." + +#. Tag: para +#: TreeCache_FAQ.xml:248 +#, no-c-format +msgid "" +"I'm using Buddy Replication. Do I need to have some form of session affinity?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:251 +#, no-c-format +msgid "" +"Session affinity relates to returning to the same cache instance for the " +"same data being used. While this is strictly not a requirement for Buddy " +"Replication, it is greatly recommended to minimize moving state around a " +"cluster." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:261 +#, fuzzy, no-c-format +msgid "" +"If I have the need for different configuration properties (e.g., " +"<literal>CacheMode</literal> and <literal>IsolationLevel</literal> ), do I " +"simply need to create multiple <literal>org.jboss.cache.Cache</literal> " +"instances with the appropriate configuration?" +msgstr "" +"Falls Bedarf für verschiedene TreeCache Properties existiert (z.B. " +"<literal>CacheMode</literal> und <literal>IsolationLevel</literal> ), muss " +"ich dann einfach multiple TreeCache Instanzen mit der entsprechenden " +"Konfiguration erstellen?" + +#. Tag: para +#: TreeCache_FAQ.xml:272 +#, fuzzy, no-c-format +msgid "" +"Yes. All the above mentioned properties are per cache instance. Therefore " +"you will need separate <literal>org.jboss.cache.Cache</literal> instances." +msgstr "" +"Ja. Alle oben genannten Properties sind pro Cache-Instanz. Sie benötigen " +"daher eine separate JBoss Cache-Instanz." + +#. Tag: para +#: TreeCache_FAQ.xml:282 +#, no-c-format +msgid "" +"Isn't this expensive from a networking standpoint, i.e., needing to create " +"sockets for each <literal>org.jboss.cache.Cache</literal> instance?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:289 +#, no-c-format +msgid "" +"Yes, it can be. For such cases it is recommended that you configure your " +"cache using the JGroups Multiplexer, which allows several caches to share a " +"single JGroups channel. Please see the Users' Guide for details on how to " +"configure the JGroups Multiplexer." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:296 +#, no-c-format +msgid "" +"A faster and more efficient approach is to use a shared transport in " +"JGroups. Please see <ulink url=\"http://www.jgroups.org\">the JGroups " +"documentation</ulink> for more details on how to do this." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:307 +#, fuzzy, no-c-format +msgid "" +"Does the <literal>ClusterName</literal> configuration element have any " +"relation to the JBoss AS cluster <literal>PartitionName</literal> ?" +msgstr "" +"Besitzt die Tree Cache Konfig <literal>ClusterName</literal> eine Beziehung " +"zum JBoss AS Cluster <literal>PartitionName</literal> ?" + +#. Tag: para +#: TreeCache_FAQ.xml:317 +#, no-c-format +msgid "" +"Yes. They are both JGroups group names. Besides the notion of a channel in " +"JGroups, it also can partition the channel into different group names." +msgstr "" +"Ja. Bei beiden handelt es sich um JGroups Gruppennamen. Neben des Begriffs " +"eines Channels in JGroups, kann dies auch den Channel in verschiedene " +"Gruppennamen partitionieren." + +#. Tag: para +#: TreeCache_FAQ.xml:326 +#, fuzzy, no-c-format +msgid "" +"When using multiple JGroups based components [cluster-service.xml, cache " +"(multiple instances)], what is the correct/valid way to configure those " +"components to make sure my multicast addresses don't conflict?" +msgstr "" +"Bei der Verwendung mehrerer JGroups basierter Komponenten [cluster-service." +"xml, treecache (multiple instances)], welches ist die korrekte/gültige Weise " +"diese Komponenten zu konfigurieren um sicherzustellen, dass es bei Multicast-" +"Adressen nicht zu einem Konflikt kommt?" + +#. Tag: para +#: TreeCache_FAQ.xml:334 +#, no-c-format +msgid "" +"There are two parameters to consider: multicast address (plus port) and the " +"group name. At minimum, you will have to run components using a different " +"group name. But whether to run them on the same channel depends upon whether " +"the communication performance is critical for you or not. If it is, then " +"it'd be best to run them on different channels." +msgstr "" +"Es gilt zwei Parameter zu berücksichtigen: Multicast-Adresse (plus Port) und " +"der Gruppenname. Sie werden zumindest Komponenten ausführen müssen, die " +"unterschiedliche Gruppennamen verwenden. Ob sie dies aber auf demselben " +"Channel tun, hängt davon ab, ob die Kommunikations-Performance von " +"kritischer Bedeutung für Sie ist oder nicht. Falls ja, ist es am besten, " +"wenn Sie sie auf unterschiedlichen Channels ausführen." + +#. Tag: para +#: TreeCache_FAQ.xml:346 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache persistence storage?" +msgstr "Unterstützt JBoss Cache derzeit Cache-Persistenzspeicher?" + +#. Tag: para +#: TreeCache_FAQ.xml:352 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache has a cache loader interface that supports cache " +"persistence. See below for more FAQs on cache loaders." +msgstr "" +"Ja. Seit Release 1.1 besitzt JBoss Cache ein CacheLoader Interface, das " +"Cache-Persistenz unterstützt. Siehe unten." + +#. Tag: para +#: TreeCache_FAQ.xml:360 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache passivation/ overflow to a data store?" +msgstr "" +"Unterstützt JBoss Cache derzeit Cache-Passivierung/Overflow in einen " +"Datenspeicher?" + +#. Tag: para +#: TreeCache_FAQ.xml:366 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache uses the cache loader to support cache passivation/ " +"overflow. See documentation on how to configure and use this feature." +msgstr "" +"Ja. Seit Release 1.2.4 verwendet JBoss Cache den CacheLoader zur " +"Unterstützung von Cache Passivierung /Overflow. In der Dokumentation finden " +"Sie Informationen zur Konfiguration und Verwendung dieses Features." + +#. Tag: para +#: TreeCache_FAQ.xml:375 +#, no-c-format +msgid "Is JBoss Cache thread safe?" +msgstr "Ist JBoss Cache Thread-sicher?" + +#. Tag: para +#: TreeCache_FAQ.xml:379 +#, no-c-format +msgid "Yes, it is thread safe." +msgstr "Ja, es ist Thread-sicher." + +#. Tag: para +#: TreeCache_FAQ.xml:385 +#, no-c-format +msgid "Does JBoss Cache support XA (2PC) transactions now?" +msgstr "Unterstützt JBoss Cache jetzt XA (2PC) Transactions?" + +#. Tag: para +#: TreeCache_FAQ.xml:389 +#, fuzzy, no-c-format +msgid "" +"No, although it is also on our to do list. Our internal implementation does " +"use a procedure similar to 2PC to coordinate a transactions among different " +"instances, but JBoss Cache is not an XA resource." +msgstr "" +"Nein, obwohl wir daran arbeiten. Unsere interne Implementierung verwendet " +"eine ähnliche 2PC Prozedur zur Koordinierung einer Transaktion zwischen " +"verschiedenen Instanzen." + +#. Tag: para +#: TreeCache_FAQ.xml:398 +#, fuzzy, no-c-format +msgid "Which transaction managers are supported by JBoss Cache?" +msgstr "Welche TransactionManagers werden durch JBoss Cache unterstützt?" + +#. Tag: para +#: TreeCache_FAQ.xml:404 +#, no-c-format +msgid "" +"JBoss Cache supports any TransactionManager that is <ulink url=\"http://java." +"sun.com/products/jta/\">JTA</ulink> compliant such as<ulink url=\"http://www." +"jboss.org/jbosstm/\">JBoss Transactions</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:408 +#, no-c-format +msgid "" +"While JBoss Cache does ships with a dummy transaction manager (<literal>org." +"jboss.cache.transaction.DummyTransactionManager</literal>), we do " +"<emphasis>not</emphasis> recommend using this for production. It is not " +"thread safe, and is intended for internal testing only." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:421 +#, no-c-format +msgid "How do I set up the cache to be transactional?" +msgstr "Wie stelle ich das Cache ein, damit es transaktional ist?" + +#. Tag: para +#: TreeCache_FAQ.xml:425 +#, fuzzy, no-c-format +msgid "" +"You either use the default transaction manager that ships with JBoss AS or " +"you have to implement the <literal>org.jboss.cache.transaction." +"TransactionManagerLookup</literal> interface, and return an instance of your " +"<literal>javax.transaction.TransactionManager</literal> implementation. The " +"configuration property <literal>TransactionManagerLookupClass</literal> " +"defines the class to be used by the cache to fetch a reference to a " +"transaction manager. It is trivial to implement this interface to support " +"other transaction managers. Once this attribute is specified, the cache will " +"look up the transaction context from this transaction manager." +msgstr "" +"Sie können entweder den standardmäßigen (JBoss) TransactionManager zur " +"Ausführung von JBossCache innerhalb von JBoss verwenden oder Sie müssen das " +"<literal>TransactionManagerLookup</literal>-Interface verwenden und eine " +"Instanz Ihres javax.transaction.TransactionManager wiedergeben. Die " +"Konfigurations-Property <literal>TransactionManagerLookupClass</literal> " +"definiert die vom Cache zu verwendende Klasse beim Abrufen einer Referenz " +"zum TransactionManager. Die Implementierung dieser Klasse zur Unterstützung " +"anderer TransactionManagers ist trivial. Nachdem dieses Attribut festgelegt " +"ist, sucht das Cache den Transaktionskontext dieses Transaktions-Managers." + +#. Tag: para +#: TreeCache_FAQ.xml:441 +#, no-c-format +msgid "" +"The <literal>org.jboss.cache.transaction.GenericTransactionManagerLookup</" +"literal> class that ships with JBoss Cache is able to detect and bind to " +"most popular transaction managers. See the " +"<literal>GenericTransactionManagerLookup</literal> javadocs for more " +"information." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:454 +#, no-c-format +msgid "How do I control the cache locking level?" +msgstr "Wie kann ich die Cache-Sperrebene steuern?" + +#. Tag: para +#: TreeCache_FAQ.xml:458 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache lets you control the cache locking level through the transaction " +"isolation level. This is configured through the attribute " +"<literal>IsolationLevel</literal> . The transaction isolation levels " +"correspond to database isolation levels, namely, <literal>NONE</literal> , " +"<literal>READ_UNCOMMITTED</literal> , <literal>READ_COMMITTED</literal> , " +"<literal>REPEATABLE_READ</literal> , and <literal>SERIALIZABLE</literal> . " +"Note that these isolation levels are ignored if optimistic locking is used. " +"For details, please refer to the user manual." +msgstr "" +"JBossCache lässt Sie die Sperrebene des Cache durch die Isolationsebene der " +"Transaktion steuern. Die Konfiguration hiervon erfolgt durch das Attribut " +"<literal>IsolationLevel</literal> . Zur Zeit führt JBossCache intern " +"pessimistisches Sperren durch. Und die Isolationsebene der Transaktion vom " +"pessimistischen Sperren entspricht JDBC-Isolationsebenen, namentlich " +"<literal>NONE</literal> , <literal>READ_UNCOMMITTED</literal> , " +"<literal>READ_COMMITTED</literal> , <literal>REPEATABLE_READ</literal> und " +"<literal>SERIALIZABLE</literal>. Bitte beachten Sie, dass diese " +"Isolationsebenen bei der Verwendung optimistischen Sperrens ignoriert " +"werden. Einzelheiten hierzu finden Sie im Benutzerhandbuch." + +#. Tag: para +#: TreeCache_FAQ.xml:480 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, when using the MVCC locking scheme, only " +"<literal>READ_COMMITTED</literal> and <literal>REPEATABLE_READ</literal> are " +"supported. Any other isolation level provided will either be upgraded or " +"downgraded accordingly." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:493 +#, no-c-format +msgid "How does JBoss Cache lock data for concurrent access?" +msgstr "Wie sperrt JBoss Cache Daten für nebenläufigen Zugriff?" + +#. Tag: para +#: TreeCache_FAQ.xml:497 +#, fuzzy, no-c-format +msgid "" +"In JBoss Cache 2.x, by default pessimistic locking is used to lock data " +"nodes, based on the isolation level configured. We also offer optimistic " +"locking to allow for greater concurrency at the cost of slight processing " +"overhead and performance. See the documentation for a more detailed " +"discussion on concurrency and locking in JBoss Cache." +msgstr "" +"Standardmäßig verwendet JBoss Cache pessimistisches Sperren, um Daten-Nodes " +"zu sperren, basierend auf der konfigurierten Isolationsebene. Seit JBoss " +"Cache 1.3.0 bieten wir auch optimistisches Sperren, um bessere " +"Nebenläufigkeit auf Kosten leichten Bearbeitungs-Overheads und Performance " +"zu liefern. Weitere Informationen zu Nebenläufigkeit und Sperren in JBoss " +"Cache finden Sie in der Dokumentation." + +#. Tag: para +#: TreeCache_FAQ.xml:505 +#, no-c-format +msgid "" +"In JBoss Cache 3.x, optimistic and pessimistic locking are deprecated in " +"favour of MVCC (multi-version concurrency control), which is far more " +"efficient than either optimistic or pessimistic locking. For a detailed " +"discussion on our MVCC implementation, see <ulink url=\"http://jbosscache." +"blogspot.com/2008/07/mvcc-has-landed.html\">this blog entry</ulink> " +"and<ulink url=\"http://www.jboss.org/community/docs/DOC-10272\">this wiki " +"page</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:520 +#, fuzzy, no-c-format +msgid "How do I enable Optimistic Locking or MVCC in JBoss Cache?" +msgstr "" +"Wie wird optimistisches Sperren (\"Optimistic Locking\" in JBoss Cache " +"aktiviert?" + +#. Tag: para +#: TreeCache_FAQ.xml:524 +#, no-c-format +msgid "Please see the configuration section of the Users' Guide for details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:532 +#, no-c-format +msgid "Can I use the cache locking level even without a transaction context?" +msgstr "Kann ich die Cache Sperrebene auch ohne Transaktionkontext verwenden?" + +#. Tag: para +#: TreeCache_FAQ.xml:538 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache controls the individual node locking behavior through the " +"isolation level semantics. This means even if you don't use a transaction, " +"you can specify the lock level via isolation level. You can think of the " +"node locking behavior outside of a transaction as if it is under transaction " +"with <literal>auto_commit</literal> on." +msgstr "" +"Ja. JBossCache steuert das individuelle Node-Sperrverhalten durch die " +"Isolationsebenensemantik. Das bedeutet, dass selbst wenn Sie keine " +"Transaktion verwendet, Sie die Sperrebene via Isolationsebene festlegen " +"können. Sie können sich das Node-Sperrverhalten außerhalb einer Transaktion " +"vorstellen als sei es unter einer Transaktion mit <literal>auto_commit</" +"literal> an." + +#. Tag: para +#: TreeCache_FAQ.xml:551 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache support <literal>SELECT FOR UPDATE</literal> semantics?" +msgstr "Unterstützt JBoss Cache <literal>Region</literal> ?" + +#. Tag: para +#: TreeCache_FAQ.xml:559 +#, no-c-format +msgid "" +"Yes, but this is is only possible if you are running within a JTA " +"transaction <emphasis>and</emphasis> are using either <literal>MVCC</" +"literal> or <literal>PESSIMISTIC</literal> as your node locking scheme." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:568 +#, no-c-format +msgid "To achieve <literal>SELECT FOR UPDATE</literal> semantics, simply do:" +msgstr "" + +#. Tag: programlisting +#: TreeCache_FAQ.xml:573 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" // start transaction ... \n" +"\n" +" cache.getInvocationContext().getOptionOverrides().setForceWriteLock" +"(true);\n" +" Node n = cache.get(\"/a/b/c\"); // this acquires a WRITE LOCK on this " +"node\n" +" ...\n" +" ...\n" +"\n" +" // end transaction\n" +"\n" +" ]]>" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:579 +#, no-c-format +msgid "" +"With replication (REPL_SYNC/REPL_ASYNC) or invalidation (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), how often does the cache broadcast messages over the " +"network?" +msgstr "" +"Mit Replikation (REPL_SYNC/REPL_ASYNC) oder Invalidierung (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), wie häufig broadcastet das Cache Nachrichten über das " +"Netzwerk?" + +#. Tag: para +#: TreeCache_FAQ.xml:586 +#, fuzzy, no-c-format +msgid "" +"If the updates are under transaction, then the broadcasts happen only when " +"the transaction is about to commit (actually during the prepare stage " +"internally). That is, it will be a batch update. However, if the operations " +"are not under transaction context, then each update will trigger " +"replication. Note that this has performance implications if network latency " +"is a problem." +msgstr "" +"Sind die Aktualisierungen unter der Transaktion, so finden Broadcasts nur " +"statt, wenn die Transaktion im Begriff ist festgeschrieben zu werden " +"(aktuell intern während der Vorbereitungsphase). Das heißt, es handelt sich " +"um eine Batch-Aktualisierung. Sind die Transaktionen jedoch nicht unter " +"Transaktionskontext, so löst jede Aktualisierung Replikation aus. Beachten " +"Sie bitte, dass dies Folgen für die Performanz hat, wenn der " +"Netzwerktransport stark ist (dies ist in der Regel der Fall)." + +#. Tag: para +#: TreeCache_FAQ.xml:598 +#, no-c-format +msgid "How can I do a mass removal?" +msgstr "Wie kann ich ein Massen-Entfernen durchführen ?" + +#. Tag: para +#: TreeCache_FAQ.xml:602 +#, fuzzy, no-c-format +msgid "" +"If you do a<literal>cache.removeNode(\"/myroot\")</literal>, it will " +"recursively remove all the entries under \"/myroot\"." +msgstr "" +"Falls Sie ein cache.remove(\"/root\") durchführen, so werden rekursiv " +"sämtliche Einträge unter \"/root\" entfernt." + +#. Tag: para +#: TreeCache_FAQ.xml:610 +#, no-c-format +msgid "Can I monitor and manage the JBoss Cache?" +msgstr "Kann ich das JBoss Cache überwachen und verwalten?" + +#. Tag: para +#: TreeCache_FAQ.xml:614 +#, fuzzy, no-c-format +msgid "" +"Yes, using a JMX console such as the one shipped with JBoss AS or Java 5's " +"<literal>jconsole</literal> utility. See the chapter titled <emphasis role=" +"\"bold\">Management Information</emphasis> in the JBoss Cache Users' Guide " +"for more details." +msgstr "" +"Mit JBoss Cache 1.3.0 geht das, wenn Sie JBoss Cache innerhalb von JBoss AS " +"ausführen oder JDK 5.0's <literal>jconsole</literal>-Dienstprogramm " +"verwenden. Im Kapitel mit Titel <emphasis role=\"bold\">Management " +"Information</emphasis> im Benutzerhandbuch zum JBoss Cache finden Sie " +"weitere Einzelheiten." + +#. Tag: para +#: TreeCache_FAQ.xml:625 +#, no-c-format +msgid "" +"JBoss Cache uses a <literal>:</literal> character in its object name. This " +"causes problems with my MBean server. What can I do about it?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:633 +#, no-c-format +msgid "" +"This is something we have seen with some MBean servers. By default, JBoss " +"Cache uses <literal>jboss.cache:service=JBossCache</literal> as a prefix to " +"all objects it binds in JMX. To work around this, use the <literal>-" +"Djbosscache.jmx.prefix</literal> JVM parameter to pass in an alternate " +"prefix." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:647 +#, fuzzy, no-c-format +msgid "Can I disable JBoss Cache management attributes?" +msgstr "" +"Kann ich JBoss Cache Management-Attribute in JBoss Cache 1.3.0 deaktivieren?" + +#. Tag: para +#: TreeCache_FAQ.xml:651 +#, no-c-format +msgid "" +"Yes, you can. See the section on configuration in the JBoss Cache Users' " +"Guide." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:658 +#, no-c-format +msgid "What happened to jboss-serialization.jar?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:662 +#, no-c-format +msgid "" +"As of JBoss Cache 2.0.0, the dependency on JBoss Serialization has been " +"dropped since most of the benefits of JBoss Serialization are available in " +"updated Java 5 VMs. Since JBoss Cache 2.0.0 is baselined on Java 5, there " +"was no need to provide these benefits separately." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:673 +#, no-c-format +msgid "Does JBoss Cache support partitioning?" +msgstr "Unterstützt JBoss Cache Partitionierung?" + +#. Tag: para +#: TreeCache_FAQ.xml:677 +#, no-c-format +msgid "" +"Not right now. JBoss Cache does not support partitioning that a user can " +"configure to have different set of data residing on different cache " +"instances while still participating as a replication group." +msgstr "" +"Im Augenblick nicht. JBoss Cache unterstützt keine Partitionierung, die " +"durch den Benutzer konfiguriert werden kann, um einen anderen Datensatz auf " +"anderen Cache Instanzen zu haben und gleichzeitig als Replikationsgruppe " +"teilzunehmen." + +#. Tag: para +#: TreeCache_FAQ.xml:682 +#, no-c-format +msgid "" +"This is on the roadmap though, so do keep an eye on <ulink url=\"http://jira." +"jboss.org/jira/browse/JBCACHE-60\">JBCACHE-60</ulink> if you are interested." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:692 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache handle the concept of application classloading inside, say, " +"a Java EE container?" +msgstr "" +"Handhabt JBoss Cache das Konzept von Anwendung Classloading innen, sagen wir " +"einen J2EE-Container?" + +#. Tag: para +#: TreeCache_FAQ.xml:698 +#, fuzzy, no-c-format +msgid "" +"Application-specific classloading is used widely inside a Java EE container. " +"For example, a web application may require a new classloader to scope a " +"specific version of the user library. However, by default JBoss Cache is " +"agnostic to the classloader. In general, this leads to two kinds of problems:" +msgstr "" +"Applikations-spezifisches Classloading findet innerhalb eines J2EE-" +"Containers breite Anwendung. Es ist etwa möglich, dass eine Webanwendung " +"einen neuen Classloader benötigt, um eine bestimmte Version der " +"Benutzerbibliothek abzugrenzen. Jedoch ist das JBoss Cache dem Classloader " +"unbekannt. Dies führt in der Regel zu zwei Arten von Problemen:" + +#. Tag: para +#: TreeCache_FAQ.xml:707 +#, no-c-format +msgid "" +"Object instance is stored in cache1 and replicated to cache2. As a result, " +"the instance in cache2 is created by the system classloader. The replication " +"may fail if the system classloader on cache2 does not have access to the " +"required class. Even if replication doesn't fail, a user thread in cache2 " +"may not be able to access the object if the user thread is expecting a type " +"defined by the application classloader." +msgstr "" +"Die Objektinstanz wird in cache1 gespeichert und nach cache2 repliziert. Als " +"Ergebnis wird die Instanz in cache2 durch den System-Classloader erstellt. " +"Die Replikation kann fehlschlagen, falls der System-Classloader auf cache2 " +"keinen Zugriff auf die erforderliche Klasse besitzt. Selbst wenn die " +"Replikation nicht fehlschlägt ist es möglich, dass ein Benutzer-Thread in " +"cache2 nicht auf das Objekt zugreifen kann, wenn der Benutzer-Thread einen " +"durch den Applikations-Classloader definierten Typ erwartet." + +#. Tag: para +#: TreeCache_FAQ.xml:718 +#, fuzzy, no-c-format +msgid "" +"Object instance is created by thread 1 and will be accessed by thread 2 " +"(with two different classloaders). JBoss Cache has no notion of the " +"different classloaders involved. As a result, you will have a " +"<literal>ClassCastException</literal> . This is a standard problem in " +"passing an object from one application space to another; JBoss Cache just " +"adds a level of indirection in passing the object." +msgstr "" +"Objektinstanz wird durch thread 1 erstellt und wird durch thread 2 (mit zwei " +"verschiedenen Classloadern) zugegriffen. JBossCache hat keinen Begriff der " +"verschiedenen involvierten Classloadern. Als Ergebnis erhalten Sie eine " +"<literal>ClassCastException</literal>. Es handelt sich um ein " +"Standardproblem bei der Weitergabe eines Objekts von einem Anwendungsraum " +"zum anderen; JBossCache fügt einfach eine Indirektionsebene in der " +"Weitergabe des Objekts hinzu." + +#. Tag: para +#: TreeCache_FAQ.xml:731 +#, fuzzy, no-c-format +msgid "" +"To solve the first kind of issue JBoss Cache uses a " +"<literal>CacheMarshaller</literal> . Basically, this allows application code " +"to register a classloader with a portion of the cache tree for use in " +"handling objects replicated to that portion. See the " +"<literal>CacheMarshaller</literal> section of the Users' Guide for more " +"details." +msgstr "" +"Um das erste Problem zu lösen, haben wir bei JBoss Cache 1.2.4 das Konzept " +"eines <literal>TreeCacheMarshaller</literal> eingeführt. Im Grunde gestattet " +"dies dem Anwendungscode einen Classloader mit einem Teil des Cache-Baums zur " +"Verwendung bei der Handhabung von zu diesem Teil hin replizierten Objekten. " +"Weitere Informationen finden Sie im TreeCacheMarshaller-Abschnitt des " +"Benutzerhandbuchs." + +#. Tag: para +#: TreeCache_FAQ.xml:742 +#, no-c-format +msgid "" +"To solve the second kind of issue, you can use the the " +"<literal>UseLazyDeserialization</literal> configuration option in JBoss " +"Cache, which wraps your objects in a <literal>Marshalledvalue</literal> " +"wrapper. The <literal>MarshalledValue</literal> serializes and deserializes " +"your object on demand, ensuring the proper thread local context class loader " +"is used each time." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:757 +#, no-c-format +msgid "" +"Does JBoss Cache currently support pre-event and post-event notification?" +msgstr "" +"Unterstützt JBoss Cache zum aktuellen Zeitpunkt Vor- und Nach-Ereignis " +"Benachrichtung?" + +#. Tag: para +#: TreeCache_FAQ.xml:763 +#, no-c-format +msgid "" +"Yes. A boolean is passed in to each notification callback identifying " +"whether the callback is before or after the event. See the <literal>org." +"jboss.cache.notifications.annotations.CacheListener</literal> annotation for " +"details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:774 +#, fuzzy, no-c-format +msgid "How do I implement a custom listener to listen to cache events?" +msgstr "" +"Wie implementiere ich einen angepassten Listener, der auf " +"<literal>TreeCache</literal>-Ereignisse horcht?" + +#. Tag: para +#: TreeCache_FAQ.xml:780 +#, no-c-format +msgid "See the Users' Guide on this subject." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:788 +#, fuzzy, no-c-format +msgid "" +"Can I use <literal>UseRegionBasedMarshalling</literal> attribute in JBoss " +"Cache in order to get around ClassCastExceptions happening when accessing " +"data in the cache that has just been redeployed?" +msgstr "" +"Kann ich das <literal>useRegionBasedMarshalling</literal>-Attribut in JBoss " +"Cache verwenden, um zu vermeiden, dass es beim Zugriff auf gerade re-" +"deployte Daten im Cache zu ClassCastExceptions kommt?" + +#. Tag: para +#: TreeCache_FAQ.xml:797 +#, fuzzy, no-c-format +msgid "" +"Yes, you can. Originally, cache Marshalling was designed as a workaround for " +"those replicated caches that upon state transfer did not have access to the " +"classloaders defining the objects in the cache." +msgstr "" +"Ja, das können Sie. Ursprünglich wurde das <literal>TreeCache</literal> " +"Marshalling entworfen, um diese replizierten Caches zu umgehen, die beim " +"Statustransfer keinen Zugriff auf die die Objekte im Cache definierenden " +"Classloader besaßen." + +#. Tag: para +#: TreeCache_FAQ.xml:802 +#, no-c-format +msgid "" +"On each deployment, JBoss creates a new classloader per the top level " +"deployment artifact, for example an EAR. You also have to bear in mind that " +"a class in an application server is defined not only by the class name but " +"also its classloader. So, assuming that the cache is not deployed as part of " +"your deployment, you could deploy an application and put instances of " +"classes belonging to this deployment inside the cache. If you did a " +"redeployment and try to do a get operation of the data previously put, this " +"would result on a ClassCastException. This is because even though the class " +"names are the same, the class definitions are not. The current classloader " +"is different to the one when the classes were originally put." +msgstr "" +"Bei jedem Deployment erstellt JBoss einen neuen Classloader per Deployment " +"Artefakt der obersten Ebene, zum Beispiel ein EAR. Sie sollten weiterhin " +"nicht vergessen, dass eine Klasse in einem Applikationsserver nicht nur " +"durch den Klassennamen, sondern auch durch den Classloader definiert ist. " +"Geht man davon aus, dass das Cache nicht als Teil Ihres Deployment deployt " +"wird, könnten Sie eine Anwendung deployen und zu diesem Deployment gehörende " +"Instanzen von Klassen im Cache platzieren. Falls Sie ein Redeployment " +"durchführen und versuchen eine \"get\"-Operation von zuvor platzierten Daten " +"durchzuführen, so kann dies in einer ClassCastException resultieren. Dies " +"ist der Fall, weil sich die Klassendefinitionen trotz gleicher Klassennamen " +"unterscheiden. Der aktuelle Classloader unterscheidet sich von demjenigen in " +"dem die Klassen ursprünglich platziert wurden." + +#. Tag: para +#: TreeCache_FAQ.xml:817 +#, fuzzy, no-c-format +msgid "" +"By enabling marshalling, you can control the lifecycle of the data in the " +"cache and if on undeployment, you deactivate the region and unregister the " +"classloader that you'd have registered on deployment, you'd evict the data " +"in the cache locally. That means that in the next deployment, the data won't " +"be in the cache, therefore avoiding the problem. Obviously, using " +"marshalling to get around this problem is only recommended when you have " +"some kind of persistence backing where the data survives, for example using " +"CacheLoaders, or when JBoss Cache is used as a second level cache in a " +"persistence framework." +msgstr "" +"Durch Aktivierung von “Marshalling” können Sie den Lebenszyklus von Daten im " +"Cache steuern und falls Sie bei Undeployment die Region deaktivieren und " +"deregistrieren, die Sie beim Deployment registriert haben, so führen Sie " +"eine Eviction der Daten im Cache auf lokaler Basis durch. Dies bedeutet, " +"dass die Daten sich beim nächsten Deployment nicht mehr im Cache befinden " +"und so das Problem vermieden wird. Natürlich wird “Marshalling” zur Umgehung " +"dieses Problems nur empfohlen, wenn Sie irgendeine Form von Persistenz-" +"Backing besitzen, bei dem die Daten überleben, etwa bei Verwendung von " +"CacheLoaders oder wenn JBossCache als Cache der zweiten Ebene in einem " +"Persistenz-Framework verwendet wird." + +#. Tag: para +#: TreeCache_FAQ.xml:830 +#, fuzzy, no-c-format +msgid "" +"To implement this feature, please follow the instructions indicated in the " +"example located in the CacheMarshaller section of the Users' Guide. It's " +"worth noting that instead of a <literal>ServletContextListener</literal> , " +"you could add this code into an <literal>MBean</literal> that contained " +"lifecycle methods, such as <literal>start()</literal> and <literal>stop()</" +"literal> . The key would be for this MBean to depend on the target cache, so " +"that it can operate as long as the cache is up and running." +msgstr "" +"Um dieses Feature zu implementieren, befolgen Sie bitte die Anweisungen im " +"Beispiel, das sich im TreeCacheMarshaller Abschnitt des Benutzerhandbuchs " +"befindet. Es sollte angemerkt werden, dass Sie statt eines " +"<literal>ServletContextListener</literal> diesen Code in einem \"Lifecycle\"-" +"Methoden enthaltenden <literal>MBean</literal> hinzufügen könnten wie " +"<literal>start()</literal> und <literal>stop()</literal>. Der Schlüssel " +"wäre, dass dieses MBean vom Ziel-Cache abhinge, so so dass es laufen kann " +"solange das Cache läuft." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Troubleshooting.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Troubleshooting.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/de-DE/Troubleshooting.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,40 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-09-20 16:08+1000\n" +"Last-Translator: \n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Troubleshooting.xml:6 +#, no-c-format +msgid "Troubleshooting" +msgstr "Fehlerbehebung" + +#. Tag: para +#: Troubleshooting.xml:11 +#, no-c-format +msgid "" +"I am having problems getting JBoss Cache to work, where can I get " +"information on troubleshooting?" +msgstr "" +"Ich habe Probleme damit, JBoss Cache zum Laufen zu bringen - wo finde ich " +"Informationen zur Fehlerbehebung?" + +#. Tag: para +#: Troubleshooting.xml:15 +#, fuzzy, no-c-format +msgid "" +"Troubleshooting section can be found in the following <ulink url=\"http://" +"www.jboss.org/community/docs/DOC-10288\">wiki link</ulink>." +msgstr "" +"Den Abschnitt zur Fehlerbehebung finden Sie in folgendem Abschnitt <ulink " +"url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheTroubleshooting" +"\">wiki link</ulink> ." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Author_Group.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Author_Group.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Author_Group.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,19 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-10-16 13:39+1000\n" +"Last-Translator: Angela Garcia\n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: firstname +#: Author_Group.xml:7 +#, no-c-format +msgid "Ben Wang, Bela Ban, Manik Surtani, Scott Marlow, Galder Zamarreño" +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Book_Info.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Book_Info.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Book_Info.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,40 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-10-16 13:39+1000\n" +"Last-Translator: Angela Garcia\n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Book_Info.xml:5 +#, fuzzy, no-c-format +msgid "JBoss Cache Frequently Asked Questions" +msgstr "Preguntas más frecuentes" + +#. Tag: subtitle +#: Book_Info.xml:6 +#, no-c-format +msgid "for Use with JBoss Enterprise Application Platform 5.0" +msgstr "" + +#. Tag: para +#: Book_Info.xml:12 +#, no-c-format +msgid "" +"This book is a compilation of frequently asked questions about JBoss Cache" +msgstr "" +"Este libro es una compilación de las preguntas más frecuentes sobre JBoss " +"Cache" + +#. Tag: holder +#: Book_Info.xml:24 +#, no-c-format +msgid "&HOLDER;" +msgstr "&HOLDER;" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/CacheLoader_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/CacheLoader_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/CacheLoader_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,366 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-10-16 13:39+1000\n" +"Last-Translator: Angela Garcia\n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: CacheLoader_FAQ.xml:6 +#, no-c-format +msgid "Cache Loaders" +msgstr "Cargadores de caché" + +#. Tag: para +#: CacheLoader_FAQ.xml:12 +#, fuzzy, no-c-format +msgid "What is a cache loader?" +msgstr "¿Qué es un CacheLoader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:16 +#, fuzzy, no-c-format +msgid "" +"A cache loader is the connection of JBoss Cache to a (persistent) data " +"store. The cache loader is called by JBoss Cache to fetch data from a store " +"when that data is not in the cache, and when modifications are made to data " +"in the cache the Cache Loader is called to store those modifications back to " +"the store." +msgstr "" +"A CacheLoader es la conección de JBossCache a un almacenamiento de datos " +"(persistente). El CacheLoader es llamado por JBossCache para buscar datos " +"desde un almacenamiento cuando esos datos no se encuentran en el caché y " +"cuando las modificaciones se realizan en los datos en el caché se llama al " +"CacheLoader para almacenar esas modificaciones en el almacenamiento." + +#. Tag: para +#: CacheLoader_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "" +"In conjunction with eviction policies, JBoss Cache with a cache loader " +"allows a user to maintain a bounded cache for a large backend datastore. " +"Frequently used data is fetched from the datastore into the cache, and the " +"least used data is evicted, in order to provide fast access to frequently " +"accessed data. This is all configured through XML, and the programmer " +"doesn't have to take care of loading and eviction." +msgstr "" +"JUnto con las políticas de eliminación, JBossCache con un CacheLoader le " +"permite a un usuario mantener un caché vinculado para un gran almacenamiento " +"de datos backend. Con frecuencia datos usados son buscados desde el " +"almacenamiento de datos en el caché y los datos menos utilizados son " +"eliminados con el fin de proporcionar un rápido acceso a los datos accedidos " +"con bastante frecuencia. Todo esto se configura por medio de XML y el " +"programador no tiene que encargarse de cargar y eliminar. " + +#. Tag: para +#: CacheLoader_FAQ.xml:32 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache currently ships with several cache loader implementations, " +"including:" +msgstr "" +"JBossCache actualmente se envía junto con varias implementaciones de " +"CacheLoader, incluyendo: " + +#. Tag: para +#: CacheLoader_FAQ.xml:37 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.FileCacheLoader</literal> : this " +"implementation uses the file system to store and retrieve data. JBoss Cache " +"nodes are mapped to directories, subnodes to subdirectories etc. Attributes " +"of a node are mapped to a data file inside the directory." +msgstr "" +"FileCacheLoader: esta implementación utiliza el sistema de archivos para " +"almacenar y recuperar datos. Los nodos de JBossCache son mapeados a " +"directorios, los subnodos a subdirectorios, etc. Los atributos de un nodo " +"son mapeados a un archivo <literal>data</literal> dentro del directorio." + +#. Tag: para +#: CacheLoader_FAQ.xml:49 +#, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.jdbm.JdbmCacheLoader</literal> : this " +"implementation is based on<ulink url=\"http://jdbm.sourceforge.net/\"> JDBM</" +"ulink>, an open source file-based transactional persistence engine." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:58 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.bdbje.BdbjeCacheLoader</literal> : this " +"implementation is based on the Oracle's Berkeley DB Java Edition database, a " +"fast and efficient transactional database. It uses a single file for the " +"entire store. Note that if you use the Berkeley DB cache loader with JBoss " +"Cache and wish to ship your product, you will have to acquire a <ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">commercial license from Oracle</" +"ulink>." +msgstr "" +"BdbjeCacheLoader: esta implementación se basa en la base de datos Sleepycat " +"Java Edition, una base de datos transaccional rápida y eficiente. Utiliza un " +"sólo archivo para todo el almacenamiento. Observe que si utiliza el " +"CacheLoader de Sleepycat con JBoss Cache y desea enviar su producto entonces " +"tendrá que adquirir una licensia comercial <ulink url=\"http://www.sleepycat." +"com/jeforjbosscache\"> de Sleepycat </ulink> ." + +#. Tag: para +#: CacheLoader_FAQ.xml:71 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.JDBCCacheLoader</literal> : this " +"implementation uses the relational database as the persistent storage." +msgstr "" +"JDBCCacheLoader: esta implementación utiliza la base de datos relacional " +"como el almacenamiento persistente." + +#. Tag: para +#: CacheLoader_FAQ.xml:79 +#, fuzzy, no-c-format +msgid "" +"And more. See the chapter on cache loaders in the Users' Guide for more " +"details." +msgstr "Y más, consulte la documentación para obtener mayores detalles." + +#. Tag: para +#: CacheLoader_FAQ.xml:88 +#, no-c-format +msgid "Is the FileCacheLoader recommended for production use?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:92 +#, no-c-format +msgid "" +"No, it is not. The FileCacheLoader has some severe limitations which " +"restrict its use in a production environment, or if used in such an " +"environment, it should be used with due care and sufficient understanding of " +"these limitations." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:99 +#, no-c-format +msgid "" +"Due to the way the FileCacheLoader represents a tree structure on disk " +"(directories and files) traversal is inefficient for deep trees." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:103 +#, no-c-format +msgid "" +"Usage on shared filesystems like NFS, Windows shares, etc. should be avoided " +"as these do not implement proper file locking and can cause data corruption." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:107 +#, no-c-format +msgid "" +"Usage with an isolation level of NONE can cause corrupt writes as multiple " +"threads attempt to write to the same file." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:111 +#, no-c-format +msgid "" +"File systems are inherently not transactional, so when attempting to use " +"your cache in a transactional context, failures when writing to the file " +"(which happens during the commit phase) cannot be recovered." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:120 +#, no-c-format +msgid "" +"As a rule of thumb, it is recommended that the FileCacheLoader not be used " +"in a highly concurrent, transactional or stressful environment, and its use " +"is restricted to testing." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:130 +#, fuzzy, no-c-format +msgid "Can writing to cache loaders be asynchronous?" +msgstr "¿La escritura en CacheLoaders puede ser asincrónica?" + +#. Tag: para +#: CacheLoader_FAQ.xml:134 +#, fuzzy, no-c-format +msgid "" +"Yes. Set the <literal>async</literal> attrobute to true. See the JBoss Cache " +"Users' Guide for a more detailed discussion. By default though, all cache " +"loader writes are synchronous and will block." +msgstr "" +"Sí desde JBossCache 1.2.4. Configure la propiedad CacheLoaderAsynchronous " +"como verdadera. Consulte la documentación de JBossCache para obtner una " +"discusión más detallada. Sin embargo, por defecto todas las escrituras de " +"los cargadores de caché son sincrónicas y se bloquearán." + +#. Tag: para +#: CacheLoader_FAQ.xml:145 +#, fuzzy, no-c-format +msgid "Can I write my own cache loader ?" +msgstr "¿Puedo escribir mi propio CacheLoader ?" + +#. Tag: para +#: CacheLoader_FAQ.xml:149 +#, fuzzy, no-c-format +msgid "" +"Yes. A cache loader is a class implementing <literal>org.jboss.cache.loader." +"CacheLoader</literal> or extending <literal>org.jboss.cache.loader." +"AbstractCacheLoader</literal> . It is configured via the XML file (see JBoss " +"Cache Users' Guide)." +msgstr "" +"Sí. Un CacheLoader es una clase implementando <literal>org.jboss.cache." +"loader.CacheLoader</literal> . Se puede configurar por medio del archivo XML " +"(consulte la documentación y los tutoriales de JBossCache)." + +#. Tag: para +#: CacheLoader_FAQ.xml:161 +#, fuzzy, no-c-format +msgid "Does a cache loader have to use a persistent store ?" +msgstr "¿Un CacheLoader tiene que utilizar un almacenamiento persistente?" + +#. Tag: para +#: CacheLoader_FAQ.xml:165 +#, fuzzy, no-c-format +msgid "" +"No, a cache loader could for example fetch (and possibly store) its data " +"from a webdav-capable webserver. Another example is a caching proxy server, " +"which fetches contents from the web. Note that an implementation of " +"CacheLoader may not implement the 'store' functionality in this case, but " +"just the 'load' functionality." +msgstr "" +"No, un CacheLoader puede por ejemplo buscar (y posiblemente almacenar) sus " +"datos desde un servidor web webdav-capable. Otro ejemplo es un srevidor " +"proxy con caché, el cual busca contenido en la web. Observe que puede que " +"una implementación de CacheLoader no implemente la funcionalidad del " +"'almacenamiento' en este caso, sino sólo la funcionalidad de 'carga'." + +#. Tag: para +#: CacheLoader_FAQ.xml:177 +#, fuzzy, no-c-format +msgid "Do I have to pay to use Oracle's Berkeley DB CacheLoader?" +msgstr "¿Tengo que pagar para utilizar el CacheLoader de Sleepycat?" + +#. Tag: para +#: CacheLoader_FAQ.xml:181 +#, fuzzy, no-c-format +msgid "" +"Not if you use it only for personal use. As soon as you distribute your " +"product with BdbjeCacheLoader, you have to purchase a commercial license " +"from Oracle. See details at <ulink url=\"http://www.sleepycat.com/" +"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ." +msgstr "" +"No si sólo es para uso personal. En el momento en que distribuya su producto " +"con BdbjeCacheLoader, tendrá que comprar una licencia comercial de " +"Sleepycat. Puede encontrar más detalles en <ulink url=\"http://www.sleepycat." +"com/jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ." + +#. Tag: para +#: CacheLoader_FAQ.xml:194 +#, no-c-format +msgid "Are there any tools available to monitor the Berkeley DB instance?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:198 +#, no-c-format +msgid "" +"Yes. Oracle ships a JMX-based monitoring tool, called <ulink url=\"http://" +"www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/" +"jmx/JEMonitor.html\"> JEMonitor </ulink> which can be downloaded from the " +"Oracle website." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:211 +#, no-c-format +msgid "" +"When tuning my Berkeley DB instance, where should I put my je.properties " +"file?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:215 +#, no-c-format +msgid "" +"<literal>je.properties</literal> should reside in your Berkeley DB home " +"directory. This is the directory you pass in to the BDBJECacheLoader's " +"<literal>location</literal> configuration property." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:227 +#, no-c-format +msgid "Can I use more than one cache loader?" +msgstr "¿Puedo utilizar más de un cargador de caché?" + +#. Tag: para +#: CacheLoader_FAQ.xml:231 +#, fuzzy, no-c-format +msgid "" +"Yes. Within the CacheLoaderConfiguration XML element (see Users' Guide " +"chapter on cache loaders) you can describe several cache loaders. The impact " +"is that the cache will look at all of the cache loaders in the order they've " +"been configured, until it finds a valid, non-null element of data. When " +"performing writes, all cache loaders are written to (except if the " +"ignoreModifications element has been set to true for a specific cache loader." +msgstr "" +"Sí desde JBossCache 1.3.0. Con el nuevo elemento XML " +"CacheLoaderConfiguration (consulte la sección del manual del usuario sobre " +"caragores de caché) ahora puede describir varios cargadores de caché. El " +"impacto es que el caché mirará todos los cargadores de caché en el orden en " +"que han sido configurados hasta que encuentre un elemento de datos válido, " +"no-nulo. Al realizar escrituras, todos los cargadores de caché se escriben " +"en (excepto si el elemento ignoreModifications ha sido configurado como " +"verdadero para un cargador de caché en especifico." + +#. Tag: para +#: CacheLoader_FAQ.xml:245 +#, no-c-format +msgid "" +"Can I migrate a JDBCacheLoader or FileCacheLoader based cache store " +"containing data formatted with JBoss Cache 1.x.x to JBoss Cache 2.0 format?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:250 +#, no-c-format +msgid "" +"Yes. See \"Transforming Cache Loaders\" section within the \"Cache Loaders\" " +"section located in the JBoss Cache Users' Guide." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:257 +#, no-c-format +msgid "Is the TCPDelegatingCacheLoader resilient to TCPCacheServer restarts?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:263 +#, no-c-format +msgid "" +"As of JBoss Cache 2.1.0, the answer is yes. See the Users' Guide for details " +"on how to configure and tune your retries and wait period for reestablishing " +"the TCP connection." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:269 +#, no-c-format +msgid "" +"Prior to that, restarting the TCPCacheServer would also mean restarting your " +"application that uses the cache." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Eviction_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Eviction_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Eviction_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,169 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-10-16 13:39+1000\n" +"Last-Translator: Angela Garcia\n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Eviction_FAQ.xml:6 +#, no-c-format +msgid "Eviction Policies" +msgstr "Políticas de eliminación" + +#. Tag: para +#: Eviction_FAQ.xml:10 +#, no-c-format +msgid "Does JBoss Cache support eviction policies?" +msgstr "¿JBoss Cache soporta políticas de eliminación?" + +#. Tag: para +#: Eviction_FAQ.xml:14 +#, no-c-format +msgid "" +"Yes. JBoss Cache currently supports multiple eviction policies such as LRU, " +"MRU, and FIFO. Users can also plug in their own eviction policy algorithms. " +"See user guide for details." +msgstr "" + +#. Tag: para +#: Eviction_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "Does JBoss Cache's eviction policy operates in replication mode?" +msgstr "" +"¿La política de eliminación LRU implementada de JBoss Cache opera en modo de " +"replicación?" + +#. Tag: para +#: Eviction_FAQ.xml:29 +#, no-c-format +msgid "Yes and no. :-)" +msgstr "Sí y no. :-)" + +#. Tag: para +#: Eviction_FAQ.xml:31 +#, fuzzy, no-c-format +msgid "" +"The eviction policy only operates in local mode. That is, nodes are only " +"evicted locally. This may cause the cache contents not to be synchronized " +"temporarily. But when a user tries to obtain the cached contents of an " +"evicted node and finds out that is null (e.g., <literal>get</literal> " +"returns null), it should get it from the other data source and re-populate " +"the data in the cache. During this moment, the node content will be " +"propagated and the cache content will be in sync." +msgstr "" +"La política LRU sólo opera en modo local. Es decir que los nodos sólo se " +"eliminan localmente. Esto puede hacer que el contenido del caché no esté " +"sincronizado temporalmente. Pero cuando un usuario trata de obtener el " +"contenido en caché de un nodo eliminado y se encuentre con que es nulo (por " +"ejemplo, <literal>get</literal> retorna nulo), debe obtenerlo de la otra " +"fuente de datos y debe repopular los datos en el caché. Durante este " +"momento, el contenido del nodo será propagado y el contenido del caché " +"estará sincronizado. " + +#. Tag: para +#: Eviction_FAQ.xml:42 +#, no-c-format +msgid "" +"However, you still can run eviction policies with cache mode set to either " +"<literal>REPL_SYNC</literal> or <literal>REPL_ASYNC</literal> . Depending on " +"your use case, you can set multiple cache instances to have their own " +"eviction policy (which are applied locally) or just have selected instances " +"with eviction policies activated." +msgstr "" +"Sin embargo, puede ejeuctar políticas de eliminacióncon el modo caché " +"configurado como <literal>REPL_SYNC</literal> o <literal>REPL_ASYNC</" +"literal> . Dependiendo de su caso, puede configurar múltiples instancias " +"caché para que tengan su propia política de eliminación (las cuales se " +"aplican localmente) o simplemente tenga instancias seleccionadas con " +"políticas de eliminación activadas." + +#. Tag: para +#: Eviction_FAQ.xml:53 +#, no-c-format +msgid "" +"Also note that, with cache loader option, a locally evicted node can also be " +"persisted to the backend store and a user can retrieve it from the store " +"later on." +msgstr "" +"También observe que con la opción de cargador caché, un nodo eliminado " +"localmente también puede ser persistido en el almacenamiento backend y un " +"usuario puede recuperarlo del almacenamiento después. " + +#. Tag: para +#: Eviction_FAQ.xml:62 +#, no-c-format +msgid "Does JBoss Cache support <literal>Region</literal> ?" +msgstr "¿JBoss Cache soporta <literal>Region</literal> ?" + +#. Tag: para +#: Eviction_FAQ.xml:69 +#, no-c-format +msgid "" +"Yes. JBoss Cache has the notion of region where a user can configure the " +"eviction policy parameters (e.g., <literal>maxNodes</literal> or " +"<literal>timeToIdleSeconds</literal> )" +msgstr "" +"Sí. JBoss Cache cuenta con la noción de región en donde un usuario puede " +"configurar los parámetros de la política de eliminación (por ejemplo, " +"<literal>maxNodes</literal> o <literal>timeToIdleSeconds</literal> )" + +#. Tag: para +#: Eviction_FAQ.xml:77 +#, fuzzy, no-c-format +msgid "" +"A region in JBoss Cache denotes a portion of tree hierarchy, e.g., a fully " +"qualified name ( <literal>org.jboss.cache.Fqn</literal> ). For example, a " +"user can define <literal>/org/jboss</literal> and <literal>/org/foocom</" +"literal> as two separate regions. But note that you can configure the region " +"programmatically now, i.e., everything has to be configured through the xml " +"file." +msgstr "" +"Una región en JBoss Cache denota una porción de jerarquía de árbol, por " +"ejemplo, un nombre completamente calificado ( <literal>FQN</literal> ). Por " +"ejemplo, un usuario puede definir <literal>/org/jboss</literal> y <literal>/" +"org/foocom</literal> como dos regiones separadas. Pero note que puede " +"configurar la región programáticamente, por ejemplo, todo tiene que ser " +"configurado por medio del archivo xml." + +#. Tag: para +#: Eviction_FAQ.xml:94 +#, no-c-format +msgid "" +"I have turned on the eviction policy, why do I still get \"out of memory" +"\" (OOM) exception?" +msgstr "" +"La política de eliminación está prendida, ¿por qué sigo recibiendo la " +"excepción \"out of memory\" (OOM)?" + +#. Tag: para +#: Eviction_FAQ.xml:100 +#, fuzzy, no-c-format +msgid "" +"OOM can happen when the speed of cache access exceeds the speed of eviction " +"policy handling timer. Eviction policy handler will wake up every " +"<literal>wakeUpInterval</literal> milliseconds (or " +"<literal>wakeUpIntervalSeconds</literal> seconds, prior to 3.x) to process " +"the eviction event queue. So when the queue size is full, it will create a " +"backlog and cause out-of-memory exceptions to happen unless the eviction " +"timer catches up. To address this problem, in addition to increase the VM " +"heap size, you can also reduce the <literal>wakeUpInterval</literal> so the " +"timer thread processes the queue more frequently." +msgstr "" +"OOM puede tener lugar cuando la velocidad del acceso al caché excede la " +"velocidad del temporizador de manejo de la política de eliminación. El " +"manejador de la política de eliminación se despertará cada " +"<literal>wakeUpIntervalInSeconds</literal> segundos para procesar la cola " +"del evento de eliminación. El tamaño de la cola está fijo en 20000. Así que " +"cuando el tamaño de la cola esté lleno, creará un backlog y hará que tenga " +"lugar un OOM a menos de que el temporizador de eliminación lo alcance. Para " +"solucionar este problema, además de incrementar el tamaño heap de la MV " +"también puede reducir el <literal>wakeUpIntervaleInSeconds</literal> de " +"manera que el hilo del temporizador procesa la cola con más frecunecia." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/General_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/General_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/General_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,165 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-10-16 13:39+1000\n" +"Last-Translator: Angela Garcia\n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: General_FAQ.xml:6 +#, no-c-format +msgid "General Information" +msgstr "Información general" + +#. Tag: para +#: General_FAQ.xml:10 +#, no-c-format +msgid "What is JBoss Cache?" +msgstr "¿Qué es JBoss Cache?" + +#. Tag: para +#: General_FAQ.xml:14 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache is a replicated and transactional cache. It is replicated since " +"multiple JBoss Cache instances can be distributed (either within the same " +"JVM or across several JVMs whether they reside on the same machine or on " +"different machines on a network) and data is replicated across the whole " +"group. It is transactional because a user can configure a <ulink url=" +"\"http://java.sun.com/products/jta/\">JTA</ulink> compliant transaction " +"manager and make any cache interaction transactional, and caches would " +"participate in ongoing JTA transactions. Note that the cache can also be run " +"without any replication; this is the local mode." +msgstr "" +"JBoss Cache es un caché transaccional y replicado. Es replicado ya que se " +"pueden distribuir múltiples instancias de JBoss Cache (ya sea dentro de la " +"misma MVJ o a través de varias MVJ ya sea que se encuentren en la misma " +"máquina o en diferentes máquinas en una red) y los datos se replican a " +"través de todo el grupo. Es transaccional ya que el usuario puede configurar " +"un administrador de transacciones que cumpla con los requerimientos de JTA y " +"hacer la operación del caché transaccional. Observe que el caché también se " +"puede ejecutar sin ninguna replicación, este es el modo local. " + +#. Tag: para +#: General_FAQ.xml:28 +#, no-c-format +msgid "" +"JBoss Cache comes in two flavours: Core and POJO versions. The core library " +"(using the <literal>org.jboss.cache.Cache</literal> interface) is the " +"underlying library that organises data in a tree-like structure and handles " +"all locking, passivation, eviction and replication characteristics of data " +"in the cache. The POJO library (using the <literal>org.jboss.cache.pojo." +"PojoCache</literal> interface) is built atop the core library and allows " +"introspection of objects in the cache providing transparent coherence by " +"using JBoss AOP. Note that the POJO edition of JBoss Cache (often referred " +"to as POJO Cache) comes with a separate set of documentation (Users' Guide, " +"FAQ, etc.) available on the JBoss Cache <ulink url=\"http://www.jboss.org/" +"jbosscache/\">documentation website</ulink>." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:66 +#, no-c-format +msgid "Who are the JBoss Cache developers?" +msgstr "¿Quiénes son los desarrolladores de JBoss Cache?" + +#. Tag: para +#: General_FAQ.xml:70 +#, no-c-format +msgid "" +"JBoss Cache has an active community of developers and contributors. The " +"project was founded by Bela Ban and is currently led by Manik Surtani. Jason " +"Greene is the lead for the POJO Cache subsystem, and other contributors both " +"past and present include Ben Wang, Harald Gliebe, Brian Stansberry, Vladimir " +"Blagojevic, Mircea Markus, Jimmy Wilson, Galder Zamarreño and Elias Ross." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:139 +#, no-c-format +msgid "How do I know the version of JBoss Cache that I am using?" +msgstr "¿Cómo saber que versión de JBoss Cache estoy utilizando?" + +#. Tag: para +#: General_FAQ.xml:143 +#, no-c-format +msgid "" +"<literal>java -jar jbosscache-core.jar</literal> will spit out version " +"details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:152 +#, fuzzy, no-c-format +msgid "" +"Can I run JBoss Cache outside of the JBoss Enterprise Application Platform?" +msgstr "¿Puedo ejecutar JBoss Cache por fuera del JBoss Application Server?" + +#. Tag: para +#: General_FAQ.xml:157 +#, no-c-format +msgid "" +"Absolutely! Even though JBoss Cache comes integrated with the JBoss " +"Enterprise Application Platform, it can also be used in any other Java EE " +"server such as BEA WebLogic, IBM Websphere or Tomcat. It can also run in a " +"standalone Java process, completely outside of an application server. See " +"the Users' Guide for more details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:170 +#, no-c-format +msgid "" +"How can I migrate my application and configuration from using JBoss Cache 1." +"x to 2.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:173 +#, no-c-format +msgid "" +"Look at <ulink url=\"http://www.jboss.org/community/docs/DOC-10246\">this " +"wiki page</ulink> for help." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:182 +#, no-c-format +msgid "What about from 2.x to 3.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:185 +#, no-c-format +msgid "" +"JBoss Cache 3.x is API compatible with 2.x, although as far as possible you " +"should refactor your code not to use deprecated methods as these may " +"disappear in future releases of JBoss Cache." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:190 +#, no-c-format +msgid "" +"JBoss Cache 3.x comes with an all new configuration format. Old 2.x " +"configuration files will still work, although you will get a warning in the " +"logs about this. Again, as far as possible, we recommend migrating your " +"configuration file to the new format. Scripts are provided with the JBoss " +"Cache 3.x distribution to migrate configuration files (see " +"<literal>config2to3.sh</literal> and<literal>config2to3.bat</literal>)." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:201 +#, no-c-format +msgid "" +"Note that to take advantage of some of the new features in JBoss Cache 3.x, " +"you need to be using the new configuration format." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/JBoss_Cache_Frequently_Asked_Questions.po =================================================================== Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Revision_History.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Revision_History.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Revision_History.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,25 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-10-16 13:39+1000\n" +"Last-Translator: Angela Garcia\n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Revision_History.xml:6 +#, no-c-format +msgid "Revision History" +msgstr "" + +#. Tag: author +#: Revision_History.xml:12 +#, fuzzy, no-c-format +msgid "<firstname></firstname> <surname></surname> <email></email>" +msgstr "<firstname>John</firstname> <surname>Doe</surname>" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/TreeCache_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/TreeCache_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/TreeCache_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,1083 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-10-16 13:39+1000\n" +"Last-Translator: Angela Garcia\n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: TreeCache_FAQ.xml:6 +#, fuzzy, no-c-format +msgid "JBoss Cache: Core" +msgstr "JBoss Cache 1.4.1" + +#. Tag: para +#: TreeCache_FAQ.xml:26 +#, no-c-format +msgid "Can I run multiple JBoss Cache instances on the same VM?" +msgstr "¿Puedo ejecutar múltiples instancias de JBoss Cache en la misma MV? " + +#. Tag: para +#: TreeCache_FAQ.xml:30 +#, no-c-format +msgid "" +"Yes. There are some scenarios where you may want to run multiple instances " +"of JBoss Cache. For example, you want to run multiple local cache instances " +"with each instance having its own configuration (e.g., different cache " +"policy). In this case, you will need multiple xml configuration files." +msgstr "" +"Sí. Hay varios escenarios en donde podría ejecutar múltiples instacias de " +"JBoss Cache. Por ejemplo, quiere ejecutar múltiples instancias caché locales " +"en donde cada instancia tiene su propia configuración (por ejemplo, un " +"política de caché diferente). En este caso, necesitará múltiples archivos de " +"configuración xml. " + +#. Tag: para +#: TreeCache_FAQ.xml:41 +#, fuzzy, no-c-format +msgid "Can JBoss Cache run as a second level cache inside Hibernate?" +msgstr "" +"¿TreeCache puede ejecutar como un caché de segundo nivel dentro de " +"Hibernate? " + +#. Tag: para +#: TreeCache_FAQ.xml:47 +#, fuzzy, no-c-format +msgid "" +"Yes. Since Hibernate 3.0 release, you can configure it to use JBoss Cache as " +"a second level cache. For details, see Hibernate documentation, and also see " +"<ulink url=\"http://www.jboss.org/community/docs/DOC-10265\">this wiki page</" +"ulink>." +msgstr "" +"Sí. Desde el lanzamiento de Hibernate 3.0 puede configurarlo para que " +"utilice JBoss Cache (TreeCache) como un caché de segundo nivel. para obtener " +"más detalles consulte la documentación de Hibernate y también refiérase a " +"<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate\&... " +"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate </ulink>" + +#. Tag: para +#: TreeCache_FAQ.xml:52 +#, no-c-format +msgid "" +"JBoss Cache 3.x with MVCC in particular works very well as a Hibernate " +"second level cache." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:60 +#, fuzzy, no-c-format +msgid "What about using POJO Cache as a Hibernate cache?" +msgstr "¿Qué tal utilizar PojoCache como un caché Hibernate?" + +#. Tag: para +#: TreeCache_FAQ.xml:64 +#, fuzzy, no-c-format +msgid "" +"It is not necessary to use POJO Cache for second level cache inside " +"Hibernate because Hibernate manages fine-grained fields in Java objects. " +"Using POJO Cache won't provide any advantage, and will be an unnecessary " +"performance drawback." +msgstr "" +"No es necesario utilizar PojoCache para un caché de segundo nivel dentro de " +"Hibernate ya que Hibernate administra campos detallados en objetos Java. Así " +"que el utilizar PojoCache no proporcionará ninguna ventaja." + +#. Tag: para +#: TreeCache_FAQ.xml:74 +#, no-c-format +msgid "How can I configure JBoss Cache?" +msgstr "¿Cómo puedo configurar JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:78 +#, no-c-format +msgid "" +"You can configure the JBoss Cache through a configuration xml file or " +"programmatically using a <literal>org.jboss.cache.config.Configuration</" +"literal> object, passed in to the <literal>org.jboss.cache.CacheFactory</" +"literal> instance." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:90 +#, no-c-format +msgid "" +"Can I use a schema or DTD to validate my JBoss Cache configuration file?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:95 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, yes. An XSD schema is provided in your jbosscache-" +"core.jar file, and is also available online, on<ulink url=\"http://www.jboss." +"org/jbosscache/jbosscache-config-3.0.xsd\"> http://www.jboss.org/jbosscache/" +"jbosscache-config-3.0.xsd</ulink>. You can configure your IDE, text editor " +"or XML authoring tool to use this schema to validate your file." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:108 +#, no-c-format +msgid "What is the difference between the different cache modes?" +msgstr "¿Cuál es la diferencia entre los diferentes modos caché? " + +#. Tag: para +#: TreeCache_FAQ.xml:113 +#, no-c-format +msgid "" +"JBossCache has five different cache modes, i.e., <literal>LOCAL</literal> , " +"<literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> and <literal>INVALIDATION_ASYNC</" +"literal> . If you want to run JBoss Cache as a single instance, then you " +"should set the cache mode to <literal>LOCAL</literal> so that it won't " +"attempt to replicate anything. If you want to have synchronous replication " +"among different JBoss Cache instances, you set it to <literal>REPL_SYNC</" +"literal> . For asynchronous replication, use <literal>AYSNC_REPL</literal> . " +"If you do not wish to replicate cached data but simply inform other caches " +"in a cluster that data under specific addresses are now stale and should be " +"evicted from memory, use <literal>INVALIDATION_SYNC</literal> or " +"<literal>INVALIDTAION_ASYNC</literal> . Synchronous and asynchronous " +"behavior applies to invalidation as well as replication." +msgstr "" +"JBossCache tiene cinco modos caché diferentes, por ejemplo, <literal>LOCAL</" +"literal> , <literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> y <literal>INVALIDATION_ASYNC</" +"literal> . Si quiere ejecutar JBoss Cache como una sola instancia entonces " +"nececita configurar el modo del caché como <literal>LOCAL</literal> para que " +"no intente replicar nada. Si quiere tener una replicación sincrónica entre " +"diferentes instancias de JBoss Cache, entonces configúrelo como " +"<literal>REPL_SYNC</literal> . Para una replicación asincrónica, use " +"<literal>AYSNC_REPL</literal> . Si no quiere replicar datos en caché sino " +"simplemente informar otros cachés en un clúster que los datos bajo " +"direcciones especificas ya son viejos y por lo tanto se deben sacar de la " +"memoria, utilice <literal>INVALIDATION_SYNC</literal> o " +"<literal>INVALIDTAION_ASYNC</literal> . Los comportamientos sincrónico y " +"asincronico aplican a la invalidación así como a la replicación." + +#. Tag: para +#: TreeCache_FAQ.xml:143 +#, no-c-format +msgid "" +"Note that <literal>ASYNC_REPL</literal> and <literal>INVALIDATION_ASYNC</" +"literal> are non-blocking. This can be useful when you want to have another " +"JBoss Cache serving as a mirror or backup and you don't want to wait for " +"confirmation that this mirror has received your messages." +msgstr "" +"Observe que <literal>ASYNC_REPL</literal> y <literal>INVALIDATION_ASYNC</" +"literal> no-bloquean. Esto puede ser útil cuando quiere tener otro JBoss " +"Cache siviendo como espejo o copia de seguridad y no quiere esperar la " +"confirmación de que este espejo ha recibido sus mensajes." + +#. Tag: para +#: TreeCache_FAQ.xml:157 +#, no-c-format +msgid "How does JBoss Cache's replication mechanism work?" +msgstr "¿Cómo funciona el mecanismo de replicación de JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:161 +#, no-c-format +msgid "" +"JBoss Cache leverages <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"for network communications. A JGroups configuration section is present in " +"your JBoss Cache configuration." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:166 +#, fuzzy, no-c-format +msgid "" +"A user can configure the cluster of JBoss Cache instances by sharing the " +"same cluster name ( <literal>cluster name</literal> ). There is also an " +"option of whether to populate the cache data upon starting a new instance in " +"the <literal>ClusterConfig</literal> attribute." +msgstr "" +"JBoss Cache leverages <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"como capa de replicación. Un usuario puede configurar el clúster de " +"instancias de JBoss Cache al compartir el mismo nombre de clúster " +"( <literal>cluster name</literal> ). Tambié hay una opción de popular los " +"datos en caché a iniciar una nueva instancia en el atributo " +"<literal>ClusterConfig</literal>." + +#. Tag: para +#: TreeCache_FAQ.xml:178 +#, fuzzy, no-c-format +msgid "" +"Note that once all instances join the same replication group, every " +"replication change is propagated to all participating members. There is no " +"mechanism for sub-partitioning where some replication can be done within " +"only a subset of members, unless you use the Buddy Replication features. See " +"the Users' Guide for more details on this." +msgstr "" +"Observe que una vez que todas las instancias se unen al mismo grupo de " +"replicación, todo cambio en la replicación se propaga a todos los miembros " +"participantes. No hay mecanismo para realizar sub-particiones en donde " +"algunas replicas se pueden realizar dentro de sólo un subgrupo de miembros. " +"Esto se encuentra en nuestra lista de cosas por hacer. " + +#. Tag: para +#: TreeCache_FAQ.xml:190 +#, no-c-format +msgid "" +"I run a 2 node cluster. If the network dies, do the caches continue to run?" +msgstr "" +"Tengo un clúster de 2 nodos. Si la red se muere ¿los cachés continuan " +"ejecutando?" + +#. Tag: para +#: TreeCache_FAQ.xml:194 +#, no-c-format +msgid "" +"Yes, both will continue to run, but depending on your replication mode, all " +"transactions or operations may not complete. If <literal>REPL_SYNC</literal> " +"is used, operations will fail while if <literal>REPL_ASYNC</literal> is used " +"they will succeed. Even if they succeed though, caches will be out of sync." +msgstr "" +"Sí, ambos continuarán ejecutando, pero dependiendo de su modo de " +"replicación, puede que no todas las transacciones u operaciones se " +"completen. Si se utiliza <literal>REPL_SYNC</literal> las operaciones " +"fallarán mientras que si utiliza <literal>REPL_ASYNC</literal> las " +"operaciones serán exitosas. Incluso si tienen exito, los cachés no estarán " +"sincronizados. " + +#. Tag: para +#: TreeCache_FAQ.xml:207 +#, no-c-format +msgid "" +"Can I plug in library X instead of JGroups to handle remote calls and group " +"communications?" +msgstr "" +"¿Puedo conectar la biblioteca X en vez de JGroups para manejar llamadas " +"remotas y la comunicación de grupos? " + +#. Tag: para +#: TreeCache_FAQ.xml:212 +#, fuzzy, no-c-format +msgid "" +"At this stage the answer is no. We do have an abstraction layer between the " +"communication suite and JBoss Cache in the pipelines, and this may appear as " +"a feature at some stage in the future." +msgstr "" +"En este punto (JBoss Cache 1.x) la respuesta es no. Sí contamos con una capa " +"de abstracción entre la suite de comunicación y JBoss Cache en las tuberías " +"y puede que esta funcionalidad se agregue en algún momento en el futuro. " + +#. Tag: para +#: TreeCache_FAQ.xml:223 +#, no-c-format +msgid "" +"Does the cache need to replicate to every other instance in the cluster? " +"Isn't this slow if the cluster is large?" +msgstr "" +"¿El caché necesita replicarse en todas las instancias en el clúster? ¿Esto " +"no sería muy lento si el clúster es grande? " + +#. Tag: para +#: TreeCache_FAQ.xml:230 +#, fuzzy, no-c-format +msgid "" +"Replication need not occur to every node in the cluster. This feature - " +"called Buddy Replication - allows each node to pick one or more 'buddies' in " +"the cluster and only replicate to its buddies. This allows a cluster to " +"scale very easily with no extra impact on memory or network traffic with " +"each node added." +msgstr "" +"Desde JBoss Cache 1.4.0, no es necesario que la replicación tenga lugar en " +"todos los nodos en el clúster. Esta funcionalidad - llamada replicación de " +"compañero - le permite a cada nodo seleccionar uno o más 'compañeros' en el " +"clúster y sólo replica en su compañeros. Esto le permite al clúster escalar " +"fáiclmente sin un impacto extra en la memoria o en el tráfico de red con " +"cada nodo añadido." + +#. Tag: para +#: TreeCache_FAQ.xml:237 +#, fuzzy, no-c-format +msgid "" +"See the Users' Guide for more information on Buddy Replication, and how it " +"can be used to achieve very high scalability." +msgstr "" +"Consulte el manual del usuario para obtener mayor información sobre la " +"replicación de compañeros y la manera que se puede utilizar para lograr una " +"alta escalabilidad. " + +#. Tag: para +#: TreeCache_FAQ.xml:248 +#, no-c-format +msgid "" +"I'm using Buddy Replication. Do I need to have some form of session affinity?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:251 +#, no-c-format +msgid "" +"Session affinity relates to returning to the same cache instance for the " +"same data being used. While this is strictly not a requirement for Buddy " +"Replication, it is greatly recommended to minimize moving state around a " +"cluster." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:261 +#, fuzzy, no-c-format +msgid "" +"If I have the need for different configuration properties (e.g., " +"<literal>CacheMode</literal> and <literal>IsolationLevel</literal> ), do I " +"simply need to create multiple <literal>org.jboss.cache.Cache</literal> " +"instances with the appropriate configuration?" +msgstr "" +"Si necesito diferentes propiedades TreeCache (por ejemplo, " +"<literal>CacheMode</literal> y <literal>IsolationLevel</literal> ), necesito " +"simplemente crear múltiples instancias TreeCache con la configuración " +"apropiada?" + +#. Tag: para +#: TreeCache_FAQ.xml:272 +#, fuzzy, no-c-format +msgid "" +"Yes. All the above mentioned properties are per cache instance. Therefore " +"you will need separate <literal>org.jboss.cache.Cache</literal> instances." +msgstr "" +"Sí. Todas las porpiedades mencionadas anteriormente son por cada instancia " +"de caché. Por lo tanto necesitará una instancia JBoss Cache por separado. " + +#. Tag: para +#: TreeCache_FAQ.xml:282 +#, no-c-format +msgid "" +"Isn't this expensive from a networking standpoint, i.e., needing to create " +"sockets for each <literal>org.jboss.cache.Cache</literal> instance?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:289 +#, no-c-format +msgid "" +"Yes, it can be. For such cases it is recommended that you configure your " +"cache using the JGroups Multiplexer, which allows several caches to share a " +"single JGroups channel. Please see the Users' Guide for details on how to " +"configure the JGroups Multiplexer." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:296 +#, no-c-format +msgid "" +"A faster and more efficient approach is to use a shared transport in " +"JGroups. Please see <ulink url=\"http://www.jgroups.org\">the JGroups " +"documentation</ulink> for more details on how to do this." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:307 +#, fuzzy, no-c-format +msgid "" +"Does the <literal>ClusterName</literal> configuration element have any " +"relation to the JBoss AS cluster <literal>PartitionName</literal> ?" +msgstr "" +"La configuración <literal>ClusterName</literal> de Tree Cache tiene alguna " +"relación con el <literal>PartitionName</literal> del clúster de JBoss AS?" + +#. Tag: para +#: TreeCache_FAQ.xml:317 +#, no-c-format +msgid "" +"Yes. They are both JGroups group names. Besides the notion of a channel in " +"JGroups, it also can partition the channel into different group names." +msgstr "" +"Sí. Ambos son nombres de grupo JGroups. Además de la noción de canal en " +"JGroups, también puede realizar particiones en el canal en diferentes " +"nombres de grupos. " + +#. Tag: para +#: TreeCache_FAQ.xml:326 +#, fuzzy, no-c-format +msgid "" +"When using multiple JGroups based components [cluster-service.xml, cache " +"(multiple instances)], what is the correct/valid way to configure those " +"components to make sure my multicast addresses don't conflict?" +msgstr "" +"Al utilizar múltiples componentes basados en JGroups [cluster-service.xml, " +"treecache (multiple instances)], ¿cuál es la manera correcta/válida para " +"configurar esos componentes para asegurarme de que esas direcciones " +"multicast no entren en conflicto? " + +#. Tag: para +#: TreeCache_FAQ.xml:334 +#, no-c-format +msgid "" +"There are two parameters to consider: multicast address (plus port) and the " +"group name. At minimum, you will have to run components using a different " +"group name. But whether to run them on the same channel depends upon whether " +"the communication performance is critical for you or not. If it is, then " +"it'd be best to run them on different channels." +msgstr "" +"Hay dos parámetros que se deben tomar en consideración: dirección multicast " +"(más el puerto) y el nombre del grupo. Como mínimo tendrá que ejecutar " +"componentes utilizando un nombre de grupo diferente. El ejecutarlos en el " +"mismo canal depende de si el rendimiento de la comunicación es crítico para " +"usted o no. Si sí lo es entonces sería mejor ejecutarlos en canales " +"diferentes. " + +#. Tag: para +#: TreeCache_FAQ.xml:346 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache persistence storage?" +msgstr "" +"¿Actualmente JBoss Cache soporta el almacenamiento de persistencia en caché?" + +#. Tag: para +#: TreeCache_FAQ.xml:352 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache has a cache loader interface that supports cache " +"persistence. See below for more FAQs on cache loaders." +msgstr "" +"Sí. Desde el lanzamiento 1.1, JBoss Cache tiene una interfaz CacheLoader que " +"soporta la persistencia de caché. Vea a continuación. " + +#. Tag: para +#: TreeCache_FAQ.xml:360 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache passivation/ overflow to a data store?" +msgstr "" +"¿Actualmente JBoss Cache soporta el caché pasivo/en exceso en un " +"almacenamiento de datos?" + +#. Tag: para +#: TreeCache_FAQ.xml:366 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache uses the cache loader to support cache passivation/ " +"overflow. See documentation on how to configure and use this feature." +msgstr "" +"Sí. Desde el lanzamiento 1.2.4, JBoss Cache ustiliza el CacheLoader para " +"soportar el caché pasivo/en exceso. Consulte la documentación para aprender " +"cómo configurar y utilizar esta funcionalidad. " + +#. Tag: para +#: TreeCache_FAQ.xml:375 +#, no-c-format +msgid "Is JBoss Cache thread safe?" +msgstr "¿JBoss Cache es seguro con hilos?" + +#. Tag: para +#: TreeCache_FAQ.xml:379 +#, no-c-format +msgid "Yes, it is thread safe." +msgstr "Sí, es seguro con hilos. " + +#. Tag: para +#: TreeCache_FAQ.xml:385 +#, no-c-format +msgid "Does JBoss Cache support XA (2PC) transactions now?" +msgstr "¿Ahora JBoss Cache soporta transacciones XA (2PC)?" + +#. Tag: para +#: TreeCache_FAQ.xml:389 +#, fuzzy, no-c-format +msgid "" +"No, although it is also on our to do list. Our internal implementation does " +"use a procedure similar to 2PC to coordinate a transactions among different " +"instances, but JBoss Cache is not an XA resource." +msgstr "" +"No aunque también se encuentra en nuestra lista de cosas por hacer. Nuestra " +"implementación interna utiliza un procedimiento 2PC similar para coordinar " +"una transacción entre diferentes instancias. " + +#. Tag: para +#: TreeCache_FAQ.xml:398 +#, fuzzy, no-c-format +msgid "Which transaction managers are supported by JBoss Cache?" +msgstr "¿Qué TransactionManagers son soportados por JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:404 +#, no-c-format +msgid "" +"JBoss Cache supports any TransactionManager that is <ulink url=\"http://java." +"sun.com/products/jta/\">JTA</ulink> compliant such as<ulink url=\"http://www." +"jboss.org/jbosstm/\">JBoss Transactions</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:408 +#, no-c-format +msgid "" +"While JBoss Cache does ships with a dummy transaction manager (<literal>org." +"jboss.cache.transaction.DummyTransactionManager</literal>), we do " +"<emphasis>not</emphasis> recommend using this for production. It is not " +"thread safe, and is intended for internal testing only." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:421 +#, no-c-format +msgid "How do I set up the cache to be transactional?" +msgstr "¿Cómo configuro el caché para que sea transaccional?" + +#. Tag: para +#: TreeCache_FAQ.xml:425 +#, fuzzy, no-c-format +msgid "" +"You either use the default transaction manager that ships with JBoss AS or " +"you have to implement the <literal>org.jboss.cache.transaction." +"TransactionManagerLookup</literal> interface, and return an instance of your " +"<literal>javax.transaction.TransactionManager</literal> implementation. The " +"configuration property <literal>TransactionManagerLookupClass</literal> " +"defines the class to be used by the cache to fetch a reference to a " +"transaction manager. It is trivial to implement this interface to support " +"other transaction managers. Once this attribute is specified, the cache will " +"look up the transaction context from this transaction manager." +msgstr "" +"Puede utilizar el TransactionManager predeterminado (JBoss) para ejecutar " +"JBossCache dentro de JBoss o tiene que implementar la interfaz " +"<literal>TransactionManagerLookup</literal> y retornar una instancia de su " +"javax.transaction.TransactionManager. La propiedad de configuración " +"<literal>TransactionManagerLookupClass</literal> define la clase que el " +"caché debe utilizar para buscar una referencia en un TransactionManager. Es " +"trivial el implementar esta clase para soportar otros TransactionManagers. " +"Una vez este atributo se especifique entonces el caché buscará el contexto " +"de transacción desde este administrador de transacciones." + +#. Tag: para +#: TreeCache_FAQ.xml:441 +#, no-c-format +msgid "" +"The <literal>org.jboss.cache.transaction.GenericTransactionManagerLookup</" +"literal> class that ships with JBoss Cache is able to detect and bind to " +"most popular transaction managers. See the " +"<literal>GenericTransactionManagerLookup</literal> javadocs for more " +"information." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:454 +#, no-c-format +msgid "How do I control the cache locking level?" +msgstr "¿Cómo puedo controlar el nivel de bloqueo del caché?" + +#. Tag: para +#: TreeCache_FAQ.xml:458 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache lets you control the cache locking level through the transaction " +"isolation level. This is configured through the attribute " +"<literal>IsolationLevel</literal> . The transaction isolation levels " +"correspond to database isolation levels, namely, <literal>NONE</literal> , " +"<literal>READ_UNCOMMITTED</literal> , <literal>READ_COMMITTED</literal> , " +"<literal>REPEATABLE_READ</literal> , and <literal>SERIALIZABLE</literal> . " +"Note that these isolation levels are ignored if optimistic locking is used. " +"For details, please refer to the user manual." +msgstr "" +"JBossCache le permite controlar el nivel de bloqueo del caché por medio del " +"nivel de aislamiento de transacciones. Esto se configura por medio del " +"atributo <literal>IsolationLevel</literal> . Actualmente, JBossCache emplea " +"el bloqueo pesimista internamente.El nivel de aislamiento de transacciones " +"desde el bloqueo pesimista corresponde a los niveles de aislamiento JDBC, a " +"saber, <literal>NONE</literal> , <literal>READ_UNCOMMITTED</literal> , " +"<literal>READ_COMMITTED</literal> , <literal>REPEATABLE_READ</literal> y " +"<literal>SERIALIZABLE</literal> . Observe que los niveles de aislamiento se " +"ignoran si se está utilizando un bloqueo optimista. Para obtener mayores " +"detalles consulte el manual del usuario." + +#. Tag: para +#: TreeCache_FAQ.xml:480 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, when using the MVCC locking scheme, only " +"<literal>READ_COMMITTED</literal> and <literal>REPEATABLE_READ</literal> are " +"supported. Any other isolation level provided will either be upgraded or " +"downgraded accordingly." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:493 +#, no-c-format +msgid "How does JBoss Cache lock data for concurrent access?" +msgstr "¿Cómo hace JBoss Cache para bloquear datos para acceso simultáneo?" + +#. Tag: para +#: TreeCache_FAQ.xml:497 +#, fuzzy, no-c-format +msgid "" +"In JBoss Cache 2.x, by default pessimistic locking is used to lock data " +"nodes, based on the isolation level configured. We also offer optimistic " +"locking to allow for greater concurrency at the cost of slight processing " +"overhead and performance. See the documentation for a more detailed " +"discussion on concurrency and locking in JBoss Cache." +msgstr "" +"Por defecto JBoss Cache utiliza el bloqueo pesimista para bloquear nodos de " +"datos con base en el nivel a aislamiento configurado. Desde JBoss Cache " +"1.3.0, también ofrecemos el bloqueo optimista para permitir una mayor " +"simultaneidad con un pequeño costo en el procesamiento y en el rendimeinto. " +"Consulte la documentación y allí encontrará una discusión más detallada " +"sobre concurrencia y bloqueo en JBoss Cache." + +#. Tag: para +#: TreeCache_FAQ.xml:505 +#, no-c-format +msgid "" +"In JBoss Cache 3.x, optimistic and pessimistic locking are deprecated in " +"favour of MVCC (multi-version concurrency control), which is far more " +"efficient than either optimistic or pessimistic locking. For a detailed " +"discussion on our MVCC implementation, see <ulink url=\"http://jbosscache." +"blogspot.com/2008/07/mvcc-has-landed.html\">this blog entry</ulink> " +"and<ulink url=\"http://www.jboss.org/community/docs/DOC-10272\">this wiki " +"page</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:520 +#, fuzzy, no-c-format +msgid "How do I enable Optimistic Locking or MVCC in JBoss Cache?" +msgstr "¿Cómo habilito el bloqueo optimista en JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:524 +#, no-c-format +msgid "Please see the configuration section of the Users' Guide for details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:532 +#, no-c-format +msgid "Can I use the cache locking level even without a transaction context?" +msgstr "" +"¿Puedo utilizar el nivel de bloqueo de caché incluso sin un contexto " +"transaccional? " + +#. Tag: para +#: TreeCache_FAQ.xml:538 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache controls the individual node locking behavior through the " +"isolation level semantics. This means even if you don't use a transaction, " +"you can specify the lock level via isolation level. You can think of the " +"node locking behavior outside of a transaction as if it is under transaction " +"with <literal>auto_commit</literal> on." +msgstr "" +"Sí. JBossCache controla el comportamiento de bloqueo individual de nodos por " +"medio de la semántica a nivel de aislamiento. Esto significa que incluso si " +"no utiliza una transacción puede especificar el nivel de bloqueo por medio " +"del nivel de aislamiento. Puede considerar el comportamiento de bloqueo de " +"nodos por fuera de una transacción como si se encontrara bajo una " +"transacción con el <literal>auto_commit</literal> funcionando." + +#. Tag: para +#: TreeCache_FAQ.xml:551 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache support <literal>SELECT FOR UPDATE</literal> semantics?" +msgstr "¿JBoss Cache soporta <literal>Region</literal> ?" + +#. Tag: para +#: TreeCache_FAQ.xml:559 +#, no-c-format +msgid "" +"Yes, but this is is only possible if you are running within a JTA " +"transaction <emphasis>and</emphasis> are using either <literal>MVCC</" +"literal> or <literal>PESSIMISTIC</literal> as your node locking scheme." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:568 +#, no-c-format +msgid "To achieve <literal>SELECT FOR UPDATE</literal> semantics, simply do:" +msgstr "" + +#. Tag: programlisting +#: TreeCache_FAQ.xml:573 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" // start transaction ... \n" +"\n" +" cache.getInvocationContext().getOptionOverrides().setForceWriteLock" +"(true);\n" +" Node n = cache.get(\"/a/b/c\"); // this acquires a WRITE LOCK on this " +"node\n" +" ...\n" +" ...\n" +"\n" +" // end transaction\n" +"\n" +" ]]>" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:579 +#, no-c-format +msgid "" +"With replication (REPL_SYNC/REPL_ASYNC) or invalidation (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), how often does the cache broadcast messages over the " +"network?" +msgstr "" +"Con replicación (REPL_SYNC/REPL_ASYNC) o invalidación (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), ¿con que frecuencia el caché emite mensajes en la red?" + +#. Tag: para +#: TreeCache_FAQ.xml:586 +#, fuzzy, no-c-format +msgid "" +"If the updates are under transaction, then the broadcasts happen only when " +"the transaction is about to commit (actually during the prepare stage " +"internally). That is, it will be a batch update. However, if the operations " +"are not under transaction context, then each update will trigger " +"replication. Note that this has performance implications if network latency " +"is a problem." +msgstr "" +"Si las actualizaciones se encuentran bajo una transacción entonces las " +"emisiones sólo tienen lugar cuando la transacción está a punto de guardar " +"los cambios (de hecho durante la fase de preparación internamente). Es " +"decir, será una actualización en grupo. Sin embargo, si las operaciones no " +"se encuentran bajo el contexto de transacción entonces cada actualización " +"disparará la replicación. Observe que esto conlleva implicaciones en el " +"rendimiento si el transporte de una red es pesado (usualmente lo es). " + +#. Tag: para +#: TreeCache_FAQ.xml:598 +#, no-c-format +msgid "How can I do a mass removal?" +msgstr "¿Cómo puedo realizar una eliminación en masa? " + +#. Tag: para +#: TreeCache_FAQ.xml:602 +#, fuzzy, no-c-format +msgid "" +"If you do a<literal>cache.removeNode(\"/myroot\")</literal>, it will " +"recursively remove all the entries under \"/myroot\"." +msgstr "" +"Si realiza cache.remove(\"/root\"), eliminará recursivamente todas las " +"entradas bajo \"/root\"." + +#. Tag: para +#: TreeCache_FAQ.xml:610 +#, no-c-format +msgid "Can I monitor and manage the JBoss Cache?" +msgstr "¿Puedo monitorear y administrar el JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:614 +#, fuzzy, no-c-format +msgid "" +"Yes, using a JMX console such as the one shipped with JBoss AS or Java 5's " +"<literal>jconsole</literal> utility. See the chapter titled <emphasis role=" +"\"bold\">Management Information</emphasis> in the JBoss Cache Users' Guide " +"for more details." +msgstr "" +"Con JBoss Cache 1.3.0 lo puede hacer si está ejecutando JBoss Cache dentro " +"de JBoss AS o si está utilizando la utilidad <literal>jconsole</literal> de " +"JDK 5.0. Consulte el capítulo titulado <emphasis role=\"bold\">Management " +"Information</emphasis> en el manual del usuario de JBoss Cache para obtener " +"más detalles." + +#. Tag: para +#: TreeCache_FAQ.xml:625 +#, no-c-format +msgid "" +"JBoss Cache uses a <literal>:</literal> character in its object name. This " +"causes problems with my MBean server. What can I do about it?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:633 +#, no-c-format +msgid "" +"This is something we have seen with some MBean servers. By default, JBoss " +"Cache uses <literal>jboss.cache:service=JBossCache</literal> as a prefix to " +"all objects it binds in JMX. To work around this, use the <literal>-" +"Djbosscache.jmx.prefix</literal> JVM parameter to pass in an alternate " +"prefix." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:647 +#, fuzzy, no-c-format +msgid "Can I disable JBoss Cache management attributes?" +msgstr "" +"¿Puedo deshabilitar los atributos de administración de JBoss Cache en JBoss " +"Cache 1.3.0?" + +#. Tag: para +#: TreeCache_FAQ.xml:651 +#, no-c-format +msgid "" +"Yes, you can. See the section on configuration in the JBoss Cache Users' " +"Guide." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:658 +#, no-c-format +msgid "What happened to jboss-serialization.jar?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:662 +#, no-c-format +msgid "" +"As of JBoss Cache 2.0.0, the dependency on JBoss Serialization has been " +"dropped since most of the benefits of JBoss Serialization are available in " +"updated Java 5 VMs. Since JBoss Cache 2.0.0 is baselined on Java 5, there " +"was no need to provide these benefits separately." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:673 +#, no-c-format +msgid "Does JBoss Cache support partitioning?" +msgstr "¿JBoss Cache soporta particionamientos?" + +#. Tag: para +#: TreeCache_FAQ.xml:677 +#, no-c-format +msgid "" +"Not right now. JBoss Cache does not support partitioning that a user can " +"configure to have different set of data residing on different cache " +"instances while still participating as a replication group." +msgstr "" +"Por ahora no. JBoss Cache no soporta particionamientos que un usuario puede " +"configurar para tener diferentes grupos de datos residiendo en diferentes " +"instancias caché y al mismo tiempo participando como un grupo de replicación." + +#. Tag: para +#: TreeCache_FAQ.xml:682 +#, no-c-format +msgid "" +"This is on the roadmap though, so do keep an eye on <ulink url=\"http://jira." +"jboss.org/jira/browse/JBCACHE-60\">JBCACHE-60</ulink> if you are interested." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:692 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache handle the concept of application classloading inside, say, " +"a Java EE container?" +msgstr "" +"¿JBoss Cache maneja el concepto de la aplicación de carga de clase dentro de " +"digamos, un contendor J2EE?" + +#. Tag: para +#: TreeCache_FAQ.xml:698 +#, fuzzy, no-c-format +msgid "" +"Application-specific classloading is used widely inside a Java EE container. " +"For example, a web application may require a new classloader to scope a " +"specific version of the user library. However, by default JBoss Cache is " +"agnostic to the classloader. In general, this leads to two kinds of problems:" +msgstr "" +"La carga de clase especifica a la aplicación se utiliza bastante dentro de " +"un contenedor J2EE. Por ejemplo, una aplicación web puede requerir un nuevo " +"cargador de clase para poner en ámbito una versión especifica de la " +"biblioteca del usuario. Sin embargo, por defecto JBoss Cache es agnóstico " +"para el cargador de clase. En general, esto conlleva dos clases de problemas:" + +#. Tag: para +#: TreeCache_FAQ.xml:707 +#, no-c-format +msgid "" +"Object instance is stored in cache1 and replicated to cache2. As a result, " +"the instance in cache2 is created by the system classloader. The replication " +"may fail if the system classloader on cache2 does not have access to the " +"required class. Even if replication doesn't fail, a user thread in cache2 " +"may not be able to access the object if the user thread is expecting a type " +"defined by the application classloader." +msgstr "" +"La instancia del objeto se almacena en el cache1 y la réplica en cache2. " +"Como consecuencia, el cargador de clase del sistema crea la instancia en " +"cache2. Puede que la replicación falle si el cargador de clase del sistema " +"en cache2 no tiene acceso a la clase requerida. Inclusive si la replicación " +"no falla, puede que un hilo de usuario en cache2 no pueda acceder al objeto " +"si el hilo del usuario está esperando un tipo definido por el cargador de " +"clase. " + +#. Tag: para +#: TreeCache_FAQ.xml:718 +#, fuzzy, no-c-format +msgid "" +"Object instance is created by thread 1 and will be accessed by thread 2 " +"(with two different classloaders). JBoss Cache has no notion of the " +"different classloaders involved. As a result, you will have a " +"<literal>ClassCastException</literal> . This is a standard problem in " +"passing an object from one application space to another; JBoss Cache just " +"adds a level of indirection in passing the object." +msgstr "" +"La instancia del objeto es creada por el hilo 1 y será accedida por el hilo " +"2 (con dos cargadores de clase diferentes). JBossCache no tiene noción de " +"los diferentes cargadores de clase involucrados. Como consecuencia, se " +"presentará una <literal>ClassCastException</literal>. Este es un problema " +"estándar al pasar un objeto del espacio de una aplicación a otro; JBossCache " +"simplemente añade un nivel de indirección al pasar el objeto. " + +#. Tag: para +#: TreeCache_FAQ.xml:731 +#, fuzzy, no-c-format +msgid "" +"To solve the first kind of issue JBoss Cache uses a " +"<literal>CacheMarshaller</literal> . Basically, this allows application code " +"to register a classloader with a portion of the cache tree for use in " +"handling objects replicated to that portion. See the " +"<literal>CacheMarshaller</literal> section of the Users' Guide for more " +"details." +msgstr "" +"Para solucionar esta primera clase de problema, en JBoss Cache 1.2.4 " +"introdujimos el concepto de un <literal>TreeCacheMarshaller</literal> . " +"Básicamente, esto le permite al código de aplicación el registrar un " +"cargador de clase con una parte del arbol caché para utilizarlo al manejar " +"objetos replicados en esa parte. Consulte la sección sobre " +"TreeCacheMarshaller del manual del usuario para obtener más detalles. " + +#. Tag: para +#: TreeCache_FAQ.xml:742 +#, no-c-format +msgid "" +"To solve the second kind of issue, you can use the the " +"<literal>UseLazyDeserialization</literal> configuration option in JBoss " +"Cache, which wraps your objects in a <literal>Marshalledvalue</literal> " +"wrapper. The <literal>MarshalledValue</literal> serializes and deserializes " +"your object on demand, ensuring the proper thread local context class loader " +"is used each time." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:757 +#, no-c-format +msgid "" +"Does JBoss Cache currently support pre-event and post-event notification?" +msgstr "" +"¿Actualmente JBoss Cache soporta la notificación de pre-eventos y post-" +"eventos?" + +#. Tag: para +#: TreeCache_FAQ.xml:763 +#, no-c-format +msgid "" +"Yes. A boolean is passed in to each notification callback identifying " +"whether the callback is before or after the event. See the <literal>org." +"jboss.cache.notifications.annotations.CacheListener</literal> annotation for " +"details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:774 +#, fuzzy, no-c-format +msgid "How do I implement a custom listener to listen to cache events?" +msgstr "" +"¿Cómo puedo implementar un escucha personalizado para que escuche los " +"eventos <literal>TreeCache</literal> events?" + +#. Tag: para +#: TreeCache_FAQ.xml:780 +#, no-c-format +msgid "See the Users' Guide on this subject." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:788 +#, fuzzy, no-c-format +msgid "" +"Can I use <literal>UseRegionBasedMarshalling</literal> attribute in JBoss " +"Cache in order to get around ClassCastExceptions happening when accessing " +"data in the cache that has just been redeployed?" +msgstr "" +"¿Puedo utilizar el atributo <literal>useRegionBasedMarshalling</literal> en " +"JBoss Cache con el fin de evitar ClassCastExceptions al acceder datos en el " +"caché que acaba de ser redesplegado?" + +#. Tag: para +#: TreeCache_FAQ.xml:797 +#, fuzzy, no-c-format +msgid "" +"Yes, you can. Originally, cache Marshalling was designed as a workaround for " +"those replicated caches that upon state transfer did not have access to the " +"classloaders defining the objects in the cache." +msgstr "" +"Sí, si puede. Originalmente, <literal>TreeCache</literal> Marshalling fue " +"diseñado como una solución opcional para aquellos cachés replicados que en " +"estado de transferencia no tenían acceso a los cargadores de clase que " +"definen los objetos en el caché. " + +#. Tag: para +#: TreeCache_FAQ.xml:802 +#, no-c-format +msgid "" +"On each deployment, JBoss creates a new classloader per the top level " +"deployment artifact, for example an EAR. You also have to bear in mind that " +"a class in an application server is defined not only by the class name but " +"also its classloader. So, assuming that the cache is not deployed as part of " +"your deployment, you could deploy an application and put instances of " +"classes belonging to this deployment inside the cache. If you did a " +"redeployment and try to do a get operation of the data previously put, this " +"would result on a ClassCastException. This is because even though the class " +"names are the same, the class definitions are not. The current classloader " +"is different to the one when the classes were originally put." +msgstr "" +"En cada despliegue, JBoss crea un nuevo cargador de clase por cada artefacto " +"de despliegue a nivel superior, por ejemplo un EAR. También tiene que tener " +"en cuenta que una clase en un servidor de aplicaciones está definido no sólo " +"por el nombre de la clase sino también por su cargador de clase. Así que " +"asumiendo que el caché no es desplegado como parte de su implementación, " +"podría implementar una aplicación y poner instancias de clases " +"pertenecientes a este despliegue dentro del caché. Si realizara una re-" +"implementación y si tratara de realizar una operación get de los datos que " +"previamente se incluyeron, esto generaría una ClassCastException. Esto se " +"debe a que aunque los nombres de las clases son los mismos, las definiciones " +"de clase no lo son. El cargador de clase actual es diferente al que se " +"utilizó cuando originalmente se pusieron las clases. " + +#. Tag: para +#: TreeCache_FAQ.xml:817 +#, fuzzy, no-c-format +msgid "" +"By enabling marshalling, you can control the lifecycle of the data in the " +"cache and if on undeployment, you deactivate the region and unregister the " +"classloader that you'd have registered on deployment, you'd evict the data " +"in the cache locally. That means that in the next deployment, the data won't " +"be in the cache, therefore avoiding the problem. Obviously, using " +"marshalling to get around this problem is only recommended when you have " +"some kind of persistence backing where the data survives, for example using " +"CacheLoaders, or when JBoss Cache is used as a second level cache in a " +"persistence framework." +msgstr "" +"Al habilitar el marshalling, puede controlar el ciclo de vida de los datos " +"en el caché o si lo va a borrar, puede inactivar la región y des-registrar " +"el cargador de clase que habría registrado en el despliegue y sacaría los " +"datos en el caché localmente. Eso significa que en el próximo despliegue, " +"los datos no estarán en el caché y por lo tanto se evitará el problema. " +"Obviamente, el utilizar marshalling para evitar este problema sólo se " +"recomienda cuando tenga alguna clase de persistencia respaldando en donde " +"los datos sobreviven, por ejemplo, utilizando CacheLoaders, o cuando " +"JBossCache se utiliza como caché de segundo nivel en un marco de trabajo de " +"persistencia. " + +#. Tag: para +#: TreeCache_FAQ.xml:830 +#, fuzzy, no-c-format +msgid "" +"To implement this feature, please follow the instructions indicated in the " +"example located in the CacheMarshaller section of the Users' Guide. It's " +"worth noting that instead of a <literal>ServletContextListener</literal> , " +"you could add this code into an <literal>MBean</literal> that contained " +"lifecycle methods, such as <literal>start()</literal> and <literal>stop()</" +"literal> . The key would be for this MBean to depend on the target cache, so " +"that it can operate as long as the cache is up and running." +msgstr "" +"Para implementar esta característica siga las instrucciones indicadas en el " +"ejemplo que se encuentra en la sección TreeCacheMarshaller del manual del " +"usuario. Vale la pena anotar que en vez de un " +"<literal>ServletContextListener</literal>, podría añadir este códido en un " +"<literal>MBean</literal> que contenía métodos de ciclos de vida, tal como " +"<literal>start()</literal> y <literal>stop()</literal>. La clave sería que " +"este MBean dependiera del caché destino de manera que pueda operar en tanto " +"el caché se encuentre funcionando. " Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Troubleshooting.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Troubleshooting.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/es-ES/Troubleshooting.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,40 @@ +# translation of Colophon.po to +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-10-16 13:39+1000\n" +"Last-Translator: Angela Garcia\n" +"Language-Team: <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Troubleshooting.xml:6 +#, no-c-format +msgid "Troubleshooting" +msgstr "Resolución de problemas" + +#. Tag: para +#: Troubleshooting.xml:11 +#, no-c-format +msgid "" +"I am having problems getting JBoss Cache to work, where can I get " +"information on troubleshooting?" +msgstr "" +"Tengo problemas en hacer funcionar JBoss Cache, ¿dónde puedo obtener " +"información sobre resolución de problemas?" + +#. Tag: para +#: Troubleshooting.xml:15 +#, fuzzy, no-c-format +msgid "" +"Troubleshooting section can be found in the following <ulink url=\"http://" +"www.jboss.org/community/docs/DOC-10288\">wiki link</ulink>." +msgstr "" +"La sección sobre resolución de problemas se puede encontrar en el siguiente " +"enlace wiki <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?" +"page=JBossCacheTroubleshooting\"></ulink> ." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Author_Group.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Author_Group.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Author_Group.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,20 @@ +# translation of Cache_Frequently_Asked_Questions.po to French +# Corina Roe <croe(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Cache_Frequently_Asked_Questions\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-14 15:57+1000\n" +"Last-Translator: Corina Roe <croe(a)redhat.com&gt;\n&quot; +"Language-Team: French <i18(a)redhat.com&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: firstname +#: Author_Group.xml:7 +#, no-c-format +msgid "Ben Wang, Bela Ban, Manik Surtani, Scott Marlow, Galder Zamarreño" +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Book_Info.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Book_Info.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Book_Info.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,41 @@ +# translation of Cache_Frequently_Asked_Questions.po to French +# Corina Roe <croe(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Cache_Frequently_Asked_Questions\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-14 15:57+1000\n" +"Last-Translator: Corina Roe <croe(a)redhat.com&gt;\n&quot; +"Language-Team: French <i18(a)redhat.com&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Book_Info.xml:5 +#, no-c-format +msgid "JBoss Cache Frequently Asked Questions" +msgstr "" + +#. Tag: subtitle +#: Book_Info.xml:6 +#, no-c-format +msgid "for Use with JBoss Enterprise Application Platform 5.0" +msgstr "" + +#. Tag: para +#: Book_Info.xml:12 +#, no-c-format +msgid "" +"This book is a compilation of frequently asked questions about JBoss Cache" +msgstr "" +"Cet ouvrage couvre les questions les plus fréquemment posées à propos de " +"JBoss Cache." + +#. Tag: holder +#: Book_Info.xml:24 +#, no-c-format +msgid "&HOLDER;" +msgstr "&HOLDER;" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/CacheLoader_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/CacheLoader_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/CacheLoader_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,370 @@ +# translation of Cache_Frequently_Asked_Questions.po to French +# Corina Roe <croe(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Cache_Frequently_Asked_Questions\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-14 15:57+1000\n" +"Last-Translator: Corina Roe <croe(a)redhat.com&gt;\n&quot; +"Language-Team: French <i18(a)redhat.com&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: CacheLoader_FAQ.xml:6 +#, no-c-format +msgid "Cache Loaders" +msgstr "Cache Loaders" + +#. Tag: para +#: CacheLoader_FAQ.xml:12 +#, fuzzy, no-c-format +msgid "What is a cache loader?" +msgstr "Qu'est-ce qu'un CacheLoader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:16 +#, fuzzy, no-c-format +msgid "" +"A cache loader is the connection of JBoss Cache to a (persistent) data " +"store. The cache loader is called by JBoss Cache to fetch data from a store " +"when that data is not in the cache, and when modifications are made to data " +"in the cache the Cache Loader is called to store those modifications back to " +"the store." +msgstr "" +"Un CacheLoader est la connexion de JBossCache à un store de données " +"(persistantes). JBossCache appelle CacheLoader pour collecter des données " +"d'un store quand elles ne sont pas dans le cache, et quand les modifications " +"sont faites dans le cache, le CacheLoader est appelé à récupérer ces " +"modifications dans le store." + +#. Tag: para +#: CacheLoader_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "" +"In conjunction with eviction policies, JBoss Cache with a cache loader " +"allows a user to maintain a bounded cache for a large backend datastore. " +"Frequently used data is fetched from the datastore into the cache, and the " +"least used data is evicted, in order to provide fast access to frequently " +"accessed data. This is all configured through XML, and the programmer " +"doesn't have to take care of loading and eviction." +msgstr "" +"En conjonction avec ces politiques d'éviction, JBossCache combiné à " +"CacheLoader, permet à un utilisateur de maintenir un cache borné pour un " +"grand backend datastore. Souvent, les données utilisées sont extraites du " +"datastore vers le cache, et les données les moins utilisées sont expulsées, " +"de manière à procurer un accès rapide aux données auxquelles on accède " +"souvent. Tout cela est configuré à travers XML, et le programmeur n'a pas " +"besoin de s'occuper du chargement ou de l'éviction." + +#. Tag: para +#: CacheLoader_FAQ.xml:32 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache currently ships with several cache loader implementations, " +"including:" +msgstr "" +"JBossCache est actuellement présenté avec plusieurs implémentations " +"CacheLoader, qui comprennent:" + +#. Tag: para +#: CacheLoader_FAQ.xml:37 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.FileCacheLoader</literal> : this " +"implementation uses the file system to store and retrieve data. JBoss Cache " +"nodes are mapped to directories, subnodes to subdirectories etc. Attributes " +"of a node are mapped to a data file inside the directory." +msgstr "" +"FileCacheLoader: cette implémentation utilise le système de fichiers pour " +"stocker et retirer les données. Les noeuds JbossCache sont mappés dans les " +"répertoires, sous-noeuds, sous-répertoires, etc.. Les attributs d'un noeud " +"sont mappés à un fichier <literal>data</literal> à l'intérieur d'un " +"répertoire." + +#. Tag: para +#: CacheLoader_FAQ.xml:49 +#, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.jdbm.JdbmCacheLoader</literal> : this " +"implementation is based on<ulink url=\"http://jdbm.sourceforge.net/\"> JDBM</" +"ulink>, an open source file-based transactional persistence engine." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:58 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.bdbje.BdbjeCacheLoader</literal> : this " +"implementation is based on the Oracle's Berkeley DB Java Edition database, a " +"fast and efficient transactional database. It uses a single file for the " +"entire store. Note that if you use the Berkeley DB cache loader with JBoss " +"Cache and wish to ship your product, you will have to acquire a <ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">commercial license from Oracle</" +"ulink>." +msgstr "" +"BdbjeCacheLoader: cette implémentation est basée sur la base de données " +"Sleepycat Java Edition, une bases de données transactionelle rapide et " +"efficace. Il utilise une seul fichier pour le store complet. Notez que si " +"vous utilisez Sleepycat'sCacheLoader en conjonction avec JBoss Cache et que " +"vous souhaitez distribuer votre produit, vous devrez acquérir une <ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">commercial license from " +"Sleepycat </ulink> ." + +#. Tag: para +#: CacheLoader_FAQ.xml:71 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.JDBCCacheLoader</literal> : this " +"implementation uses the relational database as the persistent storage." +msgstr "" +"JDBCCacheLoader: cette implementation utilise la base de données " +"relationnelle pour le stockage persistant. " + +#. Tag: para +#: CacheLoader_FAQ.xml:79 +#, fuzzy, no-c-format +msgid "" +"And more. See the chapter on cache loaders in the Users' Guide for more " +"details." +msgstr "Et davantage. Voir la documentation pour davantage d'informations." + +#. Tag: para +#: CacheLoader_FAQ.xml:88 +#, no-c-format +msgid "Is the FileCacheLoader recommended for production use?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:92 +#, no-c-format +msgid "" +"No, it is not. The FileCacheLoader has some severe limitations which " +"restrict its use in a production environment, or if used in such an " +"environment, it should be used with due care and sufficient understanding of " +"these limitations." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:99 +#, no-c-format +msgid "" +"Due to the way the FileCacheLoader represents a tree structure on disk " +"(directories and files) traversal is inefficient for deep trees." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:103 +#, no-c-format +msgid "" +"Usage on shared filesystems like NFS, Windows shares, etc. should be avoided " +"as these do not implement proper file locking and can cause data corruption." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:107 +#, no-c-format +msgid "" +"Usage with an isolation level of NONE can cause corrupt writes as multiple " +"threads attempt to write to the same file." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:111 +#, no-c-format +msgid "" +"File systems are inherently not transactional, so when attempting to use " +"your cache in a transactional context, failures when writing to the file " +"(which happens during the commit phase) cannot be recovered." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:120 +#, no-c-format +msgid "" +"As a rule of thumb, it is recommended that the FileCacheLoader not be used " +"in a highly concurrent, transactional or stressful environment, and its use " +"is restricted to testing." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:130 +#, fuzzy, no-c-format +msgid "Can writing to cache loaders be asynchronous?" +msgstr "Est-ce que CacheLoaders peut être asynchrone?" + +#. Tag: para +#: CacheLoader_FAQ.xml:134 +#, fuzzy, no-c-format +msgid "" +"Yes. Set the <literal>async</literal> attrobute to true. See the JBoss Cache " +"Users' Guide for a more detailed discussion. By default though, all cache " +"loader writes are synchronous and will block." +msgstr "" +"JbossCache 1.2.4, oui. Configurer la propriété de CacheLoaderAsynchronous " +"comme 'vrai'. Voir la documentation JBossCache pour une discussion plus " +"élaborée. Par défaut, toutes les écritures cache loader sont synchrones et " +"vont bloquer." + +#. Tag: para +#: CacheLoader_FAQ.xml:145 +#, fuzzy, no-c-format +msgid "Can I write my own cache loader ?" +msgstr "Puis-je écrire mon propre CacheLoader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:149 +#, fuzzy, no-c-format +msgid "" +"Yes. A cache loader is a class implementing <literal>org.jboss.cache.loader." +"CacheLoader</literal> or extending <literal>org.jboss.cache.loader." +"AbstractCacheLoader</literal> . It is configured via the XML file (see JBoss " +"Cache Users' Guide)." +msgstr "" +"Oui. Un CacheLoader est une classe qui implémente <literal>org.jboss.cache." +"loader.CacheLoader</literal> . C'est configuré par le fichier XML (voir " +"JBossCache et la documentation tutorielle)." + +#. Tag: para +#: CacheLoader_FAQ.xml:161 +#, fuzzy, no-c-format +msgid "Does a cache loader have to use a persistent store ?" +msgstr "Est-ce que le CacheLoader peut utiliser un store persistant?" + +#. Tag: para +#: CacheLoader_FAQ.xml:165 +#, fuzzy, no-c-format +msgid "" +"No, a cache loader could for example fetch (and possibly store) its data " +"from a webdav-capable webserver. Another example is a caching proxy server, " +"which fetches contents from the web. Note that an implementation of " +"CacheLoader may not implement the 'store' functionality in this case, but " +"just the 'load' functionality." +msgstr "" +"Non, un CacheLoader pourrait par exemple obtenir (et potentiellement " +"stocker) ses données d'un serveur Web capable-webdav. Un autre exemple est " +"un serveur proxy caching, qui va chercher son contenu sur le web. Notez " +"qu'une implémentation de CacheLoader n'implémente pas la fonctionnalité du " +"'store' dans ce cas, mais juste la fonctionnalité 'chargement'." + +#. Tag: para +#: CacheLoader_FAQ.xml:177 +#, fuzzy, no-c-format +msgid "Do I have to pay to use Oracle's Berkeley DB CacheLoader?" +msgstr "Dois-je payer quelque chose pour utiliser Sleepycat's CacheLoader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:181 +#, fuzzy, no-c-format +msgid "" +"Not if you use it only for personal use. As soon as you distribute your " +"product with BdbjeCacheLoader, you have to purchase a commercial license " +"from Oracle. See details at <ulink url=\"http://www.sleepycat.com/" +"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ." +msgstr "" +"Non, si vous l'utilisez uniquement pour votre usage personnel. Dès que vous " +"distribuez votre produit avec BdbjeCacheLoader, vous devrez acquérir une " +"licence commerciale pour Sleepycat. Voir davantage d'informations sur <ulink " +"url=\"http://www.sleepycat.com/jeforjbosscache\">http://www.sleepycat.com/" +"jeforjbosscache </ulink> ." + +#. Tag: para +#: CacheLoader_FAQ.xml:194 +#, no-c-format +msgid "Are there any tools available to monitor the Berkeley DB instance?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:198 +#, no-c-format +msgid "" +"Yes. Oracle ships a JMX-based monitoring tool, called <ulink url=\"http://" +"www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/" +"jmx/JEMonitor.html\"> JEMonitor </ulink> which can be downloaded from the " +"Oracle website." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:211 +#, no-c-format +msgid "" +"When tuning my Berkeley DB instance, where should I put my je.properties " +"file?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:215 +#, no-c-format +msgid "" +"<literal>je.properties</literal> should reside in your Berkeley DB home " +"directory. This is the directory you pass in to the BDBJECacheLoader's " +"<literal>location</literal> configuration property." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:227 +#, no-c-format +msgid "Can I use more than one cache loader?" +msgstr "Puis-je utiliser plus d'un cache loader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:231 +#, fuzzy, no-c-format +msgid "" +"Yes. Within the CacheLoaderConfiguration XML element (see Users' Guide " +"chapter on cache loaders) you can describe several cache loaders. The impact " +"is that the cache will look at all of the cache loaders in the order they've " +"been configured, until it finds a valid, non-null element of data. When " +"performing writes, all cache loaders are written to (except if the " +"ignoreModifications element has been set to true for a specific cache loader." +msgstr "" +"Avec JBossCache 1.3.0, oui. Avec le nouvel élément CacheLoaderConfiguration " +"XML (voir la section du manuel utilisateur sur les cache loaders), vous " +"pouvez maintenant décrire plusieurs cache loaders. L'impact, c'est que le " +"cache va scanner tous les cache loaders dans l'ordre dans lequel ils ont été " +"configurés, jusqu'à ce qu'il trouve une donnée valide non nulle. En " +"écriture, tous les cache loader sont écrits (sauf si l'élément " +"ignoreModifications a été paramétré à 'vrai' pour un cache loader " +"spécifique)." + +#. Tag: para +#: CacheLoader_FAQ.xml:245 +#, no-c-format +msgid "" +"Can I migrate a JDBCacheLoader or FileCacheLoader based cache store " +"containing data formatted with JBoss Cache 1.x.x to JBoss Cache 2.0 format?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:250 +#, no-c-format +msgid "" +"Yes. See \"Transforming Cache Loaders\" section within the \"Cache Loaders\" " +"section located in the JBoss Cache Users' Guide." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:257 +#, no-c-format +msgid "Is the TCPDelegatingCacheLoader resilient to TCPCacheServer restarts?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:263 +#, no-c-format +msgid "" +"As of JBoss Cache 2.1.0, the answer is yes. See the Users' Guide for details " +"on how to configure and tune your retries and wait period for reestablishing " +"the TCP connection." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:269 +#, no-c-format +msgid "" +"Prior to that, restarting the TCPCacheServer would also mean restarting your " +"application that uses the cache." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Eviction_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Eviction_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Eviction_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,170 @@ +# translation of Cache_Frequently_Asked_Questions.po to French +# Corina Roe <croe(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Cache_Frequently_Asked_Questions\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-14 15:57+1000\n" +"Last-Translator: Corina Roe <croe(a)redhat.com&gt;\n&quot; +"Language-Team: French <i18(a)redhat.com&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Eviction_FAQ.xml:6 +#, no-c-format +msgid "Eviction Policies" +msgstr "Politiques d'éviction" + +#. Tag: para +#: Eviction_FAQ.xml:10 +#, no-c-format +msgid "Does JBoss Cache support eviction policies?" +msgstr "Est-ce que JBoss Cache supporte les politiques d'éviction?" + +#. Tag: para +#: Eviction_FAQ.xml:14 +#, no-c-format +msgid "" +"Yes. JBoss Cache currently supports multiple eviction policies such as LRU, " +"MRU, and FIFO. Users can also plug in their own eviction policy algorithms. " +"See user guide for details." +msgstr "" + +#. Tag: para +#: Eviction_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "Does JBoss Cache's eviction policy operates in replication mode?" +msgstr "" +"Est-ce que la politique d'éviction JBoss Cache LRU implémentée, opère en " +"mode de réplication?" + +#. Tag: para +#: Eviction_FAQ.xml:29 +#, no-c-format +msgid "Yes and no. :-)" +msgstr "Oui et non. :-)" + +#. Tag: para +#: Eviction_FAQ.xml:31 +#, fuzzy, no-c-format +msgid "" +"The eviction policy only operates in local mode. That is, nodes are only " +"evicted locally. This may cause the cache contents not to be synchronized " +"temporarily. But when a user tries to obtain the cached contents of an " +"evicted node and finds out that is null (e.g., <literal>get</literal> " +"returns null), it should get it from the other data source and re-populate " +"the data in the cache. During this moment, the node content will be " +"propagated and the cache content will be in sync." +msgstr "" +"La politique LRU opère uniquement en mode local. C'est à dire que les noeuds " +"ne sont évictés que localement. Cela peut entrainer que les contenus des " +"caches ne soient pas synchronisés temporairement. Mais quand un utilisateur " +"essaie d'obtenir les contenus cache d'un noeud évicté et découvre qu'ils " +"sont nuls (par ex. <literal>get</literal> retourne null), il doit l'obtenir " +"d'une autre source de données et doit re-populer les données dans le cache. " +"Pendant ce temps, le contenu du noeud sera propagé et le contenu du cache " +"sera synchronisé." + +#. Tag: para +#: Eviction_FAQ.xml:42 +#, no-c-format +msgid "" +"However, you still can run eviction policies with cache mode set to either " +"<literal>REPL_SYNC</literal> or <literal>REPL_ASYNC</literal> . Depending on " +"your use case, you can set multiple cache instances to have their own " +"eviction policy (which are applied locally) or just have selected instances " +"with eviction policies activated." +msgstr "" +"Cependant, vous pouvez toujours éxécuter des politiques d'éviction en mode " +"cache avec <literal>REPL_SYNC</literal> ou <literal>REPL_ASYNC</literal>. " +"Suivant vos habitudes d'utilisation, vous pouvez déterminer plusieurs " +"instances de cache multiple avec leur propre politique d'éviction (qui sont " +"applicables localement) ou sélectionnez des instances avec des politiques " +"d'éviction activées." + +#. Tag: para +#: Eviction_FAQ.xml:53 +#, no-c-format +msgid "" +"Also note that, with cache loader option, a locally evicted node can also be " +"persisted to the backend store and a user can retrieve it from the store " +"later on." +msgstr "" +"Aussi, notez qu'avec l'option chargeur cache, un noeud evicté localement " +"peut également demeurrer persistant dans le store backend et un utilisateur " +"peut le retirer du store plus tard." + +#. Tag: para +#: Eviction_FAQ.xml:62 +#, no-c-format +msgid "Does JBoss Cache support <literal>Region</literal> ?" +msgstr "Est-ce que JBoss Cache prend en charge <literal>Region</literal> ?" + +#. Tag: para +#: Eviction_FAQ.xml:69 +#, no-c-format +msgid "" +"Yes. JBoss Cache has the notion of region where a user can configure the " +"eviction policy parameters (e.g., <literal>maxNodes</literal> or " +"<literal>timeToIdleSeconds</literal> )" +msgstr "" +"Oui. JBoss Cache a la notion d'une région où l'utilisateur peut configurer " +"les para mètres de politique d'éviction (par ex. <literal>maxNodes</literal> " +"ou <literal>timeToIdleSeconds</literal> )" + +#. Tag: para +#: Eviction_FAQ.xml:77 +#, fuzzy, no-c-format +msgid "" +"A region in JBoss Cache denotes a portion of tree hierarchy, e.g., a fully " +"qualified name ( <literal>org.jboss.cache.Fqn</literal> ). For example, a " +"user can define <literal>/org/jboss</literal> and <literal>/org/foocom</" +"literal> as two separate regions. But note that you can configure the region " +"programmatically now, i.e., everything has to be configured through the xml " +"file." +msgstr "" +"Une région de JBoss Cache denote une portion de hiérarchie d'aborescence, " +"par ex. un nom de package ( <literal>FQN</literal> ). Ainsi, un utilisateur " +"peut distinguer <literal>/org/jboss</literal> et <literal>/org/foocom</" +"literal> en tant que deux régions séparées. Mais notez que vous pouvez " +"configurer la région pragrammatiquement maintenant, par ex., tout doit être " +"configuré par le fichier xml." + +#. Tag: para +#: Eviction_FAQ.xml:94 +#, no-c-format +msgid "" +"I have turned on the eviction policy, why do I still get \"out of memory" +"\" (OOM) exception?" +msgstr "" +"J'ai initié la politique d'éviction, pourquoi est-ce que je reçois toujours " +"l'exception \"out of memory\" (OOM) (manque de mémoire)?" + +#. Tag: para +#: Eviction_FAQ.xml:100 +#, fuzzy, no-c-format +msgid "" +"OOM can happen when the speed of cache access exceeds the speed of eviction " +"policy handling timer. Eviction policy handler will wake up every " +"<literal>wakeUpInterval</literal> milliseconds (or " +"<literal>wakeUpIntervalSeconds</literal> seconds, prior to 3.x) to process " +"the eviction event queue. So when the queue size is full, it will create a " +"backlog and cause out-of-memory exceptions to happen unless the eviction " +"timer catches up. To address this problem, in addition to increase the VM " +"heap size, you can also reduce the <literal>wakeUpInterval</literal> so the " +"timer thread processes the queue more frequently." +msgstr "" +"OOM peut survenir quand la vitesse d'accès cache dépasse la vitesse du " +"d'éviction. Le gestionnaire de la politique d'éviction se réveillera toutes " +"les <literal>wakeUpIntervalInSeconds</literal> secondes pour traiter la " +"queue d'événements d'évictions. Et la taille de la queue est maintenant " +"fixée à 20000. Ainsi, quand la taille de la queue atteint sa capacité " +"maximum, cela cause un backlog et un OOM à moins que le timer d'éviction ne " +"les rattrappe. Pour régler ce problème, en plus d'augmenter la taille VM " +"heap, vous pouvez également réduire <literal>wakeUpIntervaleInSeconds</" +"literal> de façon à ce que le thread puisse traiter la queue plus " +"fréquemment." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/General_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/General_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/General_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,167 @@ +# translation of Cache_Frequently_Asked_Questions.po to French +# Corina Roe <croe(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Cache_Frequently_Asked_Questions\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-14 15:57+1000\n" +"Last-Translator: Corina Roe <croe(a)redhat.com&gt;\n&quot; +"Language-Team: French <i18(a)redhat.com&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: General_FAQ.xml:6 +#, no-c-format +msgid "General Information" +msgstr "Informations générales" + +#. Tag: para +#: General_FAQ.xml:10 +#, no-c-format +msgid "What is JBoss Cache?" +msgstr "Qu'est-ce que JBoss Cache?" + +#. Tag: para +#: General_FAQ.xml:14 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache is a replicated and transactional cache. It is replicated since " +"multiple JBoss Cache instances can be distributed (either within the same " +"JVM or across several JVMs whether they reside on the same machine or on " +"different machines on a network) and data is replicated across the whole " +"group. It is transactional because a user can configure a <ulink url=" +"\"http://java.sun.com/products/jta/\">JTA</ulink> compliant transaction " +"manager and make any cache interaction transactional, and caches would " +"participate in ongoing JTA transactions. Note that the cache can also be run " +"without any replication; this is the local mode." +msgstr "" +"JBoss Cache est un cache transactionnel et dupliqué. Il est dupliqué depuis " +"que des instances multiples de JBoss Cache peuvent être distribuées (soit " +"avec les mêmes JVM ou à travers plusieurs JVM, qu'ils résident sur la même " +"machine, ou sur différentes machines du réseau) et des données sont " +"dupliquées à travers tout le groupe. C'est transactionnel car un utilisateur " +"peut configurer un gestionnaire de transactions conforme à JTA et rendre " +"l'opération cache transactionnelle. Notez que le cache peut également être " +"exécuté sans aucune duplication: c'est le mode local." + +#. Tag: para +#: General_FAQ.xml:28 +#, no-c-format +msgid "" +"JBoss Cache comes in two flavours: Core and POJO versions. The core library " +"(using the <literal>org.jboss.cache.Cache</literal> interface) is the " +"underlying library that organises data in a tree-like structure and handles " +"all locking, passivation, eviction and replication characteristics of data " +"in the cache. The POJO library (using the <literal>org.jboss.cache.pojo." +"PojoCache</literal> interface) is built atop the core library and allows " +"introspection of objects in the cache providing transparent coherence by " +"using JBoss AOP. Note that the POJO edition of JBoss Cache (often referred " +"to as POJO Cache) comes with a separate set of documentation (Users' Guide, " +"FAQ, etc.) available on the JBoss Cache <ulink url=\"http://www.jboss.org/" +"jbosscache/\">documentation website</ulink>." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:66 +#, no-c-format +msgid "Who are the JBoss Cache developers?" +msgstr "Qui sont les développeurs JBoss Cache?" + +#. Tag: para +#: General_FAQ.xml:70 +#, no-c-format +msgid "" +"JBoss Cache has an active community of developers and contributors. The " +"project was founded by Bela Ban and is currently led by Manik Surtani. Jason " +"Greene is the lead for the POJO Cache subsystem, and other contributors both " +"past and present include Ben Wang, Harald Gliebe, Brian Stansberry, Vladimir " +"Blagojevic, Mircea Markus, Jimmy Wilson, Galder Zamarreño and Elias Ross." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:139 +#, no-c-format +msgid "How do I know the version of JBoss Cache that I am using?" +msgstr "Comment puis-je savoir quelle version de JBoss Cache j'utilise?" + +#. Tag: para +#: General_FAQ.xml:143 +#, no-c-format +msgid "" +"<literal>java -jar jbosscache-core.jar</literal> will spit out version " +"details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:152 +#, fuzzy, no-c-format +msgid "" +"Can I run JBoss Cache outside of the JBoss Enterprise Application Platform?" +msgstr "" +"Puis-je exécuter un JBoss Cache en dehors d'un serveur JBoss Application? " + +#. Tag: para +#: General_FAQ.xml:157 +#, no-c-format +msgid "" +"Absolutely! Even though JBoss Cache comes integrated with the JBoss " +"Enterprise Application Platform, it can also be used in any other Java EE " +"server such as BEA WebLogic, IBM Websphere or Tomcat. It can also run in a " +"standalone Java process, completely outside of an application server. See " +"the Users' Guide for more details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:170 +#, no-c-format +msgid "" +"How can I migrate my application and configuration from using JBoss Cache 1." +"x to 2.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:173 +#, no-c-format +msgid "" +"Look at <ulink url=\"http://www.jboss.org/community/docs/DOC-10246\">this " +"wiki page</ulink> for help." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:182 +#, no-c-format +msgid "What about from 2.x to 3.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:185 +#, no-c-format +msgid "" +"JBoss Cache 3.x is API compatible with 2.x, although as far as possible you " +"should refactor your code not to use deprecated methods as these may " +"disappear in future releases of JBoss Cache." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:190 +#, no-c-format +msgid "" +"JBoss Cache 3.x comes with an all new configuration format. Old 2.x " +"configuration files will still work, although you will get a warning in the " +"logs about this. Again, as far as possible, we recommend migrating your " +"configuration file to the new format. Scripts are provided with the JBoss " +"Cache 3.x distribution to migrate configuration files (see " +"<literal>config2to3.sh</literal> and<literal>config2to3.bat</literal>)." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:201 +#, no-c-format +msgid "" +"Note that to take advantage of some of the new features in JBoss Cache 3.x, " +"you need to be using the new configuration format." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/JBoss_Cache_Frequently_Asked_Questions.po =================================================================== Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Revision_History.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Revision_History.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Revision_History.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,26 @@ +# translation of Cache_Frequently_Asked_Questions.po to French +# Corina Roe <croe(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Cache_Frequently_Asked_Questions\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-14 15:57+1000\n" +"Last-Translator: Corina Roe <croe(a)redhat.com&gt;\n&quot; +"Language-Team: French <i18(a)redhat.com&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Revision_History.xml:6 +#, no-c-format +msgid "Revision History" +msgstr "" + +#. Tag: author +#: Revision_History.xml:12 +#, fuzzy, no-c-format +msgid "<firstname></firstname> <surname></surname> <email></email>" +msgstr "<firstname>John</firstname> <surname>Doe</surname>" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/TreeCache_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/TreeCache_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/TreeCache_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,1094 @@ +# translation of Cache_Frequently_Asked_Questions.po to French +# Corina Roe <croe(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Cache_Frequently_Asked_Questions\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-14 15:57+1000\n" +"Last-Translator: Corina Roe <croe(a)redhat.com&gt;\n&quot; +"Language-Team: French <i18(a)redhat.com&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: TreeCache_FAQ.xml:6 +#, fuzzy, no-c-format +msgid "JBoss Cache: Core" +msgstr "JBoss Cache 1.4.1" + +#. Tag: para +#: TreeCache_FAQ.xml:26 +#, no-c-format +msgid "Can I run multiple JBoss Cache instances on the same VM?" +msgstr "Puis-je multiplier les instances de JBoss Cache sur le même VM?" + +#. Tag: para +#: TreeCache_FAQ.xml:30 +#, no-c-format +msgid "" +"Yes. There are some scenarios where you may want to run multiple instances " +"of JBoss Cache. For example, you want to run multiple local cache instances " +"with each instance having its own configuration (e.g., different cache " +"policy). In this case, you will need multiple xml configuration files." +msgstr "" +"Oui. Il existe quelques scénarios pour lesquels vous souhaiteriez peut-être " +"exécuter plusieurs instances de JBoss Cache. Par exemple, vous souhaitez " +"exécuter des instances cache locales multiples avec une configuration " +"séparée pour chaque instance (par ex. différentes politiques cache). Dans ce " +"cas, vous aurez besoin de fichiers de configuration xml multiples." + +#. Tag: para +#: TreeCache_FAQ.xml:41 +#, fuzzy, no-c-format +msgid "Can JBoss Cache run as a second level cache inside Hibernate?" +msgstr "" +"Est-ce que TreeCache peut opérer en tant que cache de second niveau à " +"l'intérieur d'Hibernate?" + +#. Tag: para +#: TreeCache_FAQ.xml:47 +#, fuzzy, no-c-format +msgid "" +"Yes. Since Hibernate 3.0 release, you can configure it to use JBoss Cache as " +"a second level cache. For details, see Hibernate documentation, and also see " +"<ulink url=\"http://www.jboss.org/community/docs/DOC-10265\">this wiki page</" +"ulink>." +msgstr "" +"Oui. Depuis la version Hibernate 3.0, vous pouvez le configurer en utilisant " +"JBoss Cache (notamment, TreeCache) en tant que cache de second niveau. Pour " +"davantage de détails, voir la documentation Hibernate, et aussi <ulink url=" +"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate\"> http://" +"wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate </ulink>" + +#. Tag: para +#: TreeCache_FAQ.xml:52 +#, no-c-format +msgid "" +"JBoss Cache 3.x with MVCC in particular works very well as a Hibernate " +"second level cache." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:60 +#, fuzzy, no-c-format +msgid "What about using POJO Cache as a Hibernate cache?" +msgstr "Peut-on utiliser PojoCache en tant que cache Hibernate?" + +#. Tag: para +#: TreeCache_FAQ.xml:64 +#, fuzzy, no-c-format +msgid "" +"It is not necessary to use POJO Cache for second level cache inside " +"Hibernate because Hibernate manages fine-grained fields in Java objects. " +"Using POJO Cache won't provide any advantage, and will be an unnecessary " +"performance drawback." +msgstr "" +"Il n'est pas utile d'utiliser PojoCache pour cache de second niveau à " +"l'intérieur d'Hibernate car Hibernate gère des champs raffinés dans les " +"objects Java. Donc, utiliser PojoCache n'apportera aucun avantage." + +#. Tag: para +#: TreeCache_FAQ.xml:74 +#, no-c-format +msgid "How can I configure JBoss Cache?" +msgstr "Comment puis-je configurer JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:78 +#, no-c-format +msgid "" +"You can configure the JBoss Cache through a configuration xml file or " +"programmatically using a <literal>org.jboss.cache.config.Configuration</" +"literal> object, passed in to the <literal>org.jboss.cache.CacheFactory</" +"literal> instance." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:90 +#, no-c-format +msgid "" +"Can I use a schema or DTD to validate my JBoss Cache configuration file?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:95 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, yes. An XSD schema is provided in your jbosscache-" +"core.jar file, and is also available online, on<ulink url=\"http://www.jboss." +"org/jbosscache/jbosscache-config-3.0.xsd\"> http://www.jboss.org/jbosscache/" +"jbosscache-config-3.0.xsd</ulink>. You can configure your IDE, text editor " +"or XML authoring tool to use this schema to validate your file." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:108 +#, no-c-format +msgid "What is the difference between the different cache modes?" +msgstr "Quelle est la différence entre les différents modes cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:113 +#, no-c-format +msgid "" +"JBossCache has five different cache modes, i.e., <literal>LOCAL</literal> , " +"<literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> and <literal>INVALIDATION_ASYNC</" +"literal> . If you want to run JBoss Cache as a single instance, then you " +"should set the cache mode to <literal>LOCAL</literal> so that it won't " +"attempt to replicate anything. If you want to have synchronous replication " +"among different JBoss Cache instances, you set it to <literal>REPL_SYNC</" +"literal> . For asynchronous replication, use <literal>AYSNC_REPL</literal> . " +"If you do not wish to replicate cached data but simply inform other caches " +"in a cluster that data under specific addresses are now stale and should be " +"evicted from memory, use <literal>INVALIDATION_SYNC</literal> or " +"<literal>INVALIDTAION_ASYNC</literal> . Synchronous and asynchronous " +"behavior applies to invalidation as well as replication." +msgstr "" +"JBossCache a cinq modes cache différents, par ex., <literal>LOCAL</" +"literal> , <literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> and <literal>INVALIDATION_ASYNC</" +"literal> . Si vous souhaitez exécuter JBoss Cache en tant qu'instance " +"unique, alors vous devrez configurer le mode cache à <literal>LOCAL</" +"literal> de façon à ce qu'il n'y ait pas de tentative de duplicata. Si vous " +"souhaitez obtenir une duplication synchronisée entre les différentes " +"instances JBoss Cache, configurez à <literal>REPL_SYNC</literal> . Pour " +"toute duplication asynchrone, utiliser <literal>AYSNC_REPL</literal> . Si " +"vous ne souhaitez pas dupliquer les données cache, mais que vous souhaitez " +"tout simplement informer les autres caches d'un groupement que les données " +"correspondantes à certaines adresses sont maintenant périmées et devraient " +"être évincées de la mémoire, utiliser <literal>INVALIDATION_SYNC</literal> " +"ou <literal>INVALIDTAION_ASYNC</literal> . Un comportement synchronisé ou " +"asynchronisé s'applique pour invalider ou pour dupliquer. " + +#. Tag: para +#: TreeCache_FAQ.xml:143 +#, no-c-format +msgid "" +"Note that <literal>ASYNC_REPL</literal> and <literal>INVALIDATION_ASYNC</" +"literal> are non-blocking. This can be useful when you want to have another " +"JBoss Cache serving as a mirror or backup and you don't want to wait for " +"confirmation that this mirror has received your messages." +msgstr "" +"Noter que <literal>ASYNC_REPL</literal> et <literal>INVALIDATION_ASYNC</" +"literal> sont 'non-bloquants'. Cela peut être utile quand vous voulez avoir " +"un autre JBoss Cache pour servir de miroir ou de backup et que vous ne " +"souhaitez pas attendre la confirmation que ce miroir a bien reçu vos " +"messages." + +#. Tag: para +#: TreeCache_FAQ.xml:157 +#, no-c-format +msgid "How does JBoss Cache's replication mechanism work?" +msgstr "Comment le mécanisme de duplication JBoss Cache fonctionne-t-il?" + +#. Tag: para +#: TreeCache_FAQ.xml:161 +#, no-c-format +msgid "" +"JBoss Cache leverages <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"for network communications. A JGroups configuration section is present in " +"your JBoss Cache configuration." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:166 +#, fuzzy, no-c-format +msgid "" +"A user can configure the cluster of JBoss Cache instances by sharing the " +"same cluster name ( <literal>cluster name</literal> ). There is also an " +"option of whether to populate the cache data upon starting a new instance in " +"the <literal>ClusterConfig</literal> attribute." +msgstr "" +"JBoss Cache utilise <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"comme couche de duplication. Un utilisateur peut configurer le groupement " +"d'instances JBoss Cache en partageant le même nom de groupement " +"( <literal>cluster name</literal> ). Une autre option consiste à charger les " +"données cache au moment du lancement d'une nouvelle instance dans l'attribut " +"<literal>ClusterConfig</literal> ." + +#. Tag: para +#: TreeCache_FAQ.xml:178 +#, fuzzy, no-c-format +msgid "" +"Note that once all instances join the same replication group, every " +"replication change is propagated to all participating members. There is no " +"mechanism for sub-partitioning where some replication can be done within " +"only a subset of members, unless you use the Buddy Replication features. See " +"the Users' Guide for more details on this." +msgstr "" +"Notez bien qu'une fois que toutes les instances ont rejoint le même groupe " +"de duplication, tout changement de duplication est propagé à tous les " +"membres participants. Il n'existe pas de mécanisme de sous-partition pour " +"lesquels certaines replications ne peuvent être faites qu'avec un nombre " +"limité de membres. Cela reste sur notre liste de choses à régler." + +#. Tag: para +#: TreeCache_FAQ.xml:190 +#, no-c-format +msgid "" +"I run a 2 node cluster. If the network dies, do the caches continue to run?" +msgstr "" +"J'exécute un groupement de noeuds. Si le réseau se meurt, est-ce que les " +"caches continuent d'être exécutés?" + +#. Tag: para +#: TreeCache_FAQ.xml:194 +#, no-c-format +msgid "" +"Yes, both will continue to run, but depending on your replication mode, all " +"transactions or operations may not complete. If <literal>REPL_SYNC</literal> " +"is used, operations will fail while if <literal>REPL_ASYNC</literal> is used " +"they will succeed. Even if they succeed though, caches will be out of sync." +msgstr "" +"Oui, ils continueront tous deux d'être exécutés, mais suivant votre mode de " +"replication, toutes les transactions ou opérations n'aboutiront pas " +"forcément. Si <literal>REPL_SYNC</literal> est utilisé, les opérations " +"échoueront. Si <literal>REPL_SYNC</literal> est utilisé, elles aboutiront. " +"Même si elles aboutissent, les caches seront désynchronisés." + +#. Tag: para +#: TreeCache_FAQ.xml:207 +#, no-c-format +msgid "" +"Can I plug in library X instead of JGroups to handle remote calls and group " +"communications?" +msgstr "" +"Puis-je ajouter une bibliothèque de programmes X à la place de JGroups pour " +"gérer les appels distants et les communications de groupe?" + +#. Tag: para +#: TreeCache_FAQ.xml:212 +#, fuzzy, no-c-format +msgid "" +"At this stage the answer is no. We do have an abstraction layer between the " +"communication suite and JBoss Cache in the pipelines, and this may appear as " +"a feature at some stage in the future." +msgstr "" +"Pour l'instant (JBoss Cache 1.x), la réponse est non. Nous avons une couche " +"d'abstractions situées entre la suite de communication et JBoss Cache dans " +"les pipelines, et cela pourrait aboutir à une fonctionnalité au bout d'un " +"moment." + +#. Tag: para +#: TreeCache_FAQ.xml:223 +#, no-c-format +msgid "" +"Does the cache need to replicate to every other instance in the cluster? " +"Isn't this slow if the cluster is large?" +msgstr "" +"Est-ce que le cache a besoin d'être dupliqué aux autres instances dans le " +"groupement? Cela prend-il du temps si le groupement est important?" + +#. Tag: para +#: TreeCache_FAQ.xml:230 +#, fuzzy, no-c-format +msgid "" +"Replication need not occur to every node in the cluster. This feature - " +"called Buddy Replication - allows each node to pick one or more 'buddies' in " +"the cluster and only replicate to its buddies. This allows a cluster to " +"scale very easily with no extra impact on memory or network traffic with " +"each node added." +msgstr "" +"Pour JBoss Cache 1.4.0, la duplication n'est pas utile pour chaque noeud " +"dans le groupement. Cette fonctionnalité - appelée Buddy Replication -permet " +"à chaque noeud de choisir un ou plusieurs 'compagnons' (buddy) dans le " +"groupement et de se limiter à ceux-ci pour se dupliquer. Cela permet au " +"groupement d'être modulé facilement sans impact supplémentaire sur la " +"mémoire ou sur le volume de trafic à chaque fois qu'un noeud est ajouté." + +#. Tag: para +#: TreeCache_FAQ.xml:237 +#, fuzzy, no-c-format +msgid "" +"See the Users' Guide for more information on Buddy Replication, and how it " +"can be used to achieve very high scalability." +msgstr "" +"Voir le guide d'utilisateur pour davantage d'informations sur Buddy " +"Replication, et comment l'utiliser pour obtenir un très haut niveau de " +"modulabilité." + +#. Tag: para +#: TreeCache_FAQ.xml:248 +#, no-c-format +msgid "" +"I'm using Buddy Replication. Do I need to have some form of session affinity?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:251 +#, no-c-format +msgid "" +"Session affinity relates to returning to the same cache instance for the " +"same data being used. While this is strictly not a requirement for Buddy " +"Replication, it is greatly recommended to minimize moving state around a " +"cluster." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:261 +#, fuzzy, no-c-format +msgid "" +"If I have the need for different configuration properties (e.g., " +"<literal>CacheMode</literal> and <literal>IsolationLevel</literal> ), do I " +"simply need to create multiple <literal>org.jboss.cache.Cache</literal> " +"instances with the appropriate configuration?" +msgstr "" +"Si j'ai besoin de propriétés TreeCache différentes (par ex. " +"<literal>CacheMode</literal> and <literal>IsolationLevel</literal> ), aurais-" +"je besoin de créer les instances TreeCache multiples dans la configuration " +"qui convient?" + +#. Tag: para +#: TreeCache_FAQ.xml:272 +#, fuzzy, no-c-format +msgid "" +"Yes. All the above mentioned properties are per cache instance. Therefore " +"you will need separate <literal>org.jboss.cache.Cache</literal> instances." +msgstr "" +"Oui. Toutes les propriétés mentionnées ci-dessus sont par instance cache. De " +"ce fait, vous aurez besoin d'une instance JBoss Cache séparée." + +#. Tag: para +#: TreeCache_FAQ.xml:282 +#, no-c-format +msgid "" +"Isn't this expensive from a networking standpoint, i.e., needing to create " +"sockets for each <literal>org.jboss.cache.Cache</literal> instance?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:289 +#, no-c-format +msgid "" +"Yes, it can be. For such cases it is recommended that you configure your " +"cache using the JGroups Multiplexer, which allows several caches to share a " +"single JGroups channel. Please see the Users' Guide for details on how to " +"configure the JGroups Multiplexer." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:296 +#, no-c-format +msgid "" +"A faster and more efficient approach is to use a shared transport in " +"JGroups. Please see <ulink url=\"http://www.jgroups.org\">the JGroups " +"documentation</ulink> for more details on how to do this." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:307 +#, fuzzy, no-c-format +msgid "" +"Does the <literal>ClusterName</literal> configuration element have any " +"relation to the JBoss AS cluster <literal>PartitionName</literal> ?" +msgstr "" +"Est-ce que la configuration <literal>ClusterName</literal> ne comporte " +"aucune relation avec JBoss AS Cluster <literal>PartitionName</literal> (nom " +"de partition)?" + +#. Tag: para +#: TreeCache_FAQ.xml:317 +#, no-c-format +msgid "" +"Yes. They are both JGroups group names. Besides the notion of a channel in " +"JGroups, it also can partition the channel into different group names." +msgstr "" +"Oui. Ce sont tous les deux des noms de groupes JGroups. En plus de la notion " +"de réseau dans JGroups, il peut également partitionner le réseau en " +"différents noms de groupes." + +#. Tag: para +#: TreeCache_FAQ.xml:326 +#, fuzzy, no-c-format +msgid "" +"When using multiple JGroups based components [cluster-service.xml, cache " +"(multiple instances)], what is the correct/valid way to configure those " +"components to make sure my multicast addresses don't conflict?" +msgstr "" +"Lorsque vous utilisez des composants basés-JGroups multiples [cluster-" +"service.xml, treecache (multiple instances)], quelle est la façon qui " +"convient de configurer ces composants de façon à ce que les adresses de " +"diffusion sélective n'entrent pas en conflit?" + +#. Tag: para +#: TreeCache_FAQ.xml:334 +#, no-c-format +msgid "" +"There are two parameters to consider: multicast address (plus port) and the " +"group name. At minimum, you will have to run components using a different " +"group name. But whether to run them on the same channel depends upon whether " +"the communication performance is critical for you or not. If it is, then " +"it'd be best to run them on different channels." +msgstr "" +"Il faut considérer deux paramètres: l'adresse multidestination de groupe " +"(plus port) et le nom de groupe. Au minimum, vous devrez opérer sur le même " +"réseau, suivant que la performance de communication est critique ou non pour " +"vous. Si elle est critique, alors il vaut mieux les exécuter sur des réseaux " +"différents." + +#. Tag: para +#: TreeCache_FAQ.xml:346 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache persistence storage?" +msgstr "" +"Est-ce que JBoss Cache prend actuellement en charge le stockage de " +"persistance cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:352 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache has a cache loader interface that supports cache " +"persistence. See below for more FAQs on cache loaders." +msgstr "" +"Oui. A partir de la version 1.1, JBoss Cache possède une interface " +"CacheLoader qui supporte la persistance cache. Voir ci-dessous." + +#. Tag: para +#: TreeCache_FAQ.xml:360 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache passivation/ overflow to a data store?" +msgstr "" +"Est-ce que JBoss Cache prend actuellement en charge la passivation/" +"dépassement dans un store de données?" + +#. Tag: para +#: TreeCache_FAQ.xml:366 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache uses the cache loader to support cache passivation/ " +"overflow. See documentation on how to configure and use this feature." +msgstr "" +"Oui. A partir de la version 1.2.4, JBoss Cache utilise CacheLoader pour " +"prendre en charge la passivation/dépassement. Voir la documentation sur la " +"façon de configurer et d'utiliser cette fonctionnalité." + +#. Tag: para +#: TreeCache_FAQ.xml:375 +#, no-c-format +msgid "Is JBoss Cache thread safe?" +msgstr "Est-ce que le thread JBoss Cache est sécurisé?" + +#. Tag: para +#: TreeCache_FAQ.xml:379 +#, no-c-format +msgid "Yes, it is thread safe." +msgstr "Oui, il est sécurisé." + +#. Tag: para +#: TreeCache_FAQ.xml:385 +#, no-c-format +msgid "Does JBoss Cache support XA (2PC) transactions now?" +msgstr "" +"Est-ce que JBoss Cache prend en charge les transactions XA (2PC) maintenant?" + +#. Tag: para +#: TreeCache_FAQ.xml:389 +#, fuzzy, no-c-format +msgid "" +"No, although it is also on our to do list. Our internal implementation does " +"use a procedure similar to 2PC to coordinate a transactions among different " +"instances, but JBoss Cache is not an XA resource." +msgstr "" +"Non, mais c'est sur notre liste de choses à régler. Notre implémentation " +"interne utilise une procédure 2PC similaire pour coordonner une transaction " +"entre des instances différentes." + +#. Tag: para +#: TreeCache_FAQ.xml:398 +#, fuzzy, no-c-format +msgid "Which transaction managers are supported by JBoss Cache?" +msgstr "Quels TransactionManagers sont-ils pris en charge par JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:404 +#, no-c-format +msgid "" +"JBoss Cache supports any TransactionManager that is <ulink url=\"http://java." +"sun.com/products/jta/\">JTA</ulink> compliant such as<ulink url=\"http://www." +"jboss.org/jbosstm/\">JBoss Transactions</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:408 +#, no-c-format +msgid "" +"While JBoss Cache does ships with a dummy transaction manager (<literal>org." +"jboss.cache.transaction.DummyTransactionManager</literal>), we do " +"<emphasis>not</emphasis> recommend using this for production. It is not " +"thread safe, and is intended for internal testing only." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:421 +#, no-c-format +msgid "How do I set up the cache to be transactional?" +msgstr "Comment puis-je configurer cache pour qu'il soit transactionnel?" + +#. Tag: para +#: TreeCache_FAQ.xml:425 +#, fuzzy, no-c-format +msgid "" +"You either use the default transaction manager that ships with JBoss AS or " +"you have to implement the <literal>org.jboss.cache.transaction." +"TransactionManagerLookup</literal> interface, and return an instance of your " +"<literal>javax.transaction.TransactionManager</literal> implementation. The " +"configuration property <literal>TransactionManagerLookupClass</literal> " +"defines the class to be used by the cache to fetch a reference to a " +"transaction manager. It is trivial to implement this interface to support " +"other transaction managers. Once this attribute is specified, the cache will " +"look up the transaction context from this transaction manager." +msgstr "" +"Vous pouvez soit utiliser le TransactionManager (JBoss) par défaut pour " +"exécuter JBossCache à l'intérieur de JBoss, soit implémenter l'interface " +"<literal>TransactionManagerLookup</literal>, et retourner une instance de " +"votre javax.transaction.TransactionManager. La propriété de configuration " +"<literal>TransactionManagerLookupClass</literal> détermine la classe pour " +"que le cache puisse chercher une référence dans le TransactionManager. Il " +"est trivial d'implémenter cette classe pour supporter les autres " +"TransactionManagers. Une fois que cet attribut est spécifié, le cache " +"vérifiera le contexte de transaction pour ce gestionnaire de transaction." + +#. Tag: para +#: TreeCache_FAQ.xml:441 +#, no-c-format +msgid "" +"The <literal>org.jboss.cache.transaction.GenericTransactionManagerLookup</" +"literal> class that ships with JBoss Cache is able to detect and bind to " +"most popular transaction managers. See the " +"<literal>GenericTransactionManagerLookup</literal> javadocs for more " +"information." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:454 +#, no-c-format +msgid "How do I control the cache locking level?" +msgstr "Comment puis-je contrôler le niveau de verrouillage du cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:458 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache lets you control the cache locking level through the transaction " +"isolation level. This is configured through the attribute " +"<literal>IsolationLevel</literal> . The transaction isolation levels " +"correspond to database isolation levels, namely, <literal>NONE</literal> , " +"<literal>READ_UNCOMMITTED</literal> , <literal>READ_COMMITTED</literal> , " +"<literal>REPEATABLE_READ</literal> , and <literal>SERIALIZABLE</literal> . " +"Note that these isolation levels are ignored if optimistic locking is used. " +"For details, please refer to the user manual." +msgstr "" +"JBossCache vous laisse contrôler le niveau de verrouillage du cache à " +"travers le niveau d'isolation de la transaction. Ce niveau est configuré à " +"travers l'attribut <literal>IsolationLevel</literal> . Actuellement, " +"JBossCache emploie des verrouillages pessimistes internes. Le niveau " +"d'isolation de la transaction du verrouillage pessimiste correspond aux " +"niveaux d'isolation JDBC, c'est à dire <literal>NONE</literal> , " +"<literal>READ_UNCOMMITTED</literal> , <literal>READ_COMMITTED</literal> , " +"<literal>REPEATABLE_READ</literal> , and <literal>SERIALIZABLE</literal> . " +"Noter que ces niveaux d'isolation ne sont pas pris en considération si le " +"verrouillage optimiste est utilisé. Pour davantage d'informations, veuillez " +"consulter le manuel d'utilisateur." + +#. Tag: para +#: TreeCache_FAQ.xml:480 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, when using the MVCC locking scheme, only " +"<literal>READ_COMMITTED</literal> and <literal>REPEATABLE_READ</literal> are " +"supported. Any other isolation level provided will either be upgraded or " +"downgraded accordingly." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:493 +#, no-c-format +msgid "How does JBoss Cache lock data for concurrent access?" +msgstr "" +"Comment JBoss Cache verrouille-t-il les données en cas d'accès simultané?" + +#. Tag: para +#: TreeCache_FAQ.xml:497 +#, fuzzy, no-c-format +msgid "" +"In JBoss Cache 2.x, by default pessimistic locking is used to lock data " +"nodes, based on the isolation level configured. We also offer optimistic " +"locking to allow for greater concurrency at the cost of slight processing " +"overhead and performance. See the documentation for a more detailed " +"discussion on concurrency and locking in JBoss Cache." +msgstr "" +"Par défaut, JBoss Cache utilise le verrouillage pessimiste pour les noeuds " +"de données, sur la base du niveau d'isolation configuré. A partir de JBoss " +"Cache 1.3.0, nous proposons également le verrouillage optimiste pour une " +"plus grande concurrence au détriment d'une légère diminution de la " +"performance. Voir la documentation pour une discussion plus détaillée sur la " +"concurrence et sur le verrouillage dans JBoss Cache. " + +#. Tag: para +#: TreeCache_FAQ.xml:505 +#, no-c-format +msgid "" +"In JBoss Cache 3.x, optimistic and pessimistic locking are deprecated in " +"favour of MVCC (multi-version concurrency control), which is far more " +"efficient than either optimistic or pessimistic locking. For a detailed " +"discussion on our MVCC implementation, see <ulink url=\"http://jbosscache." +"blogspot.com/2008/07/mvcc-has-landed.html\">this blog entry</ulink> " +"and<ulink url=\"http://www.jboss.org/community/docs/DOC-10272\">this wiki " +"page</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:520 +#, fuzzy, no-c-format +msgid "How do I enable Optimistic Locking or MVCC in JBoss Cache?" +msgstr "Comment activer le verrouillage optimiste dans JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:524 +#, no-c-format +msgid "Please see the configuration section of the Users' Guide for details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:532 +#, no-c-format +msgid "Can I use the cache locking level even without a transaction context?" +msgstr "" +"Puis-je utiliser le niveau de verrouillage cache même en dehors d'un " +"contexte de transaction?" + +#. Tag: para +#: TreeCache_FAQ.xml:538 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache controls the individual node locking behavior through the " +"isolation level semantics. This means even if you don't use a transaction, " +"you can specify the lock level via isolation level. You can think of the " +"node locking behavior outside of a transaction as if it is under transaction " +"with <literal>auto_commit</literal> on." +msgstr "" +"Oui. JBossCache contrôle le comportement de verrouillage d'un noeud " +"individuel par les sémantiques du niveau d'isolation. Cela signifie que même " +"si vous n'utilisez pas une transaction, vous pouvez en spécifier le niveau " +"de verrouillage grâce au niveau d'isolation. Vous pouvez imaginer le " +"comportement de verrouillage du noeud en dehors de la transaction comme s'il " +"était en cours de transaction sous <literal>auto_commit</literal>." + +#. Tag: para +#: TreeCache_FAQ.xml:551 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache support <literal>SELECT FOR UPDATE</literal> semantics?" +msgstr "Est-ce que JBoss Cache prend en charge <literal>Region</literal> ?" + +#. Tag: para +#: TreeCache_FAQ.xml:559 +#, no-c-format +msgid "" +"Yes, but this is is only possible if you are running within a JTA " +"transaction <emphasis>and</emphasis> are using either <literal>MVCC</" +"literal> or <literal>PESSIMISTIC</literal> as your node locking scheme." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:568 +#, no-c-format +msgid "To achieve <literal>SELECT FOR UPDATE</literal> semantics, simply do:" +msgstr "" + +#. Tag: programlisting +#: TreeCache_FAQ.xml:573 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" // start transaction ... \n" +"\n" +" cache.getInvocationContext().getOptionOverrides().setForceWriteLock" +"(true);\n" +" Node n = cache.get(\"/a/b/c\"); // this acquires a WRITE LOCK on this " +"node\n" +" ...\n" +" ...\n" +"\n" +" // end transaction\n" +"\n" +" ]]>" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:579 +#, no-c-format +msgid "" +"With replication (REPL_SYNC/REPL_ASYNC) or invalidation (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), how often does the cache broadcast messages over the " +"network?" +msgstr "" +"Sous replication (REPL_SYNC/REPL_ASYNC) ou invalidation (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), combien de fois le cache diffuse-t-il des messages sur " +"le réseau?" + +#. Tag: para +#: TreeCache_FAQ.xml:586 +#, fuzzy, no-c-format +msgid "" +"If the updates are under transaction, then the broadcasts happen only when " +"the transaction is about to commit (actually during the prepare stage " +"internally). That is, it will be a batch update. However, if the operations " +"are not under transaction context, then each update will trigger " +"replication. Note that this has performance implications if network latency " +"is a problem." +msgstr "" +"Si les mises à jour sont sous transaction, alors les diffusions n'ont lieu " +"que lorsque la transaction est prête à être validée (exactement au moment de " +"la préparation en interne). C'est à dire qu'il s'agira d'une mise à jour " +"d'un batch. Cependant, si les opérations ne sont pas sous le contexte d'une " +"transaction, alors chaque mise à jour entraînera une duplication. Notez que " +"cela comporte des implications de performance si le transport réseau est " +"lourd (ce qui est souvent le cas)." + +#. Tag: para +#: TreeCache_FAQ.xml:598 +#, no-c-format +msgid "How can I do a mass removal?" +msgstr "Comment puis-je faire un retrait en masse?" + +#. Tag: para +#: TreeCache_FAQ.xml:602 +#, fuzzy, no-c-format +msgid "" +"If you do a<literal>cache.removeNode(\"/myroot\")</literal>, it will " +"recursively remove all the entries under \"/myroot\"." +msgstr "" +"Si vous faites une cache.remove (\"/root\"), toutes les entrées sous \"/root" +"\" vont être retirées récursivement." + +#. Tag: para +#: TreeCache_FAQ.xml:610 +#, no-c-format +msgid "Can I monitor and manage the JBoss Cache?" +msgstr "Puis-je contrôler et gérer le JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:614 +#, fuzzy, no-c-format +msgid "" +"Yes, using a JMX console such as the one shipped with JBoss AS or Java 5's " +"<literal>jconsole</literal> utility. See the chapter titled <emphasis role=" +"\"bold\">Management Information</emphasis> in the JBoss Cache Users' Guide " +"for more details." +msgstr "" +"Avec JBoss Cache 1.3.0, vous le pouvez si vous exécutez JBoss Cache dans " +"JBoss AS ou si vous utilisez la console <literal>jconsole</literal> de " +"l'utilité JDK 5.0's. Voir le chapitre intitulé <emphasis role=\"bold" +"\">Management Information</emphasis> dans le guide d'utilisation JBoss Cache " +"pour plus d'informations." + +#. Tag: para +#: TreeCache_FAQ.xml:625 +#, no-c-format +msgid "" +"JBoss Cache uses a <literal>:</literal> character in its object name. This " +"causes problems with my MBean server. What can I do about it?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:633 +#, no-c-format +msgid "" +"This is something we have seen with some MBean servers. By default, JBoss " +"Cache uses <literal>jboss.cache:service=JBossCache</literal> as a prefix to " +"all objects it binds in JMX. To work around this, use the <literal>-" +"Djbosscache.jmx.prefix</literal> JVM parameter to pass in an alternate " +"prefix." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:647 +#, fuzzy, no-c-format +msgid "Can I disable JBoss Cache management attributes?" +msgstr "" +"Puis-je désactiver les attributs de gestion JBoss Cache dans JBoss Cache " +"1.3.0?" + +#. Tag: para +#: TreeCache_FAQ.xml:651 +#, no-c-format +msgid "" +"Yes, you can. See the section on configuration in the JBoss Cache Users' " +"Guide." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:658 +#, no-c-format +msgid "What happened to jboss-serialization.jar?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:662 +#, no-c-format +msgid "" +"As of JBoss Cache 2.0.0, the dependency on JBoss Serialization has been " +"dropped since most of the benefits of JBoss Serialization are available in " +"updated Java 5 VMs. Since JBoss Cache 2.0.0 is baselined on Java 5, there " +"was no need to provide these benefits separately." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:673 +#, no-c-format +msgid "Does JBoss Cache support partitioning?" +msgstr "Est-ce que JBoss Cache prend en charge le partitionnement?" + +#. Tag: para +#: TreeCache_FAQ.xml:677 +#, no-c-format +msgid "" +"Not right now. JBoss Cache does not support partitioning that a user can " +"configure to have different set of data residing on different cache " +"instances while still participating as a replication group." +msgstr "" +"Pas pour l'instant. JBoss Cache ne supporte pas le partitionnement qu'un " +"utilisateur peut configurer pour obtenir plusieurs groupes de données " +"résidant dans des instances cache différentes tandis qu'ils continuent de " +"participer à un groupe de duplication." + +#. Tag: para +#: TreeCache_FAQ.xml:682 +#, no-c-format +msgid "" +"This is on the roadmap though, so do keep an eye on <ulink url=\"http://jira." +"jboss.org/jira/browse/JBCACHE-60\">JBCACHE-60</ulink> if you are interested." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:692 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache handle the concept of application classloading inside, say, " +"a Java EE container?" +msgstr "" +"Est-ce que JBoss Cache contient le concept de chargement de classes " +"d'applications, comme un container J2EE?" + +#. Tag: para +#: TreeCache_FAQ.xml:698 +#, fuzzy, no-c-format +msgid "" +"Application-specific classloading is used widely inside a Java EE container. " +"For example, a web application may require a new classloader to scope a " +"specific version of the user library. However, by default JBoss Cache is " +"agnostic to the classloader. In general, this leads to two kinds of problems:" +msgstr "" +"Classloading (chargement de classe) spécifique-application, est utilisé " +"largement à l'intérieur d'un container J@EE. Ainsi, il est possible qu'une " +"application web puisse avoir besoin d'un nouveau classloader pour obtenir " +"une version particulière de la bibliothèque de l'utilisateur. Mais, par " +"défaut, cela mène à deux sortes de problèmes:" + +#. Tag: para +#: TreeCache_FAQ.xml:707 +#, no-c-format +msgid "" +"Object instance is stored in cache1 and replicated to cache2. As a result, " +"the instance in cache2 is created by the system classloader. The replication " +"may fail if the system classloader on cache2 does not have access to the " +"required class. Even if replication doesn't fail, a user thread in cache2 " +"may not be able to access the object if the user thread is expecting a type " +"defined by the application classloader." +msgstr "" +"L'instance d'objets est stockée dans cache1 et répliquée dans cache2. Ainsi, " +"l'instance dans cache2 est créée dans le classloader du système. La " +"replication peut échouer si le classloader de cache 2 n'a pas accès à la " +"classe qui convient. Même si la replication n'échoue pas, un thread " +"utilisateur de cache2 n'est pas forcément en mesure d'accéder à l'objet si " +"le thread utilisateur s'attend à un type défini par le classloader de " +"l'application." + +#. Tag: para +#: TreeCache_FAQ.xml:718 +#, fuzzy, no-c-format +msgid "" +"Object instance is created by thread 1 and will be accessed by thread 2 " +"(with two different classloaders). JBoss Cache has no notion of the " +"different classloaders involved. As a result, you will have a " +"<literal>ClassCastException</literal> . This is a standard problem in " +"passing an object from one application space to another; JBoss Cache just " +"adds a level of indirection in passing the object." +msgstr "" +"L'instance d'objet est créée par thread 1 et pourra être accédée par thread " +"2 (avec deux classloaders différents). JBossCache n'a aucune idée des " +"classloaders impliqués. Ainsi, vous aurez un <literal>ClassCastException</" +"literal> . C'est un problème normal lorsqu'on passe un objet d'un espace " +"d'application à un autre; JBossCache rajoute un niveau d'indirection en " +"passant l'objet." + +#. Tag: para +#: TreeCache_FAQ.xml:731 +#, fuzzy, no-c-format +msgid "" +"To solve the first kind of issue JBoss Cache uses a " +"<literal>CacheMarshaller</literal> . Basically, this allows application code " +"to register a classloader with a portion of the cache tree for use in " +"handling objects replicated to that portion. See the " +"<literal>CacheMarshaller</literal> section of the Users' Guide for more " +"details." +msgstr "" +"Pour résoudre ce premier genre de problèmes, dans JBoss Cache 1.2.4, nous " +"avons introduit le concept de <literal>TreeCacheMarshaller</literal> . Cela " +"permet à un code d'application d'enregistrer un classloader avec une portion " +"du tree cache pour pouvoir manipuler les objets dupliqués dans cette " +"portion. Voir la section TreeCacheMarshaller du guide d'utilisation pour " +"davantage d'informations." + +#. Tag: para +#: TreeCache_FAQ.xml:742 +#, no-c-format +msgid "" +"To solve the second kind of issue, you can use the the " +"<literal>UseLazyDeserialization</literal> configuration option in JBoss " +"Cache, which wraps your objects in a <literal>Marshalledvalue</literal> " +"wrapper. The <literal>MarshalledValue</literal> serializes and deserializes " +"your object on demand, ensuring the proper thread local context class loader " +"is used each time." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:757 +#, no-c-format +msgid "" +"Does JBoss Cache currently support pre-event and post-event notification?" +msgstr "" +"Est-ce que JBoss Cache supporte actuellemet les notifications pre-event et " +"post-event?" + +#. Tag: para +#: TreeCache_FAQ.xml:763 +#, no-c-format +msgid "" +"Yes. A boolean is passed in to each notification callback identifying " +"whether the callback is before or after the event. See the <literal>org." +"jboss.cache.notifications.annotations.CacheListener</literal> annotation for " +"details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:774 +#, fuzzy, no-c-format +msgid "How do I implement a custom listener to listen to cache events?" +msgstr "" +"Comment dois-je implémenter un custom listener pour qu'il écoute des " +"événements <literal>MarshalledValue</literal>?" + +#. Tag: para +#: TreeCache_FAQ.xml:780 +#, no-c-format +msgid "See the Users' Guide on this subject." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:788 +#, fuzzy, no-c-format +msgid "" +"Can I use <literal>UseRegionBasedMarshalling</literal> attribute in JBoss " +"Cache in order to get around ClassCastExceptions happening when accessing " +"data in the cache that has just been redeployed?" +msgstr "" +"Puis-je utiliser l'attribut <literal>useRegionBasedMarshalling</literal> " +"dans JBoss Cache de façon à éviter ClassCastExceptions lorsqu'on accède aux " +"données qui viennent juste d'avoir été déployées dans le cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:797 +#, fuzzy, no-c-format +msgid "" +"Yes, you can. Originally, cache Marshalling was designed as a workaround for " +"those replicated caches that upon state transfer did not have access to the " +"classloaders defining the objects in the cache." +msgstr "" +"Oui, vous le pouvez. A l'origine, <literal>TreeCache</literal> Marshalling " +"était conçu pour éviter ces problèmes pour ces caches dupliqués, qui au " +"moment des transferts d'état, n'avaient pas accès aux chargement de classes " +"déterminant les objets dans le cache." + +#. Tag: para +#: TreeCache_FAQ.xml:802 +#, no-c-format +msgid "" +"On each deployment, JBoss creates a new classloader per the top level " +"deployment artifact, for example an EAR. You also have to bear in mind that " +"a class in an application server is defined not only by the class name but " +"also its classloader. So, assuming that the cache is not deployed as part of " +"your deployment, you could deploy an application and put instances of " +"classes belonging to this deployment inside the cache. If you did a " +"redeployment and try to do a get operation of the data previously put, this " +"would result on a ClassCastException. This is because even though the class " +"names are the same, the class definitions are not. The current classloader " +"is different to the one when the classes were originally put." +msgstr "" +"Pour chaque déploiement, JBoss crée un nouveau chargeur de classes par " +"l'artifact de déploiement de haut niveau, par exemple un EAR. Vous devrez " +"également vous souvenir qu'une classe dans un serveur d'application n'est " +"uniquement définie que par le nom de classe mais aussi par son chargeur de " +"classe. Donc, en assumant que le cache n'est pas déployé dans le cadre de " +"votre déploiement, vous pouvez déployer une application et mettre des " +"instances de classes qui appartiennent à ce déploiement à l'intérieur du " +"cache. Si vous procédiez à un déploiement et que vous essayiez une opération " +"'get' sur les données rajoutées au préalable, cela pourrait aboutir à une " +"ClassCastException. Car même si les noms de classes sont les mêmes, les " +"définitions de classes ne sont pas les mêmes. Le classloader actuel est " +"différent de celui qui était en place quand les classes ont été désignées à " +"l'origine." + +#. Tag: para +#: TreeCache_FAQ.xml:817 +#, fuzzy, no-c-format +msgid "" +"By enabling marshalling, you can control the lifecycle of the data in the " +"cache and if on undeployment, you deactivate the region and unregister the " +"classloader that you'd have registered on deployment, you'd evict the data " +"in the cache locally. That means that in the next deployment, the data won't " +"be in the cache, therefore avoiding the problem. Obviously, using " +"marshalling to get around this problem is only recommended when you have " +"some kind of persistence backing where the data survives, for example using " +"CacheLoaders, or when JBoss Cache is used as a second level cache in a " +"persistence framework." +msgstr "" +"En activant marshalling, vous pouvez contrôler le cycle de vie des données " +"dans le cache et si au moment du retour de déploiement (undeployment), vous " +"désactivez la région et annulez l'enregistrement du classloader que vous " +"avez enregistré au moment du déploiement, vous expulserez les données " +"localement dans les caches. Cela signifie qu'au prochain déploiement, les " +"données ne seront plus dans le cache, évitant ainsi le problème. De toute " +"évidence, utiliser le marshalling pour circonscrire ce problème n'est " +"recommandé que quand vous avez une certaine persistance backing là où les " +"données survivent, par exemple en utilisant CacheLoaders, ou quand " +"JBossCache est utilisé en tant que cache de second niveau dans une structure " +"de persistance." + +#. Tag: para +#: TreeCache_FAQ.xml:830 +#, fuzzy, no-c-format +msgid "" +"To implement this feature, please follow the instructions indicated in the " +"example located in the CacheMarshaller section of the Users' Guide. It's " +"worth noting that instead of a <literal>ServletContextListener</literal> , " +"you could add this code into an <literal>MBean</literal> that contained " +"lifecycle methods, such as <literal>start()</literal> and <literal>stop()</" +"literal> . The key would be for this MBean to depend on the target cache, so " +"that it can operate as long as the cache is up and running." +msgstr "" +"Pour implémenter cette fonctionnalité, veuillez suivre les instructions " +"indiquées dans l'exemple situé dans la section du guide d'utilisateur. Il " +"est important de noter qu'au lieu de <literal>ServletContextListener</" +"literal>, vous pouvez ajouter ce code dans un <literal>MBean</literal> qui " +"contient les méthodes de cycles de vie, comme <literal>start()</literal> et " +"<literal>stop()</literal>. Pour ce MBean, la clé serait de dépendre du cache " +"de la cible, de façon à ce qu'il puisse opérer tant que le cache est en " +"cours d'exécution." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Troubleshooting.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Troubleshooting.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/fr-FR/Troubleshooting.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,41 @@ +# translation of Cache_Frequently_Asked_Questions.po to French +# Corina Roe <croe(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Cache_Frequently_Asked_Questions\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-14 15:57+1000\n" +"Last-Translator: Corina Roe <croe(a)redhat.com&gt;\n&quot; +"Language-Team: French <i18(a)redhat.com&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Troubleshooting.xml:6 +#, no-c-format +msgid "Troubleshooting" +msgstr "Résolution de pannes" + +#. Tag: para +#: Troubleshooting.xml:11 +#, no-c-format +msgid "" +"I am having problems getting JBoss Cache to work, where can I get " +"information on troubleshooting?" +msgstr "" +"J'ai des problèmes à faire fonctionner JBoss Cache, où puis-je obtenir des " +"informations sur la résolution de pannes?" + +#. Tag: para +#: Troubleshooting.xml:15 +#, fuzzy, no-c-format +msgid "" +"Troubleshooting section can be found in the following <ulink url=\"http://" +"www.jboss.org/community/docs/DOC-10288\">wiki link</ulink>." +msgstr "" +"La section 'résolution de pannes' se trouve par le lien suivant <ulink url=" +"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheTroubleshooting\">wiki " +"link</ulink> ." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Author_Group.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Author_Group.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Author_Group.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,21 @@ +# translation of Colophon.po to Japanese +# Noriko Mizumoto <noriko(a)redhat.com&gt;, 2007. +# Junko Ito <junko.ito(a)rehdat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-05 08:49+1000\n" +"Last-Translator: Junko Ito <junko.ito(a)rehdat.com&gt;\n&quot; +"Language-Team: Japanese <ja(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: firstname +#: Author_Group.xml:7 +#, no-c-format +msgid "Ben Wang, Bela Ban, Manik Surtani, Scott Marlow, Galder Zamarreño" +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Book_Info.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Book_Info.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Book_Info.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,41 @@ +# translation of Colophon.po to Japanese +# Noriko Mizumoto <noriko(a)redhat.com&gt;, 2007. +# Junko Ito <junko.ito(a)rehdat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-05 08:49+1000\n" +"Last-Translator: Junko Ito <junko.ito(a)rehdat.com&gt;\n&quot; +"Language-Team: Japanese <ja(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Book_Info.xml:5 +#, fuzzy, no-c-format +msgid "JBoss Cache Frequently Asked Questions" +msgstr "よくある質問とその回答 (FAQ) " + +#. Tag: subtitle +#: Book_Info.xml:6 +#, no-c-format +msgid "for Use with JBoss Enterprise Application Platform 5.0" +msgstr "" + +#. Tag: para +#: Book_Info.xml:12 +#, no-c-format +msgid "" +"This book is a compilation of frequently asked questions about JBoss Cache" +msgstr "" +"このブックは、JBoss Cache についてよくある質問とその回答をまとめたものです。" + +#. Tag: holder +#: Book_Info.xml:24 +#, no-c-format +msgid "&HOLDER;" +msgstr "&HOLDER;" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/CacheLoader_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/CacheLoader_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/CacheLoader_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,364 @@ +# translation of Colophon.po to Japanese +# Noriko Mizumoto <noriko(a)redhat.com&gt;, 2007. +# Junko Ito <junko.ito(a)rehdat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-05 08:49+1000\n" +"Last-Translator: Junko Ito <junko.ito(a)rehdat.com&gt;\n&quot; +"Language-Team: Japanese <ja(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: CacheLoader_FAQ.xml:6 +#, no-c-format +msgid "Cache Loaders" +msgstr "キャッシュローダー" + +#. Tag: para +#: CacheLoader_FAQ.xml:12 +#, fuzzy, no-c-format +msgid "What is a cache loader?" +msgstr "CacheLoader とは何ですか？" + +#. Tag: para +#: CacheLoader_FAQ.xml:16 +#, fuzzy, no-c-format +msgid "" +"A cache loader is the connection of JBoss Cache to a (persistent) data " +"store. The cache loader is called by JBoss Cache to fetch data from a store " +"when that data is not in the cache, and when modifications are made to data " +"in the cache the Cache Loader is called to store those modifications back to " +"the store." +msgstr "" +"CacheLoader は、JBossCache を（永続）データストアへ接続します。データがキャッ" +"シュにない場合、ストアからデータを読み出すため CacheLoader が JBossCache によ" +"り呼び出されます。また、キャッシュのデータに変更があった場合、変更をストアに" +"保存するため CacheLoader が呼び出されます。" + +#. Tag: para +#: CacheLoader_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "" +"In conjunction with eviction policies, JBoss Cache with a cache loader " +"allows a user to maintain a bounded cache for a large backend datastore. " +"Frequently used data is fetched from the datastore into the cache, and the " +"least used data is evicted, in order to provide fast access to frequently " +"accessed data. This is all configured through XML, and the programmer " +"doesn't have to take care of loading and eviction." +msgstr "" +"エビクションポリシーと共に、CacheLoader を持つ JBossCache を利用すると、大き" +"なバックエンドデータストアのバインドされたキャッシュを維持することができま" +"す。頻繁に使用されるデータはデータストアからキャッシュへ読み出されます。頻繁" +"にアクセスされるデータのアクセス速度を向上するため、使用頻度が最も低いデータ" +"はエビクトされます。設定はすべて XML で行われ、プログラマはローディングやエビ" +"クションを考慮する必要はありません。" + +#. Tag: para +#: CacheLoader_FAQ.xml:32 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache currently ships with several cache loader implementations, " +"including:" +msgstr "" +"現在、JBossCache には下記を含む複数の CacheLoader 実装が同梱されています。" + +#. Tag: para +#: CacheLoader_FAQ.xml:37 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.FileCacheLoader</literal> : this " +"implementation uses the file system to store and retrieve data. JBoss Cache " +"nodes are mapped to directories, subnodes to subdirectories etc. Attributes " +"of a node are mapped to a data file inside the directory." +msgstr "" +"FileCacheLoader: この実装はファイルシステムを使用してデータを保存し、読み出し" +"ます。JBossCache のノードは、ディレクトリやサブノード、サブディレクトリなどに" +"マップされます。ノードの属性は、ディレクトリ内の <literal>data</literal> ファ" +"イルにマップされます。" + +#. Tag: para +#: CacheLoader_FAQ.xml:49 +#, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.jdbm.JdbmCacheLoader</literal> : this " +"implementation is based on<ulink url=\"http://jdbm.sourceforge.net/\"> JDBM</" +"ulink>, an open source file-based transactional persistence engine." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:58 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.bdbje.BdbjeCacheLoader</literal> : this " +"implementation is based on the Oracle's Berkeley DB Java Edition database, a " +"fast and efficient transactional database. It uses a single file for the " +"entire store. Note that if you use the Berkeley DB cache loader with JBoss " +"Cache and wish to ship your product, you will have to acquire a <ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">commercial license from Oracle</" +"ulink>." +msgstr "" +"BdbjeCacheLoader: 速度が速く、効率的なトランザクションデータベースである " +"Sleepycat Java Edition データベースを基にした実装です。ストア全体に対して 1 " +"つのファイルを使用します。Sleepycat の CacheLoader を JBoss Cache に使用し、" +"製品として同梱したい場合は、<ulink url=\"http://www.sleepycat.com/" +"jeforjbosscache\">Sleepycat の商用ライセンス</ulink>を取得する必要がありま" +"す。" + +#. Tag: para +#: CacheLoader_FAQ.xml:71 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.JDBCCacheLoader</literal> : this " +"implementation uses the relational database as the persistent storage." +msgstr "" +"JDBCCacheLoader: この実装は、リレーショナルデータベースを永続ストレージとして" +"使用します。" + +#. Tag: para +#: CacheLoader_FAQ.xml:79 +#, fuzzy, no-c-format +msgid "" +"And more. See the chapter on cache loaders in the Users' Guide for more " +"details." +msgstr "その他の実装については、ドキュメンテーションをご覧ください。" + +#. Tag: para +#: CacheLoader_FAQ.xml:88 +#, no-c-format +msgid "Is the FileCacheLoader recommended for production use?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:92 +#, no-c-format +msgid "" +"No, it is not. The FileCacheLoader has some severe limitations which " +"restrict its use in a production environment, or if used in such an " +"environment, it should be used with due care and sufficient understanding of " +"these limitations." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:99 +#, no-c-format +msgid "" +"Due to the way the FileCacheLoader represents a tree structure on disk " +"(directories and files) traversal is inefficient for deep trees." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:103 +#, no-c-format +msgid "" +"Usage on shared filesystems like NFS, Windows shares, etc. should be avoided " +"as these do not implement proper file locking and can cause data corruption." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:107 +#, no-c-format +msgid "" +"Usage with an isolation level of NONE can cause corrupt writes as multiple " +"threads attempt to write to the same file." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:111 +#, no-c-format +msgid "" +"File systems are inherently not transactional, so when attempting to use " +"your cache in a transactional context, failures when writing to the file " +"(which happens during the commit phase) cannot be recovered." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:120 +#, no-c-format +msgid "" +"As a rule of thumb, it is recommended that the FileCacheLoader not be used " +"in a highly concurrent, transactional or stressful environment, and its use " +"is restricted to testing." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:130 +#, fuzzy, no-c-format +msgid "Can writing to cache loaders be asynchronous?" +msgstr "CacheLoader への書き込みを非同期にできますか？" + +#. Tag: para +#: CacheLoader_FAQ.xml:134 +#, fuzzy, no-c-format +msgid "" +"Yes. Set the <literal>async</literal> attrobute to true. See the JBoss Cache " +"Users' Guide for a more detailed discussion. By default though, all cache " +"loader writes are synchronous and will block." +msgstr "" +"JBossCache 1.2.4 より非同期に対応しています。CacheLoaderAsynchronous プロパ" +"ティを true に設定します。詳細については、JBossCache のドキュメンテーションを" +"ご覧ください。デフォルトの設定では、キャッシュローダーはすべて非同期で書き込" +"みを行い、ブロックします。" + +#. Tag: para +#: CacheLoader_FAQ.xml:145 +#, fuzzy, no-c-format +msgid "Can I write my own cache loader ?" +msgstr "独自の CacheLoader を書くことはできますか？" + +#. Tag: para +#: CacheLoader_FAQ.xml:149 +#, fuzzy, no-c-format +msgid "" +"Yes. A cache loader is a class implementing <literal>org.jboss.cache.loader." +"CacheLoader</literal> or extending <literal>org.jboss.cache.loader." +"AbstractCacheLoader</literal> . It is configured via the XML file (see JBoss " +"Cache Users' Guide)." +msgstr "" +"可能です。CacheLoader は <literal>org.jboss.cache.loader.CacheLoader</" +"literal> を実装するクラスです。設定は XML ファイルで行います（JBossCache と" +"チュートリアルのドキュメンテーションを参照してください）。 " + +#. Tag: para +#: CacheLoader_FAQ.xml:161 +#, fuzzy, no-c-format +msgid "Does a cache loader have to use a persistent store ?" +msgstr "CacheLoader は永続ストアを使用しなければなりませんか？" + +#. Tag: para +#: CacheLoader_FAQ.xml:165 +#, fuzzy, no-c-format +msgid "" +"No, a cache loader could for example fetch (and possibly store) its data " +"from a webdav-capable webserver. Another example is a caching proxy server, " +"which fetches contents from the web. Note that an implementation of " +"CacheLoader may not implement the 'store' functionality in this case, but " +"just the 'load' functionality." +msgstr "" +"使用する必要はありません。例えば、CacheLoader は webdav 対応のウェブサーバー" +"よりデータを読み出しすることができます（可能な場合は保存もできます）。また、" +"ウェブよりコンテンツを取得するキャッシングプロキシサーバーも利用できます。こ" +"の場合、CacheLoader の実装は「ロード」機能のみ実装し、「保存」機能は実装しな" +"い場合があります。" + +#. Tag: para +#: CacheLoader_FAQ.xml:177 +#, fuzzy, no-c-format +msgid "Do I have to pay to use Oracle's Berkeley DB CacheLoader?" +msgstr "Sleepycat の CacheLoader の使用は有料ですか？" + +#. Tag: para +#: CacheLoader_FAQ.xml:181 +#, fuzzy, no-c-format +msgid "" +"Not if you use it only for personal use. As soon as you distribute your " +"product with BdbjeCacheLoader, you have to purchase a commercial license " +"from Oracle. See details at <ulink url=\"http://www.sleepycat.com/" +"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ." +msgstr "" +"個人的に使用する場合は無料です。BdbjeCacheLoader を含む製品を配布する場合は、" +"Sleepycat より商用ライセンスを購入する必要があります。詳細は、<ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">http://www.sleepycat.com/" +"jeforjbosscache </ulink> をご覧ください。" + +#. Tag: para +#: CacheLoader_FAQ.xml:194 +#, no-c-format +msgid "Are there any tools available to monitor the Berkeley DB instance?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:198 +#, no-c-format +msgid "" +"Yes. Oracle ships a JMX-based monitoring tool, called <ulink url=\"http://" +"www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/" +"jmx/JEMonitor.html\"> JEMonitor </ulink> which can be downloaded from the " +"Oracle website." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:211 +#, no-c-format +msgid "" +"When tuning my Berkeley DB instance, where should I put my je.properties " +"file?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:215 +#, no-c-format +msgid "" +"<literal>je.properties</literal> should reside in your Berkeley DB home " +"directory. This is the directory you pass in to the BDBJECacheLoader's " +"<literal>location</literal> configuration property." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:227 +#, no-c-format +msgid "Can I use more than one cache loader?" +msgstr "複数のキャッシュローダーを使用することはできますか？" + +#. Tag: para +#: CacheLoader_FAQ.xml:231 +#, fuzzy, no-c-format +msgid "" +"Yes. Within the CacheLoaderConfiguration XML element (see Users' Guide " +"chapter on cache loaders) you can describe several cache loaders. The impact " +"is that the cache will look at all of the cache loaders in the order they've " +"been configured, until it finds a valid, non-null element of data. When " +"performing writes, all cache loaders are written to (except if the " +"ignoreModifications element has been set to true for a specific cache loader." +msgstr "" +"JBossCache 1.3.0 より複数のキャッシュローダーを使用できるようになりました。新" +"たに導入された CacheLoaderConfiguration XML 要素（詳細はキャッシュローダーに" +"関するユーザーマニュアルを参照）を使用して、複数のキャッシュローダーを指定で" +"きます。この結果、有効な null 要素でないデータが見つかるまで、キャッシュは設" +"定された順番ですべてのキャッシュローダーを確認します。書き込みは、すべての" +"キャッシュローダーに対して行われます（ignoreModifications 要素が true に設定" +"されてるキャッシュローダーがある場合を除く）。" + +#. Tag: para +#: CacheLoader_FAQ.xml:245 +#, no-c-format +msgid "" +"Can I migrate a JDBCacheLoader or FileCacheLoader based cache store " +"containing data formatted with JBoss Cache 1.x.x to JBoss Cache 2.0 format?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:250 +#, no-c-format +msgid "" +"Yes. See \"Transforming Cache Loaders\" section within the \"Cache Loaders\" " +"section located in the JBoss Cache Users' Guide." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:257 +#, no-c-format +msgid "Is the TCPDelegatingCacheLoader resilient to TCPCacheServer restarts?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:263 +#, no-c-format +msgid "" +"As of JBoss Cache 2.1.0, the answer is yes. See the Users' Guide for details " +"on how to configure and tune your retries and wait period for reestablishing " +"the TCP connection." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:269 +#, no-c-format +msgid "" +"Prior to that, restarting the TCPCacheServer would also mean restarting your " +"application that uses the cache." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Eviction_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Eviction_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Eviction_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,165 @@ +# translation of Colophon.po to Japanese +# Noriko Mizumoto <noriko(a)redhat.com&gt;, 2007. +# Junko Ito <junko.ito(a)rehdat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-05 08:49+1000\n" +"Last-Translator: Junko Ito <junko.ito(a)rehdat.com&gt;\n&quot; +"Language-Team: Japanese <ja(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Eviction_FAQ.xml:6 +#, no-c-format +msgid "Eviction Policies" +msgstr "エビクションポリシー" + +#. Tag: para +#: Eviction_FAQ.xml:10 +#, no-c-format +msgid "Does JBoss Cache support eviction policies?" +msgstr "JBoss Cache はエビクションポリシーをサポートしていますか？" + +#. Tag: para +#: Eviction_FAQ.xml:14 +#, no-c-format +msgid "" +"Yes. JBoss Cache currently supports multiple eviction policies such as LRU, " +"MRU, and FIFO. Users can also plug in their own eviction policy algorithms. " +"See user guide for details." +msgstr "" + +#. Tag: para +#: Eviction_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "Does JBoss Cache's eviction policy operates in replication mode?" +msgstr "" +"JBoss Cache の実装された LRU エビクションポリシーはレプリケーションモードで動" +"作しますか？" + +#. Tag: para +#: Eviction_FAQ.xml:29 +#, no-c-format +msgid "Yes and no. :-)" +msgstr "場合によります。" + +#. Tag: para +#: Eviction_FAQ.xml:31 +#, fuzzy, no-c-format +msgid "" +"The eviction policy only operates in local mode. That is, nodes are only " +"evicted locally. This may cause the cache contents not to be synchronized " +"temporarily. But when a user tries to obtain the cached contents of an " +"evicted node and finds out that is null (e.g., <literal>get</literal> " +"returns null), it should get it from the other data source and re-populate " +"the data in the cache. During this moment, the node content will be " +"propagated and the cache content will be in sync." +msgstr "" +"LRU ポリシーはローカルモードでのみ動作します。そのため、ノードはローカルでの" +"みエビクトされ、これにより一時的にキャッシュの内容が同期されないことがありま" +"す。しかし、エビクトされたノードのキャッシュの内容を取得しようとし、それが " +"null だと分かった場合（例：<literal>get</literal> は null を返します）、他の" +"データソースから取得し、キャッシュのデータを再度投入するはずです。その間、" +"ノードの内容は伝搬され、キャッシュの内容は同期されます。" + +#. Tag: para +#: Eviction_FAQ.xml:42 +#, no-c-format +msgid "" +"However, you still can run eviction policies with cache mode set to either " +"<literal>REPL_SYNC</literal> or <literal>REPL_ASYNC</literal> . Depending on " +"your use case, you can set multiple cache instances to have their own " +"eviction policy (which are applied locally) or just have selected instances " +"with eviction policies activated." +msgstr "" +"キャッシュモードを <literal>REPL_SYNC</literal> または <literal>REPL_ASYNC</" +"literal> に設定してエビクションポリシーを実行することもできます。ユースケース" +"によっては、複数のキャッシュインスタンスを設定して独自のエビクションポリシー" +"を持ったり（ローカルで適応されます）、エビクションポリシーをアクティブにして" +"一部のインスタンスのみを持つこともできます。" + +#. Tag: para +#: Eviction_FAQ.xml:53 +#, no-c-format +msgid "" +"Also note that, with cache loader option, a locally evicted node can also be " +"persisted to the backend store and a user can retrieve it from the store " +"later on." +msgstr "" +"また、キャッシュローダーオプションを利用すると、ローカルでエビクトされたノー" +"ドをバックエンドストアへ永続化することもでき、後にそのノードをバックエンドス" +"トアより読み出すこともできます。" + +#. Tag: para +#: Eviction_FAQ.xml:62 +#, no-c-format +msgid "Does JBoss Cache support <literal>Region</literal> ?" +msgstr "JBoss Cache は <literal>Region</literal> をサポートしていますか？" + +#. Tag: para +#: Eviction_FAQ.xml:69 +#, no-c-format +msgid "" +"Yes. JBoss Cache has the notion of region where a user can configure the " +"eviction policy parameters (e.g., <literal>maxNodes</literal> or " +"<literal>timeToIdleSeconds</literal> )" +msgstr "" +"サポートしています。JBoss Cache はエビクションポリシーパラメータを設定するリ" +"ジョンの概念を持っています (例：<literal>maxNodes</literal>、" +"<literal>timeToIdleSeconds</literal> など)。" + +#. Tag: para +#: Eviction_FAQ.xml:77 +#, fuzzy, no-c-format +msgid "" +"A region in JBoss Cache denotes a portion of tree hierarchy, e.g., a fully " +"qualified name ( <literal>org.jboss.cache.Fqn</literal> ). For example, a " +"user can define <literal>/org/jboss</literal> and <literal>/org/foocom</" +"literal> as two separate regions. But note that you can configure the region " +"programmatically now, i.e., everything has to be configured through the xml " +"file." +msgstr "" +"JBoss Cache におけるリジョンとは、完全修飾名（<literal>FQN</literal>）などの" +"ツリー階層の一部を意味します。例えば、<literal>/org/jboss</literal> と " +"<literal>/org/foocom</literal> を個別の 2 つのリジョンとして定義できますが、" +"現在リジョンはプログラム化して設定することができます（例：すべて xml ファイル" +"で設定されなければならない）。" + +#. Tag: para +#: Eviction_FAQ.xml:94 +#, no-c-format +msgid "" +"I have turned on the eviction policy, why do I still get \"out of memory" +"\" (OOM) exception?" +msgstr "" +"エビクションポリシーを有効にしたのに「メモリー不足」(OOM) 例外が発生するのは" +"なぜですか？" + +#. Tag: para +#: Eviction_FAQ.xml:100 +#, fuzzy, no-c-format +msgid "" +"OOM can happen when the speed of cache access exceeds the speed of eviction " +"policy handling timer. Eviction policy handler will wake up every " +"<literal>wakeUpInterval</literal> milliseconds (or " +"<literal>wakeUpIntervalSeconds</literal> seconds, prior to 3.x) to process " +"the eviction event queue. So when the queue size is full, it will create a " +"backlog and cause out-of-memory exceptions to happen unless the eviction " +"timer catches up. To address this problem, in addition to increase the VM " +"heap size, you can also reduce the <literal>wakeUpInterval</literal> so the " +"timer thread processes the queue more frequently." +msgstr "" +"キャッシュのアクセス速度がタイマーに対応するエビクションポリシーの速度を越え" +"ると OOM が発生します。エビクションポリシーハンドラーは、" +"<literal>wakeUpIntervalInSeconds</literal> 秒毎にウェイクアップし、エビクショ" +"ンイベントキューを処理します。また、キューのサイズは現在 20000 に固定されてい" +"ます。そのため、キューのサイズが満杯になるとバックログが発生するため、エビク" +"ションタイマーが処理に追いつかないと OOM が発生します。この問題に対応し、VM " +"ヒープサイズを増強するには、<literal>wakeUpIntervaleInSeconds</literal> の値" +"を小さくし、タイマースレッドがキューをより頻繁に処理するようにします。" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/General_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/General_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/General_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,166 @@ +# translation of Colophon.po to Japanese +# Noriko Mizumoto <noriko(a)redhat.com&gt;, 2007. +# Junko Ito <junko.ito(a)rehdat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-05 08:49+1000\n" +"Last-Translator: Junko Ito <junko.ito(a)rehdat.com&gt;\n&quot; +"Language-Team: Japanese <ja(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: General_FAQ.xml:6 +#, no-c-format +msgid "General Information" +msgstr "一般的な情報" + +#. Tag: para +#: General_FAQ.xml:10 +#, no-c-format +msgid "What is JBoss Cache?" +msgstr "JBoss Cache とは何ですか？" + +#. Tag: para +#: General_FAQ.xml:14 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache is a replicated and transactional cache. It is replicated since " +"multiple JBoss Cache instances can be distributed (either within the same " +"JVM or across several JVMs whether they reside on the same machine or on " +"different machines on a network) and data is replicated across the whole " +"group. It is transactional because a user can configure a <ulink url=" +"\"http://java.sun.com/products/jta/\">JTA</ulink> compliant transaction " +"manager and make any cache interaction transactional, and caches would " +"participate in ongoing JTA transactions. Note that the cache can also be run " +"without any replication; this is the local mode." +msgstr "" +"JBoss Cache はレプリケートされたトランザクションキャッシュです。複数の JBoss " +"Cache インスタンスを配布できるため、レプリケートされています（同じ JVM 内での" +"配布か、同じマシンまたはネットワーク上の異なるマシン上に存在する複数の JVM 間" +"での配布）。データはグループ全体でレプリケートされます。ユーザーが JTA 準拠の" +"トランザクションマネージャを設定でき、キャッシュ動作をトランザクション化でき" +"るため、トランザクションキャッシュになります。キャッシュはレプリケーションな" +"しでも実行でき、これをローカルモードと呼びます。" + +#. Tag: para +#: General_FAQ.xml:28 +#, no-c-format +msgid "" +"JBoss Cache comes in two flavours: Core and POJO versions. The core library " +"(using the <literal>org.jboss.cache.Cache</literal> interface) is the " +"underlying library that organises data in a tree-like structure and handles " +"all locking, passivation, eviction and replication characteristics of data " +"in the cache. The POJO library (using the <literal>org.jboss.cache.pojo." +"PojoCache</literal> interface) is built atop the core library and allows " +"introspection of objects in the cache providing transparent coherence by " +"using JBoss AOP. Note that the POJO edition of JBoss Cache (often referred " +"to as POJO Cache) comes with a separate set of documentation (Users' Guide, " +"FAQ, etc.) available on the JBoss Cache <ulink url=\"http://www.jboss.org/" +"jbosscache/\">documentation website</ulink>." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:66 +#, no-c-format +msgid "Who are the JBoss Cache developers?" +msgstr "JBoss Cache の開発者は誰ですか？" + +#. Tag: para +#: General_FAQ.xml:70 +#, no-c-format +msgid "" +"JBoss Cache has an active community of developers and contributors. The " +"project was founded by Bela Ban and is currently led by Manik Surtani. Jason " +"Greene is the lead for the POJO Cache subsystem, and other contributors both " +"past and present include Ben Wang, Harald Gliebe, Brian Stansberry, Vladimir " +"Blagojevic, Mircea Markus, Jimmy Wilson, Galder Zamarreño and Elias Ross." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:139 +#, no-c-format +msgid "How do I know the version of JBoss Cache that I am using?" +msgstr "使用している JBoss Cache のバージョンを確認する方法を教えてください。" + +#. Tag: para +#: General_FAQ.xml:143 +#, no-c-format +msgid "" +"<literal>java -jar jbosscache-core.jar</literal> will spit out version " +"details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:152 +#, fuzzy, no-c-format +msgid "" +"Can I run JBoss Cache outside of the JBoss Enterprise Application Platform?" +msgstr "JBoss Application Server の外部で JBoss Cache を実行できますか？" + +#. Tag: para +#: General_FAQ.xml:157 +#, no-c-format +msgid "" +"Absolutely! Even though JBoss Cache comes integrated with the JBoss " +"Enterprise Application Platform, it can also be used in any other Java EE " +"server such as BEA WebLogic, IBM Websphere or Tomcat. It can also run in a " +"standalone Java process, completely outside of an application server. See " +"the Users' Guide for more details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:170 +#, no-c-format +msgid "" +"How can I migrate my application and configuration from using JBoss Cache 1." +"x to 2.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:173 +#, no-c-format +msgid "" +"Look at <ulink url=\"http://www.jboss.org/community/docs/DOC-10246\">this " +"wiki page</ulink> for help." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:182 +#, no-c-format +msgid "What about from 2.x to 3.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:185 +#, no-c-format +msgid "" +"JBoss Cache 3.x is API compatible with 2.x, although as far as possible you " +"should refactor your code not to use deprecated methods as these may " +"disappear in future releases of JBoss Cache." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:190 +#, no-c-format +msgid "" +"JBoss Cache 3.x comes with an all new configuration format. Old 2.x " +"configuration files will still work, although you will get a warning in the " +"logs about this. Again, as far as possible, we recommend migrating your " +"configuration file to the new format. Scripts are provided with the JBoss " +"Cache 3.x distribution to migrate configuration files (see " +"<literal>config2to3.sh</literal> and<literal>config2to3.bat</literal>)." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:201 +#, no-c-format +msgid "" +"Note that to take advantage of some of the new features in JBoss Cache 3.x, " +"you need to be using the new configuration format." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/JBoss_Cache_Frequently_Asked_Questions.po =================================================================== Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Revision_History.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Revision_History.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Revision_History.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,27 @@ +# translation of Colophon.po to Japanese +# Noriko Mizumoto <noriko(a)redhat.com&gt;, 2007. +# Junko Ito <junko.ito(a)rehdat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-05 08:49+1000\n" +"Last-Translator: Junko Ito <junko.ito(a)rehdat.com&gt;\n&quot; +"Language-Team: Japanese <ja(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Revision_History.xml:6 +#, no-c-format +msgid "Revision History" +msgstr "" + +#. Tag: author +#: Revision_History.xml:12 +#, fuzzy, no-c-format +msgid "<firstname></firstname> <surname></surname> <email></email>" +msgstr "<firstname>John</firstname> <surname>Doe</surname>" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/TreeCache_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/TreeCache_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/TreeCache_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,1060 @@ +# translation of Colophon.po to Japanese +# Noriko Mizumoto <noriko(a)redhat.com&gt;, 2007. +# Junko Ito <junko.ito(a)rehdat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-05 08:49+1000\n" +"Last-Translator: Junko Ito <junko.ito(a)rehdat.com&gt;\n&quot; +"Language-Team: Japanese <ja(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: TreeCache_FAQ.xml:6 +#, fuzzy, no-c-format +msgid "JBoss Cache: Core" +msgstr "JBoss Cache 1.4.1" + +#. Tag: para +#: TreeCache_FAQ.xml:26 +#, no-c-format +msgid "Can I run multiple JBoss Cache instances on the same VM?" +msgstr "同じ VM で複数の JBoss Cache インスタンスを実行できますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:30 +#, no-c-format +msgid "" +"Yes. There are some scenarios where you may want to run multiple instances " +"of JBoss Cache. For example, you want to run multiple local cache instances " +"with each instance having its own configuration (e.g., different cache " +"policy). In this case, you will need multiple xml configuration files." +msgstr "" +"実行できます。独自の設定（例：異なるキャッシュポリシーなど）を持つローカル" +"キャッシュインスタンスを複数実行したい時など、JBoss Cache のインスタンスを複" +"数実行したい場合があります。この例の場合、xml 形式の設定ファイルが複数必要と" +"なります。" + +#. Tag: para +#: TreeCache_FAQ.xml:41 +#, fuzzy, no-c-format +msgid "Can JBoss Cache run as a second level cache inside Hibernate?" +msgstr "" +"TreeCache を第 2 レベルキャッシュとして Hibernate 内部で実行することはできま" +"すか？" + +#. Tag: para +#: TreeCache_FAQ.xml:47 +#, fuzzy, no-c-format +msgid "" +"Yes. Since Hibernate 3.0 release, you can configure it to use JBoss Cache as " +"a second level cache. For details, see Hibernate documentation, and also see " +"<ulink url=\"http://www.jboss.org/community/docs/DOC-10265\">this wiki page</" +"ulink>." +msgstr "" +"Hibernate 3.0 リリースとそれ以降のリリースでは、JBoss Cache (TreeCache) を第 " +"2 キャッシュとして設定し、使用できます。詳細については、Hibernate のドキュメ" +"ンテーションおよび <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?" +"page=JBossCacheHibernate\"> http://wiki.jboss.org/wiki/Wiki.jsp?" +"page=JBossCacheHibernate </ulink> をご覧ください。" + +#. Tag: para +#: TreeCache_FAQ.xml:52 +#, no-c-format +msgid "" +"JBoss Cache 3.x with MVCC in particular works very well as a Hibernate " +"second level cache." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:60 +#, fuzzy, no-c-format +msgid "What about using POJO Cache as a Hibernate cache?" +msgstr "PojoCache を Hibernate のキャッシュとして使用できますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:64 +#, fuzzy, no-c-format +msgid "" +"It is not necessary to use POJO Cache for second level cache inside " +"Hibernate because Hibernate manages fine-grained fields in Java objects. " +"Using POJO Cache won't provide any advantage, and will be an unnecessary " +"performance drawback." +msgstr "" +"Hibernate は Java オブジェクトの細かなフィールドを管理するため、Hibernate 内" +"部で PojoCache を第 2 レベルキャッシュとして使用する必要はありません。よっ" +"て、PojoCache を使用する利点はありません。" + +#. Tag: para +#: TreeCache_FAQ.xml:74 +#, no-c-format +msgid "How can I configure JBoss Cache?" +msgstr "JBoss Cache の設定方法を教えてください。" + +#. Tag: para +#: TreeCache_FAQ.xml:78 +#, no-c-format +msgid "" +"You can configure the JBoss Cache through a configuration xml file or " +"programmatically using a <literal>org.jboss.cache.config.Configuration</" +"literal> object, passed in to the <literal>org.jboss.cache.CacheFactory</" +"literal> instance." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:90 +#, no-c-format +msgid "" +"Can I use a schema or DTD to validate my JBoss Cache configuration file?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:95 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, yes. An XSD schema is provided in your jbosscache-" +"core.jar file, and is also available online, on<ulink url=\"http://www.jboss." +"org/jbosscache/jbosscache-config-3.0.xsd\"> http://www.jboss.org/jbosscache/" +"jbosscache-config-3.0.xsd</ulink>. You can configure your IDE, text editor " +"or XML authoring tool to use this schema to validate your file." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:108 +#, no-c-format +msgid "What is the difference between the different cache modes?" +msgstr "キャッシュモードの違いを教えてください。" + +#. Tag: para +#: TreeCache_FAQ.xml:113 +#, no-c-format +msgid "" +"JBossCache has five different cache modes, i.e., <literal>LOCAL</literal> , " +"<literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> and <literal>INVALIDATION_ASYNC</" +"literal> . If you want to run JBoss Cache as a single instance, then you " +"should set the cache mode to <literal>LOCAL</literal> so that it won't " +"attempt to replicate anything. If you want to have synchronous replication " +"among different JBoss Cache instances, you set it to <literal>REPL_SYNC</" +"literal> . For asynchronous replication, use <literal>AYSNC_REPL</literal> . " +"If you do not wish to replicate cached data but simply inform other caches " +"in a cluster that data under specific addresses are now stale and should be " +"evicted from memory, use <literal>INVALIDATION_SYNC</literal> or " +"<literal>INVALIDTAION_ASYNC</literal> . Synchronous and asynchronous " +"behavior applies to invalidation as well as replication." +msgstr "" +"JBossCache には、<literal>LOCAL</literal>、<literal>REPL_SYNC</literal>、" +"<literal>REPL_ASYNC</literal>、<literal>INVALIDATION_SYNC</literal>、" +"<literal>INVALIDATION_ASYNC</literal> の 5 つのキャッシュモードがあります。" +"JBoss Cache を単一のインスタンスとして実行する場合は、レプリケートしないよう" +"にキャッシュモードを <literal>LOCAL</literal> に設定します。異なる JBoss " +"Cache インスタンス間で同期レプリケーションを行う場合は、<literal>REPL_SYNC</" +"literal> に設定します。非同期レプリケーションの場合は <literal>AYSNC_REPL</" +"literal> を設定します。キャッシュしたデータをレプリケートせずに、特定アドレス" +"下の陳腐化したデータをメモリーより削除すべきであることをクラスタの他のキャッ" +"シュに通知したい場合は、<literal>INVALIDATION_SYNC</literal> または " +"<literal>INVALIDTAION_ASYNC</literal> を設定します。同時および非同期の動作" +"は、インバリデーションおよびレプリケーションに適応されます。" + +#. Tag: para +#: TreeCache_FAQ.xml:143 +#, no-c-format +msgid "" +"Note that <literal>ASYNC_REPL</literal> and <literal>INVALIDATION_ASYNC</" +"literal> are non-blocking. This can be useful when you want to have another " +"JBoss Cache serving as a mirror or backup and you don't want to wait for " +"confirmation that this mirror has received your messages." +msgstr "" +"<literal>ASYNC_REPL</literal> および <literal>INVALIDATION_ASYNC</literal> は" +"非ブロッキングであることに注意してください。これは、他の JBoss Cache をミラー" +"またはバックアップをして使用する場合に便利で、ミラーのメッセージ受信を確認す" +"るための待ち時間が発生しません。" + +#. Tag: para +#: TreeCache_FAQ.xml:157 +#, no-c-format +msgid "How does JBoss Cache's replication mechanism work?" +msgstr "JBoss Cache のレプリケーションメカニズムについて教えてください。" + +#. Tag: para +#: TreeCache_FAQ.xml:161 +#, no-c-format +msgid "" +"JBoss Cache leverages <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"for network communications. A JGroups configuration section is present in " +"your JBoss Cache configuration." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:166 +#, fuzzy, no-c-format +msgid "" +"A user can configure the cluster of JBoss Cache instances by sharing the " +"same cluster name ( <literal>cluster name</literal> ). There is also an " +"option of whether to populate the cache data upon starting a new instance in " +"the <literal>ClusterConfig</literal> attribute." +msgstr "" +"JBoss Cache は <ulink url=\"http://www.jgroups.org\">JGroups</ulink> をレプリ" +"ケーション層として使用します。JBoss Cache インスタンスのクラスタを設定するに" +"は、同じクラスタ名 (<literal>cluster name</literal>) を共有するようにします。" +"また、新しいインスタンスの開始時にキャッシュデータを投入するかは " +"<literal>ClusterConfig</literal> 属性でオプションとして指定できます。" + +#. Tag: para +#: TreeCache_FAQ.xml:178 +#, fuzzy, no-c-format +msgid "" +"Note that once all instances join the same replication group, every " +"replication change is propagated to all participating members. There is no " +"mechanism for sub-partitioning where some replication can be done within " +"only a subset of members, unless you use the Buddy Replication features. See " +"the Users' Guide for more details on this." +msgstr "" +"すべてのインスタンスが同じレプリケーショングループに参加すると、レプリケー" +"ションの変更がすべての参加メンバーに伝搬されます。メンバーの一部によってレプ" +"リケーションを行えるようなサブパーティションのメカニズムは存在しません。この" +"メカニズムは、今後の開発される予定です。" + +#. Tag: para +#: TreeCache_FAQ.xml:190 +#, no-c-format +msgid "" +"I run a 2 node cluster. If the network dies, do the caches continue to run?" +msgstr "" +"2 ノードクラスタを使用しています。ネットワークに障害が発生した場合、キャッ" +"シュの実行は維持されますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:194 +#, no-c-format +msgid "" +"Yes, both will continue to run, but depending on your replication mode, all " +"transactions or operations may not complete. If <literal>REPL_SYNC</literal> " +"is used, operations will fail while if <literal>REPL_ASYNC</literal> is used " +"they will succeed. Even if they succeed though, caches will be out of sync." +msgstr "" +"両キャッシュの実行が維持されますが、レプリケーションモードによってはトランザ" +"クションや操作がすべて完全に行われない場合があります。<literal>REPL_SYNC</" +"literal> の場合は操作に失敗しますが、<literal>REPL_ASYNC</literal> の場合は操" +"作に成功します。成功しても、キャッシュは非同期の状態になります。" + +#. Tag: para +#: TreeCache_FAQ.xml:207 +#, no-c-format +msgid "" +"Can I plug in library X instead of JGroups to handle remote calls and group " +"communications?" +msgstr "" +"リモート呼び出しやグループ通信に対応するため、JGroups の代わりに library X を" +"接続することはできますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:212 +#, fuzzy, no-c-format +msgid "" +"At this stage the answer is no. We do have an abstraction layer between the " +"communication suite and JBoss Cache in the pipelines, and this may appear as " +"a feature at some stage in the future." +msgstr "" +"現時点 (JBoss Cache 1.x) ではできません。パイプラインのコミュニケーションス" +"イートと JBoss Cache の間に抽象層があるため、将来的には機能として導入されるか" +"もしれません。" + +#. Tag: para +#: TreeCache_FAQ.xml:223 +#, no-c-format +msgid "" +"Does the cache need to replicate to every other instance in the cluster? " +"Isn't this slow if the cluster is large?" +msgstr "" +"キャッシュはクラスタ内にある他すべてのインスタンスに対してレプリケートする必" +"要がありますか？クラスタが大きい場合、処理に時間がかかりませんか？" + +#. Tag: para +#: TreeCache_FAQ.xml:230 +#, fuzzy, no-c-format +msgid "" +"Replication need not occur to every node in the cluster. This feature - " +"called Buddy Replication - allows each node to pick one or more 'buddies' in " +"the cluster and only replicate to its buddies. This allows a cluster to " +"scale very easily with no extra impact on memory or network traffic with " +"each node added." +msgstr "" +"JBoss Cache 1.4.0 より、クラスタ内にあるすべてのノードに対してレプリケーショ" +"ンを行う必要がなくなりました。この機能はバディーレプリケーションと呼ばれ、各" +"ノードはクラスタ内で 1 つ以上の「バディー」を選択し、このバディーに対してのみ" +"レプリケートすることができます。これにより、ノードが追加されてもメモリーや" +"ネットワークトラフィックは影響を受けないため、クラスターの拡張が容易になりま" +"す。" + +#. Tag: para +#: TreeCache_FAQ.xml:237 +#, fuzzy, no-c-format +msgid "" +"See the Users' Guide for more information on Buddy Replication, and how it " +"can be used to achieve very high scalability." +msgstr "" +"バディーレプリケーションの詳細や高拡張性の実現方法については、「ユーザーガイ" +"ド」をご覧ください。" + +#. Tag: para +#: TreeCache_FAQ.xml:248 +#, no-c-format +msgid "" +"I'm using Buddy Replication. Do I need to have some form of session affinity?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:251 +#, no-c-format +msgid "" +"Session affinity relates to returning to the same cache instance for the " +"same data being used. While this is strictly not a requirement for Buddy " +"Replication, it is greatly recommended to minimize moving state around a " +"cluster." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:261 +#, fuzzy, no-c-format +msgid "" +"If I have the need for different configuration properties (e.g., " +"<literal>CacheMode</literal> and <literal>IsolationLevel</literal> ), do I " +"simply need to create multiple <literal>org.jboss.cache.Cache</literal> " +"instances with the appropriate configuration?" +msgstr "" +"異なる TreeCache プロパティが必要な場合（例：<literal>CacheMode</literal> と " +"<literal>IsolationLevel</literal> など）、適切な設定のTreeCache を複数作成す" +"るだけでよいですか？ " + +#. Tag: para +#: TreeCache_FAQ.xml:272 +#, fuzzy, no-c-format +msgid "" +"Yes. All the above mentioned properties are per cache instance. Therefore " +"you will need separate <literal>org.jboss.cache.Cache</literal> instances." +msgstr "" +"その通りです。上記のプロパティはすべてキャッシュ毎のインスタンスです。よっ" +"て、個別の JBoss Cache インスタンスが必要になります。" + +#. Tag: para +#: TreeCache_FAQ.xml:282 +#, no-c-format +msgid "" +"Isn't this expensive from a networking standpoint, i.e., needing to create " +"sockets for each <literal>org.jboss.cache.Cache</literal> instance?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:289 +#, no-c-format +msgid "" +"Yes, it can be. For such cases it is recommended that you configure your " +"cache using the JGroups Multiplexer, which allows several caches to share a " +"single JGroups channel. Please see the Users' Guide for details on how to " +"configure the JGroups Multiplexer." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:296 +#, no-c-format +msgid "" +"A faster and more efficient approach is to use a shared transport in " +"JGroups. Please see <ulink url=\"http://www.jgroups.org\">the JGroups " +"documentation</ulink> for more details on how to do this." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:307 +#, fuzzy, no-c-format +msgid "" +"Does the <literal>ClusterName</literal> configuration element have any " +"relation to the JBoss AS cluster <literal>PartitionName</literal> ?" +msgstr "" +"Tree Cache の設定 <literal>ClusterName</literal> は、JBoss AS クラスタの " +"<literal>PartitionName</literal> と関係がありますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:317 +#, no-c-format +msgid "" +"Yes. They are both JGroups group names. Besides the notion of a channel in " +"JGroups, it also can partition the channel into different group names." +msgstr "" +"両方とも JGroups のグループ名です。JGroups におけるチャネルの概念だけでなく、" +"チャネルを異なるグループ名にパーティションすることができます。" + +#. Tag: para +#: TreeCache_FAQ.xml:326 +#, fuzzy, no-c-format +msgid "" +"When using multiple JGroups based components [cluster-service.xml, cache " +"(multiple instances)], what is the correct/valid way to configure those " +"components to make sure my multicast addresses don't conflict?" +msgstr "" +"JGroups ベースのコンポーネント [cluster-service.xml、treecache (複数インスタ" +"ンス)] を複数使用する場合に、マルチキャストアドレスが競合しないよう正しくコン" +"ポーネントを設定する方法を教えてください。" + +#. Tag: para +#: TreeCache_FAQ.xml:334 +#, no-c-format +msgid "" +"There are two parameters to consider: multicast address (plus port) and the " +"group name. At minimum, you will have to run components using a different " +"group name. But whether to run them on the same channel depends upon whether " +"the communication performance is critical for you or not. If it is, then " +"it'd be best to run them on different channels." +msgstr "" +"マルチキャストアドレス（およびポート）とグループ名の 2 つのパラメータを考慮し" +"なければなりません。最低でも、コンポーネントを異なるグループ名で実行するよう" +"にしなければなりません。同じチャネルで実行するかは、通信パフォーマンスの重要" +"度によって判断します。通信パフォーマンスが重要であれば、異なるチャネルで実行" +"した方がよいでしょう。" + +#. Tag: para +#: TreeCache_FAQ.xml:346 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache persistence storage?" +msgstr "現在、JBoss Cache はキャッシュの永続ストレージをサポートしていますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:352 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache has a cache loader interface that supports cache " +"persistence. See below for more FAQs on cache loaders." +msgstr "" +"サポートしています。JBoss Cache はリリース 1.1 よりキャッシュの永続をサポート" +"する CacheLoader インターフェイスを導入しています。以下を確認してください。" + +#. Tag: para +#: TreeCache_FAQ.xml:360 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache passivation/ overflow to a data store?" +msgstr "" +"現在、JBoss Cache はデータストアに対するキャッシュのパッシベーション／オー" +"バーフローをサポートしていますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:366 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache uses the cache loader to support cache passivation/ " +"overflow. See documentation on how to configure and use this feature." +msgstr "" +"サポートしています。キャッシュパッシベーション／オーバーフローをサポートする" +"ため、JBoss Cache はリリース 1.2.4. より Cache Loader を使用しています。この" +"機能の設定方法や使用方法についてはドキュメンテーションを参照してください。" + +#. Tag: para +#: TreeCache_FAQ.xml:375 +#, no-c-format +msgid "Is JBoss Cache thread safe?" +msgstr "JBoss Cache はスレッドセーフですか？" + +#. Tag: para +#: TreeCache_FAQ.xml:379 +#, no-c-format +msgid "Yes, it is thread safe." +msgstr "スレッドセーフです。" + +#. Tag: para +#: TreeCache_FAQ.xml:385 +#, no-c-format +msgid "Does JBoss Cache support XA (2PC) transactions now?" +msgstr "JBoss Cache は現在 XA (2PC) トランザクションをサポートしていますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:389 +#, fuzzy, no-c-format +msgid "" +"No, although it is also on our to do list. Our internal implementation does " +"use a procedure similar to 2PC to coordinate a transactions among different " +"instances, but JBoss Cache is not an XA resource." +msgstr "" +"現在サポートしていませんが、将来的に開発される予定です。内部実装は、異なるイ" +"ンスタンス間のトランザクションを調整するために似たような 2PC の手順を使用して" +"います。" + +#. Tag: para +#: TreeCache_FAQ.xml:398 +#, fuzzy, no-c-format +msgid "Which transaction managers are supported by JBoss Cache?" +msgstr "JBoss Cache がサポートする TransactionManager について教えてください。" + +#. Tag: para +#: TreeCache_FAQ.xml:404 +#, no-c-format +msgid "" +"JBoss Cache supports any TransactionManager that is <ulink url=\"http://java." +"sun.com/products/jta/\">JTA</ulink> compliant such as<ulink url=\"http://www." +"jboss.org/jbosstm/\">JBoss Transactions</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:408 +#, no-c-format +msgid "" +"While JBoss Cache does ships with a dummy transaction manager (<literal>org." +"jboss.cache.transaction.DummyTransactionManager</literal>), we do " +"<emphasis>not</emphasis> recommend using this for production. It is not " +"thread safe, and is intended for internal testing only." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:421 +#, no-c-format +msgid "How do I set up the cache to be transactional?" +msgstr "" +"キャッシュをトランザクション化するにはキャッシュをどのように設定したらよいで" +"すか？" + +#. Tag: para +#: TreeCache_FAQ.xml:425 +#, fuzzy, no-c-format +msgid "" +"You either use the default transaction manager that ships with JBoss AS or " +"you have to implement the <literal>org.jboss.cache.transaction." +"TransactionManagerLookup</literal> interface, and return an instance of your " +"<literal>javax.transaction.TransactionManager</literal> implementation. The " +"configuration property <literal>TransactionManagerLookupClass</literal> " +"defines the class to be used by the cache to fetch a reference to a " +"transaction manager. It is trivial to implement this interface to support " +"other transaction managers. Once this attribute is specified, the cache will " +"look up the transaction context from this transaction manager." +msgstr "" +"デフォルトの (JBoss) TransactionManager を使用して JBoss 内部で JBossCache を" +"実行するか、<literal>TransactionManagerLookup</literal> インターフェイスを実" +"装して javax.transaction.TransactionManager のインスタンスを返すようにしま" +"す。設定プロパティである <literal>TransactionManagerLookupClass</literal> " +"は、TransactionManager への参照を取得するためにキャッシュが使用するクラスを定" +"義します。他の TransactionManager をサポートするためにこのクラスを実装するこ" +"とは重要ではありません。属性が指定されると、キャッシュはトランザクションマ" +"ネージャよりトランザクションコンテキストをルックアップします。" + +#. Tag: para +#: TreeCache_FAQ.xml:441 +#, no-c-format +msgid "" +"The <literal>org.jboss.cache.transaction.GenericTransactionManagerLookup</" +"literal> class that ships with JBoss Cache is able to detect and bind to " +"most popular transaction managers. See the " +"<literal>GenericTransactionManagerLookup</literal> javadocs for more " +"information." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:454 +#, no-c-format +msgid "How do I control the cache locking level?" +msgstr "キャッシュロッキングレベルはどのように制御しますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:458 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache lets you control the cache locking level through the transaction " +"isolation level. This is configured through the attribute " +"<literal>IsolationLevel</literal> . The transaction isolation levels " +"correspond to database isolation levels, namely, <literal>NONE</literal> , " +"<literal>READ_UNCOMMITTED</literal> , <literal>READ_COMMITTED</literal> , " +"<literal>REPEATABLE_READ</literal> , and <literal>SERIALIZABLE</literal> . " +"Note that these isolation levels are ignored if optimistic locking is used. " +"For details, please refer to the user manual." +msgstr "" +"JBoss Cache では、トランザクション分離レベルよりキャッシュロッキングレベルを" +"制御できます。この設定は、<literal>IsolationLevel</literal> 属性より行いま" +"す。現在、JBossCache はペシミスティックロッキングを内部で採用しています。ペシ" +"ミスティックロッキングからのトランザクション分離レベルは、JDBC 分離レベルであ" +"る <literal>NONE</literal>、<literal>READ_UNCOMMITTED</literal>、" +"<literal>READ_COMMITTED</literal>、<literal>REPEATABLE_READ</literal>、" +"<literal>SERIALIZABLE</literal> に対応しています。オプティミスティックロッキ" +"ングが使用された場合は、これらの隔離レベルは無視されます。詳細については、" +"ユーザーマニュアルをご覧ください。" + +#. Tag: para +#: TreeCache_FAQ.xml:480 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, when using the MVCC locking scheme, only " +"<literal>READ_COMMITTED</literal> and <literal>REPEATABLE_READ</literal> are " +"supported. Any other isolation level provided will either be upgraded or " +"downgraded accordingly." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:493 +#, no-c-format +msgid "How does JBoss Cache lock data for concurrent access?" +msgstr "JBoss Cache は並行アクセスに対してどのようにデータをロックしますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:497 +#, fuzzy, no-c-format +msgid "" +"In JBoss Cache 2.x, by default pessimistic locking is used to lock data " +"nodes, based on the isolation level configured. We also offer optimistic " +"locking to allow for greater concurrency at the cost of slight processing " +"overhead and performance. See the documentation for a more detailed " +"discussion on concurrency and locking in JBoss Cache." +msgstr "" +"デフォルトでは、JBoss Cache は設定した隔離レベルを基にペシミスティックロッキ" +"ングを使用してデータノードをロックします。JBoss Cache 1.3.0 およびそれ以降で" +"は、オプティミスティックロッキングも提供しています。これにより、並行処理の能" +"力を向上できるようになりましたが、処理のオーバヘッドやパフォーマンスが若干悪" +"化します。JBoss Cache における並行処理やロッキングについての詳細はドキュメン" +"テーションをご覧ください。" + +#. Tag: para +#: TreeCache_FAQ.xml:505 +#, no-c-format +msgid "" +"In JBoss Cache 3.x, optimistic and pessimistic locking are deprecated in " +"favour of MVCC (multi-version concurrency control), which is far more " +"efficient than either optimistic or pessimistic locking. For a detailed " +"discussion on our MVCC implementation, see <ulink url=\"http://jbosscache." +"blogspot.com/2008/07/mvcc-has-landed.html\">this blog entry</ulink> " +"and<ulink url=\"http://www.jboss.org/community/docs/DOC-10272\">this wiki " +"page</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:520 +#, fuzzy, no-c-format +msgid "How do I enable Optimistic Locking or MVCC in JBoss Cache?" +msgstr "" +"JBoss Cache でオプティミスティックロッキングを有効にする方法を教えてくださ" +"い。" + +#. Tag: para +#: TreeCache_FAQ.xml:524 +#, no-c-format +msgid "Please see the configuration section of the Users' Guide for details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:532 +#, no-c-format +msgid "Can I use the cache locking level even without a transaction context?" +msgstr "" +"トランザクションコンテキストなしでキャッシュロッキングレベルを使用できます" +"か？" + +#. Tag: para +#: TreeCache_FAQ.xml:538 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache controls the individual node locking behavior through the " +"isolation level semantics. This means even if you don't use a transaction, " +"you can specify the lock level via isolation level. You can think of the " +"node locking behavior outside of a transaction as if it is under transaction " +"with <literal>auto_commit</literal> on." +msgstr "" +"使用できます。JBossCache は隔離レベルのセマンティクスにより各ノードロッキング" +"動作を制御します。そのため、トランザクションを使用しなくても、隔離レベルより" +"ロッキングレベルを指定することができます。トランザクション外部のノードロッキ" +"ング動作は、<literal>auto_commit</literal> が有効なトランザクション下の場合と" +"同様に考えることができます。" + +#. Tag: para +#: TreeCache_FAQ.xml:551 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache support <literal>SELECT FOR UPDATE</literal> semantics?" +msgstr "JBoss Cache は <literal>Region</literal> をサポートしていますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:559 +#, no-c-format +msgid "" +"Yes, but this is is only possible if you are running within a JTA " +"transaction <emphasis>and</emphasis> are using either <literal>MVCC</" +"literal> or <literal>PESSIMISTIC</literal> as your node locking scheme." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:568 +#, no-c-format +msgid "To achieve <literal>SELECT FOR UPDATE</literal> semantics, simply do:" +msgstr "" + +#. Tag: programlisting +#: TreeCache_FAQ.xml:573 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" // start transaction ... \n" +"\n" +" cache.getInvocationContext().getOptionOverrides().setForceWriteLock" +"(true);\n" +" Node n = cache.get(\"/a/b/c\"); // this acquires a WRITE LOCK on this " +"node\n" +" ...\n" +" ...\n" +"\n" +" // end transaction\n" +"\n" +" ]]>" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:579 +#, no-c-format +msgid "" +"With replication (REPL_SYNC/REPL_ASYNC) or invalidation (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), how often does the cache broadcast messages over the " +"network?" +msgstr "" +"レプリケーション (REPL_SYNC/REPL_ASYNC) または インバリデーション " +"(INVALIDATION_SYNC/INVALIDATION_ASYNC) の場合に、キャッシュがネットワーク上で" +"メッセージをブロードキャストする頻度を教えてください。" + +#. Tag: para +#: TreeCache_FAQ.xml:586 +#, fuzzy, no-c-format +msgid "" +"If the updates are under transaction, then the broadcasts happen only when " +"the transaction is about to commit (actually during the prepare stage " +"internally). That is, it will be a batch update. However, if the operations " +"are not under transaction context, then each update will trigger " +"replication. Note that this has performance implications if network latency " +"is a problem." +msgstr "" +"アップデートがトランザクション下である場合、トランザクションがコミットしよう" +"とする時（内部では準備段階）のみブロードキャストされます。よって、バッチアッ" +"プデートになりますが、操作がトランザクションコンテキスト下でない場合、各アッ" +"プデートによってレプリケーションがトリガされます。ネットワーク転送は通常重い" +"ため、パフォーマンスに影響します。" + +#. Tag: para +#: TreeCache_FAQ.xml:598 +#, no-c-format +msgid "How can I do a mass removal?" +msgstr "一括削除を行う方法を教えてください。" + +#. Tag: para +#: TreeCache_FAQ.xml:602 +#, fuzzy, no-c-format +msgid "" +"If you do a<literal>cache.removeNode(\"/myroot\")</literal>, it will " +"recursively remove all the entries under \"/myroot\"." +msgstr "" +"cache.remove(\"/root\") を実行すると、/root 以下のエントリをすべて再帰的に削" +"除できます。" + +#. Tag: para +#: TreeCache_FAQ.xml:610 +#, no-c-format +msgid "Can I monitor and manage the JBoss Cache?" +msgstr "JBoss Cache を監視し管理することはできますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:614 +#, fuzzy, no-c-format +msgid "" +"Yes, using a JMX console such as the one shipped with JBoss AS or Java 5's " +"<literal>jconsole</literal> utility. See the chapter titled <emphasis role=" +"\"bold\">Management Information</emphasis> in the JBoss Cache Users' Guide " +"for more details." +msgstr "" +"JBoss Cache 1.3.0 において JBoss AS 内部で JBoss Cache を実行するするか、JDK " +"5.0 の <literal>jconsole</literal> ユーティリティを使用すれば JBoss Cache の" +"管理や監視が可能です。詳細については、JBoss Cache ユーザーガイドの<emphasis " +"role=\"bold\">管理情報</emphasis>の章を参照してください。" + +#. Tag: para +#: TreeCache_FAQ.xml:625 +#, no-c-format +msgid "" +"JBoss Cache uses a <literal>:</literal> character in its object name. This " +"causes problems with my MBean server. What can I do about it?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:633 +#, no-c-format +msgid "" +"This is something we have seen with some MBean servers. By default, JBoss " +"Cache uses <literal>jboss.cache:service=JBossCache</literal> as a prefix to " +"all objects it binds in JMX. To work around this, use the <literal>-" +"Djbosscache.jmx.prefix</literal> JVM parameter to pass in an alternate " +"prefix." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:647 +#, fuzzy, no-c-format +msgid "Can I disable JBoss Cache management attributes?" +msgstr "JBoss Cache 1.3.0 の JBoss Cache 管理属性を無効にできますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:651 +#, no-c-format +msgid "" +"Yes, you can. See the section on configuration in the JBoss Cache Users' " +"Guide." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:658 +#, no-c-format +msgid "What happened to jboss-serialization.jar?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:662 +#, no-c-format +msgid "" +"As of JBoss Cache 2.0.0, the dependency on JBoss Serialization has been " +"dropped since most of the benefits of JBoss Serialization are available in " +"updated Java 5 VMs. Since JBoss Cache 2.0.0 is baselined on Java 5, there " +"was no need to provide these benefits separately." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:673 +#, no-c-format +msgid "Does JBoss Cache support partitioning?" +msgstr "JBoss Cache はパーティショニングをサポートしていますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:677 +#, no-c-format +msgid "" +"Not right now. JBoss Cache does not support partitioning that a user can " +"configure to have different set of data residing on different cache " +"instances while still participating as a replication group." +msgstr "" +"現時点ではサポートしていません。異なるデータセットを異なるキャッシュインスタ" +"ンスに存在させながら 1 つのレプリケーショングループとして参加させるためにユー" +"ザーが設定するようなパーティショニングを JBoss Cache はサポートしていません。" + +#. Tag: para +#: TreeCache_FAQ.xml:682 +#, no-c-format +msgid "" +"This is on the roadmap though, so do keep an eye on <ulink url=\"http://jira." +"jboss.org/jira/browse/JBCACHE-60\">JBCACHE-60</ulink> if you are interested." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:692 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache handle the concept of application classloading inside, say, " +"a Java EE container?" +msgstr "" +"JBoss Cache は、J2EE コンテナ内のアプリケーションクラスローティングの概念に対" +"応できますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:698 +#, fuzzy, no-c-format +msgid "" +"Application-specific classloading is used widely inside a Java EE container. " +"For example, a web application may require a new classloader to scope a " +"specific version of the user library. However, by default JBoss Cache is " +"agnostic to the classloader. In general, this leads to two kinds of problems:" +msgstr "" +"アプリケーション特有のクラスローディングは J2EE コンテナ内部で広く使用されて" +"います。例えば、ユーザーライブラリの特定のバージョンをスコープするため、ウェ" +"ブアプリケーションに新しいクラスローダーが必要になったとします。デフォルトで" +"は、JBoss Cache はクラスローダーにとらわれません。これにより 2 つの問題が発生" +"します。" + +#. Tag: para +#: TreeCache_FAQ.xml:707 +#, no-c-format +msgid "" +"Object instance is stored in cache1 and replicated to cache2. As a result, " +"the instance in cache2 is created by the system classloader. The replication " +"may fail if the system classloader on cache2 does not have access to the " +"required class. Even if replication doesn't fail, a user thread in cache2 " +"may not be able to access the object if the user thread is expecting a type " +"defined by the application classloader." +msgstr "" +"オブジェクトインスタンスは cache1 に保存され、cache2 へレプリケートされます。" +"この結果、cache2 のインスタンスはシステムクラスローダーによって作成されます。" +"cache2 のシステムクラスローダーが必要なクラスにアクセスできない場合、レプリ" +"ケーションに失敗します。レプリケーションに失敗しなくても、cache2 のユーザース" +"レッドがアプリケーションクラスローダーによって定義されたタイプを要求する場" +"合、このユーザースレッドはオブジェクトにアクセスできません。" + +#. Tag: para +#: TreeCache_FAQ.xml:718 +#, fuzzy, no-c-format +msgid "" +"Object instance is created by thread 1 and will be accessed by thread 2 " +"(with two different classloaders). JBoss Cache has no notion of the " +"different classloaders involved. As a result, you will have a " +"<literal>ClassCastException</literal> . This is a standard problem in " +"passing an object from one application space to another; JBoss Cache just " +"adds a level of indirection in passing the object." +msgstr "" +"オブジェクトインスタンスはスレッド 1 によって作成され、スレッド 2 によってア" +"クセスされます（2 つの異なるクラスローダーがある場合）。JBossCache は関係する" +"異なるクラスローダーについて概念がありません。そのため、" +"<literal>ClassCastException</literal> を持つことになります。これは、オブジェ" +"クトを 1 つのアプリケーションスペースから別のアプリケーションスペースへ渡す場" +"合の典型的な問題です。JBossCache はオブジェクトを渡す際に間接的なレベルのみを" +"追加します。" + +#. Tag: para +#: TreeCache_FAQ.xml:731 +#, fuzzy, no-c-format +msgid "" +"To solve the first kind of issue JBoss Cache uses a " +"<literal>CacheMarshaller</literal> . Basically, this allows application code " +"to register a classloader with a portion of the cache tree for use in " +"handling objects replicated to that portion. See the " +"<literal>CacheMarshaller</literal> section of the Users' Guide for more " +"details." +msgstr "" +"最初に挙げたような問題を解決するため、<literal>TreeCacheMarshaller</literal> " +"の概念を JBoss Cache 1.2.4 に導入しました。これにより、アプリケーション内の" +"コードが、キャッシュツリーの一部（そこにレプリケートされたオブジェクトを処理" +"する）に対して使用されるクラスローダーを作成できるようになりました。詳細につ" +"いては、ユーザーガイドの TreeCacheMarshaller の項をご覧ください。" + +#. Tag: para +#: TreeCache_FAQ.xml:742 +#, no-c-format +msgid "" +"To solve the second kind of issue, you can use the the " +"<literal>UseLazyDeserialization</literal> configuration option in JBoss " +"Cache, which wraps your objects in a <literal>Marshalledvalue</literal> " +"wrapper. The <literal>MarshalledValue</literal> serializes and deserializes " +"your object on demand, ensuring the proper thread local context class loader " +"is used each time." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:757 +#, no-c-format +msgid "" +"Does JBoss Cache currently support pre-event and post-event notification?" +msgstr "" +"現在、JBoss Cache は前処理イベントおよび後処理イベントの通知をサポートしてい" +"ますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:763 +#, no-c-format +msgid "" +"Yes. A boolean is passed in to each notification callback identifying " +"whether the callback is before or after the event. See the <literal>org." +"jboss.cache.notifications.annotations.CacheListener</literal> annotation for " +"details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:774 +#, fuzzy, no-c-format +msgid "How do I implement a custom listener to listen to cache events?" +msgstr "" +"<literal>TreeCache</literal> イベントをリッスンするようにカスタムリスナを実装" +"する方法を教えてください。" + +#. Tag: para +#: TreeCache_FAQ.xml:780 +#, no-c-format +msgid "See the Users' Guide on this subject." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:788 +#, fuzzy, no-c-format +msgid "" +"Can I use <literal>UseRegionBasedMarshalling</literal> attribute in JBoss " +"Cache in order to get around ClassCastExceptions happening when accessing " +"data in the cache that has just been redeployed?" +msgstr "" +"再デプロイされたキャッシュのデータにアクセスする際に ClassCastExceptions を回" +"避するため、JBoss Cache で<literal>useRegionBasedMarshalling</literal> 属性を" +"使用できますか？" + +#. Tag: para +#: TreeCache_FAQ.xml:797 +#, fuzzy, no-c-format +msgid "" +"Yes, you can. Originally, cache Marshalling was designed as a workaround for " +"those replicated caches that upon state transfer did not have access to the " +"classloaders defining the objects in the cache." +msgstr "" +"使用できます。元々 <literal>TreeCache</literal> マーシャリングは、ステート転" +"送の際にキャッシュのオブジェクトを定義するクラスローダーへアクセスできないレ" +"プリケートされたキャッシュを回避するための方法でした。" + +#. Tag: para +#: TreeCache_FAQ.xml:802 +#, no-c-format +msgid "" +"On each deployment, JBoss creates a new classloader per the top level " +"deployment artifact, for example an EAR. You also have to bear in mind that " +"a class in an application server is defined not only by the class name but " +"also its classloader. So, assuming that the cache is not deployed as part of " +"your deployment, you could deploy an application and put instances of " +"classes belonging to this deployment inside the cache. If you did a " +"redeployment and try to do a get operation of the data previously put, this " +"would result on a ClassCastException. This is because even though the class " +"names are the same, the class definitions are not. The current classloader " +"is different to the one when the classes were originally put." +msgstr "" +"デプロイする際、JBoss はトップレベルのデプロイメント成果物（例：EAR）のために" +"新しいクラスローダーを作成します。また、アプリケーションサーバー内のクラス" +"は、クラス名だけでなくクラスローダーによっても定義されます。例えば、デプロイ" +"メントの一部としてキャッシュをデプロイしない場合、アプリケーションをデプロイ" +"し、デプロイメントに属するクラスのインスタンスをキャッシュの内部に配置できま" +"すが、再デプロイを行って以前に配置したデータの get 操作を試行すると、" +"ClassCastException が生じます。これは、クラス名が同じでもクラス定義が異なるた" +"めです。この場合、現在のクラスローダーはクラスが最初に配置されたクラスロー" +"ダーとは異なります。" + +#. Tag: para +#: TreeCache_FAQ.xml:817 +#, fuzzy, no-c-format +msgid "" +"By enabling marshalling, you can control the lifecycle of the data in the " +"cache and if on undeployment, you deactivate the region and unregister the " +"classloader that you'd have registered on deployment, you'd evict the data " +"in the cache locally. That means that in the next deployment, the data won't " +"be in the cache, therefore avoiding the problem. Obviously, using " +"marshalling to get around this problem is only recommended when you have " +"some kind of persistence backing where the data survives, for example using " +"CacheLoaders, or when JBoss Cache is used as a second level cache in a " +"persistence framework." +msgstr "" +"マーシャリングを有効にすると、キャッシュにあるデータのライフサイクルを制御す" +"ることができます。また、アンデプロイする際にリジョンを非アクティブにし、デプ" +"ロイの際に登録したクラスタの登録を抹消した場合、キャッシュにあるデータをロー" +"カルでエビクションします。よって、次にデプロイする際、データがキャッシュにな" +"いため、問題を回避することができます。データが存続する永続的なバッキングがあ" +"る場合（例：CacheLoader の使用）や、JBoss Cache が永続化フレームワークの第 2 " +"レベルキャッシュとして使用されている場合のみ、マーシャリングによる問題の回避" +"が推奨されます。" + +#. Tag: para +#: TreeCache_FAQ.xml:830 +#, fuzzy, no-c-format +msgid "" +"To implement this feature, please follow the instructions indicated in the " +"example located in the CacheMarshaller section of the Users' Guide. It's " +"worth noting that instead of a <literal>ServletContextListener</literal> , " +"you could add this code into an <literal>MBean</literal> that contained " +"lifecycle methods, such as <literal>start()</literal> and <literal>stop()</" +"literal> . The key would be for this MBean to depend on the target cache, so " +"that it can operate as long as the cache is up and running." +msgstr "" +"必ず、ユーザーガイドの TreeCacheMarshaller 項に記載されている説明に従ってこの" +"機能を実装してください。<literal>ServletContextListener</literal> の代わり" +"に、<literal>start()</literal> や <literal>stop()</literal> などのライフサイ" +"クルメソッドを格納する <literal>MBean</literal> にこのコードを追加することも" +"できます。重要な点は、キャッシュが実行している間は動作できるよう、MBean を" +"ターゲットキャッシュに依存させることです。" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Troubleshooting.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Troubleshooting.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/ja-JP/Troubleshooting.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,42 @@ +# translation of Colophon.po to Japanese +# Noriko Mizumoto <noriko(a)redhat.com&gt;, 2007. +# Junko Ito <junko.ito(a)rehdat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-05 08:49+1000\n" +"Last-Translator: Junko Ito <junko.ito(a)rehdat.com&gt;\n&quot; +"Language-Team: Japanese <ja(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Troubleshooting.xml:6 +#, no-c-format +msgid "Troubleshooting" +msgstr "トラブルシューティング" + +#. Tag: para +#: Troubleshooting.xml:11 +#, no-c-format +msgid "" +"I am having problems getting JBoss Cache to work, where can I get " +"information on troubleshooting?" +msgstr "" +"JBoss Cache がうまく動作しないのですが、トラブルシューティングの情報はどこで" +"入手できますか？" + +#. Tag: para +#: Troubleshooting.xml:15 +#, fuzzy, no-c-format +msgid "" +"Troubleshooting section can be found in the following <ulink url=\"http://" +"www.jboss.org/community/docs/DOC-10288\">wiki link</ulink>." +msgstr "" +"トラブルシューティングに関する情報は、次の<ulink url=\"http://wiki.jboss.org/" +"wiki/Wiki.jsp?page=JBossCacheTroubleshooting\"> wiki リンク</ulink> を参照し" +"てください。" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Author_Group.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Author_Group.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Author_Group.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,20 @@ +# translation of Colophon.po to Brazilian Portuguese +# Leticia de Lima <ldelima(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-25 11:29+1000\n" +"Last-Translator: Leticia de Lima <ldelima(a)redhat.com&gt;\n&quot; +"Language-Team: Brazilian Portuguese <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: firstname +#: Author_Group.xml:7 +#, no-c-format +msgid "Ben Wang, Bela Ban, Manik Surtani, Scott Marlow, Galder Zamarreño" +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Book_Info.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Book_Info.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Book_Info.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,40 @@ +# translation of Colophon.po to Brazilian Portuguese +# Leticia de Lima <ldelima(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-25 11:29+1000\n" +"Last-Translator: Leticia de Lima <ldelima(a)redhat.com&gt;\n&quot; +"Language-Team: Brazilian Portuguese <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Book_Info.xml:5 +#, fuzzy, no-c-format +msgid "JBoss Cache Frequently Asked Questions" +msgstr "Perguntas Freqüentes" + +#. Tag: subtitle +#: Book_Info.xml:6 +#, no-c-format +msgid "for Use with JBoss Enterprise Application Platform 5.0" +msgstr "" + +#. Tag: para +#: Book_Info.xml:12 +#, no-c-format +msgid "" +"This book is a compilation of frequently asked questions about JBoss Cache" +msgstr "" +"Este livro é uma compilação das perguntas mais comuns sobre o JBoss Cache." + +#. Tag: holder +#: Book_Info.xml:24 +#, no-c-format +msgid "&HOLDER;" +msgstr "&HOLDER;" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/CacheLoader_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/CacheLoader_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/CacheLoader_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,372 @@ +# translation of Colophon.po to Brazilian Portuguese +# Leticia de Lima <ldelima(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-25 11:29+1000\n" +"Last-Translator: Leticia de Lima <ldelima(a)redhat.com&gt;\n&quot; +"Language-Team: Brazilian Portuguese <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: CacheLoader_FAQ.xml:6 +#, no-c-format +msgid "Cache Loaders" +msgstr "Cache Loaders" + +#. Tag: para +#: CacheLoader_FAQ.xml:12 +#, fuzzy, no-c-format +msgid "What is a cache loader?" +msgstr "O que é o CacheLoader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:16 +#, fuzzy, no-c-format +msgid "" +"A cache loader is the connection of JBoss Cache to a (persistent) data " +"store. The cache loader is called by JBoss Cache to fetch data from a store " +"when that data is not in the cache, and when modifications are made to data " +"in the cache the Cache Loader is called to store those modifications back to " +"the store." +msgstr "" +"O CacheLoader é a conexão do JBossCache a um armazenamento de dados " +"(persistentes). O CacheLoader é chamado pelo JBossCache para produzir dados " +"a partir de um armazenamento, quando os mesmos dados não estiverem no cache, " +"e, também, quando as modificações efetuadas aos dados do CacheLoader forem " +"chamadas para armazenar aquelas modificações de volta ao armazenamento." + +#. Tag: para +#: CacheLoader_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "" +"In conjunction with eviction policies, JBoss Cache with a cache loader " +"allows a user to maintain a bounded cache for a large backend datastore. " +"Frequently used data is fetched from the datastore into the cache, and the " +"least used data is evicted, in order to provide fast access to frequently " +"accessed data. This is all configured through XML, and the programmer " +"doesn't have to take care of loading and eviction." +msgstr "" +"Em conjunção às políticas de remoção, o JBossCache com o CacheLoader " +"permitem que o usuário mantenha um cache vinculado para um grande " +"armazenamento de dados backend. Os dados usados são freqüentemente " +"produzidos a partir de um armazenamento de dados dentro do cache, e os dados " +"menos utilizados são removidos. Tudo isto, com o objetivo de fornecer o " +"acesso rápido aos dados acessados com mais freqüência. Isto é completamente " +"configurado através do XML e o programador não precisa preocupar-se com o " +"carregamento e a remoção. " + +#. Tag: para +#: CacheLoader_FAQ.xml:32 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache currently ships with several cache loader implementations, " +"including:" +msgstr "" +"O JBossCache atualmente lança diversas implementações do CacheLoader, " +"incluindo:" + +#. Tag: para +#: CacheLoader_FAQ.xml:37 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.FileCacheLoader</literal> : this " +"implementation uses the file system to store and retrieve data. JBoss Cache " +"nodes are mapped to directories, subnodes to subdirectories etc. Attributes " +"of a node are mapped to a data file inside the directory." +msgstr "" +"FileCacheLoader: isto implementa o uso do sistema do arquivo para o " +"armazenamento e restauração de dados. Os nós do JBossCache estão mapeados " +"para diretórios e sub-nós para sub-diretórios, etc. Os atributos de um nó " +"estão mapeados para um arquivo de <literal>data</literal>, dentro do " +"diretório." + +#. Tag: para +#: CacheLoader_FAQ.xml:49 +#, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.jdbm.JdbmCacheLoader</literal> : this " +"implementation is based on<ulink url=\"http://jdbm.sourceforge.net/\"> JDBM</" +"ulink>, an open source file-based transactional persistence engine." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:58 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.bdbje.BdbjeCacheLoader</literal> : this " +"implementation is based on the Oracle's Berkeley DB Java Edition database, a " +"fast and efficient transactional database. It uses a single file for the " +"entire store. Note that if you use the Berkeley DB cache loader with JBoss " +"Cache and wish to ship your product, you will have to acquire a <ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">commercial license from Oracle</" +"ulink>." +msgstr "" +"BdbjeCacheLoader: esta implementação baseia-se no banco de dados de Edição " +"Java Sleepycat, um banco de dados transacional rápido e eficiente. Isto " +"utiliza um arquivo único para o armazenamento completo. Perceba que se você " +"usar o Sleepycat do CacheLoader com o JBoss Cache e desejar lançar seu " +"produto, você terá que adquirir uma <ulink url=\"http://www.sleepycat.com/" +"jeforjbosscache\"> licença comercial a partir do Sleepycat</ulink>." + +#. Tag: para +#: CacheLoader_FAQ.xml:71 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.JDBCCacheLoader</literal> : this " +"implementation uses the relational database as the persistent storage." +msgstr "" +"JDBCCacheLoader: esta implementação usa o banco de dados relacional como um " +"armazenamento persistente." + +#. Tag: para +#: CacheLoader_FAQ.xml:79 +#, fuzzy, no-c-format +msgid "" +"And more. See the chapter on cache loaders in the Users' Guide for more " +"details." +msgstr "" +"Por favor, consulte a documentação para maiores detalhes e informações." + +#. Tag: para +#: CacheLoader_FAQ.xml:88 +#, no-c-format +msgid "Is the FileCacheLoader recommended for production use?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:92 +#, no-c-format +msgid "" +"No, it is not. The FileCacheLoader has some severe limitations which " +"restrict its use in a production environment, or if used in such an " +"environment, it should be used with due care and sufficient understanding of " +"these limitations." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:99 +#, no-c-format +msgid "" +"Due to the way the FileCacheLoader represents a tree structure on disk " +"(directories and files) traversal is inefficient for deep trees." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:103 +#, no-c-format +msgid "" +"Usage on shared filesystems like NFS, Windows shares, etc. should be avoided " +"as these do not implement proper file locking and can cause data corruption." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:107 +#, no-c-format +msgid "" +"Usage with an isolation level of NONE can cause corrupt writes as multiple " +"threads attempt to write to the same file." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:111 +#, no-c-format +msgid "" +"File systems are inherently not transactional, so when attempting to use " +"your cache in a transactional context, failures when writing to the file " +"(which happens during the commit phase) cannot be recovered." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:120 +#, no-c-format +msgid "" +"As a rule of thumb, it is recommended that the FileCacheLoader not be used " +"in a highly concurrent, transactional or stressful environment, and its use " +"is restricted to testing." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:130 +#, fuzzy, no-c-format +msgid "Can writing to cache loaders be asynchronous?" +msgstr "Eu posso rodar o CacheLoaders como assíncrono?" + +#. Tag: para +#: CacheLoader_FAQ.xml:134 +#, fuzzy, no-c-format +msgid "" +"Yes. Set the <literal>async</literal> attrobute to true. See the JBoss Cache " +"Users' Guide for a more detailed discussion. By default though, all cache " +"loader writes are synchronous and will block." +msgstr "" +"Como parte do JBossCache 1.2.4, sim. Configure a propriedade do " +"CacheLoaderAsynchronous para verdadeiro. Consulte a documentação do " +"JBossCache para informações mais detalhadas. Pelo padrão, todos os " +"carregadores de cache são assíncronos e irão bloquear. " + +#. Tag: para +#: CacheLoader_FAQ.xml:145 +#, fuzzy, no-c-format +msgid "Can I write my own cache loader ?" +msgstr "Eu posso gravar meu próprio CacheLoader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:149 +#, fuzzy, no-c-format +msgid "" +"Yes. A cache loader is a class implementing <literal>org.jboss.cache.loader." +"CacheLoader</literal> or extending <literal>org.jboss.cache.loader." +"AbstractCacheLoader</literal> . It is configured via the XML file (see JBoss " +"Cache Users' Guide)." +msgstr "" +"Sim. O CacheLoader é uma classe implementando o <literal>org.jboss.cache." +"loader.CacheLoader</literal>. Ele é configurado através do arquivo XML " +"(consulte o JBossCache e a documentação tutorial)." + +#. Tag: para +#: CacheLoader_FAQ.xml:161 +#, fuzzy, no-c-format +msgid "Does a cache loader have to use a persistent store ?" +msgstr "O CacheLoader precisa utilizar um armazenamento persistente?" + +#. Tag: para +#: CacheLoader_FAQ.xml:165 +#, fuzzy, no-c-format +msgid "" +"No, a cache loader could for example fetch (and possibly store) its data " +"from a webdav-capable webserver. Another example is a caching proxy server, " +"which fetches contents from the web. Note that an implementation of " +"CacheLoader may not implement the 'store' functionality in this case, but " +"just the 'load' functionality." +msgstr "" +"Não, um CacheLoader poderia produzir (e possivelmente armazenar), por " +"exemplo, os próprios dados a partir de um webdav-capable webserver. Outro " +"exemplo, é o servidor caching proxy, pelo qual produz os conteúdos a partir " +"da web. Perceba que uma implementação do CacheLoader não poderá implementar " +"a funcionalidade de 'armazenamento' neste caso, mas apenas a funcionalidade " +"de 'carregamento'." + +#. Tag: para +#: CacheLoader_FAQ.xml:177 +#, fuzzy, no-c-format +msgid "Do I have to pay to use Oracle's Berkeley DB CacheLoader?" +msgstr "Eu preciso pagar para usar o Sleepycat do CacheLoader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:181 +#, fuzzy, no-c-format +msgid "" +"Not if you use it only for personal use. As soon as you distribute your " +"product with BdbjeCacheLoader, you have to purchase a commercial license " +"from Oracle. See details at <ulink url=\"http://www.sleepycat.com/" +"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ." +msgstr "" +"Não, mas apenas se você utilizá-lo para uso pessoal. Logo após a " +"distribuição de seu produto com o BdbjeCacheLoader, você terá que comprar " +"uma licença comercial a partir do Sllepycat. Consulte <ulink url=\"http://" +"www.sleepycat.com/jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache " +"</ulink>, para maiores detalhes a respeito deste assunto." + +#. Tag: para +#: CacheLoader_FAQ.xml:194 +#, no-c-format +msgid "Are there any tools available to monitor the Berkeley DB instance?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:198 +#, no-c-format +msgid "" +"Yes. Oracle ships a JMX-based monitoring tool, called <ulink url=\"http://" +"www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/" +"jmx/JEMonitor.html\"> JEMonitor </ulink> which can be downloaded from the " +"Oracle website." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:211 +#, no-c-format +msgid "" +"When tuning my Berkeley DB instance, where should I put my je.properties " +"file?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:215 +#, no-c-format +msgid "" +"<literal>je.properties</literal> should reside in your Berkeley DB home " +"directory. This is the directory you pass in to the BDBJECacheLoader's " +"<literal>location</literal> configuration property." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:227 +#, no-c-format +msgid "Can I use more than one cache loader?" +msgstr "Posso usar mais de um cache loader?" + +#. Tag: para +#: CacheLoader_FAQ.xml:231 +#, fuzzy, no-c-format +msgid "" +"Yes. Within the CacheLoaderConfiguration XML element (see Users' Guide " +"chapter on cache loaders) you can describe several cache loaders. The impact " +"is that the cache will look at all of the cache loaders in the order they've " +"been configured, until it finds a valid, non-null element of data. When " +"performing writes, all cache loaders are written to (except if the " +"ignoreModifications element has been set to true for a specific cache loader." +msgstr "" +"A partir do JBossCache 1.30, sim. Você pode agora descrever diversos " +"armazenamentos de cache (consulte a seção de armazenamentos de cache no " +"manual do usuário) com o novo elemento do CacheLoaderConfiguration XML. O " +"impacto é que o cache observará todos os armazenamentos do cache na ordem em " +"que eles foram configurados, até que isto encontre um elemento válido e não-" +"nulo de dados. Todos os armazenamentos de cache são gravados (a não que o " +"elemento ignoreModifications tenha sido configurado para verdadeiro num " +"carregador de cache específico)." + +#. Tag: para +#: CacheLoader_FAQ.xml:245 +#, no-c-format +msgid "" +"Can I migrate a JDBCacheLoader or FileCacheLoader based cache store " +"containing data formatted with JBoss Cache 1.x.x to JBoss Cache 2.0 format?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:250 +#, no-c-format +msgid "" +"Yes. See \"Transforming Cache Loaders\" section within the \"Cache Loaders\" " +"section located in the JBoss Cache Users' Guide." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:257 +#, no-c-format +msgid "Is the TCPDelegatingCacheLoader resilient to TCPCacheServer restarts?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:263 +#, no-c-format +msgid "" +"As of JBoss Cache 2.1.0, the answer is yes. See the Users' Guide for details " +"on how to configure and tune your retries and wait period for reestablishing " +"the TCP connection." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:269 +#, no-c-format +msgid "" +"Prior to that, restarting the TCPCacheServer would also mean restarting your " +"application that uses the cache." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Eviction_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Eviction_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Eviction_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,171 @@ +# translation of Colophon.po to Brazilian Portuguese +# Leticia de Lima <ldelima(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-25 11:29+1000\n" +"Last-Translator: Leticia de Lima <ldelima(a)redhat.com&gt;\n&quot; +"Language-Team: Brazilian Portuguese <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Eviction_FAQ.xml:6 +#, no-c-format +msgid "Eviction Policies" +msgstr "Políticas de Remoção" + +#. Tag: para +#: Eviction_FAQ.xml:10 +#, no-c-format +msgid "Does JBoss Cache support eviction policies?" +msgstr "O JBoss Cache suporta as políticas de remoção?" + +#. Tag: para +#: Eviction_FAQ.xml:14 +#, no-c-format +msgid "" +"Yes. JBoss Cache currently supports multiple eviction policies such as LRU, " +"MRU, and FIFO. Users can also plug in their own eviction policy algorithms. " +"See user guide for details." +msgstr "" + +#. Tag: para +#: Eviction_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "Does JBoss Cache's eviction policy operates in replication mode?" +msgstr "" +"O JBoss Cache de política de remoção LRU implementada opera no modo de " +"replicação?" + +#. Tag: para +#: Eviction_FAQ.xml:29 +#, no-c-format +msgid "Yes and no. :-)" +msgstr "Sim e não. :-)" + +#. Tag: para +#: Eviction_FAQ.xml:31 +#, fuzzy, no-c-format +msgid "" +"The eviction policy only operates in local mode. That is, nodes are only " +"evicted locally. This may cause the cache contents not to be synchronized " +"temporarily. But when a user tries to obtain the cached contents of an " +"evicted node and finds out that is null (e.g., <literal>get</literal> " +"returns null), it should get it from the other data source and re-populate " +"the data in the cache. During this moment, the node content will be " +"propagated and the cache content will be in sync." +msgstr "" +"A política LRU apenas opera no modo local. Isto é, os nós são apenas " +"removidos localmente. O resultado disto poderá ser que os conteúdos do cache " +"não sejam sincronizados temporariamente. Mas, quando um usuário tentar obter " +"os conteúdos do cache de um nó removido e descobrir que ele é nulo (por " +"exemplo: o <literal>get</literal> retornar nulo), ele deverá obter isto a " +"partir de outra fonte de recurso e re-abastecer os dados no cache. Neste " +"momento, o conteúdo do nó será propagado e o conteúdo do cache estará em " +"sync." + +#. Tag: para +#: Eviction_FAQ.xml:42 +#, no-c-format +msgid "" +"However, you still can run eviction policies with cache mode set to either " +"<literal>REPL_SYNC</literal> or <literal>REPL_ASYNC</literal> . Depending on " +"your use case, you can set multiple cache instances to have their own " +"eviction policy (which are applied locally) or just have selected instances " +"with eviction policies activated." +msgstr "" +"No entanto, você pode continuar rodando as políticas de remoção com a " +"configuração de modo do cache, para tanto o <literal>REPL_SYNC</literal> ou " +"<literal>REPL_ASYNC</literal>. Dependo do seu caso de uso, você poderá " +"configurar instâncias de cache múltiplas para ter a própria política de " +"remoção (da qual é aplicada localmente) ou apenas possui instâncias " +"selecionadas com as políticas de remoção ativadas." + +#. Tag: para +#: Eviction_FAQ.xml:53 +#, no-c-format +msgid "" +"Also note that, with cache loader option, a locally evicted node can also be " +"persisted to the backend store and a user can retrieve it from the store " +"later on." +msgstr "" +"Perceba também, com a opção do carregador do cache, um nó removido " +"localmente pode também ser persistido ao armazenamento backend e um usuário " +"poderá restaurar isto, a partir do armazenamento mais tarde." + +#. Tag: para +#: Eviction_FAQ.xml:62 +#, no-c-format +msgid "Does JBoss Cache support <literal>Region</literal> ?" +msgstr "O JBoss Cache suporta <literal>Region</literal>?" + +#. Tag: para +#: Eviction_FAQ.xml:69 +#, no-c-format +msgid "" +"Yes. JBoss Cache has the notion of region where a user can configure the " +"eviction policy parameters (e.g., <literal>maxNodes</literal> or " +"<literal>timeToIdleSeconds</literal> )" +msgstr "" +"Sim. O JBoss Cache possui a noção de região, onde um usuário pode configurar " +"os parâmetros da política de remoção (por exemplo: <literal>maxNodes</" +"literal> ou <literal>timeToIdleSeconds</literal>)." + +#. Tag: para +#: Eviction_FAQ.xml:77 +#, fuzzy, no-c-format +msgid "" +"A region in JBoss Cache denotes a portion of tree hierarchy, e.g., a fully " +"qualified name ( <literal>org.jboss.cache.Fqn</literal> ). For example, a " +"user can define <literal>/org/jboss</literal> and <literal>/org/foocom</" +"literal> as two separate regions. But note that you can configure the region " +"programmatically now, i.e., everything has to be configured through the xml " +"file." +msgstr "" +"Uma região no JBoss Cache marca uma porção da hierarquia tree, por exemplo: " +"um nome inteiramente qualificado (<literal>FQN</literal>). Por exemplo: um " +"usuário poderá definir<literal>/org/jboss</literal> e <literal>/org/foocom</" +"literal> como duas regiões separadas. No entanto, perceba que você poderá " +"configurar a região de maneira programática agora, por exemplo: tudo deve " +"ser configurado através do arquivo xml." + +#. Tag: para +#: Eviction_FAQ.xml:94 +#, no-c-format +msgid "" +"I have turned on the eviction policy, why do I still get \"out of memory" +"\" (OOM) exception?" +msgstr "" +"Eu acionei a política de remoção, por que eu continuo obtendo a exceção " +"(OOM) \"fora da memória\"?" + +#. Tag: para +#: Eviction_FAQ.xml:100 +#, fuzzy, no-c-format +msgid "" +"OOM can happen when the speed of cache access exceeds the speed of eviction " +"policy handling timer. Eviction policy handler will wake up every " +"<literal>wakeUpInterval</literal> milliseconds (or " +"<literal>wakeUpIntervalSeconds</literal> seconds, prior to 3.x) to process " +"the eviction event queue. So when the queue size is full, it will create a " +"backlog and cause out-of-memory exceptions to happen unless the eviction " +"timer catches up. To address this problem, in addition to increase the VM " +"heap size, you can also reduce the <literal>wakeUpInterval</literal> so the " +"timer thread processes the queue more frequently." +msgstr "" +"OOM pode ocorrer quando a velocidade de acesso do cache excede a velocidade " +"do controlador de tempo de manuseio da política de remoção. O manuseador da " +"política de remoção estimulará cada segundo do " +"<literal>wakeUpIntervalInSeconds</literal> para processar a fila do evento " +"de remoção. Além disso, o tamanho da fila é fixado em 2000, agora. Desta " +"maneira, quando o tamanho da fila estiver cheio, ele criará um backlog, " +"fazendo com que o OOM aconteça, a não ser que o controlador de tempo da " +"remoção o alcance. Para endereçar este problema, adicionado ao aumento do " +"tamanho de empilhamento VM, você poderá também reduzir o " +"<literal>wakeUpIntervaleInSeconds</literal>, de forma que o segmento do " +"controlador de tempo a fila mais freqüente. " Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/General_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/General_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/General_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,167 @@ +# translation of Colophon.po to Brazilian Portuguese +# Leticia de Lima <ldelima(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-25 11:29+1000\n" +"Last-Translator: Leticia de Lima <ldelima(a)redhat.com&gt;\n&quot; +"Language-Team: Brazilian Portuguese <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: General_FAQ.xml:6 +#, no-c-format +msgid "General Information" +msgstr "Informações Gerais" + +#. Tag: para +#: General_FAQ.xml:10 +#, no-c-format +msgid "What is JBoss Cache?" +msgstr "O que é o JBoss Cache?" + +#. Tag: para +#: General_FAQ.xml:14 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache is a replicated and transactional cache. It is replicated since " +"multiple JBoss Cache instances can be distributed (either within the same " +"JVM or across several JVMs whether they reside on the same machine or on " +"different machines on a network) and data is replicated across the whole " +"group. It is transactional because a user can configure a <ulink url=" +"\"http://java.sun.com/products/jta/\">JTA</ulink> compliant transaction " +"manager and make any cache interaction transactional, and caches would " +"participate in ongoing JTA transactions. Note that the cache can also be run " +"without any replication; this is the local mode." +msgstr "" +"O JBoss Cache é um cache replicado e transacional. Ele é replicado, uma vez " +"que as instâncias do JBoss Cache múltiplas poderão ser distribuídas (tanto " +"com o mesmo JVM ou através de diversos JVMs, se é que eles residem na mesma " +"máquina ou em diferentes máquinas na rede), além dos dados serem replicados " +"através de todo grupo. Isto é transacional uma vez que um usuário pode " +"configurar um gerenciador de transação compilante JTA e fazer a operação de " +"cache transacional. Perceba que o cache pode também ser rodado sem qualquer " +"replicação, sendo que este é o modo local." + +#. Tag: para +#: General_FAQ.xml:28 +#, no-c-format +msgid "" +"JBoss Cache comes in two flavours: Core and POJO versions. The core library " +"(using the <literal>org.jboss.cache.Cache</literal> interface) is the " +"underlying library that organises data in a tree-like structure and handles " +"all locking, passivation, eviction and replication characteristics of data " +"in the cache. The POJO library (using the <literal>org.jboss.cache.pojo." +"PojoCache</literal> interface) is built atop the core library and allows " +"introspection of objects in the cache providing transparent coherence by " +"using JBoss AOP. Note that the POJO edition of JBoss Cache (often referred " +"to as POJO Cache) comes with a separate set of documentation (Users' Guide, " +"FAQ, etc.) available on the JBoss Cache <ulink url=\"http://www.jboss.org/" +"jbosscache/\">documentation website</ulink>." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:66 +#, no-c-format +msgid "Who are the JBoss Cache developers?" +msgstr "Quem são os desenvolvedores do JBoss Cache?" + +#. Tag: para +#: General_FAQ.xml:70 +#, no-c-format +msgid "" +"JBoss Cache has an active community of developers and contributors. The " +"project was founded by Bela Ban and is currently led by Manik Surtani. Jason " +"Greene is the lead for the POJO Cache subsystem, and other contributors both " +"past and present include Ben Wang, Harald Gliebe, Brian Stansberry, Vladimir " +"Blagojevic, Mircea Markus, Jimmy Wilson, Galder Zamarreño and Elias Ross." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:139 +#, no-c-format +msgid "How do I know the version of JBoss Cache that I am using?" +msgstr "" +"Como é que eu posso saber em qual versão do JBoss Cache eu estou trabalhando?" + +#. Tag: para +#: General_FAQ.xml:143 +#, no-c-format +msgid "" +"<literal>java -jar jbosscache-core.jar</literal> will spit out version " +"details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:152 +#, fuzzy, no-c-format +msgid "" +"Can I run JBoss Cache outside of the JBoss Enterprise Application Platform?" +msgstr "Eu posso rodar o JBoss Cache fora do Servidor do Aplicativo JBoss?" + +#. Tag: para +#: General_FAQ.xml:157 +#, no-c-format +msgid "" +"Absolutely! Even though JBoss Cache comes integrated with the JBoss " +"Enterprise Application Platform, it can also be used in any other Java EE " +"server such as BEA WebLogic, IBM Websphere or Tomcat. It can also run in a " +"standalone Java process, completely outside of an application server. See " +"the Users' Guide for more details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:170 +#, no-c-format +msgid "" +"How can I migrate my application and configuration from using JBoss Cache 1." +"x to 2.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:173 +#, no-c-format +msgid "" +"Look at <ulink url=\"http://www.jboss.org/community/docs/DOC-10246\">this " +"wiki page</ulink> for help." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:182 +#, no-c-format +msgid "What about from 2.x to 3.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:185 +#, no-c-format +msgid "" +"JBoss Cache 3.x is API compatible with 2.x, although as far as possible you " +"should refactor your code not to use deprecated methods as these may " +"disappear in future releases of JBoss Cache." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:190 +#, no-c-format +msgid "" +"JBoss Cache 3.x comes with an all new configuration format. Old 2.x " +"configuration files will still work, although you will get a warning in the " +"logs about this. Again, as far as possible, we recommend migrating your " +"configuration file to the new format. Scripts are provided with the JBoss " +"Cache 3.x distribution to migrate configuration files (see " +"<literal>config2to3.sh</literal> and<literal>config2to3.bat</literal>)." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:201 +#, no-c-format +msgid "" +"Note that to take advantage of some of the new features in JBoss Cache 3.x, " +"you need to be using the new configuration format." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/JBoss_Cache_Frequently_Asked_Questions.po =================================================================== Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Revision_History.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Revision_History.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Revision_History.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,26 @@ +# translation of Colophon.po to Brazilian Portuguese +# Leticia de Lima <ldelima(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-25 11:29+1000\n" +"Last-Translator: Leticia de Lima <ldelima(a)redhat.com&gt;\n&quot; +"Language-Team: Brazilian Portuguese <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Revision_History.xml:6 +#, no-c-format +msgid "Revision History" +msgstr "" + +#. Tag: author +#: Revision_History.xml:12 +#, fuzzy, no-c-format +msgid "<firstname></firstname> <surname></surname> <email></email>" +msgstr "<firstname>John</firstname> <surname>Doe</surname>" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/TreeCache_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/TreeCache_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/TreeCache_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,1076 @@ +# translation of Colophon.po to Brazilian Portuguese +# Leticia de Lima <ldelima(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-25 11:29+1000\n" +"Last-Translator: Leticia de Lima <ldelima(a)redhat.com&gt;\n&quot; +"Language-Team: Brazilian Portuguese <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: TreeCache_FAQ.xml:6 +#, fuzzy, no-c-format +msgid "JBoss Cache: Core" +msgstr "JBoss Cache 1.4.1" + +#. Tag: para +#: TreeCache_FAQ.xml:26 +#, no-c-format +msgid "Can I run multiple JBoss Cache instances on the same VM?" +msgstr "Posso rodar instâncias múltiplas do JBoss Cache no mesmo VM?" + +#. Tag: para +#: TreeCache_FAQ.xml:30 +#, no-c-format +msgid "" +"Yes. There are some scenarios where you may want to run multiple instances " +"of JBoss Cache. For example, you want to run multiple local cache instances " +"with each instance having its own configuration (e.g., different cache " +"policy). In this case, you will need multiple xml configuration files." +msgstr "" +"Sim. Existem alguns cenários onde você talvez queira rodar instâncias " +"múltiplas do JBoss Cache. Por exemplo, você poderá rodar as instâncias " +"múltiplas de um cache local, pelas quais cada instância possui sua própria " +"configuração (por exemplo: diferente política de cache). Neste caso, você " +"precisará de arquivos de configuração xml múltiplos." + +#. Tag: para +#: TreeCache_FAQ.xml:41 +#, fuzzy, no-c-format +msgid "Can JBoss Cache run as a second level cache inside Hibernate?" +msgstr "" +"O TreeCache pode rodar como um cache de segundo nível dentro do Hibernate?" + +#. Tag: para +#: TreeCache_FAQ.xml:47 +#, fuzzy, no-c-format +msgid "" +"Yes. Since Hibernate 3.0 release, you can configure it to use JBoss Cache as " +"a second level cache. For details, see Hibernate documentation, and also see " +"<ulink url=\"http://www.jboss.org/community/docs/DOC-10265\">this wiki page</" +"ulink>." +msgstr "" +"Sim. Desde a versão 3.0 do Hibernate, você pode configurá-lo usando o JBoss " +"Cache (nomeadamente, TreeCache), como um cache de segundo nível. Para " +"maiores detalhes, consulte a documentação Hibernate e veja também o link: " +"<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate\&... " +"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate </ulink>." + +#. Tag: para +#: TreeCache_FAQ.xml:52 +#, no-c-format +msgid "" +"JBoss Cache 3.x with MVCC in particular works very well as a Hibernate " +"second level cache." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:60 +#, fuzzy, no-c-format +msgid "What about using POJO Cache as a Hibernate cache?" +msgstr "E a respeito do uso do PojoCache como um cache Hibernate?" + +#. Tag: para +#: TreeCache_FAQ.xml:64 +#, fuzzy, no-c-format +msgid "" +"It is not necessary to use POJO Cache for second level cache inside " +"Hibernate because Hibernate manages fine-grained fields in Java objects. " +"Using POJO Cache won't provide any advantage, and will be an unnecessary " +"performance drawback." +msgstr "" +"Não há a necessidade de usar o PojoCache para um cache de segundo nível " +"dentro do Hibernate, uma vez que o Hibernate gerencia campos fine-grained em " +"objetos Java. Desta forma, o uso do PojoCache não trará nenhuma vantagem." + +#. Tag: para +#: TreeCache_FAQ.xml:74 +#, no-c-format +msgid "How can I configure JBoss Cache?" +msgstr "Como eu posso configurar o JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:78 +#, no-c-format +msgid "" +"You can configure the JBoss Cache through a configuration xml file or " +"programmatically using a <literal>org.jboss.cache.config.Configuration</" +"literal> object, passed in to the <literal>org.jboss.cache.CacheFactory</" +"literal> instance." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:90 +#, no-c-format +msgid "" +"Can I use a schema or DTD to validate my JBoss Cache configuration file?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:95 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, yes. An XSD schema is provided in your jbosscache-" +"core.jar file, and is also available online, on<ulink url=\"http://www.jboss." +"org/jbosscache/jbosscache-config-3.0.xsd\"> http://www.jboss.org/jbosscache/" +"jbosscache-config-3.0.xsd</ulink>. You can configure your IDE, text editor " +"or XML authoring tool to use this schema to validate your file." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:108 +#, no-c-format +msgid "What is the difference between the different cache modes?" +msgstr "Qual é a diferença entre os diferentes modos de cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:113 +#, no-c-format +msgid "" +"JBossCache has five different cache modes, i.e., <literal>LOCAL</literal> , " +"<literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> and <literal>INVALIDATION_ASYNC</" +"literal> . If you want to run JBoss Cache as a single instance, then you " +"should set the cache mode to <literal>LOCAL</literal> so that it won't " +"attempt to replicate anything. If you want to have synchronous replication " +"among different JBoss Cache instances, you set it to <literal>REPL_SYNC</" +"literal> . For asynchronous replication, use <literal>AYSNC_REPL</literal> . " +"If you do not wish to replicate cached data but simply inform other caches " +"in a cluster that data under specific addresses are now stale and should be " +"evicted from memory, use <literal>INVALIDATION_SYNC</literal> or " +"<literal>INVALIDTAION_ASYNC</literal> . Synchronous and asynchronous " +"behavior applies to invalidation as well as replication." +msgstr "" +"O JBoss Cache possui cinco diferentes modos de cache, por exemplo: " +"<literal>LOCAL</literal>, <literal>REPL_SYNC</literal>, <literal>REPL_ASYNC</" +"literal>, <literal>INVALIDATION_SYNC</literal> e " +"<literal>INVALIDATION_ASYNC</literal>. Caso você queira rodar o JBoss Cache " +"como uma instância única, então você terá que configurar o modo do cache " +"para <literal>LOCAL</literal>, de forma que isto não tente replicar coisa " +"alguma. Caso você deseje ter replicações síncronas no meio de diferentes " +"instâncias do JBoss Cache, você configurará isto para <literal>REPL_SYNC</" +"literal>. Para a replicação síncrona, use <literal>AYSNC_REPL</literal>. " +"Caso você não queira replicar os dados, mas simples informar os demais " +"caches num cluster, do qual os dados sob endereços específicos são antigos e " +"deverão ser removido da memória, utilize <literal>INVALIDATION_SYNC</" +"literal> ou <literal>INVALIDTAION_ASYNC</literal>. Os comportamentos " +"síncronos ou assíncronos são aplicados para a invalidação assim como a " +"replicação." + +#. Tag: para +#: TreeCache_FAQ.xml:143 +#, no-c-format +msgid "" +"Note that <literal>ASYNC_REPL</literal> and <literal>INVALIDATION_ASYNC</" +"literal> are non-blocking. This can be useful when you want to have another " +"JBoss Cache serving as a mirror or backup and you don't want to wait for " +"confirmation that this mirror has received your messages." +msgstr "" +"Perceba que o <literal>ASYNC_REPL</literal> e <literal>INVALIDATION_ASYNC</" +"literal> não são bloqueados. Isto pode ser usado quando você desejar ter o " +"serviço de outro cache como um espelho ou back up, além de você não querer " +"esperar pela confirmação que este espelho recebeu suas mensagens." + +#. Tag: para +#: TreeCache_FAQ.xml:157 +#, no-c-format +msgid "How does JBoss Cache's replication mechanism work?" +msgstr "Como o mecanismo da replicação do JBoss Cache funciona?" + +#. Tag: para +#: TreeCache_FAQ.xml:161 +#, no-c-format +msgid "" +"JBoss Cache leverages <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"for network communications. A JGroups configuration section is present in " +"your JBoss Cache configuration." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:166 +#, fuzzy, no-c-format +msgid "" +"A user can configure the cluster of JBoss Cache instances by sharing the " +"same cluster name ( <literal>cluster name</literal> ). There is also an " +"option of whether to populate the cache data upon starting a new instance in " +"the <literal>ClusterConfig</literal> attribute." +msgstr "" +"O JBoss Cache nivela o <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"como uma camada de replicação. O usuário pode configurar o cluster de " +"instâncias do JBoss Cache apenas dividindo o mesmo nome de cluster " +"(<literal>cluster name</literal>). Há também a opção de se preencher os " +"dados do cache ou não, até o período de instalação da nova instância no " +"atributo <literal>ClusterConfig</literal>. " + +#. Tag: para +#: TreeCache_FAQ.xml:178 +#, fuzzy, no-c-format +msgid "" +"Note that once all instances join the same replication group, every " +"replication change is propagated to all participating members. There is no " +"mechanism for sub-partitioning where some replication can be done within " +"only a subset of members, unless you use the Buddy Replication features. See " +"the Users' Guide for more details on this." +msgstr "" +"Perceba que em algum momento todas as instâncias juntam-se ao mesmo grupo de " +"replicação, e que cada mudança de replicação é propagada para todos os " +"membros participantes. Não há nenhum mecanismo para sub-particionamento onde " +"algumas replicações podem ser feitas com apenas um sub-conjunto de membros. " +"Isto pertence a nossa lista de tarefas a serem feitas." + +#. Tag: para +#: TreeCache_FAQ.xml:190 +#, no-c-format +msgid "" +"I run a 2 node cluster. If the network dies, do the caches continue to run?" +msgstr "" +"Eu estou rodando um cluster de nó 2. Os caches continuarão a rodar, no caso " +"da rede cair?" + +#. Tag: para +#: TreeCache_FAQ.xml:194 +#, no-c-format +msgid "" +"Yes, both will continue to run, but depending on your replication mode, all " +"transactions or operations may not complete. If <literal>REPL_SYNC</literal> " +"is used, operations will fail while if <literal>REPL_ASYNC</literal> is used " +"they will succeed. Even if they succeed though, caches will be out of sync." +msgstr "" +"Sim, ambos continuarão a rodar, mas dependendo do ser modo de replicação, " +"todas as transações ou operações não serão completadas. Caso o " +"<literal>REPL_SYNC</literal> seja utilizado, as operações falharão enquanto " +"que o <literal>REPL_ASYNC</literal> é usado, elas irão sobreviver. Mesmo que " +"elas sejam bem sucedidas, os caches estarão fora do sync." + +#. Tag: para +#: TreeCache_FAQ.xml:207 +#, no-c-format +msgid "" +"Can I plug in library X instead of JGroups to handle remote calls and group " +"communications?" +msgstr "" +"Eu posso clicar na biblioteca X ao invés do JGroups para manusear as " +"chamadas remotas e os grupos de comunicações?" + +#. Tag: para +#: TreeCache_FAQ.xml:212 +#, fuzzy, no-c-format +msgid "" +"At this stage the answer is no. We do have an abstraction layer between the " +"communication suite and JBoss Cache in the pipelines, and this may appear as " +"a feature at some stage in the future." +msgstr "" +"Nestas alturas (JBoss Cache 1.x) a resposta é não. Nós possuimos uma camada " +"de abstração entre a suíte de comunicação e o JBoss Cache e as tubulações, e " +"isto poderá aparecer como um recurso em qualquer estado a frente." + +#. Tag: para +#: TreeCache_FAQ.xml:223 +#, no-c-format +msgid "" +"Does the cache need to replicate to every other instance in the cluster? " +"Isn't this slow if the cluster is large?" +msgstr "" +"O cache precisa realizar a replicação para todas as demais instâncias no " +"cluster? Isto não será muito lento, caso o cluster seja grande?" + +#. Tag: para +#: TreeCache_FAQ.xml:230 +#, fuzzy, no-c-format +msgid "" +"Replication need not occur to every node in the cluster. This feature - " +"called Buddy Replication - allows each node to pick one or more 'buddies' in " +"the cluster and only replicate to its buddies. This allows a cluster to " +"scale very easily with no extra impact on memory or network traffic with " +"each node added." +msgstr "" +"Assim como o JBoss Cache 1.4.0, a replicação não precisa ocorrer para cada " +"nó no cluster. Este recurso - chamado Replicação Buddy - permite que cada nó " +"escolha um ou mais 'buddies' no cluster, e apenas realiza a replicação para " +"os próprios buddies. Isto permite que um cluster realize uma escala com " +"facilidade, sem nenhum impacto na memória ou no tráfico de rede de cada nó " +"adicionado." + +#. Tag: para +#: TreeCache_FAQ.xml:237 +#, fuzzy, no-c-format +msgid "" +"See the Users' Guide for more information on Buddy Replication, and how it " +"can be used to achieve very high scalability." +msgstr "" +"Consulte o Guia do Usuário para maiores informações sobre a Replicação Buddy " +"e como isto pode ser usada para atingir um alto nível de escabilidade." + +#. Tag: para +#: TreeCache_FAQ.xml:248 +#, no-c-format +msgid "" +"I'm using Buddy Replication. Do I need to have some form of session affinity?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:251 +#, no-c-format +msgid "" +"Session affinity relates to returning to the same cache instance for the " +"same data being used. While this is strictly not a requirement for Buddy " +"Replication, it is greatly recommended to minimize moving state around a " +"cluster." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:261 +#, fuzzy, no-c-format +msgid "" +"If I have the need for different configuration properties (e.g., " +"<literal>CacheMode</literal> and <literal>IsolationLevel</literal> ), do I " +"simply need to create multiple <literal>org.jboss.cache.Cache</literal> " +"instances with the appropriate configuration?" +msgstr "" +"Caso eu tenha a necessidade de possuir diferentes propriedades de TreeCache " +"(por exemplo: <literal>CacheMode</literal> e <literal>IsolationLevel</" +"literal>), eu precisarei criar instâncias TreeCache múltiplas com a " +"configuração apropriada?" + +#. Tag: para +#: TreeCache_FAQ.xml:272 +#, fuzzy, no-c-format +msgid "" +"Yes. All the above mentioned properties are per cache instance. Therefore " +"you will need separate <literal>org.jboss.cache.Cache</literal> instances." +msgstr "" +"Sim. Todas as propriedades mencionadas acima são por instância de cache. " +"Portanto, você precisará uma instância do JBoss Cache separada." + +#. Tag: para +#: TreeCache_FAQ.xml:282 +#, no-c-format +msgid "" +"Isn't this expensive from a networking standpoint, i.e., needing to create " +"sockets for each <literal>org.jboss.cache.Cache</literal> instance?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:289 +#, no-c-format +msgid "" +"Yes, it can be. For such cases it is recommended that you configure your " +"cache using the JGroups Multiplexer, which allows several caches to share a " +"single JGroups channel. Please see the Users' Guide for details on how to " +"configure the JGroups Multiplexer." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:296 +#, no-c-format +msgid "" +"A faster and more efficient approach is to use a shared transport in " +"JGroups. Please see <ulink url=\"http://www.jgroups.org\">the JGroups " +"documentation</ulink> for more details on how to do this." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:307 +#, fuzzy, no-c-format +msgid "" +"Does the <literal>ClusterName</literal> configuration element have any " +"relation to the JBoss AS cluster <literal>PartitionName</literal> ?" +msgstr "" +"O Tree Cache config <literal>ClusterName</literal> possui qualquer relação " +"com o JBoss AS cluster <literal>PartitionName</literal>?" + +#. Tag: para +#: TreeCache_FAQ.xml:317 +#, no-c-format +msgid "" +"Yes. They are both JGroups group names. Besides the notion of a channel in " +"JGroups, it also can partition the channel into different group names." +msgstr "" +"Sim. Existem ambos os nomes do grupo JGroups. Fora a noção de um canal no " +"JGroups, isto pode também dividir o canal em nomes de grupos diferentes." + +#. Tag: para +#: TreeCache_FAQ.xml:326 +#, fuzzy, no-c-format +msgid "" +"When using multiple JGroups based components [cluster-service.xml, cache " +"(multiple instances)], what is the correct/valid way to configure those " +"components to make sure my multicast addresses don't conflict?" +msgstr "" +"Quando utilizando os componentes baseados do JGroups múltiplos [cluster-" +"service.xml, treecache (instâncias múltiplas)], qual é a maneira correta/" +"válida para configurar aqueles componentes, certificando-se de que meus " +"endereços multicast não sofrerão conflitos?" + +#. Tag: para +#: TreeCache_FAQ.xml:334 +#, no-c-format +msgid "" +"There are two parameters to consider: multicast address (plus port) and the " +"group name. At minimum, you will have to run components using a different " +"group name. But whether to run them on the same channel depends upon whether " +"the communication performance is critical for you or not. If it is, then " +"it'd be best to run them on different channels." +msgstr "" +"Existem dois parâmetros a serem considerados: endereços multicast (mais o " +"porto) e o nome do grupo. No mínimo, você terá que rodar os componentes " +"usando um nome de grupo diferente. Porém, a opção de rodá-los no mesmo canal " +"ou não, dependerá se o desempenho de comunicação estiver crítico para você " +"ou não. Caso, isto seja, então seria melhor rodá-los em diferentes canais." + +#. Tag: para +#: TreeCache_FAQ.xml:346 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache persistence storage?" +msgstr "" +"O JBoss Cache suporta atualmente o armazenamento de persistência do cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:352 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache has a cache loader interface that supports cache " +"persistence. See below for more FAQs on cache loaders." +msgstr "" +"Sim. Inicializando com a versão 1.1, o JBoss Cache possui a interface " +"CacheLoader, da qual suporta a persistência do cache. Veja a seguir." + +#. Tag: para +#: TreeCache_FAQ.xml:360 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache passivation/ overflow to a data store?" +msgstr "" +"O JBoss Cache suporta atualmente a passivação/overflow do cache para o " +"armazenamento de dados?" + +#. Tag: para +#: TreeCache_FAQ.xml:366 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache uses the cache loader to support cache passivation/ " +"overflow. See documentation on how to configure and use this feature." +msgstr "" +"Sim. Inicializando com a versão 1.2.4. o JBoss Cache usa o CacheLoader para " +"suportar a passivação/overflow do cache. Consulte a documentação em como " +"configurar e usar este recurso." + +#. Tag: para +#: TreeCache_FAQ.xml:375 +#, no-c-format +msgid "Is JBoss Cache thread safe?" +msgstr "O segmento do JBoss Cache é seguro?" + +#. Tag: para +#: TreeCache_FAQ.xml:379 +#, no-c-format +msgid "Yes, it is thread safe." +msgstr "Sim, ele é um segmento seguro." + +#. Tag: para +#: TreeCache_FAQ.xml:385 +#, no-c-format +msgid "Does JBoss Cache support XA (2PC) transactions now?" +msgstr "O JBoss Cache suporta as transações XA (2PC) agora?" + +#. Tag: para +#: TreeCache_FAQ.xml:389 +#, fuzzy, no-c-format +msgid "" +"No, although it is also on our to do list. Our internal implementation does " +"use a procedure similar to 2PC to coordinate a transactions among different " +"instances, but JBoss Cache is not an XA resource." +msgstr "" +"Não, mesmo que isto esteja também na nossa lista de tarefas. Nossa " +"implementação interna usa um procedimento similar 2PC para coordenar uma " +"transação entre instâncias diferentes. " + +#. Tag: para +#: TreeCache_FAQ.xml:398 +#, fuzzy, no-c-format +msgid "Which transaction managers are supported by JBoss Cache?" +msgstr "Qual das TransactionManagers são suportadas pelo JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:404 +#, no-c-format +msgid "" +"JBoss Cache supports any TransactionManager that is <ulink url=\"http://java." +"sun.com/products/jta/\">JTA</ulink> compliant such as<ulink url=\"http://www." +"jboss.org/jbosstm/\">JBoss Transactions</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:408 +#, no-c-format +msgid "" +"While JBoss Cache does ships with a dummy transaction manager (<literal>org." +"jboss.cache.transaction.DummyTransactionManager</literal>), we do " +"<emphasis>not</emphasis> recommend using this for production. It is not " +"thread safe, and is intended for internal testing only." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:421 +#, no-c-format +msgid "How do I set up the cache to be transactional?" +msgstr "Como é que eu posso configurar o cache para ser transacional?" + +#. Tag: para +#: TreeCache_FAQ.xml:425 +#, fuzzy, no-c-format +msgid "" +"You either use the default transaction manager that ships with JBoss AS or " +"you have to implement the <literal>org.jboss.cache.transaction." +"TransactionManagerLookup</literal> interface, and return an instance of your " +"<literal>javax.transaction.TransactionManager</literal> implementation. The " +"configuration property <literal>TransactionManagerLookupClass</literal> " +"defines the class to be used by the cache to fetch a reference to a " +"transaction manager. It is trivial to implement this interface to support " +"other transaction managers. Once this attribute is specified, the cache will " +"look up the transaction context from this transaction manager." +msgstr "" +"Você tanto usará o padrão (JBoss) TransactionManager para a execução do " +"JBossCache dentro do JBoss, ou você terá que implementar a interface " +"<literal>TransactionManagerLookup</literal> e retornar a uma instância de " +"seu javax.transaction.TransactionManager. A propriedade de configuração " +"<literal>TransactionManagerLookupClass</literal> define a classe a ser usada " +"pelo cache para busca de uma referência a um TransactionManager. " + +#. Tag: para +#: TreeCache_FAQ.xml:441 +#, no-c-format +msgid "" +"The <literal>org.jboss.cache.transaction.GenericTransactionManagerLookup</" +"literal> class that ships with JBoss Cache is able to detect and bind to " +"most popular transaction managers. See the " +"<literal>GenericTransactionManagerLookup</literal> javadocs for more " +"information." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:454 +#, no-c-format +msgid "How do I control the cache locking level?" +msgstr "Como eu posso controlar o nível de bloqueamento do cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:458 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache lets you control the cache locking level through the transaction " +"isolation level. This is configured through the attribute " +"<literal>IsolationLevel</literal> . The transaction isolation levels " +"correspond to database isolation levels, namely, <literal>NONE</literal> , " +"<literal>READ_UNCOMMITTED</literal> , <literal>READ_COMMITTED</literal> , " +"<literal>REPEATABLE_READ</literal> , and <literal>SERIALIZABLE</literal> . " +"Note that these isolation levels are ignored if optimistic locking is used. " +"For details, please refer to the user manual." +msgstr "" +"O JBossCache permite você controlar o nível de bloqueamento do cache através " +"do nível de isolação de transação. Isto é configurado através do atributo " +"<literal>IsolationLevel</literal> . Atualmente, o JBossCache emprega um " +"bloqueamento pessimista internamente. O Nível de isolação de transação a " +"partir do bloqueamento pessimista corresponde aos níveis de isolações JDBC, " +"nomeadamente <literal>NONE</literal>, <literal>READ_UNCOMMITTED</literal>, " +"<literal>READ_COMMITTED</literal>, <literal>REPEATABLE_READ</literal> e " +"<literal>SERIALIZABLE</literal>. Perceba que estes níveis de isolação são " +"ignorados, caso o bloqueamento otimista for utilizado. Para maiores " +"detalhes, por favor refira-se ao manual do usuário." + +#. Tag: para +#: TreeCache_FAQ.xml:480 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, when using the MVCC locking scheme, only " +"<literal>READ_COMMITTED</literal> and <literal>REPEATABLE_READ</literal> are " +"supported. Any other isolation level provided will either be upgraded or " +"downgraded accordingly." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:493 +#, no-c-format +msgid "How does JBoss Cache lock data for concurrent access?" +msgstr "Como o JBoss Cache bloqueia os dados para o acesso atual?" + +#. Tag: para +#: TreeCache_FAQ.xml:497 +#, fuzzy, no-c-format +msgid "" +"In JBoss Cache 2.x, by default pessimistic locking is used to lock data " +"nodes, based on the isolation level configured. We also offer optimistic " +"locking to allow for greater concurrency at the cost of slight processing " +"overhead and performance. See the documentation for a more detailed " +"discussion on concurrency and locking in JBoss Cache." +msgstr "" +"Pelo padrão, o JBoss Cache usa o bloqueamento pessimista para bloquear os " +"nós dos dados, baseando-se no nível configurado de isolação. Desde o JBoss " +"Cache 1.3.0, nós também oferecemos o bloqueamento otimista para permitir uma " +"boa atualização de custo do pequeno processamento elevado e desempenho. " +"Consulte a documentação para um melhor exclarecimento na concorrência e " +"bloqueamento do JBoss Cache. " + +#. Tag: para +#: TreeCache_FAQ.xml:505 +#, no-c-format +msgid "" +"In JBoss Cache 3.x, optimistic and pessimistic locking are deprecated in " +"favour of MVCC (multi-version concurrency control), which is far more " +"efficient than either optimistic or pessimistic locking. For a detailed " +"discussion on our MVCC implementation, see <ulink url=\"http://jbosscache." +"blogspot.com/2008/07/mvcc-has-landed.html\">this blog entry</ulink> " +"and<ulink url=\"http://www.jboss.org/community/docs/DOC-10272\">this wiki " +"page</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:520 +#, fuzzy, no-c-format +msgid "How do I enable Optimistic Locking or MVCC in JBoss Cache?" +msgstr "Como eu ativo o Bloqueamento Otimista no JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:524 +#, no-c-format +msgid "Please see the configuration section of the Users' Guide for details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:532 +#, no-c-format +msgid "Can I use the cache locking level even without a transaction context?" +msgstr "" +"Eu posso usar o nível de bloqueamento do cache sem um contexto de transação?" + +#. Tag: para +#: TreeCache_FAQ.xml:538 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache controls the individual node locking behavior through the " +"isolation level semantics. This means even if you don't use a transaction, " +"you can specify the lock level via isolation level. You can think of the " +"node locking behavior outside of a transaction as if it is under transaction " +"with <literal>auto_commit</literal> on." +msgstr "" +"Sim. O JBossCache controla o nó individual de comportamento de bloqueamento " +"através das semânticas de nível de isolação. Isto significa que mesmo que " +"você não utilize uma transação, você poderá especificar o nível de " +"bloqueamento através do nível de isolação. Você poderá pensar no " +"comportamento de bloqueamento do nó fora da transação, como se isto " +"estivesse sob a transação com o <literal>auto_commit</literal> conectado." + +#. Tag: para +#: TreeCache_FAQ.xml:551 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache support <literal>SELECT FOR UPDATE</literal> semantics?" +msgstr "O JBoss Cache suporta <literal>Region</literal>?" + +#. Tag: para +#: TreeCache_FAQ.xml:559 +#, no-c-format +msgid "" +"Yes, but this is is only possible if you are running within a JTA " +"transaction <emphasis>and</emphasis> are using either <literal>MVCC</" +"literal> or <literal>PESSIMISTIC</literal> as your node locking scheme." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:568 +#, no-c-format +msgid "To achieve <literal>SELECT FOR UPDATE</literal> semantics, simply do:" +msgstr "" + +#. Tag: programlisting +#: TreeCache_FAQ.xml:573 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" // start transaction ... \n" +"\n" +" cache.getInvocationContext().getOptionOverrides().setForceWriteLock" +"(true);\n" +" Node n = cache.get(\"/a/b/c\"); // this acquires a WRITE LOCK on this " +"node\n" +" ...\n" +" ...\n" +"\n" +" // end transaction\n" +"\n" +" ]]>" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:579 +#, no-c-format +msgid "" +"With replication (REPL_SYNC/REPL_ASYNC) or invalidation (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), how often does the cache broadcast messages over the " +"network?" +msgstr "" +"Qual é a freqüência das mensagens do cache broadcast sobre a rede com a " +"replicação (REPL_SYNC/REPL_ASYNC) ou invalidação (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC)?" + +#. Tag: para +#: TreeCache_FAQ.xml:586 +#, fuzzy, no-c-format +msgid "" +"If the updates are under transaction, then the broadcasts happen only when " +"the transaction is about to commit (actually during the prepare stage " +"internally). That is, it will be a batch update. However, if the operations " +"are not under transaction context, then each update will trigger " +"replication. Note that this has performance implications if network latency " +"is a problem." +msgstr "" +"Caso as atualizações estejam sob a transação, então os broadcasts " +"acontecerão apenas quando a transação estiver para ser confirmada (na " +"realidade, durante o estágio de preparação interno). Isto é, ela será uma " +"atualização em lote. No entanto, caso as operações não estejam sob o " +"contexto da transação, então cada atualização efetuar o trigger na " +"replicação. Perceba que, isto implica no desempenho caso o transporte da " +"rede for pesado (normalmente, ele é)." + +#. Tag: para +#: TreeCache_FAQ.xml:598 +#, no-c-format +msgid "How can I do a mass removal?" +msgstr "Como eu posso realizar uma remoção em massa?" + +#. Tag: para +#: TreeCache_FAQ.xml:602 +#, fuzzy, no-c-format +msgid "" +"If you do a<literal>cache.removeNode(\"/myroot\")</literal>, it will " +"recursively remove all the entries under \"/myroot\"." +msgstr "" +"Caso você realize um cache.remove(\"/root\"), ele removerá de maneira " +"repetitiva todas as entradas sob \"/root\"." + +#. Tag: para +#: TreeCache_FAQ.xml:610 +#, no-c-format +msgid "Can I monitor and manage the JBoss Cache?" +msgstr "Eu posso monitorar e gerenciar o JBoss Cache?" + +#. Tag: para +#: TreeCache_FAQ.xml:614 +#, fuzzy, no-c-format +msgid "" +"Yes, using a JMX console such as the one shipped with JBoss AS or Java 5's " +"<literal>jconsole</literal> utility. See the chapter titled <emphasis role=" +"\"bold\">Management Information</emphasis> in the JBoss Cache Users' Guide " +"for more details." +msgstr "" +"Você poderá realizar isto, caso você esteja rodando o JBoss Cache como o " +"JBoss AS ou caso você esteja usando o JDK 5.0 de utilidade " +"<literal>jconsole</literal>. Verifique o capítulo de título <emphasis role=" +"\"bold\">Management Information</emphasis> no guia do usuário do JBoss " +"Cache, para maiores informações." + +#. Tag: para +#: TreeCache_FAQ.xml:625 +#, no-c-format +msgid "" +"JBoss Cache uses a <literal>:</literal> character in its object name. This " +"causes problems with my MBean server. What can I do about it?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:633 +#, no-c-format +msgid "" +"This is something we have seen with some MBean servers. By default, JBoss " +"Cache uses <literal>jboss.cache:service=JBossCache</literal> as a prefix to " +"all objects it binds in JMX. To work around this, use the <literal>-" +"Djbosscache.jmx.prefix</literal> JVM parameter to pass in an alternate " +"prefix." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:647 +#, fuzzy, no-c-format +msgid "Can I disable JBoss Cache management attributes?" +msgstr "" +"Eu posso desativar os atributos do gerenciador do JBoss Cache no JBoss Cache " +"1.3.0?" + +#. Tag: para +#: TreeCache_FAQ.xml:651 +#, no-c-format +msgid "" +"Yes, you can. See the section on configuration in the JBoss Cache Users' " +"Guide." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:658 +#, no-c-format +msgid "What happened to jboss-serialization.jar?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:662 +#, no-c-format +msgid "" +"As of JBoss Cache 2.0.0, the dependency on JBoss Serialization has been " +"dropped since most of the benefits of JBoss Serialization are available in " +"updated Java 5 VMs. Since JBoss Cache 2.0.0 is baselined on Java 5, there " +"was no need to provide these benefits separately." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:673 +#, no-c-format +msgid "Does JBoss Cache support partitioning?" +msgstr "O JBoss Cache suporta o particionamento?" + +#. Tag: para +#: TreeCache_FAQ.xml:677 +#, no-c-format +msgid "" +"Not right now. JBoss Cache does not support partitioning that a user can " +"configure to have different set of data residing on different cache " +"instances while still participating as a replication group." +msgstr "" +"Não, ele não suporta isto agora. O JBoss Cache não suporta o particionamento " +"que um usuário pode configurar para ter diferentes conjunto de dados " +"residindo em diferentes instâncias, enquanto participando como um grupo de " +"replicação." + +#. Tag: para +#: TreeCache_FAQ.xml:682 +#, no-c-format +msgid "" +"This is on the roadmap though, so do keep an eye on <ulink url=\"http://jira." +"jboss.org/jira/browse/JBCACHE-60\">JBCACHE-60</ulink> if you are interested." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:692 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache handle the concept of application classloading inside, say, " +"a Java EE container?" +msgstr "" +"O JBoss Cache pode manusear o conceito do carregamento de classe do " +"aplicativo, por exemplo: um container J2EE?" + +#. Tag: para +#: TreeCache_FAQ.xml:698 +#, fuzzy, no-c-format +msgid "" +"Application-specific classloading is used widely inside a Java EE container. " +"For example, a web application may require a new classloader to scope a " +"specific version of the user library. However, by default JBoss Cache is " +"agnostic to the classloader. In general, this leads to two kinds of problems:" +msgstr "" +"O carregamento de classe do aplicativo específico é usado abertamente dentro " +"de um container J2EE. Por exemplo: o aplicativo da web pode solicitar um " +"novo carregador de classe para o escopo numa versão específica da biblioteca " +"do usuário. No entanto, pelo padrão o JBoss Cache é agnóstico ao carregador " +"de classe. Em geral, isto leva a dois tipos de problemas:" + +#. Tag: para +#: TreeCache_FAQ.xml:707 +#, no-c-format +msgid "" +"Object instance is stored in cache1 and replicated to cache2. As a result, " +"the instance in cache2 is created by the system classloader. The replication " +"may fail if the system classloader on cache2 does not have access to the " +"required class. Even if replication doesn't fail, a user thread in cache2 " +"may not be able to access the object if the user thread is expecting a type " +"defined by the application classloader." +msgstr "" +"A instância do objeto é armazenada no cache1 e replicada ao cache2. Como " +"resultado, a instância no cache2 é criada pelo carregador de classe do " +"sistema. A replicação poderá falhar, caso o carregador de classe do sistema " +"no cache2 não possua acesso à classe solicitada. Mesmo que a replicação não " +"falhe, um segmento do usuário no cache2 poderá não ter acesso ao objeto, " +"caso o segmento do usuário esteja esperando por um tipo definido do " +"carregador de classe do aplicativo." + +#. Tag: para +#: TreeCache_FAQ.xml:718 +#, fuzzy, no-c-format +msgid "" +"Object instance is created by thread 1 and will be accessed by thread 2 " +"(with two different classloaders). JBoss Cache has no notion of the " +"different classloaders involved. As a result, you will have a " +"<literal>ClassCastException</literal> . This is a standard problem in " +"passing an object from one application space to another; JBoss Cache just " +"adds a level of indirection in passing the object." +msgstr "" +"A instância do objeto é criada pelo segmento 1 e será acessada pelo segmento " +"2 (com dois carregadores de classe diferentes). O JbossCache não possui " +"noção dos diferentes carregadores de classe envolvidos. Como resultado, você " +"terá um <literal>ClassCastException</literal>. Este é um problema padrão na " +"passagem de um objeto, a partir de um espaço do aplicativo para outro. O " +"JBoss Cache apenas adiciona um nível de indireções na passagem do objeto. " + +#. Tag: para +#: TreeCache_FAQ.xml:731 +#, fuzzy, no-c-format +msgid "" +"To solve the first kind of issue JBoss Cache uses a " +"<literal>CacheMarshaller</literal> . Basically, this allows application code " +"to register a classloader with a portion of the cache tree for use in " +"handling objects replicated to that portion. See the " +"<literal>CacheMarshaller</literal> section of the Users' Guide for more " +"details." +msgstr "" +"Para resolver o primeiro tipo de problema, nós introduzimos, no JBoss Cache " +"1.2.4, o conceito de um <literal>TreeCacheMarshaller</literal>. Basicamente, " +"isto permite o código do aplicativo registrar o carregador da classe com a " +"porção do cache tree, para o uso do manuseio dos objetos replicados daquela " +"porção. Consulte a seção TreeCacheMarshaller do guia do usuário, para " +"maiores informações." + +#. Tag: para +#: TreeCache_FAQ.xml:742 +#, no-c-format +msgid "" +"To solve the second kind of issue, you can use the the " +"<literal>UseLazyDeserialization</literal> configuration option in JBoss " +"Cache, which wraps your objects in a <literal>Marshalledvalue</literal> " +"wrapper. The <literal>MarshalledValue</literal> serializes and deserializes " +"your object on demand, ensuring the proper thread local context class loader " +"is used each time." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:757 +#, no-c-format +msgid "" +"Does JBoss Cache currently support pre-event and post-event notification?" +msgstr "O JBoss Cache suporta atualmente a notificação de pré e pós-evento?" + +#. Tag: para +#: TreeCache_FAQ.xml:763 +#, no-c-format +msgid "" +"Yes. A boolean is passed in to each notification callback identifying " +"whether the callback is before or after the event. See the <literal>org." +"jboss.cache.notifications.annotations.CacheListener</literal> annotation for " +"details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:774 +#, fuzzy, no-c-format +msgid "How do I implement a custom listener to listen to cache events?" +msgstr "" +"Como eu implemento um ouvinte personalizado para escutar os eventos do " +"<literal>TreeCache</literal>?" + +#. Tag: para +#: TreeCache_FAQ.xml:780 +#, no-c-format +msgid "See the Users' Guide on this subject." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:788 +#, fuzzy, no-c-format +msgid "" +"Can I use <literal>UseRegionBasedMarshalling</literal> attribute in JBoss " +"Cache in order to get around ClassCastExceptions happening when accessing " +"data in the cache that has just been redeployed?" +msgstr "" +"Posso usar o atributo <literal>useRegionBasedMarshalling</literal> no JBoss " +"Cache com a finalidade das ClassCastExceptions ocorrerem, quando acessando " +"os dados em cada cache, do qual acabou de ser re-implementado?" + +#. Tag: para +#: TreeCache_FAQ.xml:797 +#, fuzzy, no-c-format +msgid "" +"Yes, you can. Originally, cache Marshalling was designed as a workaround for " +"those replicated caches that upon state transfer did not have access to the " +"classloaders defining the objects in the cache." +msgstr "" +"Sim, você pode. Originalmente o <literal>TreeCache</literal> Marshalling foi " +"criado como um trabalho para aqueles caches replicados que até o estado de " +"transferência, não possui acesso aos carregadores de classe definindo os " +"objetos no cache." + +#. Tag: para +#: TreeCache_FAQ.xml:802 +#, no-c-format +msgid "" +"On each deployment, JBoss creates a new classloader per the top level " +"deployment artifact, for example an EAR. You also have to bear in mind that " +"a class in an application server is defined not only by the class name but " +"also its classloader. So, assuming that the cache is not deployed as part of " +"your deployment, you could deploy an application and put instances of " +"classes belonging to this deployment inside the cache. If you did a " +"redeployment and try to do a get operation of the data previously put, this " +"would result on a ClassCastException. This is because even though the class " +"names are the same, the class definitions are not. The current classloader " +"is different to the one when the classes were originally put." +msgstr "" +"Em cada implementação, o JBoss cria um novo carregador de classe por " +"artefato de implementação de nível top, por exemplo um EAR. Você terá que " +"ter em mente que a classe no servidor do aplicativo é definido não apenas " +"pelo nome da classe, mas também por seu carregador de classe. Desta forma, " +"assumimos que o cache não é implementado como parte de sua implementação. " +"Você poderá implementar um aplicativo e colocar instâncias de classes " +"pertencentes a esta implementação dentro do cache. Caso você tenha feito a " +"re-implementação e tentar realizar a obtenção da operação dos dados " +"adicionados anteriormente, isto poderá resultar numa ClassCastException. " +"Isto deve-se ao fato de que mesmo que os nomes das classes serem os mesmos, " +"as definições de classes não são as mesmas. O carregador de classe atual é " +"diferente ao daquele em que as classes foram originalmente aderidas." + +#. Tag: para +#: TreeCache_FAQ.xml:817 +#, fuzzy, no-c-format +msgid "" +"By enabling marshalling, you can control the lifecycle of the data in the " +"cache and if on undeployment, you deactivate the region and unregister the " +"classloader that you'd have registered on deployment, you'd evict the data " +"in the cache locally. That means that in the next deployment, the data won't " +"be in the cache, therefore avoiding the problem. Obviously, using " +"marshalling to get around this problem is only recommended when you have " +"some kind of persistence backing where the data survives, for example using " +"CacheLoaders, or when JBoss Cache is used as a second level cache in a " +"persistence framework." +msgstr "" +"Pela ativação do controle, você poderá controlar o ciclo de vida dos dados " +"no cache e caso de uma desimplementação, você desativará a região e des-" +"registrará o carregador de classe que você registrou na implementação. Você " +"removeria os dados localmente no cache. Isto significa que na próxima " +"implementação, os dados não estarão no cache, portanto evitando o problema. " +"É claro que o uso do controle para buscar este problema, é apenas " +"recomendado quando você possuir algum tipo de persistência retornando para " +"onde os dados sobrevivem, por exemplo o uso dos carregadores de Cache, ou " +"quando o JbossCache for usado como cache de segundo nível num framework de " +"persistência." + +#. Tag: para +#: TreeCache_FAQ.xml:830 +#, fuzzy, no-c-format +msgid "" +"To implement this feature, please follow the instructions indicated in the " +"example located in the CacheMarshaller section of the Users' Guide. It's " +"worth noting that instead of a <literal>ServletContextListener</literal> , " +"you could add this code into an <literal>MBean</literal> that contained " +"lifecycle methods, such as <literal>start()</literal> and <literal>stop()</" +"literal> . The key would be for this MBean to depend on the target cache, so " +"that it can operate as long as the cache is up and running." +msgstr "" +"Para implementação deste recurso, por favor siga as instruções indicadas no " +"exemplo encontrado na seção TreeCacheMarshaller do guia do usuário. É " +"importante perceber que ao invés de um <literal>ServletContextListener</" +"literal>, você poderá adicionar um código ao <literal>MBean</literal>, que " +"contém os métodos de ciclo de vida, como por exemplo: <literal>start()</" +"literal> e <literal>stop()</literal>. A chave para este MBean dependerá no " +"cache de destinação, de forma que ele pode operar contanto que o cache " +"esteja funcionando e rodando. " Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Troubleshooting.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Troubleshooting.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/pt-BR/Troubleshooting.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,41 @@ +# translation of Colophon.po to Brazilian Portuguese +# Leticia de Lima <ldelima(a)redhat.com&gt;, 2008. +msgid "" +msgstr "" +"Project-Id-Version: Colophon\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2008-08-25 11:29+1000\n" +"Last-Translator: Leticia de Lima <ldelima(a)redhat.com&gt;\n&quot; +"Language-Team: Brazilian Portuguese <en(a)li.org&gt;\n&quot; +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Tag: title +#: Troubleshooting.xml:6 +#, no-c-format +msgid "Troubleshooting" +msgstr "Troubleshooting" + +#. Tag: para +#: Troubleshooting.xml:11 +#, no-c-format +msgid "" +"I am having problems getting JBoss Cache to work, where can I get " +"information on troubleshooting?" +msgstr "" +"Eu estou enfrentando dificuldades em inicializar o JBoss Cache. Onde eu " +"posso obter informações a respeito do troubleshooting?" + +#. Tag: para +#: Troubleshooting.xml:15 +#, fuzzy, no-c-format +msgid "" +"Troubleshooting section can be found in the following <ulink url=\"http://" +"www.jboss.org/community/docs/DOC-10288\">wiki link</ulink>." +msgstr "" +"A seção de Troubleshooting pode ser encontrada no seguinte link: <ulink url=" +"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheTroubleshooting\">wiki " +"link</ulink>." Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Author_Group.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Author_Group.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Author_Group.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,20 @@ +# Language zh-CN translations for JBoss_EAP package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: JBoss_EAP 4_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2009-01-13 06:01+0000\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: firstname +#: Author_Group.xml:7 +#, no-c-format +msgid "Ben Wang, Bela Ban, Manik Surtani, Scott Marlow, Galder Zamarreño" +msgstr "Ben Wang, Bela Ban, Manik Surtani, Scott Marlow, Galder Zamarreño" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Book_Info.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Book_Info.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Book_Info.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,39 @@ +# Language zh-CN translations for JBoss_EAP package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: JBoss_EAP 4_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2009-01-13 06:01+0000\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 +#: Book_Info.xml:5 +#, no-c-format +msgid "JBoss Cache Frequently Asked Questions" +msgstr "" + +#. Tag: subtitle +#: Book_Info.xml:6 +#, no-c-format +msgid "for Use with JBoss Enterprise Application Platform 5.0" +msgstr "" + +#. Tag: para +#: Book_Info.xml:12 +#, no-c-format +msgid "" +"This book is a compilation of frequently asked questions about JBoss Cache" +msgstr "本书是 JBoss Cache 常见问题解答的汇集" + +#. Tag: holder +#: Book_Info.xml:24 +#, no-c-format +msgid "&HOLDER;" +msgstr "&HOLDER;" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/CacheLoader_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/CacheLoader_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/CacheLoader_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,349 @@ +# Language zh-CN translations for JBoss_EAP package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: JBoss_EAP 4_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2009-01-13 06:01+0000\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 +#: CacheLoader_FAQ.xml:6 +#, no-c-format +msgid "Cache Loaders" +msgstr "Cache Loader" + +#. Tag: para +#: CacheLoader_FAQ.xml:12 +#, fuzzy, no-c-format +msgid "What is a cache loader?" +msgstr "什么是 CacheLoader？" + +#. Tag: para +#: CacheLoader_FAQ.xml:16 +#, fuzzy, no-c-format +msgid "" +"A cache loader is the connection of JBoss Cache to a (persistent) data " +"store. The cache loader is called by JBoss Cache to fetch data from a store " +"when that data is not in the cache, and when modifications are made to data " +"in the cache the Cache Loader is called to store those modifications back to " +"the store." +msgstr "" +"CacheLoader 是 JBossCache 和持久性数据库的连接。当数据不在缓存里时，" +"JBossCache 调用 CacheLoader 来从数据源获取数据，而当缓存里的数据有变到时，它" +"调用 CacheLoader 来把这些变到存回数据库里。" + +#. Tag: para +#: CacheLoader_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "" +"In conjunction with eviction policies, JBoss Cache with a cache loader " +"allows a user to maintain a bounded cache for a large backend datastore. " +"Frequently used data is fetched from the datastore into the cache, and the " +"least used data is evicted, in order to provide fast access to frequently " +"accessed data. This is all configured through XML, and the programmer " +"doesn't have to take care of loading and eviction." +msgstr "" +"配合 eviction 策略的使用，带有 CacheLoader 的 JBossCache 允许用户维护用于大型" +"后台数据库的有界缓存。被频繁使用的数据从数据库提取到缓存里，而最少使用的数据" +"则被剔除，这是为了提供对被频繁使用的数据的快速访问。这都可以通过 XML 进行配" +"置，程序员不需要担心数据的加载和剔除。" + +#. Tag: para +#: CacheLoader_FAQ.xml:32 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache currently ships with several cache loader implementations, " +"including:" +msgstr "JBossCache 目前带有几个 CacheLoader 实现，如：" + +#. Tag: para +#: CacheLoader_FAQ.xml:37 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.FileCacheLoader</literal> : this " +"implementation uses the file system to store and retrieve data. JBoss Cache " +"nodes are mapped to directories, subnodes to subdirectories etc. Attributes " +"of a node are mapped to a data file inside the directory." +msgstr "" +"FileCacheLoader：这个实现使用文件系统来存储和提取数据。JBossCache 节点映射到" +"目录，而子节点则对应子目录。节点的属性映射为目录里的 <literal>data</literal> " +"文件。" + +#. Tag: para +#: CacheLoader_FAQ.xml:49 +#, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.jdbm.JdbmCacheLoader</literal> : this " +"implementation is based on<ulink url=\"http://jdbm.sourceforge.net/\"> JDBM</" +"ulink>, an open source file-based transactional persistence engine." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:58 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.bdbje.BdbjeCacheLoader</literal> : this " +"implementation is based on the Oracle's Berkeley DB Java Edition database, a " +"fast and efficient transactional database. It uses a single file for the " +"entire store. Note that if you use the Berkeley DB cache loader with JBoss " +"Cache and wish to ship your product, you will have to acquire a <ulink url=" +"\"http://www.sleepycat.com/jeforjbosscache\">commercial license from Oracle</" +"ulink>." +msgstr "" +"BdbjeCacheLoader：这个实现基于 Sleepycat 的 Java 版本的数据库，这是一个高效的" +"事务性数据库。对于整个数据库，它使用单个文件。请注意，如果你将 Sleepycat 的 " +"CacheLoader 和 JBoss Cache 一起使用并希望分发自己的产品，你将需要从 " +"Sleepycat 获得<ulink url=\"http://www.sleepycat.com/jeforjbosscache\">商业性" +"的许可证书</ulink>。" + +#. Tag: para +#: CacheLoader_FAQ.xml:71 +#, fuzzy, no-c-format +msgid "" +"<literal>org.jboss.cache.loader.JDBCCacheLoader</literal> : this " +"implementation uses the relational database as the persistent storage." +msgstr "JDBCCacheLoader：这个实现把关系型数据库用作持久性存储。" + +#. Tag: para +#: CacheLoader_FAQ.xml:79 +#, fuzzy, no-c-format +msgid "" +"And more. See the chapter on cache loaders in the Users' Guide for more " +"details." +msgstr "关于其他的实现，请参考相关文档。" + +#. Tag: para +#: CacheLoader_FAQ.xml:88 +#, no-c-format +msgid "Is the FileCacheLoader recommended for production use?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:92 +#, no-c-format +msgid "" +"No, it is not. The FileCacheLoader has some severe limitations which " +"restrict its use in a production environment, or if used in such an " +"environment, it should be used with due care and sufficient understanding of " +"these limitations." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:99 +#, no-c-format +msgid "" +"Due to the way the FileCacheLoader represents a tree structure on disk " +"(directories and files) traversal is inefficient for deep trees." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:103 +#, no-c-format +msgid "" +"Usage on shared filesystems like NFS, Windows shares, etc. should be avoided " +"as these do not implement proper file locking and can cause data corruption." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:107 +#, no-c-format +msgid "" +"Usage with an isolation level of NONE can cause corrupt writes as multiple " +"threads attempt to write to the same file." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:111 +#, no-c-format +msgid "" +"File systems are inherently not transactional, so when attempting to use " +"your cache in a transactional context, failures when writing to the file " +"(which happens during the commit phase) cannot be recovered." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:120 +#, no-c-format +msgid "" +"As a rule of thumb, it is recommended that the FileCacheLoader not be used " +"in a highly concurrent, transactional or stressful environment, and its use " +"is restricted to testing." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:130 +#, fuzzy, no-c-format +msgid "Can writing to cache loaders be asynchronous?" +msgstr "对 CacheLoader 的写入可以是异步的吗？" + +#. Tag: para +#: CacheLoader_FAQ.xml:134 +#, fuzzy, no-c-format +msgid "" +"Yes. Set the <literal>async</literal> attrobute to true. See the JBoss Cache " +"Users' Guide for a more detailed discussion. By default though, all cache " +"loader writes are synchronous and will block." +msgstr "" +"到 JBossCache 1.2.4 为止，可以。请把 CacheLoaderAsynchronous 属性设置为 " +"true。详情请参考 JBossCache 的文档。但在缺省情况下，所有对 cache loader 的写" +"入都是同步的且可能阻塞。" + +#. Tag: para +#: CacheLoader_FAQ.xml:145 +#, fuzzy, no-c-format +msgid "Can I write my own cache loader ?" +msgstr "我可以编写自己的 CacheLoader 吗？" + +#. Tag: para +#: CacheLoader_FAQ.xml:149 +#, fuzzy, no-c-format +msgid "" +"Yes. A cache loader is a class implementing <literal>org.jboss.cache.loader." +"CacheLoader</literal> or extending <literal>org.jboss.cache.loader." +"AbstractCacheLoader</literal> . It is configured via the XML file (see JBoss " +"Cache Users' Guide)." +msgstr "" +"可以。CacheLoader 是一个实现 <literal>org.jboss.cache.loader.CacheLoader</" +"literal> 的类。它可以通过 XML 文件来配置（请参考 JBossCache 教程）。" + +#. Tag: para +#: CacheLoader_FAQ.xml:161 +#, fuzzy, no-c-format +msgid "Does a cache loader have to use a persistent store ?" +msgstr "CacheLoader 必须使用持久性存储吗？" + +#. Tag: para +#: CacheLoader_FAQ.xml:165 +#, fuzzy, no-c-format +msgid "" +"No, a cache loader could for example fetch (and possibly store) its data " +"from a webdav-capable webserver. Another example is a caching proxy server, " +"which fetches contents from the web. Note that an implementation of " +"CacheLoader may not implement the 'store' functionality in this case, but " +"just the 'load' functionality." +msgstr "" +"否，例如 CacheLoader 可以从启用 webdav 的 web 服务器中获取数据。另外一个例子" +"就是缓存代理服务器，它也从 web 提取数据。请注意，此时 CacheLoader 的实现可以" +"仅仅实现 'load' 功能而不实现 'store' 功能。" + +#. Tag: para +#: CacheLoader_FAQ.xml:177 +#, fuzzy, no-c-format +msgid "Do I have to pay to use Oracle's Berkeley DB CacheLoader?" +msgstr "我需要为 Sleepycat 的 CacheLoader 付费吗？" + +#. Tag: para +#: CacheLoader_FAQ.xml:181 +#, fuzzy, no-c-format +msgid "" +"Not if you use it only for personal use. As soon as you distribute your " +"product with BdbjeCacheLoader, you have to purchase a commercial license " +"from Oracle. See details at <ulink url=\"http://www.sleepycat.com/" +"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ." +msgstr "" +"如果你只是把它用于私人目的则不需要。但如果你分发带有 BdbjeCacheLoader 的产" +"品，你就得从 Sleepycat 购买商业许可证。详情请访问 <ulink url=\"http://www." +"sleepycat.com/jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </" +"ulink>。" + +#. Tag: para +#: CacheLoader_FAQ.xml:194 +#, no-c-format +msgid "Are there any tools available to monitor the Berkeley DB instance?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:198 +#, no-c-format +msgid "" +"Yes. Oracle ships a JMX-based monitoring tool, called <ulink url=\"http://" +"www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/" +"jmx/JEMonitor.html\"> JEMonitor </ulink> which can be downloaded from the " +"Oracle website." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:211 +#, no-c-format +msgid "" +"When tuning my Berkeley DB instance, where should I put my je.properties " +"file?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:215 +#, no-c-format +msgid "" +"<literal>je.properties</literal> should reside in your Berkeley DB home " +"directory. This is the directory you pass in to the BDBJECacheLoader's " +"<literal>location</literal> configuration property." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:227 +#, no-c-format +msgid "Can I use more than one cache loader?" +msgstr "我可以使用多个 cache loader 吗？" + +#. Tag: para +#: CacheLoader_FAQ.xml:231 +#, fuzzy, no-c-format +msgid "" +"Yes. Within the CacheLoaderConfiguration XML element (see Users' Guide " +"chapter on cache loaders) you can describe several cache loaders. The impact " +"is that the cache will look at all of the cache loaders in the order they've " +"been configured, until it finds a valid, non-null element of data. When " +"performing writes, all cache loaders are written to (except if the " +"ignoreModifications element has been set to true for a specific cache loader." +msgstr "" +"到 JBossCache 1.3.0 为止，可以。使用新的 CacheLoaderConfiguration XML 元素" +"（请参考用户手册），你现在可以描述多个 cache loader。这样缓存就会按照配置顺序" +"查找所有的 cache loader，直到它找到一个有效的、非空的数据元素。当执行写操作" +"时，所有的 cache loader 都可以写入（除非某个 cache loader 的 " +"ignoreModifications 元素已经设置为 true）。" + +#. Tag: para +#: CacheLoader_FAQ.xml:245 +#, no-c-format +msgid "" +"Can I migrate a JDBCacheLoader or FileCacheLoader based cache store " +"containing data formatted with JBoss Cache 1.x.x to JBoss Cache 2.0 format?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:250 +#, no-c-format +msgid "" +"Yes. See \"Transforming Cache Loaders\" section within the \"Cache Loaders\" " +"section located in the JBoss Cache Users' Guide." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:257 +#, no-c-format +msgid "Is the TCPDelegatingCacheLoader resilient to TCPCacheServer restarts?" +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:263 +#, no-c-format +msgid "" +"As of JBoss Cache 2.1.0, the answer is yes. See the Users' Guide for details " +"on how to configure and tune your retries and wait period for reestablishing " +"the TCP connection." +msgstr "" + +#. Tag: para +#: CacheLoader_FAQ.xml:269 +#, no-c-format +msgid "" +"Prior to that, restarting the TCPCacheServer would also mean restarting your " +"application that uses the cache." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Eviction_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Eviction_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Eviction_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,152 @@ +# Language zh-CN translations for JBoss_EAP package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: JBoss_EAP 4_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2009-01-13 06:01+0000\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 +#: Eviction_FAQ.xml:6 +#, no-c-format +msgid "Eviction Policies" +msgstr "Eviction 策略" + +#. Tag: para +#: Eviction_FAQ.xml:10 +#, no-c-format +msgid "Does JBoss Cache support eviction policies?" +msgstr "JBoss Cache 支持 eviction 策略吗？" + +#. Tag: para +#: Eviction_FAQ.xml:14 +#, no-c-format +msgid "" +"Yes. JBoss Cache currently supports multiple eviction policies such as LRU, " +"MRU, and FIFO. Users can also plug in their own eviction policy algorithms. " +"See user guide for details." +msgstr "" + +#. Tag: para +#: Eviction_FAQ.xml:23 +#, fuzzy, no-c-format +msgid "Does JBoss Cache's eviction policy operates in replication mode?" +msgstr "JBoss Cache 的 LRU eviction 策略应用于复制模式吗？" + +#. Tag: para +#: Eviction_FAQ.xml:29 +#, no-c-format +msgid "Yes and no. :-)" +msgstr "可以说是，也可以说不是。：）" + +#. Tag: para +#: Eviction_FAQ.xml:31 +#, fuzzy, no-c-format +msgid "" +"The eviction policy only operates in local mode. That is, nodes are only " +"evicted locally. This may cause the cache contents not to be synchronized " +"temporarily. But when a user tries to obtain the cached contents of an " +"evicted node and finds out that is null (e.g., <literal>get</literal> " +"returns null), it should get it from the other data source and re-populate " +"the data in the cache. During this moment, the node content will be " +"propagated and the cache content will be in sync." +msgstr "" +"LRU 策略只用于本地模式。也就是说，只在本地剔除节点。这可能导致缓存内容临时地" +"不同步。但当用户试图从被剔除的节点获取缓存内容并发现它是空值时（如 " +"<literal>get</literal> 返回 null），用户应该从其他数据源获取数据并在缓存里重" +"新填充这些内容。此时，内容将在节点间传递，缓存内容又会同步了。" + +#. Tag: para +#: Eviction_FAQ.xml:42 +#, no-c-format +msgid "" +"However, you still can run eviction policies with cache mode set to either " +"<literal>REPL_SYNC</literal> or <literal>REPL_ASYNC</literal> . Depending on " +"your use case, you can set multiple cache instances to have their own " +"eviction policy (which are applied locally) or just have selected instances " +"with eviction policies activated." +msgstr "" +"然而，你仍然可以用 <literal>REPL_SYNC</literal> 或 <literal>REPL_ASYNC</" +"literal> 缓存模式来运行 eviction 策略。根据需要，你可以使多个缓存实例具有自己" +"的 eviction 策略（在本地应用）或者只激活某些实例的 eviction 策略。" + +#. Tag: para +#: Eviction_FAQ.xml:53 +#, no-c-format +msgid "" +"Also note that, with cache loader option, a locally evicted node can also be " +"persisted to the backend store and a user can retrieve it from the store " +"later on." +msgstr "" +"也请注意，如使用 cache loader 选项，本地剔除的节点也可以持久化到后台数据库" +"里，以后用户可以从中提取它。" + +#. Tag: para +#: Eviction_FAQ.xml:62 +#, no-c-format +msgid "Does JBoss Cache support <literal>Region</literal> ?" +msgstr "JBoss Cache 支持 <literal>Region</literal>？" + +#. Tag: para +#: Eviction_FAQ.xml:69 +#, no-c-format +msgid "" +"Yes. JBoss Cache has the notion of region where a user can configure the " +"eviction policy parameters (e.g., <literal>maxNodes</literal> or " +"<literal>timeToIdleSeconds</literal> )" +msgstr "" +"是的。JBoss Cache 具有 region 标记，用户可以配置 eviction 策略的参数（如 " +"<literal>maxNodes</literal> 或 <literal>timeToIdleSeconds</literal>）。" + +#. Tag: para +#: Eviction_FAQ.xml:77 +#, fuzzy, no-c-format +msgid "" +"A region in JBoss Cache denotes a portion of tree hierarchy, e.g., a fully " +"qualified name ( <literal>org.jboss.cache.Fqn</literal> ). For example, a " +"user can define <literal>/org/jboss</literal> and <literal>/org/foocom</" +"literal> as two separate regions. But note that you can configure the region " +"programmatically now, i.e., everything has to be configured through the xml " +"file." +msgstr "" +"JBoss Cache 的 region 构成树型分层结构的一部分，如全限定名（<literal>FQN</" +"literal>）。例如，用户可以把 <literal>/org/jboss</literal> 和 <literal>/org/" +"foocom</literal> 定义为两个独立的 region。但请注意，目前你还不能在程序里配置 " +"region，也就是说一切都得通过 XML 文件进行配置。" + +#. Tag: para +#: Eviction_FAQ.xml:94 +#, no-c-format +msgid "" +"I have turned on the eviction policy, why do I still get \"out of memory" +"\" (OOM) exception?" +msgstr "" +"我已经启用了 eviction 策略，但为什么还遇到 \"out of memory\" (OOM) 异常？" + +#. Tag: para +#: Eviction_FAQ.xml:100 +#, fuzzy, no-c-format +msgid "" +"OOM can happen when the speed of cache access exceeds the speed of eviction " +"policy handling timer. Eviction policy handler will wake up every " +"<literal>wakeUpInterval</literal> milliseconds (or " +"<literal>wakeUpIntervalSeconds</literal> seconds, prior to 3.x) to process " +"the eviction event queue. So when the queue size is full, it will create a " +"backlog and cause out-of-memory exceptions to happen unless the eviction " +"timer catches up. To address this problem, in addition to increase the VM " +"heap size, you can also reduce the <literal>wakeUpInterval</literal> so the " +"timer thread processes the queue more frequently." +msgstr "" +"当缓存速度超出了 eviction 策略处理定时器的速度时，OOM 就会出现。Eviction 策略" +"处理程序将每隔<literal>wakeUpIntervalInSeconds</literal> 秒被唤醒并处理 " +"eviction 队列。队列的大小目前被固定为 20000。所以，当队列满了，它将创建积压，" +"除非被 eviction 定时器捕获，否则 OOM 将出现。要解决这个问题，出了增加 VM 的堆" +"大小，你也可以减少 <literal>wakeUpIntervaleInSeconds</literal>，让定时器线程" +"更加频繁地进行处理。" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/General_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/General_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/General_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,163 @@ +# Language zh-CN translations for JBoss_EAP package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: JBoss_EAP 4_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2009-01-13 06:01+0000\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 +#: General_FAQ.xml:6 +#, no-c-format +msgid "General Information" +msgstr "常见问题" + +#. Tag: para +#: General_FAQ.xml:10 +#, no-c-format +msgid "What is JBoss Cache?" +msgstr "什么是 JBoss Cache？" + +#. Tag: para +#: General_FAQ.xml:14 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache is a replicated and transactional cache. It is replicated since " +"multiple JBoss Cache instances can be distributed (either within the same " +"JVM or across several JVMs whether they reside on the same machine or on " +"different machines on a network) and data is replicated across the whole " +"group. It is transactional because a user can configure a <ulink url=" +"\"http://java.sun.com/products/jta/\">JTA</ulink> compliant transaction " +"manager and make any cache interaction transactional, and caches would " +"participate in ongoing JTA transactions. Note that the cache can also be run " +"without any replication; this is the local mode." +msgstr "" +"JBoss Cache 是一个事务性的复制缓存。因为多个 JBoss Cache 实例可以分布运行（可" +"以在同一主机或不同主机上的相同或不同的 LVM 里）且数据在整个组群里进行复制，所" +"以称之为复制缓存。因为用户可以配置 JTA 兼容的事务管理者并使缓存操作事务化，所" +"以它是事务性的缓存。请注意，这个缓存也可以不进行任何复制，也就是以本地模式运" +"行。" + +#. Tag: para +#: General_FAQ.xml:28 +#, no-c-format +msgid "" +"JBoss Cache comes in two flavours: Core and POJO versions. The core library " +"(using the <literal>org.jboss.cache.Cache</literal> interface) is the " +"underlying library that organises data in a tree-like structure and handles " +"all locking, passivation, eviction and replication characteristics of data " +"in the cache. The POJO library (using the <literal>org.jboss.cache.pojo." +"PojoCache</literal> interface) is built atop the core library and allows " +"introspection of objects in the cache providing transparent coherence by " +"using JBoss AOP. Note that the POJO edition of JBoss Cache (often referred " +"to as POJO Cache) comes with a separate set of documentation (Users' Guide, " +"FAQ, etc.) available on the JBoss Cache <ulink url=\"http://www.jboss.org/" +"jbosscache/\">documentation website</ulink>." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:66 +#, no-c-format +msgid "Who are the JBoss Cache developers?" +msgstr "JBoss Cache 的开发人员是什么人？" + +#. Tag: para +#: General_FAQ.xml:70 +#, no-c-format +msgid "" +"JBoss Cache has an active community of developers and contributors. The " +"project was founded by Bela Ban and is currently led by Manik Surtani. Jason " +"Greene is the lead for the POJO Cache subsystem, and other contributors both " +"past and present include Ben Wang, Harald Gliebe, Brian Stansberry, Vladimir " +"Blagojevic, Mircea Markus, Jimmy Wilson, Galder Zamarreño and Elias Ross." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:139 +#, no-c-format +msgid "How do I know the version of JBoss Cache that I am using?" +msgstr "我如何知道所使用的 JBoss Cache 的版本？" + +#. Tag: para +#: General_FAQ.xml:143 +#, no-c-format +msgid "" +"<literal>java -jar jbosscache-core.jar</literal> will spit out version " +"details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:152 +#, fuzzy, no-c-format +msgid "" +"Can I run JBoss Cache outside of the JBoss Enterprise Application Platform?" +msgstr "我可以在 JBoss 应用服务器之外运行 JBoss Cache 吗？" + +#. Tag: para +#: General_FAQ.xml:157 +#, no-c-format +msgid "" +"Absolutely! Even though JBoss Cache comes integrated with the JBoss " +"Enterprise Application Platform, it can also be used in any other Java EE " +"server such as BEA WebLogic, IBM Websphere or Tomcat. It can also run in a " +"standalone Java process, completely outside of an application server. See " +"the Users' Guide for more details." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:170 +#, no-c-format +msgid "" +"How can I migrate my application and configuration from using JBoss Cache 1." +"x to 2.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:173 +#, no-c-format +msgid "" +"Look at <ulink url=\"http://www.jboss.org/community/docs/DOC-10246\">this " +"wiki page</ulink> for help." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:182 +#, no-c-format +msgid "What about from 2.x to 3.x?" +msgstr "" + +#. Tag: para +#: General_FAQ.xml:185 +#, no-c-format +msgid "" +"JBoss Cache 3.x is API compatible with 2.x, although as far as possible you " +"should refactor your code not to use deprecated methods as these may " +"disappear in future releases of JBoss Cache." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:190 +#, no-c-format +msgid "" +"JBoss Cache 3.x comes with an all new configuration format. Old 2.x " +"configuration files will still work, although you will get a warning in the " +"logs about this. Again, as far as possible, we recommend migrating your " +"configuration file to the new format. Scripts are provided with the JBoss " +"Cache 3.x distribution to migrate configuration files (see " +"<literal>config2to3.sh</literal> and<literal>config2to3.bat</literal>)." +msgstr "" + +#. Tag: para +#: General_FAQ.xml:201 +#, no-c-format +msgid "" +"Note that to take advantage of some of the new features in JBoss Cache 3.x, " +"you need to be using the new configuration format." +msgstr "" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/JBoss_Cache_Frequently_Asked_Questions.po =================================================================== Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Revision_History.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Revision_History.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Revision_History.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,26 @@ +# Language zh-CN translations for JBoss_EAP package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: JBoss_EAP 4_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2009-01-13 06:01+0000\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 +#: Revision_History.xml:6 +#, no-c-format +msgid "Revision History" +msgstr "" + +#. Tag: author +#: Revision_History.xml:12 +#, fuzzy, no-c-format +msgid "<firstname></firstname> <surname></surname> <email></email>" +msgstr "<firstname>John</firstname> <surname>Doe</surname>" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/TreeCache_FAQ.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/TreeCache_FAQ.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/TreeCache_FAQ.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,992 @@ +# Language zh-CN translations for JBoss_EAP package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: JBoss_EAP 4_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2009-01-13 06:01+0000\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 +#: TreeCache_FAQ.xml:6 +#, fuzzy, no-c-format +msgid "JBoss Cache: Core" +msgstr "JBoss Cache 1.4.1" + +#. Tag: para +#: TreeCache_FAQ.xml:26 +#, no-c-format +msgid "Can I run multiple JBoss Cache instances on the same VM?" +msgstr "我可以在同一个 VM 里运行多个 JBoss Cache 实例吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:30 +#, no-c-format +msgid "" +"Yes. There are some scenarios where you may want to run multiple instances " +"of JBoss Cache. For example, you want to run multiple local cache instances " +"with each instance having its own configuration (e.g., different cache " +"policy). In this case, you will need multiple xml configuration files." +msgstr "" +"可以。在某些情况下，你可能希望运行多个 JBoss Cache 实例。例如，你想运行多个本" +"地缓存实例，而每个实例都有自己的配置（例如，不同的缓存策略）。此时，你将需要" +"多个 xml 配置文件。" + +#. Tag: para +#: TreeCache_FAQ.xml:41 +#, fuzzy, no-c-format +msgid "Can JBoss Cache run as a second level cache inside Hibernate?" +msgstr "TreeCache 可以作为 Hibernate 内部的二级缓存运行吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:47 +#, fuzzy, no-c-format +msgid "" +"Yes. Since Hibernate 3.0 release, you can configure it to use JBoss Cache as " +"a second level cache. For details, see Hibernate documentation, and also see " +"<ulink url=\"http://www.jboss.org/community/docs/DOC-10265\">this wiki page</" +"ulink>." +msgstr "" +"可以。从 Hibernate 3.0 开始，你可以配置它把 JBoss Cache（亦即 TreeCache）用作" +"二级缓存。细节请参考 Hibernate 文档和 <ulink url=\"http://wiki.jboss.org/" +"wiki/Wiki.jsp?page=JBossCacheHibernate\"> http://wiki.jboss.org/wiki/Wiki." +"jsp?page=JBossCacheHibernate </ulink>。" + +#. Tag: para +#: TreeCache_FAQ.xml:52 +#, no-c-format +msgid "" +"JBoss Cache 3.x with MVCC in particular works very well as a Hibernate " +"second level cache." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:60 +#, fuzzy, no-c-format +msgid "What about using POJO Cache as a Hibernate cache?" +msgstr "如果把 PojoCache 作为 Hibernate 缓存使用呢？" + +#. Tag: para +#: TreeCache_FAQ.xml:64 +#, fuzzy, no-c-format +msgid "" +"It is not necessary to use POJO Cache for second level cache inside " +"Hibernate because Hibernate manages fine-grained fields in Java objects. " +"Using POJO Cache won't provide any advantage, and will be an unnecessary " +"performance drawback." +msgstr "" +"因为 Hibernate 管理 Java 对象里的细颗粒度字段，所以没有必要在 Hibernate 里把 " +"PojoCache 作为二级缓存使用。使用 PojoCache 并不会提供任何益处。" + +#. Tag: para +#: TreeCache_FAQ.xml:74 +#, no-c-format +msgid "How can I configure JBoss Cache?" +msgstr "我该如何配置 JBoss Cache？" + +#. Tag: para +#: TreeCache_FAQ.xml:78 +#, no-c-format +msgid "" +"You can configure the JBoss Cache through a configuration xml file or " +"programmatically using a <literal>org.jboss.cache.config.Configuration</" +"literal> object, passed in to the <literal>org.jboss.cache.CacheFactory</" +"literal> instance." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:90 +#, no-c-format +msgid "" +"Can I use a schema or DTD to validate my JBoss Cache configuration file?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:95 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, yes. An XSD schema is provided in your jbosscache-" +"core.jar file, and is also available online, on<ulink url=\"http://www.jboss." +"org/jbosscache/jbosscache-config-3.0.xsd\"> http://www.jboss.org/jbosscache/" +"jbosscache-config-3.0.xsd</ulink>. You can configure your IDE, text editor " +"or XML authoring tool to use this schema to validate your file." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:108 +#, no-c-format +msgid "What is the difference between the different cache modes?" +msgstr "不同的缓存模式之间的区别是什么？" + +#. Tag: para +#: TreeCache_FAQ.xml:113 +#, no-c-format +msgid "" +"JBossCache has five different cache modes, i.e., <literal>LOCAL</literal> , " +"<literal>REPL_SYNC</literal> , <literal>REPL_ASYNC</literal> , " +"<literal>INVALIDATION_SYNC</literal> and <literal>INVALIDATION_ASYNC</" +"literal> . If you want to run JBoss Cache as a single instance, then you " +"should set the cache mode to <literal>LOCAL</literal> so that it won't " +"attempt to replicate anything. If you want to have synchronous replication " +"among different JBoss Cache instances, you set it to <literal>REPL_SYNC</" +"literal> . For asynchronous replication, use <literal>AYSNC_REPL</literal> . " +"If you do not wish to replicate cached data but simply inform other caches " +"in a cluster that data under specific addresses are now stale and should be " +"evicted from memory, use <literal>INVALIDATION_SYNC</literal> or " +"<literal>INVALIDTAION_ASYNC</literal> . Synchronous and asynchronous " +"behavior applies to invalidation as well as replication." +msgstr "" +"JBossCache 具有 5 种不同的缓存模式，它们是：<literal>LOCAL</literal>、" +"<literal>REPL_SYNC</literal>、<literal>REPL_ASYNC</literal>、" +"<literal>INVALIDATION_SYNC</literal> 和 <literal>INVALIDATION_ASYNC</" +"literal>。如果你想以单个实例的方式运行 JBoss Cache，你应该把缓存模式设置为 " +"<literal>LOCAL</literal>，这样它就不会试图进行任何复制。如果你想在不同的 " +"JBoss Cache 实例间同步进行复制，你需要设置它为 <literal>REPL_SYNC</literal>。" +"对于异步复制，请使用 <literal>AYSNC_REPL</literal>。如果你不希望复制缓存数据" +"但需要简单地通知群集里的其他缓存特殊地址上的数据已经过期且应该从内存里剔出，" +"请使用 <literal>INVALIDATION_SYNC</literal> 或 <literal>INVALIDTAION_ASYNC</" +"literal>。同步和异步行为既可用于 invalidation（失效），也可用于 replication" +"（复制）。" + +#. Tag: para +#: TreeCache_FAQ.xml:143 +#, no-c-format +msgid "" +"Note that <literal>ASYNC_REPL</literal> and <literal>INVALIDATION_ASYNC</" +"literal> are non-blocking. This can be useful when you want to have another " +"JBoss Cache serving as a mirror or backup and you don't want to wait for " +"confirmation that this mirror has received your messages." +msgstr "" +"请注意，<literal>ASYNC_REPL</literal> 和 <literal>INVALIDATION_ASYNC</" +"literal> 是非阻塞的。当你希望用另外一个 JBoss Cache 作为镜像或备份，而不希望" +"等候该镜像确认收到你的消息时，你就可以使用这两个模式。" + +#. Tag: para +#: TreeCache_FAQ.xml:157 +#, no-c-format +msgid "How does JBoss Cache's replication mechanism work?" +msgstr "JBoss Cache 的复制机制是怎样工作的？" + +#. Tag: para +#: TreeCache_FAQ.xml:161 +#, no-c-format +msgid "" +"JBoss Cache leverages <ulink url=\"http://www.jgroups.org\">JGroups</ulink> " +"for network communications. A JGroups configuration section is present in " +"your JBoss Cache configuration." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:166 +#, fuzzy, no-c-format +msgid "" +"A user can configure the cluster of JBoss Cache instances by sharing the " +"same cluster name ( <literal>cluster name</literal> ). There is also an " +"option of whether to populate the cache data upon starting a new instance in " +"the <literal>ClusterConfig</literal> attribute." +msgstr "" +"JBoss Cache 把 <ulink url=\"http://www.jgroups.org\">JGroups</ulink> 作为复制" +"层。用户可以通过共享相同的群集名称（<literal>cluster name</literal>）来配置 " +"JBoss Cache 实例的群集。你也可以配置 <literal>ClusterConfig</literal> 属性里" +"的选项来选择在启动新的实例时是否传递缓存数据。" + +#. Tag: para +#: TreeCache_FAQ.xml:178 +#, fuzzy, no-c-format +msgid "" +"Note that once all instances join the same replication group, every " +"replication change is propagated to all participating members. There is no " +"mechanism for sub-partitioning where some replication can be done within " +"only a subset of members, unless you use the Buddy Replication features. See " +"the Users' Guide for more details on this." +msgstr "" +"请注意，一旦所有的实例都加入了相同的复制组，每个复制的变化都会传递给所有参与" +"的成员。这里没有可以在成员子集里完成复制的子分区机制。这是我们下一步的目标。" + +#. Tag: para +#: TreeCache_FAQ.xml:190 +#, no-c-format +msgid "" +"I run a 2 node cluster. If the network dies, do the caches continue to run?" +msgstr "我的群集里有两个节点。如果网络发生了故障，缓存还会继续运行吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:194 +#, no-c-format +msgid "" +"Yes, both will continue to run, but depending on your replication mode, all " +"transactions or operations may not complete. If <literal>REPL_SYNC</literal> " +"is used, operations will fail while if <literal>REPL_ASYNC</literal> is used " +"they will succeed. Even if they succeed though, caches will be out of sync." +msgstr "" +"是的，两者都会继续运行，但这取决于你的复制模式，所有的事务或操作都可能没有完" +"成。如果使用了 <literal>REPL_SYNC</literal>，操作将会失败；而如果使用了 " +"<literal>REPL_ASYNC</literal>，它们将完成。但即使它们成功地完成了，缓存还是会" +"不同步。" + +#. Tag: para +#: TreeCache_FAQ.xml:207 +#, no-c-format +msgid "" +"Can I plug in library X instead of JGroups to handle remote calls and group " +"communications?" +msgstr "我可以用 library X 替代 JGroups 来处理远程调用和组通讯吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:212 +#, fuzzy, no-c-format +msgid "" +"At this stage the answer is no. We do have an abstraction layer between the " +"communication suite and JBoss Cache in the pipelines, and this may appear as " +"a feature at some stage in the future." +msgstr "" +"在目前阶段（JBoss Cache 1.x）答案是否。在通讯套件和 JBoss Cache 之间确实有一" +"个绝对层，在将来这可能会作为新的功能出现。" + +#. Tag: para +#: TreeCache_FAQ.xml:223 +#, no-c-format +msgid "" +"Does the cache need to replicate to every other instance in the cluster? " +"Isn't this slow if the cluster is large?" +msgstr "缓存需要复制到群集里的每个其他实例吗？如果群集很大，这会不会很慢？" + +#. Tag: para +#: TreeCache_FAQ.xml:230 +#, fuzzy, no-c-format +msgid "" +"Replication need not occur to every node in the cluster. This feature - " +"called Buddy Replication - allows each node to pick one or more 'buddies' in " +"the cluster and only replicate to its buddies. This allows a cluster to " +"scale very easily with no extra impact on memory or network traffic with " +"each node added." +msgstr "" +"到 JBoss Cache 1.4.0 为止，复制不需要应用到群集里的每个节点。这个功能 - 称为 " +"Buddy Replication - 允许每个节点在群集里挑选一个或多个 'buddies' 并只复制到这" +"些 buddy 里。这使得群集可以轻易地添加节点进行扩充而不会对内存或网络负载有额外" +"的影响。" + +#. Tag: para +#: TreeCache_FAQ.xml:237 +#, fuzzy, no-c-format +msgid "" +"See the Users' Guide for more information on Buddy Replication, and how it " +"can be used to achieve very high scalability." +msgstr "" +"关于 Buddy Replication 的更多信息以及怎样用它来实现更好的扩充性，请参考《用户" +"指南》。" + +#. Tag: para +#: TreeCache_FAQ.xml:248 +#, no-c-format +msgid "" +"I'm using Buddy Replication. Do I need to have some form of session affinity?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:251 +#, no-c-format +msgid "" +"Session affinity relates to returning to the same cache instance for the " +"same data being used. While this is strictly not a requirement for Buddy " +"Replication, it is greatly recommended to minimize moving state around a " +"cluster." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:261 +#, fuzzy, no-c-format +msgid "" +"If I have the need for different configuration properties (e.g., " +"<literal>CacheMode</literal> and <literal>IsolationLevel</literal> ), do I " +"simply need to create multiple <literal>org.jboss.cache.Cache</literal> " +"instances with the appropriate configuration?" +msgstr "" +"如果我需要不同的 TreeCache 属性（如 <literal>CacheMode</literal> 和 " +"<literal>IsolationLevel</literal>），我是不是只要用合适的配置创建多个 " +"TreeCache 实例就可以了？" + +#. Tag: para +#: TreeCache_FAQ.xml:272 +#, fuzzy, no-c-format +msgid "" +"Yes. All the above mentioned properties are per cache instance. Therefore " +"you will need separate <literal>org.jboss.cache.Cache</literal> instances." +msgstr "" +"对。上面提及的所有属性都是为每个实例进行配置的。因此你需要单独的 JBoss Cache " +"实例。" + +#. Tag: para +#: TreeCache_FAQ.xml:282 +#, no-c-format +msgid "" +"Isn't this expensive from a networking standpoint, i.e., needing to create " +"sockets for each <literal>org.jboss.cache.Cache</literal> instance?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:289 +#, no-c-format +msgid "" +"Yes, it can be. For such cases it is recommended that you configure your " +"cache using the JGroups Multiplexer, which allows several caches to share a " +"single JGroups channel. Please see the Users' Guide for details on how to " +"configure the JGroups Multiplexer." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:296 +#, no-c-format +msgid "" +"A faster and more efficient approach is to use a shared transport in " +"JGroups. Please see <ulink url=\"http://www.jgroups.org\">the JGroups " +"documentation</ulink> for more details on how to do this." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:307 +#, fuzzy, no-c-format +msgid "" +"Does the <literal>ClusterName</literal> configuration element have any " +"relation to the JBoss AS cluster <literal>PartitionName</literal> ?" +msgstr "" +"Tree Cache 配置里的 <literal>ClusterName</literal> 和 JBoss AS 群集的 " +"<literal>PartitionName</literal> 有任何联系吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:317 +#, no-c-format +msgid "" +"Yes. They are both JGroups group names. Besides the notion of a channel in " +"JGroups, it also can partition the channel into different group names." +msgstr "" +"有。它们都是 JGroups 组名。除了 JGroups 里的通道标记外，通道也可以分成不同的" +"组。" + +#. Tag: para +#: TreeCache_FAQ.xml:326 +#, fuzzy, no-c-format +msgid "" +"When using multiple JGroups based components [cluster-service.xml, cache " +"(multiple instances)], what is the correct/valid way to configure those " +"components to make sure my multicast addresses don't conflict?" +msgstr "" +"当使用多个基于 JGroups 的组件 [cluster-service.xml、treecache (多个实例)] " +"外，怎样正确地配置这组件来避免多点传送地址不会冲突？" + +#. Tag: para +#: TreeCache_FAQ.xml:334 +#, no-c-format +msgid "" +"There are two parameters to consider: multicast address (plus port) and the " +"group name. At minimum, you will have to run components using a different " +"group name. But whether to run them on the same channel depends upon whether " +"the communication performance is critical for you or not. If it is, then " +"it'd be best to run them on different channels." +msgstr "" +"你可以考虑两个参数：多点传送地址（以及端口）和组名。你最少得用不同的组名来运" +"行组件。但是否在同一通道里运行组件取决于通信性能对你而言是否很重要。如果是，" +"那么你最好在不同的通道里运行它们。" + +#. Tag: para +#: TreeCache_FAQ.xml:346 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache persistence storage?" +msgstr "JBoss Cache 目前支持缓存的持久性存储吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:352 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache has a cache loader interface that supports cache " +"persistence. See below for more FAQs on cache loaders." +msgstr "" +"是的。从 1.1 版本开始，JBoss Cache 有一个 CacheLoader 接口来支持缓存的持久" +"化。请参考下面的内容。" + +#. Tag: para +#: TreeCache_FAQ.xml:360 +#, fuzzy, no-c-format +msgid "Does JBoss Cache support cache passivation/ overflow to a data store?" +msgstr "JBoss Cache 目前支持缓存钝化/溢出至数据库吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:366 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache uses the cache loader to support cache passivation/ " +"overflow. See documentation on how to configure and use this feature." +msgstr "" +"是的。从 1.2.4 开始，JBoss Cache 使用 CacheLoader 来支持缓存钝化/溢出。请参考" +"和如何配置和使用该功能相关的文档。" + +#. Tag: para +#: TreeCache_FAQ.xml:375 +#, no-c-format +msgid "Is JBoss Cache thread safe?" +msgstr "JBoss Cache 是线程安全（thread-safe）的吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:379 +#, no-c-format +msgid "Yes, it is thread safe." +msgstr "是的。" + +#. Tag: para +#: TreeCache_FAQ.xml:385 +#, no-c-format +msgid "Does JBoss Cache support XA (2PC) transactions now?" +msgstr "JBoss Cache 目前支持 XA (2PC) 事务吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:389 +#, fuzzy, no-c-format +msgid "" +"No, although it is also on our to do list. Our internal implementation does " +"use a procedure similar to 2PC to coordinate a transactions among different " +"instances, but JBoss Cache is not an XA resource." +msgstr "" +"不支持，虽然我们已经将其提上议程了。但我们内部的实现使用一个类似的 2PC 过程来" +"协调多个实例间的事务。" + +#. Tag: para +#: TreeCache_FAQ.xml:398 +#, fuzzy, no-c-format +msgid "Which transaction managers are supported by JBoss Cache?" +msgstr "JBoss Cache 支持哪些 TransactionManager？" + +#. Tag: para +#: TreeCache_FAQ.xml:404 +#, no-c-format +msgid "" +"JBoss Cache supports any TransactionManager that is <ulink url=\"http://java." +"sun.com/products/jta/\">JTA</ulink> compliant such as<ulink url=\"http://www." +"jboss.org/jbosstm/\">JBoss Transactions</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:408 +#, no-c-format +msgid "" +"While JBoss Cache does ships with a dummy transaction manager (<literal>org." +"jboss.cache.transaction.DummyTransactionManager</literal>), we do " +"<emphasis>not</emphasis> recommend using this for production. It is not " +"thread safe, and is intended for internal testing only." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:421 +#, no-c-format +msgid "How do I set up the cache to be transactional?" +msgstr "我怎样设立事务性的缓存？" + +#. Tag: para +#: TreeCache_FAQ.xml:425 +#, fuzzy, no-c-format +msgid "" +"You either use the default transaction manager that ships with JBoss AS or " +"you have to implement the <literal>org.jboss.cache.transaction." +"TransactionManagerLookup</literal> interface, and return an instance of your " +"<literal>javax.transaction.TransactionManager</literal> implementation. The " +"configuration property <literal>TransactionManagerLookupClass</literal> " +"defines the class to be used by the cache to fetch a reference to a " +"transaction manager. It is trivial to implement this interface to support " +"other transaction managers. Once this attribute is specified, the cache will " +"look up the transaction context from this transaction manager." +msgstr "" +"你可以使用缺省的 TransactionManager 在 JBoss 里运行 JBossCache，或者你得实现 " +"<literal>TransactionManagerLookup</literal> 接口并返回 javax.transaction." +"TransactionManager 实例。配置属性 <literal>TransactionManagerLookupClass</" +"literal> 定义了缓存用来获取 TransactionManager 引用的类。要支持其他 " +"TransactionManager 并不需要实现这个类。一旦指定了这个属性，缓存将查找该 " +"TransactionManager 的事务上下文。 " + +#. Tag: para +#: TreeCache_FAQ.xml:441 +#, no-c-format +msgid "" +"The <literal>org.jboss.cache.transaction.GenericTransactionManagerLookup</" +"literal> class that ships with JBoss Cache is able to detect and bind to " +"most popular transaction managers. See the " +"<literal>GenericTransactionManagerLookup</literal> javadocs for more " +"information." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:454 +#, no-c-format +msgid "How do I control the cache locking level?" +msgstr "我怎样才能控制缓存的锁级别？" + +#. Tag: para +#: TreeCache_FAQ.xml:458 +#, fuzzy, no-c-format +msgid "" +"JBoss Cache lets you control the cache locking level through the transaction " +"isolation level. This is configured through the attribute " +"<literal>IsolationLevel</literal> . The transaction isolation levels " +"correspond to database isolation levels, namely, <literal>NONE</literal> , " +"<literal>READ_UNCOMMITTED</literal> , <literal>READ_COMMITTED</literal> , " +"<literal>REPEATABLE_READ</literal> , and <literal>SERIALIZABLE</literal> . " +"Note that these isolation levels are ignored if optimistic locking is used. " +"For details, please refer to the user manual." +msgstr "" +"JBossCache 允许你通过事务隔离级别来控制锁级别。这是通过配置 " +"<literal>IsolationLevel</literal> 属性来实现的。目前，JBossCache 内部采用了悲" +"观锁定机制。悲观锁的事务隔离级别对应 JDBC 的隔离级别，也就是<literal>NONE</" +"literal>、<literal>READ_UNCOMMITTED</literal>、 <literal>READ_COMMITTED</" +"literal>、<literal>REPEATABLE_READ</literal> 和 <literal>SERIALIZABLE</" +"literal>。请注意，如果使用乐观锁定，这些隔离级别将被忽略。详情请参考相关的用" +"户手册。" + +#. Tag: para +#: TreeCache_FAQ.xml:480 +#, no-c-format +msgid "" +"As of JBoss Cache 3.x, when using the MVCC locking scheme, only " +"<literal>READ_COMMITTED</literal> and <literal>REPEATABLE_READ</literal> are " +"supported. Any other isolation level provided will either be upgraded or " +"downgraded accordingly." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:493 +#, no-c-format +msgid "How does JBoss Cache lock data for concurrent access?" +msgstr "JBoss Cache 在并行访问时如何锁定数据？" + +#. Tag: para +#: TreeCache_FAQ.xml:497 +#, fuzzy, no-c-format +msgid "" +"In JBoss Cache 2.x, by default pessimistic locking is used to lock data " +"nodes, based on the isolation level configured. We also offer optimistic " +"locking to allow for greater concurrency at the cost of slight processing " +"overhead and performance. See the documentation for a more detailed " +"discussion on concurrency and locking in JBoss Cache." +msgstr "" +"JBoss Cache 缺省使用悲观锁并基于隔离级别来锁定数据节点。从 JBoss Cache 1.3.0 " +"开始，我们也提供乐观锁，在对负载和性能有稍许影响的情况下允许更大的并行性。关" +"于 JBoss Cache 里的并行性和锁的详细讨论，请参考相关文档。" + +#. Tag: para +#: TreeCache_FAQ.xml:505 +#, no-c-format +msgid "" +"In JBoss Cache 3.x, optimistic and pessimistic locking are deprecated in " +"favour of MVCC (multi-version concurrency control), which is far more " +"efficient than either optimistic or pessimistic locking. For a detailed " +"discussion on our MVCC implementation, see <ulink url=\"http://jbosscache." +"blogspot.com/2008/07/mvcc-has-landed.html\">this blog entry</ulink> " +"and<ulink url=\"http://www.jboss.org/community/docs/DOC-10272\">this wiki " +"page</ulink>." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:520 +#, fuzzy, no-c-format +msgid "How do I enable Optimistic Locking or MVCC in JBoss Cache?" +msgstr "我怎样才能启用 JBoss Cache 里的乐观锁？" + +#. Tag: para +#: TreeCache_FAQ.xml:524 +#, no-c-format +msgid "Please see the configuration section of the Users' Guide for details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:532 +#, no-c-format +msgid "Can I use the cache locking level even without a transaction context?" +msgstr "我可以使用不带有事务上下文的缓存锁级别吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:538 +#, fuzzy, no-c-format +msgid "" +"Yes. JBoss Cache controls the individual node locking behavior through the " +"isolation level semantics. This means even if you don't use a transaction, " +"you can specify the lock level via isolation level. You can think of the " +"node locking behavior outside of a transaction as if it is under transaction " +"with <literal>auto_commit</literal> on." +msgstr "" +"可以。JBossCache 通过隔离级别模式控制单个节点的锁行为。这意味着即使你不使用事" +"务，你也可以通过隔离级别指定锁级别。你可以仅考虑锁级别，就好像它处于事务里并" +"启用了 <literal>auto_commit</literal>。" + +#. Tag: para +#: TreeCache_FAQ.xml:551 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache support <literal>SELECT FOR UPDATE</literal> semantics?" +msgstr "JBoss Cache 支持 <literal>Region</literal>？" + +#. Tag: para +#: TreeCache_FAQ.xml:559 +#, no-c-format +msgid "" +"Yes, but this is is only possible if you are running within a JTA " +"transaction <emphasis>and</emphasis> are using either <literal>MVCC</" +"literal> or <literal>PESSIMISTIC</literal> as your node locking scheme." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:568 +#, no-c-format +msgid "To achieve <literal>SELECT FOR UPDATE</literal> semantics, simply do:" +msgstr "" + +#. Tag: programlisting +#: TreeCache_FAQ.xml:573 +#, no-c-format +msgid "" +"<![CDATA[\n" +"\n" +" // start transaction ... \n" +"\n" +" cache.getInvocationContext().getOptionOverrides().setForceWriteLock" +"(true);\n" +" Node n = cache.get(\"/a/b/c\"); // this acquires a WRITE LOCK on this " +"node\n" +" ...\n" +" ...\n" +"\n" +" // end transaction\n" +"\n" +" ]]>" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:579 +#, no-c-format +msgid "" +"With replication (REPL_SYNC/REPL_ASYNC) or invalidation (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC), how often does the cache broadcast messages over the " +"network?" +msgstr "" +"使用 replication (REPL_SYNC/REPL_ASYNC) 或 invalidation (INVALIDATION_SYNC/" +"INVALIDATION_ASYNC)，如缓存每隔多久会在网络上广播消息？" + +#. Tag: para +#: TreeCache_FAQ.xml:586 +#, fuzzy, no-c-format +msgid "" +"If the updates are under transaction, then the broadcasts happen only when " +"the transaction is about to commit (actually during the prepare stage " +"internally). That is, it will be a batch update. However, if the operations " +"are not under transaction context, then each update will trigger " +"replication. Note that this has performance implications if network latency " +"is a problem." +msgstr "" +"如果在事务里进行更新，广播只发生在事务将要提交时（实际是在内部的预备阶段）。" +"也就是说，这将是一个批量的更新。然而，如果该操作不处于事务上下文里，那每个更" +"新都将触发复制（replication）。请注意，如果网络传输负担较重的话（这是很常见" +"的），这可能导致性能问题。" + +#. Tag: para +#: TreeCache_FAQ.xml:598 +#, no-c-format +msgid "How can I do a mass removal?" +msgstr "我怎样才能进行大量删除？" + +#. Tag: para +#: TreeCache_FAQ.xml:602 +#, fuzzy, no-c-format +msgid "" +"If you do a<literal>cache.removeNode(\"/myroot\")</literal>, it will " +"recursively remove all the entries under \"/myroot\"." +msgstr "" +"如果你使用 cache.remove(\"/root\")，它将递归低删除 \"/root\" 下的所有条目。" + +#. Tag: para +#: TreeCache_FAQ.xml:610 +#, no-c-format +msgid "Can I monitor and manage the JBoss Cache?" +msgstr "我怎样才能监控和管理 JBoss Cache？" + +#. Tag: para +#: TreeCache_FAQ.xml:614 +#, fuzzy, no-c-format +msgid "" +"Yes, using a JMX console such as the one shipped with JBoss AS or Java 5's " +"<literal>jconsole</literal> utility. See the chapter titled <emphasis role=" +"\"bold\">Management Information</emphasis> in the JBoss Cache Users' Guide " +"for more details." +msgstr "" +"对于 JBoss Cache 1.3.0，它如果是在 JBoss AS 里运行或者使用了 JDK 5.0 的 " +"<literal>jconsole</literal> 工具，你就可以监控和管理它。详情请参考《JBoss " +"Cache 用户指南》里的 <emphasis role=\"bold\">Management Information</" +"emphasis> 章节。" + +#. Tag: para +#: TreeCache_FAQ.xml:625 +#, no-c-format +msgid "" +"JBoss Cache uses a <literal>:</literal> character in its object name. This " +"causes problems with my MBean server. What can I do about it?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:633 +#, no-c-format +msgid "" +"This is something we have seen with some MBean servers. By default, JBoss " +"Cache uses <literal>jboss.cache:service=JBossCache</literal> as a prefix to " +"all objects it binds in JMX. To work around this, use the <literal>-" +"Djbosscache.jmx.prefix</literal> JVM parameter to pass in an alternate " +"prefix." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:647 +#, fuzzy, no-c-format +msgid "Can I disable JBoss Cache management attributes?" +msgstr "我可以禁用 JBoss Cache 1.3.0 里的 JBoss Cache 管理属性吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:651 +#, no-c-format +msgid "" +"Yes, you can. See the section on configuration in the JBoss Cache Users' " +"Guide." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:658 +#, no-c-format +msgid "What happened to jboss-serialization.jar?" +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:662 +#, no-c-format +msgid "" +"As of JBoss Cache 2.0.0, the dependency on JBoss Serialization has been " +"dropped since most of the benefits of JBoss Serialization are available in " +"updated Java 5 VMs. Since JBoss Cache 2.0.0 is baselined on Java 5, there " +"was no need to provide these benefits separately." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:673 +#, no-c-format +msgid "Does JBoss Cache support partitioning?" +msgstr "JBoss Cache 支持分区（partitioning）吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:677 +#, no-c-format +msgid "" +"Not right now. JBoss Cache does not support partitioning that a user can " +"configure to have different set of data residing on different cache " +"instances while still participating as a replication group." +msgstr "" +"现在还不行。JBoss Cache 并不支持用户在不同的缓存实例里具有不同的数据但却以复" +"制组的形式存在。" + +#. Tag: para +#: TreeCache_FAQ.xml:682 +#, no-c-format +msgid "" +"This is on the roadmap though, so do keep an eye on <ulink url=\"http://jira." +"jboss.org/jira/browse/JBCACHE-60\">JBCACHE-60</ulink> if you are interested." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:692 +#, fuzzy, no-c-format +msgid "" +"Does JBoss Cache handle the concept of application classloading inside, say, " +"a Java EE container?" +msgstr "JBoss Cache 是否和 J2EE 容器一样具有内部的应用程序类加载机制？" + +#. Tag: para +#: TreeCache_FAQ.xml:698 +#, fuzzy, no-c-format +msgid "" +"Application-specific classloading is used widely inside a Java EE container. " +"For example, a web application may require a new classloader to scope a " +"specific version of the user library. However, by default JBoss Cache is " +"agnostic to the classloader. In general, this leads to two kinds of problems:" +msgstr "" +"J2EE 容器内部广泛地使用了应用程序专有的类加载。例如，web 应用程序可能需要新的" +"类加载器来为特定版本的用户库划定作用域。然而，JBoss Cache 缺省是不使用类加载" +"器的。因为这通常会导致两类问题：" + +#. Tag: para +#: TreeCache_FAQ.xml:707 +#, no-c-format +msgid "" +"Object instance is stored in cache1 and replicated to cache2. As a result, " +"the instance in cache2 is created by the system classloader. The replication " +"may fail if the system classloader on cache2 does not have access to the " +"required class. Even if replication doesn't fail, a user thread in cache2 " +"may not be able to access the object if the user thread is expecting a type " +"defined by the application classloader." +msgstr "" +"对象实例存储在 cache1 并复制到 cache2。因此，cache2 里的实例由系统类加载器创" +"建。但如果 cache2 里的系统加载器没有对所需类的访问权限，则应用程序可能会运行" +"失败。即使复制没有失败，如果 cache2 里的用户线程没有获得所期望的类加载器定义" +"的类型，它也可能不能访问对象。" + +#. Tag: para +#: TreeCache_FAQ.xml:718 +#, fuzzy, no-c-format +msgid "" +"Object instance is created by thread 1 and will be accessed by thread 2 " +"(with two different classloaders). JBoss Cache has no notion of the " +"different classloaders involved. As a result, you will have a " +"<literal>ClassCastException</literal> . This is a standard problem in " +"passing an object from one application space to another; JBoss Cache just " +"adds a level of indirection in passing the object." +msgstr "" +"对象实例由 thread1 创建且将被 thread2 访问（使用两个不同的类加载器）。而 " +"JBossCache 没有不同类加载器的标记，所以你会遇到 <literal>ClassCastException</" +"literal>。在把对象从一个应用程序空间传递到另外一个时，这是一个标准的问题。" +"JBossCache 只是在传递对象时添加一个间接层。" + +#. Tag: para +#: TreeCache_FAQ.xml:731 +#, fuzzy, no-c-format +msgid "" +"To solve the first kind of issue JBoss Cache uses a " +"<literal>CacheMarshaller</literal> . Basically, this allows application code " +"to register a classloader with a portion of the cache tree for use in " +"handling objects replicated to that portion. See the " +"<literal>CacheMarshaller</literal> section of the Users' Guide for more " +"details." +msgstr "" +"为了解决第一类的问题，我们在 JBoss Cache 1.2.4 里引入了 " +"<literal>TreeCacheMarshaller</literal> 的概念。基本上，这允许应用程序代码在类" +"加载器里注册为缓存树的一部分而只处理该部分的对象复制。请参考《用户指南》的 " +"TreeCacheMarshaller 部分来获得更多信息。" + +#. Tag: para +#: TreeCache_FAQ.xml:742 +#, no-c-format +msgid "" +"To solve the second kind of issue, you can use the the " +"<literal>UseLazyDeserialization</literal> configuration option in JBoss " +"Cache, which wraps your objects in a <literal>Marshalledvalue</literal> " +"wrapper. The <literal>MarshalledValue</literal> serializes and deserializes " +"your object on demand, ensuring the proper thread local context class loader " +"is used each time." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:757 +#, no-c-format +msgid "" +"Does JBoss Cache currently support pre-event and post-event notification?" +msgstr "JBoss Cache 目前支持 pre-event 和 post-event 通知吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:763 +#, no-c-format +msgid "" +"Yes. A boolean is passed in to each notification callback identifying " +"whether the callback is before or after the event. See the <literal>org." +"jboss.cache.notifications.annotations.CacheListener</literal> annotation for " +"details." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:774 +#, fuzzy, no-c-format +msgid "How do I implement a custom listener to listen to cache events?" +msgstr "我怎样实现自定义的 listener 来侦听 <literal>TreeCache</literal> 事件" + +#. Tag: para +#: TreeCache_FAQ.xml:780 +#, no-c-format +msgid "See the Users' Guide on this subject." +msgstr "" + +#. Tag: para +#: TreeCache_FAQ.xml:788 +#, fuzzy, no-c-format +msgid "" +"Can I use <literal>UseRegionBasedMarshalling</literal> attribute in JBoss " +"Cache in order to get around ClassCastExceptions happening when accessing " +"data in the cache that has just been redeployed?" +msgstr "" +"在访问缓存里被重部署的数据时，我可以使用 JBoss Cache 里的 " +"<literal>useRegionBasedMarshalling</literal> 属性来绕开 ClassCastExceptions " +"吗？" + +#. Tag: para +#: TreeCache_FAQ.xml:797 +#, fuzzy, no-c-format +msgid "" +"Yes, you can. Originally, cache Marshalling was designed as a workaround for " +"those replicated caches that upon state transfer did not have access to the " +"classloaders defining the objects in the cache." +msgstr "" +"可以。<literal>TreeCache</literal> 原来的解码机制的设计目的是作为复制缓存在状" +"态转换不能访问定义对象的类加载器时的绕开办法。" + +#. Tag: para +#: TreeCache_FAQ.xml:802 +#, no-c-format +msgid "" +"On each deployment, JBoss creates a new classloader per the top level " +"deployment artifact, for example an EAR. You also have to bear in mind that " +"a class in an application server is defined not only by the class name but " +"also its classloader. So, assuming that the cache is not deployed as part of " +"your deployment, you could deploy an application and put instances of " +"classes belonging to this deployment inside the cache. If you did a " +"redeployment and try to do a get operation of the data previously put, this " +"would result on a ClassCastException. This is because even though the class " +"names are the same, the class definitions are not. The current classloader " +"is different to the one when the classes were originally put." +msgstr "" +"每次部署时，JBoss 都会为每个顶层部署创建一个新的类加载器，例如为 EAR 文件。你" +"也得记住应用服务器里的类不仅由类名也由自己的类加载器定义。所以，假设缓存没有" +"作为部署的一部分部署，你也可以部署应用程序并把属于这个部署的类的实例放入缓" +"存。如果你进行重部署并试图进行前面所放入的数据的 get 操作，就会导致 " +"ClassCastException 异常。这是因为即使类名相同，类定义也会不同。当前的类加载器" +"和最开始放入类时的不同。" + +#. Tag: para +#: TreeCache_FAQ.xml:817 +#, fuzzy, no-c-format +msgid "" +"By enabling marshalling, you can control the lifecycle of the data in the " +"cache and if on undeployment, you deactivate the region and unregister the " +"classloader that you'd have registered on deployment, you'd evict the data " +"in the cache locally. That means that in the next deployment, the data won't " +"be in the cache, therefore avoiding the problem. Obviously, using " +"marshalling to get around this problem is only recommended when you have " +"some kind of persistence backing where the data survives, for example using " +"CacheLoaders, or when JBoss Cache is used as a second level cache in a " +"persistence framework." +msgstr "" +"通过启用 marshalling，你可以控制缓存中数据的生命周期，在卸载时，你取消激活 " +"region 并取消部署时注册的类加载器，你将在本地剔除缓存里的数据。这意味着在下一" +"次部署时，数据不会在缓存里，因此避开这个问题。很明显，使用 marshalling 来绕开" +"这个问题只适用于你具有某种持久化数据的支持（如使用类加载器），或在持久性框架" +"里把 JBossCache 当作二级缓存的时候。" + +#. Tag: para +#: TreeCache_FAQ.xml:830 +#, fuzzy, no-c-format +msgid "" +"To implement this feature, please follow the instructions indicated in the " +"example located in the CacheMarshaller section of the Users' Guide. It's " +"worth noting that instead of a <literal>ServletContextListener</literal> , " +"you could add this code into an <literal>MBean</literal> that contained " +"lifecycle methods, such as <literal>start()</literal> and <literal>stop()</" +"literal> . The key would be for this MBean to depend on the target cache, so " +"that it can operate as long as the cache is up and running." +msgstr "" +"要实现这个特征，请遵循《用户手册》里 TreeCacheMarshaller 部分的例程中的说明。" +"你可以把 <literal>ServletContextListener</literal> 代码添加到包含生命周期方法" +"（如 <literal>start()</literal> 和 <literal>stop()</literal>）的 " +"<literal>MBean</literal> 里。这个 MBean 的关键是目标缓存，只要缓存启动和运" +"行，它就可以操作。" Added: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Troubleshooting.po =================================================================== --- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Troubleshooting.po (rev 0) +++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_FAQ/zh-CN/Troubleshooting.po 2009-09-14 23:41:10 UTC (rev 8224) @@ -0,0 +1,40 @@ +# Language zh-CN translations for JBoss_EAP package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: JBoss_EAP 4_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-09-14 23:35+0000\n" +"PO-Revision-Date: 2009-01-13 06:01+0000\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 +#: Troubleshooting.xml:6 +#, no-c-format +msgid "Troubleshooting" +msgstr "故障解除" + +#. Tag: para +#: Troubleshooting.xml:11 +#, no-c-format +msgid "" +"I am having problems getting JBoss Cache to work, where can I get " +"information on troubleshooting?" +msgstr "" +"我在使用 JBoss Cache 时遇到了一些问题，我在哪可以获得和故障解除相关的信息？" + +#. Tag: para +#: Troubleshooting.xml:15 +#, fuzzy, no-c-format +msgid "" +"Troubleshooting section can be found in the following <ulink url=\"http://" +"www.jboss.org/community/docs/DOC-10288\">wiki link</ulink>." +msgstr "" +"你可以在下面的 <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?" +"page=JBossCacheTroubleshooting\">wiki link</ulink> 里的 Troubleshooting 部分" +"找到相关信息。"