Minor confusion on the issues doc

Paul Benedict pbenedict at apache.org
Wed Jun 22 20:39:54 UTC 2016

Since reflection is all about "magic" that transgressing programming
boundaries (such as reading private fields), why isn't letting core
reflection be "jailbreaking" a compelling argument? Minus the enforcement
of the security policy, I think core reflection should allow programs to
roam free like they are today. Introducing module enforcement is way too
strict for the magic that people want with reflection.


On Wed, Jun 22, 2016 at 3:22 PM, Volker Berlin <volker.berlin at goebel-clan.de
> wrote:

> A good question. Will the command line switch -XaddExports be the only
> option to enable the reflection?
> Am 22.06.2016 um 15:03 schrieb David M. Lloyd:
>> The #ReflectionWithoutReadability issue resolution is not indented to the
>> same level as the bullet point for that issue, leading multiple people to
>> ask me how that resolution applies to the whole section.  Is there any way
>> to either fix the indent, or barring that, indicate that the resolution
>> applies to just that issue?
>> http://openjdk.java.net/projects/jigsaw/spec/issues/#ReflectionWithoutReadability

More information about the jpms-spec-observers mailing list