We are upgrading from Windchill PDMLink 12.0.2.17 ro 13.0.2.0 and during the compilation of our Java customizations we get these errors:com.thoughtworks.xstream does not existXStream library dependencies removed in Windchill 12.1+See: https://www.ptc.com/en/support/article/CS386935 javax.ws.rs does not exist:Running: windchill wt.util.jmx.Which javax/ws/rs/coreWC12 - URL: jar:file:/has/fs01/opt/ptc/windchill/codebase/WEB-INF/lib/wc3rdpartylibs.jar!/javax/ws/rs/coreWC13 - Resource not foundjavax.servlet does not exist:Running: windchill wt.util.jmx.Which javax/servletWC12 - URL: jar:file:/has/fs01/opt/ptc/windchill/codebase/WEB-INF/lib/ie3rdpartylibs.jar!/javax/servlet/andURL: jar:file:/has/fs01/opt/ptc/windchill/lib/servlet.jar!/javax/servletWC13 - Resource not foundHas anyone else stumbled upon this and was able to fix it?

12-Amethyst

Solved

Customizations using com.thoughtworks.xstream, javax.ws.rs and javax.servlet

We are upgrading from Windchill PDMLink 12.0.2.17 ro 13.0.2.0 and during the compilation of our Java customizations we get these errors:

com.thoughtworks.xstream does not exist

XStream library dependencies removed in Windchill 12.1+

javax.ws.rs does not exist:

Running: windchill wt.util.jmx.Which javax/ws/rs/core

WC12 - URL: jar:file:/has/fs01/opt/ptc/windchill/codebase/WEB-INF/lib/wc3rdpartylibs.jar!/javax/ws/rs/core
WC13 - Resource not found

javax.servlet does not exist:
Running: windchill wt.util.jmx.Which javax/servlet

WC12 - URL: jar:file:/has/fs01/opt/ptc/windchill/codebase/WEB-INF/lib/ie3rdpartylibs.jar!/javax/servlet/
and
URL: jar:file:/has/fs01/opt/ptc/windchill/lib/servlet.jar!/javax/servlet
WC13 - Resource not found

Has anyone else stumbled upon this and was able to fix it?

Best answer by HelesicPetr

Hi @ocorten-2

Yes,

take the old library from the old system separate the classes that are needed by your app from there and add it to new system.

I did it many times if some methods classes where removed from the system but they were useful for me.

PetrH

Answer

22-Sapphire II

Hi @ocorten-2

Yes,

take the old library from the old system separate the classes that are needed by your app from there and add it to new system.

I did it many times if some methods classes where removed from the system but they were useful for me.

PetrH

Author

12-Amethyst

Thanks a lot. Sounds like a quick (and dirty) solution.
It will give us time to rewrite the code to use other libraries.

22-Sapphire II

Hi @ocorten-2

The clear way is "do not use it" 😄 I know it is also wrong way 😄

PetrH