3

Quarkus 3 has introduced Jakarta EE 10 that need to replace all the javax.* package with jakarta. package.

In our application we set these system properties at startup:

-Djavax.net.ssl.trustStore=...
-Djavax.net.ssl.trustStorePassword=...

Do we need to change it in jakarta.net.ssl.... ?

Thanks

BalusC
  • 1,082,665
  • 372
  • 3,610
  • 3,555
Sh4iDo
  • 33
  • 3
  • 1
    It does not replace all the `javax.*` packages. Affected packages are `javax.xml.bind`, `javax.servlet` and `javax.xml.ws` (perhaps some others), but AFAIK not `javax.net`. – f1sh May 15 '23 at 15:55
  • 4
    Does `javax.net.ssl.*` come from Jakarta EE? No, therefore you don't need to (and must not, in fact) change those properties. – Ladicek May 15 '23 at 16:02

1 Answers1

4

As Commented…

For any javax package, ask yourself if that class is from one of the Jakarta EE libraries? When you look up the latest Javadoc, does that page reside at the Jakarta EE web site?

If so, change the package name to that which is documented. If not, leave the javax package as-is.

Java still has many packages in the javax namespace. This x naming is a leftover from older development practices during the early Sun Microsystems days of Java’s history.

The package javax.net.ssl is still a part of the current Java release, Java 20. Not in Jakarta EE.

The first versions of Jakarta EE did use the javax.* package naming, as part of a transition when Oracle Corp handed over Java EE to the Eclipse Foundation. My Answer here assumes you have moved on to the later versions of Jakarta EE that now use jakarta.* packages.

Basil Bourque
  • 303,325
  • 100
  • 852
  • 1,154