1

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.

Anticrombie23
  • 25
  • 8
  • 1
    Did you try doing a mvn clean install? – robot_alien May 04 '17 at 15:06
  • Yep yep -- that's how I run it every time. The clean itself is successful, but the clean install fails.[INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 17.672s [INFO] Finished at: Thu May 04 10:16:02 CDT 2017 [INFO] Final Memory: 12M/21M – Anticrombie23 May 04 '17 at 15:16
  • are you pointing to the correct repository `${user.home}/.m2/repository` and also are the credentials correctly entered in your `settings.xml` file? – robot_alien May 04 '17 at 15:20
  • Yep yep -- it all builds proper previous to the upgrade to 1.7. I brought it in and built this, successfully, with the repository pulls occurring proper. It's not error'ing on downloading dependencies, it's flat out saying they don't exist on a maven build – Anticrombie23 May 04 '17 at 15:26
  • May be this can help you out: (Not exact issue but kinda pointer) http://stackoverflow.com/a/17251659/1004631 – robot_alien May 04 '17 at 15:31

1 Answers1

0

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.

Shailesh Pratapwar
  • 4,054
  • 3
  • 35
  • 46
  • Do you know the dependency by chance? I attempted to add the WAS 8.5 server as a dependency, but that seems to create further errors com.ibm.tools.target was 8.5.5 pom provided – Anticrombie23 May 04 '17 at 15:44
  • com.ibm.ws.webservices.thinclient_8.5.0 is the dependency which you need and which you generate from wsdl. So, first generate the thin client from wsdl, then install that thin client jar in local maven repo using install:install-file goal and then use that in your pom. – Shailesh Pratapwar May 04 '17 at 16:20