RFR: 8169993: Class::desiredAssertionStatus should call getClassLoader0 (original) (raw)
David Holmes david.holmes at oracle.com
Sun Nov 20 01:36:42 UTC 2016
- Previous message: RFR: 8169993: Class::desiredAssertionStatus should call getClassLoader0
- Next message: RFR: 8169993: Class::desiredAssertionStatus should call getClassLoader0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 19/11/2016 12:52 AM, Claes Redestad wrote:
Hi,
having classes ask the security manager for permission to access its own class loader when probing for assertion status during class initialization appears pointless.
For our internal JDK classloaders perhaps, but you seem to be extrapolating this to all classloaders and all security manager implementations. This would be an observable change in behaviour so at a minimum should be thoroughly examined before being changed.
David
Bug: https://bugs.openjdk.java.net/browse/JDK-8169993 Webrev: http://cr.openjdk.java.net/~redestad/8169993/webrev.01/
Thanks! /Claes
- Previous message: RFR: 8169993: Class::desiredAssertionStatus should call getClassLoader0
- Next message: RFR: 8169993: Class::desiredAssertionStatus should call getClassLoader0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]