Code Review Request for CR 7167056 - Clarify that BasicPermission names that contain non-wildcard asterisks are not invalid
xuelei.fan at oracle.com
Fri Nov 16 16:01:51 UTC 2012
Looks fine to me.
On 11/16/2012 10:54 PM, Sean Mullan wrote:
> This change affects components in the security and core libs areas.
> This is a minor specification clarification to avoid the use of the terms
> "valid" and "invalid" when describing the syntax for wildcard names in
> java.security.BasicPermission and various subclasses. This could be implied that
> these wildcard names are illegal and the constructors should throw an exception.
> However, they are acceptable, but simply won't be treated as wildcards by the
> implies method when matching against other permissions.
> bug : http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7167056
> webrev: http://cr.openjdk.java.net/~mullan/webrevs/7167056/webrev.00/
More information about the core-libs-dev