Fix issue 3734 - Make network group policies extensible. See issue tracker for more details.

Updated the copyright statement to reflect that Sun owns the full copyright on the project files.

Fix for issue 2446 part #1. Add support to the admin framework for specifying one or more "default" managed objects which should be created automatically when a parent managed object is created. The XML mark-up is provided as part of the parent managed object's relation definition as follows (the sample is taken from the LocalDBBackend XML definition): <adm:relation name="local-db-index"> <adm:one-to-many naming-property="attribute"> <adm:default-managed-object name="aci"> <adm:property name="index-type"> <adm:value>presence</adm:value> </adm:property> <adm:property name="attribute"> <adm:value>aci</adm:value> </adm:property> </adm:default-managed-object> <adm:default-managed-object name="entryUUID"> <adm:property name="index-type"> <adm:value>equality</adm:value> </adm:property> <adm:property name="attribute"> <adm:value>entryUUID</adm:value> </adm:property> </adm:default-managed-object> <adm:default-managed-object name="objectClass"> <adm:property name="index-type"> <adm:value>equality</adm:value> </adm:property> <adm:property name="attribute"> <adm:value>objectClass</adm:value> </adm:property> </adm:default-managed-object> </adm:one-to-many> The functionality is implemented on the client-side API in a generic manner so that it is independent of the underlying driver implementation (so the default indexes would be created if we had an offline direct to file driver as well).

Handle special case where the requested managed object is the root configuration.

Remove unnecessary comment accidentally copied from the Driver javadoc.

Partial fix for issue 1451: admin framework constraint and dependency support. This change provides a client-side framework for enforcing arbitrary constraints between managed objects and their properties. This framework enables us to (not exhaustive): 1) support referential integrity between managed objects (required by issue 1449) 2) support dependencies between properties (e.g. if A is true then B is mandatory). This is useful for optional features like SSL configuration 3) support constraints between properties (e.g. integer property A must always be less than integer property B) A subsequent change will provide server-side support.

Fix issue 1734: Admin framework: refactor client APIs This change refactors the client APIs so that it is now possible to easily implement features that require direct access to properties and managed objects (e.g. dependency/constraint enforcement call-backs - issue 1451). Previous to this change an application would have to drill down from the root managed object in order to find the required managed object and its properties. This change is required by issue 1451 (dependency support), which in turn is required by issue 1449 (aggregation support). Description: ------------ This change splits the client API into two: * org.opends.server.admin.client: this contains APIs which client applications such as dsconfig should use to interact with the admin framework * org.opends.server.admin.client.spi: (new package) this contains the APIs which driver implementations (e.g. JNDI driver) should use as a basis for their implementation. This package includes a Driver class which is intended for use by ManagedObject implementations as well as dependency call-backs. In addition, I have refactored the LDAPManagedObject implementation so that code that is likely to be used by other driver implementations is pushed up into an AbstractManagedObject and the Driver base class. Testing: -------- All unit tests pass and basic walk-through of dsconfig interactive mode also works fine.

Minor code cleanup (fixed some comments, added a couple of missing default constructors, and removed example client classes).

Merge admin framework from config-prototype-branch onto trunk.