[jboss-cvs] JBossAS SVN: r78978 - projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Oct 1 02:23:21 EDT 2008
Author: xhuang at jboss.com
Date: 2008-10-01 02:23:21 -0400 (Wed, 01 Oct 2008)
New Revision: 78978
Modified:
projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Architecture.po
projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Book_Info.po
projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Colophon.po
projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Instrumentation.po
projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/JBoss_Cache_Pojo_Cache_Guide.po
projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Term.po
Log:
update
Modified: projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Architecture.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Architecture.po 2008-10-01 06:07:20 UTC (rev 78977)
+++ projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Architecture.po 2008-10-01 06:23:21 UTC (rev 78978)
@@ -9,8 +9,8 @@
"Project-Id-Version: Architecture\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-21 04:57+0000\n"
-"PO-Revision-Date: 2008-09-30 13:56+1000\n"
-"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"PO-Revision-Date: 2008-10-01 09:09+1000\n"
+"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -275,7 +275,7 @@
"feature that we just explained. Notice how a <literal>Person</literal> "
"object (e.g., <literal>joe</literal>) that has complex object references "
"will be mapped into the underlying cache store as explained above."
-msgstr ""
+msgstr "下面是一个对象的可达性映射功能的代码片段。请注意具有复杂对象引用的 <literal>Person</literal> 对象（如 <literal>joe</literal>）是如何映射到底层的缓存库里的。"
#. Tag: programlisting
#: Architecture.xml:95
@@ -696,6 +696,10 @@
"retrieve this proxy reference and use this reference to perform POJO "
"operations."
msgstr ""
+"继承 <literal>Set</literal>、<literal>List</"
+"literal> 和 <literal>Map</literal> 的 POJO 类被自动当作是 \"aspectized\"。也就是说，用户不需要通过注解或在 XML 配置文件里将其声明为 \"prepared\"。既然 instrument Java 系统库是不允许的，我们将使用代理的方法。也就是说，当我们遇到任何集合实例时，我们将：<itemizedlist> <listitem> "
+"<para>创建一个集合代理实例并放入缓存（而不是放入引用）。集合元素的映射仍将递归进行。</para> </listitem> <listitem> "
+"<para>如果集合实例是一个子对象，如位于另外一个 POJO 内部，我们将用新的代理来交换原始的引用，从而促进使用的透明化。</para> </listitem> </itemizedlist>为了获得代理引用，用户可以使用另外一个 <literal>getObject</literal> 来获取代理引用并使用这个引用来执行 POJO 操作。"
#. Tag: para
#: Architecture.xml:160
@@ -770,11 +774,10 @@
#. Tag: para
#: Architecture.xml:168
#, no-c-format
-#, fuzzy
msgid ""
"As you can see, <literal>getLanguages</literal> simply returns the field "
"reference that has been swapped out for the proxy reference counterpart."
-msgstr "如你所看到的，<literal>getLanguages</literal> 只是简单地返回字段引用"
+msgstr "如你所看到的，<literal>getLanguages</literal> 只是简单地返回已经和代理引用交换的字段引用。"
#. Tag: para
#: Architecture.xml:171
@@ -784,7 +787,7 @@
"<literal>removeObject</literal>), you still can use the proxy reference "
"since we will update the in-memory copy of that reference during detachment. "
"Below is a code snippet illustrating this:"
-msgstr ""
+msgstr "最后，当你从缓存删除一个集合引用时（如通过 <literal>removeObject</literal>），既然我们将在脱管期间更新引用的 in-memory 拷贝，你仍可以使用这个代理引用。下面是解释这一点的代码片段："
#. Tag: programlisting
#: Architecture.xml:174
Modified: projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Book_Info.po 2008-10-01 06:07:20 UTC (rev 78977)
+++ projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Book_Info.po 2008-10-01 06:23:21 UTC (rev 78978)
@@ -9,8 +9,8 @@
"Project-Id-Version: Book_Info\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-21 04:57+0000\n"
-"PO-Revision-Date: 2008-09-18 11:11+1000\n"
-"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"PO-Revision-Date: 2008-10-01 08:56+1000\n"
+"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -21,13 +21,13 @@
#: Book_Info.xml:5
#, no-c-format
msgid "JBoss Cache Pojo Cache Guide"
-msgstr ""
+msgstr "JBoss Cache Pojo Cache 指南"
#. Tag: subtitle
#: Book_Info.xml:6
#, no-c-format
msgid "for Use with JBoss Enterprise Application Platform 4.3"
-msgstr ""
+msgstr "针对 JBoss 企业级应用程序平台 4.3"
#. Tag: para
#: Book_Info.xml:12
@@ -41,8 +41,3 @@
msgid "&HOLDER;"
msgstr "&HOLDER;"
-#~ msgid "Pojo Cache 1.4.1"
-#~ msgstr "Pojo Cache 1.4.1"
-
-#~ msgid "User Guide"
-#~ msgstr "用户指南"
Modified: projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Colophon.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Colophon.po 2008-10-01 06:07:20 UTC (rev 78977)
+++ projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Colophon.po 2008-10-01 06:23:21 UTC (rev 78978)
@@ -1,26 +1,28 @@
+# translation of Colophon.po to
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: Colophon\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-21 04:57+0000\n"
-"PO-Revision-Date: 2007-04-17 00:25-0500\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-10-01 09:10+1000\n"
+"Last-Translator: \n"
+"Language-Team: <en at li.org>\n"
"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
#: Colophon.xml:4
#, no-c-format
msgid "Bibliography"
-msgstr ""
+msgstr "参考书目"
#. Tag: title
#: Colophon.xml:5
#, no-c-format
msgid "Authors"
-msgstr ""
+msgstr "作者"
#. Tag: author
#: Colophon.xml:6
@@ -29,6 +31,8 @@
"<honorific>Mr</honorific><firstname>Norman</firstname> <surname>Walsh</"
"surname>"
msgstr ""
+"<honorific>Mr</honorific><firstname>Norman</firstname> <surname>Walsh</"
+"surname>"
#. Tag: affiliation
#: Colophon.xml:9
@@ -38,21 +42,25 @@
"jobtitle><orgname>ArborText, Inc.</orgname><orgdiv>Application Developement</"
"orgdiv>"
msgstr ""
+"<shortaffil>ATI</shortaffil><jobtitle>Senior Application Analyst</"
+"jobtitle><orgname>ArborText, Inc.</orgname><orgdiv>Application Developement</"
+"orgdiv>"
#. Tag: title
#: Colophon.xml:11
#, no-c-format
msgid "Translator"
-msgstr ""
+msgstr "翻译者"
#. Tag: othercredit
#: Colophon.xml:12
#, no-c-format
msgid "<firstname>John</firstname> <surname>Doe</surname>"
-msgstr ""
+msgstr "<firstname>John</firstname> <surname>Doe</surname>"
#. Tag: contrib
#: Colophon.xml:14
#, no-c-format
msgid "Extensive review and rough drafts of Section 1.3, 1.4, and 1.5"
-msgstr ""
+msgstr "1.3、1.4 和 1.5 章节的审核和草稿"
+
Modified: projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Instrumentation.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Instrumentation.po 2008-10-01 06:07:20 UTC (rev 78977)
+++ projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Instrumentation.po 2008-10-01 06:23:21 UTC (rev 78978)
@@ -8,7 +8,7 @@
"Project-Id-Version: Instrumentation\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-21 04:57+0000\n"
-"PO-Revision-Date: 2008-09-26 11:46+1000\n"
+"PO-Revision-Date: 2008-10-01 15:50+1000\n"
"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -20,7 +20,7 @@
#: Instrumentation.xml:5
#, no-c-format
msgid "Instrumentation"
-msgstr ""
+msgstr "Instrumentation"
#. Tag: para
#: Instrumentation.xml:6
@@ -33,7 +33,7 @@
"use JDK5.0 and load-time mode, then all you need to do is annotation your "
"POJO (or declare it in a xml file). This makes your PojoCache programming "
"nearly transparent."
-msgstr ""
+msgstr "在本章里，我们将解释如何通过 JBossAop 来 instrument（或“aspectize”）POJO。JBossAop 需要两个步骤：1) POJO 声明，2) instrumentation。但根据你使用的 JDK 和 instrumentation 模式，你可能根本不需要预处理 POJO。那就是说，如果你使用 JDK5.0 以及 load-time 模式，你所需要做的就是注解 POJO（或在 XML 文件里声明）。这使得 PojoCache 编程几乎是透明的。"
#. Tag: para
#: Instrumentation.xml:9
@@ -42,7 +42,7 @@
"For the first step, since we are using the dynamic Aop feature, a POJO is "
"only required to be declared \"prepare\". Basically, there are two ways to "
"do this: either via explicit xml or annotation (new since release 1.2.3.)"
-msgstr ""
+msgstr "在第一步里，既然我们使用了 Dynamic AOP 功能，POJO 只被要求声明为 \"prepare\"。基本上有两个方法可以实现这一点：通过 XML 或注解（1.2.3 版本后）。"
#. Tag: para
#: Instrumentation.xml:12
@@ -51,13 +51,13 @@
"As for the second step, either we can ask JBossAop to do load-time (through "
"a special class loader, so-called loadtime mode) or compile-time "
"instrumentation (use of an aopc pre-compiler, so-called precompiled mode)"
-msgstr ""
+msgstr "对于第二步，我们可以请求 JBossAop 进行加载时（load-time）（通过特殊的类加载器，亦即所谓的 loadtime 模式）或编译时（compile-time）（使用 aopc 预编译器，即所谓的 precompiled 模式）的 instrumentation。"
#. Tag: title
#: Instrumentation.xml:15
#, no-c-format
msgid "XML descriptor"
-msgstr ""
+msgstr "XML 描述符"
#. Tag: para
#: Instrumentation.xml:16
@@ -76,6 +76,9 @@
"start intercepting either method, field, or constructor invocations using "
"the dynamic Aop."
msgstr ""
+"要通过 XML 配置文件声明 POJO，你的 classpath 里需要 <literal>META-"
+"INF/jboss-aop.xml</literal>。JBossAOP 框架将在启动时读取这个文件来为通知（advice）和介绍（introduction）进行必需的字节码操作。或者你可以用预编译器 <literal>aopc</literal> 预编译它，这样在加载时就不需要 XML 文件了。JBossAop 提供了一种所谓的<literal>切入点（pointcut）</"
+"literal>语言，它由常规表达式组成来指定拦截点（用 AOP 语言来说是<literal>连接点</literal>）。连接点可以是构造函数、方法调用或者字段。你需要声明任何 POJO 为 \"prepared\"，这样 AOP 框架才知道用动态 AOP 启动对方法、字段或构造函数调用的拦截。"
#. Tag: para
#: Instrumentation.xml:19
@@ -86,7 +89,7 @@
"it is the state that we are interested in. So you should only need to change "
"your POJO class name. For details of the pointcut language, please refer to "
"JBossAop."
-msgstr ""
+msgstr "对于 PojoCache 来说，我们只允许拦截所有的字段（读和写）。也就是说，我们不关心方法级别的拦截。所以，你应该只需要修改 POJO 类的名称。关于切入点语言的细节，请参考 JBossAop。"
#. Tag: para
#: Instrumentation.xml:22
@@ -99,6 +102,10 @@
"Appendix section. But here is the snippet for <literal>META-INF/jboss-aop."
"xml</literal> :"
msgstr ""
+"独立的 <literal>JBossCache</literal> 发行包提供了对教程里的类的声明示例，也就是 <literal>Person</"
+"literal> 和 <literal>Address</literal>。附录里将提供 <literal>Person</"
+"literal> 和 <literal>Address</literal> 的详细类声明。这里是 <literal>META-INF/jboss-aop."
+"xml</literal> 的代码片段："
#. Tag: programlisting
#: Instrumentation.xml:25
@@ -126,13 +133,13 @@
"JBossAop. But above statements basically declare all field read and write "
"operations in classes <code>Address</code> and <code>Person</code> will be "
"\"prepared\" (or \"aspectized\"). Note that:"
-msgstr ""
+msgstr "你可以在 JBossAop 文档里找到 <literal>jboss-aop.xml</literal> 的详细解释。但上面的语句把 <code>Address</code> 和 <code>Person</code> 类里所有字段的读写操作都声明成为 \"prepared\" （或 \"aspectized\"）。请注意："
#. Tag: para
#: Instrumentation.xml:31
#, no-c-format
msgid "The wildcard at the end of the expression signifies all fields in the POJO"
-msgstr ""
+msgstr "表达式结尾的通配符表示这个 POJO 里的所有字段"
#. Tag: para
#: Instrumentation.xml:34
@@ -140,7 +147,7 @@
msgid ""
"You can potentially replace specific class name with wildcard that includes "
"all the POJOs inside the same package space"
-msgstr ""
+msgstr "你可以用包括相同包空间里所有 POJO 的通配符来替代特殊的类名。"
#. Tag: para
#: Instrumentation.xml:37
@@ -150,7 +157,7 @@
"the specific POJO will also be \"aspectized\". For example, if a "
"<code>Student</code> class is a subclass of <code>Person</code> , JBossAop "
"will automatically instrument it as well!"
-msgstr ""
+msgstr "<code>instanceof</code> 操作符声明了某个 POJO 的任何子类或子类型也都是切面化的（aspectized）。例如，如果 <code>Student</code> 类是 <code>Person</code> 的子类，那么 JBossAop 也将自动地 instrument 它！"
#. Tag: para
#: Instrumentation.xml:40
@@ -161,6 +168,8 @@
"The main reason being that we consider all fields as stateful data. However, "
"we can relax this requirement in the future if there is a use case for it."
msgstr ""
+"我们拦截所有访问级别（如 <literal>private</"
+"literal>、<literal>protected</literal>、<literal>public</literal> 等）的字段。主要原因是我们把所有字段都当作有状态的数据。然而，将来有需要时我们可以放松这个要求。"
#. Tag: para
#: Instrumentation.xml:43
@@ -172,12 +181,14 @@
"either. If you don't want your field to be managed by the cache, you can "
"declare them with these modifiers, e.g., transient."
msgstr ""
+"但我们不拦截限定符为 <literal>static</literal>、"
+"<literal>final</literal> 和 <literal>transient</literal> 的字段。那就是说，带有这些限定符的字段不会存放在缓存里，也不会被复制。如果你不想某个字段被缓存管理，你可以用这些限定符来声明它，如 transient。"
#. Tag: title
#: Instrumentation.xml:46
#, no-c-format
msgid "Annotation"
-msgstr ""
+msgstr "注解"
#. Tag: para
#: Instrumentation.xml:47
@@ -188,7 +199,7 @@
"since there will be no need for external metadata xml descriptor. In order "
"to support Java 1.4 as well, JBossAop has also used a xdoclet type "
"annotation syntax, and as a result will need an annotation pre-compiler."
-msgstr ""
+msgstr "注解是 Java 5.0 里的一个新特征，它可以在编译以及运行时包含元数据。既然不需要要外部的 XML 描述符，它也可用于 AOP 声明。为了支持 Java 1.4，JBossAop 使用 xdoclet 的 annotation 语法，因此也需要一个注解预编译器。"
#. Tag: para
#: Instrumentation.xml:50
@@ -196,13 +207,13 @@
msgid ""
"Note that PojoCache starts to support the use of annotation since release "
"1.2.3 with Java 1.4, and release 1.3 with Java 5.0."
-msgstr ""
+msgstr "请注意，从基于 Java 1.4 的 1.2.3 版本以及基 Java 5.0 的 1.3 版本开始，PojoCache 开始支持注解的使用。"
#. Tag: title
#: Instrumentation.xml:53
#, no-c-format
msgid "JDK1.4"
-msgstr ""
+msgstr "JDK1.4"
#. Tag: para
#: Instrumentation.xml:54
@@ -214,6 +225,8 @@
"declare a regular POJO, while the latter one is used to declare the POJO and "
"its sub-classes or sub-types."
msgstr ""
+"为了提供最大的透明性，我们已经创建了两个 AOP marker 的接口：<code>@@org.jboss.cache.aop.AopMarker</code> 和 <code>@@org."
+"jboss.cache.aop.InstanceOfAopMarker.</code>。第一个接口用来声明常规的 POJO，而第二个则用来声明 POJO 及其子类和子类型。"
#. Tag: para
#: Instrumentation.xml:57
@@ -234,6 +247,14 @@
" </programlisting> Basically, it simply states that any "
"annotation with both marker interfaces will be \"aspectized\" accordingly."
msgstr ""
+"最后，为了支持注解（简化用户端的开发），JBossCache 在 <literal>resources</literal> 下附带了一个 <literal>jboss-aop.xml</literal>。当你使用注解预编译器时，这个文件需要位于 classpath 里。例如，请参考 <literal>annoc</literal> Ant build 目标。下面是该 <literal>jboss-aop.xml</literal> 的部分内容：<programlisting>\n"
+" <aop>\n"
+" <prepare expr=\"field(* @@org.jboss.cache.aop.AopMarker-"
+">*)\" />\n"
+" <prepare expr=\"field(* $instanceof{@@org.jboss."
+"cache.aop.InstanceOfAopMarker}->*)\" />\n"
+" </aop>\n"
+" </programlisting> 基本上，它简单地声明了使用这两个 Market 接口的任何注解都是切面化的。"
#. Tag: para
#: Instrumentation.xml:62
@@ -241,7 +262,7 @@
msgid ""
"Here is two code snippets that illustrate the declaration of both types "
"through 1.4 style annotation:"
-msgstr ""
+msgstr "下面是解释这两种类型的 Java 1.4 风格注解的代码片段："
#. Tag: programlisting
#: Instrumentation.xml:66
@@ -263,7 +284,7 @@
msgid ""
"The above declaration will instrument the class <literal>Address</literal>, "
"and"
-msgstr ""
+msgstr "上面的声明将 instrument <literal>Address</literal> 类和"
#. Tag: programlisting
#: Instrumentation.xml:70
@@ -274,6 +295,10 @@
" */\n"
" public class Person {...}"
msgstr ""
+"/**\n"
+" * @@org.jboss.cache.aop.InstanceOfAopMarker\n"
+" */\n"
+" public class Person {...}"
#. Tag: para
#: Instrumentation.xml:72
@@ -283,7 +308,7 @@
"and all of its sub-classes. That is, if <literal>Student</literal> sub-class "
"from <literal>Personal</literal>, then it will get instrumented "
"automatically without further annotation declaration."
-msgstr ""
+msgstr "上面的声明将 instrument <literal>Person</literal> 类及其所有子类。这就是说，如果 <literal>Student</literal> 是 <literal>Person</literal> 的子类，那它将自动被 instrument，而无需进行注解声明。"
#. Tag: para
#: Instrumentation.xml:73
@@ -292,13 +317,13 @@
"Note that the simplicity of declaring POJOs through annotation and its "
"marker interfaces (although you will need to use the annotation pre-"
"compiler.) See the build.xml target <code>annoc</code> for example."
-msgstr ""
+msgstr "请注意通过注解声明 POJO 的简洁性及其 Market 接口（虽然你将需要使用注解预编译器）。请以 build.xml 文件里 <code>annoc</code> 目标为例子。"
#. Tag: title
#: Instrumentation.xml:77
#, no-c-format
msgid "JDK5.0"
-msgstr ""
+msgstr "JDK5.0"
#. Tag: para
#: Instrumentation.xml:78
@@ -315,12 +340,17 @@
"Note that we have decided to use different annotation naming convention "
"between JDK1.4 and 5.0."
msgstr ""
+"JDK5.0 注解和 JDK1.4 类似，除了注解名自身的区别，例如<code>@org.jboss.cache.aop.annotation.PojoCacheable</code> 和 <code>@org."
+"jboss.cache.aop.annotation.InstanceOfPojoCacheable.</code>。例如，在使用 JDK5.0 注解时，你将使用<code>@org.jboss.cache.aop.annotation."
+"PojoCacheable</code> 而不是 <code>@@org.jboss.cache.aop."
+"AopMarker</code>。在本发行版本的 <code>examples/"
+"PojoCache/annotated50</code> 目录里，你可以找到使用 JDK5.0 注解的例程。请注意，我们已经决定对于 JDK1.4 和 5.0 使用不同的注解命名规则。"
#. Tag: title
#: Instrumentation.xml:81
#, no-c-format
msgid "JDK5.0 field level annotations"
-msgstr ""
+msgstr "JDK5.0 的字段级注解"
#. Tag: para
#: Instrumentation.xml:82
@@ -332,6 +362,8 @@
"as the Java language <code>transient</code> keyword. That is, PojoCache "
"won't put this field into cache management (and therefore no replication)."
msgstr ""
+"在 1.4 版本里，我们为自定义行为添加了两个额外的字段级注解。第一个是 <code>@org.jboss.cache.aop.annotation."
+"Transient</code>。当应用到字段变量时，它和 Java 的 <code>transient</code> 关键字具有相同的效应。也就是说，PojoCache 不会把这个字段置于缓存的管理之下（因此不会进行复制）。"
#. Tag: para
#: Instrumentation.xml:85
@@ -342,7 +374,7 @@
"<code>Serializable</code>, even when it is <code>PojoCacheable</code>. "
"However, the field will need to implement the <code>Serializable</code> "
"interface such that it can be replicated."
-msgstr ""
+msgstr "第二个是 <code>@org.jboss.cache.aop.annotation.Serializable</code>，当应用到字段变量时，PojoCache 将把这个字段当作<code>可序列化的</code>、甚至是 <code>PojoCacheable</code>。然而，这个字段需要实现 <code>Serializable</code> 接口才能被复制。"
#. Tag: para
#: Instrumentation.xml:88
@@ -361,6 +393,17 @@
"}\n"
"</programlisting> Then when we do:"
msgstr ""
+"下面的代码片段解释了这两种注解的用法。假设你有一个 Gadget 类：<programlisting>\n"
+"public class Gadget\n"
+"{\n"
+" // resource won't be replicated\n"
+" @Transient Resource resource;\n"
+" // specialAddress is treated as a Serializable object but still has "
+"object relationship\n"
+" @Serializable SpecialAddress specialAddress;\n"
+" // other state variables\n"
+"}\n"
+"</programlisting> 当我们："
#. Tag: programlisting
#: Instrumentation.xml:90
@@ -414,7 +457,7 @@
#: Instrumentation.xml:92
#, no-c-format
msgid "Weaving"
-msgstr ""
+msgstr "Weaving"
#. Tag: para
#: Instrumentation.xml:93
@@ -426,6 +469,8 @@
"<literal>jboss-aop.xml</literal> and weave the POJO byte code at compile "
"time. This is a convenient feature to make the aop less intrusive."
msgstr ""
+"如前面所提到的，用户可以使用 AOP 预编译器（<literal>aopc</"
+"literal>）来预编译 POJO 类，因此在运行时不需要额外的系统类加载器。预编译器将读取 <literal>jboss-aop.xml</literal> 并在编译时编排 POJO 字节码。这是一个使 AOP 具有更低侵入性的功能。"
#. Tag: para
#: Instrumentation.xml:96
@@ -435,6 +480,8 @@
"targets that we are listing here. User can refer to the <literal>build.xml</"
"literal> in the distribution for full details."
msgstr ""
+"下面是一段 Ant 脚本，它定义了这里列出的不同 Ant 目标所需的库。用户可以参考 <literal>build.xml</"
+"literal> 来获得全部的细节。"
#. Tag: programlisting
#: Instrumentation.xml:97
@@ -464,7 +511,7 @@
msgid ""
"Ant target for running load-time instrumentation using specialized class "
"loader"
-msgstr ""
+msgstr "用专门的加载器运行加载时 instrumentation 的 Ant 目标"
#. Tag: para
#: Instrumentation.xml:100
@@ -477,7 +524,7 @@
"Note that since JBossAop 1.3, a new "
"<literal>GenerateInstrumentedClassLoader</literal> has been used since the "
"previous <literal>SystemClassLoader</literal> is error prone."
-msgstr ""
+msgstr "下面是通过特殊的类加载器进行加载时 instrumentation 的 Ant 目标。Ant 目标 <literal>one.test.aop</literal> 使用 <literal>generateClassLoader</literal> 目标生成的 bootclass 加载器来进行独立的测试。请注意由于以前的 <literal>SystemClassLoader</literal> 很容易出错，从 JBossAop 1.3 开始，我们已经使用了新的 <literal>GenerateInstrumentedClassLoader</literal>。"
#. Tag: programlisting
#: Instrumentation.xml:103
@@ -572,7 +619,7 @@
"If you are running JDK5.0, you can also use the <code>javaagent</code> "
"option that does not require a separate Classloader. Here are the ant "
"snippet from <code>one-test-aop50</code>, for example."
-msgstr ""
+msgstr "如果你使用的是 JDK5.0，你也可以使用不要求单独类加载器的 <code>javaagent</code> 选项。下面是 <code>one-test-aop50</code> 里的 Ant 脚本片段。"
#. Tag: programlisting
#: Instrumentation.xml:105
@@ -618,7 +665,7 @@
#: Instrumentation.xml:107
#, no-c-format
msgid "Ant target for aopc"
-msgstr ""
+msgstr "使用 aopc 的 Ant 目标"
#. Tag: para
#: Instrumentation.xml:108
@@ -627,7 +674,7 @@
"Below is the code snippet for the <literal>aopc</literal> Ant target. "
"Running this target will do compile-time weaving of the POJO classes "
"specified."
-msgstr ""
+msgstr "下面是 <literal>aopc</literal> Ant 目标的代码片段。运行这个目标将编排指定的 POJO 类。"
#. Tag: programlisting
#: Instrumentation.xml:111
@@ -667,18 +714,20 @@
"that couple extra classes have been generated because of <literal>aopc</"
"literal>."
msgstr ""
+"下面是应用 aopc 时生成的文件快照。请注意因为 <literal>aopc</"
+"literal> 生成的额外的几个类。"
#. Tag: title
#: Instrumentation.xml:116
#, no-c-format
msgid "Classes generated after aopc"
-msgstr ""
+msgstr "在 aopc 之后生成的类"
#. Tag: title
#: Instrumentation.xml:123
#, no-c-format
msgid "Ant target for annotation compiler"
-msgstr ""
+msgstr "注解编译器使用的 Ant 目标"
#. Tag: para
#: Instrumentation.xml:124
@@ -688,7 +737,7 @@
"run this step if you are using the JDK1.4 annotation. After this step is "
"successfully run, you decide either to use compile-time or load-time mode of "
"weaving."
-msgstr ""
+msgstr "下面是 <literal>annoc</literal> Ant 目标的代码片段。如果使用 JDK1.4 注解，你会执行到这一步。在成功执行这一步后，你可以决定使用编译时还是加载时模式进行编排。"
#. Tag: programlisting
#: Instrumentation.xml:127
Modified: projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/JBoss_Cache_Pojo_Cache_Guide.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/JBoss_Cache_Pojo_Cache_Guide.po 2008-10-01 06:07:20 UTC (rev 78977)
+++ projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/JBoss_Cache_Pojo_Cache_Guide.po 2008-10-01 06:23:21 UTC (rev 78978)
@@ -7,7 +7,7 @@
"Project-Id-Version: JBoss_Cache_Pojo_Cache_Guide\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-21 04:57+0000\n"
-"PO-Revision-Date: 2008-09-29 13:14+1000\n"
+"PO-Revision-Date: 2008-10-01 16:22+1000\n"
"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -58,7 +58,7 @@
"site</ulink> . If you are interested in the development of PojoCache, post a "
"message on the forum. If you are interested in translating this "
"documentation into your language, contact us on the developer mailing list."
-msgstr ""
+msgstr "如果你有任何问题，请访问 <ulink url=\"http://labs.jboss.com/jbosscache\">JBoss Cache 网站</ulink>上的<ulink url=\"http://www.jboss.com/index.html?module=bb&op=viewforum&f=157\">用户论坛</ulink>。我们也在 <ulink url=\"http://jira.jboss.com\">JBoss JIRA issue tracker </ulink> 里提供一种跟踪程序错误和请求新功能的机制。如果你对开发 JBoss Cache 或翻译本文档感兴趣，你可以在用户论坛上发布消息或联系 <ulink url=\"http://lists.jboss.org\">developer mailing list </ulink>。"
#. Tag: para
#: JBoss_Cache_Pojo_Cache_Guide.xml:16
@@ -70,6 +70,8 @@
"ulink> ). JBoss Cache is a project of the JBoss Professional Open Source "
"product suite."
msgstr ""
+"JBossCache 是一个基于 LGPL 的开源产品。JBoss Inc（ <ulink url=\"http://www.jboss.com\">JBoss 网站</"
+"ulink>）提供商业开发支持、产品支持和培训。JBoss Cache 是 JBoss 专业级开源产品套件里的一个项目。"
#. Tag: para
#: JBoss_Cache_Pojo_Cache_Guide.xml:19
Modified: projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Term.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Term.po 2008-10-01 06:07:20 UTC (rev 78977)
+++ projects/docs/enterprise/4.3/Cache/Cache_Pojo_Cache_Guide/zh-CN/Term.po 2008-10-01 06:23:21 UTC (rev 78978)
@@ -1,30 +1,32 @@
+# translation of Term.po to
# Language /tmp/mike/JBEAP420/Cache translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
+# Copyright (C) 2007, 2008 Free Software Foundation, Inc.
# Automatically generated, 2007.
#
msgid ""
msgstr ""
-"Project-Id-Version: JBEAP 420\n"
+"Project-Id-Version: Term\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-21 04:57+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-10-01 16:18+1000\n"
+"Last-Translator: \n"
+"Language-Team: <en at li.org>\n"
"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
#: Term.xml:5
#, no-c-format
msgid "Terminology"
-msgstr ""
+msgstr "术语"
#. Tag: title
#: Term.xml:6
#, no-c-format
msgid "Overview"
-msgstr ""
+msgstr "概述"
#. Tag: para
#: Term.xml:7
@@ -32,13 +34,13 @@
msgid ""
"The section lists some basic terminology that will be used throughout this "
"guide."
-msgstr ""
+msgstr "本节列出本指南使用的一些基本术语。"
#. Tag: term
#: Term.xml:13
#, no-c-format
msgid "<term>Aop</term>"
-msgstr ""
+msgstr "<term>Aop</term>"
#. Tag: para
#: Term.xml:15
@@ -51,12 +53,16 @@
"layered design. AOP allows you to intercept any event in a Java program and "
"trigger functionality based on those events."
msgstr ""
+"面向切面编程（Aspect-Oriented Programming，AOP）是一个新的模型，它允许你"
+"用传统面向对象方法不可能实现的方法组织应用程序和进行分层。切面（Aspect）允许你透"
+"明地把功能粘合在一起，从而实现更加层次化的设计。AOP 允许你在 Java 程序里拦截任何"
+"事件并触发基于这些事件的功能。"
#. Tag: term
#: Term.xml:21
#, no-c-format
msgid "JBossAop"
-msgstr ""
+msgstr "JBossAop"
#. Tag: para
#: Term.xml:23
@@ -65,13 +71,13 @@
"JBossAop is an open-source Aop framework library developed by JBoss. It is "
"100% Java based and can be run either as a standalone or inside an "
"application server environment. More details can be found at www.jboss.com."
-msgstr ""
+msgstr "JBossAop 是 JBoss 开发的开源 AOP 框架库。它是 100% 的 Java 程序，它既可以独立运行也可以运行在应用服务器内部。更多细节请访问 www.jboss.com。"
#. Tag: term
#: Term.xml:29
#, no-c-format
msgid "Dynamic Aop"
-msgstr ""
+msgstr "Dynamic Aop"
#. Tag: para
#: Term.xml:31
@@ -80,13 +86,13 @@
"Dynamic Aop is a feature of JBossAop that provides a hook so that a caller "
"can insert event interception on the POJO at runtime. PojoCache currently "
"uses this feature to perform field level interception."
-msgstr ""
+msgstr "Dynamic Aop 是 JBossAop 的一个功能，它提供了让调用者可以在运行时对 POJO 插入事件拦截的钩子（Hook）。PojoCache 目前使用这个功能来执行字段级的拦截。"
#. Tag: term
#: Term.xml:37
#, no-c-format
msgid "JGroups"
-msgstr ""
+msgstr "JGroups"
#. Tag: para
#: Term.xml:39
@@ -97,13 +103,13 @@
"membership management. It has been a de facto replication layer used by "
"numerous open-source projects for clustering purposes. It is also used by "
"JBossCache for replication layer."
-msgstr ""
+msgstr "JGroups 是一个可靠的 Java 组消息库，它是开源的且基于 LGPL。除了可靠的消息传输之外，它也执行组成员管理。它已经成为大量开源项目用于群集的复制层。JBossCache 也把它作为复制层使用。"
#. Tag: term
#: Term.xml:45
#, no-c-format
msgid "TreeCache"
-msgstr ""
+msgstr "TreeCache"
#. Tag: para
#: Term.xml:47
@@ -115,24 +121,26 @@
"memory, replicated, and persistent. PojoCache currently is a sub-class of "
"TreeCache."
msgstr ""
+"TreeCache 是 JBossCache 的一个组件，它是一个普通缓存系统。这就是说，它直接存储 Java 对象的引用，并要求对象为可序列化的以执行二进制复制。它是基于 Java 的、in-"
+"memory、复制性和持久性的缓存。PojoCache 目前是 TreeCache 的子类。"
#. Tag: term
#: Term.xml:53
#, no-c-format
msgid "POJO"
-msgstr ""
+msgstr "POJO"
#. Tag: para
#: Term.xml:55
#, no-c-format
msgid "Plain old Java object."
-msgstr ""
+msgstr "Plain old Java object。"
#. Tag: term
#: Term.xml:61
#, no-c-format
msgid "Annotation"
-msgstr ""
+msgstr "注解"
#. Tag: para
#: Term.xml:63
@@ -141,13 +149,13 @@
"Annotation is a new feature in JDK5.0. It introduces metadata along side the "
"Java code that can be accessed at runtime. PojoCache currently use both "
"JDK1.4 and JDK50 annotation to support POJO instrumentation."
-msgstr ""
+msgstr "注解是 Java 5.0 里的一个新特征，它可以在编译以及运行时包含元数据。为了支持 POJO instrumentation，PojoCache 既使用 JDK1.4 也使用 JDK50 注解。"
#. Tag: term
#: Term.xml:69
#, no-c-format
msgid "Prepare"
-msgstr ""
+msgstr "Prepare"
#. Tag: para
#: Term.xml:71
@@ -160,12 +168,14 @@
"listing. Note that When a POJO is declared properly either through the xml "
"or annotation, we consider it \"aspectized\"."
msgstr ""
+"Prepare 是 JBossAop 切入点（pointcut）语言里的一个关键字，它用于指定需要 instrument 的 POJO。它出现在 <literal>jboss-aop.xml</"
+"literal> 文件里。然而，如果你使用注解来指定 POJO instrumentation，那就不需要 <literal>jboss-aop.xml</literal> 列表。请注意，当使用 XML 或注解正确地声明 POJO 时，我们就认为它是切面化的（aspectized）。"
#. Tag: term
#: Term.xml:77
#, no-c-format
msgid "Instrumentation"
-msgstr ""
+msgstr "Instrumentation"
#. Tag: para
#: Term.xml:79
@@ -177,4 +187,5 @@
"(<literal>aopc</literal>) while load-time is done to specify a special "
"classloader in the run script. This step is necessary for an Aop system to "
"intercept events that are interesting to users."
-msgstr ""
+msgstr "Instrumentation 是一个 AOP 过程，它预处理（如执行字节码编排）POJO。它有两种模式：编译时（compile-time）和加载时（load-time）。编译时编排可以用 Aop 预编译器（<literal>aopc</literal>）完成，而加载时编排通过在 run 脚本里指定特殊的类加载器来实现。为了让 AOP 系统拦截用户感兴趣的事件，这个步骤是必需的。"
+
More information about the jboss-cvs-commits
mailing list