One thing I notice is that your application (assuming that it’s packaged in tech.flexpoint.dashman) does not seem to be opened up to Spring in any way, which will surely result in failed class loading/illegal access. I would expect to see something like this in module-info.java (depending on your Spring dependencies): opens tech.flexpoint.dashman to spring.core, spring.beans, … Read more
Very simplified answer After Jigsaw, public will be public only within the JAR scope. To see the class outside the JAR it must be exported. Java will force modularization because any inter module interaction will have to be specified in the module-info file. For example, if you produce a WAR it will remain almost unchanged … Read more
I first answer your actual question (“What is an automatic module?”), but I also explain what they are there for. It is hard to understand why automatic modules behave the way they do without that information. What is an automatic module? The module system creates a module from every JAR it finds on the module … Read more
Jigsaw and OSGi are trying to solve the same problem: how to allow coarser-grained modules to interact while shielding their internals. In Jigsaw’s case, the coarser-grained modules include Java classes, packages, and their dependencies. Here’s an example: Spring and Hibernate. Both have a dependency on a 3rd party JAR CGLIB, but they use different, incompatible … Read more
The purpose of JMODs are not well documented and existing documentation is rather sparse. Here is an in-depth explanation of system, from my understanding. Parts of this answer are rather long, verbose, partially redundant, and a tough read. Constructive, structural, or grammatical edits are more than welcome to improve readability for future readers. Short(er) Answer … Read more
With –add-exports the package is exported, meaning all public types and members therein are accessible at compile and run time. With –add-opens the package is opened, meaning all types and members (not only public ones!) therein are accessible at run time. So the main difference at run time is that –add-opens allows “deep reflection”, meaning … Read more
First understand that Jigsaw’s primary use case is to modularise the JRE itself. As a secondary goal it will offer a module system that may be used by other Java libraries and applications. My position is that something like Jigsaw is probably necessary for the JRE only, but that it will create far more problems … Read more
No. There is no need to switch to modules. There has never been a need to switch to modules. Java 9 and later releases support traditional JAR files on the traditional class path, via the concept of the unnamed module, and will likely do so until the heat death of the universe. Whether to start … Read more
The exception is caused by the Java Platform Module System that was introduced in Java 9, particularly its implementation of strong encapsulation. It only allows access under certain conditions, the most prominent ones are: the type has to be public the owning package has to be exported The same limitations are true for reflection, which … Read more
Apart from an understanding of the accesses amongst modules and their respective packages. I believe the crux of it lies in the Module System#Relaxed-strong-encapsulation and I would just cherry-pick the relevant parts of it to try and answer the question. What defines an illegal reflective access and what circumstances trigger the warning? To aid in … Read more