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. Regards Reto > -----Ursprüngliche Nachricht----- > Von: Alan Bateman [mailto:alan.bate...@oracle.com] > Gesendet: Dienstag, 16. Mai 2017 08:00 > An: Reto Merz; jigsaw-dev@openjdk.java.net > Betreff: Re: Java 9 EA 169 Webstart NoClassDefFoundError: > javax/xml/ws/Service > > On 15/05/2017 15:10, Reto Merz wrote: > > > Hello, > > > > It seems that Java 9 Webstart (still) does not add all modules to the > class/module path. > > Our Webstart app is signed, requests all-permision and works with the > latest Java 6, 7 and 8. > > > > With 9-ea+169 we get this error: > > > > java.lang.NoClassDefFoundError: javax/xml/ws/Service > > ... first 45 from cause > > Caused by: java.lang.ClassNotFoundException: javax.xml.ws.Service > > at jdk.deploy@9- > ea/com.sun.deploy.security.DeployURLClassLoader.findClass(Unknown > Source) > > : > > > > Is this a known bug or should this be reported via bugreport.java.com? > > > Java Web Start is aligned with the default policy for root modules in > JEP 261. This means that the EE modules aren't resolved by default. I > suspect this is what you need in the JNLP: > > <j2se version="9+" java-vm-args="--add-modules=java.xml.ws"/> > > -Alan
