Really useful to get the context and basic concepts. Need to find another video though that goes a bit more in to the syntax / directives though before I feel practically useful
The presentation was going smooth until the "open" keyword appeared... What kind of errors happen when a framework tries to "reflectively" access application code not "opened" via the module declaration file?
Missing a mention how to specify modules in MANIFEST.MF so I can run the .jar (hint: Import-Package: OSGi header seems to be needed in addition to the Class-Path: and Main-Class: to enable modules in additional JARs)
is it me or the modularity in jdk 9 is all about profiling the jdk(including deprecating legacy techs like cobra) and limiting the public class access from outside the jars?
Based on module descriptors you also can create custom runtime images with jlink. The resulting runtime images are generally smaller than monolithic JREs from Java 8 or older. Which means they can be used on a bigger set of devices.
Okay, this is the first talk about module system that actually makes sense to me. Great job by the speaker.
a very useful overview of the module system, wish I had viewed this sooner
Really useful to get the context and basic concepts. Need to find another video though that goes a bit more in to the syntax / directives though before I feel practically useful
You didn't explain the difference between the dashed lines and the solid lines in the "java.se" module graph :)
each and every sentence of yours have some meaning. It's like new knowledge to me.
The presentation was going smooth until the "open" keyword appeared... What kind of errors happen when a framework tries to "reflectively" access application code not "opened" via the module declaration file?
Just "cannot access " . Easy fix.
Missing a mention how to specify modules in MANIFEST.MF so I can run the .jar (hint: Import-Package: OSGi header seems to be needed in addition to the Class-Path: and Main-Class: to enable modules in additional JARs)
Great talk, enlightening indeed.
I would not be surprised a library comes in to auto create modules export imports.
is it me or the modularity in jdk 9 is all about profiling the jdk(including deprecating legacy techs like cobra) and limiting the public class access from outside the jars?
Based on module descriptors you also can create custom runtime images with jlink. The resulting runtime images are generally smaller than monolithic JREs from Java 8 or older. Which means they can be used on a bigger set of devices.
Very nice notes
Hi, thanks, I will switch to c#.
Ha ha, good luck with that.