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

2017-05-19 Thread Andrew Guibert
; From: Michael Rasmussen <michael.rasmus...@zeroturnaround.com> > To: Reto Merz <reto.m...@abacus.ch> > Cc: jigsaw-dev <jigsaw-dev@openjdk.java.net> > Date: 05/17/2017 03:13 AM > Subject: Re: AW: Java 9 EA 169 Webstart NoClassDefFoundError: javax/ > xml/ws/Service

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

2017-05-17 Thread Michael Rasmussen
On 16 May 2017 at 16:52, Reto Merz wrote: > They need weeks to plan and test an upcoming server-side > software update before they can install it on the production system. > Java 9 will be released on 2017/07/27, so we are under high business pressur. Assuming Java 9 follows

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

2017-05-16 Thread Reto Merz
First, I want to say thanks for your help in this and the previous threads. > The JNLP fragment in my first mail can be used to resolve java.xml.ws > for JNLP applications that depend on the JAX-WS version included in the > JRE. It's predicated on the version of the runtime so you should be able

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

2017-05-16 Thread Alan Bateman
On 16/05/2017 12:26, Reto Merz wrote: 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

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

2017-05-16 Thread Reto Merz
.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

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

2017-05-16 Thread Alan Bateman
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

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

2017-05-16 Thread Reto Merz
: 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, r

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

2017-05-16 Thread Alan Bateman
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 9 EA 169 Webstart NoClassDefFoundError: javax/xml/ws/Service

2017-05-15 Thread Reto Merz
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