[jboss-cvs] JBossAS SVN: r101212 - 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
Sun Feb 21 18:32:26 EST 2010
Author: xhuang at jboss.com
Date: 2010-02-21 18:32:25 -0500 (Sun, 21 Feb 2010)
New Revision: 101212
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/What_This_Book_Covers.po
Log:
update
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-02-21 21:37:03 UTC (rev 101211)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Web_Services.po 2010-02-21 23:32:25 UTC (rev 101212)
@@ -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-22 09:24+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"
@@ -22,14 +22,14 @@
msgstr "Web 服务"
#. Tag: secondary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "web services"
-msgstr "Web 服务"
+msgstr "Web 服务 "
#. Tag: primary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBossWS"
-msgstr "JBossQL "
+msgstr "JBossWS"
#. Tag: primary
#, no-c-format
@@ -38,66 +38,32 @@
#. Tag: indexterm
#, no-c-format
-msgid ""
-"Web services are a key contributing factor in the way Web commerce is "
-"conducted today. Web services enable applications to communicate by sending "
-"small and large chunks of data to each other."
+msgid "Web services are a key contributing factor in the way Web commerce is conducted today. Web services enable applications to communicate by sending small and large chunks of data to each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"A web service is essentially a software application that supports "
-"interaction of applications over a computer network or the world wide web. "
-"Web services usually interact through XML documents that map to an object, "
-"computer program, business process or database. To communicate, an "
-"application sends a message in XML document format to a web service which "
-"sends this message to the respective programs. Responses may be received "
-"based on requirements, the web service receives and then sends them in XML "
-"document format to the required program or applications. Web services can be "
-"used in many ways, examples include supply chain information management and "
-"business integration."
+msgid "A web service is essentially a software application that supports interaction of applications over a computer network or the world wide web. Web services usually interact through XML documents that map to an object, computer program, business process or database. To communicate, an application sends a message in XML document format to a web service which sends this message to the respective programs. Responses may be received based on requirements, the web service receives and then sends them in XML document format to the required program or applications. Web services can be used in many ways, examples include supply chain information management and business integration."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"JBossWS is a web service framework included as part of the JBoss Enterprise "
-"Application Platform. It implements the JAX-WS specification that defines a "
-"programming model and run-time architecture for implementing web services in "
-"Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5). Even "
-"though JAX-RPC is still supported (the web service specification for J2EE "
-"1.4), JBossWS does put a clear focus on JAX-WS."
+msgid "JBossWS is a web service framework included as part of the JBoss Enterprise Application Platform. It implements the JAX-WS specification that defines a programming model and run-time architecture for implementing web services in Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5). Even though JAX-RPC is still supported (the web service specification for J2EE 1.4), JBossWS does put a clear focus on JAX-WS."
msgstr ""
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The need for web services"
-msgstr "定时器服务"
+msgstr "对 Web 服务的需求"
#. Tag: para
#, no-c-format
-msgid ""
-"Enterprise systems communication may benefit from a wise adoption of web "
-"service technologies. Focusing attention on well designed contracts allows "
-"developers to establish an abstract view of their service capabilities. "
-"Considering the standardized way contracts are written, this definitely "
-"helps communication with third-party systems and eventually supports "
-"business-to-business integration; everything is clear and standardized in "
-"the contract the provider and consumer agree on. This also reduces the "
-"dependencies between implementations allowing other consumers to easily use "
-"the provided service without major changes."
+msgid "Enterprise systems communication may benefit from a wise adoption of web service technologies. Focusing attention on well designed contracts allows developers to establish an abstract view of their service capabilities. Considering the standardized way contracts are written, this definitely helps communication with third-party systems and eventually supports business-to-business integration; everything is clear and standardized in the contract the provider and consumer agree on. This also reduces the dependencies between implementations allowing other consumers to easily use the provided service without major changes."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Other benefits exist for enterprise systems that incorporate web service "
-"technologies for internal heterogenous subsystems communication as web "
-"service interoperability boosts service reuse and composition. Web services "
-"eliminates the need to rewrite whole functionalities because they were "
-"developed by another enterprise department using a different software "
-"language."
+msgid "Other benefits exist for enterprise systems that incorporate web service technologies for internal heterogenous subsystems communication as web service interoperability boosts service reuse and composition. Web services eliminates the need to rewrite whole functionalities because they were developed by another enterprise department using a different software language."
msgstr ""
#. Tag: title
@@ -107,28 +73,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Web services are not the solution for every software system communication."
+msgid "Web services are not the solution for every software system communication."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Nowadays they are meant to be used for loosely-coupled coarse-grained "
-"communication, message (document) exchange. Recent times has seen many "
-"specifications (WS-*) discussed and finally approved to establish "
-"standardized ws-related advanced aspects, including reliable messaging, "
-"message-level security and cross-service transactions. Web service "
-"specifications also include the notion of registries to collect service "
-"contract references, to easily discover service implementations."
+msgid "Nowadays they are meant to be used for loosely-coupled coarse-grained communication, message (document) exchange. Recent times has seen many specifications (WS-*) discussed and finally approved to establish standardized ws-related advanced aspects, including reliable messaging, message-level security and cross-service transactions. Web service specifications also include the notion of registries to collect service contract references, to easily discover service implementations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"This all means that the web services technology platform suits complex "
-"enterprise communication and is not simply the latest way of doing remote "
-"procedure calls."
+msgid "This all means that the web services technology platform suits complex enterprise communication and is not simply the latest way of doing remote procedure calls."
msgstr ""
#. Tag: title
@@ -138,29 +93,13 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"With document style web services two business partners agree on the exchange "
-"of complex business documents that are well defined in XML schema. For "
-"example, one party sends a document describing a purchase order, the other "
-"responds (immediately or later) with a document that describes the status of "
-"the purchase order. The payload of the SOAP message is an XML document that "
-"can be validated against XML schema. The document is defined by the style "
-"attribute on the SOAP binding."
-msgstr ""
-"对于文档类型的 Web 服务而言，两个商业伙伴同意交换以 XML 模式定义的复杂商业文"
-"档。例如，一方发送描述采购订单的文档，而另一方以描述订单状态的文档进行响应"
-"（立即或以后）。它们都不需要对底层的细节达成协议，如操作名称和相关的参数。"
-"SOAP 消息是一个可以根据 XML 模式进行校验的 XML 文档。文档通过 SOAP 绑定的 "
-"style 属性来定义。 "
+msgid "With document style web services two business partners agree on the exchange of complex business documents that are well defined in XML schema. For example, one party sends a document describing a purchase order, the other responds (immediately or later) with a document that describes the status of the purchase order. The payload of the SOAP message is an XML document that can be validated against XML schema. The document is defined by the style attribute on the SOAP binding."
+msgstr "对于文档类型的 Web 服务而言，两个商业伙伴同意交换以 XML 模式定义的复杂商业文档。例如，一方发送描述采购订单的文档，而另一方以描述订单状态的文档进行响应（立即或以后）。它们都不需要对底层的细节达成协议，如操作名称和相关的参数。SOAP 消息是一个可以根据 XML 模式进行校验的 XML 文档。文档通过 SOAP 绑定的 style 属性来定义。 "
#. Tag: para
#, no-c-format
-msgid ""
-"With document style web services the payload of every message is defined by "
-"a complex type in XML schema."
-msgstr ""
-"对于文档类型的 Web 服务而言，每条消息的负荷根据 XML 模式里的一个复杂类型来定"
-"义。 "
+msgid "With document style web services the payload of every message is defined by a complex type in XML schema."
+msgstr "对于文档类型的 Web 服务而言，每条消息的负荷根据 XML 模式里的一个复杂类型来定义。 "
#. Tag: para
#, no-c-format
@@ -179,21 +118,12 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Bare is an implementation detail from the Java domain. Neither in the "
-"abstract contract (for instance, wsdl+schema) nor at the SOAP message level "
-"is a bare endpoint recognizable. A bare endpoint or client uses a Java bean "
-"that represents the entire document payload."
-msgstr ""
-"Bare 是基于 Java 域的实现细节。Bare endpoint 既不识别 abstract contract（也就"
-"是 wsdl+schema）也不识别 SOAP 消息。Bare endpoint 或客户使用代表整个文档负荷"
-"的 Java Bean。 "
+msgid "Bare is an implementation detail from the Java domain. Neither in the abstract contract (for instance, wsdl+schema) nor at the SOAP message level is a bare endpoint recognizable. A bare endpoint or client uses a Java bean that represents the entire document payload."
+msgstr "Bare 是基于 Java 域的实现细节。Bare endpoint 既不识别 abstract contract（也就是 wsdl+schema）也不识别 SOAP 消息。Bare endpoint 或客户使用代表整个文档负荷的 Java Bean。 "
#. Tag: para
#, no-c-format
-msgid ""
-"The trick is that the Java beans representing the payload contain JAXB "
-"annotations that define how the payload is represented on the wire."
+msgid "The trick is that the Java beans representing the payload contain JAXB annotations that define how the payload is represented on the wire."
msgstr "通常代表负荷的 Java bean 包含 JAXB 注解，定义如何表示这种负荷。 "
#. Tag: title
@@ -203,22 +133,12 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Wrapped is an implementation detail from the Java domain. Neither in the "
-"abstract contract (for instance, wsdl+schema) nor at the SOAP message level "
-"is a wrapped endpoint recognizable. A wrapped endpoint or client uses the "
-"individual document payload properties. Wrapped is the default and does not "
-"have to be declared explicitly."
-msgstr ""
-"Bare 是基于 Java 域的实现细节。Bare endpoint 既不识别 abstract contract（也就"
-"是 wsdl+schema）也不识别 SOAP 消息。Bare endpoint 或客户使用代表整个文档负荷"
-"的 Java Bean。 "
+msgid "Wrapped is an implementation detail from the Java domain. Neither in the abstract contract (for instance, wsdl+schema) nor at the SOAP message level is a wrapped endpoint recognizable. A wrapped endpoint or client uses the individual document payload properties. Wrapped is the default and does not have to be declared explicitly."
+msgstr "Bare 是基于 Java 域的实现细节。Bare endpoint 既不识别 abstract contract（也就是 wsdl+schema）也不识别 SOAP 消息。Bare endpoint 或客户使用代表整个文档负荷的 Java Bean。 "
#. Tag: para
#, no-c-format
-msgid ""
-"With JBossWS the request and response wrapper annotations are not required, "
-"they will be generated on demand using sensible defaults."
+msgid "With JBossWS the request and response wrapper annotations are not required, they will be generated on demand using sensible defaults."
msgstr ""
#. Tag: title
@@ -228,10 +148,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"With RPC there is a wrapper element that names the endpoint operation. Child "
-"elements of the RPC parent are the individual parameters. The SOAP body is "
-"constructed based on some simple rules:"
+msgid "With RPC there is a wrapper element that names the endpoint operation. Child elements of the RPC parent are the individual parameters. The SOAP body is constructed based on some simple rules:"
msgstr ""
#. Tag: para
@@ -251,9 +168,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"With RPC style web services the portType names the operation (i.e. the java "
-"method on the endpoint)"
+msgid "With RPC style web services the portType names the operation (i.e. the java method on the endpoint)"
msgstr ""
#. Tag: para
@@ -263,17 +178,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"There is no complex type in XML schema that could validate the entire SOAP "
-"message payload."
+msgid "There is no complex type in XML schema that could validate the entire SOAP message payload."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"The element names of RPC parameters/return values may be defined using the "
-"JAX-WS Annotations#javax.jws.WebParam and JAX-WS Annotations#javax.jws."
-"WebResult respectively."
+msgid "The element names of RPC parameters/return values may be defined using the JAX-WS Annotations#javax.jws.WebParam and JAX-WS Annotations#javax.jws.WebResult respectively."
msgstr ""
#. Tag: title
@@ -283,28 +193,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"SOAP encodeding style is defined by the infamous <ulink url=\"http://www.w3."
-"org/TR/2000/NOTE-SOAP-20000508/#_Toc478383512\">chapter 5</ulink> of the "
-"<ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/\">SOAP-1.1</"
-"ulink> specification. It has inherent interoperability issues that cannot be "
-"fixed. The <ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-"
-"04-16.html\">Basic Profile-1.0</ulink> prohibits this encoding style in "
-"<ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16."
-"html#refinement16448072\">4.1.7 SOAP encodingStyle Attribute</ulink>. "
-"JBossWS has basic support for RPC/Encoded that is provided as is for simple "
-"interop scenarios with SOAP stacks that do not support literal encoding. "
-"Specifically, JBossWS does not support:-"
-msgstr ""
-"SOAP 编码风格是由 <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"
-"\">SOAP-1.1</ulink> 规格的 <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-"
-"20000508/#_Toc478383512\">chapter 5</ulink> 定义的。它天生具有互用性的问题而"
-"无法解决。<ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-"
-"16.html\">Basic Profile-1.0</ulink> 禁止 <ulink url=\"http://www.ws-i.org/"
-"Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072\">4.1.7 SOAP "
-"encodingStyle Attribute</ulink> 里的这个编码风格。JBossWS 具有对 rpc/encoded "
-"的基本支持，它作为简单的带有不支持 literal 编码的 SOAP 栈的互用模式。特别是，"
-"JBossWS 不支持："
+msgid "SOAP encodeding style is defined by the infamous <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383512\">chapter 5</ulink> of the <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/\">SOAP-1.1</ulink> specification. It has inherent interoperability issues that cannot be fixed. The <ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html\">Basic Profile-1.0</ulink> prohibits this encoding style in <ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072\">4.1.7 SOAP encodingStyle Attribute</ulink>. JBossWS has basic support for RPC/Encoded that is provided as is for simple interop scenarios with SOAP stacks that do not support literal encoding. Specifically, JBossWS does not support:-"
+msgstr "SOAP 编码风格是由 <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/\">SOAP-1.1</ulink> 规格的 <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383512\">chapter 5</ulink> 定义的。它天生具有互用性的问题而无法解决。<ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html\">Basic Profile-1.0</ulink> 禁止 <ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072\">4.1.7 SOAP encodingStyle Attribute</ulink> 里的这个编码风格。JBossWS 具有对 rpc/encoded 的基本支持，它作为简单的带有不支持 literal 编码的 SOAP 栈的互用模式。特别是，JBossWS 不支持："
#. Tag: para
#, no-c-format
@@ -323,16 +213,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"JAX-WS simplifies the development model for a web service endpoint a great "
-"deal. In short, an endpoint implementation bean is annotated with JAX-WS "
-"annotations and deployed to the server. The server automatically generates "
-"and publishes the abstract contract (for instance, wsdl+schema) for client "
-"consumption. All marshalling/unmarshalling is delegated to JAXB."
-msgstr ""
-"JAX-WS 简化了 web 服务端点的部署模式，端点实现 bean 用 JAX-WS 进行注解并部署"
-"到服务器里。服务器自动地生成和发布用于客户消费的抽象合约（也就是 wsdl"
-"+schema）。所有的 marshalling/unmarshalling 都委托给了 JAXB [2]。"
+msgid "JAX-WS simplifies the development model for a web service endpoint a great deal. In short, an endpoint implementation bean is annotated with JAX-WS annotations and deployed to the server. The server automatically generates and publishes the abstract contract (for instance, wsdl+schema) for client consumption. All marshalling/unmarshalling is delegated to JAXB."
+msgstr "JAX-WS 简化了 web 服务端点的部署模式，端点实现 bean 用 JAX-WS 进行注解并部署到服务器里。服务器自动地生成和发布用于客户消费的抽象合约（也就是 wsdl+schema）。所有的 marshalling/unmarshalling 都委托给了 JAXB [2]。"
#. Tag: title
#, no-c-format
@@ -341,12 +223,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Let us take a look at simple POJO endpoint implementation. All endpoint "
-"associated metadata are provided via JSR-181 annotations"
-msgstr ""
-"让我们看一个简单的 POJO 终端实现。所有和终端相关的元数据由 JSR-181 注解来提"
-"供。"
+msgid "Let us take a look at simple POJO endpoint implementation. All endpoint associated metadata are provided via JSR-181 annotations"
+msgstr "让我们看一个简单的 POJO 终端实现。所有和终端相关的元数据由 JSR-181 注解来提供。"
#. Tag: title
#, no-c-format
@@ -365,16 +243,12 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"A JSR-181 java service endpoint (JSE) is packaged as a web application in a "
-"<filename>*.war</filename> file."
+msgid "A JSR-181 java service endpoint (JSE) is packaged as a web application in a <filename>*.war</filename> file."
msgstr "JAX-WS java 服务终端被部署为 web 应用程序。"
#. Tag: para
#, no-c-format
-msgid ""
-"Only the endpoint implementation bean and <filename>web.xml</filename> file "
-"are required."
+msgid "Only the endpoint implementation bean and <filename>web.xml</filename> file are required."
msgstr ""
#. Tag: title
@@ -384,25 +258,13 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"A successfully deployed service endpoint will show up in the service "
-"endpoint manager. This is also where you find the links to the generated "
-"WSDL."
-msgstr ""
-"成功部署的服务终端将出现在服务终端管理者里。这饿里也是你找到所生成的 wsdl 的"
-"链接的地方。"
+msgid "A successfully deployed service endpoint will show up in the service endpoint manager. This is also where you find the links to the generated WSDL."
+msgstr "成功部署的服务终端将出现在服务终端管理者里。这饿里也是你找到所生成的 wsdl 的链接的地方。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"It is also possible to generate the abstract contract off line using jboss "
-"tools. For details of that see <ulink url=\"http://www.jboss.org/community/"
-"wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume\">#Top Down (Using "
-"wsconsume)</ulink>"
-msgstr ""
-"请注意，用 jbossw 工具生成离线抽象合约（abstract contract）也是可能的。相关细"
-"节请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Top_Down_.28Java_to_WSDL.29\">#Top Down (Java to WSDL)</ulink>"
+msgid "It is also possible to generate the abstract contract off line using jboss tools. For details of that see <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume\">#Top Down (Using wsconsume)</ulink>"
+msgstr "请注意，用 jbossw 工具生成离线抽象合约（abstract contract）也是可能的。相关细节请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Top_Down_.28Java_to_WSDL.29\">#Top Down (Java to WSDL)</ulink>"
#. Tag: title
#, no-c-format
@@ -411,54 +273,28 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The JAX-WS programming model support the same set of annotations on EJB3 "
-"stateless session beans as on <ulink url=\"http://www.jboss.org/community/"
-"wiki/JBossWS-UserGuide#Plain_old_Java_Object_POJO\"># Plain old Java Object "
-"(POJO)</ulink> endpoints. EJB-2.1 endpoints are supported using the JAX-RPC "
-"progamming model."
-msgstr ""
-"JAX-WS 编程模型支持和 <ulink url=\"http://jbws.dyndns.org/mediawiki/index."
-"php?title=JAX-WS_User_Guide#_Plain_old_Java_Object_.28POJO.29\"># Plain old "
-"Java Object (POJO)</ulink> 终端上相同的 EJB3 stateless session bean 的注解集"
-"合。EJB-2.1 终端可用 JAX-RPC 编程模型来支持。"
+msgid "The JAX-WS programming model support the same set of annotations on EJB3 stateless session beans as on <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-UserGuide#Plain_old_Java_Object_POJO\"># Plain old Java Object (POJO)</ulink> endpoints. EJB-2.1 endpoints are supported using the JAX-RPC progamming model."
+msgstr "JAX-WS 编程模型支持和 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#_Plain_old_Java_Object_.28POJO.29\"># Plain old Java Object (POJO)</ulink> 终端上相同的 EJB3 stateless session bean 的注解集合。EJB-2.1 终端可用 JAX-RPC 编程模型来支持。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Above you see an EJB-3.0 stateless session bean that exposes one method both "
-"on the remote interface and as an endpoint operation."
-msgstr ""
-"在上面你看到的是在远程接口和端点操作上开放方法的 EJB-3.0 stateless session "
-"bean。"
+msgid "Above you see an EJB-3.0 stateless session bean that exposes one method both on the remote interface and as an endpoint operation."
+msgstr "在上面你看到的是在远程接口和端点操作上开放方法的 EJB-3.0 stateless session bean。"
#. Tag: para
#, no-c-format
-msgid ""
-"A JSR-181 EJB service endpoint is packaged as an ordinary ejb deployment."
+msgid "A JSR-181 EJB service endpoint is packaged as an ordinary ejb deployment."
msgstr "JSR-181 EJB 服务终端作为普通的 EJB 部署文件打包。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"A successfully deployed service endpoint will show up in the service "
-"endpoint manager. This is also where you will find the links to the "
-"generated WSDL."
-msgstr ""
-"成功部署的服务终端将出现在服务终端管理者里。这饿里也是你找到所生成的 wsdl 的"
-"链接的地方。"
+msgid "A successfully deployed service endpoint will show up in the service endpoint manager. This is also where you will find the links to the generated WSDL."
+msgstr "成功部署的服务终端将出现在服务终端管理者里。这饿里也是你找到所生成的 wsdl 的链接的地方。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"It is also possible to generate the abstract contract offline using JbossWS "
-"tools. For details of that please see <ulink url=\"http://www.jboss.org/"
-"community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume\">#Top Down "
-"(Using wsconsume)</ulink>"
-msgstr ""
-"请注意，用 jbossw 工具生成离线抽象合约（abstract contract）也是可能的。相关细"
-"节请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Top_Down_.28Java_to_WSDL.29\">#Top Down (Java to WSDL)</ulink>"
+msgid "It is also possible to generate the abstract contract offline using JbossWS tools. For details of that please see <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume\">#Top Down (Using wsconsume)</ulink>"
+msgstr "请注意，用 jbossw 工具生成离线抽象合约（abstract contract）也是可能的。相关细节请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Top_Down_.28Java_to_WSDL.29\">#Top Down (Java to WSDL)</ulink>"
#. Tag: title
#, no-c-format
@@ -467,43 +303,22 @@
#. Tag: para
#, no-c-format
-msgid ""
-"JAX-WS services typically implement a native Java service endpoint interface "
-"(SEI), perhaps mapped from a WSDL port type, either directly or via the use "
-"of annotations."
-msgstr ""
-"JAX-WS 服务通常实现一个原生 Java 服务端点接口（SEI），直接或通过注解映射 "
-"WSDL 端口类型。"
+msgid "JAX-WS services typically implement a native Java service endpoint interface (SEI), perhaps mapped from a WSDL port type, either directly or via the use of annotations."
+msgstr "JAX-WS 服务通常实现一个原生 Java 服务端点接口（SEI），直接或通过注解映射 WSDL 端口类型。"
#. Tag: para
#, no-c-format
-msgid ""
-"Java SEIs provide a high level Java-centric abstraction that hides the "
-"details of converting between Java objects and their XML representations for "
-"use in XML-based messages. However, in some cases it is desirable for "
-"services to be able to operate at the XML message level. The Provider "
-"interface offers an alternative to SEIs and may be implemented by services "
-"wishing to work at the XML message level."
-msgstr ""
-"Java SEI 提供一个高级别的以 Java 为中心的抽象层，它隐藏了在 Java 对象和 XML "
-"标识之间转换的细节。然而，在某些情况下，服务能够在 XML 消息级别操作是令人想要"
-"的结果。Provider 接口提供了 SEI 的替代方案且可以由希望在 XML 消息级别操作的服"
-"务来实现。"
+msgid "Java SEIs provide a high level Java-centric abstraction that hides the details of converting between Java objects and their XML representations for use in XML-based messages. However, in some cases it is desirable for services to be able to operate at the XML message level. The Provider interface offers an alternative to SEIs and may be implemented by services wishing to work at the XML message level."
+msgstr "Java SEI 提供一个高级别的以 Java 为中心的抽象层，它隐藏了在 Java 对象和 XML 标识之间转换的细节。然而，在某些情况下，服务能够在 XML 消息级别操作是令人想要的结果。Provider 接口提供了 SEI 的替代方案且可以由希望在 XML 消息级别操作的服务来实现。"
#. Tag: para
#, no-c-format
-msgid ""
-"A Provider based service instance’s invoke method is called for each message "
-"received for the service."
+msgid "A Provider based service instance’s invoke method is called for each message received for the service."
msgstr "对于每个接收的消息都会调用基于 Provider 的服务实例的 invoke 方法。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<property>Service.Mode.PAYLOAD</property> is the default and does not have "
-"to be declared explicitly. You can also use <property>Service.Mode.MESSAGE</"
-"property> to access the entire SOAP message (for example, with "
-"<property>MESSAGE</property> the Provider can also see SOAP Headers)"
+msgid "<property>Service.Mode.PAYLOAD</property> is the default and does not have to be declared explicitly. You can also use <property>Service.Mode.MESSAGE</property> to access the entire SOAP message (for example, with <property>MESSAGE</property> the Provider can also see SOAP Headers)"
msgstr "服务 服务"
#. Tag: title
@@ -513,13 +328,7 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The <classname>WebServiceContext</classname> is treated as an injectable "
-"resource that can be set at the time an endpoint is initialized. The "
-"<classname>WebServiceContext</classname> object will then use thread-local "
-"information to return the correct information regardless of how many threads "
-"are concurrently being used to serve requests addressed to the same endpoint "
-"object."
+msgid "The <classname>WebServiceContext</classname> is treated as an injectable resource that can be set at the time an endpoint is initialized. The <classname>WebServiceContext</classname> object will then use thread-local information to return the correct information regardless of how many threads are concurrently being used to serve requests addressed to the same endpoint object."
msgstr "WebServiceContext WebServiceContext."
#. Tag: title
@@ -534,23 +343,13 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<literal>Service</literal> is an abstraction that represents a WSDL service. "
-"A WSDL service is a collection of related ports, each of which consists of a "
-"port type bound to a particular protocol and available at a particular "
-"endpoint address."
+msgid "<literal>Service</literal> is an abstraction that represents a WSDL service. A WSDL service is a collection of related ports, each of which consists of a port type bound to a particular protocol and available at a particular endpoint address."
msgstr "<literal> 服务</literal>."
#. Tag: para
#, no-c-format
-msgid ""
-"For most clients, you will start with a set of stubs generated from the "
-"WSDL. One of these will be the service, and you will create objects of that "
-"class in order to work with the service (see \"static case\" below)."
-msgstr ""
-"对于大多数客户端，你将用一系列 WSDL 生成的 stub 来启动。其中一个将是 "
-"service，你会创建该类的对象并与 service 一同工作（参看下面的 \"static case"
-"\"）。"
+msgid "For most clients, you will start with a set of stubs generated from the WSDL. One of these will be the service, and you will create objects of that class in order to work with the service (see \"static case\" below)."
+msgstr "对于大多数客户端，你将用一系列 WSDL 生成的 stub 来启动。其中一个将是 service，你会创建该类的对象并与 service 一同工作（参看下面的 \"static case\"）。"
#. Tag: title
#, no-c-format
@@ -564,61 +363,28 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Most clients will start with a WSDL file, and generate some stubs using "
-"jbossws tools like <emphasis>wsconsume</emphasis>. This usually gives a mass "
-"of files, one of which is the top of the tree. This is the service "
-"implementation class."
-msgstr ""
-"大多数客户端都用 WSDL 文件启动并用 jbossws 工具（如 <emphasis>wsconsume</"
-"emphasis>）生成一些 stub。这通常产生大量的文件，其中一个位于树的顶层。这是 "
-"service 的实现类。"
+msgid "Most clients will start with a WSDL file, and generate some stubs using jbossws tools like <emphasis>wsconsume</emphasis>. This usually gives a mass of files, one of which is the top of the tree. This is the service implementation class."
+msgstr "大多数客户端都用 WSDL 文件启动并用 jbossws 工具（如 <emphasis>wsconsume</emphasis>）生成一些 stub。这通常产生大量的文件，其中一个位于树的顶层。这是 service 的实现类。"
#. Tag: para
#, no-c-format
-msgid ""
-"The generated implementation class can be recognised as it will have two "
-"public constructors, one with no arguments and one with two arguments, "
-"representing the wsdl location (a java.net.URL) and the service name (a "
-"javax.xml.namespace.QName) respectively."
-msgstr ""
-"生成的实现类可以被识别，因为它有两个属性为 public 的构造器，其中一个没有参"
-"数，另外一个带有两个参数，分别代表 WSDL 的位置（java.net.URL）和服务名称"
-"（javax.xml.namespace.QName）。"
+msgid "The generated implementation class can be recognised as it will have two public constructors, one with no arguments and one with two arguments, representing the wsdl location (a java.net.URL) and the service name (a javax.xml.namespace.QName) respectively."
+msgstr "生成的实现类可以被识别，因为它有两个属性为 public 的构造器，其中一个没有参数，另外一个带有两个参数，分别代表 WSDL 的位置（java.net.URL）和服务名称（javax.xml.namespace.QName）。"
#. Tag: para
#, no-c-format
-msgid ""
-"Usually you will use the no-argument constructor. In this case the WSDL "
-"location and service name are those found in the WSDL. These are set "
-"implicitly from the WebServiceClient annotation that decorates the generated "
-"class."
-msgstr ""
-"通常你将使用无参的构造器。在这种情况下，WSDL 位置和服务名是 WSDL 里找到的位置"
-"和服务名。它们是通过所生成的类里的 WebServiceClient 注解隐形地进行设置的。"
+msgid "Usually you will use the no-argument constructor. In this case the WSDL location and service name are those found in the WSDL. These are set implicitly from the WebServiceClient annotation that decorates the generated class."
+msgstr "通常你将使用无参的构造器。在这种情况下，WSDL 位置和服务名是 WSDL 里找到的位置和服务名。它们是通过所生成的类里的 WebServiceClient 注解隐形地进行设置的。"
#. Tag: para
#, no-c-format
-msgid ""
-"The following code snippet shows the generated constructors from the "
-"generated class:"
+msgid "The following code snippet shows the generated constructors from the generated class:"
msgstr "下面的代码片段显示了所生成的类里的构造器："
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Section <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-"
-"UserGuide#Dynamic_Proxy\">#Dynamic Proxy</ulink> explains how to obtain a "
-"port from the service and how to invoke an operation on the port. If you "
-"need to work with the XML payload directly or with the XML representation of "
-"the entire SOAP message, have a look at <ulink url=\"http://www.jboss.org/"
-"community/wiki/JBossWS-UserGuide#Dispatch\">#Dispatch</ulink>."
-msgstr ""
-"<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Dynamic_Proxy\">#Dynamic Proxy</ulink> 章节解释了如何从服务获取"
-"端口和调用该端口上的操作。如果你需要直接使用 XML payload 或是整个 SOAP 消息"
-"的 XML 表达式，请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index."
-"php?title=JAX-WS_User_Guide#Dispatch\">#Dispatch</ulink>。"
+msgid "Section <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-UserGuide#Dynamic_Proxy\">#Dynamic Proxy</ulink> explains how to obtain a port from the service and how to invoke an operation on the port. If you need to work with the XML payload directly or with the XML representation of the entire SOAP message, have a look at <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-UserGuide#Dispatch\">#Dispatch</ulink>."
+msgstr "<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Dynamic_Proxy\">#Dynamic Proxy</ulink> 章节解释了如何从服务获取端口和调用该端口上的操作。如果你需要直接使用 XML payload 或是整个 SOAP 消息的 XML 表达式，请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Dispatch\">#Dispatch</ulink>。"
#. Tag: title
#, no-c-format
@@ -627,10 +393,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"In the dynamic case, when nothing is generated, a web service client uses "
-"<literal>Service.create</literal> to create Service instances, the following "
-"code illustrates this process."
+msgid "In the dynamic case, when nothing is generated, a web service client uses <literal>Service.create</literal> to create Service instances, the following code illustrates this process."
msgstr "<literal> 服务</literal> 服务."
#. Tag: para
@@ -645,30 +408,12 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"JAX-WS provides a flexible plug-in framework for message processing modules, "
-"known as handlers, that may be used to extend the capabilities of a JAX-WS "
-"runtime system. <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-"
-"UserGuide#Handler_Framework\">Handler Framework</ulink> describes the "
-"handler framework in detail. A <classname>Service</classname> instance "
-"provides access to a <classname>HandlerResolver</classname> via a pair of "
-"<methodname>getHandlerResolver</methodname> and "
-"<methodname>setHandlerResolver</methodname> methods that may be used to "
-"configure a set of handlers on a per-service, per-port or per-protocol "
-"binding basis."
-msgstr ""
-"<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Handler_Framework\"></ulink> 服务."
+msgid "JAX-WS provides a flexible plug-in framework for message processing modules, known as handlers, that may be used to extend the capabilities of a JAX-WS runtime system. <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-UserGuide#Handler_Framework\">Handler Framework</ulink> describes the handler framework in detail. A <classname>Service</classname> instance provides access to a <classname>HandlerResolver</classname> via a pair of <methodname>getHandlerResolver</methodname> and <methodname>setHandlerResolver</methodname> methods that may be used to configure a set of handlers on a per-service, per-port or per-protocol binding basis."
+msgstr "<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Handler_Framework\"></ulink> 服务."
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"When a <classname>Service</classname> instance is used to create a proxy or "
-"a <classname>Dispatch</classname> instance then the handler resolver "
-"currently registered with the service is used to create the required handler "
-"chain. Subsequent changes to the handler resolver configured for a "
-"<classname>Service</classname> instance do not affect the handlers on "
-"previously created proxies, or <classname>Dispatch</classname> instances."
+msgid "When a <classname>Service</classname> instance is used to create a proxy or a <classname>Dispatch</classname> instance then the handler resolver currently registered with the service is used to create the required handler chain. Subsequent changes to the handler resolver configured for a <classname>Service</classname> instance do not affect the handlers on previously created proxies, or <classname>Dispatch</classname> instances."
msgstr "服务 服务."
#. Tag: title
@@ -678,13 +423,7 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<classname>Service</classname> instances can be configured with a "
-"<classname>java.util.concurrent.Executor</classname>. The executor will then "
-"be used to invoke any asynchronous callbacks requested by the application. "
-"The <methodname>setExecutor</methodname> and <methodname>getExecutor</"
-"methodname> methods of <classname>Service</classname> can be used to modify "
-"and retrieve the executor configured for a service."
+msgid "<classname>Service</classname> instances can be configured with a <classname>java.util.concurrent.Executor</classname>. The executor will then be used to invoke any asynchronous callbacks requested by the application. The <methodname>setExecutor</methodname> and <methodname>getExecutor</methodname> methods of <classname>Service</classname> can be used to modify and retrieve the executor configured for a service."
msgstr "服务 服务."
#. Tag: title
@@ -694,38 +433,18 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"You can create an instance of a client proxy using one of "
-"<methodname>getPort</methodname> methods on the <ulink url=\"http://java.sun."
-"com/javaee/5/docs/api/javax/xml/ws/Service.html\"><classname>Service</"
-"classname></ulink>."
-msgstr ""
-"<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Service\"> 服务</ulink>."
+msgid "You can create an instance of a client proxy using one of <methodname>getPort</methodname> methods on the <ulink url=\"http://java.sun.com/javaee/5/docs/api/javax/xml/ws/Service.html\"><classname>Service</classname></ulink>."
+msgstr "<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Service\"> 服务</ulink>."
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The <emphasis>Service Endpoint Interface</emphasis> (SEI) is usually "
-"generated using tools. For details see <ulink url=\"http://www.jboss.org/"
-"community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume\">Top Down (Using "
-"wsconsume)</ulink>."
-msgstr ""
-"服务终端接口（SEI）通常是用工具生成的。细节请参考 <ulink url=\"http://jbws."
-"dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#_Top_Down_.28WSDL_to_Java.29\"># Top Down (WSDL to Java)</"
-"ulink>"
+msgid "The <emphasis>Service Endpoint Interface</emphasis> (SEI) is usually generated using tools. For details see <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume\">Top Down (Using wsconsume)</ulink>."
+msgstr "服务终端接口（SEI）通常是用工具生成的。细节请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#_Top_Down_.28WSDL_to_Java.29\"># Top Down (WSDL to Java)</ulink>"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"A generated static <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-"
-"UserGuide#Service\"><classname>Service</classname></ulink> usually also "
-"offers typed methods to get ports. These methods also return dynamic proxies "
-"that implement the SEI."
-msgstr ""
-"<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Service\"> 服务</ulink>."
+msgid "A generated static <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-UserGuide#Service\"><classname>Service</classname></ulink> usually also offers typed methods to get ports. These methods also return dynamic proxies that implement the SEI."
+msgstr "<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Service\"> 服务</ulink>."
#. Tag: title
#, no-c-format
@@ -734,47 +453,22 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The <classname>WebServiceRef</classname> annotation is used to declare a "
-"reference to a Web service. It follows the resource pattern exemplified by "
-"the <classname>javax.annotation.Resource</classname> annotation in JSR-250 "
-"[5]"
+msgid "The <classname>WebServiceRef</classname> annotation is used to declare a reference to a Web service. It follows the resource pattern exemplified by the <classname>javax.annotation.Resource</classname> annotation in JSR-250 [5]"
msgstr "代理服务"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"There are two uses to the <classname>WebServiceRef</classname> annotation:"
+msgid "There are two uses to the <classname>WebServiceRef</classname> annotation:"
msgstr "代理服务:"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"To define a reference whose type is a generated service class. In this case, "
-"the type and value element will both refer to the generated service class "
-"type. Moreover, if the reference type can be inferred by the field or method "
-"declaration then the annotation is applied to the type, and value elements "
-"<emphasis>may</emphasis> have the default value (<classname>Object.class</"
-"classname>, that is). If the type cannot be inferred, then at least the type "
-"element <emphasis>must</emphasis> be present with a non-default value."
-msgstr ""
-"要定义类型为生成服务类的引用。在这个例子里，type 和 value 元素将引用生成服务"
-"类的类型。而且，如果引用类型可以通过 field/method 声明引用，type 和 value 元"
-"素可以有缺省值（Object.class）。如果类型不能进行推断，则至少 type 元素必须带"
-"有非缺省值。"
+msgid "To define a reference whose type is a generated service class. In this case, the type and value element will both refer to the generated service class type. Moreover, if the reference type can be inferred by the field or method declaration then the annotation is applied to the type, and value elements <emphasis>may</emphasis> have the default value (<classname>Object.class</classname>, that is). If the type cannot be inferred, then at least the type element <emphasis>must</emphasis> be present with a non-default value."
+msgstr "要定义类型为生成服务类的引用。在这个例子里，type 和 value 元素将引用生成服务类的类型。而且，如果引用类型可以通过 field/method 声明引用，type 和 value 元素可以有缺省值（Object.class）。如果类型不能进行推断，则至少 type 元素必须带有非缺省值。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"To define a reference whose type is a SEI. In this case, the type element "
-"<emphasis>may</emphasis> be present with its default value if the type of "
-"the reference can be inferred from the annotated field and method "
-"declaration, but the value element <emphasis>must</emphasis> always be "
-"present and refer to a generated service class type (a subtype of "
-"<classname>javax.xml.ws.Service</classname>). The <property>wsdlLocation</"
-"property> element, if present, overrides <property>theWSDL</property> "
-"location information specified in the <classname>WebService</classname> "
-"annotation of the referenced generated service class."
+msgid "To define a reference whose type is a SEI. In this case, the type element <emphasis>may</emphasis> be present with its default value if the type of the reference can be inferred from the annotated field and method declaration, but the value element <emphasis>must</emphasis> always be present and refer to a generated service class type (a subtype of <classname>javax.xml.ws.Service</classname>). The <property>wsdlLocation</property> element, if present, overrides <property>theWSDL</property> location information specified in the <classname>WebService</classname> annotation of the referenced generated service class."
msgstr "服务."
#. Tag: title
@@ -784,13 +478,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"In JBoss Enterprise Application Platform 5.0 we offer a number of overrides "
-"and extensions to the <classname>WebServiceRef</classname> annotation. These "
-"include:"
-msgstr ""
-"在 jboss-5.0.x 里，我们提供了大量的对 WebServiceRef 注解的覆盖和扩展理。其中"
-"包括"
+msgid "In JBoss Enterprise Application Platform 5.0 we offer a number of overrides and extensions to the <classname>WebServiceRef</classname> annotation. These include:"
+msgstr "在 jboss-5.0.x 里，我们提供了大量的对 WebServiceRef 注解的覆盖和扩展理。其中包括"
#. Tag: para
#, no-c-format
@@ -799,8 +488,7 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"define default <property>Stub</property> property settings for Stub objects"
+msgid "define default <property>Stub</property> property settings for Stub objects"
msgstr "为 Stub 对象定义缺省的 Stub 属性设置"
#. Tag: para
@@ -820,21 +508,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"XML Web Services use XML messages for communication between services and "
-"service clients. The higher level JAX-WS APIs are designed to hide the "
-"details of converting between Java method invocations and the corresponding "
-"XML messages, but in some cases operating at the XML message level is "
-"desirable. The Dispatch interface provides support for this mode of "
-"interaction."
+msgid "XML Web Services use XML messages for communication between services and service clients. The higher level JAX-WS APIs are designed to hide the details of converting between Java method invocations and the corresponding XML messages, but in some cases operating at the XML message level is desirable. The Dispatch interface provides support for this mode of interaction."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Dispatch supports two usage modes, identified by the constants "
-"<property>javax.xml.ws.Service.Mode.MESSAGE</property> and <property>javax."
-"xml.ws.Service.Mode.PAYLOAD</property> respectively:"
+msgid "Dispatch supports two usage modes, identified by the constants <property>javax.xml.ws.Service.Mode.MESSAGE</property> and <property>javax.xml.ws.Service.Mode.PAYLOAD</property> respectively:"
msgstr "服务 服务:"
#. Tag: title
@@ -844,14 +523,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"In this mode, client applications work directly with protocol-specific "
-"message structures. For example, when used with a SOAP protocol binding, a "
-"client application would work directly with a SOAP message."
-msgstr ""
-"<emphasis role=\"bold\">Message</emphasis>：在这个模式下，客户端应用程序直接"
-"处理和协议专有的消息结构，例如，当和 SOAP 协议绑定一起使用时，客户端应用程序"
-"将直接操作 SOAP 消息。"
+msgid "In this mode, client applications work directly with protocol-specific message structures. For example, when used with a SOAP protocol binding, a client application would work directly with a SOAP message."
+msgstr "<emphasis role=\"bold\">Message</emphasis>：在这个模式下，客户端应用程序直接处理和协议专有的消息结构，例如，当和 SOAP 协议绑定一起使用时，客户端应用程序将直接操作 SOAP 消息。"
#. Tag: title
#, fuzzy, no-c-format
@@ -860,27 +533,13 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"In this mode, client applications work with the payload of messages rather "
-"than the messages themselves. For example, when used with a SOAP protocol "
-"binding, a client application would work with the contents of the SOAP Body "
-"rather than the SOAP message as a whole."
-msgstr ""
-"<emphasis role=\"bold\">Message Payload</emphasis>：在这个模式下，客户端应用"
-"程序处理消息的有效负荷而不是消息本身。例如，当使用 SOAP 协议绑定时，客户端应"
-"用程序将处理 SOAP 主体的内容而不是整个 SOAP 消息。"
+msgid "In this mode, client applications work with the payload of messages rather than the messages themselves. For example, when used with a SOAP protocol binding, a client application would work with the contents of the SOAP Body rather than the SOAP message as a whole."
+msgstr "<emphasis role=\"bold\">Message Payload</emphasis>：在这个模式下，客户端应用程序处理消息的有效负荷而不是消息本身。例如，当使用 SOAP 协议绑定时，客户端应用程序将处理 SOAP 主体的内容而不是整个 SOAP 消息。"
#. Tag: para
#, no-c-format
-msgid ""
-"Dispatch is a low level API that requires clients to construct messages or "
-"message payloads as XML and requires an intimate knowledge of the desired "
-"message or payload structure. Dispatch is a generic class that supports "
-"input and output of messages or message payloads of any type."
-msgstr ""
-"Dispatch 是一个低级别的 API，它要求客户把消息或其有效负荷构建为 XML 并要求对"
-"所需的消息或有效负载结构有深入了解。Dispatch 是一个通用类，它支持任何类型的消"
-"息和有效负载的输入和输出。"
+msgid "Dispatch is a low level API that requires clients to construct messages or message payloads as XML and requires an intimate knowledge of the desired message or payload structure. Dispatch is a generic class that supports input and output of messages or message payloads of any type."
+msgstr "Dispatch 是一个低级别的 API，它要求客户把消息或其有效负荷构建为 XML 并要求对所需的消息或有效负载结构有深入了解。Dispatch 是一个通用类，它支持任何类型的消息和有效负载的输入和输出。"
#. Tag: title
#, no-c-format
@@ -889,21 +548,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The <classname>BindingProvider</classname> interface represents a component "
-"that provides a protocol binding for use by clients, it is implemented by "
-"proxies and is extended by the <classname>Dispatch</classname> interface."
+msgid "The <classname>BindingProvider</classname> interface represents a component that provides a protocol binding for use by clients, it is implemented by proxies and is extended by the <classname>Dispatch</classname> interface."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<classname>BindingProvider</classname> instances may provide asynchronous "
-"operation capabilities. When used, asynchronous operation invocations are "
-"decoupled from the <classname>BindingProvider</classname> instance at "
-"invocation time such that the response context is not updated when the "
-"operation completes. Instead a separate response context is made available "
-"using the <classname>Response</classname> interface."
+msgid "<classname>BindingProvider</classname> instances may provide asynchronous operation capabilities. When used, asynchronous operation invocations are decoupled from the <classname>BindingProvider</classname> instance at invocation time such that the response context is not updated when the operation completes. Instead a separate response context is made available using the <classname>Response</classname> interface."
msgstr ""
#. Tag: title
@@ -913,14 +563,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<property>@Oneway</property> indicates that the given web method has only an "
-"input message and no output. Typically, a one-way method returns the thread "
-"of control to the calling application prior to executing the actual business "
-"method."
-msgstr ""
-"@Oneway 指定 web 方法只有一个输入消息且没有输出。通常，oneway 方法在执行真正"
-"的商业方法之前返回控制线程到调用的应用程序。"
+msgid "<property>@Oneway</property> indicates that the given web method has only an input message and no output. Typically, a one-way method returns the thread of control to the calling application prior to executing the actual business method."
+msgstr "@Oneway 指定 web 方法只有一个输入消息且没有输出。通常，oneway 方法在执行真正的商业方法之前返回控制线程到调用的应用程序。"
#. Tag: title
#, no-c-format
@@ -929,16 +573,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"This sections describes concepts that apply equally to <ulink url=\"http://"
-"www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Endpoints\">#Web "
-"Service Endpoints</ulink> and <ulink url=\"http://www.jboss.org/community/"
-"wiki/JBossWS-UserGuide#Web_Service_Clients\">#Web Service Clients</ulink>"
-msgstr ""
-"<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Web_Service_Endpoints\"> 服务</ulink><ulink url=\"http://jbws."
-"dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Web_Service_Clients"
-"\"> 服务</ulink>"
+msgid "This sections describes concepts that apply equally to <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Endpoints\">#Web Service Endpoints</ulink> and <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Clients\">#Web Service Clients</ulink>"
+msgstr "<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Web_Service_Endpoints\"> 服务</ulink><ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Web_Service_Clients\"> 服务</ulink>"
#. Tag: title
#, no-c-format
@@ -947,38 +583,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The handler framework is implemented by a JAX-WS protocol binding in both "
-"client and server side runtimes. Proxies, and Dispatch instances, known "
-"collectively as binding providers, each use protocol bindings to bind their "
-"abstract functionality to specific protocols."
-msgstr ""
-"Handler 框架由在运行时绑定在客户和服务器端的 JAX-WS 协议实现。代理和 "
-"Dispatch 实例，被合称为绑定提供者，它们都使用协议绑定来把抽象功能绑定到特殊的"
-"协议上。"
+msgid "The handler framework is implemented by a JAX-WS protocol binding in both client and server side runtimes. Proxies, and Dispatch instances, known collectively as binding providers, each use protocol bindings to bind their abstract functionality to specific protocols."
+msgstr "Handler 框架由在运行时绑定在客户和服务器端的 JAX-WS 协议实现。代理和 Dispatch 实例，被合称为绑定提供者，它们都使用协议绑定来把抽象功能绑定到特殊的协议上。"
#. Tag: para
#, no-c-format
-msgid ""
-"Client and server-side handlers are organized into an ordered list known as "
-"a handler chain. The handlers within a handler chain are invoked each time a "
-"message is sent or received. Inbound messages are processed by handlers "
-"prior to binding provider processing. Outbound messages are processed by "
-"handlers after any binding provider processing."
-msgstr ""
-"客户和服务器端处理程序构成一个排序列表，它被称为处理程序链。链里的处理程序在"
-"每次消息被发送或接收时被调用。转入的消息在绑定提供者处理之前由处理程序进行处"
-"理。转出消息在绑定提供者处理之后才由处理程序进行处理。"
+msgid "Client and server-side handlers are organized into an ordered list known as a handler chain. The handlers within a handler chain are invoked each time a message is sent or received. Inbound messages are processed by handlers prior to binding provider processing. Outbound messages are processed by handlers after any binding provider processing."
+msgstr "客户和服务器端处理程序构成一个排序列表，它被称为处理程序链。链里的处理程序在每次消息被发送或接收时被调用。转入的消息在绑定提供者处理之前由处理程序进行处理。转出消息在绑定提供者处理之后才由处理程序进行处理。"
#. Tag: para
#, no-c-format
-msgid ""
-"Handlers are invoked with a message context that provides methods to access "
-"and modify inbound and outbound messages and to manage a set of properties. "
-"Message context properties may be used to facilitate communication between "
-"individual handlers and between handlers and client and service "
-"implementations. Different types of handlers are invoked with different "
-"types of message context."
+msgid "Handlers are invoked with a message context that provides methods to access and modify inbound and outbound messages and to manage a set of properties. Message context properties may be used to facilitate communication between individual handlers and between handlers and client and service implementations. Different types of handlers are invoked with different types of message context."
msgstr "处理程序"
#. Tag: title
@@ -988,11 +603,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Handlers that only operate on message context properties and message "
-"payloads. Logical handlers are protocol agnostic and are unable to affect "
-"protocol specific parts of a message. Logical handlers are handlers that "
-"implement <classname>javax.xml.ws.handler.LogicalHandler</classname>."
+msgid "Handlers that only operate on message context properties and message payloads. Logical handlers are protocol agnostic and are unable to affect protocol specific parts of a message. Logical handlers are handlers that implement <classname>javax.xml.ws.handler.LogicalHandler</classname>."
msgstr ""
#. Tag: title
@@ -1002,13 +613,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Handlers that operate on message context properties and protocol specific "
-"messages. Protocol handlers are specific to a particular protocol and may "
-"access and change protocol specific aspects of a message. Protocol handlers "
-"are handlers that implement any interface derived from <classname>javax.xml."
-"ws.handler.Handler</classname> except <classname>javax.xml.ws.handler."
-"LogicalHandler</classname>."
+msgid "Handlers that operate on message context properties and protocol specific messages. Protocol handlers are specific to a particular protocol and may access and change protocol specific aspects of a message. Protocol handlers are handlers that implement any interface derived from <classname>javax.xml.ws.handler.Handler</classname> except <classname>javax.xml.ws.handler.LogicalHandler</classname>."
msgstr ""
#. Tag: title
@@ -1018,9 +623,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"On the service endpoint, handlers are defined using the "
-"<property>@HandlerChain</property> annotation."
+msgid "On the service endpoint, handlers are defined using the <property>@HandlerChain</property> annotation."
msgstr ""
#. Tag: para
@@ -1030,20 +633,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"1. An absolute java.net.URL in externalForm. (ex: <ulink url=\"http://"
-"myhandlers.foo.com/handlerfile1.xml\">http://myhandlers.foo.com/handlerfile1."
-"xml</ulink>)"
-msgstr ""
-"1. externalForm 里的绝对 java.net.URL（如： <ulink url=\"http://myhandlers."
-"foo.com/handlerfile1.xml\">http://myhandlers.foo.com/handlerfile1.xml</"
-"ulink>）"
+msgid "1. An absolute java.net.URL in externalForm. (ex: <ulink url=\"http://myhandlers.foo.com/handlerfile1.xml\">http://myhandlers.foo.com/handlerfile1.xml</ulink>)"
+msgstr "1. externalForm 里的绝对 java.net.URL（如： <ulink url=\"http://myhandlers.foo.com/handlerfile1.xml\">http://myhandlers.foo.com/handlerfile1.xml</ulink>）"
#. Tag: para
#, no-c-format
-msgid ""
-"2. A relative path from the source file or class file. (ex: bar/handlerfile1."
-"xml)"
+msgid "2. A relative path from the source file or class file. (ex: bar/handlerfile1.xml)"
msgstr "2. 源文件或类文件的相对路径（如：bar/handlerfile1.xml）"
#. Tag: title
@@ -1053,13 +648,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"On the client side, handler can be configured using the "
-"<property>@HandlerChain</property> annotation on the SEI or dynamically "
-"using the API."
-msgstr ""
-"在客户端，处理程序可用 SEI 上的 @HandlerChain 注解或动态地使用 API 来进行配"
-"置。"
+msgid "On the client side, handler can be configured using the <property>@HandlerChain</property> annotation on the SEI or dynamically using the API."
+msgstr "在客户端，处理程序可用 SEI 上的 @HandlerChain 注解或动态地使用 API 来进行配置。"
#. Tag: title
#, no-c-format
@@ -1068,27 +658,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"MessageContext is the super interface for all JAX-WS message contexts. It "
-"extends Map<String,Object> with additional methods and constants to "
-"manage a set of properties that enable handlers in a handler chain to share "
-"processing related state. For example, a handler may use the put method to "
-"insert a property in the message context that one or more other handlers in "
-"the handler chain may subsequently obtain via the get method."
-msgstr ""
-"MessageContext 是所有 JAX-WS 消息上下文的 super 接口。它继承了 Map<String,"
-"Object> "
+msgid "MessageContext is the super interface for all JAX-WS message contexts. It extends Map<String,Object> with additional methods and constants to manage a set of properties that enable handlers in a handler chain to share processing related state. For example, a handler may use the put method to insert a property in the message context that one or more other handlers in the handler chain may subsequently obtain via the get method."
+msgstr "MessageContext 是所有 JAX-WS 消息上下文的 super 接口。它继承了 Map<String,Object> "
#. Tag: para
#, no-c-format
-msgid ""
-"Properties are scoped as either APPLICATION or HANDLER. All properties are "
-"available to all handlers associated with particular endpoint. E.g., if a "
-"logical handler puts a property in the message context, that property will "
-"also be available to any protocol handlers in the chain during the "
-"execution. APPLICATION scoped properties are also made available to client "
-"applications and service endpoint implementations. The default scope for a "
-"property is HANDLER."
+msgid "Properties are scoped as either APPLICATION or HANDLER. All properties are available to all handlers associated with particular endpoint. E.g., if a logical handler puts a property in the message context, that property will also be available to any protocol handlers in the chain during the execution. APPLICATION scoped properties are also made available to client applications and service endpoint implementations. The default scope for a property is HANDLER."
msgstr ""
#. Tag: title
@@ -1098,9 +673,7 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Users can access the message context in handlers or in endpoints via "
-"<literal>@WebServiceContext</literal> annotation."
+msgid "Users can access the message context in handlers or in endpoints via <literal>@WebServiceContext</literal> annotation."
msgstr "当然，我们需要一个 <literal>@WebService</literal> 注解。"
#. Tag: title
@@ -1110,16 +683,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"LogicalMessageContext is passed to <literal>Logical Handlers</literal> at "
-"invocation time. LogicalMessageContext extends MessageContext with methods "
-"to obtain and modify the message payload, it does not provide access to the "
-"protocol specific aspects of a message. A protocol binding defines what "
-"component of a message are available via a logical message context. The SOAP "
-"binding defines that a logical handler deployed in a SOAP binding can access "
-"the contents of the SOAP body but not the SOAP headers whereas the XML/HTTP "
-"binding defines that a logical handler can access the entire XML payload of "
-"a message."
+msgid "LogicalMessageContext is passed to <literal>Logical Handlers</literal> at invocation time. LogicalMessageContext extends MessageContext with methods to obtain and modify the message payload, it does not provide access to the protocol specific aspects of a message. A protocol binding defines what component of a message are available via a logical message context. The SOAP binding defines that a logical handler deployed in a SOAP binding can access the contents of the SOAP body but not the SOAP headers whereas the XML/HTTP binding defines that a logical handler can access the entire XML payload of a message."
msgstr ""
#. Tag: title
@@ -1129,10 +693,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"SOAPMessageContext is passed to <literal>SOAP handlers</literal> at "
-"invocation time. SOAPMessageContext extends MessageContext with methods to "
-"obtain and modify the SOAP message payload."
+msgid "SOAPMessageContext is passed to <literal>SOAP handlers</literal> at invocation time. SOAPMessageContext extends MessageContext with methods to obtain and modify the SOAP message payload."
msgstr ""
#. Tag: title
@@ -1157,9 +718,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"In case of the latter JBossWS generates the required fault wrapper beans at "
-"runtime if they are not part of the deployment"
+msgid "In case of the latter JBossWS generates the required fault wrapper beans at runtime if they are not part of the deployment"
msgstr ""
#. Tag: title
@@ -1174,32 +733,22 @@
#. Tag: para
#, no-c-format
-msgid ""
-"JAXB is heavily driven by Java Annotations on the Java Bindings. It "
-"currently doesn't support an external binding configuration."
+msgid "JAXB is heavily driven by Java Annotations on the Java Bindings. It currently doesn't support an external binding configuration."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"In order to support this, we built on a JAXB RI feature whereby it allows "
-"you to specify a RuntimeInlineAnnotationReader implementation during "
-"JAXBContext creation (see JAXBRIContext)."
+msgid "In order to support this, we built on a JAXB RI feature whereby it allows you to specify a RuntimeInlineAnnotationReader implementation during JAXBContext creation (see JAXBRIContext)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"We call this feature \"JAXB Annotation Introduction\" and we've made it "
-"available for general consumption i.e. it can be checked out, built and used "
-"from SVN:"
+msgid "We call this feature \"JAXB Annotation Introduction\" and we've made it available for general consumption i.e. it can be checked out, built and used from SVN:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://anonsvn.jboss.org/repos/jbossws/projects/jaxbintros/"
-"\">http://anonsvn.jboss.org/repos/jbossws/projects/jaxbintros/</ulink>"
+msgid "<ulink url=\"http://anonsvn.jboss.org/repos/jbossws/projects/jaxbintros/\">http://anonsvn.jboss.org/repos/jbossws/projects/jaxbintros/</ulink>"
msgstr ""
#. Tag: para
@@ -1209,12 +758,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JAXBIntroductions"
-"\">JAXB Introductions</ulink>"
-msgstr ""
-"关于 JBossXB 的更多信息，请参考 <ulink url=\"http://wiki.jboss.org/wiki/Wiki."
-"jsp?page=JBossXB\">JBossXB wiki page</ulink>。"
+msgid "<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JAXBIntroductions\">JAXB Introductions</ulink>"
+msgstr "关于 JBossXB 的更多信息，请参考 <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossXB\">JBossXB wiki page</ulink>。"
#. Tag: title
#, no-c-format
@@ -1223,10 +768,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"JBoss-WS4EE relied on a deprecated attachments technology called SwA (SOAP "
-"with Attachments). SwA required soap/encoding which is disallowed by the WS-"
-"I Basic Profile. JBossWS provides support for WS-I AP 1.0, and MTOM instead."
+msgid "JBoss-WS4EE relied on a deprecated attachments technology called SwA (SOAP with Attachments). SwA required soap/encoding which is disallowed by the WS-I Basic Profile. JBossWS provides support for WS-I AP 1.0, and MTOM instead."
msgstr ""
#. Tag: title
@@ -1236,25 +778,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"This section describes Message Transmission Optimization Mechanism (MTOM) "
-"and XML-binary Optimized Packaging (XOP), a means of more efficiently "
-"serializing XML Infosets that have certain types of content. The related "
-"specifications are"
+msgid "This section describes Message Transmission Optimization Mechanism (MTOM) and XML-binary Optimized Packaging (XOP), a means of more efficiently serializing XML Infosets that have certain types of content. The related specifications are"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.w3.org/TR/soap12-mtom/\">SOAP Message Transmission "
-"Optimization Mechanism (MTOM)</ulink>"
+msgid "<ulink url=\"http://www.w3.org/TR/soap12-mtom/\">SOAP Message Transmission Optimization Mechanism (MTOM)</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.w3.org/TR/xop10/\">XML-binary Optimized Packaging "
-"(XOP)</ulink>"
+msgid "<ulink url=\"http://www.w3.org/TR/xop10/\">XML-binary Optimized Packaging (XOP)</ulink>"
msgstr ""
#. Tag: title
@@ -1299,19 +833,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The above table shows a list of supported endpoint parameter types. The "
-"recommended approach is to use the <ulink url=\"http://java.sun.com/j2ee/1.4/"
-"docs/api/javax/activation/DataHandler.html\">javax.activation.DataHandler</"
-"ulink> classes to represent binary data as service endpoint parameters."
+msgid "The above table shows a list of supported endpoint parameter types. The recommended approach is to use the <ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/activation/DataHandler.html\">javax.activation.DataHandler</ulink> classes to represent binary data as service endpoint parameters."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Microsoft endpoints tend to send any data as application/octet-stream. The "
-"only Java type that can easily cope with this ambiguity is javax.activation."
-"DataHandler"
+msgid "Microsoft endpoints tend to send any data as application/octet-stream. The only Java type that can easily cope with this ambiguity is javax.activation.DataHandler"
msgstr ""
#. Tag: title
@@ -1321,10 +848,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"On the server side MTOM processing is enabled through the "
-"<literal>@BindingType</literal> annotation. JBossWS does handle SOAP1.1 and "
-"SOAP1.2. Both come with or without MTOM flavours:"
+msgid "On the server side MTOM processing is enabled through the <literal>@BindingType</literal> annotation. JBossWS does handle SOAP1.1 and SOAP1.2. Both come with or without MTOM flavours:"
msgstr ""
#. Tag: para
@@ -1344,17 +868,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Web service clients can use the same approach described above or rely on the "
-"<literal>Binding</literal> API to enable MTOM (Excerpt taken from the "
-"<literal>org.jboss.test.ws.jaxws.samples.xop.doclit.XOPTestCase</literal>):"
+msgid "Web service clients can use the same approach described above or rely on the <literal>Binding</literal> API to enable MTOM (Excerpt taken from the <literal>org.jboss.test.ws.jaxws.samples.xop.doclit.XOPTestCase</literal>):"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"You might as well use the JBossWS configuration templates to setup "
-"deployment defaults."
+msgid "You might as well use the JBossWS configuration templates to setup deployment defaults."
msgstr "你也可以使用 JBossWS 配置模板来设置部署的缺省设置。"
#. Tag: title
@@ -1364,24 +883,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24."
-"html\">WS-I Attachment Profile 1.0</ulink> defines mechanism to reference "
-"MIME attachment parts using <ulink url=\"http://www.ws-i.org/Profiles/"
-"AttachmentsProfile-1.0-2004-08-24."
-"html#Referencing_Attachments_from_the_SOAP_Envelope\">swaRef</ulink>. In "
-"this mechanism the content of XML element of type wsi:swaRef is sent as MIME "
-"attachment and the element inside SOAP Body holds the reference to this "
-"attachment in the CID URI scheme as defined by <ulink url=\"http://www.ietf."
-"org/rfc/rfc2111.txt\">RFC 2111</ulink>."
-msgstr ""
-"<ulink url=\"http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24."
-"html\">WS-I Attachment Profile 1.0</ulink> 定义了用 <ulink url=\"http://www."
-"ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24."
-"html#Referencing_Attachments_from_the_SOAP_Envelope\">swaRef</ulink> 应用 "
-"MIME 附件的机制。在这个机制里，类型为 wsi:swaRef 的 XML 元素的内容以 MIME 附"
-"件被发送，且 SOAP 主体里的元素以 CID RUI 模式持有对这个附件的引用，如 <ulink "
-"url=\"http://www.ietf.org/rfc/rfc2111.txt\">RFC 2111</ulink> 所定义的。"
+msgid "<ulink url=\"http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24.html\">WS-I Attachment Profile 1.0</ulink> defines mechanism to reference MIME attachment parts using <ulink url=\"http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24.html#Referencing_Attachments_from_the_SOAP_Envelope\">swaRef</ulink>. In this mechanism the content of XML element of type wsi:swaRef is sent as MIME attachment and the element inside SOAP Body holds the reference to this attachment in the CID URI scheme as defined by <ulink url=\"http://www.ietf.org/rfc/rfc2111.txt\">RFC 2111</ulink>."
+msgstr "<ulink url=\"http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24.html\">WS-I Attachment Profile 1.0</ulink> 定义了用 <ulink url=\"http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24.html#Referencing_Attachments_from_the_SOAP_Envelope\">swaRef</ulink> 应用 MIME 附件的机制。在这个机制里，类型为 wsi:swaRef 的 XML 元素的内容以 MIME 附件被发送，且 SOAP 主体里的元素以 CID RUI 模式持有对这个附件的引用，如 <ulink url=\"http://www.ietf.org/rfc/rfc2111.txt\">RFC 2111</ulink> 所定义的。"
#. Tag: title
#, no-c-format
@@ -1390,19 +893,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"JAX-WS endpoints delegate all marshalling/unmarshalling to the JAXB API. The "
-"most simple way to enable SwaRef encoding for <literal>DataHandler</literal> "
-"types is to annotate a payload bean with the <literal>@XmlAttachmentRef</"
-"literal> annotation as shown below:"
+msgid "JAX-WS endpoints delegate all marshalling/unmarshalling to the JAXB API. The most simple way to enable SwaRef encoding for <literal>DataHandler</literal> types is to annotate a payload bean with the <literal>@XmlAttachmentRef</literal> annotation as shown below:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"With document wrapped endpoints you may even specify the "
-"<literal>@XmlAttachmentRef</literal> annotation on the service endpoint "
-"interface:"
+msgid "With document wrapped endpoints you may even specify the <literal>@XmlAttachmentRef</literal> annotation on the service endpoint interface:"
msgstr ""
#. Tag: para
@@ -1417,10 +913,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"If you chose the contract first approach then you need to ensure that any "
-"element declaration that should use SwaRef encoding simply refers to wsi:"
-"swaRef schema type:"
+msgid "If you chose the contract first approach then you need to ensure that any element declaration that should use SwaRef encoding simply refers to wsi:swaRef schema type:"
msgstr ""
#. Tag: para
@@ -1435,17 +928,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The JAX-WS tools provided by JBossWS can be used in a variety of ways. First "
-"we will look at server-side development strategies, and then proceed to the "
-"client. When developing a Web Service Endpoint (the server-side) you have "
-"the option of starting from Java (bottom-up development), or from the "
-"abstact contract (WSDL) that defines your service (top-down development). If "
-"this is a new service (no existing contract), the bottom-up approach is the "
-"fastest route; you only need to add a few annotations to your classes to get "
-"a service up and running. However, if you are developing a service with an "
-"already defined contract, it is far simpler to use the top-down approach, "
-"since the provided tool will generate the annotated code for you."
+msgid "The JAX-WS tools provided by JBossWS can be used in a variety of ways. First we will look at server-side development strategies, and then proceed to the client. When developing a Web Service Endpoint (the server-side) you have the option of starting from Java (bottom-up development), or from the abstact contract (WSDL) that defines your service (top-down development). If this is a new service (no existing contract), the bottom-up approach is the fastest route; you only need to add a few annotations to your classes to get a service up and running. However, if you are developing a service with an already defined contract, it is far simpler to use the top-down approach, since the provided tool will generate the annotated code for you."
msgstr "服务."
#. Tag: para
@@ -1460,8 +943,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Providing a new service, and you want the contract to be generated for you"
+msgid "Providing a new service, and you want the contract to be generated for you"
msgstr "提供了一个新的服务，且你想生成相应的合约。"
#. Tag: para
@@ -1471,23 +953,17 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Replacing the implementation of an existing Web Service without breaking "
-"compatibility with older clients"
+msgid "Replacing the implementation of an existing Web Service without breaking compatibility with older clients"
msgstr "服务'"
#. Tag: para
#, no-c-format
-msgid ""
-"Exposing a service that conforms to a contract specified by a third party (e."
-"g. a vender that calls you back using an already defined protocol)."
+msgid "Exposing a service that conforms to a contract specified by a third party (e.g. a vender that calls you back using an already defined protocol)."
msgstr "开放了符合第三方（如用已定义的协议回调的供应商）定义合约的服务。"
#. Tag: para
#, no-c-format
-msgid ""
-"Creating a service that adheres to the XML Schema and WSDL you developed by "
-"hand up front"
+msgid "Creating a service that adheres to the XML Schema and WSDL you developed by hand up front"
msgstr ""
#. Tag: para
@@ -1507,44 +983,32 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide"
-"\">wsprovide</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide\">wsprovide</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Generates JAX-WS portable artifacts, and provides the abstract contract. "
-"Used for bottom-up development."
+msgid "Generates JAX-WS portable artifacts, and provides the abstract contract. Used for bottom-up development."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume"
-"\">wsconsume</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume\">wsconsume</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"Consumes the abstract contract (WSDL and Schema files), and produces "
-"artifacts for both a server and client. Used for top-down and client "
-"development"
+msgid "Consumes the abstract contract (WSDL and Schema files), and produces artifacts for both a server and client. Used for top-down and client development"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsrunclient"
-"\">wsrunclient</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsrunclient\">wsrunclient</ulink>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Executes a Java client (that has a main method) using the JBossWS classpath."
+msgid "Executes a Java client (that has a main method) using the JBossWS classpath."
msgstr "用 JBossWS classpath 执行 Java 客户程序（具有 main 方法）。"
#. Tag: title
@@ -1554,17 +1018,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The bottom-up strategy involves developing the Java code for your service, "
-"and then annotating it using JAX-WS annotations. These annotations can be "
-"used to customize the contract that is generated for your service. For "
-"example, you can change the operation name to map to anything you like. "
-"However, all of the annotations have sensible defaults, so only the "
-"@WebService annotation is required."
-msgstr ""
-"bottom-up 策略包括为你的服务开发 Java 代码，然后用 JAX-WS 进行注解。这些注解"
-"可以用于为你的服务生成的自定义合约。利润，你可以修改操作名称来映射任何所需要"
-"的东西。然而，所有的注解都有缺省值，所有只有 @WebService 注解是必需的。"
+msgid "The bottom-up strategy involves developing the Java code for your service, and then annotating it using JAX-WS annotations. These annotations can be used to customize the contract that is generated for your service. For example, you can change the operation name to map to anything you like. However, all of the annotations have sensible defaults, so only the @WebService annotation is required."
+msgstr "bottom-up 策略包括为你的服务开发 Java 代码，然后用 JAX-WS 进行注解。这些注解可以用于为你的服务生成的自定义合约。利润，你可以修改操作名称来映射任何所需要的东西。然而，所有的注解都有缺省值，所有只有 @WebService 注解是必需的。"
#. Tag: para
#, no-c-format
@@ -1573,40 +1028,13 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"A JSE or EJB3 deployment can be built using this class, and it is the only "
-"Java code needed to deploy on JBossWS. The WSDL, and all other Java "
-"artifacts called \"wrapper classes\" will be generated for you at deploy "
-"time. This actually goes beyond the JAX-WS specification, which requires "
-"that wrapper classes be generated using an offline tool. The reason for this "
-"requirement is purely a vender implementation problem, and since we do not "
-"believe in burdening a developer with a bunch of additional steps, we "
-"generate these as well. However, if you want your deployment to be portable "
-"to other application servers, you will need to use a tool and add the "
-"generated classes to your deployment."
-msgstr ""
-"JSE 或 EJB3 部署可以用这个类进行构建，且它是唯一需要部署在 JBossWS 上的 Java "
-"代码。WSDL 和其他的被称为 \"wrapper classes\" 的 Java 类将在部署时生成。这实"
-"际上超出了 JAX-WS 规格，因为它要求 wrapper 类使用离线工具来生成。其原因是这种"
-"要求纯粹是供应商方面的问题，既然我们不相信这会使开发人员负担额外的步骤，我们"
-"就生成它。然而，如果你希望部署是可移植到其他应用服务器上的，你就需要使用工具"
-"并把生成的类添加到部署里。"
+msgid "A JSE or EJB3 deployment can be built using this class, and it is the only Java code needed to deploy on JBossWS. The WSDL, and all other Java artifacts called \"wrapper classes\" will be generated for you at deploy time. This actually goes beyond the JAX-WS specification, which requires that wrapper classes be generated using an offline tool. The reason for this requirement is purely a vender implementation problem, and since we do not believe in burdening a developer with a bunch of additional steps, we generate these as well. However, if you want your deployment to be portable to other application servers, you will need to use a tool and add the generated classes to your deployment."
+msgstr "JSE 或 EJB3 部署可以用这个类进行构建，且它是唯一需要部署在 JBossWS 上的 Java 代码。WSDL 和其他的被称为 \"wrapper classes\" 的 Java 类将在部署时生成。这实际上超出了 JAX-WS 规格，因为它要求 wrapper 类使用离线工具来生成。其原因是这种要求纯粹是供应商方面的问题，既然我们不相信这会使开发人员负担额外的步骤，我们就生成它。然而，如果你希望部署是可移植到其他应用服务器上的，你就需要使用工具并把生成的类添加到部署里。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"This is the primary purpose of the <ulink url=\"http://www.jboss.org/"
-"community/wiki/JBossWS-wsprovide\">wsprovide</ulink> tool, to generate "
-"portable JAX-WS artifacts. Additionally, it can be used to \"provide\" the "
-"abstract contract (WSDL file) for your service. This can be obtained by "
-"invoking <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide"
-"\">wsprovide</ulink> using the \"-w\" option:"
-msgstr ""
-"这是 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide"
-"\">wsprovide</ulink> 工具的主要目的，也就是生成可移植的 JAX-WS 代码。此外，它"
-"可用于“提供”抽象合约（WSDL 文件）。这可以通过用 \"-w\" 选项调用 <ulink url="
-"\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</"
-"ulink> 来获得："
+msgid "This is the primary purpose of the <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide\">wsprovide</ulink> tool, to generate portable JAX-WS artifacts. Additionally, it can be used to \"provide\" the abstract contract (WSDL file) for your service. This can be obtained by invoking <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide\">wsprovide</ulink> using the \"-w\" option:"
+msgstr "这是 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink> 工具的主要目的，也就是生成可移植的 JAX-WS 代码。此外，它可用于“提供”抽象合约（WSDL 文件）。这可以通过用 \"-w\" 选项调用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink> 来获得："
#. Tag: para
#, no-c-format
@@ -1620,28 +1048,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Remember that <emphasis role=\"bold\">when deploying on JBossWS you do not "
-"need to run this tool.</emphasis> You only need it for generating portable "
-"artifacts and/or the abstract contract for your service."
-msgstr ""
-"请记住：<emphasis role=\"bold\">当在 JBossWS 上部署时，你不需要运行这个工具。"
-"</emphasis> 只有在生成可移植的代码和/或抽象合约时才需要它。"
+msgid "Remember that <emphasis role=\"bold\">when deploying on JBossWS you do not need to run this tool.</emphasis> You only need it for generating portable artifacts and/or the abstract contract for your service."
+msgstr "请记住：<emphasis role=\"bold\">当在 JBossWS 上部署时，你不需要运行这个工具。</emphasis> 只有在生成可移植的代码和/或抽象合约时才需要它。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Let us create a POJO endpoint for deployment on JBoss Enterprise Application "
-"Platform. A simple <filename>web.xml</filename> needs to be created:"
-msgstr ""
-"让我们为 JBoss AS 上的部署创建一个 POJO 端点。我们需要创建一个简单的 web."
-"xml："
+msgid "Let us create a POJO endpoint for deployment on JBoss Enterprise Application Platform. A simple <filename>web.xml</filename> needs to be created:"
+msgstr "让我们为 JBoss AS 上的部署创建一个 POJO 端点。我们需要创建一个简单的 web.xml："
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The <filename>web.xml</filename> and the single class can now be used to "
-"create a WAR:"
+msgid "The <filename>web.xml</filename> and the single class can now be used to create a WAR:"
msgstr " web.xml 和 single 类现在可用来创建了 war 文件了："
#. Tag: para
@@ -1651,23 +1068,12 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"At deploy time JBossWS will internally invoke <ulink url=\"http://www.jboss."
-"org/community/wiki/JBossWS-wsprovide\">wsprovide</ulink>, which will "
-"generate the WSDL. If deployment was successful, and you are using the "
-"default settings, it should be available here: <ulink url=\"http://"
-"localhost:8080/echo/Echo?wsdl\">http://localhost:8080/echo/Echo?wsdl</ulink>"
-msgstr ""
-"这将在内部调用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?"
-"title=Wsprovide\">wsprovide</ulink>，它会生成 WSDL。如果部署成功，且你正在使"
-"用缺省设置，它应该可以这样访问：<ulink url=\"http://localhost:8080/echo/Echo?"
-"wsdl\">http://localhost:8080/echo/Echo?wsdl</ulink>。"
+msgid "At deploy time JBossWS will internally invoke <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide\">wsprovide</ulink>, which will generate the WSDL. If deployment was successful, and you are using the default settings, it should be available here: <ulink url=\"http://localhost:8080/echo/Echo?wsdl\">http://localhost:8080/echo/Echo?wsdl</ulink>"
+msgstr "这将在内部调用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink>，它会生成 WSDL。如果部署成功，且你正在使用缺省设置，它应该可以这样访问：<ulink url=\"http://localhost:8080/echo/Echo?wsdl\">http://localhost:8080/echo/Echo?wsdl</ulink>。"
#. Tag: para
#, no-c-format
-msgid ""
-"For a portable JAX-WS deployment, the wrapper classes generated earlier "
-"could be added to the deployment."
+msgid "For a portable JAX-WS deployment, the wrapper classes generated earlier could be added to the deployment."
msgstr "对于可移植的 JAX-WS 部署，早前生成的 wrapper 类可以添加到部署里："
#. Tag: title
@@ -1677,17 +1083,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The top-down development strategy begins with the abstract contract for the "
-"service, which includes the WSDL file and zero or more schema files. The "
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume"
-"\">wsconsume</ulink> tool is then used to consume this contract, and produce "
-"annotated Java classes (and optionally sources) that define it."
-msgstr ""
-" top-down 开发策略从服务的抽象合约（abstract contract）开始，包括 WSDL 文件和"
-"零到多个模式文件（Schema）。<ulink url=\"http://jbws.dyndns.org/mediawiki/"
-"index.php?title=Wsconsume\">wsconsume</ulink> 工具用于消费这个合约，并产生定"
-"义它的 Java 类注解。"
+msgid "The top-down development strategy begins with the abstract contract for the service, which includes the WSDL file and zero or more schema files. The <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume\">wsconsume</ulink> tool is then used to consume this contract, and produce annotated Java classes (and optionally sources) that define it."
+msgstr " top-down 开发策略从服务的抽象合约（abstract contract）开始，包括 WSDL 文件和零到多个模式文件（Schema）。<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink> 工具用于消费这个合约，并产生定义它的 Java 类注解。"
#. Tag: para
#, no-c-format
@@ -1696,17 +1093,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Using the WSDL file from the bottom-up example, a new Java implementation "
-"that adheres to this service can be generated. The \"-k\" option is passed "
-"to <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume"
-"\">wsconsume</ulink> to preserve the Java source files that are generated, "
-"instead of providing just classes:"
-msgstr ""
-"使用 bottom-up 例子里的 WSDL 文件，就可以生成依附于这个服务的新的 Java 实现。"
-"\"-k\" 选项被传递给 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?"
-"title=Wsconsume\">wsconsume</ulink> 以保存所生成的 Java 源文件，而不是只提供"
-"类："
+msgid "Using the WSDL file from the bottom-up example, a new Java implementation that adheres to this service can be generated. The \"-k\" option is passed to <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume\">wsconsume</ulink> to preserve the Java source files that are generated, instead of providing just classes:"
+msgstr "使用 bottom-up 例子里的 WSDL 文件，就可以生成依附于这个服务的新的 Java 实现。\"-k\" 选项被传递给 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink> 以保存所生成的 Java 源文件，而不是只提供类："
#. Tag: para
#, no-c-format
@@ -1785,17 +1173,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Examining the Service Endpoint Interface reveals annotations that are more "
-"explicit than in the class written by hand in the bottom-up example, "
-"however, these evaluate to the same contract:"
+msgid "Examining the Service Endpoint Interface reveals annotations that are more explicit than in the class written by hand in the bottom-up example, however, these evaluate to the same contract:"
msgstr "服务:"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The only missing piece (besides the packaging) is the implementation class, "
-"which can now be written using the above interface."
+msgid "The only missing piece (besides the packaging) is the implementation class, which can now be written using the above interface."
msgstr "这里未出现的（除了 packaging）是实现类，它可用上面的接口进行编写。"
#. Tag: title
@@ -1805,44 +1188,13 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Before going into detail on the client-side it is important to understand "
-"the decoupling concept that is central to Web Services. Web Services are not "
-"the best fit for internal RPC, even though they can be used in this way; "
-"there are much better technologies for achieving this (CORBA, and RMI for "
-"example). Web Services were designed specifically for interoperable coarse-"
-"grained correspondence. There is no expectation or guarantee that any party "
-"participating in a Web Service interaction will be at any particular "
-"location, running on any particular operating system, or written in any "
-"particular programming language. So because of this, it is important to "
-"clearly separate client and server implementations. The only thing they "
-"should have in common is the abstract contract definition. If, for whatever "
-"reason, your software does not adhere to this principal, then you should not "
-"be using Web Services. For the above reasons, the <emphasis role=\"bold\"> "
-"<emphasis>recommended methodology for developing a client is</emphasis> </"
-"emphasis> to follow <emphasis role=\"bold\"> <emphasis>the top-down "
-"approach</emphasis> </emphasis> , even if the client is running on the same "
-"server."
-msgstr ""
-"服务<emphasis role=\"bold\"><emphasis></emphasis></emphasis><emphasis role="
-"\"bold\"><emphasis></emphasis></emphasis>."
+msgid "Before going into detail on the client-side it is important to understand the decoupling concept that is central to Web Services. Web Services are not the best fit for internal RPC, even though they can be used in this way; there are much better technologies for achieving this (CORBA, and RMI for example). Web Services were designed specifically for interoperable coarse-grained correspondence. There is no expectation or guarantee that any party participating in a Web Service interaction will be at any particular location, running on any particular operating system, or written in any particular programming language. So because of this, it is important to clearly separate client and server implementations. The only thing they should have in common is the abstract contract definition. If, for whatever reason, your software does not adhere to this principal, then you should not be using Web Services. For the above reasons, the <emphasis role=\"bold\"> <emphasis>recommend!
ed methodology for developing a client is</emphasis> </emphasis> to follow <emphasis role=\"bold\"> <emphasis>the top-down approach</emphasis> </emphasis> , even if the client is running on the same server."
+msgstr "服务<emphasis role=\"bold\"><emphasis></emphasis></emphasis><emphasis role=\"bold\"><emphasis></emphasis></emphasis>."
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Let's repeat the process of the top-down section, although using the "
-"deployed WSDL, instead of the one generated offline by <ulink url=\"http://"
-"www.jboss.org/community/wiki/JBossWS-wsprovide\">wsprovide</ulink>. The "
-"reason why we do this is just to get the right value for soap:address. This "
-"value must be computed at deploy time, since it is based on container "
-"configuration specifics. You could of course edit the WSDL file yourself, "
-"although you need to ensure that the path is correct."
-msgstr ""
-"让我们重复 top-down 章节里的过程，虽然这是通过所部署的 WSDL 而不是用 <ulink "
-"url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide"
-"\">wsprovide</ulink> 脱线生成的那个。我们要这样做的原因是获取正确的 soap:"
-"address 值。既然这个值是基于容器配置的，它必须在部署时进行计算。你当然可以自"
-"己编辑 WSDL 文件，但你需要确保路径是正确的。"
+msgid "Let's repeat the process of the top-down section, although using the deployed WSDL, instead of the one generated offline by <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide\">wsprovide</ulink>. The reason why we do this is just to get the right value for soap:address. This value must be computed at deploy time, since it is based on container configuration specifics. You could of course edit the WSDL file yourself, although you need to ensure that the path is correct."
+msgstr "让我们重复 top-down 章节里的过程，虽然这是通过所部署的 WSDL 而不是用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink> 脱线生成的那个。我们要这样做的原因是获取正确的 soap:address 值。既然这个值是基于容器配置的，它必须在部署时进行计算。你当然可以自己编辑 WSDL 文件，但你需要确保路径是正确的。"
#. Tag: para
#, no-c-format
@@ -1856,43 +1208,22 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Using the online deployed version with <ulink url=\"http://www.jboss.org/"
-"community/wiki/JBossWS-wsconsume\">wsconsume</ulink>:"
-msgstr ""
-"和在线部署的版本一起使用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index."
-"php?title=Wsconsume\">wsconsume</ulink>："
+msgid "Using the online deployed version with <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume\">wsconsume</ulink>:"
+msgstr "和在线部署的版本一起使用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink>："
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The one class that was not examined in the top-down section, was "
-"<filename>EchoService.java</filename>. Notice how it stores the location the "
-"WSDL was obtained from."
-msgstr ""
-"top-down 部分没有讨论的类是 EchoService.java。请注意它是怎样存储 WSDL 所处的"
-"位置的。"
+msgid "The one class that was not examined in the top-down section, was <filename>EchoService.java</filename>. Notice how it stores the location the WSDL was obtained from."
+msgstr "top-down 部分没有讨论的类是 EchoService.java。请注意它是怎样存储 WSDL 所处的位置的。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"As you can see, this generated class extends the main client entry point in "
-"JAX-WS, <classname>javax.xml.ws.Service</classname>. While you can use "
-"<classname>Service</classname> directly, this is far simpler since it "
-"provides the configuration info for you. The only method we really care "
-"about is the <methodname>getEchoPort()</methodname> method, which returns an "
-"instance of our <classname>Service Endpoint Interface</classname>. Any Web "
-"Services operation can then be called by just invoking a method on the "
-"returned interface."
+msgid "As you can see, this generated class extends the main client entry point in JAX-WS, <classname>javax.xml.ws.Service</classname>. While you can use <classname>Service</classname> directly, this is far simpler since it provides the configuration info for you. The only method we really care about is the <methodname>getEchoPort()</methodname> method, which returns an instance of our <classname>Service Endpoint Interface</classname>. Any Web Services operation can then be called by just invoking a method on the returned interface."
msgstr "服务 服务 服务."
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"It is not recommended to refer to a remote WSDL URL in a production "
-"application. This causes network I/O every time you instantiate the Service "
-"Object. Instead, use the tool on a saved local copy, or use the URL version "
-"of the constructor to provide a new WSDL location."
+msgid "It is not recommended to refer to a remote WSDL URL in a production application. This causes network I/O every time you instantiate the Service Object. Instead, use the tool on a saved local copy, or use the URL version of the constructor to provide a new WSDL location."
msgstr "' 服务."
#. Tag: para
@@ -1902,17 +1233,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"It can then be easily executed using the <ulink url=\"http://www.jboss.org/"
-"community/wiki/JBossWS-wsrunclient\">wsrunclient</ulink> tool. This is just "
-"a convenience tool that invokes java with the needed classpath:"
+msgid "It can then be easily executed using the <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsrunclient\">wsrunclient</ulink> tool. This is just a convenience tool that invokes java with the needed classpath:"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"It is easy to change the endpoint address of your operation at runtime, "
-"setting <property>ENDPOINT_ADDRESS_PROPERTY</property> as shown below:"
+msgid "It is easy to change the endpoint address of your operation at runtime, setting <property>ENDPOINT_ADDRESS_PROPERTY</property> as shown below:"
msgstr "在运行时修改操作的终端地址很简单，只要设置 ENDPOINT_ADDRESS_PROPERTY："
#. Tag: title
@@ -1922,23 +1248,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume"
-"\">wsconsume reference page</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsconsume\">wsconsume reference page</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide"
-"\">wsprovide reference page</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsprovide\">wsprovide reference page</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsrunclient"
-"\">wsrunclient reference page</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-wsrunclient\">wsrunclient reference page</ulink>"
msgstr ""
#. Tag: title
@@ -1953,10 +1273,7 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<ulink url=\"http://java.sun.com/webservices/docs/2.0/jaxws/customizations."
-"html\">http://java.sun.com/webservices/docs/2.0/jaxws/customizations.html</"
-"ulink>"
+msgid "<ulink url=\"http://java.sun.com/webservices/docs/2.0/jaxws/customizations.html\">http://java.sun.com/webservices/docs/2.0/jaxws/customizations.html</ulink>"
msgstr "http://java.sun.com/webservices/docs/2.0/jaxws/customizations.html"
#. Tag: para
@@ -1966,9 +1283,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"https://jax-ws.dev.java.net/source/browse/jax-ws/guide/docs/"
-"wsdl-customization.xsd?rev=1.2&view=log\">binding customization</ulink>"
+msgid "<ulink url=\"https://jax-ws.dev.java.net/source/browse/jax-ws/guide/docs/wsdl-customization.xsd?rev=1.2&view=log\">binding customization</ulink>"
msgstr ""
#. Tag: title
@@ -1983,12 +1298,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"This section describes how <ulink url=\"http://www.w3.org/TR/ws-addr-core"
-"\">WS-Addressing</ulink> can be used to provide a staful service endpoint."
-msgstr ""
-"本节描述如何使用 <ulink url=\"http://www.w3.org/TR/ws-addr-core\">WS-"
-"Addressing</ulink> 来提供有状态的服务终端。"
+msgid "This section describes how <ulink url=\"http://www.w3.org/TR/ws-addr-core\">WS-Addressing</ulink> can be used to provide a staful service endpoint."
+msgstr "本节描述如何使用 <ulink url=\"http://www.w3.org/TR/ws-addr-core\">WS-Addressing</ulink> 来提供有状态的服务终端。"
#. Tag: title
#, fuzzy, no-c-format
@@ -1997,29 +1308,17 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"WS-Addressing is defined by a combination of the following specifications "
-"from the W3C Recommendation. The WS-Addressing API is standardized by <ulink "
-"url=\"http://www.jcp.org/en/jsr/detail?id=224\">JSR-224 - Java API for XML-"
-"Based Web Services (JAX-WS)</ulink>"
-msgstr ""
-"WS-Addressing 由 W3C Candidate Recommendation 17 August 2005 里的下列规格组合"
-"进行定义。WS-Addressing API 由 <ulink url=\"http://www.jcp.org/en/jsr/detail?"
-"id=261\">JSR-261 - Java API for XML Web Services Addressing</ulink> 进行标准"
-"化。"
+msgid "WS-Addressing is defined by a combination of the following specifications from the W3C Recommendation. The WS-Addressing API is standardized by <ulink url=\"http://www.jcp.org/en/jsr/detail?id=224\">JSR-224 - Java API for XML-Based Web Services (JAX-WS)</ulink>"
+msgstr "WS-Addressing 由 W3C Candidate Recommendation 17 August 2005 里的下列规格组合进行定义。WS-Addressing API 由 <ulink url=\"http://www.jcp.org/en/jsr/detail?id=261\">JSR-261 - Java API for XML Web Services Addressing</ulink> 进行标准化。"
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.w3.org/TR/ws-addr-core\">Web Services Addressing 1.0 "
-"- Core</ulink>"
+msgid "<ulink url=\"http://www.w3.org/TR/ws-addr-core\">Web Services Addressing 1.0 - Core</ulink>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<ulink url=\"http://www.w3.org/TR/ws-addr-soap\">Web Services Addressing 1.0 "
-"- SOAP Binding</ulink>"
+msgid "<ulink url=\"http://www.w3.org/TR/ws-addr-soap\">Web Services Addressing 1.0 - SOAP Binding</ulink>"
msgstr "Web Services Addressing 1.0 - SOAP Binding"
#. Tag: title
@@ -2029,16 +1328,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The following endpoint implementation has a set of operation for a typical "
-"stateful shopping chart application."
+msgid "The following endpoint implementation has a set of operation for a typical stateful shopping chart application."
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"It uses the JAX-WS 2.1 defined <literal>javax.xml.ws.soap.Addressing</"
-"literal> annotation to enable the server side addressing handler."
+msgid "It uses the JAX-WS 2.1 defined <literal>javax.xml.ws.soap.Addressing</literal> annotation to enable the server side addressing handler."
msgstr ""
#. Tag: title
@@ -2048,16 +1343,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The client code uses <literal>javax.xml.ws.soap.AddressingFeature</literal> "
-"feature from JAX-WS 2.1 API to enable the WS-Addressing."
+msgid "The client code uses <literal>javax.xml.ws.soap.AddressingFeature</literal> feature from JAX-WS 2.1 API to enable the WS-Addressing."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">A client connecting to the stateful endpoint</"
-"emphasis>"
+msgid "<emphasis role=\"bold\">A client connecting to the stateful endpoint</emphasis>"
msgstr "连接到有状态端点的客户端"
#. Tag: para
@@ -2077,24 +1368,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"WS-Security addresses message level security. It standardizes authorization, "
-"encryption, and digital signature processing of web services. Unlike "
-"transport security models, such as SSL, WS-Security applies security "
-"directly to the elements of the web service message. This increases the "
-"flexibility of your web services, by allowing any message model to be used "
-"(point to point, multi-hop relay, etc)."
-msgstr ""
-"WS-Security 解决消息级别的安全性。它标准化 web service 的授权、加密和数字签名"
-"处理。不象传输安全模型如 SSL，WS-Security 把安全性直接应用到 web service 消息"
-"的元素里。通过使用消息模型（点对点、多中继点传输等），这增加了 web service 的"
-"灵活性。"
+msgid "WS-Security addresses message level security. It standardizes authorization, encryption, and digital signature processing of web services. Unlike transport security models, such as SSL, WS-Security applies security directly to the elements of the web service message. This increases the flexibility of your web services, by allowing any message model to be used (point to point, multi-hop relay, etc)."
+msgstr "WS-Security 解决消息级别的安全性。它标准化 web service 的授权、加密和数字签名处理。不象传输安全模型如 SSL，WS-Security 把安全性直接应用到 web service 消息的元素里。通过使用消息模型（点对点、多中继点传输等），这增加了 web service 的灵活性。"
#. Tag: para
#, no-c-format
-msgid ""
-"This chapter describes how to use WS-Security to sign and encrypt a simple "
-"SOAP message."
+msgid "This chapter describes how to use WS-Security to sign and encrypt a simple SOAP message."
msgstr "本章讨论了如何使用 WS-Security 来签署和加密一条简单的 SOAP 消息。"
#. Tag: para
@@ -2104,48 +1383,37 @@
#. Tag: para
#, no-c-format
-msgid ""
-"WS-Security is defined by the combination of the following specifications:"
+msgid "WS-Security is defined by the combination of the following specifications:"
msgstr "WS-Security 由下列规格的组合定义："
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-"
-"message-security-1.0.pdf\">SOAP Message Security 1.0</ulink>"
+msgid "<ulink url=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf\">SOAP Message Security 1.0</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-"
-"username-token-profile-1.0.pdf\">Username Token Profile 1.0</ulink>"
+msgid "<ulink url=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf\">Username Token Profile 1.0</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-"
-"token-profile-1.0.pdf\">X.509 Token Profile 1.0</ulink>"
+msgid "<ulink url=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf\">X.509 Token Profile 1.0</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.w3.org/TR/xmlenc-core\">W3C XML Encryption</ulink>"
+msgid "<ulink url=\"http://www.w3.org/TR/xmlenc-core\">W3C XML Encryption</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.w3.org/TR/xmldsig-core\">W3C XML Signature</ulink>"
+msgid "<ulink url=\"http://www.w3.org/TR/xmldsig-core\">W3C XML Signature</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html"
-"\">Basic Security Profile 1.0 (Still in Draft)</ulink>"
+msgid "<ulink url=\"http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html\">Basic Security Profile 1.0 (Still in Draft)</ulink>"
msgstr ""
#. Tag: title
@@ -2155,28 +1423,12 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"JBossWS uses handlers to identify ws-security encoded requests and invoke "
-"the security components to sign and encrypt messages. In order to enable "
-"security processing, the client and server side need to include a "
-"corressponding handler configuration. The preferred way is to reference a "
-"predefined <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-"
-"WSEndpointConfiguration\">JAX-WS Endpoint Configuration</ulink> or <ulink "
-"url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSClientConfiguration"
-"\">JAX-WS Client Configuration</ulink> respectively."
-msgstr ""
-"JBossWS 使用一些处理程序来标识用 ws-security 加密的请求并调用安全性组件来签署"
-"和加密消息。为了启用安全处理，客户和服务器端都需要包含一个对应的处理程序配"
-"置。首选的办法是分别引用预定义的 <ulink url=\"http://jbws.dyndns.org/"
-"mediawiki/index.php?title=JAX-WS_Endpoint_Configuration\">JAX-WS Endpoint "
-"Configuration</ulink> 或 <ulink url=\"http://jbws.dyndns.org/mediawiki/index."
-"php?title=JAX-WS_Client_Configuration\">JAX-WS Client Configuration</ulink>。"
+msgid "JBossWS uses handlers to identify ws-security encoded requests and invoke the security components to sign and encrypt messages. In order to enable security processing, the client and server side need to include a corressponding handler configuration. The preferred way is to reference a predefined <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSEndpointConfiguration\">JAX-WS Endpoint Configuration</ulink> or <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSClientConfiguration\">JAX-WS Client Configuration</ulink> respectively."
+msgstr "JBossWS 使用一些处理程序来标识用 ws-security 加密的请求并调用安全性组件来签署和加密消息。为了启用安全处理，客户和服务器端都需要包含一个对应的处理程序配置。首选的办法是分别引用预定义的 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Endpoint_Configuration\">JAX-WS Endpoint Configuration</ulink> 或 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Client_Configuration\">JAX-WS Client Configuration</ulink>。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"You need to setup both the endpoint configuration and the WSSE declarations "
-"i. e. two separate steps."
+msgid "You need to setup both the endpoint configuration and the WSSE declarations i. e. two separate steps."
msgstr "你需要设置终端配置和 WSSE 声明。这是两个单独的步骤。"
#. Tag: title
@@ -2186,143 +1438,77 @@
#. Tag: para
#, no-c-format
-msgid ""
-"In this example we configure both the client and the server to sign the "
-"message body. Both also require this from each other. So, if you remove "
-"either the client or the server security deployment descriptor, you will "
-"notice that the other party will throw a fault explaining that the message "
-"did not conform to the proper security requirements."
-msgstr ""
-"在这个例子里，我们配置客户端和服务器端来签署消息主体。它们对对方都有这样的要"
-"求。所以，如果你删除了客户端或者是服务器端的部署描述符，你将注意到另外一方会"
-"抛出异常，指出消息没有遵循正确的安全性要求。"
+msgid "In this example we configure both the client and the server to sign the message body. Both also require this from each other. So, if you remove either the client or the server security deployment descriptor, you will notice that the other party will throw a fault explaining that the message did not conform to the proper security requirements."
+msgstr "在这个例子里，我们配置客户端和服务器端来签署消息主体。它们对对方都有这样的要求。所以，如果你删除了客户端或者是服务器端的部署描述符，你将注意到另外一方会抛出异常，指出消息没有遵循正确的安全性要求。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"This specifies that the key store we wish to use is <filename>WEB-INF/wsse."
-"keystore</filename>, which is located in our war file."
-msgstr ""
-"这指定了我们希望使用的密钥库是 WEB-INF/wsse.keystore，它位于 WAR 文件里。"
+msgid "This specifies that the key store we wish to use is <filename>WEB-INF/wsse.keystore</filename>, which is located in our war file."
+msgstr "这指定了我们希望使用的密钥库是 WEB-INF/wsse.keystore，它位于 WAR 文件里。"
#. Tag: para
#, no-c-format
-msgid ""
-"This specifies that the store password is \"jbossws\". Password can be "
-"encypted using the {EXT} and {CLASS} commands. Please see samples for their "
-"usage."
-msgstr ""
-"这指定了库的密码是 \"jbossws\"。密码必须用 {EXT} 和 {CLASS} 命令进行加密。其"
-"详细用法请参考相关示例。"
+msgid "This specifies that the store password is \"jbossws\". Password can be encypted using the {EXT} and {CLASS} commands. Please see samples for their usage."
+msgstr "这指定了库的密码是 \"jbossws\"。密码必须用 {EXT} 和 {CLASS} 命令进行加密。其详细用法请参考相关示例。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"This specifies that the trust store we wish to use is <filename>WEB-INF/wsse."
-"truststore</filename>, which is located in our war file."
-msgstr ""
-"这指定了我们要使用的信任库是 WEB-INF/wsse.truststore，它位于 WAR 文件里。"
+msgid "This specifies that the trust store we wish to use is <filename>WEB-INF/wsse.truststore</filename>, which is located in our war file."
+msgstr "这指定了我们要使用的信任库是 WEB-INF/wsse.truststore，它位于 WAR 文件里。"
#. Tag: para
#, no-c-format
-msgid ""
-"This specifies that the trust store password is also \"jbossws\". Password "
-"can be encrypted using the {EXT} and {CLASS} commands. Please see samples "
-"for their usage."
-msgstr ""
-"这指定了信任库的密码也是 \"jbossws\"。密码可以用 {EXT} 和 {CLASS} 进行加密。"
-"其详细用法请参考相关示例。"
+msgid "This specifies that the trust store password is also \"jbossws\". Password can be encrypted using the {EXT} and {CLASS} commands. Please see samples for their usage."
+msgstr "这指定了信任库的密码也是 \"jbossws\"。密码可以用 {EXT} 和 {CLASS} 进行加密。其详细用法请参考相关示例。"
#. Tag: para
#, no-c-format
-msgid ""
-"Here we start our root config block. The root config block is the default "
-"configuration for all services in this war file."
-msgstr ""
-"这里我们开始根配置块（root config block）。根配置块是 WAR 文件里所有服务的缺"
-"省配置。"
+msgid "Here we start our root config block. The root config block is the default configuration for all services in this war file."
+msgstr "这里我们开始根配置块（root config block）。根配置块是 WAR 文件里所有服务的缺省配置。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"This means that the server must sign the message body of all responses. Type "
-"means that we are using X.509v3 certificate (a standard certificate). The "
-"alias option says that the certificate and key pair to use for signing is in "
-"the key store under the \"wsse\" alias"
-msgstr ""
-"这表示服务器必须签署所有回复的消息主体。Type 表示我们将使用 X.509v3 证书（一"
-"种标准证书）。alias 选项表示这个证书/密钥对位于密钥库里的 \"wsse\" 别名下。"
+msgid "This means that the server must sign the message body of all responses. Type means that we are using X.509v3 certificate (a standard certificate). The alias option says that the certificate and key pair to use for signing is in the key store under the \"wsse\" alias"
+msgstr "这表示服务器必须签署所有回复的消息主体。Type 表示我们将使用 X.509v3 证书（一种标准证书）。alias 选项表示这个证书/密钥对位于密钥库里的 \"wsse\" 别名下。"
#. Tag: para
#, no-c-format
-msgid ""
-"Here we start our optional requires block. This block specifies all security "
-"requirements that must be met when the server receives a message."
-msgstr ""
-"在这里我们开始可选的 requires 块。这里的内容指定服务器接收消息时必须满足的所"
-"有安全要求。"
+msgid "Here we start our optional requires block. This block specifies all security requirements that must be met when the server receives a message."
+msgstr "在这里我们开始可选的 requires 块。这里的内容指定服务器接收消息时必须满足的所有安全要求。"
#. Tag: para
#, no-c-format
-msgid ""
-"This means that all web services in this war file require the message body "
-"to be signed."
+msgid "This means that all web services in this war file require the message body to be signed."
msgstr "这表示 WAR 文件里所有的 web service 都要求签署消息主体。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"By default an endpoint does not use the WS-Security configuration. Users can "
-"use proprietary <literal>@EndpointConfig</literal> annotation to set the "
-"config name. See <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-"
-"JAX-WSEndpointConfiguration\">JAX-WS_Endpoint_Configuration</ulink> for the "
-"list of available config names."
-msgstr ""
-"在缺省情况下，终端不使用 WS-Security 配置。它使用专有的 @EndpointConfig 注解"
-"来设置配置名。请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?"
-"title=JAX-WS_Endpoint_Configuration\">JAX-WS_Endpoint_Configuration</ulink> "
-"里关于可用配置名的列表。"
+msgid "By default an endpoint does not use the WS-Security configuration. Users can use proprietary <literal>@EndpointConfig</literal> annotation to set the config name. See <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSEndpointConfiguration\">JAX-WS_Endpoint_Configuration</ulink> for the list of available config names."
+msgstr "在缺省情况下，终端不使用 WS-Security 配置。它使用专有的 @EndpointConfig 注解来设置配置名。请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Endpoint_Configuration\">JAX-WS_Endpoint_Configuration</ulink> 里关于可用配置名的列表。"
#. Tag: title
#, fuzzy, no-c-format
-msgid ""
-"Client side WSSE declaration (<filename>jboss-wsse-client.xml</filename>)"
+msgid "Client side WSSE declaration (<filename>jboss-wsse-client.xml</filename>)"
msgstr "客户端的 WSSE 声明（jboss-wsse-client.xml）"
#. Tag: para
#, no-c-format
-msgid ""
-"Here we start our root config block. The root config block is the default "
-"configuration for all web service clients (Call, Proxy objects)."
-msgstr ""
-"在这里我们开始根配置块。它是所有 web service 客户（调用、代理对象）的缺省配"
-"置。"
+msgid "Here we start our root config block. The root config block is the default configuration for all web service clients (Call, Proxy objects)."
+msgstr "在这里我们开始根配置块。它是所有 web service 客户（调用、代理对象）的缺省配置。"
#. Tag: para
#, no-c-format
-msgid ""
-"This means that the client must sign the message body of all requests it "
-"sends. Type means that we are to use a X.509v3 certificate (a standard "
-"certificate). The alias option says that the certificate/key pair to use for "
-"signing is in the key store under the \"wsse\" alias"
-msgstr ""
-"这表示客户必须签署它发送的所有请求的消息主体。Type 表示我们将使用 X.509v3 证"
-"书（一种标准证书）。alias 选项表示用于签署的证书/密钥对位于密钥库的 \"wsse\" "
-"别名下。"
+msgid "This means that the client must sign the message body of all requests it sends. Type means that we are to use a X.509v3 certificate (a standard certificate). The alias option says that the certificate/key pair to use for signing is in the key store under the \"wsse\" alias"
+msgstr "这表示客户必须签署它发送的所有请求的消息主体。Type 表示我们将使用 X.509v3 证书（一种标准证书）。alias 选项表示用于签署的证书/密钥对位于密钥库的 \"wsse\" 别名下。"
#. Tag: para
#, no-c-format
-msgid ""
-"Here we start our optional requires block. This block specifies all security "
-"requirements that must be met when the client receives a response."
-msgstr ""
-"这里开始可选的 requires 块。它指定客户接收响应时必须满足的所有安全性要求。"
+msgid "Here we start our optional requires block. This block specifies all security requirements that must be met when the client receives a response."
+msgstr "这里开始可选的 requires 块。它指定客户接收响应时必须满足的所有安全性要求。"
#. Tag: para
#, no-c-format
-msgid ""
-"This means that all web service clients must receive signed response "
-"messages."
+msgid "This means that all web service clients must receive signed response messages."
msgstr "这表示所有的 web service 客户必须接收已签署的响应消息。"
#. Tag: title
@@ -2332,15 +1518,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"We did not specify a key store or trust store, because client apps instead "
-"use the wsse System properties instead. If this was a web or ejb client "
-"(meaning a webservice client in a war or ejb jar file), then we would have "
-"specified them in the client descriptor."
-msgstr ""
-"我们没有指定密钥库或信任库，因为客户端应用程序会使用 wsse 系统属性。如果这是"
-"一个 web 或 EJB 客户（就是 WAR 或 EJB JAR 文件里的 webservice 客户），我们就"
-"需要在客户的描述符里进行指定。"
+msgid "We did not specify a key store or trust store, because client apps instead use the wsse System properties instead. If this was a web or ejb client (meaning a webservice client in a war or ejb jar file), then we would have specified them in the client descriptor."
+msgstr "我们没有指定密钥库或信任库，因为客户端应用程序会使用 wsse 系统属性。如果这是一个 web 或 EJB 客户（就是 WAR 或 EJB JAR 文件里的 webservice 客户），我们就需要在客户的描述符里进行指定。"
#. Tag: para
#, no-c-format
@@ -2349,14 +1528,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Below you see the incomming SOAP message with the details of the security "
-"headers ommited. The idea is, that the SOAP body is still plain text, but it "
-"is signed in the security header and therefore can not be manipulated in "
-"transit."
-msgstr ""
-"下面看到的转入 SOAP 消息的安全信息头被忽略了。也就是说，SOAP 的主体仍然是普通"
-"文本，但签署了安全性头部信息，因此不能在转换时操作。"
+msgid "Below you see the incomming SOAP message with the details of the security headers ommited. The idea is, that the SOAP body is still plain text, but it is signed in the security header and therefore can not be manipulated in transit."
+msgstr "下面看到的转入 SOAP 消息的安全信息头被忽略了。也就是说，SOAP 的主体仍然是普通文本，但签署了安全性头部信息，因此不能在转换时操作。"
#. Tag: para
#, no-c-format
@@ -2370,33 +1543,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The information below has originaly been provided by <ulink url=\"http://www."
-"bouncycastle.org/specifications.html#install\">The Legion of the Bouncy "
-"Castle</ulink>."
-msgstr ""
-"下面的信息最初是由 <ulink url=\"http://www.bouncycastle.org/specifications."
-"html#install\">The Legion of the Bouncy Castle</ulink> 提供的。"
+msgid "The information below has originaly been provided by <ulink url=\"http://www.bouncycastle.org/specifications.html#install\">The Legion of the Bouncy Castle</ulink>."
+msgstr "下面的信息最初是由 <ulink url=\"http://www.bouncycastle.org/specifications.html#install\">The Legion of the Bouncy Castle</ulink> 提供的。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The provider can be configured as part of your environment via static "
-"registration by adding an entry to the <filename>java.security</filename> "
-"properties file (found in <filename>$JAVA_HOME/jre/lib/security/java."
-"security</filename>, where <filename>$JAVA_HOME</filename> is the location "
-"of your JDK and JRE distribution). You will find detailed instructions in "
-"the file but basically it comes down to adding a line:"
-msgstr ""
-"提供者可以通过静态注册配置为环境的一部分，这是通过在 java.security "
-"properties 文件（$JAVA_HOME/jre/lib/security/java.security 里，这里的 "
-"$JAVA_HOME 是 JDK/JRE 的安装位置）里添加一个条目来实现的。在这个文件里，你会"
-"找到详细的说明，但其实只需要加入这样一行："
+msgid "The provider can be configured as part of your environment via static registration by adding an entry to the <filename>java.security</filename> properties file (found in <filename>$JAVA_HOME/jre/lib/security/java.security</filename>, where <filename>$JAVA_HOME</filename> is the location of your JDK and JRE distribution). You will find detailed instructions in the file but basically it comes down to adding a line:"
+msgstr "提供者可以通过静态注册配置为环境的一部分，这是通过在 java.security properties 文件（$JAVA_HOME/jre/lib/security/java.security 里，这里的 $JAVA_HOME 是 JDK/JRE 的安装位置）里添加一个条目来实现的。在这个文件里，你会找到详细的说明，但其实只需要加入这样一行："
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Where <code><n></code> is the preference you want the provider at."
+msgid "Where <code><n></code> is the preference you want the provider at."
msgstr "这里的 <n> 是你设置的提供者序号。"
#. Tag: para
@@ -2406,17 +1563,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Where users will put the provider jar is mostly up to them, although with "
-"jdk5 the best (and in some cases only) place to have it is in <filename>"
-"$JAVA_HOME/jre/lib/ext</filename>. Under Windows there will normally be a "
-"JRE and a JDK install of Java. If user think he have installed it correctly "
-"and it still doesn't work then with high probability the provider "
-"installation is not used."
-msgstr ""
-"把 JAR 放在哪里由你来决定，虽然对于 jdk1.4 来说，最佳（在某些情况下是必须）位"
-"置是 $JAVA_HOME/jre/lib/ext。在 Windows 里，如果正确安装了 JRE 和 JDK 还是不"
-"能使用，那有可能是你添加了并没有使用的提供者。"
+msgid "Where users will put the provider jar is mostly up to them, although with jdk5 the best (and in some cases only) place to have it is in <filename>$JAVA_HOME/jre/lib/ext</filename>. Under Windows there will normally be a JRE and a JDK install of Java. If user think he have installed it correctly and it still doesn't work then with high probability the provider installation is not used."
+msgstr "把 JAR 放在哪里由你来决定，虽然对于 jdk1.4 来说，最佳（在某些情况下是必须）位置是 $JAVA_HOME/jre/lib/ext。在 Windows 里，如果正确安装了 JRE 和 JDK 还是不能使用，那有可能是你添加了并没有使用的提供者。"
#. Tag: title
#, no-c-format
@@ -2425,27 +1573,13 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"J2EE 5.0 mandates support for Java API for XML Registries (JAXR). Inclusion "
-"of a XML Registry with the J2EE 5.0 certified Application Server is "
-"optional. JBoss EAP5 ships a UDDI v2.0 compliant registry, the Apache jUDDI "
-"registry. We also provide support for JAXR Capability Level 0 (UDDI "
-"Registries) via integration of Apache Scout."
-msgstr ""
-"J2EE 1.4 支持 Java API for XML Registries (JAXR)。J2EE 1.4 认证的应用服务器里"
-"带有 XML 注册表是可选的。从 jboss-4.0.2 开始，JBoss 附带一个兼容 UDDI v2.0 的"
-"注册表，也就是 Apache jUDDI 注册表。我们也通过集成 Apache Scout 提供对 JAXR "
-"Capability Level 0 (UDDI Registries) 的支持。"
+msgid "J2EE 5.0 mandates support for Java API for XML Registries (JAXR). Inclusion of a XML Registry with the J2EE 5.0 certified Application Server is optional. JBoss EAP5 ships a UDDI v2.0 compliant registry, the Apache jUDDI registry. We also provide support for JAXR Capability Level 0 (UDDI Registries) via integration of Apache Scout."
+msgstr "J2EE 1.4 支持 Java API for XML Registries (JAXR)。J2EE 1.4 认证的应用服务器里带有 XML 注册表是可选的。从 jboss-4.0.2 开始，JBoss 附带一个兼容 UDDI v2.0 的注册表，也就是 Apache jUDDI 注册表。我们也通过集成 Apache Scout 提供对 JAXR Capability Level 0 (UDDI Registries) 的支持。"
#. Tag: para
#, no-c-format
-msgid ""
-"This chapter describes how to configure the jUDDI registry in JBoss and some "
-"sample code outlines for using JAXR API to publish and query the jUDDI "
-"registry."
-msgstr ""
-"本章介绍如何配置 JBoss 里的 jUDDI 注册表以及一些使用 JAXR API 发布和查询 "
-"jUDDI 注册表的代码示例。"
+msgid "This chapter describes how to configure the jUDDI registry in JBoss and some sample code outlines for using JAXR API to publish and query the jUDDI registry."
+msgstr "本章介绍如何配置 JBoss 里的 jUDDI 注册表以及一些使用 JAXR API 发布和查询 jUDDI 注册表的代码示例。"
#. Tag: title
#, no-c-format
@@ -2454,12 +1588,7 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Configuration of the jUDDI registry happens via an MBean Service that is "
-"deployed in the juddi-service.sar archive in the \"all\" configuration. The "
-"configuration of this service can be done in the <filename>jboss-service."
-"xml</filename> of the META-INF directory in the <filename>juddi-service.sar</"
-"filename>"
+msgid "Configuration of the jUDDI registry happens via an MBean Service that is deployed in the juddi-service.sar archive in the \"all\" configuration. The configuration of this service can be done in the <filename>jboss-service.xml</filename> of the META-INF directory in the <filename>juddi-service.sar</filename>"
msgstr "服务"
#. Tag: para
@@ -2474,16 +1603,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Database Tables (Should they be created on start, Should they be dropped on "
-"stop, Should they be dropped on start etc)"
+msgid "Database Tables (Should they be created on start, Should they be dropped on stop, Should they be dropped on start etc)"
msgstr "数据库表（是否在启动时创建、在关闭时删除或是启动时删除等）"
#. Tag: para
#, no-c-format
-msgid ""
-"JAXR Connection Factory to be bound in JNDI. (Should it be bound? and under "
-"what name?)"
+msgid "JAXR Connection Factory to be bound in JNDI. (Should it be bound? and under what name?)"
msgstr "绑定在 JNDI 里的 JAXR 连接工厂（是否被绑定？以什么名字绑定？）"
#. Tag: para
@@ -2493,12 +1618,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Add authorized users to access the jUDDI registry. (Add a sql insert "
-"statement in a single line)"
-msgstr ""
-"添加授权用户来访问 jUDDI 注册表（在单独一行里添加一个 SQL insert insert 语"
-"句）。"
+msgid "Add authorized users to access the jUDDI registry. (Add a sql insert statement in a single line)"
+msgstr "添加授权用户来访问 jUDDI 注册表（在单独一行里添加一个 SQL insert insert 语句）。"
#. Tag: title
#, no-c-format
@@ -2507,19 +1628,12 @@
#. Tag: para
#, no-c-format
-msgid ""
-"In this section, we will discuss the configuration needed to run the JAXR "
-"API. The JAXR configuration relies on System properties passed to the JVM. "
-"The System properties that are needed are:"
-msgstr ""
-"在本节，我们将讨论运行 JAXR API 所需的配置。JAXR 配置依赖于传递给 JVM 的系统"
-"属性。所需的系统属性为："
+msgid "In this section, we will discuss the configuration needed to run the JAXR API. The JAXR configuration relies on System properties passed to the JVM. The System properties that are needed are:"
+msgstr "在本节，我们将讨论运行 JAXR API 所需的配置。JAXR 配置依赖于传递给 JVM 的系统属性。所需的系统属性为："
#. Tag: para
#, no-c-format
-msgid ""
-"Please remember to change the hostname from \"localhost\" to the hostname of "
-"the UDDI service/JBoss Server."
+msgid "Please remember to change the hostname from \"localhost\" to the hostname of the UDDI service/JBoss Server."
msgstr "请记得把主机名从 \"localhost\" 修改为 UDDI 服务/JBoss 服务器的主机名。"
#. Tag: para
@@ -2529,24 +1643,13 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"When the client code is running inside JBoss (maybe a servlet or an EJB). "
-"Then you will need to pass the System properties in the <filename>run.sh</"
-"filename> or <filename>run.bat</filename> scripts to the java process via "
-"the <code>\"-D\"</code> option."
-msgstr ""
-"当客户代码运行在 JBoss（可以是 servlet 或 EJB）内部时，你需要把 run.sh/run."
-"bat 脚本里的系统属性通过 \"-D\" 选项传递给 java 进程。"
+msgid "When the client code is running inside JBoss (maybe a servlet or an EJB). Then you will need to pass the System properties in the <filename>run.sh</filename> or <filename>run.bat</filename> scripts to the java process via the <code>\"-D\"</code> option."
+msgstr "当客户代码运行在 JBoss（可以是 servlet 或 EJB）内部时，你需要把 run.sh/run.bat 脚本里的系统属性通过 \"-D\" 选项传递给 java 进程。"
#. Tag: para
#, no-c-format
-msgid ""
-"When the client code is running in an external JVM. Then you can pass the "
-"properties either as \"-D\" options to the java process or explicitly set "
-"them in the client code(not recommended)."
-msgstr ""
-"当客户代码运行外部 JVM 里时，你可以用 \"-D\" 选项传递给 java 进程或者显性地在"
-"客户代码里进行设置（我们不推荐这种方式）。"
+msgid "When the client code is running in an external JVM. Then you can pass the properties either as \"-D\" options to the java process or explicitly set them in the client code(not recommended)."
+msgstr "当客户代码运行外部 JVM 里时，你可以用 \"-D\" 选项传递给 java 进程或者显性地在客户代码里进行设置（我们不推荐这种方式）。"
#. Tag: title
#, no-c-format
@@ -2555,63 +1658,27 @@
#. Tag: para
#, no-c-format
-msgid ""
-"There are two categories of API: JAXR Publish API and JAXR Inquiry API. The "
-"important JAXR interfaces that any JAXR client code will use are the "
-"following."
-msgstr ""
-"API 有两个类别：JAXR Publish API 和 JAXR Inquiry API。任何 JAXR 客户代码将使"
-"用的重要的 JAXR 接口如下："
+msgid "There are two categories of API: JAXR Publish API and JAXR Inquiry API. The important JAXR interfaces that any JAXR client code will use are the following."
+msgstr "API 有两个类别：JAXR Publish API 和 JAXR Inquiry API。任何 JAXR 客户代码将使用的重要的 JAXR 接口如下："
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<ulink url=\"http://java.sun.com/javaee/5/docs/api/javax/xml/registry/"
-"RegistryService.html\">javax.xml.registry.RegistryService</ulink> From J2EE "
-"5.0 JavaDoc: \"This is the principal interface implemented by a JAXR "
-"provider. A registry client can get this interface from a Connection to a "
-"registry. It provides the methods that are used by the client to discover "
-"various capability specific interfaces implemented by the JAXR provider.\""
-msgstr ""
-"J2EE 1.4 JavaDoc 里的 <ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/"
-"javax/xml/registry/RegistryService.html\">javax.xml.registry."
-"RegistryService</ulink>：这是 JAXR 提供者实现的主要接口。注册表客户可以从和注"
-"册表的连接里获取这个接口。它提供了客户可用来发现 JAXR 提供者实现的不同功能专"
-"有的接口的方法。"
+msgid "<ulink url=\"http://java.sun.com/javaee/5/docs/api/javax/xml/registry/RegistryService.html\">javax.xml.registry.RegistryService</ulink> From J2EE 5.0 JavaDoc: \"This is the principal interface implemented by a JAXR provider. A registry client can get this interface from a Connection to a registry. It provides the methods that are used by the client to discover various capability specific interfaces implemented by the JAXR provider.\""
+msgstr "J2EE 1.4 JavaDoc 里的 <ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/RegistryService.html\">javax.xml.registry.RegistryService</ulink>：这是 JAXR 提供者实现的主要接口。注册表客户可以从和注册表的连接里获取这个接口。它提供了客户可用来发现 JAXR 提供者实现的不同功能专有的接口的方法。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<ulink url=\"http://java.sun.com/javaee/5/docs/api/javax/xml/registry/"
-"BusinessLifeCycleManager.html\">javax.xml.registry.BusinessLifeCycleManager</"
-"ulink> From J2EE 5.0 JavaDoc: \"The <classname>BusinessLifeCycleManager</"
-"classname> interface, which is exposed by the Registry Service, implements "
-"the life cycle management functionality of the Registry as part of a "
-"business level API. There is no authentication information provided, because "
-"the Connection interface keeps that state and context on behalf of the "
-"client.\""
-msgstr ""
-"<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/"
-"BusinessLifeCycleManager.html\"></ulink> 服务"
+msgid "<ulink url=\"http://java.sun.com/javaee/5/docs/api/javax/xml/registry/BusinessLifeCycleManager.html\">javax.xml.registry.BusinessLifeCycleManager</ulink> From J2EE 5.0 JavaDoc: \"The <classname>BusinessLifeCycleManager</classname> interface, which is exposed by the Registry Service, implements the life cycle management functionality of the Registry as part of a business level API. There is no authentication information provided, because the Connection interface keeps that state and context on behalf of the client.\""
+msgstr "<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/BusinessLifeCycleManager.html\"></ulink> 服务"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<ulink url=\"http://java.sun.com/javaee/5/docs/api/javax/xml/registry/"
-"BusinessQueryManager.html\">javax.xml.registry.BusinessQueryManager</ulink> "
-"From J2EE 5.0 JavaDoc: \"The <classname>BusinessQueryManager</classname> "
-"interface, which is exposed by the Registry Service, implements the business "
-"style query interface. It is also referred to as the focused query interface."
-"\""
-msgstr ""
-"<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/"
-"BusinessQueryManager.html\"></ulink> 服务"
+msgid "<ulink url=\"http://java.sun.com/javaee/5/docs/api/javax/xml/registry/BusinessQueryManager.html\">javax.xml.registry.BusinessQueryManager</ulink> From J2EE 5.0 JavaDoc: \"The <classname>BusinessQueryManager</classname> interface, which is exposed by the Registry Service, implements the business style query interface. It is also referred to as the focused query interface.\""
+msgstr "<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/BusinessQueryManager.html\"></ulink> 服务"
#. Tag: para
#, no-c-format
-msgid ""
-"Let us now look at some of the common programming tasks performed while "
-"using the JAXR API:"
+msgid "Let us now look at some of the common programming tasks performed while using the JAXR API:"
msgstr "让我们来看看使用 JAXR API 时一些常见的编程任务："
#. Tag: para
@@ -2636,9 +1703,7 @@
#. Tag: para
#, no-c-format
-msgid ""
-"For more examples of code using the JAXR API, please refer to the resources "
-"in the Resources Section."
+msgid "For more examples of code using the JAXR API, please refer to the resources in the Resources Section."
msgstr "关于使用 JAXR API 的更多例子，请参考资源章节的内容。"
#. Tag: title
@@ -2648,47 +1713,23 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">I cannot connect to the registry from JAXR.</"
-"emphasis> Please check the inquiry and publish url passed to the JAXR "
-"ConnectionFactory."
-msgstr ""
-"<emphasis role=\"bold\">I cannot connect to the registry from JAXR.</"
-"emphasis> 请检查查询语句并把 publish URL 传递给 JAXR 的连接工厂。"
+msgid "<emphasis role=\"bold\">I cannot connect to the registry from JAXR.</emphasis> Please check the inquiry and publish url passed to the JAXR ConnectionFactory."
+msgstr "<emphasis role=\"bold\">I cannot connect to the registry from JAXR.</emphasis> 请检查查询语句并把 publish URL 传递给 JAXR 的连接工厂。"
#. Tag: para
#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">I cannot connect to the jUDDI registry.</emphasis> "
-"Please check the jUDDI configuration and see if there are any errors in the "
-"server.log. And also remember that the jUDDI registry is available only in "
-"the \"all\" configuration."
-msgstr ""
-"<emphasis role=\"bold\">I cannot connect to the jUDDI registry.</emphasis> 请"
-"检查 jUDDI 配置并查看 server.log 里是否有任何错误。也请记住 jUDDI 注册表只在 "
-"\"all\" 配置里才可用。"
+msgid "<emphasis role=\"bold\">I cannot connect to the jUDDI registry.</emphasis> Please check the jUDDI configuration and see if there are any errors in the server.log. And also remember that the jUDDI registry is available only in the \"all\" configuration."
+msgstr "<emphasis role=\"bold\">I cannot connect to the jUDDI registry.</emphasis> 请检查 jUDDI 配置并查看 server.log 里是否有任何错误。也请记住 jUDDI 注册表只在 \"all\" 配置里才可用。"
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">I cannot authenticate to the jUDDI registry.</"
-"emphasis> Have you added an authorized user to the jUDDI database, as "
-"described earlier in the chapter?"
-msgstr ""
-"<emphasis role=\"bold\">I cannot authenticate to the jUDDI registry.</"
-"emphasis> 如本章前面所描述的，你已经在 jUDDI 数据库里添加了授权用户吗？"
+msgid "<emphasis role=\"bold\">I cannot authenticate to the jUDDI registry.</emphasis> Have you added an authorized user to the jUDDI database, as described earlier in the chapter?"
+msgstr "<emphasis role=\"bold\">I cannot authenticate to the jUDDI registry.</emphasis> 如本章前面所描述的，你已经在 jUDDI 数据库里添加了授权用户吗？"
#. Tag: para
#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">I would like to view the SOAP messages in transit "
-"between the client and the UDDI Registry.</emphasis> Please use the tcpmon "
-"tool to view the messages in transit. <ulink url=\"http://tcpmon.dev.java."
-"net/\">TCPMon</ulink>"
-msgstr ""
-"<emphasis role=\"bold\">I would like to view the SOAP messages in transit "
-"between the client and the UDDI Registry.</emphasis> 请使用 tcpmon 工具来查看"
-"传输消息。<ulink url=\"http://tcpmon.dev.java.net/\">TCPMon</ulink>"
+msgid "<emphasis role=\"bold\">I would like to view the SOAP messages in transit between the client and the UDDI Registry.</emphasis> Please use the tcpmon tool to view the messages in transit. <ulink url=\"http://tcpmon.dev.java.net/\">TCPMon</ulink>"
+msgstr "<emphasis role=\"bold\">I would like to view the SOAP messages in transit between the client and the UDDI Registry.</emphasis> 请使用 tcpmon 工具来查看传输消息。<ulink url=\"http://tcpmon.dev.java.net/\">TCPMon</ulink>"
#. Tag: title
#, no-c-format
@@ -2697,23 +1738,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://java.sun.com/webservices/jaxr/learning/tutorial/index."
-"html\">JAXR Tutorial and Code Camps</ulink>"
+msgid "<ulink url=\"http://java.sun.com/webservices/jaxr/learning/tutorial/index.html\">JAXR Tutorial and Code Camps</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://java.sun.com/j2ee/1.4/docs/tutorial/doc/\">J2EE 1.4 "
-"Tutorial</ulink>"
+msgid "<ulink url=\"http://java.sun.com/j2ee/1.4/docs/tutorial/doc/\">J2EE 1.4 Tutorial</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.amazon.com/exec/obidos/ASIN/0321146182\">J2EE Web "
-"Services by Richard Monson-Haefel</ulink>"
+msgid "<ulink url=\"http://www.amazon.com/exec/obidos/ASIN/0321146182\">J2EE Web Services by Richard Monson-Haefel</ulink>"
msgstr ""
#. Tag: title
@@ -2733,13 +1768,8 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"For the set of standard annotations, please have a look at <ulink url="
-"\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSAnnotations\">JAX-WS "
-"Annotations</ulink>"
-msgstr ""
-"关于标准注解的集合，请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/"
-"index.php?title=JAX-WS_Annotations\">JAX-WS Annotations</ulink>"
+msgid "For the set of standard annotations, please have a look at <ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSAnnotations\">JAX-WS Annotations</ulink>"
+msgstr "关于标准注解的集合，请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Annotations\">JAX-WS Annotations</ulink>"
#. Tag: title
#, no-c-format
@@ -2763,23 +1793,17 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-"
-"WSEndpointConfiguration\">JAX-WS Endpoint Configuration</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSEndpointConfiguration\">JAX-WS Endpoint Configuration</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-"
-"WSClientConfiguration\">JAX-WS Client Configuration</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSClientConfiguration\">JAX-WS Client Configuration</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSAnnotations"
-"\">JAX-WS Annotations</ulink>"
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/JBossWS-JAX-WSAnnotations\">JAX-WS Annotations</ulink>"
msgstr ""
#. Tag: title
@@ -2789,28 +1813,21 @@
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://www.jcp.org/en/jsr/detail?id=224\">JSR-224 - Java API "
-"for XML-Based Web Services (JAX-WS) 2.0</ulink>"
+msgid "<ulink url=\"http://www.jcp.org/en/jsr/detail?id=224\">JSR-224 - Java API for XML-Based Web Services (JAX-WS) 2.0</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://jaxb.dev.java.net/\">JSR 222 - Java Architecture for XML "
-"Binding (JAXB) 2.0</ulink>"
+msgid "<ulink url=\"http://jaxb.dev.java.net/\">JSR 222 - Java Architecture for XML Binding (JAXB) 2.0</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://jcp.org/en/jsr/detail?id=250\">JSR-250 - Common "
-"Annotations for the Java Platform</ulink>"
+msgid "<ulink url=\"http://jcp.org/en/jsr/detail?id=250\">JSR-250 - Common Annotations for the Java Platform</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid ""
-"<ulink url=\"http://jcp.org/en/jsr/detail?id=181\">JSR 181 - Web Services "
-"Metadata for the Java Platform</ulink>"
+msgid "<ulink url=\"http://jcp.org/en/jsr/detail?id=181\">JSR 181 - Web Services Metadata for the Java Platform</ulink>"
msgstr ""
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/What_This_Book_Covers.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/What_This_Book_Covers.po 2010-02-21 21:37:03 UTC (rev 101211)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/What_This_Book_Covers.po 2010-02-21 23:32:25 UTC (rev 101212)
@@ -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-22 09:24+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"
@@ -22,31 +22,12 @@
msgstr "本书涵盖的内容"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The primary focus of this book is the presentation of the standard JBoss "
-"Enterprise Application Platform 5.0 architecture components from both the "
-"perspective of their configuration and architecture. As a user of a standard "
-"JBoss distribution you will be given an understanding of how to configure "
-"the standard components. This book is not an introduction to JavaEE or how "
-"to use JavaEE in applications. It focuses on the internal details of the "
-"JBoss server architecture and how our implementation of a given JavaEE "
-"container can be configured and extended."
-msgstr ""
-"本书主要是从配置和架构的角度对标准的 &JBPAPP; &VER; 组件进行介绍。作为标准 "
-"JBoss 发行版本的用户，你将理解如何配置标准的组件。请注意，本书不是对 J2EE 和"
-"如何在应用程序里使用 J2EE 的介绍。它着重于 JBoss 服务器架构的内部细节以及如何"
-"配置和扩展 J2EE 容器的实现。"
+#, no-c-format
+msgid "The primary focus of this book is the presentation of the standard JBoss Enterprise Application Platform 5.0 architecture components from both the perspective of their configuration and architecture. As a user of a standard JBoss distribution you will be given an understanding of how to configure the standard components. This book is not an introduction to JavaEE or how to use JavaEE in applications. It focuses on the internal details of the JBoss server architecture and how our implementation of a given JavaEE container can be configured and extended."
+msgstr "本书主要是从配置和架构的角度对标准的 JBoss 企业级应用程序平台 5.0 架构组件进行介绍。作为标准 JBoss 发行版本的用户，你将理解如何配置标准的组件。请注意，本书不是对 JavaEE 和如何在应用程序里使用 JavaEE 的介绍。它着重于 JBoss 服务器架构的内部细节以及如何配置和扩展 JavaEE 容器的实现。"
#. Tag: para
#, no-c-format
-msgid ""
-"As a JBoss developer, you will be given a good understanding of the "
-"architecture and integration of the standard components to enable you to "
-"extend or replace the standard components for your infrastructure needs. We "
-"also show you how to obtain the JBoss source code, along with how to build "
-"and debug the JBoss server."
-msgstr ""
-"作为 JBoss 的开发人员，你会很好的理解标准组件的集成和架构，从而根据需要扩展和"
-"替换标准的组件。我们也会向你展示如何获取 JBoss 源码和构建以及调试 JBoss 服务"
-"器。"
+msgid "As a JBoss developer, you will be given a good understanding of the architecture and integration of the standard components to enable you to extend or replace the standard components for your infrastructure needs. We also show you how to obtain the JBoss source code, along with how to build and debug the JBoss server."
+msgstr "作为 JBoss 的开发人员，你会很好的理解标准组件的集成和架构，从而根据需要扩展和替换标准的组件。我们也会向你展示如何获取 JBoss 源码和构建以及调试 JBoss 服务器。"
+
More information about the jboss-cvs-commits
mailing list