JAX-WS / CXF中的/ encoded和/ literal支持 [英] /encoded and /literal support in JAX-WS/CXF

问题描述

我从来没有在Java中使用过RPC调用，因此我对需要研究的一些旧代码有些困惑。

I've never used RPC calls in java, so I'm a bit confused about some legacy code I will need to look into.

我希望你会

1）CXF不支持 rpc / encoded 调用（ JAXWS 2.0中不支持Rpc /编码的wsdls问题）。 CXF是否完全支持 rpc / literal 并为此在JAX-WS中指定？在此处提及，但不幸的是（为什么？）没有明确消息不支持RPC +编码的组合？我是否应该更深入（进入JSR 224）？

1) CXF doesn't support rpc/encoded calls("Rpc/encoded wsdls are not supported in JAXWS 2.0" problem). Is rpc/literal fully supported by CXF, and specified in JAX-WS for that matter? It is mentioned here but unfortunately(why???) there's no explicit message that a combination of RPC + Encoded is not supported? Should I look deeper(into JSR 224)?

2）文档/编码怎么样？是否由JAX-WS及其参考实现（至少为CXF）完全支持/指定（至少是CXF）？

2) What about document/encoded? Is it fully supported by/specified in JAX-WS and its reference implementations(CXF at least)?

推荐答案

在现代soap框架中例如CXF或JAX-WS，您可以仅使用 document / literal 或 rpc / literal 。

In modern soap frameworks such as CXF or JAX-WS you can only use document/literal or rpc/literal.

您在调查方面做得很好，但也许您应该将研究重点更多地放在WSDL和SOAP标准上，而不是jax-ws和cxf文档。

You did good in investigating but maybe you should have focused your research more on WSDL and SOAP standards instead of jax-ws and cxf documentation.

WS-I（ Web服务互操作性）组织定义了一组创建Web服务时要遵循的规则，以使其正常运行，而与编程语言或用于实现该服务的技术无关。该标准称为基本配置文件（通常称为WS -I BP），当前版本为2.0。

The WS-I (Web Services-Interoperability) organization defines a set of rules to be followed when creating a web service so it will work well, independently of the programming language or technologies used to implement it. This standard is called Basic Profile (usually referred as WS-I BP) and is currently on version 2.0.

WS-I BP建议不使用编码样式和仅使用文字。而且由于我们一直希望我们的Web服务符合BP（遵守Basic Profile），因此JAX-WS等较新的Web服务框架开始放弃对创建 rpc / encoded 和文档/编码的网络服务。

WS-I BP recommends not to use the 'encoded' style and use only 'literal'. And since we always want our web services to be BP compliant (to adhere to the Basic Profile), newer web services frameworks such as JAX-WS started dropping support for creating rpc/encoded and document/encodedweb services.

您不应花太多时间研究 document / encoded 组合，因为它从未被任何人真正使用过，因为这就像说您要使用xml架构类型进行消息传递，但不会包含任何xml架构。这就是为什么您很可能在任何地方都找不到有关文档/编码的信息。

You should not spend too much time looking into the document/encoded combination because it was never really used by anyone since it's like saying you are going to use xml schema types for the messaging but you are not going to include any xml schema. That's why it's very likely that you will find no information about document/encoded anywhere.

由于 rpc / encoded 是一种非常古老的消息传递样式，您应该使用相同时代的框架，例如轴1.4 和忘记了 CXF或JAX-WS，因为我认为他们从不支持它。

Since rpc/encoded is a very old messaging style you should use a framework of the same era, such as Axis 1.4 and forget about CXF or JAX-WS because I think they never supported it.

这篇关于JAX-WS / CXF中的/ encoded和/ literal支持的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！