Please enable JavaScript.

Coggle requires JavaScript to display documents.

Java 9 new features (modules (is a uniquely named, reusable group of…

- - - - It’s recommended to give a Java module the same name as the name of the root Java package contained in the module, if possible.
      - A Java module follows the same naming rules as Java packages.
    - - A dependency is what is expressed by a requires directive.
      - There is also a requires static directive to indicate that a module is required at compile-time, but is optional at runtime.This is known as an optional dependency.
      - Finally, you can also use the transitive keyword to ensure that other modules reading your module also read that dependency, known as implied readability.
    - - A package can only be exported by a single Java module, otherwise, this will lead to a ResolutionException at runtime because a so-called split-package is created
      - The exported packages are declared in the module descriptor
      - No sub-packages of the exported package are exported.
    - - A Java module that wants to implement a service interface from another module must take the following steps:
        Require the other module, in this case com.continuum.service.
        Implement the service interface OurService with a Java class OurServiceImpl.
        Declare the service interface implementation using the provides <interface> with <implementation class> notation.
      - module com.continuum.implementation { requires com.continuum.service; provides com.continuum.service.OurService with com.continuum.service.OurServiceImpl }
    - - the opens keyword specifies the name of a package to be opened by the current module. For code in other modules, this grants access at run time (but not compile-time) to the public and protected types in the package
      - It’s also possible to open it up for only one or more modules using the opens … to keywords. It’s strongly advised not to use the open keyword to open up an entire module,