--- old/src/java.naming/share/classes/com/sun/jndi/ldap/EventSupport.java 2019-03-13 15:10:01.000000000 -0400 +++ new/src/java.naming/share/classes/com/sun/jndi/ldap/EventSupport.java 2019-03-13 15:10:00.000000000 -0400 @@ -1,5 +1,5 @@ /* - * Copyright (c) 1999, 2017, Oracle and/or its affiliates. All rights reserved. + * Copyright (c) 1999, 2019, Oracle and/or its affiliates. All rights reserved. * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. * * This code is free software; you can redistribute it and/or modify it @@ -78,20 +78,20 @@ *When a context no longer needs this EventSupport, it should invoke *cleanup() on it. *
- *
* JNDI applications need a way to communicate various preferences * and properties that define the environment in which naming and @@ -138,7 +138,7 @@ * *
* To simplify the task of setting up the environment * required by a JNDI application, @@ -165,7 +165,7 @@ * There are two kinds of JNDI resource files: * provider and application. * - *
* Some directories have the notion of "operational attributes" which are * attributes associated with a directory object for administrative @@ -127,7 +127,7 @@ * In order to retrieve operational attributes, you must name them explicitly. * * - *
* There are certain methods in which the name must resolve to a context * (for example, when searching a single level context). The documentation @@ -138,7 +138,7 @@ * Aside from these methods, there is no requirement that the * named object be a DirContext. * - *
* An {@code Attributes}, {@code SearchControls}, or array object * passed as a parameter to any method will not be modified by the @@ -150,7 +150,7 @@ * the caller. The caller may subsequently modify it; the service * provider will not. * - *
* All the methods in this interface can throw a NamingException or * any of its subclasses. See NamingException and their subclasses --- old/src/java.naming/share/classes/javax/naming/event/EventContext.java 2019-03-13 15:10:11.000000000 -0400 +++ new/src/java.naming/share/classes/javax/naming/event/EventContext.java 2019-03-13 15:10:10.000000000 -0400 @@ -1,5 +1,5 @@ /* - * Copyright (c) 1999, 2013, Oracle and/or its affiliates. All rights reserved. + * Copyright (c) 1999, 2019, Oracle and/or its affiliates. All rights reserved. * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. * * This code is free software; you can redistribute it and/or modify it @@ -34,7 +34,7 @@ * Contains methods for registering/deregistering listeners to be notified of * events fired when objects named in a context changes. * - *
* There are two types of request controls: *
Unless explicitly qualified, the term "request controls" refers to * context request controls. * - *
ldapContext.newInstance(reqCtls)
@@ -97,7 +97,7 @@
* A context instance's request controls are retrieved using
* the method {@code getRequestControls()}.
*
- *
@@ -133,7 +133,7 @@
* A context instance's connection request controls are retrieved using
* the method {@code getConnectControls()}.
*
- * Service Provider Requirements
+ * Service Provider Requirements
*
* A service provider supports connection and context request controls
* in the following ways. Context request controls must be associated on
@@ -143,7 +143,7 @@
* property "java.naming.ldap.control.connect" and pass this environment
* property on to context instances that it creates.
*
- * Response Controls
+ * Response Controls
*
* The method {@code LdapContext.getResponseControls()} is used to
* retrieve the response controls generated by LDAP operations executed
@@ -153,7 +153,7 @@
* To get only the reconnection response controls,
* use {@code reconnect()} followed by {@code getResponseControls()}.
*
- * Parameters
+ * Parameters
*
* A {@code Control[]} array
* passed as a parameter to any method is owned by the caller.