7

Modules jta and java.sql export package javax.transaction.xa to module dom4j

As you can see, both modules jta and java.sql export the same package, javax.transaction.xa. However, the package in jta has classes that I require that are not present in java.sql. I would simply not require the java.sql module, but I need java.sql.SQLException.

Is it possible to prevent java.sql from exporting javax.transaction.xa?

Jacob G.
  • 28,856
  • 5
  • 62
  • 116

2 Answers2

4

The JTA GitHub reads the following in confirmation to what @Alan already pointed out in a comment -

This standalone release of Java(TM) Java Transaction API (JTA), uses a Java Platform Module System "automatic" module name of java.transaction, to match the module name used in JDK 9. A future version will include full module metadata. Moreover javax.transaction.xa package is now owned by Java SE.

You can use the version with Maven(e.g) using :-

<dependency>
    <groupId>javax.transaction</groupId>
    <artifactId>javax.transaction-api</artifactId>
    <version>1.3</version>
</dependency>

Here is the release notes for JTA1.3MR.

Additionally the JEP 320: Remove the Java EE and CORBA Modules elaborates on the same -

... The javax.transaction.xa package supports XA transactions in JDBC. This "XA package" is co-located with JDBC in the java.sql module in Java SE 9. Because the java.sql module is not upgradeable, it is not possible for a standalone version of JTA to override the Java SE version of the XA package

and to further note for extensibility in your solution

...For ease of maintenance, the XA package in Java SE may be moved to a different non-upgradeable module in the future, but as an architectural matter it will remain in Java SE alongside JDBC for the long term...

and as planned

In early 2018, JTA 1.3 will be defined to consist of just the CORBA interop package; the JAR file will be updated accordingly.

Naman
  • 27,789
  • 26
  • 218
  • 353
  • 2
    I was already aware of this *fix*, but I only managed to get it working by removing `module-info.java` and adding the modules via the command line instead (Spring doesn't want to cooperate with the module path :P). Thanks though! – Jacob G. Jun 24 '18 at 14:11
  • 2
    With JDK 9 and JDK 10, if you are deploying JTA 1.3 as a module then you need to deploy it on the upgrade module path so that it overrides the java.transaction module in the run-time image. That complication does not exist in JDK 11 as the java.transaction is proposed to be dropped from Java SE 11. – Alan Bateman Jun 25 '18 at 06:02
-1

You could use javac -d -cp /PATHTOYOURFILE -d and -cp flags to compile only required directories and classpath. Classpath can also be comma seperated.

James Wong
  • 4,529
  • 4
  • 48
  • 65
mtn
  • 3
  • 4