[jboss-cvs] JBossAS SVN: r104353 - 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
Thu Apr 29 21:27:28 EDT 2010
Author: xhuang at jboss.com
Date: 2010-04-29 21:27:27 -0400 (Thu, 29 Apr 2010)
New Revision: 104353
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/AOP.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Web_Services.po
Log:
update
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/AOP.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/AOP.po 2010-04-30 00:47:57 UTC (rev 104352)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/AOP.po 2010-04-30 01:27:27 UTC (rev 104353)
@@ -8,8 +8,8 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:17:59\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-04-28 15:40+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,48 +23,22 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<indexterm><primary>JBoss AOP</primary><secondary>aspect oriented framework</"
-"secondary></indexterm> <indexterm><primary>AOP</primary><see>JBoss AOP</"
-"see></indexterm> JBoss AOP is a 100% Pure Java Aspected Oriented Framework "
-"usable in any programming environment or tightly integrated with our "
-"application server. Aspects allow you to more easily modularize your code "
-"base when regular object oriented programming just doesn't fit the bill. It "
-"can provide a cleaner separation from application logic and system code. It "
-"provides a great way to expose integration points into your software. "
-"Combined with JDK 1.5 Annotations, it also is a great way to expand the Java "
-"language in a clean pluggable way rather than using annotations solely for "
-"code generation."
-msgstr ""
+msgid "<indexterm><primary>JBoss AOP</primary><secondary>aspect oriented framework</secondary></indexterm> <indexterm><primary>AOP</primary><see>JBoss AOP</see></indexterm> JBoss AOP is a 100% Pure Java Aspected Oriented Framework usable in any programming environment or tightly integrated with our application server. Aspects allow you to more easily modularize your code base when regular object oriented programming just doesn't fit the bill. It can provide a cleaner separation from application logic and system code. It provides a great way to expose integration points into your software. Combined with JDK 1.5 Annotations, it also is a great way to expand the Java language in a clean pluggable way rather than using annotations solely for code generation."
+msgstr "<indexterm><primary>JBoss AOP</primary> <secondary>面向切面的框架</secondary></indexterm> <indexterm><primary>AOP</primary><see>JBoss AOP</see></indexterm> JBoss AOP 是 100% 纯 Java 的面向切面的框架，它可用在任何编程环境或者和应用服务器集成。切面（Aspect）允许你更容易地将代码模块化，而常规的面向对象的编程做不到这一点。它提供了一个很好的方法以开放软件里的集成点。和 JDK 1.5 的组合，使它可以可插拔的方式扩展 Java，而无需单独使用用于代码生成的注解。"
#. Tag: para
#, no-c-format
-msgid ""
-"JBoss AOP is not only a framework, but also a prepackaged set of aspects "
-"that are applied via annotations, pointcut expressions, or dynamically at "
-"runtime. Some of these include caching, asynchronous communication, "
-"transactions, security, remoting, and many many more."
+msgid "JBoss AOP is not only a framework, but also a prepackaged set of aspects that are applied via annotations, pointcut expressions, or dynamically at runtime. Some of these include caching, asynchronous communication, transactions, security, remoting, and many many more."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"An aspect is a common feature that is typically scattered across methods, "
-"classes, object hierarchies, or even entire object models. It is behavior "
-"that looks and smells like it should have structure, but you can't find a "
-"way to express this structure in code with traditional object-oriented "
-"techniques."
+msgid "An aspect is a common feature that is typically scattered across methods, classes, object hierarchies, or even entire object models. It is behavior that looks and smells like it should have structure, but you can't find a way to express this structure in code with traditional object-oriented techniques."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"For example, metrics is one common aspect. To generate useful logs from your "
-"application, you have to (often liberally) sprinkle informative messages "
-"throughout your code. However, metrics is something that your class or "
-"object model really shouldn't be concerned about. After all, metrics is "
-"irrelevant to your actual application: it doesn't represent a customer or an "
-"account, and it doesn't realize a business rule. It's simply orthogonal."
+msgid "For example, metrics is one common aspect. To generate useful logs from your application, you have to (often liberally) sprinkle informative messages throughout your code. However, metrics is something that your class or object model really shouldn't be concerned about. After all, metrics is irrelevant to your actual application: it doesn't represent a customer or an account, and it doesn't realize a business rule. It's simply orthogonal."
msgstr ""
#. Tag: title
@@ -79,12 +53,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"A <emphasis>joinpoint</emphasis> is any point in your Java program. The call "
-"of a method, the execution of a constructor, the access of a field; all "
-"these are joinpoints. You could also think of a joinpoint as a particular "
-"Java event, where an event is a method call, constructor call, field access, "
-"etc."
+msgid "A <emphasis>joinpoint</emphasis> is any point in your Java program. The call of a method, the execution of a constructor, the access of a field; all these are joinpoints. You could also think of a joinpoint as a particular Java event, where an event is a method call, constructor call, field access, etc."
msgstr ""
#. Tag: title
@@ -94,10 +63,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"An <emphasis>invocation</emphasis> is a JBoss AOP class that encapsulates "
-"what a joinpiont is at runtime. It could contain information like which "
-"method is being called, the arguments of the method, etc."
+msgid "An <emphasis>invocation</emphasis> is a JBoss AOP class that encapsulates what a joinpiont is at runtime. It could contain information like which method is being called, the arguments of the method, etc."
msgstr ""
#. Tag: title
@@ -107,11 +73,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"An <emphasis>advice</emphasis> is a method that is called when a particular "
-"joinpoint is executed, such as the behavior that is triggered when a method "
-"is called. It could also be thought of as the code that performs the "
-"interception. Another analogy is that an advice is an \"event handler\"."
+msgid "An <emphasis>advice</emphasis> is a method that is called when a particular joinpoint is executed, such as the behavior that is triggered when a method is called. It could also be thought of as the code that performs the interception. Another analogy is that an advice is an \"event handler\"."
msgstr ""
#. Tag: title
@@ -121,10 +83,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<emphasis>Pointcuts</emphasis> are AOP's expression language. Just as a "
-"regular expression matches strings, a pointcut expression matches a "
-"particular joinpoint."
+msgid "<emphasis>Pointcuts</emphasis> are AOP's expression language. Just as a regular expression matches strings, a pointcut expression matches a particular joinpoint."
msgstr ""
#. Tag: title
@@ -134,10 +93,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"An <emphasis>introduction</emphasis> modifies the type and structure of a "
-"Java class. It can be used to force an existing class to implement an "
-"interface or to add an annotation to anything."
+msgid "An <emphasis>introduction</emphasis> modifies the type and structure of a Java class. It can be used to force an existing class to implement an interface or to add an annotation to anything."
msgstr ""
#. Tag: title
@@ -147,10 +103,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"An <emphasis>aspect</emphasis> is a plain Java class that encapsulates any "
-"number of advices, pointcut definitions, mixins, or any other JBoss AOP "
-"construct."
+msgid "An <emphasis>aspect</emphasis> is a plain Java class that encapsulates any number of advices, pointcut definitions, mixins, or any other JBoss AOP construct."
msgstr ""
#. Tag: title
@@ -160,29 +113,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"An <emphasis>interceptor</emphasis> is an aspect with only one advice, named "
-"<literal>invoke</literal>. It is a specific interface that you can implement "
-"if you want your code to be checked by forcing your class to implement an "
-"interface. It also will be portable and can be reused in other JBoss "
-"environments like EJBs and JMX MBeans."
+msgid "An <emphasis>interceptor</emphasis> is an aspect with only one advice, named <literal>invoke</literal>. It is a specific interface that you can implement if you want your code to be checked by forcing your class to implement an interface. It also will be portable and can be reused in other JBoss environments like EJBs and JMX MBeans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"In AOP, a feature like metrics is called a <emphasis>crosscutting concern</"
-"emphasis>, as it is a behavior that \"cuts\" across multiple points in your "
-"object models, yet is distinctly different. As a development methodology, "
-"AOP recommends that you abstract and encapsulate crosscutting concerns."
+msgid "In AOP, a feature like metrics is called a <emphasis>crosscutting concern</emphasis>, as it is a behavior that \"cuts\" across multiple points in your object models, yet is distinctly different. As a development methodology, AOP recommends that you abstract and encapsulate crosscutting concerns."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"For example, let's say you wanted to add code to an application to measure "
-"the amount of time it would take to invoke a particular method. In plain "
-"Java, the code would look something like the following."
+msgid "For example, let's say you wanted to add code to an application to measure the amount of time it would take to invoke a particular method. In plain Java, the code would look something like the following."
msgstr ""
#. Tag: para
@@ -192,46 +133,28 @@
#. Tag: para
#, no-c-format
-msgid ""
-"It's extremely difficult to turn metrics on and off, as you have to manually "
-"add the code in the <code>try</code>/<code>finally</code> blocks to each and "
-"every method or constructor you want to benchmark."
+msgid "It's extremely difficult to turn metrics on and off, as you have to manually add the code in the <code>try</code>/<code>finally</code> blocks to each and every method or constructor you want to benchmark."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Profiling code should not be combined with your application code. It makes "
-"your code more verbose and difficult to read, since the timings must be "
-"enclosed within the <code>try</code>/<code>finally</code> blocks."
+msgid "Profiling code should not be combined with your application code. It makes your code more verbose and difficult to read, since the timings must be enclosed within the <code>try</code>/<code>finally</code> blocks."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"If you wanted to expand this functionality to include a method or failure "
-"count, or even to register these statistics to a more sophisticated "
-"reporting mechanism, you'd have to modify a lot of different files (again)."
+msgid "If you wanted to expand this functionality to include a method or failure count, or even to register these statistics to a more sophisticated reporting mechanism, you'd have to modify a lot of different files (again)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"This approach to metrics is very difficult to maintain, expand, and extend, "
-"because it is dispersed throughout your entire code base. In many cases, OOP "
-"may not always be the best way to add metrics to a class."
+msgid "This approach to metrics is very difficult to maintain, expand, and extend, because it is dispersed throughout your entire code base. In many cases, OOP may not always be the best way to add metrics to a class."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Aspect-oriented programming gives you a way to encapsulate this type of "
-"behavior functionality. It allows you to add behavior such as metrics "
-"\"around\" your code. For example, AOP provides you with programmatic "
-"control to specify that you want calls to <classname>BankAccountDAO</"
-"classname> to go through a metrics aspect before executing the actual body "
-"of that code."
-msgstr ""
+msgid "Aspect-oriented programming gives you a way to encapsulate this type of behavior functionality. It allows you to add behavior such as metrics \"around\" your code. For example, AOP provides you with programmatic control to specify that you want calls to <classname>BankAccountDAO</classname> to go through a metrics aspect before executing the actual body of that code."
+msgstr "面向切面的编程可以封装这种行为。"
#. Tag: title
#, fuzzy, no-c-format
@@ -240,62 +163,32 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<indexterm><primary>JBoss AOP</primary><secondary>creating aspects</"
-"secondary></indexterm> In short, all AOP frameworks define two things: a way "
-"to implement crosscutting concerns, and a programmatic construct — a "
-"programming language or a set of tags to specify how you want to apply those "
-"snippets of code. Let's take a look at how JBoss AOP, its cross-cutting "
-"concerns, and how you can implement a metrics aspect in JBoss Enterprise "
-"Application Platform."
+msgid "<indexterm><primary>JBoss AOP</primary><secondary>creating aspects</secondary></indexterm> In short, all AOP frameworks define two things: a way to implement crosscutting concerns, and a programmatic construct — a programming language or a set of tags to specify how you want to apply those snippets of code. Let's take a look at how JBoss AOP, its cross-cutting concerns, and how you can implement a metrics aspect in JBoss Enterprise Application Platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"The first step in creating a metrics aspect in JBoss AOP is to encapsulate "
-"the metrics feature in its own Java class. The following code extracts the "
-"<code>try</code>/<code>finally</code> block in our first code example's "
-"<methodname>BankAccountDAO.withdraw()</methodname> method into "
-"<literal>Metrics</literal>, an implementation of a JBoss AOP Interceptor "
-"class."
+msgid "The first step in creating a metrics aspect in JBoss AOP is to encapsulate the metrics feature in its own Java class. The following code extracts the <code>try</code>/<code>finally</code> block in our first code example's <methodname>BankAccountDAO.withdraw()</methodname> method into <literal>Metrics</literal>, an implementation of a JBoss AOP Interceptor class."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"The following example code demonstrates implementing metrics in a JBoss AOP "
-"Interceptor"
+msgid "The following example code demonstrates implementing metrics in a JBoss AOP Interceptor"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Under JBoss AOP, the Metrics class wraps <methodname>withdraw()</"
-"methodname>: when calling code invokes <methodname>withdraw()</methodname>, "
-"the AOP framework breaks the method call into its parts and encapsulates "
-"those parts into an Invocation object. The framework then calls any aspects "
-"that sit between the calling code and the actual method body."
+msgid "Under JBoss AOP, the Metrics class wraps <methodname>withdraw()</methodname>: when calling code invokes <methodname>withdraw()</methodname>, the AOP framework breaks the method call into its parts and encapsulates those parts into an Invocation object. The framework then calls any aspects that sit between the calling code and the actual method body."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"When the AOP framework is done dissecting the method call, it calls "
-"<classname>Metrics</classname>'s invoke method at line 3. Line 8 wraps and "
-"delegates to the actual method and uses an enclosing <code>try</code>/"
-"<code>finally</code> block to perform the timings. Line 13 obtains "
-"contextual information about the method call from the <classname>Invocation</"
-"classname> object, while line 14 displays the method name and the calculated "
-"metrics."
+msgid "When the AOP framework is done dissecting the method call, it calls <classname>Metrics</classname>'s invoke method at line 3. Line 8 wraps and delegates to the actual method and uses an enclosing <code>try</code>/<code>finally</code> block to perform the timings. Line 13 obtains contextual information about the method call from the <classname>Invocation</classname> object, while line 14 displays the method name and the calculated metrics."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Having the <classname>Metrics</classname> code within its own object allows "
-"us to easily expand and capture additional measurements later on. Now that "
-"metrics are encapsulated into an aspect, let's see how to apply it."
+msgid "Having the <classname>Metrics</classname> code within its own object allows us to easily expand and capture additional measurements later on. Now that metrics are encapsulated into an aspect, let's see how to apply it."
msgstr ""
#. Tag: title
@@ -305,90 +198,42 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<indexterm><primary>JBoss AOP</primary><secondary>applying aspects</"
-"secondary></indexterm> To apply an aspect, you define when to execute the "
-"aspect code. Those points in execution are called <emphasis>pointcuts</"
-"emphasis>. An analogy to a pointcut is a regular expression. Where a regular "
-"expression matches strings, a pointcut expression matches events or "
-"<emphasis>points</emphasis> within your application. For example, a valid "
-"pointcut definition would be, \"for all calls to the JDBC method "
-"<methodname>executeQuery()</methodname>, call the aspect that verifies SQL "
-"syntax.\""
+msgid "<indexterm><primary>JBoss AOP</primary><secondary>applying aspects</secondary></indexterm> To apply an aspect, you define when to execute the aspect code. Those points in execution are called <emphasis>pointcuts</emphasis>. An analogy to a pointcut is a regular expression. Where a regular expression matches strings, a pointcut expression matches events or <emphasis>points</emphasis> within your application. For example, a valid pointcut definition would be, \"for all calls to the JDBC method <methodname>executeQuery()</methodname>, call the aspect that verifies SQL syntax.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"An entry point could be a field access, or a method or constructor call. An "
-"event could be an exception being thrown. Some AOP implementations use "
-"languages akin to queries to specify pointcuts. Others use tags. JBoss AOP "
-"uses both."
+msgid "An entry point could be a field access, or a method or constructor call. An event could be an exception being thrown. Some AOP implementations use languages akin to queries to specify pointcuts. Others use tags. JBoss AOP uses both."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"The following listing demonstrates defining a pointcut for the Metrics "
-"example in JBoss AOP:"
+msgid "The following listing demonstrates defining a pointcut for the Metrics example in JBoss AOP:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Lines 1-3 define a pointcut that applies the <literal>metrics</literal> "
-"aspect to the specific method <methodname>BankAccountDAO.withdraw()</"
-"methodname>. Lines 4-6 define a general pointcut that applies the "
-"<literal>metrics</literal> aspect to all methods in all classes in the "
-"<filename>com.mc.billing</filename> package. There is also an optional "
-"annotation mapping if you prefer to avoid XML. For more information, see the "
-"JBoss AOP reference documentation."
+msgid "Lines 1-3 define a pointcut that applies the <literal>metrics</literal> aspect to the specific method <methodname>BankAccountDAO.withdraw()</methodname>. Lines 4-6 define a general pointcut that applies the <literal>metrics</literal> aspect to all methods in all classes in the <filename>com.mc.billing</filename> package. There is also an optional annotation mapping if you prefer to avoid XML. For more information, see the JBoss AOP reference documentation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"JBoss AOP has a rich set of pointcut expressions that you can use to define "
-"various points or events in your Java application. Once your points are "
-"defined, you can apply aspects to them. You can attach your aspects to a "
-"specific Java class in your application or you can use more complex "
-"compositional pointcuts to specify a wide range of classes within one "
-"expression."
+msgid "JBoss AOP has a rich set of pointcut expressions that you can use to define various points or events in your Java application. Once your points are defined, you can apply aspects to them. You can attach your aspects to a specific Java class in your application or you can use more complex compositional pointcuts to specify a wide range of classes within one expression."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"With AOP, as this example shows, you can combine all crosscutting behavior "
-"into one object and apply it easily and simply, without complicating your "
-"code with features unrelated to business logic. Instead, common crosscutting "
-"concerns can be maintained and extended in one place."
+msgid "With AOP, as this example shows, you can combine all crosscutting behavior into one object and apply it easily and simply, without complicating your code with features unrelated to business logic. Instead, common crosscutting concerns can be maintained and extended in one place."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Note that code within the <classname>BankAccountDAO</classname> class does "
-"not detect that it is being profiled. Profiling is part of what aspect-"
-"oriented programmers deem orthogonal concerns. In the object-oriented "
-"programming code snippet at the beginning of this chapter, profiling was "
-"part of the application code. AOP allows you to remove that code. A modern "
-"promise of middleware is transparency, and AOP clearly delivers."
+msgid "Note that code within the <classname>BankAccountDAO</classname> class does not detect that it is being profiled. Profiling is part of what aspect-oriented programmers deem orthogonal concerns. In the object-oriented programming code snippet at the beginning of this chapter, profiling was part of the application code. AOP allows you to remove that code. A modern promise of middleware is transparency, and AOP clearly delivers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Orthogonal behavior can also be included after development. In object-"
-"oriented code, monitoring and profiling must be added at development time. "
-"With AOP, a developer or an administrator can easily add monitoring and "
-"metrics as needed without touching the code. This is a very subtle but "
-"significant part of AOP, as this separation allows aspects to be layered on "
-"top of or below the code that they cut across. A layered design allows "
-"features to be added or removed at will. For instance, perhaps you snap on "
-"metrics only when you're doing some benchmarks, but remove it for "
-"production. With AOP, this can be done without editing, recompiling, or "
-"repackaging the code."
+msgid "Orthogonal behavior can also be included after development. In object-oriented code, monitoring and profiling must be added at development time. With AOP, a developer or an administrator can easily add monitoring and metrics as needed without touching the code. This is a very subtle but significant part of AOP, as this separation allows aspects to be layered on top of or below the code that they cut across. A layered design allows features to be added or removed at will. For instance, perhaps you snap on metrics only when you're doing some benchmarks, but remove it for production. With AOP, this can be done without editing, recompiling, or repackaging the code."
msgstr ""
#. Tag: title
@@ -398,62 +243,27 @@
#. Tag: para
#, no-c-format
-msgid ""
-"To deploy an AOP application in JBoss Enterprise Application Platform you "
-"need to package it. AOP is packaged similarly to SARs (MBeans). You can "
-"either deploy an XML file directly in the <filename>deploy/</filename> "
-"directory with the signature <filename>*-aop.xml</filename> along with your "
-"package (this is how the <filename>base-aop.xml</filename>, included in the "
-"<filename>jboss-aop.deployer</filename> file works) or you can include it in "
-"the JAR file containing your classes. If you include your XML file in your "
-"JAR, it must have the file extension <filename>.aop</filename> and a "
-"<filename>jboss-aop.xml</filename> file must be contained in a "
-"<filename>META-INF</filename> directory, for instance: <filename>META-INF/"
-"jboss-aop.xml</filename>."
+msgid "To deploy an AOP application in JBoss Enterprise Application Platform you need to package it. AOP is packaged similarly to SARs (MBeans). You can either deploy an XML file directly in the <filename>deploy/</filename> directory with the signature <filename>*-aop.xml</filename> along with your package (this is how the <filename>base-aop.xml</filename>, included in the <filename>jboss-aop.deployer</filename> file works) or you can include it in the JAR file containing your classes. If you include your XML file in your JAR, it must have the file extension <filename>.aop</filename> and a <filename>jboss-aop.xml</filename> file must be contained in a <filename>META-INF</filename> directory, for instance: <filename>META-INF/jboss-aop.xml</filename>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"In the JBoss Enterprise Application Platform 5, you <emphasis>must</"
-"emphasis> specify the schema used, otherwise your information will not be "
-"parsed correctly. You do this by adding the <varname>xmlns=\"urn:jboss:aop-"
-"beans:1:0</varname> attribute to the root <literal>aop</literal> element, as "
-"shown here:"
+msgid "In the JBoss Enterprise Application Platform 5, you <emphasis>must</emphasis> specify the schema used, otherwise your information will not be parsed correctly. You do this by adding the <varname>xmlns=\"urn:jboss:aop-beans:1:0</varname> attribute to the root <literal>aop</literal> element, as shown here:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"If you want to create anything more than a non-trivial example, using the "
-"<filename>.aop</filename> JAR files, you can make any top-level deployment "
-"contain an AOP file containing the XML binding configuration. For instance "
-"you can have an AOP file in an EAR file, or an AOP file in a WAR file. The "
-"bindings specified in the <filename>META-INF/jboss-aop.xml</filename> file "
-"contained in the AOP file will affect all the classes in the whole WAR file."
+msgid "If you want to create anything more than a non-trivial example, using the <filename>.aop</filename> JAR files, you can make any top-level deployment contain an AOP file containing the XML binding configuration. For instance you can have an AOP file in an EAR file, or an AOP file in a WAR file. The bindings specified in the <filename>META-INF/jboss-aop.xml</filename> file contained in the AOP file will affect all the classes in the whole WAR file."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"To pick up an AOP file in an EAR file, it must be listed in the <filename>."
-"ear/META-INF/application.xml</filename> as a Java module, as follows:"
+msgid "To pick up an AOP file in an EAR file, it must be listed in the <filename>.ear/META-INF/application.xml</filename> as a Java module, as follows:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"In the JBoss Enterprise Application Platform 5, the contents of the "
-"<filename>.ear</filename> file are deployed in the order they are listed in "
-"the <filename>application.xml</filename>. When using loadtime weaving the "
-"bindings listed in the <filename>example.aop</filename> file must be "
-"deployed before the classes being advised are deployed, so that the bindings "
-"exist in the system before (for example) the <classname>ejb</classname> and "
-"<classname>servlet</classname> classes are loaded. This is acheived by "
-"listing the AOP file at the start of the <filename>application.xml</"
-"filename>. Other types of archives are deployed before anything else and so "
-"do not require special consideration, such as <filename>.sar</filename> and "
-"<filename>.war</filename> files."
+msgid "In the JBoss Enterprise Application Platform 5, the contents of the <filename>.ear</filename> file are deployed in the order they are listed in the <filename>application.xml</filename>. When using loadtime weaving the bindings listed in the <filename>example.aop</filename> file must be deployed before the classes being advised are deployed, so that the bindings exist in the system before (for example) the <classname>ejb</classname> and <classname>servlet</classname> classes are loaded. This is acheived by listing the AOP file at the start of the <filename>application.xml</filename>. Other types of archives are deployed before anything else and so do not require special consideration, such as <filename>.sar</filename> and <filename>.war</filename> files."
msgstr ""
#. Tag: title
@@ -463,89 +273,52 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The <classname>AspectManager</classname> Service can be managed at runtime "
-"using the JMX console, which is found at <filename>http://localhost:8080/jmx-"
-"console</filename>. It is registered under the ObjectName <literal>jboss.aop:"
-"service=AspectManager</literal>. If you want to configure it on startup you "
-"need to edit some configuration files."
+msgid "The <classname>AspectManager</classname> Service can be managed at runtime using the JMX console, which is found at <filename>http://localhost:8080/jmx-console</filename>. It is registered under the ObjectName <literal>jboss.aop:service=AspectManager</literal>. If you want to configure it on startup you need to edit some configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"In JBoss Enterprise Application Platform 5 the <classname>AspectManager</"
-"classname> Service is configured using a JBoss Microcontainer bean. The "
-"configuration file is <filename>jboss-as/server/xxx/conf/bootstrap/aop.xml</"
-"filename>. The <classname>AspectManager</classname> Service is deployed with "
-"the following XML:"
+msgid "In JBoss Enterprise Application Platform 5 the <classname>AspectManager</classname> Service is configured using a JBoss Microcontainer bean. The configuration file is <filename>jboss-as/server/xxx/conf/bootstrap/aop.xml</filename>. The <classname>AspectManager</classname> Service is deployed with the following XML:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Later we will talk about changing the class of the <classname>AspectManager</"
-"classname> Service. To do this, replace the contents of the <varname>class</"
-"varname> attribute of the <classname>bean</classname> element."
+msgid "Later we will talk about changing the class of the <classname>AspectManager</classname> Service. To do this, replace the contents of the <varname>class</varname> attribute of the <classname>bean</classname> element."
msgstr ""
#. Tag: title
#, fuzzy, no-c-format
-msgid ""
-"Loadtime transformation in the JBoss Enterprise Application Platform Using "
-"Sun JDK"
+msgid "Loadtime transformation in the JBoss Enterprise Application Platform Using Sun JDK"
msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
#. Tag: para
#, no-c-format
-msgid ""
-"The JBoss Enterprise Application Platform has special integration with JDK "
-"to do loadtime transformations. This section explains how to use it."
+msgid "The JBoss Enterprise Application Platform has special integration with JDK to do loadtime transformations. This section explains how to use it."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"If you want to do load-time transformations with JBoss Enterprise "
-"Application Platform 5 and Sun JDK, these are the steps you must take."
+msgid "If you want to do load-time transformations with JBoss Enterprise Application Platform 5 and Sun JDK, these are the steps you must take."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Set the <varname>enableLoadtimeWeaving</varname> attribute/property to "
-"<literal>true</literal>. By default, JBoss Application Server will not do "
-"load-time bytecode manipulation of AOP files unless this is set. If "
-"<varname>suppressTransformationErrors</varname> is <literal>true</literal>, "
-"failed bytecode transformation will only give an error warning. This flag is "
-"needed because sometimes a JBoss deployment will not include all of the "
-"classes referenced."
+msgid "Set the <varname>enableLoadtimeWeaving</varname> attribute/property to <literal>true</literal>. By default, JBoss Application Server will not do load-time bytecode manipulation of AOP files unless this is set. If <varname>suppressTransformationErrors</varname> is <literal>true</literal>, failed bytecode transformation will only give an error warning. This flag is needed because sometimes a JBoss deployment will not include all of the classes referenced."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Copy the <filename>pluggable-instrumentor.jar</filename> from the "
-"<filename>lib/</filename> directory of your JBoss AOP distribution to the "
-"<filename>bin/</filename> directory of your JBoss Enterprise Application "
-"Platform."
+msgid "Copy the <filename>pluggable-instrumentor.jar</filename> from the <filename>lib/</filename> directory of your JBoss AOP distribution to the <filename>bin/</filename> directory of your JBoss Enterprise Application Platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Next edit <filename>run.sh</filename> or <literal>run.bat</literal> "
-"(depending on what OS you're on) and add the following to the "
-"<varname>JAVA_OPTS</varname> environment variable:"
+msgid "Next edit <filename>run.sh</filename> or <literal>run.bat</literal> (depending on what OS you're on) and add the following to the <varname>JAVA_OPTS</varname> environment variable:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"The class of the AspectManager Service must be <literal>org.jboss.aop."
-"deployers.AspectManagerJDK5</literal> or <literal>org.jboss.aop.deployment."
-"AspectManagerServiceJDK5</literal> as these are what work with the <code>-"
-"javaagent</code> option."
+msgid "The class of the AspectManager Service must be <literal>org.jboss.aop.deployers.AspectManagerJDK5</literal> or <literal>org.jboss.aop.deployment.AspectManagerServiceJDK5</literal> as these are what work with the <code>-javaagent</code> option."
msgstr ""
#. Tag: title
@@ -555,71 +328,37 @@
#. Tag: para
#, no-c-format
-msgid ""
-"JRockit also supports the <code>-javaagent</code> switch mentioned in <xref "
-"linkend=\"running-as-sun-jdk\" />. If you wish to use that, then the steps "
-"in <xref linkend=\"running-as-sun-jdk\" /> are sufficient. However, JRockit "
-"also comes with its own framework for intercepting when classes are loaded, "
-"which might be faster than the <code>-javaagent</code> switch. If you want "
-"to do load-time transformations using the special JRockit hooks, these are "
-"the steps you must take."
+msgid "JRockit also supports the <code>-javaagent</code> switch mentioned in <xref linkend=\"running-as-sun-jdk\" />. If you wish to use that, then the steps in <xref linkend=\"running-as-sun-jdk\" /> are sufficient. However, JRockit also comes with its own framework for intercepting when classes are loaded, which might be faster than the <code>-javaagent</code> switch. If you want to do load-time transformations using the special JRockit hooks, these are the steps you must take."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Set the <literal>enableLoadtimeWeaving</literal> attribute/property to true. "
-"By default, JBoss Enterprise Application Platform will not do load-time "
-"bytecode manipulation of AOP files unless this is set. If "
-"<varname>suppressTransformationErrors</varname> is <literal>true</literal>, "
-"failed bytecode transformation will only give an error warning. This flag is "
-"needed because sometimes a JBoss deployment will not include all the classes "
-"referenced."
+msgid "Set the <literal>enableLoadtimeWeaving</literal> attribute/property to true. By default, JBoss Enterprise Application Platform will not do load-time bytecode manipulation of AOP files unless this is set. If <varname>suppressTransformationErrors</varname> is <literal>true</literal>, failed bytecode transformation will only give an error warning. This flag is needed because sometimes a JBoss deployment will not include all the classes referenced."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Copy the <filename>jrockit-pluggable-instrumentor.jar</filename> from the "
-"<filename>lib/</filename> directory of your JBoss AOP distribution to the "
-"<filename>bin/</filename> directory of your the JBoss Enterprise Application "
-"Platform installation."
+msgid "Copy the <filename>jrockit-pluggable-instrumentor.jar</filename> from the <filename>lib/</filename> directory of your JBoss AOP distribution to the <filename>bin/</filename> directory of your the JBoss Enterprise Application Platform installation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Next edit <filename>run.sh</filename> or <filename>run.bat</filename> "
-"(depending on what OS you're on) and add the following to the "
-"<varname>JAVA_OPTS</varname> and <varname>JBOSS_CLASSPATH</varname> "
-"environment variables:"
+msgid "Next edit <filename>run.sh</filename> or <filename>run.bat</filename> (depending on what OS you're on) and add the following to the <varname>JAVA_OPTS</varname> and <varname>JBOSS_CLASSPATH</varname> environment variables:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Set the class of the <classname>AspectManager</classname> Service to "
-"<literal>org.jboss.aop.deployers.AspectManagerJRockit</literal> on JBoss "
-"Enterprise Application Platform 5, or <literal>org.jboss.aop.deployment."
-"AspectManagerService</literal> as these are what work with special hooks in "
-"JRockit."
+msgid "Set the class of the <classname>AspectManager</classname> Service to <literal>org.jboss.aop.deployers.AspectManagerJRockit</literal> on JBoss Enterprise Application Platform 5, or <literal>org.jboss.aop.deployment.AspectManagerService</literal> as these are what work with special hooks in JRockit."
msgstr ""
#. Tag: title
#, fuzzy, no-c-format
-msgid ""
-"Improving Loadtime Performance in the JBoss Enterprise Application Platform "
-"Environment"
+msgid "Improving Loadtime Performance in the JBoss Enterprise Application Platform Environment"
msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
#. Tag: para
#, no-c-format
-msgid ""
-"The same rules apply to the JBoss Enterprise Application Platform for tuning "
-"loadtime weaving performance as standalone Java. Switches such as pruning, "
-"optimized, include and exclude are configured through the <filename>jboss-5."
-"x.x.GA/server/xxx/conf/aop.xml</filename> file talked about earlier in this "
-"chapter."
+msgid "The same rules apply to the JBoss Enterprise Application Platform for tuning loadtime weaving performance as standalone Java. Switches such as pruning, optimized, include and exclude are configured through the <filename>jboss-5.x.x.GA/server/xxx/conf/aop.xml</filename> file talked about earlier in this chapter."
msgstr ""
#. Tag: title
@@ -629,13 +368,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"By default all deployments in JBoss are global to the whole application "
-"server. That means that any EAR, SAR, or JAR (for example), that is put in "
-"the deploy directory can see the classes from any other deployed archive. "
-"Similarly, AOP bindings are global to the whole virtual machine. This "
-"<emphasis>global</emphasis> visibility can be turned off per top-level "
-"deployment."
+msgid "By default all deployments in JBoss are global to the whole application server. That means that any EAR, SAR, or JAR (for example), that is put in the deploy directory can see the classes from any other deployed archive. Similarly, AOP bindings are global to the whole virtual machine. This <emphasis>global</emphasis> visibility can be turned off per top-level deployment."
msgstr ""
#. Tag: title
@@ -645,18 +378,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The following process may change in future versions of JBoss AOP. If you "
-"deploy an AOP file as part of a scoped archive, the bindings (for instance) "
-"applied within the <filename>.aop/META-INF/jboss-aop.xml</filename> file "
-"will only apply to the classes within the scoped archive and not to anything "
-"else in the application server. Another alternative is to deploy <filename>-"
-"aop.xml</filename> files as part of a service archive (SAR). Again, if the "
-"SAR is scoped, the bindings contained in the <filename>-aop.xml</filename> "
-"files will only apply to the contents of the SAR file. It is not currently "
-"possible to deploy a standalone <filename>-aop.xml</filename> file and have "
-"that attach to a scoped deployment. Standalone <filename>-aop.xml</filename> "
-"files will apply to classes in the whole application server."
+msgid "The following process may change in future versions of JBoss AOP. If you deploy an AOP file as part of a scoped archive, the bindings (for instance) applied within the <filename>.aop/META-INF/jboss-aop.xml</filename> file will only apply to the classes within the scoped archive and not to anything else in the application server. Another alternative is to deploy <filename>-aop.xml</filename> files as part of a service archive (SAR). Again, if the SAR is scoped, the bindings contained in the <filename>-aop.xml</filename> files will only apply to the contents of the SAR file. It is not currently possible to deploy a standalone <filename>-aop.xml</filename> file and have that attach to a scoped deployment. Standalone <filename>-aop.xml</filename> files will apply to classes in the whole application server."
msgstr ""
#. Tag: title
@@ -666,27 +388,16 @@
#. Tag: para
#, no-c-format
-msgid ""
-"If you have an application that uses classloader isolation, as long as you "
-"have prepared your classes, you can later attach an AOP file to that "
-"deployment. If we have an EAR file scoped using a <filename>jboss-app.xml</"
-"filename> file, with the scoped loader repository <literal>jboss.test:"
-"service=scoped</literal>:"
+msgid "If you have an application that uses classloader isolation, as long as you have prepared your classes, you can later attach an AOP file to that deployment. If we have an EAR file scoped using a <filename>jboss-app.xml</filename> file, with the scoped loader repository <literal>jboss.test:service=scoped</literal>:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"We can later deploy an AOP file containing aspects and configuration to "
-"attach that deployment to the scoped EAR. This is done using the "
-"<literal>loader-repository</literal> tag in the AOP file's <filename>META-"
-"INF/jboss-aop.xml</filename> file."
+msgid "We can later deploy an AOP file containing aspects and configuration to attach that deployment to the scoped EAR. This is done using the <literal>loader-repository</literal> tag in the AOP file's <filename>META-INF/jboss-aop.xml</filename> file."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"This has the same effect as deploying the AOP file as part of the EAR as we "
-"saw previously, but allows you to hot deploy aspects into your scoped "
-"application."
+msgid "This has the same effect as deploying the AOP file as part of the EAR as we saw previously, but allows you to hot deploy aspects into your scoped application."
msgstr ""
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Web_Services.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Web_Services.po 2010-04-30 00:47:57 UTC (rev 104352)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Web_Services.po 2010-04-30 01:27:27 UTC (rev 104353)
@@ -33,7 +33,7 @@
"to each other."
msgstr ""
"Web 服务是目前 Web 业务的一个关键因素。Web 服务让应用程序可以通过彼此发送数据"
-"来进行通讯。"
+" 来进行通讯。"
#. Tag: para
#, no-c-format
More information about the jboss-cvs-commits
mailing list