On Mon, 14 Dec 2020 19:36:48 GMT, Brent Christian <bchri...@openjdk.org> wrote:
> This is part of an effort in the JDK to replace archaic/non-inclusive words
> with more neutral terms (see JDK-8253315 for details).
>
> Here are the changes covering core libraries code and tests. Terms were
> changed as follows:
> 1. grandfathered -> legacy
> 2. blacklist -> filter or reject
> 3. whitelist -> allow or accept
> 4. master -> coordinator
> 5. slave -> worker
>
> Addressing similar issues in upstream 3rd party code is out of scope of this
> PR. Such changes will be picked up from their upstream sources.
Marked as reviewed by joehw (Reviewer).
src/java.management.rmi/share/classes/javax/management/remote/rmi/RMIConnectorServer.java
line 135:
> 133: * The pattern must be in same format as used in
> 134: * {@link java.io.ObjectInputFilter.Config#createFilter}.
> 135: * It may define an accept-list of permitted classes, a reject-list
> of
should accept-list be allow-list to be consistent with the other two RMI
classes and ObjectInputFilter.Status#ALLOWED?
src/java.management.rmi/share/classes/javax/management/remote/rmi/RMIConnectorServer.java
line 152:
> 150: * <p>
> 151: * Care must be taken when defining such a filter, as defining
> 152: * an accept-list too restrictive or a too-wide reject-list may
would "an allow-list too restrictive or a reject-list too wide" read better?
-------------
PR: https://git.openjdk.java.net/jdk/pull/1771
