It looks to me like the problem is caused only by the messages used for the HTTP bindings, they have parts defined without types :
<wsdl:message name="RequestMainXMLHttpGetOut"> <wsdl:part name="Body"></wsdl:part> </wsdl:message>
These are then used later on in the HTTP bindings
<wsdl:binding name="ServiceHttpGet" type="tns:ServiceHttpGet"> <http:binding verb="GET"></http:binding> <wsdl:operation name="RequestMainXML"> <http:operation location="/RequestMainXML"></http:operation> <wsdl:input> <http:urlEncoded></http:urlEncoded> </wsdl:input> <wsdl:output> <mime:content part="Body" type="text/xml"></mime:content> </wsdl:output> </wsdl:operation> ...
The problem is I don't think the CXF wsdl2java compiler ever supported this binding. Do you intend invoking using this binding? It looks like you have the same service exposed using multiple bindings. If you don't intend invoking using this binding from CXF you could copy the WSDL locally to the client and remove the offending messages and their porttypes/bindings/ports.
You may be able to invoke against these endpoints using CXF the CXF support for JAX-RS, but I haven't used this much.