JDK-8047774 : Audit JAXB and scope out API/other changes that might be needed to work with modules
  • Type: Task
  • Component: xml
  • Sub-Component: jaxb
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-06-22
  • Updated: 2016-01-06
  • Resolved: 2015-06-26
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Fixed
Related Reports
Relates :  
JDK-8129946 - JAXB tools - exporting generated java types
Relates :  
JDK-8080502 - Update JAXB and JAX-WS to work with resource encapsulation
Relates :  
JDK-8072839 - JAX-B Plugability Layer: using java.util.ServiceLoader
Description
This task is submitted to track auditing of JAXB with a view to scoping out what API and other changes (if any) are required for JAXB to work with modules in Java SE 9 / JDK 9. It is important to understand if API changes will be required as JAXB is tied to a standalone JSR (JSR-222) and so might require JCP activity to update.
Comments
There are some issues identified (see linked items) + we are expecting some class visibility/accessibility issues to be solved by Module::addReads(); Closing this task as done.
26-06-2015
To have complete picture, all the unit tests must be transformed to get rid off all the tools - mvn, ant, junit etc. Currently known issues: 1) using service loader - CCC 8072839 (JAX-B) in process - in JAX-B and SAAJ java.util.ServiceLoader can't be used without introducing new interface/class and changing the name being looked for 2) property file configuration in implementation discovery algorithms ( JDK-8049380, JDK-8049381) 3) requirement to export java types (generated, but not only) from client module because of using reflection on those - after transforming unit tests we'll have more complete picture what must be exported 4) changing jax-b tools to generate with java types also necessary exports for module-info.java / or complete module-info.java (?) - not sure if we need it - user could do it by himself, but it is "nice to have".
26-06-2015
Miran - would it be possible to write in an updated status? It may be that we can close this issue and create issues for follow-on updates (like the MR for the JSR and any javadoc updates that are needed).
25-06-2015