From 61dfebf3a3931588ff5d5d4b17dcea60c1e6f197 Mon Sep 17 00:00:00 2001
From: Jean-Noël Rouvignac <jean-noel.rouvignac@forgerock.com>
Date: Fri, 05 Aug 2016 18:35:35 +0000
Subject: [PATCH] Partial OPENDJ-2625 Convert all code that uses JNDI to use the SDK instead
---
opendj-config/src/main/java/org/forgerock/opendj/config/ManagedObjectPathSerializer.java | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/opendj-config/src/main/java/org/forgerock/opendj/config/ManagedObjectPathSerializer.java b/opendj-config/src/main/java/org/forgerock/opendj/config/ManagedObjectPathSerializer.java
index 624109d..9158f12 100644
--- a/opendj-config/src/main/java/org/forgerock/opendj/config/ManagedObjectPathSerializer.java
+++ b/opendj-config/src/main/java/org/forgerock/opendj/config/ManagedObjectPathSerializer.java
@@ -12,6 +12,7 @@
* information: "Portions Copyright [year] [name of copyright owner]".
*
* Copyright 2008-2009 Sun Microsystems, Inc.
+ * Portions Copyright 2016 ForgeRock AS.
*/
package org.forgerock.opendj.config;
@@ -19,8 +20,8 @@
* A strategy for serializing managed object paths.
* <p>
* This interface provides a generic means for serializing managed object paths
- * into application specific forms. For example, a JNDI client would use this
- * interface to construct <code>LdapName</code> objects from a path. Similarly,
+ * into application specific forms. For example, a client would use this
+ * interface to construct {@code DN} objects from a path. Similarly,
* on the server side, a serialization strategy is used to construct
* <code>DN</code> instances from a path.
* <p>
--
Gitblit v1.10.0