[RFR] 8205525 : Improve exception messages during manifest parsing of jar archives

Chris Hegarty chris.hegarty at oracle.com
Fri Jul 20 10:24:11 UTC 2018

> On 19 Jul 2018, at 15:42, Sean Mullan <sean.mullan at oracle.com> wrote:
>> ...
> Note that making this a security property for all general cases may have performance implications in certain scenarios since the java.security file will need to be loaded and fully parsed before it can be used. If you are already parsing the java.security file for something else (which is probably the case for jdk.net.includeInExceptions), then it should be fine, but that may not always be the case if this is made into a more general property. Just something to think about …

Good point Sean.

My concern is more along the lines of a whole plethora of specific
properties being added, rather than the implications of such. That
should be scrutinised separately.

What I am suggesting is to generalise the existing property so that
it can, if applicable, be used in other areas. Not that it must be
used in all other areas.  The current proposal, to add a new
property, already has this concern. What I am suggesting does not
cause the file to be parsed any more than it would already.


More information about the core-libs-dev mailing list