On 05/04/16 11:17, Alan Bateman wrote: . . . > We recently updated JEP 261 proposing that "java.se" be the only java.* > root module that is resolved when compiling code in the unnamed module > or at runtime when the main class is loaded from the class path [1]. On > the surface then it will "appear" to developers that the JDK does not > have the EE components but from everything we've seen so far, then those > EE components are usually on the class path anyway.
Ah ok, so this means that the problem has been punted to the other foot i.e. the only apps affected will be those which i) don't have an EE jar on their classpath and ii) require the (partial) stub implementations provided by Java SE. That sounds much better since such a configuration is of almost no use to anyone and hence is very unlikely to arise. regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (US), Michael O'Neill (Ireland), Paul Argiry (US)
