Error during Maven Build when generating WSDL client: “ error: package com.ibm.ws.webservices.engine.encoding does not exist”

Question

I am upgrading a maven (3.3.9) project with multiple modules from java 1.6 to 1.7 and I am seeing the following errors upon regeneration of the WSDL client (jax-RPC).

When I generated the WSDL client via the Web Services --> Generate Client tool, it creates a referenced library of the thin client "com.ibm.ws.webservices.thinclient_8.5.0.jar" where all these dependencies lie. None of my generated classes have red compilation errors (before compile, it can find all these dependencies in the same package...)

...but upon maven build, it cannot seem to find these packages. My webserver is pointing towards 1.7, my IDE (which is RSA..) is 1.7. Pom dependencies are 1.7, deleted the previous generated client and regenerated via 1.7. What gives?

Errors:

error:  package com.ibm.ws.webservices.engine.encoding.ser  does    not exist
error:  package com.ibm.ws.webservices.engine.description   does    not exist
error:  package com.ibm.ws.webservices.engine.encoding  does    not exist
error:  package com.ibm.ws.webservices.multiprotocol    does    not exist

Pic 1

Note that the thin client is in the build path. I've attempted to delete/re-add it to the build path (refresh...regenerated client......etc) to no avail

Pic2

Note that my classes contain no red. It seems to find the path here, but not in maven.

Answer 1

I can see in the image that client is added in classpath through build path option. This is not right.

If you want the client to get referred in your classpath in maven build, you need to first publish that as a maven dependency and then add that dependency in pom.