OPENDJ-879 (CR-1603) Add HTTP access log Consolidated common code for the *Logger classes prior to implementing the HTTP access log. AbstractLogger.java: ADDED Pulled up from the *Logger classes. AccessLogger.java, ErrorLogger.java, DebugLogger.java: Now inherit from AbstractLogger. Removed code pulled up into AbstractLogger: initializeErrorLogger(), isConfigurationAddAcceptable(), applyConfigurationAdd(), applyConfigurationChange(), isConfigurationDeleteAcceptable(), applyConfigurationDelete(), isJavaClassAcceptable(), getErrorPublisher(). Added the loggerStorage static variable. Added a ctor + implemented getJavaClassPropertyDefinition() and getStorage(). LoggerConfigManager.java: Replaced the calls to the various initialize*Logger() methods with calling initializeLogger(). Extracted method getLoggerInstance() and used it in all the other methods. LogPublisherConfiguration.xml: Pulled up the declaration of "java-class" property here from sub configurations. AccessLogPublisherConfiguration.xml, DebugLogPublisherConfiguration.xml, ErrorLogPublisherConfiguration.xml, LogPublisherConfiguration.xml: Replaced the declaration of "java-class" property by a property-override. StaticUtils.java: Added close(Collection<Closeable>)

Fixed an issue where a NPE could be thrown when the server processes a mod DN operation with a new superior entry thats in the subtree to be moved. An informative error message is added so the user can fix the mistake. This patch also enables the debug logger to print the cause of an exception message as well as all the stack frames by default. It also removes the deadlock retry configuration parameter from the JE backend configuration definition since deadlocks can no longer occur in the JE backend. Fix for issue 3236

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

Doc changes to Log Publisher Configuration docs and some copyright changes. Thanks to Daniel for the review.

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.

Update configuration definitions to make a few different types of changes: - Add CDDL headers to files that were missing them - Change the syntax for some attributes whose values were supposed to be attribute types into "attribute-type" - Add appropriate base values for some properties with the DN syntax - Change a couple of descriptions that had inaccuracies or copy-and-paste typos - Change a couple of default values to match what's defined in the config file - Provide a couple of overrides for classes in config definitions that extend a parent definition (in particular, override classes for attribute syntax implementations)

Fix the debug log publisher relation with debug targets to use a naming property and mark the naming property (debug-scope) as read-only. Also fix some minor typos in the descriptions.

Fix issue 1884: remove support for operand names in CLI profile.

Add a CLI profile for defining CLI related annotations to managed object and property definitions. The CLI profile defines two annotations at the moment: * the operand name which should be used in sub-command usage help to identify the names of managed objects being added, removed, modified, etc * the list of properties which should be displayed by default in list-xxx sub-commands. For example, when listing connection handlers we can display a summary table that lists the "enabled", "listen-port", and "use-ssl" properties by default Both of these annotations apply only to relation definitions. Existing relations have been updated to include these CLI annotations, although their content is subject to change if we decide that better operand names/default properties exist. These annotations will be used in the forthcoming dsconfig CLI.

Major changes made to the logging framework. It should resolve the following issues: 1. Migrated configuration to the new admin framework. 2. Removed all dependencies on the JDK logger. (Issue 1503) 3. Added option to set the file permissions on all log files. (Issue 202) 4. Added option to write log files asynchronously. 5. Retention and rotation policies are now separate managed objects registered to the Directory Server. 6. Rotation and retention policies are not extensible. 6. Post-rotation actions are not yet implemented in this set of changes. 7. Tools and tasks can now use a custom log publisher that only picks up messages generated by a specific thread or thread group. 8. Debug logger no longer creates a log record object for every message. 9. Configurable Log File Paths (Issue 174) 10. Log Level Support by Category/Severity. This capability is limited for error logger. (Issue 177) 11. Support log file rotation (Issue 188) 12. Sized-based, Time-based rotation policies (Issues 190, 191) 13. Time-based, max size-based, file count-based retention policies (Issues 199, 201, 202) 14. Debug logger configurable via the admin framework (Issue 836)