The java.xml.ws module was removed from JDK 11 (Custom Implementation)

The java.xml.ws module was removed from JDK 11. The java.xml.ws module included the following packages:

This rule flags applications that use any of the packages listed earlier and package their own JAX-WS implementation. Previously, a JAX-WS implementation might have relied on the APIs listed earlier to be accessible from the JDK. However, starting JDK 11, those APIs are no longer accessible.

Applications packaging their own JAX-WS implementation will need to update their packaged JAX-WS implementation with a Java 11 compatible version that packages the removed APIs along with the implementation.

Another solution is to switch to the Liberty default JAX-WS implementation. This can be done by adding the jaxws-2.2 feature to the Liberty server.xml configuration file. In addition, any JAX-WS implementations previously packaged in the application must be removed to avoid class-loading issues.

The wsgen and the wsimport tools were removed from JDK 11 as well. These tools are available in the Liberty bin/jaxws directory of the Liberty installation.

The automated fix provided by the Java SE 11 general rule updates the javax.xml.ws module in the application's dependencies to ensure that it is not packaged in the application. In most cases, this fix will prevent class loading issues. Copy the custom configuration to your application build file to enable the fix automation.

For more information on JDK 11 changes, see Removal of Java EE and CORBA Modules.