How to Migrate SOAP Project from Mule 3.9 to 4.5?

We're upgrading from Mule 3.9 to Mule 4.5 (Community Edition). We have a few Mule connectors that act as bridges between our application and some third party services on the Internet using SOAP. Here is an example:

	<http:listener-config name="HTTP_Listener_Configuration"
		host="0.0.0.0" port="${mule.port}" basePath="${mule.base.path}"
		doc:name="HTTP Listener Configuration" />
	<http:request-config name="HTTP_Request_Configuration"
		host="${outside.host}" port="${outside.port}" basePath="${outside.base.path}"
		doc:name="HTTP Request Configuration" />
	<flow name="bridgeFlow">
		<http:listener config-ref="HTTP_Listener_Configuration"
			path="${mule.app.path}" allowedMethods="POST" doc:name="Mule Listener" />
		<cxf:proxy-service namespace="${wsdl.namespace}"
			service="${wsdl.service}" payload="envelope" wsdlLocation="${wsdl.location}"
			soapVersion="1.2" doc:name="CXF" />
		<http:request config-ref="HTTP_Request_Configuration"
			path="${outside.app.path}" method="POST" doc:name="Outside Requester" />
	</flow>

The CXF component references a WSDL file in the resources directory of the Mule project that is slightly different from the WSDL returned by the outside service. I'm not a SOAP expert and I'm not sure why it was done this way, but it has been working for 10 years. The goal of this migration is for it to continue to work without having to make changes to our Java application.

I've looked at using a Web Service Consumer instead of the CXF component, but I can't figure out how to get it to work. Is this doable with Mule 4? If so, could somebody point me to simple example I could use to migrate our old Mule projects?