The answer lied in the fact that the vendor actually intended consumers to use xmlbeans for bindings and not jaxb as per the current jax-ws standard. So in order to create client code from the wsdl I was able to do either one of the following.
On windows (if you have the tool):
md YourServiceFolderName
WSDL2java -uri YourService.wsdl -ss -sd -ssi -g -d xmlbeans -o YourServiceFolderName
With Maven plugin, under your "plugins" tag (be sure to sort out the dependancies you'll need as well - not given here):
<plugin>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-codegen-plugin</artifactId>
<version>2.7.8</version>
<executions>
<execution>
<id>generate-sources</id>
<phase>generate-sources</phase>
<configuration>
<wsdlOptions>
<wsdlOption>
<wsdl>YourService?wsdl</wsdl>
<extraargs>
<extraarg>-databinding</extraarg>
<extraarg>xmlbeans</extraarg>
</extraargs>
</wsdlOption>
</configuration>
<goals>
<goal>wsdl2java</goal>
</goals>
</execution>
</executions>
</plugin>
This should give you all the java artefacts you need to get on with your service consumption. Hope this helps someone.