From 0a2e22293f5c36807d89441f9bd8c56ae0b59097 Mon Sep 17 00:00:00 2001
From: matthew_swift <matthew_swift@localhost>
Date: Fri, 16 Nov 2007 16:40:35 +0000
Subject: [PATCH] Update admin framework and dsconfig to support tagging of component definitions as advanced and customizable:
---
opends/resource/admin/admin-cli.xsd | 24 ++++++++++++++++++++++++
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/opends/resource/admin/admin-cli.xsd b/opends/resource/admin/admin-cli.xsd
index 0c7b788..ddf5363 100644
--- a/opends/resource/admin/admin-cli.xsd
+++ b/opends/resource/admin/admin-cli.xsd
@@ -14,6 +14,30 @@
experience.
</xsd:documentation>
</xsd:annotation>
+ <xsd:element name="managed-object">
+ <xsd:annotation>
+ <xsd:documentation>
+ Defines CLI annotations for use with managed object definitions.
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexType>
+ <xsd:attribute name="custom" default="false" type="xsd:boolean">
+ <xsd:annotation>
+ <xsd:documentation>
+ Indicates whether the CLI should refer to this managed
+ object type as "custom" as opposed to "generic". Custom
+ managed object types generally are the top-level type of
+ component (e.g. connection-handler but not
+ ldap-connection-handler) having a non-advanced java-class
+ property. Users create this type of component with a custom
+ implementation class. It is better to refer to these as
+ "custom" since the term "generic" can mislead users (e.g.
+ many users confuse a generic backend as being a JE backend).
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+ </xsd:complexType>
+ </xsd:element>
<xsd:element name="relation">
<xsd:annotation>
<xsd:documentation>
--
Gitblit v1.10.0