Summary of Web Service communication framework between heterogeneous systems (completion of planning)

This article does not discuss WS performance issues, nor does it discuss the use of non-framework methods such as TCP spoofed HTTP protocol communication, and only discuss the use of HTTP+SOAP communication framework between common systems and minefields.

Most of this article comes from thinking after migrating two heterogeneous ESB products within two months.

• Java

Java under the framework of many, the common problem is a get (HTTP get) WSDL file and then the framework of dynamic compilation, and then the post service. There is nothing wrong with the performance of the case. If the service URL is inaccessible in the obtained WSDL, the framework generates an error. If you cannot change the source to direct post, one solution is to put the manually downloaded WSDL and XSD files (if any) into a directory, and specify Wsdlurl as the file://protocol in the properties file and point to the WSDL file location.

1. Apache AXIS 1.4

The Org.apache.axis.component.encoding.utf8encoder::writeencoded method is overweight for char greater than 0x7f, and if some C-write backend services do not parse the NC encoding correctly, receive content such as # In the form of XXXX, you may consider modifying the above method.

1. Apache AXIS 2
2. Apache CXF
3. Jaxb

• Linux/C + +

1. gSOAP

The most common pit to be encountered is random coredump/segment Fault, which is usually caused by the allocation of memory without emptying. gSOAP use points: After using Soap_malloc, be sure to empty the obtained memory, using Memset or bzero.

And if you don't want to add debug options to the print log at compile time, or if you want to customize the save log, consider using the gSOAP logging plugin.

Please refer to: https://www.cs.fsu.edu/~engelen/soapdoc2.html#tth_sEc19.38

2. Apache AXIS 2

• Windows/C + +

1. gSOAP
2. WWS API

Using the WWS API has a further set of alternatives for the WS framework under Windows. The appropriate version of the Windows SDK must be installed using the WWS API. Although you can write code that uses the WWS API and compile successfully after Windows 2003 Server SP2 installs Visual Studio by default, the lack of WebServices.DLL programs does not work.

Please refer to: https://msdn.microsoft.com/zh-cn/library/ee617176 (v=vs.85). aspx

• . NET Framework

I believe everyone hates and loves the. Net framework.

1. WCF uses configuration to implement log behavior: https://msdn.microsoft.com/en-us/library/ms730064 (v=vs.110). aspx
2. The Web Reference extension Iendpointbehavior,iclientmessageinspector implements the log behavior.

Summary of Web Service communication framework between heterogeneous systems (completion of planning)