-
CSR
-
Resolution: Approved
-
P3
-
None
-
source, binary
-
minimal
-
There should be no compatibility issues with this change. Any module that `requires java.sql` will continue to have access to the public classes in the javax.transaction.xa package at both compile-time and run-time.
-
Java API, Other
-
SE
Summary
JSR 907 1.3 MR indicated that the javax.transaction.xa package will be subsumed by Java SE. As part of that effort, we will need to create a new module java.transaction.xa.
Problem
javax.transaction.xa should be provided in its own module now that it has been subsumed by Java SE.
Solution
Remove javax.transaction.xa from the java.sql module and create the java.transaction.xa module. The java.sql module will still require use of the new module but it will make it easier for other technologies who may desire to use the javax.transaction.xa package.
Specification
The changes may be seen at http://cr.openjdk.java.net/~lancea/8197533/webrev.00/index.html and the webrev is also attached.
- csr of
-
JDK-8197533 Split java.sql to create module java.transaction.xa
-
- Resolved
-
- relates to
-
JDK-8198861 13.3: Discuss binary compatibility of splitting a module
-
- Open
-