Downloaded 193 times
Uploaded byStephen Colebourne
Java SE 9 modules (JPMS) - an introduction
The document introduces Java SE 9 modules, detailing the Java Platform Module System (JPMS) and its significance for enhancing security, maintainability, and performance. It explains the new module structure, including module dependencies and encapsulation principles, while also addressing various requirements and migration challenges. The summary emphasizes the non-trivial nature of transitioning to modules, cautioning users about reflecting on JDK internals and the need for command line flags due to certain restrictions.
In this document
Powered by AI
Introduces Java SE 9 modules and Project Jigsaw, which aims to enhance Java's modularity, security, and performance.
Discusses the goals of modularization, the large size of the JDK, and introduces the new modular structure in Java SE 9.
Lists six deprecated modules in Java SE 9 and provides an overview of the modular structure using a module graph.
Mentions JEPs for modular JDK, the concept of classpaths, and introduces ClassLoaders for loading classes.
Details on reliable configuration, multi-package applications, and the necessity for strong encapsulation in modules.
Explains what constitutes a module, and contrasts code usage without and with modules, emphasizing encapsulation.
Covers the module metadata, dependency management, and the structure of module graphs ensuring integrity and accessibility.
Discusses service access implementation in modules and how packages can be hidden or exported for access control.
How reflection allows access to module internals and outlines the stricter access rules for reflection in Java SE 9.
Migration challenges from older Java versions to Java SE 9, including use of classpath and handling of automatic modules.
Discusses ongoing concerns around module naming conventions, the role of Maven in module dependency, and contrasts with OSGi.
Summarizes key points on Java modularization, reflection limitations, and encourages testing Java SE 9.
Java SE 9 modules (JPMS) - an introduction
- 1. Java SE 9modules An introduction Stephen Colebourne - @jodastephen Engineering Lead, OpenGamma April 2017
- 2. Topics ● Introduction ● Issuesand Requirements ● Module basics ● Module info ● Calling code ● Reflection ● Migration ● Summary
- 3. Modules - ProjectJigsaw https://www.flickr.com/photos/distillated/4019168958/
- 4. Modules ● JPMS -Java Platform Module System ● Main feature of Java SE 9 ● Developed as Project Jigsaw ● Originally targetted at Java SE 7 ○ first JSR was in 2005, 12 years ago ● Still incomplete even though very late in 9 development ● Planned release date of July 27th 2017 ○ just over 100 days!
- 5. Goals ● Scale JavaSE to small devices ● Improve security and maintainability ● Better application performance ● Easier to construct & maintain libraries/applications
- 6. JDK too big ●Java SE 8 has 210 packages ● Many are not needed by all applications ○ CORBA, Swing, AWT, XML ● Need to split JDK into smaller units, aka modules
- 7. Modularised JDK ● 24modules in Java SE 9 ● Every application gets java.base ○ packages java.lang, io, math, net, nio, util, security, text, time ● Separate modules for ○ logging ○ sql ○ xml ○ desktop (AWT/Swing) ○ prefs ○ rmi
- 8.
- 9. Deprecated modules ● 6modules are deprecated for removal ○ java.activation ○ java.corba ○ java.transaction ○ java.xml.bind ○ java.xml.ws ○ java.xml.ws.annotation ● Mass deletion from the JDK! ● Not in Java 9 by default!
- 10. Module graph Out ofdate, but gives general idea!
- 11. Official process ● JEP ○200: The Modular JDK ○ 201: Modular Source Code ○ 220: Modular Run-Time Images ○ 260: Encapsulate Most Internal APIs ○ 261: Module System ○ 282: jlink: The Java Linker ● JSR ○ JSR 376: Java Platform Module System
- 12.
- 13. Classpath ● Classes areloaded on demand ● Classpath specifies where to find bytecode ○ java -classpath lib/aaa.jar;lib/bbb.jar ● Boot classpath loads the JDK - rt.jar ● Extension classpath loads standard extensions ● User classpath loads user code ○ Defaults to current directory ○ Typically specified using -classpath or -cp ○ Can be jar files or directories
- 14. ClassLoader ● Every classis loaded by one class loader ● Most class loaders delegate to a parent ● One class loader for each of the three classpaths
- 15. ClassLoader ● Get classfrom ClassLoader ● Look in parent first ● Searching can be slow Application ClassLoader Extension ClassLoader Boot ClassLoader MyFoo.class String.class
- 16. Questions ● What happensif class not found on classpath? ● What happens if class appears twice on classpath? ● Does order matter in the classpath? ● What happens if same class is loaded by two different class loaders?
- 17. Classpath Once on theclasspath ● A can call B and vice versa ● A can call C and vice versa ● B can call C and vice versa Jar files meaningless A.class B.class C.class
- 18. Requirement 1 ● Reliableconfiguration ○ replace classpath with graph of dependencies ○ know what is needed to run the application ● When application starts ○ check everything present ○ check no duplicates ○ potentially perform lookup optimisations
- 19. Packages are allwe have ● Applications & libraries need to be multi-package ● More things public than desirable ● Often see packages with "impl" or "internal" in name ● Clear sign of a missing language feature
- 20. Example ● Jackson JSON/XMLserialization ○ com.fasterxml.jackson.databind ○ com.fasterxml.jackson.databind.deser ○ com.fasterxml.jackson.databind.deser.impl ○ com.fasterxml.jackson.databind.jsontype ○ com.fasterxml.jackson.databind.jsontype.impl ○ com.fasterxml.jackson.databind.ser ○ com.fasterxml.jackson.databind.ser.impl ○ com.fasterxml.jackson.databind.ser.std ○ com.fasterxml.jackson.databind.type ○ com.fasterxml.jackson.databind.util
- 21. Example ● You werenever supposed to use code in: ○ sun.misc.* ○ jdk.internal.* ○ etc.
- 22. Requirement 2 ● Strongencapsulation ○ module can declare an API to other modules ○ packages not on the API are hidden ● Use this to enhance security ○ non-public elements cannot be accessed
- 23.
- 24. What is amodule? ● Named ● Set of packages (classes/interfaces) ● Module metadata (module-info.class) ● Typically packaged as a .jar file ● Enforced by the JVM ○ JVM understands classes, interfaces, packages, and now modules
- 25.
- 26. Without modules opengamma-util.jar com.opengamma.util com.opengamma.util.math com.opengamma.util.impl If this.jar file is on classpath, any public type/method from any package can be used
- 27.
- 28. With modules opengamma.util com.opengamma.util com.opengamma.util.math module-info.class com.opengamma.util.impl module opengamma.util{ exports com.opengamma.util; exports com.opengamma.util.math; }
- 29. With modules opengamma.util com.opengamma.util com.opengamma.util.math module-info.class com.opengamma.util.impl module opengamma.util{ exports com.opengamma.util; exports com.opengamma.util.math; } Non-exported packages cannot be seen outside the module
- 30. How is itenforced ● Modulepath as well as classpath ● Jar must have a module-info.class ● Module rules enforced when jar on modulepath ● Rules not enforced when jar on classpath ● JVM determines and validates module graph ○ checked at startup ○ advanced use cases can alter parts of the graph at runtime
- 31. Modular JDK ● JDKmodules always run in module mode ● Classpath sees whole JDK ● Modules specify which JDK modules they need ● Changes JDK structure ○ no more rt.jar ○ packaged as .jmod files ○ no more boot classpath ○ no more extension classpath
- 32.
- 33. Creating a module ●Two basic questions ● What modules does it depend on? ○ depends on java.base by default ● What packages does it export? ○ nothing exported by default
- 34. Module metadata module opengamma.util{ // other modules this module depends on requires google.guava; requires joda.beans; // packages this module exports to other modules exports com.opengamma.util; }
- 35.
- 36. Dependencies ● org.joda.beans dependson org.joda.convert module joda.beans { // other modules this module depends on requires joda.convert; // packages this module exports to other modules exports org.joda.beans; }
- 37.
- 38. Transitive dependencies ● But,Joda-Beans exposes types from Joda-Convert ● Express concept using "requires transitive" module joda.beans { // other modules this module depends on requires transitive joda.convert; // packages this module exports to other modules exports org.joda.beans; }
- 39.
- 40. Optional dependencies ● Butorg.joda.convert has optional dependency ● If Guava exists at runtime, Joda-Convert adapts module joda.convert { // other modules this module depends on requires static google.guava; // packages this module exports to other modules exports org.joda.convert; }
- 41.
- 42. Checks ● Module pathcontains a set of modules ● One module is the root ● Other modules are resolved to form a graph ● System ensures all necessary modules are available ● System ensures no module found twice ● System ensures same package not in two modules ● System ensures graph has no cycles
- 43. Modulepath ● A coherentmodulepath is your problem ● Versions, and their selection, not part of JPMS ○ do not put version in module name ● Typically will be done by Maven or Gradle ● Just like the classpath is assembled today Open to debate as to how much this achieves the reliable configuration requirement
- 44. Services ● SQL drivers,XML parsers, etc. ● Can be specified in module-info ● Module that contains the service implementation: ○ provides com.foo.XmlParser with com.foo.MyXmlParser ● Module that uses the service: ○ uses com.foo.XmlParser
- 45. Calling code inanother module https://www.flickr.com/photos/distillated/4019168958/
- 46. Hiding packages ● Giventwo packages ○ org.joda.beans ○ org.joda.beans.impl ● It is possible to completely hide the internal package ○ export org.joda.beans ○ do not export org.joda.beans.impl
- 47.
- 48. Access ● Only exportedpackages are visible to other modules ● All other packages are private to the module ● "public" no longer means "public" ● Other modules can only see and use code if: ○ public ○ package is exported by target module ○ package is readable from this module ● Combination referred to as "accessibility"
- 49. Access opengamma.util joda.beansgoogle.guava org.joda.beans org.joda.beans.impl com.opengamma.util com.google.guava joda.convert org.joda.convert JVM only allowpublic method to be used if readable (downward arrows) and package is exported (dark blue)
- 50.
- 51. Targetted exports ● Packagecan be exported to a specific module: ○ exports org.joda.beans.impl to joda.special ● Effectively a kind of "friend" access ● Usually suggests poor package structure
- 52. Lockdown ● Ability tolockdown packages is powerful ● However, it only works on the modulepath ● Paranoid code could refuse to work on classpath
- 53.
- 54. Reflection ● Powerful mechanismto access code ● Access package and private scope ○ use setAccessible() ● Vital to frameworks, particularly for bean creation
- 55. Reflection in 9 ●Can access public elements of exported packages ● Cannot access package/private types/members ● Cannot access non-exported packages ● Much stronger barrier than previously ○ setAccessible() does not help
- 56. Reflection module joda.beans { //other modules this module depends on requires transitive joda.convert; // packages this module exports to other modules exports org.joda.beans; opens org.joda.beans.impl; } ● Modules can selectively allow reflection ● Use "opens", also enables setAccessible()
- 57. Reflection open module joda.beans{ // other modules this module depends on requires transitive joda.convert; // packages this module exports to other modules exports org.joda.beans; } ● Modules can open all packages if desired
- 58. Reflection on theJDK ● JDK is fully modular ● JDK does not have "open" packages ● Thus, cannot reflect on non-public JDK ● Big security boost ● Breaks many existing libraries ● Can use command line flags to force JDK open ○ useful in the short term until the libraries are fixed
- 59. Reflecting on modules ●Module information is available to reflection ○ new Module class and getModule() method ○ allows the JVM module graph to be accessed ● See also the ModuleLayer concept ○ intended for advanced use cases
- 60.
- 61. Migration ● Take existingcode and migrate it ● New rules make this tricky in some cases ○ eg. SLF4J will need major rework
- 62. Use classpath ● Mostexisting code will run on Java SE 9 classpath ● If it uses internal JDK API, fix or use a flag: ○ --add-exports, --add-opens, --permit-illegal-access ● If it uses removed JDK module, fix or use a flag: ○ --add-modules java.xml.bind
- 63. Migration ● Classpath mappedto the "unnamed module" ● Unnamed module reads all other modules ● Cannot access non-exported packages ● Most existing code should run fine in unnamed module ● Named modules cannot access the unnamed module
- 64.
- 65.
- 66.
- 67. Migration ● Additional "automaticmodule" concept ● Jars without module-info on modulepath ● Exports all packages in jar ● Reads the all other modules, including unnamed ● Used to handle libraries that have not yet modularized WARNING! There are serious concerns about using automatic modules in open source projects. Maven Central will likely ban projects that depend on an automatic module.
- 68.
- 69. Module naming ● Noagreement on module names yet ● Please wait until clear convention agreed ● Might be like package names ○ org.joda.convert ● Might be shorter, but this will lead to clashes ○ joda.convert WARNING! There are still serious naming concerns from the open source community.
- 70. Modules and Maven ●Maven creates a tree of dependencies ● Often enforced by IDEs ● Not enforced at runtime ● Likely that each pom.xml will be a JPMS module ○ unclear whether module-info.java will be hand written ○ or derived from pom.xml (I suspect hand written, with IDE help) ● JPMS does not handle versions ● JPMS does not select jar files from Maven repo
- 71. Modules and OSGi ●OSGi is a module system based on the classpath ● It still works fine on the classpath ● Dynamic loading, lifecycle etc. not part of JPMS ● JPMS is not ClassLoader based ○ all classes in a module have the same ClassLoader ○ same ClassLoader may be used by many modules
- 72.
- 73. Summary ● Modules area new JVM concept, exposed in Java ○ don't confuse with Maven, OSGi, JBoss modules ● Moving to modules is non-trivial ○ no reflection on JDK internals without command line flag ○ parts of the JDK removed by default and need command line flag ● Reflection is being restricted ○ command line flags allow this to be broken ● Don't rush to modularize! ○ wait for open source to do so first
- 74. Summary ● Project Jigsaw: ○http://openjdk.java.net/projects/jigsaw/ ○ Time to test Java SE 9 for bugs is NOW! ● Stephen Colebourne: ○ @jodastephen - feedback & questions ○ http://blog.joda.org ● OpenGamma ○ Strata - open source market risk analytics ○ Cloud-based metrics for derivatives trading and clearing