From efa949b25f472d7e4c39733678d8f0e5229f8201 Mon Sep 17 00:00:00 2001
From: Nicolas Capponi <nicolas.capponi@forgerock.com>
Date: Thu, 26 Dec 2013 15:31:32 +0000
Subject: [PATCH] Checkpoint commit for OPENDJ-1235 : Migrate configuration framework
---
opendj-sdk/opendj-admin/src/main/java/org/opends/server/admin/DefinitionResolver.java | 61 ++++++++++++++----------------
1 files changed, 28 insertions(+), 33 deletions(-)
diff --git a/opendj-sdk/opendj-admin/src/main/java/org/opends/server/admin/DefinitionResolver.java b/opendj-sdk/opendj-admin/src/main/java/org/opends/server/admin/DefinitionResolver.java
index aef966c..2231d7e 100644
--- a/opendj-sdk/opendj-admin/src/main/java/org/opends/server/admin/DefinitionResolver.java
+++ b/opendj-sdk/opendj-admin/src/main/java/org/opends/server/admin/DefinitionResolver.java
@@ -25,47 +25,42 @@
*/
package org.opends.server.admin;
-
-
/**
* This interface is used to determine the "best match" managed object
* definition in a definition hierarchy.
* <p>
- * Managed object definitions, like Java classes, are arranged in an
- * inheritance hierarchy. When managed objects are decoded (e.g. from
- * LDAP entries), the driver implementation is provided with an
- * "expected managed object definition". However, the actual decoded
- * managed object is often an instance of a sub-type of this
- * definition. For example, when decoding a connection handler managed
- * object, the actual type can never be a connection handler because
- * it is an abstract managed object type. Instead, the decoded managed
- * object must be a "concrete" sub-type: an LDAP connection handler or
- * JMX connection handler.
+ * Managed object definitions, like Java classes, are arranged in an inheritance
+ * hierarchy. When managed objects are decoded (e.g. from LDAP entries), the
+ * driver implementation is provided with an
+ * "expected managed object definition". However, the actual decoded managed
+ * object is often an instance of a sub-type of this definition. For example,
+ * when decoding a connection handler managed object, the actual type can never
+ * be a connection handler because it is an abstract managed object type.
+ * Instead, the decoded managed object must be a "concrete" sub-type: an LDAP
+ * connection handler or JMX connection handler.
* <p>
* This resolution process is coordinated by the
- * <code>resolveManagedObjectDefinition</code> method in managed
- * object definitions, where it is passed a
- * <code>DefinitionResolver</code> implementation. The
- * <code>resolveManagedObjectDefinition</code> method takes care of
- * recursively descending through the definition hierarchy and invokes
- * the {@link #matches(AbstractManagedObjectDefinition)} method
- * against each potential sub-type. It is the job of the resolver to
- * indicate whether the provided managed object definition is a
- * candidate definition. For example, the LDAP driver provides a
- * definition resolver which uses the decoded LDAP entry's object
- * classes to determine the final appropriate managed object
+ * <code>resolveManagedObjectDefinition</code> method in managed object
+ * definitions, where it is passed a <code>DefinitionResolver</code>
+ * implementation. The <code>resolveManagedObjectDefinition</code> method takes
+ * care of recursively descending through the definition hierarchy and invokes
+ * the {@link #matches(AbstractManagedObjectDefinition)} method against each
+ * potential sub-type. It is the job of the resolver to indicate whether the
+ * provided managed object definition is a candidate definition. For example,
+ * the LDAP driver provides a definition resolver which uses the decoded LDAP
+ * entry's object classes to determine the final appropriate managed object
* definition.
*/
public interface DefinitionResolver {
- /**
- * Determines whether or not the provided managed object definition matches
- * this resolver's criteria.
- *
- * @param d
- * The managed object definition.
- * @return Returns <code>true</code> if the the provided managed object
- * definition matches this resolver's criteria.
- */
- boolean matches(AbstractManagedObjectDefinition<?, ?> d);
+ /**
+ * Determines whether or not the provided managed object definition matches
+ * this resolver's criteria.
+ *
+ * @param d
+ * The managed object definition.
+ * @return Returns <code>true</code> if the the provided managed object
+ * definition matches this resolver's criteria.
+ */
+ boolean matches(AbstractManagedObjectDefinition<?, ?> d);
}
--
Gitblit v1.10.0