cxf reversely generates server-side code based on .net wsdl content

Historical legacy projects, developed with c#, the original web service is .net, and now I want to replace it with a java version of the server, but the client is still the old .net client, which needs to be reversed according to the wsdl contentWrite java web service code, the following is the result of tossing in the past few days.

The web service on the java side wants to be developed based on cxf, using cxf springboot start, the process of creating a project is relatively simple, the key point is referenced in maven's pom.xml file

 org.apache.cxfcxf-spring-boot-starter-jaxws3.5.3

Write another cxf automatic configuration class

package com.xxx.webservicedemo.config;import com.xxx.webservicedemo.service.OrderWebService;import org.apache.cxf.Bus;import org.apache.cxf.jaxws.EndpointImpl;import org.springframework.beans.factory.annotation.Autowired;import org.springframework.boot.autoconfigure.EnableAutoConfiguration;import org.springframework.context.annotation.Bean;import org.springframework.context.annotation.Configuration;import javax.xml.ws.Endpoint;@[email protected] class CxfConfig {@Autowiredprivate Bus bus;@AutowiredOrderWebService orderWebService;/** JAX-WS* Site Services* **/@Beanpublic Endpoint endpoint() {EndpointImpl endpoint = new EndpointImpl(bus, orderWebService);endpoint.publish("/orderService");return endpoint;}}

That's it, the rest is to write the OrderWebService interface and the implementation class. These two use cxf to reverse-generate the server-side code implementation based on the wsdl description.

Download the complete apache cxf archive and configure the CXF_HOME and path environment variables.

Save the WSDL description xml file of the web service developed by .net to the client's local, because the content needs to be modified, otherwise an error will be reported:

WSDLToJava Error: file:/xxx.xml: undefined simple or complex type 'soapenc:Array'

This undefined simple or complex type 'soapenc:Array' error is caused by the old and non-standard version of the .net web service protocol. The solution is to download a https://schemasxmlsoap.azurewebsites.net/soap/encoding/

file, save it to the client's local and the .net web service description xml file in the same directory, for example, name it encoding.xsd, then modify the web service interface description xml document content, find

Change to

Then execute wsdl2java.bat -p com.xxx.webservice -d d:\temp\ -server -impl -autoNameResolution service1.xml

Then several conflict errors will be reported. When this happens, open the encoding.xsd file and modify the corresponding line according to the prompts. Generally, the type definitions such as int, string, and bool conflict. Comment out.Yes, for example:

This will generate successfully.