Modular Programming in Java 9

Handling non-standard access

Wait! There's a catch! The unnamed module reads all Java platform modules and because of that, I mentioned it mimics the free-for-all behavior of the pre-Java 9 platform. But that's not exactly true. Pre-Java 9, the entire platform, and all the classes in it were accessible to your application code. With Java 9 platform modularization, there are several internal types in platform modules that are not exported, thus making them encapsulated. It's a good thing that the unnamed module automatically reads all platform modules by default, but is that enough? Not really, because it just enables the code in the classpath to access only the types exported from the modules. But what if your legacy code uses a type that ...