The ideal way to resolve this would be to reporting this to the maintainers of org.python.core.PySystemState and asking them to fix such reflective access going forward. If the default mode permits illegal reflective access, however, then it’s essential to make that known so that people aren’t surprised when this is no longer the default mode … Read more
You can definitely take a look at javaee/glassfish-corba. The documented home page reads – The GlassFish ORB complies with the CORBA 2.3.1 specification, and with the CORBA 3.0 specifications for the Interoperable Name Service and Portable Interceptors. It includes both IDL and RMI-IIOP support. The GlassFish ORB has an open, extensible architecture that supports flexible … Read more
The module system does not distinguish between production code and test code, so if you choose to modularize test code, the prod.module and the test.module cannot share the same package com.acme.project, as described in the specs: Non-interference — The Java compiler, virtual machine, and run-time system must ensure that modules that contain packages of the … Read more
In JDK 9+, add the following option to the JVM to disable the warning from Spring’s use of CGLIB: –add-opens java.base/java.lang=ALL-UNNAMED for example: java –add-opens java.base/java.lang=ALL-UNNAMED -jar target/*.jar No need to report it; it’s a known Spring bug. This happens because the new JDK 9 module system detected an illegal access that will be disallowed … 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
Readability recap If module bar requires module drink, then the module system… enforces the presence of drink (called reliable configuration) allows bar to read drink (called readability) allows code in bar to access public classes in exported packages in drink (called accessibility) Exactly the same happens if bar requires transitive drink – drink must be … Read more
I had a similar case, and (as mentioned by @Holger in the comment) the module info in the message is simply misleading – this is an actual case of trying to cast something to something that doesn’t match it. In your case, ClientImpl simply is not a subtype of XigniteCurrenciesSoap.
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
Instead of using the deprecated Java EE modules, use the following artifacts. JAF (java.activation) JavaBeans Activation Framework (now Jakarta Activation) is a standalone technology (available on Maven Central): <dependency> <groupId>com.sun.activation</groupId> <artifactId>jakarta.activation</artifactId> <version>1.2.2</version> </dependency> (Source) CORBA (java.corba) From JEP 320: There will not be a standalone version of CORBA unless third parties take over maintenance of … Read more