2

I have a JPMS framework that dynamically creates JPMS layers and add modules to them. After some tests it seems to me that --add-opens JVM parameter works only for the boot layer, I mean the layer that is created when application starts.

So, the question - does --add-opens work for dynamically created layers in JPMS?

Concrete example 

--add-opens java.base/java.lang=weld.servlet.shaded

will java.base/java.lang be opened to weld.servlet.shaded if weld.servlet.shaded is in dynamically created layer?

Daniel Widdis
  • 8,424
  • 13
  • 41
  • 63
Pavel_K
  • 10,748
  • 13
  • 73
  • 186
  • 4
    The --add-opens CLI option is for the boot layer only. – Alan Bateman Apr 01 '20 at 09:21
  • @AlanBateman Thank you for the answer. That's bad and I think this is an obvious flaw of JPMS. Could you say if I should open feature request or there is no chance it will be implemented? – Pavel_K Apr 01 '20 at 09:52
  • 3
    It's not a flaw or oversight. If you really want to do this then you'll need to open the package to the module in the boot layer that creates the child layer. It can then use `Object.class.getModule().addOpens("java.lang", weldModule)` to open it to the weld module. It's a workaround until Weld is fixed to not hack into non-public methods. – Alan Bateman Apr 01 '20 at 11:05

1 Answers1

1

The answer was given by @AlanBateman

The --add-opens CLI option is for the boot layer only.

Pavel_K
  • 10,748
  • 13
  • 73
  • 186