Fix for issue OPENDJ-214. Rebranded as OpenDJ and now uses product-name variable.

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

On behalf of Gene (doc team), Some modification for the doc generation.

- [Issue 2007] generic mechanism for using mulitple caches. - [Issue 2049] dsconfig is unable to configure the entry cache.

Tag components as advanced or intended for customization. This relates to issue 1829.

Advanced properties phase 1: tag advanced properties and perform various clean-up to the XML definitions: * clean up typos and any bad grammar in the synopsis/description elements * fixed common errors. For example, there were many places where the synopsis was repeated in the description (the description is only ever used in conjunction with the synopsis). There were also many places where the <adm:user-friendly-name> was being used in property definition description elements to refer to the property name, when it actually refers to the managed object name * split big synopsis (not sure of the plural form - synopsi?) where possible - there were lots of cases where we'd have a big synopsis but no description * overrode properties with sensible default values where appropriate (for example, I provided sensible default values for some of the attribute-type properties in the virtual attribute definitions) * generally made documentation more consistent across the definitions * removed unneeded XML attributes of the form 'mandatory="false"'. Attributes only need to be specified if their value is true as they default to false. Adding redundant attributes just makes the XML harder to read * removed any documentation that referred to the configuration in LDAP related terms (with one exception in the Schema backend). All documentation now refers to other properties using the property names, not their associated LDAP attribute.

Merge branches/temp-admin@3208 onto trunk@3208.

Add support for tagging managed object definitions so that similar types of managed object can be grouped together. Tagging will enable us to automatically generate more user-friendly documentation and administration tools as a result of them being easier to navigate and search. For example, an administration CLI will be able to split the available set of sub-commands into categories, thus making it easier for administrators to find the sub-command that they need. This change is implemented as follows: * provide an extensible way in which tags can be defined: the XML root configuration definition element now supports an "adm:tag-definition" element, which can be used as follows: <adm:tag-definition name="logging"> <adm:synopsis>Logging</adm:synopsis> </adm:tag-definition> * provide a means for tagging managed object definitions with zero or more tags using an "adm:tag" element, which can be used as follows: <adm:tag name="logging"/> * add support to the admin framework APIs for querying a managed object definition's tags * define an initial set of tags and tag managed object definitions appropriately (this is just an initial guess and is likely to change): * logging * replication (incl. mmr) * database (incl. caching) * security (authn and authz) * identity (user account management, pwp, etc) * core (connection handlers, virtual attributes, etc)

Update all of the configuration definition XML files to include the CDDL header and copyright information.

Revert the addition of the copyright header to the configuration definitions because it breaks the XML validation.

Update all of the configuration definition XML files to include the CDDL header and copyright information.

Issue #1560 - Migrate some objects to the new admin framework: - Entry Cache - Account Status Notification Handler - Password Storage Scheme