On 14.07.2016 10:59, Andrew Dinn wrote:
On 13/07/16 17:00, Alan Bateman wrote:
On 13/07/2016 12:47, David M. Lloyd wrote:
Isn't that what this entire thread is about? And also, what the whole
#ReflectiveAccessToNonExportedTypes issue is about?
I think that's a good question, esp as some frameworks allow for
annotations or configuration on non-public types or members. The
`exports dynamic` proposal on the #ReflectiveAccessToNonExportedTypes
thread exports the package at runtime and so allows the slimy
setAccessible(true) to break in. In the very long term then
setAccessible needs to go away of course but I do think non-public types
in non-exported packages is part of the discussion too.
Alan, you previously described setAccessible as a 'sledge hammer that
breaks down the door' and now resort to calling it 'slimy'. Clearly, you
don't think much of this API. However, I'll put aside the
appropriateness of such descriptions in order to challenge the assertion
that it 'needs to go away'.
I believe that this was discussed before at
http://mail.openjdk.java.net/pipermail/jpms-spec-observers/2015-September/000122.html
.
cheers,
dalibor topic
--
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+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
<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment
