Change the binding style to document literal non-wrapped.
将绑定风格改成document literal non -wrapped。
This supports RPC literal, RPC encoded, and document literal styles.
它支持rpc文字、rpc编码和文档文字形式。
Unlike an explicitly bound attachment, it has a document literal wrapped style.
与显示绑定附件不同，它是文档文字封装式风格。
Document literal wrapped is the default binding style in Integration Developer.
文档文字封装风格是IntegrationDeveloper中默认的绑定风格。
Within these operations, an XML document literal payload is exchanged within the SOAP body.
在这些操作里面，一个XML文档的文本载荷是在SOAP主体里面被交换的。
Create an interface as before, but leave the binding style as document literal wrapped.
和之前一样创建接口，将绑定风格设为document literalwrapped。
It follows the best practice of being defined according to the wrapped document literal form.
它遵循根据包装文档的文本形式定义的最佳实践。
When Document Literal encoded Web services have methods that take more than one parameter
Document Literal编码的Web服务中的方法使用多个参数时
An interface operation is not restricted to only a document literal non-wrapped or RPC literal binding style.
接口操作不限于文档文字非封装式或RPC文字绑定风格。
You can assign an XML processing instruction literal to a variable or include it in an XML document literal.
可以将XML处理指令文本分配给一个变量，也可以将它包含在XML文档文本中。
However, you can use either a document literal non-wrapped or document literal wrapped binding style with the referenced attachment with a swaRef-typed element.
但是，对于包含swaref类型的元素的引用附件，既可使用文档文字非封装绑定风格，也可使用文档文字封装式绑定风格。
Listing 18 shows the part of a generated WSDL that is not WS-I compliant for both Document Wrapped and Document Literal, which contains the namespace attribute.
清单18展示了生成的WSDL的一部分，它对于DocumentWrapped和Document Literal都不满足WS - i依从性，二者包含了namespace属性。
This article identifies the value addition provided by wrapped document literal pattern in the WSDL design and the shortcoming on method overloading programming practice.
本文介绍了由WSDL设计中的wrapped文档文本模式提供的附加价值，以及方法重载编程实践中的缺点。
NOTE: the header and fault elements for RPC Literal Web services should be defined in the same style as in Document Literal encoding as per assertion requirement R2205.
注意：RPCLiteralWeb服务的header元素和fault元素都应按Document Literal中相同的样式来定义，按照断言需求r 2205编码。
In addition to basic support for JDK 1.4 (5.1.1), the new WebSphere Studio tooling provides numerous Web services wizards to support document literal and RPC SOAP-encoded services.
除了基本的支持JDK 1.4(5.1.1)，新WebSphereStudio工具提供了大量的Web服务向导，以支持文档文字和RPCSOAP编码服务。
Because we are using the document literal non-wrapped binding style instead of the document literal wrapped binding style typically used in Integration Developer, we see this unexpected code.
由于我们使用的是文档文字非封装式绑定风格而非IntegrationDeveloper中常用的文档文字封装式绑定风格，我们看到的不是预期的代码。
For example, many tools do not properly handle WSDL files that import schemas instead of embedding them; and fully automated support for producing wrapped-document literal WSDL is lacking.
例如，许多工具不能正确地处理导入模式而不是嵌入模式的WSDL文件，而且也缺少对生成包装的文档文本样式的WSDL的全自动支持。
So you must use the document/literal, non-wrapped style or one of the RPC styles.
所以您必须采用文档/文字非包装的样式或某种RPC样式。
The way wrapped document/literal style is defined, it ends up invoking a remote procedure.
“包装的文档/文本”样式已定义，它将以调用远程过程结束。
Among SOAP advocates, recent emphasis has shifted from SOAP's RPC roots to what is called the document-literal style of SOAP.
在SOAP的提倡者中，最近的重点已经从SOAP的RPC源头转移到了所谓的实文档方式的SOAP。
Document style with operation mode literal (document/literal).
带有文字的操作模式（文档／文字的）的文档样式。
The most common combination of these two is called "document/literal."
这两项的最常见组合称为“文档/文本”。
For example, using the document-literal encoding imposes wrapped versions of each method class, and that, in turn, creates additional manageability and maintainability issues.
例如，使用文档文字编码利用了每个方法类的封装版本，并造成了额外的可管理性与可维护性的问题。
Here the document is provided as a literal value, but it could also be passed to the database through a parameter marker or host variable.
在这里，以字面值形式提供文档，但是也可以通过参数标志或主机变量把文档传递给数据库。
In this way, REST is similar to the document-literal style of SOAP services.
使用这种方法，REST就与文档文本风格的SOAP服务非常类似。
You created a wrapped object, as per the document-literal wrapped WSDL style.
您根据文档-文本包装WSDL 样式创建了一个经过包装的对象。
Therefore, you are safest if you only use Document/literal as your encoding style.
因此，如果您只使用Document/literal作为编码样式，则您是最安全的。
Figure 3: Mapping of one parameter operation for a Document-Literal service call.
图3：一个文档-文字式的服务调用的一个操作参数映射。
Figure 5: Mapping of a complex parameter operation for a Document-Literal service call.
图5：一个文档-文字式的服务调用的一个复杂操作参数映射。
Thus, if you anticipate any interoperability with your services, we would strongly advocate that you plan on using the document-literal style for your Web Services.
因此，如果您预先考虑您的服务的互操作性，我们将会强烈建议您计划在您的 Web 服务中使用文档-文字样式。
应用推荐