Listing 8 shows the corresponding mapping for the method parameter to the message part.
清单8显示消息部分中方法参数的映射。
Is a constant delimiter, followed by the optional name of the message part to be accessed.
是一个常量分隔符，后跟要访问的消息部分的可选名称。
The message part name is mandatory for interface typed variables, and optional for data typed variables.
消息部分的名称对于接口类型的变量是必需的，对于数据类型的变量是可选的。
The content of the <wsdlsoap:header> element identifies the message part that is to be transferred in the header.
<wsdlsoap:header>元素的内容能够识别在消息头中传送的消息部分。
Each element has both a name and type attribute that specify the message part name and its corresponding data type.
每一个元素具有一个名字和类型属性来定义消息part的名字及相应的数据类型。
Each message part contains one or more headers, followed by the part contents.
每一个消息部件含有一个或多个报头，后跟部件内容。
Repeat the above steps, create a new message getQuotesResponse, add a message part quotes, and set the type for quotes.
重复上述步骤，创建新消息getQuotesResponse，添加消息部件quotes，并为 quotes设置类型。
Optionally, there can follow an XPath expression prefixed by a backslash to access only a specific element of the message part.
可选地，后面还可以跟着一个前缀为反斜杠的XPath表达式，以仅访问该消息部分的特定元素。
Optionally, there can follow an XPath expression prefixed by a backslash, to access only a specific element of the message part.
可选地，后面还可以跟着一个前缀为反斜杠的XPath表达式，以仅访问该消息部分的特定元素。
The message part name is mandatory for interface typed variables, and defaults to "Parameters" for doclit/wrapped style interfaces.
消息部分的名称对接口类型的变量是强制性的，doclit/wrapped样式的接口的缺省值是“Parameters”。
Each message part within that element must correspond exactly (in name and order) to a parameter of that programming-language operation.
在这个元素中的每个消息部分必须严格地对应(在名称和次序方面)于该编程语言操作的参数。
The JAX-RPC runtime catches a user exception and serializes it to XML data based on the schema definition referenced by the message part of the wsdl:fault.
JAX-RPCruntime捕获用户异常，并且基于通过 wsdl:fault 的消息部分所引用的schema定义来将其序列化成XML数据。
The part boundary includes a random component (" 41184676334 ") to ensure that the boundary string does not accidentally appear inside a message part.
部件边界包含了一个随机组件(“41184676334”)，以确保边界字符串不会偶然出现在消息部件之中。
If the message part that is transferred in the header does not show up anywhere in the element, you have an implicit header. Listing 4 shows what this might look like.
如果在消息头中传送的消息部分没有在元素中显示，那么它就是一个隐式消息头。
When a message part falls outside the rules, the Web services runtime presents it to the application (and vice versa) as a generic SOAPElement rather than a mapped type.
当消息部分超出了规则时，Web服务运行时就会把它作为一般的SOAPElement而不是映射的类型呈现给应用程序(反之亦然)。
Most importantly, it is usable only for SOAP-formatted messages, and it cannot modify message part types or sequence of message interrogations that is sometimes critical in high-volume situations.
最重要的是，它只能用于soap格式的消息，并且不能修改消息部分的类型或者消息查询的顺序，而对于大容量情况而言，这一点有时是至关重要的。
Optionally, there can follow an XPath expression to access only a specific element of the message (part).
此外，还可以后跟一个XPath表达式，仅访问消息（部分）的特定元素。
Optionally, there can follow an XPath expression to access only a specific element of the message (part).
此外，还可以后跟一个XPath表达式，仅访问消息（部分）的特定元素。
应用推荐