Fix OPENDJ-18 - keystore import failes due to empty PIN Review CR-2353 * Removed constraints on the mandatory presence of a PIN, to allow use of empty PIN. These contraints were implemented in several places : - configuration files : FileBasedKeyManagerProviderConfiguration.xml, PKCS11KeyManagerProviderConfiguration.xml - corresponding provider classes : FileBasedKeyManagerProvider.java, PKCS11KeyManagerProvider.java - setup tool : CertificateManager.java, InstallDS.java (for CLI), SecurityOptionsDialog.java (for GUI) * Removed corresponding admin messages that are no more used in FileBasedKeyManagerProviderCfgDefn.properties and PKCS11KeyManagerProviderCfgDefn.properties * Removed corresponding messages that are no more used in extension.properties and quicksetup.properties * Added management of issue JDK-6879539 that prevents usage of empty PIN. This issue occurs on JDK older than JDK7. * Modified unit tests according to new behavior : FileBasedKeyManagerProviderTestCase.java, CertificateManagerTestCase.java * Added a new utility method StaticUtils#stackTraceContainsCause to check if an exception contains a given cause.

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

Initial doc review on Key Manager Provider Configuration Doc and some copyright changes.

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.