AW: Java 9 EA 169 Webstart NoClassDefFoundError: javax/xml/ws/Service

[Reto Merz]

> So I think Java Web Start is right to align with the policy for
> applications launched on the command line.

The difference is that in case of Webstart the Java version is controlled by the user.
They are trained to install the latest Java version and keep it up-to-date.
All our customers download Java via java.com
They would not understand that they should stay with an old Java version until release X of software Y is available because they have never do that before.
We use Webstart over 10 years and it is the first time we see that Oracle will break compatibility between Java N and N+1 and Oracle is already aware about it.
The issue is easy to fix because only the Webstart launcher would be affected by the changes.
This changes would give Webstart app devs more time to migrate.

I think it is wrong to compare Webstart with a classic application
and Oracle should add all SE/EE modules by default and also enable --permit-illegal-access
by default in case ob Webstart.

Regards
Reto


> -----Ursprüngliche Nachricht-----
> Von: Alan Bateman [mailto:Alan.Bateman at oracle.com]
> Gesendet: Dienstag, 16. Mai 2017 12:15
> An: Reto Merz; jigsaw-dev at openjdk.java.net
> Betreff: Re: Java 9 EA 169 Webstart NoClassDefFoundError:
> javax/xml/ws/Service
> 
> On 16/05/2017 09:49, Reto Merz wrote:
> 
> > Thanks Alan.
> >
> > Wouldn't it make sense to add all modules by default in Java 9 in case of
> Webstart and print
> > a warning to the Webstart console the first time a future non-default
> module is accessed
> > with the message that the JNLP must be extended with a --add-
> modules=moduleXY in Java 10?
> >
> > So all the Webstart app devs would get more time to adjust the JNLP to
> support Java9/10.
> >
> The proposal in JSR 379 is java.xml.ws and the other modules that
> overlap with EE be deprecated (forRemoval=true) so that we can drop them
> from Java SE in a future release (hopefully 10 if the JSR for Java SE 10
> agrees).
> 
> So I think Java Web Start is right to align with the policy for
> applications launched on the command line.
> 
> -Alan.