Book Image

Modular Programming in Java 9

By : Koushik Srinivas Kothagal
Book Image

Modular Programming in Java 9

By: Koushik Srinivas Kothagal

Overview of this book

The Java 9 module system is an important addition to the language that affects the way we design, write, and organize code and libraries in Java. It provides a new way to achieve maintainable code by the encapsulation of Java types, as well as a way to write better libraries that have clear interfaces. Effectively using the module system requires an understanding of how modules work and what the best practices of creating modules are. This book will give you step-by-step instructions to create new modules as well as migrate code from earlier versions of Java to the Java 9 module system. You'll be working on a fully modular sample application and add features to it as you learn about Java modules. You'll learn how to create module definitions, setup inter-module dependencies, and use the built-in modules from the modular JDK. You will also learn about module resolution and how to use jlink to generate custom runtime images. We will end our journey by taking a look at the road ahead. You will learn some powerful best practices that will help you as you start building modular applications. You will also learn how to upgrade an existing Java 8 codebase to Java 9, handle issues with libraries, and how to test Java 9 applications.
Table of Contents (19 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Readability


Readability is an important concept in modularity and it describes how modules work with each other. We've been using module dependencies to have one module require another module and use its APIs. Whenever a module depends on another module, the first module is said to read the second module. Also, the second module is said to be readable by the first. When a module reads another module, it has access to the types exported by the second module. In other words, the readability relationship between two modules is the arrow in the module graph that we've seen so far.

For example, in the address book viewer application, the module packt.addressbook reads packt.sortutil, packt.contact, and java.logging. That's because it requires those modules in the module descriptor.

Consider an example. The following diagram shows the relationships between three modules A, B, and C:

Module A requires module B. So, module Areadsmodule B. Module B is readable by module A. Module C also readsmodule...