The stubs are correct, there shouldn't be any CXF-specific imports in them because all the information CXF needs can be represented using the JAX-WS standard annotations. At runtime the CXF client libraries will be used if they are on the class path, or the RI ones built in to the JDK will be used if CXF is not available. The generated stubs will work with either.
You asked in the comments about which CXF JARs are required if you're just running a client - as far as I know it's just cxf-rt-frontend-jaxws
and cxf-rt-transports-http
plus their transitive dependencies. If your project is built with maven then just declare those two dependencies and everything else should come in automatically, if not then download the Apache Ivy main JAR and then run
java -jar ivy-2.3.0.jar -dependency org.apache.cxf cxf-rt-frontend-jaxws 2.7.3 -retrieve "[artifact]-[revision](-[classifier]).jar"
java -jar ivy-2.3.0.jar -dependency org.apache.cxf cxf-rt-transports-http 2.7.3 -retrieve "[artifact]-[revision](-[classifier]).jar"
This should resolve the transitive dependencies and download the relevant JARs from Maven Central into the current directory.