Alternative mechanism for reflective access control (#ReflectiveAccessToNonExportedTypes / #AwkwardStrongEncapsulation)

dalibor topic dalibor.topic at
Tue Sep 27 09:27:50 UTC 2016

On 26.09.2016 18:37, Andrew Dinn wrote:
> On 26/09/16 14:19, Alan Bateman wrote:
>> On 26/09/2016 12:36, Andrew Dinn wrote:
>>> :
>>> I addressed that in the text you snipped. The one point of relevance is
>>> that which the original poster asked about:
>>>    -- Why do we need Jigsaw to constrain access control when we can do so
>>> using a security manager?


>> The access checks happen irrespective of whether there is a security
>> manager or not (and of course there is no equivalent at compile time).


> I think those involved in this discussion already know all that you have
> stated here regarding /what/ this project is doing. The present question
> is /why/ is something that it is doing needed.

Paraphrasing, your question seems to be

"If A is true, why does B need to be true?"

whereas Alan's answer seems to be

"A is not universally true."

So it appears that he answered this specific question by providing two 
counter examples:

   1. "no security manager at runtime", and
   2. "no equivalent at compile time"

when A (i.e. being able to constrain access control using a security 
manager) can not be true.

dalibor topic

<> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961

ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher

<> Oracle is committed to developing
practices and products that help protect the environment

More information about the jigsaw-dev mailing list