[jboss-cvs] JBossAS SVN: r100233 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Feb 2 00:00:14 EST 2010
Author: xhuang at jboss.com
Date: 2010-02-02 00:00:14 -0500 (Tue, 02 Feb 2010)
New Revision: 100233
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Book_Info.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po
Log:
update
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Book_Info.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Book_Info.po 2010-02-02 04:58:05 UTC (rev 100232)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Book_Info.po 2010-02-02 05:00:14 UTC (rev 100233)
@@ -8,8 +8,8 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-12-09T13:49:17\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-02-02 14:59+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,18 +17,17 @@
"X-Generator: KBabel 1.11.4\n"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Administration And Configuration Guide"
-msgstr "群集配置"
+msgstr "管理和配置指南"
#. Tag: subtitle
-#, fuzzy, no-c-format
+#, no-c-format
msgid "for JBoss Enterprise Application Platform 5.0"
-msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
+msgstr "用于 JBoss 企业级应用程序平台 5.0"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"This book is a guide to the administration and configuration of JBoss "
-"Enterprise Application Platform 5.0."
-msgstr "本书是配置用于 JBoss 企业级应用程序平台的 JBoss 应用服务器的指南。"
+#, no-c-format
+msgid "This book is a guide to the administration and configuration of JBoss Enterprise Application Platform 5.0."
+msgstr "本书是配置用于 JBoss 企业级应用程序平台 5.0 的管理和配置指南。"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po 2010-02-02 04:58:05 UTC (rev 100232)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po 2010-02-02 05:00:14 UTC (rev 100233)
@@ -8,8 +8,8 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-12-09T13:49:17\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-02-02 14:59+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -23,13 +23,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"In a JBoss Enterprise Application Platform cluster, entity bean instance "
-"caches need to be kept in sync across all nodes. If an entity bean provides "
-"remote services, the service methods need to be load balanced as well."
-msgstr ""
-"在 JBoss AS 群集系统里，entity bean 实例需要在所有节点间保持同步。如果某个 "
-"entity bean 提供了远程服务，那么该服务的方法也需要进行负载平衡。"
+msgid "In a JBoss Enterprise Application Platform cluster, entity bean instance caches need to be kept in sync across all nodes. If an entity bean provides remote services, the service methods need to be load balanced as well."
+msgstr "在 JBoss AS 群集系统里，entity bean 实例需要在所有节点间保持同步。如果某个 entity bean 提供了远程服务，那么该服务的方法也需要进行负载平衡。"
#. Tag: title
#, no-c-format
@@ -38,15 +33,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"In EJB 3.0, entity beans primarily serve as a persistence data model. They "
-"do not provide remote services. Hence, the entity bean clustering service in "
-"EJB 3.0 primarily deals with distributed caching and replication, instead of "
-"load balancing."
-msgstr ""
-"在 EJB 3.0 里，entity beans 主要以持久化数据模型出现。它们不提供远程服务。因"
-"此，EJB 3.0 里的 entity bean 群集服务主要处理分布式缓存和复制，而不是负载平"
-"衡。"
+msgid "In EJB 3.0, entity beans primarily serve as a persistence data model. They do not provide remote services. Hence, the entity bean clustering service in EJB 3.0 primarily deals with distributed caching and replication, instead of load balancing."
+msgstr "在 EJB 3.0 里，entity beans 主要以持久化数据模型出现。它们不提供远程服务。因此，EJB 3.0 里的 entity bean 群集服务主要处理分布式缓存和复制，而不是负载平衡。"
#. Tag: title
#, no-c-format
@@ -55,70 +43,37 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"To avoid round trips to the database, you can use a cache for your entities. "
-"JBoss EJB 3.0 entity beans are implemented by Hibernate, which has support "
-"for a second-level cache. The second-level cache provides the following "
-"functionalities:"
-msgstr ""
-"为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 "
-"Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 "
-"JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能："
+msgid "To avoid round trips to the database, you can use a cache for your entities. JBoss EJB 3.0 entity beans are implemented by Hibernate, which has support for a second-level cache. The second-level cache provides the following functionalities:"
+msgstr "为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能："
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"If you persist a cache-enabled entity bean instance to the database via the "
-"entity manager, the entity will be inserted into the cache."
-msgstr ""
-"如果你通过 entity manager 来使应用缓存的 entity bean 的实例持久化，这个 "
-"entity 会被储存到缓存里。"
+msgid "If you persist a cache-enabled entity bean instance to the database via the entity manager, the entity will be inserted into the cache."
+msgstr "如果你通过 entity manager 来使应用缓存的 entity bean 的实例持久化，这个 entity 会被储存到缓存里。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"If you update an entity bean instance, and save the changes to the database "
-"via the entity manager, the entity will be updated in the cache."
-msgstr ""
-"如果你通过 entity manager 更新 entity bean 实例并把更改保存到数据库里，缓存里"
-"的这个 entity 将被更新。"
+msgid "If you update an entity bean instance, and save the changes to the database via the entity manager, the entity will be updated in the cache."
+msgstr "如果你通过 entity manager 更新 entity bean 实例并把更改保存到数据库里，缓存里的这个 entity 将被更新。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"If you remove an entity bean instance from the database via the entity "
-"manager, the entity will be removed from the cache."
-msgstr ""
-"如果你通过 entity manager 把 entity bean 实例从数据库里删除，这个 entity 也将"
-"从缓存里删除。"
+msgid "If you remove an entity bean instance from the database via the entity manager, the entity will be removed from the cache."
+msgstr "如果你通过 entity manager 把 entity bean 实例从数据库里删除，这个 entity 也将从缓存里删除。"
#. Tag: para
#, no-c-format
-msgid ""
-"If loading a cached entity from the database via the entity manager, and "
-"that entity does not exist in the database, it will be inserted into the "
-"cache."
-msgstr ""
-"如果你通过 entity manager 从数据库里载入缓存的 entity，而这个这个 entity 并不"
-"在缓存里，这个 entity 会被插入到缓存里。"
+msgid "If loading a cached entity from the database via the entity manager, and that entity does not exist in the database, it will be inserted into the cache."
+msgstr "如果你通过 entity manager 从数据库里载入缓存的 entity，而这个这个 entity 并不在缓存里，这个 entity 会被插入到缓存里。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"As well as a region for caching entities, the second-level cache also "
-"contains regions for caching collections, queries, and timestamps. The "
-"Hibernate setup used for the JBoss EJB 3.0 implementation uses JBoss Cache "
-"as its underlying second-level cache implementation."
-msgstr ""
-"为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 "
-"Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 "
-"JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能："
+msgid "As well as a region for caching entities, the second-level cache also contains regions for caching collections, queries, and timestamps. The Hibernate setup used for the JBoss EJB 3.0 implementation uses JBoss Cache as its underlying second-level cache implementation."
+msgstr "为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能："
#. Tag: para
#, no-c-format
-msgid ""
-"Configuration of a the second-level cache is done via your EJB3 deployment's "
-"<filename>persistence.xml</filename>."
+msgid "Configuration of a the second-level cache is done via your EJB3 deployment's <filename>persistence.xml</filename>."
msgstr ""
#. Tag: para
@@ -139,8 +94,7 @@
#. Tag: term
#, fuzzy, no-c-format
msgid "hibernate.cache.use_query_cache"
-msgstr ""
-"<property name=\"hibernate.cache.use_query_cache\" value=\"true\"/>"
+msgstr "<property name=\"hibernate.cache.use_query_cache\" value=\"true\"/>"
#. Tag: para
#, no-c-format
@@ -154,17 +108,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Defines the <literal>RegionFactory</literal> implementation that dictates "
-"region-specific caching behavior. Hibernate ships with 2 types of JBoss "
-"Cache-based second-level caches: shared and multiplexed."
+msgid "Defines the <literal>RegionFactory</literal> implementation that dictates region-specific caching behavior. Hibernate ships with 2 types of JBoss Cache-based second-level caches: shared and multiplexed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"A shared region factory uses the same Cache for all cache regions - much "
-"like the legacy CacheProvider implementation in older Hibernate versions."
+msgid "A shared region factory uses the same Cache for all cache regions - much like the legacy CacheProvider implementation in older Hibernate versions."
msgstr ""
#. Tag: para
@@ -179,9 +128,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Uses a single JBoss Cache configuration, from a newly instantiated "
-"CacheManager, for all cache regions."
+msgid "Uses a single JBoss Cache configuration, from a newly instantiated CacheManager, for all cache regions."
msgstr ""
#. Tag: title
@@ -190,14 +137,14 @@
msgstr ""
#. Tag: entry
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Property"
-msgstr "端口"
+msgstr "属性"
#. Tag: entry
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Default"
-msgstr "Defaults"
+msgstr "缺省"
#. Tag: entry
#, no-c-format
@@ -210,15 +157,13 @@
msgstr ""
#. Tag: entry
-#, fuzzy, no-c-format
+#, no-c-format
msgid "treecache.xml"
-msgstr "oracle-ds.xml"
+msgstr "treecache.xml"
#. Tag: entry
#, no-c-format
-msgid ""
-"The classpath or filesystem resource containing the JBoss Cache "
-"configuration settings."
+msgid "The classpath or filesystem resource containing the JBoss Cache configuration settings."
msgstr ""
#. Tag: entry
@@ -233,9 +178,7 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The classpath or filesystem resource containing the JGroups protocol stack "
-"configurations."
+msgid "The classpath or filesystem resource containing the JGroups protocol stack configurations."
msgstr ""
#. Tag: term
@@ -245,9 +188,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Uses a single JBoss Cache configuration, from an existing CacheManager bound "
-"to JNDI, for all cache regions."
+msgid "Uses a single JBoss Cache configuration, from an existing CacheManager bound to JNDI, for all cache regions."
msgstr ""
#. Tag: title
@@ -256,21 +197,18 @@
msgstr ""
#. Tag: entry
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<emphasis>Required</emphasis>"
-msgstr "<emphasis>FD</emphasis>"
+msgstr "<emphasis>必需属性</emphasis>"
#. Tag: entry
#, no-c-format
-msgid ""
-"JNDI name to which the shared <literal>Cache</literal> instance is bound."
+msgid "JNDI name to which the shared <literal>Cache</literal> instance is bound."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"A multiplexed region factory uses separate Cache instances, using optimized "
-"configurations for each cache region."
+msgid "A multiplexed region factory uses separate Cache instances, using optimized configurations for each cache region."
msgstr ""
#. Tag: title
@@ -290,10 +228,7 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The JBoss Cache configuration used for the entity cache region. Alternative "
-"configurations: mvcc-entity, pessimistic-entity, mvcc-entity-repeatable, "
-"optimistic-entity-repeatable, pessimistic-entity-repeatable"
+msgid "The JBoss Cache configuration used for the entity cache region. Alternative configurations: mvcc-entity, pessimistic-entity, mvcc-entity-repeatable, optimistic-entity-repeatable, pessimistic-entity-repeatable"
msgstr ""
#. Tag: entry
@@ -303,10 +238,7 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The JBoss Cache configuration used for the collection cache region. The "
-"collection cache region typically uses the same configuration as the entity "
-"cache region."
+msgid "The JBoss Cache configuration used for the collection cache region. The collection cache region typically uses the same configuration as the entity cache region."
msgstr ""
#. Tag: entry
@@ -321,10 +253,7 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The JBoss Cache configuration used for the query cache region. By default, "
-"cached query results are not replicated. Alternative configurations: "
-"replicated-query"
+msgid "The JBoss Cache configuration used for the query cache region. By default, cached query results are not replicated. Alternative configurations: replicated-query"
msgstr ""
#. Tag: entry
@@ -339,11 +268,7 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The JBoss Cache configuration used for the timestamp cache region. If query "
-"caching is used, the corresponding timestamp cache must be replicating, even "
-"if the query cache is non-replicating. The timestamp cache region must never "
-"share the same cache as the query cache."
+msgid "The JBoss Cache configuration used for the timestamp cache region. If query caching is used, the corresponding timestamp cache must be replicating, even if the query cache is non-replicating. The timestamp cache region must never share the same cache as the query cache."
msgstr ""
#. Tag: term
@@ -353,9 +278,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Uses separate JBoss Cache configurations, from a newly instantiated "
-"CacheManager, per cache region."
+msgid "Uses separate JBoss Cache configurations, from a newly instantiated CacheManager, per cache region."
msgstr ""
#. Tag: title
@@ -380,10 +303,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Uses separate JBoss Cache configurations, from a JNDI-bound CacheManager, "
-"see <xref linkend=\"clustering-blocks-jbc-cachemanager\" />, per cache "
-"region."
+msgid "Uses separate JBoss Cache configurations, from a JNDI-bound CacheManager, see <xref linkend=\"clustering-blocks-jbc-cachemanager\" />, per cache region."
msgstr ""
#. Tag: title
@@ -398,19 +318,13 @@
#. Tag: entry
#, fuzzy, no-c-format
-msgid ""
-"JNDI name to which the <literal>CacheManager</literal> instance is bound."
+msgid "JNDI name to which the <literal>CacheManager</literal> instance is bound."
msgstr "<literal>Scheduler</literal> 将设置为 null 的任何权限定类名。"
#. Tag: para
#, no-c-format
-msgid ""
-"Now, we have JBoss Cache configured to support distributed caching of EJB "
-"3.0 entity beans. We still have to configure individual entity beans to use "
-"the cache service."
-msgstr ""
-"现在，我们配置了 JBoss Cache 来支持 EJB 3.0 entity beans 的分布式缓存。我们仍"
-"不得不配置单个的 entity bean 来使用这个缓存服务。"
+msgid "Now, we have JBoss Cache configured to support distributed caching of EJB 3.0 entity beans. We still have to configure individual entity beans to use the cache service."
+msgstr "现在，我们配置了 JBoss Cache 来支持 EJB 3.0 entity beans 的分布式缓存。我们仍不得不配置单个的 entity bean 来使用这个缓存服务。"
#. Tag: title
#, no-c-format
@@ -419,53 +333,18 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Next we need to configure which entities to cache. The default is to not "
-"cache anything, even with the settings shown above. We use the <literal>@org."
-"hibernate.annotations.Cache</literal> annotation to tag entity beans that "
-"needs to be cached."
-msgstr ""
-"下一步我们需要配置哪些实体被缓存。就像上面所展示的样，缺省是什么都不缓存。我"
-"们使用 <literal>@org.hibernate.annotations.Cache</literal> 注解来标记需要缓存"
-"的 entity bean。"
+msgid "Next we need to configure which entities to cache. The default is to not cache anything, even with the settings shown above. We use the <literal>@org.hibernate.annotations.Cache</literal> annotation to tag entity beans that needs to be cached."
+msgstr "下一步我们需要配置哪些实体被缓存。就像上面所展示的样，缺省是什么都不缓存。我们使用 <literal>@org.hibernate.annotations.Cache</literal> 注解来标记需要缓存的 entity bean。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"A very simplified rule of thumb is that you will typically want to do "
-"caching for objects that rarely change, and which are frequently read. You "
-"can fine tune the cache for each entity bean in the appropriate JBoss Cache "
-"configuration file, e.g. jboss-cache-manager-jboss-beans.xml. For instance, "
-"you can specify the size of the cache. If there are too many objects in the "
-"cache, the cache can evict the oldest or least used objects, depending on "
-"configuration, to make room for new objects. Assuming the region_prefix "
-"specified in <literal>persistence.xml</literal> was <literal>myprefix</"
-"literal>, the default name of the cache region for the <literal>com."
-"mycompany.entities.Account</literal> entity bean would be <literal>/myprefix/"
-"com/mycompany/entities/Account</literal>."
-msgstr ""
-"一个简单的原则就是，你应该对很少变动和频繁使用的对象进行缓存.你可以在 "
-"<literal>ejb3-entity-cache-service.xml</literal> 配置文件里为每个 entity "
-"bean 微调缓存设置。例如，你可以指定缓存的大小。如果缓存里的对象太多，缓存有可"
-"能挤掉最老的对象（或者最少用的对象，依你的配置而定）来给新对象留出空间。假设 "
-"<literal>persistence.xml</literal> 里指定的 region_prefix 是 myprefix，"
-"entity bean 的<literal>com.mycompany.entities.Account</literal> 缺省的缓存 "
-"region 是 <literal>/myprefix/com/mycompany/entities/Account</literal>。"
+msgid "A very simplified rule of thumb is that you will typically want to do caching for objects that rarely change, and which are frequently read. You can fine tune the cache for each entity bean in the appropriate JBoss Cache configuration file, e.g. jboss-cache-manager-jboss-beans.xml. For instance, you can specify the size of the cache. If there are too many objects in the cache, the cache can evict the oldest or least used objects, depending on configuration, to make room for new objects. Assuming the region_prefix specified in <literal>persistence.xml</literal> was <literal>myprefix</literal>, the default name of the cache region for the <literal>com.mycompany.entities.Account</literal> entity bean would be <literal>/myprefix/com/mycompany/entities/Account</literal>."
+msgstr "一个简单的原则就是，你应该对很少变动和频繁使用的对象进行缓存.你可以在 <literal>ejb3-entity-cache-service.xml</literal> 配置文件里为每个 entity bean 微调缓存设置。例如，你可以指定缓存的大小。如果缓存里的对象太多，缓存有可能挤掉最老的对象（或者最少用的对象，依你的配置而定）来给新对象留出空间。假设 <literal>persistence.xml</literal> 里指定的 region_prefix 是 myprefix，entity bean 的<literal>com.mycompany.entities.Account</literal> 缺省的缓存 region 是 <literal>/myprefix/com/mycompany/entities/Account</literal>。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"If you do not specify a cache region for an entity bean class, all instances "
-"of this class will be cached using the <literal>defaultEvictionRegionConfig</"
-"literal> as defined above. The @Cache annotation exposes an optional "
-"attribute “region” that lets you specify the cache region where an entity is "
-"to be stored, rather than having it be automatically be created from the "
-"fully-qualified class name of the entity class."
-msgstr ""
-"如果你没有为 entity bean 类指定缓存区（cache region），这个类的所有实例将象上"
-"面定义的一样缓存在 <literal>/_default</literal> 区里。@Cache 注解开放一个可选"
-"的属性“region”，它让你指定实体所存储的缓存区，而不是根据实体类的全限定名自动"
-"创建。"
+msgid "If you do not specify a cache region for an entity bean class, all instances of this class will be cached using the <literal>defaultEvictionRegionConfig</literal> as defined above. The @Cache annotation exposes an optional attribute “region” that lets you specify the cache region where an entity is to be stored, rather than having it be automatically be created from the fully-qualified class name of the entity class."
+msgstr "如果你没有为 entity bean 类指定缓存区（cache region），这个类的所有实例将象上面定义的一样缓存在 <literal>/_default</literal> 区里。@Cache 注解开放一个可选的属性“region”，它让你指定实体所存储的缓存区，而不是根据实体类的全限定名自动创建。"
#. Tag: para
#, no-c-format
@@ -479,68 +358,33 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The EJB3 Query API also provides means for you to save the results (i.e., "
-"collections of primary keys of entity beans, or collections of scalar "
-"values) of specified queries in the second-level cache. Here we show a "
-"simple example of annotating a bean with a named query, also providing the "
-"Hibernate-specific hints that tells Hibernate to cache the query."
-msgstr ""
-"EJB3 Query API 也为你提供了把查询结果（如 entity bean 的主键集合或标量结果的"
-"集合）保存在二级缓存里的方法。在这里我们演示了一个简单的例子，它注解了带有命"
-"名查询的 bean，且提供 Hibernate 专有的指令来让 Hibernate 缓存这个查询。"
+msgid "The EJB3 Query API also provides means for you to save the results (i.e., collections of primary keys of entity beans, or collections of scalar values) of specified queries in the second-level cache. Here we show a simple example of annotating a bean with a named query, also providing the Hibernate-specific hints that tells Hibernate to cache the query."
+msgstr "EJB3 Query API 也为你提供了把查询结果（如 entity bean 的主键集合或标量结果的集合）保存在二级缓存里的方法。在这里我们演示了一个简单的例子，它注解了带有命名查询的 bean，且提供 Hibernate 专有的指令来让 Hibernate 缓存这个查询。"
#. Tag: para
#, no-c-format
-msgid ""
-"First, in persistence.xml you need to tell Hibernate to enable query caching:"
+msgid "First, in persistence.xml you need to tell Hibernate to enable query caching:"
msgstr "首先，在 persistence.xml 里，你需要告诉 Hibernate 启用查询缓存："
#. Tag: para
#, no-c-format
-msgid ""
-"Next, you create a named query associated with an entity, and tell Hibernate "
-"you want to cache the results of that query:"
-msgstr ""
-"然后，你创建和实体相关的命名查询，并告诉 Hibernate 你要缓存该查询的结果。"
+msgid "Next, you create a named query associated with an entity, and tell Hibernate you want to cache the results of that query:"
+msgstr "然后，你创建和实体相关的命名查询，并告诉 Hibernate 你要缓存该查询的结果。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The @NamedQueries, @NamedQuery and @QueryHint annotations are all in the "
-"javax.persistence package. See the Hibernate and EJB3 documentation for more "
-"on how to use EJB3 queries and on how to instruct EJB3 to cache queries."
-msgstr ""
-"@NamedQueries, @NamedQuery and @QueryHint 注解都在 javax.persistence 包里。关"
-"于如何使用 EJB3 查询以及缓存查询结果的更多信息，请参考 Hibernate 和 EJB3 的文"
-"档。"
+msgid "The @NamedQueries, @NamedQuery and @QueryHint annotations are all in the javax.persistence package. See the Hibernate and EJB3 documentation for more on how to use EJB3 queries and on how to instruct EJB3 to cache queries."
+msgstr "@NamedQueries, @NamedQuery and @QueryHint 注解都在 javax.persistence 包里。关于如何使用 EJB3 查询以及缓存查询结果的更多信息，请参考 Hibernate 和 EJB3 的文档。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"By default, Hibernate stores query results in JBoss Cache in a region named "
-"{region_prefix}/org/hibernate/cache/StandardQueryCache. Based on this, you "
-"can set up separate eviction handling for your query results. So, if the "
-"region prefix were set to myprefix in <filename>persistence.xml</filename>, "
-"you could, for example, create this sort of eviction handling:"
-msgstr ""
-"在缺省情况下，Hibernate 把查询结果存储在 JBoss Cache 的名为 {region_prefix}/"
-"org/hibernate/cache/StandardQueryCache 区里。基于此点，你可以为查询结果设立单"
-"独的逐出处理过程。所以，如果在 persistence.xml 里把区前缀设置为 myprefix，你"
-"可以创建这样的逐出处理过程："
+msgid "By default, Hibernate stores query results in JBoss Cache in a region named {region_prefix}/org/hibernate/cache/StandardQueryCache. Based on this, you can set up separate eviction handling for your query results. So, if the region prefix were set to myprefix in <filename>persistence.xml</filename>, you could, for example, create this sort of eviction handling:"
+msgstr "在缺省情况下，Hibernate 把查询结果存储在 JBoss Cache 的名为 {region_prefix}/org/hibernate/cache/StandardQueryCache 区里。基于此点，你可以为查询结果设立单独的逐出处理过程。所以，如果在 persistence.xml 里把区前缀设置为 myprefix，你可以创建这样的逐出处理过程："
#. Tag: para
#, no-c-format
-msgid ""
-"The @NamedQuery.hints attribute shown above takes an array of vendor-"
-"specific @QueryHints as a value. Hibernate accepts the “org.hibernate."
-"cacheRegion” query hint, where the value is the name of a cache region to "
-"use instead ofthe default /org/hibernate/cache/StandardQueryCache. For "
-"example:"
-msgstr ""
-"上面的 @NamedQuery.hints 采用一个供应商专有的 @QueryHints 队列。Hibernate 接"
-"受“org.hibernate.cacheRegion”，它的值是所使用的缓存区的名称，而不是缺省的 /"
-"org/hibernate/cache/StandardQueryCache。例如："
+msgid "The @NamedQuery.hints attribute shown above takes an array of vendor-specific @QueryHints as a value. Hibernate accepts the “org.hibernate.cacheRegion” query hint, where the value is the name of a cache region to use instead ofthe default /org/hibernate/cache/StandardQueryCache. For example:"
+msgstr "上面的 @NamedQuery.hints 采用一个供应商专有的 @QueryHints 队列。Hibernate 接受“org.hibernate.cacheRegion”，它的值是所使用的缓存区的名称，而不是缺省的 /org/hibernate/cache/StandardQueryCache。例如："
#. Tag: para
#, no-c-format
@@ -554,93 +398,31 @@
#. Tag: para
#, no-c-format
-msgid ""
-"First of all, it is worth noting that clustering 2.x entity beans is a bad "
-"thing to do. Its exposes elements that generally are too fine grained for "
-"use as remote objects to clustered remote objects and introduces data "
-"synchronization problems that are non-trivial. Do NOT use EJB 2.x entity "
-"bean clustering unless you fit into the sepecial case situation of read-"
-"only, or one read-write node with read-only nodes synched with the cache "
-"invalidation services."
-msgstr ""
-"首先，值得注意的是使用群集 2.x 的 entity bean 并非好主意。它向群集的远程对象"
-"开放（exposes）通常过于细颗粒度的元素（elements），导致了严重的数据同步问题。"
-"除非你遇到特殊的情况，如只读或者只写的节点和使用缓存失效服务（cache "
-"invalidation services）的只读节点同步，否则不要使用 EJB 2.x entity bean 的群"
-"集。"
+msgid "First of all, it is worth noting that clustering 2.x entity beans is a bad thing to do. Its exposes elements that generally are too fine grained for use as remote objects to clustered remote objects and introduces data synchronization problems that are non-trivial. Do NOT use EJB 2.x entity bean clustering unless you fit into the sepecial case situation of read-only, or one read-write node with read-only nodes synched with the cache invalidation services."
+msgstr "首先，值得注意的是使用群集 2.x 的 entity bean 并非好主意。它向群集的远程对象开放（exposes）通常过于细颗粒度的元素（elements），导致了严重的数据同步问题。除非你遇到特殊的情况，如只读或者只写的节点和使用缓存失效服务（cache invalidation services）的只读节点同步，否则不要使用 EJB 2.x entity bean 的群集。"
#. Tag: para
#, no-c-format
-msgid ""
-"To use a clustered entity bean, the application does not need to do anything "
-"special, except for looking up EJB 2.x remote bean references from the "
-"clustered HA-JNDI."
-msgstr ""
-"为了使用群集的 entity bean，应用程序不需要做任何特殊的事情，除了从群集的 HA-"
-"JNDI 里查找 EJB 2.x bean 的远程引用。"
+msgid "To use a clustered entity bean, the application does not need to do anything special, except for looking up EJB 2.x remote bean references from the clustered HA-JNDI."
+msgstr "为了使用群集的 entity bean，应用程序不需要做任何特殊的事情，除了从群集的 HA-JNDI 里查找 EJB 2.x bean 的远程引用。"
#. Tag: para
#, no-c-format
-msgid ""
-"To cluster EJB 2.x entity beans, you need to add the <literal><"
-"clustered></literal> element to the application's <literal>jboss.xml</"
-"literal> descriptor file. Below is a typical <literal>jboss.xml</literal> "
-"file."
-msgstr ""
-"要群集 EJB 2.x entity beans，你需要把 <literal><clustered></literal> 元"
-"素加入到应用程序的 <literal>jboss.xml</literal> 描述符文件里。下面是一个典型"
-"的 <literal>jboss.xml</literal> 文件。"
+msgid "To cluster EJB 2.x entity beans, you need to add the <literal><clustered></literal> element to the application's <literal>jboss.xml</literal> descriptor file. Below is a typical <literal>jboss.xml</literal> file."
+msgstr "要群集 EJB 2.x entity beans，你需要把 <literal><clustered></literal> 元素加入到应用程序的 <literal>jboss.xml</literal> 描述符文件里。下面是一个典型的 <literal>jboss.xml</literal> 文件。"
#. Tag: para
#, no-c-format
-msgid ""
-"The EJB 2.x entity beans are clustered for load balanced remote invocations. "
-"All the bean instances are synchronized to have the same contents on all "
-"nodes."
-msgstr ""
-"为了平衡远程调用的负载，我们群集 EJB 2.x entity beans。所有的 bean 实例都实现"
-"同步，具有所有节点上的相同内容。"
+msgid "The EJB 2.x entity beans are clustered for load balanced remote invocations. All the bean instances are synchronized to have the same contents on all nodes."
+msgstr "为了平衡远程调用的负载，我们群集 EJB 2.x entity beans。所有的 bean 实例都实现同步，具有所有节点上的相同内容。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"However, clustered EJB 2.x Entity Beans do not have a distributed locking "
-"mechanism or a distributed cache. They can only be synchronized by using row-"
-"level locking at the database level (see <literal><row-lock></literal> "
-"in the CMP specification) or by setting the Transaction Isolation Level of "
-"your JDBC driver to be <literal>TRANSACTION_SERIALIZABLE</literal>. Because "
-"there is no supported distributed locking mechanism or distributed cache "
-"Entity Beans use Commit Option \"B\" by default (See <literal>standardjboss."
-"xml</literal> and the container configurations Clustered CMP 2.x EntityBean, "
-"Clustered CMP EntityBean, or Clustered BMP EntityBean). It is not "
-"recommended that you use Commit Option \"A\" unless your Entity Bean is read-"
-"only. (There are some design patterns that allow you to use Commit Option \"A"
-"\" with read-mostly beans. You can also take a look at the Seppuku pattern "
-"<ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\" />. JBoss may "
-"incorporate this pattern into later versions.)"
-msgstr ""
-"然而，群集的 EJB 2.x Entity Beans 没有分布式的锁定机制或是缓存。它们只能用数"
-"据库层面的行级锁定（请参考 CMP 规范的<literal><row-lock></literal>）或"
-"是把 JDBC 驱动的事务隔离（Transaction Isolation）级别设为 "
-"<literal>TRANSACTION_SERIALIZABLE</literal> 来实现同步。因为缺乏分布式的锁定"
-"机制或是缓存支持，Entity Beans 缺省使用提交选项 \"B\"（请参考 "
-"<literal>standardjboss.xml</literal> 和 the container configurations "
-"Clustered CMP 2.x EntityBean，Clustered CMP EntityBean，或 Clustered BMP "
-"EntityBean）。我们不推荐你使用提交选项 \"A\"，除非你的 Entity Bean 是只读的。"
-"（有些设计模式允许你把提交选项\"A\" 用于 read-mostly beans。你也可以看看 "
-"Seppuku 模式：<ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\"></"
-"ulink>。JBoss 有可能把这个模式集成到以后的版本里。）"
+msgid "However, clustered EJB 2.x Entity Beans do not have a distributed locking mechanism or a distributed cache. They can only be synchronized by using row-level locking at the database level (see <literal><row-lock></literal> in the CMP specification) or by setting the Transaction Isolation Level of your JDBC driver to be <literal>TRANSACTION_SERIALIZABLE</literal>. Because there is no supported distributed locking mechanism or distributed cache Entity Beans use Commit Option \"B\" by default (See <literal>standardjboss.xml</literal> and the container configurations Clustered CMP 2.x EntityBean, Clustered CMP EntityBean, or Clustered BMP EntityBean). It is not recommended that you use Commit Option \"A\" unless your Entity Bean is read-only. (There are some design patterns that allow you to use Commit Option \"A\" with read-mostly beans. You can also take a look at the Seppuku pattern <ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\" />. JBoss may incorp!
orate this pattern into later versions.)"
+msgstr "然而，群集的 EJB 2.x Entity Beans 没有分布式的锁定机制或是缓存。它们只能用数据库层面的行级锁定（请参考 CMP 规范的<literal><row-lock></literal>）或是把 JDBC 驱动的事务隔离（Transaction Isolation）级别设为 <literal>TRANSACTION_SERIALIZABLE</literal> 来实现同步。因为缺乏分布式的锁定机制或是缓存支持，Entity Beans 缺省使用提交选项 \"B\"（请参考 <literal>standardjboss.xml</literal> 和 the container configurations Clustered CMP 2.x EntityBean，Clustered CMP EntityBean，或 Clustered BMP EntityBean）。我们不推荐你使用提交选项 \"A\"，除非你的 Entity Bean 是只读的。（有些设计模式允许你把提交选项\"A\" 用于 read-mostly beans。你也可以看看 Seppuku 模式：<ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\"></ulink>。JBoss 有可能把这个模式集成到以后的版本里。）"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"If you are using Bean Managed Persistence (BMP), you are going to have to "
-"implement synchronization on your own. The MVCSoft CMP 2.0 persistence "
-"engine (see <ulink url=\"http://www.jboss.org/jbossgroup/partners.jsp\" />) "
-"provides different kinds of optimistic locking strategies that can work in a "
-"JBoss cluster."
-msgstr ""
-"如果你正在使用 Bean Managed Persistence (BMP），你将不得不实现自己的同步机"
-"制。MVCSoft CMP 2.0 持久化引擎（persistence engine）(请参考 <ulink url="
-"\"http://www.jboss.org/jbossgroup/partners.jsp\"></ulink>）提供可以在 JBoss "
-"群集里使用的各种优化锁定策略。"
+msgid "If you are using Bean Managed Persistence (BMP), you are going to have to implement synchronization on your own. The MVCSoft CMP 2.0 persistence engine (see <ulink url=\"http://www.jboss.org/jbossgroup/partners.jsp\" />) provides different kinds of optimistic locking strategies that can work in a JBoss cluster."
+msgstr "如果你正在使用 Bean Managed Persistence (BMP），你将不得不实现自己的同步机制。MVCSoft CMP 2.0 持久化引擎（persistence engine）(请参考 <ulink url=\"http://www.jboss.org/jbossgroup/partners.jsp\"></ulink>）提供可以在 JBoss 群集里使用的各种优化锁定策略。"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po 2010-02-02 04:58:05 UTC (rev 100232)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po 2010-02-02 05:00:14 UTC (rev 100233)
@@ -8,8 +8,8 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-12-09T13:49:19\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-02-02 14:58+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,248 +17,112 @@
"X-Generator: KBabel 1.11.4\n"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Security"
-msgstr "WS-Security"
+msgstr "Security"
#. Tag: secondary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBossAS"
-msgstr "JBossQL "
+msgstr "JBossAS"
#. Tag: primary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBoss Enterprise Application Platform"
-msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
+msgstr "JBoss 企业级应用程序平台"
#. Tag: para
#, no-c-format
-msgid ""
-"The JBoss security framework default implementation is based on JAAS. It "
-"implements standard J2EE authentication and authorization but also supports "
-"extended security models with <ulink url=\"http://wiki.jboss.org/wiki/Edit."
-"jsp?page=SecurityProxy\">SecurityProxy?</ulink> and <ulink url=\"http://wiki."
-"jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</"
-"ulink> implementations."
-msgstr ""
+msgid "The JBoss security framework default implementation is based on JAAS. It implements standard J2EE authentication and authorization but also supports extended security models with <ulink url=\"http://wiki.jboss.org/wiki/Edit.jsp?page=SecurityProxy\">SecurityProxy?</ulink> and <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</ulink> implementations."
+msgstr "JBoss 安全框架的缺省实现基于 JAAS。它实现了标准的 J2EE 验证和授权，它也用 <ulink url=\"http://wiki.jboss.org/wiki/Edit.jsp?page=SecurityProxy\">SecurityProxy?</ulink> 和 <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</ulink> 实现来支持扩展的安全模型。"
#. Tag: para
#, no-c-format
-msgid ""
-"JAAS based implementation enables pluggable authentication modules (PAMs) "
-"which is a way to integrate with existing authentication frameworks in your "
-"enterprise."
-msgstr ""
+msgid "JAAS based implementation enables pluggable authentication modules (PAMs) which is a way to integrate with existing authentication frameworks in your enterprise."
+msgstr "基于 JAAS 的实现启用了可插拔的验证模块（PAM），这是一种集成企业里现有验证框架的方法。"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Changes affecting Security in JBoss Enterprise Application Platform 5"
-msgstr "JBoss EAP 4.X 不支持 JTS 和 XTS 组件。"
+msgstr "影响 JBoss 企业级应用程序平台 5 的安全性的改动"
#. Tag: title
#, no-c-format
msgid "Web Layer"
-msgstr ""
+msgstr "Web 层"
#. Tag: para
#, no-c-format
-msgid ""
-"Previously the server.xml of the tomcat service contained either the "
-"JaasSecurityMgrRealm? or JaccAuthorizationRealm? (for JACC) in the "
-"<filename>server.xml</filename> Starting JBoss5, we have consolidated the "
-"realms into one \"org.jboss.web.tomcat.security.JBossWebRealm?\". The "
-"Authorization Framework is used to plugin default, jacc or xacml "
-"authorization modes."
+msgid "Previously the server.xml of the tomcat service contained either the JaasSecurityMgrRealm? or JaccAuthorizationRealm? (for JACC) in the <filename>server.xml</filename> Starting JBoss5, we have consolidated the realms into one \"org.jboss.web.tomcat.security.JBossWebRealm?\". The Authorization Framework is used to plugin default, jacc or xacml authorization modes."
msgstr ""
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "General Configuration"
-msgstr "JGroups Configuration"
+msgstr "通用配置"
#. Tag: para
#, no-c-format
-msgid ""
-"We are making an effort to get away from the previous <ulink url=\"http://"
-"wiki.jboss.org/wiki/Wiki.jsp?page=JaasSecurityManagerService"
-"\">JaasSecurityManagerService</ulink> MBean service configuration in conf/"
-"jboss-service.xml. We are trying to introduce POJO beans such as the ones "
-"defined in deployers/security-deployer-beans.xml."
-msgstr ""
+msgid "We are making an effort to get away from the previous <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JaasSecurityManagerService\">JaasSecurityManagerService</ulink> MBean service configuration in conf/jboss-service.xml. We are trying to introduce POJO beans such as the ones defined in deployers/security-deployer-beans.xml."
+msgstr "我们正在努力取消以前的 conf/jboss-service.xml 里的 <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JaasSecurityManagerService\">JaasSecurityManagerService</ulink> MBean 服务配置。我们正在尝试引入在 deployers/security-deployer-beans.xml 里定义的 POJO bean。"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Security Context"
-msgstr "安全角色"
+msgstr "安全上下文"
#. Tag: para
#, no-c-format
-msgid ""
-"We have the concept of <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?"
-"page=SecurityContext\">SecurityContext</ulink> to replace the legacy <ulink "
-"url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation"
-"\">SecurityAssociation</ulink>. Now it is possible to inject custom "
-"securitycontext objects by providing the FQN of it in the ejb2/web "
-"deployers. In the file: <filename>deployers/ejb-deployer-beans.xml</"
-"filename> <programlisting><bean name=\"EJB2xDeployer\" class=\"org.jboss."
-"ejb.deployers.EjbDeployer\"> ... <!-- Specify an unauthenticated "
-"identity --> <property name=\"unauthenticatedIdentity\">"
-"anonymous</property> <!-- Specify a SecurityManagement Wrapper --"
-"> <property name=\"securityManagement\"> <inject bean="
-"\"JNDIBasedSecurityManagement\"/> </property> <!-- Specify a "
-"SecurityContext FQN class name --> <property name="
-"\"securityContextClassName\">org.jboss.security.plugins."
-"JBossSecurityContext </property> <!-- Specify a SecurityDomain as "
-"fallback --> <property name=\"defaultSecurityDomain\">jboss-ejb-"
-"policy</property></programlisting> For the web deployer: In the file: "
-"<filename>deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml</"
-"filename> <programlisting><!-- The WebMetaData to service mbean deployer "
-"--> <bean name=\"WarDeployer\" class=\"org.jboss.web.tomcat.service."
-"deployers.TomcatDeployer\"> ... <!-- The JAAS security domain to use "
-"in the absense of an explicit security-domain specification in the war WEB-"
-"INF/jboss-web.xml --> <property name=\"defaultSecurityDomain\">"
-"java:/jaas/jboss-web-policy</property> <property name="
-"\"securityManagerService\"> <inject bean=\"jboss.security:"
-"service=JaasSecurityManager\" /> </property> <!-- Specify a "
-"SecurityManagement Wrapper --> <property name=\"securityManagement"
-"\"> <inject bean=\"JNDIBasedSecurityManagement\"/> </"
-"property> <!-- Specify a SecurityContext FQN class name --> <"
-"property name=\"securityContextClassName\"> org.jboss.security.plugins."
-"JBossSecurityContext</property></programlisting>"
+msgid "We have the concept of <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityContext\">SecurityContext</ulink> to replace the legacy <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</ulink>. Now it is possible to inject custom securitycontext objects by providing the FQN of it in the ejb2/web deployers. In the file: <filename>deployers/ejb-deployer-beans.xml</filename> <programlisting><bean name=\"EJB2xDeployer\" class=\"org.jboss.ejb.deployers.EjbDeployer\"> ... <!-- Specify an unauthenticated identity --> <property name=\"unauthenticatedIdentity\">anonymous</property> <!-- Specify a SecurityManagement Wrapper --> <property name=\"securityManagement\"> <inject bean=\"JNDIBasedSecurityManagement\"/> </property> <!-- Specify a SecurityContext FQN class name --> <property name=\"securityContextClassName\">org.jboss.security.plugins.JBossSecurityContext <!
;/property> <!-- Specify a SecurityDomain as fallback --> <property name=\"defaultSecurityDomain\">jboss-ejb-policy</property></programlisting> For the web deployer: In the file: <filename>deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml</filename> <programlisting><!-- The WebMetaData to service mbean deployer --> <bean name=\"WarDeployer\" class=\"org.jboss.web.tomcat.service.deployers.TomcatDeployer\"> ... <!-- The JAAS security domain to use in the absense of an explicit security-domain specification in the war WEB-INF/jboss-web.xml --> <property name=\"defaultSecurityDomain\">java:/jaas/jboss-web-policy</property> <property name=\"securityManagerService\"> <inject bean=\"jboss.security:service=JaasSecurityManager\" /> </property> <!-- Specify a SecurityManagement Wrapper --> <property name=\"securityManagement\"> <inject bean=\"JNDIBasedSecurityManagement\"/> </property&!
gt; <!-- Specify a SecurityContext FQN class name --> &l!
t;proper
ty name=\"securityContextClassName\"> org.jboss.security.plugins.JBossSecurityContext</property></programlisting>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Default Security Domains for the EJB and WEB deployments."
-msgstr ""
+msgstr "用于 EJB 和 WEB 部署的缺省安全域。"
#. Tag: para
#, no-c-format
-msgid ""
-"We have defined application policies \"jboss-ejb-policy\" and \"jboss-web-"
-"policy\" as the fall back security domains for the ejb and web layers. These "
-"are defined in deploy/security-policies-service.xml"
+msgid "We have defined application policies \"jboss-ejb-policy\" and \"jboss-web-policy\" as the fall back security domains for the ejb and web layers. These are defined in deploy/security-policies-service.xml"
msgstr ""
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Securing a Web Application in JBoss Enterprise Application Platform"
-msgstr "本书是配置用于 JBoss 企业级应用程序平台的 JBoss 应用服务器的指南。"
+msgstr "设置 JBoss 企业级应用程序平台里的 Web 应用程序的安全性"
#. Tag: para
#, no-c-format
-msgid ""
-"Securing web resources basically involves setting some stuff in the web "
-"deployment descriptor, and in jboss-web.xml. You also have to do a little "
-"prep work to the server itself to configure a security domain for JBoss SX. "
-"These instructions assume that you have JBoss AS installed, and you have a "
-"server instance created with at least Tomcat included. The \"default\" "
-"instance is a good choice here. The variable ${JBOSS_HOME} refers to the "
-"location you extracted/installed JBoss AS to, and ${server_configuration} "
-"corresponds to the name of the server instance you are configuring for "
-"security. The first part of these instructions refers to setting up JBoss SX "
-"for security, and the second part deals with setting up the web application "
-"for security using basic authentication. You can access the instructions in "
-"the following section."
+msgid "Securing web resources basically involves setting some stuff in the web deployment descriptor, and in jboss-web.xml. You also have to do a little prep work to the server itself to configure a security domain for JBoss SX. These instructions assume that you have JBoss AS installed, and you have a server instance created with at least Tomcat included. The \"default\" instance is a good choice here. The variable ${JBOSS_HOME} refers to the location you extracted/installed JBoss AS to, and ${server_configuration} corresponds to the name of the server instance you are configuring for security. The first part of these instructions refers to setting up JBoss SX for security, and the second part deals with setting up the web application for security using basic authentication. You can access the instructions in the following section."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Create a simple security domain for JBoss SX"
-msgstr ""
+msgstr "创建 JBoss SX 所用的一个简单安全域"
#. Tag: para
#, no-c-format
-msgid ""
-"Setting up a security domain is simple with JBoss SX. The following "
-"instructions are a step by step methodology for creating a simple domain "
-"that uses two properties files to hold user ids, passwords, and roles for "
-"those users."
-msgstr ""
+msgid "Setting up a security domain is simple with JBoss SX. The following instructions are a step by step methodology for creating a simple domain that uses two properties files to hold user ids, passwords, and roles for those users."
+msgstr "设置 JBoss SX 的安全域是很简单的。下面的说明是创建一个简单的安全域的逐步的方法，它使用两个属性文件来保存用户 ID、密码和角色。"
#. Tag: para
#, no-c-format
-msgid ""
-"Open the <filename> ${JBOSS_HOME}/server/${server_configuration}/conf/login-"
-"config.xml</filename> file. This file sets up the configuration for the "
-"security domains available to applications running in the server. The file "
-"already has a few domains in there for some example/default resources, so "
-"you might want to look to those for inspiration. JBoss SX uses JAAS for the "
-"underlying security infrastructure, and JAAS uses a class called a \"login "
-"module\" to interact with a security store for authenticating credentials. "
-"This file basically hooks up a security domain (just a name really) to a "
-"JAAS login module. JBoss Enterprise Application Platform comes packed with a "
-"few different login modules which you can find more information about on the "
-"JBoss SX wiki page at JBossSX."
-msgstr ""
+msgid "Open the <filename> ${JBOSS_HOME}/server/${server_configuration}/conf/login-config.xml</filename> file. This file sets up the configuration for the security domains available to applications running in the server. The file already has a few domains in there for some example/default resources, so you might want to look to those for inspiration. JBoss SX uses JAAS for the underlying security infrastructure, and JAAS uses a class called a \"login module\" to interact with a security store for authenticating credentials. This file basically hooks up a security domain (just a name really) to a JAAS login module. JBoss Enterprise Application Platform comes packed with a few different login modules which you can find more information about on the JBoss SX wiki page at JBossSX."
+msgstr "打开 <filename> ${JBOSS_HOME}/server/${server_configuration}/conf/login-config.xml</filename> 文件。这个文件对服务器里运行的应用程序可用的安全域进行配置。它也包含一些用于示例/缺省资源的域，所以你可以查看这些域以获取灵感。JBoss SX 使用 JAAS 作为底层的安全基础结构，JAAS 使用一个名为“登录模块”的类来和安全库（security store）进行交互以进行验证。这个文件基本上安全域（实际上是其名称）和 JAAS 登录模块对应起来。JBoss 企业级应用程序平台带有一些不同的登录模块，你可以在 JBoss SX 维基页面种找到更多的信息。"
#. Tag: para
#, no-c-format
-msgid ""
-"The easiest login module to start with is the <ulink url=\"http://wiki.jboss."
-"org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</"
-"ulink>. This login module allows you to specify user names, passwords and "
-"roles in a simple property file. Obviously, this module isn't one of the "
-"more secure modules, so you probably would want to use something like LDAP "
-"to store/lookup credentials in production."
+msgid "The easiest login module to start with is the <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</ulink>. This login module allows you to specify user names, passwords and roles in a simple property file. Obviously, this module isn't one of the more secure modules, so you probably would want to use something like LDAP to store/lookup credentials in production."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Copy the \"jmx-console\" domain policy as a starting point. The \"jmx-console"
-"\" security domain policy contains the basics for configuring a "
-"UsersRolesLoginModule based security domain. Here is a copy of that section: "
-"<programlisting><application-policy name = \"jmx-console\"> <"
-"authentication> <login-module code=\"org.jboss.security.auth.spi."
-"UsersRolesLoginModule\" flag = \"required\"> <module-option name="
-"\"usersProperties\"> props/jmx-console-users.properties </module-"
-"option> <module-option name=\"rolesProperties\"> props/jmx-console-"
-"roles.properties </module-option> </login-module> </"
-"authentication> </application-policy></programlisting> Copy this "
-"section to the bottom of the file, and change the \"name\" attribute on the "
-"application-policy attribute to \"my-web\". Also, change the \"userProperties"
-"\" module-option text value to be \"props/my-web-users.properties\", and the "
-"\"roleProperties\" module-option text value to be \"props/my-web-roles."
-"properties\". Save the login-config.xml file. The \"name\" attribute on the "
-"\"application-policy\" element specifies the name of the security domain. "
-"This name is important because it is what will be used to tie the security "
-"domain to the web application later. The \"login-module\" element specifies "
-"the login module that this domain will use. You can actually have multiple "
-"\"login-module\" elements to have multi-level authentication, but we'll "
-"stick to one for this simple case. The \"flag\" attribute on the login-"
-"module element specifies how to handle failed authentications from this "
-"module, and how it interacts with other modules. The \"required\" value is "
-"what you would want for a single login module, but you can refer to the DTD "
-"for the login-config.xml file for more info about the other options. "
-"Finally, the \"module-option\" elements specify some values to pass into the "
-"login module's \"initialize\" method. These values are passed in as a name-"
-"value map to that method. In the case of the <ulink url=\"http://wiki.jboss."
-"org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</"
-"ulink>, we need to tell the module what properties files to use for looking "
-"up user information (usersProperties), and what file to use for looking up "
-"role information (rolesProperties). These paths are relative to the "
-"${JBOSS_HOME}/server/${server_configuration}/conf directory."
+msgid "Copy the \"jmx-console\" domain policy as a starting point. The \"jmx-console\" security domain policy contains the basics for configuring a UsersRolesLoginModule based security domain. Here is a copy of that section: <programlisting><application-policy name = \"jmx-console\"> <authentication> <login-module code=\"org.jboss.security.auth.spi.UsersRolesLoginModule\" flag = \"required\"> <module-option name=\"usersProperties\"> props/jmx-console-users.properties </module-option> <module-option name=\"rolesProperties\"> props/jmx-console-roles.properties </module-option> </login-module> </authentication> </application-policy></programlisting> Copy this section to the bottom of the file, and change the \"name\" attribute on the application-policy attribute to \"my-web\". Also, change the \"userProperties\" module-option text value to be \"props/my-web-users.properties\", and the \"roleProperties\" module-option !
text value to be \"props/my-web-roles.properties\". Save the login-config.xml file. The \"name\" attribute on the \"application-policy\" element specifies the name of the security domain. This name is important because it is what will be used to tie the security domain to the web application later. The \"login-module\" element specifies the login module that this domain will use. You can actually have multiple \"login-module\" elements to have multi-level authentication, but we'll stick to one for this simple case. The \"flag\" attribute on the login-module element specifies how to handle failed authentications from this module, and how it interacts with other modules. The \"required\" value is what you would want for a single login module, but you can refer to the DTD for the login-config.xml file for more info about the other options. Finally, the \"module-option\" elements specify some values to pass into the login module's \"initialize\" method. These values are passed !
in as a name-value map to that method. In the case of the <uli!
nk url=\
"http://wiki.jboss.org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</ulink>, we need to tell the module what properties files to use for looking up user information (usersProperties), and what file to use for looking up role information (rolesProperties). These paths are relative to the ${JBOSS_HOME}/server/${server_configuration}/conf directory."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"In the ${JBOSS_HOME}/server/conf/props directory, copy the jmx-console-users."
-"properties into a new file called my-web-users.properties, and copy the jmx-"
-"console-roles.properties into a new file called my-web-roles.properties. "
-"Opening the my-web-users.properties file, you will see a single entry like "
-"this: \"admin=admin\". When a user logs into this security domain, the login "
-"module will examine the properties data in this file for known users. The "
-"structure of the entries in this file is \"username=password\". Let's add a "
-"new entry to the file for your own user by pasting \"chris=secure\" on a new "
-"line below the \"admin=admin\" line in the file. Save this file. Next, open "
-"the <filename>my-web-roles.properties</filename> file, and you should see an "
-"line like the following: \"<emphasis>admin=JBossAdmin,HttpInvoker</emphasis>"
-"\". The entries in this file define what roles a user has associated with "
-"their account when they login. The form of these entries is \"username=Role1,"
-"Role2,...\" where the username is the user you wish to assign roles to, and "
-"the Roles entries are a comma separated list of roles to assign to that "
-"user. Add a new entry to this file by pasting \"chris=WebAppUser\" on a new "
-"line below the \"admin=....\" line. Save this file."
-msgstr ""
+msgid "In the ${JBOSS_HOME}/server/conf/props directory, copy the jmx-console-users.properties into a new file called my-web-users.properties, and copy the jmx-console-roles.properties into a new file called my-web-roles.properties. Opening the my-web-users.properties file, you will see a single entry like this: \"admin=admin\". When a user logs into this security domain, the login module will examine the properties data in this file for known users. The structure of the entries in this file is \"username=password\". Let's add a new entry to the file for your own user by pasting \"chris=secure\" on a new line below the \"admin=admin\" line in the file. Save this file. Next, open the <filename>my-web-roles.properties</filename> file, and you should see an line like the following: \"<emphasis>admin=JBossAdmin,HttpInvoker</emphasis>\". The entries in this file define what roles a user has associated with their account when they login. The form of these entries is \"username=Ro!
le1,Role2,...\" where the username is the user you wish to assign roles to, and the Roles entries are a comma separated list of roles to assign to that user. Add a new entry to this file by pasting \"chris=WebAppUser\" on a new line below the \"admin=....\" line. Save this file."
+msgstr "在 ${JBOSS_HOME}/server/conf/props 目录里，把 jmx-console-users.properties 复制为一个名为 my-web-users.properties 的文件，并把 jmx-console-roles.properties 复制为 my-web-roles.properties。打开 my-web-users.properties 文件，你将看到一个类似 \"admin=admin\" 的条目。当用户登录到这个安全域时，登录模块将检查这个文件李的属性数据来确认已知用户。这个文件里的条目的结构是 \"username=password\"。让我们在 \"admin=admin\" 下面添加一个自己的新条目 \"chris=secure\"。然后，打开 <filename>my-web-roles.properties</filename> 文件，你应该看到 \"<emphasis>admin=JBossAdmin,HttpInvoker</emphasis>\"。这个外键里的条目定义了用户相关联的角色。这些条目的格式是 \"username=Role1,Role2,...\"，这里的 username 你要分配角色的用户，而角色条目是一个以逗号隔开的角色列表。在 \"admin=....\" 下面添加一条 \"chris=WebAp!
pUser\" 的条目。保存这个文件。"
+
More information about the jboss-cvs-commits
mailing list