Thank you for the clarification - I had misunderstood that. So if you ask for access and return false, with an error due to resolution - you just re throw the resolution failure. If there was no resolution error, then IllegalAccessError is returned with no cause.
thank you! Karen > On Nov 1, 2017, at 9:10 PM, David Holmes <[email protected]> wrote: > > <trimming> > > On 2/11/2017 1:01 AM, Karen Kinnear wrote: >> IV Nestmates: >> summary of spec issues: >> 1. Reflection APIs - being discussed in an email with David Holmes >> 2. additional exception information - David Holmes proposed adding a cause >> to IllegalAccessError, >> e.g. as a way to report class not found or verifier error or ... >> Dan H ok with that approach > > This was superceded by Dan S.' JVMS changes to access checking. Resolution > errors are simply rethrown (though I do wrap NCDFE in a new NCDFE so that I > can tell the user it came from nest-host resolution). Nest membership > validation failures result in IllegalAccessErrors (and I add a suitable > message explaining why). > > David > ----- > >> 3. transitive overriding - Karen sent an email >> Dan H will check out - then we can re-review the JVMS overriding description >> with Dan S >> V. MVT binary timing? >> 1-2 weeks >> We are racing stability bug fixing and binary release process >> Remi: The build takes 40 minutes, Running a test takes 4-5 seconds - so >> looking forward to pre-built binary >> Good luck to Bjorn in his new job - we will miss working with you . >> Tobi Ajila will be attending these meetings >> thanks, >> Karen >>
