2023年4月6日 20:36:37go评论75阅读模式

英文:

Expose SOAP API using WSDL 1.1 as REST API in WSO2 API Manager 4.1

问题

我尝试将我旧的SOAP后端暴露为WSO2 API Manager中的REST API，但我遇到了这个错误："错误：响应状态为415"。

如附图所示

在carbon日志中找到的日志。

英文:

I Try to expose my old SOAP Backend which use WSDL version 1.1 as a REST API in WSO2 API Manager but i got this error "Error: response status is 415".

As shown in the attached photo below

Logs found in carbon logs .

TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;POST /Amplitude-WS/public?wsdl HTTP/1.1[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Origin: https://uib-as522.uib.socgen:9443[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;SOAPAction: [\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Referer: https://uib-as522.uib.socgen:9443/[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Sec-Fetch-Dest: empty[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Sec-Fetch-Site: same-site[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Accept-Encoding: gzip, deflate, br[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;accept: application/json[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Sec-Fetch-Mode: cors[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;activityid: 083f1db3-599f-4c90-942c-31d1ed180b58[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;sec-ch-ua: &quot;Google Chrome&quot;;v=&quot;111&quot;, &quot;Not(A:Brand&quot;;v=&quot;8&quot;, &quot;Chromium&quot;;v=&quot;111&quot;[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;sec-ch-ua-mobile: ?0[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;sec-ch-ua-platform: &quot;Windows&quot;[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Accept-Language: fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Content-Type: application/soap+xml[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Transfer-Encoding: chunked[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Host: uib-as150.uib.socgen:9443[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;Connection: Keep-Alive[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;1ce[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;&lt;?xml version=&#39;1.0&#39; encoding=&#39;UTF-8&#39;?&gt;&lt;soapenv:Envelope xmlns:soapenv=&quot;http://www.w3.org/2003/05/soap-envelope&quot; xmlns:web=&quot;http://services.omnichannel.ws.uib.tn.com/&quot;&gt;&lt;soapenv:Body&gt;&lt;web:BranchList&gt;&lt;BranchListRequest&gt;&lt;MessageHeader&gt;&lt;RequestChannel&gt;string&lt;/RequestChannel&gt;&lt;InitialRequestId&gt;string&lt;/InitialRequestId&gt;&lt;RequestTime&gt;string&lt;/RequestTime&gt;&lt;RequestId&gt;string&lt;/RequestId&gt;&lt;/MessageHeader&gt;&lt;/BranchListRequest&gt;&lt;/web:BranchList&gt;&lt;/soapenv:Body&gt;&lt;/soapenv:Envelope&gt;[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;0[\r][\n]&quot;
TID: [-1234] [] [2023-04-05 13:00:35,962] DEBUG {org.apache.synapse.transport.http.wire} - HTTPS-Sender I/O dispatcher-1 &lt;&lt; &quot;[\r][\n]&quot;

答案1

得分: 0

根据您的问题，看起来您的后端是SOAP 1.1。但是APIM生成的SOAP请求是SOAP 1.2。要解决这个问题，您需要进行以下更改：

更改端点格式为SOAP 1.1

此设置位于API配置 -> 端点 -> 单击齿轮图标以打开高级配置界面

在转换配置中更改消息类型和SOAP信封

此设置位于API配置 -> 资源 -> 展开一个资源并可以看到它的末尾。

将消息类型属性从 application/soap+xml 更改为 text/xml，如下所示：

<property description="messageProperty" name="messageType" scope="axis2" type="STRING" value="text/xml"/>

在PayloadFactory中将SOAP命名空间从 https://www.w3.org/2003/05/soap-envelope 更改为 https://schemas.xmlsoap.org/soap/envelope/，如下所示：

<payloadFactory description="transform" media-type="xml">
  <format>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Header/>
    <soapenv:Body>
      ...
</payloadFactory>

英文:

According to your question, it looks like your backend is SOAP 1.1. But the SOAP request generated by APIM is SOAP 1.2. To fix this you will need to make the following changes,

Change the endpoint format to SOAP 1.1

This setting can be found at API Configurations -> Endpoints -> Click on the gear icon to open the Advanced Configurations UI

Change the messageType and SOAP envelope in Transformation Configurations

This setting can be found at API Configurations -> Resources -> Expand a resource and can see this to the end of it.

Change the messageType property from application/soap+xml to text/xml as follows,

&lt;property description=&quot;messageProperty&quot; name=&quot;messageType&quot; scope=&quot;axis2&quot; type=&quot;STRING&quot; value=&quot;text/xml&quot;/&gt;

Change the SOAP Namespace from https://www.w3.org/2003/05/soap-envelope to https://schemas.xmlsoap.org/soap/envelope/ in the PayloadFactory as follows,

&lt;payloadFactory description=&quot;transform&quot; media-type=&quot;xml&quot;&gt;
  &lt;format&gt;
    &lt;soapenv:Envelope xmlns:soapenv=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;&gt;
    &lt;soapenv:Header/&gt;
    &lt;soapenv:Body&gt;
      ...
&lt;/payloadFactory&gt;

通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。

使用 WSO2 API Manager 4.1 将 WSDL 1.1 作为 REST API 暴露为 SOAP API。

问题

答案1

Webclient on Eclipse Java CXF 2.7.9 – 修复格式错误的 .wsdl 文件

WSO2 IS 持续出现打开的文件过多的错误。

WSO2：WSO2的一些仓库之间有哪些区别？

In the API Manager custom policy, I need to call an endpoint and the response need to store in the Property Mediator

What's the correct way to type hint an empty list as a literal in python?

如何在Highcharts Gantt中更改本地化的星期名称

如何在同一个流中使用多个过滤器和映射函数？

如何使用Map/Set来将代码优化到O(n)？

.NET MAUI Android在GitHub Actions上构建失败，错误代码为1。

如何在Playwright视觉比较中屏蔽多个定位器？

在C++中，可以使用可变模板参数来检索类型的内部类型。

selenium.common.exceptions.StaleElementReferenceException: Message: stale element reference: stale element not found

Creating and opening a URL to log in to Website via Basic Auth with Robot Framework/Selenium (Python)

AG Grid 在上下文菜单中以大文本形式打开

发表评论