APIs JAXB / JAX-WS / JAF / CORBA / JTA deprecated in JDK 9 and removed from JDK 11

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.x
  • OpenJDK 9
  • OpenJDK 11

Issue

APIs JAXB / JAX-WS / JAF / CORBA / JTA deprecated in JDK 9 and removed from JDK 11

Resolution

The JDK /Java SE removed the following Java Enterprise edition (JEE) API:

  • JAXB
  • JAX-WS
  • JAF
  • CORBA
  • JTA

As a consequence, applications running in JBoss EAP would have access to these APIs as they are JEE APIs and JBoss EAP is a JEE implementation.

If an application is failing to compile with JDK 11, because of missing classes, then the application needs to depend on the appropriate artifacts such as using the JBoss Maven Repository.

Managing Project Dependencies JBoss EAP Documentation

Root Cause

Source Content from openjdk.java.net is not included.JEP 320: Remove the Java EE and CORBA Modules

In Java SE 9, the Java SE modules that contain Java EE and CORBA technologies are annotated as deprecated for removal, indicating the intent to remove them in a future release:

java.xml.ws (JAX-WS, plus the related technologies SAAJ and Web Services Metadata)
java.xml.bind (JAXB)
java.activation (JAF)
java.xml.ws.annotation (Common Annotations)
java.corba (CORBA)
java.transaction (JTA)
Related modules in Java SE 9 are also deprecated for removal:

java.se.ee (Aggregator module for the six modules above)
jdk.xml.ws (Tools for JAX-WS)
jdk.xml.bind (Tools for JAXB)
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.