[jboss-cvs] JBossAS SVN: r92470 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Aug 18 01:12:45 EDT 2009
Author: xhuang at jboss.com
Date: 2009-08-18 01:12:45 -0400 (Tue, 18 Aug 2009)
New Revision: 92470
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Web_Services.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Web_Services.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Web_Services.po 2009-08-18 04:06:02 UTC (rev 92469)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Web_Services.po 2009-08-18 05:12:45 UTC (rev 92470)
@@ -9,7 +9,7 @@
"Project-Id-Version: Web_Services\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-07-27 09:50+1000\n"
+"PO-Revision-Date: 2009-08-18 14:07+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -21,14 +21,12 @@
#: Web_Services.xml:5
#, no-c-format
msgid "Web Services"
-msgstr "Web 服务 "
+msgstr "Web 服务"
#. Tag: para
#: Web_Services.xml:6
#, no-c-format
-msgid ""
-"The biggest new feature of J2EE 1.4 is the ability of J2EE components to act "
-"both as web service providers and consumers."
+msgid "The biggest new feature of J2EE 1.4 is the ability of J2EE components to act both as web service providers and consumers."
msgstr "J2EE 1.4 最大的新特征是 J2EE 组件可以既作为 web service 的提供者又可作为消费者。"
#. Tag: title
@@ -40,30 +38,15 @@
#. Tag: para
#: Web_Services.xml:11
#, 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. No need to agree on such low level details as operation "
-"names and their associated parameters. The payload of the SOAP message is an "
-"XML document that can be validated against XML schema. 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. No need to agree on such low level details as operation names and their associated parameters. The payload of the SOAP message is an XML document that can be validated against XML schema. Document is defined by the style attribute on the SOAP binding."
+msgstr "对于文档类型的 Web 服务而言，两个商业伙伴同意交换以 XML 模式定义的复杂商业文档。例如，一方发送描述采购订单的文档，而另一方以描述订单状态的文档进行响应（立即或以后）。它们都不需要对底层的细节达成协议，如操作名称和相关的参数。SOAP 消息是一个可以根据 XML 模式进行校验的 XML 文档。文档通过 SOAP 绑定的 style 属性来定义。 "
#. Tag: programlisting
#: Web_Services.xml:15
#, no-c-format
msgid ""
-"<binding name='EndpointInterfaceBinding' type='tns:"
-"EndpointInterface'>\n"
-" <soap:binding style='document' transport='http://"
-"schemas.xmlsoap.org/soap/http'/>\n"
+"<binding name='EndpointInterfaceBinding' type='tns:EndpointInterface'>\n"
+" <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>\n"
" <operation name='concat'>\n"
" <soap:operation soapAction=''/>\n"
" <input>\n"
@@ -75,10 +58,8 @@
" </operation>\n"
" </binding>"
msgstr ""
-"<binding name='EndpointInterfaceBinding' type='tns:"
-"EndpointInterface'>\n"
-" <soap:binding style='document' transport='http://"
-"schemas.xmlsoap.org/soap/http'/>\n"
+"<binding name='EndpointInterfaceBinding' type='tns:EndpointInterface'>\n"
+" <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>\n"
" <operation name='concat'>\n"
" <soap:operation soapAction=''/>\n"
" <input>\n"
@@ -93,12 +74,8 @@
#. Tag: para
#: Web_Services.xml:17
#, 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: programlisting
#: Web_Services.xml:19
@@ -106,42 +83,34 @@
msgid ""
"<complexType name='concatType'>\n"
" <sequence>\n"
-" <element name='String_1' nillable='true' "
-"type='string'/>\n"
+" <element name='String_1' nillable='true' type='string'/>\n"
" <element name='long_1' type='long'/>\n"
" </sequence>\n"
" </complexType>\n"
-" <element name='concat' type='tns:concatType'/"
-">\n"
+" <element name='concat' type='tns:concatType'/>\n"
" Therefore, message parts must refer to an element from the schema. \n"
" <message name='EndpointInterface_concat'>\n"
-" <part name='parameters' element='tns:"
-"concat'/>\n"
+" <part name='parameters' element='tns:concat'/>\n"
" </message>\n"
"The following message definition is invalid. \n"
"<message name='EndpointInterface_concat'>\n"
-" <part name='parameters' type='tns:concatType'/"
-">\n"
+" <part name='parameters' type='tns:concatType'/>\n"
"</message>"
msgstr ""
"<complexType name='concatType'>\n"
" <sequence>\n"
-" <element name='String_1' nillable='true' "
-"type='string'/>\n"
+" <element name='String_1' nillable='true' type='string'/>\n"
" <element name='long_1' type='long'/>\n"
" </sequence>\n"
" </complexType>\n"
-" <element name='concat' type='tns:concatType'/"
-">\n"
+" <element name='concat' type='tns:concatType'/>\n"
" Therefore, message parts must refer to an element from the schema. \n"
" <message name='EndpointInterface_concat'>\n"
-" <part name='parameters' element='tns:"
-"concat'/>\n"
+" <part name='parameters' element='tns:concat'/>\n"
" </message>\n"
"The following message definition is invalid. \n"
"<message name='EndpointInterface_concat'>\n"
-" <part name='parameters' type='tns:concatType'/"
-">\n"
+" <part name='parameters' type='tns:concatType'/>\n"
"</message>"
#. Tag: title
@@ -153,15 +122,8 @@
#. Tag: para
#: Web_Services.xml:25
#, no-c-format
-msgid ""
-"Bare is an implementation detail from the Java domain. Neither in the "
-"abstract contract (i.e. 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 (i.e. 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: programlisting
#: Web_Services.xml:27
@@ -192,9 +154,7 @@
#. Tag: para
#: Web_Services.xml:29
#, 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: programlisting
@@ -202,27 +162,21 @@
#, no-c-format
msgid ""
"@XmlAccessorType(XmlAccessType.FIELD)\n"
-" @XmlType(name = \"SubmitBareRequest\", namespace=\"http://soapbinding."
-"samples.jaxws.ws.test.jboss.org/\", propOrder = { \"product\" })\n"
-" @XmlRootElement(namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss."
-"org/\", name = \"SubmitPO\")\n"
+" @XmlType(name = \"SubmitBareRequest\", namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss.org/\", propOrder = { \"product\" })\n"
+" @XmlRootElement(namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss.org/\", name = \"SubmitPO\")\n"
" public class SubmitBareRequest\n"
" {\n"
-" @XmlElement(namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss.org/"
-"\", required = true)\n"
+" @XmlElement(namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss.org/\", required = true)\n"
" private String product;\n"
" ...\n"
" }"
msgstr ""
"@XmlAccessorType(XmlAccessType.FIELD)\n"
-" @XmlType(name = \"SubmitBareRequest\", namespace=\"http://soapbinding."
-"samples.jaxws.ws.test.jboss.org/\", propOrder = { \"product\" })\n"
-" @XmlRootElement(namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss."
-"org/\", name = \"SubmitPO\")\n"
+" @XmlType(name = \"SubmitBareRequest\", namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss.org/\", propOrder = { \"product\" })\n"
+" @XmlRootElement(namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss.org/\", name = \"SubmitPO\")\n"
" public class SubmitBareRequest\n"
" {\n"
-" @XmlElement(namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss.org/"
-"\", required = true)\n"
+" @XmlElement(namespace=\"http://soapbinding.samples.jaxws.ws.test.jboss.org/\", required = true)\n"
" private String product;\n"
" ...\n"
" }"
@@ -237,11 +191,7 @@
#: Web_Services.xml:37
#, no-c-format
msgid ""
-"Wrapped is an implementation detail from the Java domain. Neither in the "
-"abstract contract (i.e. 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. <programlisting>\n"
+"Wrapped is an implementation detail from the Java domain. Neither in the abstract contract (i.e. 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. <programlisting>\n"
"\n"
"@WebService\n"
"public class DocWrappedServiceImpl\n"
@@ -254,15 +204,9 @@
" ...\n"
" }\n"
" }\n"
-"</programlisting> Note, that with JBossWS the request/response wrapper "
-"annotations are not required, they will be generated on demand using "
-"sensible defaults."
+"</programlisting> Note, that with JBossWS the request/response wrapper annotations are not required, they will be generated on demand using sensible defaults."
msgstr ""
-"Wrapped is an implementation detail from the Java domain. Neither in the "
-"abstract contract (i.e. 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. <programlisting>\n"
+"Wrapped is an implementation detail from the Java domain. Neither in the abstract contract (i.e. 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. <programlisting>\n"
"\n"
"@WebService\n"
"public class DocWrappedServiceImpl\n"
@@ -275,9 +219,7 @@
" ...\n"
" }\n"
" }\n"
-"</programlisting> Note, that with JBossWS the request/response wrapper "
-"annotations are not required, they will be generated on demand using "
-"sensible defaults."
+"</programlisting> Note, that with JBossWS the request/response wrapper annotations are not required, they will be generated on demand using sensible defaults."
#. Tag: title
#: Web_Services.xml:45
@@ -288,53 +230,35 @@
#. Tag: para
#: Web_Services.xml:46
#, 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: <itemizedlist> <listitem> <para> The "
-"port type operation name defines the endpoint method name </para> </"
-"listitem> <listitem> <para> Message parts are endpoint method parameters </"
-"para> </listitem> </itemizedlist> RPC is defined by the style attribute on "
-"the SOAP binding."
-msgstr ""
-"使用 RPC 时，wrapper 元素命名了终端操作。RPC 的子元素是单个的参数。SOAP 主体是基于一些简单的规则进行构建的：<itemizedlist> <listitem> <para> port type 操作的名称定义了终端方法的名称 </para> </"
-"listitem> <listitem> <para> Message parts 是终端方法的参数 </"
-"para> </listitem> </itemizedlist> RPC 由 SOAP 绑定的 style 属性定义的。"
+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: <itemizedlist> <listitem> <para> The port type operation name defines the endpoint method name </para> </listitem> <listitem> <para> Message parts are endpoint method parameters </para> </listitem> </itemizedlist> RPC is defined by the style attribute on the SOAP binding."
+msgstr "使用 RPC 时，wrapper 元素命名了终端操作。RPC 的子元素是单个的参数。SOAP 主体是基于一些简单的规则进行构建的：<itemizedlist> <listitem> <para> port type 操作的名称定义了终端方法的名称 </para> </listitem> <listitem> <para> Message parts 是终端方法的参数 </para> </listitem> </itemizedlist> RPC 由 SOAP 绑定的 style 属性定义的。"
#. Tag: programlisting
#: Web_Services.xml:60
#, no-c-format
msgid ""
-"<binding name='EndpointInterfaceBinding' type='tns:"
-"EndpointInterface'>\n"
-" <soap:binding style='rpc' transport='http://schemas."
-"xmlsoap.org/soap/http'/>\n"
+"<binding name='EndpointInterfaceBinding' type='tns:EndpointInterface'>\n"
+" <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/>\n"
" <operation name='echo'>\n"
" <soap:operation soapAction=''/>\n"
" <input>\n"
-" <soap:body namespace='http://org.jboss.ws/"
-"samples/jsr181pojo' use='literal'/>\n"
+" <soap:body namespace='http://org.jboss.ws/samples/jsr181pojo' use='literal'/>\n"
" </input>\n"
" <output>\n"
-" <soap:body namespace='http://org.jboss.ws/"
-"samples/jsr181pojo' use='literal'/>\n"
+" <soap:body namespace='http://org.jboss.ws/samples/jsr181pojo' use='literal'/>\n"
" </output>\n"
" </operation>\n"
" </binding>"
msgstr ""
-"<binding name='EndpointInterfaceBinding' type='tns:"
-"EndpointInterface'>\n"
-" <soap:binding style='rpc' transport='http://schemas."
-"xmlsoap.org/soap/http'/>\n"
+"<binding name='EndpointInterfaceBinding' type='tns:EndpointInterface'>\n"
+" <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/>\n"
" <operation name='echo'>\n"
" <soap:operation soapAction=''/>\n"
" <input>\n"
-" <soap:body namespace='http://org.jboss.ws/"
-"samples/jsr181pojo' use='literal'/>\n"
+" <soap:body namespace='http://org.jboss.ws/samples/jsr181pojo' use='literal'/>\n"
" </input>\n"
" <output>\n"
-" <soap:body namespace='http://org.jboss.ws/"
-"samples/jsr181pojo' use='literal'/>\n"
+" <soap:body namespace='http://org.jboss.ws/samples/jsr181pojo' use='literal'/>\n"
" </output>\n"
" </operation>\n"
" </binding>"
@@ -343,27 +267,21 @@
#: Web_Services.xml:62
#, no-c-format
msgid ""
-"With rpc style web services the portType names the operation (i.e. the java "
-"method on the endpoint) <programlisting>\n"
+"With rpc style web services the portType names the operation (i.e. the java method on the endpoint) <programlisting>\n"
" <portType name='EndpointInterface'>\n"
-" <operation name='echo' parameterOrder='"
-"String_1'>\n"
-" <input message='tns:EndpointInterface_echo'/"
-">\n"
-" <output message='tns:"
-"EndpointInterface_echoResponse'/>\n"
+" <operation name='echo' parameterOrder='String_1'>\n"
+" <input message='tns:EndpointInterface_echo'/>\n"
+" <output message='tns:EndpointInterface_echoResponse'/>\n"
" </operation>\n"
" </portType> \n"
-"</programlisting> Operation parameters are defined by individual message "
-"parts. <programlisting>\n"
+"</programlisting> Operation parameters are defined by individual message parts. <programlisting>\n"
" <message name='EndpointInterface_echo'>\n"
" <part name='String_1' type='xsd:string'/>\n"
" </message>\n"
" <message name='EndpointInterface_echoResponse'>\n"
" <part name='result' type='xsd:string'/>\n"
" </message>\n"
-"</programlisting> Note, there is no complex type in XML schema that could "
-"validate the entire SOAP message payload. <programlisting>\n"
+"</programlisting> Note, there is no complex type in XML schema that could validate the entire SOAP message payload. <programlisting>\n"
"\n"
" @WebService\n"
" @SOAPBinding(style = SOAPBinding.Style.RPC)\n"
@@ -376,31 +294,23 @@
" ...\n"
" }\n"
"} \n"
-"</programlisting> 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."
+"</programlisting> 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 ""
-"With rpc style web services the portType names the operation (i.e. the java "
-"method on the endpoint) <programlisting>\n"
+"With rpc style web services the portType names the operation (i.e. the java method on the endpoint) <programlisting>\n"
" <portType name='EndpointInterface'>\n"
-" <operation name='echo' parameterOrder='"
-"String_1'>\n"
-" <input message='tns:EndpointInterface_echo'/"
-">\n"
-" <output message='tns:"
-"EndpointInterface_echoResponse'/>\n"
+" <operation name='echo' parameterOrder='String_1'>\n"
+" <input message='tns:EndpointInterface_echo'/>\n"
+" <output message='tns:EndpointInterface_echoResponse'/>\n"
" </operation>\n"
" </portType> \n"
-"</programlisting> Operation parameters are defined by individual message "
-"parts. <programlisting>\n"
+"</programlisting> Operation parameters are defined by individual message parts. <programlisting>\n"
" <message name='EndpointInterface_echo'>\n"
" <part name='String_1' type='xsd:string'/>\n"
" </message>\n"
" <message name='EndpointInterface_echoResponse'>\n"
" <part name='result' type='xsd:string'/>\n"
" </message>\n"
-"</programlisting> Note, there is no complex type in XML schema that could "
-"validate the entire SOAP message payload. <programlisting>\n"
+"</programlisting> Note, there is no complex type in XML schema that could validate the entire SOAP message payload. <programlisting>\n"
"\n"
" @WebService\n"
" @SOAPBinding(style = SOAPBinding.Style.RPC)\n"
@@ -413,9 +323,7 @@
" ...\n"
" }\n"
"} \n"
-"</programlisting> 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."
+"</programlisting> 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."
#. Tag: title
#: Web_Services.xml:72
@@ -426,18 +334,7 @@
#. Tag: para
#: Web_Services.xml:73
#, 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:-"
+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 ""
#. Tag: para
@@ -455,33 +352,25 @@
#. Tag: title
#: Web_Services.xml:90
#, no-c-format
-#, fuzzy
msgid "Web Service Endpoints"
msgstr "代理服务"
#. Tag: para
#: Web_Services.xml:91
#, 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 (i.e. wsdl+schema) for client "
-"consumption. All marshalling/unmarshalling is delegated to 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 (i.e. wsdl+schema) for client consumption. All marshalling/unmarshalling is delegated to JAXB [2]."
msgstr ""
#. Tag: title
#: Web_Services.xml:97
#, no-c-format
msgid "Plain old Java Object (POJO)"
-msgstr ""
+msgstr "Plain old Java Object (POJO)"
#. Tag: para
#: Web_Services.xml:98
#, no-c-format
-msgid ""
-"Let's take a look at simple POJO endpoint implementation. All endpoint "
-"associated metadata is provided via JSR-181 annotations"
+msgid "Let's take a look at simple POJO endpoint implementation. All endpoint associated metadata is provided via JSR-181 annotations"
msgstr ""
#. Tag: programlisting
@@ -512,9 +401,9 @@
#. Tag: title
#: Web_Services.xml:105
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The endpoint as a web application"
-msgstr "设置 web 应用程序的上下文根目录（context root）"
+msgstr "作为 web 应用程序的终端"
#. Tag: para
#: Web_Services.xml:106
@@ -529,8 +418,7 @@
"<web-app ...>\n"
" <servlet>\n"
" <servlet-name>TestService</servlet-name>\n"
-" <servlet-class>org.jboss.test.ws.jaxws.samples.jsr181pojo."
-"JSEBean01</servlet-class>\n"
+" <servlet-class>org.jboss.test.ws.jaxws.samples.jsr181pojo.JSEBean01</servlet-class>\n"
" </servlet>\n"
" <servlet-mapping>\n"
" <servlet-name>TestService</servlet-name>\n"
@@ -541,8 +429,7 @@
"<web-app ...>\n"
" <servlet>\n"
" <servlet-name>TestService</servlet-name>\n"
-" <servlet-class>org.jboss.test.ws.jaxws.samples.jsr181pojo."
-"JSEBean01</servlet-class>\n"
+" <servlet-class>org.jboss.test.ws.jaxws.samples.jsr181pojo.JSEBean01</servlet-class>\n"
" </servlet>\n"
" <servlet-mapping>\n"
" <servlet-name>TestService</servlet-name>\n"
@@ -560,63 +447,51 @@
#: Web_Services.xml:114
#, no-c-format
msgid ""
-"A JSR-181 java service endpoint (JSE) is packaged as a web application in a "
-"*.war file. <programlisting>\n"
+"A JSR-181 java service endpoint (JSE) is packaged as a web application in a *.war file. <programlisting>\n"
"\n"
" <war warfile=\"${build.dir}/libs/jbossws-samples-jsr181pojo.war\" \n"
-" webxml=\"${build.resources.dir}/samples/jsr181pojo/WEB-"
-"INF/web.xml\">\n"
+" webxml=\"${build.resources.dir}/samples/jsr181pojo/WEB-INF/web.xml\">\n"
" <classes dir=\"${build.dir}/classes\">\n"
-" <include name=\"org/jboss/test/ws/samples/jsr181pojo/JSEBean01.class\"/"
-">\n"
+" <include name=\"org/jboss/test/ws/samples/jsr181pojo/JSEBean01.class\"/>\n"
" </classes>\n"
"</war> \n"
-"</programlisting> Note, only the endpoint implementation bean and web.xml "
-"are required."
+"</programlisting> Note, only the endpoint implementation bean and web.xml are required."
msgstr ""
-"A JSR-181 java service endpoint (JSE) is packaged as a web application in a "
-"*.war file. <programlisting>\n"
+"A JSR-181 java service endpoint (JSE) is packaged as a web application in a *.war file. <programlisting>\n"
"\n"
" <war warfile=\"${build.dir}/libs/jbossws-samples-jsr181pojo.war\" \n"
-" webxml=\"${build.resources.dir}/samples/jsr181pojo/WEB-"
-"INF/web.xml\">\n"
+" webxml=\"${build.resources.dir}/samples/jsr181pojo/WEB-INF/web.xml\">\n"
" <classes dir=\"${build.dir}/classes\">\n"
-" <include name=\"org/jboss/test/ws/samples/jsr181pojo/JSEBean01.class\"/"
-">\n"
+" <include name=\"org/jboss/test/ws/samples/jsr181pojo/JSEBean01.class\"/>\n"
" </classes>\n"
"</war> \n"
-"</programlisting> Note, only the endpoint implementation bean and web.xml "
-"are required."
+"</programlisting> Note, only the endpoint implementation bean and web.xml are required."
#. Tag: title
#: Web_Services.xml:122
#, no-c-format
msgid "<title>Accessing the generated WSDL</title>"
-msgstr ""
+msgstr "<title>访问生成的 WSDL</title>"
#. Tag: para
-#: Web_Services.xml:123 Web_Services.xml:151
+#: Web_Services.xml:123
+#: Web_Services.xml:151
#, 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."
+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 ""
#. Tag: programlisting
-#: Web_Services.xml:127 Web_Services.xml:154
+#: Web_Services.xml:127
+#: Web_Services.xml:154
#, no-c-format
msgid "http://yourhost:8080/jbossws/services"
msgstr "http://yourhost:8080/jbossws/services"
#. Tag: para
-#: Web_Services.xml:127 Web_Services.xml:155
+#: Web_Services.xml:127
+#: Web_Services.xml:155
#, no-c-format
-msgid ""
-"Note, it is also possible to generate the abstract contract off line using "
-"jbossw tools. For details of that please see <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 "Note, it is also possible to generate the abstract contract off line using jbossw tools. For details of that please see <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>"
msgstr ""
#. Tag: title
@@ -628,17 +503,8 @@
#. Tag: para
#: Web_Services.xml:134
#, 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://jbws.dyndns.org/mediawiki/"
-"index.php?title=JAX-WS_User_Guide#_Plain_old_Java_Object_.28POJO.29\"># "
-"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://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#_Plain_old_Java_Object_.28POJO.29\"># 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: programlisting
#: Web_Services.xml:137
@@ -677,44 +543,36 @@
#. Tag: para
#: Web_Services.xml:138
#, no-c-format
-msgid ""
-"Above you see an EJB-3.0 stateless session bean that exposes one method both "
-"on the remote interface and on and as an endpoint operation."
+msgid "Above you see an EJB-3.0 stateless session bean that exposes one method both on the remote interface and on and as an endpoint operation."
msgstr ""
#. Tag: emphasis
#: Web_Services.xml:142
#, no-c-format
msgid "<emphasis>Packaging the endpoint</emphasis>"
-msgstr ""
+msgstr "<emphasis>将终端打包</emphasis>"
#. Tag: para
#: Web_Services.xml:144
#, no-c-format
msgid "A JSR-181 EJB service endpoint is packaged as an ordinary ejb deployment."
-msgstr ""
+msgstr "JSR-181 EJB 服务终端作为普通的 EJB 部署文件打包。"
#. Tag: programlisting
#: Web_Services.xml:147
#, no-c-format
msgid ""
-"<jar jarfile="${build.dir}/libs/jbossws-samples-jsr181ejb.jar""
-">\n"
+"<jar jarfile="${build.dir}/libs/jbossws-samples-jsr181ejb.jar">\n"
"<fileset dir="${build.dir}/classes">\n"
-"<include name="org/jboss/test/ws/samples/jsr181ejb/EJB3Bean01."
-"class"/>\n"
-"<include name="org/jboss/test/ws/samples/jsr181ejb/"
-"EJB3RemoteInterface.class"/>\n"
+"<include name="org/jboss/test/ws/samples/jsr181ejb/EJB3Bean01.class"/>\n"
+"<include name="org/jboss/test/ws/samples/jsr181ejb/EJB3RemoteInterface.class"/>\n"
"</fileset>\n"
"</jar>"
msgstr ""
-"<jar jarfile="${build.dir}/libs/jbossws-samples-jsr181ejb.jar""
-">\n"
+"<jar jarfile="${build.dir}/libs/jbossws-samples-jsr181ejb.jar">\n"
"<fileset dir="${build.dir}/classes">\n"
-"<include name="org/jboss/test/ws/samples/jsr181ejb/EJB3Bean01."
-"class"/>\n"
-"<include name="org/jboss/test/ws/samples/jsr181ejb/"
-"EJB3RemoteInterface.class"/>\n"
+"<include name="org/jboss/test/ws/samples/jsr181ejb/EJB3Bean01.class"/>\n"
+"<include name="org/jboss/test/ws/samples/jsr181ejb/EJB3RemoteInterface.class"/>\n"
"</fileset>\n"
"</jar>"
@@ -722,47 +580,35 @@
#: Web_Services.xml:149
#, no-c-format
msgid "<emphasis>Accessing the generated WSDL</emphasis>"
-msgstr ""
+msgstr "<emphasis>访问生成的 WSDL</emphasis>"
#. Tag: title
#: Web_Services.xml:161
#, no-c-format
msgid "Endpoint Provider"
-msgstr ""
+msgstr "终端提供者"
#. Tag: para
#: Web_Services.xml:162
#, 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."
+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 ""
#. Tag: para
#: Web_Services.xml:165
#, 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."
+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 ""
#. Tag: para
#: Web_Services.xml:168
#, 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 ""
#. Tag: programlisting
#: Web_Services.xml:171
#, no-c-format
-#, fuzzy
msgid ""
"@WebServiceProvider\n"
"@ServiceMode(value = Service.Mode.PAYLOAD)\n"
@@ -778,11 +624,7 @@
#. Tag: para
#: Web_Services.xml:172
#, no-c-format
-#, fuzzy
-msgid ""
-"Note, Service.Mode.PAYLOAD is the default and does not have to be declared "
-"explicitly. You can also use Service.Mode.MESSAGE to access the entire SOAP "
-"message (i.e. with MESSAGE the Provider can also see SOAP Headers)"
+msgid "Note, Service.Mode.PAYLOAD is the default and does not have to be declared explicitly. You can also use Service.Mode.MESSAGE to access the entire SOAP message (i.e. with MESSAGE the Provider can also see SOAP Headers)"
msgstr "服务 服务"
#. Tag: title
@@ -794,13 +636,7 @@
#. Tag: para
#: Web_Services.xml:179
#, no-c-format
-#, fuzzy
-msgid ""
-"The WebServiceContext is treated as an injectable resource that can be set "
-"at the time an endpoint is initialized. The WebServiceContext 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 WebServiceContext is treated as an injectable resource that can be set at the time an endpoint is initialized. The WebServiceContext 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: programlisting
@@ -816,8 +652,7 @@
"@WebMethod\n"
"public String testGetMessageContext()\n"
"{\n"
-"SOAPMessageContext jaxwsContext = (SOAPMessageContext)wsCtx.getMessageContext"
-"();\n"
+"SOAPMessageContext jaxwsContext = (SOAPMessageContext)wsCtx.getMessageContext();\n"
"return jaxwsContext != null ? "pass" : "fail";\n"
"}\n"
"..\n"
@@ -844,8 +679,7 @@
"@WebMethod\n"
"public String testGetMessageContext()\n"
"{\n"
-"SOAPMessageContext jaxwsContext = (SOAPMessageContext)wsCtx.getMessageContext"
-"();\n"
+"SOAPMessageContext jaxwsContext = (SOAPMessageContext)wsCtx.getMessageContext();\n"
"return jaxwsContext != null ? "pass" : "fail";\n"
"}\n"
"..\n"
@@ -866,41 +700,30 @@
#. Tag: title
#: Web_Services.xml:186
#, no-c-format
-#, fuzzy
msgid "Web Service Clients"
msgstr "代理服务"
#. Tag: title
#: Web_Services.xml:188
#, no-c-format
-#, fuzzy
msgid "Service"
msgstr "服务"
#. Tag: para
#: Web_Services.xml:189
#, no-c-format
-#, fuzzy
-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
#: Web_Services.xml:192
#, 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)."
+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
#: Web_Services.xml:196
#, no-c-format
-#, fuzzy
msgid "Service Usage"
msgstr "代理服务"
@@ -913,57 +736,39 @@
#. Tag: para
#: Web_Services.xml:200
#, 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."
+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
#: Web_Services.xml:203
#, 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."
+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
#: Web_Services.xml:206
#, 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."
+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
#: Web_Services.xml:209
#, 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: programlisting
#: Web_Services.xml:212
#, no-c-format
-#, fuzzy
msgid ""
"// Generated Service Class\n"
" \n"
-" @WebServiceClient(name="StockQuoteService", targetNamespace=""
-"http://example.com/stocks", wsdlLocation="http://example.com/"
-"stocks.wsdl")\n"
+" @WebServiceClient(name="StockQuoteService", targetNamespace="http://example.com/stocks", wsdlLocation="http://example.com/stocks.wsdl")\n"
"public class StockQuoteService extends javax.xml.ws.Service \n"
"{\n"
"public StockQuoteService() \n"
"{\n"
-"super(new URL("http://example.com/stocks.wsdl"), new QName(""
-"http://example.com/stocks", "StockQuoteService"));\n"
+"super(new URL("http://example.com/stocks.wsdl"), new QName("http://example.com/stocks", "StockQuoteService"));\n"
"}\n"
" \n"
"public StockQuoteService(String wsdlLocation, QName serviceName) \n"
@@ -982,17 +787,8 @@
#. Tag: para
#: Web_Services.xml:213
#, no-c-format
-msgid ""
-"Section <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#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://jbws.dyndns.org/"
-"mediawiki/index.php?title=JAX-WS_User_Guide#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://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#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://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#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: emphasis
#: Web_Services.xml:217
@@ -1003,30 +799,22 @@
#. Tag: para
#: Web_Services.xml:219
#, no-c-format
-#, fuzzy
-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: programlisting
#: Web_Services.xml:222
#, no-c-format
-#, fuzzy
msgid ""
"URL wsdlLocation = new URL("http://example.org/my.wsdl");\n"
-"QName serviceName = new QName("http://example.org/sample", ""
-"MyService");\n"
+"QName serviceName = new QName("http://example.org/sample", "MyService");\n"
"Service service = Service.create(wsdlLocation, serviceName);"
msgstr ""http://example.org/my.wsdl""http://example.org/sample""" 服务"
#. Tag: para
#: Web_Services.xml:223
#, no-c-format
-msgid ""
-"This is the nastiest way to work with JBossWs. Older versions have extensive "
-"details on DII as it was then known."
+msgid "This is the nastiest way to work with JBossWs. Older versions have extensive details on DII as it was then known."
msgstr ""
#. Tag: title
@@ -1038,28 +826,13 @@
#. Tag: para
#: Web_Services.xml:230
#, no-c-format
-#, fuzzy
-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://jbws.dyndns.org/mediawiki/index.php?"
-"title=JAX-WS_User_Guide#Handler_Framework\">#Handler Framework</ulink> "
-"describes the handler framework in detail. A Service instance provides "
-"access to a HandlerResolver via a pair of getHandlerResolver/"
-"setHandlerResolver methods that may be used to configure a set of handlers "
-"on a per-service, per-port or per-protocol binding basis."
+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://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Handler_Framework\">#Handler Framework</ulink> describes the handler framework in detail. A Service instance provides access to a HandlerResolver via a pair of getHandlerResolver/setHandlerResolver 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
#: Web_Services.xml:233
#, no-c-format
-#, fuzzy
-msgid ""
-"When a Service instance is used to create a proxy or a Dispatch 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 Service instance do not affect the handlers on "
-"previously created proxies, or Dispatch instances."
+msgid "When a Service instance is used to create a proxy or a Dispatch 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 Service instance do not affect the handlers on previously created proxies, or Dispatch instances."
msgstr "服务 服务."
#. Tag: title
@@ -1071,13 +844,7 @@
#. Tag: para
#: Web_Services.xml:240
#, no-c-format
-#, fuzzy
-msgid ""
-"Service instances can be configured with a java.util.concurrent.Executor. "
-"The executor will then be used to invoke any asynchronous callbacks "
-"requested by the application. The setExecutor and getExecutor methods of "
-"Service can be used to modify and retrieve the executor configured for a "
-"service."
+msgid "Service instances can be configured with a java.util.concurrent.Executor. The executor will then be used to invoke any asynchronous callbacks requested by the application. The setExecutor and getExecutor methods of Service can be used to modify and retrieve the executor configured for a service."
msgstr "服务 服务."
#. Tag: title
@@ -1089,11 +856,7 @@
#. Tag: para
#: Web_Services.xml:249
#, no-c-format
-#, fuzzy
-msgid ""
-"You can create an instance of a client proxy using one of getPort methods on "
-"the <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Service\">#Service</ulink>."
+msgid "You can create an instance of a client proxy using one of getPort methods on the <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Service\">#Service</ulink>."
msgstr "<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Service\"> 服务</ulink>."
#. Tag: programlisting
@@ -1107,8 +870,7 @@
" * specifies the service endpoint interface that is supported by\n"
" * the created dynamic proxy instance.\n"
" **/\n"
-" public <T> T getPort(QName portName, Class<T> "
-"serviceEndpointInterface)\n"
+" public <T> T getPort(QName portName, Class<T> serviceEndpointInterface)\n"
" {\n"
" ...\n"
" }\n"
@@ -1135,8 +897,7 @@
" * specifies the service endpoint interface that is supported by\n"
" * the created dynamic proxy instance.\n"
" **/\n"
-" public <T> T getPort(QName portName, Class<T> "
-"serviceEndpointInterface)\n"
+" public <T> T getPort(QName portName, Class<T> serviceEndpointInterface)\n"
" {\n"
" ...\n"
" }\n"
@@ -1159,33 +920,21 @@
#. Tag: para
#: Web_Services.xml:253
#, no-c-format
-msgid ""
-"The service endpoint interface (SEI) is usually generated using tools. For "
-"details see <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 service endpoint interface (SEI) is usually generated using tools. For details see <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>"
msgstr ""
#. Tag: para
#: Web_Services.xml:256
#, no-c-format
-#, fuzzy
-msgid ""
-"A generated static <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?"
-"title=JAX-WS_User_Guide#Service\">#Service</ulink> usually also offers typed "
-"methods to get ports. These methods also return dynamic proxies that "
-"implement the SEI."
+msgid "A generated static <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Service\">#Service</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: programlisting
#: Web_Services.xml:259
#, no-c-format
-#, fuzzy
msgid ""
-"@WebServiceClient(name = "TestEndpointService", targetNamespace = "
-""http://org.jboss.ws/wsref", \n"
-" wsdlLocation = "http://localhost.localdomain:8080/jaxws-samples-"
-"webserviceref?wsdl")\n"
+"@WebServiceClient(name = "TestEndpointService", targetNamespace = "http://org.jboss.ws/wsref", \n"
+" wsdlLocation = "http://localhost.localdomain:8080/jaxws-samples-webserviceref?wsdl")\n"
" \n"
" public class TestEndpointService extends Service\n"
" {\n"
@@ -1198,8 +947,7 @@
" @WebEndpoint(name = "TestEndpointPort")\n"
" public TestEndpoint getTestEndpointPort() \n"
" {\n"
-" return (TestEndpoint)super.getPort(TESTENDPOINTPORT, TestEndpoint."
-"class);\n"
+" return (TestEndpoint)super.getPort(TESTENDPOINTPORT, TestEndpoint.class);\n"
" }\n"
" }"
msgstr ""
@@ -1223,58 +971,36 @@
#. Tag: title
#: Web_Services.xml:263
#, no-c-format
-#, fuzzy
msgid "WebServiceRef"
msgstr "代理服务"
#. Tag: para
#: Web_Services.xml:264
#, no-c-format
-#, fuzzy
-msgid ""
-"The WebServiceRef annotation is used to declare a reference to a Web "
-"service. It follows the resource pattern exemplified by the javax.annotation."
-"Resource annotation in JSR-250 [5]"
+msgid "The WebServiceRef annotation is used to declare a reference to a Web service. It follows the resource pattern exemplified by the javax.annotation.Resource annotation in JSR-250 [5]"
msgstr "代理服务"
#. Tag: para
#: Web_Services.xml:267
#, no-c-format
-#, fuzzy
msgid "There are two uses to the WebServiceRef annotation:"
msgstr "代理服务:"
#. Tag: para
#: Web_Services.xml:272
#, 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/method "
-"declaration the annotation is applied to, the type and value elements MAY "
-"have the default value (Object.class, that is). If the type cannot be "
-"inferred, then at least the type element MUST be present with a non-default "
-"value."
+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/method declaration the annotation is applied to, the type and value elements MAY have the default value (Object.class, that is). If the type cannot be inferred, then at least the type element MUST be present with a non-default value."
msgstr ""
#. Tag: para
#: Web_Services.xml:277
#, no-c-format
-#, fuzzy
-msgid ""
-"To define a reference whose type is a SEI. In this case, the type element "
-"MAY be present with its default value if the type of the reference can be "
-"inferred from the annotated field/method declaration, but the value element "
-"MUST always be present and refer to a generated service class type (a "
-"subtype of javax.xml.ws.Service). The wsdlLocation element, if present, "
-"overrides theWSDL location information specified in the WebService "
-"annotation of the referenced generated service class."
+msgid "To define a reference whose type is a SEI. In this case, the type element MAY be present with its default value if the type of the reference can be inferred from the annotated field/method declaration, but the value element MUST always be present and refer to a generated service class type (a subtype of javax.xml.ws.Service). The wsdlLocation element, if present, overrides theWSDL location information specified in the WebService annotation of the referenced generated service class."
msgstr "服务."
#. Tag: programlisting
#: Web_Services.xml:282
#, no-c-format
-#, fuzzy
msgid ""
"public class EJB3Client implements EJB3Remote\n"
"{\n"
@@ -1293,17 +1019,13 @@
#. Tag: emphasis
#: Web_Services.xml:284
#, no-c-format
-#, fuzzy
msgid "WebServiceRef Customization"
msgstr "代理服务"
#. Tag: para
#: Web_Services.xml:286
#, no-c-format
-#, fuzzy
-msgid ""
-"In jboss-5.0.x we offer a number of overrides and extensions to the "
-"WebServiceRef annotation. These include"
+msgid "In jboss-5.0.x we offer a number of overrides and extensions to the WebServiceRef annotation. These include"
msgstr "代理服务"
#. Tag: para
@@ -1326,9 +1048,9 @@
#. Tag: para
#: Web_Services.xml:306
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Example:"
-msgstr "XMBean示例"
+msgstr "示例："
#. Tag: programlisting
#: Web_Services.xml:309
@@ -1336,29 +1058,23 @@
msgid ""
"<service-ref>\n"
"<service-ref-name>OrganizationService</service-ref-name>\n"
-"<wsdl-override>file:/wsdlRepository/organization-service.wsdl</wsdl-"
-"override>\n"
+"<wsdl-override>file:/wsdlRepository/organization-service.wsdl</wsdl-override>\n"
"</service-ref>\n"
".. \n"
"<service-ref>\n"
"<service-ref-name>OrganizationService</service-ref-name>\n"
"<config-name>Secure Client Config</config-name>\n"
"<config-file>META-INF/jbossws-client-config.xml</config-file>\n"
-"<handler-chain>META-INF/jbossws-client-handlers.xml</handler-"
-"chain>\n"
+"<handler-chain>META-INF/jbossws-client-handlers.xml</handler-chain>\n"
"</service-ref>\n"
" \n"
"<service-ref>\n"
"<service-ref-name>SecureService</service-ref-name>\n"
-"<service-class-name>org.jboss.tests.ws.jaxws.webserviceref."
-"SecureEndpointService</service-class-name>\n"
-"<service-qname>{http://org.jboss.ws/wsref}SecureEndpointService</"
-"service-qname>\n"
+"<service-class-name>org.jboss.tests.ws.jaxws.webserviceref.SecureEndpointService</service-class-name>\n"
+"<service-qname>{http://org.jboss.ws/wsref}SecureEndpointService</service-qname>\n"
"<port-info>\n"
-"<service-endpoint-interface>org.jboss.tests.ws.jaxws.webserviceref."
-"SecureEndpoint</service-endpoint-interface>\n"
-"<port-qname>{http://org.jboss.ws/wsref}SecureEndpointPort</port-"
-"qname>\n"
+"<service-endpoint-interface>org.jboss.tests.ws.jaxws.webserviceref.SecureEndpoint</service-endpoint-interface>\n"
+"<port-qname>{http://org.jboss.ws/wsref}SecureEndpointPort</port-qname>\n"
"<stub-property>\n"
"<name>javax.xml.ws.security.auth.username</name>\n"
"<value>kermit</value>\n"
@@ -1372,29 +1088,23 @@
msgstr ""
"<service-ref>\n"
"<service-ref-name>OrganizationService</service-ref-name>\n"
-"<wsdl-override>file:/wsdlRepository/organization-service.wsdl</wsdl-"
-"override>\n"
+"<wsdl-override>file:/wsdlRepository/organization-service.wsdl</wsdl-override>\n"
"</service-ref>\n"
".. \n"
"<service-ref>\n"
"<service-ref-name>OrganizationService</service-ref-name>\n"
"<config-name>Secure Client Config</config-name>\n"
"<config-file>META-INF/jbossws-client-config.xml</config-file>\n"
-"<handler-chain>META-INF/jbossws-client-handlers.xml</handler-"
-"chain>\n"
+"<handler-chain>META-INF/jbossws-client-handlers.xml</handler-chain>\n"
"</service-ref>\n"
" \n"
"<service-ref>\n"
"<service-ref-name>SecureService</service-ref-name>\n"
-"<service-class-name>org.jboss.tests.ws.jaxws.webserviceref."
-"SecureEndpointService</service-class-name>\n"
-"<service-qname>{http://org.jboss.ws/wsref}SecureEndpointService</"
-"service-qname>\n"
+"<service-class-name>org.jboss.tests.ws.jaxws.webserviceref.SecureEndpointService</service-class-name>\n"
+"<service-qname>{http://org.jboss.ws/wsref}SecureEndpointService</service-qname>\n"
"<port-info>\n"
-"<service-endpoint-interface>org.jboss.tests.ws.jaxws.webserviceref."
-"SecureEndpoint</service-endpoint-interface>\n"
-"<port-qname>{http://org.jboss.ws/wsref}SecureEndpointPort</port-"
-"qname>\n"
+"<service-endpoint-interface>org.jboss.tests.ws.jaxws.webserviceref.SecureEndpoint</service-endpoint-interface>\n"
+"<port-qname>{http://org.jboss.ws/wsref}SecureEndpointPort</port-qname>\n"
"<stub-property>\n"
"<name>javax.xml.ws.security.auth.username</name>\n"
"<value>kermit</value>\n"
@@ -1408,11 +1118,9 @@
#. Tag: para
#: Web_Services.xml:310
-#, fuzzy, no-c-format
-msgid ""
-"For details please see <emphasis role=\"bold\">service-ref_5_0.dtd</"
-"emphasis> in the jboss docs directory."
-msgstr "<emphasis role=\"bold\">file:/var/opt/apps/</emphasis>扫描指定的目录"
+#, no-c-format
+msgid "For details please see <emphasis role=\"bold\">service-ref_5_0.dtd</emphasis> in the jboss docs directory."
+msgstr "详情请参考 jboss docs 目录里的 <emphasis role=\"bold\">service-ref_5_0.dtd</emphasis>。"
#. Tag: title
#: Web_Services.xml:316
@@ -1423,72 +1131,45 @@
#. Tag: para
#: Web_Services.xml:317
#, no-c-format
-msgid ""
-"XMLWeb 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 "XMLWeb 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
#: Web_Services.xml:320
#, no-c-format
-#, fuzzy
-msgid ""
-"Dispatch supports two usage modes, identified by the constants javax.xml.ws."
-"Service.Mode.MESSAGE and javax.xml.ws.Service.Mode.PAYLOAD respectively:"
+msgid "Dispatch supports two usage modes, identified by the constants javax.xml.ws.Service.Mode.MESSAGE and javax.xml.ws.Service.Mode.PAYLOAD respectively:"
msgstr "服务 服务:"
#. Tag: para
#: Web_Services.xml:323
#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Message</emphasis> In this mode, client applications "
-"work directly with protocol-specific message structures. E.g., when used "
-"with a SOAP protocol binding, a client application would work directly with "
-"a SOAP message."
+msgid "<emphasis role=\"bold\">Message</emphasis> In this mode, client applications work directly with protocol-specific message structures. E.g., when used with a SOAP protocol binding, a client application would work directly with a SOAP message."
msgstr ""
#. Tag: para
#: Web_Services.xml:326
#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Message Payload</emphasis> In this mode, client "
-"applications work with the payload of messages rather than the messages "
-"themselves. E.g., 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."
+msgid "<emphasis role=\"bold\">Message Payload</emphasis> In this mode, client applications work with the payload of messages rather than the messages themselves. E.g., 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 ""
#. Tag: para
#: Web_Services.xml:329
#, 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."
+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 ""
#. Tag: programlisting
#: Web_Services.xml:332
#, no-c-format
-#, fuzzy
msgid ""
"Service service = Service.create(wsdlURL, serviceName);\n"
-"Dispatch dispatch = service.createDispatch(portName, StreamSource.class, "
-"Mode.PAYLOAD);\n"
+"Dispatch dispatch = service.createDispatch(portName, StreamSource.class, Mode.PAYLOAD);\n"
" \n"
-"String payload = "<ns1:ping xmlns:ns1='http://oneway.samples."
-"jaxws.ws.test.jboss.org/'/>";\n"
+"String payload = "<ns1:ping xmlns:ns1='http://oneway.samples.jaxws.ws.test.jboss.org/'/>";\n"
"dispatch.invokeOneWay(new StreamSource(new StringReader(payload)));\n"
" \n"
-"payload = "<ns1:feedback xmlns:ns1='http://oneway.samples.jaxws."
-"ws.test.jboss.org/'/>";\n"
-"Source retObj = (Source)dispatch.invoke(new StreamSource(new StringReader"
-"(payload)));"
+"payload = "<ns1:feedback xmlns:ns1='http://oneway.samples.jaxws.ws.test.jboss.org/'/>";\n"
+"Source retObj = (Source)dispatch.invoke(new StreamSource(new StringReader(payload)));"
msgstr ""
"服务 服务\n"
""<'http://oneway.samples.jaxws.ws.test.jboss.org/'>"\n"
@@ -1503,32 +1184,22 @@
#. Tag: para
#: Web_Services.xml:337
#, no-c-format
-msgid ""
-"The BindingProvider interface represents a component that provides a "
-"protocol binding for use by clients, it is implemented by proxies and is "
-"extended by the Dispatch interface."
+msgid "The BindingProvider interface represents a component that provides a protocol binding for use by clients, it is implemented by proxies and is extended by the Dispatch interface."
msgstr ""
#. Tag: para
#: Web_Services.xml:340
#, no-c-format
-msgid ""
-"BindingProvider instances may provide asynchronous operation capabilities. "
-"When used, asynchronous operation invocations are decoupled from the "
-"BindingProvider 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 Response interface."
+msgid "BindingProvider instances may provide asynchronous operation capabilities. When used, asynchronous operation invocations are decoupled from the BindingProvider 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 Response interface."
msgstr ""
#. Tag: programlisting
#: Web_Services.xml:343
#, no-c-format
-#, fuzzy
msgid ""
"public void testInvokeAsync() throws Exception\n"
"{\n"
-"URL wsdlURL = new URL("http://" + getServerHost() + ":8080/"
-"jaxws-samples-asynchronous?wsdl");\n"
+"URL wsdlURL = new URL("http://" + getServerHost() + ":8080/jaxws-samples-asynchronous?wsdl");\n"
"QName serviceName = new QName(targetNS, "TestEndpointService");\n"
"Service service = Service.create(wsdlURL, serviceName);\n"
"TestEndpoint port = service.getPort(TestEndpoint.class);\n"
@@ -1553,10 +1224,7 @@
#. Tag: para
#: Web_Services.xml:348
#, no-c-format
-msgid ""
-"@Oneway indicates that the given web method has only an input message and no "
-"output. Typically, a oneway method returns the thread of control to the "
-"calling application prior to executing the actual business method."
+msgid "@Oneway indicates that the given web method has only an input message and no output. Typically, a oneway method returns the thread of control to the calling application prior to executing the actual business method."
msgstr ""
#. Tag: programlisting
@@ -1616,13 +1284,7 @@
#. Tag: para
#: Web_Services.xml:358
#, no-c-format
-#, fuzzy
-msgid ""
-"This sections describes concepts that apply equally to <ulink url=\"http://"
-"jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Web_Service_Endpoints\">#Web Service Endpoints</ulink> and "
-"<ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_User_Guide#Web_Service_Clients\">#Web Service Clients</ulink>"
+msgid "This sections describes concepts that apply equally to <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Web_Service_Endpoints\">#Web Service Endpoints</ulink> and <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#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
@@ -1634,34 +1296,19 @@
#. Tag: para
#: Web_Services.xml:363
#, 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."
+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
#: Web_Services.xml:366
#, 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."
+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
#: Web_Services.xml:369
#, 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
@@ -1673,11 +1320,7 @@
#. Tag: para
#: Web_Services.xml:374
#, 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 javax.xml.ws.handler.LogicalHandler."
+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 javax.xml.ws.handler.LogicalHandler."
msgstr ""
#. Tag: title
@@ -1689,27 +1332,19 @@
#. Tag: para
#: Web_Services.xml:381
#, 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 javax.xml.ws.handler."
-"Handler except javax.xml.ws.handler.LogicalHandler."
+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 javax.xml.ws.handler.Handler except javax.xml.ws.handler.LogicalHandler."
msgstr ""
#. Tag: title
#: Web_Services.xml:387
#, no-c-format
-#, fuzzy
msgid "Service endpoint handlers"
msgstr "服务"
#. Tag: para
#: Web_Services.xml:388
#, no-c-format
-msgid ""
-"On the service endpoint, handlers are defined using the @HandlerChain "
-"annotation."
+msgid "On the service endpoint, handlers are defined using the @HandlerChain annotation."
msgstr ""
#. Tag: programlisting
@@ -1723,6 +1358,12 @@
"...\n"
"}"
msgstr ""
+"@WebService\n"
+"@HandlerChain(file = "jaxws-server-source-handlers.xml")\n"
+"public class SOAPEndpointSourceImpl\n"
+"{\n"
+"...\n"
+"}"
#. Tag: para
#: Web_Services.xml:392
@@ -1733,38 +1374,30 @@
#. Tag: para
#: Web_Services.xml:395
#, 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>)"
+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 ""
#. Tag: para
#: Web_Services.xml:398
#, 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 ""
#. Tag: title
#: Web_Services.xml:404
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Service client handlers"
-msgstr "服务"
+msgstr "服务客户处理程序"
#. Tag: para
#: Web_Services.xml:405
#, no-c-format
-msgid ""
-"On the client side, handler can be configured using the @HandlerChain "
-"annotation on the SEI or dynamically using the API."
+msgid "On the client side, handler can be configured using the @HandlerChain annotation on the SEI or dynamically using the API."
msgstr ""
#. Tag: programlisting
#: Web_Services.xml:408
#, no-c-format
-#, fuzzy
msgid ""
"Service service = Service.create(wsdlURL, serviceName);\n"
"Endpoint port = (Endpoint)service.getPort(Endpoint.class);\n"
@@ -1788,27 +1421,13 @@
#. Tag: para
#: Web_Services.xml:415
#, no-c-format
-#, fuzzy
-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."
+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
#: Web_Services.xml:418
#, no-c-format
-msgid ""
-"Properties are scoped as either APPLICATION or HANDLER. All properties are "
-"available to all handlers for an instance of an MEP on a 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 of an MEP instance. APPLICATION scoped properties are "
-"also made available to client applications and service endpoint "
-"implementations. The defaultscope for a property is HANDLER."
+msgid "Properties are scoped as either APPLICATION or HANDLER. All properties are available to all handlers for an instance of an MEP on a 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 of an MEP instance. APPLICATION scoped properties are also made available to client applications and service endpoint implementations. The defaultscope for a property is HANDLER."
msgstr ""
#. Tag: title
@@ -1820,16 +1439,7 @@
#. Tag: para
#: Web_Services.xml:423
#, no-c-format
-msgid ""
-"<ulink url=\"#\">#Logical Handlers</ulink> are passed a message context of "
-"type LogicalMessageContext when invoked. LogicalMessageContext extends "
-"MessageContext with methods to obtain and modify the message payload, it "
-"does not provide access to the protocol specific aspects of amessage. 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 "<ulink url=\"#\">#Logical Handlers</ulink> are passed a message context of type LogicalMessageContext when invoked. LogicalMessageContext extends MessageContext with methods to obtain and modify the message payload, it does not provide access to the protocol specific aspects of amessage. 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
@@ -1841,17 +1451,14 @@
#. Tag: para
#: Web_Services.xml:430
#, no-c-format
-msgid ""
-"SOAP handlers are passed a SOAPMessageContext when invoked. "
-"SOAPMessageContext extends MessageContext with methods to obtain and modify "
-"the SOAP message payload."
+msgid "SOAP handlers are passed a SOAPMessageContext when invoked. SOAPMessageContext extends MessageContext with methods to obtain and modify the SOAP message payload."
msgstr ""
#. Tag: title
#: Web_Services.xml:438
#, no-c-format
msgid "Fault Handling"
-msgstr ""
+msgstr "错误处理"
#. Tag: para
#: Web_Services.xml:439
@@ -1866,8 +1473,7 @@
"public void throwSoapFaultException()\n"
"{\n"
"SOAPFactory factory = SOAPFactory.newInstance();\n"
-"SOAPFault fault = factory.createFault("this is a fault string!", "
-"new QName("http://foo", "FooCode"));\n"
+"SOAPFault fault = factory.createFault("this is a fault string!", new QName("http://foo", "FooCode"));\n"
"fault.setFaultActor("mr.actor");\n"
"fault.addDetail().addChildElement("test");\n"
"throw new SOAPFaultException(fault);\n"
@@ -1876,8 +1482,7 @@
"public void throwSoapFaultException()\n"
"{\n"
"SOAPFactory factory = SOAPFactory.newInstance();\n"
-"SOAPFault fault = factory.createFault("this is a fault string!", "
-"new QName("http://foo", "FooCode"));\n"
+"SOAPFault fault = factory.createFault("this is a fault string!", new QName("http://foo", "FooCode"));\n"
"fault.setFaultActor("mr.actor");\n"
"fault.addDetail().addChildElement("test");\n"
"throw new SOAPFaultException(fault);\n"
@@ -1885,9 +1490,9 @@
#. Tag: para
#: Web_Services.xml:443
-#, fuzzy, no-c-format
+#, no-c-format
msgid "or an application specific user exception"
-msgstr "EJB 应用程序配置"
+msgstr "应用程序专有的用户异常"
#. Tag: programlisting
#: Web_Services.xml:446
@@ -1895,26 +1500,29 @@
msgid ""
"public void throwApplicationException() throws UserException\n"
"{\n"
-"throw new UserException("validation", 123, "Some validation "
-"error");\n"
+"throw new UserException("validation", 123, "Some validation error");\n"
"}"
msgstr ""
#. Tag: title
-#: Web_Services.xml:449 Web_Services.xml:576 Web_Services.xml:609
-#: Web_Services.xml:781 Web_Services.xml:814 Web_Services.xml:956
-#: Web_Services.xml:1128 Web_Services.xml:1362 Web_Services.xml:1486
+#: Web_Services.xml:449
+#: Web_Services.xml:576
+#: Web_Services.xml:609
+#: Web_Services.xml:781
+#: Web_Services.xml:814
+#: Web_Services.xml:956
+#: Web_Services.xml:1128
+#: Web_Services.xml:1362
+#: Web_Services.xml:1486
#: Web_Services.xml:1501
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Note"
-msgstr "备注"
+msgstr "注意"
#. Tag: para
#: Web_Services.xml:450
#, 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
@@ -1927,7 +1535,7 @@
#: Web_Services.xml:462
#, no-c-format
msgid "Using JAXB with non annotated classes"
-msgstr ""
+msgstr "使用不带有注解类的 JAXB"
#. Tag: para
#: Web_Services.xml:463
@@ -1938,33 +1546,19 @@
#. Tag: para
#: Web_Services.xml:466
#, no-c-format
-msgid ""
-"JAXB is heavily driven by Java Annotations on the Java Bindings. It "
-"currently doesn't support an external binding configuration. This "
-"recently became an issue for us on JBossESB since the JBossWS 2.0.0 native "
-"SOAP stack uses JAXB to perform the SOAP to Java bindings (see 1, 2). It'"
-"s an issue for JBossESB simply because it needs to be able to support user "
-"definition of JBossWS native Webservice Endpoints (e.g. JSR 181) using Java "
-"typesets that have not been \"JAXB Annotated\" (see JAXB Introductions On "
-"JBossWS)."
+msgid "JAXB is heavily driven by Java Annotations on the Java Bindings. It currently doesn't support an external binding configuration. This recently became an issue for us on JBossESB since the JBossWS 2.0.0 native SOAP stack uses JAXB to perform the SOAP to Java bindings (see 1, 2). It's an issue for JBossESB simply because it needs to be able to support user definition of JBossWS native Webservice Endpoints (e.g. JSR 181) using Java typesets that have not been \"JAXB Annotated\" (see JAXB Introductions On JBossWS)."
msgstr ""
#. Tag: para
#: Web_Services.xml:469
#, 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
#: Web_Services.xml:472
#, 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: ulink
@@ -2000,11 +1594,7 @@
#. Tag: para
#: Web_Services.xml:500
#, 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: ulink
@@ -2023,7 +1613,7 @@
#: Web_Services.xml:516
#, no-c-format
msgid "Supported MTOM parameter types"
-msgstr ""
+msgstr "所支持的 MTOM 参数类型"
#. Tag: para
#: Web_Services.xml:523
@@ -2041,10 +1631,11 @@
#: Web_Services.xml:535
#, no-c-format
msgid "text/xml"
-msgstr ""
+msgstr "text/xml"
#. Tag: para
-#: Web_Services.xml:540 Web_Services.xml:552
+#: Web_Services.xml:540
+#: Web_Services.xml:552
#, no-c-format
msgid "javax.xml.transform.Source"
msgstr "javax.xml.transform.Source"
@@ -2059,31 +1650,24 @@
#: Web_Services.xml:559
#, no-c-format
msgid "application/octet-stream"
-msgstr ""
+msgstr "application/octet-stream"
#. Tag: para
#: Web_Services.xml:564
#, no-c-format
msgid "javax.activation.DataHandler"
-msgstr ""
+msgstr "javax.activation.DataHandler"
#. Tag: para
#: Web_Services.xml:571
#, 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
#: Web_Services.xml:577
#, 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
@@ -2095,10 +1679,7 @@
#. Tag: para
#: Web_Services.xml:586
#, 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: emphasis
@@ -2120,10 +1701,8 @@
" \n"
"@Remote\n"
"@WebService(targetNamespace = "http://org.jboss.ws/xop/doclit")\n"
-"@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = "
-"SOAPBinding.ParameterStyle.BARE)\n"
-"@BindingType(value="http://schemas.xmlsoap.org/wsdl/soap/http?"
-"mtom=true") (1)\n"
+"@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = SOAPBinding.ParameterStyle.BARE)\n"
+"@BindingType(value="http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true") (1)\n"
"public interface MTOMEndpoint {\n"
" \n"
"[...]\n"
@@ -2138,10 +1717,8 @@
" \n"
"@Remote\n"
"@WebService(targetNamespace = "http://org.jboss.ws/xop/doclit")\n"
-"@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = "
-"SOAPBinding.ParameterStyle.BARE)\n"
-"@BindingType(value="http://schemas.xmlsoap.org/wsdl/soap/http?"
-"mtom=true") (1)\n"
+"@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = SOAPBinding.ParameterStyle.BARE)\n"
+"@BindingType(value="http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true") (1)\n"
"public interface MTOMEndpoint {\n"
" \n"
"[...]\n"
@@ -2162,16 +1739,12 @@
#. Tag: para
#: Web_Services.xml:603
#, 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: programlisting
#: Web_Services.xml:606
#, no-c-format
-#, fuzzy
msgid ""
"[...]\n"
"Service service = Service.create(wsdlURL, serviceName);\n"
@@ -2185,16 +1758,14 @@
#. Tag: para
#: Web_Services.xml:610
#, 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 ""
#. Tag: title
#: Web_Services.xml:620
#, no-c-format
msgid "SwaRef"
-msgstr ""
+msgstr "SwaRef"
#. Tag: para
#: Web_Services.xml:621
@@ -2205,32 +1776,19 @@
#. Tag: para
#: Web_Services.xml:624
#, 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>."
+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 ""
#. Tag: title
#: Web_Services.xml:628
#, no-c-format
msgid "Using SwaRef with JAX-WS endpoints"
-msgstr ""
+msgstr "使用带有 JAX-WS 终端的 SwaRef"
#. Tag: para
#: Web_Services.xml:629
#, 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: programlisting
@@ -2300,10 +1858,7 @@
#. Tag: para
#: Web_Services.xml:633
#, 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: programlisting
@@ -2318,8 +1873,7 @@
" \n"
"@WebMethod\n"
"@XmlAttachmentRef\n"
-"DataHandler parameterAnnotation(@XmlAttachmentRef DataHandler data, String "
-"test);\n"
+"DataHandler parameterAnnotation(@XmlAttachmentRef DataHandler data, String test);\n"
" \n"
"}"
msgstr ""
@@ -2331,8 +1885,7 @@
" \n"
"@WebMethod\n"
"@XmlAttachmentRef\n"
-"DataHandler parameterAnnotation(@XmlAttachmentRef DataHandler data, String "
-"test);\n"
+"DataHandler parameterAnnotation(@XmlAttachmentRef DataHandler data, String test);\n"
" \n"
"}"
@@ -2346,24 +1899,20 @@
#: Web_Services.xml:640
#, no-c-format
msgid ""
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
"<env:Header/>\n"
"<env:Body>\n"
-"<ns2:parameterAnnotation xmlns:ns2='http://swaref.samples.jaxws.ws."
-"test.jboss.org/'>\n"
+"<ns2:parameterAnnotation xmlns:ns2='http://swaref.samples.jaxws.ws.test.jboss.org/'>\n"
"<arg0>cid:0-1180017772935-32455963 at ws.jboss.org</arg0>\n"
"<arg1>Wrapped test</arg1>\n"
"</ns2:parameterAnnotation>\n"
"</env:Body>\n"
"</env:Envelope>"
msgstr ""
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
"<env:Header/>\n"
"<env:Body>\n"
-"<ns2:parameterAnnotation xmlns:ns2='http://swaref.samples.jaxws.ws."
-"test.jboss.org/'>\n"
+"<ns2:parameterAnnotation xmlns:ns2='http://swaref.samples.jaxws.ws.test.jboss.org/'>\n"
"<arg0>cid:0-1180017772935-32455963 at ws.jboss.org</arg0>\n"
"<arg1>Wrapped test</arg1>\n"
"</ns2:parameterAnnotation>\n"
@@ -2374,15 +1923,12 @@
#: Web_Services.xml:644
#, no-c-format
msgid "Starting from WSDL"
-msgstr ""
+msgstr "从 WSDL 开始"
#. Tag: para
#: Web_Services.xml:645
#, 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: programlisting
@@ -2408,18 +1954,7 @@
#. Tag: para
#: Web_Services.xml:660
#, no-c-format
-#, fuzzy
-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
@@ -2431,7 +1966,6 @@
#. Tag: para
#: Web_Services.xml:668
#, no-c-format
-#, fuzzy
msgid "Exposing an already existing EJB3 bean as a Web Service"
msgstr "服务"
@@ -2450,26 +1984,19 @@
#. Tag: para
#: Web_Services.xml:683
#, no-c-format
-#, fuzzy
-msgid ""
-"Replacing the implementation of an existing Web Service, and you can't "
-"break compatibility with older clients"
+msgid "Replacing the implementation of an existing Web Service, and you can't break compatibility with older clients"
msgstr "服务'"
#. Tag: para
#: Web_Services.xml:688
#, 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
#: Web_Services.xml:693
#, 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
@@ -2482,7 +2009,7 @@
#: Web_Services.xml:708
#, no-c-format
msgid "Command"
-msgstr ""
+msgstr "命令"
#. Tag: emphasis
#: Web_Services.xml:713
@@ -2494,36 +2021,31 @@
#: Web_Services.xml:720
#, no-c-format
msgid "wsprovide"
-msgstr ""
+msgstr "wsprovide"
#. Tag: para
#: Web_Services.xml:724
#, 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: ulink
#: Web_Services.xml:732
#, no-c-format
msgid "wsconsume"
-msgstr ""
+msgstr "wsconsume"
#. Tag: para
#: Web_Services.xml:736
#, 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: ulink
#: Web_Services.xml:744
-#, fuzzy, no-c-format
+#, no-c-format
msgid "wsrunclient"
-msgstr "client"
+msgstr "wsrunclient"
#. Tag: para
#: Web_Services.xml:748
@@ -2540,13 +2062,7 @@
#. Tag: para
#: Web_Services.xml:757
#, 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."
+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 ""
#. Tag: para
@@ -2574,29 +2090,13 @@
#. Tag: para
#: Web_Services.xml:764
#, 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 unfortunately need to use a tool and "
-"add the generated classes to your deployment."
+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 unfortunately need to use a tool and add the generated classes to your deployment."
msgstr ""
#. Tag: para
#: Web_Services.xml:767
#, no-c-format
-msgid ""
-"This is the primary purpose of the <ulink url=\"http://jbws.dyndns.org/"
-"mediawiki/index.php?title=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://jbws.dyndns.org/mediawiki/index.php?"
-"title=Wsprovide\">wsprovide</ulink> using the \"-w\" option:"
+msgid "This is the primary purpose of the <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=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://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink> using the \"-w\" option:"
msgstr ""
#. Tag: programlisting
@@ -2626,7 +2126,8 @@
msgstr ""
#. Tag: programlisting
-#: Web_Services.xml:774 Web_Services.xml:938
+#: Web_Services.xml:774
+#: Web_Services.xml:938
#, no-c-format
msgid ""
"<service name='EchoService'>\n"
@@ -2662,18 +2163,13 @@
#. Tag: para
#: Web_Services.xml:782
#, 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."
+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 ""
#. Tag: para
#: Web_Services.xml:787
#, no-c-format
-msgid ""
-"Let's create a POJO endpoint for deployment on JBoss AS. A simple web."
-"xml needs to be created:"
+msgid "Let's create a POJO endpoint for deployment on JBoss AS. A simple web.xml needs to be created:"
msgstr ""
#. Tag: programlisting
@@ -2682,8 +2178,7 @@
msgid ""
"<web-app xmlns="http://java.sun.com/xml/ns/j2ee"\n"
"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-"xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/"
-"xml/ns/j2ee/web-app_2_4.xsd"\n"
+"xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"\n"
"version="2.4">\n"
" \n"
"<servlet>\n"
@@ -2699,8 +2194,7 @@
msgstr ""
"<web-app xmlns="http://java.sun.com/xml/ns/j2ee"\n"
"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-"xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/"
-"xml/ns/j2ee/web-app_2_4.xsd"\n"
+"xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"\n"
"version="2.4">\n"
" \n"
"<servlet>\n"
@@ -2750,31 +2244,24 @@
#: Web_Services.xml:795
#, no-c-format
msgid "The war can then be deployed:"
-msgstr ""
+msgstr "然后这个 WAR 文件可以被部署："
#. Tag: programlisting
#: Web_Services.xml:798
#, no-c-format
msgid "cp echo.war jboss-as/server/default/deploy"
-msgstr ""
+msgstr "cp echo.war jboss-as/server/default/deploy"
#. Tag: para
#: Web_Services.xml:799
#, no-c-format
-msgid ""
-"This will internally invoke <ulink url=\"http://jbws.dyndns.org/mediawiki/"
-"index.php?title=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>"
+msgid "This will internally invoke <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=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 ""
#. Tag: para
#: Web_Services.xml:802
#, 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 ""
#. Tag: title
@@ -2786,12 +2273,7 @@
#. Tag: para
#: Web_Services.xml:809
#, 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://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume"
-"\">wsconsume</ulink> tool is then used to consume this contract, and produce "
-"annotated Java classes (and optionally sources) that define it."
+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://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink> tool is then used to consume this contract, and produce annotated Java classes (and optionally sources) that define it."
msgstr ""
#. Tag: para
@@ -2803,12 +2285,7 @@
#. Tag: para
#: Web_Services.xml:820
#, 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://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume"
-"\">wsconsume</ulink> to preserve the Java source files that are generated, "
-"instead of providing just classes:"
+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://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink> to preserve the Java source files that are generated, instead of providing just classes:"
msgstr ""
#. Tag: programlisting
@@ -2834,31 +2311,31 @@
#: Web_Services.xml:824
#, no-c-format
msgid "The following table shows the purpose of each generated file:"
-msgstr ""
+msgstr "下面的表展示了每个生成的文件的目的："
#. Tag: emphasis
#: Web_Services.xml:834
#, no-c-format
msgid "File"
-msgstr ""
+msgstr "文件"
#. Tag: emphasis
#: Web_Services.xml:839
#, no-c-format
msgid "Purpose"
-msgstr ""
+msgstr "目的"
#. Tag: para
#: Web_Services.xml:845
#, no-c-format
msgid "Echo.java"
-msgstr ""
+msgstr "Echo.java"
#. Tag: para
#: Web_Services.xml:850
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Service Endpoint Interface"
-msgstr "服务"
+msgstr "服务终端接口"
#. Tag: para
#: Web_Services.xml:857
@@ -2923,41 +2400,31 @@
#. Tag: para
#: Web_Services.xml:917
#, no-c-format
-#, fuzzy
-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: programlisting
#: Web_Services.xml:920
#, no-c-format
msgid ""
-"@WebService(name = "Echo", targetNamespace = "http://echo/"
-"")\n"
+"@WebService(name = "Echo", targetNamespace = "http://echo/")\n"
"public interface Echo {\n"
"@WebMethod\n"
"@WebResult(targetNamespace = "")\n"
-"@RequestWrapper(localName = "echo", targetNamespace = "http://"
-"echo/", className = "echo.Echo_Type")\n"
-"@ResponseWrapper(localName = "echoResponse", targetNamespace = "
-""http://echo/", className = "echo.EchoResponse")\n"
+"@RequestWrapper(localName = "echo", targetNamespace = "http://echo/", className = "echo.Echo_Type")\n"
+"@ResponseWrapper(localName = "echoResponse", targetNamespace = "http://echo/", className = "echo.EchoResponse")\n"
"public String echo(\n"
"@WebParam(name = "arg0", targetNamespace = "")\n"
"String arg0);\n"
" \n"
"}"
msgstr ""
-"@WebService(name = "Echo", targetNamespace = "http://echo/"
-"")\n"
+"@WebService(name = "Echo", targetNamespace = "http://echo/")\n"
"public interface Echo {\n"
"@WebMethod\n"
"@WebResult(targetNamespace = "")\n"
-"@RequestWrapper(localName = "echo", targetNamespace = "http://"
-"echo/", className = "echo.Echo_Type")\n"
-"@ResponseWrapper(localName = "echoResponse", targetNamespace = "
-""http://echo/", className = "echo.EchoResponse")\n"
+"@RequestWrapper(localName = "echo", targetNamespace = "http://echo/", className = "echo.Echo_Type")\n"
+"@ResponseWrapper(localName = "echoResponse", targetNamespace = "http://echo/", className = "echo.EchoResponse")\n"
"public String echo(\n"
"@WebParam(name = "arg0", targetNamespace = "")\n"
"String arg0);\n"
@@ -2967,9 +2434,7 @@
#. Tag: para
#: Web_Services.xml:921
#, 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: programlisting
@@ -3007,44 +2472,20 @@
#. Tag: para
#: Web_Services.xml:929
#, no-c-format
-#, fuzzy
-msgid ""
-"Before going to 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 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 OS, 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."
+msgid "Before going to 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 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 OS, 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 developi!
ng 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
#: Web_Services.xml:932
#, 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://"
-"jbws.dyndns.org/mediawiki/index.php?title=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."
+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://jbws.dyndns.org/mediawiki/index.php?title=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 ""
#. Tag: para
#: Web_Services.xml:935
#, no-c-format
msgid "Offline version:"
-msgstr ""
+msgstr "脱机版本："
#. Tag: para
#: Web_Services.xml:939
@@ -3058,27 +2499,21 @@
msgid ""
"<service name="EchoService">\n"
"<port binding="tns:EchoBinding" name="EchoPort">\n"
-"<soap:address location="http://localhost.localdomain:8080/echo/"
-"Echo"/>\n"
+"<soap:address location="http://localhost.localdomain:8080/echo/Echo"/>\n"
"</port>\n"
"</service>"
msgstr ""
"<service name="EchoService">\n"
"<port binding="tns:EchoBinding" name="EchoPort">\n"
-"<soap:address location="http://localhost.localdomain:8080/echo/"
-"Echo"/>\n"
+"<soap:address location="http://localhost.localdomain:8080/echo/Echo"/>\n"
"</port>\n"
"</service>"
#. Tag: para
#: Web_Services.xml:943
#, no-c-format
-msgid ""
-"Using the online deployed version with <ulink url=\"http://jbws.dyndns.org/"
-"mediawiki/index.php?title=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://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink>:"
+msgstr "和在线部署的版本一起使用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink>："
#. Tag: programlisting
#: Web_Services.xml:946
@@ -3115,19 +2550,14 @@
#. Tag: para
#: Web_Services.xml:947
#, no-c-format
-msgid ""
-"The one class that was not examined in the top-down section, was EchoService."
-"java. Notice how it stores the location the WSDL was obtained from."
+msgid "The one class that was not examined in the top-down section, was EchoService.java. Notice how it stores the location the WSDL was obtained from."
msgstr ""
#. Tag: programlisting
#: Web_Services.xml:950
#, no-c-format
-#, fuzzy
msgid ""
-"@WebServiceClient(name = "EchoService", targetNamespace = ""
-"http://echo/", wsdlLocation = "http://localhost:8080/echo/Echo?"
-"wsdl")\n"
+"@WebServiceClient(name = "EchoService", targetNamespace = "http://echo/", wsdlLocation = "http://localhost:8080/echo/Echo?wsdl")\n"
"public class EchoService extends Service\n"
"{\n"
"private final static URL ECHOSERVICE_WSDL_LOCATION;\n"
@@ -3147,14 +2577,12 @@
"}\n"
" \n"
"public EchoService() {\n"
-"super(ECHOSERVICE_WSDL_LOCATION, new QName("http://echo/", ""
-"EchoService"));\n"
+"super(ECHOSERVICE_WSDL_LOCATION, new QName("http://echo/", "EchoService"));\n"
"}\n"
" \n"
"@WebEndpoint(name = "EchoPort")\n"
"public Echo getEchoPort() {\n"
-"return (Echo)super.getPort(new QName("http://echo/", ""
-"EchoPort"), Echo.class);\n"
+"return (Echo)super.getPort(new QName("http://echo/", "EchoPort"), Echo.class);\n"
"}\n"
"}"
msgstr ""
@@ -3167,25 +2595,13 @@
#. Tag: para
#: Web_Services.xml:951
#, no-c-format
-#, fuzzy
-msgid ""
-"As you can see, this generated class extends the main client entry point in "
-"JAX-WS, javax.xml.ws.Service. While you can use Service directly, this is "
-"far simpler since it provides the configuration info for you. The only "
-"method we really care about is the getEchoPort() method, which returns an "
-"instance of our Service Endpoint Interface. Any WS 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, javax.xml.ws.Service. While you can use Service directly, this is far simpler since it provides the configuration info for you. The only method we really care about is the getEchoPort() method, which returns an instance of our Service Endpoint Interface. Any WS operation can then be called by just invoking a method on the returned interface."
msgstr "服务 服务 服务."
#. Tag: para
#: Web_Services.xml:957
#, no-c-format
-#, fuzzy
-msgid ""
-"It's 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's 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
@@ -3237,10 +2653,7 @@
#. Tag: para
#: Web_Services.xml:966
#, no-c-format
-msgid ""
-"It can then be easily executed using the <ulink url=\"http://jbws.dyndns.org/"
-"mediawiki/index.php?title=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://jbws.dyndns.org/mediawiki/index.php?title=Wsrunclient\">wsrunclient</ulink> tool. This is just a convenience tool that invokes java with the needed classpath:"
msgstr ""
#. Tag: programlisting
@@ -3256,9 +2669,7 @@
#. Tag: para
#: Web_Services.xml:970
#, no-c-format
-msgid ""
-"It is easy to change the endpoint address of your operation at runtime, "
-"setting the ENDPOINT_ADDRESS_PROPERTY as shown below:"
+msgid "It is easy to change the endpoint address of your operation at runtime, setting the ENDPOINT_ADDRESS_PROPERTY as shown below:"
msgstr ""
#. Tag: programlisting
@@ -3272,8 +2683,7 @@
"/* Set NEW Endpoint Location */\n"
"String endpointURL = "http://NEW_ENDPOINT_URL";\n"
"BindingProvider bp = (BindingProvider)echo;\n"
-"bp.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "
-"endpointURL);\n"
+"bp.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpointURL);\n"
" \n"
"System.out.println("Server said: " + echo.echo(args[0]));\n"
"..."
@@ -3285,8 +2695,7 @@
"/* Set NEW Endpoint Location */\n"
"String endpointURL = "http://NEW_ENDPOINT_URL";\n"
"BindingProvider bp = (BindingProvider)echo;\n"
-"bp.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "
-"endpointURL);\n"
+"bp.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpointURL);\n"
" \n"
"System.out.println("Server said: " + echo.echo(args[0]));\n"
"..."
@@ -3306,7 +2715,6 @@
#. Tag: ulink
#: Web_Services.xml:986
#, no-c-format
-#, fuzzy
msgid "wsprovide reference page"
msgstr "服务架构"
@@ -3349,7 +2757,6 @@
#. Tag: title
#: Web_Services.xml:1024
#, no-c-format
-#, fuzzy
msgid "Web Service Extensions"
msgstr "代理服务"
@@ -3357,18 +2764,17 @@
#: Web_Services.xml:1026
#, no-c-format
msgid "WS-Addressing"
-msgstr ""
+msgstr "WS-Addressing"
#. Tag: para
#: Web_Services.xml:1027
#, 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 ""
+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
-#: Web_Services.xml:1031 Web_Services.xml:1107
+#: Web_Services.xml:1031
+#: Web_Services.xml:1107
#, no-c-format
msgid "<title>Specifications</title>"
msgstr "<title>Specifications</title>"
@@ -3376,24 +2782,20 @@
#. Tag: para
#: Web_Services.xml:1032
#, no-c-format
-msgid ""
-"WS-Addressing is defined by a combination of the following specifications "
-"from the W3C Candidate Recommendation 17 August 2005. The WS-Addressing API "
-"is standardized by <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 Candidate Recommendation 17 August 2005. The WS-Addressing API is standardized by <ulink url=\"http://www.jcp.org/en/jsr/detail?id=261\">JSR-261 - Java API for XML Web Services Addressing</ulink>"
msgstr ""
#. Tag: ulink
#: Web_Services.xml:1038
#, no-c-format
msgid "Web Services Addressing 1.0 - Core"
-msgstr ""
+msgstr "Web Services Addressing 1.0 - Core"
#. Tag: ulink
#: Web_Services.xml:1043
#, no-c-format
msgid "Web Services Addressing 1.0 - SOAP Binding"
-msgstr ""
+msgstr "Web Services Addressing 1.0 - SOAP Binding"
#. Tag: title
#: Web_Services.xml:1050
@@ -3404,24 +2806,19 @@
#. Tag: para
#: Web_Services.xml:1051
#, 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: programlisting
#: Web_Services.xml:1054
#, no-c-format
msgid ""
-"@WebService(name = "StatefulEndpoint", targetNamespace = ""
-"http://org.jboss.ws/samples/wsaddressing\n"
-" ", serviceName = ""
-"TestService")\n"
+"@WebService(name = "StatefulEndpoint", targetNamespace = "http://org.jboss.ws/samples/wsaddressing\n"
+" ", serviceName = "TestService")\n"
"@EndpointConfig(configName = "Standard WSAddressing Endpoint")\n"
"@HandlerChain(file = "WEB-INF/jaxws-handlers.xml")\n"
"@SOAPBinding(style = SOAPBinding.Style.RPC)\n"
-"public class StatefulEndpointImpl implements StatefulEndpoint, "
-"ServiceLifecycle\n"
+"public class StatefulEndpointImpl implements StatefulEndpoint, ServiceLifecycle\n"
"{\n"
"@WebMethod\n"
"public void addItem(String item)\n"
@@ -3436,15 +2833,12 @@
"{ ... }\n"
"}"
msgstr ""
-"@WebService(name = "StatefulEndpoint", targetNamespace = ""
-"http://org.jboss.ws/samples/wsaddressing\n"
-" ", serviceName = ""
-"TestService")\n"
+"@WebService(name = "StatefulEndpoint", targetNamespace = "http://org.jboss.ws/samples/wsaddressing\n"
+" ", serviceName = "TestService")\n"
"@EndpointConfig(configName = "Standard WSAddressing Endpoint")\n"
"@HandlerChain(file = "WEB-INF/jaxws-handlers.xml")\n"
"@SOAPBinding(style = SOAPBinding.Style.RPC)\n"
-"public class StatefulEndpointImpl implements StatefulEndpoint, "
-"ServiceLifecycle\n"
+"public class StatefulEndpointImpl implements StatefulEndpoint, ServiceLifecycle\n"
"{\n"
"@WebMethod\n"
"public void addItem(String item)\n"
@@ -3462,12 +2856,7 @@
#. Tag: para
#: Web_Services.xml:1055
#, no-c-format
-msgid ""
-"It uses the <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?"
-"title=JAX-WS_Endpoint_Configuration#_Standard_WSAddressing_Endpoint\">JAX-WS "
-"Endpoint Configuration# Standard WSAddressing Endpoint</ulink> to enable the "
-"server side addressing handler. It processes the incomming WS-Addressing "
-"header elements and provides access to them through the JSR-261 API."
+msgid "It uses the <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Endpoint_Configuration#_Standard_WSAddressing_Endpoint\">JAX-WS Endpoint Configuration# Standard WSAddressing Endpoint</ulink> to enable the server side addressing handler. It processes the incomming WS-Addressing header elements and provides access to them through the JSR-261 API."
msgstr ""
#. Tag: para
@@ -3481,34 +2870,28 @@
#, no-c-format
msgid ""
"<handler-chains xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/"
-"XMLSchema-instance"\n"
-"xsi:schemaLocation="http://java.sun.com/xml/ns/javaee "
-"javaee_web_services_1_2.xsd">\n"
+" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
+"xsi:schemaLocation="http://java.sun.com/xml/ns/javaee javaee_web_services_1_2.xsd">\n"
" \n"
"<handler-chain>\n"
"<protocol-bindings>##SOAP11_HTTP</protocol-bindings>\n"
"<handler>\n"
"<handler-name>Application Server Handler</handler-name>\n"
-"<handler-class>org.jboss.test.ws.jaxws.samples.wsaddressing."
-"ServerHandler</handler-class>\n"
+"<handler-class>org.jboss.test.ws.jaxws.samples.wsaddressing.ServerHandler</handler-class>\n"
"</handler>\n"
"</handler-chain>\n"
" \n"
"</handler-chains>"
msgstr ""
"<handler-chains xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/"
-"XMLSchema-instance"\n"
-"xsi:schemaLocation="http://java.sun.com/xml/ns/javaee "
-"javaee_web_services_1_2.xsd">\n"
+" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
+"xsi:schemaLocation="http://java.sun.com/xml/ns/javaee javaee_web_services_1_2.xsd">\n"
" \n"
"<handler-chain>\n"
"<protocol-bindings>##SOAP11_HTTP</protocol-bindings>\n"
"<handler>\n"
"<handler-name>Application Server Handler</handler-name>\n"
-"<handler-class>org.jboss.test.ws.jaxws.samples.wsaddressing."
-"ServerHandler</handler-class>\n"
+"<handler-class>org.jboss.test.ws.jaxws.samples.wsaddressing.ServerHandler</handler-class>\n"
"</handler>\n"
"</handler-chain>\n"
" \n"
@@ -3517,9 +2900,7 @@
#. Tag: para
#: Web_Services.xml:1062
#, no-c-format
-msgid ""
-"defines an application specific hander that assignes/processes stateful "
-"client ids."
+msgid "defines an application specific hander that assignes/processes stateful client ids."
msgstr ""
#. Tag: title
@@ -3531,10 +2912,7 @@
#. Tag: para
#: Web_Services.xml:1069
#, no-c-format
-msgid ""
-"On the client side there are simmilar handlers that does the reverse. It "
-"uses the JSR-261 API to add WS-Addressing header elements including the "
-"clientid association."
+msgid "On the client side there are simmilar handlers that does the reverse. It uses the JSR-261 API to add WS-Addressing header elements including the clientid association."
msgstr ""
#. Tag: para
@@ -3546,7 +2924,6 @@
#. Tag: programlisting
#: Web_Services.xml:1075
#, no-c-format
-#, fuzzy
msgid ""
"Service service = Service.create(wsdlURL, serviceName);\n"
"port1 = (StatefulEndpoint)service.getPort(StatefulEndpoint.class);\n"
@@ -3563,9 +2940,7 @@
#. Tag: para
#: Web_Services.xml:1076
#, no-c-format
-msgid ""
-"The WSAddressingClientHandler is provided by JBossWS and reads/writes the "
-"addressing properties and puts then into the message context."
+msgid "The WSAddressingClientHandler is provided by JBossWS and reads/writes the addressing properties and puts then into the message context."
msgstr ""
#. Tag: emphasis
@@ -3621,7 +2996,8 @@
"}"
#. Tag: emphasis
-#: Web_Services.xml:1084 Web_Services.xml:1459
+#: Web_Services.xml:1084
+#: Web_Services.xml:1459
#, no-c-format
msgid "SOAP message exchange"
msgstr ""
@@ -3636,149 +3012,109 @@
#: Web_Services.xml:1089
#, no-c-format
msgid ""
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
-"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/"
-"addressing'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
+"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/addressing'>\n"
"<wsa:To>uri:jbossws-samples-wsaddr/TestService</wsa:To>\n"
-"<wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:"
-"Action>\n"
+"<wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:Action>\n"
"<wsa:ReferenceParameters>\n"
-"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:"
-"clientid>\n"
+"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:clientid>\n"
"</wsa:ReferenceParameters>\n"
"</env:Header>\n"
"<env:Body>\n"
-"<ns1:addItem xmlns:ns1='http://org.jboss.ws/samples/wsaddr'"
-">\n"
+"<ns1:addItem xmlns:ns1='http://org.jboss.ws/samples/wsaddr'>\n"
"<String_1>Ice Cream</String_1>\n"
"</ns1:addItem>\n"
"</env:Body>\n"
"</env:Envelope>\n"
" \n"
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
-"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/"
-"addressing'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
+"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/addressing'>\n"
"<wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>\n"
-"<wsa:Action>http://org.jboss.ws/addressing/stateful/actionReply</"
-"wsa:Action>\n"
-"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:"
-"clientid>\n"
+"<wsa:Action>http://org.jboss.ws/addressing/stateful/actionReply</wsa:Action>\n"
+"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:clientid>\n"
"</env:Header>\n"
"<env:Body>\n"
-"<ns1:addItemResponse xmlns:ns1='http://org.jboss.ws/samples/"
-"wsaddr'/>\n"
+"<ns1:addItemResponse xmlns:ns1='http://org.jboss.ws/samples/wsaddr'/>\n"
"</env:Body>\n"
"</env:Envelope>\n"
" \n"
"...\n"
" \n"
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
-"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/"
-"addressing'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
+"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/addressing'>\n"
"<wsa:To>uri:jbossws-samples-wsaddr/TestService</wsa:To>\n"
-"<wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:"
-"Action>\n"
+"<wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:Action>\n"
"<wsa:ReferenceParameters>\n"
-"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:"
-"clientid>\n"
+"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:clientid>\n"
"</wsa:ReferenceParameters>\n"
"</env:Header>\n"
"<env:Body>\n"
-"<ns1:getItems xmlns:ns1='http://org.jboss.ws/samples/wsaddr'/"
-">\n"
+"<ns1:getItems xmlns:ns1='http://org.jboss.ws/samples/wsaddr'/>\n"
"</env:Body>\n"
"</env:Envelope>\n"
" \n"
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
-"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/"
-"addressing'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
+"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/addressing'>\n"
"<wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>\n"
-"<wsa:Action>http://org.jboss.ws/addressing/stateful/actionReply</"
-"wsa:Action>\n"
-"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:"
-"clientid>\n"
+"<wsa:Action>http://org.jboss.ws/addressing/stateful/actionReply</wsa:Action>\n"
+"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:clientid>\n"
"</env:Header>\n"
"<env:Body>\n"
-"<ns1:getItemsResponse xmlns:ns1='http://org.jboss.ws/samples/"
-"wsaddr'>\n"
+"<ns1:getItemsResponse xmlns:ns1='http://org.jboss.ws/samples/wsaddr'>\n"
"<result>[Ice Cream, Ferrari]</result>\n"
"</ns1:getItemsResponse>\n"
"</env:Body>\n"
"</env:Envelope>"
msgstr ""
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
-"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/"
-"addressing'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
+"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/addressing'>\n"
"<wsa:To>uri:jbossws-samples-wsaddr/TestService</wsa:To>\n"
-"<wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:"
-"Action>\n"
+"<wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:Action>\n"
"<wsa:ReferenceParameters>\n"
-"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:"
-"clientid>\n"
+"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:clientid>\n"
"</wsa:ReferenceParameters>\n"
"</env:Header>\n"
"<env:Body>\n"
-"<ns1:addItem xmlns:ns1='http://org.jboss.ws/samples/wsaddr'"
-">\n"
+"<ns1:addItem xmlns:ns1='http://org.jboss.ws/samples/wsaddr'>\n"
"<String_1>Ice Cream</String_1>\n"
"</ns1:addItem>\n"
"</env:Body>\n"
"</env:Envelope>\n"
" \n"
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
-"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/"
-"addressing'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
+"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/addressing'>\n"
"<wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>\n"
-"<wsa:Action>http://org.jboss.ws/addressing/stateful/actionReply</"
-"wsa:Action>\n"
-"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:"
-"clientid>\n"
+"<wsa:Action>http://org.jboss.ws/addressing/stateful/actionReply</wsa:Action>\n"
+"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:clientid>\n"
"</env:Header>\n"
"<env:Body>\n"
-"<ns1:addItemResponse xmlns:ns1='http://org.jboss.ws/samples/"
-"wsaddr'/>\n"
+"<ns1:addItemResponse xmlns:ns1='http://org.jboss.ws/samples/wsaddr'/>\n"
"</env:Body>\n"
"</env:Envelope>\n"
" \n"
"...\n"
" \n"
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
-"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/"
-"addressing'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
+"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/addressing'>\n"
"<wsa:To>uri:jbossws-samples-wsaddr/TestService</wsa:To>\n"
-"<wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:"
-"Action>\n"
+"<wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:Action>\n"
"<wsa:ReferenceParameters>\n"
-"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:"
-"clientid>\n"
+"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:clientid>\n"
"</wsa:ReferenceParameters>\n"
"</env:Header>\n"
"<env:Body>\n"
-"<ns1:getItems xmlns:ns1='http://org.jboss.ws/samples/wsaddr'/"
-">\n"
+"<ns1:getItems xmlns:ns1='http://org.jboss.ws/samples/wsaddr'/>\n"
"</env:Body>\n"
"</env:Envelope>\n"
" \n"
-"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/"
-"'>\n"
-"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/"
-"addressing'>\n"
+"<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>\n"
+"<env:Header xmlns:wsa='http://schemas.xmlsoap.org/ws/2004/08/addressing'>\n"
"<wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>\n"
-"<wsa:Action>http://org.jboss.ws/addressing/stateful/actionReply</"
-"wsa:Action>\n"
-"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:"
-"clientid>\n"
+"<wsa:Action>http://org.jboss.ws/addressing/stateful/actionReply</wsa:Action>\n"
+"<ns1:clientid xmlns:ns1='http://somens'>clientid-1</ns1:clientid>\n"
"</env:Header>\n"
"<env:Body>\n"
-"<ns1:getItemsResponse xmlns:ns1='http://org.jboss.ws/samples/"
-"wsaddr'>\n"
+"<ns1:getItemsResponse xmlns:ns1='http://org.jboss.ws/samples/wsaddr'>\n"
"<result>[Ice Cream, Ferrari]</result>\n"
"</ns1:getItemsResponse>\n"
"</env:Body>\n"
@@ -3793,14 +3129,8 @@
#. Tag: para
#: Web_Services.xml:1096
#, no-c-format
-msgid ""
-"WS-BPEL is not supported with JAX-WS, please refer to <ulink url=\"http://"
-"jbws.dyndns.org/mediawiki/index.php?title=JAX-RPC_User_Guide#WS-BPEL\">JAX-"
-"RPC User Guide#WS-BPEL</ulink>."
-msgstr ""
-"JAX-WS 不支持 WS-BPEL，相关信息请参考 <ulink url=\"http://"
-"jbws.dyndns.org/mediawiki/index.php?title=JAX-RPC_User_Guide#WS-BPEL\">JAX-"
-"RPC User Guide#WS-BPEL</ulink>。"
+msgid "WS-BPEL is not supported with JAX-WS, please refer to <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-RPC_User_Guide#WS-BPEL\">JAX-RPC User Guide#WS-BPEL</ulink>."
+msgstr "JAX-WS 不支持 WS-BPEL，相关信息请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-RPC_User_Guide#WS-BPEL\">JAX-RPC User Guide#WS-BPEL</ulink>。"
#. Tag: title
#: Web_Services.xml:1102
@@ -3811,10 +3141,7 @@
#. Tag: para
#: Web_Services.xml:1103
#, no-c-format
-msgid ""
-"WS-Eventing specifies a set of operations that allow an event consumer to "
-"register (subscribe) with an event producer (source) to receive events "
-"(notifications) in an asynchronous fashion."
+msgid "WS-Eventing specifies a set of operations that allow an event consumer to register (subscribe) with an event producer (source) to receive events (notifications) in an asynchronous fashion."
msgstr "WS-Eventing 指定了一系列操作，允许事件消费者向事件生产者（源）注册（订阅）来以异步的方式接收事件（通知）。"
#. Tag: para
@@ -3838,18 +3165,13 @@
#. Tag: para
#: Web_Services.xml:1123
#, no-c-format
-msgid ""
-"The following section will introduce the main eventing actors and their "
-"responsiblities."
+msgid "The following section will introduce the main eventing actors and their responsiblities."
msgstr "下面将介绍主要的事件参与者及其相关责任。"
#. Tag: para
#: Web_Services.xml:1129
#, no-c-format
-msgid ""
-"The original eventing specification builds upon WS-Addressing 2004/08. "
-"JBossWS however decided to stick to the latest version, which is the W3C "
-"candidate release."
+msgid "The original eventing specification builds upon WS-Addressing 2004/08. JBossWS however decided to stick to the latest version, which is the W3C candidate release."
msgstr "原来的 Eventing 规格构建于 WS-Addressing 2004/08 之上。然而，JBossWS 决定遵循最新的版本，也就是 W3C 的候选版本。"
#. Tag: title
@@ -3861,78 +3183,49 @@
#. Tag: para
#: Web_Services.xml:1141
#, no-c-format
-msgid ""
-"An event sink (web service client) sends a subscribtion request to the event "
-"source endpoint. This includes the event sink endpoint address where "
-"notifications should delivered. Upon successful subscription the sink "
-"receives a leased subscription ID that can be used to identify the client in "
-"subsequent requests."
+msgid "An event sink (web service client) sends a subscribtion request to the event source endpoint. This includes the event sink endpoint address where notifications should delivered. Upon successful subscription the sink receives a leased subscription ID that can be used to identify the client in subsequent requests."
msgstr "Event Sink（Web service 客户）发送一个订阅请求给事件源终端。这包括应该递送到的 event sink 终端的地址。在成功订阅后，Event Sink 会接收到一个已租用的订阅 ID，它可用来在随后的请求里识别客户。"
#. Tag: para
#: Web_Services.xml:1146
#, no-c-format
-msgid ""
-"A successfully registered event sink directs management requests (Renew, "
-"GetStatus, Unsubscribe) to the subscription manager endpoint using the "
-"previously received subscription ID. The subscription manager endpoint "
-"address was returned as part of the subscription response in the first place."
+msgid "A successfully registered event sink directs management requests (Renew, GetStatus, Unsubscribe) to the subscription manager endpoint using the previously received subscription ID. The subscription manager endpoint address was returned as part of the subscription response in the first place."
msgstr "在成功注册后，Event sink 用之前接收到的订阅 ID 把管理性请求（Renew、GetStatus、Unsubscribe）转发给订阅管理者终端。然后，订阅管理者终端地址作为订阅响应的一部分被返回。"
#. Tag: para
#: Web_Services.xml:1151
#, no-c-format
-msgid ""
-"The actual event sink (application) emits notification messages through the "
-"JBossWS-Eventing module. JBossWS-Eventing dispatches the notification to any "
-"subscriber endpoint that is registered with a particular event source.s"
+msgid "The actual event sink (application) emits notification messages through the JBossWS-Eventing module. JBossWS-Eventing dispatches the notification to any subscriber endpoint that is registered with a particular event source.s"
msgstr "实际的 event sink（应用程序）通过 JBossWS-Eventing 模块发送通知消息。JBossWS-Eventing 把通知分发给注册到特定数据源的任何订阅者终端。"
#. Tag: para
#: Web_Services.xml:1156
#, no-c-format
-msgid ""
-"Besides notifications JBossWS-Eventing may emit lifecycle events at any "
-"time, i.e. to inform an event sink that a subscription was canceled. This "
-"can be the case when the subscription expired or the event source was "
-"undeployed."
+msgid "Besides notifications JBossWS-Eventing may emit lifecycle events at any time, i.e. to inform an event sink that a subscription was canceled. This can be the case when the subscription expired or the event source was undeployed."
msgstr "除此之外，JBossWS-Eventing 在任何时间都可能发送生命周期事件，例如，通知 event sink 某个订阅已经取消了。当订阅过期或者事件源被卸载时，就会出现这样的情况。"
#. Tag: para
#: Web_Services.xml:1162
#, no-c-format
-msgid ""
-"It is the users responsibilty to supply the web service endpoints "
-"(EventSourceEndpoint, SubscriptionManagerEndpoint) that are required for a "
-"complete event source deployment. Fortunatly JBossWS-Eventing already ships "
-"with a implementation that can be used right away. All that's left todo "
-"is packaging of standard JSR-109 deployment archive that includes the event "
-"source specific WSDL and points to the JBossWS-Eventing endpoint "
-"implementations."
+msgid "It is the users responsibilty to supply the web service endpoints (EventSourceEndpoint, SubscriptionManagerEndpoint) that are required for a complete event source deployment. Fortunatly JBossWS-Eventing already ships with a implementation that can be used right away. All that's left todo is packaging of standard JSR-109 deployment archive that includes the event source specific WSDL and points to the JBossWS-Eventing endpoint implementations."
msgstr "用户的责任是提供完整的事件源部署所要求的 web service 终端（EventSourceEndpoint、SubscriptionManagerEndpoint）。幸运的是，JBossWS-Eventing 已经附带了一个可立马使用的实现。剩下的事情是将包括事件源专有的 WSDL 的标准 JSR-109 部署文档打包并使其指向 JBossWS-Eventing 终端实现。"
#. Tag: para
#: Web_Services.xml:1165
#, no-c-format
-#, fuzzy
msgid "The relevant steps are:"
msgstr "子元素是："
#. Tag: para
#: Web_Services.xml:1170
#, no-c-format
-msgid ""
-"Create a custom WSDL that describes your event source, in respect to the "
-"notification schema (1) and the fact that is actually contains an event "
-"source port (2)"
+msgid "Create a custom WSDL that describes your event source, in respect to the notification schema (1) and the fact that is actually contains an event source port (2)"
msgstr "创建自定义的描述事件源的 WSDL，按照通知模式 (1) 以及实际包含事件源端口的事实 (2)"
#. Tag: para
#: Web_Services.xml:1175
#, no-c-format
-msgid ""
-"Use the JBossWS SEI (3) and endpoint (4) implementations (webservices.xml, "
-"web.xml)."
+msgid "Use the JBossWS SEI (3) and endpoint (4) implementations (webservices.xml, web.xml)."
msgstr "使用 JBossWS SEI (3) 和终端 (4) 实现（webservices.xml、web.xml）。"
#. Tag: title
@@ -3944,18 +3237,8 @@
#. Tag: para
#: Web_Services.xml:1184
#, no-c-format
-msgid ""
-"With JAX-WS the event source setup has actually become quiet easy. All you "
-"need to do is to subclass your endpoint implementation from "
-"<literal>AbstractEventSourceEndpoint</literal> and a subscription manager "
-"from <literal>AbstractSubscriptionManagerEndpoint</literal> and finally "
-"point that implementation to a <ulink url=\"http://jbws.dyndns.org/mediawiki/"
-"index.php?title=JAX-WS_User_Guide#The_WSDL_that_describes_an_event_source"
-"\">event source specific WSDL</ulink>."
-msgstr ""
-"使用 JAX-WS，事件源的设立就变得很容易了。你所要做的只是创建 <literal>AbstractEventSourceEndpoint</literal> 的终端实现以及订阅管理者 <literal>AbstractSubscriptionManagerEndpoint</literal> 的子类并使这个实现指向 <ulink url=\"http://jbws.dyndns.org/mediawiki/"
-"index.php?title=JAX-WS_User_Guide#The_WSDL_that_describes_an_event_source"
-"\">事件源专有的 WSDL</ulink>。"
+msgid "With JAX-WS the event source setup has actually become quiet easy. All you need to do is to subclass your endpoint implementation from <literal>AbstractEventSourceEndpoint</literal> and a subscription manager from <literal>AbstractSubscriptionManagerEndpoint</literal> and finally point that implementation to a <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#The_WSDL_that_describes_an_event_source\">event source specific WSDL</ulink>."
+msgstr "使用 JAX-WS，事件源的设立就变得很容易了。你所要做的只是创建 <literal>AbstractEventSourceEndpoint</literal> 的终端实现以及订阅管理者 <literal>AbstractSubscriptionManagerEndpoint</literal> 的子类并使这个实现指向 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#The_WSDL_that_describes_an_event_source\">事件源专有的 WSDL</ulink>。"
#. Tag: programlisting
#: Web_Services.xml:1187
@@ -3974,23 +3257,16 @@
"* @version $Id: Web_Services.xml,v 1.2 2007/11/22 13:30:13 vrenish Exp $\n"
"* @since 18.01.2007\n"
"*/\n"
-"@WebService"
-"( (1)\n"
+"@WebService( (1)\n"
"name = "EventSource",\n"
"portName = "EventSourcePort",\n"
-"targetNamespace = "http://schemas.xmlsoap.org/ws/2004/08/"
-"eventing",\n"
-"wsdlLocation = "/WEB-INF/wsdl/sysmon."
-"wsdl", (2)\n"
-"endpointInterface = "org.jboss.ws.extensions.eventing.jaxws."
-"EventSourceEndpoint")\n"
-"@EndpointConfig(configName = "Standard WSAddressing "
-"Endpoint") (3)\n"
-"public class SysmonRegistrationEndpoint extends AbstractEventSourceEndpoint "
-"{ (4)\n"
+"targetNamespace = "http://schemas.xmlsoap.org/ws/2004/08/eventing",\n"
+"wsdlLocation = "/WEB-INF/wsdl/sysmon.wsdl", (2)\n"
+"endpointInterface = "org.jboss.ws.extensions.eventing.jaxws.EventSourceEndpoint")\n"
+"@EndpointConfig(configName = "Standard WSAddressing Endpoint") (3)\n"
+"public class SysmonRegistrationEndpoint extends AbstractEventSourceEndpoint { (4)\n"
" \n"
-"private static final Logger log = Logger.getLogger"
-"(SysmonRegistrationEndpoint.class);\n"
+"private static final Logger log = Logger.getLogger(SysmonRegistrationEndpoint.class);\n"
" \n"
"protected Logger getLogger()\n"
"{\n"
@@ -4011,23 +3287,16 @@
"* @version $Id: Web_Services.xml,v 1.2 2007/11/22 13:30:13 vrenish Exp $\n"
"* @since 18.01.2007\n"
"*/\n"
-"@WebService"
-"( (1)\n"
+"@WebService( (1)\n"
"name = "EventSource",\n"
"portName = "EventSourcePort",\n"
-"targetNamespace = "http://schemas.xmlsoap.org/ws/2004/08/"
-"eventing",\n"
-"wsdlLocation = "/WEB-INF/wsdl/sysmon."
-"wsdl", (2)\n"
-"endpointInterface = "org.jboss.ws.extensions.eventing.jaxws."
-"EventSourceEndpoint")\n"
-"@EndpointConfig(configName = "Standard WSAddressing "
-"Endpoint") (3)\n"
-"public class SysmonRegistrationEndpoint extends AbstractEventSourceEndpoint "
-"{ (4)\n"
+"targetNamespace = "http://schemas.xmlsoap.org/ws/2004/08/eventing",\n"
+"wsdlLocation = "/WEB-INF/wsdl/sysmon.wsdl", (2)\n"
+"endpointInterface = "org.jboss.ws.extensions.eventing.jaxws.EventSourceEndpoint")\n"
+"@EndpointConfig(configName = "Standard WSAddressing Endpoint") (3)\n"
+"public class SysmonRegistrationEndpoint extends AbstractEventSourceEndpoint { (4)\n"
" \n"
-"private static final Logger log = Logger.getLogger"
-"(SysmonRegistrationEndpoint.class);\n"
+"private static final Logger log = Logger.getLogger(SysmonRegistrationEndpoint.class);\n"
" \n"
"protected Logger getLogger()\n"
"{\n"
@@ -4056,9 +3325,7 @@
#. Tag: para
#: Web_Services.xml:1205
#, no-c-format
-msgid ""
-"Subclass a predefined implementation that knows how to delegate to the "
-"actual eventing service implementation"
+msgid "Subclass a predefined implementation that knows how to delegate to the actual eventing service implementation"
msgstr ""
#. Tag: title
@@ -4070,17 +3337,13 @@
#. Tag: para
#: Web_Services.xml:1214
#, no-c-format
-msgid ""
-"Even though we are already using the annotation driven approach, JBossWS "
-"eventing still requires an event source specific WSDL."
+msgid "Even though we are already using the annotation driven approach, JBossWS eventing still requires an event source specific WSDL."
msgstr "即使我们已经使用注解驱动的方式，JBossWS 事件仍然需要事件源专有的 WSDL。"
#. Tag: para
#: Web_Services.xml:1217
#, no-c-format
-msgid ""
-"The following excerpt shows the relevant WSDL details that describe an event "
-"source."
+msgid "The following excerpt shows the relevant WSDL details that describe an event source."
msgstr "下面的摘要显示了描述事件源的相关 WSDL 细节。"
#. Tag: programlisting
@@ -4099,14 +3362,12 @@
"xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">\n"
" \n"
"<wsdl:import\n"
-"(1) namespace='http://schemas.xmlsoap.org/ws/2004/08/"
-"eventing'\n"
+"(1) namespace='http://schemas.xmlsoap.org/ws/2004/08/eventing'\n"
"location='jbwse.wsdl' />\n"
" \n"
"<wsdl:types>\n"
" \n"
-"<xs:schema targetNamespace='http://schemas.xmlsoap.org/ws/2004/08/"
-"eventing'>\n"
+"<xs:schema targetNamespace='http://schemas.xmlsoap.org/ws/2004/08/eventing'>\n"
"(2) <xs:include schemaLocation='jbwse.xsd'/>\n"
"</xs:schema>\n"
" \n"
@@ -4120,8 +3381,7 @@
"<xs:element name="Time " type="xs:dateTime"/>\n"
"<xs:element name="HostName" type="xs:string"/>\n"
"<xs:element name="HostAddress" type="xs:string"/>\n"
-"<xs:element name="ActiveThreadCount" type="xs:int"/"
-">\n"
+"<xs:element name="ActiveThreadCount" type="xs:int"/>\n"
"<xs:element name="FreeMemory" type="xs:string"/>\n"
"<xs:element name="MaxMemory" type="xs:string"/>\n"
"</xs:sequence>\n"
@@ -4132,21 +3392,17 @@
"</wsdl:types>\n"
" \n"
"<wsdl:message name='SystemInfoMsg'>\n"
-"<wsdl:part name='body' element='tns:SystemStatus'/"
-">\n"
+"<wsdl:part name='body' element='tns:SystemStatus'/>\n"
"</wsdl:message>\n"
" \n"
-"(4) <wsdl:portType name='SystemInfo' wse:EventSource='"
-"true'>\n"
+"(4) <wsdl:portType name='SystemInfo' wse:EventSource='true'>\n"
"<wsdl:operation name='SysmonOp'>\n"
"<wsdl:output message='tns:SystemInfoMsg'/>\n"
"</wsdl:operation>\n"
"</wsdl:portType>\n"
" \n"
-"<wsdl:binding name="SystemInfoBinding" type="tns:"
-"SystemInfo">\n"
-"<soap:binding style="document" transport="http://schemas."
-"xmlsoap.org/soap/http"/>\n"
+"<wsdl:binding name="SystemInfoBinding" type="tns:SystemInfo">\n"
+"<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>\n"
"<wsdl:operation name="SysmonOp">\n"
"<soap:operation soapAction=""/>\n"
"<wsdl:output>\n"
@@ -4169,14 +3425,12 @@
"xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">\n"
" \n"
"<wsdl:import\n"
-"(1) namespace='http://schemas.xmlsoap.org/ws/2004/08/"
-"eventing'\n"
+"(1) namespace='http://schemas.xmlsoap.org/ws/2004/08/eventing'\n"
"location='jbwse.wsdl' />\n"
" \n"
"<wsdl:types>\n"
" \n"
-"<xs:schema targetNamespace='http://schemas.xmlsoap.org/ws/2004/08/"
-"eventing'>\n"
+"<xs:schema targetNamespace='http://schemas.xmlsoap.org/ws/2004/08/eventing'>\n"
"(2) <xs:include schemaLocation='jbwse.xsd'/>\n"
"</xs:schema>\n"
" \n"
@@ -4190,8 +3444,7 @@
"<xs:element name="Time " type="xs:dateTime"/>\n"
"<xs:element name="HostName" type="xs:string"/>\n"
"<xs:element name="HostAddress" type="xs:string"/>\n"
-"<xs:element name="ActiveThreadCount" type="xs:int"/"
-">\n"
+"<xs:element name="ActiveThreadCount" type="xs:int"/>\n"
"<xs:element name="FreeMemory" type="xs:string"/>\n"
"<xs:element name="MaxMemory" type="xs:string"/>\n"
"</xs:sequence>\n"
@@ -4202,21 +3455,17 @@
"</wsdl:types>\n"
" \n"
"<wsdl:message name='SystemInfoMsg'>\n"
-"<wsdl:part name='body' element='tns:SystemStatus'/"
-">\n"
+"<wsdl:part name='body' element='tns:SystemStatus'/>\n"
"</wsdl:message>\n"
" \n"
-"(4) <wsdl:portType name='SystemInfo' wse:EventSource='"
-"true'>\n"
+"(4) <wsdl:portType name='SystemInfo' wse:EventSource='true'>\n"
"<wsdl:operation name='SysmonOp'>\n"
"<wsdl:output message='tns:SystemInfoMsg'/>\n"
"</wsdl:operation>\n"
"</wsdl:portType>\n"
" \n"
-"<wsdl:binding name="SystemInfoBinding" type="tns:"
-"SystemInfo">\n"
-"<soap:binding style="document" transport="http://schemas."
-"xmlsoap.org/soap/http"/>\n"
+"<wsdl:binding name="SystemInfoBinding" type="tns:SystemInfo">\n"
+"<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>\n"
"<wsdl:operation name="SysmonOp">\n"
"<soap:operation soapAction=""/>\n"
"<wsdl:output>\n"
@@ -4230,9 +3479,7 @@
#. Tag: para
#: Web_Services.xml:1223
#, no-c-format
-msgid ""
-"Import the default eventing WSDL, that includes service and port "
-"declarations."
+msgid "Import the default eventing WSDL, that includes service and port declarations."
msgstr "导入包括服务和端口声明的缺省事件 WSDL。"
#. Tag: para
@@ -4250,9 +3497,7 @@
#. Tag: para
#: Web_Services.xml:1238
#, no-c-format
-msgid ""
-"Declare a port type, attributed \"wse:EventSource='true'\" that "
-"points to your notification message schema."
+msgid "Declare a port type, attributed \"wse:EventSource='true'\" that points to your notification message schema."
msgstr "声明端口类型，其属性为 \"wse:EventSource='true'\"，指向通知消息模式。"
#. Tag: title
@@ -4264,9 +3509,7 @@
#. Tag: para
#: Web_Services.xml:1247
#, no-c-format
-msgid ""
-"JBossWS-Eventing registeres a event dispatcher within local JNDI tree that "
-"can be used to emit notifications from applications."
+msgid "JBossWS-Eventing registeres a event dispatcher within local JNDI tree that can be used to emit notifications from applications."
msgstr ""
#. Tag: programlisting
@@ -4305,8 +3548,7 @@
#: Web_Services.xml:1258
#, no-c-format
msgid ""
-"(1) URI eventSourceURI = new URI("http://http://www.jboss.org/sysmon/"
-"SystemInfo");\n"
+"(1) URI eventSourceURI = new URI("http://http://www.jboss.org/sysmon/SystemInfo");\n"
"(2) Element payload = DOMUtils.parse("SOME XML STRING");\n"
"try\n"
"{\n"
@@ -4320,8 +3562,7 @@
"//\n"
"}"
msgstr ""
-"(1) URI eventSourceURI = new URI("http://http://www.jboss.org/sysmon/"
-"SystemInfo");\n"
+"(1) URI eventSourceURI = new URI("http://http://www.jboss.org/sysmon/SystemInfo");\n"
"(2) Element payload = DOMUtils.parse("SOME XML STRING");\n"
"try\n"
"{\n"
@@ -4362,9 +3603,7 @@
#. Tag: para
#: Web_Services.xml:1281
#, no-c-format
-msgid ""
-"The SubscriptionManager MBean is the actual core component that drives the "
-"JBossWS-Eventing implementation. It can be accessed through the jmx-console."
+msgid "The SubscriptionManager MBean is the actual core component that drives the JBossWS-Eventing implementation. It can be accessed through the jmx-console."
msgstr "SubscriptionManager MBean 是驱动 JBossWS-Eventing 实现的实际核心组件。它可以通过 jmx-console 进行访问。"
#. Tag: programlisting
@@ -4376,11 +3615,7 @@
#. Tag: para
#: Web_Services.xml:1285
#, no-c-format
-msgid ""
-"Management operations exist to monitor and maintain active subscritions and "
-"deployed event sources. The current implementation is backed by a "
-"ThreadPoolExecutor, that asynchronously delivers messages to event sink "
-"endpoints. It can be configured through the following attributes:"
+msgid "Management operations exist to monitor and maintain active subscritions and deployed event sources. The current implementation is backed by a ThreadPoolExecutor, that asynchronously delivers messages to event sink endpoints. It can be configured through the following attributes:"
msgstr "管理性操作监控和维护活动的订阅和部署的事件源。当前的实现是 ThreadPoolExecutor，它异步地把消息递送到 EventSink 终端。它可配置下列的属性："
#. Tag: para
@@ -4410,21 +3645,13 @@
#. Tag: para
#: Web_Services.xml:1311
#, 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)."
+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
#: Web_Services.xml:1314
#, 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: emphasis
@@ -4484,27 +3711,13 @@
#. Tag: para
#: Web_Services.xml:1357
#, 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://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_Endpoint_Configuration\">JAX-WS Endpoint Configuration</ulink> or <ulink "
-"url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_Client_Configuration\">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://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Endpoint_Configuration\">JAX-WS Endpoint Configuration</ulink> or <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Client_Configuration\">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
#: Web_Services.xml:1363
#, no-c-format
-msgid ""
-"You need to setup both the endpoint configuration and the WSSE declarations. "
-"That's two separate steps."
+msgid "You need to setup both the endpoint configuration and the WSSE declarations. That's two separate steps."
msgstr "你需要设置终端配置和 WSSE 声明。这是两个单独的步骤。"
#. Tag: title
@@ -4516,27 +3729,20 @@
#. Tag: para
#: Web_Services.xml:1372
#, 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."
+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: programlisting
#: Web_Services.xml:1375
#, no-c-format
msgid ""
-"<jboss-ws-security xmlns="http://www.jboss.com/ws-security/"
-"config" \n"
+"<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" \n"
"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
"xsi:schemaLocation="http://www.jboss.com/ws-security/config \n"
"http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">\n"
"(1) <key-store-file>WEB-INF/wsse.keystore</key-store-file>\n"
"(2) <key-store-password>jbossws</key-store-password>\n"
-"(3) <trust-store-file>WEB-INF/wsse.truststore</trust-store-"
-"file>\n"
+"(3) <trust-store-file>WEB-INF/wsse.truststore</trust-store-file>\n"
"(4) <trust-store-password>jbossws</trust-store-password>\n"
"(5) <config>\n"
"(6) <sign type="x509v3" alias="wsse"/>\n"
@@ -4546,15 +3752,13 @@
"</config>\n"
"</jboss-ws-security>"
msgstr ""
-"<jboss-ws-security xmlns="http://www.jboss.com/ws-security/"
-"config" \n"
+"<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" \n"
"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
"xsi:schemaLocation="http://www.jboss.com/ws-security/config \n"
"http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">\n"
"(1) <key-store-file>WEB-INF/wsse.keystore</key-store-file>\n"
"(2) <key-store-password>jbossws</key-store-password>\n"
-"(3) <trust-store-file>WEB-INF/wsse.truststore</trust-store-"
-"file>\n"
+"(3) <trust-store-file>WEB-INF/wsse.truststore</trust-store-file>\n"
"(4) <trust-store-password>jbossws</trust-store-password>\n"
"(5) <config>\n"
"(6) <sign type="x509v3" alias="wsse"/>\n"
@@ -4567,84 +3771,56 @@
#. Tag: para
#: Web_Services.xml:1378
#, no-c-format
-msgid ""
-"This specifies that the key store we wish to use is WEB-INF/wsse.keystore, "
-"which is located in our war file."
+msgid "This specifies that the key store we wish to use is WEB-INF/wsse.keystore, which is located in our war file."
msgstr "这指定了我们希望使用的密钥库是 WEB-INF/wsse.keystore，它位于 WAR 文件里。"
#. Tag: para
#: Web_Services.xml:1383
#, 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."
+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
#: Web_Services.xml:1388
#, no-c-format
-msgid ""
-"This specifies that the trust store we wish to use is WEB-INF/wsse."
-"truststore, which is located in our war file."
+msgid "This specifies that the trust store we wish to use is WEB-INF/wsse.truststore, which is located in our war file."
msgstr "这指定了我们要使用的信任库是 WEB-INF/wsse.truststore，它位于 WAR 文件里。"
#. Tag: para
#: Web_Services.xml:1393
#, 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."
+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
#: Web_Services.xml:1398
#, 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."
+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
#: Web_Services.xml:1403
#, no-c-format
-msgid ""
-"This means that the server must sign the message body of all responses. 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"
+msgid "This means that the server must sign the message body of all responses. 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
#: Web_Services.xml:1408
#, 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."
+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
#: Web_Services.xml:1413
#, 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
#: Web_Services.xml:1418
#, no-c-format
-msgid ""
-"By default an endpoint does not use the WS-Security configuration. Use the "
-"proprietary @EndpointConfig annotation to set the config name. See <ulink "
-"url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-"
-"WS_Endpoint_Configuration\">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. Use the proprietary @EndpointConfig annotation to set the config name. See <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Endpoint_Configuration\">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: programlisting
#: Web_Services.xml:1421
@@ -4674,8 +3850,7 @@
#: Web_Services.xml:1426
#, no-c-format
msgid ""
-"<jboss-ws-security xmlns="http://www.jboss.com/ws-security/"
-"config" \n"
+"<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" \n"
"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
"xsi:schemaLocation="http://www.jboss.com/ws-security/config \n"
"http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">\n"
@@ -4687,8 +3862,7 @@
"</config>\n"
"</jboss-ws-security>"
msgstr ""
-"<jboss-ws-security xmlns="http://www.jboss.com/ws-security/"
-"config" \n"
+"<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" \n"
"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
"xsi:schemaLocation="http://www.jboss.com/ws-security/config \n"
"http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">\n"
@@ -4703,35 +3877,25 @@
#. Tag: para
#: Web_Services.xml:1429
#, 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)."
+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
#: Web_Services.xml:1434
#, 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"
+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
#: Web_Services.xml:1439
#, 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."
+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
#: Web_Services.xml:1444
#, 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
@@ -4743,11 +3907,7 @@
#. Tag: para
#: Web_Services.xml:1451
#, 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."
+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
@@ -4761,43 +3921,27 @@
#, no-c-format
msgid ""
"<sysproperty key="org.jboss.ws.wsse.keyStore"\n"
-"value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse."
-"keystore"/>\n"
+"value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse.keystore"/>\n"
"<sysproperty key="org.jboss.ws.wsse.trustStore" \n"
-"value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse."
-"truststore"/>\n"
-"<sysproperty key="org.jboss.ws.wsse.keyStorePassword" "
-"value="jbossws"/>\n"
-"<sysproperty key="org.jboss.ws.wsse.trustStorePassword" "
-"value="jbossws"/>\n"
-"<sysproperty key="org.jboss.ws.wsse.keyStoreType" value=""
-"jks"/>\n"
-"<sysproperty key="org.jboss.ws.wsse.trustStoreType" value=""
-"jks"/>"
+"value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse.truststore"/>\n"
+"<sysproperty key="org.jboss.ws.wsse.keyStorePassword" value="jbossws"/>\n"
+"<sysproperty key="org.jboss.ws.wsse.trustStorePassword" value="jbossws"/>\n"
+"<sysproperty key="org.jboss.ws.wsse.keyStoreType" value="jks"/>\n"
+"<sysproperty key="org.jboss.ws.wsse.trustStoreType" value="jks"/>"
msgstr ""
"<sysproperty key="org.jboss.ws.wsse.keyStore"\n"
-"value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse."
-"keystore"/>\n"
+"value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse.keystore"/>\n"
"<sysproperty key="org.jboss.ws.wsse.trustStore" \n"
-"value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse."
-"truststore"/>\n"
-"<sysproperty key="org.jboss.ws.wsse.keyStorePassword" "
-"value="jbossws"/>\n"
-"<sysproperty key="org.jboss.ws.wsse.trustStorePassword" "
-"value="jbossws"/>\n"
-"<sysproperty key="org.jboss.ws.wsse.keyStoreType" value=""
-"jks"/>\n"
-"<sysproperty key="org.jboss.ws.wsse.trustStoreType" value=""
-"jks"/>"
+"value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse.truststore"/>\n"
+"<sysproperty key="org.jboss.ws.wsse.keyStorePassword" value="jbossws"/>\n"
+"<sysproperty key="org.jboss.ws.wsse.trustStorePassword" value="jbossws"/>\n"
+"<sysproperty key="org.jboss.ws.wsse.keyStoreType" value="jks"/>\n"
+"<sysproperty key="org.jboss.ws.wsse.trustStoreType" value="jks"/>"
#. Tag: para
#: Web_Services.xml:1461
#, 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 can therefore not manipulated in "
-"transit."
+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 can therefore not manipulated in transit."
msgstr "下面看到的转入 SOAP 消息的安全信息头被忽略了。也就是说，SOAP 的主体仍然是普通文本，但签署了安全性头部信息，因此不能在转换时操作。"
#. Tag: para
@@ -4810,50 +3954,42 @@
#: Web_Services.xml:1467
#, no-c-format
msgid ""
-"<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
-"">\n"
+"<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">\n"
"<env:Header>\n"
"<wsse:Security env:mustUnderstand="1" ...>\n"
"<wsu:Timestamp wsu:Id="timestamp">...</wsu:Timestamp>\n"
"<wsse:BinarySecurityToken ...>\n"
"...\n"
"</wsse:BinarySecurityToken>\n"
-"<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#""
-">\n"
+"<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">\n"
"...\n"
"</ds:Signature>\n"
"</wsse:Security>\n"
"</env:Header>\n"
"<env:Body wsu:Id="element-1-1140197309843-12388840" ...>\n"
-"<ns1:echoUserType xmlns:ns1="http://org.jboss.ws/samples/"
-"wssecurity">\n"
-"<UserType_1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-"
-"instance">\n"
+"<ns1:echoUserType xmlns:ns1="http://org.jboss.ws/samples/wssecurity">\n"
+"<UserType_1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">\n"
"<msg>Kermit</msg>\n"
"</UserType_1>\n"
"</ns1:echoUserType>\n"
"</env:Body>\n"
"</env:Envelope>"
msgstr ""
-"<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
-"">\n"
+"<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">\n"
"<env:Header>\n"
"<wsse:Security env:mustUnderstand="1" ...>\n"
"<wsu:Timestamp wsu:Id="timestamp">...</wsu:Timestamp>\n"
"<wsse:BinarySecurityToken ...>\n"
"...\n"
"</wsse:BinarySecurityToken>\n"
-"<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#""
-">\n"
+"<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">\n"
"...\n"
"</ds:Signature>\n"
"</wsse:Security>\n"
"</env:Header>\n"
"<env:Body wsu:Id="element-1-1140197309843-12388840" ...>\n"
-"<ns1:echoUserType xmlns:ns1="http://org.jboss.ws/samples/"
-"wssecurity">\n"
-"<UserType_1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-"
-"instance">\n"
+"<ns1:echoUserType xmlns:ns1="http://org.jboss.ws/samples/wssecurity">\n"
+"<UserType_1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">\n"
"<msg>Kermit</msg>\n"
"</UserType_1>\n"
"</ns1:echoUserType>\n"
@@ -4869,35 +4005,20 @@
#. Tag: para
#: Web_Services.xml:1474
#, 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
#: Web_Services.xml:1477
#, no-c-format
-msgid ""
-"The provider can be configured as part of your environment via static "
-"registration by adding an entry to the java.security properties file (found "
-"in $JAVA_HOME/jre/lib/security/java.security, where $JAVA_HOME is the "
-"location of your JDK/JRE distribution). You'll find detailed "
-"instructions in the file but basically it comes down to adding a line:"
+msgid "The provider can be configured as part of your environment via static registration by adding an entry to the java.security properties file (found in $JAVA_HOME/jre/lib/security/java.security, where $JAVA_HOME is the location of your JDK/JRE distribution). You'll 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: programlisting
#: Web_Services.xml:1480
#, no-c-format
-msgid ""
-"security.provider.<n>=org.bouncycastle.jce.provider."
-"BouncyCastleProvider"
-msgstr ""
-"security.provider.<n>=org.bouncycastle.jce.provider."
-"BouncyCastleProvider"
+msgid "security.provider.<n>=org.bouncycastle.jce.provider.BouncyCastleProvider"
+msgstr "security.provider.<n>=org.bouncycastle.jce.provider.BouncyCastleProvider"
#. Tag: para
#: Web_Services.xml:1481
@@ -4914,12 +4035,7 @@
#. Tag: para
#: Web_Services.xml:1492
#, no-c-format
-msgid ""
-"Where you put the jar is mostly up to you, although with jdk1.4 the best "
-"(and in some cases only) place to have it is in $JAVA_HOME/jre/lib/ext. "
-"Under Windows there will normally be a JRE and a JDK install of Java if you "
-"think you have installed it correctly and it still doesn't work chances "
-"are you have added the provider to the installation not being used."
+msgid "Where you put the jar is mostly up to you, although with jdk1.4 the best (and in some cases only) place to have it is in $JAVA_HOME/jre/lib/ext. Under Windows there will normally be a JRE and a JDK install of Java if you think you have installed it correctly and it still doesn't work chances are you have added the provider to the installation not being used."
msgstr "把 JAR 放在哪里由你来决定，虽然对于 jdk1.4 来说，最佳（在某些情况下是必须）位置是 $JAVA_HOME/jre/lib/ext。在 Windows 里，如果正确安装了 JRE 和 JDK 还是不能使用，那有可能是你添加了并没有使用的提供者。"
#. Tag: title
@@ -4931,14 +4047,8 @@
#. Tag: para
#: Web_Services.xml:1502
#, no-c-format
-msgid ""
-"If you having a hard time understanding how the different trust- and "
-"keystore configurations are used for signature and encryption, then read "
-"this thread first: <ulink url=\"http://www.jboss.org/index.html?"
-"module=bb&op=viewtopic&t=94406\"></ulink>"
-msgstr ""
-"如果你很难理解信任库和密钥库关于签名和加密的配置，你可以先阅读这篇文章：<ulink url=\"http://www.jboss.org/index.html?"
-"module=bb&op=viewtopic&t=94406\"></ulink>。"
+msgid "If you having a hard time understanding how the different trust- and keystore configurations are used for signature and encryption, then read this thread first: <ulink url=\"http://www.jboss.org/index.html?module=bb&op=viewtopic&t=94406\"></ulink>"
+msgstr "如果你很难理解信任库和密钥库关于签名和加密的配置，你可以先阅读这篇文章：<ulink url=\"http://www.jboss.org/index.html?module=bb&op=viewtopic&t=94406\"></ulink>。"
#. Tag: title
#: Web_Services.xml:1512
@@ -4949,17 +4059,8 @@
#. Tag: para
#: Web_Services.xml:1513
#, no-c-format
-msgid ""
-"Support for the WS-Coordination, WS-AtomicTransaction and WS-"
-"BusinessActivity specifications will be provided by technology recently "
-"acquired from Arjuna Technologies Ltd. This technology will be present "
-"within the JBoss Transactions 4.2.1 release. Further information can be "
-"obtained from the <ulink url=\"http://labs.jboss.org/portal/jbosstm\">JBoss "
-"Transactions Project</ulink>"
-msgstr ""
-"最近从 Arjuna Technologies Ltd 获得的技术将提供对 WS-Coordination、WS-AtomicTransaction 和 WS-"
-"BusinessActivity 规格的支持。这种技术将在 JBoss Transactions 4.2.1 版本里出现。你可以从 <ulink url=\"http://labs.jboss.org/portal/jbosstm\">JBoss "
-"Transactions Project</ulink> 里获得进一步的信息。"
+msgid "Support for the WS-Coordination, WS-AtomicTransaction and WS-BusinessActivity specifications will be provided by technology recently acquired from Arjuna Technologies Ltd. This technology will be present within the JBoss Transactions 4.2.1 release. Further information can be obtained from the <ulink url=\"http://labs.jboss.org/portal/jbosstm\">JBoss Transactions Project</ulink>"
+msgstr "最近从 Arjuna Technologies Ltd 获得的技术将提供对 WS-Coordination、WS-AtomicTransaction 和 WS-BusinessActivity 规格的支持。这种技术将在 JBoss Transactions 4.2.1 版本里出现。你可以从 <ulink url=\"http://labs.jboss.org/portal/jbosstm\">JBoss Transactions Project</ulink> 里获得进一步的信息。"
#. Tag: title
#: Web_Services.xml:1519
@@ -4970,23 +4071,13 @@
#. Tag: para
#: Web_Services.xml:1520
#, no-c-format
-msgid ""
-"J2EE 1.4 mandates support for Java API for XML Registries (JAXR). Inclusion "
-"of a XML Registry with the J2EE 1.4 certified Application Server is "
-"optional. Starting jboss-4.0.2, JBoss 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 1.4 mandates support for Java API for XML Registries (JAXR). Inclusion of a XML Registry with the J2EE 1.4 certified Application Server is optional. Starting jboss-4.0.2, JBoss 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
#: Web_Services.xml:1523
#, 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."
+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
@@ -4998,12 +4089,7 @@
#. Tag: para
#: Web_Services.xml:1528
#, no-c-format
-#, fuzzy
-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 jboss-service.xml of the "
-"META-INF directory in the juddi-service.sar"
+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 jboss-service.xml of the META-INF directory in the juddi-service.sar"
msgstr "服务"
#. Tag: para
@@ -5023,19 +4109,15 @@
#, no-c-format
msgid ""
"<!-- Datasource to Database-->\n"
-"<attribute name="DataSourceUrl">java:/DefaultDS</"
-"attribute>"
+"<attribute name="DataSourceUrl">java:/DefaultDS</attribute>"
msgstr ""
"<!-- Datasource to Database-->\n"
-"<attribute name="DataSourceUrl">java:/DefaultDS</"
-"attribute>"
+"<attribute name="DataSourceUrl">java:/DefaultDS</attribute>"
#. Tag: para
#: Web_Services.xml:1538
#, 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: programlisting
@@ -5043,35 +4125,23 @@
#, no-c-format
msgid ""
"<!-- Should all tables be created on Start-->\n"
-" <attribute "
-"name="CreateOnStart">false</attribute>\n"
-" <!-- Should all "
-"tables be dropped on Stop-->\n"
-" <attribute "
-"name="DropOnStop">true</attribute>\n"
-" <!-- Should all "
-"tables be dropped on Start-->\n"
-" <attribute "
-"name="DropOnStart">false</attribute>"
+" <attribute name="CreateOnStart">false</attribute>\n"
+" <!-- Should all tables be dropped on Stop-->\n"
+" <attribute name="DropOnStop">true</attribute>\n"
+" <!-- Should all tables be dropped on Start-->\n"
+" <attribute name="DropOnStart">false</attribute>"
msgstr ""
"<!-- Should all tables be created on Start-->\n"
-" <attribute "
-"name="CreateOnStart">false</attribute>\n"
-" <!-- Should all "
-"tables be dropped on Stop-->\n"
-" <attribute "
-"name="DropOnStop">true</attribute>\n"
-" <!-- Should all "
-"tables be dropped on Start-->\n"
-" <attribute "
-"name="DropOnStart">false</attribute>"
+" <attribute name="CreateOnStart">false</attribute>\n"
+" <!-- Should all tables be dropped on Stop-->\n"
+" <attribute name="DropOnStop">true</attribute>\n"
+" <!-- Should all tables be dropped on Start-->\n"
+" <attribute name="DropOnStart">false</attribute>"
#. Tag: para
#: Web_Services.xml:1542
#, 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: programlisting
@@ -5082,20 +4152,16 @@
"<attribute name="ShouldBindJaxr">true</attribute>\n"
" \n"
"<!-- Context to which JaxrConnectionFactory to bind to. \n"
-"If you have remote clients, please bind it to the global namespace(default "
-"behavior). \n"
-"To just cater to clients running on the same VM as JBoss, change to java:/"
-"JAXR -->\n"
+"If you have remote clients, please bind it to the global namespace(default behavior). \n"
+"To just cater to clients running on the same VM as JBoss, change to java:/JAXR -->\n"
"<attribute name="BindJaxr">JAXR</attribute>"
msgstr ""
"<!-- Should I bind a Context to which JaxrConnectionFactory bound-->\n"
"<attribute name="ShouldBindJaxr">true</attribute>\n"
" \n"
"<!-- Context to which JaxrConnectionFactory to bind to. \n"
-"If you have remote clients, please bind it to the global namespace(default "
-"behavior). \n"
-"To just cater to clients running on the same VM as JBoss, change to java:/"
-"JAXR -->\n"
+"If you have remote clients, please bind it to the global namespace(default behavior). \n"
+"To just cater to clients running on the same VM as JBoss, change to java:/JAXR -->\n"
"<attribute name="BindJaxr">JAXR</attribute>"
#. Tag: para
@@ -5107,29 +4173,24 @@
#. Tag: para
#: Web_Services.xml:1549
#, no-c-format
-msgid ""
-"Add authorized users to access the jUDDI registry. (Add a sql insert "
-"statement in a single line)"
+msgid "Add authorized users to access the jUDDI registry. (Add a sql insert statement in a single line)"
msgstr "添加授权用户来访问 jUDDI 注册表（在单独一行里添加一个 SQL insert insert 语句）。"
#. Tag: programlisting
#: Web_Services.xml:1552
#, no-c-format
msgid ""
-"Look at the script META-INF/ddl/juddi_data.ddl for more details. Example for "
-"a user 'jboss'\n"
+"Look at the script META-INF/ddl/juddi_data.ddl for more details. Example for a user 'jboss'\n"
" \n"
"INSERT INTO PUBLISHER (PUBLISHER_ID,PUBLISHER_NAME,\n"
"EMAIL_ADDRESS,IS_ENABLED,IS_ADMIN) \n"
-"VALUES ('jboss','JBoss User','jboss at xxx','"
-"true','true');"
+"VALUES ('jboss','JBoss User','jboss at xxx','true','true');"
msgstr ""
"更多细节请参考 META-INF/ddl/juddi_data.ddl 脚本。下面是一个用户 'jboss' 的例子：\n"
" \n"
"INSERT INTO PUBLISHER (PUBLISHER_ID,PUBLISHER_NAME,\n"
"EMAIL_ADDRESS,IS_ENABLED,IS_ADMIN) \n"
-"VALUES ('jboss','JBoss User','jboss at xxx','"
-"true','true');"
+"VALUES ('jboss','JBoss User','jboss at xxx','true','true');"
#. Tag: title
#: Web_Services.xml:1556
@@ -5140,26 +4201,19 @@
#. Tag: para
#: Web_Services.xml:1557
#, 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: programlisting
#: Web_Services.xml:1560
#, no-c-format
msgid ""
-"javax.xml.registry.ConnectionFactoryClass=org.apache.ws.scout.registry."
-"ConnectionFactoryImpl \n"
+"javax.xml.registry.ConnectionFactoryClass=org.apache.ws.scout.registry.ConnectionFactoryImpl \n"
"jaxr.query.url=http://localhost:8080/juddi/inquiry \n"
"jaxr.publish.url=http://localhost:8080/juddi/publish\n"
"juddi.proxy.transportClass=org.jboss.jaxr.juddi.transport.SaajTransport"
msgstr ""
-"javax.xml.registry.ConnectionFactoryClass=org.apache.ws.scout.registry."
-"ConnectionFactoryImpl \n"
+"javax.xml.registry.ConnectionFactoryClass=org.apache.ws.scout.registry.ConnectionFactoryImpl \n"
"jaxr.query.url=http://localhost:8080/juddi/inquiry \n"
"jaxr.publish.url=http://localhost:8080/juddi/publish\n"
"juddi.proxy.transportClass=org.jboss.jaxr.juddi.transport.SaajTransport"
@@ -5167,9 +4221,7 @@
#. Tag: para
#: Web_Services.xml:1561
#, 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
@@ -5181,19 +4233,13 @@
#. Tag: para
#: Web_Services.xml:1569
#, 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 run.sh/run.bat "
-"scripts to the java process via the \"-D\" option."
+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 run.sh/run.bat scripts to the java process via the \"-D\" option."
msgstr "当客户代码运行在 JBoss（可以是 servlet 或 EJB）内部时，你需要把 run.sh/run.bat 脚本里的系统属性通过 \"-D\" 选项传递给 java 进程。"
#. Tag: para
#: Web_Services.xml:1574
#, 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)."
+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: programlisting
@@ -5211,59 +4257,31 @@
#. Tag: para
#: Web_Services.xml:1584
#, 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."
+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
#: Web_Services.xml:1589
#, no-c-format
-msgid ""
-"<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/"
-"RegistryService.html\">javax.xml.registry.RegistryService</ulink> From J2EE "
-"1.4 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/j2ee/1.4/docs/api/javax/xml/registry/RegistryService.html\">javax.xml.registry.RegistryService</ulink> From J2EE 1.4 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
#: Web_Services.xml:1594
#, no-c-format
-#, fuzzy
-msgid ""
-"<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/"
-"BusinessLifeCycleManager.html\">javax.xml.registry.BusinessLifeCycleManager</"
-"ulink> From J2EE 1.4 JavaDoc: \"The BusinessLifeCycleManager interface, "
-"which is exposed by the Registry Service, implements the life cycle "
-"management functionality of the Registry as part of a business level API. "
-"Note that there is no authentication information provided, because the "
-"Connection interface keeps that state and context on behalf of the client.\""
+msgid "<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/BusinessLifeCycleManager.html\">javax.xml.registry.BusinessLifeCycleManager</ulink> From J2EE 1.4 JavaDoc: \"The BusinessLifeCycleManager interface, which is exposed by the Registry Service, implements the life cycle management functionality of the Registry as part of a business level API. Note that 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
#: Web_Services.xml:1599
#, no-c-format
-#, fuzzy
-msgid ""
-"<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/"
-"BusinessQueryManager.html\">javax.xml.registry.BusinessQueryManager</ulink> "
-"From J2EE 1.4 JavaDoc: \"The BusinessQueryManager interface, which is "
-"exposed by the Registry Service, implements the business style query "
-"interface. It is also referred to as the focused query interface.\""
+msgid "<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/xml/registry/BusinessQueryManager.html\">javax.xml.registry.BusinessQueryManager</ulink> From J2EE 1.4 JavaDoc: \"The BusinessQueryManager 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
#: Web_Services.xml:1604
#, 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
@@ -5276,21 +4294,15 @@
#: Web_Services.xml:1610
#, no-c-format
msgid ""
-"String queryurl = System.getProperty("jaxr.query.url", ""
-"http://localhost:8080/juddi/inquiry");\n"
-"String puburl = System.getProperty("jaxr.publish.url", ""
-"http://localhost:8080/juddi/publish");\n"
+"String queryurl = System.getProperty("jaxr.query.url", "http://localhost:8080/juddi/inquiry");\n"
+"String puburl = System.getProperty("jaxr.publish.url", "http://localhost:8080/juddi/publish");\n"
".. \n"
"Properties props = new Properties();\n"
-"props.setProperty("javax.xml.registry.queryManagerURL", "
-"queryurl);\n"
-"props.setProperty("javax.xml.registry.lifeCycleManagerURL", "
-"puburl);\n"
+"props.setProperty("javax.xml.registry.queryManagerURL", queryurl);\n"
+"props.setProperty("javax.xml.registry.lifeCycleManagerURL", puburl);\n"
" \n"
-"String transportClass = System.getProperty("juddi.proxy."
-"transportClass", \n"
-" "org.jboss.jaxr.juddi."
-"transport.SaajTransport");\n"
+"String transportClass = System.getProperty("juddi.proxy.transportClass", \n"
+" "org.jboss.jaxr.juddi.transport.SaajTransport");\n"
"System.setProperty("juddi.proxy.transportClass", transportClass);\n"
" \n"
"// Create the connection, passing it the configuration properties\n"
@@ -5298,21 +4310,15 @@
"factory.setProperties(props);\n"
"connection = factory.createConnection();"
msgstr ""
-"String queryurl = System.getProperty("jaxr.query.url", ""
-"http://localhost:8080/juddi/inquiry");\n"
-"String puburl = System.getProperty("jaxr.publish.url", ""
-"http://localhost:8080/juddi/publish");\n"
+"String queryurl = System.getProperty("jaxr.query.url", "http://localhost:8080/juddi/inquiry");\n"
+"String puburl = System.getProperty("jaxr.publish.url", "http://localhost:8080/juddi/publish");\n"
".. \n"
"Properties props = new Properties();\n"
-"props.setProperty("javax.xml.registry.queryManagerURL", "
-"queryurl);\n"
-"props.setProperty("javax.xml.registry.lifeCycleManagerURL", "
-"puburl);\n"
+"props.setProperty("javax.xml.registry.queryManagerURL", queryurl);\n"
+"props.setProperty("javax.xml.registry.lifeCycleManagerURL", puburl);\n"
" \n"
-"String transportClass = System.getProperty("juddi.proxy."
-"transportClass", \n"
-" "org.jboss.jaxr.juddi."
-"transport.SaajTransport");\n"
+"String transportClass = System.getProperty("juddi.proxy.transportClass", \n"
+" "org.jboss.jaxr.juddi.transport.SaajTransport");\n"
"System.setProperty("juddi.proxy.transportClass", transportClass);\n"
" \n"
"// Create the connection, passing it the configuration properties\n"
@@ -5335,8 +4341,7 @@
"*/\n"
"protected void login() throws JAXRException\n"
"{\n"
-"PasswordAuthentication passwdAuth = new PasswordAuthentication(userid, "
-"passwd.toCharArray());\n"
+"PasswordAuthentication passwdAuth = new PasswordAuthentication(userid, passwd.toCharArray());\n"
"Set creds = new HashSet();\n"
"creds.add(passwdAuth);\n"
" \n"
@@ -5348,8 +4353,7 @@
"*/\n"
"protected void login() throws JAXRException\n"
"{\n"
-"PasswordAuthentication passwdAuth = new PasswordAuthentication(userid, "
-"passwd.toCharArray());\n"
+"PasswordAuthentication passwdAuth = new PasswordAuthentication(userid, passwd.toCharArray());\n"
"Set creds = new HashSet();\n"
"creds.add(passwdAuth);\n"
" \n"
@@ -5365,23 +4369,19 @@
#. Tag: programlisting
#: Web_Services.xml:1618
#, no-c-format
-#, fuzzy
msgid ""
"/**\n"
"* Creates a Jaxr Organization with 1 or more services\n"
"*/\n"
-"protected Organization createOrganization(String orgname) throws "
-"JAXRException\n"
+"protected Organization createOrganization(String orgname) throws JAXRException\n"
"{\n"
"Organization org = blm.createOrganization(getIString(orgname));\n"
"org.setDescription(getIString("JBoss Inc"));\n"
-"Service service = blm.createService(getIString("JBOSS JAXR "
-"Service"));\n"
+"Service service = blm.createService(getIString("JBOSS JAXR Service"));\n"
"service.setDescription(getIString("Services of XML Registry"));\n"
"//Create serviceBinding\n"
"ServiceBinding serviceBinding = blm.createServiceBinding();\n"
-"serviceBinding.setDescription(blm.createInternationalString("Test "
-"Service Binding"));\n"
+"serviceBinding.setDescription(blm.createInternationalString("Test Service Binding"));\n"
" \n"
"//Turn validation of URI off\n"
"serviceBinding.setValidateURI(false);\n"
@@ -5396,14 +4396,11 @@
"TelephoneNumber telephoneNumber = blm.createTelephoneNumber();\n"
"telephoneNumber.setNumber("111-111-7777");\n"
"telephoneNumber.setType(null);\n"
-"PostalAddress address = blm.createPostalAddress("111", "My "
-"Drive", "BuckHead", "GA", "USA", "
-""1111-111", "");\n"
+"PostalAddress address = blm.createPostalAddress("111", "My Drive", "BuckHead", "GA", "USA", "1111-111", "");\n"
"Collection postalAddresses = new ArrayList();\n"
"postalAddresses.add(address);\n"
"Collection emailAddresses = new ArrayList();\n"
-"EmailAddress emailAddress = blm.createEmailAddress("anil at apache."
-"org");\n"
+"EmailAddress emailAddress = blm.createEmailAddress("anil at apache.org");\n"
"emailAddresses.add(emailAddress);\n"
" \n"
"Collection numbers = new ArrayList();\n"
@@ -5413,22 +4410,16 @@
"user.setEmailAddresses(emailAddresses);\n"
"user.setTelephoneNumbers(numbers);\n"
" \n"
-"ClassificationScheme cScheme = getClassificationScheme("ntis-gov:"
-"naics", "");\n"
-"Key cKey = blm.createKey("uuid:C0B9FE13-324F-413D-5A5B-"
-"2004DB8E5CC2");\n"
+"ClassificationScheme cScheme = getClassificationScheme("ntis-gov:naics", "");\n"
+"Key cKey = blm.createKey("uuid:C0B9FE13-324F-413D-5A5B-2004DB8E5CC2");\n"
"cScheme.setKey(cKey);\n"
"Classification classification = blm.createClassification(cScheme, \n"
-" "Computer Systems Design and Related "
-"Services", "5415");\n"
+" "Computer Systems Design and Related Services", "5415");\n"
"org.addClassification(classification);\n"
-"ClassificationScheme cScheme1 = getClassificationScheme("D-U-N-S", "
-""");\n"
-"Key cKey1 = blm.createKey("uuid:3367C81E-FF1F-4D5A-B202-"
-"3EB13AD02423");\n"
+"ClassificationScheme cScheme1 = getClassificationScheme("D-U-N-S", "");\n"
+"Key cKey1 = blm.createKey("uuid:3367C81E-FF1F-4D5A-B202-3EB13AD02423");\n"
"cScheme1.setKey(cKey1);\n"
-"ExternalIdentifier ei = blm.createExternalIdentifier(cScheme1, "D-U-N-S "
-"number", "08-146-6849");\n"
+"ExternalIdentifier ei = blm.createExternalIdentifier(cScheme1, "D-U-N-S number", "08-146-6849");\n"
"org.addExternalIdentifier(ei);\n"
"org.addService(service);\n"
"return org;\n"
@@ -5466,13 +4457,11 @@
"findQualifiers.add(FindQualifier.SORT_BY_NAME_ASC);\n"
"Collection namePatterns = new ArrayList();\n"
"String pattern = "%" + bizname + "%";\n"
-"LocalizedString ls = blm.createLocalizedString(Locale.getDefault(), "
-"pattern);\n"
+"LocalizedString ls = blm.createLocalizedString(Locale.getDefault(), pattern);\n"
"namePatterns.add(ls);\n"
" \n"
"// Find based upon qualifier type and values\n"
-"BulkResponse response = bqm.findOrganizations(findQualifiers, namePatterns, "
-"null, null, null, null);\n"
+"BulkResponse response = bqm.findOrganizations(findQualifiers, namePatterns, null, null, null, null);\n"
" \n"
"// check how many organisation we have matched\n"
"Collection orgs = response.getCollection();\n"
@@ -5483,8 +4472,7 @@
"}\n"
"else\n"
"{\n"
-"log.debug(" -- Matched " + orgs.size() + " organizations -- "
-"");\n"
+"log.debug(" -- Matched " + orgs.size() + " organizations -- ");\n"
" \n"
"// then step through them\n"
"for (Iterator orgIter = orgs.iterator(); orgIter.hasNext();)\n"
@@ -5519,13 +4507,11 @@
"findQualifiers.add(FindQualifier.SORT_BY_NAME_ASC);\n"
"Collection namePatterns = new ArrayList();\n"
"String pattern = "%" + bizname + "%";\n"
-"LocalizedString ls = blm.createLocalizedString(Locale.getDefault(), "
-"pattern);\n"
+"LocalizedString ls = blm.createLocalizedString(Locale.getDefault(), pattern);\n"
"namePatterns.add(ls);\n"
" \n"
"// Find based upon qualifier type and values\n"
-"BulkResponse response = bqm.findOrganizations(findQualifiers, namePatterns, "
-"null, null, null, null);\n"
+"BulkResponse response = bqm.findOrganizations(findQualifiers, namePatterns, null, null, null, null);\n"
" \n"
"// check how many organisation we have matched\n"
"Collection orgs = response.getCollection();\n"
@@ -5536,8 +4522,7 @@
"}\n"
"else\n"
"{\n"
-"log.debug(" -- Matched " + orgs.size() + " organizations -- "
-"");\n"
+"log.debug(" -- Matched " + orgs.size() + " organizations -- ");\n"
" \n"
"// then step through them\n"
"for (Iterator orgIter = orgs.iterator(); orgIter.hasNext();)\n"
@@ -5560,9 +4545,7 @@
#. Tag: para
#: Web_Services.xml:1623
#, 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
@@ -5574,47 +4557,26 @@
#. Tag: para
#: Web_Services.xml:1632
#, 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
#: Web_Services.xml:1637
#, 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."
+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
#: Web_Services.xml:1642
#, 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
#: Web_Services.xml:1647
#, 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
#: Web_Services.xml:1655
@@ -5649,46 +4611,25 @@
#. Tag: para
#: Web_Services.xml:1679
#, no-c-format
-#, fuzzy
-msgid ""
-"The Web Services Policy Framework (WS-Policy) provides a general purpose "
-"model and corresponding syntax to describe the policies of a Web Service."
+msgid "The Web Services Policy Framework (WS-Policy) provides a general purpose model and corresponding syntax to describe the policies of a Web Service."
msgstr "服务."
#. Tag: para
#: Web_Services.xml:1682
#, no-c-format
-msgid ""
-"WS-Policy defines a base set of constructs that can be used and extended by "
-"other Web services specifications to describe a broad range of service "
-"requirements and capabilities."
+msgid "WS-Policy defines a base set of constructs that can be used and extended by other Web services specifications to describe a broad range of service requirements and capabilities."
msgstr ""
#. Tag: para
#: Web_Services.xml:1685
#, no-c-format
-msgid ""
-"Current JBoss implementation can instrument a webservice with policies "
-"attached at endpoint, port or port-type scope level only. There are two "
-"different methods to attach policies: providing a wsdl decorated with "
-"policies and policy attachments as defined by specifications, or using JBoss "
-"proprietary annotations. The first way has the advantage of being standard, "
-"while the second one is much more simple to implement. Of course the wsdl "
-"generated by these annotations conforms to standard defined in "
-"specifications and can be used with any ws-policy compliant client."
+msgid "Current JBoss implementation can instrument a webservice with policies attached at endpoint, port or port-type scope level only. There are two different methods to attach policies: providing a wsdl decorated with policies and policy attachments as defined by specifications, or using JBoss proprietary annotations. The first way has the advantage of being standard, while the second one is much more simple to implement. Of course the wsdl generated by these annotations conforms to standard defined in specifications and can be used with any ws-policy compliant client."
msgstr ""
#. Tag: para
#: Web_Services.xml:1688
#, no-c-format
-msgid ""
-"Please note that ws-policy specifications only define policy requirements "
-"and their attachment method to wsdl through specific extensions. It is out "
-"of the scope of ws-policy specifications and thus implementation to define "
-"and use the content of assertions. The way these assertions (called domain "
-"assertions or domain policies) have to be deployed and used is left to other "
-"specification like WS-Security-Policy or more generally to domain specific "
-"implementation."
+msgid "Please note that ws-policy specifications only define policy requirements and their attachment method to wsdl through specific extensions. It is out of the scope of ws-policy specifications and thus implementation to define and use the content of assertions. The way these assertions (called domain assertions or domain policies) have to be deployed and used is left to other specification like WS-Security-Policy or more generally to domain specific implementation."
msgstr ""
#. Tag: title
@@ -5707,15 +4648,11 @@
#: Web_Services.xml:1696
#, no-c-format
msgid ""
-"* <ulink url=\"http://www.w3.org/Submission/WS-Policy/\"> WS-Policy "
-"specification</ulink>\n"
-"* <ulink url=\"http://www.w3.org/Submission/WS-PolicyAttachment/\"> WS-"
-"Policy-Attachment specification</ulink>"
+"* <ulink url=\"http://www.w3.org/Submission/WS-Policy/\"> WS-Policy specification</ulink>\n"
+"* <ulink url=\"http://www.w3.org/Submission/WS-PolicyAttachment/\"> WS-Policy-Attachment specification</ulink>"
msgstr ""
-"* <ulink url=\"http://www.w3.org/Submission/WS-Policy/\"> WS-Policy "
-"specification</ulink>\n"
-"* <ulink url=\"http://www.w3.org/Submission/WS-PolicyAttachment/\"> WS-"
-"Policy-Attachment specification</ulink>"
+"* <ulink url=\"http://www.w3.org/Submission/WS-Policy/\"> WS-Policy specification</ulink>\n"
+"* <ulink url=\"http://www.w3.org/Submission/WS-PolicyAttachment/\"> WS-Policy-Attachment specification</ulink>"
#. Tag: title
#: Web_Services.xml:1700
@@ -5726,20 +4663,13 @@
#. Tag: para
#: Web_Services.xml:1701
#, no-c-format
-msgid ""
-"To attach policies in this manner, the only thing you have to do in a "
-"webservice class is to provide a custom wsdl. This will cause JBossws to "
-"skip wsdl generation at deploy time, since the wsdl file you provided will "
-"be published. Please refer to specification (WS-Policy-Attachment) to learn "
-"how to modify wsdl to attach a policy."
+msgid "To attach policies in this manner, the only thing you have to do in a webservice class is to provide a custom wsdl. This will cause JBossws to skip wsdl generation at deploy time, since the wsdl file you provided will be published. Please refer to specification (WS-Policy-Attachment) to learn how to modify wsdl to attach a policy."
msgstr "为了以这种方式附加策略，你唯一要做的是在 webservice 类里提供自定义的 wsdl。既然你提供的 wsdl 文件将被发布，这就使得 JBossws 在部署时跳过 wsdl 的生成。请参考相关规格（WS-Policy-Attachment）来学习如何修改 wsdl 以附加策略。"
#. Tag: para
#: Web_Services.xml:1704
#, no-c-format
-msgid ""
-"Here you find an example of a webservice class and provided wsdl with a "
-"policy containing a domain assertion for JBoss wssecurity."
+msgid "Here you find an example of a webservice class and provided wsdl with a policy containing a domain assertion for JBoss wssecurity."
msgstr "在这里你会找到一个 webservice 类的例子，它提供了带有包含 JBoss wssecurity 域判断的策略的 wsdl 文件。"
#. Tag: programlisting
@@ -5755,43 +4685,31 @@
"private Logger log = Logger.getLogger(HelloJavaBean.class);\n"
"..\n"
"@WebMethod\n"
-"public UserType echoUserType(@WebParam(name = "user") UserType "
-"in0)\n"
+"public UserType echoUserType(@WebParam(name = "user") UserType in0)\n"
"{\n"
"log.info(in0);\n"
"return in0;\n"
"}\n"
"}\n"
"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<definitions name='HelloService' targetNamespace='http://"
-"org.jboss.ws/samples/wssecuritypolicy' xmlns='http://schemas."
-"xmlsoap.org/wsdl/' xmlns:ns1='http://org.jboss.ws/samples/"
-"wssecurity' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/"
-"' xmlns:tns='http://org.jboss.ws/samples/wssecuritypolicy' "
-"xmlns:wsp='http://schemas.xmlsoap.org/ws/2004/09/policy' xmlns:"
-"xsd='http://www.w3.org/2001/XMLSchema'>\n"
+"<definitions name='HelloService' targetNamespace='http://org.jboss.ws/samples/wssecuritypolicy' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://org.jboss.ws/samples/wssecurity' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://org.jboss.ws/samples/wssecuritypolicy' xmlns:wsp='http://schemas.xmlsoap.org/ws/2004/09/policy' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>\n"
"<types>\n"
-"<xs:schema targetNamespace='http://org.jboss.ws/samples/"
-"wssecurity' version='1.0' \n"
+"<xs:schema targetNamespace='http://org.jboss.ws/samples/wssecurity' version='1.0' \n"
" xmlns:xs='http://www.w3.org/2001/XMLSchema'>\n"
"<xs:complexType name='UserType'>\n"
"<xs:sequence>\n"
-"<xs:element minOccurs='0' name='msg' type='xs:"
-"string'/>\n"
+"<xs:element minOccurs='0' name='msg' type='xs:string'/>\n"
"</xs:sequence>\n"
"</xs:complexType>\n"
"</xs:schema>\n"
"</types>\n"
"<wsp:Policy wsu:Id='X509EndpointPolicy'\n"
-" xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-"
-"wss-wssecurity-utility-1.0.xsd'>\n"
+" xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>\n"
"<wsp:All>\n"
-"<sp:jboss-ws-security xmlns:sp='http://www.jboss.com/ws-security/"
-"schema/jboss-ws-security_1_0.xsd'>\n"
+"<sp:jboss-ws-security xmlns:sp='http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd'>\n"
"<sp:key-store-file>WEB-INF/wsse.keystore</sp:key-store-file>\n"
"<sp:key-store-password>jbossws</sp:key-store-password>\n"
-"<sp:trust-store-file>WEB-INF/wsse.truststore</sp:trust-store-"
-"file>\n"
+"<sp:trust-store-file>WEB-INF/wsse.truststore</sp:trust-store-file>\n"
"<sp:trust-store-password>jbossws</sp:trust-store-password>\n"
"<sp:config>\n"
"<sp:encrypt alias='wsse' type='x509v3'/>\n"
@@ -5809,31 +4727,26 @@
"<part name='return' type='ns1:UserType'/>\n"
"</message>\n"
"<portType name='Hello'>\n"
-"<operation name='echoUserType' parameterOrder='user'"
-">\n"
+"<operation name='echoUserType' parameterOrder='user'>\n"
"<input message='tns:Hello_echoUserType'/>\n"
"<output message='tns:Hello_echoUserTypeResponse'/>\n"
"</operation>\n"
"</portType>\n"
"<binding name='HelloBinding' type='tns:Hello'>\n"
"<wsp:PolicyReference URI='#X509EndpointPolicy'/>\n"
-"<soap:binding style='rpc' transport='http://schemas."
-"xmlsoap.org/soap/http'/>\n"
+"<soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/>\n"
"<operation name='echoUserType'>\n"
"<soap:operation soapAction=''/>\n"
"<input>\n"
-"<soap:body namespace='http://org.jboss.ws/samples/"
-"wssecuritypolicy' use='literal'/>\n"
+"<soap:body namespace='http://org.jboss.ws/samples/wssecuritypolicy' use='literal'/>\n"
"</input>\n"
"<output>\n"
-"<soap:body namespace='http://org.jboss.ws/samples/"
-"wssecuritypolicy' use='literal'/>\n"
+"<soap:body namespace='http://org.jboss.ws/samples/wssecuritypolicy' use='literal'/>\n"
"</output>\n"
"</operation>\n"
"</binding>\n"
"<service name='HelloService'>\n"
-"<port binding='tns:HelloBinding' name='HelloPort'"
-">\n"
+"<port binding='tns:HelloBinding' name='HelloPort'>\n"
"<soap:address location='REPLACE_WITH_ACTUAL_URL'/>\n"
"</port>\n"
"</service>\n"
@@ -5848,43 +4761,31 @@
"private Logger log = Logger.getLogger(HelloJavaBean.class);\n"
"..\n"
"@WebMethod\n"
-"public UserType echoUserType(@WebParam(name = "user") UserType "
-"in0)\n"
+"public UserType echoUserType(@WebParam(name = "user") UserType in0)\n"
"{\n"
"log.info(in0);\n"
"return in0;\n"
"}\n"
"}\n"
"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<definitions name='HelloService' targetNamespace='http://"
-"org.jboss.ws/samples/wssecuritypolicy' xmlns='http://schemas."
-"xmlsoap.org/wsdl/' xmlns:ns1='http://org.jboss.ws/samples/"
-"wssecurity' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/"
-"' xmlns:tns='http://org.jboss.ws/samples/wssecuritypolicy' "
-"xmlns:wsp='http://schemas.xmlsoap.org/ws/2004/09/policy' xmlns:"
-"xsd='http://www.w3.org/2001/XMLSchema'>\n"
+"<definitions name='HelloService' targetNamespace='http://org.jboss.ws/samples/wssecuritypolicy' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://org.jboss.ws/samples/wssecurity' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://org.jboss.ws/samples/wssecuritypolicy' xmlns:wsp='http://schemas.xmlsoap.org/ws/2004/09/policy' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>\n"
"<types>\n"
-"<xs:schema targetNamespace='http://org.jboss.ws/samples/"
-"wssecurity' version='1.0' \n"
+"<xs:schema targetNamespace='http://org.jboss.ws/samples/wssecurity' version='1.0' \n"
" xmlns:xs='http://www.w3.org/2001/XMLSchema'>\n"
"<xs:complexType name='UserType'>\n"
"<xs:sequence>\n"
-"<xs:element minOccurs='0' name='msg' type='xs:"
-"string'/>\n"
+"<xs:element minOccurs='0' name='msg' type='xs:string'/>\n"
"</xs:sequence>\n"
"</xs:complexType>\n"
"</xs:schema>\n"
"</types>\n"
"<wsp:Policy wsu:Id='X509EndpointPolicy'\n"
-" xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-"
-"wss-wssecurity-utility-1.0.xsd'>\n"
+" xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>\n"
"<wsp:All>\n"
-"<sp:jboss-ws-security xmlns:sp='http://www.jboss.com/ws-security/"
-"schema/jboss-ws-security_1_0.xsd'>\n"
+"<sp:jboss-ws-security xmlns:sp='http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd'>\n"
"<sp:key-store-file>WEB-INF/wsse.keystore</sp:key-store-file>\n"
"<sp:key-store-password>jbossws</sp:key-store-password>\n"
-"<sp:trust-store-file>WEB-INF/wsse.truststore</sp:trust-store-"
-"file>\n"
+"<sp:trust-store-file>WEB-INF/wsse.truststore</sp:trust-store-file>\n"
"<sp:trust-store-password>jbossws</sp:trust-store-password>\n"
"<sp:config>\n"
"<sp:encrypt alias='wsse' type='x509v3'/>\n"
@@ -5902,31 +4803,26 @@
"<part name='return' type='ns1:UserType'/>\n"
"</message>\n"
"<portType name='Hello'>\n"
-"<operation name='echoUserType' parameterOrder='user'"
-">\n"
+"<operation name='echoUserType' parameterOrder='user'>\n"
"<input message='tns:Hello_echoUserType'/>\n"
"<output message='tns:Hello_echoUserTypeResponse'/>\n"
"</operation>\n"
"</portType>\n"
"<binding name='HelloBinding' type='tns:Hello'>\n"
"<wsp:PolicyReference URI='#X509EndpointPolicy'/>\n"
-"<soap:binding style='rpc' transport='http://schemas."
-"xmlsoap.org/soap/http'/>\n"
+"<soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/>\n"
"<operation name='echoUserType'>\n"
"<soap:operation soapAction=''/>\n"
"<input>\n"
-"<soap:body namespace='http://org.jboss.ws/samples/"
-"wssecuritypolicy' use='literal'/>\n"
+"<soap:body namespace='http://org.jboss.ws/samples/wssecuritypolicy' use='literal'/>\n"
"</input>\n"
"<output>\n"
-"<soap:body namespace='http://org.jboss.ws/samples/"
-"wssecuritypolicy' use='literal'/>\n"
+"<soap:body namespace='http://org.jboss.ws/samples/wssecuritypolicy' use='literal'/>\n"
"</output>\n"
"</operation>\n"
"</binding>\n"
"<service name='HelloService'>\n"
-"<port binding='tns:HelloBinding' name='HelloPort'"
-">\n"
+"<port binding='tns:HelloBinding' name='HelloPort'>\n"
"<soap:address location='REPLACE_WITH_ACTUAL_URL'/>\n"
"</port>\n"
"</service>\n"
@@ -5935,12 +4831,8 @@
#. Tag: para
#: Web_Services.xml:1708
#, no-c-format
-msgid ""
-"Please note in the wsdl file the wsp:Policy element and the wsp:"
-"PolicyReference in 'HelloBinding' binding Element."
-msgstr ""
-"请注意 wsdl 文件里的 wsp:Policy 元素以及 'HelloBinding' binding 元素里的 wsp:"
-"PolicyReference。"
+msgid "Please note in the wsdl file the wsp:Policy element and the wsp:PolicyReference in 'HelloBinding' binding Element."
+msgstr "请注意 wsdl 文件里的 wsp:Policy 元素以及 'HelloBinding' binding 元素里的 wsp:PolicyReference。"
#. Tag: title
#: Web_Services.xml:1714
@@ -5951,22 +4843,13 @@
#. Tag: para
#: Web_Services.xml:1715
#, no-c-format
-msgid ""
-"Using JBoss proprietary annotation you only have to provide the policy xml, "
-"leaving wsdl generation to the JBossWS deployer."
+msgid "Using JBoss proprietary annotation you only have to provide the policy xml, leaving wsdl generation to the JBossWS deployer."
msgstr "要使用 JBoss 专有的注解，你必须提供 policy xml，从而把 wsdl 的生成留给 JBossWS deployer。"
#. Tag: para
#: Web_Services.xml:1718
#, no-c-format
-msgid ""
-"There are two annotations to use, the first one (@PolicyAttachment) "
-"containing an array of the second one (@Policy): this lets you have many "
-"policies attached to a class or method. In future domain policy "
-"implementations might ship domain annotations extending the @Policy "
-"annotation to provide needed metadata directly as annotation parameters. The "
-"current @Policy annotation takes a reference to a xml file containing a "
-"generic policy description written respecting ws-policy specification rules."
+msgid "There are two annotations to use, the first one (@PolicyAttachment) containing an array of the second one (@Policy): this lets you have many policies attached to a class or method. In future domain policy implementations might ship domain annotations extending the @Policy annotation to provide needed metadata directly as annotation parameters. The current @Policy annotation takes a reference to a xml file containing a generic policy description written respecting ws-policy specification rules."
msgstr "你可以使用两种注解，第一种（@PolicyAttachment）包含第二种（@Policy）的队列：这让你可以把多个策略附加到类或方法上。将来的域策略实现可能带有域注解，它扩展 @Policy 注解以把所需的元数据作为参数提供。目前的 @Policy 策略引用包含关于 ws-policy 规则的普通策略描述的 XML 文件。"
#. Tag: programlisting
@@ -6008,27 +4891,22 @@
#. Tag: para
#: Web_Services.xml:1722
#, no-c-format
-msgid ""
-"And here you have the previous section example re-implemented using "
-"annotations and xml policy file:"
+msgid "And here you have the previous section example re-implemented using annotations and xml policy file:"
msgstr "这里你会用注解和 XML 策略文件重新实现前一节的例子："
#. Tag: programlisting
#: Web_Services.xml:1725
#, no-c-format
msgid ""
-"@WebService(name = "Hello", targetNamespace = "http://org."
-"jboss.ws/samples/wssecurityAnnotatedpolicy")\n"
-"@PolicyAttachment({@Policy( policyFileLocation="WEB-INF/Policy."
-"xml", scope = PolicyScopeLevel.WSDL_PORT ) })\n"
+"@WebService(name = "Hello", targetNamespace = "http://org.jboss.ws/samples/wssecurityAnnotatedpolicy")\n"
+"@PolicyAttachment({@Policy( policyFileLocation="WEB-INF/Policy.xml", scope = PolicyScopeLevel.WSDL_PORT ) })\n"
"@SOAPBinding(style = SOAPBinding.Style.RPC)\n"
"public class HelloJavaBean\n"
"{\n"
"private Logger log = Logger.getLogger(HelloJavaBean.class);\n"
" \n"
"@WebMethod\n"
-"public UserType echoUserType(@WebParam(name = "user") UserType "
-"in0)\n"
+"public UserType echoUserType(@WebParam(name = "user") UserType in0)\n"
"{\n"
"log.info(in0);\n"
"return in0;\n"
@@ -6036,18 +4914,14 @@
"}\n"
"<?xml version="1.0" encoding="UTF-8"?>\n"
"...\n"
-"<wsp:Policy wsu:Id="X509EndpointPolicy" xmlns:wsp="http://"
-"schemas.xmlsoap.org/ws/2004/09/policy" \n"
-"xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-"
-"wssecurity-utility-1.0.xsd">\n"
+"<wsp:Policy wsu:Id="X509EndpointPolicy" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" \n"
+"xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">\n"
"<wsp:ExactlyOne>\n"
"<wsp:All>\n"
-"<sp:jboss-ws-security xmlns:sp="http://www.jboss.com/ws-security/"
-"schema/jboss-ws-security_1_0.xsd">\n"
+"<sp:jboss-ws-security xmlns:sp="http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">\n"
"<sp:key-store-file>WEB-INF/wsse.keystore</sp:key-store-file>\n"
"<sp:key-store-password>jbossws</sp:key-store-password>\n"
-"<sp:trust-store-file>WEB-INF/wsse.truststore</sp:trust-store-"
-"file>\n"
+"<sp:trust-store-file>WEB-INF/wsse.truststore</sp:trust-store-file>\n"
"<sp:trust-store-password>jbossws</sp:trust-store-password>\n"
"<sp:config>\n"
"<sp:encrypt type="x509v3" alias="wsse"/>\n"
@@ -6060,18 +4934,15 @@
"</wsp:ExactlyOne> \n"
"</wsp:Policy>"
msgstr ""
-"@WebService(name = "Hello", targetNamespace = "http://org."
-"jboss.ws/samples/wssecurityAnnotatedpolicy")\n"
-"@PolicyAttachment({@Policy( policyFileLocation="WEB-INF/Policy."
-"xml", scope = PolicyScopeLevel.WSDL_PORT ) })\n"
+"@WebService(name = "Hello", targetNamespace = "http://org.jboss.ws/samples/wssecurityAnnotatedpolicy")\n"
+"@PolicyAttachment({@Policy( policyFileLocation="WEB-INF/Policy.xml", scope = PolicyScopeLevel.WSDL_PORT ) })\n"
"@SOAPBinding(style = SOAPBinding.Style.RPC)\n"
"public class HelloJavaBean\n"
"{\n"
"private Logger log = Logger.getLogger(HelloJavaBean.class);\n"
" \n"
"@WebMethod\n"
-"public UserType echoUserType(@WebParam(name = "user") UserType "
-"in0)\n"
+"public UserType echoUserType(@WebParam(name = "user") UserType in0)\n"
"{\n"
"log.info(in0);\n"
"return in0;\n"
@@ -6079,18 +4950,14 @@
"}\n"
"<?xml version="1.0" encoding="UTF-8"?>\n"
"...\n"
-"<wsp:Policy wsu:Id="X509EndpointPolicy" xmlns:wsp="http://"
-"schemas.xmlsoap.org/ws/2004/09/policy" \n"
-"xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-"
-"wssecurity-utility-1.0.xsd">\n"
+"<wsp:Policy wsu:Id="X509EndpointPolicy" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" \n"
+"xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">\n"
"<wsp:ExactlyOne>\n"
"<wsp:All>\n"
-"<sp:jboss-ws-security xmlns:sp="http://www.jboss.com/ws-security/"
-"schema/jboss-ws-security_1_0.xsd">\n"
+"<sp:jboss-ws-security xmlns:sp="http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">\n"
"<sp:key-store-file>WEB-INF/wsse.keystore</sp:key-store-file>\n"
"<sp:key-store-password>jbossws</sp:key-store-password>\n"
-"<sp:trust-store-file>WEB-INF/wsse.truststore</sp:trust-store-"
-"file>\n"
+"<sp:trust-store-file>WEB-INF/wsse.truststore</sp:trust-store-file>\n"
"<sp:trust-store-password>jbossws</sp:trust-store-password>\n"
"<sp:config>\n"
"<sp:encrypt type="x509v3" alias="wsse"/>\n"
@@ -6124,14 +4991,8 @@
#. Tag: para
#: Web_Services.xml:1739
#, no-c-format
-msgid ""
-"For the set of standard annotations, please have a look at <ulink url="
-"\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Annotations\">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://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Annotations\">JAX-WS Annotations</ulink>"
+msgstr "关于标准注解的集合，请参考 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_Annotations\">JAX-WS Annotations</ulink>"
#. Tag: title
#: Web_Services.xml:1743
@@ -6155,8 +5016,7 @@
"public @interface EndpointConfig {\n"
"... \n"
"/**\n"
-"* The optional config-name element gives the configuration name that must be "
-"present in\n"
+"* The optional config-name element gives the configuration name that must be present in\n"
"* the configuration given by element config-file.\n"
"* \n"
"* Server side default: Standard Endpoint\n"
@@ -6165,8 +5025,7 @@
"String configName() default "";\n"
"...\n"
"/**\n"
-"* The optional config-file element is a URL or resource name for the "
-"configuration.\n"
+"* The optional config-file element is a URL or resource name for the configuration.\n"
"*\n"
"* Server side default: standard-jaxws-endpoint-config.xml\n"
"* Client side default: standard-jaxws-client-config.xml\n"
@@ -6186,8 +5045,7 @@
"public @interface EndpointConfig {\n"
"... \n"
"/**\n"
-"* The optional config-name element gives the configuration name that must be "
-"present in\n"
+"* The optional config-name element gives the configuration name that must be present in\n"
"* the configuration given by element config-file.\n"
"* \n"
"* Server side default: Standard Endpoint\n"
@@ -6196,8 +5054,7 @@
"String configName() default "";\n"
"...\n"
"/**\n"
-"* The optional config-file element is a URL or resource name for the "
-"configuration.\n"
+"* The optional config-file element is a URL or resource name for the configuration.\n"
"*\n"
"* Server side default: standard-jaxws-endpoint-config.xml\n"
"* Client side default: standard-jaxws-client-config.xml\n"
@@ -6216,8 +5073,7 @@
#, no-c-format
msgid ""
"/**\n"
-"* Provides web context specific meta data to EJB based web service "
-"endpoints.\n"
+"* Provides web context specific meta data to EJB based web service endpoints.\n"
"*\n"
"* @author thomas.diesler at jboss.org\n"
"* @since 26-Apr-2005\n"
@@ -6227,8 +5083,7 @@
"public @interface WebContext {\n"
"... \n"
"/** \n"
-"* The contextRoot element specifies the context root that the web service "
-"endpoint is deployed to.\n"
+"* The contextRoot element specifies the context root that the web service endpoint is deployed to.\n"
"* If it is not specified it will be derived from the deployment short name.\n"
"* \n"
"* Applies to server side port components only. \n"
@@ -6251,15 +5106,11 @@
"String urlPattern() default "";\n"
" \n"
"/**\n"
-"* The authMethod is used to configure the authentication mechanism for the "
-"web service. \n"
-"* As a prerequisite to gaining access to any web service which are protected "
-"by an authorization\n"
-"* constraint, a user must have authenticated using the configured "
-"mechanism.\n"
+"* The authMethod is used to configure the authentication mechanism for the web service. \n"
+"* As a prerequisite to gaining access to any web service which are protected by an authorization\n"
+"* constraint, a user must have authenticated using the configured mechanism.\n"
"*\n"
-"* Legal values for this element are "BASIC", or "CLIENT-"
-"CERT".\n"
+"* Legal values for this element are "BASIC", or "CLIENT-CERT".\n"
"*/\n"
"String authMethod() default "";\n"
" \n"
@@ -6278,10 +5129,8 @@
"String transportGuarantee() default "";\n"
" \n"
"/**\n"
-"* A secure endpoint does not by default publish it's wsdl on an "
-"unsecure transport.\n"
-"* You can override this behaviour by explicitly setting the secureWSDLAccess "
-"flag to false.\n"
+"* A secure endpoint does not by default publish it's wsdl on an unsecure transport.\n"
+"* You can override this behaviour by explicitly setting the secureWSDLAccess flag to false.\n"
"* \n"
"* Protect access to WSDL. See http://jira.jboss.org/jira/browse/JBWS-723 \n"
"*/\n"
@@ -6289,8 +5138,7 @@
"}"
msgstr ""
"/**\n"
-"* Provides web context specific meta data to EJB based web service "
-"endpoints.\n"
+"* Provides web context specific meta data to EJB based web service endpoints.\n"
"*\n"
"* @author thomas.diesler at jboss.org\n"
"* @since 26-Apr-2005\n"
@@ -6300,8 +5148,7 @@
"public @interface WebContext {\n"
"... \n"
"/** \n"
-"* The contextRoot element specifies the context root that the web service "
-"endpoint is deployed to.\n"
+"* The contextRoot element specifies the context root that the web service endpoint is deployed to.\n"
"* If it is not specified it will be derived from the deployment short name.\n"
"* \n"
"* Applies to server side port components only. \n"
@@ -6324,15 +5171,11 @@
"String urlPattern() default "";\n"
" \n"
"/**\n"
-"* The authMethod is used to configure the authentication mechanism for the "
-"web service. \n"
-"* As a prerequisite to gaining access to any web service which are protected "
-"by an authorization\n"
-"* constraint, a user must have authenticated using the configured "
-"mechanism.\n"
+"* The authMethod is used to configure the authentication mechanism for the web service. \n"
+"* As a prerequisite to gaining access to any web service which are protected by an authorization\n"
+"* constraint, a user must have authenticated using the configured mechanism.\n"
"*\n"
-"* Legal values for this element are "BASIC", or "CLIENT-"
-"CERT".\n"
+"* Legal values for this element are "BASIC", or "CLIENT-CERT".\n"
"*/\n"
"String authMethod() default "";\n"
" \n"
@@ -6351,10 +5194,8 @@
"String transportGuarantee() default "";\n"
" \n"
"/**\n"
-"* A secure endpoint does not by default publish it's wsdl on an "
-"unsecure transport.\n"
-"* You can override this behaviour by explicitly setting the secureWSDLAccess "
-"flag to false.\n"
+"* A secure endpoint does not by default publish it's wsdl on an unsecure transport.\n"
+"* You can override this behaviour by explicitly setting the secureWSDLAccess flag to false.\n"
"* \n"
"* Protect access to WSDL. See http://jira.jboss.org/jira/browse/JBWS-723 \n"
"*/\n"
@@ -6374,8 +5215,7 @@
"/**\n"
"* Annotation for specifying the JBoss security domain for an EJB\n"
"* \n"
-"* @author <a href="mailto:bill at jboss.org">Bill Burke</"
-"a>\n"
+"* @author <a href="mailto:bill at jboss.org">Bill Burke</a>\n"
"**/\n"
"@Target(ElementType.TYPE) @Retention(RetentionPolicy.RUNTIME)\n"
"public @interface SecurityDomain\n"
@@ -6399,8 +5239,7 @@
"/**\n"
"* Annotation for specifying the JBoss security domain for an EJB\n"
"* \n"
-"* @author <a href="mailto:bill at jboss.org">Bill Burke</"
-"a>\n"
+"* @author <a href="mailto:bill at jboss.org">Bill Burke</a>\n"
"**/\n"
"@Target(ElementType.TYPE) @Retention(RetentionPolicy.RUNTIME)\n"
"public @interface SecurityDomain\n"
More information about the jboss-cvs-commits
mailing list