Deprecated Java EE Modules in JDK9

Heiko Wagner heiko.wagner at apis.de
Thu Apr 20 07:38:11 UTC 2017


Sorry for my ignotance, but I need some advice on how to properly write
a desktop app that uses JAX-WS to pull some data from a WS-I Service. 

I can understand why JAX-WS is deprecated and marked for removel to help
out the Java EE crwod to migrate their application servers to JDK9, but
I don't fully understand what the right thing would be to do in my
situation. Is the java.xml.ws module just "moved" to Java EE or is it
completely removed and replaced with a module that has a new name? 

In the first case I ussume it would be the right thing to decare a
dependency on java.xml.ws and rely on the presence of the module in Java
SE 9 and ship a module implementing JAX-WS in Java SE 10 along my
application. I assume jlink would help me out to get a appropriate
runtime image in both cases. This would be just like the Java Mail API
case, where there is nothing wrong with using it in th Java SE context,
when you make sure you supply a implementation with your app and rely on
the platform to provide a implementation in the Java EE context. 

In the latter case, is there already a proper new module name or module
alias I can depend on in my application? 

Thanks for the help, 

Heiko

-- 
Heiko Wagner - APIS Informationstechnologien GmbH
Gewerbepark A 13, 93086 Wörth a.d. Donau, Deutschland
Web: http://www.apis.de
E-Mail: heiko.wagner at apis.de
Tel.: +49 (0) 9482 - 9415 - 0
Fax: +49 (0) 9482 - 9415 - 25
Sitz der GmbH: Wörth/Donau, Amtsgericht Regensburg (HRB 6684)
Geschäftsführer: Julia Anna Dietz, Jürgen Eilers, Peter Rosenbeck


More information about the core-libs-dev mailing list